A Smart List in Oracle EPM Planning is a custom enumerated list that is assigned to a specific member of the account or custom dimensions — replacing the standard numeric data cell at that account/member intersection with a drop-down selector that allows the user to choose from a defined set of text values. Smart Lists are used in planning forms where a planning assumption is a categorical selection rather than a numeric value: the depreciation method applicable to a capital project (Straight-Line, Accelerated, Units of Production), the headcount classification of a new position (Permanent, Fixed-Term, Contractor), the approval status of a capital expenditure item, or the regional market classification of a revenue line. By constraining input to the Smart List’s predefined values, the planning application enforces data quality at the point of entry — the user cannot type an invalid value, and the business rule that reads the Smart List value operates on a known, consistent input set.
Smart List Architecture
| Smart List Element | Content |
|---|---|
| Smart List name | The identifier used to reference the list in member formula and Calc Script |
| Entries | The set of selectable values — each entry has a Label (displayed to the user) and an internal numeric ID (used in Calc Script references) |
| Missing label | The text displayed when no value is selected (default: #MISSING) |
| Account member assignment | The Account dimension member (or custom dimension member) to which the Smart List is assigned — replacing the numeric data type with the Smart List selector |
Smart Lists in Business Rule Logic
The primary use of Smart Lists in planning applications beyond data quality enforcement is calculation branching — where a business rule uses the Smart List selection to determine how a value is calculated. For example, a workforce planning model might have a “Contract Type” Smart List with entries Permanent (ID: 1), Fixed-Term (ID: 2), and Contractor (ID: 3). A headcount cost calculation business rule reads the “Contract Type” member for each position and branches the cost calculation: Permanent positions calculate employer social insurance contribution (GOSI in Saudi Arabia, GPSSA in UAE) on top of base salary; Fixed-Term positions do not; Contractors calculate a management fee markup on the day rate. This conditional calculation in Calc Script or member formula uses the Smart List’s numeric ID — IF(@SMARTLIST(“ContractType”) == 2) — to identify Fixed-Term positions and apply the appropriate cost logic.
GCC Context: Smart Lists for Localisation
Smart Lists in GCC planning applications are frequently used to capture regional compliance classifications that affect cost calculations. A Saudi headcount planning form might include a “Nationality” Smart List (Saudi, Non-Saudi) that drives Saudisation/Nitaqat compliance tracking and determines whether GOSI employer contributions apply at the Saudi rate or the expat rate. A UAE entity’s project planning form might include a “Contract Category” Smart List that determines whether UAE labour law provisions — gratuity accruals, UAE WPS compliance categories — apply to the position. These localisation-driven Smart Lists connect the planning model to the regional compliance requirements without requiring the planner to know the precise contribution rates — the business rule looks up the rates from a rate table based on the Smart List selection.
What Goes Wrong in Practice
The most common Smart List failure in production planning applications is a business rule that references a Smart List entry ID that was subsequently changed or deleted when the Smart List was modified. Smart List entry IDs — the numeric identifiers that Calc Script references — are assigned at list creation and should never be changed; if an entry is deleted and a new entry with a different ID is added to replace it, every business rule that referenced the original entry ID produces incorrect branching logic. Smart List entries must be treated as immutable once they are referenced in business rule logic; adding new entries is safe, but deleting or renumbering existing entries requires updating all business rules that reference the affected IDs.
How Loop Wise Solutions Designs Smart Lists
We document every Smart List in the EPM application design specification — listing the entries, their IDs, the account members they are assigned to, and every business rule that references each entry ID. This documentation prevents the entry modification errors that are otherwise discovered only when a calculation produces an unexpected result after a Smart List maintenance change.
