JP2003316968A - Matter management system and program in edi - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a document management work flow system suiting EDI work carrying out the management of documents by applying a concept of a work flow in EDI work carrying out exchange of data by using different business protocols with a plurality of customers with respect to one work matter. <P>SOLUTION: An analysis/assembly module, a formal definition, and a template for documentation are prepared for each business protocol, a message from a client is sorted, and it is sent to a corresponding business protocol analysis module. A plurality of work processes are defined with respect to one work matter like a work flow, and document data and identifiers with respect to the matter and work processes are managed in association with each other. It also has a GUI used by a client (an operator), and sent and received documents are aligned and displayed per each matter/work process. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a matter management system and a program for EDI business between companies.

[0002]

2. Description of the Related Art Conventional workflow systems are mainly classified into two types. One is a circulation type workflow system in which a document is handed over from one person to another person between business processes when the matter is divided into business process units. The other is a reference type workflow system in which documents used between business processes are collectively managed in a database or a predetermined directory for each business process and referred to by a person in charge as necessary. The former is known as a general workflow system. The latter is
The meaning is slightly different from the original definition of the workflow, but it is disclosed in, for example, Japanese Patent Laid-Open No. 11-73459.

On the other hand, conventional inter-company EDI (Electr
Looking at the onic Data Interchange system, the basic method is to use a one-to-one EDI for exchanging data with one customer using one business protocol for one item.

[0004]

In the conventional inter-enterprise EDI system, when conducting a transaction with a plurality of companies to process one item, a mechanism for managing the entire transaction flow as one item is provided. Absent. For example, it is assumed that there are two business processes A and B in one case and there is a business flow from A to B. Further, it is assumed that A uses a business protocol of X and B uses a business protocol of Y, and conducts transactions in EDI with different companies. At this time, in the conventional EDI system between companies, A and B are regarded as independent cases, not as one case in the entire flow of the business processes A to B. That is, a mechanism for performing EDI with a plurality of companies using a plurality of business protocols for one case is not currently provided.

On the other hand, a workflow is known as a technique for managing the flow of work. However, in the conventional workflow technology, when a business process is requested from one business process to the next business process, the data such as the document created by the requesting business process is directly passed to the next business process of the requestee. That is the basis. However,
In EDI between companies, a business partner company is involved during a business process and it is necessary to pass data such as a document in a different format for each business partner company. Therefore, the conventional workflow technique cannot be applied as it is. Note that Japanese Patent Laid-Open No. 11-73459 cited in the prior art discloses a method of connecting a business process (task) and data such as a document by using a GUI, but it takes too much time for human judgment and labor. , Not applicable in EDI.

[0006] Therefore, an object of the present invention is to allow the processing of one item in EDI between companies to be managed as one business flow by the concept of workflow. Another object is to enable management of data such as documents used in a business process in correspondence with the business process without human intervention. Still another object is to enable processing of a business protocol different for each business partner company without being aware of the operator of the case.

[0007]

In order to achieve the above object, in the present invention, the idea of a workflow is applied to an EDI business item, one item includes a plurality of business processes, and each business process is , Document data can be exchanged with multiple business partners using different business protocols. Therefore, an analysis means for preparing distribution definition information for distributing the received message for each business protocol, determining the business protocol of the received message, and analyzing the message of the business protocol based on the distribution definition information Sort into. The analysis means is provided for each business protocol, analyzes the distributed message, and acquires the item identifier and business process identifier of the message. The document data included in the received message is stored together with the acquired matter identifier and business process identifier. Further, a list of documents that can be created is displayed for each item and each business process, a document template corresponding to a specific document selected by the user is displayed, and the document data created on the document template is assembled according to the business protocol. To create a message that follows the format of the business protocol.

The message exchanged with the trading partner is usually an EDI message specific to the business protocol. Other basic processing such that means for analyzing this EDI message, means for assembling, format definition of business protocol, and template for document creation corresponding to business protocol can be put together and added / replaced for each business protocol. Keep loosely coupled with the department.
A function for allocating a message received from a trading partner to an analysis means of a corresponding business protocol is provided together with a distribution definition so that the corresponding analysis means is called when a message is received from the trading partner. This allows
It can support multiple business protocols. The analysis unit analyzes the document data in the message and acquires the identifier of the case and the business process to which the document data belongs. Finally, the document data is stored in the DB along with those information.
Throw in. A GUI may be provided on the client side of the worker who manages the case. This allows the client to perform processing such as receiving, creating, transmitting, and referring to the document. There is another function for generating a GUI screen, and the documents are arranged and displayed for each case and business process based on the document information acquired from the DB. As a result, it becomes possible to manage documents for each case and business process.

[0009]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram of a system which is an embodiment of the present invention. The document management workflow system (1) is a system that is constructed as a system of a trading company and electronically exchanges documents with a system of a trading company (2) or a company department (3). Communication with the customer system is performed using a leased line or the Internet (4). The communication protocol used for communication is not specified, but is usually HTTP (HyperTe
xt Transfer Protocol), FTP
(File Transfer Protocol),
SMTP (Simple Mail Transfer)
Protocol) or the like is used.

