Jobs included in replication data

Preload jobs

The preload jobs preload a new database that has just been created with settings data, item master, customers, user and other information needed from an existing database. The preload jobs do not replicate any “running” data such as transactions or number sequence values.

Preload LS Commerce

  • Includes all the same information as Preload POS. So either of these jobs can be used to preload the LS Commerce server.

  • Runs normal jobs for all tables included in the job

Preload POS

  • Includes all the tables with information needed for at the point of sale.

  • Runs normal jobs for all tables included in the job

Preload Store

  • Includes all the tables with information needed for the store level in a three tier environment setup.

  • Runs normal jobs for all tables included in the job

Update jobs (actions)

These jobs update different tables for different objects which are reflected in the name of the job. The customer job replicates everything to do with customer and so on.

All of these job include subjobs that are action jobs. This means that only actions created in REPLICATIONACTIONS table for the subjobs are run when the job is run, so only changes made through Site Manager and create actions are replicated to the destination database.

If you need to replicate everything, because you made some changes directly on the database or for some reason a table was not update correctly you can run the job ‘as normal’ and then the whole table will be replicated.

Customer

  • Replicates customers, loyalty cards and schemes, customer groups and addresses

Discount

  • Replicates all periodic discounts and promotions available in system.

Hospitality

  • Replicates everything related to the hospitality setup. Layouts, station printing, tables, hospitality setups and types.

Infocodes

  • Replicates info codes

Item

  • Replicates items and everything related to them including sales prices and trade agreement discounts.

POS settings

  • Replicates settings for the POS. Receipts, till layouts and such

Replication data

  • Replicates replication data, distribution locations, jobs, subjobs and setup.

Report

  • Replicates reports

Store settings

  • Replicates settings for the Store. Store info, Terminals, tenders and other store related settings.

Suspension settings

  • Replicates settings for suspending transactions (why is this not included in POS settings job?)

Synchronize LS Commerce

  • Replicates all data needed to update LS Commerce.

System settings

  • Replicates administrative options and settings.

Tax

  • Replicates tax related data, tax groups and tax codes.

Users

  • Replicates users, permissions, groups and other user related data.

Transaction jobs

Transactions from POS

  • Moves transactional data from the terminal database up to the store level
  • Can also be used for moving the transactions to the head quarters level if the statements are done there.
  • Normal job with replication counters

Transaction from Store

  • Replicates transaction and statement data from store to head quarters if using a three tier organization.
  • Normal job with replication counters

Pull from POS

  • Is used with replication settings in functionality profile (Post-transaction DD job) which causes POS to trigger instant replication of transaction data after finalizing each transaction.
  • Uses sub jobs from ‘Transactions from POS’ job.

Clean up jobs

The clean up jobs run delete directly from tables in destination location database.

Audit management

  • Cleans lines from tables in Audit database after ‘Manage logs’ has been used to delete logs on head office. This procedure creates the actions used for the job that can be run to the Store and POS. Most often it is the HQ db that has the largest number of actions since it is there the changes are made.

Clean actions

  • Cleans lines from REPLICATIONACTIONS table in the destination location database, according to from table filters of the CleanActions subjob. (Default value is D-60 days)

Clean log

  • Cleans lines from POSISLOG table in the destination location database, according to from table filters of the CleanLog subbjob. (Default value is D-60 days)

Other

My time plan export

  • Exports sales data to MTP for shift planning