JP2009217763A - Method, device and program for format conversion of edi system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem, wherein a request that it is of highest priority for distributing slip data cannot be responded in conventional EDI technologies, to make affairs more efficient and to enhance the reliability in an EDI system of distribution, or the like. <P>SOLUTION: In the EDI system, when format conversion processing is performed on electronic transaction data, presence/absence of unauthorized data in the electronic transaction data for format conversion is detected (step S705), when the unauthorized data is detected; the unauthorized data is removed from an object for the format conversion processing (step S712); and the electronic transaction data from which the unauthorized data is removed is output, by performing the format conversion (steps S703-S707, S702, S708, S709). <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an EDI (Electronic Data Interchange) system (electronic data conversion system), and more particularly to a technique suitable for improving the efficiency and reliability of operations such as distribution in an EDI system.

  Currently, in the EDI system, in order to be able to use a common slip data format for all business transactions, "message type", "message structure", "data item", "meaning of data item" and "data" The standardization ("Extensible Markup Language") format that standardizes "attributes" is performed.

  However, at present, for example, the data format used in the EDI system in the distribution industry varies depending on the business partner, such as XML, fixed length, CSV (Comma Separated Values) format, and the like. Therefore, in the distribution EDI center, when slip data is received from a business partner and transmitted to another business partner, it is necessary to convert the data into a different format for each business partner.

  Further, there are many cases in which a unique code is used for each business partner and the data notation format is different, and appropriate code conversion and data conversion must be performed as necessary.

  As described above, a format conversion mechanism for general-purpose slip data that is not limited to a specific business partner or data format is required.

  In order to correctly convert data in the format conversion system, it is assumed that the electronic transaction data before conversion is in the correct format. However, in the current situation where there is a case where a unique code is used for each business partner, since it is unique, there is a possibility that the mistake of the electronic transaction data creator for each company may occur, and setting unexpected data There may be a situation where the electronic transaction data is created in the state.

  In the case of data fraud at the time of creation of electronic transaction data, the EDI Center cannot correct the data, and it is necessary for the business partner to correct the data and retransmit the data. There will be a significant delay in arriving at.

  For example, Patent Literature 1 describes a technique for providing a format correction method in an electronic data conversion system and a data conversion method for re-execution of data conversion using the corrected format. In this technology, a flag is set for an illegal data portion, and normal data is reused after correcting illegal data, thereby reducing the time required for re-execution of data conversion.

  However, in the distribution EDI, there is a request that the highest priority is to distribute the slip data without stopping. Therefore, it is necessary to keep normal data as much as possible. Although the above-mentioned technology certainly shortens the time to correct and re-execute illegal data, the entire electronic transaction data including the normal data part is not output and transmitted due to the presence of some illegal data. , Business will be delayed.

  In this case, it is impossible to respond to the request that the distribution of slip data is the highest priority in the distribution EDI.

Japanese Patent Laid-Open No. 2001-60240

  The problem to be solved is that the prior art cannot respond to a request that distribution of slip data is the highest priority in distribution EDI, for example. That is, in the conventional technology, it is possible to improve the efficiency of debugging and shorten the time by transmitting the fact that illegal data exists to the data creator and reusing normal data. Because some data is not output and stays, business is delayed.

  An object of the present invention is to solve these problems of the prior art and to improve the efficiency and reliability of business in an EDI system such as distribution.

In order to achieve the above object, according to the present invention, illegal data and normal data are separated, and format conversion processing is executed only on the normal data portion and output. As a result, valid normal data can be transmitted to the business partner in real time, and only the illegal data portion needs to be corrected, reconverted and retransmitted, and it is possible to improve the operational efficiency of distribution EDI. .
That is, in the present invention, when format conversion processing is executed, the data after format conversion is not immediately output to a file, but temporarily stored in an internal memory. At that time, the range of data stored in the internal memory is limited to the range below the hierarchy that is to be discarded when an error occurs. Reading of the input file and storage in the memory are repeated, and the data in the stored range no longer contains invalid data. Output to a file when there is no possibility of mixing. As described above, normal data and illegal data can be separated without destroying the hierarchical structure of the slip data and without wasting the internal memory.
If invalid data exists, an item that can identify the illegal data location is extracted from the converted data stored in the memory, and is output to the error list file. Thereby, the position on the file where the illegal data exists can be easily specified even later.

  According to the present invention, only illegal data in distribution business or only a certain range of data including illegal data is excluded, normal data is converted and output as usual, and illegal data locations In the reality of the distribution EDI industry, delays in arrival of slip data to business partners can cause inconveniences such as missing items and excess inventory. Usable slip data can be transmitted in real time as much as possible, and it is only necessary to correct, reconvert, and retransmit only the illegal data portion, thereby improving business efficiency and improving reliability.

  The best mode for carrying out the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a configuration example of an EDI system provided with a format conversion apparatus according to the present invention, FIG. 2 is a block diagram showing a configuration example of a conversion processing unit in FIG. 1, and FIG. 4 is an explanatory diagram showing an example of illegal data detection processing procedure by the conversion processing unit in FIG. 4, FIG. 4 is an explanatory diagram showing an example of the hierarchical structure of data handled by the conversion processing unit in FIG. 1, and FIG. 5 is a conversion by the conversion processing unit in FIG. FIG. 6 is an explanatory diagram showing a first hierarchical structure example of data before and after processing, FIG. 6 is an explanatory diagram showing a second hierarchical structure example of data before and after the conversion processing by the conversion processing unit in FIG. 1, and FIG. 5 is a flowchart showing an example of a format conversion processing procedure according to the present invention of a conversion processing unit in FIG.

  An EDI system (described as “EDI center” in FIG. 1) 103 in FIG. 1 has a computer configuration including a CPU (Central Processing Unit), a main memory, a display device, an input device, and an external storage device. After the program and data recorded in a storage medium such as a CD-ROM are installed in the external storage device, the program is read from the external storage device into the main memory and processed by the CPU, thereby the data reception processing unit 104 and the present invention. The function of each processing unit of the conversion processing unit 105, the data transmission processing unit 106, and the communication unit (described as “communication” in the figure) 107 as the format conversion apparatus is executed.

  In the EDI system 103 of this example, when the electronic transaction data is subjected to the format conversion process by the conversion processing unit 105 as the format conversion apparatus of the present invention, the presence or absence of illegal data in the electronic transaction data to be converted is detected. When the unauthorized data is detected, the unauthorized data is removed from the format conversion target, and the electronic transaction data from which the unauthorized data is removed is format-converted and output.

  In addition, when the data processing including code conversion accompanying the format conversion of electronic transaction data is performed, the conversion processing unit 105 generates illegal data if there is data other than predetermined data in the data. It detects that it is.

  Further, the electronic transaction data has a hierarchical structure, and the conversion processing unit 105 removes the data in the lower layer of the illegal data together with the illegal data from the target of the format conversion process.

  Further, the conversion processing unit 105 temporarily accumulates data (normal data) whose format has been normally converted in a storage device, and all other data in the same hierarchy as the accumulated normal data is normal. After detection, normal data accumulated in the storage device is output as converted data.

  Furthermore, the conversion processing unit 105 generates and outputs list information (list) that identifies the detected illegal data.

  Details of the EDI system 103 that performs such processing will be described below.

  As shown in FIG. 1, the EDI system 103 and the computer terminal device of the business partner (1) 101 (described as “core system etc.” in the figure) 101a, and the EDI system 103 and the computer terminal device of the business customer (2) 102 (Denoted as “core system etc.” in the figure) 102a is connected by a network such as a public line via respective communication units (denoted as “communication” in the figure) 101b, 102b, 107, and electronic transaction data of each other. Send and receive.

  The EDI system 103 receives the electronic transaction data transmitted from the computer terminal device 101a of the business partner (1) 101 by the communication unit 107 and the data reception processing unit 104, and the business partner (2) 102 by the conversion processing unit 105. Is converted to a format used by the computer terminal device 102a, and is transmitted to the customer (2) 102 by the data transmission processing unit 106 and the communication unit 107.

  At that time, the conversion processing unit 105 detects whether or not unexpected illegal data is mixed in the electronic transaction data received from the computer terminal device 101a of the supplier (1) 101. Outputs the information specifying the unauthorized data to the file or the like as an error list 108, and transmits the electronic transaction data other than the illegal data portion to the computer terminal device 102a of the customer (2) 102.

  The output error list 108 is notified to the business partner (1) 101 by a method such as facsimile or electronic mail to the computer terminal device 101a. The customer (1) 101 who has received this error list 108 corrects the corresponding illegal data based on the illegal data location information described in the error list 108, and includes only the corrected data or a fixed data including the corrected data. The range data is transmitted again to the EDI system 103 by the computer terminal device 101a.

  When the correction data is received from the computer terminal device 101a, the EDI system 103 performs conversion processing into the format used by the customer (2) 102 by the conversion processing unit 105, and the computer terminal of the customer (2) 102 Transmission is performed to the device 102a, and a series of electronic transaction data relay processing is completed.

  The operation of the format conversion process in the EDI system 103 in FIG. 1 will be described in detail with reference to FIG.

  Currently, there are fixed-length format (fixed-length slip data file 210a), CSV format (CSV slip data file 211a), and XML format (XML slip data file 212a) as file formats of electronic transaction data used for distribution business. Even when the electronic transaction data in any file format is received from the computer terminal device 101a of the business partner (1) 101, the conversion processing unit 105 uses the format conversion program corresponding to each by the format conversion processing unit 200a. The intermediate common CSV data file 201 is converted in common, and the contents of the intermediate common CSV data file 201 are stored in the intermediate common CSV data database 202.

  Further, the format conversion processing unit 200b uses the corresponding format conversion program to convert the intermediate common CSV data file 201 into a file format used by the customer (2) 102, that is, a fixed length format (fixed length slip). Data file 210b), CSV format (CSV slip data file 211b), and XML format (XML slip data file 212b) are converted into one of them, and the computer terminal device 102a of the customer (2) 102 via the communication unit 107 The electronic transaction data whose format has been converted is transmitted.

  During the format conversion processing by the format conversion processing units 200a and 200b, the presence / absence of illegal data is detected, and information for identifying the detected illegal data is extracted and output as error list files 203a and 203b.

  Hereinafter, an outline of the illegal data detection process in the format conversion processing units 200a and 200b will be described with reference to FIG.

  As shown in FIG. 3, the electronic transaction data conversion process, that is, the conversion process from the pre-conversion format data 311 to the post-conversion format data 312 is performed by the format conversion program 303 by the data hierarchy structure of the electronic transaction data used for the conversion. In accordance with the setting contents of the hierarchy definition parameter file 301 that defines the data and the setting contents of the schema definition parameter file 302 that defines the correspondence between the slip item data in the electronic transaction data before and after conversion and the data editing procedure. Is called.

  If it is necessary to edit data such as data code conversion or numeric expression format conversion at the time of this format conversion, the format conversion is performed while appropriately calling the data editing module 304 having a data editing function necessary for distribution work. Execute.

  In this example, the typical case of judging that the electronic transaction data before conversion contains illegal data is when an unexpected code is included in the electronic conversion data before conversion at the time of data code conversion It is.

  Data code conversion is performed on the data editing module 304, and the data editing module 304 executes code conversion of data based on information in the preset code conversion table file 308. The code conversion table file If a code not set on 308 exists in the electronic transaction data before conversion, it is determined that the data is illegal data, and the illegal data existence notification 305 is displayed in the format that is the caller of the data editing module 304 Return to the conversion program 303.

  The format conversion program 303 that has received the unauthorized data existence notification 305 recognizes that the data currently being processed is unauthorized data, and extracts slip item data necessary to identify the unauthorized data from the electronic transaction data. Then, the data is listed as invalid data specifying information 306 and output to the error list file 307.

  Next, a skip process in units of hierarchies for illegal data detected during the format conversion process in the conversion processing unit 105 in the EDI system 103 will be described with reference to FIGS.

  First, as a premise for explaining skip processing in units of data hierarchies of format conversion processing at the time of detecting illegal data, the concept of the hierarchical structure of data in electronic transaction data will be explained using FIG.

  The data hierarchy is a data structure form in which a master-slave relationship is established between data and the data that are semantically related are grouped together. Normally, grouped data is allowed to appear multiple times as needed.

  The slip data used in the distribution business will be described as an example. As shown in FIG. 4, a slip header hierarchy 401, which is a group of data generated for each business partner, composed of a slip number, a business partner name, etc. It can be said that there is a slip specification hierarchy 402 that is a group of data generated for each product, which is composed of a specification number, a product name, a unit price, and the like.

  Basically, the slip header hierarchy 401 is allowed to appear multiple times (“slip header hierarchy 1”, “slip header hierarchy 2”,..., “Slip header hierarchy N”), and the same slip header hierarchy The slip detail hierarchy 402 is allowed to appear multiple times under “401” (“slip detail hierarchy 1”, “slip detail hierarchy 2”,..., “Slip detail hierarchy N”).

  However, although the slip header hierarchy 401 does not appear, the slip detail hierarchy 402 is not allowed to appear. The above is the basic concept of the hierarchical structure of data.

  Next, the unit of the data hierarchy to be skipped and discarded will be described with reference to FIGS.

  In FIG. 5, the hierarchy subject to data destruction is set to “slip detail hierarchy” or lower, and the data “507” of the item “reason for missing items” belonging to “slip detail hierarchy 4” indicated by reference numeral 506 is an incorrect value. An example is shown.

  First, the data belonging to “slip header hierarchy 1” 501 and the data belonging to “slip header hierarchy 1” 502 and “slip detail hierarchy 2” 503 having a relationship according to this “slip header hierarchy 1” 501 are normal. The format conversion process is performed, and the file is output as data belonging to “slip header hierarchy 1” 509 and “slip detail hierarchy 1” 510 and “slip detail hierarchy 2” 511 according thereto.

  Next, if the “missing part reason data” 507 is an invalid value, all data belonging to the “slip detail hierarchy 4” 508 becomes unusable for business, so that the “slip detail hierarchy 4” 506 itself is unnecessary. Become.

  Accordingly, the data belonging to “slip header hierarchy 2” 504 and the data belonging to “slip header hierarchy 2” 504 having the relationship according to “slip header hierarchy 2” 504 are normally subjected to format conversion processing and output as a file. However, all the data belonging to “slip detail hierarchy 4” 506 is discarded without being output to the converted file.

  Then, the data after “slip header hierarchy 3” 508 is normally subjected to format conversion processing. Finally, all data after format conversion except for data belonging to “slip description hierarchy 4” 508 is output as a file.

  On the other hand, FIG. 6 shows an example in which the hierarchy to be discarded is set to the slip header hierarchy or lower and “delivery classification data” 606 belonging to “slip header hierarchy 2” 604 has an invalid value. It is shown.

  First, the data belonging to “slip header hierarchy 1” 601 and the “slip detail hierarchy 1” 602 and the data belonging to “slip detail hierarchy 2” 603 having a relationship according to this “slip header hierarchy 1” 601 are: Then, the format conversion process is normally performed, and the file is output as data belonging to “slip header hierarchy 1” 609, “slip detail hierarchy 1” 610, and “slip detail hierarchy 2” 611 according thereto.

  On the other hand, if the “delivery category data” 606 is an invalid value, all data belonging to the “slip header hierarchy 2” 604 becomes unusable for business, so the “slip header hierarchy 2” 604 itself is unnecessary. Accordingly, the “slip detail hierarchy 3” 606 and the “slip detail hierarchy 4” 607 are not required.

  Therefore, all the data belonging to “slip header hierarchy 2” 604 and all the data belonging to “slip detail hierarchy 3” 605 and “slip detail hierarchy 4” 607 having a relationship according to “slip header hierarchy 2” 604. Is discarded without being output to the file after conversion.

  The data after “slip header hierarchy 3” 608 is normally subjected to format conversion processing. Finally, the data belonging to “slip header hierarchy 2” 604 and the relationship according to “slip header hierarchy 2” 604 are obtained. All data after format conversion except for data belonging to a certain “slip detail hierarchy 3” 605 and “slip detail hierarchy 4” 607 is output as a file.

  If invalid data exists in a hierarchy higher than the set data discard target hierarchy, the format conversion process itself is stopped when the invalid data is detected as a format conversion process error.

  For example, in FIG. 5, when the data discard target hierarchy is set to be lower than the slip detail hierarchy, and “delivery classification data” 515 belonging to the slip header hierarchy positioned higher than that is an invalid value, At this point, the format conversion process is stopped, and the process ends without executing the format conversion process for data that appears after the “slip header hierarchy 2” 504.

  As described above, in the data discarding process in units of data hierarchies, if one or more data frauds exist in a hierarchy, the data belonging to that hierarchy and the data belonging to the hierarchy following that hierarchy are integrated. By discarding all of them, it is possible to prevent the occurrence of inconsistencies in the data structure and the like, and to maintain the validity of the data structure even after discarding illegal data.

  Next, a skip process and a discard process for each data layer in the format conversion process at the time of detecting illegal data will be described with reference to FIG.

  First, one line of data is read from the pre-conversion data (step S701), and it is determined whether or not the read data is data located in a hierarchy lower than the illegal data discard target hierarchy specified by the user (step S701). Step S702).

  If the data is located in a hierarchy lower than the illegal data discarding target hierarchy, the process proceeds to step S703. If the data is located in a hierarchy higher than the illegal data discarding target hierarchy, the process proceeds to step S708. Here, the concept of the hierarchy to be used is determined based on the contents set in the hierarchy definition parameter file.

  In step S703, the format conversion process is performed on the pre-conversion data based on the contents set in the hierarchy definition parameter file and the schema definition parameter file. If data value editing is necessary, data editing processing is performed according to the setting contents of the schema definition parameter file (step S704).

  It is determined whether or not illegal data is detected during the data editing process (step S705). If invalid data is not detected, the converted data is stored in the internal memory for storing the converted data (cache memory, main memory, etc.). Then, the data is written to a storage device that is directly accessible from the CPU (step S706).

  In the process of step S706, output to a file is not performed. This is because at the time of the process of step S706, it is not yet determined that illegal data is not mixed in the hierarchy currently being processed, and at the time of this process, the data is stored in units of one line of the pre-conversion data file. When file output is performed, invalid data of the same level appears later, and even if all data file output of the layer being processed becomes unnecessary, the data has already been output to the file. Because it becomes.

  Therefore, when the converted data is actually output to the file, in the determination process in step S702, one line of the pre-conversion data read in the process in step S701 is the same hierarchy as the discard target hierarchy specified by the user, or If the data is located in a higher hierarchy, that is, the stage in the process of step S708.

  If illegal data is detected in the process of step S705, data necessary for specifying the location of the illegal data is acquired from the contents of the converted data (step S710). Note that the data necessary for specifying the location of the illegal data is determined in advance between the EDI center and the business partner, and the determined data is acquired from the converted data.

  The illegal data specifying information acquired in step S710 is output to the error list file (step S711). Then, the converted data including the illegal data for which the error list is output is discarded (step S712). That is, with respect to the post-conversion data including illegal data, neither data writing nor file output to the internal memory for storing post-conversion data is performed as in the processing in step S706.

  After discarding the converted data in step S712 or accumulating the converted data in the internal memory in step S706, the presence of unprocessed data is confirmed (step S707). Then, the process proceeds to the process of step S701, and the next line before conversion is read. If it does not exist, the series of format conversion processes is terminated as it is.

  In step S708, all the contents of the internal memory for storing the converted data are output as a file, and then in step S708, the contents of the internal memory for storing the converted data are deleted.

  As described above with reference to FIGS. 1 to 7, in this example, in the format conversion process of the EDI system, illegal data and normal data are separated, and the format conversion process is executed on only the normal data part and output. To do. As a result, valid normal data can be transmitted to the business partner in real time, and only the illegal data portion needs to be corrected, reconverted and retransmitted, and it is possible to improve the operational efficiency of distribution EDI. .

  More specifically, when the format conversion process is executed, the data after the format conversion is not immediately output to a file, but temporarily stored in the internal memory. At that time, the range of data stored in the internal memory is limited to the range below the hierarchy that is to be discarded when an error occurs. Reading of the input file and storage in the memory are repeated, and the data in the stored range no longer contains invalid data. Output to a file when there is no possibility of mixing. Thereby, normal data and illegal data can be separated without destroying the hierarchical structure of the slip data and without wasting the internal memory. If invalid data exists, an item that can identify the illegal data location is extracted from the converted data stored in the memory and output to the error list file. Thereby, it is possible to easily specify the position on the file where the illegal data exists even later.

  As described above, according to this example, only data that is illegal in distribution business or a certain range of data including illegal data is excluded, normal data is converted and output as usual, and illegal data is output. In the reality of the distribution EDI industry, delays in arrival of slip data to business partners can lead to inconveniences such as missing items and excess inventory by providing information that identifies data locations. The voucher data that can be used can be transmitted in real time as much as possible, and only the illegal data part needs to be corrected, reconverted, and retransmitted, improving the efficiency of business and improving the reliability. .

  In addition, this invention is not limited to the example demonstrated using FIGS. 1-7, A various change is possible in the range which does not deviate from the summary. For example, in this example, an EDI system that performs format conversion processing of electronic transaction data having slip information of a distribution business has been described as an example. However, an EDI system that performs format conversion processing of electronic transaction data in other industries is described. Also good.

  The computer configuration example of this example may also be a computer configuration without a keyboard or optical disk drive. In this example, an optical disk is used as a recording medium. However, an FD (Flexible Disk) or the like may be used as a recording medium. As for the program installation, the program may be downloaded and installed via a network via a communication device.

It is a block diagram which shows the structural example of the EDI system which provided the format conversion apparatus which concerns on this invention. It is a block diagram which shows the structural example of the conversion process part in FIG. It is explanatory drawing which shows the example of an unauthorized data detection process procedure by the conversion process part in FIG. It is explanatory drawing which shows the hierarchical structure example of the data handled by the conversion process part in FIG. It is explanatory drawing which shows the 1st hierarchical structure example of the data before and behind the conversion process by the conversion process part in FIG. It is explanatory drawing which shows the 2nd hierarchical structure example of the data before and behind the conversion process by the conversion process part in FIG. It is a flowchart which shows the example of a format conversion process procedure which concerns on this invention of the conversion process part in FIG.

Explanation of symbols

101: Customer (1), 101a, 102a :.
101b, 102b: communication unit,
103: EDI system 104: Data reception processing unit 105: Conversion processing unit (format conversion apparatus) 106: Data transmission processing unit 107: Communication unit 108: Error list 200a, 200b: Format conversion processing unit 201 : Intermediate common CSV data file, 202: intermediate common CSV data database, 203a, 203b: error list file, 210a, 210b: fixed length slip data file, 211a, 211b: CSV slip data file, 212a, 212b: XML slip data File, 301: hierarchy definition parameter file, 302: schema definition parameter file, 303: format conversion program, 304: data editing module, 305: invalid data existence notification, 306: illegal data specifying information, 30 : Error list, 308: Code conversion table file, 311: Format data before conversion, 312: Format data after conversion successfully converted, 401: Slip header hierarchy (1) to (N), 402: Slip detail hierarchy (1 ) To (N), 501: slip header hierarchy (1), 502: slip detail hierarchy (1), 503: slip detail hierarchy (2), 504: slip header hierarchy (2), 505: slip detail hierarchy (3) 506: slip detail hierarchy (4), 507: reason for missing item (illegal data), 508: slip header hierarchy (3), 509: slip header hierarchy (1), 510: slip detail hierarchy (1), 511: slip Detail hierarchy (2), 512: slip header hierarchy (2), 513: slip detail hierarchy (3), 514: slip header hierarchy (3), 601: slip header hierarchy (1), 602: slip detail hierarchy ( ): 603: slip detail hierarchy (2), 604: slip header hierarchy (2), 605: slip detail hierarchy (3), 606: delivery category (incorrect data), 607: slip detail hierarchy (4), 608: slip Header hierarchy (3), 609: slip header hierarchy (1), 610: slip detail hierarchy (1), 611: slip detail hierarchy (2), 612: slip header hierarchy (3).

