JP2005242933A - Slip registration processing system, slip registration processing method and slip registration processing program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a slip registration processing system, slip registration processing method and slip registration processing program for preventing double transfer at the time of executing a portion of slip registration processing in parallel without locking each IDoc. <P>SOLUTION: As for slip data received in parallel from a transmission side system 10, an EDI server 200 in a reception side system 20 issues a counter file number by each reception unit. As for each of a plurality of pieces of slip data included in the reception unit, the EDI server 200 issues a reception counter number, generates a record identifier constituted of a partner profile written in the received slip data and the counter file number and reception counter number issued to the slip data, identifies the slip data according to the generated record identifier, and executes slip registration processing in parallel. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a slip registration processing system, slip registration processing method, and slip registration processing program for executing slip registration processing in parallel.

Conventionally, the following methods are known as parallel processing techniques. For example, Patent Document 1 discloses a technique for parallelizing object selection processing. According to the present invention, the command distribution device that has input a plurality of commands compares the command storage amounts supplied from the plurality of FIFOs, and the serial number indicating the command transfer order in order from the FIFO having the smallest command storage amount. To distribute commands. The distributed commands are processed by a plurality of processors, and the processing results are output in the order of serial numbers.
Patent Document 2 discloses a technique for maintaining real-time processing, continuity, and input / output simultaneity when executing parallel processing. According to the present invention, when time-series data is input, it is stored as block data with the processing unit block time as a basic unit. Analytical processing is performed by generating time-series data for a certain period of time for analysis from this block data, and conversion data corresponding to the output time for the processing unit block time is generated and output at the corresponding time.
With this configuration, data conversion based on analysis of time series data can be performed.
JP 10-269373 A JP 2003-5951 A

Incidentally, in recent years, electronic data interchange (EDI) using electronic ordering information based on a standard is becoming widespread. Even if the application managing the ordering information is different between the sending EDI system and the receiving EDI system, an intermediate document (hereinafter referred to as IDoc: Intermediate Document) is used to link different applications and execute transactions. Execute.
For example, the receiving EDI system receives IDoc and executes slip registration processing. The IDoc received at a time consists of a plurality of slip data, and the slip registration process is executed for each of a plurality of slip data constituting one reception unit.
Since the processing order is not defined between the plurality of slip data constituting one reception unit, there is no restriction that any one must be processed first. Therefore, conventionally, a plurality of slip data within one receiving unit has been slip registered in parallel in order to improve the processing speed.

On the other hand, since the IDoc reception frequency is low between the IDocs, it is not necessary to execute a plurality of IDoc registration processes in parallel, and the IDocs are sequentially processed without being locked.
Therefore, when the IDoc reception frequency is increased, there is a problem in that slip data of a plurality of reception units is interlaced and double transcription occurs if the IDocs are processed in parallel without being locked.

The present invention has been made in view of such circumstances, and a first object is to prevent double posting when a part of the slip registration process is executed in parallel without locking each IDoc. It is an object to provide a slip registration processing system, slip registration processing method, and slip registration processing program.
A second object is to provide a slip registration processing system, slip registration processing method, and slip registration processing program capable of executing a part of IDoc registration processing in parallel while maintaining the processing order of reception units. is there.

  The present invention has been made to solve the above problems, and the present invention relates to counter file number issuing means for issuing a counter file number for each reception unit for slip data received in parallel from an external system, and for each reception unit. For each of a plurality of slip data included, a reception counter number issuing means for issuing a reception counter number, a partner profile written in the received slip data, and a counter file issued by the counter file number issuing means to the slip data A record identifier generating means for generating a record identifier consisting of a reception counter number issued to the slip data by the reception counter number issuing means and a record identifier generated by the record identifier generated by the record identifier generating means, Document that executes registration processing in parallel Characterized by comprising a recording means.

  According to the present invention, the slip data is received in an intermediate document format including a control record, a data record, and a status record, and the record identifier generating means is a counter file issued to the slip data by the counter file number issuing means. The number is set in the message variant of the slip data in the intermediate document format, and the reception counter number issued to the slip data by the reception counter number issuing means is set in the message function and written in the control record of the slip data A record identifier including a partner profile, a message variant, and a message function is generated using the partner profile.

  Further, in the present invention, the slip registration means identifies slip data by the record identifier generated by the record identifier generation means, and executes the slip registration processing in the intermediate document database in parallel for each reception unit. The slip registration process from the document database to the own system is executed in the order of reception units.

  In the present invention, the computer issues a counter file number for each reception unit for the slip data received in parallel from the external system, and issues a reception counter number for each of the plurality of slip data included in the reception unit, A slip registration process is performed by generating a record identifier including a partner profile written in the received slip data, a counter file number issued to the slip data and a reception counter number, and identifying the slip data with the generated record identifier. Are executed in parallel.

  The present invention also provides a process for issuing a counter file number for each reception unit for the slip data received in parallel from the external system, and a process for issuing a reception counter number for each of a plurality of slip data included in the reception unit. , A partner profile written in the received slip data, a process of generating a record identifier composed of a counter file number and a reception counter number issued to the slip data, and identifying the slip data with the generated record identifier, A slip registration processing program for causing a computer to execute processing for executing slip registration in parallel.

