JP2004355382A - Edi exchange method and edi data distribution management server device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a self-institution which receives and deals with EDI(Electronic Data Interchange) data where even when the configuration of the dealing processor is changed, it is not necessary for other organization which transmits the EDI data to change the transmission destination of the EDI data. <P>SOLUTION: An EDI data distribution management server device 5 which receives and deals with EDI data decodes a business message in the received EDI data, and refers to a distribution management table storage part 10 in which transmission destination information is stored according to at least one of the data of a transmission origin enterprise code, transaction classification code and business message contents acquired by decoding in order to decide the transmission destination of the business message based on the reference result. Also, the EDI data distribution management server device reconfigures the business message as the EDI data according to the decided transmission destination. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
According to the present invention, even if the configuration of a processing device for handling EDI data is changed in the own organization receiving and handling the EDI data, the other organization sending the EDI data can change the transmission destination of the EDI data and the like. The present invention relates to an EDI exchange method, an EDI data distribution management server device, and a computer program related to the EDI exchange method and the EDI data distribution management server device, which can eliminate the necessity of performing.
[0002]
[Prior art]
It is common practice to convert information into electronic data between different organizations and to exchange information using a network. As a specific example, there is an electronic commerce system in which a request for quote and a reply to the quote are converted into EDI (Electronic Data Interchange) data, and the data is transmitted and received using a network such as the Internet.
[0003]
When constructing such an electronic commerce system, exchange of EDI data between a plurality of companies in accordance with the agreed syntax rules and "EIAJ Transactions" issued by the Japan Electronic Machine Manufacturers Association EDI Promotion Center A center server device as described in "Informatization-compatible standard" is used. Here, the center server device corresponds to a computer device installed by an intermediary company such as a VAN company, and has a function of mediating EDI data exchange between a source company and a destination company. have.
[0004]
FIG. 1 is a block diagram showing a general electronic transaction system.
[0005]
This figure shows the configuration before the equipment configuration change of the office or factory described later shown in FIG. 3. Reference numeral 1 denotes an EDI data processing device arranged in each company 3. In particular, the EDI data processing device 1 is assigned to the company A as the device A, and the EDI data processing device 1 assigned to the company B as the device B. In the following description, similar symbol names will be given to distinguish the respective companies 3 and the respective EDI data processing devices 1 as appropriate, such as A and B.
[0006]
FIG. 2 is a diagram showing a conventional distribution management table provided on the transmission side.
[0007]
When electronic commerce is performed between the company B and the company A, the EDI data processing device B determines the EDI data processing device A as the transmission destination device from the destination company code and the transaction type code recorded in the distribution management table. decide. Then, the EDI data is transmitted to the destination device.
[0008]
Here, in the company A, organizational changes such as expansion, reduction, or movement of the EDI data processing device 1 and the like may occur due to the reorganization, expansion, or reduction of offices and factories. Such a change is hereinafter simply referred to as an organization change.
[0009]
In the case where such an organization change has occurred, it is conventionally dealt with by changing a supplier table in which the supplier code and the receiver code of the company B are registered. Further, in a business partner other than the company B, it is necessary to synchronously perform the same table change operation. Further, in the method based on this table change, the transmission destination is determined by the business reception destination company code and the transaction type code registered in the transmission destination table, and therefore, it is usually not distributed depending on the contents of the business message.
[0010]
FIG. 3 is a block diagram showing the office A and the factory in the company A after changing the equipment configuration. FIG. 4 is a diagram showing a distribution management table provided on the transmission side after the equipment configuration change.
[0011]
In FIG. 3, after the equipment configuration is changed, in the company A, in addition to the conventional device A, a device A1 and a device A2 are newly installed. The company B needs to change the distribution management table of FIG. 3 as shown in FIG. 4 in response to such an organization change of the company A. The EDI data processing device 1 other than the company B also needs to be changed. In all cases where the center server method is not adopted, it is necessary to change the distribution management table of the client company.
[0012]
Further, in the distribution management table of FIG. 4, all the confirmed orders are transmitted to the EDI data processing device A1, and the confirmed orders are not transmitted to the EDI data processing device A2. Conventionally, when it is necessary, the EDI data is transferred from the EDI data processing device A1 to the EDI data processing device A2 by taking a complicated procedure shown in FIG. However, the transfer requires useless translation processing, and thus has a problem in that the load on the processing device increases. Further, since the map to be used is not the same as the EDI data processing apparatus B which is the transmission source, there are many problems such that there is no guarantee that the EDI data processing apparatus B accurately agrees with the original EDI data.
[0013]
In Patent Document 1, although a center server is used, a distribution management table is provided on the transmission source side in the same manner as in the above-described conventional example. Further, the same processing as in the above-described conventional example is performed on the transmission side and the center server.
[0014]
[Patent Document 1]
JP 2000-156703 A
[0015]
[Problems to be solved by the invention]
Such a conventional method has the following problems. That is, when a certain source organization and a destination organization intend to send and receive EDI data having a plurality of business messages, the EDI data processing device 1 of the business partner company has a set of transaction type codes corresponding to the transaction data in advance. It must be registered in the distribution management table.
[0016]
In particular, in a large company having many offices and factories, it is common to perform data processing in different offices and factories, that is, different EDI data processing apparatuses 1 for each type of transaction such as a quote request and a firm order. And the configuration may be changed. Therefore, due to the consolidation or reorganization of offices and factories in one company that conducts e-commerce, the number of sets of transaction type codes for which a business relationship is established will increase or decrease. It is necessary to update the contents of the distribution management table of the EDI data processing apparatus 1.
[0017]
In the distribution management table of FIG. 4, the EDI data processing device names corresponding to the offices and factories of the receiving company A are associated with each transaction type code. Every time the establishment or factory of the receiving company A is reorganized, it is necessary to correct the contents of the distribution management table. As described above, the EDI data source company and the center server must always be aware of where to send the EDI data to the establishment or factory of the destination company.
[0018]
In addition, even with the same transaction type code, the detailed business message content associated therewith generally has various patterns. For example, in the case of a firm order code, which is one of the transaction type codes, various kinds of merchandise types to be firmly ordered can be considered. It is fully conceivable that the company receiving the quote request will need to process the quote request data in a different department for each product, that is, in a different EDI data processing device 1. However, in the related art, since the EDI data processing device 1 to which the EDI data is to be distributed is specified only by the estimate request code, the EDI data processing device 1 suitable for processing the estimate request data of each product is provided. It was impossible to identify. According to the contents of the distribution management table in FIG. 5, all the EDI data having the confirmed order code 0002 is distributed to the same EDI data processing device A1 of the company A.
[0019]
SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned conventional problems, and the EDI system transmits EDI data even when the configuration of a processing device for handling the EDI data is changed in the own organization that receives and handles the EDI data. It is an object of the present invention to provide an EDI exchange method and an EDI data distribution management server device that can eliminate the need to change the destination of EDI data or the like in another organization on the side.
[0020]
It is to be noted that an additional object of the present invention is to separately install a local server device which is a direct contact point of EDI data exchange with a business partner company, thereby hierarchically laying out the contents of the distribution management table, and establishing a business establishment of the own company or An object of the present invention is to realize transmission and reception of a plurality of EDI data without making a business partner company aware of a factory configuration. Another object of the present invention is to reconstruct a plurality of EDI data received at one time as a correct EDI data format even if the EDI data is divided for each EDI data processing device 1. Further, the purpose is to specify the EDI data processing device 1 to which EDI data is to be distributed based not on the transaction type code itself but on the business message content itself.
[0021]
[Means for Solving the Problems]
First, the EDI exchange method according to the first invention of the present application, on the side of receiving and handling EDI data, decodes a business message in the received EDI data, and obtains the source company code, transaction type code, and transaction type code obtained by the decoding. At least one of the business message content data refers to a distribution management table storing destination information, and a distribution analysis procedure for determining a destination of the business message based on the reference result. The procedure for reconstructing the business message as EDI data according to the transmission destination, and in the case of adding or changing equipment on the reception handling side, it is necessary to change the setting by adding or changing the EDI data to the other party transmitting the EDI data. By solving the problem, the above-mentioned problem is solved.
[0022]
In the EDI exchange method, at least one of data of a source company code, a destination company code, a transaction type code, and a business message content obtained by decoding a business message in the received EDI data. By having a procedure for retrieving the aggregation management table by one and performing aggregation according to the search result for each content of the business message in the aggregation management table, the above problem can be solved and the result collection for each content of the business message can be performed. Aggregation can be performed. According to the totaling result, by grasping the respective load amounts of the destinations of the business message of the reconstructed EDI data, it is possible to prevent the operation of each device from being congested due to overload. Useful information can be provided.
[0023]
Further, in the EDI exchange method, when transmitting the EDI data, a business message in the EDI data is decrypted, and a source company code, a destination company code, a transaction type code, and a business message obtained by the decryption are obtained. By providing a procedure for searching the total management table based on at least one of the data of the contents and performing the total according to the search result for each content of the business message in the total management table, the above-mentioned problem can be solved and EDI can be performed. Regarding data transmission, the result collection can be totaled for each business message content. According to the totaling result, by grasping the respective load amounts of the destinations of the business message of the reconstructed EDI data, it is possible to prevent the operation of each device from being congested due to overload. Useful information can be provided.
[0024]
Further, in the EDI exchange method, the reconstructing procedure is a procedure of reassembling EDI data by collecting a plurality of business messages of the same destination as one EDI data. It is possible to improve the processing efficiency at the destination of the data business message.
[0025]
Next, the EDI data distribution management server device of the second invention of the present application, on the side receiving and handling the EDI data, decodes the business message in the received EDI data, and obtains the source company code and the transaction obtained by the decoding. A distribution analysis unit that refers to a distribution management table storing transmission destination information based on at least one of the type code and the data of the business message content, and determines the transmission destination of the business message based on the reference result. And a business message reconstructing unit that reconstructs a business message as EDI data according to the determined transmission destination, and is provided on the side that receives and handles the EDI data. Things.
[0026]
Further, a computer program according to a third invention of the present application provides a computer program for implementing the EDI exchange method according to the first invention or the EDI data distribution management server device according to the second invention. Thus, the above problem has been solved.
[0027]
Hereinafter, the operation of the present invention will be briefly described.
[0028]
According to the present invention, on the side of receiving and handling EDI data, first, as a distribution analysis procedure, a business message in the received EDI data is decoded. Then, at least one of the source company code, transaction type code, and business message content data obtained by the decryption refers to the distribution management table storing the destination information, and based on the reference result. To determine the destination of the business message.
[0029]
As a subsequent rebuilding procedure, the business message is rebuilt as EDI data in accordance with the determined destination.
[0030]
Therefore, even if the organization change occurs on the side receiving and handling the EDI data, the countermeasure for the organization change can be performed on the side receiving and handling the EDI data. Further, it is easy to change the distribution of the received business message on the side receiving and handling the EDI data, and it is possible to cope with complicated distribution.
[0031]
As described above, according to the present invention, even if the structure of the processing apparatus for receiving and handling the EDI data is changed in the own organization receiving and handling the EDI data, the EDI data is transmitted to the other organization sending the EDI data. It is possible to eliminate the need to change the transmission destination or the like.
[0032]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
[0033]
FIG. 6 is a block diagram showing the configuration of the first embodiment to which the present invention is applied.
[0034]
As shown in this figure, in the present embodiment, a plurality of EDI data processing apparatuses 1, that is, processing apparatuses A, A1, and A2 are provided in a company A that receives EDI data. Further, an EDI data management server device 5 to which the present invention is applied is provided. The EDI data processing device 1 and the EDI data management server device 5 constitute a computer system in the organization of the company A.
[0035]
Then, EDI data sent from a source of another organization such as the company B is once received by the EDI data management server device 5. The EDI data management server device 5 functions as a reception window for receiving EDI data from others. The EDI data management server device 5 has a distribution management table, and functions as a replacement computer device by using the distribution management table. Also, the EDI data management server device 5 processes the received EDI data and distributes the processed EDI data to its own EDI data processing device 1.
[0036]
FIG. 7 is a block diagram showing the configuration of the EDI data management server device used in the present embodiment.
[0037]
In this figure, the EDI data distribution management server device 5 includes a distribution management table storage unit 10 provided with a distribution management table, a business message receiving unit 20, a business message decomposing unit 22, a distribution analysis unit 24, a business It has a message reconstructing unit 26 and a business message transmitting unit 28. The distribution management table records a set of EDI data items and business message contents, and a distribution destination organization associated with the set.
[0038]
FIG. 8 is a flowchart showing processing performed in the EDI data distribution management server device 5 of the present embodiment.
[0039]
First, in step 212, the business message receiving unit 20 receives a business message from the outside.
[0040]
In step 214, the business message disassembly unit 22 receives the data file for the own organization received from another organization such as the company B from the business message reception unit 20. Further, the business message decomposing unit 22 decomposes a plurality of business messages included in the data file into individual business messages according to a predetermined EDI format.
[0041]
In step 216, the distribution analysis unit 24 analyzes the business message according to a predetermined EDI format and distributes the business message to each EDI data processing device 1 of the client in the own organization. Specifically, the distribution analysis unit 24 reads EDI data items such as a source organization code, a destination organization code, a transaction type code, and a business message content from the business message decomposed by the business message decomposing unit 22. Then, the distribution analysis unit 24 collates the read EDI data items with the contents of the distribution management table, and outputs information on the distribution destination (distribution destination organization) associated with the EDI data items in the distribution management table. The business message is obtained and distributed to the EDI data processing device 1 in the own organization according to the information. Further, the distribution analysis unit 24 classifies the business message for each distribution destination (distribution destination organization).
[0042]
In step 218, the business message restructuring unit 26 collects the business messages classified for each distribution destination (distribution destination organization) and reconstructs them into an EDI data format that can be processed by the EDI data processing device 1. Specifically, the business message restructuring unit 26 reconstructs the decomposed individual business messages according to a message group header and a message group trailer, and returns the business message to a predetermined EDI format.
[0043]
In step 220, the business message transmitting unit 28 transmits the reconstructed business message to the EDI data processing device 1 in the own company.
[0044]
9 to 11 are diagrams showing predetermined EDI formats assumed for describing the present embodiment. Although FIGS. 9 to 11 are originally one diagram, they are exploded into three diagrams for the sake of drawing the application. 9 follows the lower part of FIG. 9, and the lowermost line in FIG. 9 and the uppermost line in FIG. 10 are overlapped in the drawing, and they are the same line. In addition, FIG. 11 is continued below in FIG.
[0045]
The EDI format of the EDI data example shown in these figures has a source company code, a destination company code, a transaction type code, a business message content, and the number of business messages for each transaction type code. The business message content is one request for quote and three confirmed orders.
[0046]
In the EDI data structure, a plurality of business message data are surrounded by a pair of one message group header and message group trailer, thereby forming a business message group.
[0047]
This structure is based on the CII syntax rules defined by the Japan Information Processing Development Association, and the basic structure is shown in FIG.
[0048]
FIG. 13 is a diagram showing the contents of the distribution management table of the present embodiment.
[0049]
In the table of this figure, a source company code, a destination company code, and a transaction type code correspond to a sender code, a receiver code, and an information classification code in the EDI data of the present embodiment, respectively. The message content comparison item indicates a comparison item of the EDI data indicated by the data tag.
[0050]
In the table shown in the figure, EDI data in which the items of the source company code, the destination company code, and the transaction type code are “222222222222”, “111111111111”, and “0001”, respectively, are distributed to the EDI data processing apparatus A. . The items of the source company code, the destination company code, and the transaction type code are “222222222222”, “111111111111”, and “0002”, respectively, and the data tag is “10”, that is, the product type is “X” or “Z”. The EDI data "" is distributed to the EDI data processing device A1. The items of the source company code, the destination company code, and the transaction type code are “222222222222”, “111111111111”, “AAAAAAA”, and “0002”, respectively, and EDI data whose product type is “Y” is EDI. It is indicated that the data should be distributed to the data processing device A2.
[0051]
It is assumed that the company B transmits the EDI data shown in FIGS. First, EDI data is transmitted from the company B to the company A. At this time, the company B does not need to recognize the configuration of the EDI data processing device 1 of the company A, and transmits the data to the representative EDI data processing device 1 of the company A.
[0052]
The transmitted EDI data is received by the business message receiving unit 20 of the EDI data distribution management server device 5, which is the representative EDI data processing device 1 of the company A.
[0053]
The business message decomposing unit 22 receives the EDI data from the business message receiving unit 20, and decomposes the EDI data into a plurality of business messages according to a predetermined EDI format.
[0054]
FIG. 15 is a flowchart showing the procedure of the disassembly in the business message disassembly unit 22. FIG. 14 is a diagram showing the decomposed EDI data.
[0055]
More specifically, the business message disassembly unit 22 extracts a message header (Step 250), a message (Step 260), and a message trailer (Step 254) from a business message group including one or more business messages that are EDI data. . Further, for each individual business message included in the business message group, a message header and a message trailer information are generated and added, and decomposed in business message units (step 256).
[0056]
FIG. 16 is a flowchart illustrating a procedure of distribution analysis in the distribution analysis unit 24.
[0057]
The distribution analysis unit 24 first acquires the EDI data item of the target business message group (step 282). Next, a sender code, a receiver code, an information division code, and a product type required for matching are read from the distribution management table in accordance with a predetermined EDI format (step 284). Also, the distribution analysis unit 24 collates the acquired EDI data item with the contents of the distribution management table, and acquires information indicating the distribution destination stored in the distribution management table in association with the EDI data item. (Step 286). Then, the distribution analysis unit 24 determines the distribution to the in-house EDI data processing device 1 (step 290).
[0058]
For example, in the first business message in FIG. 14, the items of the source company code, the destination company code, and the transaction type code are “222222222222”, “111111111111”, and “0001”, respectively. Then, the EDI data processing device 1 that corresponds to the first set of the distribution management table in FIG. 13 and that is to be transmitted is “A”.
[0059]
In the second business message, the items of the source company code, the destination company code, and the transaction type code are “222222222222”, “111111111111”, and “0002”, respectively, and the product type is the product “X”. . Then, the EDI data processing device 1 corresponding to the second set of the distribution management table and to be transmitted is “A1”.
[0060]
In the third business message, the items of the source company code, the destination company code, and the transaction type code are “222222222222”, “111111111111”, and “0002”, respectively, and the product type is the product “Y”. . Then, the EDI data processing device 1 that corresponds to the third group of the distribution management table and is to be transmitted is “A2”.
[0061]
In the fourth business message, the items of the source company code, the destination company code, and the transaction type code are “222222222222”, “111111111111”, and “0002”, respectively, and the product type is the product “Z”. . Then, the EDI data processing device 1 corresponding to the second set of the distribution management table and to be transmitted is “A1”.
[0062]
At this point, if a reception acknowledgment message is required to notify whether or not a business message that can be interpreted in a predetermined EDI data exchange operation format has been received, a business message is created in accordance with the predetermined EDI format, Reply to
[0063]
FIG. 18 is a flowchart illustrating a procedure of the business message restructuring distribution analysis in the business message restructuring unit 26.
[0064]
The business message restructuring unit 26 edits a message group header and a message group trailer of each business message distributed for each EDI data processing apparatus 1 in the own organization, and converts the edited message into a predetermined EDI format.
[0065]
First, in step 312, information about a business message group to be reconstructed is obtained, and a message group header and a message group trailer of each business message included in the business message group are obtained. In steps 314 to 318, a process of collecting a plurality of business messages having the same destination as one EDI data is performed. In steps 320 to 324, the creation date and time of the compiled EDI data is obtained, the final sequence number and the hash total value are calculated, and the creation date and time, the final sequence number and the hash total value of the EDI data are calculated accordingly. Update.
[0066]
When the predetermined EDI data is CII, the correct EDI format cannot be recognized unless the final sequence number and the hash total number, which means the number of business messages included, are recalculated. The recipient code and the date and time of creation can be changed according to the operational rules. In this example, the creation date and time is the time when the business message is reconstructed, and the recipient code is not changed.
[0067]
The business messages that have the same distribution destination in the business message restructuring unit 26 and have the same business message group at the time of reception are combined again, and the combined business message groups are sequentially processed. The second business message, ie, message 2-1 and the fourth business message, ie, message 2-3 in FIG. FIG. 17 shows EDI data synthesized for each distribution destination.
[0068]
The business message distributed to the EDI data processing apparatus A in FIG. 17 changes the creation date and time of the message group header to the processing time. If it is 00:00:00 on January 1, 2003, it is “030101000010”. Since the number of business messages is “1”, the final sequence number is “1”.
[0069]
Since the first total item Nol of the message group header is “020”, the data of the items of the quantity whose data tag is “20” is totaled, and the hash total 1 becomes “1000”.
[0070]
Similarly, the business message distributed to the EDI data processing device A1 has a creation date and time of “030101000010”, a final sequence number of “2”, a hash total 1 of “1000” of the message 2-1 and a message 2-3. Is "3000" in total. The business message distributed to the EDI data processing device A2 has a creation date and time of “030101000010”, a final sequence number of “1”, and a hash total of “2000”.
[0071]
FIGS. 19 to 21 show EDI data obtained by changing the message group header and the message group trailer.
[0072]
The business message transmitting unit 28 transmits EDI data reconstructed for each EDI data processing device 1 in the own company to each EDI data processing device 1.
[0073]
Further, each EDI data processing device 1 processes the EDI data transmitted in this way and transmitted to itself.
[0074]
When transmission is performed from the individual EDI data processing apparatuses 1 of the company A to the company B, a method of directly transmitting the data may be used as a rule during operation. Alternatively, the data may be collected in the EDI data distribution management server device 5 once.
[0075]
In the present embodiment, the matching is performed only by the product type of the business message content, but more detailed classification is also possible.
[0076]
For example, by operating the distribution management table, it is possible to deliver to the office A3 if the final order of the product Y is 100 or less. In this case, “10 == Y and 20 <= 100” is set in the business message content comparison item. The product type (data tag = 10) is “Y”, and the quantity (data tag = 20) means “100 or less”.
[0077]
As described above, the business message exchange is performed between the company A and the company B, but the company B is aware of a future configuration change including the business message type and the current internal configuration of the company A. There will be no need. Further, even with the same message type, the EDI data processing device 1 to which the EDI data is to be distributed can be selected according to the target product type, so that the EDI data processing efficiency on the company side can be expected.
[0078]
As described above, according to the present embodiment, the present invention can be effectively applied.
[0079]
Next, FIG. 22 is a block diagram showing a configuration of a second embodiment to which the present invention is applied.
[0080]
In the present embodiment, it is assumed that EDI data is transmitted and received from a plurality of companies.
[0081]
FIG. 23 is a block diagram showing the configuration of the EDI data management server device used in the present embodiment.
[0082]
In this figure, the EDI data distribution management server device 5 includes a distribution management table storage unit 10 provided with a distribution management table, a total management table storage unit 12 provided with a total management table, and a total table storage unit 14. , A business message receiving unit 20, a business message decomposing unit 22, a distribution analyzing unit 30, a business message reconstructing unit 26, and a business message transmitting unit 28.
[0083]
The distribution management table records a set of EDI data items and business message contents, and a distribution destination organization associated with the set. The aggregation management table records sets of EDI data items and business message contents, and distribution destination organizations associated therewith.
[0084]
The distribution analysis unit 30 first performs the same processing as the distribution analysis unit 24. Further, the distribution analysis unit 30 compares the business message being processed with the aggregation management table in step 216 using the aggregation management table as shown in FIG. , Transaction type, business message content, etc., and the history can be accumulated.
[0085]
In the case of the above table, of the business messages processed by the EDI management server, “0001”, ie, a quote request, “0002”, ie, a firm order, and “0003”, ie, “20” of an order confirmation, ie, This means that for the quantity, history recording and totaling are performed for each of the source company code and the destination company code (destination company code).
[0086]
FIG. 25 is a diagram showing a tally table when the tally management table shown in FIG. 24 is used. The tallying table is provided in the tallying table storage 14 shown in FIG. As shown in FIG. 25, in the tallying table, tallying is performed as a tallying value in units of a source company code, a destination company code (destination company code), a transaction type code, and a message content totaling item (business message content). Have been.
[0087]
In this way, data is collected not only for reception but also for transmission. This is because the same processing is performed not only for EDI messages received by the own company but also for EDI messages sent to business partners. This is a way to grasp EDI transactions in real time.
[0088]
As described above, according to the present embodiment, the present invention can be effectively applied.
[0089]
In each of the above-described embodiments, by separately installing the EDI data distribution management server device 5 which is a direct contact for EDI data exchange with other organizations, the data transmission source organization can change the internal configuration of the data reception destination organization. EDI data exchange can be performed without being conscious of this. Further, since the format of the EDI data is the same as before the installation of the EDI data distribution management server device 5, the same EDI data processing device 1 can be used, and even when newly added, the EDI data distribution management server device 5 is specialized. You don't need anything. Furthermore, since there is a mechanism for specifying the delivery destination based on the business message content itself in the EDI data without using a translator that uses a map that places a heavy load on the device, an EDI data exchange system with a more advanced distribution function is constructed. It becomes possible.
[0090]
【The invention's effect】
According to the present invention, even if the configuration of the processing device for the EDI data is changed in the own organization receiving and handling the EDI data, the destination of the EDI data is not changed in the other organization transmitting the EDI data. Need not be changed.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a conventional general electronic trading system.
FIG. 2 is a diagram showing a conventional distribution management table provided on a transmission source side;
FIG. 3 is a block diagram showing an office or a factory in a company A after a change in equipment configuration;
FIG. 4 is a diagram showing a distribution management table provided on the transmission source side after the above-described facility configuration change in the related art.
FIG. 5 is a flowchart showing a conventional EDI data transfer process;
FIG. 6 is a block diagram showing a configuration of a first embodiment to which the present invention is applied;
FIG. 7 is a block diagram showing a configuration of an EDI data management server device used in the first embodiment.
FIG. 8 is a flowchart showing processing performed in the EDI data distribution management server device 5 of the first embodiment.
FIG. 9 is a diagram showing a predetermined EDI format assumed for explaining the first embodiment;
FIG. 10 is a diagram showing a second EDI format following FIG. 9;
FIG. 11 is a diagram showing a third EDI format following FIG. 10;
FIG. 12 is a diagram showing a basic structure of a CII syntax rule defined by the Japan Information Processing Development Association.
FIG. 13 is a diagram showing contents of a distribution management table according to the first embodiment;
FIG. 14 is a diagram showing EDI data decomposed in the first embodiment.
FIG. 15 is a flowchart showing a procedure of the disassembly in the business message disassembly unit used in the first embodiment
FIG. 16 is a flowchart showing a distribution analysis procedure in a distribution analysis unit used in the first embodiment.
FIG. 17 is a diagram showing EDI data synthesized for each distribution destination in the first embodiment.
FIG. 18 is a flowchart showing a procedure of business message restructuring distribution analysis in a business message restructuring unit used in the first embodiment;
FIG. 19 is a first diagram showing EDI data obtained by changing a message group header and a message group trailer in the first embodiment.
FIG. 20 is a second diagram showing EDI data obtained by changing the message group header and the message group trailer in the first embodiment.
FIG. 21 is a third diagram showing EDI data obtained by changing the message group header and the message group trailer in the first embodiment.
FIG. 22 is a block diagram showing a configuration of a second embodiment to which the present invention is applied;
FIG. 23 is a block diagram showing a configuration of an EDI data management server device used in the second embodiment.
FIG. 24 is a diagram showing a tally management table used in the second embodiment;
FIG. 25 is a diagram showing an aggregation table used in the second embodiment.
[Explanation of symbols]
1. EDI data processing device
3… Company
5. EDI data distribution management server device
10 ... Distribution management table storage
12: Total management table storage
14: Total table storage
20: Business message receiving unit
22 Business message disassembly unit
24, 30 ... distribution analysis unit
26… Business message restructuring unit
28: Business message transmission unit

