JP2010015330A - Information exchange computer system and operation program for this system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information-communicating computer (EDI (Electronic Data Interchange)) system wherein a system changeover is facilitated. <P>SOLUTION: This information communication computer system has a connection destination management database 124 storing a plurality of data formats and communication procedures between a retail sales side computer 2 and a wholesale side computer AB by periods. In the information communication computer system, after a transmission/reception part 111 receives data of a prescribed format from the retail sales side computer 2 and performs business processing, the data format and the communication procedure of the wholesale side computer 3 in a system date are acquired from the connection destination management database 124, the data performed with the business processing are converted into the acquired data format, and the converted data are transmitted to the wholesale side computer A by the acquired communication procedure. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an information exchange computer system for exchanging information between computers having different data formats and communication procedures, and an operation program for the system. Specifically, the present invention relates to an enterprise that unifies transaction information relating to commercial transactions into a standard format. The present invention relates to an information exchange computer system capable of easily switching an operation system in an EDI (Electronic Data Interchange) center for electronic exchange between them, and an operation program for the system.

  In general, EDI systems, which are information exchange computer systems that exchange business transaction information between companies according to the prior art, often have different data exchange procedures (communication protocols) and business messages (ordering, payment, etc.) for each company. Furthermore, since there are many cases in which the format of the message is different for each retail company, it is known that there are many cases in which the company communicates via a relay center called an EDI center rather than a system in which the companies directly communicate with each other.

  In recent years, according to the Ministry of Economy, Trade and Industry's “Distribution Supply Chain Optimization Promotion Project”, “Standardization of electronic commerce methods surrounding retailing” “Establishment of infrastructure for improving operational efficiency in three layers of manufacturing, delivery, and sales The system construction aiming at "was promoted. As a result, the standardization of the business data format and the data exchange procedure, which had been different for each retail store, were implemented. In March 2007, distribution business message standard (distribution BMS) Ver. 1.0 is released, and it is expected that the number of retail and wholesale companies corresponding to this standard will increase dramatically in the future.

  For this reason, the EDI Center needs to develop a system that supports the new standard, but the transition timing from the old system to the new standard differs depending on the connection destination. Don't be.

  The switching between the old and new systems in the EDI system described above is not a system that switches all systems at the same time, but is a parallel operation in which the old system is fully operational at the time of transition from the old system to the new standard, and a trial operation is performed on the new standard system. When the transition to the new standard is accelerated in the future, it is necessary to support parallel operation for each of a large number of connection destinations, which may lead to a great amount of operation man-hours and costs.

  Further, there is a possibility that the distribution BMS will be upgraded in the future, and even when the connection destination supports the version upgrade, the same parallel operation as described above must be supported. Since the period of these parallel operations is determined by the convenience of the connection destination, it is practically impossible to carry out all the companies at the same time, and one company must deal with each period.

In addition, Patent Literature 1 listed below is a document that describes a technology for performing data migration between the old and new systems according to the prior art. In Patent Literature 1, data in the old system database is migrated to the new system database. The migration source data is converted to the migration destination data at once, the migration source difference data generated thereafter is stored in the buffer table, and the migration source difference data stored in the buffer table is converted to the migration destination data for migration. A technique for updating the previous data is described.
JP 2005-266773 A

The switching of the EDI system described above is, for example, that the connection destination A shifts from the old system to the new standard system, the parallel operation period is 2008/1/1 to 2008/1/31, and the new standard system starts production. In the case of 2/1, it is necessary to perform the following operations (1) to (3).
(1) to 2007/12/31: The actual operation is performed in the old system (the actual data is transmitted to the connection destination A in the old data format).
(2) 2008/1/1: For the data of connection destination A, production data is transmitted in the old system and trial data is transmitted in the new standard system.
(3) 2008/2/1: For the data of connection destination A, the transmission by the old system is stopped, and the production data is transmitted by the new standard system.

Similarly, the connection destination B is a distribution BMS Ver. 1.0 from distribution BMS Ver. 2.0, the parallel operation period is 2009/1/1 to 2009/1/31, the parallel operation period is 2009/1/1 to 2009/1/31, the distribution BMS Ver. When the production start at 2.0 is 2009/2/1, the following operations (1) to (3) need to be performed.
(1) to 2008/12/31: Distribution BMS Ver. 1.0 works (the transmission data is transmitted to the connection destination B by distribution BMS Ver.1.0).
(2) 2009/1/1: Distribution BMS Ver. 1.0 production data, distribution BMS Ver. Send trial data at 2.0.
(3) 2009/2/1: For the data of connection destination B, distribution BMS Ver. The production data is transmitted at 2.0.

  As mentioned above, EDI system switching, old period, parallel period, and new period need to be switched for each connection destination, companies that transition from old procedures to new procedures, and companies that introduce new procedures There is a problem that it takes a great deal of man-hours and costs to cope with this. This is because the system for the old procedure and the system for the new procedure are required separately, and when moving from the old procedure to the new procedure, trial operation is performed in the new procedure while running in the old procedure (parallel operation) This is because a process is required in which the old procedure is stopped after a certain day and the new procedure is put into production. In the EDI system according to the prior art, it is expected that the shift to the new procedure is accelerated, but there is a problem that a large amount of man-hours is required for this correspondence.

  Although the technique described in Patent Document 1 described above can migrate data from the migration source system to the migration destination system without stopping the system, the old and new systems are operated in parallel as in the EDI system to which the present invention is applied. It was something that could not be applied to those that do.

  An object of the present invention is to provide an information exchange computer system capable of easily switching between data formats and communication procedures, and an operation program for the system.

