JPH1027119A - Management method and management method of received data in EDI system - Google Patents

Abstract

(57) [Summary] [Problem] Each sender's unique data format and CII
Provided is a method of managing received data in an EDI system for coexisting and using data in a standard format. An EDI server analyzes a file name of a collection file 10 received and stored by a data receiving unit 12 to determine a format of data to be sent.
If it conforms to the I standard format, it sorts the collection file 10 into sections based on the specified sorting information, and if it does not conform to the CII standard format,
The data is stored as it is, and then the distribution file 2
4 and a security check unit 20 for checking the validity of the data transmission / reception destination.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an industrial information technology promotion center (CII: Center for the Info).
EDI (Elect) compliant with the CII standard format proposed by the
(Ric Data Interchange) system relates to the coexistence of data conforming to the CII standard format and non-compliant data.

[0002]

2. Description of the Related Art Each company handles various types of data such as ordering, shipping, invoices, and other data related to financing and material procurement. Created and stored. When transmitting the aforementioned data, such as an order and an invoice, created by each company to another company, the data is transmitted to the other company via a network according to a communication protocol such as the Zengin protocol or FTP.

[0003] FIG. 8 is a network configuration diagram in the case where each company is connected by a general wide area network. In a company, terminal devices and the like of each department are generally connected by a LAN. Orders created in the company by a server in the company connected to the LAN and also to a wide area network.
Data such as invoices is collected for each transmission destination and transmitted to a designated bank or business partner, and data from the bank or business partner is collectively received. Since data received at one time may include data for a plurality of departments, the server sorts and stores the received data for each department as necessary. Then, each section receives the sorted files.

A server has a variety of applications to realize various processing functions. When data is received via a wide area network, the server activates an application specified by the type or source of the data. By that
Understand the contents of the received data created in a format unique to other companies, sort and store the received data for each prescribed department such as the material department and accounting department in the company or for each cooperating company, and store it in each department if necessary. Sending. The source of the received data is identified by arranging a file name for storing the received data between companies in advance. In other words, in communication protocols such as FTP,
Before actual data is actually transmitted, a file name for storing transmission data is specified in advance by a transmission source, and is transmitted to a transmission destination. In a communication protocol such as the Zengin protocol, a transmission destination, that is, a receiver side determines a file name for storing data to be transmitted, and transmits data after that. Therefore, the server
Identify the data source by referring to the file name sent from the source or predetermined,
A predetermined application is started, and data received under a specified file name is stored.

[0005] As described above, in a situation where communication is performed between companies using a unique data format, there are many items to be decided for each company, and specifications and management become complicated. Therefore, the CII has established a standard data exchange rule (CII syntax rule) so that it can be used by many companies, and each company follows the standard format that conforms to this rule, thereby allowing data to be exchanged between companies. Communication, storage, and the like can be easily managed.

FIG. 9 is a diagram showing an outline of a data structure of a reception file (which is called a collection file) according to the CII standard format. A file sent in one data communication can include a plurality of message groups. Each message group includes a message group header described later, a transaction record corresponding to actual data, and a trailer having a length of 251 bytes indicating the end of the message group.

FIG. 10 shows a format of a message group header in the CII standard format. The message group header is composed of 251 bytes. The file sender specifies a predetermined code for identifying the company that is the data sender in the “sender code” field included in the header, and a predetermined code for specifying the data reception destination in the “recipient code” field. By making these settings, the server can easily identify the source and destination of data without having to know the collection file name in advance.

