Symptom
When using the API_MANAGE_WORKFORCE_TIMESHEET OData V2 API, the following scenarios are observed where the API fails silently:
- Scenario 1: $orderby is silently ignored. Requests containing $orderby on TimeSheetEntryCollection return results without ordering, with no error returned to the caller.
- Scenario 2: The $filter operators gt (greater than) and lt (less than) on TimeSheetDate are either ignored or return incorrect results. Only EQ, GE, LE, and BT produce correct behaviour.
- Scenario 3: $inlinecount=allpages is silently ignored. The __count property is absent from the response body even when explicitly requested.
- Scenario 4: A POST request submitted without the TimeSheetOperation field returns HTTP 201 with no error message, but no timesheet entry is created or modified (silent failure).
Read more...
Environment
SAP S/4HANA Cloud Public Edition.
Product
Keywords
API_MANAGE_WORKFORCE_TIMESHEET, OData V2, $orderby ignored, $filter gt lt, $inlinecount allpages, __count missing, TimeSheetOperation, silent failure, HTTP 201, POST no entry created, TimeSheetDataFields, TimeSheetEntryCollection, mandatory fields, TimeSheetIsReleasedOnSave, TimeSheetPredecessorRecord, RecordedQuantity, HoursUnitOfMeasure, PurchaseOrder, contingent worker, reversal, correction, supported capabilities, CA-TS-S4, CATS, HCM, SAP S/4HANA Cloud Public Edition. , KBA , CA-TS-S4 , Cross Application Timesheet in S/4HANA , Bug Filed
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview