A pricing strategy is a pricing entity that defines the overall pricing approach for a market segment. A pricing strategy consists of a header and one or more pricing segments.The header contains the general information and settings for the pricing strategy, such as the name, description, objective, business unit, default currency, start date, and end date1.When creating a pricing strategy header, the following fields are required2:
* Name: The name of the pricing strategy. It must be unique within the pricing business unit.
* Business Unit: The business unit that owns the pricing strategy. It determines the scope and visibility of the pricing strategy.
* Default Currency: The currency that is used for the pricing strategy. It is used to convert the prices of the items that are priced in different currencies.
* Start Date: The date when the pricing strategy becomes effective. It cannot be earlier than the current date.
References:
* Overview of Pricing Entities
* Create Pricing Strategy Headers

http://www.oracle.com/technetwork/fusion-apps/orderorchestrationguide-e22707-01-1514572.pdf

To enforce the requirement that the front camera option is not available when the customer chooses the widescreen display, the client needs to use two configurator model components: configurator rules and model structure. Configurator rules are the logic and constraints that define the valid and feasible configurations for a product or service.Model structure is the hierarchical representation of the features and options that the customer can select1. By using configurator rules and model structure, the client can create a conditional expression that hides or disables the front camera option when the widescreen display feature is selected.
References:
* Overview of Configurator Models

Needs to be run manually for Inventory MINMAX

Extensible Flexfield attributes are custom attributes that you can add to Order Management entities to capture additional information that is specific to your business needs. You can use these attributes in approval rules for sales orders to define conditions and actions based on the values of the attributes. The order entities that support the use of Extensible Flexfield attributes in approval rules for sales orders are Header, Line, and Fulfillment Line. These entities have predefined Extensible Flexfield categories that you can configure and deploy in the Setup and Maintenance work area. You can also access and update these attributes in the Order Management work area.
References:
* Overview of Using Extensible Flexfields in Order Management
* Set Up Extensible Flexfields in Order Management
* Oracle Order Management Cloud - Extensions