PODISP Job not Updating ACTIVITY_DATE, LAST_DTTM_UPDATE or OPRID_MODIFIED_BY
(Doc ID 2077583.1)
Last updated on DECEMBER 09, 2019
Applies to:
PeopleSoft Enterprise SCM Purchasing - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
When run the PODISP Job, on PO_HDR the values for ACTIVITY_DATE, LAST_DTTM_UPDATE and OPRID_MODIFIED_BY should be updated when dispatch the PO.
Steps
----------------
1. Identify a purchase order that is approved.
Query the PO_HDR and note the values for ACTIVITY_DATE, LAST_DTTM_UPDATE and OPRID_MODIFIED_BY
2. Log in as VP2
3. Create a PO Dispatch run control The process is Success
4. Query PO_HDR again and check the field values. The PO_STATUS is now Dispatched, but the other fields did not update.
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 |