EHR: Questions Related to Implementation Issues Fluid Position Management
(Doc ID 2517737.1)
Last updated on SEPTEMBER 13, 2023
Applies to:
PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Development said the following about Position Management fluid page functionality-
====================================================
The classic pages for managing positions will be de-supported December 2020. We will not be adding any additional functionality to the classic pages moving forward but will continue bug fixes through December 2020.
All new enhancements will only be made to the fluid pages of position management.
Goal
Questions for Development as it relates to Fluid Position Management
Fluid Position Management was delivered in HCM 9.2 PUM Image 29; there is an alternate table structure POSITION_DATA_E instead of POSITION_DATA
Qn1: Is there some strategy for customers to start using Fluid PM when they are currently using PM in Classic or can they use both (Classic and Fluid)?
Qn2: Is it necessary to copy data from the Classic Table to the Fluid Table?
Qn3: If so are there any scripts delivered to help with this and/or any guidance/instructions on how to re-configure the system data and/or user security to enable us to cut over to the New Fluid System?
Qn4: What affect if customer changes to Fluid Position Management will this have on Position Data updates to Job Data, if any?
Qn5: Does the POS_SYNC_FLU (Sync Fluid Position Data) process need to be scheduled regularly or it is a One time Process to load the data?
Qn6: How Long Will the Classic Pages be Supported for Managing Positions?
Solution
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
| Goal |
| Solution |
| References |