Oracle E-Business Suite for Manufacturing Industry
General Software needs of Manufacturing Industry
Work in Process – Oracle Work in Process is the core of Oracle’s Discrete Manufacturing solution. Oracle Work in Process by itself provides a complete production management system that improves productivity, quality, and responsiveness while maximizing throughput and production. Oracle WIP supports Discrete, Repetitive, Project and ATO type of Work Orders.
Bill of Materials – A bill of material identifies the manufacture of finished products (end items), subassemblies, and components. Oracle uses a bill of material as a master list when generating the parts lists for work orders; cost roll-ups; lead-time roll-ups; Master Production Schedule (MPS), Material Requirements Planning (MRP), and Distribution Requirements Planning (DRP) generation; and kit processing for sales orders.
Configurator – Oracle Configurator provides a Graphical representation of the Items and its sub-assemblies which the users can review and select while placing orders from various sources like Order Management, iStore, Oracle Manufacturing.
Manufacturing Process Flows – Oracle Manufacturing provides solutions for the following types of Manufacturing processes
Shop Floor Management
Oracle Configurator – Setups and Flow
Oracle Configurator is an application or part of an application that allows users to configure products or services. The Configuration Model which is typically based on BOM Model consists of structures, rules and UI Definition.
Oracle Configurator consists of the following main elements:
Runtime Oracle Configurator
Oracle Configurator Servlet
Configuration Interface Object
Oracle Configurator schema within an Oracle Applications Database
Oracle Configurator Developer
The only Prerequisite before using Oracle Configurator is to have Oracle Inventory and Oracle Bills of Material setups completed. Some of the Mandatory Profile Options are:
Oracle Configurator is driven by the Model (ATO or PTO) type of items. Generally Oracle Configurator is used for guided selling i.e. user is presented with various questions and based on user inputs respective components are selected. So user should be allowed to select various product properties. These properties are stored as Item Catalog values in Oracle Inventory.
The first step of Configurator Data setup is to setup item data and its Bills of Material containing various components and option classes.
Create ATO Model, ATO Option Classes and ATO Items
Create minimum of 1 ATO Model, 1 ATO Option Class and 1 ATO Item so that these items can be included in the BOM Model. Make sure these Items are assigned to at least 1 Child Inventory Org.
Once all the required Items are created in Inventory, we need to setup the BOM Model for these Items. This can be done in Oracle Bills of Material module. First create BOM for the ATO Option Class with ATO Items as its Components
Next, create a BOM for the ATO Model ‘CN1000-KHU0213’ with all the ATO Option Class under it.
Next, the ATO Optional Class needs to be added under the ATO Model. This can be achieved by creating an Indented BOM.
Step3: Once all the BOM Model Bills are created, we need to interface this data to Configurator Schema. To achieve this we need run the Concurrent Program ‘Populate Configuration Model’
(R) Oracle Configurator Administrator
(N) Concurrent Programs ? Schedule
Review all the parameters and the Schedule details and click on Submit to submit the Concurrent Program.
Once the Program is executed, we can view the Model in the Main Repository under the Oracle Configurator Developer page.
Once the Model and related components are created, we can move all the related components under the new folder.
Next we need to create a new User Interface and assign to the Model. This UI can be customized as per the Business Needs. To Create the UI for the Model ‘Configured PC Model KHU(204 244962)’ -
Once all the General details are defined, we need to define the Structure of the BOM Model and its child Items. This structure will decide how the components are stored in an Hierarchical manner during Run-time
Next, Rules can be created which will modify the Configuration structure based on some User Inputs. This gives more flexibility of the Configuration Structure.
Finally, we need to assign existing UI or create new UI for the Model. By creating new UI’s we can customize the way the Configurator looks and feels during run-time.
Next, click on ‘Test Model’ to execute the Configuration to make sure the appearance and the functionality of the Configurator is working as expected.
This will generate the Run-time UI where-in Developers can review the Configurator page and make changes to the UI as needed.
Once the Configurator has been defined, we need to Publish this to different Applications like ‘Manufacturing’, ‘Order Management’, ‘iStore’ .
Next, select the appropriate UI, Target Database Instance, Mode and all the Applications to which this Configuration Model should be visible. Once the Publication is generated it will be in ‘Pending’ status. We need to execute the concurrent program ‘Process a single publication’ to update the status to ‘Complete’. Once this is done the Configuration model will be available under the selected Applications.
Once the setup of the Configuration Model is complete, we can test the configuration by creating a Sales Order in OM and entering the BOM Item in the Sales Order Line.
Create a Sales Order in Order Management. Under the SO line enter the Item i.e. the BOM Model (CN1000-KHU0213)
Next, the Configurator page opens up with the Run-time UI that was set for this Configurator Model.
Once Finish button is click, the Configurator page closes and the control goes back to Order Management Sales Order Form.