When Requistion Line is Sourced to Multiple Purchase Orders, and One PO is Finalized, Reducing Another PO Returns Qty and Pre-encumbrance Back to Requisition But It Cannot Be Sourced. (Doc ID 1669266.1)

Last updated on JANUARY 13, 2017

Applies to:

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

Symptoms

When requisition line is sourced to multiple purchase orders, and one PO is finalized, reducing another PO returns qty and pre-encumbrance back to requisition but it cannot be sourced.

1. Enter a requisition for 100 EA at $1. Run budget check and entry events. This will create a REQPOST for $100
2. Enter a PO based on the requisition in step 1 for 50 EA at $1. Run budget check and entry events. This will create a REQREVERSAL for $50
3. Enter a second PO based on the requisition in step 1 for 50 EA at $1 and click the "Final" checkbox. Run budget check and entry events. This will create a REQREVERSAL for $50 and the kk_liquidation table will have $0.
4. Reduce the PO amount entered in step 2 from 50 EA to 40 EA. Run budget check and entry events. This backs out the REQREVERSAL for $50 and restates it for $40, and the kk_liquidation table now has $10 on it.

The req is now available for sourcing with Open Qty of 10 EA.  However, the req distribution has Commitment Control Close Flag selected (KK_CLOSE_FLAG = Y).  At this point the req cannot be sourced to another PO (even though its available for sourcing).  The req also cannot be reduced from 100ea to 90ea because distrib qty cannot be changed.  Also, the first PO cannot be finalized because req line has already been finalized by the second PO.

 

 

 

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