JP4819559B2 - Data conversion apparatus, data conversion method, and data conversion program - Google Patents

Description

  The present invention relates to an apparatus and method for converting data in an EDI (Electronic Data Interchange) system into data in, for example, an ECALGA (Electronic Commerce Alliance for Global business Activity) system, which is a new standard. It is intended to reduce.

For example, in the “data exchange and management method and computer program” disclosed in Patent Document 1, various EDI users, for example, the orderer, place orders with other users, for example, the contractor, and the contractor uses the in-house code to receive the order data. A data conversion technique for converting and using a difference in data format between a certain user and another user, such as in the case of using the Internet, is disclosed.
FIG. 22 shows a conversion method when the technique disclosed in Patent Document 1 as Conventional Example 1 is applied to conversion from EIAJ (Electronic Industries Association of Japan) standard data to ECALGA data.
The operation in the conventional technique will be described.
First, data items for each EDI user (input ordering user and received order receiving user) are set in the data item definition for each user.
The data converter of the data converter receives the input data shown in FIG. 3 from the orderer. Then, the value of the orderer code is read, the user-specific data item definition on the input side is referred to, and the data item sequence of the input data is acquired. FIG. 23 shows a per-user data item definition of a user whose orderer code is 0000000000010001.
The data conversion unit registers the data item and the value in the input data together with the user ID as a data item and an item value in the common DB (database). FIG. 25 shows the common DB.
FIG. 24 shows a per-user data item definition of a user whose orderer code is 0000000000020001. The data conversion unit refers to the value of the contractor code of the input data, and generates output data from the common DB according to the above-mentioned data item definition for each user corresponding to the contractor code. FIG. 26 shows an example of output data.
In this way, output data converted into the code on the contractor side is obtained.

According to the “EDI format conversion method” of Patent Document 2 as Conventional Example 2, from the user-specific database based on the user-specific code system on the transmission side, the data is converted into pseudo-relational database data as necessary and expanded. Then, the extracted data is once converted into an EDI format which is a common code system, and the converted data is transmitted.
On the other hand, on the receiving side, a method is shown in which this is converted into pseudo-relational database data and further converted from an EDI format to a company-specific format to create a user-specific database on the receiving side.
However, each of the above conventional examples is effective when all the user-specific data of the previous (orderer or sender) can be converted into the user-specific data of the subsequent (ordering party or receiver), but the first user-specific data There is no description about the processing when there are no items.
JP 2004-288209 A JP-A-6-19756

By the way, in the exchange of accounts payable item information often used in the EDI system, certain information takes various values corresponding to input patterns. Conventionally, the EIAJ format, which is a format added by creating additional items corresponding to such information, has been extended.
For example, CBCID (complex business collaboration identifier), BCID (business collaboration identifier), BTID (business transaction identifier), and BAID (business action identifier) take values as shown in FIG. There is a problem that it is necessary to expand the database by human power and to input an item addition.

  The present invention has been made to solve the above-described problems, and it is possible to add new items necessary for each ordering data in accordance with the intention of the orderer without manually expanding the input data items. Objective.

The data conversion apparatus according to the present invention stores various billing method information in a memory as a method table, and determines a billing method corresponding to the input information from input information including input items based on the method table And
An item addition unit that stores an extension item for each billing method in the memory as an additional item table, and adds the extension item to the input item of the determined billing method based on the additional item table;
An item conversion unit that stores a conversion table for converting the input item into an output item in a memory, converts the input item into an output item based on the conversion table, and obtains output information together with the added extension item; And with.

  According to the present invention, since the (billing) method determination unit, the item addition unit, and the item (data) conversion unit are provided, an appropriate item corresponding to the method intended by the user can be obtained without manually inputting the extension item again. There is an effect that an item can be set by a new standard format by adding an extended item.

