Qeasy Cloud
Get Started

Wangdiantong and Kingdee Cloud Cosmos Supply Chain Integration: Architecture and Implementation of 35 Strategies

· 冯潇· Integration Solutions· 8 views· 6 min read
WDTKingdee Cloud供应链集成Order SyncInventory Sync主数据映射

Scenario and Value

In a typical e-commerce retail business, the OMS/WMS (represented by Wangdiantong) and the backend ERP (represented by Kingdee Cloud Cosmos) serve different roles. Wangdiantong handles order intake, shipping, inventory execution, and store management, while Kingdee Cloud Cosmos handles financial accounting, procurement management, and organization-based inventory and supply chain document flows. When data exchange between the two systems relies on manual entry or scattered scripts, problems such as document latency, inconsistent coding, inventory drift, and reconciliation difficulties inevitably arise.

This solution designs 35 collaborative data synchronization strategies for supply chain integration, covering sales outbound and returns, purchase inbound and returns, pre-inbound, inventory transfers, inventory surplus and loss, other inbound/outbound documents, return-and-refund-without-return scenarios, and master data synchronization. Its core value is to converge cross-system document flows into a set of observable, schedulable, and retryable integration processes, so that order execution on the e-commerce side stays consistent with financial and supply chain documents on the ERP side.

Integration Architecture and Data Flows

The overall architecture follows a bidirectional synchronization plus master data lookup pattern. The integration platform acts as the data hub with three types of responsibilities:

  • A_TO_B (Wangdiantong → Kingdee), 12 strategies: Push execution-oriented documents generated on the e-commerce side to the ERP, including ToB/ToC sales outbound, sales returns, return-and-refund-without-return, purchase inbound, purchase return material, pre-inbound, inventory surplus, inventory loss, other outbound, other inbound, transfer outbound, and transfer inbound.
  • B_TO_A (Kingdee → Wangdiantong), 6 strategies: Push planning-oriented documents from the ERP down to the e-commerce side, including material receipt notice → purchase order, delivery notice → original order, and transfer application → transfer order.
  • QUERY_ONLY, 16 strategies: Including KD1 to KD5, Q1, Q7, BNS distributor-customer correspondence, and Wangdiantong store queries, used only for data preloading and cross-system lookups without writing to the target system.
  • INTERNAL, 1 strategy: Clean up historical data older than two months.

Execution dependencies follow the order of "master data first → planning dispatch → execution feedback": master data such as KD3 Kingdee warehouses, BNS distributor-customer correspondence, and Wangdiantong stores must be preloaded first to support the encoding mapping in subsequent documents. Kingdee transfer applications must first be dispatched to Wangdiantong to generate transfer orders, after which the transfer outbound and transfer inbound on the Wangdiantong side are written back to Kingdee in a step-by-step manner. Material receipt notices must first be converted into Wangdiantong purchase orders so that subsequent purchase inbound documents can be matched against those orders.

Interface List

Source PlatformTarget PlatformData ObjectSync Direction
WangdiantongKingdee Cloud CosmosToB Sales Outbound / ToC Sales OutboundA_TO_B
WangdiantongKingdee Cloud CosmosToB Sales Return / ToC Sales ReturnA_TO_B
WangdiantongKingdee Cloud CosmosReturn and Refund Without ReturnA_TO_B
WangdiantongKingdee Cloud CosmosPurchase Inbound / Purchase Return MaterialA_TO_B
WangdiantongKingdee Cloud CosmosPre-InboundA_TO_B
WangdiantongKingdee Cloud CosmosInventory Surplus / Loss / Other Outbound / Other InboundA_TO_B
WangdiantongKingdee Cloud CosmosTransfer Outbound / Transfer Inbound (step-by-step transfer)A_TO_B
Kingdee Cloud CosmosWangdiantongMaterial Receipt Notice → Purchase OrderB_TO_A
Kingdee Cloud CosmosWangdiantongDelivery Notice → Original OrderB_TO_A
Kingdee Cloud CosmosWangdiantongTransfer Application → Transfer OrderB_TO_A
Kingdee Cloud CosmosIntegration PlatformWarehouses, customers, suppliers, materials, inventory, auxiliary data, organizations, and other master dataQUERY_ONLY
WangdiantongIntegration PlatformStores, original orders, order queriesQUERY_ONLY

Implementation Points

Encoding mapping is the first task in implementation. Materials, customers, warehouses, and suppliers each have independent encoding systems in the two systems, and cross-system document synchronization must rely on mapping tables. Materials are mapped from Wangdiantong's spec_no/goods_no to Kingdee's FMaterialId (including _FNumber), warehouses from warehouse_no to FStockId.FNumber, suppliers from provider_no to FSupplierId.FNumber, and customers in ToB/ToC scenarios also need secondary mapping through BNS distributor-customer correspondence. Mapping fields such as F_KD_WDTSTOCK must be maintained in advance as custom fields on the Kingdee side.

