In Oracle Planning 2024, the approval process uses an approval unit hierarchy where parent and child relationships influence the review workflow. The two ways these relationships affect the process are:
A. When the status of all children changes to one status (for example, Signed Off), the parent status changes to the same status: Correct. In a bottom-up approval process, when all child approval units reach a uniform status (e.g., Signed Off, Approved), the parent’s status automatically updates to match, reflecting the completion of the children’s review.
B. When you approve a parent, its children are Signed Off: Incorrect. Approving a parent does not automatically sign off its children; the workflow typically moves bottom-up, requiring children to be approved first.
C. After all children are promoted to the same owner, the parent status is changed to Signed Off: Incorrect. Promotion to an owner changes ownership, not necessarily status (e.g., Signed Off). Status changes are driven by approval actions, not just ownership.
D. After all children are promoted to the same owner, the parent is promoted to the owner: Correct. In the approval hierarchy, once all child units are promoted to a new owner (e.g., for review), the parent unit is also promoted to that owner, ensuring the hierarchy progresses together.
The Oracle documentation confirms that A (status aggregation) and D (owner promotion) are key behaviors of parent/child relationships in the approval process, making them the correct answers.
