Real-world integration solutions: scenarios, architecture, API inventories and implementation notes
32 articles
This article focuses on a single strategy—incrementally syncing warehouse master data from Jky to a MySQL reconciliation system. It covers data flow, field mapping, configuration essentials on the Qeasy data integration platform, phased scheduling, and common pitfalls such as idCheck, status derivation, and incremental time windows. A practical guide for engineers integrating master data like warehouses or suppliers.
Drawing on a retail supply-chain integration project, this tutorial walks through using Qeasy to incrementally pull Wangdiantong sales orders by modified time, cleanse them in the middleware layer, and land both header and line items into MySQL via REPLACE INTO, with field mappings, implementation steps, pitfall review, and scope boundaries.
This guide uses the Kingdee Cloud to MySQL customer master data sync as a case study, explaining how to configure incremental filtering, organization isolation, nested-object flattening, and upsert writes on the Qeasy data integration platform, with a recap of common pitfalls.
Drawing on a real manufacturing project, this guide explains how to use the Qeasy data integration platform to push MOM purchase order close, terminate, and delete events to DingTalk in near real time. It covers source SQL joins, incremental sync, field mapping, and Markdown message assembly end to end.
Drawing on a real manufacturing project, this guide explains how to use the Qeasy data integration platform to push MOM purchase order close, terminate, and delete events to DingTalk in near real time. It covers source SQL joins, incremental sync, field mapping, and Markdown message assembly end to end.
This tutorial is designed for enterprise IT teams. It details how to use the Qeasy Data Integration Platform to accurately push purchase return material orders from MySQL to Kingdee Cloud Cosmos based on their audited status, completing the audit submission. It covers data flow, field mapping, key platform configuration points, phased scheduling strategies, and common pitfalls.
Focused on a single sales contract sync strategy, this guide explains the data flow, field mapping, key configuration points on the Qeasy platform, phased scheduling, and common pitfalls when integrating a CRM system with MySQL in a supply chain context.
This tutorial focuses on writing back the delivered status of sales outbound orders from MySQL (WMS) to Kingdee Cloud (ERP). It covers field mapping, batchSave partial update, incremental scheduling, and common pitfalls, serving as a hands-on guide for on-premise teams.
Aiming at the pain point of inconsistent inventory figures across systems in manufacturing and retail enterprises, this article takes a concrete 'raw material real-time inventory' sync strategy as an example, breaks down field mapping, scheduling design, and pitfall review from Kingdee Cloud to MySQL, and provides reusable configuration points on the Qeasy data integration platform.
This tutorial uses the Jushuitan sales outbound order to MySQL sync as a case study, explaining how to configure a single synchronization strategy on the Qeasy data integration platform. From business scenarios, field mapping, and scheduling strategies to lessons learned, it provides practical, reusable practices for IT teams handling order integration.
For multi-brand beverage supply chain scenarios, this solution consolidates 34 integration strategies from Wangdiantong Qimen into a MySQL data aggregation layer, covering stores, goods, warehouses, sales, purchasing, returns, and inventory. It uses staged scheduling, staggered execution, code mapping, and retry mechanisms to ensure data consistency and observability.
This article focuses on the inventory transfer requisition, walking through a flat-table, single-MySQL sync strategy from Kingdee Cloud to MySQL. It covers source API setup, field mapping, and incremental/full dual-track scheduling on the Qeasy data integration platform, with practical lessons on encoding mapping, staggered crontabs, and REPLACE INTO deduplication.
Basic unit information is the foundational dictionary of supply chain master data. This article walks through a specific strategy for pulling unit-of-measure master data from MySQL and landing it into Kingdee Cloud, covering incremental SQL extraction, field mapping, scheduling cadence, and common pitfalls.
Strategy-level walkthrough of pulling sales order headers from Kingdee Cloud on a */4 schedule via executeBillQuery, landing them into an in-house MySQL OMS table through Qeasy Data Integration. Covers field mapping, phased scheduling, lessons learned, and scope boundaries.
This tutorial focuses on one specific strategy — syncing sales return inbound orders from Wangdiantong to MySQL — covering scenarios, field mapping, Qeasy configuration essentials, phased scheduling, and lessons learned, written for engineers delivering supply chain integration projects.
This tutorial focuses on one specific strategy — syncing sales return inbound orders from Wangdiantong to MySQL — covering scenarios, field mapping, Qeasy configuration essentials, phased scheduling, and lessons learned, written for engineers delivering supply chain integration projects.
Using channel info sync from a reconciliation system as the entry point, this tutorial shows how to configure a single strategy in the Qeasy Data Integration Platform to land JikeCloud channel master data into a MySQL SRM database on an incremental basis. It covers scenario value, field mapping, configuration essentials, scheduling design, and lessons learned, aimed at integration engineers handling supply-chain master data landing.
This article uses a manufacturing enterprise's production return order synchronization as a case study, breaking down the complete chain: extracting production return data from a MySQL intermediate database, mapping fields through the Qeasy data integration platform, and writing to Kingdee Cloud. It covers data flow, field mapping, platform configuration, scheduling design, and lessons learned.
For retail and e-commerce scenarios, this solution writes 19 data objects from Jushuitan (Qimen and non-Qimen channels), including sales, purchasing, returns, inventory, and master data, into an enterprise MySQL database through phased scheduling, achieving automated closed-loop and observable operations for supply chain documents.
This tutorial focuses on a single integration strategy that syncs after-sales orders from Jushuitan via its Qimen interface into MySQL. It walks through the business scenario, field mapping, configuration on the Qeasy platform, phased implementation, and common pitfalls, serving integration engineers who need to land after-sales data into a data warehouse or downstream systems.
