GL Account Code Systematically Changes when Contract is Added to a Purchase Order (PO)
(Doc ID 2002829.1)
Last updated on DECEMBER 13, 2016
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.
GL Account Code systematically changes between the requisition and the Purchase Order (PO) when buyer adds the contract to the PO.
The issue can be reproduced at will with the following steps:
1. Create requisition from eProcurement
Login as POS1, Create a requisition for Requestor = POS1, Buyer=VP1, Vendor and Item ID = 10032
Change Account that was defaulted
The ePro req account is 212000.
Save and Submit the ePro requisition
Save requisition 0000000034
2. Approve ePro requisition
Login as MGR3 to approve the ePro Req
3. Create PO
Add vendor and press Copy Form <Requisition>
Search for and select the Req and Press Copy to PO
Check the Account in the PO Distribution and notice the Account is the same Account as in the ePro Requisition, 212000.
From the Contract Tab, Add the contract to PO. (Since the BU Setup has <Default Contract on PO> = No, then no contract ID will default)
Therefore, in this test, add the contract created above - 0000000000000000000000066
Press OK to message: "Override Schedule Quantity with Contract Quantity Scheduled on Line (1), Item (10032)? (10200,435)"
4. Save the PO
5. Check the PO Distribution - The Account was changed to 212020
It is expected to have in PO the same account as in the ePro Requisition, 212000.
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