As described above, according to the present invention, for the slip data received in parallel from the external system, the computer issues a counter file number for each reception unit, and receives each of the plurality of slip data included in the reception unit. Issuing a counter number, generating a record identifier consisting of the partner profile written in the received slip data, the counter file number issued to the slip data and the received counter number, and identifying the slip data by the generated record identifier The slip registration process is executed in parallel.
Therefore, when the slip data registration processing is executed in parallel without locking each slip data for each reception unit, an effect of preventing double posting can be obtained. Further, it is possible to obtain an effect that a part of the slip data registration process can be executed in parallel while maintaining the processing order of the reception unit.

According to the present invention, the slip data is received in an intermediate document format composed of a control record, a data record, and a status record, and the counter file number is set in the message variant of the slip data in the intermediate document format, and the reception counter number Is set to the message function, and a record identifier including the partner profile, the message variant, and the message function is generated using the partner profile written in the control record of the slip data.
Therefore, in the case where the slip data registration processing is executed in parallel without locking each slip data for each IDoc reception unit, an effect that double transcription can be prevented is obtained. Further, it is possible to obtain an effect that a part of the slip data registration process can be executed in parallel while maintaining the processing order of the IDoc reception unit.

In addition, according to the present invention, slip data is identified by the generated record identifier, the slip registration processing to the intermediate document database is executed in parallel for each reception unit, and slip registration processing from the intermediate document database to the own system is performed. Execute in order of reception unit.
Accordingly, the slip data registration process is always executed in the order of reception units, so that the effect of being able to execute part of the slip data registration process in parallel while maintaining the processing order of IDoc reception units is obtained.

  Hereinafter, the best mode for carrying out the present invention will be described.

Hereinafter, an embodiment of a slip registration processing system of the present invention will be described with reference to the drawings. FIG. 1 is a configuration diagram of a slip registration processing system 1 according to the present embodiment.
As shown in FIG. 1, the slip registration processing system 1 of the present embodiment is configured by connecting a transmission side system 10 and a reception side system 20 via a network (not shown). EDI servers 100 and 200 and database systems 110 and 210 for implementing electronic transaction applications are provided.
An IDoc digitized based on a predetermined data format is used to transmit and receive messages (slip data) having different data structures between applications executed in the EDI servers 100 and 200 on the transmission side and the reception side. .

As illustrated in FIG. 2, the transmission-side system 10 includes an application 11, an IDoc output unit 12, an IDoc transmission unit 13, and a transmission mechanism 14. From the application 11 that is executed in the upper layer to the IDoc output unit 12. The transaction information is output, converted into IDoc by the IDoc output unit 12, and passed to the IDoc transmission unit 13 executed in the middle layer. Then, IDoc is transmitted to the receiving-side system 20 via the transmission mechanism 14 executed in the lower layer.
Similarly to the transmission side system 10, the reception side system 20 also has an application 21, an IDoc input unit 22, an IDoc reception unit 23, and a reception mechanism 24, and through the reception mechanism 24 executed in the lower layer, The IDoc receiving unit 23 receives IDoc, executes slip registration processing by the IDoc input unit 22, and then returns transaction information to the application 21 executed in the upper layer.

  In this way, the slip data is transmitted and received in the IDoc format between the transmission side system 10 and the reception side system 20. As shown in FIG. 3, the IDoc format used here includes a control record, a data record, and a status record. The IDoc control record parameters include partner profile identification information, message variant, and message function. The partner profile defines an order processing method for each slip data, is created for each transmission / reception unit, and is stored in the database systems 110 and 210 connected to the EDI servers 100 and 200. The message variant and message function are used to uniquely identify slip data in the IDoc format.

