Jushuitan Inventory Count Sync to Xingchen Surplus: A Practical Guide Based on Qeasy

What This Strategy Solves

A retail enterprise uses Jushuitan for daily inventory counts, while the finance side needs to book surplus and loss in Kingdee Cloud Xingchen. Running separately, the two systems rely on manual transcription at month-end, causing frequent errors. We use the Qeasy Data Integration Platform to automatically push Jushuitan count documents into Xingchen surplus documents, so inventory differences enter the finance system the same day and do not pile up at month-end.

Data Flow and Field Mapping

Data flows from Jushuitan, passes through Qeasy's intermediate layer for cleansing and mapping, and is written into Xingchen surplus documents. Key field correspondences are as follows:

The intermediate layer handles code mapping (Jushuitan warehouse code to Xingchen warehouse code), difference calculation (actual minus book), and document status validation (only sync approved count docs).

How to Configure on Qeasy

On the Qeasy Data Integration Platform, this strategy is configured in four parts:

1. Source System Data Source: Configure Jushuitan API access credentials and store authorization. Qeasy's built-in connector can directly pull count document lists and details.

2. Target System Data Source: Configure Kingdee Cloud Xingchen V2 open platform authorization, confirming surplus document write permission and organization code.

3. Field Mapping and Transformation: Drag and drop field correspondences in Qeasy's mapping canvas, and calculate the difference via formula nodes. We recommend centralized management of code mappings—Qeasy supports maintaining an independent mapping table, from which warehouse, product category, and batch rules are read. This way, adding or changing warehouses or stores later requires editing only one place.

4. Write Control: Surplus documents typically have a header (document number, warehouse, date) and body (line item details). Qeasy's header-and-body phased configuration fits perfectly—the header is written first to obtain the document's internal ID, then body lines are written in batch, avoiding incomplete documents.

Implementation Steps

We recommend a three-phase rollout:

Phase 1: Full Initialization. Sync all historically approved count documents to Xingchen at once, using Qeasy's manual trigger mode for full sync. After completion, manually verify document counts and differences on both sides, then enable automatic scheduling once confirmed.

Phase 2: Set the Incremental Starting Point. In Qeasy's scheduling configuration, set the incremental start to midnight of the day after the first full sync completes. Thereafter, pull newly created or modified count documents from Jushuitan daily on schedule. Incremental and full sync run on parallel tracks: full for initialization, incremental for daily operations.

Phase 3: Enable Schedule Frequency. Inventory counting is usually not high-frequency; we suggest setting Qeasy's scheduled task to run once daily in the early morning, avoiding Xingchen's account closing period. If the customer requires more real-time sync, the frequency can be raised to hourly, but watch out for Xingchen's API rate limits.

Lessons Learned

1. Wrong difference calculation turns surplus into loss. In some cases, Jushuitan's "difference" field uses positive numbers for surplus and negative for loss, but Xingchen surplus documents only accept positive values. A safe approach is to use absolute value conversion in the intermediate layer and add a validation rule: negative differences should go to loss documents, not surplus documents.

2. Warehouse codes mismatch, document write fails. Jushuitan's warehouse codes are internal IDs, while Xingchen uses warehouse archives within its organizational structure. If codes do not match and no mapping exists, documents get stuck in Qeasy's error queue. A typical mistake is writing source codes directly—this is a common pitfall. You must pass through the mapping table first.

3. Unapproved count documents get synced too. Counters may still be modifying documents after creation in Jushuitan, and syncing at that point generates dirty data. Always add a status filter in configuration, syncing only documents with "approved" status.

4. Body line write order is wrong. Body line items must be written in order, otherwise Xingchen reports a sequence error. Qeasy's header-and-body phased configuration avoids this problem, but ensure body batch writes are sorted by source document line number.

5. Incremental start set too early, causing duplicate sync. If the incremental start is set before full sync completes, some documents get synced twice. We suggest confirming the timestamp of the last successful record in Qeasy's log after full sync, then setting the incremental start to after that time.

Applicable and Non-Applicable Scenarios

Applicable: Multi-store retail enterprises using Jushuitan for inventory management, where the finance side needs to record surplus and loss in Xingchen and generate vouchers; count results need to be booked the same day rather than batch-processed at month-end.

Not applicable: The counting process is completed entirely within a single system; surplus and loss require an approval workflow rather than mere data sync; source and target systems are the same.