Syncing Kingdee Other-Inbound Documents to Wangdiantong Subcontracting Inbound: A Single-Strategy Practical Guide
What This Strategy Solves
In a warehousing unification project for a retail enterprise, Kingdee Cloud Galaxy serves as the ERP backend for financial bookkeeping and inventory book calculations, while Wangdiantong acts as the warehouse execution system that records actual inbound operations. In subcontracting scenarios, the "Other-Inbound Documents" generated by Kingdee (reflecting subcontracted finished goods or semi-finished products returned) need to be synced to Wangdiantong's "Subcontracting Inbound Documents" as the execution basis for downstream warehouse receiving and put-away. Without synchronization, warehouse operators cannot see subcontracting tasks, and book inventory will drift from physical inventory over time.
Data Flow and Field Mapping
The data flow is unidirectional: Kingdee Cloud Galaxy → middleware (Qeasy Data Integration Platform) → Wangdiantong Enterprise. We recommend avoiding scattering mapping logic across multiple scripts. Instead, perform a one-time "centralized encoding mapping" at the middleware layer. Source system document numbers, organization codes, warehouse codes, and material codes are standardized at the middleware layer before being written into the target system.
Below is a key field mapping table (only common fields are listed; actual projects should follow source system metadata):
| Business Meaning | Kingdee Cloud Galaxy (Source) | Wangdiantong (Target) | Handling Notes |
|---|---|---|---|
| Document Number | FBillNo (Other-Inbound Doc No.) | external_order_no | Passed through as-is, serves as idempotency key |
| Document Type | Business document type field | order_type=subcontracting inbound | Constant mapping at middleware layer |
| Warehouse | FStockId (warehouse internal code) | warehouse_code | Converted via encoding mapping table |
| Supplier | FSupplierId | provider_code | Subcontracting supplier, must be mapped |
| Product Code | FMaterialId | goods_id | Material master must be synced before this strategy |
| Quantity | FQty | num | Units must be unified; conversion recommended at middleware |
| Remarks | FNote | remark | Text field passed through directly |
A common pitfall here: material codes. If the material master strategy hasn't completed before the document strategy runs, Wangdiantong will report "product does not exist." The reliable approach is to set the material strategy as a dependency of this strategy, with schedule order A then B.
How to Configure on Qeasy
On the Qeasy Data Integration Platform, this strategy is carried by an independent integration flow. Configuration essentials are as follows:
- Source Connection: Choose the Kingdee Cloud Galaxy adapter and pull "Other-Inbound Documents" via the query interface. The incremental starting point typically uses the last modified time (FModifyDate) field for time-window filtering, avoiding re-pulling historical documents each time.
- Target Connection: Choose the Wangdiantong Enterprise adapter and call its subcontracting inbound document creation interface.
- Data Processing: Add a "Phased Header/Body" processing node at the middleware layer—first process the header (warehouse, supplier, document number), then iterate through the body (line items). The benefit of this phased approach is that once the header is landed, line items can be written in batches, avoiding a single large transaction.
- Encoding Mapping: Maintain a separate "Kingdee-Wangdiantong Encoding Mapping Table," updated by the material master strategy; this inventory strategy only reads it. This way, encoding mapping is centralized at the middleware layer, avoiding inconsistencies from multiple strategies maintaining their own mappings.
- Idempotency Control: Use the Kingdee document number as external_order_no; Wangdiantong performs deduplication based on it, so repeated pushes will not generate duplicate documents.
Implementation Steps
We recommend breaking the rollout into a three-phase schedule:
Phase 1: Full Initialization. During a nightly window, push all historical unsynced "Other-Inbound Documents" to Wangdiantong in one batch. This step requires manual confirmation that source system data is frozen to avoid missing records.
Phase 2: Incremental Start Switchover. Record the last modified time at which full synchronization completed, and begin incremental scheduling from that point forward. We recommend running the first incremental twice: the first to confirm no new data exists (validating the window), the second to begin actual fetching.
Phase 3: Schedule Frequency. Subcontracting inbound does not require second-level response like sales orders, but financial reconciliation requires daily settlement. We generally recommend 15-minute increments, with relaxation to 1 hour during low-traffic night periods. Qeasy's scheduler directly supports cron expressions.
It should be emphasized that full and incremental operate as a "dual-track parallel" relationship, not substitution—full is for initialization, incremental is for daily rolling, and the two are strictly distinguished by the time-window field.
Pitfall Retrospective
In an actual project, we encountered these pitfalls for future reference:
- Inconsistent Units Causing Doubled Quantities. Kingdee's default unit is "base unit," while Wangdiantong inbound uses "inbound unit." Without unit conversion at the middleware layer, receiving 100 pieces in the warehouse becomes 100 base units (possibly boxes), causing inventory loss.
- Multi-Branch Organization Code Conflicts. Group enterprises have multiple organizations, and Kingdee organization codes do not map one-to-one with Wangdiantong shop codes. Without mapping, documents from all branches will be written to a single warehouse.
- Approval Status Not Synced. Kingdee documents require approval before serving as the official inbound basis. If the approval status field is not captured, draft-status documents will also be pushed, generating invalid inbound entries in Wangdiantong.
- Deleted Documents Cannot Be Rolled Back. Kingdee supports voiding documents, but Wangdiantong inbound documents are hard to delete after creation. We recommend adding a status check at the middleware layer: skip pushing if the source document is voided; already-pushed ones require manual reversal in Wangdiantong.
- Empty Subcontracting Supplier Causes Interface Errors. If the subcontracting supplier is not maintained in Kingdee, the push to Wangdiantong will definitely fail. We recommend a mandatory validation at the source—only non-empty entries enter the queue.
Applicable and Non-Applicable Scenarios
This strategy applies to: private deployment with both Kingdee Cloud Galaxy and Wangdiantong Enterprise coexisting, stable subcontracting business, and a dedicated operations team maintaining the encoding mapping table. It does not apply to: cross-group multi-account sets requiring real-time second-level synchronization (consider direct middleware database connections), projects where material master data is not yet standardized, or units change frequently.