Real-world integration solutions: scenarios, architecture, API inventories and implementation notes
14 articles
This article uses a real manufacturing scenario to explain how to incrementally sync Kingdee Cloud production orders into MySQL with Qeasy. It covers field mapping, scheduling, header/line phased sync, centralized code mapping, and post-mortem lessons.
This strategy solves the problem where MySQL business systems remain unaware that a supplier has been disabled in Kingdee Cloud and continue placing orders. By scheduling a query of Kingdee supplier document status and writing it back to MySQL via a lightweight UPDATE, combined with code mapping and incremental triggers, a reverse closed loop is achieved.
This guide dissects a single strategy—syncing WMS subcontracting stock orders from Wangdiantong to MySQL. It covers data flow, field mapping, configuration on Qeasy, phased scheduling, and practical lessons on 1:N writes, dual-track incremental and full loads, and centralized code mapping.
This tutorial focuses on a single strategy: after a MOM production plan push transfer document is generated in Kingdee Cosmos, the success status, document number, and internal ID are echoed back to the MES-side MySQL interface table. It covers the data flow, field mapping, key configuration points on the Qeasy platform, phased scheduling implementation steps, and 4 practical pitfalls to help enterprise IT teams quickly build a stable closed loop.
Syncing refund inbound orders from ERP to MySQL looks routine, but the real difficulty lies in incremental time windows, pagination, and coordinating header and detail data. This article uses a specific strategy as a blueprint to clarify the data flow, field mapping, key configuration points on Qeasy, and lessons learned along with boundaries.
This article dissects a single stock-in order sync strategy, walking through the full path of pulling header and detail records from Wangdiantong and landing them into MySQL. It focuses on choosing the incremental starting point, staging header/detail writes, centralising code mapping, and the common pitfalls encountered during implementation.
This article explains how to use the Qeasy Data Integration Platform to return production material issue processing results from Kingdee to MySQL. Using source IDs, incremental updates, phased scheduling, parameterized SQL, and exception controls helps keep task status timely, accurate, and traceable.
This tutorial walks through the strategy of syncing Kingdee Cloud Starry Sky stepwise transfer-out documents into MySQL. It covers the business scenario, field mapping, configuration on the Qeasy platform, phased scheduling, and common pitfalls for engineers working on supply chain integration.
This tutorial focuses on the DingTalk notification strategy after sales order rejection. Based on a MySQL source database and DingTalk robot message channel, it explains field mapping, scheduled tasks, userid concatenation, and msgParam template configuration, along with practical lessons learned.
This tutorial focuses on the DingTalk notification strategy after sales order rejection. Based on a MySQL source database and DingTalk robot message channel, it explains field mapping, scheduled tasks, userid concatenation, and msgParam template configuration, along with practical lessons learned.
This article walks through a concrete sync strategy—pulling production report bills from Kingdee Cloud into Qeasy DataHub—covering data flow, field mapping, scheduling, and lessons learned. Aimed at engineers integrating MES and ERP systems.
This tutorial is written for enterprise IT teams. It walks through one concrete purchase order sync strategy pushing data from MySQL to Kingdee Cloud Skyward in a private deployment. It covers the business scenario, data flow, key configuration points on the Qeasy platform, phased rollout, and lessons learned, including common patterns such as centralized code mapping and dual-track incremental and full synchronization.
