Sie sind auf Seite 1von 8

Importing Configurations

An Oracle White Paper August 2001

Importing Configurations

EXECUTIVE OVERVIEW

Oracle Order Management supports all the business processes required for configurations. This means that you can define an item with options, and allow the user to select the options at the time of order entry. For example, consider an automobile. You might be interested in buying a Volvo C70. You have several options choices to make including the interior and exterior color, whether the transmission is standard or automatic, etc. Order Management allows you to select the options when the order is entered, and then possibly drive the manufacturing process based on those selected options. If you use the selected options to drive manufacturing this process is called Assemble to Order (ATO.) If you simply pick the selected options from a warehouse the process is called Pick to Order (PTO.) Order import is a facility which allows you to enter orders in batch mode. You might want to do this if you are taking orders in another system and then loading them into Oracle Order Management for fulfillment or billing. You will also want to do this for orders that come directly from your customer through EDI. In Order Management, Order Import provides the ability to import Assemble-To-Order and Pick-To-Order (PTO) configurations.
INTRODUCTION

Within Oracle Order Management, Order Import is the process which is used to import configurations into the order management tables. This information can then be changed on the sales order pad and processed using the standard OM workflows. In addition to the information required to import an order line for a standard item (such as item number and quantity,) there is some required information that is specific to models. In general, this information is used to communicate the structure of the configuration or how the items are related to each other. For instance, one of the selected options for an automobile might be a color Black. To use this information in building the car, you need to know which option class it is associated with. The car would be built differently if it is a selection for the Exterior Color option class as opposed to the Interior Color option class. The importing process uses the Process Order API to validate the model-specific attributes in order to successfully import the configurations into Order Management. These model-specific attributes must be loaded into the order import interface tables using SQL or typed into the order import Error Corrections form prior to importing. The Corrections form allows the user to create new lines and/or change or delete existing lines in the interface tables. As part of the import process the selected configuration options are validated. This ensures that the configuration conforms to the BOM rules and the Configurator rules, if the model exists in Oracle Configurator. Order Import will let you import valid as well as invalid configurations. However, you will not be allowed to book orders with invalid configurations.

Importing Configurations

Page 1

Once the import process has run, the model, classes and/or options will populate the order management tables and the configuration will proceed through the common workflow activities for configurations. An example is given at the end of this paper of importing an ATO model and viewing the resulting sales order lines. This example shows the information required to import a configuration.
TERMINOLOGY

Understanding the following terms will help you understand configurations and order import in OM. Assemble To Order (ATO) Model - A type of configurable model where the selected options and standard mandatory components in the model go into the build process to create a single shippable item (called the configuration item). Bill of Material - A listing of all the subassemblies, parts, and raw materials that go into a parent assembly or product configuration. It shows the quantity of each part required to make an assembly. All models and option classes must have a bill of material. Configuration Item - An item that corresponds to a base model and a specific list of options chosen by the customer. A configuration item goes through the manufacturing process cycle, and is a shippable item. Included Item - A mandatory standard item in a bill of material that is shippable, indicating that it ships whenever an order that includes its parent item is shipped. Usually refers to components in the PTO model. Mandatory Components - A component in a bill of material that is not optional. Usually refers to the components in the ATO model. Model - An item whose bill of material lists options and option classes available when you place an order for the model. In the previous example, the Volvo C70 was the model. Option Class - A group of related option items. An option class is orderable only within a model. In the previous example, the transmission type was an option class with two mutually exclusive options of standard and automatic. Option Item - A non-mandatory item component in an option class or model bill of material. Order Import - an open interface that lets you create sales orders by capturing and validating order data from external systems (Oracle and non-Oracle systems). Order and Line Workflow - the mechanism that controls the processing of sales orders and lines. In Oracle Order Entry release 11 and prior, order cycles performed this function. A key difference is that with workflow each line type can have its own distinct cycle (workflow). Workflow provides the automatic coordination of parent and child processes needed for configurations. Pick to Order (PTO) Model - A type of configurable model where the selected options and included items appear on pick slips and order pickers gather the options when they ship the order. Alternative to manufacturing the parent item on a work order and then shipping it.
MODEL TYPES

Importing Configurations

Page 2

There can be two types of models for configurations: ATO Model: Includes a top level model, classes, options, configuration item and standard mandatory components. 1. Models, classes and options are priced and invoiced. If you are importing a configuration you must import lines for the model and selected options. Optionally you can import lines for the option classes. ATO options are not shippable. A configuration item is built for an ATO configuration and this configuration item is shippable. The configuration item is not imported. It is created from the selected options. Standard mandatory components are items which get exploded for manufacturing an ATO model. These are used to build the configuration item. These are not orderable items and they are not stored within the order lines table. They can not be imported.

2. 3. 4.

