In this article
This article describes the purpose of every cron job that is being used in the replication process and the area it covers.
Cron jobs are divided into two types:
Omni to Flat
These cron jobs are responsible for fetching data from LS Central and storing them in flat tables created in Magento. The jobs are only visible in website scope view with some exceptions, like repl_data_translation, repl_html_translation, and repl_data_translation_lang_code, since these three work in store view scope in order to support localization.
To open the cron listing for these cron jobs, you have to change the current scope to any website.
| Cron Job | Description |
|---|---|
| repl_item: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_item flat table of the Magento database. The job uses the ReplEcommItems function of the Commerce Replication APIs to fetch all data related to the items. Any item created, modified, or deleted will be included in this API response. |
| repl_price: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_price flat table of the Magento database. The job uses the ReplEcommPrices function of the Commerce Replication APIs to fetch all data related to item prices. Any item price created, modified, or deleted will be included in this API response. |
| repl_inv_status: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_inv_status flat table of the Magento database. The job uses the ReplEcommInventoryStatus function of the Commerce Replication APIs to fetch all data related to item inventories. Any data related to an inventory will be included in this API response. |
| repl_barcode: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_barcode flat table of the Magento database. The job uses the ReplEcommBarcodes function of the Commerce Replication APIs to fetch all data related to item barcodes. |
| repl_extended_variant_value: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_extended_variant_value flat table of the Magento database. The job uses the ReplEcommExtendedVariants function of the Commerce Replication APIs to fetch all data related to item variants. |
| repl_image_link: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_image_link flat table of the Magento database. The job uses the ReplEcommImageLinks function of the Commerce Replication APIs to fetch all data related to the images. This web service brings the list of all image links for items, variants, stores, and categories of the selected web store. Any image added, modified, or removed against all the areas of the store will be included in this API response. |
| repl_item_variant: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_item_variant flat table of the Magento database. The job uses the ReplEcommItemVariants function of the Commerce Replication APIs to fetch all data related to item variants. Any variant created, modified, or deleted will be included in this API response. |
| repl_item_variant_registration: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_item_variant_registration flat table of the Magento database. The job uses the ReplEcommItemVariantRegistrations function of the Commerce Replication APIs to fetch all data related to item variants. Any variant created, modified, or deleted will be included in this API response. |
| repl_unit_of_measure: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_unit_of_measure flat table of the Magento database. The job uses the ReplEcommUnitOfMeasures function of the Commerce Replication APIs to fetch all data related to unit of measure. Any unit of measure created, modified, or deleted will be included in this API response. |
| repl_item_unit_of_measure : | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_item_unit_of_measure flat table of the Magento database. The job uses the ReplEcommItemUnitOfMeasures function of the Commerce Replication APIs to fetch all data related to item unit of measures. Any data related to item unit of measure created, modified, or deleted will be included in this API response. |
| repl_vendor: | This job runs every four minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_vendor flat table of the Magento database. The job uses the ReplEcommVendor function of the Commerce Replication APIs to fetch all data related on vendor. Any data on a vendor created, modified, or deleted will be included in this API response. |
| repl_loy_vendor_item_mapping: | This job runs every four minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_loy_vendor_item_mapping flat table of the Magento database. The job uses the ReplEcommVendorItemMapping function of the Commerce Replication APIs to fetch all data related to vendor to product mapping. Any data on vendor to product mapping created, modified, or deleted will be included in this API response. |
| repl_country_code: | This job runs every 15 minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_country_code flat table of the Magento database. The job uses the ReplEcommCountryCode function of the Commerce Replication APIs to fetch all data related to country codes. Any data on country code created, modified, or deleted will be included in this API response. |
| repl_store_tender_type: | This job runs every15 minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_store_tender_type flat table of the Magento database. The job uses the ReplEcommStoreTenderTypes function of the Commerce Replication APIs to fetch all data related to store tender type. Any store tender type data created, modified, or deleted will be included in this API response. |
| repl_item_variant: | This job runs every two minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_item_variant flat table of the Magento database. The job uses the ReplEcommItemVariants function of the Commerce Replication APIs to fetch all data related to standard LS Central item variants. Any variant created, modified, or deleted will be included in this API response. |
| repl_unit_of_measure: | This job runs every two minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_unit_of_measure flat table of the Magento database. The job uses the ReplEcommUnitOfMeasures function of the Commerce Replication APIs to fetch all data related to available unit of measures. Any unit of measure created, modified, or deleted will be included in this API response. |
| repl_item_unit_of_measure: | This job runs every two minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_item_unit_of_measure flat table of the Magento database. The job uses the ReplEcommItemUnitOfMeasures function of the Commerce Replication APIs to fetch all data related to items connected with unit of measures. Any item unit of measure created, modified, or deleted will be included in this API response. |
| repl_hierarchy: | This job runs once every day at 10:00 hours. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_hierarchy flat table of the Magento database. The job uses the ReplEcommHierarchy function of the Commerce Replication APIs to fetch all data related to store hierarchies. |
| repl_hierarchy_node: | This job runs every four minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_hierarchy_node flat table of the Magento database. The job uses the ReplEcommHierarchyNode function of the Commerce Replication APIs to fetch all data related to the Hierarchy nodes. |
| repl_hierarchy_leaf: | This job runs every four minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_hierarchy_leaf flat table of the Magento database. The job uses the ReplEcommHierarchyLeaf function of the Commerce Replication APIs to fetch all data related hierarchy leaves. |
| repl_attribute: | This job runs every four minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_attribute flat table of the Magento database. The job uses the ReplEcommAttribute function of the Commerce Replication APIs to fetch all data related to attributes. Any attribute created, modified, or deleted will be included in this API response. |
| repl_attribute_value: | This job runs every four minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_attribute_value flat table of the Magento database. The job uses the ReplEcommAttributeValue function of the Commerce Replication APIs to fetch all data related to the attributes values assigned to items. Any new attribute value assigned to any product will be included in this API response. |
| repl_attribute_option_value: | This job runs every four minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_attribute_option_value flat table of the Magento database. The job uses the ReplAttributeOptionValue function of the Commerce Replication APIs to fetch all data related to attribute values and their sequence in the listing. Any attribute option created, modified, or deleted will be included in this API response. |
| repl_discount: | This job runs every four minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_discount flat table of the Magento database. The job uses the ReplEcommDiscounts function of the Commerce Replication APIs to fetch all data related to discounts. Any new discount created, modified, deleted, enabled, or disabled will be included in this API response. |
| repl_item_category: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_item_category flat table of the Magento database. The job uses the ReplEcommItemCategories function of the Commerce Replication APIs to fetch all data related to item categories. Any category created, modified, or deleted will be included in this API response. |
| repl_product_group: | This job runs every two minutes. The purpose of this job is to replicate all data from Commerce and store the data in the ls_replication_repl_product_group flat table of the Magento database. The job uses the ReplEcommProductGroups function of the Commerce Replication APIs to fetch all data related to product groups. |
| repl_store: | This job runs every two minutes. The purpose is to replicate all data from Commerce and store the data in the ls_replication_repl_store flat table of the Magento database. The job uses the ReplEcommStores function of the Commerce Replication APIs to fetch all data related to stores. Any changes related to a store will be included in this API response. |
| repl_inv_status_reset: | This job runs once every day at 00:00 hours. The purpose of this cron job is to reset the replication counter of the repl_inv_status cron back to zero so that it can fetch all the new data from LS Central related to the inventory for that day. The reason is that there may be lots of offline inventories being sold that may not be updated in Magento. |
| repl_price_status_reset: | This job runs once every day at 00:00 hours. The purpose of this cron job is to reset the replication counter of repl_price cron back to zero so that it can fetch the best price of the day for all the products. |
| repl_discount_status_reset: | This job runs once every dayat 00:00 hours. The purpose of this cron job is to reset the replication counter of repl_discount cron back to zero so that it can fetch all Discounts of the day from LS Central to be processed in Magento. |
Flat to Magento
These cron jobs are responsible for processing available data in flat tables and creating required entities like items, categories, sync order, sync customers, and so on in Magento. They are only visible in store view scope.
To open the cron listing for these cron jobs, you have to change the current scope to any store view.
| Cron Job | Description |
|---|---|
| repl_data_translation: | This job runs every 15 minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_data_translation flat table of the Magento database. The job uses the ReplEcommDataTranslation function of the Commerce Replication APIs to fetch all the data related to the items. Any data translation created, modified, or deleted will be included in this API response. |
| repl_html_translation: | This job runs every15 minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_html_translation flat table of the Magento database. The job uses the ReplEcommHtmlTranslation function of the Commerce Replication APIs to fetch all the data related to the items. Any html translation created, modified, or deleted will be included in this API response. |
| repl_data_translation_lang_code: | This job runs every 15 minutes. The purpose of this job is to replicate all the data from Commerce and store the data in the ls_replication_repl_data_translation_lang_code flat table of the Magento database. The job uses the ReplEcommDataTranslationLangCode function of the Commerce Replication APIs to fetch all the data related to the items. Any language code created, modified, or deleted will be included in this API response. |
| repl_attributes: | This job runs every five minutes. The purpose of this cron job is to fetch all data related to attributes in the flat tables and process the data in Magento. This cron job fetches all new or updated data from ls_replication_repl_extended_variant_value, ls_replication_repl_attribute, and ls_replication_repl_attribute_option_value, and processes the data in Magento as Product Attributes. Status of the cron job is Pending, unless the job processes all the values in those tables and sets status as Processed. |
| repl_category: | This job runs every five minutes. The purpose of this cron job is to process all data related to product categories. This cron picks all new or updated data from the ls_replication_repl_hierarchy_node table, and creates or updates categories in Magento based on the information in there. Status of the cron job is Pending, unless the job processes all the values in those tables and sets the status as Processed. |
| repl_products: | This job runs every five minutes. This is the most important cron job in the system which summarizes the replication of products and creates it in Magento. This cron picks data from multiple tables related to item and variants and process the data in Magento. This cron has explicit dependency on other cron jobs which means it will only run once the status of its dependent job is set to Complete. |
| repl_tax_setup: | This job runs every five minutes . The purpose of this cron job is to replicate all tax setup data from Commerce and store the data in the ls_replication_repl_tax_setup flat table of the Magento database. The job uses the ReplEcommTaxSetup function of the Commerce Replication APIs to fetch all data related to tax setup. Any item created, modified, or deleted will be included in this API response. |
| repl_data_translation_to_magento: | This job runs every five minutes. The purpose of this cron job is to fetch all data related to data translation details in the flat tables and process the data in Magento. This cron job fetches all new or updated data from the ls_replication_repl_data_translation table and processes the data in Magento. Status of the cron job will be Pending, unless the job processes all the values in those tables and sets status as Processed. |
| repl_discount_create: | This job runs every five minutes. The purpose of this cron job is to process all data related to discounts and create catalog rules in Magento against the data. This cron picks all new or updated data from the ls_replication_repl_discount table, and creates or updates catalog rules in Magento based on the information in there. |
| repl_data_translation_to_magento: | This job runs every five minutes. The purpose of this cron job is to process all data related to translation of Magento categories and products. This cron picks all new or updated data from the ls_replication_repl_data_translation, repl_html_translation, repl_data_translation_lang_code tables, and creates or updates catalog rules in Magento based on the information in there. |
| repl_price_sync: | This job runs every five minutes. The purpose of this cron job is to process all data related to prices in Magento. This cron picks all new or updated data from the ls_replication_repl_price table and updates product prices in Magento. |
| repl_inventory_sync: | This job runs every five minutes. The purpose of this cron job is to process all data related to product inventories in Magento. This cron picks all new or updated data from the ls_replication_repl_inv_status table, and updates product inventories in Magento. |
| repl_item_updates_sync: | This job runs every five minutes. The purpose of this cron job is to process all data related to products assigned to categories in Magento. This cron picks all new or updated data from the ls_replication_repl_hierarchy_leaf table, and updates the data in Magento. |
| repl_attributes_value_sync: | This job runs every five minutes. The purpose of this cron job is to synchronize the data of newly created attributes and assign the data to products. This cron picks all new or updated data from the ls_replication_repl_attribute_value table, and updates the data in Magento against the affected items. |
| repl_item_images_sync: | This job runs every five minutes. The purpose of this cron job is to process all data related to product images in Magento. This cron picks all new or updated data from the ls_replication_repl_image_link table that are related to Item or Item Variants and processes those images in Magento against its respective products. |
| repl_tax_rules: | This job runs every five minutes. The purpose of this cron job is to sync all replicated data on tax setup from the ls_replication_repl_tax_setup flat table to Magento. |
| repl_vendor_attributes_sync: | This job runs every five minutes. The purpose of this cron job is to fetch all data related to vendor attributes in the flat tables and process the data in Magento. This cron job fetches all new or updated data from the ls_replication_repl_vendor_attributes_sync table and processes the data to products in Magento. Status of the cron job will be Pending, unless the job processes all the values in those tables and sets status as Processed. |
| sync_version: | This job runs once every week. The purpose of this cron job is to automatically synchronize the version of LS Central and Commerce (if updated) in the Magento configuration database. The version values are used to cater to specific requirements in the integration to support customization done against each LS Central version. |
| sync_orders: | This job runs every 15 minutes. The purpose of this cron job is to automatically synchronize all the pending orders with LS Central. This comes in handy when for some reason an order could not be synchronized with LS Central on checkout, maybe due to network issues or some other unforeseen situations. |
| sync_customers: | This job runs every 15 minutes. The purpose of this cron job is to automatically synchronize pending customers with LS Central. This comes in handy when for some reason a customer could not be synchronized with LS Central on customer registration, maybe due to network issues or some other unforeseen situations. |