Claims (7)

A format conversion processing method for an EDI system in which electronic transaction data is subjected to format conversion processing and relayed to a network by programmed computer processing,
As a programmed computer processing execution procedure,
A first procedure for detecting the presence or absence of unauthorized data in electronic transaction data subject to format conversion;
A second procedure for removing illegal data from the target of format conversion processing when illegal data is detected in the first procedure;
A format conversion method for an EDI system, comprising: a third procedure for converting the format of electronic transaction data from which illegal data has been removed in the second procedure and outputting the data. A format conversion method for an EDI system according to claim 1,
In the first procedure,
When performing data editing processing including code conversion accompanying the format conversion of the electronic transaction data, if there is data other than predetermined data in the data, detecting that the data is invalid A format conversion method for an EDI system. A method for converting the format of an EDI system according to claim 1 or 2,
The electronic transaction data has a hierarchical structure,
In the second procedure, a format conversion method for an EDI system is characterized in that, together with the illegal data, data in a lower layer of the illegal data is removed from the target of format conversion processing. A format conversion method for an EDI system according to claim 3,
As a programmed computer processing execution procedure,
A procedure for temporarily storing the data subjected to format conversion in the third procedure as normal data in a storage device;
And a procedure for outputting normal data stored in the storage device as converted data after all the other data in the same hierarchy as the stored normal data is detected to be normal by the first procedure. A format conversion method for an EDI system. A method for converting the format of an EDI system according to any one of claims 1 to 4,
As a programmed computer processing execution procedure,
A format conversion method for an EDI system, including a procedure for generating and outputting list information for specifying illegal data detected in the first procedure.   The program for making a computer perform each procedure in the format conversion method of the EDI system in any one of Claims 1-5. By programmed computer processing
A format conversion device of an EDI system that relays electronic transaction data having slip information of a distribution business by performing format conversion processing,
As programmed computer processing execution means
6. An EDI system format conversion apparatus comprising means for executing each procedure in the EDI system format conversion method according to claim 1.

Images