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.
11
Control and Tactical Center
The Control and Tactical Center (CTC) is an administration workspace in Oracle Retail AI Foundation. It provides centralized access to shared business rules, strategies, alerts, credentials, and application settings for Pricing Optimization, Inventory Optimization, and Promotion Management.
Depending on your assigned role and the applications licensed for your environment, one or more of the following modules may be available:
-
Rules Management: Create and maintain business rules for supported Oracle Retail applications.
-
Strategy Management: Define strategies and associate business rules with supported optimization workflows.
-
Manage System Configuration: Configure application and system parameters.
-
Alert Management: Configure and monitor application alerts.
-
Credential Stores: Manage credentials used by Oracle Retail applications and integrations.
Because CTC supports multiple Oracle Retail applications, the available rule categories, strategies, alerts, and configuration options depend on the products deployed in your environment.
Before finalizing, verify that Strategy Management , Manage System Configuration , and Alert Management exactly match the labels currently displayed in the product UI.
-
Rule: Logic that controls a process such as optimization, automatic approval, or alert generation. A rule is based on business requirements and consists of rule criteria and one or more rule values.
-
Rule criteria: The conditions that must be satisfied for a rule to take effect.
-
Rule value: A value assigned to a field used by the rule.
-
Strategy: A group of related rules that work together to support a business objective. Two types of strategies are available:
-
Default strategy: Contains the rules used during batch runs.
-
What-if strategy: Can be selected when performing an ad hoc run from the user interface.
-
Pricing Optimization
Lifecycle Pricing Optimization (LPO) uses business rules to ensure that regular price, promotion, and markdown recommendations support the retailer’s pricing objectives. Rules can protect margin, control price changes, maintain competitive positioning, and help achieve inventory and sell-through targets.
Here are the pricing optimization rules:
-
Promotion/Markdown: These rules define the constraints used to generate promotion and markdown recommendations. They include budget, pricing objective, sell-through target, exit date, temporal, pricing group, targeted offer, post-processing, promotion, and markdown rules. Together, they control factors such as available budget, promotion and markdown timing and depth, merchandise exit dates, inventory targets, no-touch periods, and coordinated pricing actions across related items.
-
Regular Pricing: These rules guide initial and updated regular-price recommendations. They define requirements related to competitor pricing, cost changes, price ranges, margins, pack pricing, price ladders, and relationships among items, locations, or price zones. They can also establish revenue, margin, and volume objectives.
Regular Pricing rules can be forecast-based or non-forecast-based. Forecast-based rules use projected demand to optimize revenue, margin, or volume. Non-forecast-based rules use business information such as costs, competitor prices, margins, and price relationships. Rules Based Regular Pricing uses only non-forecast-based rules.
Refer to the Oracle Retail Lifecycle Pricing Optimization (LPO) User Guide for the complete list of LPO’s rules for Markdown/Promotion and Regular Pricing Optimization. The list of rules also can be re-referred from the PRO_OPTIMIZATION_RULES table.
1):52, No. of Weeks Added to Exit Date (Reference Date Month 2-12): 26, Reference Date Type: M
6. For company: Company in price zone: France, season: ALL, set Reference Date Type: Model start date, No. of Weeks Added to Exit Date (Any Reference Month): 26.
7. For department: Men’s Activewear Tops class in price zone: Sweden, season: 2023 Summer, product group: brand sunset, set total budget: $250,000, allocate budget: N, include planned promotions: N.
8. For Class: Women’s Tops Sweaters, price zone: ALL, season: ALL, set Maximum number of markdowns: 4
9. For style color: Easy Fit Jean Washed Blue Medium in price zone: ALL, season: ALL, set Optimization Goal: Maximize Revenue.
10. For company: Company in price zone: France and Germany and Italy and Netherlands and United Kingdom and season: ALL, set Absolute Exit Date: 2026-02-2
Examples for Regular Pricing Rules
1. For Department 101-Women’s Tops in United States primary zone group, Price of item needs to be less or equal than this value: 200. Soft priority 8.
2. For Group 12-Men’s Clothing in all zones, maximize revenue.
3. For Department 101-Women’s Tops in Primary Zone Group, apply the price max rule with value 200 for either United States or Canada as a soft constraint with priority 8.
4. For Department 104-Women’s Bottoms in United States, Products in Set A need a price greater or equal than this value compared to items in Set B.: 10. Product Group Set A is Brand - 21Sunset and Product Group Set B is Brand - Adidas. Soft priority 100.
5. For Class 3-Coffee & Tea in United States, Volume for group of items needs to be greater or equal than this value: 500. Soft priority 4.
6. For Sub Class 6-Sweetcorn in Canada, Price of item needs to be greater or equal than this value: 2.50. Soft priority 5.
Manage Strategy
A strategy is a collection of business rules that work together to support a specific business objective. Use Manage Strategies to create, review, and maintain strategies and to associate the appropriate rules with each strategy. Because rules can be reused across strategies, updates to a rule are reflected in every strategy that uses it.
Creating a new strategy works in a similar way for Pricing and Inventory Management; The following process describes creating a rule for Pricing Management (LPO).
3 Partitions: high_ROS : 6554 SKU-Location med_FhOS : 5800 $KU-Location low_ROS : 4522 SKU-Location
In this guide
- Guide: AI Foundation User Guide
- Previous: 10 Oracle Digital Assistant
- Next: 12 Forecast Engine