JP2003296159A - Edi-erp coordination system and coordination method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce the load on a system operator in an EDI-ERP (electronic data interchange-enterprise resource planning) cooperation system. <P>SOLUTION: In this system, since an error generated in at least one of transmitting processing and receiving processing of an EDI system 1 is reported to an ERP system 2, a person in charge need not regularly monitor whether a processing is normally ended or not, and its load can be reduced. After the error is reported, the transmitting processing state, receiving processing state, operation record and processing data in the EDI system 1 can be collated from the ERP system 2 side, and the correction of a conversion master file 5 can be performed from the ERP system 2. Accordingly, the repair can be easily and quickly performed. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

TECHNICAL FIELD The present invention relates to an EDI (Electro)
nic Data Interchange system and ERP (Enterpr)
The present invention relates to a cooperation system and a cooperation method with an ise Resource Planning system.

[0002]

[Prior Art] Conventionally, each company has
There is ERP (Corporate Resource Planning) as a concept for effectively utilizing the management resources of a company by integrating the core system developed at each head office. The package software that realizes this ERP concept is an integration of multiple subsystems such as financial accounting, management accounting, inventory / purchasing management, sales management, production planning / management, and quality management.
This enables centralized management within the company.

On the other hand, since it has become possible to exchange data online between companies, "data for commercial transactions between different companies can be exchanged via a communication line under standard rules (various widely agreed upon types). The concept of "between computers (including terminals) is exchanged using the rules"
(Electronic data exchange). The EDI system is a system that controls data transmission.

[0004]

The data format of the EDI system is a standardized format for the purpose of exchanging data between a plurality of companies. on the other hand,
The data format of the ERP system is the format conventionally used in the company. Therefore, conceptually, the same information is completely different.

Therefore, there is a need for a system that links the EDI system and the ERP system. EDI-ERP
The cooperation system is composed of a plurality of steps in order to perform conversion processing from the EDI system to the ERP system or from the ERP system to the EDI system, and the cooperation process is normally executed several times a day. .

Conventionally, a person in charge constantly monitors whether or not the cooperative processing has been normally completed, and when an abnormality occurs, the procedure for recovering is complicated, or
Since the two systems are linked, it is necessary to perform operation management from each system, which poses a great burden on the operator.

The present invention has been made in view of the above points, and it is an object of the present invention to reduce the burden on the person in charge of operating a system.

[0008]

In order to achieve the above-mentioned object, the present invention is constructed as follows.

That is, the present invention links an EDI system for electronically exchanging information on commercial transactions between companies and an ERP system for integrated management of management resources of the companies, wherein the EDI system comprises: While performing a transmission process of converting the transmission data from the ERP system based on the conversion master file and transmitting it to the outside,
Receiving data from the outside is converted based on the conversion master file and is transferred to the ERP system. The receiving process is performed by at least one of the transmitting process and the receiving process of the EDI system. The generated error is notified to the ERP system.

According to the present invention, the ERP system is notified of an error that has occurred in at least one of the sending process and the receiving process of the EDI system, so that the person in charge must constantly monitor whether or not the process is completed normally. Without
The burden is reduced.

In a preferred embodiment of the invention, E
In response to a request from the RP system, the status of transmission processing, the status of reception processing, operation records and processing data in the EDI system are transferred to the ERP system.

According to the present invention, after an error is notified to the ERP system, for example, in order to investigate the cause of the error, the ERP system sends a message to the EDI system.
If the transmission processing status, the reception processing status, the operation record, and the processing data are requested as needed, the requested information is E
Since it is transferred to the RP system, it is possible for the ERP system side to easily identify the cause of the error based on the information and take appropriate action.

In one embodiment of the invention, the ER
The conversion master file modified by the P system is transferred to the EDI system.

According to the present invention, after the defect of the conversion master file causing the error is corrected on the ERP system side, it is transferred to the EDI system and the conversion master file of the EDI system can be replaced with the corrected conversion master file. it can.

In still another embodiment of the present invention, the EDI system re-executes the processing in which the error occurred based on the modified conversion master file.

According to the present invention, the EDI system can be re-executed from the processing in which an error has occurred, based on the corrected conversion master file, and can be quickly recovered.

[0017]

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a schematic configuration diagram of an EDI-ERP cooperation system according to one embodiment of the present invention.

This EDI-ERP cooperation system uses the ED
The I system 1 and the ERP system 2 cooperate with each other to communicate with the outside via a network 3 such as JD-NET.

