What are Data Maps in PBCS

Data maps are maps between a source application and a reporting application. In PBCS this would typically be a Source Planning Application (BSO) and a Target Reporting Application (ASO). But could also be a Source Workforce Planning Application (BSO) and a Target Income Statement Application (BSO).

 

From an Essbase/Hyperion Planning world then Data Maps are very similar to Essbase Partitions.

 

If you want to know “How to Create Data Maps” click on the link.

 

When would you use Data Maps

Data Maps are typically used when moving larger amounts of data once or twice a day. Such as a nightly process where all business rules and data movements are run to ensure the applications are synced up.

 

If you want to move smaller amounts of data more regularly then we would suggest using either Smart Push or X-Write. X-Refs can also be used if you want to pull the data from one application to another.

 

Another alternative method to moving larger amounts of data less regularly is Data Management (FDMEE).

 

Unsupported Features with Data Maps

The following features are not supported with Data Maps:

  • ASO Database’s with Duplicate Members enabled
  • Attribute Dimensions
  • Attribute member selections

 

Using Substitution Variables in Data Maps

  • For the Planning Application, the variable name is passed and evaluated when you move data
  • For the Reporting Application, the variable is evaluated against the Planning application and then the data value is used when you choose to clear the data in a Push Data

 

Copying Comments and Attachments using Data Maps (Only applies to BSO to BSO mappings)

With Collate turn on:

  • If there is one-to-one mapping between the source cells and target cells, then Comments and Attachments are copied from the source cells to the target cells
  • If there isn’t a one-to-one mapping between the source cells and target cells, then the Comments and Attachments from the source cells are combined and saved in the target cells

 

With Collate turned off:

  • If there is one-to-one mapping between the source cells and target cells, then Comments and Attachments are copied from the source cells to the target cells
  • If there isn’t a one-to-one mapping between the source cells and the target cells, then the last source cell’s Comments and Attachments are copied into the corresponding target cell. “Last Source Cell” means the last source cell among multiple source cells that has non-empty relational data.

 

If there is one-to-one mapping then turning Collate On or Off does not matter. It really only applies if there isn’t a one-to-one mapping.

 

Copying Supporting Detail using Data Maps (Only applies to BSO to BSO mappings)

  1. If there is a one-to-one mapping between the source cells and the target cells, then copy Supporting details are copied from the source cells to the target cells
  2. If there isn’t a one-to-one mapping between the source cells and target cells, then the Supporting details are not copied to the target cells.

 

The relational data (Comments and Attachments and Supporting Detail) selected to be copied in the Data Map Options dialog box applies only to moving data from one cube to another cube. It doesn’t apply to moving data to a reporting cube. This is only an option when moving data from a BSO to BSO database. It is not available when moving data from a BSO to an ASO database.

 

Validation Rules for Default Member

  • If the reporting cube is an aggregate storage database, then the default members must be level 0 members.
  • If the reporting cube is a block storage database, then the default members can be any members with the Store Data property.
  • If the Planning application has only dimension to dimension mappings, then the default members can be any level or data storage type.
  • If the Planning application has Smart List to dimension mappings, then default members must be only level 0. In addition, the source cube must contain a dense Account dimension with at least one member associated with a Smart List.
  • If Descendants (Acct_Default) is selected in a mapping, the Acct_Default member must exist in the reporting cube.

 

Moving Data

After setting up data maps, you can move data to a reporting cube. Planning validates the selected data maps, and then moves the mapped Planning dimension data to the reporting cube dimensions. You can also check the Job for the job status.

 

To move data to a reporting cube

  1. Create the reporting cube.
  2. Create the data map.
  3. Click Application, and then click Data Maps.
  4. To the right of the data map, click settings icon, and then select Push Data.

Confirm whether you want to clear the data before moving it.

 

Now that you understand what data maps are and do, in the next blog in the series we will show you “How to Create Data Maps in PBCS”.

 

If you have any questions please feel free to contact me at ggibney@gibneyconsulting.com