Embodiment 1 FIG.
Based on the old standard item data to which existing items are applied, new standard item data used in a method for applying a new item, for example, a billing method for each orderer, from the contents stored in the device without manual input A data conversion apparatus and data conversion method for taking out necessary items and adding them to new items will be described.
FIG. 1 is an explanatory diagram of the conversion process of the data conversion apparatus, showing the conversion order and tools in the data conversion process of the first embodiment. 2 is a diagram showing the configuration of the data conversion apparatus according to the first embodiment. In FIG. 2, the same elements as those in FIG. 1 are indicated by the same numbers, and the data flow is indicated by dotted lines. Yes.
First, in FIG. 1, the input data 1 is read with the EIAJ standard data item as an old standard item as an example, and the data conversion apparatus 10 outputs an ECALGA item as a new standard data item as an example with the following elements: Output data (ECALGA standard data item).

  As a specific element, there is an orderer-side billing method determination unit (method determination unit) 12 that determines a billing method with reference to an orderer-side billing method table (method table) 13 from the input side. Furthermore, after the determination, CBCID (Complex Business Identification Identifier), BCID (Business ID, Business ID, ID of ID), BTID (Business ID, ID of ID) , BAID determination unit 15, CBCID, BCID, BTID, BAID determination unit 16 by remark character string, CBCID, BCID, BTID, BAID determination unit 17 by remark (kanji) character string CBCID, BCID, BTID, BAID table 21 for each day, CB for each day Referring to ID, BCID, BTID, BAID table 22, remark character string, CBCID, BCID, BTID, BAID table 23, remark (kanji) character string, CBCID, BCID, BTID, BAID table 24 Data of items, that is, extended items is obtained. The EIAJ-ECALGA data conversion unit (item conversion unit) 19 refers to the EIAJ-ECALGA mapping table (conversion table) 20 as the output data 11 for the data with the added item.

The hardware configuration will be described based on FIG. 2 including the relationship with the conversion process explanatory diagram of FIG.
In FIG. 2, the data conversion apparatus 10 includes a control unit 31 including a processor, reads a computer program (not shown), and performs a control operation shown later in an operation flow. The memory 32 represents an auxiliary memory such as hardware or a magnetic disk for storing such a control program, or a main memory in which necessary portions of the control program are expanded so that the processor can be read out and executed by the processor. The input data 1 is read and executed by the input unit 33 and stored in the input data memory 1b. In this example, the input data 1 is data based on the EIAJ standard data item. The method determination unit 12 determines a method by referring to the orderer side billing method table (method table) 13 stored in the method table memory 13b. For the method thus determined, the item addition unit 34 refers to the additional item table memory 35 to determine additional items (extended items). In the present embodiment, the item adding unit 34 includes CBCID, BCID, BTID, BAID determination unit 14 for each orderer, CBCID, BCID, BTID, BAID determination unit 15 for each day, CBCID, BCID, BTID, BAID determination unit 16, CBCID, BCID, BTID, BAID determination unit 17 based on remark (kanji) character string, and any one of these corresponds to the billing method determined by the method determination unit 12 Operate. Similarly, in the present embodiment, the additional item table memory 35 includes CBCID, BCID, BTID, BAID table 21 for each orderer, CBCID, BCID, BTID, BAID table 22 for each orderer, CBCID, A BCID, BTID, BAID table 23, and a CBCID, BCID, BTID, BAID table 24 based on a remark (kanji) character string are stored.

The EIAJ-ECALGA data conversion unit (item conversion unit) 19 is based on the EIAJ-ECALGA mapping table (conversion table) 20 stored in the mapping table memory 20b with respect to the virtual table expanded by defining additional items. Output data 11 is generated. The output data (ECALGA standard data item) 11 including the item expanded by the item conversion unit 19 is temporarily stored in the output data memory 11b.
When output is required, the control unit 31 reads the output data 11 and outputs it from the communication unit 36 to the outside. In some cases, the communication unit 36 may simply output to a hardware medium such as a CD, and another computer may read this medium and perform necessary processing. In that case, the communication unit 36 becomes an output unit.
In addition, there is an output unit 37 that outputs to a display device or the like, and reads and displays the above-mentioned arbitrary data file and data in the course of processing.
In the method determination unit 12, the item addition unit 34, and the item conversion unit 19, dedicated programs are expanded in the memory, and the control unit 31 reads the programs and performs control operations shown in an operation flow described later. Do.
That is, the data conversion apparatus according to the present embodiment determines the billing method based on the method table stored in the memory, and adds from the billing method determined above based on the additional item table stored in the memory. The extension item to be determined is determined and added, the item between the old standard item and the new standard item is converted based on the conversion table stored in the memory, and the new standard item is obtained together with the added item, This new standard item is stored in memory to prepare for the required output.