Specifically, the partner profile has data for storing the user's e-mail address, contact information, and the like, and is associated with IDoc identification information (IDoc number). Further, the partner profile is set as one for each system or server unit of the receiving destination, and an object ID is set for each order receiving party (customer) developed in each IDoc.
For example, each EDI server 100 of the plurality of transmission side systems 10 is registered using a partner profile, and is responsible for receiving orders corresponding to transaction information that is the source of IDoc issued from the EDI server 100. Each person in charge of the error notification destination is registered using the object ID.
The IDoc identification information is written, for example, in the IDoc data record described above.

Next, a specific configuration of the EDI server 200 in the receiving system 20 will be described. As shown in FIG. 4, the IDoc receiving unit 23 constructed in the EDI server 200 is composed of a plurality of EDI subsystems 201 and 202, and receives slip data for each reception unit from an external system (transmitting EDI server 100). In parallel reception, the processing is distributed to the respective EDI subsystems 201 and 202, and slip registration processing is executed. Each of the EDI subsystems 201 and 202 includes a counter file number issuing unit 30 and a counter number issuing unit 31 that generate identifiers for identifying each slip data in the IDoc format in units of reception and individual slip data. In the record identifier generation unit 32, the issued identifier is written in the message variant and message function of IDoc.
Specifically, the counter file number issuing unit 30 identifies the reception unit of the slip data received in parallel from the sending EDI server 100 by a file transfer identifier such as HULFTID of the slip data, and the counter file number for each reception unit. Issue. The counter number issuing unit 31 issues a reception counter number for each of a plurality of slip data included in the reception unit.

  The record identifier generation unit 32 receives the partner profile written in the received slip data, the counter file number issued by the counter file number issuing unit 30 to the slip data, and the reception counter number issuing unit 31 issued to the slip data. Generates a record identifier consisting of a counter number. At this time, the counter file number issued by the counter file number issuing unit 30 to the slip data is set in the message variant of the slip data in the IDoc format, and the reception counter number issued by the reception counter number issuing unit 31 to the slip data. Is set in the message function of the slip data in the IDoc format, and a record identifier including the partner profile, the message variant, and the message function written in the control record of the slip data is generated. In this way, the slip data reception unit is always uniquely determined.

  The IDoc input unit 22 constructed in the EDI server 200 has a slip registration unit 40. The slip registration unit 40 identifies the slip data with the record identifier generated by the record identifier generation unit 32, stores the slip data in the IDoc database 220 constructed in the database system 210, and then executes the slip data registration processing in parallel. To do. The slip data registration processing is executed in parallel for each reception unit until the slip registration processing in the IDoc database 220, and the slip registration processing from the IDoc database 220 to the application 21 in the own system is executed in the order of reception units.

Next, the operation of the slip registration processing system 1 of the present embodiment will be described with reference to the drawings. FIG. 5 is a flowchart showing the process of slip registration processing in the slip registration processing system 1 of the present embodiment.
First, as preprocessing for the receiving EDI server 200, a partner profile such as the transmitting EDI server 100 is registered in the database system 210.
When the receiving side EDI server 200 receives the slip data of one receiving unit to which the HULFTID is added as a file transfer identifier from the transmitting side EDI server 100, the IDoc receiving unit 23 sends the receiving unit of the receiving unit to the EDI subsystem 201. Assign slip registration processing of slip data.
In the EDI subsystem 201, first, the counter file number issuing unit 30 generates a counter file number (for example, 001) for identifying the one receiving unit, and the counter number issuing unit 31 sequentially includes the one receiving unit. A counter number for identifying each of the plurality of slip data is generated (see, for example, 001 to 004 in FIG. 6). With these identifiers, each slip data in the IDoc format is identified by the reception unit and individual slip data unit.

The record identifier generation unit 32 receives the partner profile written in the received slip data, the counter file number issued by the counter file number issuing unit 30 to the slip data, and the reception counter number issuing unit 31 issued to the slip data. Generates a record identifier consisting of a counter number.
At this time, the counter file number issued by the counter file number issuing unit 30 to the slip data is set in the message variant of the slip data in the IDoc format, and the reception counter number issued by the reception counter number issuing unit 31 to the slip data. Is set in the message function of the slip data in the IDoc format, and a record identifier including the partner profile, the message variant, and the message function written in the control record of the slip data is generated.
In this way, the slip data reception unit is always uniquely determined.

