Latest industry insights, tutorials, best practices and case studies.
634 articles
This tutorial focuses on a specific integration strategy: after a business document is written into Kingdee Cloud Skylight, a comment notification is automatically posted back to DingTalk. Using the Qeasy data integration platform as the backbone, we walk through scenario value, field mapping, configuration highlights, and common pitfalls in a single end-to-end playbook.
This tutorial zooms into one concrete strategy—syncing delivery notifications from the ERP to an OA approval flow. It covers the business scenario, field mapping, key configuration points on the Qeasy platform, phased rollout, and lessons learned from real engagements, giving enterprise IT teams a practical, deployment-ready reference.
This tutorial walks retail and e-commerce teams through syncing rejection-refund after-sales orders from Jushuitan into Kingdee Cloud Return Orders, using the Qeasy data integration platform. It covers scenario analysis, field mapping, configuration essentials, and lessons learned for a reusable supply chain integration.
This article takes the single strategy 'Sync pending asset data from fixed assets to Kingdee asset cards' as an example, breaking down the source OpenCallback query, the key field mapping for the target batchSave write, typical configuration points on the Qeasy Data Integration Platform, along with scheduling, pitfalls, and boundaries.
This tutorial focuses on one specific strategy: syncing sales outbound red-letter vouchers from Yonyou U8 into other-inbound vouchers in Wangdiantong. It covers data flow, field mapping, key configuration points in the Qeasy platform, phased scheduling, and lessons learned—delivered as a practical, ready-to-execute guide for enterprise IT teams.
This tutorial focuses on a single strategy: pushing down to generate a Kingdee payment bill after DingTalk approval completes. It covers the data flow, key field mapping, Qeasy configuration essentials, phased scheduling, and lessons learned from real-world pitfalls. The integration side only passes the document number; field-level conversion is handled by Kingdee's internal push-down rules, making it ideal for financial closed-loop scenarios where upstream initiates approval and downstream writes back the voucher.
This article focuses on a specific inventory transfer synchronization strategy—pushing transfer orders from Jushuitan to Kingdee Xingchen transfer-out documents (non-Qimen channel). It walks through the business background, field mapping, Qeasy configuration essentials, phased scheduling, and lessons learned from real-world pitfalls, helping enterprise IT teams implement multi-system inventory collaboration.
This tutorial systematically consolidates the practical points of querying the Operator master data (BD_OPERATOR) via the Kingdee Cloud executeBillQuery WebAPI. Drawing on multiple real integration projects, it covers field definitions, incremental filters, pagination strategies, and cross-system mapping experience, enabling engineers to master the full integration in one read.
This tutorial centers on P2-342 (Query Kingdee Other Outbound Order, row-by-row), aggregating hands-on experience from multiple supply chain integration projects. It covers executeBillQuery field mappings, request parameters, pagination and incremental patterns, Qeasy platform packaging, and common pitfalls, giving engineers a one-stop reference for cross-system outbound order integration.
抖店的资金账单把所有费用项塞进同一份 CSV——平台服务费、佣金、拦截费、提现、消费者赔付、月付贴息……一个店铺月结就有十几种费用类型，每种还要落到金蝶不同的单据。抖店费用转换脚本 v1.1.0（2026-09-03 用户定稿）用「**流水级直查 + 13 条规则 + 应付带符号净额**」回答这个问题——不经过对账聚合层，直接按「单据类型 × 核算项目」从账单行成单，扣款出正数、退还出红字冲减，单据合计与费用计划聚合净额对平。本文拆开这 13 条规则的分组、应付带符号净额的反直觉之处、v1.1.0 之后的版本演进，以及试跑批次与 Excel 验算锚点。
把一份《智能对账系统选型清单》发给 12 家候选厂商，得到的答案往往是"功能都有"。但认真翻一遍代码、跑一遍沙箱、对一遍生产数据后会发现：宣称"沙箱执行"的产品里有 11 家其实是"提交工单 + 等待回执"的黑盒；宣称"AI Agent 编写脚本"的有 9 家只是把模板拼接丢给大模型；宣称"集成中心"的有 8 家不告诉你"重启用会清空运维配置"。本文不讲功能表上的"都有"，只讲 10 个生产环境里真实好用、不易被同行抄袭的工程细节。
库存级核算是电商精细化财务核算的"最后一公里"——前 4 个维度（店铺级 / SKU 级 / 毛利级 / 税务级）算的是"账面赚了多少钱"，库存级算的是"账面利润被库存吃掉了多少"。一家年 GMV 5 亿的电商公司，看似 18% 的净利率，扣除「在库滞销 + FBA 长期仓储 + 退货在途 + 缺货损失」4 类隐性库存成本后，真实净利可能只有 6.8%——11.2 个百分点的差额就是库存黑洞。本文给出 CFO 必须看清的 4 类库存成本、多仓核算口径、库存周转"虚假拉长"的 3 大陷阱，以及 FBA 仓 + 国内仓的多仓合并视图。
Strategy-level walkthrough of pulling sales order headers from Kingdee Cloud on a */4 schedule via executeBillQuery, landing them into an in-house MySQL OMS table through Qeasy Data Integration. Covers field mapping, phased scheduling, lessons learned, and scope boundaries.
This article walks through a typical auxiliary data value pull-back scenario from Kingdee Cloud to MySQL, covering data flow, field mapping, Qeasy configuration, phased scheduling, and lessons learned on code mapping, incremental start points, and idempotent deduplication.
In sales order scenarios, enterprise bank account data is often scattered inside the ERP, while the CRM side needs to reconcile by account. This article uses the 'Query YongYou Enterprise Bank Accounts' strategy as a concrete example, breaking down the paging structure, scheduling design, and configuration points on the Qeasy data integration platform.
A field-tested walkthrough of syncing inventory-loss outbound documents from JikeCloud to Kingdee Cosmic, covering field mapping, scheduling cadence, and common pitfalls on the Qeasy integration platform.
Focused on the after-sales refund-order query scenario, this guide walks through configuring a single-strategy flow from LingXing ERP into the Qeasy integration platform. It covers data flow, field mapping, configuration highlights, phased scheduling, and common pitfalls.
This article focuses on one procurement monthly settlement sync strategy, explaining how the source system's monthly settlement instances are incrementally pulled by update time and written into downstream ERP business documents via Qeasy, with full configuration, scheduling and lessons learned.
This tutorial aggregates hands-on experience from real-world private-deployment integration projects, using the Kingdee Cloud Galaxy Sales Order query and the Xiaoshouyi currency and bank account queries as the example. It covers authentication, incremental pagination, nested field extraction, code mapping, scheduling, and retry practices.
This guide focuses on a single store-to-customer synchronization strategy, covering field mapping, Qeasy configuration, incremental and full synchronization scheduling, and common issues. Its goal is to prevent duplicate customers, coding mismatches, and the reintroduction of inactive records.