The receiver code is composed of 12 bytes, of which the upper 6 bytes are a code (company ID) for specifying a company, and the lower 6 bytes are arbitrarily designated by the company name. Here are the code parts that can be A code (department ID) for identifying each department in the company is normally assigned to the lower six bytes. If the file sender specifies the department code in the lower 6 bytes and transmits the data, the data addressed to a plurality of departments can be transmitted collectively by one file transfer. On the other hand, the server that has received the file can divide the transmitted file by referring to the “recipient code” for each message group, so that the file can be sorted for each predetermined department and stored. Thus, by transmitting and receiving data conforming to the CII standard format, data can be easily received and stored. Further, by designating an arbitrary code in the "information division" field, even if the data is addressed to the same department, it is possible to perform more detailed classification of data such as the type of slip. Further, as is apparent from FIGS. 9 and 10, data addressed to a plurality of departments can be transferred by one file transfer.

[0009]

However, at present, it can not be said that there are still many companies that conduct business using only the CII standard format, and how to store data in the CII standard format is not yet known. Determining the management scheme is an issue for the future.

In the conventional system configuration, CII
When attempting to perform data communication that conforms to the standard format, the data sent in each company's own data format does not conform to the format of the message group header described above, so it is easy to identify the sender and receiver. Can not. On the other hand, if data communication is performed using the data format unique to each company, C
Data communication conforming to the II standard format cannot be performed.

[0011] That is, in the transitional stage of transition to data communication conforming to the CII standard format, EDI
When trying to make the data format unique to each company and the CII standard format coexist in the system,
It has been difficult to determine the data format of the received data and store it in a format that can handle each.

The present invention has been made to solve the above problems, and an object of the present invention is to provide an EDI system for coexisting and using data in a data format unique to each sender and a CII standard format. And a management method of the received data in the above.

[0013]

SUMMARY OF THE INVENTION In order to achieve the above object, the present invention provides an EDI system which receives a file name for storing data from a data source in advance and stores received data with the file name. In the received data management method described in the above, the data received from the data transmission source is received and stored in the collection file, and the data is transmitted based on the collection file name specified by the data transmission source. Data format discriminating means for discriminating the data format of the incoming data, a sorting information database containing sorting information for sorting the collection file in units of division, and a case where the transmitted data conforms to the CII standard format. The received file is sorted and classified based on the sorting information specified in the received data. And, if not compliant with the CII standard format, and having a data management means for storing the data as it is.

Further, the data format discriminating means recognizes that the transmission source specifying information and the transmission destination specifying information are specified at predetermined positions in the character string constituting the file name, so that the data format determining unit converts the character string into a CII standard format. It is characterized in that it is determined that the data is not compliant.

[0015] The data management means sorts the collection file based on a data transmission destination and a type of data.

With the above configuration, both data can be handled whether or not the transmitted data conforms to the CII standard format.

Also, a subscriber information database including an identification code for identifying a data transmission / reception destination and storing information on a communication party performing data communication, and a transmission source or transmission destination capable of data communication or a combination thereof are stored as security information. And a security monitoring means for validating data transmitted only when a transmission / reception destination capable of data communication is designated. With this configuration, data accumulation processing can be performed only when a valid combination of transmission and reception destinations is specified.

Further, in the method for managing received data in the EDI system according to the present invention, a file name for storing data is received in advance from a data transmission source, and the received data is managed in the EDI system for storing received data with the file name. A data format determining step for determining whether or not the transmitted data conforms to the CII standard format from a file name transmitted from the data source;
If the data conforms to the standard format, the data is sorted and stored in a specified divisional unit. If the data does not conform to the CII standard format, the data is stored as it is. The received data is sorted according to (1). By following this procedure, the transmitted data will be CII
Both can be handled with or without conforming to the standard format.

[0019]

Preferred embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing a configuration example of an EDI server conforming to the CII standard format. ED
The overall configuration of the EDI system including the I server is the same as that in FIG. 8, and this EDI server corresponds to the server in FIG. The EDI server according to the present embodiment receives data transmitted from a data transmission source and stores the data in a collection file 10 as a data receiving unit 1 as a data receiving unit.
2, a data format discriminator 14 as a data format discriminating means for discriminating the data format of the data transmitted based on the collection file name specified by the data transmission source, and the transmitted data being in the CII standard format. If the received data is compliant, the received file 10 is sorted based on the sorting information specified in the received data, stored in the sorting data file 16, and stored in the sorting data file 16.
If the data does not conform to the I standard format, the data storage management unit 18 as data management means for storing the data as it is, and the transmission / reception capable of performing data communication in order to realize the security check function provided in the present embodiment. A security check unit 20 as a security monitoring unit for validating data transmitted only when a destination is designated; and a data conversion unit for converting data conforming to the CII standard format into a data format unique to the company. And a data conversion unit 22. Further, the data storage management unit 18 creates a distribution file 24 for distribution to each section from the sorting data file 16.

Further, as a database in the present embodiment, the collection file 10 is sorted in units of sections, and a sorting information database 26 including sorting information for generating the sorting data file 16; A subscriber information database 28 containing information about a communication party performing data communication, including a code, a security information database 30 storing, as security information, a source or a destination or a combination thereof capable of performing data communication; File management information database 32 for storing information for managing the sorting data file, assortment data management information database 34 for storing information for managing the sorting data file 16, and distribution file 2.
4, and a distribution file management information database 36 that stores information for managing the management file 4.

FIG. 2 is a diagram showing an example of setting assortment information registered in the assortment information database 26. FIG. 2 (a)
Is a table in which a department ID for identifying a department in a company is associated with the department name, and sorts the collection file 10 into sections based on this table.
FIG. 2B is a table in which codes (information division IDs) that can be specified in the “information division” field of the message group header and the information division names thereof are associated with each other. Is specified, the collection file 10 is further finely divided into division units based on this table. In the case where data is classified for each type of slip as in the present embodiment, the slip name becomes the information category name. FIG.
(C) is a table in which the types of slips that can be received for each section are assigned, and the section ID and the information section ID
Specify with.

FIG. 3 is a diagram showing a setting example of the subscriber information database 28. Subscriber information database 28
Stores information about a subscriber, that is, a communicator, such as a company ID, a company name, a subscriber code, an address, and a telephone number for each subscriber of the EDI system. The company ID is a 6-byte length code specified in the sender code and the receiver code of the message group header conforming to the CII standard format. The subscriber code is a 2-byte length identification code of each company specified in the collection file name. Details of the specification of the file name will be described later. If the subscriber code can be 6 bytes long, the company ID can be used as the subscriber code.

FIG. 4 shows the security information database 3.
It is a figure showing an example of setting of 0. The security information database 30 stores a sender company ID that specifies a company that can be a transmission source and a company ID that specifies a department that can receive data from the transmission source company in association with each other. For example, data from Bank B can only be received by the accounting department. Note that the other management information databases 32, 34, 36
I will explain later.

A characteristic feature of the present embodiment is that the above-described configuration can simultaneously handle both cases where transmitted data conforms to the CII standard format and cases where data does not conform to the CII standard format. .

Next, in this embodiment, a collective data accumulation process for sorting and storing data included in a file when the file is received via the network based on FTP using the flowchart shown in FIG. Will be explained.

The data receiving unit 12 receives data from a data transmission source in accordance with a predetermined communication protocol (step 101), and stores the data under a file name of a specified concentrating file 10 described later (step 102). In the received data, a file name is specified before the actual data as described above. FIG. 6 is a diagram showing an example of a method of designating a collection file name used in the present embodiment. In the present embodiment, the source company is C
To transmit data in a company-specific data format that does not conform to the II standard format, it is necessary to set a file name in accordance with the rules shown in FIG. In the present embodiment, the file name is formed by a common code, a source subscriber code, a destination subscriber code, and a branch number. The common code is a code for setting to indicate that the file is handled by the present system, but is not always necessary. The transmission source subscriber code is transmission source identification information composed of an identification code (subscriber code) for identifying a data transmission source. The transmission destination subscriber code is transmission destination specifying information composed of a subscriber code for identifying a transmission destination of data. The subscriber code is registered in the subscriber information database 28 described above. The branch number is a number arbitrarily set by the sender, and can be used, for example, for version management of a transmission file. Since the file name length is determined by the operating system (OS) handling the file, the number of digits of the branch number depends on the OS.
Note that each code length can also be set to an appropriate length by the OS of the EDI server.

When the data receiving unit 12 receives the data,
By analyzing the received file name (step 103), the data format determination unit 14 can determine the format of the real data to be sent later.
That is, if the file name conforms to the rules described above, it is determined that the data format is a company-specific data format that does not conform to the CII standard format (step 10).
4).

When it is determined that the data format does not conform to the CII standard format, the data storage management unit 18 designates the actual data to be received from now on in the format in which the data was transferred after the security check described below. The file name is stored. On the other hand, CI
In the case of the data format conforming to the I standard format, the received data is sorted by a method described later after the security check.

In this embodiment, security check can be performed by the security check unit 20 as an additional function. The security check in the present embodiment is performed based on information registered in the subscriber information database 28 and the security information database 30.

First, the processing in step 105 in which the received data does not conform to the CII standard format will be described. As described above, the file name sent in advance includes the source subscriber code and the destination subscriber code. Since it is designated, it is checked whether the subscriber code included in this file name is registered in the subscriber information database 28. If not registered, the received data is invalidated and discarded.

As is apparent from the above processing, since the source subscriber code and the destination subscriber code are specified at predetermined positions of the file name, the transmission source identification information and the transmission destination It is determined that the data sent other than the use as the specific information does not conform to the CII standard format. That is, it is possible to determine whether or not the data conforms to the CII standard format by using a common code or the like.
This is a design matter.

Also, in the above description, the data format discriminating unit 14 determines the data format by analyzing the received file name. However, the received file name and the file conform to the CII standard format. It is also possible to prepare in advance a file management information database paired with data format information indicating whether or not the data format of the actual data to be received is determined with reference to this database.

On the other hand, the security check in step 106 where the received data conforms to the CII standard format is performed based on the sender code, the receiver code, and the information classification of the message group header conforming to the CII standard format. Will be First, the validity of the code designation of the source and destination of the transmitted data is checked. This checks whether the sender ID specified in the message group header and the company ID included in the receiver code are registered in the subscriber information database 28, and checks the receiver code specified in the message group header. Figure 2 contains the department ID
It is checked whether the information is registered in the table of the sorting information database 26 shown in FIG. If the information section is specified, the validity is checked based on the table shown in FIG.

In addition to the validity check of the designated code, a combination check of the designated source and destination is performed. This is the security information database 3
Based on the security information registered in “0”, it is checked whether the combination of the transmission source and the transmission destination is valid. As a result, it is possible to prevent data communication from a certain company to an unrelated department and erroneous transmission to another department, and only a department that can use received data can properly receive the data. If the information division is designated, the combination of the department ID and the information division ID is checked based on the table of the sorting information database 26 shown in FIG.

In the case of data conforming to the CII standard format, the data is subsequently sorted (step 107). The data storage management unit 18 sorts the collection file 10 by department ID or by department ID and information category ID based on the department ID constituting the receiver code of the received data and the information category ID if specified. I do. The transmitted data (collection file)
As described above, a plurality of message groups can be included as shown in FIG. That is, the collection file 10
It will be sorted for each message group. Data (sorting data) obtained by dividing the collection file 10 is stored as a sorting data file 16.

FIG. 7 shows the transition of the file for creating the distribution file 24 from the received file 16 and the received file 10, the sorting data file 1 received in this embodiment.
6 is a diagram showing an example of contents of management information databases 32, 34, and 36 of the distribution file 24 and the distribution file 24, respectively. In the sorting process in step 107, for each department ID specified in the message group header,
If D is specified, the collection file 10 is divided for each department ID and for each information division ID, and a sorting data file 16 is created. In the sorting data management information database 34,
An ID is assigned to each sorting data file 16 and managed. As described above, more detailed sorting can be performed by using the information section ID.

The data storage management unit 18 does not perform the above-described sorting process when the transmitted data does not conform to the CII standard format.

When the data sorting is completed, the data converter 22 converts the data in the CII standard format into a data format for handling in the company (step 108). In the case of a data format conforming to the CII standard format, data conversion is performed by an application that performs the same conversion process regardless of the transmission source.

In the case of data in a data format that does not conform to the CII standard format, the transmission source can be specified by the transmission source subscriber code included in the file name. A data conversion application is activated to perform data conversion (step 109). This process may be the same as the conventional one.

Note that the data conversion process need not always be performed here. This is the case, for example, when there is a department that wants to perform data conversion with its own application after receiving the distribution file 24, or when data conversion is not to be performed depending on the transmission source, such as the sorting information database 26 or the subscriber information. By adding the flag information to the database 28, the execution of the data conversion process can be controlled.

Next, the sorting data file 16 or
If the data does not conform to the CII standard format, the distribution file 24 is created based on the unsorted file (step 110). By the way, the distribution file 24 is a file in which the sorting data files 16 sorted based on the received files are grouped into designated department units to be distributed. Therefore, as shown in FIG. 7, assortment data files a1 and a2 destined for the section a that has sorted the collection file with the ID of 100, and assortment data files a3 that have been sorted for the collection file with the ID of 200 and addressed to the section a.
Is formed as one distribution file. To be more precise, the assortment data file a3 is appended to the distribution file previously created with the assortment data files a1 and a2. If the data does not conform to the CII standard format, it is created as a separate distribution file 24 and is not appended.

If the information division ID is set in the assortment data management information database 34, the distribution file 24 is created collectively for each information division. For example,
Of the data addressed to the accounting department, only the withdrawal slip can be summarized separately from other slips addressed to the accounting department. That is, different distribution files are created even for the same department.

The distribution file 24 created as described above
An ID is assigned to each of them, and is managed by the distribution file management information database 36. When the distribution file 24 is created, each section appropriately stores the distribution file 24 addressed to its own section.
Get from DI server. Distribution file 2 for own department
No. 4 can be identified by determining a file name in advance. Of course, the EDI server may transmit the information to each department.

In the case of data that does not conform to the CII standard format, the collection file 10 has not been sorted yet, so that the file is sorted using a previously prepared application and the distribution file 24 is Create. Which application is to be activated can be specified by the collection file name as described in the determination processing of the data format of the received data in step 103. Here, the data conversion processing in step 109 may be performed.

As described above, according to the present embodiment, C
A data format discriminating unit 1 that provides a data management method in the II standard format and recognizes transmission source specifying information and transmission destination specifying information specified in a file name.
4 is provided so that different processing can be performed depending on whether or not the received data conforms to the CII standard format, so that both the case where the received data conforms to the CII standard format and the case where the received data does not conform to the CII standard format can be handled simultaneously. . The processing when the data does not conform to the CII standard format is basically the same as the conventional one.

The present embodiment is characterized in that a data format discriminating section 14 is provided so that it is possible to discriminate whether received data conforms to the CII standard format, and to specify a transmission source and a transmission destination by a file name. And one of them. Therefore, the specification regarding the file name is a design matter. For example, the code order and code length are O
S may be determined, or the data format may be identified by the common code as described above.

Further, it is merely a matter of design to provide a function of appropriately recording a failure history when any inconvenience occurs in the above-described processing and providing a management means for various databases. This is not the gist of the present embodiment.

Further, the security check processing, the sorting processing, and the data conversion processing after the determination of the data format can be executed even if they are not in the order described above.

In the above description, the collection of data from other devices has been described.
By distributing data to other servers, the server can set file names, perform reverse conversion of the proprietary data format to the CII standard format, and generate data conforming to the CII standard format. it can.

[0051]

