Last updated on MARCH 08, 2017
Applies to:Oracle Item Master - Version 12.2 and later
Information in this document applies to any platform.
Lot_divisible_flag is controlled at the master level.
When a NON lot controlled item is created and assigned to child organizations, the lot_divisible_flag is initialized with value 'N'.
This is true whether the items are created and assigned via the application, the API or Standard Import Items.
However, any subsequent update to the child organization item via the API or the Import Items process will set the lot_divisible_flag to NULL values at the organization level. This will set the item up for future API and Interface failures of INV_IOI_MASTER_CHILD_7I when the mismatch between master and child are detected.
NOTE: This behavior does not present if the item is updated in the application.
Also, the issue does not present if the item IS lot controlled and the lot_divisible_flag = Y,
LOT_DIVISIBLE_FLAG will remain populated with N, unless intentionally changed at the master level.
The issue can be reproduced at will with the following steps:
Using either the EGO_ITEM_PUB API or the Import Items Process:
1. Create Item (Non Lot Controlled Item) at Master
Result: Item Created at Master with Lot Divisible Flag as N
2. Assign Item to Child Organization
Result: Item Assigned to the Child Organization with Lot Divisible Flag as N
3. Update any attribute at Child Organization
Lot Divisible Flag Updated to NULL at the Child Organization
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms