Interface Field Manual: Weaver OA-E9Http & Kingdee Cloud Skylink Supply Chain Integration
What This Interface Solves
In supply chain digitization scenarios for manufacturing and retail, business documents must flow bidirectionally between OA approval workflows and ERP. Weaver OA-E9Http serves as the approval entry point, while Kingdee Cloud Skylink acts as the financial and supply chain data backbone. This manual focuses on the interface field implementation details for their integration, covering core documents including materials, customers, suppliers, expense items, purchase orders, sales orders, delivery notices, and payment orders, so it can help engineers avoid common pitfalls around code mapping, workflow version differences, and incremental synchronization.
Interface Capability Overview
Authentication: Weaver OA-E9Http uses HTTP interface with Token/Session authentication; Kingdee Cloud Skylink uses OAuth2.0 with AppSecret signature, typically carried in request headers via X-KDApi-AuthType and AccessToken.
Request Structure: The Kingdee side relies on two core methods, executeBillQuery (query) and Save (save), with FormId identifying document types (e.g., BD_MATERIAL, PUR_PurchaseOrder, SAL_SaleOrder, AP_OtherPayable). The Weaver side initiates/rewrites processes based on process instance ID and detail row JSON structure.
Response Structure: Kingdee returns standard JSON with key fields including Result.ResultStatus, Result.FID, Result.FBillNo, and Result.Errors; Weaver returns the process instance ID and approval node status.
Pagination/Incremental Mode: Supports incremental queries based on FModifyDate, as well as full validation during initial deployment. Query strategies are recommended every 30 minutes, business document strategies every 10 minutes, and system maintenance (queue cleanup) once daily.
Typical Field Mapping
| Field Name | Type | Meaning | Implementation Notes |
|---|---|---|---|
| FNumber | String | Kingdee material/customer/supplier code | Basis for primary key mapping, unique across systems |
| FName | String | Name | Display field on OA side |
| FSpecification | String | Specification model | Required for material scenarios |
| FMaterialGroup.FNumber | String | Material group code | Multi-level groups need to be expanded |
| FBaseUnitId.FNumber | String | Base unit of measure | Affects purchase quantity calculation |
| FModifyDate | Time | Last modification time | Time anchor for incremental sync |
| FBillNo | String | Document number | Usually generated from process number or Kingdee coding rule |
| FPayableAmount/FPayAmount | Number | Payable/payment amount | Requires summarizing detail row amounts |
| FSupplierId | String | Business partner | Uses COLLECTION type to look up Kingdee ID via mapping table |
| FExpenseId | String | Expense item | Depends on expense item mapping table |
| F_WMMX_OAId | String | Weaver echoed internal code | Used for cross-system code echo |
| FDate | Date | Business date | Maps from OA application date |
| FNote | String | Remarks | Process remarks passed through |
How to Configure on Qeasy
On the Qeasy Data Integration Platform, this set of interfaces is typically configured as follows: the platform comes with pre-built adapters for both Kingdee Cloud Skylink and Weaver OA-E9Http HTTP, allowing direct document mounting by selecting FormId; the field mapper in Qeasy automatically recognizes standard fields such as FNumber and FName and generates DIRECT mappings. For fields like FSupplierId and FExpenseId that require code conversion, a one-click toggle to COLLECTION mapping can be made and linked to the built-in mapping table; the scheduler in Qeasy supports setting different frequencies by strategy type, the exception handling module provides retry and dead-letter queue configuration, and a single failure will not block subsequent data flow.
Cross-Project Implementation Points
- Master Data First: Materials, customers, suppliers, expense items, organizations, employees, users, and other master data must be synchronized before business documents, otherwise downstream strategies will fail due to missing mappings.
- FD003 Multi-Version Adaptation: Non-production payment applications are implemented as separate strategies per process version (393/422/443/481/484/499/554/NEW), with slightly different field structures that require version-specific mapping configuration.
- SD001 Supplier Hidden Number: When production order approval generates purchase orders, the supplier field on the OA side needs to be changed to a hidden number to prevent users from selecting the wrong supplier.
- Bidirectional Code Echo: Materials, customers, suppliers, and expense items all need bidirectional mapping tables; after the Weaver side modifies the ID, it echoes back to Kingdee custom fields (such as F_WMMX_OAId).
- Dependency Chain Management: Kingdee's submit purchase order depends on the FID returned by the upstream Save; OA approval echo to ERP depends on the sales order/delivery notice having been successfully pushed to the OA process.
- Full Validation Fallback: Master data is recommended for full validation once daily to prevent missed incremental records; sales order push requires querying the document first then the attachment to ensure attachments are transmitted together.
Pitfall Retrospective
- Pitfall 1: Incremental sync missed records. Due to
FModifyDatetimezone or precision issues, cross-day data was missed; the safe approach is daily full validation plus incremental fallback. - Pitfall 2: Field changes after FD003 process version upgrade. When a customer upgraded the process version, custom fields were added and the old strategy reported errors directly; the lesson is that every process version change requires re-checking the field mapping table.
- Pitfall 3: Downstream did not receive context after Kingdee Save returned FID. Kingdee's submit purchase order depends on the upstream Save FID; if context passing fails, subsequent audit strategies cannot find the document.
- Pitfall 4: The supplier field was not changed to a hidden number, causing users to select the wrong supplier and generate incorrect purchase orders.
- Pitfall 5: Sales order attachments were not queried before process push, resulting in OA not receiving attachments and approvers being unable to verify.
When to Use
Suitable for manufacturing and retail scenarios where OA approval workflows are deeply coupled with ERP supply chains, especially for enterprises requiring closed-loop flow of expense reimbursement, payment applications, production order approval, and sales order approval between two systems. Boundary: not applicable for pure document printing or lightweight data reporting scenarios, nor for pure internal Kingdee module-to-module integration.