PTO Model and Kits: A PTO Model includes a top level model, classes, options and included items. A Kit has ONLY included items, and no configurable options. Kits behave in a similar manner to PTOs and thus we talk about these together. 1. PTO options can be shippable. If you are importing a configuration you must import lines for the model and selected options. Optionally you can import lines for the option classes. 2. Included items are shipped along with a kit, PTO model or class. Included items can not be imported; they are added automatically when the BOM is exploded.

ADDITIONAL FIELDS NEEDED FOR IMPORTING CONFIGURATIONS This paper assumes that you know how to import standard items using order import, and only describes the additional information that is required for importing configurations. If you need more information about order import, please refer to the Order Management Open Interfaces manual.

To successfully import a sales order line, you must include an item identifier to specify the item and you must specify the quantity. Two additional fields are required for importing a model line: Item Type - The field item_type_code must have the value of MODEL for the model line. Line Reference - The model line must have a reference number which is used by the other lines in the configuration to link to the top model line. This value is stored in the original_sys_line_ref field. One additional field is required for all option classes and options. Top Model Line Reference - The field top_model_line_ref links the class and option lines to their associated model. It should have the value which matches the original_system_line_ref of the model. Finally, one field is conditionally required for linking the options with the correct option class if there is ambiguity in the BOM structure. For example, suppose for your car there is an item named Black which is a valid option for both the exterior color and interior color option class. You must indicate when you select Black whether you are selecting it as the interior color or the exterior

Importing Configurations

Page 3

color. Component Code - The field is optionally required to resolve ambiguity in the BOM structure. It contains the concatenated item IDs for the model, option classes and option so that it uniquely identifies the item and where it appears in the BOM.

EXAMPLE

The following example illustrates importing a configuration and viewing the resulting sales order. A customer wants to purchase a new car from Volvo. Suppose that they have configured their car using the web store for your dealership. You are the programmer for the dealership, and your job is to get this information into the Order Management system so that the car can be built and delivered to the customer. The customer has many options to choose, from engine size to interior color. The Oracle BOM which represents the available options for a C70 looks like this:

Model - C70 Option Class - Engine Option - V6 Option - V8 Option Class - Transmission Option - Standard Option - Automatic Option Class - Exterior Color Option - Black Option - Navy Option - Red Option Class - Interior Color Option - Black Option - Beige Option - Gray Option - Alloy Wheels Option - Sun Roof The model and all the option classes and options must have been defined in MTL_SYSTEM_ITEMS before the BOM was created. Each of the items has a unique item ID. Assume the following internal item IDs: Model - C70 345

Importing Configurations

Page 4

Option Class - Exterior Color Option - Black

973 760

In this example, the customer has worked with the dealer to select their options through the web store and has chosen to buy a C70 model with the following options: Option Class Engine Transmission Exterior Color Interior Color Selected Option v8 Automatic Black Beige

As a programmer, your program needs to take this selected information and load the following information into the interface tables: Item C70 V8 Automatic Black Beige Item Type Code MODEL Orig Sys Line Ref 182 182 182 182 182 345-973-760 Top Model Line Ref Component Code

Note that you had to specify the component code for the option Black because it appears twice in the BOM - once as an option in the Exterior Color option class and once as an option in the Interior Color option class. The component code specifies the item IDs at each level of the BOM. After you run the order import concurrent program, you can find the sales order that you imported. If you open the order and turn Show Line Details on from the Tools menu option, you should see the following information in the sales order lines: Line Number 1.1 1.1.1 1.1.2 1.1.3 1.1.4 1.1.5 Ordered Item C70 Engine V8 Transmission Automatic Exterior Color

Importing Configurations

Page 5

1.1.6 1.1.7 1.1.8

Black Interior Color Beige

Note: If you have an interface where you cant code the logic to recognize the ambiguity and derive the Component Code, then you need to define your item and BOM structure so that there is no ambiguity. In the above example, you would need to define two separate items for black - one for the exterior color and another for the interior color. Each of the items would appear only once in the bill of material, and specifying the item would clearly indicate the items position in the BOM.
CONCLUSION

Order Management provides a powerful and flexible tool with the Order Import open interface. This program manages many business needs by capturing and validating all types of orders from different sources. With the proper setup, you can import all types of orders, including configurations, with ease and accuracy.

Importing Configurations

Page 6

Importing Configurations June 2001 Author: Sandy Rota Contributing Authors: Gayatri Pendse, Alok Singh Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 Web: www.oracle.com This document is provided for informational purposes only and the information herein is subject to change without notice. Please report any errors herein to Oracle Corporation. Oracle Corporation does not provide any warranties covering and specifically disclaims any liability in connection with this document. Oracle is a registered trademark, and Oracle Order Management is a trademark of Oracle corporation. All other names may be trademarks of their respective owners. Copyright Oracle Corporation 2001 All Rights Reserved