The objectives for the POSTTARGET step are:

  • To create views on top of the dimension and fact tables, so that Vertica for PPM reporting users can understand the data easily.
  • To open a window for content engineers to perform any analytical functions after all data are loaded into the target tables.

The system defines templates for creating views. Vertica for PPM creates the following types of views based on the table types and metadata defined in the target table:

  • Hierarchy Drill UP View /Hierarchy Drill Down View

    Those two views are created for Vertica for PPMreporting users, so they do not have to combine BRIDGE_HIEARCHY tables by themselves. If one dimension entity has hierarchy defined, the system automatically creates those two views. Users can select Hierarchy Drill UP View if they want to know all parent records and Hierarchy Drill Down View if they want to know all child records.

  • User Data View

    The system creates User Data View only if a dynamic_view attribute is defined in the target JSON file. The system leverages the context information defined in PPM to provide USER_DATA fields in PPM with a meaningful name in the views.

    If a dimension entity has both bridge and dynamic_view defined, the system generates the consolidated view automatically.

  • Common View

    For all other target tables, the system also creates a view layer. Extended entities can be joined with the OOTB entity through the view layer for better a user experience.

In the stream JSON definition, you can also define the post_target_transforms attribute. For examples, see OOTB PPM_RESOURCE_DEMAND_STREAM.json (under <VDW_HOME>/Content/CUSTOMIZATION_PPM.cp/dwmetadata/streams).

All SQL-defined post_target_transforms attributes are executed in this step as well.