Generally, in EDI, a transmission / reception target is a message (EDI message), and document data (EDI data) is included in the message. Protocol (5) in the figure does not mean the communication protocol, but ED
E, which defines the message format and transmission rules of I for each industry
It is a DI-specific protocol (business protocol),
It is located above the communication protocol. Protocols A, B, and C in FIG. 1 indicate that different business protocols are used for each customer.

On the other hand, on the transaction source side, a GUI is used by a person in charge of business (client) to create, send, receive, and refer to documents
(Graphical User Interface)
Is required. In the example of FIG. 1, the GUI is WWW.
You are using the browser (6). WWW browser (6)
Request is sent to the WWW server (7) of the document management workflow system (1) via a leased line or the Internet (4).

The inside of the document management workflow system (1) is composed of a plurality of functions and definitions. Functions include a message transmission / reception function (8) for controlling transmission / reception of messages to / from a business partner, a message distribution function (9) for distributing received messages by business protocol, and a message management table (DB) (10) for managing messages ( 11) Or document management table (12)
A DB operation function (13) for performing operations such as data acquisition and insertion from the HTML page, an HTML page generation function (14) for generating a page to be displayed on the WWW browser (6), and an existing document mapped to the created document. A transcription function (15) that transcribes item values, a document data creation function (16) that has the function of collecting the data entered on the WWW browser (6) in the form of a record, and temporarily holding it internally, when receiving or referencing a document A document data extraction function (17) that sometimes extracts the corresponding document via the DB operation function (13) and manages existing document information, and additional information such as destination information when transmitting the document It has eight functions of a document data transmission function (18) in the form of a message that can be transmitted.

Also, as a group of replaceable parts (19) prepared for each business protocol, an analysis module (20) for analyzing a message, an assembly module (21) for assembling a message, a message format and a message for a business protocol It has a format definition (22) that defines the format of the data contained therein, and a document creation template (23) used when creating the document.

In addition, a matter definition (24) that defines matter information and business process information for each matter, and an identification definition (2) that defines rules for identifying matter IDs and business process IDs
5), four definitions: a distribution definition (26) that defines rules for the message distribution function (9) to distribute messages for each business protocol, and a transfer definition (27) that defines matching rules for items between documents. Have. These definitions can be defined using the definition creation tool. The relationship between the above functions and definitions and the flow of data will be described in order with reference to FIG. 1 and subsequent figures.

FIG. 2 shows an application example of the document management workflow system (1). It is assumed that an order will be received for an item (XXX) as a matter. In the case example shown in FIG. 2A, a plan / quotation (A1), an order (A2), a transportation arrangement (A
It includes three business processes: 3), delivery (A4), and settlement (A5). A plurality of documents are exchanged for each of these business processes. Further, it is assumed that there are a plurality of trading partners in this case. Specifically, as shown in FIG. 2B, in the business process of the order accepting company (A6) that has introduced this system, the processes of planning / estimating, ordering, and delivering are the ordering company (A6).
Documents are exchanged between 7) and a logistics company (A8) for the transportation arrangement process and a bank (A9) for the settlement process. That is, documents are exchanged with different trading partners in each business process. Usually, in such a case, data exchange is performed by different business protocols.

FIG. 3 is a case definition (24) and identification definition (2) used in the document management workflow system (1).
It is an example of 5). The case definition (24) defines what kind of business process the case as shown in FIG. 2 includes. Specifically, item definition (B1)
Then, together with the case name (B2) and the case ID (B3), each business process information belonging to the case is defined. As the business process information, the business process name (B4), the business process ID (B5), the business protocol name (B6) used in the business process, and the business protocol type number of the document used in the business process (data Type)
Define (B7).

