Latest industry insights, tutorials, best practices and case studies.
11 articles
How long does integration take? What if the legacy ERP has no API? How is historical data migrated? Who owns inconsistencies found after go-live? Six questions customers ask most before kickoff, answered with an engineering perspective.
Reconciliation done is not the finish line — the confirmed results must become receivables, receipts and GL vouchers in the ERP. Starting from reconciliation output, this tutorial covers account mapping, voucher templates, posting via Kingdee Cosmic / Yonyou APIs, and idempotency control.
Half the communication cost of integration projects comes from terminology mismatch. This glossary defines ten foundational terms: iPaaS, ETL/ELT, API, Webhook, SDK, API orchestration, field mapping, data cleansing, middleware and connector.
A Kingdee Cloud walkthrough of the full loop: suggestion → plan confirmation → order splitting → purchase order Save/Submit/Audit → arrival backfill, with field mapping, idempotency and retry design.
Distributor master data is the foundation of channel data integration: how to define codes, tier distributors, and build credit profiles. This article provides a practical governance framework covering coding rules, attribute models, change workflows, and integration essentials.
The full onboarding flow for the YonBIP open platform: creating an app, exchanging AppKey/AppSecret for an access token, calling business APIs, and designing customer/material master data synchronization.
A hands-on walkthrough of the Kingdee Cloud WebAPI: the three core endpoints — ValidateUser login, ExecuteBillQuery for querying bills, and Save for writing bills — with parameters, pitfalls, and best practices.
There are only four basic patterns for integrating an ERP with other systems. This article analyzes direct API calls, staging tables, message queues, and iPaaS — their mechanics, fit, and hidden costs — to guide architecture decisions.
Three-way matching is the core method of e-commerce finance: business orders, cash receipts and issued invoices must corroborate each other. This article covers matching-key design, matching levels, tolerance rules and common failure scenarios.
Nearly every e-commerce and ERP platform enforces QPS and daily-call quotas. Instead of being punished with throttling errors and account penalties, govern proactively: this article lays out a complete client-side design with token buckets, concurrency gates, quota budgets and graceful degradation.
DMS governs the channel while ERP governs internal control. How the data path between them is designed determines the success of channel digitalization. This article compares point-to-point, ESB/middle-platform, and iPaaS patterns.