Before explaining the operation, various explanatory diagrams that help understand the conversion operation are shown and described.
FIG. 3 is a diagram illustrating an example of input data. FIG. 4 is a diagram showing possible values for CBCID, BCID, BTID, and BAID depending on patterns (numbers). FIG. 5 is a diagram illustrating an output method of CBCID, BCID, BTID, BAID, and the like. FIG. 6 is a diagram showing the orderer-side billing method table 13. FIG. 7 is a diagram illustrating an example of the EIAJ-ECALGA mapping table. FIG. 8 is a diagram illustrating an example of a CBCID, BCID, BTID, and BAID table for each orderer. FIG. 9 is a diagram illustrating an example of a CBCID, BCID, BTID, and BAID table for each day. FIG. 10 is a diagram illustrating an example of a CBCID, BCID, BTID, and BAID table based on a remark character string. FIG. 11 is a diagram illustrating an example of a CBCID, BCID, BTID, and BAID table based on a remark (kanji) character string. FIG. 12 is a diagram illustrating an example of output data in the present embodiment.

Since the data conversion apparatus according to the first embodiment performs “identification of accounts payable information corresponding to the date of data creation”, the ordering forms P1 to P9 of the orderer, particularly designated P1 (daily verification bill payment) and P7 (monthly) Corresponding to (next verification request payment), a CBCID, BCID, BTID, BAID table is provided for each day for storing a format taken by CBCID, BCID, BTID, BAID.
Furthermore, a CBCID, BCID, BTID, BAID table, and “by remark character string for performing“ account details information identification using the remarks column ”that can freely select the pattern of the ordering formats P1 to P9 of the orderer, and“ A CBCID, BCID, BTID, and BAID table with remarks (kanji characters) for performing “accounts payable information identification using the remarks column (kanji)” is provided. In addition, in order to enable “fixed value output” performed by the user who does not need to select such patterns P1 to P9 in the order form, a CBCID, BCID, BTID, and BAID table is provided for each orderer.

FIG. 13 is a diagram illustrating an operation flow performed by the orderer-side billing method determination unit 12. FIG. 14 is a diagram illustrating an operation flow performed by the CBCID, BCID, BTID, and BAID determination unit 14 for each orderer. FIG. 15 is a diagram illustrating an operation flow performed by the CBCID, BCID, BTID, and BAID determination unit 15 for each day. FIG. 16 is a diagram illustrating an operation flow performed by the CBCID, BCID, BTID, and BAID determination unit 16 using a remark character string. FIG. 17 is a diagram illustrating an operation flow performed by the CBCID, BCID, BTID, and BAID determination unit 17 using a remark (kanji) character string. FIG. 18 is a diagram illustrating an operation flow performed by the EIAJ-ECALGA data conversion unit 19.
The operation of the apparatus will be described with reference to these flowcharts.
The orderer-side billing method determination unit 12 first performs the operations of steps S101 to S103 (hereinafter, description of the steps is omitted). Read the orderer ID. Next, in S102, the orderer side billing method table 13 is referred to by the read orderer ID, and the billing method for the corresponding orderer ID is returned in the method determination step in S103. That is, the method determination unit 12 reads 00004 (orderer code) from the data item in FIG. 3 and obtains the orderer code = 0000000010001 as a value. Then, referring to the orderer side billing method table 13 of FIG. 6, identification information of billing method = M1 is returned.

