Draft the calculation logic.
Write a reviewable CalcScript draft from selected profile evidence, confirmed Cube scope, and user-owned calculation intent.
Book 20-min demo
EPM Rule Writer
Draft CalcScript and two bounded Groovy paths: changed-members CalcScript wrappers and direct Data Map execution, all grounded in selected Profile evidence and explicit confirmation.
Supported authoring
Write a reviewable CalcScript draft from selected profile evidence, confirmed Cube scope, and user-owned calculation intent.
For a confirmed form-grid context, collect and deduplicate edited members, add them to the CalcScript FIX scope, then call the bounded calculation.
Draft one guarded Data Map execution only when its exact name, clear-data behavior, and any RTP mappings are confirmed.
Bounded Groovy authoring
CalcScript remains the default path. Groovy is drafted only when the requester has explicitly asked for a supported pattern and the necessary Profile facts are available. Rule Writer does not turn an unclear request into open-ended Groovy.
Changed-members CalcScript wrapper
The wrapper reads an Oracle EPM form grid, collects edited member values for the confirmed dimensions, injects them into the CalcScript scope, and runs the generated calculation against that bounded set.
Direct Data Map execution
The draft checks that one named Data Map exists, applies only confirmed clear-data behavior and exact RTP mappings, then prepares one direct Data Map execution with explicit failure handling.
Review boundary
Rule Writer does not deploy to Oracle EPM or execute live EPM calculations. The user receives reviewable text to assess and paste into Calc Manager.
Missing Cube scope, unsupported selectors, unclear business intent, or unavailable facts result in a clear stop or clarification, not a fabricated rule.
Approval is not finalization. A final rule requires explicit confirmation and is kept as an immutable archive revision for later review.
FAQ
A normal AI prompt starts with what a user can describe and may be unable to validate a Cube, member, RTP, Data Map, or calculation scope. Rule Writer starts from a selected local Application Profile and confirmed Cube, reads bounded technical facts through its licensed Skill, validates the draft, and stops when required evidence is missing. It produces reviewable text only; final retention still requires explicit user confirmation.
No. It produces reviewable CalcScript or supported Groovy text for the user to review and paste into Calc Manager. It does not deploy or execute live EPM calculations.
CalcScript is the primary path. The bounded Groovy scope covers a changed-members CalcScript wrapper and a direct Data Map execution with exact mappings.
It stops when required business intent, Profile evidence, Cube scope, or supported technical facts are missing or outside the product boundary.
Only explicit user confirmation writes a final rule to the immutable Rule Archive. Revisions remain available rather than silently replacing earlier text.
We can start with a CalcScript question, a changed-members form workflow, or one exact Data Map scenario.