Item Manage SOAPUI API Defaulting L1 To L2 When Not Desired (Doc ID 3046275.1)

Last updated on SEPTEMBER 13, 2024

Applies to:

Symptoms

Problem Description:

We have found that when we add new L1 Item Supp Country records, it is defaulting them to L2 items when not desired.

For example, if we create L1 and 20 L2 items for Country X, then create 6 additional L2 items for Country Y, the system is defaulting the 6 new items to be associated to Country X. Since those 6 items are only meant to be ordered from Country Y, they should not be associated to Country X.

Steps To Reproduce:

1. Set CORESVC_ITEM_CONFIG to not default ITEM_SUPP_COUNTRY from the L1 item to the L2 items.
2. In a SOAP UI Message, Create L1 item with multiple L2 items and have origin country = X
3. Process the message into MFCS and confirm the items are created with ITEM_SUPP_COUNTRY records created for the items for Country X.
4. In a SOAP UI Message, add a new origin country = Y for the L1 item along with multiple new items.
5. Process the message into MFCS and confirm the L1 item has the new ITEM_SUPP_COUNTRY record for origin country = Y.

The multiple new L2 items created in step 4 should be created as well. Note: that the multiple new L2 items created in step 4 are also assigned to Country X...even though there is no plan to source those L2 items from that country and also since the CORESVC_ITEM_CONFIG is marked to not default from the L1 item to the L2 item. The customer believes this is inadequate because "Where the current logic is inadequate is that it is setting up items to be ordered from Supplier/Countries that are not valid for the given L2 item. This can result in the items being placed on purchase orders 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.