In the ERP system 2, the person in charge of business operations 4 performs each job such as warehousing processing, warehousing processing and billing processing, and is provided with a conversion master file 5.

The EDI system 1 has a conversion master file 5 synchronized with the conversion master file 5 of the ERP system 2.
The transmission data from the ERP system 2 is used as the unprocessed data 6 and is converted by the processing means 8 based on the conversion master file 5 and is processed as the processed data 7 to the outside via the network 3. While performing the transmission process of transmitting, the reception process of converting the received data from the outside as the unprocessed data 6 by the processing means 8 based on the conversion master file 5 and transferring it as the processed data 7 to the ERP system 2. It is something to do. Also, this EDI
The system 1 includes a transaction master file 10 and an operation record file 11.

The ERP system 2 performs the inquiry processing described later to virtually treat the pre-processing data, the post-processing data, the transaction master file, and the operation recording file in the EDI system as shown by the broken line, in the vicinity of the person in charge of business operation 4. It is the same as the one placed in.

In the EDI-ERP cooperation system of this embodiment, it is not necessary for the business staff member 4 to constantly monitor whether or not the cooperation processing of transmission and reception is normally completed, and the burden on the business staff member 4 is reduced. In order to do so, when an error occurs in the EDI system 1, the business person 4 is notified of the error.

FIG. 2 is a flow chart for explaining the operation of this error notification, and FIG. 2 shows the case of transmission processing.

First, in the ERP system 2, transmission data to be transmitted to the outside by being activated by a timer is created (step n101), and the transmission processing of the EDI system 1 is activated (step n102).

In the EDI system 1, the ERP system 2
Receives the transmission data from (step n103),
A status confirmation process described later is performed (step n10
4), intermediate format conversion processing such as code conversion is performed (step n105), status confirmation processing is performed (step n106), and further conversion processing to EDI data such as format conversion is performed (step n10).
7), status confirmation processing is performed (step n10).
8) Perform transmission processing to the outside (step n109)
The ERP system 2 is notified of the completion of transmission (step n110), and status confirmation processing is performed (step n1).
11).

As described above, the EDI system 1 performs the status confirmation process each time each step is completed.

FIG. 3 is a flow chart of this status confirmation processing.

In the status confirmation process, the EDI system 1 determines the state of each step when each step is completed.
For example, information such as the type of step, whether the step was performed normally, and the time when the step was performed,
The status is written in the status database 9 of the EDI system 1 (step n201), the status is transmitted to the ERP system 2 (step n202), and the activation processing for activating the status check of the ERP system 2 is performed (step n201). Step n
203).

The ERP system 2 analyzes the status file (step n204) and determines whether or not the status is an error (step n205). If there is an error, an error message is displayed. If not, a normal completion message is displayed. Respectively (steps n206 and n207), and obtains sender information such as who is the business person 4 who should send the message from the table prepared in advance (step n208), and sends it to the business person 4 Send an email (step n2)
09).

As a result, when an error occurs in the processing at each step, an e-mail is sent to the corresponding person in charge of business 4, so there is no need to constantly monitor it as in the conventional case.

FIG. 4 is a flow chart showing the operation in the reception process.

First, the reception process is started from the ERP system 2 to the EDI system 1 (step n30).
1). The EDI system 1 receives data from the outside (step n302), performs intermediate format conversion processing such as code conversion (step n303), and performs slip group conversion processing that collects slips by a certain number of units (step n304). , ERP data conversion processing such as format conversion is performed (step n305), transmission processing is performed to the ERP system 2 (step n306), and registration processing of the ERP system 2 is activated (step n307).

The ERP system 2 notifies the start (step n308), creates a start message (step n309), and sends a mail to the person in charge of business operation 4 (step n310). At this time, if there is an error in the reception process, the fact is notified. After that, registration processing is performed (step n311).

Therefore, in the reception process, an error is not notified at each step as in the case of the transmission process, but when there is an error after the reception process is completed, the fact is notified. Will be done.

This error notification is displayed, for example, as emergency information on the screen of the terminal of the person in charge of business 4, as shown in FIG. 5, or as a mail of data transmission failure, as shown in FIG. To be done.

Further, the EDI-ERP of this embodiment is
In the cooperative system, for example, when an error is notified, the ERP system 2 can inquire the transaction status, that is, the status of the transmission processing and the reception processing so that the transaction in which the error occurred can be easily grasped. Has been done.

