Enter Valid PO Business Unit error when Saving a Procurement Contract for a SetID and Business Unit that differs from the User's User Preferences, Default SetID and Business Unit
(Doc ID 1558595.1)
Last updated on FEBRUARY 27, 2023
Applies to:
PeopleSoft Enterprise SCM Purchasing - Version 9.1 and laterInformation in this document applies to any platform.
Symptoms
In 9.1 Procurement Contracts, Error is received when Saving a Procurement Contract for a SetID and Business Unit that differs from the User's User Preferences, Default SetID and Business Unit.
Error
------------
Error: Enter Valid PO Business Unit. (10400, 670)
STEPS TO REPLICATE
--------------------------------
1. By following these steps the issue can be reproduced:
- Business Unit US001 points to SetID = SHARE per Set Control FS_24
- Business Units US005 point to SetID = SHR02 per Set Control FS_24.
2. If my User Preferences is set to default BU = US001/SetID = SHARE
- I can save a Procurement Contract for SetID SHARE/Business Unit = US001.
- I cannot save a Procurement Contract for SetID = SHR02/Business Unit = US005.
3. If my User Preferences is set to default BU = US005/SetID = SHR02:
- I can save a Procurement Contract for SetID SHR02/Business Unit = US005.
- I cannot save a Procurement Contract for SetID = SHARE/Business Unit = US001.
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 |
Cause |
Solution |
References |