Latest industry insights, tutorials, best practices and case studies.
862 articles
This tutorial systematically covers the Kingdee Cloud Sales Order executeBillQuery API, including key fields, filter conditions, pagination, configuration in the Qeasy integration platform, and cross-project pitfalls to help engineers integrate Sales Orders with CRM systems quickly.
This guide focuses on a single real-time inventory sync strategy, walking through the business scenario, data flow, field mapping, Qeasy configuration essentials, phased rollout, and lessons learned, helping integration engineers implement inventory sync from Kingdee Cloud Cosmos to the XinBao supply chain collaboration platform.
This tutorial aggregates hands-on experience from multiple real supply chain integration projects using the Kingdee Cloud Xingchen [Linked Query] Warehouse API, covering the API capabilities, typical field mappings, configuration on the Qeasy platform, cross-scenario best practices, and common pitfalls.
For the risk supplier reinstatement scenario, this guide uses the Qeasy Data Integration Platform to bridge DingTalk approval flows with Kingdee Cloud Cosmos supplier master data. A two-phase pull plus _findCollection code mapping pattern drives automatic batchSave in Kingdee after approval, with an event script handing off to a downstream enable strategy.
This tutorial consolidates hands-on experience from multiple Xiaoman OKKI CRM × Yongyou BIP sales order integration projects, focusing on the staff query API. It covers the interface capabilities, typical fields, platform configuration, cross-project best practices, and pitfall remediation, enabling engineers to master all practical aspects of this API in one read.
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.
This tutorial focuses on a single strategy: pulling product group data from OKKICRM into the middleware layer via the Qeasy data integration platform, serving as a prerequisite for sales order master data. It covers scenarios, field mapping, configuration essentials, phased scheduling, and lessons learned from real implementations.
This tutorial focuses on a concrete strategy—querying sales orders from the Kingdee Cloud Aerospace Flagship Edition—and walks through how to use the Qeasy Data Integration Platform to extract sales orders from the source system to the intermediate layer. It covers data flow, field mapping, platform configuration, phased scheduling, and lessons learned from pitfalls, suited for engineers working on order synchronization in private deployment environments.
A field-tested playbook for synchronizing return orders from Wangdiantong to Kingdee Cloud Cosmic, covering data flow, field mapping, Qeasy configuration, phased rollout, and pitfalls.
This tutorial walks through a single integration strategy that writes the WMS vendor code back into a custom field on Kingdee Cloud, using Qeasy as the integration backbone, including field mapping, scheduling, and field-tested lessons.
This article dives into a specific supply-chain document sync strategy: pushing other goods receipt documents from Jky to Kingdee Cloud on a 25/30-minute polling cadence. It covers data flow, field mapping, configuration essentials on the Qeasy platform, phased implementation steps, and common pitfalls to help engineers in private deployments ship faster.
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.
Focused on a single sales-return sync strategy, this guide walks through scenarios, field mapping, key configuration points on the Qeasy platform, phased scheduling, and lessons learned—showing how to reliably land Jushuitan sales returns into Kingdee Cloud Xingchen in a real project, with clear boundaries on when the approach fits.
This tutorial focuses on a specific strategy—feedback of sales delivery order approval results from Kingdee Cloud Cosmos back to a MySQL MES table. Drawing from a real project, we explain how to configure, schedule, and troubleshoot this strategy on the Qeasy platform, helping enterprise IT teams close the loop on delivery order approval.
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.
This guide centers on the integration between Kingdee Cloud Skylus PUR_ReceiveBill and Jijia ERP, aggregating hands-on experience from multiple cross-border e-commerce supply chain integration projects. It details API capabilities, typical field mappings, Qeasy Cloud platform configuration, cross-solution best practices, and pitfall retrospectives, enabling engineers to master the full integration in one read.
This article uses the concrete strategy of 'Wangdiantong -> MySQL real-time inventory details' as a blueprint, explaining the data flow, field mapping, key configuration points on the Qeasy platform, phased scheduling, and 5 lessons learned from customer engagements. It is intended for supply chain integration engineers who need to land ERP inventory data at high frequency.
After a purchase return material order is submitted for audit in the MES, the approval result must be written back to the MySQL business table. This solution uses the Qeasy Data Integration Platform to orchestrate a two-stage flow—source-side scheduled polling plus target-side SQL update—closing the status loop at a 3-minute cadence. Common pitfalls include instruction document number matching, semantic alignment of status fields, and idempotency control.
In CRM-to-ERP integration, the most overlooked step is whether the sync result is written back to the CRM. This article focuses on writing back the sync status to a CRM system, dissecting a closed-loop strategy that queries orders from the order system and writes the "synchronized" status back to the CRM, with field mapping, configuration essentials, and lessons learned.
Focused on a single document sync strategy, this article explains the data flow, field mapping, key Qeasy configuration points, and phased rollout for pushing a completion acceptance document from the ERP to the downstream warehouse system, along with four practical pitfalls and scope boundaries.
