In Oracle Planning 2024, integrating detailed Workforce data (such as salary, benefits, and taxes) into Financials involves leveraging out-of-the-box integration features like data maps and Smart Push. To override expense lines in Financials with more detailed values stored in Workforce, the correct approach is to define how Workforce accounts roll up into Financials accounts using the "Financial Statement Integration" data map. This process involves mapping specific Workforce accounts (e.g., payroll taxes, total salary) to corresponding Financials accounts and then synchronizing and pushing the data to update Financials with the detailed values.
Option A is the verified answer because it directly addresses the initial setup required to move detailed Workforce values into Financials by defining the rollup mappings in the Financial Statement Integration data map. After this mapping is configured, administrators can synchronize and push the data to reflect the detailed values in Financials reporting. Option B is incorrect because the Financials Integration Summary form is used to view rolled-up data, not to calculate compensation data for updating underlying Workforce details-this is a Workforce-specific task, not a data movement step. Option C is also incorrect, as there is no "Rollup business rule" explicitly mentioned in the Financials Integration Summary form's Actions menu for this purpose; instead, rollup occurs via data maps. Option D, while related to Compensation Data synchronization, is a narrower action that does not fully address the broader task of moving detailed Workforce values into Financials expense lines, which requires the Financial Statement Integration data map.
The Oracle Planning 2024 Implementation documentation highlights that Financials integrates with Workforce using predefined data maps, such as Financial Statement Integration, to roll up detailed employee expenses into financial reporting, making Option A the most accurate and complete step for this scenario.
Oracle Planning 2024 Implementation Study Guide: "Integration Scenarios and Workflow" (docs.oracle.com, Published 2024-08-19).
Oracle EPM Cloud Documentation: "Oracle 1Z0-1080-20 Planning 2020 Implementation Essentials" (updated for 2024 workflows).
Oracle Planning Documentation: "Administering and Working with Strategic Workforce Planning" (docs.oracle.com, Published 2024-12-04).

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.
Oracle Planning 2024 Implementation Study Guide: "Approval Unit Hierarchies" (docs.oracle.com, Published 2024-09-25).
Oracle EPM Cloud Documentation: "Managing Approvals" (docs.oracle.com, Published 2023-12-20, updated for 2024).