After setting up application mappings, you can push data to a reporting application. Planning validates the selected application mappings, and then pushes the mapped Planning dimension data to the reporting application dimensions. You can also check the Job Console for the job status. See Mapping a Planning Application to a Reporting Application.
Note: | If you enabled parent members for dynamic children in both a block storage and aggregate store application and added a dynamic member, you can use Push Data to successfully push data from the block storage to the aggregate storage application without refreshing the database. |
Note: | If the aggregate storage application is created outside of Planning with members that match the names of the dynamic members used in Planning, pushing data will fail because the system looks for the Essbase bucket name. This problem does not occur if the aggregate storage database is created within Planning. |
To push data to a reporting application:
In Planning, select Administration, and then Map Reporting Application.
Clear data on destination and push data: Clears the data in the target reporting application before pushing data to it.
When the target is an aggregate storage reporting application, note the following when using the Clear data on destination and push data option:
Members with nonmatching names in the target reporting application are ignored.
This option works only with member names, not with member aliases.
Use caution when using member relationships (such as Children) when selecting members for the application mapping, because using this option can cause the calculation script to exceed its length limit.
If you use member relationships, this option expands the level 0 member list in the source Planning application. If at least one member name in the source application matches a member in the reporting application, this option proceeds without error. If at least one member does not match, the option cannot proceed.
When the target is a block storage reporting application, to proceed successfully, the Clear data on destination and push data option requires these conditions:
If you use member relationships, all member names in the source application must match all member names in the reporting application.
If you map Smart Lists to dimensions, all Smart List entries in the source application must match all member names in the reporting application.
If you map Smart Lists to dimensions, the Smart List entry label in the source Planning application must match the member name in the reporting application. If a Smart List entry label does not match a member name in the reporting application, then the Smart List entry name must match the reporting application member name.
If the previous conditions are not met, the Clear data on destination and push data option cannot proceed.
Push data: Pushes the data to the reporting application without first clearing the data in the target reporting application.
If you map Smart Lists to dimensions, Smart List labels must match either member names or aliases in the reporting application. Push data does not work with Smart List entry names.