Qeasy Cloud
Get Started

Jushuitan Other Outbound Orders → Kingdee Cloud Xingchen Other Outbound Orders: An Inventory Sync Strategy Tutorial

· 陈洁琳· Integration Solutions· 20 views· 4 min read

What This Strategy Solves

In one of our retail customers running multi-warehouse, multi-channel operations, Jushuitan acts as the front-end business system while Kingdee Cloud Xingchen serves as the back-end finance and inventory ledger. Other outbound orders — non-sales movements such as transfers, internal consumption, and inventory write-offs — exist on both sides, but with different coding rules, organizational dimensions, and batch-number definitions. Once data is re-entered manually, within three months the inventory numbers on both sides will inevitably diverge.

The core value of this strategy is to treat other outbound orders as key inventory-movement documents: the moment they occur in Jushuitan, they are pushed to Xingchen, ensuring both ledgers stay consistent, audit trails remain intact, and month-end manual reconciliation effort is reduced.

Data Flow and Field Mapping

The overall direction is unidirectional push: Jushuitan (source) → Qeasy Data Integration Platform (intermediate layer) → Kingdee Cloud Xingchen (target). The intermediate layer does not persist business data; it only performs field mapping, code translation, and exception staging.

Key field mapping (always cross-check with the actual interface fields on both sides in real projects):

Business MeaningJushuitan FieldIntermediate LayerKingdee Xingchen Field
Document Numberio_id / external no.Pass-through + uniqueness checkFBillNo
Outbound Dateio_dateyyyy-MM-dd normalizationFDate
Warehousewarehouse_nameLookup in code mapping tableFStockId
Material Codesku_idCode mapping (depends on material master strategy)FMaterialId
QuantityqtyNumeric type validationFQty
Batch Numberbatch_noPass-through, drop emptyFBatchNo
RemarksremarkTruncate + UTF-8FNote

Centralized management of code mappings is a common pattern on Qeasy — the source/target code pairs for warehouses and materials are placed in a single mapping table, referenced by every related document strategy so that one change propagates everywhere.

How to Configure on Qeasy

On the Qeasy platform, this strategy lives as one integration flow. The core configuration points are:

  1. Source Connector: Select the Jushuitan adapter, configure API authorization issued by the Jushuitan open platform (credentials themselves are never stored in plaintext), and pull from the relevant outbound-order endpoint, taking data incrementally by modified_time.
  2. Target Connector: Select the Kingdee Cloud Xingchen V2 adapter, configure access to the target tenant (again, no plaintext secrets), and set the target document type to "Other Outbound Order".
  3. Field Mapping: In Qeasy's mapping canvas, drag source fields to target fields per the table above. Prefer built-in mapping functions ("date format", "numeric validation", "code lookup") over custom scripts; reserve scripts for special logic such as how to handle an empty batch number.
  4. Code Mapping Table: Upload and maintain the warehouse and material code mapping tables — this is where the "centralized code management" pattern is implemented.
  5. Exception Handling: Enable "retry 3 times with exponential backoff"; failed documents are routed to a "pending queue" for manual remediation and re-push.
  6. Logging and Monitoring: Enable document-level logging so each push can be traced to its source snapshot, mapping result, and target response code.

Implementation Steps

We recommend a three-phase rollout rather than flipping everything on at once:

Phase 1: Incremental Start Point Confirm that historical outbound orders on Jushuitan have already been reconciled, then pick a clear starting timestamp (e.g., the first day of the month) and only push documents after that point. The inventory ledger on Xingchen is treated as the source of truth; new documents are simply added. This keeps risk minimal.

Phase 2: Full Backfill (Use with Care) If historical data must be backfilled, run a one-shot "full backfill task" on Qeasy and stop it afterward — never let it share a crontab with the incremental job. The classic mistake is mixing full and incremental in the same time window, which causes duplicate or missed documents.

Phase 3: Production Schedule Set the schedule based on volume. For high-volume near-real-time needs, a 5–10 minute interval works; for lower volume, 30 minutes to an hour is sufficient. Qeasy's crontab supports minute/hour/day granularity. We usually recommend starting at "every 15 minutes", running it for two weeks while watching target-system load, then tuning.

The safe approach is the "dual-track incremental + full" pattern: incremental runs daily as the steady state, while full is kept as a one-shot backfill tool and never left enabled long-term.

Lessons Learned

  1. Missing warehouse code mapping. In one customer project, a newly created warehouse on the source side was not present in the mapping table, so pushes silently failed without an "unknown code alert" being configured. The discrepancy surfaced only at finance reconciliation time. The fix: any code mapping strategy must ship with an automatic alert for unknown codes on day one.
  2. Inconsistent empty-batch handling. Jushuitan allows an empty batch number, but Xingchen's batch field, when populated, must match a specific format. The robust pattern is to substitute a fixed placeholder (e.g., NO_BATCH) at the mapping layer instead of passing null through.
  3. Time zone and date boundaries. In cross-day schedules, "yesterday's documents" can be attributed to "today" under different time zones, causing incremental misses. Explicitly configure source/target time zones on Qeasy and slice windows by business day rather than calendar day.
  4. Mixing full and incremental. As mentioned above, the most common customer-site failure is forgetting to disable the full-backfill script, which then runs a second full load and produces duplicate documents on the target. Mitigation: tag full-load tasks as "one-shot" so they are auto-archived upon completion.

When This Strategy Fits and When It Doesn't

Fits: multi-channel retail/distribution scenarios where Jushuitan is the front end and Kingdee Cloud Xingchen is the back-end finance and inventory system, and other outbound orders must be synced in near real time.

Does not fit: when both systems independently own inventory and reconcile separately; when Xingchen itself is the originating source for outbound documents; or when document volume is so high that an event-driven, message-queue-based approach is required instead of a scheduled pull.

Original content. Please credit the source when reposting: https://www.qeasy.cloud/insights/solutions/strat-jushuitan-kingdee-cloud-9521-nfa4873c5-c4157afe

Comments