Release Date Option
When you start the AutoCreate Configuration Items concurrent program, you can specify Release Offset Days or Flow Schedule start date, to help you minimize the impact of order changes on the planning process. By entering the Release Offset Days, you can create configuration items only for sales orders whose work order or flow schedule must be released within that number of days. In other words, if you specify Release Offset Days = 2, then you only create configuration items for orders whose work order or flow schedule must begin within two days.
The AutoCreate Configuration Item process searches your new orders, finds your orders for assemble-to-order models, and assigns an estimated work order or flow schedule release date to these order lines. Oracle Manufacturing computes the estimated work order or flow schedule release date by offsetting the scheduled ship date by the order lead time (through the workday calendar). Using the lead time information for the model item (as specified in the item master), Oracle Manufacturing calculates order lead time as follows:
fixed lead time + (quantity x variable lead time)
After assigning the estimated work order or flow schedule release dates to the new orders, the AutoCreate Configuration Item process finds all orders whose work order or flow schedule release date is within the Release Offset Days you specified and
automatically creates configuration items for those orders.
Bills of Material automatically defines a new, unique configuration item in the item master and assigns a bill of material and routing. See tables in the Resulting Bills of Material, page 5-35 and Resulting Routings, page 5-38 sections, presenting what will be assigned to the new configuration item.
Note: Do not use the parameter Release Offset Days if you use Oracle Advanced Supply Chain Planning (ASCP) and ATP based on planning output. ASCP does not plan scheduled sales orders for which a
configuration has not yet been created.
Lead Time Calculation Option
Discrete Manufacturing
Bills of Material lets you optionally compute the manufacturing and cumulative lead times for each new configuration item to establish accurate lead times based only on the options chosen. The configuration manufacturing and cumulative lead times are calculated for the configuration item, based on the configuration item routing. This calculation is performed in all organizations where routings are created for the configured item.
For example, the AutoCreate Configuration Item concurrent program could automatically compute fixed and variable lead times for the Laptop Computer
configuration based on the routing steps that were included from the model routing. In this case, the Clean Processor step would contribute to the lead time. So, if the Clean Processor step included one hour of setup time, then it would contribute one hour to the fixed lead time for the configuration.
Note: When your model's routings has no option dependent routing steps (or has a minimum amount of time spent at option dependent steps), you can choose not to calculate lead times for each configuration item. Oracle Manufacturing automatically assigns the model item's lead time information to the new configuration item when you do not specify to calculate lead times for the configuration item.
Flow Manufacturing
Configuration items with flow manufacturing routings inherit the lead times from the model item master in the appropriate manufacturing organization. Flow manufacturing environments do not calculate lead time. However, Total Product Cycle Time is an optional calculation during the AutoCreate Configuration Item process.
Related Topics
Overview of Lead Time Management, page 7-1
Item Numbering Methods
You can choose from four methods to automatically assign item numbers to configuration items:
• Replace model item number with a sequence number
• Replace model item number with the order number/line number
Note: When using the order number/line number option in a multi-level environment, the top level model item will be replaced with the order number/line number. Sub-level models will be replaced with the number/line number/sequence number to differentiate them from the top level configuration.
• Append a sequence to the model number • User defined Configuration Item numbering
For each method, you can specify which segment of the item flexfield you want to either append or replace. For the Order number/line number method, you can specify a delimiter to separate order number and line number.
For example, the following table illustrates the item numbers that would be created for different sales orders and different model item numbers. In this example, you have a two segment item flexfield with '-' as the delimiter, you have chosen '/' as the order number/line number delimiter, the sales order number is 123, the line number is 21, and the next available sequence number is 2001.
Assign Item Numbers
Method Numbering Segment Model Item Number Configuration Item Number Append with Sequence 2 Computer-00 Computer-002001 Replace with Sequence 2 Computer-00 Computer-2001
Replace with order # / line # 2 Computer-00 Computer-123/21 Append with Sequence 1 Computer-00 Computer-2001-00 Replace with Sequence 1 Computer-00 2001-00
Replace with order # / line #
1 Computer-00 123/21-00
You can also generate unique configuration numbers by using the user defined configuration item numbering method. You can develop a numbering scheme that works for your own unique business needs which must return an item number consistent with the existing ATO architecture. The unique configuration number segment returned by the package will be accepted and used to form the configuration item number. The length of the returned number should be 40 or the maximum size specified in the config segment parameter, which ever is greater. If it is longer than forty it will be truncated to 40.
Note: If the System Items flexfield has been configured to use multiple segments, then only the column specified in the BOM parameter Config Segment is available for customized modifications. Modifications to all other segments will be ignored and these segments will be inherited from the ATO model's item flexfield.
Note: Preconfigure the items in the mult-level environment.
Sub-models append automatically with sequence number, and do not depend on the profile.
Caution: When using the Append with Sequence method to assign item numbers to configuration items, be aware that the sequence numbers used can become quite large (6 digits or greater) if you have imported many items. Both the item import and AutoCreate Configuration Items programs use the same counter to assign a sequence number
(MTL_SYSTEM_ITEMS_INTERFACE_S).
Example
When using the autocreate configuration items process, you notice that the sequence number for the item starts with 34,800. You wanted the sequence to begin with 1. You chose the Append with Sequence method.
The Append with Sequence number generates from the
sequence_name: MTL_SYSTEM_ITEMS_INTERFACE_S. View the sequence with the following SQL statement:
select * from all_sequences
where sequence_name = 'MTL_SYSTEM_ITEMS_INTERFACE_S'; Both the item import and autocreate configuration items processes use this sequence number, which ensures uniqueness. In this scenario, you can ensure that your autocreate configuration items sequence starts with 1 by using a user-defined numbering method that allows customization of the ATO numbering methodology. See: BOM
AutoCreate Configuration - User Defined Configuration Item Numbering,
http://www.metalink.oracle.com, MetaLink Note # 1020052.102.
Related Topics
Defining Bills of Material Parameters, page 1-7