In the document management workflow system (1), if the message sent from the transaction partner does not include additional data including the case ID and the business process ID, the case ID
And the business process ID from the item value of the document data included in the sent message. In this case, in the identification definition (B8), which item value for each data type (B10) of the business protocol (B9) is assigned to the case ID and business process ID (B11, B12) is defined. For example, [Rule] of the identification definition (B8)
1], the data type (Datakind) is “201,
For documents 202, 203, 204, 205 ",
The value of "Remarks column 1" is the matter ID, and the value of "Remarks column 2" is the business process ID. When the definition changes depending on the trading partner, the trading partner information is added to the identification definition.

On the contrary, when the message sent from the other party has additional data indicating the case ID and the business process ID, the identification definition is not used because the identification can be made from the additional data. However, when the additional data is used, if the storage positions of the case ID and the business document ID cannot be fixed in all transactions, information for specifying the storage position is required. Therefore, the identification definition (B8) requires an item of additional data storage location information as an identification method when using additional data. Arrangement with the trading partner regarding the use of the additional data or the document data item value is, of course, necessary in advance.

FIG. 4 shows a message management table (11) and a document management table (1) on the database (10).
It is an example of 2). As an item of the message management table (C1), a message ID numbered for each message
(C3), matter ID (C4), business process ID (C
5), a transmission / reception flag (C6) indicating a transmission / reception direction, and a data ID (C7) numbered for each document data. The data ID (C7) of the document data exists for the maximum number of data in one message.

On the other hand, the item of the document management table (C2) is the data ID of the message management table (C1).
Document ID (C8) linked with (C7), business protocol (C9), data type (C10), document name (C1)
1), the number of bytes of data (C12), and the actual data (C
13) exists. Besides this, although not shown in the example,
Items included in the table include document reception date / time, transmission date / time, document receiver / sender, and read status. If the received document data matches the already registered document data in terms of byte count and data content, the data ID for that document data is not newly assigned, and the document ID of the registered document data that matches is Given. In short, it has a structure that prevents a plurality of management of the same document data.

5 to 8 are GUs used by business personnel.
It is an example of a screen of I (WWW browser (6)).

FIG. 5 shows a screen for displaying a received document. The features of this screen will be described. First, the case can be switched by the case tab (D1). In FIG.
“Matter 1” is selected. With respect to “Matter 1”, a matter folder (D2) is displayed at the highest level, and a business process folder (D3) is displayed in sequence from the top to the matter folder (D2) to represent the flow of business processes. . In each business process folder, an INBOX folder (D5) in which the received document (D4) is stored,
OUTBOX that stores the sent document (sent document)
Folder (D6), related document list folder (D7) that stores all documents related to the business process defined in the case definition, and created document folder (D8) that stores created documents (unsent documents) ) Exists. In the figure, the INBOX folder (D5) is in the selected state, and a list of received documents (D4) stored in the folder (D5) is displayed. Also, although not shown in the figure,
It also has a function to identify the business process currently involved by the color and icon.

The document in the related document list folder (D7) is not a document completed by setting a value, but represents information (document template, etc.) of a document from which a client creates a document. . In the related document list folder (D7), all documents (original data) that are supposed to be used in the business process are stored in advance. The client (this original data)
The document created from is stored in the created document folder (D8).

FIG. 6 shows an example of a document creation screen. When the related document list folder (D7) shown in FIG. 5 is selected, the document list stored in the folder (D7) is displayed, and when any one document is clicked, the corresponding document is selected. The template (23) is called and the screen of FIG. 6 is displayed in another window. This document indicates that the document is a data type 0304 (shipment information) (E2) of the business protocol AAAA (E1). On this screen, the person in charge of business operations can select each item (E3)
Enter the value (E4) for. When "Complete" (E5) is clicked at the stage where the creation of the document is completed, the created document is put into the created document folder (D8) of the corresponding business process.

FIG. 7 is an example of a screen of a created document. By selecting the created document folder (D8),
Created document (F1) existing in the folder (D8)
Is displayed. When any one document is selected from the list and "Confirm" (F2) is clicked, a screen for content confirmation and transmission is displayed. "Reset" (F3)
Click to reset the selection.

FIG. 8 is an example of a screen for confirming and transmitting contents. When "Confirm" (F2) is clicked on the created document screen described above, this screen is displayed in another window. After confirming the content, the person in charge of business inputs the destination information in the destination (G1) and clicks "Send" (G2) to transmit the document. If you have more than one document to check, click.
By clicking (G3), the contents of the next document can be confirmed. If additional information other than the destination is required at the time of transmission, it is necessary to input it before the transmission.

FIG. 9 is a diagram showing a message distribution function for each business protocol. Business protocol A
Message (H1) is the message distribution function (H
According to 2), it is sent to the analysis module (H3) for business protocol A and analyzed. Business protocol A
The format definition used for analysis by the analysis module (H3) for business is the format definition for business protocol A (H
4). Similarly, business protocol B (H5),
The message for C (H6) is also for B (H7) and C (H) by the message distribution function (H2).
It is distributed to the analysis module of 8) and analyzed respectively. The document management workflow system (1) has a function (H9) dependent on a business protocol separately from the core basic processing unit (H10). This makes it possible to flexibly support new business protocols. When a new protocol is added, it is not necessary to modify the basic processing unit (H10). Analysis modules, assembly modules, format definitions, and document creation templates (20-23 in Figure 1) for the new protocol
Is newly prepared, and a rule for allocating to a new protocol is additionally defined in the allocation definition (H11), and the system has expandability.

The flow of operation of the system shown in FIG. 1 will be described with reference to FIGS. In addition, in FIGS. 10 to 14, operations surrounded by dotted lines indicate operations performed by a person in charge of business (client). Others are operations of the document management workflow system (1) in FIG.

FIG. 10 is a diagram showing the flow of operations of the document management workflow system (1) from the reception of a message from a business partner to the storage of document data in the DB (10). First, message sending / receiving function (8)
The message receiving function in the box receives the message sent. In this embodiment, the communication protocol is not specified, but if the communication protocol is SMTP,
The message is sent to the mail server in a form covered with mail-specific data such as a mail header. In this case, the message receiving function (8) performs a process of removing the data unique to the mail after receiving the message from the mail server. Thus, the message receiving function (8) removes unnecessary data such as destination information depending on the transmission protocol, and passes the remaining message to the message distribution function (9) (step I1).

The message distribution function (9) passes the sent message to the corresponding analysis module (20) based on the distribution definition (26) (step I2).
The distribution definition (26) is, for example, a rule such as "if the value indicating the business protocol AAA is entered in the first 10 bytes, the analysis module of the business protocol AAA is selected." This is a file to be defined in a format in which (9) can be understood.

Next, the called analysis module (20) analyzes the message and the data contained in the message (step I3). At this time, the analysis module (20) first checks whether or not the message has additional data indicating the case ID and the business process ID (step I4). As described with reference to FIG. 3, when the storage position of the additional data differs for each message, the process of acquiring the storage position information from the identification definition (25) is required.

If there is additional data, the case ID and business process ID are acquired from the additional data (step I5). Conversely, if there is no additional data, first, the document data is extracted from the business protocol message format according to the business protocol format definition (22). Then, according to the identification definition (25), the matter ID and the business process ID are acquired from the corresponding item value (step I
6). After steps I5 and I6, the analysis module (2
0) passes the information registered in the DB (10) to the DB operation function (13), and the DB operation function (13) inputs the document data into the message management table (11) and the document management table (12) ( Step I7).

In FIG. 11, the INBOX (D) is actually displayed after the business person (client) updates the browser (6).
FIG. 5 is a diagram showing a flow until a document is received in 5).
First, the client updates the browser (6) with the INBOX of a specific business process opened (for example, the state of FIG. 5) (step J1). Updating the browser (6) is updating the display screen (FIG. 5) of the browser (6) to the latest data. When the browser (6) is updated, the HTML page generation function (14) automatically calls the document data extraction function (17) (step J
2).

The document data extraction function (17) internally has INBOX and OUTBOX for all cases on the screen.
Holds an information list of documents stored in the document management table, and stores the held document list and the document IDs actually stored in the document management table (12) via the DB operation function (13). Compare. As a result of the comparison, only the record of the new document is acquired from the message management table (11) and the document management table (12) via the DB operation function (13) (step J3). As a result, the document information list internally held by the document data extraction function (17) is updated.

The HTML page generation function (14) inquires of the open INBOX whether or not there is a new document to the document data extraction function (17), and if there is, the information of the document is stored in the document management table. Received from (12), the information of the document is displayed on the corresponding INBOX (step J4). On the contrary, if there is no new document, the display remains. The business process of the latest received document in the case is the business process I of the received document.
Since it can be identified by D, it can be displayed in different colors and icons as the business process currently involved.

