E1: 42i: Consign & VMI Outbound Inventory Agreement Credit Orders Update the OIM Agreement Transaction Table (F42i015) Incorrectly When Change the Location/Lot via Sales Order Entry (P42101) (Doc ID 2927920.1)

Last updated on JUNE 12, 2023

Applies to:

Symptoms

For an OIM Sales Order / Credit Order for Consign & VMI, an agreement is selected and the line type inputs as XC line type along with a blank location and lot at Sales Order Entry (P42101). The agreement is select either automatically via the program or manually via the OIM Agreement Selection window.  The order information is now written to the OIM Agreement Transaction Table (F42i015). Once you save the order and go back to make changes, the changes are not written consistently to the F42i015, or are wiped out, or added back into the table incorrectly. The sales order needs to be updated in many cases to ensure the correct serialized (Lot/Serial - LOTN) is being worked with on the order. Often, other fields are updated as well. These changes are not reflected correctly in the F42i015. The orders should maintain changes correctly and/or send an error that the program is unable to make a change to an OIM Agreement sales line directly on the line but must be in the Select OIM Agreement Window. All updates to the sales lines should be written correctly and should not remove previously written records for sales order lines. Additionally, any sales lines  should not allow an update once it has ship confirmed (F4211 SO Detail shows Indicator Field On Hand Updated (SO02) = 1). 

STEPS TO REPRODUCE
==================
1. Create a Sales Consign & VMI OIM Agreement Master & Detail with location and lots.
2. Enter several Sales Orders & Credit Orders for OIM via SO Entry P42101 with a few lines
3. Enter item and quantity and manually select the OIM agreement or let the system automatically assign an agreement (processing option setting in SO Entry OIM Tab)
4. Save the order
5. Check F42i015 OIM Agreement Table for its baseline records created
6. Update the sales order line for a new lot/serial, location, etc.
7. Save the order
8. Check the F42i015 - The data usually writes consistently the first time.
9. Re-inquire on the sales order - The location data and lot may be wiped out or written wrongly from previous update per customer. (For support, updated is correct when updated.)
10. Update the sales order lines again.
11. Check the F42O015 and note several sales order lines are missing from the table that were written originally and the location / lot & serial fields are  not updated with most recent changes.
12. Check the F42O015
13. Ship confirm a sales line or full order
14. Re-inquire on OIM Sales order
15. Update the confirmed lines for location/ lot, etc.
16. Save the order
17. Re-inquire on the order and note the changes were allowed even though the line is ship confirmed.
18. Check the F42i015 and note the table is not updated with data and is missing records.
19. The sales order can be updated any number of times and sometimes the data updates and other times it does not. Also previously wiped out records will can show as re-written in the F42i015.

 
The program should always write the OIM Agreement Transaction table (F42i015) consistently with updates to the fields whether it is lots, locations, quantities, statuses, etc. It should maintain previously written lines. No sales order lines should allow an update to a OIM sales line once it has been ship confirmed and should error.  The program should either error stating any updates to the sales line for quantity, location, lot, etc. are not allowed and should be selected via the OIM Agreement Selection >>Go To in P42101 SO Entry, or it should write consistently in the SO Detail F4211 as well as the F42i015 OIM Agreement Transaction table. Even if the program may function as designed, allowing sales order changes to a line, it should never write wipe out, add back in, or update tables incorrectly.

Cause

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