Oracle Configurator Developer-Repository & Structure
About this white paper
In continuation with previous article, now we will start discussing about creating the model structure with in Oracle Configurator Developer. In this article we are going to cover maximum types of nodes which can be created and their usages. This will include imported BOM and non-BOM Models, features, properties, populators, effectivity sets, model references, totals, resources etc.
Please note, for screen shots I am using Oracle EBS R12 but Oracle Configurator features discussed are also present in Oracle EBS 11.5.10.2.
Configuration Model
A configuration model is Model structure, configuration rules, and optionally a User Interface from which an Oracle Configurator end user makes selections to configure a valid, orderable item.
There are two kinds of Models: Models that you create in Configurator Developer, and imported BOM Models.
Models that you create in Configurator Developer are often created to provide guided buying or selling questions and may reference, or be referenced by, other Models.
Within a Model you can create any type of structure node, including Components, Features, Options and so on. You can also create References to other Models, or to a BOM Model.
Imported BOM Model
This BOM model is imported from Bills of Material using concurrent program "Populate Configuration Models" using Oracle Configurator Administrator Responsibility. The imported data is read-only in Configurator Developer because it must correspond to the BOM Model defined in Oracle Bills of Material throughout the business process. However, you can use Configurator Developer to add Components, Resources, Totals, and so on to meet your configuration requirements and achieve guided selling structure. Guided buying/selling structure provides a way to derive valid configurations from customer requirements or needs assessment questions.
When BOM is imported into Oracle Configurator following item attributes get imported in CZ schema
-
Item Name
-
Item Description
-
Definition - Basic definition about item viz. BOM Item Type, Minimum and Maximum Quantity, Default Quantity, and BOM Information like
-
The item’s optional children are mutually exclusive
-
The item is required in the configuration when its parent is selected
-
The item allows decimal quantities
-
The item is Trackable
-
-
Properties and Property Values- In item structure, properties are stored in Catalog Elements and Catalog Element Values. Many Catalog Elements are grouped into Catalog groups. Only one Catalog group can be attached to an Item.
-
Effective Dates
In Oracle Configurator, Item Type represent Item Catalog Group while properties represent individual catalog elements. In Configurator heirarchy items are children of item types.
For imported items since Oracle Bills of Material data must remain consistent in Configurator Developer, you cannot delete or modify imported Items, Item Types, or Properties. You can add Properties to imported Items or Item Types. However, if you add an imported Property to an Item or Item Type, Configurator Developer does not allow you to delete the Property.
Extending Imported BOM
Importing a BOM Model creates a model and structure automatically in Configurator Developer, but you can also create models from scratch. All nodes, whether imported with a BOM or created from scratch, can participate in configuration rules. The imported BOM can be extended by adding item within configurator developer. This is generally required for guided selling or giving more information about the MODEL/order being placed etc. The top level root node must be an imported BOM to be orderable in OM. Internally, the ORIG_SYS_REF of the configuration model root must match the INVENTORY_ITEM_ID/ORG_ID of the BOM being configured. Guided selling structure must be a child of the BOM Model root.
MODEL structure
Model structure contains various type of nodes viz.
-
BOM Models
-
BOM Option Classes - A BOM Option Class is typically a group of related BOM Standard Items
-
BOM Standard Items - A BOM Standard Item is any Oracle Inventory Item that can be a component on a bill,including purchased items, subassemblies, and finished products. A BOM Standard Item is analogous to a Feature Option in Configurator Developer.
-
Components - A Component is a configurable part of a Model
-
Feature - A Feature can either be selected or accept input (depending on its type) at runtime when configuring a Component. There are various types of features viz. Option Feature, Integer Feature, Decimal Feature, Boolean Feature and Text Feature
BOM Models have Option Classes and may also contain other BOM Models (for example, a PTO that contains an ATO). Each Option Class contains Inventory items marked as Optional in Oracle BOM. Required items are not configurable, so they are not imported into Configurator Developer. However, these items are added to the sales order automatically when the model is configured.
Components have Count parameter that determines:
Whether an instance of the Component is required (minimum is 1 or more) or optional (minimum = 0) within the configuration
The maximum number of instances of the Component that can exist in a valid configuration
In Configurator Developer:
A BOM Model is equivalent to a Component
A BOM Option Class is equivalent to a Feature
A BOM Standard Item is equivalent to an Option
Each BOM Item is imported with a Minimum Quantity, Maximum Quantity, and Default Quantity. The Minimum Quantity is the smallest number of the selected Item allowed per parent. The Maximum Quantity is the largest number of the selected Item allowed per parent. The Default Quantity is the number of the selected Item per parent if not modified in the selection process.
Properties
Imported properties come from Item Catalogs in Oracle Inventory. As discussed in earlier, Item Types in Configurator are equivalent to Item Catalog Groups in Oracle Inventory and Item Properties are same as Item Catalog Elements. You can add properties to Item Types in the Item Master using Configurator Developer. You cannot edit or delete properties added to the Model from the Item Master using Populators. You can add properties directly to nodes in the Model, but they are not added to the Item Master.
Repository
Creating various types of objects in Repository. Folders are generally created to group the items/properties etc. To start with one should first create a folder where all components, option features and other nodes reside.
Folder
Move the related imported BOM in newly created folder using Move Action.
Define MODEL
Define Model in new folder by clicking Create Icon infront of folder PB8104 and select Model as Object Type. This is a non-BOM model which will be used for guided selling of imported BOM Model. This non-BOM model can contain components, option features, text features etc. which may or may not be based on items. This can contain Non-BOM items which are necessary for guided selling.
Define Option Feature and Options
Navigate to Model Structure of newly created Model.
Click on Create Icon in MODEL (PB-Referenced Customer Requirements) line and select Node type as Option Feature. This type of Feature contains Options, which appear as children of the Feature node in Configurator Developer. End users select Options at runtime when configuring the Feature. An Option Feature is also known as a List of Options Feature. So after creating Option Feature we need to add valid Options to the structure.
Create Options for newly created Option Feature by clicking Create icon structure view infront of Option Feature Line.
Create multiple options for a given option feature. This will display the structure as follows
Item Based Option Feature
Item based Option features are created in the similar manner except instead of Basic Node one has to select Item Based Nodes and select one of the Item Types. Later while adding Options to the option feature on has to select Item Based Options and select individual items under previously selected Item Types.
Boolean Feature
As the name suggests, this type of feature can have two values True (Selected) or False (Not Selected).
To Create Boolean Feature, Click Create icon at Model Line (PB-Referenced Customer Requirements)
Similarly all other types of features can be added to the MODEL. Other types of features are as follows:
Integer Feature (Numeric Feature)
This can hold whole number at runtime. We can specify minimum and maximum values to validate the input data. Initial value can also specified at design time which is displayed at runtime when the session begins.
Decimal Feature (Numeric Feature)
This is similar to Integer Feature except it can hold decimal values.
Text Feature
This type of Feature appears as an input field in the runtime Oracle Configurator and accepts both alphabetic and numeric characters.
Model References
A Model Reference node (or just Reference) indicates another Model’s location in the structure of its parent Model. The parent Model is the Model containing the child Model (that is, the Reference). You can create References manually, in Configurator Developer. This is generally used for guided selling. Non-BOM Models can be added to Imported BOM. Non-BOM Model can contain various option features, boolean features, text features representing various questions/answers being presented to user.
To Create Model Reference click on the Create icon for imported MODEL line and select Model Reference Radio button on "Create Note:Select Type" Page.
Select the required NON-BOM Model on "Select Model" Page
Define Reference On next page
Components
A Component is a configurable part of a Model and can contain other Components, as well as Features, Resources, Totals, and Connectors. For example, a Computer Model may consist of Components called Hardware, Software, CD-ROM Drive, and Modem.
Totals and Resources
Totals and Resources can be children of a Model or Component node. A Total acts as a numeric variable in your Model, and can have either a positive or negative value. A Total an be used as a constant, or set when an Oracle Configurator end user makes a selection.
A Resource is similar to a Total, but a Resource ensures that the quantity it is keeping track of does not fall below zero (that is, become over-consumed). In other words, the runtime Oracle Configurator displays a message when a Resource’s value becomes negative, and flags the configuration as invalid until it reaches 0 (zero) or a positive value. When the initial value of a Total is unknown, Configuration Rules that involve the Total do not propagate.
Totals can have positive and negative values. Resources ensure the conservation of a quantity. A resource is violated if the quantity falls below zero and A violation message is displayed at run time.
For Creating resource for a component, select the node type as Resource after click "Create" icon at the Component/Model Line in structure view.
For Creating Totals for a component, select the node type as Total after click "Create" icon at the Component/Model Line in structure view.
Populators and Its Usage
You can define a Populator on a non-BOM node to automatically create child structure for that node using Items, Item Types, and Properties in the CZ schema’s Item Master. For example, you can create a Populator on Component X and specify the following criteria: "Create Options from Items where the Item is of Type Processor Speed." Running this Populator creates a Feature for each Item that matches the specified criterion.
Populater maintains the link between item master data and Oracle Configurator. When data in the Item Master changes, you can update all nodes created using Populators simply by re-running the Populator. This statement holds good for deletes as well.
In a MODEL structure, a given property can be marked as Imported or Inherited. Inherited Property indicates that a given property was attached by running populator.
A Populator can create structure on any Configurator Developer node that can have children. These include viz. A non-imported Model, A Component and An Option Feature. You cannot define a Populator on a BOM Model, BOM Option Class, or BOM Standard Item.
To define populate, click edit button of a Non-BOM model, component, option feature etc. In the node's details page, select the type of Item Master data you want the Populator to use when creating new Model structure from the Source list.
Effectivity and Effectivity Sets
Use effectivity to define the availability of a node or configuration rule and determine the model’s structure at run time. If a node is not effective, it does not appear in the run-time UI. You can define effectivity sets apply it to group of nodes viz.Models, Features, Components, Options, Rules, Totals, Resources, and model publications. Effectivity Sets may consists of 1.A range of dates or an Effectivity Set 2. One or more Usages 3. Both effective dates and Usage(s). Following screenshot show how effectivity sets are defined and used.
Conclusion
This concludes the Model Structure. I hope this will help you create various types of Nodes. In the next article we will discuss about creating various types of Configuration RULES using Oracle Configurator Developer.
Stay Tuned....................
Apps2Fusion Articles 
Comments
its very good artical.
I am working as a apps technical consultant. i read your artical.it seems to be functional topic.
my doubt is how oracle configarator usefull to technical consultants.
I have read your both article on above topic, It is very descriptive and very well documented
I have question on Migration of rule .If we have many rules , is it possible to load this in excel and upload though any API .
Can you please provide some information about API Available in Configarator module?.
Thanks ,
Rajendra Jagtap
I have created one model item and wanted to create some option but not able find create button, but i can see create button of your screen shot which you have provided. I am using R12 of Beacon Solutions. Please do let me know how can I enabled that option.
Thank s
Faiz
I need to use configurator developer to create a model that can be configured using connectors. Do you have a example on this.
Thanks,
Rajesh
Thanking you,
ashok.
This person can sit anywhere and needs to be a TECHNICAL Oracle Configurator NOT functional. This position will call for 50% travel.
To learn more about this opportunity please send you resume to andrew.augustine
Job description:
T his position will be responsible for particular levels of effort of Configurator module of the Oracle Implementation. As a member of the global design team this position will work closely with local Configurator and Order Management resources to create configurable models and implement these for various sales and service modules including Order Management, Quoting, iStore, and Installed Base. In addition, this position will also be responsible with the Global footprint.
Thi s position will establish and TECHNICALLY lead the team that will develop and support Configurator models on an ongoing basis.
The ideal candidate for this position will have intimate knowledge of Configurator design and modeling, Bill of Material restructuring, and the Oracle Configurator to Order processes. It would also be beneficial if the candidate had some familiarity with and awareness of Advanced Pricing, Configurator attributes, and designing Configurator Extensions are also required.
Key Tasks
Provide solution design and validation testing around:
Bills of Material restructuring
Configurator model structure
Configurator rules
Configurator user interfaces
Naming conventions
Develop Standards and Guidelines around Configurator Modeling
Lead and manage Configurator TECHNICAL development activities across sites, responsible to Project Management Office
After implementation should provide leadership towards continuous improvement
Teaching and Developing users at the site on the Configurator functionality of Oracle, if necessary
Document and review materials for setup and training
The hire categories will work with the Quote to Order technical team/support team to perform production support and new development in the area of Oracle 11i Configurator and related e-Business applications. Specifically, these individuals will serve as manager, researcher and developer on analysis, design, development, enhancements, and testing of the Oracle Configurator, Quoting, Sales Contracts, Install base and Order Management applications. These individuals will work directly with functional support team and Users to resolve production problems. Production support requires a 7x24 response for emergency conditions and off-hours work for build releases.
Responsibilit ies
Provide production support for the Oracle Configurator and related modules like Quoting, Sales Contracts, Install Base & Order Management applications.
This includes 7x24 coverage for emergency conditions.
Identify and propose technical solutions that meet business requirements.
Perform problem analysis, debugging and coding as part of production support and new development.
Create technical specifications, and unit test plans.
Provide work effort estimates.
Assist with the build release process as required. This is an off-hours activity.
Work with End-Users, DBA Team, Functional Team, Operations, and Infrastructure Teams as required on problem resolution and enhancements.
Andrew Augustine
Disy s Corporation
Te chnical Recruiter
1425 Greenway Drive
Suite 650
Irving, TX 75038
(214)329 -0125 (office)
(972) 550-6036 (fax)
(972)849 -5785 (cell)
andrew.augustine
It’s really good article. But I have very basic requirements.
I n Oracle 12i ,
•We defined new items, defined them as PTO and Finished goods.
•Defined BOM for those items
•Created sales order,
•Pressed "configurator" button, Selected couple of items which we had defined in BOM .(No additional setups done via Oracle Configurator.)
•Booked the order.
•After running "Workflow Background Process" with all options,
•order header in “Booked” status and line status in “Booked” and "Awaiting fulfillment"
•I am not able to close the order ,
Can you pls let me know how to proceed?
Regard s
I am new to Configurator, And this article has really helped me to understand.
But I have an question, If I need to maintain same Item with different confuigration, Can this be achieved? and how we can do it.
Also can we add delete item attributed that are migrated to CZ schema.
RSS feed for comments to this post