To achieve the above object, the present invention provides one computer that transmits and receives data in a predetermined data format by a predetermined communication procedure, the other computer that transmits and receives data in a predetermined data format by a predetermined communication procedure, An information exchange computer system for transmitting to the other computer after performing business processing of data received from one or the other computer,
The computer system is
A transmission / reception unit for transmitting / receiving arbitrary format data to / from the one and other computers according to an arbitrary communication procedure;
A conversion processing unit for converting data received from the one and other computers into an arbitrary data format;
A business processing unit that performs predetermined business processing of the data converted by the conversion processing unit;
A connection destination management database for storing a plurality of communication procedures and data formats with the one and the other computers for each period;
A system date / time management unit for managing the current system date / time;
A control unit for controlling the transmission / reception unit, the conversion processing unit, the business processing unit, and the connection destination management database;
The control unit
A first step in which the transceiver unit receives data in a predetermined format from one computer;
A second step of acquiring a date and time when the data is received from the system date and time management unit;
A third step of determining the data format of one computer of the date and time acquired in the second step from the connection destination management database;
A fourth step in which the conversion processing unit converts the data whose data format is determined in the third step into intermediate format data;
A fifth step in which the business processing unit performs business processing of the intermediate format data converted into the intermediate format in the fourth step;
A sixth step of acquiring the current date and time from the system date and time management unit;
A seventh step of determining the data format and communication procedure of the other computer of the date and time acquired in the sixth step from the connection destination management database;
An eighth step in which the conversion processing unit converts the intermediate format data subjected to the business process in the fifth step into the data format determined in the seventh step;
A first feature is that the transmission / reception unit executes the ninth step of transmitting the data converted in the eighth step to the other computer by the communication procedure acquired in the seventh step.

According to the present invention, in the information exchange computer system according to the first feature, two communication procedures and data formats stored in the connection destination management database for each computer and each other and for each period are stored in one period. An information exchange computer system,
The control unit is
In the seventh step, the two data formats of the other computer and the communication procedure corresponding to the data format are determined from the connection destination management database,
In the eighth step, the intermediate format data processed in the fifth step is converted into the determined two data formats,
In the ninth step, the second feature is that the two data converted into the two data formats are transmitted to the other computer by a communication procedure corresponding to the determined data format.

According to the present invention, in the information exchange computer system according to the first or second feature, the predetermined data format is a CSV format, a fixed length format, and a business message standard (distribution BMS) format, and the intermediate format data is XML. And the predetermined communication procedure is a JCA procedure which is a supplier data exchange standard communication control procedure defined by the Japan Chain Store Association, and a communication procedure based on an international standard specification for business-to-business electronic commerce in XML language. It is a JX procedure established based on an ebXML procedure and an international standard specification for a message exchange procedure for EDI between companies.
The control unit is
In the fourth step, the conversion processing unit is used to convert data in CSV format, fixed-length format, or business message standard format into XML language format,
In the eighth step, the data in the XML language format is converted into a CSV format, a fixed length format, or a business message standard format using the conversion processing unit,
In the ninth step, the data is transmitted to the other computer by the JCA procedure, the ebXML procedure, or the JX procedure obtained in the seventh step by using the transmitting / receiving unit to convert the data converted in the eighth step. And

Furthermore, the present invention provides an arbitrary format data transfer method with one computer that transmits / receives data in a predetermined data format according to a predetermined communication procedure and another computer that transmits / receives data according to a predetermined data format according to a predetermined communication procedure. A transmission / reception unit that performs transmission / reception, a conversion processing unit that converts data received from the one and the other computers into an arbitrary data format, a business processing unit that performs predetermined business processing of data converted by the conversion processing unit, A connection destination management database for storing a plurality of communication procedures and data formats for the one and the other computers for each period, a system date / time management unit for managing the current system date / time, the transmission / reception unit, a conversion processing unit, and a business process And a control unit for controlling the connection destination management database, from the one or the other computer An information exchange computer system operation program to be transmitted to the other computer after the business processing Shin data,
In the control unit,
A first function in which the transmission / reception unit receives data in a predetermined format from one computer;
A second function for acquiring a date and time when the data is received from the system date and time management unit;
A third function for determining the data format of one computer of the date and time acquired by the second function from the connection destination management database;
A fourth function in which the conversion processing unit converts the data whose data format has been determined by the third function into intermediate format data;
A fifth function in which the business processing unit performs business processing of intermediate format data converted into an intermediate format by the fourth function;
A sixth function for acquiring the current date and time from the system date and time management unit;
A seventh function for determining the data format and communication procedure of the other computer of the other date and time acquired in the sixth step from the connection destination management database;
An eighth function in which the conversion processing unit converts the intermediate format data processed by the fifth function into the data format determined by the seventh function;
A fourth feature is that the transmission / reception unit realizes a ninth function of transmitting the data converted in the eighth step to the other computer by a communication procedure acquired by the seventh function.

Further, the present invention provides the operation program according to the third feature, wherein two communication procedures and data formats for each computer and each period stored in the connection destination management database are stored in one period.
In the control unit,
In the seventh function, a function of determining two data formats of the other computer and a communication procedure corresponding to the data format from the connection destination management database;
A function of converting the intermediate format data processed in the fifth function into the determined two data formats in the eighth function;
In the ninth function, a fifth feature is that a function of transmitting the two data converted into the two data formats to the other computer by a communication procedure corresponding to the determined data format is realized.

