Table Population Overview

What Is a Table Population?

A Table Population defines and executes mapping and data transformation rules from a data source, like a DB table or Input file, into a target Logical Unit (LU) table. The population acts as a map that renders a graphical display of the transformation’s business logic from the source object to the target LU table. Source data can be mapped directly to LU table columns and Fabric transformation objects like Functions or Globals, and can be added to define the mapping logic into the LU table.

Each table can have one or several table populations that can be executed simultaneously or according to a predefined execution order. Each table population extracts data from a data source, transforms it when needed and then populates the data into an LU table. Table populations can be categorized as follows:

Table Population In an LU Schema

An LU Schema displays a hierarchical representation of the data related to the Root Table. Parent-child links in LU tables are created via their Table Population objects:

  • Each LU table can have one or several Table Population objects.
  • Each Table Population object, apart from the Table Population of the LU's Root Table, must be linked to a parent table via its Input columns.
  • Each Table Population object can be linked to a different parent LU table. Note that an LU table can be added to an LU Schema without a Table Population object. This table is not populated by the sync process of the LU Instance but can be populated by a separate transaction.

Click for more information about Building an LU Hierarchy and Linking Table Populations.

Table Population Overview

What Is a Table Population?

A Table Population defines and executes mapping and data transformation rules from a data source, like a DB table or Input file, into a target Logical Unit (LU) table. The population acts as a map that renders a graphical display of the transformation’s business logic from the source object to the target LU table. Source data can be mapped directly to LU table columns and Fabric transformation objects like Functions or Globals, and can be added to define the mapping logic into the LU table.

Each table can have one or several table populations that can be executed simultaneously or according to a predefined execution order. Each table population extracts data from a data source, transforms it when needed and then populates the data into an LU table. Table populations can be categorized as follows:

Table Population In an LU Schema

An LU Schema displays a hierarchical representation of the data related to the Root Table. Parent-child links in LU tables are created via their Table Population objects:

  • Each LU table can have one or several Table Population objects.
  • Each Table Population object, apart from the Table Population of the LU's Root Table, must be linked to a parent table via its Input columns.
  • Each Table Population object can be linked to a different parent LU table. Note that an LU table can be added to an LU Schema without a Table Population object. This table is not populated by the sync process of the LU Instance but can be populated by a separate transaction.

Click for more information about Building an LU Hierarchy and Linking Table Populations.