Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
For more information, please refer to this announcement explaining best practices for getting answers to questions.
timeRecordEventRequests create overtime entry with the wrong unit of measure
Summary:
HCM timeRecordEventRequests api seemed always creating time record with the default units?
Content (please ensure you mask any confidential information):
Sample payload:
{ "processInline": "Y", "processMode": "TIME_ENTER", "timeRecordEvent": [ { "startTime": "2025-03-02T00:00:00.000Z", "stopTime": "2025-03-02T00:00:00.000Z", "reporterIdType": "PERSON", "reporterId": "23456", "assignmentNumber": "E66789", "comment": "Missing entry due to clock down", "measure": "1", "operationType": "ADD", "timeRecordEventAttribute": [ { "attributeName": "PayrollTimeType", "attributeValue": "PT Over 4 Hours" } ] } ]}
The unit of measure associated with this type of overtime entry should be 'unit' .
{
"DisplayValue": "PT Over 4 Hours",
"UnitOfMeasure": "UN",
"IsAbsenceTypeFlag": "false",
"Code": "30000056789"
},
But the time record crated with the above API having the uom as 'hours' rather than 'hours'.