SAP Knowledge Base Article - Public

2214353 - Discrepancy Between Report and Application Data With Respect to Time Values - C4C

Symptom

Date and Time values in Reports do not match with the Actual values in Application Data.

Environment

SAP Cloud for Customer

Reproducing the Issue

  1. Go to Business Analytics Work Center.
  2. Go to Design Data Sources View.
  3. Search for the Data Source, for example Ticket Time Points & Contact Party.
  4. Click on Preview.
  5. Check the fields like closing date, completion date etc. These fields will show UTC Time Zone values.
  6. Check the same fields like closing date(local), completion date(local) etc with the suffix (local).These fields will show Local Time Zone values.
  7. In the application data the time values will be displayed based on regional time zone settings made by the user.

Cause

In the backend we always store the date / time zone content in the UTC format.

The reports pick up data from the backend, so the date and time fields will prefeberaly shows in UTC format.

It is the standard behaviour of the report.

Resolution

The conversion of date time fields to local time zone as per personalized settings by the user can be visible, provided that report in question, offers the additional data and time field locally converted. It can be found by adding the field which contains Local name, between brackets.

Example: From 1508, a number of date-time fields have been enabled as local date-time fields in the data source Ticket Time Points & Contact Party.

Local Time enabled fields.png

 

See Also

Refer to the below case document to know how to raise new requirement request.

2571552 - New Requirements in Reporting / Analytics

Keywords

Local Time zone; Reports; UTC Time zone; Date and Time , KBA , created on utc , AP-RC-ANA , C4C, ByD, Travel: Analytics Tools & Frameworks , Product Enhancement

Product

SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions