Position_Data_E and Position_Data Are Not Being Updated After Cloning Position
(Doc ID 2573765.1)
Last updated on JULY 21, 2020
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.2 and later
Information in this document applies to any platform.
Data is not writing to Position_data_E and Position_Data after cloning position.
Instead the Reason Code associated with the current row of the position POSITION_DATA) being cloned is writing to POSITION_DATA_E and POSITION_DATA.
Setup HCM > Common Definitions > Self Service > Workflow Configurations
Setup HCM > Common Definitions > Guided Self Service > Transaction Configuration
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document