Professional Documents
Culture Documents
Issue:
1. When entering a level 2 / transaction level item, the screen changes it to the level 1 parent
sku number
2. When trying to add to the order, it is an invalid sku, and it tries to insert into the
ITEM_COUNTRY table which is not used in SVAT.
Note: The second issue may be caused by the first issue. It should not change the item being
ordered to the parent number.
Data Setup
Select a Valid Location & Supplier site where the ITEM_LOC record exists and the
Source_Method is Supplier.
Navigate As follows:
I then enter the transaction level 2 item which is 1474121, as shown below:
When I exit the field it changes it to the Level 1 item number number but with the correct description of
the transaction level (L2 Sku) number.
From the Apex View, I have driven back SQL Statements for this session, and I found the following was
executed.
INSERT INTO ITEM_COUNTRY(ITEM, COUNTRY_ID) SELECT :B1 , COUNTRY_ID FROM ITEM_COUNTRY
WHERE ITEM = :B2
Not All ITEM_SUPP_COUNTRY Fields Are Not Populated For SVAT Environment (Doc ID
2177855.1)
Solution:
Going forward from Release 14.1 - we have stopped populating these fields for SVAT and use the
ITEM_SUPP_COUNTRY and ITEM_SUPP_COUNTRY_LOC costs directly under an SVAT configuration.
Other information:
The Style / Sku in question was created using the Data Conversion Toolkit.