Latest industry insights, tutorials, best practices and case studies.
1090 articles
For smart manufacturing scenarios, this solution designs 22 integration strategies between Kingdee Cloud Galaxy and Sihua MES, covering master data, production, procurement, inventory, and query flows. Execution is phased across four stages with master data first and business documents dependent on it. Code mapping, incremental fields, and staggered write windows ensure data consistency.
This tutorial uses the 'modify pushed-down payment bill' strategy as an example to explain how to incrementally write back DingTalk approval field changes to Kingdee Cloud payment bills on the Qeasy platform, covering key practices such as cross-query locating FID, enum mapping, and NeedUpDateFields restriction.
This guide dissects the single strategy of querying sales return requests, covering data flow, field mapping, configuration on Qeasy, phased scheduling, four pitfalls from real projects, and clear boundaries.
Pushing a document into Kingdee Cloud Galaxy is only the starting point; what business users really need is a visible status update in DingTalk. Using one concrete strategy, this article breaks down the source-side null-op validation, the DingTalk comment API call, and the lightweight scheduling concerns.
This article focuses on a single strategy: how to reliably push approved purchase orders from Panwei OA into Kingdee Cloud Cosmos, including header and line items. Drawing on a real project, it covers data flow, field mapping, configuration highlights on the Qeasy data integration platform, phased scheduling, and 3–5 practical lessons learned to help enterprise IT teams avoid common pitfalls.
This article focuses on the "subordinate department" master data sync strategy, explaining how to reliably push department data from Weaver (stored in SQL Server) to Kingdee via the Qeasy Data Integration Platform. It covers data flow, field mapping, configuration in Qeasy, phased implementation steps, and three practical pitfalls.
某年 GMV 9.6 亿的运动品牌在天猫、抖音、京东、唯品会、得物 5 个平台经营 16 个店铺,SKU 1 800+,直营门店 240 家、加盟店 380 家。2025 年 9 月之前,新招的财务专员平均需要 6 个月才能独立完成月结对账;门店新店长的 ERP 操作上手期平均 11 周;老员工离职时带走的不是「人」,是 5 年的对账经验与门店运营手感。2025 年 10 月上线 RAG 知识库后,**财务新人独立上岗周期从 6 个月压到 11 周(−46%)、门店新店长 ERP 上手从 11 周压到 4 周(−64%)、老员工经验沉淀覆盖率从 18% 提升到 87%**。本文还原这家运动品牌如何把「老员工脑子里的经验」沉淀成「企业可调用的 AI 知识资产」,以及这套机制背后 5 个反直觉的发现。
一家年 GMV 14 亿元的多平台电商，2026 年 Q1 利润表净利润 6800 万元，账上现金却只剩 1200 万元——CFO 在 4 月 28 日经营分析会上被问到「利润去哪了」时哑口无言。复盘发现 4 大问题里有 3 个出在「现金流预测」环节。本文给出 4 大流入 + 4 大流出的精细化建模方法论：销售回款 × 退款回收 × 平台返利 × 其他流入 / 采购付款 × 物流费 × 平台扣点 × 税费，每一条都按平台 × 店铺 × 月份 × 周 4 级颗粒度建模。
已经把京东 POP 账户流水上传到对账系统、解析也跑完了，下一步「对账」应该怎么点？本文用 5 步走完新用户的第一个收入对账计划——从「找到入口」到「整体确认 + 推送转换单据」，每个步骤都对应一个真实的按钮、一段可见的状态变化。读完这篇，你就能把一张 600 单的京东 POP 账户流水从「解析完成」变成「对账成功、推送到金蝶」，并掌握 7 态状态机、23 个 diffReason 业务标签码、整体确认与转换单据的协作方式。
京东 POP 对账完成后，账单上的每一笔订单最终都要落到金蝶。但金蝶不是直接"Save 一张财务应收单"——本账套是暂估模式，财务应收单只能由暂估应收单通过 Push 下推生成。本文讲透这条最容易踩坑的链路：合并出单 v1.7.0 的口径翻转（G1 缺口消解）、推送字段完整性契约、Push 协议本身的硬约束、状态机回写，以及 2026-07 实测的 45 张单如何与手工 Excel 逐分录对平。
电商企业的「利润黑洞」从来不在 GMV 上，而在 5 大成本项的分摊颗粒度上。商品成本、物流成本、平台佣金、广告费、运营成本——每一项都有 3 套分摊维度（按 SKU / 按订单 / 按店铺）、2 套分母口径（净额 / 绝对值）、1 套反直觉规则（推广费退货不冲减分母）。本文按 5 大成本项逐项拆：每项给出「业务口径 + 分摊维度 + 反直觉点 + 落地踩坑」，并用一份 38 店 × 1200 SKU 的真实口径，说明 CFO 月底为什么「账面赚 18%、口袋只有 11%」。
This tutorial walks through a single strategy—'Reconciliation System — Supplier Account (Create Supplier)'—and details the incremental sync from DingTalk YiDa approval forms to a MySQL supplier_account table: business value, field mapping, Qeasy configuration essentials, staggered scheduling, and five lessons learned from real rollouts.
For on-premise deployments, this guide breaks down a single-strategy sync from Kingdee Cloud production orders to MES work orders. Built on the Qeasy data integration platform, it walks through field mapping, status filtering, incremental scheduling and code lookup, delivering actionable configuration notes and pitfall reviews so integration engineers can stand up the shop-floor dispatch data path quickly.
This tutorial aggregates field-proven experience and systematically explains the practical key points of using the Kingdee Cloud Skyline executeBillQuery interface to query the "Terminal Customer" auxiliary data. It covers field mapping, pagination strategies, audit/enable status filtering, multi-organization scenarios, and pitfall retrospectives, helping engineers quickly complete dictionary master data integration in supply chain projects.
Drawn from a real retailer's return-inbound integration, this tutorial dissects a single strategy that incrementally pushes audited sales return orders from a marketing cloud into Kingdee Cosmos. It covers data flow, key field mapping, configuration tips on the Qeasy platform, scheduling, and lessons learned from the field.
This tutorial focuses on a single strategy: pulling sales outbound orders from the source system incrementally and writing them into Kingdee Cloud. It covers field mapping, configuration in Qeasy, phased scheduling, and lessons learned for similar use cases.
This tutorial dissects a material master sync strategy from Kingdee Cloud to MySQL, covering the source QUERY and target WebAPI execution flow. It focuses on centralized code mapping, header field correspondence, and dual-track incremental/full scheduling with actionable configuration guidance and pitfalls.
Based on multiple real customer projects on the Qeasy Cloud Data Integration Platform, this tutorial aggregates practical know-how for the Kingdee Cloud Skylight Customer Query interface, covering the executeBillQuery call, full BD_Customer field mapping, filtering and pagination, multi-org and invoicing/payment bank details, plus common pitfalls in customer master data synchronization.
This article dissects a single sync strategy that turns DingTalk administrative reimbursement forms into Kingdee Cloud payment vouchers. It covers data flow, field mapping, Qeasy configuration tips, phased scheduling, and common pitfalls, helping IT teams quickly build a financial document loop.
In a supply chain integration project for a retail enterprise, accumulating logs and historical data bloated the database and slowed down subsequent syncs. This tutorial explains how to use the Qeasy data integration platform to purge data older than two months at the strategy level via the DeleteStrategyData API, with configuration points, scheduling order, and lessons learned.
