EPM Tech Tips · EPCM · 02
The job finishes without errors, the status says completed, and the destination is still empty. In Oracle Enterprise Profitability and Cost Management, an allocation rule that finds nothing to allocate does not fail. It writes nothing. This guide gives you a fixed order of checks.
Before you start
Write down the exact model, POV (Years, Period, Scenario, Version) and rule name. Then run that one rule on its own. In the UI, set Processing Range to Single Rule. From EPM Automate (Service Administrator role): epmautomate calculateModel "FY26::Jan::Actual::Working" "My Model" SINGLE_RULE ruleName="My Rule" executeCalculations=true clearCalculatedData=true. Clearing removes that rule's earlier results, so use a Draft POV you may recalculate. When you rerun, select Capture Diagnostics Data under Processing Options. If the rule finds no source or no driver, the job log says so.
Pick your route. If no rule in the model posted anything, start with steps 1 and 2. If other rules post and only one comes back empty, go to steps 3, 4 and 5.
Step 1 · Did the calculation execute?
What happens. A calculation run can clear data, run rules, or both. A run that only clears calculated data finishes cleanly and leaves the destination empty. So does a run against another POV.
How to check.
Go to Home › Modeling › Calculation Control and confirm the POV you ran is the one you are reviewing, and that its Status is Draft. Published and Archived POVs cannot be calculated.
Check the Processing Options used for the run. Run Calculation must be selected, not only Clear Calculated Data.
If the run came from EPM Automate, look at the command. In calculateModel, executeCalculations defaults to false and must be set to true.
Go to Home › Modeling › Calculation Analysis, select the calculation record and confirm the model and POV it ran.
Fix. Run again with Run Calculation selected, for the right model and POV. With Clear Calculated Data on a full POV, every calculated result in it is cleared and rebuilt, so agree the run with the model owner.
Step 2 · Are the rule set and the rule enabled and valid?
What happens. Rule sets and rules each have an Enabled setting. A disabled rule, or any rule in a disabled rule set, is skipped without a warning. A rule that references a deleted or renamed member does not run either.
How to check.
Go to Home › Modeling › Designer, open the Waterfall Setup tab and select the model.
Open the rule set's Definition tab and check Enabled. Do the same on the rule's Definition tab.
Check the rule's Sequence. If you ran a range of rules, confirm the rule's sequence falls inside that range.
In Designer › Mass Edit, select the model and rule set. The rule status column shows disabled rules at once. Run Validate Model and read the Errors column.
Fix. Enable the rule set and the rule (Actions › Enable Rules in Mass Edit fixes many at once), fix any rule that fails validation, and rerun.
Step 3 · Is there source data where the rule reads it?
What happens. A rule allocates what it finds at its source intersection for the POV you calculate. Data loaded to another POV or member, or not loaded, leaves nothing to send. The source also includes amounts allocated into it by earlier rules, so a source that depends on a prior rule is empty if that rule did not run first.
How to check.
Open the rule and note every member on the Source side of the Source/Destination tab, including the Entity, Account and custom dimensions.
If Use Rule Set Context is selected on the rule, the source members also come from the rule set's Member Selections tab and from any enabled Model Context. Check those too.
Build an ad hoc grid for the POV and the source members. Check PCM_Input at PCM_Rule NoRule for loaded data, and PCM_NetBalance at the top of PCM_Rule for what earlier rules have already sent there.
On the rule's Definition tab, check Allocated Amount Type. The default is None (allocate 100%). Percentage or Currency with an Amount of zero allocates nothing.
Fix. Load the data to the right POV and members, change the source selection, or move the rule after the rule that feeds it.
Step 4 · Does every destination have driver data?
What happens. With Specify Driver Location, each destination gets its share of driver value over total driver value. A destination with no driver value gets no allocation. If no destination has a value, the whole rule allocates zero.
How to check.
Open the rule's Driver tab and check the driver basis: Allocate Evenly or Specify Driver Location.
Read the driver location. By default every dimension is Same As Destination, PCM_Rule is NoRule and PCM_Balance is PCM_Input. The driver must exist at each destination intersection, at the same custom-dimension members.
If the driver comes from an earlier rule, PCM_Rule must point to that rule and PCM_Balance to the member it writes, such as PCM_Allocation In. With the default NoRule and PCM_Input, the rule will not see it.
Check whether the driver member is dynamic or an upper-level member. Oracle advises against them, because destinations without driver data are skipped.
Query the driver in an ad hoc grid at the destination members for the same POV.
Fix. Load or compute the driver where the rule expects it. Oracle recommends a custom data prep rule that builds driver values before the allocations that use them. As a quick test, switch the rule to Allocate Evenly. If amounts now post, the problem is the driver.
Step 5 · Do source, destination and driver line up?
What happens. The driver is read at the destination's intersection unless you fix a member. If the destination uses No Product and the driver was loaded by product, or the driver is fixed to a member that has no data in this POV, the lookup returns nothing.
How to check.
Compare the Destination column with the driver location, one dimension at a time. Look for No<dimname> members on one side and real members on the other.
If a dimension is fixed in the driver, confirm that one member has data for the POV you calculate.
Fix. Align the driver location with the destination, or fix the driver to the member that holds the data.
Step 6 · Where did the rule write, if anywhere?
Go to Home › Modeling › Rule Balancing, select the cube and the POV, and click Refresh. Select the rule and use View Rule Data to see what it wrote. Then run Calculation Statistics - Summary from Calculation Analysis (More Actions) and look at the data cells the rule wrote. If you ran with Capture Diagnostics Data, the job log already names the missing side. Zero cells written means no source or no driver. Cells written but nothing at your destination means you are looking at the wrong intersection.
Quick checklist
Run Calculation selected, right Draft POV · Calculation Control, calculateModel
Rule set and rule enabled, valid, in range · Designer › Waterfall Setup, Mass Edit
Source data at the source members · Source/Destination tab, ad hoc grid
Driver data at every destination · Driver tab, ad hoc grid
Driver location aligned with destination · Driver tab vs Destination
Cells written by the rule · Rule Balancing, Calculation Statistics - Summary
Pedro San Martín · Founder & Principal, Asher & Company
