Hi,
Try this query:
SELECT T0.[CardCode], T0.[CardName], sum(T1.[LineTotal]) FROM OINV T0 INNER JOIN INV1 T1 ON T0.[DocEntry] = T1.[DocEntry] WHERE T0.[CardCode] = [%0] and T0.[DocDate] between [%1] and [%2] GROUP BY T0.[CardCode], T0.[CardName]
UNION ALL
SELECT T0.[CardCode], T0.[CardName], -sum(T1.[LineTotal]) FROM ORIN T0 INNER JOIN RIN1 T1 ON T0.[DocEntry] = T1.[DocEntry] WHERE T0.[CardCode] = [%0] and T0.[DocDate] between [%1] and [%2] GROUP BY T0.[CardCode], T0.[CardName]
Thank you
Hi Caetano,
Cool..i think the Finite scheduling in the workcenter is the key..i will check that and come back on monday. great Thanks
Regards
Jay
Hi,
Data archiving available from 8.8 version.
Thank you.
Returns factory calendar date for a date |
???
http://wiki.scn.sap.com/wiki/display/BI/Useful+ABAP+Programs+and+Function+Modules+in+SAP+BI
Hosted by: ASUG
Speaker: Peter Drury, ERP Architect, Monsanto Company
More Details: ASUG Events:
Abstract:
Monsanto has deployed the SAP Fiori user experience to improve mobile SAP approvals across a various devices and networks. By providing executives and managers with mobile apps to approve purchase requisitions and other items, the company is increasing employee productivity, shortening approval turnaround times and improving adoption of business processes. Learn about Monsanto’s UX journey including project challenges, implementation details, results, lessons learned and future plans.
Note:If you cannot attend the live broadcast, the webcast will be recorded. The link to the recording will be posted on the ASUG event page and emailed to all registrants
Hi DJ
Sorry, I do not know how you model looks like
here is another example
Start: November 17, 2015 11:00 AM (CT), 12:00 PM (ET), 10:00 AM (MT), 9:00 AM (PT)
End: November 17, 2015 12:00 PM (CT), 1:00 PM (ET), 11:00 AM (MT), 10:00 AM (PT)
Hosted by: ASUG
Speaker: Rich Lazzara, CA Technologies
More Details: ASUG Events
Abstract:
CA Technologies has deployed SAP Fiori user experience across a multiple lines of business including supply chain, human resources and procurement. The result: happy users that are able to approve and track, POs, shopping carts and more while on the move. SAP Fiori is helping CA Technologies to close the gap between user expectations in their personal lives and the ability to complete tasks on any device - from a mobile phone or tablet to a desktop. Attend this webcast to learn best practices for how CA Technologies is deploying a simple and intuitive experience that has delighted their workforce.
Note:If you cannot attend the live broadcast, the webcast will be recorded. The link to the recording will be posted on the ASUG event page and emailed to all registrants
Hi Terry;
FYI: PB Classic versions 12.5.x and 12.6 help files are in the new format and work well on W10. Only PB Classic v12.x uses the old outdated Win32 help format. So if you upgrade to a supported version of PB Classic you will be OK.
HTH
Regards ... Chris
Hi Raghav,
Yes, it works!
Seems to me that the purpose of having HNULL@MTHPROD is to let enable step #3 to include the planning level @MTHPROD as input.
If I want to have multiple YTD calculation, can I reuse the same HNULL@MTHPROD by adding additional input key figures? is there any drawback of doing so?
Thank you.
Yee Ann
HI Anthony,
I can see this query is not answered, hence I posted above.
Here are the details,
We also encountered the same problem. We are unable to publish Lumira components on BI platform using SAP Lumira. It's throwing an error as HDB05408.
We have tried sending an empty request to verify the url, http://localhost:6405/biprws/ it is returing the json {"EntitySets":["infostore]}.
We are unable to understand this message.
Regards
Nagabhushanam
Hi Folks,
I imported a WebIDE Fiori project in my eclipse workspace.
I need to import a custom .js file - stored in location WebContent > model > Config.js into the Component.js
I have declared the Config.js as --> jQuery.sap.declare("namespace.Config");
In the Component.js - when I import the Config.js using jQuery.sap.require("namespace.Config");
I keep getting the ReferenceError ... failed to load .. 'model' is undefined.
Is there any more declaration that needs to be done.
Regards,
Brian
Obrigado pela ajuda, problema resolvido.
Verificamos que a condição ICZF estava sem registro de condição criado (100%) e que o cadastro de cliente estava com tax jurisdiction code incorreto.
Try PB40
In IT 2011, is the clock out P20 locked? Otherwise it should have been processed by P2011 function to pass on to TD20 or ZD20.
Hi Gerd,
Please check if you are you using a Dimension Member Formula to calculate value for account 31811401?
- Raj
Hi Pankaj,
Authorizations for ArchiveLink are also contained in the following Basis roles:
● SAP_BPT_ADMIN
● SAP_BPT_USER
as per Roles for SAP ArchiveLink - ArchiveLink - SAP Library
Please try to add the above roles to your user and let us know if they have the same authorizations for ArchiveLink as SAP_BC_SRV_ARL_USER and SAP_BC_SRV_ARL_ADMIN .
Regards
Arun
Updated: Sept 26, 2015
There a few techniques to achieve Aging reports (calculating duration between two time points) for Service scenarios.
Starting in 1508 there are some key enhancements to the main "Ticket" data source that will allow you to configure Aging reports.
In the Ticket data source you will find the following key figures:
Notice that we include "Today" as a key figure. We included this key figure so you can create a custom calculated key figures where you can use "Today" - "Timepoint" to calculate a duration in Days. The Ticket has standard timepoints that represent specific time stamps that a ticket always goes through in this lifecycle sequence which mirrors the ticket status lifecycle:
1. Posted On (Reported On- when the issue is reported)
2. Created On (sometimes the ticket was created in an external system and via API/migration the ticket has a Created On date after the Reported On date)
3. Initial Review On (when the ticket is set to In Process status)
6. Completed On (when the ticket is set to Completed status)
7. Closed on (when the ticket is set to Closed status -> you can set a completed ticket to closed via the time based workflow engine to prevent any change to the ticket)
Anytime during the above lifecycle after a ticket is in process and prior to a completed ticket can go into:
a. Escalated "state" which the Escalated On timepoint is captured
b. Arrived On (when the technician has arrived on site and has captured an on site arrival time)
c. Resolved On (when the technician/agent has resolved the issue)
d. Changed On (when the ticket was last saved)
Today based age duration is usually relevant only for tickets that are not completed in closed status (you usually measure age for SLA compliance for tickets that are either in open or in process). Thus you will take an extra step to create a restricted key figure on the calculated key figure to only capture an Age duration for tickets in status in process or open to filter out tickets that are completed or closed.
All the above examples only work with duration calculations in days. C4C analytics can only calculate duration between Dates and Integers/Decimals. If you need to calculate age in minutes/seconds, you will need to do the following options:
Option 1: export the data into excel and use the timepoints to calculate the diff of Date/Time in excel
Option 2: use standard age key figures in seconds for a few standard duration scenarios such as
Total Time at Requestor (aggregate duration in seconds that a ticket is in customer action)
Total Time at Processor (aggregate duration in seconds that a ticket is in processor action)
For the standard durations that are in seconds, you can configure a custom key figure to calculate the duration in hours, days, etc... using simple math of Total Time at Processor (seconds) / 3600 = Total Time at Processor (hours)
Option 3: add Integer or Decimal fields to the Ticket, and using workflow engine field update rules to capture each timepoint as a UNIX EPOCH timestamp (these are counter based timestamps that increment from 1970 and beyond).
At a high level do the following
1. Add a decimal extension field to the BO (the decimal field is used to store a UNIX EPOCH time stamp)
2. Create a field update workflow rule that will populate this extension field the EPOCH Time in the extension field (This has been available since 1505 as a key user activity).
3. Add a calculated extension field if you want to calculate a duration between two decimal extension fields
4. Add key figures into analytics to do reporting
Then you can decide how to do durations. Duration can be calculated either in analytics (run an analytical report which will calculate duration when the report is run) or stored as a calculated field on the BO. The former is good for compliance/KPI reporting, such as give me distribution of tickets with a duration, counters on specific durations, etc... The later is good if you need to drive a workflow process from the duration (when the duration exceeds a threshold, then trigger a workflow to do something else)
To calculate duration in the BO as a calculated field, create a calculation rule where you subtract one decimal field from another field (similar to how you would do this in analytics).
Hi Vijay,
In the last screen shot I observed that the background job has status "scheduled". Only background jobs with status "released" are going to run. Could this be the issue, the background job with status "scheduled" will not run? It could be an authorization issue.
Best regards,
Sander
I shall be closing the thread. We opted to handle the requirement using Z development where Task-list master will play a less significant role. Thanks Pete Atkin for adding a different dimension to address the requirement.
