Problems with C4C data in SAC widget

[Karlie_C]

I am working on building a dashboard in SAP SAC, using SAP C4C data. I am trying to find the best way to build a single widget using both “Reported On” (Requestinitalrecieptdatetimecontent) and “Resolved On” (ResolvedOnDateTime) fields. However, every time I do so, the data combines the numbers skewing the data. I have tried creating new columns to reflect the “ReportedOn” and “ResolvedOn” time stamps as values, data still comes back skewed. Any suggestions on how to apply the filters/data appropriately so the numbers reflect TRUE data points?

Update-still having problems. I have also tried using both date fields as you suggested, as dimensions to reflect corresponding measures. No filters-data gets skewed, sometimes by a few thousand values.

[N1kh1l]

kconnell

Could you put some sample data you are getting, it will help us better to understand and answer you. Depending on the dataset sometimes you need to store the Reported on and Resolved On Data separately and then join them with an standalone time dimension to accurately report reported vs resolved in a particular month/year. For e.g. see the sample data below. If you wan to just show created vs closed by month from below datasets its not easy as it will require you to store creation and closed information separately and then join them to a third model which will have a date dimension without any measures.

If you bring the information in a single model, it will difficult to segregate the created and closed information properly

Hope this helps !!

Nikhil

[Karlie_C]

example-for-sap-community.xml

thank you-we are using live data from C4C-ServiceRequestCollectionQuery. attached is snip-its of the data used

[N1kh1l]

kconnell

The attachment is an xml and not readable.

[Karlie_C]

example-for-sap-community-page-1.jpg example-for-sap-community-page-2.jpg

[N1kh1l]

kconnell

Can you try this for at least a month to test

Import created ticket and solved ticket separately. As you have a common Date dimension in SAC model, first load the creation date information. Map the creation date to SAC date and you can create a calculated column with constant 1. Map this calculated column to TicketCreated Measure in SAC.

Repeat the above step but now import ticket solved information by mapping resolved date to SAC date and calculated constant column with 1. Map this to Tickets Resolved measure in SAC

Importing both measure at same time will cause discrepancy in counts. Just try the above for one month say January and see if you are getting the right counts.

Hope this helps !!

Nikhil