Bills of Material enables you to automatically deactivate item numbers associated with deactivated configuration orders. You can also deactivate configuration items to remove them from item master reports and screens before you actually purge them from the database. Deactivating a configuration from all organizations also removes it from the match tables, so that new orders will not match to a deactivated configuration. You can deactivate both autocreated and preconfigured ATO items.
When you set up Inventory and Bills of Material, you can define an item status to identify deactivated configuration items. You can use this status to disable the configuration item from all Oracle Manufacturing functions. You would normally specify No for each of the following item attributes for inactive configuration items:
BOM allowed
Build in WIP
Transactable
Stockable
When defining bills of material parameters, specify the item status to use for deactivated configuration items.
You can also set up an item template that can be used to set the status of attributes that are not available in the BOM status form. Typically, deactivated items are not:
Purchased or purchasable
Planned
Forecasted
Customer ordered, or customer orderable
Internal ordered, or internal orderable
Orderable on the Web
See BOM Parameters for more information.
If match is enabled on a model you cannot deactivate its configurations in the context of a single organization. You must go to the master organization and deactivate all configurations. When run in the master organization, the deactivate program confirms that there is no open supply or demand for the configuration in any of the child organizations and then deactivates it in all organizations, including the master, and removes it from the match tables.
The Deactivate concurrent batch program has a parameter that deactivates the base model and all its configurations in that organization. This enables you to stop producing an entire model in a specific organization. If match is enabled for a base model, then the program should be run from the master organization.
The deactivate program can be run for configurations in any organization if the item status attribute is controlled at organization level, and the base model is not using match. If the attributes are controlled at the master level or match is being used, deactivate must be run in the master organization.
You can run the Deactivate Configuration Items concurrent program to automatically deactivate all configuration items that have no open sales orders or on-hand inventory, and whose most recent transaction date is more than the number of days ago you specify. Each deactivated configuration item has its status updated and the item template applied, if specified in the program. Deactivated configurations are removed from the matching tables, so that future configurations cannot match to deactivated items.
To deactivate configuration items
From Bills of Material menu, navigate to the Submit Requests window.
Select Request and select Deactivate Configuration Items.
The Deactivate Concurrent Batch program has following parameters:
Organization ID
The organization you want to deactivate configuration items in. If you specify an item master organization, the configurations is deactivated in this organization and all child organizations. The default is Current organization.
Configuration Item
Deactivates a specific configuration. If this is enabled, all other parameters, except Transacted Days Ago and Apply Item Template are ignored if a value is entered for this parameter.
Base Model Item
If specified, deactivates the model and all its configurations in that organization. This enables you to stop producing an entire model in a specific organization. LOV includes all items assigned to this organization with a BOM item type of model and with the ATO attribute selected.
Option Item
Enabled only if base model is specified. Allows deactivation of only those configurations of a model for which this option is specified as an optional component. When the match is enabled for a bese model and the deactivation program is executed in a child organization, the program deactivates an OSS configuration in that organzation but does not remove the configuration from the match tables. This program does not update the sourcing rules, so they must be manually updated.
Transacted Days Ago
Configuration items with material transactions outside of the time frame are evaluated for deactivation. The default is 90.
Apply Item Template
Enables you to choose an item template to apply to all deactivated configurations. This enables you to control the settings of item attributes not controlled by the BOM item status. Note that the attribute settings in BOM item status will over-ride the settings of the template when the update pending status' program is run.
Note: Always use the deactivation batch program to disable configuration items. Configuration items should not be manually disabled from the Items form.
Note: Deactivate does not update sourcing rules for a configuration. If you deactivate in an organization other then the master organization, you will need to update your sourcing rules manually.
Note: You need to run the Update Pending Status program to actually change the status of the item.
All configuration items that meet the following conditions are selected for deactivation:
No Open Demand: There should not be any open demand for the configuration item (in context organization). Open demand is identified by open sales orders, quotes, and planned orders. Future demand (demand in interface tables) will also count as demand.
No Open Supply: There should not be any supply created for the configuration item in the current organization, that is, in the organization where deactivation process is run. Open supply is identified by discrete jobs, flow schedule, purchase orders, purchase requisitions, and inventory reservations.
In the case of a cancellation or delink, there might be supply created for the configuration item in another organization with no demand associated with it in this organization. In this case, we will deactivate the configuration item in this organization.
Example:
Item C*1 is sourced in organization O1 from organization O2.
There is sales order demand in O1 and planned order demand in O2. A work order for C*1 is created in O2.
Now, the order is canceled and demand for C*1 is removed from organizations O1 and O2.
If the Deactivation process is run in O1, we will find no demand for C*1 in any organization, and no supply in organization O1. Even though there is open supply in organization O2, the item will be deactivated in organization O1. The item will not be deactivated in organization O2.
We will only deactivate the item in the organization where the program is being run. This is because the same item could be enabled in other organizations due to different reasons:
As a result of the Create Configuration process, in the case of a multiorganization configuration.
Enabled manually to be used as a predefined ATO Item in other organizations
If the item needs to be deactivated in all organizations, the Deactivate Configuration Items process needs to be run in all organizations when the item attribute specified as Inactive Status is controlled at the organization level. It should be run in the master organization when the attribute Inactive Status is controlled at the master level.
There should not be any material transactions in current organization for the item ‘n’ days before the Deactivation process is run. ‘n’ is defined by the input parameter ‘Number of Days.’ Hence, if we find any material transactions for the item in the last ‘n’ days, the item will not be deactivated. Material transactions are checked only in the organization in which the program is run.
Items are not deactivated in an organization if there is any on hand in that organization.
For any organization, child organizations may have been set up. If the item is available in the child organization then, that item will not be deactivated in the master organization when the attribute specified as Inactive Status is controlled at the organization level. First, run the program once in each child organization. If the attribute is set at master level, then the item is automatically deactivated in the child organizations before it is deactivated in the master organization.
The items (to be deactivated) BOM and Routing should not be commoned by any other item that is currently active. If it is then item will not be deactivated.
Note: You can delete item information for deactivated configurations from the database, including the bills of material and routings. The ability to delete configuration items is subject to the same deletion constraints that operate for other item types as well.
Related Topics
Deleting Items, Bills, Routings, Components, and Operations.
CTO tables are populated during scheduling of an order and creation of configuration item. When you run a Order Purge program of Order Management, related data of an order inserted in CTO Tables are also purged.
If the profile BOM: Match to Existing Configurations is on, the table bom_ato_ configurations is populated every time a new configuration is created so that if similar configuration is created in future, the configuration item can be matched from this table. If it is not purged of old data, this table can grow very large and might affect the Match and Reserve performance.
This table is purged automatically anytime you deactivate a configuration item through the process described earlier in this chapter. However, it is also possible to remove specific items from the table before it is deactivated by running the Purge Configuration Items concurrent program. You may want to do this on items in which you want to process existing sales orders for the item, but you do not want to take any new sales orders for the item.
To purge specific configurations:
From Bills of Material menu, navigate to the Submit Requests window.
Select single request and select Purge Configuration Items.
Enter the criteria for the items that you want purged from the table:
Item Created Days Ago: Configuration items created earlier then sysdate minus this number are purged
Last Referenced Days ago: Configuration items that were last matched before sysdate minus this number are purged
Base Model: All configurations generated from a specific base model are purged
Option Item: You can optionally use this along with the Base Model parameter. This parameter enables purging of only those configurations of a model for which this option is specified as an optional component
Configuration item: A specific configuration is purged