Mirror of Oracle documentation
Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.
7 Business Rule Engine
This chapter describes the tasks that comprise the Business Rule Engine for IPOCS-Demand Forecasting, including:
-
Attributes Task
-
Business Rule Group Admin Task
-
Business Rule Setup Task
Attributes Task
This section describes the Attributes task for IPOCS-Demand Forecasting.
Attributes Workspaces, Steps, and Views
The following table lists the workspaces, steps, and views for the Attributes task.
Table 7-1 Attributes Workspaces, Steps, and Views
| Workspace | Step | Views |
|---|---|---|
| Attributes Workspace | Review Step | Location Attributes View |
| Product Attributes View | ||
| Product/Location Attributes View |
Attributes Workspace
The Attributes workspace allows you access to all of the views listed in Attributes Workspaces, Steps, and Views.
The Attributes workspace allows you to review attributes that you can use in rules using the Business Rule engine. The attributes can be product specific, like brand or class. They can also be location specific, like store format, or number of stores an item is sold in. Finally, they can be Product/Location specific, like average sales, or the vendor from where the products were sourced for a specific store.
The attribute data types are:
-
String - examples are brand, region
-
Date - examples are store open date, forecast end date
-
Numeric - examples are historical average sales, coefficient of variance
The sources of the attribute information can come from various source. They can be loaded or calculated. IPOCS-Demand Forecasting GA has a set of calculated attributes that can be easily expanded to including any retailer-relevant attributes. For additional technical information on how the attributes are managed, refer to the Oracle Retail Inventory Planning Optimization Cloud Service-Demand Forecasting / Inventory Planning Optimization Cloud Service-Lifecycle Allocation and Replenishment Implementation Guide .
Select Locations
Select Products
Select Business Rule Group Type
Levels & Positions
Select Business Rule Group
Levels & Positions
Pee eeCondition | Condition eBetw e en Conditions | 2 | 3 | oR | [Conditin4{ 2 | 4 | |
This measure is used when the type of the attribute is a string. Example: brand == Private Label
Condition Value (numeric)
This measure is used when the type of the attribute is numeric. Example: average sales > 10
Condition Value (Date)
This measure is used when the type of the attribute is a date. Example: today >= 02/30/2024"
Condition Value (Measure)
This measure is used when you want to refine the condition value. For instance, for coffee items, except Private Label, you want to assign items to the rule that sell more than 50 per week. For Private Label items you may want the value to be 100.
You need to populate your Condition measure with a value of 100 for all Private Label items, and the rest of the coffee items with 100.
Condition Error String
In case an error occurs, this measure displays the reason. For instance, an attribute was of type string, and was compared to a Condition Value of type date.
Total Eligible Items
Total number of items that are brought in the workspace and are eligible to be managed using business rules.
Condition Count
Number of items that are attached to each condition.
Rule Count
Number of items that are filtered to each rule.
Business Rule Process
Perform the following steps to run the business rules.
1. Once the conditions are setup, click Calculate . Then run the custom menu Validate Rule Setup . If any rules were set up incorrectly, a message appears in the Condition Error measure.
2. Correct the conditions until the error message no longer appears.
3. Run the Assign Membership custom menu. This runs the conditions in the rules, and assigns Product/Locations to the designated rules.
4. To make sure that conditions and assignments are successful, check the Condition Count and Rule Count measures. They show you how many Product/Locations are assigned to each rule. Once you see the count and membership you can commit and after running the batch the business rules will take effect.
Rule Membership View
The Rule Membership view displays the condition and rule a Product/Location is assigned to.