Real-world integration solutions: scenarios, architecture, API inventories and implementation notes
5 articles
This article dissects a single sync strategy — Guanyi delivery orders to Kingdee direct transfer orders — for luggage products. Using the Qeasy data integration platform, we walk through field mapping, configuration essentials, phased scheduling, and pitfall review, helping enterprise IT teams avoid encoding, breakpoint, and inventory drift issues.
This article focuses on a single strategy—querying Kingdee employees—and explains its business motivation, field mapping, Qeasy configuration essentials, and typical pitfalls. It does not push business documents itself, but provides the personnel primary key for all subsequent document sync, making it a frequently overlooked yet essential link in supply chain integration.
This tutorial focuses on a single material master data sync strategy. Starting from real business pain points, it walks through incremental source queries, cross-strategy lookups via _mongoQuery, idCheck upsert logic, and centralized mapping management on the Qeasy integration platform, with five hard-earned lessons from the field.
For e-commerce retail scenarios, this integration uses Guanyi Cloud as the front-end ERP and Kingdee Cloud Cosmic as the back-end ERP. Through an integration platform, two business flows are implemented: delivery orders to sales outbound orders, and return/exchange orders to sales return orders. Five strategies cover material license refresh, cross-solution query, and historical queue cleanup. The document provides actionable engineering guidance on phased scheduling, code mapping, retry logic, and monitoring thresholds.
Routing product master data from an e-commerce ERP into Qeasy as a staging layer is the first hurdle in supply-chain integration. This guide walks through a real retail project, explaining the field mapping, scheduling essentials, and lessons learned from the "no-op" strategy so IT teams can quickly lay a solid product data foundation.