FIG. 7 is a flow chart showing this transaction status inquiry processing.

First, the ERP system 2 requests the EDI system 1 to output a transaction file (step n401), and the EDI system 1 executes a transaction of the EDI system 1 under extraction conditions such as type and processing time. The transaction is extracted from the database (step n402), the extracted transaction is output to a file (step n403), and the ERP system 2 requests the EDI system 1 to transfer the transaction file (step n404). , The transaction file is transferred to the ERP system 2 (step n405), and the ERP system 2 displays the transaction status (step n406).

8 and 9 show examples of the display screen of the terminal of the person in charge of business operation 4 in the transaction status inquiry processing, and FIG. 8 shows the input screen of the extraction condition, and the start of the transaction to be extracted. Enter the time and end time and, if necessary, the type of transaction. The transactions extracted under the extraction conditions input in this way are displayed as shown in FIG.

Further, in the EDI-ERP cooperation system of this embodiment, the operation record of the EDI system 1 is
It is configured so that the P system 2 can make an inquiry.

FIG. 10 is a flow chart of this operation record inquiry process.

First, the ERP system 2 requests the EDI system 1 to transfer a log file (step n501), and the EDI system 1 transfers the log file to the ERP system 2 (step n502).
The P system 2 reads the log (step n50
3), the operation record list is displayed and the process ends (step n5).
04).

11 to 13 show examples of the display screen of the terminal of the business person 4 in the operation record inquiry process.
FIG. 11 shows an input screen for the extraction conditions of the log to be inquired. The start time and the end time of the log to be extracted are input, and if necessary, the type of the log and the like are also input. . The logs extracted under the extraction conditions input in this way are displayed as shown in FIG. 12, and on the display screen of FIG. 12, by placing the cursor on the log whose details you want to know and double-clicking it, The details are displayed as shown in FIG.

Further, the EDI-ERP of this embodiment is
In the linked system, the processing data of the EDI system 1 is
The ERP system 2 is configured to be inquired.

FIG. 14 is a flowchart of this processing data inquiry processing.

First, the ERP system 2 extracts the processing data related to the designated transaction (step n601), requests the EDI system 1 to transfer the processing data (step n602), and sends the EDI.
The system 1 transfers the corresponding process data (step n603), the ERP system 2 reads the process data (step n604), displays the process data, and ends the process (step n605).

Depending on the transaction, processing data such as input file name, output file name, error file name, etc. are associated as a transaction table, and by designating the transaction, the related processing data is extracted. be able to.

FIG. 15 and FIG. 16 show examples of the display screen of the terminal of the person in charge of business operation 4 in the process data inquiry process, and FIG. 15 shows the input screen of the process file to be inquired. The processing file input as
It is displayed as shown in FIG.

Further, in the EDI-ERP cooperation system of this embodiment, when the conversion master file 5 has an error cause, the portion causing the error is ER
After being corrected on the P system 2 side, it is transferred to the EDI system 1, the conversion master file 5 of the EDI system 1 is synchronized, and the transaction in which an error has occurred can be re-executed.

FIG. 17 is a flowchart of the correction process of the conversion master 5.

First, the conversion master file 5 in the ERP system 2 is modified (step n701), master data is transmitted to the EDI system 1 (step n702), and the master data file registration process is started (step n7).
03), in the EDI system 1, the conversion master file 5
And replace the process (step n70).
4).

FIG. 18 is a flow chart of re-execution processing from a transaction in which an error has occurred.

In ERP system 2, EDI system 1
The re-execution process of the transaction is started (step n
801), the EDI system 1 re-executes the transaction in which the error occurred (step n80).
2) In the ERP system 2, the transaction log is inquired and the process ends (step n803).

FIG. 19 shows the conversion master file 5 of the ERP system 2 and the conversion master file 5 of the EDI system 1.
FIG. 20 shows a transaction re-execution screen, and FIG. 20 shows a transaction re-execution screen.

As described above, since the conversion master file 5 can be corrected from the ERP system 2 side and the transaction in which the error has occurred can be re-executed, the recovery can be easily performed.

[0057]

As described above, according to the present invention, the ERP system is notified of an error that has occurred in at least one of the transmission processing and the reception processing of the EDI system, so that it is possible to determine whether or not the processing has ended normally. The person in charge of the system does not need to constantly monitor, and the burden on the person in charge of operating the system is reduced.