The item adding unit 34 that has received this M1, that is, the “accounting details information identification corresponding to data creation date” billing method, depends on the creation date, so the CBCID, BCID, BTID, BAID for each day of the billing method. The determination unit 15 performs an operation according to the flow from S301 to S303 shown in FIG. That is, the CBCID, BCID, BTID, and BAID determination unit 15 for each day of the item adding unit 34 reads the data creation date, the orderer ID, and the information classification (S301), and searches the CBCID, BCID, BTID, BAID22 table for each day. (S302). The CBCID, BCID, BTID, and BAID of the matching row are read and a value is set in the output data (ECALGA standard) (S303: item addition step).
Specifically, since the method number in FIG. 5 is M1 indicating the payable details information identification corresponding to the data creation date, the billing method is P1 or P7 in FIG. The CBCID, BCID, BTID, BAID determination unit 15 for each day of the item addition unit 34 reads the orderer code = 0000000010001, the data creation date = 0512215, and the information classification = 1101 by the input data 1. The format of the data creation date is YYMMDD in EIAJ, and DD = 15 is used to refer to the CBCID, BCID, BTID, and BAID table 22 for each day in FIG. 9, and data item 18002 (CBCID) = CBCS0062, 18003 (BCID) = BCSF200, 18005 (BTID) = BTSF201, 18007 (BAID) = BASF2021 is obtained.

The item conversion unit 19, in this example, the EIAJ-ECALGA data conversion unit, operates according to the flow of S700 to S710 shown in FIG. First, the EIAJ-ECALGA data converter advances the cursor to the first line of input by its program (S700). Subsequently, the EIAJ-ECALGA data conversion unit reads one line from the cursor position of the input data (S701). If it can be read (S702), the data item of the read input data is searched with the input data item string in the EIAJ-ECALGA mapping table 20, and the output data item of the matched row is obtained (S703: item conversion step). In the output data, the output data item obtained in S703 and the value of the input data read in S702 are set (S705). The cursor is advanced to the next line of the input data, and the process proceeds to step S702 (S706).
If the data could not be read in S702, the EIAJ-ECALGA data conversion unit advances the cursor to the line where the value of the output data item is 18001 in the EIAJ-ECALGA mapping table 20 (S704). Then, in the EIAJ-ECALGA mapping table, the default value of the line at the cursor is read (S707). If it can be read (S708), the read default value is set in the output data together with the data item (S709: item conversion step). In the EIAJ-ECALGA mapping table, the cursor is moved to the next line (S710). If the data cannot be read in step S708, the process ends.
These values are set in the output data. Next, the remaining output data items 00003, 00004, 00005, 00005, 00026, 18001,... In FIG. 12 are set by the EIAJ-ECALGA data conversion unit.

As described above, the data conversion apparatus 10 acquires the billing method from the input data 1 by the orderer billing method determination unit 12. When the acquired billing method is M1, as described above, the CBCID, BCID, BTID, BAID determination unit 15 sets CBCID, BCID, BTID, BAID in the output data 11 as described above.
However, if the acquired billing method is M2, the CBCID, BCID, BTID, and BAID determination unit 16 using the remark character string sets CBCID, BCID, BTID, and BAID in the output data.
After CBCID, BCID, BTID, and BAID are set, the EIAJ-ECALGA data conversion unit 19 sets the remaining output data items.

If the acquired billing method is M3, the CBCID, BCID, BTID, and BAID determination unit 17 using a remark (kanji) character string sets CBCID, BCID, BTID, and BAID in the output data. . Further, when the acquired billing method is M4, the CBCID, BCID, BTID, BAID determination unit 14 for each orderer sets CBCID, BCID, BTID, BAID in the output data.
After CBCID, BCID, BTID, and BAID are set, the EIAJ-ECALGA data conversion unit 19 sets the remaining output data items.