In FIG. 12, the person in charge of business operation (client) clicks a specific document stored in the INBOX or OUTBOX on the browser (6) until the document is displayed on the browser (6). It is a figure showing the flow of. Client is INBOX or OUTB
When a specific document included in the OX is clicked (step K1), the HTML page generation function (14) passes the document ID of the document to the document data extraction function (17) (step K2). The document data extraction function (17) acquires the document data from the document management table (12) via the DB operation function (13) using the passed document ID as a key (step K3). The HTML page generation function (14) converts the acquired document data into a format that can be displayed as a page,
It is displayed in another window (step K4).

In FIG. 13, the person in charge of business (client) clicks a specific document in the related document list folder (D7) on the browser (6) to create a document, and the created document is the created document. It is the figure which showed the flow until it throws into a folder. When the specific document in the related document folder (D7) under the business process in which the client is currently involved is clicked (step L1), the HTML page generation function (14) determines the business protocol belonging to the document and its data type as document data. It is passed to the creating function (16) (step L2). Document data creation function (16)
Selects the corresponding document creation template (23) using the passed business protocol and data type as keys (step L3).

The HTML page generation function (14) displays the selected document creation template in another window (step L4). At the time of display, the HTML page generation function (14) checks whether or not the transcription definition (27) has been previously defined for the document (step L).
5). The transcription definition (27) is a file that defines mapping of items between documents. For example, when the item (product name) of the quotation request document and the item (item name) of the quotation reply document are mapped, when the quotation reply document is created, the quotation request document (already exists in the created document folder). )
The estimate reply document is displayed in a state in which the values of the items (item names) contained therein are embedded as default values (step L5).

When the transcription definition (27) is defined,
The transcription function (15) acquires, through the document data extraction function (17), an existing document that is mapped to the document that is being created, based on the transcription definition (27), and outputs the value for the mapped item. It is embedded as a default value and the corresponding document creation template is displayed (step L6). On the contrary, when the transcription definition (27) is not defined, all items are displayed with no value (step L7).

The client inputs a value to each item on the display screen and clicks "Finish" when the document creation is completed (step L8). FIG. 6 shows a state in which a value is input for each item. The created document is temporarily held by the document data creation function (16) and put into the corresponding created document folder (D8) (step L9).

FIG. 14 is a diagram showing the flow from when the business person (client) confirms the content of the document created on the browser (6) and sends it until it is actually sent to the trading partner. is there. First, the client designates the created document from the created document folder of the corresponding business process on the screen as shown in FIG. 7, and clicks the “confirm” button (step M1). The content confirmation and transmission screen as shown is displayed. After confirming the content on this screen, the client specifies the destination of the trading partner and clicks the "Send" button (step M
2), the HTML page generation function (14) is the case ID,
Business process ID, business protocol, data type,
The document data and the destination information are collectively passed to the document data transmission function (18) (step M3).

The document data transmission function (18) uses the business protocol as a key, and the corresponding assembly module (21).
Is specified, and all data other than the destination information passed from the HTML page generation function (14) is passed to the assembly module (21) (step M4). Assembly module (2
1) assembles the data according to the corresponding format definition (22), and finally creates the message format of the corresponding business protocol. At this time, the DB operation function (13) registers the data and message information in the message management table (11) and the document management table (12) (step M5). The created message is added with the destination information by the document data transmission function (18) and is passed to the message transmission function (8) (step M6). In reality, the information added depends on the transmission protocol. Finally, the message sending function (8) sends the message to the trading partner (step M7).

It is assumed that the transmitted document data is moved from the created document folder to the OUTBOX folder.

[0045]

As described above, according to the present invention,
With respect to one EDI business case, it is possible to exchange documents for each business process using a business protocol different from that of a plurality of business partners. Further, the business documents exchanged in the flow of the case are managed for each case and the business process, and the client using the GUI can instantly confirm his / her status in each case. Further, even when the number of business protocols used increases, the system can be easily expanded by adding only the processing depending on the business protocol to be added.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a system according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating an example of a case and a relationship with a trading partner in the present embodiment.

FIG. 3 is a diagram illustrating an example of a case definition and an example of an identification definition.

FIG. 4 is a diagram showing an example of a message management table and a document management table.

FIG. 5 is a diagram showing an example of a document reception screen displayed on a client.

FIG. 6 is a diagram showing an example of a document creation screen displayed on the client.

FIG. 7 is a diagram showing an example of a document content confirmation and transmission screen displayed on the client.

FIG. 8 is a diagram showing an example of a document reception screen displayed on the client.

FIG. 9 is a diagram showing a message distribution function.

FIG. 10 is a diagram showing a flow of message reception processing.

