The AutoCreate Final Assembly Orders load program creates final assembly orders (discrete jobs) from sales order demand, and links each sales order to the final assembly order supplying it. You can create final assembly orders for ATO configuration items, or standard ATO items.

You can submit the program in specified intervals. For example, to submit the program each day at midnight, specify midnight in the Run Options.

You have the option to create supply for lower level configurations when running the AutoCreate Final Assembly Orders program. This is based on the setting for the Create Lower Level Supply parameter in Oracle Bills of Material. See: Parameters, Oracle Configure to Order Implementation Manual. You have three options:

• No - Creates supply only to the top level ATO item or configuration

• Auto Created Configuration Items only - Creates supply for any lower level configuration generated because of the specific sales order generation.

• Auto Created Configuration Items and ATO Items - Creates supply for all lower level ATO, preconfigured, and autocreated configured items.

The Assemble To Order Mass Load Report is automatically printed after submitting the AutoCreate Final Assembly Orders program. This report lists the sales orders where final assembly orders could not be created

   To autocreate final assembly orders:

1. Navigate to the AutoCreate Final Assembly Orders window. The Parameters window appears.

2. Optionally, select the Sales Order number.

   A discrete job is created for each sales order shipment number associated with the sales order number. If you enter an order number, you cannot enter Offset Days, Load Type, or Organization. If you do not enter an order number, you must enter Offset Days and Load Type.

3. If you have not selected a sales order, enter the number of Offset Days.

   The number of offset days is added to the current date to determine when final assembly orders must be released to the shop floor to be completed by the sales order due date. The final assembly order release date is backwards scheduled using the order from the sales order due date. For example, if the current date is 01-JAN-2007 and you specify 7 offset days, final assembly orders are created that must be released between 01-JAN-2007 and 08-JAN-2007 to meet the due dates of the sales orders they are supplying. Orders that should have been released before the current date are also included.

4. If you have not selected a sales order, select one of the following Load Type options. The Create Lower Level Supply parameter in Oracle Bills of Material must be set correctly to specify the option selected here. See: Parameters, Oracle Configure to Order Implementation Manual

   Configured Orders only: Final assembly orders created from configured sales orders. A configured order begins with a model and options, and then generates or links a configured item using the AutoCreate Configuration Items program in Oracle Bills of Material.

   Non-configured Orders only: Final assembly orders created from sales orders placed directly for ATO items.

   Both configured and non-configured Orders: Final assembly orders created from both configured and non-configured items.

5. If you have not selected a sales order, select one of the following job Statuses: Unreleased, Released, or On Hold. See: Discrete Job Statuses.

6. If you have not selected a sales order, select an Organization.

   If you do not select an Organization, sales order demand across all organizations is examined.

7. Select an accounting Class. This accounting class is the default for the jobs that are created.

   Default accounting classes may be displayed but can be overwritten. See: WIP Accounting Class Defaults, Discrete Parameters, and Discrete Accounting Classes.

8. Choose OK to display the request window.

9. Submit the autocreate request.

Other Sources

• Overview to Supplying Unique Configurations, Oracle Configure To Order Implementation Manual.