Shipment Supply Data Exists After Full Correction to Over Received ASN (Data Fix)
(Doc ID 1204303.1)
Last updated on JUNE 03, 2024
Applies to:
Oracle Inventory Management - Version 11.5.10 and laterInformation in this document applies to any platform.
Form:INVDVDSD.FMB - View Item Supply/Demand Information
Report:CSTRITVR.RDF - Intransit Value Report
Symptoms
Intransit Shipments are still visible even though the associated Purchase Order has been Closed.
This occurs after a negative correction is performed against an ASN that was over-received.
Steps
The issue can be reproduced at will with the following steps:
1) Navigate to Receipt Transaction Summary form
For Receipt Number <receipt number> / PO Number <po number> see the following transactions
Receive Quantity = 120
Receive Quantity = 350
Correct Quantity = -350
Deliver Quantity = 120
2) Navigate to Purchase Order Summary Shipments form
See for PO Number <po number>
Quantity = 120
Quantity Due = 0
Quantity Received = 120
3) Navigate to Supply/Demand Detail form INVDVDSD
for Item , still see 1 record
Date Supply / Demand Type Identifier Quantity
28-OCT-2014 Intransit Shipment <receipt number> 350
4) Rcv11i output from <Note 402245.1> shows
RCV_SHIPMENT_HEADERS
Shipment_Header_Id <shipment header>
Receipt_Source_Code VENDOR
Shipment_Num <shipment num>
Receipt_Num <receipt num>
Asn_Type ASN
Ship_To_Org_Id <org_id>
RCV_SHIPMENT_LINES
Shipment_Line_Id <shipment_line_id>
Shipment_Header_Id <shipment_header_id>
Quantity_Shipped 120
Quantity_Received 120
Item_Id <item_id>
Shipment_Line_Status_Code FULLY RECEIVED
Source_Document_Code PO
Po_Header_Id <po_header_id>
Po_Line_Location_Id <location_id>
To_Organization_Id <organization_id>
Asn_Line_Flag Y
Transaction_Id | Transaction_Type | Transaction_Date | Quantity | Unit_Of_Measure | Shipment_Header_Id | Destination_Type_Code | Parent_Transaction_Id | Po_Header_Id |
<transaction_id> | RECEIVE | 10-21-2014 | 120 | DB | <shipment_header_id> | RECEIVING | <parent_transaction_id> | <po_header_id> |
<transaction_id> | RECEIVE | 10-21-2014 | 350 | DB | <shipment_header_id> | RECEIVING | <parent_transaction_id> | <po_header_id> |
<transaction_id> | CORRECT | 10-21-2014 | -350 | DB | <shipment_header_id> | RECEIVING | <parent_transaction_id> | <po_header_id> |
<transaction_id> | DELIVER | 10-21-2014 | 120 | DB | <shipment_header_id> | INVENTORY | <parent_transaction_id> | <po_header_id> |
MTL_SUPPLY
Supply_Type_Code SHIPMENT
Supply_Source_Id <supply_source_id>
Po_Header_Id <po_header_id>
Po_Line_Location_Id <location_id>
Shipment_Header_Id <shipment_header_id>
Shipment_Line_Id <shipment_line_id>
Rcv_Transaction_Id
Item_Id <item_id>
Quantity 350
Unit_Of_Measure DB
To_Organization_Id <to_org_id>
PO_LINE_LOCATIONS_ALL
Line_Location_Id <line_location_id>
Po_Header_Id <po_header_id>
Quantity 120
Quantity_Received 120
Qty_Rcv_Tolerance 5
Qty_Rcv_Exception_Code NONE
Quantity_Shipped 350
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |