TW444176B - System and method for automatic XML/EDI data transformation - Google Patents

Abstract

The present invention provides a system and method for automatic XML/EDI data transformation. The system includes at least two exchange servers having XML/EDI objects transmitted therebetween. Each exchange server includes: a receiving module for receiving XML/EDI objects, a document type defined module having DTD data, and a parsing module. The parsing module parses the XML/EDI objects according to the DTD data to store them into a repository after tablization.

Description

444 7 76 V. Description of the invention (1) The present invention relates to an XML / EDI architecture, and more particularly to an XML / EDI data automatic conversion system and method. "Extensible Markup Language" (referred to as xml for short) is a new generation of markup language. It originates from the "Standard Generalization" set by the International Standards Organization (ISO) in 1986. Markup Language "(Standard Generalized Markup Language, SGML for short). At the end of 1996, it was proposed by the World Wide Web Consortium to establish a global information network standard, which was mainly developed for how to transmit or process large and complex electronic documents on the information network. XML retains SGML's document self-describing system and document structure function, but it also eliminates the shortcomings of SGML which is too large and complex and difficult to popularize. Although the lightweight and easy-to-understand HTML promotes the rapid popularization of the World Wide Web, the application of HTML tags is very limited and only applies to the processing of a small amount of documents. It is diversified in the multimedia and layout of the World Wide Web platform and the eagerness of e-commerce Requirements, the HTML syntax is no longer sufficient. Therefore, the characteristics of XML, even with the powerful functions and flexibility of SGML, can also meet the use environment of the World Wide Web. Through the interoperability and extensibility of XML, it has become a new generation of standard languages. Electronic Data Interchange (hereinafter referred to as ED I) has been in use since the beginning of the 1960s and was widely used in the automotive, retail, transportation, and international trade fields in the mid-1980s. Improving information exchange between trading partners, suppliers and customers

444? 76 5. Description of the invention (2), reducing the obstacles to interaction and business exchanges. In short, EDI is a technology for expressing business information in a standard electronic format, which enables rapid circulation and exchange of business information. In order to achieve the purpose of data exchange, ED I creates relevant EDI messages from the database according to the nature of the data, and clearly lists the attributes of the data, so that the provider can be positive when the data is exchanged. Corresponding to different Message. $ & Because the characteristics of XML and EDI coincide, some XML / EDI architects have been proposed to allow industries to use XML language tools to write documents, transmit and process EDI messages. The XML / EDI architecture usually includes five main components: 'Internet data exchange conforming to XML format, traditional ED 1 business rights and § interest structure, template based on professional knowledge processing rules, and performing special functions Agent for data processing, and a network storage database (rep0sit〇ry) for storing documents and rule templates ^ XML and EDI are existing standards, and agents and storage databases are XML files used in The communication mechanism required in electronic transactions is based on the conversion of EDI message standards widely used in various industries into XML markup structures. One object of the present invention is to provide an XML / edi data automatic conversion system and method, which is based on the traditional EDi attribute definition when the data to be exchanged is converted and converted into an asset management mode in an automatic and flexible manner. The cost-effectiveness and the flexibility to deal with the exchange of data and information efficiently. In order to achieve the above object of the present invention, it can be accomplished by an automatic data conversion system. This system, / FnT ^ ^. This system includes at least two exchange servers with XML / EDI objects passed between them. Each J ^ exchange server includes:

