You want to track budgets and review status, process issues, and approval unit ownership. Which two statements are true about approval unit hierarchies?

Approval unit hierarchies in Planning are highly flexible. They can be configured to use a secondary dimension (A) in addition to the primary dimension (usually Entity), allowing for a more granular review process (e.g., by Entity and Product). Furthermore, the approval process is specific to a Scenario and Version combination. This means you must set up separate approval unit hierarchies for different planning cycles like Budget and Forecast (C), as they may involve different owners, reviewers, and data slices. This separation allows each process to be managed independently.

B. This option lists incorrect terminology for approval setup. The process involves defining the hierarchy, promotional path, and owners, not selecting from these templates.
D. The approval path is defined by the approval unit hierarchy itself, which can be, but is not required to be, based on an organizational structure.

Oracle Cloud

Administering Planning

"Managing the Approval Process

" Section: "Creating the Approval Unit Hierarchy." This section notes

"You can select a secondary dimension for the approval unit hierarchy."

Oracle Cloud

Administering Planning

"Managing the Approval Process

" Section: "Working with Approval Unit Hierarchies." The documentation illustrates that an approval unit hierarchy is tied to a specific Scenario and Version

necessitating separate setups for Budget vs. Forecast scenarios.