Differences Between Position Management Tables PS_POSITION_DATA_E and PS_POSITION_DATA (Doc ID 2677223.1)

Last updated on MAY 15, 2023

Applies to:

Goal

Fluid Position Management uses PS_POSITION_DATA_E record/table
Classic Mode Position Data uses PS_POSITION_DATA record/table

These 2 records will need to co-exist even after enabling Fluid Position Management.

The tables may go out-of-sync for a variety of reasons.

Examples:
- When a position is created using Fluid Position Management, for the period before the position is approved
- If the approval process fails during the update to PS_POSITION_DATA will not occur
- If the approval fails for any other reason (such as incumbents couldn't be updated)

If the tables are found to be out-of-sync, how to address the out-of-sync problem?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.