4/76 V. Description of the invention (3) --- Receive one of the XML / EDI objects i * ji. — Receive Bin group, a document type semantic module with a DTD data, and a ,, / Ρητ, λ. Analysis of Bin group. The parsing module is based on the DTD data for XML / EDI objects and is not in the 4ii —. Repository. The analysis is performed on a table and stored in a database. The present invention provides a method for automatic conversion of XML / EDI data, which is suitable for passing XML / EDI objects between at least two exchange servers. First, the XML / EDI object is received by one of the exchange servers. Then, based on a DTD data, the XML / EDI object is parsed. The parsed XML / EDI objects are then tabulated and stored in a database. In order to make the above and other objects, features, and advantages of the present invention more comprehensible, a preferred embodiment is given below in conjunction with the accompanying drawings to make a detailed description as follows: Brief description of the drawings: FIG. 1 It is a block diagram showing the first preferred embodiment of the XML / EDI data automatic conversion system according to the present invention; FIG. 2 is a block diagram showing the module architecture of the EDI exchange server of FIG. 1; A block diagram of the second preferred embodiment of the XML / EDI data automatic conversion system; and FIG. 4 is a block diagram showing the third preferred embodiment of the XML / EDI data automatic conversion system according to the present invention. Explanation of symbols: 1, 2 ~ EDI exchange server; 3 ~ XML / EDI objects; 4,5 ~ relationship database; 7,8 ~ MIS system; 20 ~ receiving module; 2bu transmission module;

444 f 76

22 ~ analysis module; 23 ~ XML generation module; 24 ~ document type definition module; 25 ~ database interface module; and 26 ~ EDI interface module. Embodiment: First Embodiment Please refer to FIG. 1, which shows a block diagram of a first preferred embodiment of an XML / ED I data automatic conversion system according to the present invention. In Figure 1, the symbols j and 2 represent EDI exchange servers, and XML / EDI objects 3 exchange between them. 'E DI exchange feeders 1 and 2 can be through an intranet, Local area network (LAN), wide area network (WAN), Internet (Internet) transmits XML / EDI objects3. The meaning of XML / EDI object 3 here means the EDI data object with XML language format. In Figure 1, the relationship between the EDI exchange server 1 and the management information system (hereinafter referred to as the MIS system) of company A can be a server-client network architecture. That is, the EDI exchange server 1 is a server, and the MIS system 6 of company A is a client. Similarly, the EDI exchange server 2 and the MIS system 7 of company B also have a master-slave network structure, that is, the EDI exchange server 2 is the server, and the MIS system 7 of company B is the client. According to the present invention, the EDI data required to be received by the company's M IS system 6 is first processed by the EDI exchange server 1 and then stored in the related database 4 for the company A's M IS system 6 Read it for further processing. The EDI data required by the MIS system 6 of company A is also processed by the EDI exchange server 1 and converted into XML / EDI objects 3 with XML language format.

Page 7 4 44 f 76 5. Description of the invention (5) Send it out. Similarly, the EDI data required by the M IS system 7 of company B is first converted and processed by the EDI exchange server 2 and then stored in the related database 5 for reading by the M IS system 7 of company B. Take it for further processing. The EDI data required by the MIS system 7 of company B is also processed by the EDI exchange server 1 and converted into an XML / EDI object 3 with an XML language format, and then transmitted. Please refer to Figure 2, which shows the module architecture diagram of EDI exchange server 1 or 2. In the figure, the module structure includes: receiving module 20, transmitting module 21, parser 22, XML generating module 23, document type definition module (DTD for short) 24.Information

