EPro Requisition Can Be Submitted When The Account Is Still Blank
(Doc ID 2265070.1)
Last updated on NOVEMBER 23, 2019
Applies to:PeopleSoft Enterprise SCM eProcurement - Version 9.2 and later
Information in this document applies to any platform.
When filling in an ePro Req, distribution is created without an account and the warning message 18036,6076 is received. If the user ignores that message, they are still able to save/submit the Requisition. Is that the intended functionality? Customer is expecting that to be an Error message. There is no reasonable way to initiate a combo edit to make the account required. At least one chartfield has be required by the system to use as the anchor to specify all other chartfields that you want to designate as required via combo edits. Usually, that is account?
Customer noted the same behavior on the regular requisition page too. Even though these will eventually fail budget checking, customer would want the user not to be able to save the Req without the chartfield string being "correct" from an edit perspective.
Is there some configuration that can be changed to make this an error?
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