Data Maps Design

Designing effective data maps is crucial for ensuring accurate data integration and transformation during data loads.

Include data maps in your design to realize these benefits:

• Trickle feed data for real time reporting

• Synchronize cell commentary, supporting details between cubes and applications

• Real-time data synchronization

• Instant data movement based on user changes

• Trickle feed data from one app to another across instances

• Support member level mapping, substitution variables, and cross-dimensional combination members

• Smart List as a source while doing member mapping

Follow these best practices for effective data map design, as described in Application Design for EPM Planning (Part III): ASO, Data Maps, and Smart Push:

• Trickle feed into ASO with small slices of data for best performance.
• Smart Push enforces a limit of data movement for optimal performance. Work within this limit.
• Large data movement using Smart Push should be limited to only a few concurrent users.
• Use the database suppression option to suppress missing data at the Essbase level.
• Perform large slices of data movement using data maps.
• Use Smart Push to move data during user activity .
• Smart push gets precedence:
  • A high degree of concurrency for data push and Smart Push will cause contention
  • Data push jobs will wait
• Use Groovy to set overwrite selection to only modified data for grids with sparse members on rows.

Get additional design guidelines for data maps:

• Understanding Data Maps
• Defining Data Maps
• Moving Data