Effective Date Issue When Deactivate/Active Operating Unit, ShipTo and Location
(Doc ID 2879202.1)
Last updated on MAY 03, 2023
Applies to:
PeopleSoft Enterprise SCM Purchasing - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Effective Date Issue When Deactivate/Active Operating Unit, ShipTo and Location.
Operating unit/location is deactivated. There are Purchase Orders already in the system with this Operating Unit. A new Operating Unit replaces this Operating Unit and trying to update the existing POs with new Operating Unit for the schedules which are in future.
Error:
Steps to replicate the issue:
1. Go to Operating Unit ‘NEWYORK’. Effective Date: 01/01/1900. Navigation: Menu > Setup Financials/Supply Chain > Common Definitions > Design Chartfields > Define Values > Define ChartField Value
2. Go to ShipTo ‘ US001’. Effective Date: 01/01/1900. Navigation: Menu > Setup Financials/Supply Chain > Product Related > Procurement Options > Purchasing > Ship to Locations
3. Location ‘US001’. Effective Date: 01/01/1900. Navigation: Menu > Setup Financials/Supply Chain > Common Definitions > Location > Setting Up Locations
4. Create Purchase Order with Operating Unit. PO Created on 04/06/2022. Navigation: Menu > Purchasing > Purchase Orders > Add/Update POs.
5. Schedule line 1: Due Date: 04/06/2022 and Schedule line 2: Due Date: 06/15/2022
6. Distribution line 1. Oper Unit = ‘NEWYORK’ and Location = ‘US001’. Distribution Line 2. Oper Unit = ‘NEWYORK’ and Location = ‘US001’
7. Go back to Setup: Deactivate Operating Unit ‘US001’ on 05/01/2022.
8. Deactivate SHIPTO ‘US001’ Effective Date: 05/01/2022
9. Deactivate Location ‘US001’ Effective Date: 05/01/2022
10. Create New Operating Unit ‘ORLANDO’ Effdt:05/02/2022
11. Create New Location ‘NEWLOC’ Effdt:05/02/2022
12. Create New Ship to ‘NEWLOC’ Effdt:05/02/2022
13. Go back to Purchase Order page. For 1st schedule the PO due date 04/06/2022 is older than the new Operating Unit effective date. For Schedule2 on PO the effdate of new Operating Unit/Location /Shipto Location is newer than PO’s due date i.e. 06/15/2022. Line 1 Schedule 1 remains as is.
14. Line Schedule 2 is being updated with new Operating Unit/Location /Shipto Location
15. Getting the message:
'Invalid value -- press the prompt button or hyperlink for a list of valid values (15,11)
The value entered in the field does not match one of the allowable values. You can see the allowable values by pressing the Prompt button or hyperlink associated with field, which is currently focused.'
16. Updating Shipto to ‘NEWLOC’ but it doesn’t take. It is also not appearing in the prompt list.
17. Since new Operating Unit/Shipto/Location are effective before the 2nd schedules due date, expectation is that PO should save with the new Unit/Shipto/Location.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |