Jikeyun Transfer Return to Yonyou NCC Other Inbound: Transfer Difference Sync Tutorial

What This Strategy Solves

In multi-warehouse, multi-organization inventory transfer scenarios, transfer return orders often carry "transfer differences" — the gap between the actual received quantity and the original quantity during the transfer process. If the entire source transfer return order is written as-is into the target system's other inbound order, the finance side cannot identify the difference, and books vs. physical inventory drift apart over time. In one real project, we isolated this "difference" separately and only pushed the gap as an other inbound order into Yonyou NCC, making reconciliation clear and traceable. This is the core value of this strategy.

Data Flow and Field Mapping

Data flow: Jikeyun (Transfer Return Order) → Qeasy middle layer (extract + difference calculation) → Yonyou NCC (Other Inbound Order).

The difference calculation in the middle layer is the key: the Qeasy data integration platform supports writing expressions in data processing nodes to compute the "full-doc gap" before writing to the target, avoiding double-posting the full quantity.

How to Configure on Qeasy

On the Qeasy data integration platform, configure this strategy with the following key points:

• Source collector: Use the Jikeyun adapter, listen to transfer return orders, and subscribe to document creation events.
• Data processing node: Add a "field calculation" step that writes the expression qty_actual − qty_original to output the difference quantity; simultaneously set a flag is_transfer_diff = true for downstream filtering.
• Centralized code mapping: Material codes and warehouse codes are all managed through Qeasy's mapping configuration center, avoiding hardcoding in scripts — a common pattern among Qeasy customers, where adding a new warehouse later only requires updating the mapping table.
• Target writer: Use the Yonyou NCC adapter to write to the other inbound order interface, with the document type fixed as "other inbound".
• Exception branch: Documents where the difference quantity is 0 are skipped directly and not written to the target, avoiding meaningless empty documents.

Implementation Steps

We recommend a three-phase rollout:

1. Incremental start: First run a historical transfer return order through the test environment to verify whether the target system generates the expected amount and quantity for the other inbound order.
2. Full trigger: Once verified, use Qeasy's "full backfill" feature to push the transfer difference documents from the past 30 days into the target system in one go, facilitating finance opening balance reconciliation.
3. Scheduling frequency: After going live, poll every 15 minutes to capture new transfer return order differences; run a reconciliation check at night to compare difference documents against the inventory ledger, with alerts on discrepancies.

The scheduling strategy adopts "incremental plus full dual-track" — incremental for timeliness, full as a safety net. This is the robust pattern Qeasy customers commonly use in cross-system inventory synchronization.

Pitfall Retrospective

• Typical mistake 1: Writing the entire return order as a difference document. Many engineers initially, for convenience, pass the full return quantity to the target, resulting in double-posting of the gap. The reliable approach is to perform difference calculation in the middle layer and skip documents where the gap is 0.
• Typical mistake 2: Hardcoding material codes in scripts. During one on-site investigation, we found that after a new warehouse was added, old materials still threw errors because code tables were scattered across multiple scripts. After centralizing them in Qeasy's mapping configuration center, the issue disappeared.
• Typical mistake 3: Missing batch field causing inventory disorder. In transfer scenarios, batch is an important inventory dimension. The source field name is batch_no while the target is lot_no; passing without mapping will fall to the default batch. We recommend listing the batch separately in the field mapping table.
• Typical mistake 4: Duplicate document numbers written. Qeasy defaults to using the source doc number as the target doc number, but Yonyou NCC enforces uniqueness on doc numbers, and duplicate triggers will throw errors. We adopted a "source doc number + date suffix" concatenation strategy to avoid this.
• Typical mistake 5: Ignoring idempotency. After an abnormal rerun, duplicate other inbound orders appeared in the target system. We recommend performing dedup checks based on the doc number before writing, or relying on Qeasy's idempotency control switch.

Applicable and Non-Applicable Scenarios

Applicable: Multi-warehouse, multi-organization retail or manufacturing enterprises with frequent transfer business, where finance needs to clearly identify "transfer differences"; hybrid architectures using Jikeyun as the front-end business system and Yonyou NCC as the back-end finance and inventory system.

Not applicable: Enterprises with single warehouses or no transfer business; scenarios where the target system is not the Yonyou NCC other inbound order interface; and lightweight integrations where difference accounting is not required and only totals matter.