After the error is notified, the EDI
The status of the transmission process, the status of the reception process, the operation record, and the processing data in the system can be inquired from the ERP system side, and the conversion master file can be corrected from the ERP system side, so that the recovery can be performed easily and quickly.

[Brief description of drawings]

FIG. 1 is an EDI-ERP according to an embodiment of the present invention.
It is a schematic block diagram of a cooperation system.

FIG. 2 is a flowchart for explaining an error notification operation in transmission processing.

FIG. 3 is a flowchart of status confirmation processing of FIG.

FIG. 4 is a flowchart for explaining an error notification operation in a reception process.

FIG. 5 is a diagram showing an example of an error notification display screen.

FIG. 6 is a diagram showing an example of an error notification display screen.

FIG. 7 is a flowchart showing a transaction status inquiry process.

FIG. 8 is a diagram showing an example of a display screen of a transaction status inquiry process.

FIG. 9 is a diagram showing an example of a display screen of transaction status inquiry processing.

FIG. 10 is a flowchart of an operation record inquiry process.

FIG. 11 is a diagram showing an example of a display screen of an operation record inquiry process.

FIG. 12 is a diagram showing an example of a display screen of an operation record inquiry process.

FIG. 13 is a diagram showing an example of a display screen of an operation record inquiry process.

FIG. 14 is a flowchart of a process data inquiry process.

FIG. 15 is a diagram showing an example of a display screen of processing data inquiry processing.

FIG. 16 is a diagram showing an example of a display screen of processing data inquiry processing.

FIG. 17 is a flowchart of a conversion master correction process.

FIG. 18 is a flowchart of re-execution processing from a transaction in which an error has occurred.

FIG. 19 is a diagram showing an example of a display screen when the conversion master file 5 of the ERP system 2 and the conversion master file 5 of the EDI system 1 are synchronously executed.

FIG. 20 is a diagram showing an example of a display screen at the time of re-execution of a transaction.

[Explanation of symbols]

1 EDI system 2 ERP system 3 network 4 Business personnel 5 Conversion master file

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Hideki Ishida             Osaka Prefecture Osaka City Nishi Ward Shinmachi 1-5-8 Stock Association             Company Japan Research Institute (72) Inventor Yoshiaki Kaji             Osaka Prefecture Osaka City Nishi Ward Shinmachi 1-5-8 Stock Association             Company Japan Research Institute (72) Inventor Goji Sakurai             Osaka Prefecture Osaka City Nishi Ward Shinmachi 1-5-8 Stock Association             Company Japan Research Institute F-term (reference) 5B082 GA02                 5B085 AC11 AC17 BA06

Claims (8)

[Claims] 1. A cooperation system that cooperates with an EDI system for electronically exchanging information on business transactions between companies and an ERP system for integrated management of management resources of the company, wherein the EDI system is the ERP system. The transmission data from the outside is converted and transmitted to the outside based on the conversion master file, while the reception data from the outside is converted to the ERP system based on the conversion master file. The receiving process for transferring is performed, and the error generated in at least one of the transmitting process and the receiving process of the EDI system is detected by the ER.
EDI-ERP characterized by notifying P system
Cooperation system. 2. The status of the transmission process in the EDI system in response to a request from the ERP system,
2. The EDI-ER according to claim 1, wherein the reception processing status, operation record and processing data are transferred to the ERP system.
P cooperation system. 3. The EDI-ERP cooperation system according to claim 1, wherein the conversion master file modified by the ERP system is transferred to the EDI system. 4. The EDI-ERP cooperation system according to claim 3, wherein the EDI system re-executes a process in which an error has occurred, based on the modified conversion master file. 5. A method of linking an EDI system for electronically exchanging information on business transactions between companies and an ERP system for integrated management of management resources of a company, wherein the EDI system is provided from the ERP system. The transmission data is converted based on the conversion master file and transmitted to the outside, while the reception data from the outside is converted to the ERP system based on the conversion master file. Which is performed by the ER, the error occurring in at least one of the transmission processing and the reception processing of the EDI system is detected by the ER.
A cooperation method characterized by notifying the P system. 6. The status of the transmission process in the EDI system in response to a request from the ERP system,
The cooperation method according to claim 5, wherein the reception processing status, operation record, and processing data are transferred to the ERP system. 7. The cooperation method according to claim 5, wherein the conversion master file modified by the ERP system is transferred to the EDI system. 8. The cooperation method according to claim 7, wherein the EDI system re-executes the processing in which an error has occurred, based on the corrected conversion master file.