In the case of using the CBCID, BCID, BTID, BAID determination unit 14 for each orderer, the flow is performed by the CBCID, BCID, BTID, BAID determination unit 14 for each orderer shown in FIG. That is, the CBCID, BCID, BTID, BAID determination unit 14 for each orderer reads the orderer ID and the information classification (S201), and then searches the CBCID, BCID, BTID, BAID table for each orderer (S202). . The CBCID, BCID, BTID, and BAID of the matching row are read, and the value is set in the memory for the output data (ECALGA standard) (S203: item addition step).
In the case of the CBCID, BCID, BTID, and BAID determination unit 16 using the remark character string, the flow is performed by the CBCID, BCID, BTID, and BAID determination unit 16 using the remark character string shown in FIG. That is, the CBCID, BCID, BTID, BAID determination unit 16 based on the remark character string reads the remark character string, the orderer ID, and the information classification (S401), and searches the CBCID, BCID, BTID, BAID table based on the remark character string. (S402). The CBCID, BCID, BTID, and BAID of the matching row are read, and a value is set in the memory for the output data (ECALGA standard) (S403: item addition step).

When the CBCID, BCID, BTID, and BAID determination unit 17 uses a remark (kanji) character string, the flow is performed by the CBCID, BCID, BTID, and BAID determination unit 17 using the remark (kanji) character string shown in FIG. That is, the CBCID, BCID, BTID, and BAID determination unit 17 based on the remark (kanji) character string reads the remark character string, the orderer ID, and the information classification (S501), and the CBCID, BCID, BTID based on the remark (kanji) character string. The BAID table is searched (S502). The CBCID, BCID, BTID, and BAID of the matching row are read, and the value is set in the memory for the output data (ECALGA standard) (S503: item addition step).
As described above, since the ECALGA standard data item is generated by changing the way of handling the existing EIAJ standard data item, the EIAJ standard data format is used in the data conversion between the EIAJ data item and the ECALGA data item. The CBCID, BCID, BTID, and BAID can be changed for each order data without adding an extension item.

In addition, regarding the output method of the additional item in FIG. 5, the case of the method number M1 has been described above. However, when “content” of another method number is set in advance, it corresponds to M2 to M4. A place to obtain information on additional items can be defined.
For example, when the data shown in FIG. 19 is input, the data conversion apparatus 10 reads the orderer code = 0000000040001 by the orderer-side billing method determination unit 12 and uses the orderer-side billing method table of FIG. Obtain M4. That is, the operation shown in FIG. 14 is performed. That is, since the EIAJ-ECALGA data conversion apparatus has acquired the billing method M4, the CBCID, BCID, BTID, BAID determination unit 14 for each orderer uses the orderer code = 0000000010001, information classification from the input data. = 1101 is read. The data items 18002 (CBCID) = CBCS0061, 18003 (BCID) = BCSF120, 18005 (BTID) = BTSF124, 18007 (BAID) = BASF1241 are obtained by referring to the CBCID, BCID, BTID, BAID table 21 for each orderer. These values are set in the output data. Next, the remaining output data items 00003, 00004, 00005, 00005, 00026, 18001... Are set by the EIAJ-ECALGA data conversion unit.

  Furthermore, when the data shown in FIG. 20 is input, the data conversion apparatus 10 reads the orderer code = 0000000020001 by the orderer-side billing method determination unit 12 and sets the billing method = M2 according to the orderer's billing method table. obtain. That is, the operation shown in FIG. 16 is performed. In other words, since the EIAJ-ECALGA data conversion apparatus has acquired the billing method M2, the CBCID, BCID, BTID, BAID determination unit 16 based on the remark character string determines the orderer code = 0000000020001, remark = GETJJ, information classification = 1101 is read. Referring to the CBCID, BCID, BTID, and BAID table 23 based on the remark character string shown in FIG. Get. These values are set in the output data. Next, the remaining output data items 00003, 00004, 00005, 00005, 00026, 18001... Are set by the EIAJ-ECALGA data conversion unit.

  Furthermore, when the data shown in FIG. 21 is input, the EIAJ-ECALGA data conversion apparatus reads the orderer code = 0000000030001 by the orderer's billing method determination unit, and the billing method = Obtain M3. That is, the operation shown in FIG. 17 is performed. In other words, the EIAJ-ECALGA data conversion apparatus has acquired the billing method M3, so the CBCID, BCID, BTID, BAID determination unit 17 based on the remark (kanji) character string determines the orderer code = 0000000030001 from the input data. Remarks (kanji) = monthly, information classification = 1101 is read. Remarks (Kanji) Character strings 18002 (CBCID) = CBCS0061, 18003 (BCID) = BCSF110, 18005 (BTID) = BTSF111, 18007 (BAID) = BASF1121 with reference to the CBCID, BCID, BTID, BAID table 24 Get. These values are set in the output data. Next, the remaining output data items 00003, 00004, 00005, 00005, 00026, 18001... Are set by the EIAJ-ECALGA data conversion unit.

In the above description, an apparatus and a method for selecting and adding necessary extension items in the case of EIAJ-ECALGA conversion have been described. In the case where some items after the conversion do not have items on the input side and a new input is required, as another case in which the device adds an extension item, the user can input the EIAJ standard input. You may want to add company-specific extension items. Also at this time, the extension item to be added according to the input pattern can be prepared and stored in the additional item table, the pattern can be determined, and the extension item can be extracted and added from the additional item table. This eliminates the need for input of extended items.
The same applies to the case where the user wants to add an extension item unique to the company to the ECALGA standard input. That is, it is possible to prepare and store an extension item to be added according to the input pattern in the additional item table, determine the pattern, and extract and add the extension item from the additional item table.

That is, the example of this system includes an orderer side billing method table for setting a billing method for each order, an EIAJ standard data item, an EIAJ-ECALGA mapping table for setting a correspondence between ECALGA standard data items, and an EIAJ standard data item. Sets the correspondence between the orderer user code, data creation date and ECALGA standard data items CBCID, BCID, BTID, and BAID, determines the daily CBCID, BCID, BTID, BAID table, and the billing method for each orderer The orderer side billing method determination unit, the daily CBCID, BCID, BTID, BAID determination unit, CBCID, BCID, BTID, BAID for determining CBCID, BCID, BTID, BAID according to the data creation date described in the input data Data items other than Data conversion system comprising a data converting device comprising a EIAJ-ECALGA data converter for converting a.
Also, the correspondence between the orderer user code and the CBCID, BCID, BTID, and BAID in the EIAJ standard data item is set. The CBCID, BCID, BTID, and BAID table for each orderer, and the CBCID, BCID, and BTID unique to each orderer, A data conversion system including a CBCID, a BCID, a BTID, and a BAID determination unit for each orderer who gives a BAID.
Furthermore, the correspondence between the remarks in the EIAJ standard data items and CBCID, BCID, BTID, BAID is set. The CBCID, BCID, BTID, BAID table by the remark character string and the remark character string are used to determine CBCID, BCID, BTID, BAID. A data conversion system including a CBCID, BCID, BTID, and BAID determination unit using a remark character string.
Furthermore, the correspondence between the remarks (kanji) in the EIAJ standard data items and the CBCID, BCID, BTID, BAID is set, the CBCID, BCID, BTID, BAID table by the remarks (kanji) character string, and the remarks (kanji) character string, A data conversion system including a CBCID, BCID, BTID, and BAID determination unit based on a remark (kanji) character string that determines CBCID, BCID, BTID, and BAID.

In the above description, the data conversion apparatus 10 has been described as having the hardware configuration shown in FIG. 2, but as mentioned above, the method determination unit 12, the item addition unit 34, the item conversion unit 19 and the like are shown in FIGS. The function shown in the operation flow 18 may be described by a program and executed by the control unit 31 including a processor.
Furthermore, even if such a program is read and recorded on a medium that can be read and executed by a general-purpose computer, and the general-purpose computer develops the program in its own memory using an input device, the program is executed as described above. Similar effects can be obtained.

