Data Replication LS Retail Series Part 4:- What are replication Counters?

Replication Counters

Replication counters are nothing but a Integer field which acts like a counter to track till which record replication has been completed. 

What does LS Retail says about Replication counter?

This field contains the number of the field that is used as a replication counter for the From-Table ID in the replication process.

The Replication Counter allows the replication process to recognize the records that have been inserted or updated in the database being replicated from since the last replication took place to the same location, and replicate these records only.

When the Replication Method of the data exchange is Normal, the Replication Counter is a number of a field in the From Table that is given a value when a record in the table is inserted or modified. The value is a number one higher than the Replication Counter number that was given to the last record inserted or modified in the table. With this method, it is not possible to keep track of records that have been deleted.

If you want to replicate only records that have been inserted or modified, you need to select the by Normal Replication Method and add a Replication Counter field to the table. The field must be of type number (integer) for the replication to function.

Replication Counter in the Transaction Header (99001472)

*Replication counter increases by one after record is inserted on the Transaction Table

In the Schedular Job Card the Last replication counter table wise is maintained

Data Replication LS Retail Series Part 3- Transaction Jobs

 

Transaction Jobs

This is the 3rd part in the series of the data replication in LS Central/LS Retail brought you by Triknow Innovations. We are going to discuss about the Transaction Jobs replication. 

What are transaction Jobs?

Transaction jobs are used to replicate the Transactional data from store database to the HO database. Since LS Central architecture is distributed one company can have multiple stores and general transactions happen in the individual database for the respective stores. So each store can have its own database and the end of day or as when transactions replication is scheduled the transaction is replicated from store to HO database.

Example of Transaction Job

Refer to the below image which shows you job in the LS Central standard database having multiple transactional table which would replicate.

Why Transaction Subjobs are Normal?

There are several tables which are inculded in the Transaction Jobs. Those are kept normal and replication happen with help of replication counter. Replication counter is nothing but the integer field which keeps on updating as soon as data is inserted in the table. We have table called Transaction header (Table ID: 99001472), in this table there is field with ID no. 1002(Replication Counter). This is a increment counter which is updated by 1 for each record added on the table. 

Next article we would learn in detail about the replication counter and about the Sub-Jobs. Stay tuned to our blog.

Last 2 articles in the series can be refered from the below link.

Part 1:- https://navlsretail365.blogspot.com/2021/06/data-replication-ls-retail-series-part-1.html

Part 2:- https://navlsretail365.blogspot.com/2021/06/data-replication-ls-retail-series-part.html