Inventory Sync in Practice: Pushing KinKingdom Other-Inbound Documents into WangDianTong
What This Strategy Solves
In the supply chain of a retail enterprise, financial inventory accounting is anchored in KinKingdom, while physical inbound and outbound execution is driven by WangDianTong. The "Other-Inbound" document typically carries scenarios such as inventory surplus, adjustments, and material returns. If both sides enter data independently, the inventory variance between books and reality can widen within three months. This strategy pushes KinKingdom's Other-Inbound documents toward WangDianTong's "Internal Warehouse Receipt" as a single closed-loop inventory sync path.
Data Flow and Field Mapping
Data flow: KinKingdom (Other-Inbound document) → Qeasy data integration platform (intermediate transformation and mapping) → WangDianTong (Internal Warehouse Receipt). The middle layer handles code mapping, field renaming, batch/unit conversion, and header-body splitting.
Key field mapping:
| Business Semantic | KinKingdom Source Field | Qeasy Middle Layer | WangDianTong Target Field |
|---|---|---|---|
| Document Number | FBillNo | bill_no (prefix stripped) | outer_code |
| Document Date | FDate | biz_date (yyyyMMdd) | order_time |
| Warehouse | FStockOrgId/FStockId | wh_code (org-warehouse mapping) | warehouse_no |
| Business Type | FBizTypeId | biz_type (enum normalization) | io_type |
| SKU Code | FMaterialId | sku_code (material master mapping) | spec_code |
| Quantity | FBaseQty | qty (precision normalization) | num |
| Remark | FNote | remark | remark |
Code mapping is maintained centrally in Qeasy's mapping tables. Organization, SKU, and warehouse dictionaries are best kept as hot-updatable mapping resources rather than hardcoded into scripts.
How to Configure on Qeasy
When configuring a single strategy on the Qeasy data integration platform, the typical essentials are:
- Source side: Select KinKingdom's Other-Inbound view/form, enable incremental window filtering (by FModifyDate), and check the approved-status filter to only pick up approved documents.
- Middle layer: Use Qeasy's field mapping component to configure one-to-one header-body mapping. Normalize FBizTypeId into the io_type recognized by WangDianTong via enum mapping. Route organization and warehouse through centralized mapping tables.
- Target side: Write into WangDianTong's "Internal Warehouse Receipt" interface, using outer_code as the idempotency key (WangDianTong typically rejects duplicates of outer_code or reports it as existing).
- Exception handling: Configure an error queue and retry policy on Qeasy. For mapping-missing errors like "warehouse not found" or "SKU master missing," it is recommended to route them into a manual repair queue rather than retrying indefinitely.
Implementation Steps
- Incremental start point confirmation: Use the project go-live date as the baseline. Take the approved Other-Inbound documents from the past 7 days in KinKingdom as the initial incremental package to avoid a one-time flood of historical data hitting the target system.
- Full-volume trigger (optional): Before go-live, perform a one-time backfill of the past 3 months of historical data as a full-volume batch, then immediately switch to incremental scheduling. Dual-track operation of incremental and full-volume is a common steady-state pattern among Qeasy customers.
- Scheduling frequency: Inventory documents are sensitive to real-time performance. It is recommended to trigger an incremental poll every 5-10 minutes. If the link load is high, extend to 15 minutes, but assess the tolerable inventory variance.
- Post-go-live inspection: For the first two weeks, compare document counts and amounts between the two sides daily. Investigate immediately if orphan documents or write-back failures are discovered.
Pitfall Retrospective
- Typical mistake 1: Forgetting to filter approved status. Pushing draft-state documents through causes WangDianTong to create orders that cannot be unapproved and cleaned up, requiring manual reversal. The safe approach: the source side must include the approved condition.
- Typical mistake 2: outer_code is not unique. Repeated imports of KinKingdom document numbers cause WangDianTong to reject orders. It is recommended to add a composite idempotency key of source system document number + document date in Qeasy's middle layer.
- Typical mistake 3: Inconsistent body units. The KinKingdom base unit and WangDianTong sales unit are not necessarily the same. Qeasy must explicitly perform a unit conversion and write it into a field, instead of relying on the target system's automatic conversion.
- Typical mistake 4: Mapping tables not updated after org revision. After a warehouse organization change, old mappings continue to hit, causing inbound to land in the wrong warehouse. Mapping tables should carry version cues. Qeasy customers commonly use "effective date + expiry date" to manage multiple versions.
- Typical mistake 5: Reverse reversal not configured. Once KinKingdom reverses an Other-Inbound document with a red-letter entry, WangDianTong does not automatically follow. This strategy only covers forward transfer-in. Reversals are best handled as a separate strategy rather than adding branch logic into the same link.
Applicable and Non-Applicable Scenarios
Applicable: Internal warehouse receipt, transfer-in, and inventory surplus entry under single or multi-organization scenarios; incremental real-time requirements within 15 minutes. Not applicable: Purchase inbound (use the purchasing link), subcontracting inbound (different business flow), and scenarios requiring two-way write-back of inventory balances (requires a separate inventory balance strategy).