Proactive insights, news and tips from Oracle Hyperion EPM and BI Support. Learn Oracle from Oracle.

Enterprise Performance Management (EPM) Cloud - Data Maps and Smart Push Optimization

Tanya Heise
Sr Principal Technical Support Engineer

Data Maps and Smart Push Optimization

Thank you to the Oracle EPM Cloud - Planning Development team for the presentation on this topic!

Check out the presentation for details on the following topics:

  • Introduction to Data Maps
  • ASO Cube Design Considerations
  • Optimal Performance Design Considerations
  • Groovy for Data Movement
  • Exclusion Feature


Data Maps:

Below are the use cases for bulk data movement:




Data Map Definition

  • Dimension to Dimension Mapping
    • Source Member Names should match with member names or aliases on target
  • Smart List from Source Mapped to Dimension
    • Smart List Labels should match with member names in target
  • Source Unmapped  Dimensions
    • Can contain functions – data from source sums up in target
  • Target Unmapped Dimension
    • Only single member allowed

Data Map Options

1. Smart List Dimension

  • Members of the dense dimension which have smart list
  • Can also be used to pivot the dense dimension to improve data extraction performance from source when no smart lists are mapped

2. Exclude Dynamic Calc Members

  • Turn off dense dynamic calcs and improve data extraction performance

3. Allow Smart Push Simultaneously

  • Allows data maps to run along with user activity
  • Size of data push should be small

4. Select Items to Copy

  • Applicable only for Smart push
  • Allows Comments, Supporting Detail and Attachments to be moved to target cube

5. Synchronize

  • Use whenever target metadata is changed before AMW


Smart Push

  • One or More Data Maps Associated to the form
  • Form Context
    • Pick Current Page/POV/Row/Column selections Union of Members from Multi Segmented forms
  • Overwrite Selection
    • Overrides the Form Context or Data Map definition for selections
    • Useful for multi-segmented forms or for scope of data outside the form definition for calculated data
    • Supports subvar/user variable selection
  • Honors User Read Security while extracting data from source and honors ‘write’ security while writing to target
  • Optimum performance when trickle fed data into the reporting cube
  • Use Database suppression
    • Compress missing data while extracting from source
    • Provides better performance in Hybrid
  • Run Smart Push in Background
    • Releases the UI thread immediately to the user
    • Use sparingly
  • Run on Save
    • Runs upon data save on the form – also known as involuntary push
    • User can invoke Smart Push voluntarily from Actions menu of the form



For more information on ASO Cube – Design Considerations, Optimal Performance Considerations and Groovy Use for Data Movement, refer to the presentation.




Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.