The connection between Jushuitan and Kingdee Cloud Xingkong integrates return and refund inquiries [Jushuitan][Added sales return order standard]-v1
Docking System Jushuitan
Jushuitan was established in 2014. The founder and CEO Luo Haidong has nearly 30 years of experience in the development, implementation and deployment of traditional and e-commerce ERP. At the beginning of its establishment, Jushuitan entered the market with e-commerce SaaSERP, and quickly gained market recognition with its excellent products and services. With the ever-changing needs of customers, Jushuitan has now developed into a SaaS collaborative platform with SaaSERP as the core and integrating various business services. After more than 8 years of development, the company's employees have increased from 9 at the beginning of its establishment in 2014 to nearly 4,000 now. Jushuitan has established more than 100 offline service outlets across the country, covering more than 400 cities and towns, providing customers with timely, thoughtful and professional services.
Docking system: Kingdee Cloud and Starry Sky
Kingdee K/3Cloud (Kingdee Cloud Starry Sky) is a new type of ERP in the mobile Internet era, and a new era enterprise management service platform based on WEB2.0 and cloud technology. Kingdee K/3Cloud focuses on "ecology, everyone, and experience" and aims to help enterprises create an ecological interconnection and collaboration platform for the new era, and provide readily available cloud services around each role in the ecosystem, and finally realize agile collaboration , a new realm of enterprise operation with intelligent operation. The entire product adopts the SOA architecture and is completely based on the BOS platform. The business architecture runs through the process-driven and role-driven ideas, combined with the Chinese management model and the accumulation of Chinese management practices, to support corporate financial management, supply chain management, production management, and supply in a refined manner. Chain collaborative management, human resource management and other core applications. In terms of technical architecture, the product is built on a platform, supports cross-database applications, and supports three deployment methods: local deployment, private cloud deployment, and public cloud deployment. At the same time, it also opens China's first ERP-based collaborative development cloud platform on the public cloud. Any enterprise that uses Kingdee K/3Cloud products has many IT service partners including Kingdee that provide services based on the same platform.
Data docking scheme
By dragging, pulling, and dragging the visual interface, you can easily and quickly build the data integration process, connect the interface data between Jushuitan and Kingdee Cloud and Starry Sky, support online data preview, debug the whole process of the data integration process, and track and debug logs on the web interface. . The platform has both real-time data processing and data integration and distribution functions. Users can complete the data processing logic through visual drag and drop, and distribute the data to downstream business systems or other heterogeneous storage after processing.
Jushuitan interface details
- API：/open/refund/single/query
- NAME: Return Refund Inquiry
- METHOD：POST
request parameters
| interface field | Field Name | default value | describe |
|---|---|---|---|
| shop_id | store number | store number | |
| is_offline_shop | shop_id is 0 and is_offline_shop is true to query offline store receipts | shop_id is 0 and is_offline_shop is true to query offline store receipts | |
| modified_begin | Modify start time | The modification start time and end time must exist at the same time, the time interval cannot exceed seven days, and the online order number cannot be empty at the same time | |
| modified_end | Modify end time | The modification end time and start time must exist at the same time, the time interval cannot exceed seven days, and the online order number cannot be empty at the same time | |
| so_ids | online order number | Specify the online order number, and the time period cannot be empty at the same time | |
| shop_buyer_ids | Designated buyer account | Designated buyer account, up to 50 | |
| page_index | The first page, starting from the first page, default 1 | 1 | The first page, starting from the first page, default 1 |
| page_size | How many items per page, default 30, maximum 50 | 50 | How many items per page, default 30, maximum 50 |
| as_ids | After-sales order number | "10741298" |
response parameter
| interface field | Field Name | default value | describe |
|---|---|---|---|
| as_id | ERP after-sales order number | ERP after-sales order number | |
| as_date | application time | application time | |
| outer_as_id | Platform return and refund order number | 10741298 | Platform return and refund order number |
| o_id | Internal tracking number | Internal tracking number | |
| so_id | Online tracking number | Online tracking number | |
| type | Aftermarket type | After-sales type, ordinary return, other, rejected return, refund only, complaint, reissue, exchange | |
| created | check-in time | check-in time | |
| modified | Change the time | Change the time | |
| status | state | Status (WaitConfirm: pending confirmation, Confirmed: confirmed, Cancelled: void, Merged: merged) | |
| shop_status | Order corresponding status | WAIT_SELLER_AGREE: The buyer has applied for a refund, waiting for the seller to agree, WAIT_BUYER_RETURN_GOODS: The seller has agreed to refund, waiting for the buyer to return the product, WAIT_SELLER_CONFIRM_GOODS: The buyer has returned the product, waiting for the seller to confirm receipt, SELLER_REFUSE_BUYER: The seller refused to refund, CLOSED: Refund Close, SUCCESS: Refund successful | |
| remark | Remark | Remark | |
| question_type | question type | question type | |
| warehouse | storehouse | storehouse | |
| refund | refund amount | refund amount | |
| payment | Compensation amount | Compensation amount | |
| good_status | cargo status | Goods status (BUYER_NOT_RECEIVED: The buyer has not received the goods, BUYER_RECEIVED: The buyer has received the goods, BUYER_RETURNED_GOODS: The buyer has returned the goods, SELLER_RECEIVED: The seller has received the returned goods) | |
| node | After-sales offline remarks | After-sales offline remarks | |
| order_status | Original order status | Original order status | |
| shop_id | store number | store number | |
| logistics_company | logistics company | logistics company | |
| l_id | shipment number | shipment number | |
| wh_id | warehouse number | warehouse number | |
| wms_co_id | Warehouse number | Warehouse number | |
| confirm_date | Last confirmed date | Last confirmed date | |
| freight | The seller should refund the shipping fee | The seller should refund the shipping fee | |
| drp_co_id_from | Distributor number | Distributor number | |
| receiver_mobile | The recipient's phone | The recipient's phone | |
| receiver_name | recipient name | recipient name | |
| shop_buyer_id | Buyer account | Buyer account | |
| items | product list | product list | |
| items.asi_id | After-sales order number | After-sales order number | |
| items.as_id | ERP after-sales order number | ERP after-sales order number | |
| items.sku_id | commodity code | commodity code | |
| items.qty | quantity | quantity | |
| items.price | unit price | unit price | |
| items.amount | the amount | the amount | |
| items.name | product name | product name | |
| items.pic | The map's address | The map's address | |
| items.type | Type (return, exchange, reissue) | Type (return, exchange, reissue) | |
| items.properties_value | color specification | color specification | |
| items.outer_oi_id | sub order number | sub order number | |
| items.sku_type | Product Types | Product Types | |
| items.r_qty | Received Return Quantity | Received Return Quantity | |
| items.i_id | style code | style code | |
| items.batchs | batch collection | ||
| items.batchs.batch_no | batch number | ||
| items.batchs.sku_id | commodity code | ||
| items.batchs.qty | Number of Products | ||
| items.batchs.product_date | batch date | ||
| items.batchs.supplier_id | supplier code | ||
| items.batchs.supplier_name | Supplier name |
Kingdee Cloud Xingkong interface details
- Interface: batchSave
- 接口名称：[聚水潭][销售退货单标准新增]-v1
- 接口方法：POST
请求参数
| 字段 | 名称 | 类型 | 描述 |
|---|---|---|---|
| FBillTypeID | 单据类型 | string | 单据类型 |
| FBillNo | 单据编号 | string | 单据编号 |
| FSaleOrgId | 销售组织 | string | 销售组织 |
| FDate | 日期 | string | 日期 |
| FStockOrgId | 库存组织 | string | 库存组织 |
| FRetcustId | 退货客户 | string | 退货客户 |
| FSettleCurrId | 结算币别 | string | 结算币别 |
| FHeadNote | 备注 | string | 备注 |
| FEntity | 明细信息 | array | 明细信息 |
| FEntity.FMaterialId | 物料编码 | string | 物料编码 |
| FEntity.FRealQty | 实退数量 | string | 实退数量 |
| FEntity.FPrice | 单价 | string | 单价 |
| FEntity.FTaxPrice | 含税单价 | string | 含税单价 |
| FEntity.FIsFree | 是否赠品 | string | 是否赠品 |
| FEntity.FEntryTaxRate | 税率% | string | 税率% |
| FEntity.FReturnType | 退货类型 | string | 退货类型 |
| FEntity.FOwnerTypeId | 货主类型 | string | 货主类型 |
| FEntity.FOwnerId | 货主 | string | 货主 |
| FEntity.FStockId | 仓库 | string | 仓库 |
| FEntity.FNote | 备注 | string | 备注 |
| FEntity.F_PSEH_TEXT | 网上订单号 | string | |
| FEntity.FSrcBillTypeID | 源单类型 | string | |
| FEntity.FSrcBillNo | 源单编号 | string | |
| FEntity.F_PSEH_AMOUNT1 | 管易价税合计 | string | |
| FEntity.FDISCOUNT | 折扣额 | string | |
| FEntity.FLot | 批次号 | string | |
| FEntity.FProduceDate | 生产日期 | string | |
| FEntity.FExpiryDate | 有效期至 | string | |
| FEntity.FUnitID | 库存单位 | string | |
| FEntity.SubHeadEntity | 财务信息 | object | 财务信息 |
| FEntity.SubHeadEntity.FSettleOrgId | 结算组织 | string | 结算组织 |
| FEntity.SubHeadEntity.FAllDisCount | FAllDisCount | string | |
| FEntity.SubHeadEntity.F_KLF_Text | 聚水潭订单号 | string | |
| FEntity.SubHeadEntity.F_KLF_Text1 | 聚水潭物流单号 | string | |
| FEntity.SubHeadEntity.FormId | 业务对象表单Id | string | 必须填写金蝶的表单ID如
|
| FEntity.SubHeadEntity.Operation | 执行的操作 | string | |
| FEntity.SubHeadEntity.IsAutoSubmitAndAudit | 提交并审核 | bool | |
| FEntity.SubHeadEntity.IsVerifyBaseDataField | 验证基础资料 | bool | 是否验证所有的基础资料有效性，布尔类，默认false（非必录） |
系统数据集成价值
随着企业数字化业务的深入发展，对于企业的 IT 或者 CIO 来讲，正在面临一个愈发重要的问题——系统的结构太复杂了，尤其是头部企业，至少有十多套系统，这些系统之间的蛛网状的接口如果经常出问题。企业内部以及企业内部与外部建立起越来越多的业务应用系统，如何整合企业的现有IT资源，使企业中计算机孤岛式的应用向集体协作的方向发展，发挥资源效益的最大化，降低企业成本，正在逐渐成为企业关注的重要问题。用户希望企业内所有系统集成在一个平台上，操作统一，以节省培训时间。使用在轻易云应用集成平台 + MDM基础数据平台的解决方案中，轻易云应用集成平台负责实现异构、分布式系统之间互联互通，实现服务API治理以及数据传输交换。通过轻易云预置的各种适配器组件，连接现有各孤立应用系统，以图形化、拖拽方式构建集成流程和服务，提高应用系统集成工作效率，降低异构系统集成风险。针对未来可能出现的业务需求变更，在应用集成平台上进行动态调整，实现各应用系统之间的集成策略平滑升级。
