My Oracle Support Banner

Printing Incorrect Purchase Order Details From Different Operating Unit or Print Out is Blank (Doc ID 579617.1)

Last updated on JANUARY 16, 2020

Applies to:

Oracle Purchasing - Version 11.5.10.2 to 11.5.10.4 [Release 11.5]
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

When approving a Purchase Order (PO) from the worklist in another operating unit, if the other operating unit has a PO with the same number when the concurrent request to Print (poxppo) is spawned the wrong PO is printed. PO Details from the operating unit the Approver is logged in as, is printed rather than the PO from the Operating Unit where the PO was submitted for approval from.

Another symptom was the print out on the printer was blank and in reviewing the print job log file there was  no org_id listed.

EXPECTED BEHAVIOR
-----------------------------------
Expect that no matter what Operating Unit the PO is approved from, the correct
PO should be printed.

STEPS TO REPRODUCE THE PROBLEM:
-------------------------------
1. Purchasing > Buyer in the Operating Unit A responsibility creates a PO which
requires approval by the Purchasing Manager. Select print in the approval window
and "Approve".

2. The purchasing manger is working in Operating Unit B and gets his notification
of approval. The manager goes to his worklist and selects the PO and approves.

3. POXPPO is automatically spawned and from View Requests we can see the PO has the same po number but the PO details for the Operating Unit B is in the output.

To replicate this issue the following conditions must be met:
>The same PO number resides in both Operating Units.
>The approver is logged in and approves from the Operating Unit that the PO was not created in.

4. Additionally the log file should contain and pass the correct org_id. For example:

POXPPO module: Print Purchase Orders
+---------------------------------------------------------------------------+
Current system time is 20-MAR-2009 13:48:01
+---------------------------------------------------------------------------+
+-----------------------------
| Starting concurrent program execution...
+-----------------------------

Arguments
------------
P_REPORT_TYPE='R'
P_TEST_FLAG='N'
P_PO_NUM_FROM='21550'
P_PO_NUM_TO='21550'
P_USER_ID='1007881'
P_QTY_PRECISION='0'
P_BLANKET_LINES='Y'
P_PRINT_RELEASES='N'
ORG_ID='204'

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.