PO Lines On RCVRCERC Are Not Sorted As Expected (Doc ID 397437.1)

Last updated on MAY 05, 2016

Applies to:

Oracle Inventory Management - Version: 11.5.9 to 11.5.10
This problem can occur on any platform.
FORM:RCVRCERC.FMB - Enter Receipts GUI
FORM:RCVTXERT.FMB - Enter Receiving Transactions GUI

Symptoms

When performing receipts against a specific Purchase Order or RMA, the order of lines displayed for that order on the Enter Receipts form differs from the order displayed on the PO and Receiving Transactions form.

Steps to reproduce, using a Purchasing Super User responsibility:

1) Create a new standard purchase order with multiple lines, all within the same organization.

Navigation: Purchase Orders -> Purchase Orders
- Type = Standard
- Create three (3) lines.  All lines have Unit Price = 1, Need-By and Promised Dates of same value
- Line 1 has quantity 100, one shipment/distribution for full quantity
- Save the document --> note the purchase order number for subsequent steps (6563 for this example)
- Line 2 has quantity 200, one shipment/distribution for full quantity
- Line 3 has quantity 300, one shipment/distribution for full quantity
- Re-saved the PO. Document status is still Incomplete.
- Now, go back to line 1 and open the shipment.  Split the Line 1 shipment 1 into two separate shipments of quantity 50.  Only one distribution for each shipment is needed.
--- Line 1 Shipment 1 now has quantity 50
--- Line 1 Shipment 2 has the remaining quantity 50
- Save the PO again and approve it.


2) Run the following SQL - notice how the LINE_LOCATION_ID is no longer in sync, due to one line (line 1) having been split into two shipments after all three PO lines were created:

SQL> select pll.promised_date, pll.need_by_date,
  2         pll.po_line_id, pl.line_num,
  3         pll.shipment_num, pll.line_location_id
  4  from   po_line_locations_all pll, po_lines_all pl
  5  where  pll.po_line_id = pl.po_line_id
  6  and    pll.po_header_id in
  7         (select po_header_id
  8          from   po_headers_all
  9          where  segment1 = '&enter_po_number'
 10          and    type_lookup_code = 'STANDARD'
 11          and org_id = &enter_org_id);

PROMISED_ NEED_BY_D PO_LINE_ID   LINE_NUM SHIPMENT_NUM LINE_LOCATION_ID
--------- --------- ---------- ---------- ------------ ----------------
31-AUG-05 31-AUG-05      40551          1            1            53758
31-AUG-05 31-AUG-05      40551          1            2            53761
31-AUG-05 31-AUG-05      40552          2            1            53759
31-AUG-05 31-AUG-05      40553          3            1            53760

 

3) Attempt to receive the purchase order so that the sorting order of the expected shipments can be reviewed.

Navigation: Receiving -> Receipts
- Entered the Purchase Order number and clicked Find --> the items are displayed in the following order:
--- Line 1 Shipment 1 quantity 50 (LINE_LOCATION_ID 53758)
--- Line 2 Shipment 2 quantity 200 (LINE_LOCATION_ID 53759)
--- Line 3 Shipment 3 quantity 300 (LINE_LOCATION_ID 53760)
--- Line 1 Shipment 2 quantity 50 (LINE_LOCATION_ID 53761)


This becomes a functional problem whenever there are dozens of expected receipt shipments to be received and the users have to manually scroll through each of the lines whenever the specific purchase order line number is unknown to the user.

When the expected receipt date and need-by date are the same for all lines/shipments, the expected shipments are sorting by PO_LINE_LOCATION_ID, which is not necessarily in order of the PO line numbers, depending on whether or not the buyer goes back to a previously-created PO line and adds an additional shipment before approving the purchase order.

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