← Back to BlogsTechnical

End-date Person Labor Rate Schedule entries on termination

S
Atul Jain·

Based on current Oracle Fusion PPM functionality, there is no standard feature that automatically end-dates Person Labor Rate Schedule entries when a worker is terminated in Oracle HCM. This requirement would typically require an integration and/or automation process.

Is there a supported method to identify all Person Labor Rate Schedules associated with an employee?

Yes.

Oracle provides the Rate Schedules REST API. For rate schedules of type Employee (Person), the rate lines contain attributes such as:

  • Person Number
  • Person ID
  • Person Name
  • Start Date Active
  • End Date Active
  • Rate

The REST API supports querying rate schedules and their child rate lines, enabling an integration to identify all schedule entries where a specific employee/person number exists.

API documentation

  • Rate Schedules REST Endpoints: /rateSchedules
  • Rates child resource: /rateSchedules/{RateScheduleId}/child/Rates

Is there a supported API, import process, or interface to update the effective end date?

Yes. Oracle supports both REST API and FBDI-based approaches.

REST API (Recommended for automation)

The Rate Schedules REST API supports creating, viewing, updating, and deleting rate schedule lines for Person rate schedules. The rate line object includes the EndDateActive attribute. Therefore, an integration can update the employee's rate line and populate the termination date as the end date.

FBDI / Import Project Rate Schedules

Oracle also provides:

  • Import Project Rate Schedules Process
  • Project Rate Schedule Import Template (FBDI)

These processes support creating and updating project rate schedules and person rate records through interface tables and scheduled processes. For a real-time or near real-time termination process, REST is generally a better fit than FBDI.

Limitations and recommended approach

  • Employee termination occurs in Oracle HCM.
  • An HCM integration event (OIC, HDL extract, REST polling, Atom feed, etc.) identifies terminated workers.
  • The integration retrieves all Person Rate Schedule lines associated with the employee.
  • The integration updates EndDateActive to the employee termination date.
  • Optionally, exclude already end-dated records.

This leverages delivered APIs and avoids direct database manipulation.

Considerations

An employee may exist in multiple Person Labor Rate Schedules, so the integration must search across all applicable schedules rather than assuming a single schedule.

Historical transactions are not automatically re-rated simply because the rate line is end-dated. Existing billing or cost processing results should be evaluated separately.

Security privileges must allow the integration user to read and update project rate schedules.

Is similar functionality available as a standard Oracle feature?

No standard delivered feature automatically synchronizes employee termination status in HCM with Person Labor Rate Schedule end dates in PPM.

Oracle provides

  • HCM worker termination processing
  • PPM Rate Schedule maintenance
  • REST APIs and FBDI interfaces for rate management

However, Oracle does not provide an out-of-the-box process that automatically updates Person Labor Rate Schedule entries when a worker becomes inactive or terminated. A custom integration or orchestration (typically Oracle Integration Cloud) is generally required.

Oracle Documentation References

  • Manage Rates for Rate Schedules (REST API): Describes Person Rate Schedule lines, including StartDateActive and EndDateActive attributes, and create/update capabilities.
  • Rate Schedules REST Endpoints: Documents the Rate Schedules REST resources used to manage project rate schedules.
  • Import Project Rate Schedules Process: Describes FBDI-based importing and updating of rate schedules and person rates.
  • Import Project Rate Schedules and Overrides (FBDI): Documents the supported import framework and interface objects.
← Back to Blogs