3494743 - Time Entry Replication Issue From FSM To C4C

In scenarios where two time entries are replicated simultaneously from FSM to C4C, you may observe that only one of the entries is successfully replicated, while the other is not—despite both appearing with a successful status in message monitoring.

SAP Cloud for Customer core applications

Pre-requisite:
Collect the message IDs for both time entry payloads from the customer.

Steps:

1. Navigate to the Administrator work center in C4C.

2. Go to Web Service Message Monitoring.

3. Search using the collected message IDs.

4. You will observe that both payloads show a "Successful" status.

5. However, when checking the actual time entries, only one is visible in the system.

C4C has built-in backend validation logic during time entry replication. This logic checks for potential duplicates based on the following parameters:

• date

• start_date_time

• end_date_time

• object_type

• employee_uuid-content

• item_reference_uuid-content

• header_reference_uuid-content

If two time entries have identical values across these parameters, the system treats the second entry as a duplicate, removes it, and fails the replication for that entry—even if the message status appears successful.

To ensure successful replication of time entries from FSM to C4C, make sure there are differences in at least one of the following parameters for each entry:

• Start and end timestamps

• Reference UUIDs (item or header level)

• Object type or employee UUID

Avoid sending identical time entries for the same time frame and user, as this will trigger the duplication check and prevent successful replication of all entries.

FSM to C4C Replication, Time effort, Time Entries, Time Entry Replication, Replication failed, Multiple Time Entries , KBA , LOD-CRM-SRP-CSI , Integration of service ticket with Core systems , LOD-CRM-SRP , Service Request Processing , Problem