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.
14 Manage Databags
This chapter describes the Databag concept and the functionality that allow users to create and update Databags.
Databag Concept
A Databag is a collection of Product, Location, Source Location, Attributes, and Alert positions that are used to facilitate the selection process when using the Replenishment Admin workspaces. The databag is the scope of a user’s work. When working in the replenishment workspace, you only need to select the databag that you want to work with and the wizard process loads automatically all products, locations, attributes, and alerts linked to the selected databag. This way you do not need to go through the selection process every time. You only need to create a new Replenishment Admin workspace.
The following image illustrates different databags with different scopes and users. Each databag has its own scope with the assigned products, locations, calendar, attributes, and alerts.
ORACLE:
Admin User
Alerted Items/Location
Item/Location at Discovery Phase
Item/Location EOL Phase
Table 14-1 Manage Databags Workspace, Steps, and Views
| Workspace | Steps | Tab | Views |
|---|---|---|---|
| Databag Scope Workspace | Setup | Setup | Setup View |
| Product Group Scope | Product Group ScopeView | ||
| Location Group Scope | Location Group Scope View | ||
| Source Group Scope | Source Group Scope View | ||
| Alert Scope | Alert Scope View | ||
| Attributes Scope | Attributes Scope View | ||
| Databag Review Workspace | Enable & Publish | Enable & Setup | Enable & Setup View |
| Filter Conditions | Filter Conditions View | ||
| Today & Parameters | Today & Parameters View | ||
| Review Databag Details | Products | Associated Product View | |
| Locations | Associated Location View | ||
| Sources | Associated Source Location Association Count View | ||
| Weeks | Associated Week View | ||
| Alerts | Associated Alerts View | ||
| Attributes | Associated Attributes View | ||
| Product- Locations | Associated Product-Location View | ||
| Review Attributes & Alerts | Product | Product Attributes View | |
| Location | Location Attributes | ||
| Product- Location | Product-Location Attributes | ||
| Alerts | Product-Location Alerts |
Databag Scope and Review Workspaces
To build the Databag Scope or Databag Review workspaces, perform these steps:
1. From the left sidebar menu, click the Task Module to view the available tasks.
| Alerts Scope | ||||
|---|---|---|---|---|
| we | Databag | a | ||
| 1m | Alert an | a | [< | |
| Databag | Datab | agO1.01 + | DatabagO1 | .02 = |
| Alert | ||||
| Future Promotions | View | * | ||
| MaturitytoBOL | View | ad | ||
| Max Display | View | ~ | ||
| Max Stockroom | View | ~ | View | |
| Min Display | View | ~ | Filter | |
| NewSKU | View | + | ||
| No Replenishment | Filter | ~ | Filter | ¥ |
| NoReplenishmentMethod | Filter | ~ | Filter | ¥ |
• View
This value indicates that the alert should be included in the databag. The alert is then available in the Replenishment workspaces to aid in analysis and navigation. .
• Filter
This value indicates that the alert should be included in the databag scope and the alert is then available in the Replenishment workspace. Additionally, when the Filter values are selected, the scope of the databag is recalculated based on the product and alerts that match the alert.
Note
For example, if the alert New Item is included in the databag scope and set as a Filter value, the databag is recalculated and only the products associated with the New Item alert, within the defined product scope, are included in the databag. The remaining items are filtered out.
Attributes Scope View
The Attributes Scope View , under the Attributes Scope tab , allows you to select all or any specific product, location, or product-location attributes to be included in the scope of the databag.
-
Local : The Product and Location scope of this databag is based on the set up of the scope defined in the Product Group Scope and Location Group Scope views.
-
All Product : The Product scope of this databag is all Products and it ignores the set up of the scope defined in the Product Group Scope view. While the Location is based on the set up of the scope defined in the Location Group Scope view.
-
All Location : The Product scope of this databag is based on the set up of the scope defined in the Product Group Scope view. While the Location scope is all Location, it ignores the set up of the scope defined in the Location Group Scope view.
-
Global : The Product and Location scope is based on all Products and all Locations and it ignores the set up of the scopes defined in the Product Group Scope and Location Group Scope views.
Databag User Description
Databag User Description is an editable measure used to modify the description of a databag. This databag description can be set as a Visible Attribute for databag hierarchy in any other workspace.
Databag Mask
This measure allows you to select additional filters for the Product and Location scope. The valid values for this measure are:
-
All : The Product and Location scope is based on the scope defined by you in the Product Group Scope and Location Group Scope views. No additional filtering is applied.
-
Associated Valid : The Product and Location scopes defined by you in the Product Group Scope and Location Group Scope views are filtered out if the product and location combination is not assorted. This way, only valid assortment combinations is part of the databag.
-
Lifecycle Valid : The Product and Location scopes defined by you in the Product Group Scope and Location Group Scope views are filtered out if the product and location combination does not have a valid lifecycle. For example, typically, warehouses are not assorted. Therefore they are excluded by the Assorted Valid mask. However, as warehouses source assorted products for one or more stores, then they have a valid lifecycle for the products.
Matching Product-Location Condition
Matching Product-Location Condition is a calculated measure that indicates the filter condition defined in the Filter Conditions view. If there is no condition defined, it displays All. Otherwise, it displays the string with the conditions defined in the Filter Conditions view.
Product Scope Count
Product Scope Count is a calculated measure that indicates the number of products based on the product groups selected in the Product Group Scope view and the databag mask value.
Product Association Count
Product Association Count is a calculated measure that indicates the number of products based on the product groups selected in the Product Group Scope view with the filter conditions applied and the databag mask value.
Product Association %
Product Association Percentage is a calculated measure that indicates the percentage of products that are being considered for the databag. It is calculated as:
100 PRODAssoc. Count PRODScopeCount
100 LOC Assoc. Count LOCScopeCount
Table 14-2 (Cont.) Within Condition Operator Measure Available Operators
| Possible Operators | Descriptions | Example |
|---|---|---|
| < | Checks if the attribute value is less than the Condition Value | Standard deviation of sales <6 |
| ⇐ | Checks if the attribute value is less or equal to the Condition Value | |
| contain | ||
| not contain | ||
| match | ||
| not match |
Condition Value
The Condition Value measure is used when the type of the attribute is numeric. Example: average sales > 10
Condition Value String
The Condition Value String measure is used when the type of the attribute is a string. Example: brand == Private Label
Condition Value Measure
The value of the Condition Value measure is a measure name, which is populated by an expression that let’s you refine the condition value. For instance private label versus nonprivate label.
This measure is used when you want to refine the condition value.
For instance, for the 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 50.
Condition Value Date
The Condition Value Date measure is used when the type of the attribute is a date. Example: today >= 02/30/2024”
Between Condition Operator
Within a rule there can be multiple conditions and also multiple condition groups. This is specified in the Condition Group measure. Conditions with the same Condition Group value belong to the same group.
For example, if a rule has four conditions, Conditions 1 and 2 can belong to Condition group 1, and Conditions 3 and 4 can belong to the Condition group 2. Also, the Condition Order measure gives the ranking of the conditions inside the group.
The following table is an assumed use case:
Table 14-3 Between Condition Operator Assumed Use Case
| Condition | Between Condition Operator | Condition Order | Condition Group |
|---|---|---|---|
| Condition 1 | AND | 1 | 1 |
| Condition 2 | OR | 2 | 1 |
| Condition 3 | OR | 3 | 2 |
| Condition 4 | 4 | 2 |
The value for the Between Condition Operator can be the logical operators AND or OR.
The conditions are evaluated first inside a condition group and then between groups. In the previous case, the resulting condition is:
(Condition 1 AND Condition 2) OR (Condition 3 OR Condition 4)
Here is an example where all conditions belong to the same condition group:
Table 14-4 Example: All Conditions Belong to the Same Condition Group
| Condition | Between Condition Operator | Condition Order | Condition Group |
|---|---|---|---|
| Condition 1 | AND | 1 | 1 |
| Condition 2 | OR | 2 | 1 |
| Condition 3 | OR | 3 | 1 |
| Condition 4 | 4 | 1 |
The resulting condition for the rule is given by:
Condition 1 AND Condition 2 OR Condition 3 OR Condition 4
Note that the conditions are evaluated in the order given by the values in the Condition Order measure.
Condition Order
The Condition Order measure displays the order in which conditions are evaluated, wither independently or inside a condition group.
Condition Group
The Condition Group measure allows you to group conditions. This is useful when you want to evaluate conditions in a two-step process. First, the conditions are evaluated inside groups. In the second step, the group results are evaluated .
Validation Result
The Validation Result measure displays the condition expressions that are validated.
Invalid Flag
The Invalid Flag measure indicates if a condition is invalid.
Valid Flag
The Valid Flag measure indicates if a condition is valid.
| ReviewA | ttributes & Alert | s ¥ Prod | uct Location | —Product-Location | Alerts | ® | ||
|---|---|---|---|---|---|---|---|---|
| Mew | 882 | . | : | T_T | ||||
| PROD Attr | ibutes | ua f #*x | ||||||
| 4 © | Attribute £7 | [1 | Dimensions | Positio | nQuery# Measu | re(Defaut) v¥ #7 | ||
| Class | Company | Department | Division | Grandparent | Group | trem NemGroup ItemPerformance Pack Type Parent | ||
| 123 - 1234600 | 4582 olgers-Breakfast | Coffee | ‘Company | Beverage | Long LifeCyde | Folgers-Ground | Pantry | 1234582 - Folgers - Folgers -Breakfast |
| - | Maxwel House - | Coffee | ‘Company | Beverage | Long LifeCyde | MaxwellHouse- | Pantry | 1234600 -Marwe ManvelHouse - el |
| 1234747R | iese100% | Coffee | Company | Beverage | LongLifeCyde | Raa’Ground | Pantry | 1234747 -(eS ae=100% |
| 123 - F 4234759 | 4753 olgers - DarkRoast | Coffee | ‘Company | Beverage | LongLifeCyde | Folgers - Ground | Pantry | 1234753 - Folgers - Folgers -Dark Roast |
| - 4234762 | ees“Medium | Colle | ‘Company | Beverage | LongLifeCycle | Folgers-Ground | Pantry | 1234759-Folgers- poe~Medium |
| - 41234768 | oiges-French | Coffee | ‘Company | Beverage | LongLifeCyde | Folgers-Ground | Pantry | 1234765-Folgers- FeigeFoals |
- | L-100% | Coffee | ‘Company | Beverage | LongLife Cycle | PL-Ground | Pantry | 1234768 -PL- PL-100% |
| 1234769-P | L-FrenchRoast | Coffee | Company | Beverage | Long LiteCyde | PL-Ground | Pantry | 1234769 - PL- PL- French Roast |
| 123 - | 4770 L-FrenchRoast | Coffee | ‘Company | Beverage | Long LifeCyde | PL-Whole | Pantry | 1234770-PL- PsFrancheast |
| 41234771 - | L-BreakfastRoast | Coffee | Company | Beverage | LongLiteCyde | PL- Whole | Pantry | 3234771 -PL- PL BreakfastRoast |
| 1234772 - | L | |||||||
| - | -DarkRoast | ee | ‘Co | e | PL | 3 - =Dark -D rkRoast | ||
| 1234774 - | PL FrenchRosst | Coffee | ‘Company | Beverage | LongLife Cyde | PL-Ground | Pantry | WSATT4=PL- PeFrenchRoast v |
| <I | 7 | ] | > BBcalcuate(F9) |
This measure displays the product-location attribute values.
Manage Databag Action Buttons
The Manage Databag workspace has the following action buttons available:
- Calculation Databags
Use the Calculation Databags action button to calculate the databag scope based on all the set up you created. The result is the Boolean measure that is used by the Replenishment workspace to load the correct scope of products, locations, source locations, attributes and alerts.
- Publish Data
Use the Publish Data action button to commit the changes made in the Manage Databag workspace. It also saves the audit information of the update and commits the measures Last Databag Publish User ID and Last Databag Publish Date based on who and when the Publish Data was last run.
- Validate Databag
Use the Validate Databags action button after you make the desired setup for the databags. If there are no errors, you can run the Calculate Databags action button to create the databags.
- Lookup Attributes
Use the Lookup Attributes action button to populate the relevant attribute values when setting up the rule conditions.
The sequence of actions in the Manage Databag workspace is expected to be:
1. Build workspace.
2. Click Lookup Attributes action button if you want to set up rules or you want to perform What-if.
3. Set up rule conditions.
4. Click Validate Databag action button.
5. If no errors, click Calculate Databag action button.
6. View results.