With Contributing Author: Simona Sutu

 

As per current behavior (through 12.2.13) the below validations happen in all organizations (active and inactive) when item attributes are updated using Item Open Interface (INCOIN), EGO_ITEM_PUB API,  Import Catalog Items and Web ADI (EGO Spreadsheet Java Concurrent Program – EGOIJAVA).

  1.  Master controlled attributes should be identical across all organizations
  2.  Other validations on Organization controlled attributes (For ex: Valid buyer, Dependent validations on lot attributes, etc. )
  3.  Non Nullable attributes should have their default values

A new behavior was introduced in 12.2.14. With this changed behavior, item updates will no longer be validating the attributes in inactive organizations.

This change will be valid for all the Item update flows – Master Items, Product Hub Item Overview, PL/SQL APIs (EGO_ITEM_PUB / INV_ITEM_PUB), Product Hub Item Update from Excel, Item Open Interface (INCOIN) and Import Catalog Items (EGOIMDCP).

If an inactive organization is activated again by removing “Date To” in Organization definition, user will have to validate all the items in this organization by following the steps in the earlier section of the document – Approach to resolve the inconsistent attributes or detailed steps on (Doc ID 2943884.1) – How To Validate All Item Attributes (Master And Organization Controlled) To Ensure Consistency Using Item Open Interface (INCOIN).

 

For more details reference note: Master Child Conflict On Attributes — Validations Happening In Inactive Organizations ? (Doc ID 2366062.1)