Real-world integration solutions: scenarios, architecture, API inventories and implementation notes
89 articles
This article focuses on the single strategy of querying Kingdee salespeople, walking through the practice of pulling salesperson master data from Kingdee Cloud Sky into the Qeasy data integration platform. It explains why the strategy is QUERY_ONLY (pull-only, no write), why it runs at dawn via cron, and why it relies on executeBillQuery, along with hands-on lessons such as staged header/body processing and centralized code mapping.
This article explains how to incrementally sync shop master data to customer records via the Qeasy Data Integration Platform in an e-commerce retail scenario. Focused on the 'do not resync already-synced data' requirement, it details field mapping, organization constants, scheduling, and five common pitfalls.
For multi-store retail scenarios, this guide walks through pushing completed WanDianTong refund orders into Kingdee Cloud's XSTHD01_SYS voucher, organized by store. It covers source API selection, store/customer code mapping, incremental windows, organization auto-resolution, and the practical pitfalls encountered when implementing the strategy on the Qeasy iPaaS platform.
Targeting the scenario where a manufacturing enterprise pushes material master data from Kingdee KIS Private Cloud to OKKI CRM, this article dissects a time-window-based incremental sync strategy. It covers data flow, field mapping, key configuration points in Qeasy, three-phase scheduling, and lessons learned from real pitfalls.
This tutorial walks through a single purchase inbound sync strategy: pulling audited inbound orders from the marketing cloud, mapping suppliers and SKUs, and writing them into the finance ERP. It covers data flow, field mapping, configuration tips, incremental and full scheduling, and field-tested pitfalls—written for integration engineers who want a concrete playbook.
Purchase inbound sync is the most frequent and error-prone link in Jky–Kingdee Cloud supply chain integration. This article dissects a tested strategy across field mapping, paginated incremental pull, target bill type, and lessons learned, showing how Qeasy reliably lands inbound documents into Kingdee Cloud.
This tutorial walks through a single strategy of incrementally pulling item master data from Kingdee's cloud suite by modification time, landing it on the target via the Qeasy Data Integration Platform. It covers field mapping, scheduling design, common pitfalls, and applicable boundaries.
This article walks through a concrete sales stock-out sync strategy: incrementally pulling audited/dispatched stock-out orders from the source ERP, mapping and de-duplicating fields on the Qeasy data integration platform, then pushing them into the target financial system as sales delivery orders. It covers data flow, field mapping, configuration tips, scheduling design, and lessons learned.
This article breaks down a typical stock order synchronization strategy: pulling shipped batches from a cross-border ERP and landing them as transfer orders in Kingdee Cloud via the Qeasy data integration platform. It focuses on field mapping, incremental start points, scheduling frequency, and common pitfalls, providing practical guidance for IT teams.
This guide focuses on a single strategy—pushing purchase orders from Xiaoman OKKI CRM into Kingdee Cloud Xingchen. It covers the business scenario, field mapping, key configuration points in Qeasy, phased scheduling, and common pitfalls, suitable for enterprise IT teams to follow step by step.
This article focuses on a supply chain scenario where sales outbound orders from Kingdee Cloud are synced to a WMS via the Qeasy data integration platform. Drawing on lessons from a real project, it breaks down four key points: code mapping, incremental starting point, scheduled staggering, and staged header/line processing.
This tutorial drills into one specific strategy: pulling shipped sales-outstock orders from Wangdiant and writing the logistics tracking numbers back to the SAL_OUTSTOCK form in Kingdee Cloud. It covers the incremental anchor, time window, field mapping, batchSave submission, and lessons learned—ready to implement on the Qeasy 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.
Focused on the 'Query Starry Unit Info' strategy within a Jushuitan ↔ Kingdee YXC supply-chain integration: incrementally pull measure units from the source, land them via the Qeasy integration platform, and centralize error-prone code mapping in the middleware layer.
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.
Pushing supplier master data from a source system into Kingdee Cloud looks straightforward—until code mapping, organization fields, and group relations are mishandled. This article dissects a single 'supplier sync' policy: data flow, field mapping, configuration on Qeasy, phased scheduling, and lessons learned.
This article focuses on a single integration strategy: pushing purchase inbound orders from Kingdee Cloud to a WMS as fast inbound orders. It walks through the business pain point, data flow and field mapping, configuration in the Qeasy integration platform, phased rollout, lessons learned from real projects, and the boundaries of applicability—written for enterprise IT teams implementing private-deployment supply chain integrations.
Drawing on a real retail project, this tutorial explains how to use the Qeasy Data Integration Platform to incrementally pull sales orders from Xiaoman OKKICRM, cleanse and map fields, and write them into Lingmao. It covers data flow, field mapping, platform configuration, phased scheduling, and common pitfalls for on-premise deployments.
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.
This tutorial unpacks the 'Query XiaoMan Customers' strategy from a basic-data sync plan between XiaoMan OKKICRM and Kingdee Cosmic. It covers the source API, paging parameters, cron schedule, and how the result lands in the Qeasy hub, so engineers can reuse the pattern on a new CRM-to-ERP master data integration.
