SUPP_PACK_SIZE Is Not Updated Correctly for Purchase Orders Created from a What If Allocation (Doc ID 2192817.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Retail Allocation - Version 14.0 and later
Information in this document applies to any platform.

Symptoms

When a purchase order is created with What-if allocation functionality, and when using an item with SUPP_PACK_SIZE not equal to 1, the SUPP_PACK_SIZE value of the purchase order in the ORDSKU table is still defaulted to 1.


Steps to Reproduce:

  1. Find an item with the following attributes: ITEM_MASTER.STANDARD_UOM is "EA" (Each); ITEM_SUPP_COUNTRY.SUPP_PACK_SIZE not equal to 1; ITEM_SUPP_COUNTRY.DEFAULT_UOP is "C" (Case).
  2. Create a What-if Allocation with the item from the previous step.
  3. Fill out the necessary details for the allocation and click the "Calculate" button.
  4. Go to "Manage Allocation" and reopen the previously created what-if allocation.
  5. Click the "What-if Summary" button.
  6. Set the PO type to Cross-dock, tick the checkbox beside the item, and select "Each" as the PO multiple.
  7. Click Apply.
  8. Click Preview Purchase Order (PO).
  9. Click Create PO.
  10. Open the created purchase order in Retail Merchandising System (RMS).
  11. Click the "Item" button from the PO Header Maintenance screen.
  12. Notice that the Order Qty is the same as the allocation qty, but the PO Multiple (Allocation Tool) and Unit of Purchase (RMS) are different.
  13. The ORDSKU data of the purchase order has a SUPP_PACK_SIZE = 1.

 

Changes

 

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