According to the present invention, different processing can be performed according to the format of the transmitted data, so that different data formats can be handled simultaneously. In other words, it is possible to control to execute different processing depending on whether the data conforms to the CII standard format or not, so that it is possible to perform appropriate accumulation data collection processing for each case.

In particular, by analyzing the file name sent before transmission / reception of the actual data, the format of the actual data to be sent later can be determined.

Further, since the received files can be sorted in units of division based on not only the data transmission destination but also the specified data type, it is possible to perform more detailed classification than the data transmission destination. . That is, even if the data is for the same data transmission destination, only the type of data, for example, only the payment slip, can be separately sorted and sorted.

Further, since the security monitoring means for performing a security check based on registered security information and the like is provided, communication from a valid source to a valid destination can be reliably performed, and erroneous transmission of data is performed. Can be prevented.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration example of an EDI server conforming to a CII standard format which is an embodiment of a management system of received data in an EDI system according to the present invention.

FIG. 2 is a diagram illustrating a setting example of assortment information registered in an assortment information database according to the present embodiment.

FIG. 3 is a diagram showing a setting example of a subscriber information database in the present embodiment.

FIG. 4 is a diagram showing a setting example of a security information database according to the present embodiment.

FIG. 5 is a flowchart illustrating a collected data accumulation process according to the present embodiment.

FIG. 6 is a diagram showing an example of a method of designating a collection file name used in the present embodiment.

FIG. 7 is a diagram showing a transition of a file for creating a distribution file from a received file in the present embodiment, and an example of contents of a management information database of each of the collected file, the sorting data file, and the distributed file.

FIG. 8 is a network configuration diagram when each company is connected by a general wide area network.

FIG. 9 is a diagram showing an outline of a data structure of a collection file according to a CII standard format.

FIG. 10 is a diagram showing a format of a message group header in the CII standard format.

[Explanation of symbols]

10 Received file, 12 Data receiver, 14 Data format discriminator, 16 Sorting data file, 1
8 data storage management unit, 20 security check unit, 22 data conversion unit, 24 distribution file, 26
Assortment information database, 28 subscriber information database, 30 security information database, 32 collection file management information database, 34 assortment data management information database, 36 distribution file management information database.

Claims (5)

[Claims] 1. A reception data management method in an EDI system which receives a file name for storing data from a data transmission source in advance and stores reception data with the file name, receives data transmitted from the data transmission source. Data receiving means for storing the received data in the received file, and data format determining means for determining the data format of the transmitted data based on the received file name specified by the data source. A sorting information database that contains sorting information for sorting in sorting units; and if the transmitted data conforms to the CII standard format, sorts the received file based on the sorting information specified in the received data. If it is sorted and stored in units and does not conform to the CII standard format,
A data management means for storing the data as it is; and a management method of received data in the EDI system. 2. The data format discriminating means recognizes that source-specific information and destination-specific information are specified at predetermined positions in a character string constituting a file name, and converts the data into a CII standard format. 2. The method according to claim 1, wherein the data is determined to be non-compliant. 3. The system according to claim 1, wherein said data management means sorts said collection files based on a data transmission destination and a type of data. 4. A subscriber information database including an identification code for identifying a data transmission / reception destination and storing information on a communication party performing data communication, and a transmission source or transmission destination capable of data communication or a combination thereof is stored as security information. 3. The EDI according to claim 1, further comprising: a security information database for performing the communication, and security monitoring means for validating data transmitted only when a transmission / reception destination capable of data communication is designated. Management system for received data in the system. 5. A method for managing received data in an EDI system in which a file name for storing data is received in advance from a data transmission source and the received data is stored under the file name, the file name transmitted from the data transmission source is specified. A data format determining step of determining whether or not the transmitted data conforms to the CII standard format; and, if the transmitted data conforms to the CII standard format, classify the data into a designated category. And a data storage step of storing the data as a unit and storing the data as it is when the data does not conform to the CII standard format. How to manage incoming data.