Syncing Kingdee Cloud Skyvia Material Master Data to Wangdiantong Product Archive: A Single-Strategy Tutorial
What This Strategy Solves
In one retail customer scenario, the ERP runs on Kingdee Cloud Skyvia while store POS and e-commerce fulfillment run on Wangdiantong. Material master data was being maintained on both sides, and after three months the codes, names, and units no longer matched. This strategy addresses that by making Kingdee the single source of truth and pushing material master data one-way into Wangdiantong's product archive.
On-site, we used the Qeasy (Qingyi Cloud Data Integration Platform) to host this as a single sync strategy in a source → middleware → target three-stage flow. Adding new material fields later only requires minor adjustments.
Data Flow and Field Mapping
The flow is unidirectional: Kingdee Cloud Skyvia (source) → Qeasy middleware (mapping, cleansing, versioning) → Wangdiantong (target, writes into product archive).
Key field mapping (only the tricky ones):
| Business meaning | Kingdee (source) | Qeasy middleware | Wangdiantong (target) | Notes |
|---|---|---|---|---|
| Material code | FNumber | material_code | Product code | Unique key, centralized encoding mapping |
| Material name | FName | material_name | Product name | Name changes need versioning, not overwrite |
| Base unit | FBaseUnit | base_unit_id | Base unit | Unit code conversion |
| Specification | FModel | spec | Specification | Text truncation |
| Barcode | FBarCode (sub-table) | barcode_list | Product barcode (multi-value) | Header/body handled in phases |
| Default warehouse | FDefaultLoc | default_stock | Default warehouse code | Warehouse code mapping |
One common pattern with Qeasy is to extract "encoding mapping" to the platform layer so that when either side adjusts its coding system, you only change it in one place.
How to Configure It in Qeasy
In Qeasy, this strategy exists as a standalone task under the "Material Master Data Sync" business domain. Key configuration points:
- Source connection: Select Kingdee Cloud Skyvia and pull material master data via its API; use the "last modified time" field as the incremental cursor to avoid full-table scans.
- Middleware processing: In Qeasy's mapping canvas, first perform "encoding standardization"—converge different source codes into an internal standard—then do field mapping.
- Target write: Write into Wangdiantong's product archive using an upsert logic: "update if exists by code, insert if not."
- Dependencies and sequence: As a master data sync, this strategy does not depend on other business documents, but it is depended upon by downstream strategies like sales outbound orders and sales return orders, so its sequence sits at the front of segment A.
- Failure handling: Qeasy drops failed records into an "exception pool" by default; on-site we typically require 30 days of traceability.
Implementation Steps
We recommend a three-phase rollout rather than a big-bang cutover:
Phase 1: Full-load trigger (on go-live day)
- Manually trigger a "full sync" in Qeasy to push all active materials from Kingdee to Wangdiantong.
- The goal is to align the baseline on both sides, not to slowly chase parity through incrementals.
- Immediately after full sync completes, freeze manual material creation on the Wangdiantong side to prevent data backflow.
Phase 2: Incremental starting point (00:00 the day after full sync)
- In Qeasy, set the incremental cursor to "Kingdee material last modified time ≥ full sync completion time."
- We usually recommend a 15-minute scheduling interval—near real-time without overwhelming the source API.
- During off-peak hours, run an additional full reconciliation to catch any omissions.
Phase 3: Steady-state operation (2 weeks after go-live)
- Move scheduling to normal business days, with one "full validation" run at night (compare only, do not write) to detect drift.
- Configure alerts on the Qeasy monitoring dashboard: incremental failure rate > 1% or exception pool > 50 records triggers immediate notification.
Another common Qeasy customer pattern is "incremental plus full-load dual track": incrementals during the day, full reconciliation at night—real-time responsiveness with consistency safety net.
Pitfall Retrospective
1. Do not stuff multi-value fields like barcodes into the main table. In one project, we concatenated barcodes into the product archive's remarks field, and stores couldn't scan properly afterward. The safe approach is to split barcodes into a sub-table in the Qeasy middleware, handle header and body in phases—write the main table first, then the sub-table, rolling back the main table on failure.
2. Do not directly overwrite material name changes. Many legacy products in Wangdiantong are referenced by historical orders; overwriting names directly causes historical documents to display incorrectly. We later added a version number in the middleware: names are appended, not overwritten, and historical orders see the snapshot at the time of placement.
3. Do not scatter encoding mapping across SQL. Early on we had hard-coded conversions spread across multiple strategies; once the counterparty upgraded its coding system, it took a week to fix. After centralizing, one change propagates everywhere.
4. Incremental cursor rollback causes data loss. Once the source system performed a data fix and "last modified time" was rolled back to an earlier point, changes during that window were not pushed. The safe approach is to make the cursor "monotonically increasing" in Qeasy and never accept rollbacks.
5. Do not enable high-frequency scheduling on day one. Day one has large data volumes and many exceptions; a 15-minute interval will slow the source system. For the first three days, use a 1-hour interval, then ramp up once stable.
Applicable and Non-Applicable Scenarios
Applicable: Retail, e-commerce, and distribution enterprises where Kingdee Cloud Skyvia is the ERP master data source and Wangdiantong is the store/e-commerce execution system; material change frequency is manageable (less than several thousand per day); minute-level latency is acceptable.
Not applicable: Scenarios requiring bidirectional sync where Wangdiantong also generates materials (e.g., store-defined products); second-level real-time requirements; or transitional periods where Kingdee and Wangdiantong coding systems have not yet been unified.