Practical Configuration for Syncing Inventory Overflow Inbound Orders from Jike Cloud to Kingdee Cloud Stellar

What This Strategy Solves

In a typical retail operation, warehouse staff record inventory overflow entries in Jike Cloud during physical counts, while Kingdee Cloud Stellar serves as the backend accounting system that requires a complete overflow voucher for inventory and cost adjustments. Manual re-entry is inefficient and error-prone. This strategy incrementally syncs overflow inbound orders from Jike Cloud to Kingdee Cloud Stellar as overflow vouchers, achieving "record once at the site, balance automatically at the backend."

Data Flow and Field Mapping

The flow is unidirectional: Jike Cloud (overflow inbound order) → Qeasy integration platform (intermediate layer) → Kingdee Cloud Stellar (overflow voucher).

Master data fields such as material codes and warehouse codes must first be populated through base data strategies like "Material Sync" and "Supplier Sync"; otherwise the Kingdee side will throw errors due to missing primary keys.

How to Configure on Qeasy

Step 1: Create a new strategy with Jike Cloud as the source and Kingdee Cloud Stellar as the target. Select the business domain as "Supply Chain Integration - Business Documents - Inventory Sync." Use a clear naming convention like "(Jike Cloud -> Kingdee) Overflow Inbound (Jike Cloud) -> Overflow Voucher (Kingdee Cloud Stellar)" for easier troubleshooting later.

Step 2: On the source side, use the Jike Cloud overflow inbound interface, set an incremental starting point (typically the last 30 days), and apply a filter for "Document Status = Approved." On the target side, call the Kingdee overflow voucher save interface. Disable auto-submit so the voucher is saved first and then approved manually or by a follow-up action.

Step 3: Centralize field mappings in the Qeasy mapping canvas rather than scattering them across scripts. In one real project, we extracted code mappings into a "Centralized Code Mapping" module, which meant new warehouses could be added later without touching the strategy.

Step 4: Handle the header and line items in phases. Run the header first to confirm the voucher lands correctly, then enable line items. This is especially important for overflow vouchers because the line items carry overflow quantities and variance calculations; running everything at once can easily trigger inventory validation errors on the target.

Step 5: Attach "Schedule - Retry on Failure - Alert Notification" to the strategy. Overflow vouchers are low-frequency but sensitive documents; a 30-minute interval is usually sufficient. Trigger mode is reserved for cases where the push must happen immediately after the count is finished.

Implementation Steps

Phase 1: Incremental starting point. At go-live, use a fixed business date as the start point and push all historical overflow vouchers within the backfill window so nothing is missed on day one.

Phase 2: Full-volume trigger. Once the incremental run is stable, use Qeasy's "Full Backfill" feature to replay data in batches by warehouse or time range and confirm that the voucher counts on the target side match the source.

Phase 3: Daily scheduling. Set the strategy interval to 30 minutes and adopt a "dual-track" model: incremental every 30 minutes, full reconciliation once a day in the early hours. Any discrepancy triggers an automatic alert. This approach has proven extremely useful at customer sites.

Phase 4: One week after go-live, perform a reconciliation between the Jike Cloud overflow inbound orders and the Kingdee overflow vouchers, verifying amounts, quantities, and batches before handing over to the business team for daily use.

Pitfalls Recap

First, missing material mapping. Overflow voucher line items always carry materials. If master data is not synced first, low-level errors like "Material does not exist" will appear. The safe approach is to explicitly declare the dependency on the material sync strategy within Qeasy's orchestration, so the downstream strategy will not start until prerequisites are complete.

Second, inconsistent quantity units. Jike Cloud commonly uses "piece" as an auxiliary unit while Kingdee uses the base unit. A typical mistake is passing the Jike quantity through directly, leading to amount discrepancies. A unit conversion must be performed in the mapping layer.

Third, time zone issues on date fields. Jike Cloud returns a timestamp with time zone, while Kingdee expects a business date string. The typical pitfall here is mismatched date values. A robust practice is to truncate timestamps to "YYYY-MM-DD" in Qeasy's field transformation.

Fourth, strict approval status validation. Once an overflow voucher is saved in Kingdee, it triggers inventory updates by default. If a draft status is passed through, the approval must be handled through a dedicated Kingdee interface rather than stuffing status fields into the mapping.

Fifth, idempotency in retries. Overflow vouchers typically use the document number as the idempotency key. Qeasy deduplicates by document number by default, so do not add random suffixes in custom scripts, or duplicate vouchers will be created.

Applicable and Non-Applicable Scenarios

Applicable: Single-entity or small multi-entity retail and wholesale businesses that use Jike Cloud for frontline operations and Kingdee Cloud Stellar for backend accounting, with standardized counting workflows. Not applicable: large groups with multiple legal entities requiring separate account books, or scenarios that require real-time write-back of Kingdee's approval status to the frontend. For those cases, event-driven integration is preferred over scheduled sync.