According to the present invention, in the operation program for the information exchange computer system according to the fourth or fifth feature,
The predetermined data format is a CSV format, a fixed length format, a business message standard (distribution BMS) format, the intermediate format data is an XML language format, and the predetermined communication procedure is a transaction specified by the Japan Chain Store Association. International standard specifications for the JCA procedure, which is a standard data exchange standard communication control procedure, the ebXML procedure, which is a communication procedure based on the international standard specification for business-to-business electronic commerce in XML language, and the message exchange procedure for EDI between businesses. JX procedure established based on
In the control unit,
In the fourth step, a function of converting data in a CSV format, a fixed length format, or a business message standard format into an XML language format using the conversion processing unit;
In the eighth step, a function for converting data in XML language format into CSV format, fixed-length format, or business message standard format using the conversion processing unit;
In the ninth step, realizing the function of transmitting data to the other computer by the JCA procedure, the ebXML procedure, or the JX procedure obtained in the seventh step by using the transmission / reception unit to convert the data converted in the eighth step. The sixth feature.

  An information exchange computer system and an operation program according to the present invention provide a connection destination management database for storing a plurality of communication procedures and data formats for one and the other computers for each period, and a control unit receives data of a predetermined format from one computer. After the transmission / reception unit receives and performs the business process, the data format and communication procedure of the other computer at the system date and time are determined with reference to the connection destination management database, and the data subjected to the business process is determined as the determined data format And the converted data is transmitted to the other computer according to the determined communication procedure, so that the system can be easily transferred to another system having a different data format or communication procedure.

  Hereinafter, an embodiment in which an information exchange computer system according to the present invention and an operation program for the system are applied to an EDI system will be described in detail with reference to the drawings.

  FIG. 1 is a diagram for explaining an EDI system to which an operation method according to this embodiment is applied, and FIG. 2 is a flowchart showing a processing procedure when retail data from a retailer is transmitted to a wholesaler according to this embodiment. 3 is a flowchart showing a processing procedure when wholesale data from the wholesaler in this embodiment is transmitted to the retailer, FIG. 4 is a data content diagram held in the connection destination management DB of the EDI center in this embodiment, and FIG. Is a data content diagram held in the connection destination management DB of the EDI center, FIG. 6 is a diagram showing connection destination parameters that define the communication procedure for the production order, and FIG. 7 is a connection that defines the communication procedure for the trial order. FIG. 8 is a diagram showing connection destination parameters that define the data format for the same ordering, FIG. 9 is a diagram showing connection destination parameters that define the data format for the trial ordering, and FIG. FIG. 11 is a diagram showing connection destination parameters that define communication procedures for the same ordering, FIG. 11 is a diagram showing connection destination parameters that define communication procedures for the trial ordering, and FIG. 12 defines a data format for the same ordering. FIG. 13 is a diagram illustrating connection destination parameters, FIG. 13 is a diagram illustrating connection destination parameters that define a data format for trial ordering, and FIG. 14 is a diagram illustrating connection destination parameters that define communication procedures for the same production ordering.

  15 is a diagram showing connection destination parameters that define the communication procedure for trial ordering in the present embodiment, FIG. 16 is a diagram showing connection destination parameters that define the data format for the actual ordering, and FIG. FIG. 18 is a diagram showing connection destination parameters that define communication procedures for the same pre-shipment shipment, and FIG. 19 is a connection diagram that defines communication procedures for the same trial pre-shipment. FIG. 20 is a diagram illustrating a connection destination parameter that defines a data format for the same production advance shipment, FIG. 21 is a diagram illustrating a connection destination parameter that defines a data format for the same trial advance shipment, and FIG. Is a diagram showing connection destination parameters defining communication procedures for the same pre-shipment shipment, FIG. 23 is a diagram showing connection destination parameters defining communication procedures for the same trial pre-shipment, and FIG. FIG. 25 is a diagram showing connection destination parameters that define the data format for the trial advance shipment, FIG. 25 is a diagram showing connection destination parameters that define the data format for the trial advance shipment, and FIG. FIG. 27 is a diagram illustrating a connection destination parameter that defines a communication procedure for the same trial advance shipment, FIG. 28 is a diagram illustrating a connection destination parameter that defines a data format for the actual advance shipment, and FIG. FIG. 5 is a diagram showing connection destination parameters that define a data format for the same trial advance shipment.

[Constitution]
[overall structure]
As shown in FIG. 1, an EDI center 1 that is a computer system to which an operation method and a program according to the present embodiment are applied is located between a plurality of wholesale 3 computers and a retail 2 computer. A retail transmission / reception server 11 that transmits / receives data via the transmission / reception processing unit 111, a wholesale transmission / reception server 14 that transmits / receives data to / from the wholesale 3 computer via the transmission / reception processing unit 141, A business server 12 that executes business processing of data transmitted / received via the retail transmission / reception server 11 and wholesale transmission / reception server 14, a host 13 having a transmission / reception processing unit 131, and a system date / time for managing the current date / time Business data (retail format, EDI security) received from the wholesale 3 side and retail 2 computers. Intermediate format, fixed-length format, distribution BMS format) is converted into an intermediate format (XML language format) in the business server 12, and after necessary business processing is performed, it is converted to a destination data format and transmitted. It is configured.

  The EDI center 1 includes a job execution management unit 121 that controls program execution in the EDI center, a conversion processing unit 122 that executes data conversion in a retail format, an EDI center intermediate format, a fixed length format, and a distribution BMS format, A business processing unit 123 that executes processing defined for each message, a connection destination management DB 124 that stores connection destination setting information, a connection destination parameter storage unit 125 that stores definition information of connection destinations as parameters, and The connection destination management DB 124 is referred to, and the connection destination parameter output processing unit 126 outputs the connection destination parameters every day.

  The conversion processing unit 122 has four types of business data formats used for commercial transactions: retail (CSV) format, EDI center intermediate (XML) format, fixed length format, and distribution BMS format. Execute. The conversion processing unit 122 has a function of converting input data into data of an appropriate format according to a processing instruction of the job execution management unit 121, and a connection destination parameter stored in the connection destination parameter storage unit 125 at the time of data conversion. And has a function of switching the data conversion method. The distribution BMS has a plurality of versions (Ver.1.0, Ver.2.0...), And each version needs to be converted. The various functions in the present application may be configured as software operating on a computer, or the functions may be achieved as hardware.

  The transmission procedure and data format of business data by the transmission / reception servers 11 and 14 differ depending on the computer system of wholesale 3 and retail 2, and JCA procedure (customer data exchange standard communication control procedure prescribed by Japan Chain Store Association), ebXML procedure (International standard specification for inter-company electronic commerce using XML), JX procedure (guideline established based on international standard specification [SOAP-RPC] for message exchange procedure for inter-company EDI) There are four types of data formats, CSV / XML / fixed length / distribution BMS, but the present invention is not limited to this.

  The connection destination management DB 124 stores a system switching mode in advance, and stores switching information (connection parameters) as shown in FIG. 5 when the following items are assumed as an example of the system switching mode. .

