In Oracle Planning 2024, data maps with Smart Push or manual execution can push various types of data between cubes within the same application or across applications. However, not all items can be transferred.
The item that cannot be pushed is:
* A. Comments: Incorrect. Comments (cell-level annotations) can be pushed between cubes using data maps, provided the mappings include the necessary dimensions.
* B. Attachments: Incorrect. Attachments linked to data cells can be transferred via data maps, as long as the target cube supports them and the mapping is configured correctly.
* C. Data change history: Correct. Data change history (audit trails tracking who changed what and when) is not transferable via data maps. It is metadata tied to the source cube's audit log, not a pushable data element.
* D. Supporting detail: Incorrect. Supporting detail (breakdowns of aggregated values) can be pushed between cubes if the target cube is configured to accept it and the mapping includes it.
The Oracle documentation specifies that data change history is excluded from data map transfers, as it's a system-maintained log, not a user-editable or movable data type, making C the correct answer.
References:
Oracle Planning 2024 Implementation Study Guide: "Data Maps and Pushable Items" (docs.oracle.com, Published 2024-10-05).
Oracle EPM Cloud Documentation: "Smart Push Capabilities" (docs.oracle.com, Published 2023-12-15, updated for 2024).

In the Oracle Planning 2024 Workforce module, the Synchronize Definitions Mass Update form is the tool provided to update employee properties, job properties, or salary-related information in bulk. This form allows administrators to modify and synchronize metadata definitions across multiple employees or jobs efficiently, ensuring consistency in workforce planning data.
* D. Synchronize Definitions: This form enables updates to employee properties (e.g., status, department), job properties (e.g., job code, title), and salary-related information (e.g., salary basis, grade). It is designed to handle mass updates to metadata and ensure that changes are reflected across the Workforce model.
* A. Synchronize Defaults: This option is related to applying default assumptions or settings to data, not specifically for updating employee, job, or salary properties.
* B. Process Updated Data: This form focuses on processing data changes (e.g., recalculating costs after data entry), not on updating properties or definitions.
* C. Process Data and Synchronize Defaults: This is a combined action that processes data and applies defaults, but it does not specifically target updates to employee properties, job properties, or salary information.
The Synchronize Definitions form stands out as the correct choice because it directly addresses bulk updates to workforce metadata, aligning with the question's focus on properties and salary-related information.
References
* Oracle Enterprise Performance Management Cloud Documentation: "Managing Workforce - Mass Update Forms" (docs.oracle.com, updated 2024). Describes the "Synchronize Definitions" form as the tool for updating "employee properties, job properties, and salary-related information."
* Oracle Planning 2024 Implementation Study Guide: Confirms that "Synchronize Definitions" is the Mass Update form for modifying workforce metadata.