On the other hand, the IDoc receiving unit 23 receives the slip data in parallel for each reception unit from the sending EDI server 100, and further distributes the processing to the EDI subsystem 202 to execute the slip registration processing. That is, the EDI subsystem 202 starts a slip registration process for slip data of one receiving unit assigned by the IDoc receiving unit 23, as in the EDI subsystem 201.
Similar to the EDI subsystem 201, the EDI subsystem 202 first generates a counter file number for identifying the one reception unit in the counter file number issuing unit 30.
A counter file number generated by the counter file number issuing unit 30 is assigned a one-way identifier such as a serial number in a plurality of EDI subsystems in the EDI server 200. Specifically, the latest counter file number (for example, 001) is always incremented by 1 and issued as the next latest counter file number (for example, 002).

On the other hand, in the counter number issuing unit 31, when a new counter file number is assigned to the EDI subsystem 202, the counter number for sequentially identifying each of the plurality of slip data included in the one reception unit is obtained. Generate (for example, 001 to 004). With these identifiers, each slip data in the IDoc format is identified by the reception unit and individual slip data unit.
As in the previous case, the record identifier generation unit 32 has the partner profile written in the received slip data, the counter file number issued by the counter file number issuing unit 30 and the received counter number issuing unit 31 in the slip data. Generate a record identifier consisting of the reception counter number issued to the data.
At this time, the counter file number issued by the counter file number issuing unit 30 to the slip data is set in the message variant of the slip data in the IDoc format, and the reception counter number issued by the reception counter number issuing unit 31 to the slip data. Is set in the message function of the slip data in the IDoc format, and a record identifier including the partner profile, the message variant, and the message function written in the control record of the slip data is generated.
In this way, the slip data reception unit is always uniquely determined.

  By configuring in this way, for example, even if the partner profile is received multiple times in a short time from the same recipient, the reception unit of the slip data is always uniquely determined, so double reception The effect which can prevent is acquired.

When the identifier of the slip data indicated by partner profile × message variant × message function is mapped to the control record, the EDI subsystems 201 and 202 output the slip data of the reception unit to the IDoc input unit 22.
In this way, the EDI subsystems 201 and 202 (or the IDoc receiving unit 23) use the message variant and message function that are parameters of the IDoc control record, and the variant so that the IDoc format slip data is unique. Set and execute parallel processing.

That is, when the EDI subsystems 201 and 202 receive the slip data from the external system, a variant name (record identifier) including a partner profile, a message variant, and a message function is generated and stored in the IDoc database 220.
However, the partner profile is read from the slip data, and the message variant code is read from the counter file No generated for each HULFTID. Further, the message function is read from the reception counter No. which is counted for each order data written in the slip data of the reception unit (HULFTID).
The IDoc input unit 22 inputs the slip data of each reception unit input from the EDI subsystems 201 and 202 to the IDoc database 220 constructed in the database system 210 and registers in parallel with the record identifiers generated in this way. Identify the slip data to be processed. Then, the IDoc input unit 22 activates the slip registration unit 40 for each slip data, and executes an order slip registration process.

FIG. 7 shows the flow of processing when the slip registration unit 40 is activated in parallel. As shown in FIG. 7, when individual processing is performed in each EDI server 201, 202 (step S1 in FIG. 7) and the registration process in the IDoc database 220 is completed (step S2), the order slip registration process in the application 22 is performed. Is executed (step S3). At this point, the slip registration unit 40 is activated. The slip registration unit 40 is triggered by the fact that slip data for one reception unit is registered in the IDoc database 220, and assigns all slip data for one reception unit to a plurality of processes (threads) for parallel processing ( Voucher registration kick process Step S4).
Since the activation of the slip registration unit 40 is performed in the order of registration in the IDoc database 220, when the result of the parallel processing after the kick processing returns in the order of activation of the slip registration unit 40, the processing order of the reception unit is maintained. Yes. However, when the result of parallel processing is nested, there is a problem that the processing does not end in the order of activation.

Therefore, as shown in FIG. 8, the next order receiving process is made to wait until the slip registration kick process for one receiving destination is completed. Specifically, the individual processing (step S1), IDoc registration processing (step S2), and order registration processing (step S3) are processed in parallel, and the subsequent slip registration kick processing (step S4) is one receiving unit. After confirming that all the slip data has been processed, the slip data of the next reception unit is processed.
That is, after waiting for notification of completion of the slip registration kick process (step S4) for the slip data of the first reception unit (steps S5 and S6), the slip registration kick process is executed for the slip data of the next reception unit. (Steps S7 to S10).
In this way, after sequentially waiting for notification of completion of the slip registration kick process for the slip data of the previous reception unit (steps S7 to S10), the slip registration kick process is executed for the slip data of the next reception unit. (Steps S11 to S14).

  With this configuration, when parallel processing is performed between a plurality of slip data constituting one reception unit, it is possible to prevent slip data of subsequent reception units from being nested. The slip registration process is guaranteed.

