Enhancement Request - PO's for Consignment Items Need Improved Visibility to Supplier, Should not be Changed Via Purchase Order Acknowledgment (POA)

(Doc ID 1995951.1)

Last updated on DECEMBER 13, 2016

Applies to:

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

Symptoms

Enhancement Request to make consignment items more visible to suppliers.  Issue can arise when a consignment supplier changed the qty and price through the eSupplier portal Purchase Order Acknowledgment (POA). The buyer also accepted the changes.  There's no visibility that the PO or PO line item is a consignment item. It would be helpful if there were an icon on the PO line, the POA for the buyer and on the eSupplier pages - something to indicate the PO is consignment. One better would be to not allow a POA on a Consignment PO/line.

We would like to indicate to the Supplier that the PO or PO lines are related to a consignment item and potentially not allow the supplier to create a POA as changing the price, qty, and/or due date seems to create downstream issues for consignment items.

Example:
The consignment item has been delivered and is on the dock waiting to be received into the non-owned location.  The item is received before the Supplier creates their POA.  The receipt is created with the original PO values/dollars.  The supplier shouldn't be changing the values and should probably be more aware of their consignment items, but there's also no visibility to the fact that the PO /lines are consigned items. This would be confusing to a Supplier - especially when they have a large mix of consigned and non consigned items.  This information would be great to see on the Purchase Order pages as well, rather than buried in the schedule and or distribution.

1) Locate a consignment item
2) Create a PO
3) Dispatch the PO
4) Receive the material into a non-owned location
5) Supplier creates POA and updates Price, qty, and/or due date, not realizing the PO is related to consignment
6) Buyer accepts the POA and PO is updated and dispatched again.
7) Issue the material from inventory
8) A system generated voucher is created causing the voucher to not create with the correct price.

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