Real-world integration solutions: scenarios, architecture, API inventories and implementation notes
4 articles
This tutorial focuses on a single strategy: pulling purchase requisitions from the WMS flagship edition every 5 minutes and writing them into two SQL Server staging tables (header and line). The mapping is pure field-level passthrough, header and line are linked by purchase_apply_no, and there is no encoding translation or custom scripting. It covers the data flow, field mapping, key configuration points on the Qeasy platform, a phased rollout, and five lessons learned from real projects, aimed at engineers running supply-chain integration in on-premise environments.
Return-order cross-system sync looks simple but easily trips on code mapping, staged header/line writes, incremental windows, and deduplication. Drawing on a real project, this guide explains how to pull audited return orders from the marketing cloud and land them into SQL Server header and line tables on the Qeasy data integration platform, with reusable configuration and scheduling recommendations.
For a manufacturing enterprise's supply chain scenario, this article walks through syncing employee user records from the source system to Kingdee Cloud employee profiles. It covers the end-to-end configuration on Qeasy data integration platform: data flow, field mapping, scheduling, lessons learned, and boundaries—useful as a reference for IT teams in private deployment environments.
Focused on the pain point of a retail enterprise where sales outbound orders remain unconfirmed after logistics sign-off, this guide explains one sync strategy that reads logistics sign-off facts from SQL Server and batch-updates the receipt date in Kingdee Cloud, covering field mapping, Qeasy configuration, incremental scheduling, and common pitfalls.