[Prerequisite system switching mode]
(1) Wholesale A computer (hereinafter abbreviated as “Wholesale A”) started operation on January 1, 2008 in JCA procedure, fixed-length format data format.
(2) Wholesale B computer (hereinafter abbreviated as “Wholesale B”) started on January 1, 2008 with ebXML procedure, distribution BMS Ver. Operates in 1.0 data format.
(3) Wholesale A has passed the parallel operation period of 1 month from April 1, 2008 to April 30, 2008, and from May 1, 2008, ebXML procedure, distribution BMS Ver. Moved to 1.0 data format.
(4) Wholesale B has passed the parallel operation period of 1 month from April 1, 2008 to April 30, 2008, and from May 1, 2008, ebXML procedure, distribution BMS Ver. Moved to 2.0 data format.

  The connection destination parameters (switching information) registered in the connection destination management DB 124 shown in FIG. 5 according to the present embodiment include, for example, a connection destination such as “wholesale A”, a business type such as “ordering”, and “2008 / Operation start date such as “1/1”, operation end date such as “2008/4/30”, communication procedure such as “JCA procedure”, data format such as “fixed length”, “production” and “test” And the above-described flags for each communication destination / work type / period / communication procedure / data format / test or production. This connection destination parameter is rewritten, for example, from the state before the parallel operation plan shown in FIG. 4 to the state after the parallel operation plan shown in FIG.

  When the system date / time corresponding to the date of the current day is 2008/3/1 from the connection destination management DB 124 in the daily batch processing, the connection destination parameter output processing unit 126 stores the business type and communication procedure or data format of the corresponding date. The record is retrieved and output, and stored in the connection destination parameter storage unit 125.

[Destination parameters as of 2008/03/01]
For example, when the system date is 2008/3/1, the connection date stored in the connection parameter storage unit 125 includes the system date and time from the connection destination management DB 124 as the operation start date and the operation end date, and the actual date. Alternatively, the corresponding record of the connection destination parameter that matches each trial (test) type is output, for example, as shown in FIGS.

  For example, FIG. 6 shows a connection destination parameter record for a production communication procedure with a job type “Order” and an operation flag “Production” as of 2008/3/1 retrieved from the connection destination management DB 124 and output. , “Wholesale A” is a setting of “JCA procedure”, and “Wholesale B” is a setting of “ebXML procedure”. Similarly, FIG. 8 shows a connection destination parameter record in the production data format in which the business type at the time of 2008/3/1 is “Order” and the operation flag is “Production”, and is output. "Is a setting of" fixed length "and" wholesale B "is a setting of" distribution BMS version 1.0 ". Further, FIG. 7 searches for the trial communication procedure for the “ordering” business on the same day, and FIG. 9 retrieves the trial data format for the “ordering” business on the same day, but there is no record that satisfies these conditions. Represents that.

[Destination parameters as of 2008/04/01]
Similarly, when the system date and time is 2008/4/1, the connection destination parameter storage unit 125, as shown in FIG. 10 to FIG. 13, connects to the connection destination parameter record of the actual communication procedure for each connection destination on the corresponding day (FIG. 10). Connection destination parameter record (FIG. 11) of trial communication procedure for each connection destination, production data format for each connection destination (FIG. 12), connection destination parameter record for trial data format for each connection destination (FIG. 11) 12) is stored.

[Connection destination parameters as of 2008/05/01]
Similarly, when the system date and time is 2008/5/1, the connection destination parameter storage unit 125, as shown in FIG. 14 to FIG. 17, connects to the connection destination parameter record of the actual communication procedure for each connection destination on the corresponding day (FIG. 14). Connection destination parameter record of trial communication procedure for each connection destination (FIG. 15), connection destination parameter record of actual data format for each connection destination (FIG. 16), connection of trial data format for each connection destination The destination parameter record (FIG. 17) is stored.

[Other business connection parameters]
The connection destination parameters stored in the connection destination parameter storage unit 125 are not limited to the above-mentioned “ordering” work, but for each connection destination on the corresponding day of the “advance shipment” work shown in FIGS. Connection destination parameter record for actual communication procedure (FIGS. 18, 22, and 26), connection destination parameter record for trial communication procedure for each connection destination (FIGS. 19, 23, and 27), for each connection destination The connection destination parameter record (FIGS. 20, 24, and 28) in the production data format and the connection destination parameter record (FIGS. 21, 25, and 29) in the trial data format for each connection destination are stored.

[Operation]
Next, the operation of the operation method of the EDI system configured as described above according to the present embodiment will be described for each received data type and period.
[Operation when order data is received as of 3/1/2008: Only the old system is in operation]
(1) First, the operation of the EDI center 1 when order data from a retail 2 computer to a wholesale 3 computer is transmitted on 2008/3/1 will be described with reference to FIG.

  In the EDI center 1, when the transmission / reception processing unit 111 of the EDI center 1 receives the order data from the retailer on the date 2008/3/1 (step S21), the job execution management unit 121 calls the conversion processing unit 122 and receives it. The data (retail format) is converted into the EDI center intermediate format (step S22), and the job execution management unit 121 calls the job processing unit 123 for the converted received data, based on the data in the EDI center intermediate format. Business processing is executed (step S23).

