What to Do When the Regional Localization Global Descriptive Flexfield JG_MTL_SYSTEM_ITEMS is Populated in the Item Master
Last updated on AUGUST 21, 2016
Applies to:Oracle Inventory Management - Version 12.1.3 and later
Information in this document applies to any platform.
Global Descriptive Flexfield (GDF) for Regional Localizations / JG_MTL_SYSTEM_ITEMS Displays in Item Master
When creating a new item, the Global Descriptive Flexfield (GDF) for Regional Localizations / JG_MTL_SYSTEM_ITEMS is populated in the Master Item. This happens when the Master Organization has Accounting Information setup in one of the following Regional Localization countries:
Once the Context Value of the associated country is populated in the master item, that value will be passed to all new child organization items (upon assignment) regardless of the country to which the child organization item belongs. The users will not be able to select the correct Context Value to obtain the correct GDF segments for the child organization item.
Always create the Master Organization with Accounting (Set of Books, Legal Entity, Operating Unit) that is associated with a country that does NOT use the Regional Localizations / JG_MTL_SYSTEM_ITEMS GDF. In this way, the Context Value (GLOBAL_ATTRIBUTE_CATEGORY) remains NULL for the master organization item and no value is passed to the child organization items on assignment. When the GLOBAL_ATTRIBUTE_CATEGORY is set to NULL values, the user is free to select the appropriate Context Value for the country in which the child organization item resides.
Workaround When Master Organization is Linked with Regional Localization Country:
Once the Item Master is setup with accounting that points to a Localization Country and all items are assigned, it is virtually impossible to change, especially if the Master has been used for a period of time.
To overcome the automatic population of the GLOBAL_ATTRIBUTE_CATEGORY when a Master Item is created, the following would need to take place:
a) If the Item is created online, the user would need to open the Global Descriptive Flexfield and NULL out the Context Value before saving the item.
b) If the Item is created via the Import Items interface or EGO_ITEM_PUB API, the user would need to populate the field GLOBAL_ATTRIBUTE_CATEGORY with an exclamation mark (!), to ensure that the attribute is set to NULL values on creation.
Following is an example of how to correct invalid values in GLOBAL_ATTRIBUTE_CATEGORY:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms