A landing table provides intermediate storage in the flow of data from source systems into

Informatica MDM Hub

. In effect, landing tables are “where data lands” from source systems into the

Hub Store

. You use the Schema Manager in the Model workbench to define landing tables.

The manner in which source systems populate landing tables with data is entirely external to

Informatica MDM Hub

. The data model you use for collecting data in landing tables from various source systems is also external to

Informatica MDM Hub

. One source system could populate multiple landing tables. A single landing table could receive data from different source systems. The data model you use is entirely up to your particular implementation requirements.

Inside

Informatica MDM Hub

, however, landing tables are mapped to staging tables. It is in the staging table—mapped to a landing table—where the source system supplying the data to the base object is identified. During the load process,

Informatica MDM Hub

copies data from a landing table to a target staging table, tags the data with the source system identification, and optionally cleanses data in the process. A landing table can be mapped to one or more staging tables. A staging table is mapped to only one landing table.

Landing tables are populated using batch or real-time approaches that are external to

Informatica MDM Hub

. After a landing table is populated, the stage process pulls data from the landing tables, further cleanses the data if appropriate, and then populates the appropriate staging tables.