Batch Budget Checking Process For Purchase Order Not Updating OPRID_MODIFIED_BY Field
(Doc ID 2231121.1)
Last updated on FEBRUARY 07, 2017
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 9.2 and later
Information in this document applies to any platform.
When a purchase order is budget checked by the batch budget checking process (by a different user than who entered the PO), only fields LAST_DTTM_UPDATE and the PROCESS_INSTANCE are getting updated. The OPRID_MODIFIED_BY fields remains unchanged.
The issue can be reproduced with the following steps:
1. Create a Purchase Order using OPRID1 login
2. Budget check the Purchase Order via the batch process using OPRID2 login
3. Verify the last modified time stamps and oprid.
The issue has the following business impact: Unable to review batch budget details and see who modified
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