ETL 9.2 Third Party Schedule AE Processing
(Doc ID 2712856.1)
Last updated on SEPTEMBER 27, 2020
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
- When manually creating schedules - punches/shifts are defined at the schedule definition or separately at the shift creation levels. Punch schedule definitions cannot be saved without shift population. How to address this constraint when needing a schedule definition to accommodate a third party schedule and the shift/punch details in that schedule cannot be anticipated in advance?
- Is there a minimum or maximum constraint on what can be accepted via third party schedule? In other words, could I not test with a single day to determine if my import specs are acceptable?
- Which SCHED_SOURCE is correct for a third party imported workforce management schedule?
- According to the PeopleBooks, PS_SCH_MNG_SCH_TBL is getting populated when SCH_EXTVALID.AE completes, and at the same time the data is getting moved to PS_SCH_ADHOC_DTL. Is there some other mechanism that is also supposed to populate this in advance?
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