Inventory Surplus Sync in Practice: From Jushuitan to Kingdee Cloud Skyline Other Inbound Orders

What This Strategy Solves

In retail and distribution scenarios, if inventory surplus orders generated after stocktaking only circulate within Jushuitan, financial reconciliation and general ledger data will not align. In one actual project, a retail enterprise needed daily stocktaking surplus results synced to Kingdee Cloud Skyline as other inbound orders the same night, otherwise next day's closing would stall. This strategy solves the cross-system consistency of inventory variance documents, keeping business front-end and finance back-end inventory quantities in sync.

Data Flow and Field Mapping

The data flow is unidirectional: Jushuitan (Inventory Surplus Order) → Qeasy middleware → Kingdee Cloud Skyline (Other Inbound Order). The middleware handles code conversion, field completion, and unit conversion.

Key field mapping table (desensitized):

Centralized code mapping management is a common pattern among Qeasy customers: all warehouse and material correspondences are maintained in one mapping table, so system upgrades on either side do not affect the main flow.

How to Configure in Qeasy

In Qeasy Data Integration Platform, this strategy's configuration mainly falls on three nodes:

1. Source data extraction: Select Jushuitan's inventory surplus order interface, set filter conditions (usually created today or audited today), page size recommended 50-100 records to avoid triggering rate limits by pulling too much at once.
2. Transformation orchestration: Attach scripts in Qeasy's transformer, mainly doing three things—code mapping, field completion (e.g., default cost price falls back to standard price), and splitting/reassembling document header and body. Phased header-body processing is another common customer practice: write the document header first, then loop through the body, retry only the body on failure without redoing the header.
3. Target write: Call Kingdee Cloud Skyline's other inbound order save interface. It's recommended to enable Kingdee's two-step mode (draft then submit): draft first to confirm no field errors, then formally submit.

Incremental and full-volume dual-track is very useful here: run incremental daily (by time window), and run a full-volume difference check at the start of each month.

Implementation Steps

Phased scheduling is key to stable rollout:

Step 1: Align incremental starting point After both systems' clocks are aligned, take a clear timestamp as the incremental starting point. It is recommended to observe the actual generation rhythm of Jushuitan surplus orders for one week first, confirming whether they concentrate before closing time or disperse throughout the day, then finalize the initial sync time.

Step 2: Full-volume trigger and backtracking Before first launch, use Qeasy's full backtracking function to sync surplus orders from the past 7 days to Kingdee, verifying field mapping is correct. After full-volume completes, switch to incremental mode.

Step 3: Scheduling frequency Surplus orders are not high-frequency documents, once a day is usually enough. A common practice is to set scheduled execution during off-peak hours, such as 2 AM daily; if the customer requires more timeliness, it can be shortened to every 4 hours, but minute-level is unnecessary.

Step 4: Exception monitoring Configure alert rules in Qeasy to notify operations when field mapping fails, interface times out, or document quantity is abnormal. Within the first week of launch, it is recommended to manually reconcile quantities on both sides daily.

Pitfall Review

Pitfall 1: Code mapping scattered across scripts A typical mistake is each engineer maintaining their own mapping script, requiring changes in multiple places. The stable approach is to store all code mappings centrally in Qeasy's mapping table with centralized permission management to avoid version drift.

Pitfall 2: Syncing unaudited surplus orders Jushuitan surplus orders have a "saved but unaudited" state. If unaudited documents are synced directly to Kingdee, finance side will see a bunch of dirty data. The easy-to-flip point here is not filtering by status—always add status = audited condition in source extraction.

Pitfall 3: Empty cost price causes Kingdee validation failure Some products don't maintain surplus cost price, syncing to Kingdee triggers required field validation. The stable approach is to add default value fallback in the transformer, such as retrieving material standard price or last purchase price.

Pitfall 4: Warehouse mapping missed After new warehouses go live in Jushuitan, if not synced to the mapping table timely, Kingdee side will reject writes. Incremental and full-volume dual-track verification can detect such issues early; running a full-volume comparison at the start of each month is recommended.

Pitfall 5: Kingdee document concurrent submission If the same surplus order is retried due to network jitter, it may generate duplicate inbound orders in Kingdee. The easy-to-flip point here is no idempotency control—the stable approach is to use Jushuitan surplus order number as Kingdee document number, Kingdee's duplicate save validation will directly reject the second submission.

Applicable and Non-applicable Scenarios

Applicable scenarios: Inventory variance documents such as surplus/loss needing real-time sync to finance system; inventory adjustments in multi-warehouse multi-owner scenarios; enterprises needing Kingdee Cloud Skyline for general ledger accounting.

Non-applicable scenarios: High-frequency real-time inventory query (recommend using real-time inventory interface rather than document sync); cross-organization transfers (should use transfer order strategy rather than surplus order); business draft documents not yet audited in source system.