Integration Solution Between Sihua Smart Manufacturing MES and Kingdee Cloud Cosmic: 14 Strategies Linking Master Data to Production and Inventory

Scenario and Value

In smart manufacturing scenarios where MES and ERP must collaborate, the Manufacturing Execution System records shop-floor actions such as routing, material issue, warehousing, quality inspection, and subcontracting, while the ERP carries the books for finance, supply chain, and planning. Without integration between the two systems, business data is fragmented between shop floor and finance: work orders cannot feed back into costing, subcontract processing lacks voucher basis, inspection results must be re-entered manually, and inventory discrepancies are hard to trace.

This solution targets supply chain integration between the Web-based MES and Kingdee Cloud Cosmic (ERP for finance and supply chain), and provides an overall workflow composed of 14 integration strategies covering master data through production and inventory. The core value is: taking the routing as the main thread, it maps MES routing masters, semi-finished product flow, subcontracting requests and material issues, inspection results, and production reports onto the corresponding virtual materials, virtual warehouses, purchase requisitions, production orders, and inbound/outbound documents in Kingdee Cloud Cosmic, forming a traceable and cost-accountable unified supply chain view.

Integration Architecture and Data Flow

The overall architecture is a one-way data channel of "Source MES → Integration Middle Layer → Target ERP", supplemented by a query channel of "Source MES → Integration Platform Cache". The integration middle layer is responsible for scheduling, field mapping, code conversion, incremental/full control, and credential management. On the Kingdee Cloud Cosmic side, pre-configured virtual materials and virtual warehouses are used to receive routing-level semi-finished product flow.

According to the dependency relationships, the 14 strategies are divided into five phases that must be enabled in order:

• Phase 1: Master Data + Queries. MES routing masters are synchronized into virtual materials in BD_MATERIAL; pending purchase orders and routing information are pulled as QUERY_ONLY into the integration platform for cross-system lookup. This phase has no prerequisites, can run in parallel, and is recommended at a 30-minute interval.
• Phase 2: Semi-finished Product Synchronization. MES semi-finished product issues and warehousing are written into Other Outbound and Other Inbound documents in Kingdee, hitting pre-configured virtual warehouses to enable semi-finished product flow between routings. This depends on virtual materials and virtual warehouses from Phase 1, recommended at a 15-minute interval.
• Phase 3: Procurement Business Synchronization. MES routing subcontracting requests are mapped to PUR_ReqBill expense purchase requisitions; MES inspection documents, when "routing is empty", are written into purchase warehousing; MES production warehousing requests are used as Kingdee production reports associated with production orders. This depends on material, routing, and production order mapping, recommended at a 15-minute interval.
• Phase 4: Production Business Synchronization. MES routing subcontract material issues (raw materials) are mapped to Kingdee production material issue; MES internal production material issue, supplement, and return are written into the corresponding Kingdee documents, all associated with production orders. Recommended at a 15-minute interval.
• Phase 5: Inventory Business Synchronization. MES routing subcontract material issues (semi-finished products) are written into Other Outbound; MES inspections with "routing not empty" are written into Other Inbound. Recommended at a 15-minute interval.

By business domain, the data flow can be grouped into four categories: master data flow (routing masters to virtual materials, semi-finished product issue/warehousing), procurement business flow (subcontracting request to expense purchase requisition, inspection to purchase warehousing, production warehousing request to production report), production business flow (subcontract raw material issue to production material issue, internal production issue/supplement/return), inventory business flow (subcontract semi-finished product issue to Other Outbound, inter-routing inspection to Other Inbound), plus a query flow for business cross-lookup.

Interface List

Implementation Points

First, code mapping must be maintained up front. Materials, routings, warehouses, units, production orders, and suppliers are primary keys for cross-system identification. It is recommended to build independent mapping tables in the integration layer rather than performing conversion in real time at document write time.

Second, two types of basic data must be pre-configured on the Kingdee side: "virtual materials" that correspond one-to-one with MES routings, used for routing costing and production report association; and "virtual warehouses" used to receive routing-level semi-finished product issues and warehousing.

Third, both incremental and full synchronization modes must coexist. It is recommended to use time fields such as bill_date, apply_date, issue_date, inspect_date, modify_time, and create_time as incremental pull conditions; for initial go-live or data repair, remove the incremental conditions and trigger a full synchronization.

Fourth, there is a "splitting" logic for inspection and subcontract material issue. MES inspection documents must be split into purchase warehousing or Other Inbound based on whether "routing is empty"; MES routing subcontract material issue must be split into production material issue or Other Outbound based on "raw material / semi-finished product". This splitting rule should be embedded in the transformation component of the middle layer to avoid mismatched document types downstream.

Fifth, production order association is a common prerequisite for production domain strategies. MES work order number (work_order_no) must be mapped to Kingdee production order FBillNo; production reports, material issue, supplement, and return must all carry this association field, otherwise the Kingdee side cannot locate the cost object.

Sixth, credentials and sensitive fields, following private deployment conventions, should be stored in environment variables or a key management service, and not written into strategy configuration.

Best Practices

• Phased rollout: Enable strategies strictly in the order of Phase 1 to Phase 5. Observe the synchronization results for some time in each phase before opening the next phase, to avoid large-scale downstream document failures caused by missing master data.
• Decouple query strategies: Pending purchase orders and routing information are pulled as QUERY_ONLY only, written into the integration platform cache for cross-system lookup, and do not enter the Kingdee document flow, to avoid polluting ERP books.
• Retry and alerting in parallel: Phases 2 through 5 are all high-frequency strategies at 15-minute intervals. It is recommended to configure exponential backoff retry and set alerting thresholds for consecutive failures.
• Trace full synchronization: Each manual or scheduled full synchronization should record execution time and affected record count, to facilitate traceability of historical data repair actions.
• Pre-check MES document status: An incomplete status machine on the source side will be directly transmitted to the target side. It is recommended to add status validation in the middle layer and synchronize only finalized or effective documents.