Claims (6)

On the side receiving and handling the EDI data, the business message in the received EDI data is decoded, and at least one of the source company code, the transaction type code, and the business message content data obtained by the decoding, A distribution analysis procedure for referring to a distribution management table storing transmission destination information and determining a transmission destination of the business message based on the reference result;
Reconstructing a business message as EDI data according to the determined destination;
An EDI exchange method, comprising: in a case where equipment is added or changed on the reception handling side, a procedure that does not require the other party transmitting the EDI data to change the setting by the addition or change. The EDI exchange method according to claim 1, further comprising:
Searching the aggregation management table by at least one of the source company code, the destination company code, the transaction type code, and the business message content data obtained by decrypting the business message in the received EDI data, An EDI exchange method, comprising: a procedure for performing totalization according to the search result for each content of a business message in a total management table. The EDI exchange method according to claim 2,
When the EDI data is transmitted, a business message in the EDI data is decrypted, and at least one of data of a source company code, a destination company code, a transaction type code, and a business message content obtained by the decryption is decoded. An EDI exchange method characterized by comprising a procedure of searching a total management table by one of the methods and performing a total according to the search result for each content of a business message in the total management table. The EDI exchange method according to any one of claims 1 to 3,
An EDI exchange method, wherein the reconstructing procedure is a procedure of reassembling EDI data by collecting a plurality of business messages to the same destination as one EDI data. On the side receiving and handling the EDI data, the business message in the received EDI data is decoded, and at least one of the source company code, the transaction type code, and the business message content data obtained by the decoding, A distribution analysis unit that refers to a distribution management table in which transmission destination information is stored, and determines a transmission destination of the business message based on the reference result;
A business message reconstructing unit for reconstructing a business message as EDI data in accordance with the determined destination;
An EDI data distribution management server device provided on a side that receives and handles EDI data. A computer program for implementing the EDI exchange method according to any one of claims 1 to 4, or the EDI data distribution management server device according to claim 5.

Images