FIG. 11 is a diagram showing a flow of document reception processing.

FIG. 12 is a diagram showing a flow of document reference processing.

FIG. 13 is a diagram showing a flow of document creation processing.

FIG. 14 is a diagram showing a flow of document transmission processing.

[Explanation of symbols]

1 ... Document management workflow system, 6 ... WWW browser, 7 ... WWW server, 9 ... Message transmission / reception function, 1
0 ... Database, 11 ... Message management table, 1
2 ... Document management table, 13 ... DB operation function, 14 ... H
TML page generation function, 15 ... transcription function, 16 ... document data transmission function, 17 ... document data extraction function, 18 ... document data transmission function, 20 ... analysis module, 21 ... assembly module, 22 ... format definition, 23 ... document creation Template, 24 ... Matter definition, 25 ... Identification definition, 26 ... Sorting definition, 27 ... Posting definition, C1 ... Message management table example, C2 ... Document management table example, C3 ... Message I
D, C4 ... matter ID, C5 ... business process ID, C6 ...
Transmission / reception flag, C7 ... Data ID, C8 ... Document ID, C
9 ... Business protocol, C10 ... Data type, C11
... Number of bytes, C12 ... Actual data, H2 ... Message distribution function, H10 ... Basic processing unit, H11 ... Distribution definition.

Continued front page    (72) Inventor Jun Sugihara             5030 Totsuka Town, Totsuka Ward, Yokohama City, Kanagawa Prefecture             Ceremony company Hitachi Ltd. software division (72) Inventor Toshiaki Oda             5030 Totsuka Town, Totsuka Ward, Yokohama City, Kanagawa Prefecture             Ceremony company Hitachi Ltd. software division F-term (reference) 5B085 BA06 BG02 CE06

Claims (6)

[Claims] 1. A matter management system applied to EDI (Electronic Data Interchange) business for exchanging documents with business partners, and means for storing distribution definition information for distributing received messages according to business protocols. And a distribution means for determining the business protocol of the received message and distributing to the analysis means for analyzing the message of the business protocol based on the distribution definition information, and provided for each business protocol, and distributed by the distribution means. Analyzing means for analyzing the message and acquiring the matter identifier and business process identifier of the message; and means for storing the document data included in the received message together with the matter identifier and business process identifier obtained by the analyzing means. A case management system characterized by having. 2. The case management system according to claim 1, wherein the document data is displayed as a list for each case and for each business process in one case, and the list display is provided. A case management system further comprising means for displaying document data selected from among them. 3. The item management system according to claim 1, wherein a means for displaying a list of documents that can be created for each item and each business process, and a specific document selected by the user from the list of documents that can be created A means for displaying a corresponding document template, a means for creating document data by setting a value inputted by the user in the document template, and a destination for the created document data when the transmission is instructed The passed document data is referred to by referring to the means for passing the created document data to the assembling means according to the business protocol to which the data belongs and the format definition information provided for each business protocol and defining the format of the business protocol. And an assembling means for creating a message according to the format of the business protocol to which the document data belongs from Case management system, characterized in that the means for transmitting messages to the destination, further comprising. 4. The item management system according to claim 1, wherein the analyzing means, the assembling means, the format definition information, and the document template are prepared for each business protocol, and these constituent elements depending on the business protocol are subjected to basic processing. A case management system characterized by preventing loosening of the basic processing part of the system by addition, change and deletion of business protocol processing by loosely coupling with parts. 5. A matter management program applied to EDI (Electronic Data Interchange) business for exchanging documents with suppliers, referring to distribution definition information for distributing received messages by business protocol. , Determining the business protocol of the received message and assigning it to an analysis processing step for analyzing the message of the business protocol, and a message provided for each business protocol and analyzing the message assigned by the assigning step, and analyzing the message And a step of storing the document data included in the received message together with the case identifier and business process identifier acquired by the analysis processing step. Case management program characterized by comprising. 6. The item management program according to claim 5, wherein a step of displaying a list of documents that can be created for each item and each business process, and a specific document selected by a user from the list of documents that can be created A step of displaying a corresponding document template; a step of creating document data by setting a value input by the user in the document template; and a step of creating the document data when the destination is designated and transmission is instructed. The step of passing the created document data to the assembly step according to the business protocol to which the data belongs, and the passed document data by referring to the format definition information provided for each business protocol and defining the format of the business protocol Create a message according to the format of the business protocol to which the document data belongs from And falling step, the case management program characterized by the steps of transmitting to the destination of the message created, further comprising.