Kingdee Cloud Xingkong and Wangdiantong·Enterprise Qimen Document Interface Docking
Data source platform: Wangdiantong Enterprise Qimen
Huice (formerly Wangdiantong) is a technology-driven smart retail service provider. Based on cloud computing PaaS and SaaS models, it uses integrated smart retail solutions to help retail companies upgrade digitally and intelligently to achieve large-scale development of enterprises.
Target system: Kingdee Cloud and Starry Sky
Kingdee K/3Cloud combines today's advanced management theories and best application practices of hundreds of thousands of domestic customers to provide a general ERP service platform for business divisions, multi-sites, multi-factories and other operation coordination and control enterprises and group companies. Collaborative applications supported by K/3Cloud include but are not limited to: centralized/decentralized sales, centralized/decentralized procurement, B2B e-commerce management, B2C e-commerce center, supplier collaboration, multi-factory planning, cross-factory picking, cross-factory processing, factory Interim transfer, internal transaction and settlement, group financial management, amoeba operation, etc.
Multi-system interconnection scheme configuration
Create an integration solution through the easy cloud system data integration platform, and then select the corresponding source platform in the data source platform as: Wangdiantong·Enterprise Qimen, and select the corresponding connector (about Wangdiantong·Enterprise Qimen How to configure the interface connector can be found in the Qeasy cloud system data integration communication community bbs.qeasy.cloud). Select the corresponding query storage order management interface as the data docking source. Then configure the target system as Kingdee Cloud Star by writing to the target platform, and select the corresponding connector. Selecting other corresponding new interfaces for warehousing as the data writing action can complete the first step of data docking configuration; break the cross-system connection and make data easily interoperable become a reality.
Wangdiantong·Enterprise Qimen interface details
- API：wdt.stockin.order.query
- NAME: query storage order management
- METHOD：POST
request parameters
| interface field | Field Name | default value | describe |
|---|---|---|---|
| start_time | Starting time | { {LAST_SYNC_TIME datetime}} | Acquire data according to the last modification time increment, start_time as the start time, format: yyyy-MM-dd HH:mm:ss |
| end_time | End Time | { {CURRENT_TIME datetime}} | Acquire data according to the last modification time increment, end_time as the end time, format: yyyy-MM-dd HH:mm:ss |
| order_type | Source document category | 6 | Source document category 1 Purchase storage, 2 Transfer storage, 4 Disk surplus storage, 5 Production storage, 6 Other storage, 7 Warranty storage, 8 Error correction storage, 9 Initialization storage, 10 Pre-storage, 11 JIT Return warehousing 12 Outsourcing warehousing |
| status | Inbound order status | Storage order status 10 canceled 20 editing 25 waiting for price confirmation 30 waiting for review 32 waiting for push 33 push failure 35 outsourcing waiting for storage 60 waiting for settlement 80 completed Then query 80 completed documents by default) | |
| warehouse_no | warehouse number | The unique code representing all the attributes of the warehouse is used to distinguish warehouses. ERP supports customization (ERP warehouse interface settings), which is used to obtain the specified warehouse document information (does not support pushing multiple warehouse numbers at a time) | |
| src_order_no | Upper level document number | Upper-level document number, this field can be passed without the start time and end time | |
| stockin_no | Warehousing order number | Inbound order number, this field can be passed without the start time and end time | |
| page_size | Paging Size | { {PAGINATION_PAGE_SIZE}} | The number of data items returned per page, the input value range is 1100, if this parameter is not passed, the input value defaults to 40, click here for an example of use |
| page_no | page number | { {PAGINATION_START_PAGE}} | If no value is passed, it starts from page 0 by default |
response parameter
| interface field | Field Name | default value | describe |
|---|---|---|---|
| stockin_id | Inbound single primary key id | Inbound single primary key id | |
| order_no | Warehousing order number | The system storage order number, which starts with RK by default | |
| stockin_no | Warehousing order number | Warehousing order number | |
| wms_status | Outsourcing status | Outsourcing status | |
| wms_result | error message | error message | |
| warehouse_id | Warehouse ID | warehouse id | |
| src_order_type | Storage type | 1Purchasing storage, 2Transfer storage, 3Return storage, 4Plan surplus storage, 5Production storage, 6Other storage, 7Warranty storage, 8Error correction storage,9Initialization storage10Pre-storage 11JIT returns and storage 12Outsourcing storage' | |
| src_order_id | storage id | storage id | |
| reason_id | Other reasons for storage | Other reasons for storage | |
| fa_status | Financial Sync Status | Financial Sync Status | |
| logistics_id | logistics company | logistics company | |
| post_share_type | postage sharing type | Postage allocation type 0, no allocation 1, allocation by quantity 2, allocation by amount | |
| operator_id | Person in charge | Person in charge | |
| note_count | Number of sticky notes | Number of sticky notes | |
| flag_id | mark color | mark color | |
| modified | Last Modified | Last Modified | |
| warehouse_no | warehouse number | The unique code representing all the attributes of the warehouse is used to distinguish warehouses, and ERP supports customization (ERP warehouse interface settings) | |
| warehouse_name | warehouse name | System warehouse name in ERP | |
| status | state | 10 Canceled 20 Editing 25 Pending price confirmation 30 Pending review 32 Pending pushing 33 Pushing failed 35 Subcontracting Pending warehousing 60 Pending settlement 80 Completed | |
| stockin_time | Storage time | Storage time, format: YYYY-MM-DDHH:MM:SS | |
| created_time | creation time | Creation time, format: yyyy-MM-dd HH:mm:ss | |
| remark | Remark | Remark | |
| stockin_reason | Reason for storage | Reason for storage | |
| order_type | order category | order category | |
| order_type_name | Order category name | Order category name | |
| goods_count | Item Quantity | Item Quantity | |
| goods_amount | Total payment | Total payment | |
| total_price | Total payment after deduction of discount | Total payment after deduction of discount | |
| discount | Discounted price | Discounted price | |
| tax_amount | After-tax amount | After-tax amount | |
| post_fee | postage | postage | |
| other_fee | other fee | other fee | |
| logistics_type | Logistics type | Logistics method, for details, click here | |
| check_time | Review time | Review time, format: YYYY-MM-DDHH:MM:SS | |
| src_order_no | Source tracking number | The upper-level document number, if it is purchased into the warehouse, it is the purchase order number, and the transfer into the warehouse is the transfer number, and so on | |
| outer_no | External tracking number | External tracking number | |
| logistics_no | shipment number | Logistics order number, before obtaining this field, the version needs to be upgraded to V2.3.9.1 and above stable version | |
| operator_name | operator name | operator name | |
| details_list | Item list node | Level 2 data node of the response parameter, a data node containing all item attribute information of a single storage order, see the following "stockin_list" list for details of the data fields under the node | |
| details_list.stockin_id | 入库单主键id | 入库单主键id | |
| details_list.rec_id | 主键 | 主键（与业务无关） | |
| details_list.src_order_detail_id | 上层单据明细主键 | 上层单据明细主键 | |
| details_list.src_order_type | 入库类型 | 1采购入库,2调拨入库,3退货入库,4盘盈入库,5生产入库,6其他入库,7保修入库,8纠错入库,9初始化入库10预入库11JIT退货入库12委外入库' | |
| details_list.org_stockin_detail_id | 原始入库单明细 | 原始入库单明细 | |
| details_list.spec_id | 规格ID | 规格ID | |
| details_list.batch_id | 批次 | 批次 | |
| details_list.position_id | 货位ID | 货位ID，入库时默认ID，后来做货位调拨不再修改 | |
| details_list.num | 库存单位 | 库存单位 | |
| details_list.num2 | 辅助单位量 | 辅助单位量 | |
| details_list.unit_id | 辅助单位 | 辅助单位 | |
| details_list.base_unit_id | 基本单位 | 基本单位 | |
| details_list.unit_ratio | 单位换算关系 | 单位换算关系 | |
| details_list.expect_num | 预期入库数量 | 预期入库数量（基本单位数量，显示可自动转换成辅助单位） | |
| details_list.cost_price2 | 辅助成本价 | 辅助成本价 | |
| details_list.share_post_cost | 邮资分摊成本 | 邮资分摊成本 | |
| details_list.share_post_total | 邮资分摊总成本 | 邮资分摊总成本 | |
| details_list.modified | 最后修改时间 | 最后修改时间 | |
| details_list.created | 创建时间 | 创建时间 | |
| details_list.spec_no | 商家编码 | 代表单品(sku)所有属性的编码，SKU概念介绍,单击这里 | |
| details_list.goods_count | 货品数量 | 货品数量 | |
| details_list.discount | 优惠金额 | 入库单管理的“优惠” | |
| details_list.right_num | 调整后数量 | 货品数量+纠错数量 | |
| details_list.right_price | 调整后单价 | 调整后单价 | |
| details_list.right_cost | 调整后总金额 | 扣除优惠后货款总额+入库后续调整价格,right_num*right_price | |
| details_list.cost_price | 成本价 | 入库单管理的“入库价” | |
| details_list.production_date | 生产日期 | 生产日期，格式：yyyy-MM-dd HH:mm:ss | |
| details_list.validity_days | 有效期天数 | 生产日期 | |
| details_list.expire_date | 有效期 | 有效期，格式：yyyy-MM-dd HH:mm:ss | |
| details_list.src_price | 原价 | 原价 | |
| details_list.tax_price | 税后单价 | 税后单价 | |
| details_list.tax_amount | 税后金额 | 税后金额 | |
| details_list.tax | 税率 | 税率 | |
| details_list.total_cost | 总成本 | 总成本 | |
| details_list.remark | 备注 | 入库单备注 | |
| details_list.adjust_num | 调整数量 | 调整数量，计算方式为调整后数量-原数量 | |
| details_list.adjust_price | 调整单价金额 | 调整单价金额，计算方式为调整后价格-原价 | |
| details_list.brand_no | 品牌编号 | 品牌编号 | |
| details_list.brand_name | 品牌名称 | 品牌名称 | |
| details_list.goods_name | 货品名称 | 货品名称 | |
| details_list.goods_no | 货品编号 | 代表货品(spu)所有属性的编号，SPU概念介绍,单击这里 | |
| details_list.spec_name | 规格名称 | 规格名称 | |
| details_list.spec_code | 规格码 | 规格码 | |
| details_list.prop2 | 自定义属性2 | 单品列表的自定义属性2 | |
| details_list.goods_unit | 单位 | 货品单位 | |
| details_list.batch_no | 批次号 | 批次号 | |
| details_list.batch_remark | 批次备注 | 批次备注 | |
| details_list.position_no | 货位编号 | 货位编号 |
金蝶云星空接口明细
- 接口：batchSave
- 接口名称：其他入库新增
- 接口方法：POST
请求参数
| 字段 | 名称 | 类型 | 描述 |
|---|---|---|---|
| FBillNo | 单据编号 | string | |
| FBillTypeID | 单据类型 | string | |
| FStockOrgId | 库存组织 | string | |
| FDate | 日期 | string | |
| FSUPPLIERID | 供应商 | string | |
| FDEPTID | 部门 | string | |
| FNOTE | 备注 | string | |
| FEntity | 明细信息 | array | |
| FEntity.FMATERIALID | 物料编码 | string | |
| FEntity.FCMKBarCode | 零售条形码 | string | |
| FEntity.FSTOCKID | 收货仓库 | string | |
| FEntity.FQty | 实收数量 | string | |
| FEntity.FPrice | 成本价 | string | |
| FEntity.FEntryNote | 备注 | string | |
| FEntity.FormId | 业务对象表单Id | string | |
| FEntity.IsVerifyBaseDataField | 验证基础资料 | bool | |
| FEntity.Operation | 执行的操作 | string | |
| FEntity.IsAutoSubmitAndAudit | 提交并审核 | bool |
系统数据集成价值
异构系统都具有非常丰富的业务流程、复杂的系统架构和服务接口。在很多情况下，这两个系统都是分别独立部署和运行的，各自拥有不同的技术栈和编程模型，甚至两者在系统平台、技术平台和编程语言上是完全异构的。采用“轻易云集成方案”的解决方案，可以满足客户的实际业务需求，推动软件工程的规范化，使开发人员遵循统一的概要设计开发实现，降低系统实现的风险，做到系统设计资料的规范性与全面性，以利于系统的实现、测试、维护、版本升级等。通过轻易云系统集成平台完美结合：打破企业内部数据孤岛，无需繁琐的处理工序，与数据集成服务完美结合，让数据真正通起来。 资源互补：汇集各种行业解决方案，资源互补，企业管理融合提升。