The library interface module 25, the EDI interface module 26, and the like. The following describes the receiving and transmitting process of the XML / EDI object 3, and describes the functions of each module 20-26. When the EDI exchange server 1 or 2 receives the XML / EDI object 3, it is received by the receiving module 20. Processing, this receiving module 20 is used as the interface between the EDI exchange server 1 or 2 and the transmission network. Then, the parsing module 22 analyzes the XML / EDI object 3. Since the xML / edI object 3 is in the XML language format, the parsing module 22 will define the module 24 according to the file type. The definition of each tag in XML / EDI object 3 is analyzed. If the XML / EDI object 3 is an order, its XML language format is as follows: k &lt;? Xm1 version = &quot; 1.〇 &quot;? &Gt; iiMi mm page 8 4 44 彳 7 (5 Description of the invention (6) &lt;! DOCTYPE quotation SYSTEM &quot; quotation.dtd &quot; &gt; 〈quotation SenderName: &quot; III '丨〉 &lt; appno &gt; 000001 &lt; / appno &gt; &lt; s2 &gt; s2 &lt; / s 2 &gt; &lt; c2 &gt; c2 &lt; / c2 &gt; &lt; ex2 &gt; ex2 &lt; / ex 2 &gt; &lt; sender &gt; &lt; sendername &gt; xx &lt; / sendername &gt; &lt; senderaddr &gt; bb &lt; / senderaddr &gt; &lt; / sender &gt; &lt; rec ei ver &gt; &lt; receivernarae &gt; xx &lt; / receivernaine &gt; &lt; receiveraddr &gt; bb &lt; / receiveraddr &gt; &lt; / rece iver &gt; <detail> &lt; appnol &gt; &lt; 0000 + 1 ; &lt; productid &gt; ASIK01 &lt; / productid &gt; &lt; spec &gt; ASIK01 &lt; / spec &gt; &lt; a_qty &gt; 10 &lt; / a_qty &gt; 〈/ detail〉 &lt; / quot at i on &gt;

Page 9 4 4417 5. Description of the invention (7) The DTD of this order for the document type definition module 24 is as follows: &lt;? Xml encoding = &quot; US-ASCII &quot;? &Gt; &lt;! ELEMENT quotation

Cappno | s2 | c2 | ex2Isenderlreceiver I detail) wood &gt; &lt;! ATTLIST quotation DB CDATA #FIXED &quot; IIIBUYER &quot;

Table CDATA #FIXED &quot; BAPUR07M &quot; SenderName CDATA # REQUIRED &gt; &lt;! ELEMENT appno (#PCDATA) &gt; &lt;! ATTLI ST appno

Field CDATA #FIXED &quot; APP_NOn &gt; &lt;! ELEMENT s2 (#PCDATA) &gt; &lt;! ATTLIST s2

Field CDATA #FIXED &quot; S2n &gt; &lt;! ELEMENT c2 (#PCDATA) &gt; &lt; iATTLIST c2

Field CDATA #FIXED &quot; C2 &quot; &gt; &lt;! ELEMENT ex2 (#PCDATA) &gt; &lt;! ATTLIST ex2

Field CDATA #FIXED &quot; EX2 &quot; &gt; &lt;! ELEMENT sender (sendernameIsenderaddr) * &gt; &lt;! ATTLIST sender

Page 10 444 t 7 6 V. Description of the invention (8)

Table CDATA #FIXED &quot; BAPDROl &quot;

