Incorrect Supplier Default UOM Selected Into Purchase Order When Sourcing Inventory Item From Requisition After Applying Bug 29011562 from PUM 32 (Doc ID 2721273.1)

Last updated on FEBRUARY 23, 2024

Applies to:

Symptoms

After upgrading from PUM 29 to PUM 34, Requisitions are sourcing to Purchase Orders in the wrong UOM, by not converting to the supplier's default ordering UOM. This is causing a large number of our orders to be rejected by the supplier resulting in delays in receiving crucial supplies.

Steps to reproduce the issue:
1.In Purchasing Item Attributes:
.in Purchasing Controls, unchecked Contract Required
.in Item Supplier, unchecked Accept Any UOM
.in Item Supplier UOM:
  -Set up BOX as Default UOM, Conversion Rate Type = Override, Rate 10.0000
  -Set up EA as another UOM
2.In Procurement Contract:
  -checked Auto Default
  -set to Status Approve
  -in Pricing Info, unchecked Use Contract Base Price
3.In Req Loader Defaults:
  -Under Req Loader Options
    -Check Consolidate With Other Reqs
    -ChecK Default Contract on Req
4.In PO BU Definition:
   - When Contract is Specified on Req, checked Allow Req Consolidation
5.Set up Item Replenishment for the Item and IN BU
6.Run Replenishment for IN BU US010
7.confirm replenishment requests generated for the IN BU and inventory item
under Manage Replenishment Requests
8.Run Req Loader for System Source BIN, Req Loader BU US010
9.Open req and verify below:
  a.Contract is populated in req line (per Req Loader Defaults)
  b.Consolidate Flag is checked in req line Sourcing tab
10.Run PO Autosource to source req from Req Loader into a PO
11.Open resulting PO, see PO line incorrectly got req uom EA instead of supplier default uom BOX [issue replicated]

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.