What You Need to Know to Design an Oracle EPM Cloud Application: Part 2

When designing a new Oracle EPM Cloud application, there are many factors to take into consideration.  This two-part blog series addresses items necessary to design, build, and ultimately go-live with an Oracle EPM Cloud implementation; the first post in the series is available here. This second installment focuses on business rules, security, navigation flows, task lists/approvals, and data exporting.

Business Rules:

At the heart of most Oracle EPM Cloud applications are the business rules used to create, manipulate, and move data. Business rules can be run independently, as part of a task list, or within a form. Questions to ask about business rules include:

  1. Do rules need to be established to set up any automations?

  2. Is there a need to aggregate or clear data in a “Block Storage Option” (BSO) cube?

  3. Will the budgeting or forecasting process utilize any seeding or spreading? If so, what sort of statistical accounts are required to manipulate the data as needed?

  4. How will different dimensions be used to move or group data?

  5. Is there a need to prepare data in different versions, scenarios, etc. before running a rule?

  6. Will ancillary accounts need to be populated based on seeded data? For example, automatically calculating a fringe benefits account when compensation accounts are used would require additional rules or parts of rules.

  7. If forms require action menus or smart lists, do any of those menus require a rule to run to properly execute (adding a suppressed row generally requires a calculation to input a data point to allow it to pass suppression)?

  8. Is there any sort of validation that needs to be performed on any aspect of the process?

  9. Is there some sort of check required to determine if users are entering data at a valid account string?


Establishing application security can be a very time-consuming and arduous task. Some security questions to ask include:

  1. What security is needed for dimensions, forms, task lists, approvals, etc.?

  2. How and when will security be added to the system?

  3. How complex will the security setup be? In other words, will security include manually entering users into dimensions, forms, task lists, approvals, etc., or will groups be a more efficient security method because they will allow for less manual work down the line when executing changes to the security profile?

  4. Will you use an approvals process? Can groups be established to handle this?

Navigation Flows:

Navigation flows can be one of the most useful pieces of a system build.  With the removal of composite forms, they offer a tremendous way to achieve the same capabilities as tabular forms and provide a cleaner system design in general. Some items to consider when determining whether to utilize navigation flows are:

  1. Is the ability to limit what the users see considered a “plus” or a “minus?” Navigation flows can be a major plus for design as they take away some of the anxiety related to moving to a new system with user interface items such as icons that users may not understand.

  2. Can navigation flows be used to replace composite forms?

  3. Where will most of the end users be doing their work (if the answer is in the system, this is a good use of navigation flows; if the answer is outside the systems in Smart View, navigation flows aren’t compatible at this point and task lists are a better option)?

Task Lists and Approvals:

Task lists and approvals are a tremendous way to secure application workflow, while also giving end users guidance on how to navigate the solution in a fashion appropriate to their responsibilities. When designing task lists or approvals, these are some things to take into consideration:

  1. Are task lists perceived as enhancing the user experience?

  2. Is locking users out of the system at various points so that only predetermined users can see/edit items perceived as a “good thing?”

  3. Is there a “chain of ownership” that needs to be followed so that the budget is promoted through proper channels to approval?

  4. Is it necessary for there to be a way to show the end users that they have completed all their tasks?

  5. How many levels of hierarchy will there be in an approvals process? Will this be anchored by more than one dimension?

Data Exporting:

Once the entire system has been built, there is likely a need to get the data generated back into a system of record.  This process should be simple and straightforward, but a few things to remember include:

  1. Will end users need to export data or will this only be a task for system administrators?

  2. Should this be established as an automated job or should it be created to execute on demand?

That’s all for this series; please stay tuned for more upcoming blog posts!  For additional information on successfully designing, building, and going live with EPM Cloud applications, please contact us at

#oracle #tasklists #security #OracleEPMCloud #Businessrules #enterpriseperformancemanagement #EPM #approvals #dataexporting #cloud #Hyperion #navigationflows