Purchase Receipt Push-Down Sync in Practice: Field Mapping and Scheduling from WDT to Yongyou BIP
What This Strategy Solves
In one retailer's supply chain integration, buyers entered purchase orders in WDT, then had to re-enter receipts in Yongyou BIP for warehouse and financial posting. Double entry doubled the workload, and within three months the inventory ledger drifted away from the financial ledger because coding conventions diverged. The "purchase receipt push-down" strategy lets WDT receipts flow into Yongyou BIP automatically under a single agreed convention — the business side records once.
Data Flow and Field Mapping
The chain is: WDT (purchase receipt) → Qeasy Data Integration Platform (middleware, for cleansing and mapping) → Yongyou BIP (purchase receipt).
The middleware has three core responsibilities: centralized coding mapping, staged header/body persistence, and a dual-track of incremental and full sync. Coding mapping is the most failure-prone piece and must be extracted on its own.
Key field mapping (excerpt):
| Business meaning | WDT (source) | Middleware handling | Yongyou BIP (target) |
|---|---|---|---|
| Document number | bill_no | pass-through | billno |
| Vendor code | provider_id | via vendor mapping table | vendorcode |
| Warehouse code | warehouse_id | via warehouse mapping table | stockorgcode |
| Business date | bill_time | normalized to yyyy-MM-dd | bizdate |
| Material code | sku_id | via material mapping table | materialcode |
| Quantity | num | unit conversion if needed | qty |
| Price | price | keep 6 decimal places | price |
| Remarks | remark | truncate to 200 chars | memo |
Tip: confirm every field with the business side before go-live, especially the coding conventions for warehouses, vendors, and materials.
How to Configure on Qeasy
On the Qeasy Data Integration Platform, a typical push-down strategy is assembled from four building blocks:
- Source reader: calls WDT's purchase receipt query API, fetching incrementally by last-modified-time and document status.
- Target writer: calls Yongyou BIP's purchase receipt save API, using push-down or new-document mode.
- Mapping & transformation node: handles the cleansing and mapping described in the field table above, kept in Qeasy's data transformation node — not scattered in scripts.
- Scheduler: decides when to run, how often, and what to do on failure.
We recommend keeping coding mappings in Qeasy's master data mapping module rather than hardcoding them into every strategy. We have seen the same vendor mapping duplicated across six strategies at a customer site — changing it took half a day.
Implementation Steps
We usually split a push-down strategy like this into three phases:
Phase 1: Incremental start point. Define an initial timestamp — we recommend "00:00:00 of the go-live day". After that, Qeasy rolls forward by modification time and never looks back.
Phase 2: Full trigger. Run a one-time historical backfill before go-live to push all documents before the start point. One-shot only, never scheduled daily. A typical mistake is leaving full sync inside the daily schedule, which then re-pushes history every day.
Phase 3: Schedule cadence. Purchase receipts do not need sub-minute latency; we recommend a 10–15 minute cadence with failed jobs going into Qeasy's retry-and-alert channel. An additional overnight catch-up run helps drain any backlog caused by daytime network hiccups.
In terms of go-live ordering, first stabilize the master data syncs (shop-customer mapping, materials), then turn on the purchase receipt push-down. If master data is wrong, pushed business documents are wrong too.
Pitfalls & Lessons Learned
- Pitfall 1: Treating full sync as incremental. Forgetting the modification-time filter causes the daily job to re-push historical documents. Safer approach: run full sync as a one-shot script and force a time window on every scheduled run.
- Pitfall 2: Scattered mapping management. The same vendor mapping duplicated across multiple strategies means a business-side code change only fixes some of them. Safer approach: centralize all mappings in Qeasy's master data mapping module so every strategy reads from the same source.
- Pitfall 3: Unit and precision mismatch. WDT uses "pieces" while Yongyou BIP uses "base units"; without conversion, quantities get multiplied by 12. Safer approach: do explicit unit conversion in the middleware and standardize to 6 decimal places.
- Pitfall 4: Silent failures. Occasional API timeouts fail quietly and the business only notices the next morning. Safer approach: pair Qeasy's retry mechanism with enterprise WeChat alerts.
- Pitfall 5: Ignoring reversal and red-letter scenarios. Only forward receipts are considered, not returns. Safer approach: pull cancellation flags and original document numbers in the source reader, then branch by business type on the target side.
When It Applies — and When It Doesn't
Applies: Stable document structure, clear field conventions, upstream being an e-commerce ERP like WDT and downstream being Yongyou BIP for financial posting — a typical supply chain consolidation scenario.
Does not apply: Master data coding conventions not yet aligned, business processes still changing frequently, or real-time requirements stricter than one minute (in which case a message-queue based approach is preferable).