Data coming from ERP systems is usually messy. Load Rules are the 'Customs Officers' that clean, filter, and translate that data so it fits perfectly into your cube.
1. The Definition: The .RUL File
A Load Rule is a file containing instructions on how to process external data. It handles three main tasks:
* Mapping: Deciding which column belongs to which Dimension.
* Filtering: Skipping rows that you don't need (like headers or zero-value rows).
* Transformation: Changing member names or scaling numbers (e.g., dividing by 1000) during the load.
2. The "International Airport" Example
Think of an Airport Customs gate:
* The Source: Travelers arriving with different passports and languages.
* The Load Rule: The officer who checks visas (Filtering), directs people to the right lines (Mapping), and ensures they are carrying the right currency (Transformation).
Why is this helpful? It means you don't have to ask the IT department to 'clean' the data file for you. You can handle the cleaning yourself inside the rule!
3. How it is useful while building an application
* Automation: Build it once, and your daily data loads become a 'one-click' process.
* Error Handling: Load rules create 'Error Logs'. if a record fails, the rule tells you exactly why (e.g., 'Member Not Found').
* Consistency: It ensures that data is mapped the exact same way every single month, removing human error.
4. Where do we use these concepts?
* Actuals Loading: Importing monthly financial results from tools like Oracle Fusion or SAP.
* Metadata Loading: Using a rule to automatically add new 'Departments' or 'Products' to your outline.
* SQL Queries: Connecting Essbase directly to a relational database to 'pull' data using a rule.
5. Extra Information: The 'Ignore' Field
Architect Pro-Tip: You don't need to use every column in a source file. If a file has 50 columns but your cube only has 7 dimensions, you can set the other 43 columns to 'Ignore'. This makes your data processing much faster and prevents 'ghost data' from entering your system.