In step S23, the business processing unit 123 refers to the connection destination parameters shown in FIGS. 8 and 9, and divides the data in the EDI center intermediate format into production data for wholesale A and production data for wholesale B. This is performed by executing a predetermined business process. The production / trial determination flag is embedded in the EDI center intermediate format data and is referred to by the conversion processing unit 122. (2) Next, in the EDI center 1, the job execution management unit 121 sets the conversion processing unit 122. The data is converted into data for wholesale A and wholesale B in the EDI center intermediate format (step S24). In step S24, the conversion processing unit 122 refers to the actual connection destination parameter shown in FIG. 8 for data processing for wholesale A, and determines that the data for wholesale A is fixed-length data. Based on the determination result, the conversion processing unit 122 converts the data for wholesale A into a fixed-length format, and the conversion processing unit 122 sets the actual connection destination parameter in FIG. 8 for data processing for wholesale B. The data for wholesale B is distributed BMS Ver. 1.0, and based on the determination result, the conversion processing unit 122 distributes data for wholesale B to the distribution BMS Ver. This is done by converting to 1.0 format.

(3) Further, the EDI center 1 transmits the data converted in step S24 by the job execution management unit 121 to wholesale B (step S25). In step S25, the job execution management unit 121 refers to the actual connection destination parameter in FIG. 6 for transmission to wholesale A, and determines that the communication procedure to wholesale A is the JCA procedure. 6, the job execution management unit 121 calls the transmission / reception processing unit 131 of the host 13 to transmit fixed-length data for wholesale A, and the job execution management unit 121 transmits the data to wholesale B in FIG. , It is determined that the communication procedure to wholesale B is an ebXML procedure, and based on this determination result, job execution management unit 121 calls transmission / reception processing unit 141 of wholesale transmission / reception server 14, Distribution BMS Ver. This is done by sending 1.0 format data.
Thus, at the time of 2008/3/30, both wholesalers A and B are operating only in the old system, so the connection destination parameters (data format and communication procedure) held in the connection destination parameter storage unit 125 are in the previous format. Conversion and transmission are performed according to (Wholesale A: JCA communication procedure and fixed length format, Wholesale B: ebXML communication procedure and distribution BMS Ver1.0 format).

[Operation when order data is received as of April 1, 2008: Parallel operation]
Next, when the ordering data from the retail 2 computer is received on 2008/4/1 by the transmission / reception processing unit 111 of the EDI center 1 (step S21 in FIG. 2), the job execution management unit 121 converts the EDI center 1 The processing unit 122 is called to convert the received data (retail format) into the EDI center intermediate format (step S22), and then the job execution management unit 121 calls the job processing unit 123 to perform the job processing using the converted intermediate data. Execute (Step S23).

In the conversion process in step S23, the conversion processing unit 122 executes the following process.
(1) With reference to the production connection destination parameters shown in FIG. 12, it is determined that the production data for wholesale A is in a fixed-length format, and the intermediate data format for wholesale A is converted into a fixed-length format.
(2) Referring to the trial connection destination parameters shown in FIG. 13, trial data for wholesale A is distributed BMS Ver. 1.0 format, and the intermediate data format for wholesale A is distributed BMS Ver. Convert to 1.0 format.
(3) Referring to the production connection parameter in FIG. 12, the production data for wholesale B is distributed BMS Ver. 1.0 and determine that the production data for wholesale B is distributed BMS Ver. Convert to 1.0.
(4) Referring to the trial connection parameter in FIG. 13, trial data for wholesale B is distributed BMS Ver. 2.0 and determine trial data for wholesale B as distribution BMS Ver. The difference between the data contents of the wholesale data described above and the trial data is only the production / trial discrimination flag.

Next, the job execution management unit 121 of the EDI center 1 transmits the data converted in step S24 in the following manner according to the communication procedure defined for wholesalers A and B.
(5) Refer to the production connection destination parameter in FIG. 10 for transmission of production data to wholesale A, and determine that the production communication procedure to wholesale A is JCA.
(6) The transmission / reception processing unit 131 of the host 13 is called and fixed length data for wholesale A is transmitted.
(7) The trial connection destination parameter in FIG. 11 is referred to for trial data transmission to wholesale A, and it is determined that the trial communication procedure to wholesale A is ebXML.
(8) Call the transmission / reception processing unit 141 of the wholesale side transmission / reception server 14 to distribute the distribution BMS Ver. 1.0 data is transmitted.

(9) Refer to the production connection destination parameters in FIG. 10 for transmission of production data to wholesale B, and determine that the production communication procedure to wholesale B is ebXML.
(10) Call the transmission / reception processing unit 141 of the wholesale side transmission / reception server 14 and distribute the distribution BMS Ver. 1.0 data is transmitted.
(11) The trial connection destination parameter in FIG. 11 is referred to for trial data transmission to wholesale B, and it is determined that the trial communication procedure to wholesale B is ebXML.
(12) Calls the transmission / reception processing unit 141 of the wholesale side transmission / reception server 14 and distributes the distribution BMS Ver. Send 2.0 data.

  As described above, the EDI center 1 according to the present embodiment is operating in both the old and new systems (the old is the production and the new is the trial) in the period of 04/0 to 04/30 which is the parallel period. The connection destination parameters (data format and communication procedure) held in the connection destination parameter storage unit 125 are the old and new formats (wholesale A old: JCA communication procedure and fixed length format, wholesale A new: ebXML communication procedure and distribution BMS Ver1. 0, wholesale B old: ebXML communication procedure and distribution BMS Ver1.0 format, wholesale B new: ebXML communication procedure and distribution BMS Ver2.0 format).

[Operation when receiving order data as of 5/1/2008: After transition to new system]
Next, when the ordering data from the retailer is received on 2008/5/1 by the transmission / reception processing unit 111 of the EDI center 1 (step S21 in FIG. 2), the job execution management unit 121 converts the EDI center 1 into the conversion processing unit 122. The received data (retail format) is converted into the EDI center intermediate format (step S22), and then the job execution management unit 121 calls the business processing unit 123, and executes the business processing using the converted intermediate data (step S22). Step S23).

