E1: 49: When Change Bulk Dispatch From Ambient to Standard at Time of Compartment In-Transit Load Confirmation System Creates Two Records in Batch Header (F0011) Table Leaving the First One In Use Status (Doc ID 2987929.1)

Last updated on FEBRUARY 08, 2024

Applies to:

Symptoms

When load confirming a compartment in transit load(CI) at Standard bulk dispatch type, two batch records are created in F0011 tables. One is blank and remains in use and the second one is what correctly represents the transaction.

SETUP:

1. P4101 - Bulk item used
2. P4102 – Branch Plant MCB
3. P49003 – Load Type Revisions – make sure Dispatch Type is set to Volume (V)

Steps:

1. P4210 FGS4 – New created order # 23000191 S4, bulk Item.
2. P4980 - See that the shipment has been correctly routed.
3. P4960 - Build a Compartment In-transit Load (CI) - See Load # 26 is created.
4. P4960 - Approve Compartment In-Transit load type
5. P4960 - Work with load. Confirm Load (P49640) via the row exit
6. In P49640 W49640B form the default bulk dispatch type is Ambient although P4205 is set to ship at standard volume.
7. At this moment, user changes bulk dispatch from Ambient to Standard. Now, we see that Batch Number (96404) field is populated.
8. Click OK (green check mark) to confirm the load. See that load status advance to “50”. All fine.
9. DATABROWSER – F0011 Table. See that there is one record for batch # 96404 with status "In Use" and a second record with batch # 96405 correctly in approved status.
10. DATABROWSER – F0911 – See also in GL table, two records
    
    

Changes

Cause

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