When should a full data map be used instead of Smart Push?

In Oracle Enterprise Performance Management Cloud, Data Maps and Smart Push serve complementary roles for moving data between cubes or applications. Smart Push is optimized for moving small, targeted slices of data dynamically, such as when a user saves a web form. In contrast, running a full data map execution is designed for moving large volumes of data or bulk synchronization across applications or plan types. Full data maps execute as asynchronous background jobs capable of processing extensive dimension intersections without causing form submission latency or exceeding real-time payload limits. Therefore, when transferring comprehensive data sets or performing end-of-period bulk data transfers, a full data map must be executed rather than using Smart Push.

B. Generating financial reports is a reporting function performed via Financial Reporting or Reports, not an operational use case for executing full data maps.

C. Reconfiguring user roles is an administrative access management task handled in Access Control or Identity Management, completely unrelated to data map execution.

D. Automating period mapping is configured within Data Integration or Data Management settings, not a reason for choosing full data maps over Smart Push.

- Oracle Cloud EPM Documentation, Administering Planning, "Moving Data Between Cubes Using Data Maps"

- Oracle Cloud EPM Documentation, Administering Planning, "About Smart Push and Data Maps"