In the reception to conversion processing in steps S21 to S22, the conversion processing unit 122 executes the following processing.
(1) Referring to the connection destination parameters in FIGS. 16 and 17, the data in the EDI center intermediate format is divided into production data for wholesale A and production data for wholesale B.
(2) For data processing for wholesale A, the data for wholesale A is distributed BMS Ver. It is determined that the data is 1.0.
(3) Distribution of data for wholesale A to BMS Ver. Convert to 1.0 format.
(4) For data processing for wholesale B, refer to the connection destination parameters for production in FIG. 16 and the data for wholesale B is distributed BMS Ver. 2.0 is determined.
(5) Distribution of data for wholesale B to BMS Ver. Convert to 2.0 format.

Next, the EDI center 1 performs data transmission according to the communication procedure addressed to each wholesaler by the job execution management unit 121 executing the next step S24.
(6) Refer to the actual connection destination parameter in FIG. 14 for transmission to wholesale A, and determine that the communication procedure to wholesale A is the ebXML procedure.
(7) Calls the transmission / reception processing unit 141 of the wholesale side transmission / reception server 14 and distributes BMS Ver. Send data in 1.0 format.
(8) Refer to the actual connection destination parameter in FIG. 14 for transmission to wholesale B, and determine that the communication procedure to wholesale B is the ebXML procedure.
(9) Call the transmission / reception processing unit 141 of the wholesale side transmission / reception server 14 and distribute the distribution BMS Ver. Send 2.0 format data.

As described above, since the EDI center 1 according to the present embodiment is operating in the new system for both wholesalers A and B as of 2008/5/1, the connection destination parameter (data format) is held in the connection destination parameter storage unit 125. And communication procedure) are converted and transmitted in a new format (wholesale A new: ebXML communication procedure and distribution BMS Ver1.0, wholesale B new: ebXML communication procedure and distribution BMS Ver2.0 format).
As described above, when the EDI center 1 according to the present embodiment receives the order data from the retail side, the job execution management unit 121 converts the order data received by the job execution management unit 121 into the EDI center intermediate format and executes a predetermined business process. The data format and communication procedure corresponding to the wholesaler on the current day stored in the connection destination parameter storage unit 125 is determined, the data after the business processing described above is converted according to the determined data format, and the converted data is determined as the determination It operates to send to the wholesaler according to the communication procedure.

Next, an operation when the EDI center 1 according to the present embodiment transmits advance shipment data from the wholesaler to the retailer will be described with reference to FIG.
[Operation when receiving shipping data from wholesaler A as of 3/1/2008: When operating only the old system]
(1) When pre-shipment data from wholesaler A is received on 2008/3/1 by the transmission / reception processing unit 131 of the host 13 (step S31), the job execution management unit 121 calls the conversion processing unit 122 to receive data (fixed) (Long) is converted to the EDI center intermediate format (step S32).
(2) The job execution management unit 121 executes business processing based on the data in the EDI center intermediate format (step S33).
(3) The job execution management unit 122 calls the conversion processing unit 122 to convert EDI center intermediate format data into retail format data (step S34).
(4) The job execution management unit 122 calls the transmission / reception processing unit 111 of the retail-side transmission / reception server 11 and transmits retail-format data to the retail 2 (step S35).

[Operation when receiving shipment data from wholesale B as of 3/1/2008: When operating only the old system]
(1) When the transmission / reception processing unit 141 of the wholesale transmission / reception server 14 receives pre-shipment data from wholesale B on 2008/3/1 (step S31), the job execution management unit 121 calls the conversion processing unit 122 and receives it. Data (distributed BMS Ver.1.0 format) is converted into an EDI center intermediate format (step S32).
(2) The job execution management unit 121 executes business processing based on the data in the EDI center intermediate format (step S33).
(3) The job execution management unit 122 calls the conversion processing unit 122 to convert EDI center intermediate format data into retail format data (step S34).
(4) The job execution management unit 122 calls the transmission / reception processing unit 111 of the retail-side transmission / reception server 11 and transmits retail-format data to the retail 2 (step S35).

[Operation when receiving shipment data from wholesaler A as of April 1, 2008: Parallel A during previous operation]
(1) When pre-shipment data from wholesaler A is received on 2008/4/1 by the transmission / reception processing unit 131 of the host 13 (step S31), the job execution management unit 121 calls the conversion processing unit 122 to receive data (fixed) (Long) is converted to the EDI center intermediate format (step S32).
(2) The job execution management unit 121 executes business processing based on the data in the EDI center intermediate format (step S33).
(3) The job execution management unit 122 calls the conversion processing unit 122 to convert EDI center intermediate format data into retail format data (step S34).
(4) The job execution management unit 122 calls the transmission / reception processing unit 111 of the retail-side transmission / reception server 11 and transmits retail-format data to the retail 2 (step S35).

[Operation when receiving shipping data from wholesaler A as of April 1, 2008: When parallel A is in operation]
(1) When the pre-shipment data from wholesale A on 2008/4/1 is received by the transmission / reception processing unit 141 of the wholesale transmission / reception server 14 (step S31), the job execution management unit 121 calls the conversion processing unit 122 and receives it. Data (distributed BMS Ver.1.0) is converted into an EDI center intermediate format (step S32).
(2) The job execution management unit 121 executes business processing based on the data in the EDI center intermediate format (step S33).
(3) The job execution management unit 122 calls the conversion processing unit 122 to convert EDI center intermediate format data into retail format data (step S34).
(4) The job execution management unit 122 calls the transmission / reception processing unit 111 of the retail-side transmission / reception server 11 and transmits retail-format data to the retail 2 (step S35).

[Operation when receiving shipment data from wholesale B as of April 1, 2008: When parallel B is operating]
(1) When the pre-shipment data from wholesale B on 2008/4/1 is received by the transmission / reception processing unit 141 of the wholesale transmission / reception server 14 (step S31), the job execution management unit 121 calls the conversion processing unit 122 and receives it. Data is converted into an EDI center intermediate format (step S32). At this time, the conversion processing unit 122 opens the received data before conversion, acquires the version of the distribution BMS message and the production / trial determination flag, and refers to the connection destination parameters in FIGS. 24 and 25 to acquire the acquired data. It is determined whether or not the combination exists in the connection destination parameter. The combination includes distribution BMS Ver. 1.0 & combination with production, or distribution BMS Ver. 2.0 & is a determination of whether it is a combination of trials.