Sender CDATA «FIXED &quot; SUP_NO &quot; &gt; &lt;! ELEMENT sendername (#PCDATA) &gt; &lt;! ATTLIST sendername

Field CDATA #FIXED &quot; SUP_NAMEH &gt; &lt;! ELEMENT senderaddr (#PCDATA) &gt; &lt;! ATTLIST senderaddr

Field CDATA #FIXED &quot; SUP_ADDR &quot; &gt; &lt;! ELEMENT receiver (receivername | receiveraddr) ^ &gt; &lt;! ATTLIST receiver

Table CDATA #FIXED &quot; BAPUROl &quot;

Receiver CDATA #FIXED &quot; SUP_NO &quot; &gt; &lt;! ELEMENT receivername (#PCDATA) &gt; &lt;! ATTL I ST receivername

Field CDATA #FIXED &quot; SUP_NAME &quot; &gt; &lt;! ELEMENT receiveraddr (#PCDATA) &gt; &lt;! ATTLIST receiveraddr

Field CDATA #FIXED &quot; SUP_ADDR &quot; &gt; &lt;! ELEMENT detail (appnol | iteinno | productid | spec | a_qty) * &gt; 〈’· ATTLIST detail

Table CDATA #FIXED &quot; BAPUR07D &quot;

Foreign CDATA #FIXED Mappno &quot; &gt; &lt;! ELEMENT appnol (#PCDATA) &gt;

Page 11 444176 V. Description of the invention (9) &lt;! ATTLIST appnol

Field CDATA #FIXED &quot; APP_N0 &quot; &gt; &lt;! ELEMENT itemno (#PCDATA) &gt; &lt;! ATTL1ST itemno

Field CDATA #FIXED MITEM_N0 &quot; &gt; &lt;! ELEMENT productid (#PCDATA) &gt; &lt;! ATTLIST productid

Field CDATA #FIXED nPRODUCT_IDH &gt; &lt;! ELEMENT spec (#PCDATA) &gt; &lt;! ATTLIST spec

Field CDATA #FIXED &quot; SPEC &quot; &gt; &lt;! ELEMENT a ^ qty (#PCDATA) &gt; &lt;! ATTLIST a-qty

Field CDATA #FIXED &quot; A_QTY &quot; &gt; According to this, the parsing module 22 can add tags in XML / EDI object 3 (such as: appno, s2, c2, ex2, sendname, senderaddr 'r ece i vername, receiveraddr' appnol 'itemno' productid, spec, aqty, etc.), based on the DTD analysis of the module type definition module 24.

Since the XML / EDI data automatic conversion system of the present invention can achieve the purpose of EDI data exchange without changing the original MIS system 6 or 7. Therefore, the EDI interface module 26 will first define the EDI data format, attributes, etc. processed by the MIS system 6 or 7. Therefore, after the data interface 444 1 7 6 V. Invention description (10) Group 25 will convert the objects analyzed by the analysis module 2 2 according to the data of the ED I interface module 2 6 into the columns of the table type. Bit 'For example: The language structure for converting an order object into an order master table is as follows:

Drop Table BAPUR07M

Create Table BAPUR07M (/ * Requisition record master file / APP_N0 CHAR (8) NOT NULL, / Requisition order number APP_DATE CHAR (IO) NULL, / * Purchase date * / REQ_DATE CHAR (IO) NULL, / * Demand day * / 51 CHAR (12) NULL, / * Signed by the class leader * /

Cl CHAR (6) NULL, / * Lecturer's instructions / EX1 CHAR (40) NULL, / * Lecturer's approval instructions / 52 CHARC12) NULL, / * Manager's approval * / C2 CHAR (6) NULL, / * Manager Approval status wood / EX2 CHAR (40) NULL, / * Manager approves approval wood / ASTATUS CHAR (IO) NULL, / * Requisition status wood / SECT0R_ID CHAR (3) NULL, / * Department η code * / PERSON CHAR (5 ) NULL, / * clerk / ADDR CHAR (50) NULL, / * address * /

Primary Key Clustered (APP_N0

Page 13 ^ 44 ί 7 6

The language structure for converting an order item into an order detail table is as follows: 5. Description of the invention (π)

Drop Table BAPUR07D

Create Table BAPUR07D (/ * Purchase record details APP_N0 CHAR (8) NOT NULL, / * Shen Pei | Force Girl ITEM JO INT NOT NULL, / 氺 Item times ^) PRODUCT_ID CHAR (6) NULL, / * Item code wood / SPEC CHAR (8) NULL, specification 'A one QTY FLOAT NULL, / * repurchase quantity wood / ODR CHAR (l) NULL defaiilt (' F,), / wood order structure &quot; CONTENT CHAR (60) NULL, / Wood content wood /

Primary Key Clustered (APP_N0,

ITEM—NO Then ’stores the order master form and order detail form in the relational database 5 or 4. Therefore, the MIS system 6 or 7 can go to the photo library 5 or 4 to retrieve EDI data. T should be used as an EDI exchange server! Or 2 when you want to send XML / EDI object 3 崾 library interface module 25, after reading related data from the relational database 5 or 4

444? V. Description of the invention (12) The XML generation module 23 defines the module 24 according to the file type]) td to generate the corresponding object with the XML language format. Then, the transmission module 21 converts the XML / EDI object 3 Send it out. Therefore, the XML / EDI data automatic conversion system of the present invention, when the EM exchange server receives the XML / EDI object, it will automatically convert it into £ d I data ', which can be used without replacing the original MIS system. The purpose of the transmission of ed I data was obtained. In addition, the “xMl / EDI objects transmitted between the EDI exchange servers” is automatically and flexibly converted to XML data mode, which can efficiently process the exchange information and has the flexibility of data exchange. The second embodiment, please refer to FIG. 3, which is a block diagram of a second preferred embodiment of an automatic conversion system of xrjl / EDI data according to the present invention. The difference between this embodiment and the first embodiment lies in the relationship The databases 5 and 4 have XML data blocks 40 and 50, respectively. In this example, 'if EDI exchange servers 1 and 2 receive or transmit XML / EDI object 3', the received / transmitted XML / EDI object 3 is also stored in XML data blocks 40 and 50. Third Embodiment Please refer to FIG. 3, which is a block diagram showing a third preferred embodiment of an XML / EDI data automatic conversion system according to the present invention. The difference between this embodiment and the first embodiment is that the relational databases 5 and 4 have an XML data block 40 and 50 and an independent data block 42 and 52, respectively. Among them, if the EDI exchange servers 1 and 2 receive or transmit the XML / EDI object 3, the received / transmitted XML / EDI object 3 is also stored in the XML data blocks 40 and 50. In addition, the form objects processed by the analysis module 22 are stored in

