My Oracle Support Banner

Getting Differences in POPO008 Report and PORECON Log After Apply Bug 34533325 (Doc ID 2944266.1)

Last updated on AUGUST 08, 2023

Applies to:

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

Symptoms

Getting Differences in POPO008 report and PORECON Log Process After Apply <Bug 34533325>
 

Note: In the Replication Steps, User Details / Company Names / Addresses / Emails / Telephone Numbers / Etc. are fictitious (based upon made-up data used in the Oracle DEMO Environments), any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.


The issue can be reproduced at will with the following steps:
1. Go to Menu > Purchasing > Purchase Orders > Review PO Information > Purchase Orders.
  Search for OLD PO that is already closed: BU = ‘US001’ PO_ID = ‘0000000156’
2. Go to Menu > Purchasing > Purchase Orders > Reconcile POs > Close Purchase Orders. Run PORECON by Business Unit. BU = ‘US003’. Process using PO_POREP job.  
3. POPO008 report listing PO BU = ‘US001’ PO_ID = ‘0000000156’ that is already closed and should not be listed.
  Also in the run control the BU is ‘US003’ and the POPO008 is listing ‘US001’.
 

Changes

 

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.