It is a data conversion process explanatory drawing in Embodiment 1 of this invention. 1 is a diagram illustrating a configuration of a data conversion device in Embodiment 1. FIG. 6 is a diagram illustrating an example of input data according to Embodiment 1. FIG. 6 is a diagram illustrating values that can be taken by CBCID, BCID, BTID, and BAID in Embodiment 1. FIG. It is a figure which shows the content of the billing system in Embodiment 1. FIG. 6 is a diagram illustrating an example of an orderer billing method table according to Embodiment 1. FIG. 6 is a diagram illustrating an example of an EIAJ-ECALGA mapping table in the first embodiment. FIG. It is a figure which shows the example of the CBCID, BCID, BTID, BAID table for every orderer in Embodiment 1. FIG. It is a figure which shows the example of the CBCID, BCID, BTID, BAID table for every day in Embodiment 1. FIG. It is a figure which shows the example of the CBCID, BCID, BTID, BAID table by the remarks character string in Embodiment 1. FIG. It is a figure which shows the example of the CBCID, BCID, BTID, BAID table by the remarks (kanji) character string in Embodiment 1. FIG. 6 is a diagram illustrating an example of output data in the first embodiment. FIG. It is a figure which shows the operation | movement flow which the ordering person billing system determination part in Embodiment 1 performs. 6 is a diagram illustrating an operation flow performed by a CBCID, BCID, BTID, and BAID determination unit for each orderer in the first embodiment. FIG. FIG. 10 is a diagram illustrating an operation flow performed by the CBCID, BCID, BTID, and BAID determination unit for each day in the first embodiment. It is a figure which shows the operation | movement flow which CBCID, BCID, BTID, and a BAID determination part perform by the remarks character string in Embodiment 1. It is a figure which shows the operation | movement flow which the CBCID, BCID, BTID, and BAID determination part perform by the remarks (kanji) character string in Embodiment 1. 6 is a diagram illustrating an operation flow performed by an EIAJ-ECALGA data conversion unit according to Embodiment 1. FIG. FIG. 10 is a diagram showing other input data in the first embodiment. FIG. 10 is a diagram showing other input data in the first embodiment. FIG. 10 is a diagram showing other input data in the first embodiment. It is a figure which shows the example of a conversion at the time of applying the conventional data exchange and management method. It is a figure which shows the example of the data input by an orderer. It is a figure which shows the example output with the code | cord | chord system of the order receiver. It is a figure which shows the example of data of the conventional common database. It is a figure which shows the example of output data.

Explanation of symbols

  1 input data, 1b input data memory, 10 data conversion device, 11 output data, 11b output data memory, 12 (orderer side billing) method judgment unit, 13 (orderer side billing) method table, 13b (orderer) Side billing) method table memory, 14 CBCID, BCID, BTID, BAID determination unit for each orderer, CBCID, BCID, BTID, BAID determination unit for every 15 days, 16 Remarks CBCID, BCID, BTID, BAID determination unit, 17 CBCID, BCID, BTID, BAID determination unit, 19 (EIAJ-ECALGA) item conversion unit, 20 EIAJ-ECALGA mapping table (conversion table), 20b mapping (conversion) table by remark (kanji) character string・ Memory, 21 per orderer, BCID, BCID, BTID, BAID table, every 22 days, CBCID, BCID, BTID, BAID table, 23 Remark character string, CBCID, BCID, BTID, BAID table, 24 Remarks BTID, BAID table, 31 control unit including processor, 32 memory, 33 input unit, 34 item addition unit, 35 additional item table / memory, 36 communication unit, 37 output unit.

Claims (5)

