In this article, we have made a detailed interpretation of EDIFACT. You can start to have an in-depth understanding of ORDERS orders based on this. - 220 = purchase order Purchase order.

Arrow Arrow and its suppliers transmit packets of the EDIFACT standard, with two business models: AOI (Arrow Owned Inventory) mode and SOI (Supplier Owned Inventory) mode, also known as VMI (Vendor Managed Inventory).

No matter which business model is adopted by the supplier, it is necessary to receive orderS order from Arrow Electronics. How to understand EDIFACT messages in previous articles? In this article, we have made a detailed interpretation of EDIFACT. You can start to have an in-depth understanding of ORDERS orders based on this.

This article will interpret ORDERS orders that comply with the EDIFACT message standards and convert them into a more easily processed XML format file.

The following is a comparison chart before and after the conversion of the EDI system through Zhixingzhiqiao:

ORDERS sample order interpretation

Arrow will send EDIFACT standard EDI ORDERS orders to the supplier, where UNA is optional, and the UNB in ​​the second row and the UNZ in the last row belong to the Interchange part of EDIFACT, which is a must. Normally, core information starts with the BGM field.

Arrow Arrow and its suppliers transmit packets of the EDIFACT standard, with two business models: AOI (Arrow Owned Inventory) mode and SOI (Supplier Owned Inventory) mode, also known as VMI (Vendor Managed Inventory).

No matter which business model is adopted by the supplier, it is necessary to receive orderS order from Arrow Electronics. How to understand EDIFACT messages in previous articles? In this article, we have made a detailed interpretation of EDIFACT. You can start to have an in-depth understanding of ORDERS orders based on this.

This article will interpret ORDERS orders that comply with the EDIFACT message standards and convert them into a more easily processed XML format file.

The following is a comparison chart before and after the conversion of the EDI system through Zhixingzhiqiao:

ORDERS sample order interpretation

Arrow will send EDIFACT standard EDI ORDERS orders to the supplier, where UNA is optional, and the UNB in ​​the second row and the UNZ in the last row belong to the Interchange part of EDIFACT, which is a must. Normally, core information starts with the BGM field.The example is as follows:

5

7

9

0

11

2

13

4

15

1 = Assigned by Vendor or Vendors agent

QTY+21:21000:PCE'

- 21 = Ordered quantity Requirement quantity

- 21000: Requirement quantity

- PCE: Unit of quantity

PRI+AAA:0.6599:CA::1:PCE'

- AAA = Calculation net Calculation net Calculation net Calculation net

.6599: Calculation net

- CA = Catalog / distributor price Directory/Distribution price

- CT = Contract price Contract price

- QT = Quote price quotation

: Product id function qualification Product ID function qualifier

- Quantity unit: PCE

RFF+LI::1'

- LI = Line Number Material line number

- PR = Quote reference Reference

- CT = Contract / DBP reference contract / DBP reference

: Material line number

SCC+1'

- 1 = Firm

QTY+21:21000'

1 = Ordered Quantity Order quantity

1000: Order quantity

DTM+2:20220523:102'

- 2 = Delivery Date Delivery Date

0220523: Delivery Date

02 = CCYYMMDD Date format

UNS+S'

S = Detail/summary section separation Detailed part

UNT+17+00000000000000000001'

UNZ+1+0000000000000000003'

Through the above message interpretation, we can see that the EDIFACT ORDERS message we received is poorly readable, and it is difficult for both the business personnel of the enterprise and the IT personnel to obtain valid business information directly from the above orders.Therefore, this ORDERS order needs to be converted in format.

Use the Bridge of Zhixing EDI system to convert it into a target XML format file with more readability for further processing. The conversion effect is as follows:

5

7

9

0

11

2

13

4

15html l3

6

17

8

19

0

21

2

23

4

25

6

27

8

29

0

31

2

33

4

35

?xml version="1.0" encoding="UTF-8"?

Items xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

po_header table="`dbo`.`po_header`" action="upsert"

id key="true"9682064cb9794790ac11c651d32ca959/id

buyer_contactWei, Iris/buyer_contact Buyer's contact

buyer_numberC-0100191/buyer_number Buyer's number

currencyUSD/currency Currency

delivery_number/delivery_number Delivery code

po_numberTEST000210001/po_number Purchase order number

status type="int"0/status

seller_number65000192/seller_number Seller number

po_item Order material

idb79cfbbc1e034597a3ccf2864e4452f4/id

buyer_item_number/buyer_item_number_number Buyer's material number

hid/hid

item_desc/item_desc Material details

line_item_number1/line_item_number Material line number

line_number/line_number Line number

price/price Price

price_type/price_type Price type

price_unit/price_unit Price unit

quantity_unit/quantity_unit Quantity unit

status0/status Status code

supplier_item_number/supplier_item_number Supplier material number

total_ordered_quantity/total_ordered_quantity Total order quantity

unit_price/unit_price Unit price

po_detail Order details

ide98445c108924a36afa6a3eb98a589c5/id

ordered_quantity/ordered_quantity Order quantity

plan_status1/plan_statusstatus0/status

tid/tid

/po_detail

/po_item

/po_header

/Items

You can see that in the target XML file converted by the EDI system, all the business data and its business meaning are one by one. This file is more readable and more convenient for the next data processing.

workflow example

Through the above explanation, I believe everyone is very interested in the conversion process of Arrow ORDERS orders in the Zhixing Bridge EDI system. The following is the above workflow example.

Import the above workflow and test file

in the Zhixing Bridge EDI system as shown in the figure below:

Upload the test file: In EDIFACT_IN on the port of , enter tab, click more , upload the test file: Arrow ORDERS test flies.edifact

Download the converted test file: Under the Arrow_ORDER_IN tab of port Output , click Arrow ORDERS test files.xml to download the file and see the converted effect.

Detailed conversion operation process

In the Zhixing Bridge EDI system, the above conversion is implemented, using two ports: EDIFACT and XML Map, that is, the ORDERS order is converted from EDIFACT format to the target XML format:

Step 1: Use the EDIFACT port to convert the received ORDERS order from EDI to standard XML.

Under the output tab, you can see the ORDERS order converted to standard XML format. At this time, the converted format is not the target XML format. Since this is just an intermediate format for us to convert the format, we will not repeat it here.

Step 2, uses the XML Map port to convert the standard XML format ORDERS order obtained in the first step into the target XML format that the business system can further process. XML Map ports are designed to implement format conversion between any different XML, and are not limited to EDI standard message conversion process.

This step requires configuring the source file and the target file and field mapping in mapping . (The source file and the target file have been configured in the sample workflow, and can be used directly)

The source XML file and the header information of the target XML file are mapped as follows:

We take the Order Number included in the BGM field as an example:

Through the official specification file provided by Arrow, we can see that the detailed location of the order number is located in the BGM field C106_1004. In the 2021 edition of Zhixing Bridge EDI System, find the corresponding field from the source file on the left of the XML Map port shown in the figure above, select it and drag it to the po_number on the right to establish a mapping relationship. At this time, the green font will be displayed in the target file on the right: [BGM/C106/_1004], and a gray line will appear to connect the two nodes. The mapping relationship of other field information can be the same as the above method, so I will not repeat it again.

or above is a detailed introduction to the interpretation and conversion of Arrow EDI ORDERS messages received. Learn more about Arrow EDI message information. Welcome to communicate.

For more EDI information, please refer to: What is EDI? | EDI Communication Expert

Original link: Arrow EDI ORDERS Order Interpretation | EDI Communication Expert