As described above, according to the slip registration system 1 of the present embodiment, the EDI server 200 in the receiving system 20 issues a counter file number for each reception unit for slip data received in parallel from the sending system 10. For each of a plurality of slip data included in the reception unit, a reception counter number is issued, and includes a partner profile written in the received slip data, a counter file number and a reception counter number issued to the slip data. A record identifier is generated, slip data is identified by the generated record identifier, and slip registration processing is executed in parallel.
Therefore, double transfer can be prevented when the slip data registration processing is executed in parallel without locking each slip data for each reception unit. In addition, part of the slip data registration process can be executed in parallel while maintaining the processing order of the reception units.

A series of processes related to the slip registration process described above is stored in a computer-readable recording medium in the form of a program, and the above process is performed by the computer reading and executing this program.
That is, each processing means and processing unit in the EDI servers 100 and 200 is such that a central processing unit such as a CPU reads the above program into a main storage device such as a ROM or a RAM and executes information processing / calculation processing. Is realized.
Here, the computer-readable recording medium means a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, or the like. Alternatively, the computer program may be distributed to the computer via a communication line, and the computer that has received the distribution may execute the program.

1 is a configuration diagram of a slip registration processing system 1. FIG. Explanatory drawing of IDoc transmission / reception. The data block diagram of IDoc. 1 is a configuration diagram of an EDI server 200. FIG. The flowchart of a slip registration process. The data block diagram of the reception parameter of slip data. The flowchart which parallelized slip registration kick processing. The flowchart which does not parallelize slip registration kick processing.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Slip registration processing system 10 ... Transmission side system 11, 21 ... Electronic commerce application 12 ... IDoc output part 13 ... IDoc transmission part 14 ... Transmission mechanism 20 ... Reception side system 22 ... IDoc input part 23 ... IDoc reception part 24 ... Reception Mechanism 30 ... counter file number issuing unit 31 ... counter number issuing unit 32 ... record identifier generating unit 40 ... slip registration unit 100 ... sending EDI server 200 ... receiving EDI server 110, 210 ... database system 201, 202 ... EDI subsystem 220 ... IDoc database

Claims (5)

Counter file number issuing means for issuing a counter file number for each reception unit for slip data received in parallel from an external system;
Receiving counter number issuing means for issuing a receiving counter number for each of a plurality of slip data included in the receiving unit;
A record identifier comprising a partner profile written in the received slip data, a counter file number issued to the slip data by the counter file number issuing means, and a reception counter number issued to the slip data by the receiving counter number issuing means A record identifier generating means for generating
A slip registration processing system comprising: slip registration means for identifying slip data with a record identifier generated by the record identifier generation means and executing slip registration processing in parallel. The slip data is received in an intermediate document format consisting of a control record, a data record and a status record,
The record identifier generating means sets the counter file number issued to the slip data by the counter file number issuing means in a message variant of slip data in the intermediate document format, and the reception counter number issuing means adds to the slip data. The issued reception counter number is set in a message function, and a record identifier including a partner profile, a message variant, and a message function is generated using a partner profile written in the control record of the slip data. The slip registration processing system according to 1. The slip registration means identifies slip data by the record identifier generated by the record identifier generation means, and executes in parallel for each reception unit until slip registration processing in the intermediate document database, from the intermediate document database to the own system. The slip registration processing system according to claim 1, wherein the slip registration processing is executed in the order of reception units. Computer
For slip data received in parallel from an external system, issue a counter file number for each reception unit,
For each of a plurality of slip data included in the reception unit, issue a reception counter number,
Generate a record identifier consisting of a partner profile written in the received slip data, a counter file number issued to the slip data and a reception counter number,
A slip registration processing method, wherein slip data is identified by the generated record identifier, and slip registration processing is executed in parallel. For slip data received in parallel from an external system, processing to issue a counter file number for each reception unit;
A process of issuing a reception counter number for each of a plurality of slip data included in the reception unit;
A process of generating a record identifier comprising a partner profile written in the received slip data, a counter file number issued to the slip data, and a reception counter number;
A slip registration processing program for causing a computer to execute slip registration in parallel by identifying slip data with the generated record identifier.

Images