An input unit for inputting input information including a plurality of input items and a value of each input item;
Stores any one of the preceding method table scheme is shown of a plurality of kinds of billing scheme for each value of a predetermined input item to the memory, based on the system table, the input information input by the input unit A method determination unit for determining a billing method corresponding to the value of the predetermined input item included ;
An additional item table indicating the value of the extension item is stored in the memory for each billing method, and the input information input by the input unit is added based on the additional item table corresponding to the billing method determined by the method determination unit. An item addition part for adding the value of the extension item;
A conversion table for converting an input item into an output item is stored in a memory, and an input item of input information input by the input unit is converted into an output item based on the conversion table. An item conversion unit that obtains output information together with values,
The above item addition part is
For each billing method, store an additional item table in which one or more extended item values are indicated for a combination of two or more specific input item values;
From the additional item table corresponding to the billing method determined by the method determination unit, the value of the extension item corresponding to the combination of the values of the two or more specific input items included in the input information input by the input unit And a value of the acquired extension item is added to the input information input by the input unit. The above item addition part is
2. The data conversion apparatus according to claim 1, further comprising an additional item table for each billing method in which a combination of values of the two or more specific input items is different for each billing method. The item addition part is a daily addition part or an addition part for each orderer corresponding to whether multiple types of billing methods are daily, per orderer, order by remark character string, or order by remark (kanji) character string Or an additional part with a remark character string, or an additional part with a remark (kanji) character string,
The additional item table includes 1) a complex business collaboration identifier (daily CBCID), a business collaboration identifier (BCID), a business transaction identifier (BTID), and a business action identifier (BAID) for each day corresponding to the above billing method. Additional item table or
2) Is it an additional item table including CBCID, BCID, BTID, and BAID for each orderer?
3) Is it an additional item table that includes CBCID, BCID, BTID, and BAID by remark character string?
4) Is it an additional item table including CBCID, BCID, BTID, and BAID by remark (kanji) character string?
2. The data conversion apparatus according to claim 1, wherein the data conversion apparatus is any one of the above. An input step in which the input unit inputs input information including a plurality of input items and a value of each input item;
A method table indicating any one of a plurality of billing methods is stored for each value of a predetermined input item, and a method determination unit is input by the input unit based on the method table. A method determination step for determining a billing method corresponding to the value of the predetermined input item included in the input information;
An additional item table indicating the value of the extended item is stored for each billing method, and the item adding unit is input by the input unit based on the additional item table corresponding to the billing method determined by the method determining unit. An item addition step for adding an extended item value to the input information,
A conversion table for converting input items to output items is stored, and the item conversion unit converts the input items of the input information input by the input unit based on the conversion table into output items, and is added An item conversion step for obtaining output information together with the value of the extended item,
The above item addition step is
For each billing method, an additional item table in which one or more extended item values are indicated for a combination of two or more specific input item values is stored;
The item addition unit corresponds to a combination of values of the two or more specific input items included in the input information input by the input unit from the additional item table corresponding to the billing method determined by the method determination unit. A data conversion method comprising: acquiring an extension item value to be added, and adding the acquired extension item value to the input information input by the input unit. A program executed by a computer for performing data conversion between an old standard format and a new standard format having different formats,
An input step for inputting input information including a plurality of input items and a value of each input item;
Stores a method table indicating any one of a plurality of billing methods for each value of a predetermined input item, and is included in the input information input by the input unit based on the method table A method determination step of determining a billing method corresponding to the value of the predetermined input item ,
An additional item table indicating the value of the extended item is stored for each billing method, and the input information input by the input step is expanded based on the additional item table corresponding to the billing method determined by the method determination step. An item addition step for adding an item value;
A conversion table for converting input items to output items is stored. Based on the conversion table, the input item of the input information input by the input step is converted into an output item, and the value of the added extension item And an item conversion step for obtaining output information,
The above item addition step is
For each billing method, an additional item table in which one or more extended item values are indicated for a combination of two or more specific input item values is stored;
The value of the extension item corresponding to the combination of the values of the two or more specific input items included in the input information input by the input step from the additional item table corresponding to the billing method determined by the method determination step And a value of the acquired extension item is added to the input information input in the input step.

Images