About replication

This can refer to the process of copying data from a local environment (even cloud-based) to the Infor Data Lake. Or it might refer to the use of Business Object Documents (BODs) to transfer data from your local Factory Track application to a different application such as M3. Replication is also used in ION APIs to transfer data.

Replication also allows the system to transmit stored procedure execution requests (SPs) between the source and target locations. The "source" location is defined as the original database in which the data exists and from which it is replicated. The "target" location, then, is the database that the data is replicated to.

When data is updated in the target database using replication, the replication process bypasses business rule validation and triggers. This means that replication should only be performed between “trusted” sites. Referential integrity and database-level constraints still apply. Note also that trigger validation is not applied to tables in any case.

Factory Track supports two basic replication methods: transactional and non-transactional. You can use transactional replication between some of your sites and non-transactional replication between others; it depends primarily on how the sites are connected and how quickly you want the data to be available.