Activating a Master Item Does Not Enable Process Execution In Child Organizations

(Doc ID 1584087.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Item Master - Version 12.1.3 and later
Information in this document applies to any platform.
Form: INVIDITM.fmb - Master Items
Package: INV_ITEM_PVT

Symptoms

On release 12.1.3:

When setting Item Status from Inactive to Active in Master Item form (INVIDITM), Process Execution Enabled item attribute does not get enabled in child organizations, whereas the same works fine with Recipe Enabled attribute which has same attribute controls.

Item Status (INVENTORY_ITEM_STATUS_CODE) attribute is controlled at master level.
Process Execution Enabled and Recipe Enabled attributes are controlled at organization level and Status Control is set to Defaults Status for both these status attributes.
On the item status definition for 'Active' status, Process Execution Enabled and Recipe Enabled attributes are both checked (enabled).

-- Expectation
Expect propagating the Process Execution Enabled item attribute from master to child organizations, like it happens with Recipe Enabled attribute.

-- Steps
The issue can be replicated per the below steps:
1. Create an item as Inactive and assign it to a child organization
At this stage, the below OPM attributes are disabled in both the master and child organizations:
Process Execution Enabled
Recipe Enabled
2. Update the Item Status to Active through the Master Item form
3. You are still in Master Item form
Go to Process Manufacturing tab
See Process Execution Enabled and Recipe Enabled are now checked / enabled
4. Go to Organization Item form for the child organization
See Item Status is Inactive there as expected
Go to Process Manufacturing tab
See the following:
Recipe Enabled is now checked / enabled as expected
Process Execution Enabled remains unchecked / disabled

-- Business impact
Due to this issue, users may miss that the item is not enabled for Process Execution in child organizations which may prevent users from operating properly.

Changes

The issue has been reported after applying <Patch:9944329:R12.ITM.C>.
Before applying the patch, the problem was occurring for both the Process Execution Enabled and Recipe Enabled attributes.

Cause

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