Syncing Kingdee Inventory Surplus Vouchers to Wangdiantong Outsourced Inbound Orders: A Cloud-Warehouse Configuration Tutorial
What This Strategy Solves
In a cloud-warehouse model, a retail or manufacturing customer needs inventory surplus generated in Kingdee Cosmic (Kingdee Cloud Stellar / Kingdee Cloud Sky) to flow into Wangdiantong as outsourced inbound orders. The voucher value is small and the frequency is low, but if any record is missed, the downstream warehouse ledger drifts away from the ERP and the finance team keeps asking questions during the monthly reconciliation. This strategy maps Kingdee surplus vouchers to Wangdiantong outsourced inbound orders through Qeasy, closing the inventory loop.
Data Flow and Field Mapping
Data flows from Kingdee Cosmic to Wangdiantong. Qeasy acts as the middle layer handling field translation, code alignment, and exception routing.
| Key Field | Kingdee Surplus Voucher (Source) | Middle Layer Handling | Wangdiantong Outsourced Inbound Order (Target) |
|---|---|---|---|
| Document Number | Surplus voucher number | Pass through, keep prefix | External order number |
| Warehouse | Inventory org + warehouse code | Translated via code-mapping table | Warehouse code |
| Owner | Owner dimension | Default value or main owner | Owner code |
| Item Code | Material code + batch | Unified material mapping | SKU code |
| Quantity | Surplus quantity | Validate non-negative, filter decimals | Inbound quantity |
| Outsourced Supplier | — | Default supplier mapped from org | Outsourced supplier code |
| Remark | Business remark | Concatenate with surplus reason | Remark field |
Code mappings are centrally stored in Qeasy's Data Mapping Center. Adding new warehouses or items later only requires changing one place, avoiding scattered maintenance across multiple strategies.
How to Configure in Qeasy
- Connect the source system: Create a Kingdee Cosmic connector in the Qeasy Data Integration Platform. Configure the API gateway endpoint (input after desensitization) and select "Surplus Voucher" as the collection object.
- Connect the target system: Create a Wangdiantong·Qiye Qimen connector, authorize the cloud-warehouse account, and confirm that the outsourced inbound order interface is available.
- Field mapping: Enter the strategy canvas and wire each field in the table above one by one. Encoding fields should be pulled from the Mapping Center, not hard-coded in scripts.
- Data filtering: Add source-side filter conditions: "Document status = Approved" and "Business type = Surplus", to prevent draft or adjustment vouchers from being pushed downstream.
- Exception handling: Attach a branch node in Qeasy — surplus vouchers that fail validation fall into an exception pool, alerts are pushed to the enterprise IM, and engineers handle them manually.
Implementation Steps
We recommend a three-phase rollout to avoid going fully live at once.
Phase 1: Incremental Start. First, take the surplus vouchers approved in the last 7 days for small-batch validation. Verify that field mapping, code alignment, and order write-back all work, then open the formal pipeline.
Phase 2: Full Trigger. Configure a one-time full task in Qeasy to backfill historical surplus vouchers into the Wangdiantong cloud warehouse in time slices (1 day per slice). After backfill completes, perform a stock reconciliation to confirm quantities on both sides match.
Phase 3: Scheduling Frequency. Surplus voucher frequency is not high, so we suggest scheduling the Qeasy strategy to poll every 15 minutes. During promotion periods, you can temporarily tighten it to 5 minutes. Note: faster scheduling is not always better; too frequent polling will trigger rate limiting on the target platform.
After both incremental and full pipelines are online, the daily workload runs on incremental, and full acts as the reconciliation compensation channel at month-end.
Lessons Learned from the Field
Pitfall 1: Surplus and shortage vouchers collected together. In Kingdee, surplus and shortage share the same document type and are distinguished only by business type. A typical mistake is to grab everything where "Document type = Stocktake voucher", which ends up pushing shortage vouchers into outsourced inbound orders and inflating stock. The safe approach is to hardcode "Business type = Surplus" in the source-side filter and add a second whitelist check in Qeasy's filter node.
Pitfall 2: Outsourced supplier code not maintained. Outsourced inbound orders must carry a supplier, but the surplus voucher itself does not. The common approach is to maintain a default supplier mapping table by inventory organization in Qeasy, so that when the organization changes the supplier switches automatically — never hardcode a constant.
Pitfall 3: Batch number and production date format mismatch. Kingdee batch numbers carry a prefix; Wangdiantong does not. Date formats also differ. Format them uniformly in the middle layer; otherwise batch validation will fail when the cloud warehouse receives the inbound.
Pitfall 4: Write-back status not closed-loop. After pushing the outsourced inbound order, we did not write back the Wangdiantong-issued inbound order number into a custom field on the Kingdee surplus voucher, which forced manual lookups during reconciliation. The safe approach is to use Qeasy's callback node to write the target order number back to the source document and tag it as "Synced".
Pitfall 5: Exception records fail silently. In the early stage, no exception pool was attached. Occasionally a surplus voucher failed to push due to a missing code, and no one noticed until the month-end reconciliation revealed the discrepancy. Always configure exception alerts in Qeasy and persist the failure reason to a log.
Applicable and Non-Applicable Scenarios
Applicable: Multi-organization, multi-warehouse retail or manufacturing enterprises where Kingdee is the finance and inventory master and Wangdiantong handles e-commerce fulfillment and cloud-warehouse outsourced inbound.
Not applicable: Scenarios where Wangdiantong is not running in cloud-warehouse mode, or surplus is handled through direct adjustment without generating inbound; also not applicable to test-only environments without real inventory variance.