Disclaimer: Although the topic here is called "EDI technology shallow", it does not indicate that EDI does require deep technologies, just say it is good, give people a deep confusion ^ O ^
1.EDi (Electronic Data Interchange Electronic Data Exchange, Paperless Trade [Jinshan Words 2003 Explanation])
2. Flat file: electronic data file independent of computer operating system
3.edi packet
It is a file that exchanges data by electronic media. During this exchange data, it is mainly composed of two parts, format, and platforms.
The format refers to the specific data format of the packet. The platform refers to the operating system platform of the packet (but most EDI messages are transmitted in flat file format, but due to the existence of Windows, the packets of the excel and other fixed platform formats are also very common)
4.edi definition
EDI packet definitions refers to the format of the EDI packet, which is a convention common to both trading partners. Due to the popularity of the computer, the United Nations and the Ministry of Communications have the format definition of various electronic messages, of which we are usually referred to as Edifact. Of course, you can set a format definition with your trading partners, but this will be greatly reduced in terms of versatility. So we recommend using the United Nations and Ministry of Communications
5. A universal EDI reception verification send model - programmer's most concerned issue
When developing projects in the development of transportation, we often involve issues for receiving the EDI packet.
For example, the production management of a container terminal will involve reception and sending verification issues with a large number of EDI data between other container terminals, containers, cargo agents.
However, due to the irregularity of the EDI format, and other container terminals, container companies, goods agents, the imperfect technology, and EDI packet generation, and the inevitable avoidance of the transmission process, still give EDI packets. Receiving verification sent work has caused considerable difficulties. Secondly, the reception and verification of unknown packets is also a fairly headache for programmers.
So, how can I develop a relatively universal EDI system? A model is given below.
Check the Administrative Measures for the Administration of Customs Banks in the People's Republic of China)
Http://customs.huzhou.gov.cn/zcfg/hggz/ysgj/1.htm
?
Or self-search (relevant standards of the Ministry of Communications of the People's Republic of China)
Or United Nations standard boat map (P1)
Read the following
Part 1: Data format definition
Compose from about 6 parts:
(1) Data (packet) code (commodity inspection packet, customs packet) is equivalent to the name of a class of books
(2) Data (packet) standard definition (trade inspection box single standard, customs criteria) defined standards, equivalent to a class of literary books, such as ancient Chinese literature, modern English literature. When we see this standard, you know that her format is either Chinese characters, or English
(3) Record (Customs Bank Standard: Wildermat Record, Shimono Record, Shipment SLR - Container Record) Usually contain multiple records in a standard, if there is only one record, then this is the simplest message, the most Easy to handle, it is formatted
(4) Specific content in the field record, such as a container box number MSKU1234567
(5) Field Properties We have to receive (read) rules when this field
(6) Database table definition which piece we want to read the data to which one of the specific items specifically in the database?
In this section, the most important thing is (3) and (5) two parts, because we will define a read rule in these two parts. ▲ record: We should implement
1. What is the record of reading?
A. According to the length (so the customs standard must
B. According to a specific segmentation symbol (this must be the case)
C. Read according to the beginning of the flag (so that the transportation format must be
D. Other ... (XML format)
2. Is this recorded? Is this recorded in nested loop? - How to deal with the loop of the record?
A. Follow a sign (the EQD in P1 will tell us, a segment group cycle (that is, record cycle. Segment group: Nesting loop record)))
B. Follow the specified digital loop (Customs shipping list)
other...
▲ Field: We should implement
1. Where did you read?
To be able to set which field read to the table, this may appear
2. How to read?
A. Read according to the length (the customs manifest can only be like this)
B. Read according to the identity
C. Read according to the division (this should be the case)
E.g:
NAD CA CMA: 172: ZZZ '
LOC 147 0250702 :: 5 '
NAD, LOC is a record identity, CA, 147 as a specific value of the field, divided by division ( )
Note CMA: 172: Zzz is a nest, CMA, 172, ZZZ below NAD is a field, which is divided by (:), so we should call NAD a segment group.
D. The function function should be provided.
E.g,
(A) Repeat the setting function, I can repeat the CA insertion into a field in all records in the table.
(B) Judgment the function, when the data in the first field of NAD record is equal to CA, I will convert CA to CN.
(C) TRIM, LEFT, RIGHT, MID function, intercept string
(D) Field extraction function, when you should write CMA, I will extract the value of CA, write (this time CA must be read, otherwise there will be a problem)
(E) Other functions
Through the above analysis, we will see
It can be basically universal, but the control is quite inconsistent, the specific details are too many, and there is no more experience in analyzing 2 or 3 standards.
A little experience:
The various standards of the United Nations are most cumbersome, because should be adapted to the whole world! If you can make the united standards over again, other criteria will work more smoothly.
Due to the development of XML, XML is a trend as a platform file transmission.