(2) The conversion processing unit 122 executes conversion processing according to the acquired version, and converts it into the EDI center intermediate format (step S32).
(3) The job execution management unit 121 executes business processing based on the data in the EDI center intermediate format (step S33).
(4) The job execution management unit 122 calls the conversion processing unit 122 to convert EDI center intermediate format data into retail format data (step S34).
(5) The job execution management unit 122 calls the transmission / reception processing unit 111 of the retail-side transmission / reception server 11 and transmits retail-format data to the retail 2 (step S35).

[Operation when receiving shipping data from wholesaler A as of 5/1/2008: When new A is operating]
(1) When the transmission / reception processing unit 141 of the wholesale transmission / reception server 14 receives pre-shipment data from the wholesaler A on 2008/5/1 (step S31), the job execution management unit 121 calls the conversion processing unit 122 and receives it. Data (distributed BMS Ver.1.0) is converted into an EDI center intermediate format (step S32).

(2) The job execution management unit 121 executes business processing based on the data in the EDI center intermediate format (step S33).
(3) The job execution management unit 122 calls the conversion processing unit 122 to convert EDI center intermediate format data into retail format data (step S34).
(4) The job execution management unit 122 calls the transmission / reception processing unit 111 of the retail-side transmission / reception server 11 and transmits retail-format data to the retail 2 (step S35).

[Operation when receiving shipping data from wholesale B as of 5/1/2008: When new B is operating]
(1) When pre-shipment data from wholesale B on 2008/5/1 is received by transmission / reception processing unit 141 of wholesale transmission / reception server 14 (step S31), job execution management unit 121 calls conversion processing unit 122 and receives it Data (distributed BMS Ver. 2.0) is converted into an EDI center intermediate format (step S32).

(2) The job execution management unit 121 executes business processing based on the data in the EDI center intermediate format (step S33).
(3) The job execution management unit 122 calls the conversion processing unit 122 to convert EDI center intermediate format data into retail format data (step S34).
(4) The job execution management unit 122 calls the transmission / reception processing unit 111 of the retail-side transmission / reception server 11 and transmits retail-format data to the retail 2 (step S35).

  As described above, the EDI system according to the present embodiment can handle system switching for wholesale A and wholesale B and operations for parallel operation only by maintenance of the connection destination management database, thereby reducing the man-hours involved in the operation as much as possible. Thus, even when the system is switched for a large number of connection destinations, it is possible to cope with very little man-hours.

The figure for demonstrating the EDI system to which the operation method by one Embodiment of this invention is applied. The flowchart figure which shows the process sequence at the time of transmitting the retail data from the retail side by this embodiment to the wholesale side. The flowchart figure which shows the process sequence at the time of transmitting the wholesale data from the wholesaler in this embodiment to the retail side. The data content figure which the connection destination management DB of the EDI center in this embodiment hold | maintains. The data content figure which the connection destination management DB of the same EDI center holds. The figure which shows the connection destination parameter which defined the communication procedure for the same production order. The figure which shows the connection destination parameter which defined the communication procedure for the trial ordering. The figure which shows the connection destination parameter which defined the data format for the same production order. The figure which shows the connection destination parameter which defined the data format for the trial ordering. The figure which shows the connection destination parameter which defined the communication procedure for the same production order. The figure which shows the connection destination parameter which defined the communication procedure for the trial ordering. The figure which shows the connection destination parameter which defined the data format for the same production order. The figure which shows the connection destination parameter which defined the data format for the trial ordering. The figure which shows the connection destination parameter which defined the communication procedure for the same production order. The figure which shows the connection destination parameter which defined the communication procedure for the trial ordering. The figure which shows the connection destination parameter which defined the data format for the same production order. The figure which shows the connection destination parameter which defined the data format for the trial ordering. The figure which shows the connection destination parameter which defined the communication procedure for the same advance shipping. The figure which shows the connection destination parameter which defined the communication procedure for the trial advance shipment. The figure which shows the connection destination parameter which defined the data format for the same advance shipping. The figure which shows the connection destination parameter which defined the data format for the trial advance shipment. The figure which shows the connection destination parameter which defined the communication procedure for the same advance shipping. The figure which shows the connection destination parameter which defined the communication procedure for the trial advance shipment. The figure which shows the connection destination parameter which defined the data format for the same advance shipping. The figure which shows the connection destination parameter which defined the data format for the trial advance shipment. The figure which shows the connection destination parameter which defined the communication procedure for the same advance shipping. The figure which shows the connection destination parameter which defined the communication procedure for the trial advance shipment. The figure which shows the connection destination parameter which defined the data format for the same advance shipping. The figure which shows the connection destination parameter which defined the data format for the trial advance shipment.

Explanation of symbols

  1: EDI center, 2: retail computer, 11: retail transmission / reception server, 12: business server, 13: host, 14: wholesale transmission / reception server, 111: transmission / reception processing unit, 121: job execution management unit, 122: conversion Processing unit 123: Business processing unit 124: Connection destination management database (DB) 125: Connection destination parameter storage unit 126: Connection destination parameter output processing unit 131: Transmission / reception processing unit 141: Transmission / reception processing unit

Claims (6)