Field mapping for key documents needs item-by-item verification. Taking ToB/ToC sales outbound as an example: order_no → FBillNo, consign_time → FDate, goods_count → FQty, sell_price → FPrice, shop_no → FStockOrgId.FNumber. Purchase inbound needs to use outer_no to cross-reference the Kingdee material receipt notice to maintain document association. Inventory surplus and loss only require four core fields: document number, warehouse, material, and quantity. Transfer documents need to carry both the source warehouse and target warehouse encoding mappings.

Incremental and full synchronization modes should run in parallel. Master data query strategies typically achieve incremental synchronization based on FModifyDate>='{{LAST_SYNC_TIME}}'. Execution-oriented documents need to switch to full mode during initial go-live or data backfill, then return to incremental mode after completion. It is recommended to provide a mode toggle at the scheduling layer to avoid document omissions caused by incomplete historical data synchronization during the initial go-live period.

Exception retry and alerting must be paired. Common reasons for document write failures include missing encoding mappings, empty required fields, insufficient inventory, and document status validation failures. It is recommended to configure a limited number of automatic retries at the strategy layer (for example, 3 retries with exponential backoff). After exceeding the threshold, the document enters a manual processing queue, and error notifications are pushed via enterprise WeChat or DingTalk.

Best Practices

  • Tiered scheduling frequencies: Master data queries every 15 to 30 minutes; sales outbound and returns every 10 to 15 minutes; delivery notice → original order every 15 minutes; purchase inbound and return material every 20 minutes; pre-inbound every 30 minutes; inventory surplus and loss every 30 minutes; transfers every 20 minutes; return-and-refund-without-return 1 to 2 times per day is sufficient; query strategies on demand or every 2 hours; historical data cleanup once per day. High-frequency strategies prioritize real-time performance, while low-frequency strategies avoid putting query pressure on the source systems.
  • Master data strategies should go live before business strategies: Query strategies such as KD3 Kingdee warehouses, BNS distributor customers, and Wangdiantong stores must run stably before sales, procurement, and transfer strategies. Otherwise, business documents will fail due to missing mappings.
  • Use step-by-step writeback for transfers: Kingdee transfer applications are first dispatched to Wangdiantong to generate transfer orders. After Wangdiantong completes the actual transfer, the transfer outbound and transfer inbound are written back to Kingdee separately, avoiding document status confusion on the Kingdee side caused by a single writeback.
  • Set a retention window for historical data cleanup: Strategy 35's cleanup policy recommends a two-month retention window, which both controls the data volume in the integration platform and leaves an investigation period in case of reconciliation issues.
  • Complete mapping table integrity and consistency checks before go-live: This includes full comparison of warehouses, materials, suppliers, and customers. Any missing or conflicting entries need to be supplemented in both systems in advance before switching to incremental synchronization mode.
  • Overall integration workflow document: this article
  • Complete solution design: detailed design document with per-strategy field mapping, exception handling, and scheduling recommendations

Interface Manual Excerpts

Purchase Return Material Application (PUR_MRAPP)

Used to pre-apply and record return material information including materials, quantities, return types, return modes, and replenishment/deduction details before formal purchase return material outbound processing. The form ID is PUR_MRAPP, queried by page using the executeBillQuery WebAPI. The Target is configured as a write-empty operation, indicating a pure query strategy. Key fields include FBillNo (document number), FDocumentStatus (document status), FBusinessType (business type: standard procurement / outsourced / asset procurement / VMI), FRMTYPE (return type: inspection return / inventory return), FRMMODE (return mode: return-and-replenish / return-and-deduct), FREPLENISHMODE (replenishment mode), and FConfirmStatus (confirmation status).

Kingdee Warehouse (BD_STOCK)

Used to establish encoding mapping between Wangdiantong warehouses and Kingdee warehouses, serving as the foundation for warehouse field mapping in business documents such as inbound/outbound and transfer documents. The form ID is BD_STOCK, queried via executeBillQuery. In addition to the basic fields FStockId, FNumber, FName, FGroup, and FUseOrgId, the core mapping field F_KD_WDTSTOCK (Wangdiantong warehouse encoding) is used to establish a one-to-one mapping between Kingdee warehouses and Wangdiantong warehouses, and is the key mapping field for warehouse master data in this solution.

Delivery Notice (SAL_DELIVERYNOTICE)

Used for the correlation and traceability between sales orders and delivery notices, serving as the core data source for delivery status pre-synchronization. The form ID is SAL_DELIVERYNOTICE, queried with incremental filtering by approval date and other conditions via executeBillQuery. In addition to basic fields, the cross-system mapping field F_KD_SubOrderNo (Wangdiantong sub-order number) is used to establish precise correlation between Wangdiantong sub-orders and Kingdee delivery notice details.

  • Complete solution design: detailed design document with per-strategy field mapping, exception handling, and scheduling recommendations
Original content. Please credit the source when reposting: https://www.qeasy.cloud/insights/solutions/sol-wdt-kingdee-cloud-5343

Comments