Enhancement: OPRID_MODIFIED_BY and LAST_DTTM_UPDATE being updated even when the Purchase Order is not Updated. (Doc ID 1937526.1)

Last updated on JULY 20, 2017

Applies to:

PeopleSoft Enterprise SCM Purchasing - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

When PO_PORECON runs, but does not update any purchase orders, the OPRID_MODIFIED_BY and the LAST_DTTM_UPDATE fields are updated.


The issue can be reproduced at will with the following steps:
Lop in as User A.
Create a PO with 2 lines. Receiving and Matching are required.
Budget Check and Dispatch the PO.
Receive Line 1 in full.
Voucher the Receipt. Budget Check, Match and Post the Voucher.
Query PO_HDR and note the PROCESS_INSTANCE, OPRID_MODIFIED_BY and
LAST_DTTM_UPDATE field values.

Log in as User B.
Create a PO Recon run control by Business Unit and run the process.
Query PO_HDR and note the PROCESS_INSTANCE, OPRID_MODIFIED_BY and
LAST_DTTM_UPDATE field values.

Log in as User A.
Budget Check the PO.
Query PO_HDR and note the PROCESS_INSTANCE, OPRID_MODIFIED_BY and
LAST_DTTM_UPDATE field values.

Log in as User B.
Run PO Recon using the same run control as above.
Query PO_HDR and note the PROCESS_INSTANCE, OPRID_MODIFIED_BY and
LAST_DTTM_UPDATE field values.

The message log shows that 0 Header, Lines, Schedules, Distributions were
closed, yet the PROCESS_INSTANCE, OPRID_MODIFIED_BY and LAST_DTTM_UPDATE
values were updated.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms