MDO/COE: How is Eligibility Criteria Configured? (Doc ID 1604117.1)

Last updated on FEBRUARY 01, 2016

Applies to:

Oracle Retail Clearance Optimization Engine - Version 13.3.1 and later
Oracle Retail Markdown Optimization - Version 4.0 and later
Information in this document applies to any platform.

Goal

Eligibility in Oracle Retail Markdown Optimization (MDO) and Oracle Retail Clearance Optimization Engine (COE) is defined as all the items (where an item is the merchandise-location combination at the optimization level) that will be passed to the Calculation Engine (CE).  Not all of these items will get a forecast or recommendation; some will fail validation or not need a recommendation.  However, all items will be passed to the CE.  In MDO, all of these items will be visible in the frontend for users to review.

It is important to define eligibility criteria so that only items which need to be acted upon will be processed.  Sending all items to the model is often unnecessary and impacts run-time.  For MDO, users may wish to see non-forecastable items (for example, items with a very recent exit date or new items without a model start date) in the frontend, and thus the eligibility criteria may be broader.  For COE, eligibility can be restricted to items that users will want forecasted (recommended by the CE or for What If purposes).

How then, is eligibility configured?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms