Using Smart Push to synchronize plan types in Oracle PBCS

Oracle PBCS offers a feature called Smart Push that allows you to push data i.e. synchronize data between plan types when a form is saved. For example, you can setup Smart Push so that data from the BSO plan type is pushed to the ASO plan type whenever a form is saved thus ensuring that the ASO reporting plan type is always consistent with the BSO plan type.

Please note that by default only the form context (i.e. member intersection or POV) is set to be copied over but this can be over ridden and member selections can be done to copy over a much larger data set than that covered by the form intersection. The override option (which is what I think makes it Smart) is useful when you have a business rule set to run on save on the form that will manipulate data other than just the intersections on the form and you want this additional data to be pushed over as well.

Set up Reporting Application Mapping

To use Smart Push, you must first set up a mapping using the ‘Map Reporting Application’. To do this, from within the PBCS Workspace, navigate to Administration->Map Reporting Application. Next, Click on ‘+’ sign to create a new map.

01 Oracle PBCS Map Reporting Application

02 Oracle PBCS Create Map

Provide a name (e.g. BSOToASOMap) to the mapping and then select the source plan type from the source application. From the Reporting Application section, click and select the target plan type. In this case I have selected an ASO reporting application with plan type ‘RptApp’.

02 Oracle PBCS Create Mapping

Then click on Next to map the individual dimension members. The default settings are all level zero descendants from the source plan type dimensions are mapped to all level zero descendants of the target plan type dimensions. There are three types of mappings available. Not Linked mapping is where you do not want to map a dimension, Dimension to Dimension is a straight one to one mapping and Smart List to Dimension displays the available Smart Lists. When a Smart List is selected, the account members associated with it are displayed. If there is only one member, it is automatically selected.

Based on your design, there may be an instance where the number of dimensions in the source and target are different. In this example, my source plan type does not have the Employee dimension and hence it is not linked. The next step will allows you to map the data to a member in the target plan type employee dimension. Make changes here based on your synchronizing needs. Then, click on Next.

03 Oracle PBCS Map Dimensions

In the point of view tab, I have put in ‘No Employee’ as the member within the employee dimension where I want to load data from the source plan type. Click on Next.

04 Oracle PBCS Point of View

The ‘Data Options’ tab allows you set copy options for Comments, Attachments and Supporting Detail. The default is ‘Do Not Copy’. Click ‘Finish’ to finish setting the map reporting application.

Add Smart Push to the data form

To set up a form to use Smart Push, edit the data form and go to the Smart Push tab. Click on the ‘+’ sign

05 Oracle PBCS Enable Smart Push on Form

You will see a list of all the mappings that you may have created. Select the mapping you want to use and click Ok.

06 Oracle PBCS Select Mapping on Form

The default view is as shown below with an option to ‘Run on Save’ option. Make a note of a very useful feature to expand the mapping and override the form context with different member selection. This feature is what I find particularly useful or ‘Smart’.

07 Oracle PBCS Smart Push Overwrite

Expand the mapping by clicking on the expand option on the left of the mapping name to reveal a feature to override the form context. In the example below, for Currency dimension, I unchecked the ‘Use Form Context’ option so that I can override it. On my data form, the member from Currency dimension is ‘Local Currency’, however I am doing a currency conversion with a business rule set to run on save and hence I am overriding this to include USD and EUR along with Local Currency. When the form is saved, data for Local Currency, USD and EUR will be copied over to the target application. Click on Finish to finish editing the form.

08 Oracle PBCS Smart Push Overwrite Selection

When a form on which Smart Push is enabled is saved, you will receive a success notification if all goes well. The sequence of activities is Data is saved, Business Rule is executed and then Smart Push is executed.

09 Oracle PBCS Smart Push Successful Message

11 thoughts on “Using Smart Push to synchronize plan types in Oracle PBCS

    • Hi Pete,

      Nothing in the documentation that says anything specific on the functionality used to push the data.

      However, per the Oracle documentation, “Smart Push always clears data in the target region before pushing new data”
      This hints towards using a direct partition as opposed to a Java API or dataexport and load rules.


      Hi Pete,

      I stand corrected. This uses Java API internally.


  1. Hi,
    Pushing data from Map Reporting application is much faster than running the same mapping from Smart push. It is supposed to be faster for better user experience.


  2. Question1:
    If smartpush always clear target region means,it will also clears extra dimensions like employee as part of reporting ASO cube?

    Question 2:
    How to load data into
    Reporting ASO cube with extra dimensions like employee which is not in BSO?

  3. Basically I wanted to know in PBCS instance how to load the data (plan specific data into BSO&reporting specific additional data into ASO) through FDMEE

  4. Answer 1: Smart Push will clear the data for the region specified in the mapping. It will not clear any dimensions.

    Answer 2: If you read the post, I have given an example where we are loading data from a source plan type that does not have an Employee dimension to a target which has an employee dimension. In this case you will map the data to a ‘No Employee’ or something similar in the target.

    In FDMEE, navigate to Setup->Register->Target Application. Then click on ‘+ ADD’. In the Select Application drop down, select Essbase. This will then list all the ASO plan types you have setup. Once you have added this target, load data as you would normally using FDMEE.

  5. Hi,

    It is a very informative blog.Thanks very much for this.

    I have two queries regarding PBCS. First one is there any option for partitioning in PBCS ?

    2.If not then how can we move data between two plan type ? is smart push is the only option ? or is there any other mechanism exist ? Does XREF work here ?

    Will wait for your early reply.


    • Hi Moumita,

      Thank you very much. There is no partitioning available in PBCS.
      You can move data between two plan types using:
      Smart Push,
      XREF (you can get location alias through Calc Manager),
      Using a feature called as ‘Map Reporting Application’


Leave a Comment