Dear Reader
Let us suppose that we have a requirement, where the inventory item is defined in the master organization but it is not yet attached/assigned to the child organizations, then this can be done via the below API call instead of using the interface tables
EGO_ITEM_PUB.ASSIGN_ITEM_TO_ORG
(
p_api_version => 1.0
, p_init_msg_list => fnd_api.g_true
, p_commit => fnd_api.g_false
, p_inventory_item_id => :p_inventory_item_id
, p_item_number => :p_item_number
, p_organization_id => :p_organization_id
, p_organization_code => :p_organization_code
, p_primary_uom_code => :p_primary_uom_code
, x_return_status => lv_return_status
, x_msg_count => lv_msg_count
);
Let us suppose that we have a requirement, where the inventory item is defined in the master organization but it is not yet attached/assigned to the child organizations, then this can be done via the below API call instead of using the interface tables
EGO_ITEM_PUB.ASSIGN_ITEM_TO_ORG
(
p_api_version => 1.0
, p_init_msg_list => fnd_api.g_true
, p_commit => fnd_api.g_false
, p_inventory_item_id => :p_inventory_item_id
, p_item_number => :p_item_number
, p_organization_id => :p_organization_id
, p_organization_code => :p_organization_code
, p_primary_uom_code => :p_primary_uom_code
, x_return_status => lv_return_status
, x_msg_count => lv_msg_count
);
Cheers
A
This comment has been removed by the author.
ReplyDelete