This chapter covers the following topics:
This chapter describes the integration of Oracle iStore with Oracle Bills of Material.
Oracle Manufacturing and Oracle Order Management use Oracle Bills of Material (BOM) to store lists of items (products) associated with a parent item and information about each item's relationship with its parent.
Oracle Bills of Material supports the following types of bills of material:
Standard
Models
Option class
Planning
You can use Oracle Bills of Material to set up configurable models, model bundles, and items with standard warranties for sale in your sites. This chapter addresses only the setup of model bundles in Oracle iStore using Oracle Bills of Material.
For information about creating bills of material for other types of products, see Oracle Bills of Material User's Guide and Oracle Inventory User's Guide. For more information on setting up configurable items, see the chapter, Integrating Oracle iStore with Oracle Configurator.
The Oracle iStore product catalog supports model bundles. A model bundle is a pre-configured model item in which all components (option classes) are mandatory.
A model bundle exists in Oracle Inventory and Oracle Bills of Material as follows:
In Oracle Inventory, one model item is the top item in the model bundle. Option classes represent every other item in the model bundle.
In Oracle Bills of Material, the model item's bill lists every option class as a mandatory component. Each option class's bill lists only one item as an option.
From the customer perspective, the model bundle consists of the Oracle Inventory model item and the items listed on the option class bills in Oracle Bills of Material.
Use a model bundle only when revenue recognition at the component item level is required. Otherwise, use a standard item for better performance.
The catalog display of model bundles is similar to standard item display.
Model bundle products are displayed in the catalog as follows:
The catalog display price is the sum of the prices for the model bundle's model item and other components, including option classes and items.
In section pages, a model bundle is listed with the descriptions of its model item. The model bundle's other components are not listed.
In a section page with single item selection, an Add to Cart button appears next to a model bundle.
In a section page with multiple item selection (which normally appears with items listed in a pull-down menu), an Add to Cart button appears next to a model bundle. Customers cannot include a model bundle when selecting multiple items for addition to their carts.
Model bundles do not appear in the menus unless Express Checkout is turned off.
The item detail page displays descriptions of the model bundle's model item and lists the model bundle's components.
Express Checkout is not available for model bundles.
The shopping cart display of model bundles is similar to standard item display.
Model bundle products are displayed in the shopping cart as follows:
A model bundle appears as one line in the shopping cart.
A Bundle Details link appears in the shopping cart line. Clicking it displays a list of the model bundle's items.
If a customer wants to use a commitment for the model bundle at checkout, he or she can only apply an open commitment. See the "Implementing Pricing" chapter for more information on commitments.
A model bundle's price is the sum of the prices for the model item and other component items.
You can set up pricing for a model bundle component in one of the following ways:
The component's price varies depending on whether the component is purchased separately or as part of a model bundle.
The component's price is always the same.
Use the pricing attribute Model Id to allow variable component pricing depending on whether it is purchased separately or as part of a particular model. When the component is purchased separately, no pricing attribute is passed to Oracle Pricing. When the component is purchased as part of a model, the model ID is passed to Oracle Pricing as the pricing attribute Model Id.
Model bundle pricing is available only for the model item's primary unit of measure (UOM).
Example: Pricing Model Bundle Components
The item Java Book has the following pricing:
$20 when purchased separately
$5 when purchased as part of a Java course
To establish this pricing, the price list must have two lines for the item Java Book:
Java Book $20
Java Book $5, Model Id = Java course's model ID
Use the following procedure to create a model bundle. See the chapter, Verify Mandatory Dependencies, for more details about creating site products.
Prerequisites
Set up the Oracle Configurator servlet as described in the chapter, Integrating Oracle iStore with Oracle Configurator, and the Oracle Configurator Installation Guide. Oracle iStore uses the Oracle Configurator servlet to retrieve model bundle information. You do not need to create Configurator UIs for model bundles.
Set the profile option, BOM: Configurator URL of UI Manager, to Oracle Configurator Servlet URL. Set the profile option at site, application, and IBE_CUSTOMER responsibility levels. Remember, if you are implementing multiple organizations, you will have more than one customer responsibility. Be sure to set the profile option for all customer responsibilities for all organizations. See the appendix, Profile Options, for details.
Steps
Login to Oracle Forms with Inventory responsibility. In Oracle Inventory, create the model bundle's model item with the following settings:
In the Bills of Material tab:
BOM Allowed = Yes (checked)
BOM Item Type = Model
In the Work In Process tab:
Build In WIP = No (unchecked)
Supply Type = Push
In the Order Management tab:
Pick Components = Yes (checked)
Remember that pricing for a model bundle is available only for the model item's primary UOM.
In Oracle Inventory, create the model bundle's option classes with the following settings:
In the Bills of Material tab:
BOM Allowed = Yes (checked)
BOM Item Type = Option Class
In the Work In Process tab:
Build In WIP = No (unchecked)
Supply Type = Phantom
In the Order Management tab:
Pick Components = Yes (checked)
In Oracle Inventory, create the model bundle's non-model items with the following settings:
BOM Allowed = Yes (checked)
BOM Item Type = Standard
These items will be included in the option classes' bills in Oracle Bills of Material.
In Oracle Bills of Material, create a bill for each option class in the model bundle. Each option class bill should have only one item.
To ensure that prices are displayed and calculated for the model bundle's items, make the items in the option class bills optional. Oracle Order Management does not price items in a model bundle if they are mandatory.
In Oracle Bills of Material, create a bill for the model bundle's model item. Include the model bundle's option classes in the bill as mandatory components.
When you create a bill, it exists only in the current organization. If you are implementing multiple organizations, copy the bill to your other organizations, or reference the bill as a common bill. See Oracle Bills of Material User's Guide for additional details.
In Oracle Pricing, set up pricing for the model bundle's items. If you want an item to have different prices depending on whether it is included in a model bundle, use the pricing attribute Model Id as described in the section, "Model Bundle Pricing", in this chapter.
The model bundle's model item should have a price of zero, without any modifiers.
The model bundle's option classes should have prices of zero, without any modifiers.
The items in the option classes' bills should be set up with prices and any applicable modifiers.
If you have set up a pricing attribute for an item, you must run the Build Attribute Mapping Rules concurrent program to generate and display the correct prices. Follow the directions in Oracle Pricing User's Guide. Restart the Application server after the concurrent program completes.
See also:
Oracle Bills of Material User's Guide
Oracle Inventory User's Guide
Oracle Pricing User's Guide