This chapter covers the following topics:
The Configure-to-Order process (CTO) is a cross-modular process that enables you to select options in the sales order window to define a possibly unique item, build the item using Oracle's Manufacturing Applications Suite, and continue processing the item as if it were a standard item through the shipping and invoicing activities. This section defines the CTO process as well as the related processes of Assemble-to-Order (ATO), Pick-to-Order (PTO) and Kits. It provides an overview of how this business process is implemented, the workflow processes that support it, and the required setup.
Oracle Configure to Order Process Manual
The CTO process goes through these basic steps:
CTO Process
First, you navigate to the Sales Order window and enters an ATO model as an item. Depending on your setup, you can use the Configurator or Options window to select options. The system adds the options to the sales order as new lines. The system creates a new item and a new bill of material (if necessary) and then communicates with the manufacturing applications so that the item is built. The completed item is then shipped to the customer and an invoice is generated.
Note: These steps are described in detail later in this chapter.
The PTO process is similar to the CTO process except that all options are finished goods that are stocked in the warehouse, so no assembly operation is required. These are the basic steps for the PTO process.
PTO Process
The ATO process is also similar to the CTO process. The item is built based on the demand from the customer order. However, for an ATO item the customer cannot select options. Therefore the item and the bill of material are already defined. You enter an ATO item and it follows this process.
ATO Process
Finally, the kit process is similar to the CTO process, because a kit item has a bill of material structure and the included items are added as lines to the sales order. You enter a Kit item and it follows this process.
Kit Process
All models, option classes, options, and kits must be defined in Oracle Inventory and they must have their attributes set appropriately. Bills of material must be created for all models, option classes, and ATO items. Finally, the workflow processes must be correctly assigned to the transaction types.
The key attributes that control the processing of the CTO and related processes are on the Order Management tab in the Item setup window. The flag Assemble to Order should be selected for CTO items and ATO items. The Pick Components flag should be selected for PTO models. Other attributes are also important. The best way to create your items is to copy them from the following seeded templates:
ATO Model (for the Configure-to-Order process)
ATO Option Class
ATO Item
PTO Model
PTO Option Class
Kit
Bills of Material (BOMs) must be created for your models, option classes, ATO items, and kits. For models and option classes, some key attributes are defined on the Order Entry tab of the BOM window. The optional flag is checked if an option class or option is not required. If an option class is required then the configuration must include at least one of the options from the class. The option class that is not optional is called a mandatory option class. If an option is not optional it is considered an included item and it not shown as an available selection in the Configurator or option selection window. It is automatically added to the sales order. At least one item should be optional within the structure of an ATO model or a PTO model. No items can be optional in a kit. Another important attribute of the BOM is the required for revenue flag on the shipping tab. This flag is only enabled in PTO configurations for included items. If the flag is checked, then the option class or model which is the parent of the item will not be invoiced until this item has been shipped.
See: Oracle Bill of Material User's Guide
The transaction type for an order which will include CTO items must have at least two line workflow processes associated with it - one for the model, options and option classes and one for the configured item. In the Assign Line Flows window, the item type of Configuration must be specified for the workflow of the configured item. For ATO models, ATO items, PTO models, options, option classes, and kits the seeded generic line flow can be used for all the item types.
You can configure these profiles with the Configurator or through the Options Window within Order Management. In order to use the Configurator or Options Window in Order Management, the profile OM: Use Configurator must be set.
Optional profile settings for Configurations include:
OM: Charges for Included Items
If set to Yes, Order Management calculates and returns charges for included items. Keep in mind that even if the profile is set to Yes the included item is not priced. This calculates only the charges.
OM: Configuration Quick Save
If set to Yes, Oracle Order Management creates option class order lines without applying certain business functions. This is applicable only during initial order entry when the options are selected via the options window or configurator. It does not apply to update / booking / scheduling or for lines imported via Order import OR the Process order API. The option class order lines are not subject to defaulting, processing constraints, or taxation.
OM: Copy Model DFF to Child Lines
This profile option enables copying Additional Line Information flexfield data to the child lines from the model line. Context sensitive flexfields are usually desired, so the default value is No. You must set this parameter to Yes in order for the values to copy.
OM: Item View Method
This profile is used to decide the Options Window LOV item display format for models. This can be set with the following values: Description, Description without indentation, Concatenated segment values, and Concatenated segment values without indentation. This can be set at all four levels.
OM: Show Line Details
This profile option determines whether the line details of a model are displayed in the Sales Orders window.
This section will describe to steps required to order, ship and invoice a CTO item from the Order Management point of view including:
Entering the item - OM
Selecting the options - CZ or OM
Creation of a configured item - BOM
Creation of a work order - WIP
Manufacturing - WIP
Shipping and invoicing - SHP
Associated workflows - WF
Enter your item.
Enter an ATO model as the item number.
Click Configurator.
If the profile option, OM: Use Configurator is set to Yes and the Configurator product is installed, the Oracle Configurator window appears after when clicking the Configurator button.
Oracle Configurator window
Select your options.
The folders on the left side are the model and its option classes. For the selected option class (in this example the RAM option class), the available options are in the top box on the right. The options are selected by checking the box to the left of the item name. The options and option classes which are selected are in the bottom right. Required option classes which have no selections are indicated by a red asterisk on the folder icon.
Note: Oracle Configurator is a powerful tool that enables you to create complex rules for configurations and then validate those rules when you create configurations. It is completely integrated with Order Management. See: Oracle Configurator Developer User's Guide and the Oracle Configurator Installation Guide.
Click OK.
The model, option classes, and selected options are now all separate lines on the sales order window, as shown in. Note that the lines are related by the line number.
If the profile option, OM: Use Configurator is set to No, the Options Window will appear.
Options Window
Select your options.
Click OK.
Note: When using the Enhanced Effectivity functionality the options window, at the time of re-configuration also displays any previously selected options that were disabled since the last time the configuration was created/updated. Such disabled options will be flagged appropriately in the ' Disabled' column in the options window.
Each of these lines has a separate workflow and chapter will discuss the workflow process for each line in the workflow section.
After the options for the configuration are selected, the items on the order must be scheduled.
Sales Order Window with Model, Option Classes and Options
See: Scheduling
Create the configured item
This item could be completely new, or it could have been manufactured before because someone selected the same combination of options. A program runs looks for an existing configuration with these options (if the value of the profile option BOM: Match to Existing Configuration = Yes), and if one does not exist (or if the value of the profile option BOM: Match to Existing Configuration = No) it creates an item and BOM for this combination of options. To run this program from the sales order window, place your cursor on the model line (the one with a two segment line number), press the Actions button and select Progress Order. The line will be eligible for the Create Configuration activity. Select this from the list and click OK. Alternatively you can create one or more configuration items in batch mode by running the AutoCreate Configuration Items concurrent request in the Bills of Material application.
When you have completed this step, your order will have an additional line item which is known as the configured item. The item will have an item number which was created for the first order with this exact combination of selected options. The format for the configuration item number is determined by the Numbering Method parameter in the BOM parameters window.
Note: There are two batch programs, AutoCreate FAS, which creates work orders, and AutoCreate Configuration, which creates configuration items, configuration BOMs and routings, and calculates cost and lead time. These batch processes update the workflow of each order line that it processes.
Note: AutoCreate Configuration Items picks up orders that are at the Create Configuration Item Eligible block activity and creates the configuration item, configuration BOM and routing, and calculates cost roll up and lead time roll up. It then completes the Create Configuration Item Eligible block activity with a Complete result and completes the Create Configuration BOM Eligible block activity with a Config Data Created result.
Note: AutoCreate FAS picks up orders for configuration items with discrete routings that are at the Create Supply Order Eligible block activity and creates work orders for them. It the completes the Create Supply Order Eligible activity with a Reserved result.
Note: Create the work order. Creation of the work order will trigger the manufacture of the item.
The CTO process works with both Oracle's Discrete Manufacturing applications and Oracle's Flow Manufacturing applications. This section uses the terminology of the discrete manufacturing process.
To create the work order from the sales order window, place your cursor on the configured item line (the one that was added in the previous step,) click Actions and select Progress Order. The line will be eligible for the Create Final Assembly Order activity. Select this from the list and click OK. Alternatively you can create one or more work orders in batch mode by running the AutoCreate FAS concurrent request in the Work in Process (WIP) application.
Manufacture the Item.
In a production environment this could require many steps. None directly affect Order Management until the final status of work order completion. When the completion activity is performed in WIP the item is transferred to inventory with a reservation to the sales order.
At this point, the configured item is available to progress through the standard order process of shipping and the model progresses through the invoice activity. The steps are described in the sales order flow and the shipping process flows sections of this manual.
Although there are many item types in this business process, only two top level line Oracle Workflow processes are needed to support it. The seeded flow Line Flow - Generic is used for the model, option class and option lines. The seeded flow Line Flow - Configuration is used for the configured item.
The flow for the model, options and option classes all begin with the following basic process depicted in.
Line Flow - Generic Workflow Process
The lines progress through the Enter - Line and Schedule - Line subflows along the same path. At the Create Supply - Line subflow, their paths deviate.
Create Supply - Line Subprocess
The graphic above shows the variety of subflow paths that can be taken within Create - Supply Line. In the Branch on Source Type function, the options follow the path for Stock and the model follows the path for Build. Purchase Release - Line, Deferred is another subflow for drop shipments. See the corresponding section in this manual for more information on drop shipments.
The Build path, shown in the following figure, has an additional sub-process of Create Configuration - Line Manual which looks like this.
Create Configuration - Line, Manual Workflow Subprocess
This subprocess creates the new line on the order for the configuration item, and its workflow begins. This flow will be addressed in a moment. The activity also creates the new item (or finds the existing one, if applicable) and creates the BOM and Routing.
Once the Create Configuration - Line, Manual subflow is complete for the model line, the model line as well as the options and option classes have completed the Create Supply - Line subprocess and are ready for shipping. However, the model, options and option classes of a Configure to Order item are not shippable. The assumption is that in the manufacturing process the components are built into one indivisible item. So they pass through the shipping process with a result of Not Applicable, and proceed to the invoice process. The model line will be invoiced, so it goes through the Invoice Interface - Line activity and should complete. The options and option classes are not invoiced, so they go through the Invoice Interface - Line activity with a result of Not Applicable.
The configured item is created and added to the order when the model goes through the Create Configuration activity. Its workflow process is simpler than the process for models and options, shown in below.
Line Flow - Configuration Workflow Process
The figure below shows the first subprocess in the flow is the Create Manufacturing Configuration Date - Line, Manual.
Create Manufacturing Configuration Data - Line Manual Workflow Subprocess
This is the subprocess that performs the necessary Costing rollup and calculates the lead time for the configured item.
The figure below shows the next step in the configured item workflow, Create Supply Order - Line, Manual subprocess. This subprocess interfaces with the manufacturing system to trigger the assembly of the item. The Check Supply Type activity determines whether the item should be manufactured using discrete manufacturing or flow manufacturing. If the result is Flow Schedule, the Create Flow Schedule activity is executed. If the result is a Work Order, the final subprocess, the Create Work Order - Line process is executed.
Create Supply Order - Line, Manual Workflow Subprocess
Create Work Order - Line Workflow Subprocess
The above figure indicates the final subprocess flow - Create Work Order - Line. The primary activity in this flow is the AutoCreate FAS activity, which will cause the WIP application to create a work order.
After the work order is created, the sales order will wait for completion of the work order before proceeding. When the work order is complete the inventory will be received into the inventory module and automatically reserved to the sales order.
The configured item then continues through the normal shipping and fulfillment steps and then its workflow is complete. It does not have an Invoice Interface subprocess because it is never invoiced. Only the model line, option classes and options may be invoiced depending on their item attributes.
Several processes share some of the characteristics of the configure-to-order process. They include the assemble-to-order process, the pick-to-order process and the kit process. Because the configure-to-order process is the most comprehensive and includes all the steps it was described first, and the rest will be described relative to it.
The assemble-to-order process is similar to the PTO model, item, or PTO/ATO models because the items that are ordered by a customer are manufactured specifically for the customer order. So the manufacturing steps of the configured item are part of this process. However, the ATO item is not configurable for a customer in the sales order window. The ATO item is entered on the sales order window and then the order is booked without selecting any options. No option class lines or option lines are added to the order. The workflow process Line Flow - Generic supports the ATO process. The ATO item takes the ATO item branch in the Create Supply - Line workflow subprocess.
The pick-to-order process is similar to the configure-to-order process because you can select the options chosen by the customer. On the sales order window the PTO model is entered, and then you press the Configurator button to launch the options selection window. The configuration options are saved, and the option classes and options are added as lines on the sales order. However, there are no assembly steps in the PTO process. The options all continue their own workflows which include the standard sales order line activities. When you create your PTO model in the Inventory application, Inventory sets the attributes for the model, and you can specify whether or not it is Ship Model Complete. If this attribute is Yes, all the options will be in a ship set. If this attribute is No then the items can ship independently.
The kit process is similar to the pick-to-order process except that the user cannot select options to create a configuration. All the items in the kit are required; these are known as included items. Kits are similar to configure-to-order items because the included items are added to the order and have their own workflows. They are added either when the kit line is saved, when the order is booked, or when the line is pick released depending on the value of the profile option OM: Included Item Freeze Method. Ship Model Complete logic for PTO models also applies to kits.
Allows control over the behavior of configuration effectivity date based on the value of a system parameter. Supported for Oracle configurator or the OM options window. See: Oracle Order Management User's Guide for more information.
Set new system parameter OM: Configuration Effective Date to Model Creation date.
Create an order line for a model in order management on 3/20/03.
Launch Configurator or Options window for the Model.
Select options and save.
Add new option to BOM on 3/21/03. Also disable some option or option class in BOM on 3/21/03.
Re-open Configurator or Options window, new option will not be displayed. Disabled option or classes will still be available to choose.
User modifies the configuration and saves.
Set new system parameter OM: Configuration Effective Date to System Date until Booking.
Create an order line for a model in order management on 3/20/03.
Launch Configurator or Options window for the Model.
Select options and save.
Change the BOM for the model on 3/21/03 to add a new option and disable an option or a class.
Re-open Configurator or Options window. A message to user will be displayed saying one or more options / classes are disabled in this configuration and will be removed from the existing configuration. New options will be available to choose.
User accepts the message and modifies the configuration in the options window or the Configurator, and saves.
Disabled options and classes will be deleted (or cancelled) automatically.
User Books the order on 3/21/03. User changes BOM to include new options or disable options or classes.
Re-open the Configurator or Options window.
Now, new option will not be displayed. Disabled option or classes will still be available to choose.
User modifies the configuration and saves.
Set new system parameter OM: Configuration Effective Date to System Date until Booking.
Create an order line for a model in order management on 3/20/03.
Launch Configurator or Options window for the Model.
The BOM of this model has a mandatory option class and user selects one option under it and saves the configuration.
Change the BOM for the model on 3/21/03 to disable the selected option under the mandatory option class.
Book the order. System will remove the disabled option and populate an error message to indicate the same. This will result in Configuration validation error and Booking will fail.
Re-open Configurator or Options window. Choose an options for the mandatory option class and save.
Book the order, this time Booking will be successful.
Note: Mandatory option class rule is just an example and similarly some other BOM or CZ rules may result in invalid configuration with system parameter Configuration Effective Dates set to System Date until Booking.
Do not set new system parameter OM: Configuration Effective Date. This setting should be used to retain existing behavior.
Create an order line for a model in order management on 3/20/03.
Launch Configurator or Options window for the Model.
Select options and save.
Add new option to BOM on 3/21/03. Also disable some option or option class in BOM on 3/21/03.
Re-open Configurator or Options window, new option will not be displayed. Disabled option or classes will still be available to choose.
User modifies the configuration and saves.
Note: This procedure is specific to Configurator.
Set new system parameter OM: Configuration Effective Date to Model Creation Date or System Date until Booking.
Create an order line for a model in order management on 3/20/03.
Launch Configurator for the Model.
Select options and save.
Add new option to BOM on 3/21/03. Also disable some option or option class in BOM on 3/21/03.
Copy the order on 3/22/03. Disabled options will not be saved in the new order at the time of copy. Message will be populated to user to indicate that the options were not found in the BOM of model.
Re query the copied order and open Configurator.
New options will be available to choose.
User modifies the configuration and saves.
Note that point 6 is existing behavior even without setting the system parameter
Set new system parameter OM: Configuration Effective Date to System Date until Booking.
Create an order line for a model in order management on 3/20/03.
Launch Configurator or Options Window for the Model.
Select options and save.
Add new option to BOM on 3/21/03. Also disable some option or option class in BOM on 3/21/03 – this option or class should be one of the selected items in the configuration from step 4.
Change the ordered quantity of an option or a class in the configuration using sales order form. System will perform configuration validation.
System cascade the quantity change and also will remove the disabled option and populate an error message to indicate the same.
Book the Order.
Again change BOM to disable some options selected in the configuration.
Query the order and change ordered quantity on some options.
The quantity should be cascaded and newly disabled options should not be removed from the configuration.
Service Termination
Service Termination allows
Issue of full or partial credit for service lines during returns
Terminate service item (extended warranty) when product is returned.
See the Oracle Order Management User's Guide for more information.
Scheduling for ATO models allows sourcing rules to be used to select a warehouse for an ATO model: you do not need to specify a warehouse for the ATO model.
If the ATO model or any of its components are ATPable, the promised availability considers the matched configuration supply if ASCP is installed. If you drill from the Availability window to ATP Details, the quantity of available matching configured items is displayed. The Days Late column identifies options that are extending the Schedule Date on the ATP Details window.
This feature allows decimal quantities to be used on the options of an ATO Model during order entry. Decimal quantity can also be used for the options of an ATO Model even when the ATO Model is part of a parent PTO Model. ATO items and options of a PTO Model cannot use decimal quantities.
Note 1: Non-Integer ratio is allowed between the Option and its parent (Option class). It is also allowed between the Option and its Model.
Note 2: Non-Integer ratio is NOT allowed between the Option class and the Model.
Examples:
Ordered Quantity | |
ATO Model | 1 |
Option Class 1 | 10 |
Option 1A | 11 |
Option Class 2 | 20 |
Option 2A | 20 |
Ratio of Option Class: Model are integer ratios, Option level is non decimal quantity.
Ordered Quantity | |
ATO Model | 1 |
Option Class 1 | 10 |
Option 1A | 11.5 |
Option Class 2 | 20 |
Option 2A | 19 |
Ratio of Option Class: Model is an integer, Ratio of Option: Option Class/ Model is non-integer.
Option 1A has an ordered quantity which is a decimal quantity.
Ordered Quantity | |
PTO Model | |
ATO Model | 1 |
Option Class 1 | 10.4 |
Option 1A | 11.5 |
Option Class 2 | 20 |
Option 2A | 19 |
Decimal Quantity Allowed ONLY for options of an ATO Model. Decimal Quantity NOT allowed at the option class level. Ratio of Option Class: Model is a non-integer.
Ordered Quantity | |
PTO Model | |
ATO Model | 1 |
Option Class 1 | 10 |
Option 1A | 11.5 |
Option Class 2 | |
Option 2A | 20 |
PTO Option Class 2 | 1 |
PTO Option | 2.5 |
Decimal Quantity allowed for options of an ATO Model ONLY. Decimal Quantity NOT Allowed for options / option class of a PTO Model.
Ordered Quantity | |
PTO Model | |
ATO Model | 1 |
Option Class 1 | 10 |
Option 1A | 11.5 |
Option Class 2 | 20 |
Option 2A | 20 |
PTO Option Class 2 | 1 |
PTO Option | |
ATO item 3 | 2 |
Decimal Quantity allowed for options of an ATO Model ONLY. Decimal NOT Allowed for options / option class of a PTO Model OR ATO items
Ordered Quantity | |
PTO Model | |
ATO Model | 1 |
Option Class 1 | 10 |
Option 1A | 11.5 |
Option Class 2 | 20 |
Option 2A | 20 |
PTO Option Class 2 | 1 |
PTO Option | 1 |
ATO item | 4 |
Decimal Quantity Allowed for options of an ATO Model ONLY. All ratios between Option class and Model are integer ratios.
Define your planning sourcing rules, such as for Make, Transfer, and Buy
Set up the profile option BOM: Match to Existing Configurations to Yes. For the system to look for a match for your configured item at the time of scheduling, you must set this profile option to yes. The profile option for BOM: Use Custom Match Functionality is not required. If the Item attribute is null, it uses this profile option. Otherwise, it uses BOM: Match to Existing Configuration.
On the item, set Match Configuration to Standard Match. With PDS, which refers to ATP with planning output, you can match configurations. This requires that you set the Item Level Attribute, Match Configuration, in the Item master for the model. When you Enable Configuration and set Match Configuration, the following occurs:
If the item attribute Match Configuration is set to No, a Match is not performed for the configuration of this base model.
If the item attribute Match Configuration is set to Standard Match, a Match is performed for the configuration of this base model.
If the item attribute Match Configuration is set to Custom Match, a custom hook for Models is called for configuration of this base model. If the item level attribute is set for Custom Match then you must specify custom code. If this attribute is null then no match will occur.
Run Data Collections.
Create a plan for your items.
Optionally, create a folder for the ATP Details summary region to provide visibility to the Days Late attribute. Use Folders to display the Days Late attribute. The summary region of the ATP Details window is modified to show the Matched Configuration. Also, you will probably want to set up a folder to improve visibility to key attributes on the summary region of the ATP Details window.
To take full advantage of planning and create configuration features the following OM constraints have been removed:
If you have non-organization specific sourcing assignments set for your model, warehouse is no longer required prior to scheduling.
Warehouse changed allowed until a reservation is made to the configuration item ONLY for order lines for models with the "Create Configuration item, BOM" attribute set to “Based on Model." With this setting, configuration data is created from all possible sources, giving you the flexibility to change the warehouse at any time.
In all other settings, the configuration data was created only in the sourcing chain for the shipping warehouse, and you must delink the item, change the warehouse and rerun autocreate config to create the data based on the new warehouse.
If you are using match, the same item will be reused, and additional data created.
Splits are now allowed on a model line until a reservation is made to the configuration item
You can unschedule an order until it has been shipped.
Enhanced ATP and planning support for configurations supports the following features:
Note: Some of the features listed below are available only with ATP based on planning output, Advanced Planning and Scheduling, and Demand Planning.
Match during ATP and planning: ATP does a match prior to performing its availability check. If a match is found, ATP is done on the matched item instead of the model and options. This provides an accurate ATP and scheduling throughout the Order lifecycle, as well as enables customers to manage a combination of make to stock and make to order business processes. ASCP identifies that a sales order for the model and option matches an existing configuration item. This allows ASCP to net existing supplies of pre-configured stock at any supply chain bill of material level.
Global ATP for ATO Models and ATO Items: You do not have to specify a warehouse prior to scheduling or performing an ATP. ATP chooses a source based on sourcing assignments and availability to produce the specific configuration, enabling the system to recommend the best possible source for the product.
Support for Multiple Sources: You can source configurations from more then one location. This can be done through sourcing assignments that are a combination of make/buy, make/transfer, transfer/transfer, and so on. Multiple Sources also requires global forecasting, which is a feature of Demand Planning.
Option Specific Sourcing of ATO Models: You can restrict the sourcing of a model based on the options chosen. For example, a Model could be made in organizations 1 & 2, but if option 1 is chosen, it can only be made in organization 1.
Pre-configuration forecast consumption: If a forecast exists for the matched item, its forecast is consumed first, then the model and option forecast is consumed, if needed.
Planning for option dependant resources: When planning to a forecast, APS applies the planning percentages to the option dependant resources in addition to the optional material.
Supplier Capacities for ATO Models: You can specify a supplier capacity for an ATO model, and sales order for configurations of that model consumes the models capacity.
See:
Oracle Configure to Order Process Manual
Oracle Advanced Planning Implementation Guide
Oracle Global Order Promising Implementation and User's Guide
Oracle Demand Planning Implementation & Users Guide
Enhancements and changes in this area include:
Match control by Model: Control for matching is a model item attribute, enabling you to choose to match in some cases and not others.
Control where the Configured item, BOM and Routing is created: You can specify to create it only in the organizations required for this order, or in all organizations where the model exists
Option Specific Sourcing: BOM and routing creation are further restricted by the option specific sourcing setup used during ATP.
Configured Item creation for all Scheduled Orders: The auto create configured items process will now create configurations for all scheduled orders that fit the program parameters, even if scheduling happens before booking. Scheduled orders for generating the Configurations with out looking at whether the Order is booked or not. This helps planning consider the Sales order demand in the form of configured items instead of Model and Options. However, the creation of configurations through sales order workflows (Progress Order to Create Config Eligible) is not possible for scheduled orders if they are not booked. The Batch Program Auto Create Configured items when Automated to run at regular intervals picks up the scheduled and configured orders and creates configurations for them. Before creation of Configurations the demand exists as Model and Option demand. The demand is transferred to a Configured item when created and linked to the sales order De-link, Link, Match and Reserve possible before booking. For a scheduled order, de-linking the configured item, creating configured item, Match and reserve functions work before booking.
Indication of Dropped Components: If you select optional components, and they cannot be added to a bill in any organization in which the application attempts to create it, the program either stops the item/bill creation or creates it without the required item. In either case, a message is sent to the appropriate planners that action is needed and the order line is put on hold.
Decimal Quantities for Options of an ATO Model: You can enter decimal quantities on options during the configuration process. These decimals are used during the Bill creation process. Decimals are not allowed on the ATO model itself, option classes, or components of PTO models.
Re-Use for Non-Matched Models: If a configuration item is manually de-linked from a sales order, but the configuration is not changed, the same item number is re-linked to the configuration the next time auto create configuration is run.
Flexibility to delay optional processing for configured items: You can separate the optional processing (lead time roll-up, cost roll-up, purchase price roll-up) from the create config process. Batch programs do the optional processing as separate processes.
In previous releases, if you were not using Configure to Order create supply processes to create sales orders, you were required to:
Modify the workflow so that it no longer required a reservation for shipment
or
Leave the workflow as is, and run an OM auto-reserve program before being able to ship your configurations.
In previous releases, you could use the standard workflow to bypass the create supply processes in cases where you did not want to create supply for a sales order.
If you use planning to create supply for sales orders, the workflow has been modified to skip the create supply process in the following scenarios:
More then one source is defined for the configuration in the shipping organization in default assignment set
Configuration has a 100% transfer from sourcing rule in shipping organization
Customer defined logic exists.
Example
Planning is run once per week. If an order comes in within the week, create supply through the automated process, otherwise skip it and move to ship line.
Update Existing Configurations
A new program has been created to allow users to update the configuration item, BOM, Routing and sourcing rules for existing configurations when the following setup changes occur on the model:
Addition or change of sourcing rules, assignments, or option specific sourcing
Change of the Create Configured Item, BOM attribute setting
Change of ATP attributes
Business Flow Support
Oracle Supply Chain Applications have introduced support for business flows for global corporations, in which the financial ownership of goods does not necessarily follow the physical movement of goods. These include the following business flows:
Central Procurement
Central Distribution
Drop Ship Across Ledgers
If enhanced intercompany is being used, at the time of intercompany invoicing between each operating unit pair in the transaction flow:
The system checks to see if a transfer price already exists for the specific configuration (you may have a set price for a preconfigured item, for example).
If no price exists, it performs a calculation of the transfer prices based on the rolled up transfer prices of the base model and all its options. Standard, mandatory components are not included in the roll-up.
Include their prices in the price of the parent model or option class. This calculation is based on the model and options on the linked sales order (if one exists) or on the configuration bill of material.
Note: The system randomly chooses a BOM from those that exist in the system.
See: Oracle Inventory User's Guide, Oracle Purchasing User's Guide
Drop shipments occur when your customer orders product from you, you order the product from your supplier, and your supplier ships the product directly to your customer. Order Management sends information to the Purchasing Application to create that PO, and then when that PO is received (to indicate shipment from the supplier to your customer), the order line is automatically updated to indicate that it was fulfilled.
In this process, the company running Order Management is modeled as the company to whom the end customer places the original order. We call this process Vendor Drop Shipment, to indicate that we are defining the process from this point of view.
The Source Type attribute on the order line controls whether a line will be fulfilled internally or drop shipped. A source type of External indicates Drop Ship. Drop ship order lines can be processed for standard items, ATO models, Non SMC PTO models and kits. SMC PTO models cannot be used on drop ship order lines. You can define an Order Transaction type that specifies all of its lines be sourced externally.
Consider establishing a logical warehouse to receive drop shipments. This will isolate the costs of drop shipped items from items you physically stock. Order Management does not require you to use a special shipping organization for drop shipments, but you can choose to do so. In that case, define the logical warehouse as a shipping organization, and enable the items you want to be drop shipped in that warehouse.
Define line type/order types for your drop shipment orders that have a workflow containing the Create Supply—Line subprocess. This sub process could have the ' Purchase Release Line Deferred' activity - so drop ship lines are automatically interfaced to Purchasing via a workflow background process after Booking. You could include the ' Purchase Release Line - Manual' activity and allow Purchase Release to be a manual activity i.e. run adhoc or in batch mode via the concurrent program.
Define defaulting rules, based on conditions that make sense to your business process, for the source type attribute of the Order Line. If you want a line to be drop shipped, make the source type equal to External. In addition, if you defined a special warehouse for drop shipped items, you might want to create a defaulting rule to default that shipping organization to your order line.
Depending on your business needs you could use various constraints for example you could prevent changes once a PO is approved or you could choose to disable this constraint provided you have a process to handle any exceptions from the supplier.
Depending on the status of the PO / Requisition - some typical changes allowed from the sales order are - Quantity Increases / Decreases, Cancellations, Scheduled Ship Date, Ship To Location, or Referenced Data elements (ship method).
Depending on the status of the PO / Requisition / Sales Order Line - some typical changes allowed from the PO side are - Promise Date, Delete Lines, or Cancellations.
Other restrictions imposed during the change management process are included in Oracle Order Management User's Guide.
Enter and book an order.
Defaulting Rules may set source type attribute to External through the organization level item attribute setting—Default SO source type for the item, or you can manually choose External as the source type on the sales order line. Drop ship order lines can be processed for standard items, ATO models, Non SMC PTO models, and kits. SMC PTO models cannot be used on drop ship order lines. The Create Supply workflow step loads OM information into Oracle Purchasing's Requisition Import tables. Alternatively, a Purchase Release concurrent program can be run to do the same.
Run Requisition Import in Purchasing to create the requisition.
Create a PO or autocreate a Sales Agreement PO release from the approved requisition.
When the vendor ships product to your customer, you may receive an ASN, or even an invoice, to indicate shipment to the customer.
If the vendor does not send an ASN, a receipt can be entered manually (passive receiving) to record a logical receipt.
You can set the profile PO: Automatically Deliver Drop Ship ASNs to trigger automatic receipt of the ASNs in Purchasing, or choose to have manual intervention to receive the ASN. Inbound and outbound material transactions are automatically created for accounting purposes.
Order Management workflow proceeds to next step, typically invoicing of the end customer.
The Generic Line workflow contains the Create Supply activity, which branches to various sub-processes based on different characteristics of the item and sales order line.
Order Management's workflows streamline the process of loading order information into the Purchasing Requisition import tables, eliminating the need to run the Purchase Release concurrent program. You can still run Purchase Release as a concurrent program, if you prefer to batch up requisition lines.
Within a Centralized Distribution / Manufacturing environment Drop ship across Ledgers could be used for example, in a case where you use a global/regional distribution center to gain tax advantages, you can now perform clear ' arms length' ownership transfer between the operating unit shipping the goods and the operating unit which sold the goods and possibly one or more internal organizations.
Drop shipping across ledgers offers the ability to consolidate procurement functions for all global business units into one or multiple Shared Service Centers. Central Procurement Organizations:
Leverage buying volume by consolidating demand across organizations
Standardize terms and conditions across all enabled organizations
Centralize supplier relationship management
Complete transactions across international borders through foreign subsidiaries/shared service centers
When goods are shipped or received, the financial ownership through these organizations does not necessarily follow the physical movement of goods.
Drop Ship across Ledgers can fulfill drop shipments across multiple operating units (OU), ledger or legal entities, and automate inter-company transactions between multiple operating units, ledgers or legal entities.
Note: Only When using drop ship across ledgers/operating units, the requisition/purchase order is created in the operating unit of the warehouse that has been referenced on the drop ship order line.
See: Oracle Purchasing Product and Functional Overviews,
Oracle Inventory & Cost Management Enhanced Intercompany Product and Functional Overviews
Change management support between Order Management and Purchasing automatically propagates user initiated changes on the sales order to the corresponding requisition/purchase order even if they are across ledgers or in different operating units.
See: Change Management for Drop Ship Orders in Oracle Order Management User's Guide.
Enhanced integration between Oracle Order Management and Purchasing sends additional sales order data to the supplier.
See: Sales Order Elements in Oracle Order Management User's Guide.
In an environment where lead times are often only a matter of 24 hours, you may need to create a specific supply order linked to each customer order as soon as the order is booked, with the supply order hard pegged to the customer order that it is supplying. Once the supply reaches the warehouse it must not be inadvertently taken by another order or demand. Additionally, where the Sales Order line is in the process must be visible to you at all times so you can answer customer service inquiries. This process, Back-to-Back Orders, closely links the Sales Order and the supplying Purchase Order, often where one PO is tied to one Sales Order. The following shows you how you can model this process using Oracle Order Management and Oracle Configure-to-Order workflows.
Often customers order products that you do not typically stock but that you do not manufacture either. You may want to purchase that item specifically for this order, have the supplier ship it to you, and then combine it with other items you may have purchased or stocked to create one shipment to the customer. This is a common scenario for Wholesale Distributors who use the S3, or Sell-Source-Ship business model as well as for other demand channels. We call this process back-to-back orders or procure-to-order.
Keys to making this business process work are automating the Purchasing document creation, having accurate status of where the line is in the process, and pegging (or hard reservation) of the supply to the demand, so that the inventory isn't shipped to other customers once it is received.
The supply-to-order process satisfies this business need through both the familiar assemble-to-order process—in which a specific work order is created to build the item—and the procure-to-order process whereby a specific purchase order is created to fulfill the sales order demand.
Supply-to-order items are either standard items or models that have the assemble-to-order item attribute turned on. It is this attribute that launches the ATO workflows that deliver this feature. PTO models by definition cannot be supply-to-order, since turning on the assemble-to-order attribute would make them an ATO model. But you can fulfill the shippable options of a PTO model with back-to-back orders by checking the assemble-to-order item attribute of those components.
Using this process, you can:
Designate the items you want to procure each time they are customer-ordered as supply-to-order.
Set up a Buy From sourcing rule for those items or, if you don't set up sourcing rules, indicate that the item is a buy item rather than a make item.
Enter sales order lines for these items, and have the supply automatically created via a requisition. No user decision-making is required to make this happen.
Have the requisition converted into a Purchase Order or a release of a Sales Agreement and have the PO or release sent to the supplier.
View the requisition number or PO number and its status from the Sales Order.
Accept changes to the Sales Order and have the ability to notify the buyer to take appropriate action on the associated PO.
Reserve the supply from the Requisition to the PO and finally to Inventory once the PO is received.
Pick, ship and finally invoice the customer for the product.
To satisfy the above business needs, Oracle Order Management and Configure-to-Order have combined to deliver the back-to-back business flow with the following set of features:
An automatic process called Auto Create Requisition is available that creates the requisition in Purchasing for the Sales Order line. This process takes information
from the sales order line and puts it in the requisition import interface tables so that a purchase requisition can be created. This process can be run as a scheduled or on-request concurrent process, or can be initiated online from the Sales Order line using ‘Progress Order' action.
The supply for the reservation is first linked to the requisition, then moves to the PO, and finally to Inventory as the PO is received. Visibility to the supply for the reservation is provided in the View Reservations window.
A branch of the existing Create Supply workflow subprocess in the seeded generic sales order line workflow initiates the autocreate purchase requisition processing when there is a Buy result.
Use the Inventory Master Items window to define the items that you wish to supply to order. The following item attributes must be specified:
Item must be marked as Customer Orderable on the Order Management tab and Purchasable on the Purchasing tab.
Item must be marked as Assemble-to-Order on the Order Management tab.
Note: The Assemble-to-Order attribute is actually called Replenish to Order in the database. The same flag also controls Procure-to-Order. (This is not related to the Oracle Warehouse Management replenishment feature.)
Item must be marked as Build in WIP on the WIP tab.
Item must either have the make/buy flag on the General Planning tab set to Buy, or else have a sourcing rule saying that it is to be sourced from a vendor.
If you define a sourcing rule for your Supply-to-Order items, then the sourcing rule must be of type Buy From. Also, you may only define one single sourcing rule for your item, or this process will not work.
You must add this sourcing rule to the assignment set which is specified as the MRP default assignment set in the MRP: Default Sourcing Assignment Set profile option.
Note: You may not have a combination of Buy From and Make sourcing rules or more than one sourcing rule in the assignment set for the same item. If you do that, Auto Create Requisition errors out and puts details about the problem in the log file.
Enter the item on the Sales Order line.
When the line is Booked/Scheduled, the Create Supply subprocess of the workflow will put the lines through the Buy ATO Item flow which contains the autocreate purchase requisition activity. AutoCreate Requisition can be run as a concurrent program or can be initiated for an individual order by using the Progress Order action on the sales order if it is in status Create Supply Line – Eligible. As stated above, AutoCreate Requisition takes information from the Sales Order line and loads the Requisition Import interface tables.
Requisition Import must be run to create the purchase requisition tied to the sales order line. This can be done by manually submitting the Requisition Import concurrent program, or you can schedule it to run automatically. Requisitions created by this process all have an interface source type of CTO so you can identify and segregate these requisitions as needed. There are also message dictionary entries for CTO Note to Receiver that can be populated with custom text. The requisition column Note to Buyer is populated by the AutoCreate Requisition process with a message Supply for sales order: <order number> that indicates the order number of the line. Add additional custom text to the note by editing the message dictionary for CTO Note to Buyer.
Once the purchase requisition is created and identified as CTO, the regular purchasing process takes place:
A Purchase Order is created and approved and sent to the necessary supplier, or a release of a previously created Sales Agreement is used.
Once the PO or release is received, the items are recorded in inventory and a reservation is automatically made to the sales order line.
Note: View the Note to Buyer at any point in this process to find out what sales order generated this PO or release.
The sales order can now be pick released, shipped and invoiced just like other stocked items.
The following line statuses help you track where the line is in the process:
PO Req Requested
PO Req Created
PO Created
PO Received
If you want to see the Requisition number or Purchase Order number created by your Sales Order line, you must go to the Reservations Details window to find that information.
A key in making this functionality work for you is how the inventory reservation is handled. This happens automatically, and can be traced from the sales order window by using Tools->Scheduling->Reservation Details as well as by directly using Inventory's Supply/Demand forms.
When Req Import processes, the purchase requisition is reserved to the sales order line. View the Inventory Reservations window supply tab to see the reservation linked to a requisition, and the requisition number and line number.
When the requisition becomes a PO or a Sales Agreement release, the reservation moves with it. The Reservations window, supply tab, then shows the reservation is linked to a PO or a Sales Agreement, and you will see the PO number or the PO and release number, as well as the line number.
When the PO is received into inventory, the reservation is automatically transferred into Inventory, and it now looks like any other reservation from a sales order to on-hand stock.
Just as in the regular ATO process, if you manually reserve the sales order line to inventory the Create Supply workflow step will not do anything, and the line will progress to Awaiting Shipping without flowing through the requisition process.
What happens if you need to make changes to the sales order line that is in the back-to-back process? What if the order line is cancelled? What if you need to make changes to the PO or the requisition?
If the sales order line is cancelled or the quantity is reduced, then the reservation is reduced and a notification is automatically sent to the buyer explaining that there is now a PO outstanding for a higher quantity than what is needed for the sales order. The buyer can then decide whether to cancel the PO line, or to buy the product anyway and put it into inventory.
If the schedule date on the sales order line is changed, again a notification is sent to the buyer, who can then decide to either change the date on the PO or cancel it or do nothing. If the buyer decides to cancel the PO, then a new requisition will be created the next time AutoCreate Requisition is run.
If the PO is cancelled or a partial quantity is cancelled, then the reservation is cancelled or reduced appropriately. The next time AutoCreate Requisition is run, it will create another requisition for the unreserved amount on the sales order.
Note: User initiated splits are not enabled on a back to back sales order line that is purchase released and the reservations are against Purchase Order or Purchase Requisition.
Drop Shipments is similar to this back-to-back process in that your sales order line creates a requisition line that becomes a PO sent to your supplier. In a drop shipment; however, you instruct your supplier to send the item or configured item directly to your customer. The items never physically pass through your warehouse, and therefore you do not pick, pack or ship them yourselves. In the back-to-back scenario, you instruct your supplier to send you the goods, and then you ship them on to your customer.
There is a Supply Type of External Requisition to inventory reservations that also shows the purchase order or requisition that the reservation is made to in the Inventory Reservations window.
The AutoCreate Requisition program uses the OM debug system. This means you can generate a debug file if you set the OM debug profile and the OM debug log directory profiles and then run the program.
Purchasing has its own debug profile which is used by Requisition Import to log messages, but any messages regarding the reservations are logged using OM's debug facilities.
Order Management provides the functionality required to recognize fulfillment of an order line, and delays processing of some order lines until related order lines have been fulfilled.
Oracle Order Management enables you to group lines into a fulfillment set and to establish a gate activity in your workflow process. Lines in a fulfillment set will wait until all lines in the set have been fulfilled to proceed through the gate. This gate is known as the fulfillment activity. The fulfillment feature is primarily designed to allow the grouping of related lines and to keep any lines in the group from being invoiced until all lines have been fulfilled.
The following terms will be used to describe fulfillment:
Fulfillment activity: The synchronization point or gate in the workflow process at which lines wait for other lines to be fulfilled.
Fulfillment method activity: The activity in the workflow process which indicates that the line has been fulfilled.
Fulfillment set: A group of lines which must all be fulfilled before any of the lines proceed beyond the fulfillment activity in the workflow
The fulfillment activity is a seeded workflow activity named FULFILL_LINE. This activity is the synchronization point between the lines of a fulfillment set.
There are two activities that are considered fulfillment method activities in the seeded OM workflows. For a standard shippable line the fulfillment method activity is the shipping activity. For a return line the fulfillment method activity is the receiving activity. You may define any activity as the fulfillment method activity in a workflow process. The fulfillment activity must be between the fulfillment method activity and the invoice interface activity in the respective workflows.
When a line workflow reaches the fulfillment activity, the activity checks to see if the fulfillment method activity (for example, shipping or receiving) completed successfully. If so, it updates the fulfilled quantity on the line with the shipped or received quantity, and sets the fulfilled flag to Yes. It then checks to see if the line is part of a fulfillment set. If not, then it completes the fulfillment activity and continues with the next activity in the workflow process. If the line is part of a fulfillment set, it checks to see if the other lines in the fulfillment set are fulfilled. If any lines are not fulfilled, it waits at the fulfillment activity. If all the lines are fulfilled it completes the fulfillment activity for all the lines in the fulfillment set.
Service lines behave differently in Fulfillment Sets depending on the business scenario. The most common business scenario is to order a product with an associated Service line on the same order. In this situation, it is not necessary to assign a Fulfillment Set to the Service line as the Fulfillment activity takes care of fulfilling the product and Service line as a Fulfillment Set, implicitly. There are business scenarios where Fulfillment Sets can be assigned to Service lines. One scenario is in the case of ordering a Customer Product with an associated Service line. A second is when placing an order for a Service line associated to a product which is not in the same order.
PTO Models and ATO Models are treated as inherent Fulfilment Sets by the system. As an example, A PTO Model is ordered, the Fulfilment Set field does not contain a value yet all nonshippable lines from the Model wait at the Fulfilment activity for the shippable lines prior to progressing.
No setup is required to use the fulfillment functionality with the seeded workflows. If you create your own workflows, include the fulfillment activity before invoicing in each process. This will provide two benefits: it will update the fulfilled quantity for the lines, and it will allow you to use fulfillment sets. For each workflow process that you define, you will need to check the attributes of the FULFILL_LINE activity. The FULFILLMENT_ACTIVITY attribute must be your fulfillment method activity, which in the seeded flows is either the shipping activity or the receiving activity. The COMPLETION_RESULT should be the result with which the fulfillment method activity completes if it is successful. This allows you to designate any activity as a fulfillment method activity.
If you have a workflow process with two separate branches, such as a single workflow process with separate branches for ordered items and returned items, then you should have one fulfillment activity for each branch which relates to the fulfillment method activity for that branch.
You can have multiple fulfillment sets in a single order. If a line is a member of two fulfillment sets then all lines from both fulfillment sets must be fulfilled for any of the lines to complete the fulfillment activity.
If a line workflow process with a notification is in a fulfillment set, and the notification is rejected, then the other lines will not progress in their flows. You will have to delete or cancel the rejected line.
Example
Assume that you enter an order with four lines:
Standard Item 1
Standard Item 2
An item which is shippable
An extended warranty for that item.
You would like to send the customer two separate invoices: one for the two standard items; and a second for the item with an associated extended warranty.
Put the two lines with standard items into a fulfillment set. Select Sets > Assign a Fulfillment Set Name, 2 from the context menu. The Fulfillment activity recognizes the service item as associated to the shippable product and considers the two in a Fulfillment set even though a Fulfillment Set name was not identified on either line. You would not want to bill for the service contract until the item was shipped. The service item will wait at the fulfill line activity until the shippable line arrives there, and then both lines will continue to invoicing at the same time.
When the order is booked, the shippable lines must complete the scheduling and shipping activities. These activities are not applicable for the service contract, so they will complete immediately. The two standard items will progress through the Fulfillment activity as Fulfillment Set 2. Similarly, the shippable line and the service contract will progress through the Fulfillment activity together as an implicit Fulfillment Set.