CentralConnect Overview

This section provides an overview of how CentralConnect works.

System Overview

  • LS Central generates outbound data.
  • Data is serialized to JSON and stored in Azure Blob Storage.
  • Azure Functions monitor the storage container and forward the data to receiving ERP System.
  • The function packages the data into a format that is required by the receiving ERP system.
  • The receiving ERP system (for example, SAP, F&O) consumes the data package and processing.
  • Master data import requires XML documents to be sent to Azure storage and Azure service bus.
  • CentralConnect import functionality does check actively for new messages in Azure service bus. If there is a new document available, it imports the information to LS Central. Allowing the user to import the data package.
  • Using CentralConnect data mapping is utilized where the user creates data mapping from the ERP system and LS Central.
  • Once a message is processed, the data is retrieved into staging table for validation. Once data is validated, it can be inserted.
  • Finally, all steps are logged into CentralConnect logging.

Core Concepts

  • Message-Driven Integration: Loosely coupled systems communicate using standardized messages.
  • Mapping Layer: Custom data transformation logic ensures fields align across systems.
  • Logging & Auditing: Every transaction is traceable via Azure Monitor, Application Insights and inside of LS Central through the CentralConnect logging mechanism.

Data Mapping

  • Predefined templates exist for common data types, and mapping entities are maintained in an Enum value which is easily extendable.
    • SalesTransaction
    • ItemMaster
    • InventoryLevels
    • CustomerMaster
    • Vendors.