Which two are use cases for Smart Push?

Smart Push is a feature in Oracle Planning that facilitates the real-time movement of data between cubes. Its primary use case is to push data from a source Block Storage Option (BSO) cube, where users input data via a web form, to a target cube, which is often an Aggregate Storage Option (ASO) cube used for reporting. This process can be configured to run automatically when a user saves data in a form, ensuring the reporting cube is immediately updated (A). Alternatively, it can be configured to run on-demand, allowing users to trigger the data push manually from the form's action menu when they are ready (C).

B. Allow users to run Smart Push in forms to move data from source aggregate storage cubes.

Smart Push moves data from a Block Storage (BSO) cube, not an Aggregate Storage (ASO) cube. ASO cubes are typically read-only reporting targets.

D. Allow the application to schedule when to synchronize data.

Smart Push is an interactive feature triggered by user actions (on save or on demand) within a form, not a background scheduling tool. Scheduled data synchronization is handled by other tools like Data Maps run as jobs.

1. Oracle Cloud

Administering Planning for Oracle Enterprise Performance Management Cloud

"Using Smart Push to Move Data":

"Smart Push enables users to instantly move data

comments

and attachments from a source cube to a reporting cube after they've changed the data in a form... You can configure Smart Push to be executed in the background when the user clicks Save on the form. Alternatively

you can configure a form to allow users to decide when to run the Smart Push." This directly supports options A and C.

2. Oracle Cloud

Administering Planning for Oracle Enterprise Performance Management Cloud

"Designing Data Maps and Smart Push":

"You can use Smart Push to push data from a block storage cube to another block storage cube

or from a block storage cube to an aggregate storage cube." This section clarifies that the source must be a BSO cube

invalidating option B. It also reinforces that Smart Push is tied to form design and user interaction

not application-level scheduling

which invalidates option D.