One computer that transmits and receives data in a predetermined data format according to a predetermined communication procedure, the other computer that transmits and receives data in a predetermined data format according to a predetermined communication procedure, and the work of data received from the one or the other computer An information exchange computer system for transmitting to the other computer after processing,
The computer system is
A transmission / reception unit for transmitting / receiving arbitrary format data to / from the one and other computers according to an arbitrary communication procedure;
A conversion processing unit for converting data received from the one and other computers into an arbitrary data format;
A business processing unit that performs predetermined business processing of the data converted by the conversion processing unit;
A connection destination management database for storing a plurality of communication procedures and data formats with the one and the other computers for each period;
A system date / time management unit for managing the current system date / time;
A control unit for controlling the transmission / reception unit, the conversion processing unit, the business processing unit, and the connection destination management database;
The control unit
A first step in which the transceiver unit receives data in a predetermined format from one computer;
A second step of acquiring a date and time when the data is received from the system date and time management unit;
A third step of determining the data format of one computer of the date and time acquired in the second step from the connection destination management database;
A fourth step in which the conversion processing unit converts the data whose data format is determined in the third step into intermediate format data;
A fifth step in which the business processing unit performs business processing of the intermediate format data converted into the intermediate format in the fourth step;
A sixth step of acquiring the current date and time from the system date and time management unit;
A seventh step of determining the data format and communication procedure of the other computer of the date and time acquired in the sixth step from the connection destination management database;
An eighth step in which the conversion processing unit converts the intermediate format data subjected to the business process in the fifth step into the data format determined in the seventh step;
An information exchange computer system in which the transmission / reception unit executes the ninth step of transmitting the data converted in the eighth step to the other computer by the communication procedure acquired in the seventh step. The information exchange computer system stores two communication procedures and data formats for each computer and each period stored in the connection destination management database within one period, and
The control unit is
In the seventh step, the two data formats of the other computer and the communication procedure corresponding to the data format are determined from the connection destination management database,
In the eighth step, the intermediate format data processed in the fifth step is converted into the determined two data formats,
The information exchange computer system according to claim 1, wherein, in the ninth step, the two data converted into the two data formats are transmitted to the other computer by a communication procedure corresponding to the determined data format. The predetermined data format is a CSV format, a fixed length format and a business message standard format, the intermediate format data is an XML language format, and the predetermined communication procedure is a supplier data exchange standard defined by the Japan Chain Store Association. Established based on the JCA procedure, which is a communication control procedure, the ebXML procedure, which is a communication procedure based on the international standard specification for business-to-business electronic commerce in XML language, and the international standard specification for the message exchange procedure when performing EDI between businesses. JX procedure,
The control unit is
In the fourth step, the conversion processing unit is used to convert data in CSV format, fixed-length format, or business message standard format into XML language format,
In the eighth step, the data in the XML language format is converted into a CSV format, a fixed length format, or a business message standard format using the conversion processing unit,
The said 9th process WHEREIN: The data converted by this 8th process using the said transmission / reception part are transmitted to the other computer by the JCA procedure acquired in the 7th process, the ebXML procedure, or the JX procedure. Information exchange computer system. Transmission / reception unit for transmitting / receiving arbitrary format data according to an arbitrary communication procedure with one computer that transmits / receives data of a predetermined data format according to a predetermined communication procedure and the other computer that transmits / receives data according to a predetermined data format according to a predetermined communication procedure A conversion processing unit that converts data received from the one and other computers into an arbitrary data format, a business processing unit that performs predetermined business processing of the data converted by the conversion processing unit, and the one and the other Connection destination management database for storing a plurality of communication procedures and data formats with a computer for each period, a system date / time management unit for managing the current system date / time, the transmission / reception unit, the conversion processing unit, the business processing unit, and the connection destination management A control unit for controlling the database, and data received from the one or the other computer An information exchange computer system operation program to be transmitted to the other computer after the business process,
In the control unit,
A first function in which the transmission / reception unit receives data in a predetermined format from one computer;
A second function for acquiring a date and time when the data is received from the system date and time management unit;
A third function for determining the data format of one of the date and time acquired by the second function from the connection destination management database;
A fourth function in which the conversion processing unit converts the data whose data format has been determined by the third function into intermediate format data;
A fifth function in which the business processing unit performs business processing of intermediate format data converted into an intermediate format by the fourth function;
A sixth function for acquiring the current date and time from the system date and time management unit;
A seventh function for determining the data format and communication procedure of the other computer of the date and time acquired in the sixth step from the connection destination management database;
An eighth function in which the conversion processing unit converts the intermediate format data processed by the fifth function into the data format determined by the seventh function;
An operation program for an information exchange computer system for causing the transmission / reception unit to execute a ninth function of transmitting data converted in the eighth step to the other computer by a communication procedure acquired by a seventh function. The information exchange computer system operation program in which two communication procedures and data formats for each computer and each period stored in the connection destination management database are stored in one period,
In the control unit,
In the seventh function, a function of determining two data formats of the other computer and a communication procedure corresponding to the data format from the connection destination management database;
A function of converting the intermediate format data processed in the fifth function into the determined two data formats in the eighth function;
5. The information exchange computer according to claim 4, wherein the ninth function realizes a function of transmitting the two data converted into the two data formats to the other computer by a communication procedure corresponding to the determined data format. System operation program. The predetermined data format is a CSV format, a fixed length format and a business message standard format, the intermediate format data is an XML language format, and the predetermined communication procedure is a supplier data exchange standard defined by the Japan Chain Store Association. Established based on the JCA procedure, which is a communication control procedure, the ebXML procedure, which is a communication procedure based on the international standard specification for business-to-business electronic commerce in XML language, and the international standard specification for the message exchange procedure when performing EDI between businesses. JX procedure,
In the control unit,
In the fourth step, a function of converting data in a CSV format, a fixed length format, or a business message standard format into an XML language format using the conversion processing unit;
In the eighth step, a function for converting data in XML language format into CSV format, fixed-length format, or business message standard format using the conversion processing unit;
In the ninth step, the function of transmitting data to the other computer by the JCA procedure, the ebXML procedure, or the JX procedure obtained in the seventh step by using the transceiver unit in the data converted by the eighth step is realized. Item 6. An information exchange computer system operation program according to item 4 or 5.

Images