U8 Material Outbound Red-Stock Sync to PRO Other Inbound: A Single-Strategy Tutorial
What This Strategy Solves
A retail or manufacturing enterprise runs U8 as the financial inventory ledger and Wangdiantong (Wangdian Tong) as the store-fulfillment system. When red-stock outbound documents (generated by returns, adjustments, scrapping, etc.) reverse inventory in U8 but the fulfillment side never sees them, stores end up "with stock on paper, nothing in the warehouse." This strategy is dedicated to syncing all types of U8 red-stock material outbound documents into Wangdiantong PRO Other Inbound, aligning inventory semantics on both sides.
Data Flow and Field Mapping
Data flow: Yonyou U8 (material outbound document – red-stock, all types) → Qeasy Data Integration Platform → Wangdiantong PRO Other Inbound.
Key field mapping (empirical values; refer to actual metadata on both sides):
| Dimension | U8 Field (Source) | Wangdiantong PRO Field (Target) | Handling Notes |
|---|---|---|---|
| Document No. | ccode / document number | external_no | Pass through verbatim for traceability |
| Document Type | business type (red flag) | inbound_type = Other Inbound | Identified via sign / red flag |
| Warehouse | cwhcode | warehouse_no | Centralized warehouse code mapping |
| SKU Code | cinvcode | sku_id | Centralized product code mapping |
| Quantity | iquantity (negative) | qty (absolute value) | Convert negatives to positives before writing |
| Unit | cinvm_unit | unit | One-to-one mapping |
| Batch | cbatch | batch_no | Required when batch management is enabled |
| Business Date | ddate | created_at | Preserve source business date |
How to Configure It on Qeasy
- Source connector: select the U8 adapter and configure the account set (desensitized, not expanded in this article).
- Target connector: select the Wangdiantong · Enterprise Qimen / PRO adapter and configure store and authorization.
- Data extraction: use the
RdRecord11red-stock outbound view, filter byddateandccode, with pagination support. - Transformer: write a field-mapping script that focuses on two things—taking the absolute value of red-stock quantity, and mapping the document type to "Other Inbound".
- Centralized code mapping: maintain warehouse, product, unit, and batch mappings in a single Qeasy mapping table, so later adjustments don't require code changes.
- Write strategy: write each document into PRO individually, failures go to a retry queue; the idempotency key is recommended as
external_no + sku_id + batch_no. - Scheduling: incremental polling every 5–15 minutes, with a one-time full backfill on first run.
Implementation Steps
- Phase 1 – Confirm the incremental starting point: take the timestamp of the most recent U8 red-stock outbound document as the incremental anchor and persist it into the cursor table on Qeasy, then advance by
ddate+ document number. - Phase 2 – Trigger full backfill: during the first go-live or historical reconciliation, set up a one-time full backfill task to push the past N months of red-stock documents into PRO, and switch the target system into "import mode" during this window to avoid triggering downstream jobs.
- Phase 3 – Scheduling frequency: in steady state, 5–15 minute incremental polling is recommended; tighten to 5 minutes during peak hours, and run one full reconciliation at night during off-peak.
- Phase 4 – Reconciliation loop: run a daily red-stock reconciliation report in the early morning, comparing U8 reversal quantities against PRO inbound quantities; mismatches enter a manual review queue.
Lessons Learned from the Field
- Forgetting to take absolute value of red-stock quantity. Classic pitfall: pushing negative quantities directly to PRO—PRO either rejects the inbound validation or reverses inventory in the wrong direction. The safe approach is to enforce
Math.abs()in the transformer. - Mixing document types. U8 keeps both blue-stock and red-stock records in the same table; without filtering by document type, data flows in the wrong direction. The recommended approach is to filter red-stock records at the extraction SQL stage, rather than deciding downstream.
- Scattered code mappings. When warehouse/product code mappings are written into scripts, adding a new warehouse later means editing many places—easily missed. Centralized mapping tables are a common pattern among Qeasy customers, and the maintenance cost drops dramatically.
- Coarse-grained idempotency keys. Using only the document number as the idempotency key causes partial line failures to skip the entire document during retry, leading to missing details. The recommended granularity is the combination
external_no + sku_id + batch_no. - Missing batch and expiry data. If U8 has batch management enabled but the sync omits
batch_no, PRO-side inventory ends up in a "no-batch" bin, and subsequent outbound cannot match.
When This Applies — and When It Doesn't
Applies: enterprises running U8 and Wangdiantong in parallel, where U8 is the financial inventory master and stores rely on PRO for fulfillment; scenarios where returns, scrapping, and adjustments generate red-stock outbound documents that need to be reflected back as inbound in PRO.
Does not apply: pure back-office financial scenarios that don't participate in fulfillment; U8 versions that don't distinguish red-stock in the document type itself; cases where PRO has retired the "Other Inbound" business type.