"Configure To Order", CTO, Configurator process flow

Configure To Order Process

(Part 1)

"Oracle Configurator" is usually launched from a host application, such as Oracle Order Management or iStore, and displays the selected configuration model to the end user. During an Oracle Configurator session, an end user makes selections and specifies requirements for the product or service being configured.  

 Overview of Configurator flow

The steps involved in the flow of an "Oracle Configurator" implementation are as follows.

1.       The steps involved in the flow of an Oracle Configurator implementation are as follows

2.       Define Model Inventory items, Option Classes, option items and Finished Goods Items

3.       Create ATO model using Oracle Bills of Material to represent the product model.

4.       Create Common Bill

5.       Import model Bill into Oracle Configurator module to create product structure in Configurator schema.

6.       Modify the model structure in Oracle Configurator Developer (If Required)

7.       Define Rules in OCD.

8.       Generate UI definition in OCD.

9.       Test model in OCD

10.   Publish Model from OCD

11.   Invoke Configurator from the Hosting Application (Order Management responsibility)

 Below is the pictorial representation of steps to be followed for creating a configurator model.

Model Structure:

Lets use simple example of building a desktop as the model.

Below is the Desktop model structure used for this demo.

Model	Desktop - Lenovo	Optional	Mutually Exclusive	Rule
Option Class	Monitor	No	Yes
Option	24 inch IPS
Option	22 Inch IPS
Option	18 inch Basic
Option Class	Processor	No	Yes
Option	I5 8th Gen
Option	I7 7Th gen
Option	I7 7th gen
Option Class	RAM Memory	No	Yes
Option	8GB
Option	12GB
Option Class	Hard Disk	No	No
Option	1 TB HDD
Option	256GB SSD
Option	512GB SSD
Option Class	Other Accessories	Yes	NO	When monitor is selected, HDMI cable, Power card and adaptor should be selected. When 512 SSD is selected, keyboard is offered as free
Option	Web cam
Option	External Speakers
Option	Keyboard
Option	AMD Graphics card
Option	Cabinet			When processor is selected, then cabinet should be selected by default
Option	Power Cord and adaptor

Demantra Basics

Demantra

Demantra is the Demand Planning Tool from Oracle.

Oracle Demantra uses Historical sales to sense and shape the demand in order to comeup with Forecast (Prediction of Demand).

Demantra Demand Management consists of

      DM - Demand Management
      AFDM - Advanced forecasting and Demand Management
 
There are 15 statistical forecasting models in Demantra. DM uses nine models and AFDM comes with additional 6 models.

Forecasting Models in Demantra

Following Forecasting models are used in Demantra

Regression

•         Regression

•         Log (log transformation before regression)

•          CMReg (Markov chain selection of subset of causal factors)

•          Elog (uses Markov chain after log transformation)

Exponential smoothing

•          Holt

•          Bwint

Intermittent Models

•          CMReg for Intermittent

•          Regression for Intermittent

•          Croston

Time Series Models

•          ARX and ARIX

•          Logistic and AR Logistic

Other Models

•          BWint (a mixture of regression and exponential smoothing)

Lets continue...

Oracle Inventory

 Move Order Process

Move order Tables

1) MTL_TXN_REQUEST_HEADERS: Move order headers, this stores the move order number in column (REQUEST_NUMBER).

2) MTL_TXN_REQUEST_LINES: Move order lines, this is the one that drives most queries and status checks for the move order as each line can be transacted individually.

3) MTL_MATERIAL_TRANSACTIONS_TEMP: Pending material transactions table also called the transaction temporary table, this holds allocations that act like reservations on inventory.

How to check whether move order is allocated? 
Quantity Detailed

In the move order lines table (MTL_TXN_REQUEST_LINES), the quantity detailed reflects the allocated quantity for a move order line.

The quantity detailed might be greater than the quantity delivered if a move order is allocated
but not transacted.

What happens when move order is allocated?

When a move order is allocated, a corresponding record is inserted into the pending table (MTL_MATERIAL_TRANSACTIONS_TEMP as well as lot/serial tables if required).  When the move order is transacted, the record moves from the pending table to the history table (MTL_MATERIAL_TRANSACTIONS).

Move order line status codes:

The move order table (MTL_TXN_REQUEST_LINES) provides the status of the move order in the LINE_STATUS column as a numeric.

1 Incomplete
2 Pending Approval
3 Approved
4 Not Approved
5 Closed
6 Canceled
7 Pre Approved
8 Partially Approved
9 Canceled by Source

You can look the status code using the below sql

SELECT lookup_code, substr(meaning, 1, 60) "Meaning"
FROM mfg_lookups
WHERE lookup_type = 'MTL_TXN_REQUEST_STATUS'
ORDER BY lookup_code;