0213-4499TWF.ptd Page 15 1 7 fi 5. Description of the Invention (13) The independent data blocks 42 and 52 are distinguished from those of other unparsed module 22 processors. According to the above-mentioned "the construction and application of the XML / ED I data automatic conversion system of the present invention", the purpose of data exchange can be obtained by passing XML objects without changing the original MIS system. Therefore, information agents can be used to automatically process XML documents and generate EDI data exchange messages. As a result, it not only solves the shortcomings of complex processing procedures, high costs, and limited data exchange standards in the past, but also takes the application of EDI on the Internet into a real-time data update and data independence field. Although the present invention has been disclosed in the preferred embodiment as above, it is not intended to limit the present invention. 'Any person skilled in the art can make changes and retouches without departing from the spirit and scope of the present invention. The scope shall be determined by the scope of the attached patent application.

Page 16

Claims (1)

444176 6. Scope of patent application 1. An XML / EDI data automatic conversion system, including: at least two exchange servers, with XML / EDI objects passed between them, each of the EDI exchange servers includes: a receiving module, which receives the XML / EDI object; a document type definition module with DTD data; and an analysis module that analyzes the XML / EDI object based on the DTD data, forms it into a database, and stores it in a database. 2 · The system as described in item} of the patent application scope, which still includes—a database interface module, responsible for the tabular processing. 3_ The system described in item 1 of the scope of patent application, wherein the database is a related database. 4. The system according to item 3 of the scope of patent application, wherein the correlation database has an XML data block for storing the XML / EM object. 05_As described in item 3 of the scope of patent application The system, wherein the relational database has an independent data block for storing the tabular data Q 6 · The system as described in item 1 of the scope of patent application, further comprising: an XML generation module 'from The database retrieves the required iED] [After the data ', the corresponding xml / EDI object is generated according to the DTD data; and a transmitting module transmits the corresponding XML / EDI object. 7_ — An XML / EDI data automatic conversion method suitable for passing XML / EDI objects between at least two exchange servers; the method includes the following steps: one of the exchange servers receives the XML / EDI objects; 44417S Analyze the xML / EDI object according to a DTD data; form the parsed XML / EDI object into a table; and store it in a database. 8_ The method as described in item 7 of the scope of patent application, wherein the database is a correlation database. 9. The method described in item 8 of the scope of patent application, wherein the correlation database has an XML data block for storing the XML / EDI object 10. The method described in item 8 of scope of patent application Method, wherein the relational database has an independent data block for storing the tabular data 〇11. The method described in item 7 of the scope of patent application 'still includes: retrieving from the database After the required EDI data ', generate a corresponding XML / EDI object based on the DTD data; and send the corresponding XML / EDI object out ° Page 18