JP2011128891A - System, method and program for managing edi data - Google Patents

Abstract

It is possible to process transmission data in EDI transmission efficiently and at a low cost, and to reduce a time lag in business processing due to correction and retransmission of transmission data.
SOLUTION: Means for receiving product order information from a buyer side terminal and searching an address of a seller side system based on information included in the order information, and addressing check data including the order information to the address of the seller side system A means for receiving the data check result regarding the data for checking by the data check program transmitted with the check request and held in the seller side system from the seller side system, and if the database check result is satisfactory, the order transmission data including the corresponding order information The EDI data management system 100 is composed of means for transmitting the message to the seller system.
[Selection] Figure 1

Description

  The present invention relates to an EDI data management system, an EDI data management method, and an EDI data management program. Specifically, the transmission side in EDI transmission can be processed efficiently and at a low cost on the receiving side. The present invention relates to a technology capable of reducing the time lag of business processing due to data correction and retransmission.

  An EDI (Electronic Data Interchange) system that unifies business transaction data between companies in a standard format and exchanges electronically is spreading. In this EDI system, data related to ordering, quotation, settlement, and arrival / departure is digitized according to a predetermined format and transmitted / received between terminals via a network such as a dedicated line or VAN.

  In carrying out such inter-company EDI transactions, EDI data transmission specifications (layout and values) have been decided in advance, and a system that can handle both ordering parties has been developed and constructed. In addition, when operating the EDI system, it is required that the sender and receiver of the data confirm the contents of the transmitted data so that data outside the specification is not captured by the business partner. Is created and maintained by both systems.

  As an EDI system and related art, for example, in an information exchange apparatus that exchanges information encrypted using an electronic key with another information exchange apparatus connected via a communication network, a public key and An information exchange device (see Patent Document 1) having an authentication device that issues a secret key as an electronic key has been proposed.

  In addition, an integrated system (see Patent Document 2) that smoothly integrates a plurality of devices, package software, and the like having different data formats and access methods has been proposed.

  Further, in the receiving side system in the electronic data exchange system, standard format data receiving means for receiving the standard format data with tag transmitted from the sending side system, and analyzing the received data, the untagged standard A standard format data analysis unit that generates a data format data definition body, and a standard data format data definition unit generated by the standard format data analysis unit is edited and displayed to create a data definition body in a local data format unique to the receiving side. An electronic data exchange system (see Patent Document 3) including a standard data format correction unit for correction has also been proposed.

JP 2006-128856 A JP 2004-086355 A Japanese Patent Laid-Open No. 10-105631

  By the way, in the data check program in the EDI system, for example, items such as attribute, number of digits, decimal point position confirmation, and character byte are checked as data value check items. In addition to checking each of these items, it is also necessary to check the relevance and consistency of values among a plurality of items, and the check on consistency with business data.

  However, for example, the manufacturer (manufacturer) does not disclose the detailed specifications of the product being handled to the buyer as confidential information, so even if the buyer creates order information during EDI transactions, Order information generation that comprehensively considers relevance checks and business data consistency checks cannot be performed. Accordingly, when various checks are performed by the manufacturer side system that has received such order information, order information determined to be out of specification is generated one after another, and the buyer side is often forced to correct the order information.

  For data exchange for business-to-business EDI transactions, file transfer methods using FTP and Zengin TCP / IP have been used for a long time. In such a data exchange method, data = order information transmitted by EDI from the buyer side is taken into the system as a batch processing target on the manufacturer side. For example, if the order information received by the manufacturer is an individual order item, it will require a delivery date response from the factory that is the manufacturer's manufacturing base, and until the order confirmation information is returned to the buyer, It will take several hours to several days.

  If there is a defect in the order information sent by the buyer side, the buyer side has to execute data correction and retransmission of the order information, which causes a time lag from order to delivery. Therefore, the buyer side will develop a program that can check the data of order information before transmission for the specification part published by the manufacturer so that data correction and retransmission will not occur as much as possible. Also, for the unpublished specifications of the manufacturer, check the manufacturer's countermeasures whenever a problem occurs, and add a unique check program to prevent data capture fraud as much as possible. Take measures to avoid it in operation. However, in the case of a buyer who conducts EDI transactions with a plurality of manufacturers, it is necessary to create unique data check programs for the number of business partners, and the costs associated with the program become a heavy burden.

  Accordingly, the present invention has been made in view of the above circumstances, and enables transmission data in EDI transmission to be processed efficiently and at low cost on the receiving side, thereby reducing the time lag of business processing due to correction and retransmission of transmission data. The main purpose is to provide technology.

  In EDI transactions, the buyer performs the original data check that the buyer has performed based on past experience and transmission results in a program held by the seller, led by the EDI data management system. As a service. As a result, the data check programs that have been developed and maintained on the buyer side and the seller side, respectively, are concentrated on the seller side, thereby reducing the costs associated with the development and maintenance of the program as a whole. It also improves data check accuracy and reduces the risk of time lag when a data failure occurs.

  The purpose of checking data in the seller's system is to check the values input from the buyer's terminal and the interrelationship between multiple values (check the values that cannot be combined between items). This check is performed in two stages: a check for the purpose of checking the layout when transmitting the order information as data to the seller. As a result, errors due to human causes such as input mistakes and various problems at the time of order entry on the buyer side are notified to the buyer side terminal as input errors in real time, and prompt correction can be made. On the other hand, the layout check of the transmission data can be notified to the system administrator by displaying it on the output means of the EDI data management system or the like, and the modification of the program for generating the transmission data from the order information can be urged.

  Specifically, the EDI data management method of the present invention that solves the above-described problem is a computer system that manages transmission data of an EDI system related to merchandise sales, and is used to determine the address on the network of the seller side system used by the buyer side terminal. Stored storage means, means for receiving product order information from the buyer side terminal via the network, searching for the address of the seller side system in the storage means based on information included in the order information, and from the buyer side terminal The check data including the received order information is transmitted together with the check request to the address of the searched seller side system, and the data check result regarding the check data by the data check program held by the seller side system is obtained. Means for receiving from the seller's system and the data; Characterized in that it comprises means for transmitting the order data transmitted to the corresponding seller side system over scan check result including the corresponding order information as long as no problem, the.

  Also, in the EDI data management system, the data check result received from the seller side system is the check result regarding the input contents such as the number of digits of each item value included in the order information, the character type, and the presence / absence of an essential relationship between items. If the data check result indicates that the data check result received from the seller side system and the data check result received from the seller side system indicate the check result related to the layout of the check data generated from the order information. And a means for outputting the check result to the output means.

  In the EDI data management system, each time a data check result is received from the seller side system, the number of times of use of the seller's data check program for the buyer is counted, and the value of the number of uses is stored in the storage means. Calculating a service usage fee by calculating a predetermined value for the number of times of use in the storage means, applying the service usage fee to a predetermined format to generate a bill and transmitting it to the buyer side terminal; and Means for executing the process of counting and storing the number of times of use and the process of calculating the service usage fee, generating the bill and transmitting it at predetermined intervals based on a schedule stored in advance in the storage means; It may be provided.

  In the EDI data management system, the time and number of times that the buyer side has logged in to the EDI data management system are counted and stored in the storage means during the log-in and log-off processes, The means for counting the number of times of use, and the transmission size and the number of times of transmission of various data transmitted from the buyer side terminal to the seller side system via the EDI data management system are stored in the storage means. A means for calculating the amount of data transmission and the number of times, and a means for calculating the service usage fee, generating a bill, and transmitting, the value of the usage number in the storage means, the usage time of the system for each buyer, Less number of usage counts, amount of data transmitted to sellers related to the buyer, and total number of times Calculated service usage fees to both by calculating the predetermined value, it transmits the service use fee to the generated buyer terminal bill by applying a predetermined format may be.

  Further, the EDI data management method of the present invention comprises a storage means for storing addresses on the network of the seller side system used by the buyer side terminal, and a computer system for managing transmission data of the EDI system related to merchandise sales is purchased by the buyer. Receiving the order information of the product from the side terminal via the network, searching the address of the seller side system in the storage means based on the information included in the order information, and the order information received from the buyer side terminal Processing including transmitting check data including the check request to the searched seller-side system address together with a check request, and receiving from the seller-side system a data check result related to the check data by the data check program held by the seller-side system Data received from the seller's system When the check result indicates a check result regarding each item value included in the order information, a process of transmitting the corresponding data check result to the buyer side terminal, and a data check result received from the seller side system are the layout of the check data. When the check result is shown, the process of outputting the corresponding data check result to the output means is executed.

  Further, the EDI data management program of the present invention includes a storage means for storing addresses on the network of the seller side system used by the buyer side terminal, the computer system for managing the transmission data of the EDI system related to merchandise sales to the buyer. Receiving the order information of the product from the side terminal via the network, searching the address of the seller side system in the storage means based on the information included in the order information, and the order information received from the buyer side terminal Processing including transmitting check data including the check request to the searched seller-side system address together with a check request, and receiving from the seller-side system a data check result related to the check data by the data check program held by the seller-side system And received from the seller side system When the data check result indicates a check result regarding each item value included in the order information, a process of transmitting the corresponding data check result to the buyer side terminal and a data check result received from the seller side system include the check data When the check result regarding the layout is shown, the process of outputting the corresponding data check result to the output means and the execution are executed.

  In addition, the problems disclosed by the present application and the solutions thereof will be clarified by the column of the best mode for carrying out the invention and the drawings.

  According to the present invention, by using a data check program created and operated by the seller, the order information and data layout on the buyer's side are pre-checked before EDI transmission, thereby improving the data check accuracy and in the event of a data malfunction. Can reduce the risk of time lags and reduce the cost of developing and maintaining data check programs on the seller side and system.

  Further, the system can provide a data check service to the buyer, and can also charge the buyer for usage charges for the data check program and the like by counting the number of times the buyer has used the data check program. By recirculating a part of the income obtained by this bill to the seller as the data check program usage cost, it also leads to a reduction in the data check program development / operation maintenance cost on the seller side.

  Therefore, it is possible to process the transmission data in EDI transmission efficiently and at low cost, and the time lag of business processing due to correction and retransmission of the transmission data can be reduced.

It is a figure which shows the network structural example containing the EDI data management system of this embodiment. It is a figure which shows the hardware constitutions of a buyer side terminal. It is a figure which shows the hardware constitutions of a joint center ordering server. It is a figure which shows the hardware constitutions of a common center transmission schedule server. It is a figure which shows the hardware constitutions of a common center accounting total server. It is a figure which shows the hardware constitutions of a common center database server. It is a figure which shows the hardware constitutions of a seller order receiving server. It is a figure which shows the hardware constitutions of a seller order acceptance terminal. It is a figure which shows the structural example of an order information table. It is a figure which shows the structural example of an order confirmation information table. It is a figure which shows the structural example of an order progress information table. It is a figure which shows the structural example of a connection destination management table. It is a figure which shows the structural example of an order server login log | history management table. It is a figure which shows the structural example of a data check utilization log | history management table. It is a figure which shows the structural example of an order transmission log | history management table. It is a figure which shows the structural example of an order number totaling table. It is a figure which shows the structural example of an order server login total table. It is a figure which shows the structural example of a data check utilization total table. It is a figure which shows the structural example of an order transmission amount totaling table. It is a figure which shows the structural example of an accounting billing table. It is a figure which shows the structural example of an order item master. It is a figure which shows the structural example of a charging apportionment master. It is a figure which shows the structural example of a user master. It is a figure which shows the structural example of a maker master. It is a figure which shows the structural example of a company master. It is a figure which shows the structural example of an order management database. It is a figure which shows the processing flow example 1 of the EDI data management method in this embodiment. It is a figure which shows the processing flow example 2 of the EDI data management method in this embodiment. It is a figure which shows the process flow example 3 of the EDI data management method in this embodiment. It is a figure which shows the process flow example 4 of the EDI data management method in this embodiment. It is a figure which shows the structural example of the login screen of this embodiment. It is a figure which shows the structural example of the order input screen of this embodiment. It is a figure which shows the structural example of the data check result display screen of this embodiment.

--- System configuration ---
Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a diagram showing a network configuration example including an EDI data management system 100 of the present embodiment. The EDI data management system 100 (hereinafter, system 100) shown in FIG. 1 makes it possible for the receiving side to process transmission data in EDI transmission efficiently and at low cost, and reduces the time lag of business processing due to correction and retransmission of transmission data. It is a computer system that makes it possible.

  The network configuration illustrated in FIG. 1 can be said to be the overall configuration of the inter-enterprise EDI transmission system 1, and the inter-enterprise EDI transmission system 1 includes a plurality of buyer-side terminals 10 and an EDI data management system 100 ( Joint center ordering server 11, joint center schedule server 12, joint center billing and summarizing server 13, joint center database server 14), seller side system 200 (seller order server 15 and seller order approval terminal 16) Are connected and configured via a network.

  The buyer terminal 10 is a terminal for a user such as a person in charge of a company who is a buyer to input and browse order information for a manufacturer who is a seller. On the other hand, the joint center ordering server 11 is an application server for checking contents related to order information input from the buyer terminal 10 and transmitting it to the seller system 200. The joint center schedule server 12 is a server that manages schedules for batch processing, and issues instructions such as data transmission from the joint center ordering server 11 to the seller order receiving server 15 and a data check service usage fee totaling process. Server to do. The joint center billing totaling server 13 is an application server in which a program for performing a totaling process of data check service usage charges is installed. The joint center database server 14 is a database server that stores various tables and databases for storing order information and various history data.

  On the other hand, the seller order receiving server 15 is a server for processing order information from the buyer, and is an application server for transmitting and receiving order information and order confirmations and for checking the data of the order information. Further, the seller order approval terminal 16 is a terminal for the person in charge on the seller side to view the order information and approve the order. It is assumed that there are a plurality of buyer side terminals 10, seller order receiving server 15, and seller order acceptance terminal 16.

  Next, a configuration example of each device connected to the network 140 will be described. In addition, even if not specifically described, each device has a general configuration (computer, storage device, communication device such as NIC, various interfaces for input / output) provided as a computer device that can be connected to the network, and necessary functions. It is assumed that the unit is realized by a program, for example.

  FIG. 2 is a diagram illustrating a hardware configuration of the buyer terminal 10. The buyer side terminal 10 includes a storage unit 201 composed of a hard disk drive and various memories, a display unit 202 such as a display, an input unit 203 such as a keyboard and a mouse, a control unit 204 such as a CPU, and a network interface unit 205 serving as a communication means. Each part is connected to BUS.

  The storage unit 201 stores a program for the screen display function 206 as a program executed by the control unit 204. The result of the screen display program 206 executed by the control unit 204 is displayed on the display unit 202. Further, the user of the buyer side terminal inputs and operates information on the screen displayed on the display unit 202 from the input unit 203, and the information is transferred to the joint center ordering server 11 via the network interface unit 205. Deliver.

  FIG. 3 is a diagram illustrating a hardware configuration of the joint center ordering server 11. The joint center ordering server 11 includes a storage unit 301 composed of a hard disk drive, various memories, and the like, a control unit 302 such as a CPU, and a network interface unit 305 as communication means, and each unit is connected to the BUS.

  The storage unit 301 includes, as programs executed by the control unit 302, a user authentication function 304, a user screen generation function 305, an order number issuing function 306, an order progress update function 307, an order information registration function 308, and connection destination information acquisition. Function 309, order information check data generation function 310, order information check call function 311, order transmission layout check call function 312, order transmission data generation function 313, transmission data transmission / reception function 314, order confirmation registration function 315, check result notification function 316 Each program of the check history information registration function 317, the login history information registration function 318, and the transmission history information registration function 319 is stored.

  The user authentication function 304 is a program for executing user authentication when the buyer side terminal 10 logs into the joint center ordering server 11. The user screen creation function 305 is a program that generates a screen to be displayed on the buyer side terminal 10. The order number issuing function 306 is a program for issuing an order number for creating an order. Further, the order progress update function 307 receives information on the order progress until the order information issued by the order number issuing function 306 is transmitted to the seller order receiving server 15. This program is stored in the progress management table 606.

  The order information registration function 308 is a program for storing the order information input from the buyer terminal 10 in the order information table 604 of the joint center database server 14. Further, the connection destination information acquisition function 309 uses the order information check call function 311 and the order transmission layout check call function 312 to provide information on which of the plurality of seller order receiving servers 15 should be connected to the common center. This is a program for obtaining from the connection destination management table 607 of the database server 14.

  In addition, the order information check data generation function 310 may be an order information value check (eg, number of digits, character type, etc.) or a relevance check (eg: a value that is an essential combination between items, or between items. This is a program for generating check data to be sent to the seller order receiving server 15 in the case of executing the presence or absence of a combination value that does not exist. The order information check calling function 311 is a program for calling the data check function 704 of the seller order receiving server 15 when performing a value check or relevance check of the order information.

  The order transmission layout check call function 312 performs a layout check of the seller order receiving server 15 when performing a layout check of order transmission data created by the order transmission data generation function 313 (to be described later with reference to FIG. 29, etc.). This is a program for calling the function 706. The order transmission data generation function 313 is a program for generating data that is actually transmitted as an order to the seller order server 15 based on the order information table 604 registered in the joint center database server 14.

  The transmission data transmission / reception function 314 is a program for performing data transmission with the seller order receiving server 15. The order confirmation registration function 315 is a program for storing the order confirmation information transmitted from the seller order receiving server 15 in the order confirmation information table 605 of the joint center database server 14. The check result notification function 316 is a program for notifying the result of the check by the order information check call function 311 and the order transmission layout check call function 312 on the screen of the display unit 202 in the buyer terminal 10. is there.

  The check history information registration function 317 stores the history in the data check usage history management table 609 of the joint center database server 14 when the order information check call function 311 and the order transmission layout check call function 312 are executed. It is a program to do. Further, the login history information registration function 318 uses the order information server of the joint center database server 14 as the history information when the buyer side terminal 10 logs in to the joint center order server 11 via the user screen generation function 305. This is a program for storing in the login history management table 608. The transmission history information registration function 319 is a program for storing history information in the order transmission history management table 610 of the joint center database server 14 when data transmission is performed to the seller order receiving server 15. .

  FIG. 4 is a diagram illustrating a hardware configuration of the joint center transmission schedule server 12. The joint center transmission schedule server includes a storage unit 401 composed of a hard disk drive, various memories, and the like, a control unit 402 such as a CPU, and a network interface unit 403 as communication means, and each unit is connected to the BUS. The storage unit 401 stores programs of an order transmission schedule function 404 and a totaling schedule function 405 as programs executed by the control unit 402.

  The order transmission schedule function 404 is a program for instructing the joint center ordering server 11 to transmit order transmission data according to a transmission schedule (predetermined date and time, predetermined interval, etc.) registered in advance. The aggregation schedule function 405 is a program for instructing the joint center billing aggregation server 13 to perform aggregation processing according to a pre-registered time.

  FIG. 5 is a diagram illustrating a hardware configuration of the joint center billing totaling server 13. The joint center billing totaling server includes a storage unit 501 including a hard disk drive and various memories, a control unit 502 such as a CPU, and a network interface unit 503 serving as a communication unit, and each unit is connected to the BUS. The storage unit 501 includes, as programs executed by the control unit 502, an order execution count total 504, a usage user count / usage time count 505, a data check usage count total 506, an order transmission size / count count 507, an order data check service. The billing fee calculation 508 and order data check service bill generation 509 programs are stored.

  The order execution count total 504 is a program that counts the number of orders based on the order information table 604 of the joint center database server 14 and stores the result in the order count totaling table 611. In addition, the usage user count / usage time count 505 is based on the order server login history management table 608 of the joint center database server 14 and counts the usage time / count of the system 100 of each user. This is a program stored in the order server login tabulation table 612.

  The data check usage count tally 506 counts the number of usages of the data check program provided by the seller side system 200 based on the data check usage history management table 609 of the joint center database server 14, and the result is obtained. This is a program stored in the data check use tabulation table 613. Further, the order transmission size / count tally 507 is based on the order transmission history management table 610 of the joint center database server 14, for example, summing up the transmission size and the number of transmissions of order transmission data for each buyer. This is a program stored in the order transmission amount totaling table 614.

  The order data check service billing fee calculation 508 includes the order count table 611, the order server login tabulation table 612, the data check usage tabulation table 613, the order transmission amount tabulation table 614, and the charge apportionment master 617. Based on the above, the program calculates the weighting in the charge calculation of each aggregated data, calculates the charge for using the data check service for the buyer, and stores the result in the billing request table 615. The order data check service bill generation 509 is a program for generating a bill related to the use of the data check service issued to the buyer based on the billing billing table 615 of the joint center database server 14.

  FIG. 6 is a diagram illustrating a hardware configuration of the joint center database server 14. The joint center database server 14 includes a storage unit 601 composed of a hard disk drive, various memories, and the like, a control unit 602 such as a CPU, and a network interface unit 603 serving as communication means, and each unit is connected to the BUS. The storage unit 601 includes an order information table 604, an order confirmation information table 605, an order progress management table 606, a connection destination management table 607, an order server login history management table 608, a data check usage history management table 609, and an order transmission history management. Table 610, order count table 611, order server login tabulation table 612, data check usage tabulation table 613, order transmission amount tabulation table 614, billing billing table 615, order item master 616, billing apportionment master 617, user master 618, manufacturer Each table information of the master 619 and the company master 620 is stored. The outline of each table will be described below (details will be described later).

  The order information table 604 stores order information that a buyer places an order with a seller (manufacturer). The order confirmation information table 605 stores order confirmation information issued by the seller. Further, the order progress management table 606 stores the processing status of orders when a buyer places an order through the joint center ordering server 11. The connection destination management table 607 stores connection destination information when the joint center ordering server 11 causes the seller order receiving server 15 to perform a data check (including a layout check) regarding the check data.

  The order server login history management table 608 stores history information (eg, time and number of times) when the buyer terminal 10 logs in to the system of the joint center order server 11. The data check usage history management table 609 stores the number of times that the joint center ordering server 11 causes the seller order receiving server 15 to perform order information data check and layout check. The order transmission history management table 610 stores history information (time, size, number of times) of order transmission data transmitted from the joint center ordering server 11 to the seller order receiving server 15.

  Further, the order count table 611 stores, for example, order count information for each month that is tabulated based on the order information table 604. Further, the order server login tabulation table 612 stores, for example, monthly login time / count information that is tabulated based on the order server login history management table 608. The data check usage tabulation table 613 stores monthly data check frequency information that is tabulated based on the data check usage history management table 609.

  The order transmission amount totaling table 614 stores, for example, order transmission amount (size, number of times) information for each month, which is totaled based on the order transmission history management table 610. The order item master 616 is master information for storing item definitions of order information. Further, the billing apportionment master 617 calculates an order charge count table 611, an order server login count table 612, a data check use count table 613, an order transmission amount, which are the basis of charge calculation, when calculating the charge for using the data check service. This is master information for storing the weighting information of the aggregation table 614. The user master 618 is master information for storing user information and authentication information as authentication criteria when the buyer terminal 10 logs in to the joint center ordering server 11. The manufacturer master 619 is master information for storing information on a seller (manufacturer) as an ordering party for products and the like. The company master 620 is master information for storing company / department information of buyer users who use the common center (the system 100).

  FIG. 7 is a diagram illustrating a hardware configuration of the seller order receiving server 15. The seller order receiving server includes a storage unit 701 composed of a hard disk drive, a memory, and the like, a control unit 702 such as a CPU, and a network interface unit 703 as communication means, and each unit is connected to the BUS. The storage unit 701 includes a data check function 704, a data check result generation function 705, a layout check function 706, a layout check result creation function 707, a transmission data generation function 708, and transmission data transmission / reception as programs executed by the control unit 702. Each program of a function 709 and a transmission data fetch function 710 and an order data management database 711 are stored.

  The data check function 704 is a program that executes an association check between an item value of order information and a plurality of item values requested from the joint center ordering server 11. The data check result generation function 705 is a program for generating a message when returning the result of the check executed by the data check function 704 to the joint center ordering server. The layout check function 706 is a program for executing a layout check of the order transmission data requested from the joint center ordering server 11.

  The layout check result creation function 707 is a program for generating a message when returning the result of the layout check executed by the layout check function 706 to the joint center ordering server. The transmission data generation function 708 is a program for generating order confirmation data for the joint center ordering server 11. The transmission data transmission / reception function 709 transmits the order confirmation data generated by the transmission data generation function 708 to the joint center ordering server 11 and receives the order transmission data transmitted from the joint center ordering server 11. This is a program that implements the transmission function. The transmission data fetching function 710 is a program for storing the order information included in the order transmission data transmitted from the joint center ordering server 11 in the order data management database 711. The order data management database 711 is a database for managing the order information transmitted from the joint center ordering server 11 as order data.

  FIG. 8 is a diagram illustrating a hardware configuration of the seller order acceptance terminal 16. The seller order approval terminal 16 includes a storage unit 801 including a hard disk drive and a memory, a display unit 802 such as a display, an input unit 803 such as a keyboard and a mouse, a control unit 804 such as a CPU, and a network interface unit 805 serving as a communication means. Each part is connected to BUS. The storage unit 801 stores programs for a screen display function 806 and an order acceptance function 807 as programs executed by the control unit 804. The result of the executed screen display program 806 is displayed on the display unit 802. Further, the user of the seller order approval terminal 16 performs an order approval process on the order information screen displayed on the display unit 802 from the input unit 803 via the order approval function 807, and the information is the network interface unit 805. Are stored in the order data management database 711 of the seller order receiving server 15.

  Each function in the system 100, the seller-side system 200, and the buyer-side terminal 10 described so far may be realized as hardware, or as a program stored in an appropriate storage unit such as a memory or an HDD (Hard Disk Drive). It may be realized. In this case, a control unit such as a CPU reads the corresponding program from the storage unit in accordance with the program execution and executes it.

--- Configuration example of table etc .---
Next, a configuration example of tables included in the joint center database server 14 of the system 100 and the seller order receiving server 15 of the seller-side system 200 will be described. FIG. 9 is a diagram illustrating a configuration example of the order information table 604. As shown in FIG. 9, the order information table 604 includes an order number 901, a manufacturer ID 902, a company ID 903, a customer 904, a quantity 905, product information 906, specification information 907, other specification information 908, and registration. Each piece of information indicating the date and time 909 is stored in association with each other. Here, the order number 901 is information for identifying the order information that the buyer places an order with the seller. The manufacturer ID 902 is information for identifying the manufacturer on the seller side who is the ordering party. The company ID 903 is information for identifying the buyer who is the ordering source = the orderer.

  The customer 904 is an item indicating company / organization information that is actually used for the ordered item ordered by the buyer. For example, when a user who actually wants to procure a product orders a product from a manufacturer through a buyer, the customer 904 stores information on the user (company / organization) that he / she wants to procure. If the orderer is the same as the product user, the customer 904 stores the same information as the company ID 903. The quantity 905 is information indicating the order quantity of the ordered product ordered by the buyer. The product information 906 is information for identifying a product ordered by the buyer. The specification information 907 and other specification information 908 indicate detailed specification information related to the product indicated by the product information 906. The registration date 909 is information indicating the date when the order information is stored in the order information table 604.

  FIG. 10 is a diagram illustrating a configuration example of the order confirmation information table 605. As shown in FIG. 10, the order confirmation information table includes an order number 1001, a manufacturer ID 1002, a company ID 1003, a customer 1004, a quantity 1005, product information 1006, specification information 1007, other specification information 1008, and an approval. Information indicating the date and time 1009 is stored in association with each other. The order number 1001, manufacturer ID 1002, company ID 1003, customer 1004, quantity 1005, product information 1006, specification information 1007, and other specification information 1008 are items of order confirmation information sent from the seller (manufacturer). As the item information, information equivalent to the order information table 604 is shown. The approval date and time 1009 is information indicating the date and time approved by the seller order approval terminal 16.

  FIG. 11 is a diagram illustrating a configuration example of the order progress management table 606. As shown in FIG. 11, the order progress management table 606 stores order number 1101, creation date 1102, update date 1103, and information indicating order status 1104 in association with each other. The order number 1101 is information associated with the order number 901 in the order information table 604, and is information for identifying an order. The creation date and time 1102 is time information indicating the date and time when the order status 1104 is updated for the first time. The update date and time 1103 is time information indicating the date and time when the order status 1104 was last updated. The order status 1104 is information indicating a progress status from when a number is assigned to the created order information until the order confirmation is received. In the present embodiment, the order status 1104 includes “editing order”, “data checking”, “waiting for order transmission”, “under order transmission”, “order transmitted”, “order pending registration”, “order canceled”. , Manage the status by either “Order Confirmed”.

  FIG. 12 is a diagram illustrating a configuration example of the connection destination management table 607. As shown in FIG. 12, the connection destination management table 607 corresponds to information indicating the user ID 1201, the company ID 1202, the concurrent ID 1203, the manufacturer ID 1204, the connection address 1205, the expiration date 1206, and the validity / invalidity flag 1207, respectively. Stored with. The user ID 1201, the company ID 1202, and the concurrent ID 1203 are information for identifying a buyer user who uses the joint center ordering server 15 associated with the user ID 2301, the company ID 2302, and the concurrent ID 2303 of the user master 618. The manufacturer ID 1204 is information for identifying seller manufacturer information associated with the manufacturer ID 2401 of the manufacturer master 619. The connection address 1205 is information indicating that the connection destination of the seller order server 15 to be connected = the address on the network when calling the data check function 704 or the layout check function 706 of the seller order server 15 from the joint center ordering server 11. It is. The usage time limit 1206 is information indicating a usage time limit of the record, and the data check function and the layout check function are invalid for a record that has passed the time limit. The valid / invalid flag 1207 is information for identifying whether the data check function and the layout check function are valid or invalid. The valid / invalid flag 1207 is managed by either “valid” or “invalid”.

  FIG. 13 is a diagram illustrating a configuration example of the ordering server login history management table 608. As shown in FIG. 13, the order server login history management table 608 includes a date 1301, a user ID 1302, a company ID 1303, a concurrent ID 1304, a login total time 1305, a last login date 1306, and the number of authentications 1307. Are stored in association with each other. The date 1301 is time information indicating the date when the buyer terminal 10 logs into the joint center ordering server 11. The user ID 1302, the company ID 1303, and the concurrent ID 1304 are information for identifying a buyer user who uses the joint center ordering server 15 associated with the user ID 2301, the company ID 2302, and the concurrent ID 2303 of the user master 618. The log-in total time 1305 is time information indicating the sum of the use times in which the buyer terminal 10 has accessed the joint center ordering server 11 in the past. The last login date and time 1306 is information indicating the time when the buyer terminal 10 last logged into the joint center ordering server 11. The number of times of authentication 1307 is information indicating the number of times that the buyer user logs in to the joint center ordering server 11 via the buyer terminal 10.

  FIG. 14 is a diagram showing a configuration example of the data check usage history management table 609. As shown in FIG. As shown in FIG. 14, the data check use history management table 609 includes information indicating a date 1401, a check category 1402, a user ID 1403, a company ID 1404, a concurrent ID 1405, a manufacturer ID 1406, and the number of checks 1407. Are stored in association with each other. The date 1401 is information indicating date information when the joint center ordering server 11 causes the seller order receiving server 15 to perform a data check. The check category 1402 is category information for identifying a check method, and is indicated by either “data check” or “layout check”. The user ID 1403, company ID 1404, and concurrent ID 1405 are information for identifying a buyer user who uses the joint center ordering server 15 associated with the user ID 2301, company ID 2302, and concurrent ID 2303 in the user master 618. The manufacturer ID 1406 is information for identifying seller manufacturer information associated with the manufacturer ID 2401 of the manufacturer master 619. The number of checks 1407 indicates the number of times that the joint center ordering server 11 causes the seller order receiving server 15 to perform data check and layout. That is, the data check usage history management table 609 stores history information that the joint center ordering server 11 causes the seller order receiving server 15 to perform data check and layout for each user, each manufacturer, and each day.

  FIG. 15 is a diagram illustrating a configuration example of the order transmission history management table 610. As shown in FIG. 15, the order transmission history management table 610 stores information indicating transmission date and time 1501, company ID 1502, manufacturer ID 1503, and order size 1504 in association with each other. The transmission date and time 1501 is time information indicating the date and time when the order transmission data is transmitted from the joint center ordering server 11 to the seller order receiving server 15. The company ID 1502 is information for identifying which buyer user has transmitted the order transmission data to the seller order receiving server 15 via the joint center ordering server 11. The manufacturer ID 1503 is associated with the manufacturer ID 2401 of the manufacturer master 619 and is information for identifying information on the seller manufacturer of the transmission destination. The order size 1504 is information for storing the size of the order transmission data transmitted from the joint center ordering server 11 to the seller order receiving server 15. The order transmission history management table 610 manages the information generated for each order transmission.

  FIG. 16 is a diagram illustrating a configuration example of the order count table 611. As shown in FIG. 16, the order count table 611 stores information indicating year / month 1601, company ID 1602, manufacturer ID 1603, and order contract count 1604 in association with each other. The year / month 1601 is information indicating the time of year / month. The company ID 1602 is information for identifying the buyer who is the ordering source = the orderer. The manufacturer ID 1603 is information for identifying seller manufacturer information associated with the manufacturer ID 2401 of the manufacturer master 619. Further, the order execution number 1604 is information indicating the number of orders executed by the joint center ordering server 11, and is summarized by year / month information of the registration date / time 909 of the order information table 604, company ID 903, and manufacturer ID 902. It is calculated by the number of records.

  FIG. 17 is a diagram illustrating a configuration example of the order server login tabulation table 612. As shown in FIG. 17, the order server login tabulation table 612 stores information indicating year 1701, company ID 1702, login time total 1703, login count total 1704, and user count total 1705 in association with each other. Is done. The date 1701 is time information associated with the date information of the date 1301 in the order server login history management table 608. The company ID 1702 is information for identifying the buyer who is the ordering source = the orderer. The login time total 1703 is time information obtained as a result of summarizing the login total time 1305 with the company ID 1303 and the year / month information 1301 of the ordering server login history management table 608. The total number of logins 1704 is numerical information obtained as a result of summarizing the number of authentication times 1307 with the company ID 1303 and the year / month information 1301 of the ordering server login history management table 608. Further, the total number of users 1705 is obtained by the number of records summarized by the year / month information 1301 of the order server login history management table 608 and the company ID 1303.

  FIG. 18 is a diagram illustrating a configuration example of the data check use aggregation table 613. As shown in FIG. 18, the data check usage tabulation table 613 stores information indicating year / month 1801, company ID 1802, manufacturer ID 1803, and check usage count 1804 in association with each other. The year / month 1801 is time information associated with the year / month information of the year / month / day 1401 of the data check use history management table 609. The company ID 1802 is information for identifying the buyer who is the ordering source = the orderer. The manufacturer ID 1803 is information for identifying the seller (manufacturer) that provided the data check program. The check use count 1804 is numerical information obtained as a result of summarizing the check count 1407 with the company ID 1403 and the year / month / day information 1401 of the data check use history management table 609.

  FIG. 19 is a diagram illustrating a configuration example of the order transmission amount totaling table 614. As shown in FIG. 19, the order transmission amount totaling table 614 stores information indicating year 1901, company ID 1902, manufacturer ID 1903, order size total 1904, and total transmission count 1905 in association with each other. . The year 1901 is time information associated with the year / month information of the transmission date / time 1501 of the order transmission history management table 610. The company ID 1902 is information for identifying the buyer who is the ordering source = the orderer. The manufacturer ID 1903 is information for identifying information of the seller manufacturer associated with the manufacturer ID 2401 of the manufacturer master 619. The order size total 1904 is numerical information obtained as a result of summarizing the order size 1504 with the year / month information of the transmission date / time 1501 of the order transmission history management table 610, the company ID 1502, and the manufacturer ID 1503. Further, the total number of transmissions 1905 is obtained by the number of records summarized by the year / month information of the transmission date / time 1501 of the order transmission history management table 610, the company ID 1502, and the manufacturer ID 1503.

  FIG. 20 is a diagram illustrating a configuration example of the billing table 615. As shown in FIG. 20, the billing billing table 615 stores information indicating year / month 2001, company ID 2002, and billing fee 2003 in association with each other. The year / month 2001 is time information indicating a billing month. The company ID 2002 is information for identifying the buyer who is the ordering source = the orderer, and is billing destination information. The billing fee 2003 is money amount information indicating a billing fee to the billing destination.

  FIG. 21 is a diagram illustrating a configuration example of the order item master 616. As shown in FIG. 21, the order item master 616 stores item ID 2101, item name 2102, character attribute 2103, and information indicating the number of digits 2104 in association with each other. The item ID 2101 is identification information of each item constituting the order information, and the item name 2102 indicates the name of the item ID 2101. The character attribute 2103 is information indicating what character attribute the corresponding item becomes, and stores information such as numerical values and character strings, for example. The number of digits 2104 is information on the number of significant digits of the numerical value of the corresponding item and the number of bytes of the character string.

  FIG. 22 is a diagram illustrating a configuration example of the billing apportionment master 2201. As shown in FIG. 22, the billing apportionment master 2201 has a apportionment ID 2201, a check apportioning apportionment 2202, a log apportioning apportionment 2203, a transmission apportioning apportionment 2204, a transmission apportioning apportioning apportionment 2205, an order count apportioning apportionment 2206, and a scheduled charge amount 2207. Are stored in association with each other. The apportionment ID 2201 is information for identifying the apportioning method of the usage fee for the data check service to the buyer user (company). By using this ID, for example, the apportionment apportionment can be changed every year. It is also possible to change the service charge calculation method according to the usage level of the buyer user and the company scale (however, in this embodiment, any method of using this ID may be used). Further, the check frequency apportionment 2202, the transmission amount apportionment 2204, the transmission apportionment apportionment 2205, and the order number apportionment apportionment 2206 are values for weighting the use of the data check service, and the sum of each value is 100%. . Therefore, the higher the weighting value, the greater the influence on the service fee. The scheduled billing amount 2207 is information indicating the sum total of the scheduled billing amount of the data check service usage fee for the buyer user. This cost can be used as a funding source for the development / maintenance of the data check program on the seller side when the joint center side = system side returns to the manufacturer of the seller.

  FIG. 23 is a diagram illustrating a configuration example of the user master 618. As shown in FIG. 23, the user master 618 stores information indicating a user ID 2301, company ID 2302, business ID 2303, authority 2304, password 2305, expiration date 2306, and validity flag 2307 in association with each other. Is done. The user ID 2301 is identification information of a user who logs in to the system of the joint center ordering server 11 from the buyer side terminal 10. The company ID 2302 is information for identifying the company to which the user ID 2301 belongs, and is associated with 2501 of the company master 620. The concurrent ID 2303 is identification information when the user corresponding to the user ID 2301 belongs to multiple departments concurrently. The authority 2304 is identification information indicating a usable range of the joint center ordering server 11 by the user corresponding to the user ID 2301. The password 2305 is authentication information used when logging in to the joint center ordering server 11 from the buyer terminal 10. The expiration date 2306 is date information indicating how long the user can use the system of the joint center ordering server 11. The validity flag 2307 is identification information indicating whether the user ID 2301 is valid or invalid. When the validity flag 2307 is invalid, the authentication to the joint center ordering server 11 is not performed for the corresponding user.

  FIG. 24 is a diagram illustrating a configuration example of the manufacturer master 619. As shown in the drawing, the manufacturer master 619 stores information indicating a manufacturer ID 2401, a manufacturer name 2402, and a manufacturer group 2403 in association with each other. The manufacturer ID 2401 is information for identifying a manufacturer as a seller, and the manufacturer 2402 is name information associated with the manufacturer ID 2401. The manufacturer group 2403 is information for identifying a plurality of sellers when they are grouped together as a consolidated company.

  FIG. 25 is a diagram illustrating a configuration example of the company master 620. As shown in the figure, the company master 620 stores information indicating a company ID 2501, a company name 2502, and an address 2503 in association with each other. The company ID is information for identifying an organization or company that uses the system 100 or the like such as a buyer or a seller. The company name 2502 is information indicating the name of the company identified by the company ID 2501, and the address 2503 is information indicating the address of the company identified by the company ID 2501.

  FIG. 26 is a diagram illustrating a configuration example of the order data management database 711. As shown in FIG. 26, the order data management database 711 includes an order number 2601, an orderer 2602, a customer 2603, a quantity 2604, product information 2605, specification information 2606, an order reception date 2607, an approval date 2608, Information indicating the delivery date 2609 is stored in association with each other. The order number 2601, the orderer 2602, the customer 2603, the quantity 2604, the product information 2605, and the specification information 2606 are the order transmission data (= including order information) transmitted from the joint center ordering server 11. Stores the associated information. The order reception date and time 2607 is time information indicating the date and time when the order transmission data is transmitted from the joint center ordering server 11. The approval date and time 2608 is a time indicating the date and time when the order is approved from the seller order approval terminal 16. Information. The delivery date 2609 is time information indicating the delivery date and time of the ordered product.

--- Procedure example (value check) ---
Hereinafter, the actual procedure of the EDI data management method in the present embodiment will be described with reference to the drawings. The main operation corresponding to the EDI data management method described below is realized by a program that is read from the storage unit and executed by the control unit such as the CPU of each server constituting the system 100. Further, other operations are similarly realized by the devices constituting the buyer side terminal 10 and the seller side system 200. And such a program is comprised from the code | cord | chord for performing the various operation | movement demonstrated below.

  FIG. 27 and FIG. 28 are diagrams showing a processing flow example 1 and a processing flow example 2 of the EDI data management method in the present embodiment, and are flowcharts showing order information value check processing in the inter-company EDI transaction.

  Here, first, it is assumed that a buyer user = a person in charge of a company or the like inputs a login URL of the joint center ordering server 11 at the buyer terminal 10. Upon receiving this, the joint center ordering server 11 returns screen data corresponding to the login screen of FIG. 31, and the login screen is displayed by the screen display function 206 on the display unit 202 of the buyer side terminal 10 ( S2701, S2702).

  At this time, the buyer user inputs a user ID and password on the login screen of FIG. 31, and presses the login button. The buyer terminal 10 that has received the request sends an authentication request including user ID and password data to the joint center ordering server 11 (S2703).

  On the other hand, the joint center ordering server 11 uses the user authentication function 304 to set the user master 618 of the joint center database server 14 based on the user ID and password included in the authentication request transmitted from the buyer terminal 10. The authentication process is performed by using it (S2704). When the user authentication here is successful, the joint center ordering server 10 updates the login time and the number of times with the record of the corresponding user ID in the ordering server login history management table 608 by the login information history registration function 318. (S2705).

  After the log-in history update is completed, the joint center ordering server 11 transmits the order basic input screen data shown in FIG. 32 (eg, stored in advance in the storage unit) to the buyer terminal 10 for display (S2706). The buyer user inputs seller's (manufacturer) information as an ordering destination on the order basic input screen displayed on the buyer side terminal 10 and presses the registration button. Upon receiving this input and pressing the registration button, the buyer side terminal 10 sends the information obtained on the order basic input screen to the joint center ordering server 11 (S2707, S2708).

  The joint center ordering server 11 issues an order number to the order basic information sent from the buyer terminal 10 by the order number issuing function 306, and the order information table 604 corresponds to the issued order number. In addition, the order information is stored (S2709). Further, the joint center ordering server 11 stores the information in the order progress management table 606 as the order status “editing order” by the order progress update function 307 (S2710). Further, the joint center ordering server 11 transmits the order detail screen data (for example, stored in advance in the storage unit) to the buyer terminal 10 for display (S2711).

  On the order detail screen displayed on the display unit 202 of the buyer-side terminal 10, the buyer user inputs detailed information on the ordered product to be ordered and presses a registration button. Upon receiving this, the buyer terminal 10 transmits the detailed order information to the joint center order server 11 (S2801, S2802). On the other hand, the joint center ordering server 11 receives the detailed order information sent from the buyer terminal 10 and stores it in the order information table 604 (S2803). Thereafter, the joint center ordering server 11 obtains connection destination information for checking the values included in the order information (eg, order quantity, product model number, date, etc.) and the relevance of values between multiple items. The function 309 attempts to acquire the network address = connection destination information related to the seller (maker) from the connection destination management table 607 (S2804). If acquisition of the connection destination information is not successful (S2805: N), the joint center ordering server 11 uses the order progress update function 307 to display the order status regarding the corresponding order information in the order progress management table 606 as “order”. The "editing" is updated to "wait for order transmission" (S2814).

  On the other hand, if the connection destination information has been successfully acquired (S2805: Y), the joint center ordering server 11 uses the order progress update function 307 to change the order status related to the corresponding order information in the order progress management table 606 to “editing order”. To “during order check” (S2806). Thereafter, the joint center ordering server 11 uses the order information check data generation function 310 to generate check data for performing a check on order information from the order information table 604 and the order item master 616 (S2807). The generation processing of the check data by the order information check data generation function 310 has a generation procedure or the like determined in advance according to the required specifications of the check program provided in the seller side system 200 (may be an existing one) ).

  The check data generated here is transferred from the joint center ordering server 11 to the seller order receiving server 15 by the order information check calling function 311 of the joint center ordering server 11 (S2808). On the other hand, the seller order receiving server 15 uses the data check function 704 to check each item value of the order information such as the number of digits and the character type based on the check data received from the joint center ordering server 11 and the relationship between the item values. (Required or impossible relevance. For example, “When item a is set to value a, item B must be set to value b”), or “when item A is set to value a , Item C cannot be set to the value d ”(check of viewpoint)” is performed (S2809). At this time, if there is a check specific to the orderer, the orderer is identified from the company ID stored in the information sent as check data, and an individual item value check specific to the orderer is performed ( S2810). The check result is generated by the data check result generation function 705 and returned from the seller order receiving server 15 to the joint center ordering server 11 (S2811).

  The joint center ordering server 11 stores the data check result returned from the seller order receiving server 15 as a check usage history in the data check usage history management table 609 by the check history information registration function 318 (S2812). Further, the joint center ordering server 11 generates a data check result screen by the user screen generation function 305, transmits the check result to the buyer side terminal 10, and causes the display unit 202 to display the screen as shown in FIG. (S2813). If the buyer user views the screen of FIG. 33 and there is an error in the content, the order information can be immediately corrected. When the data check result does not indicate an error or when a predetermined instruction is received after correction by the user, the joint center ordering server 11 uses the order progress update function 307 to place an order on the corresponding record in the order progress management table 606. The status is updated from “during order check” to “wait for order transmission” (S2814).

--- Processing procedure example (layout check) ---
Next, the layout check will be described. FIG. 29 is a flowchart showing a layout check process for order transmission data in an inter-company EDI transaction. In this case, first, the joint center schedule server 12 instructs the joint center ordering server 11 to start transmission using the order transmission schedule function 404 according to a predetermined schedule (S2901). On the other hand, the joint center ordering server 11 receives the transmission start instruction from the joint center schedule server 12, and generates order transmission data based on the order information in the order information table 604 by the order transmission data generation function 313 (S2902). ). Since this order transmission data is data that undergoes layout check, it can also be said to be data for checking, but it is official order information between the buyer and the seller, for example, data based on specifications specified in advance by the buyer. Composed. For generating the order transmission data, for example, an order transmission data generation template is stored in advance in the storage unit of any server of the system 100, and the order transmission data generation function 313 assigns an order to each item in the template. This is done by setting the value of the corresponding item among the items in the information. Alternatively, existing technology may be employed.

  Thereafter, the joint center ordering server 11 uses the connection destination information acquisition function 309 to acquire connection information on the network of the relevant seller (manufacturer) from the acquisition connection destination management table 607 for the layout check of the generated order transmission data. (S2904). If the connection destination information is not successfully acquired (S2904: acquisition failure), the joint center ordering server 11 uses the order progress update function 307 to set the order status to “transmission waiting” in the corresponding record of the order progress management table 606. To “transmission of order”, and the order data transmission process is performed from the joint center ordering server 11 to the seller order receiving server 15 (S2904, S2912, S2913). That is, the order transmission data is transmitted to the seller side system 200 for the time being without going through the advance check in the seller side system 200.

  On the other hand, if the connection destination information has been successfully acquired (S2904: acquisition success), the joint center ordering server 11 changes the order status from “waiting for transmission” to “order” in the corresponding record of the progress management table 606 by the order progress update function 307. It is updated to “Checking” (S2905). The joint center ordering server 11 performs the order transmission layout check calling function 312, passes the order transmission data created by the order transmission data generation function 313 to the seller order receiving server 15, and requests a layout pre-check (S 2906).

  On the other hand, the seller order receiving server 15 receives a layout check request from the joint center ordering server 11 and performs a layout check by the layout check function 706 (S2907). This layout check varies depending on the specifications of the seller, and may be executed by existing technology. In any case, it is checked whether the order transmission data issued by the joint center ordering server 11 matches the specifications on the seller side.

  The check result in the seller side system 200 is generated by the layout check result creation function 707 as, for example, a predetermined message indicating the presence / absence of an error, and is returned from the seller order receiving server 15 to the joint center ordering server 11 (S2908). The joint center ordering server 11 receives the layout check result returned from the seller order receiving server 15, and uses the check history information registration function 318 to use the layout check result as data check service usage history information in a data check usage history management table. It stores in 609 (S2908).

  Subsequently, the joint center ordering server 11 determines whether the layout check result indicates an error by the check result notification function 316 (S2910). If it is determined that there is an error in this determination (S2910: There is an error), the check result notification function 316 is, for example, a predetermined terminal for error notification (eg, a terminal used by the system administrator of the joint center ordering server 11). The network address is held in advance by the system 100) and the error content is notified to a predetermined output device (S2911). A system administrator or the like who has read this notification will take necessary measures such as reviewing the order transmission data generation process in accordance with the error contents.

  On the other hand, when it is determined that there is no error in the determination (S2910: No error), the joint center ordering server 11 updates the order status with respect to the corresponding record in the progress management table 606 to “in transmission” by the order progress update function 307. (S2912) The transmission data transmission / reception function 314 sends the order transmission data to the seller order receiving server 15 (S2913). At this time, the joint center ordering server 11 uses the order progress update function 307 to update the order status in the corresponding record of the progress management table 606 from “order transmitting” to “order transmitted”, and uses the transmission history information registration function 319. The transmission history information is stored in the order transmission history management table 610 of the joint center database server 14 (S2914, S2915).

  On the other hand, the seller order receiving server 15 receives the order transmission data transmitted from the joint center ordering server 11 by the transmission data transmission / reception function 709 (S2916). Further, the order information is stored in the order data management database 711 by the transmission data fetch function 710 (S2917). About the process by this transmission data taking-in function 710, the execution timing may differ by the seller order receiving server 15. FIG.

  The seller user confirms the order information stored in the order data management database 711 from the display unit 802 of the seller order approval terminal 16. At this time, the seller order approval terminal 16 accepts the order approval from the seller user by the order approval function 807, and sets the date and time information at the time of approval to the approval date and time in the corresponding record of the order management database 711, for example (S2918). . Further, the seller order receiving server 15 selects the data whose order is approved by the seller user in the order data management database 711 by the transmission data generation function 708, for example, a record in which date / time information is set in the approval date / time column. The order confirmation data (which may be in the existing format) is generated (S2920). Further, the seller order receiving server 15 transmits the order confirmation data to the joint center ordering server 11 by the transmission data transmission / reception function 709 (S2921).

  On the other hand, the joint center ordering server 11 receives the order confirmation data by the transmission data transmission / reception function 314 (S2921), and stores it in the order confirmation information table 605 by the order confirmation registration function 315 (S2922). Further, the joint center ordering server 11 updates the order status from “order transmitted” to “order confirmed” in the corresponding record of the progress management table 606 by the order progress update function 307 (S2923).

--- Example of processing procedure (counting and billing) ---
It can be said that the system 100 provides a data check (value and layout) service related to an order while using the seller-side system 200. In providing this service, it is possible to assume a business form in which a service usage fee is collected from the buyer side. Therefore, the calculation of such service usage fees will be described below.

  FIG. 30 is a flowchart showing usage charge calculation processing of the data check service. In this case, first, the joint center schedule server 12 instructs the joint center billing and summing server 13 to start counting using a counting schedule function 405 (S3001).

  At this time, the joint center billing aggregation server 13 performs, for example, four aggregation processes in accordance with the aggregation start instruction from the collaboration center schedule server 12. Here, as a first aggregation process, the joint center billing aggregation server 13 performs an aggregation process of the number of registered order information by company (searched by company ID 903) in the order information table 604 by the order execution number aggregation function 504. The totaling result is stored in the order contract totaling table 611 (S3002).

  Next, as a second tabulation process, the joint center billing tabulation server 13 uses the number of used users / use time tabulation function 505 from the ordering server login history management table 608 to search for the use time (search by company ID 1303) for each company ( The login total time 1305) and the login count (authentication count 1307) are aggregated, and the aggregated result is stored in the ordering server login aggregation table 612 (S3003).

  As a third tabulation process, the joint center billing tabulation server 13 uses the data check usage count totaling function 506 to check the number of data checks (check count 1407) for each company (search by company ID 1404) from the data check usage history management table 609. And the totaled result is stored in the data check utilization totaling table 612 (S3004).

  As the fourth tabulation process, the joint center billing tabulation server 13 uses the order transmission size / count counting function 507 to transfer the transmission size (order size 1504) for each company (search by company ID 1502) from the order transmission history management table 610. And the number of times (number of records) are stored, and the result is stored in the order transmission amount totaling table 614 (S3005).

  Subsequently, the joint center billing totaling server 13 calculates a service charge charged to the buyer user (company) by the order data check service charge charge calculation function 508 (S3006). Specifically, the fee calculation is performed by adding the weight of the fee based on the various information collected in steps S3002 to S3005 and the charging apportionment master 617. For example, when the apportionment breakdown is “60%” for the number of checks, “10%” for the login, “10%” for the transmission amount, “10%” for the transmission amount, and “10%” for the number of orders, the above step For example, a service charge is calculated by multiplying each count result by S3002 to S3005 by a predetermined unit price and a corresponding prorated value (60% or 10%). The charge calculation result obtained in this way is stored in the charge billing table 615 by the order data check service billing charge calculation function 508 of the joint center billing aggregation server 13.

  Further, the joint center billing aggregation server 13 creates a bill for using the data check service for billing the buyer user (company) by using the order data check service bill generation function 509 (S3007). The usage bill is created by setting the monetary value obtained in step S3006 in a predetermined format (previously stored in the storage unit). Note that the total amount charged may be apportioned by the number of sellers (manufacturers) that provide the check program, and payment may be made to the seller as a usage fee.

  As described above, according to the present embodiment, transmission data in EDI transmission can be processed efficiently and at low cost on the receiving side, and the time lag of business processing due to correction or retransmission of transmission data can be reduced.

  As mentioned above, although embodiment of this invention was described concretely based on the embodiment, it is not limited to this and can be variously changed in the range which does not deviate from the summary.

1 Inter-company EDI transmission system 10 Buyer side terminal 11 Joint center ordering server 12 Joint center schedule server 13 Joint center billing totaling server 14 Joint center database server 15 Seller order receiving server 16 Seller order acceptance terminal 140 Network 100 EDI data management system 200 Seller side system

Claims (6)

A computer system for managing transmission data of an EDI system related to merchandise sales,
Storage means for storing addresses on the network of the seller side system used by the buyer side terminal;
Means for receiving the order information of the product from the buyer side terminal via the network, and searching the address of the seller side system in the storage means based on the information included in the order information;
The check data including the order information received from the buyer side terminal is transmitted to the searched seller side system address together with the check request, and the check data by the data check program held by the seller side system is related to the check data Means for receiving data check results from the seller's system;
If the database check result is not a problem, means for transmitting the order transmission data including the corresponding order information to the corresponding seller side system;
An EDI data management system comprising: If the data check result received from the seller's system indicates the check result regarding the input contents such as the number of digits of each item value included in the order information, the character type, and the presence / absence of mandatory relationships between items, the corresponding data check result is Means for transmitting to the buyer's terminal;
When the data check result received from the seller-side system indicates a check result related to the layout of the check data generated from the order information, a means for outputting the corresponding data check result to an output means;
The EDI data management system according to claim 1, further comprising: Each time a data check result is received from the seller-side system, the number of times of use of the data check program of the relevant seller for the relevant buyer is counted, and a means for storing the value of the number of uses in the storage means;
Means for calculating a service usage fee by calculating a predetermined value for the number of times of use in the storage means, applying the service usage fee to a predetermined format to generate a bill and transmitting it to the buyer side terminal;
Means for executing the process of counting and storing the number of times of use and the process of calculating the service usage fee, generating bills, and transmitting each predetermined period based on a schedule stored in advance in storage means;
The EDI data management system according to claim 1, further comprising: Means for counting the time and number of times that the buyer side has logged in to the EDI data management system during log-in and log-off processing and storing it in the storage means, and summing up the system usage time and the number of times of use for each buyer;
The transmission size and the number of transmissions of various data transmitted from the buyer side terminal to the seller side system via the EDI data management system are stored in the storage means, and the data transmission amount and the number of times for the relevant buyer are collected. And further comprising means
The means for calculating the service usage fee, generating a bill, and sending the usage number value in the storage means, the usage time of the system for each buyer, the total number of usage times, and data transmission to the relevant seller regarding the buyer Calculate a service usage fee by calculating a predetermined value for at least one of the total amount and the number of times, apply the service usage fee to a predetermined format, generate an invoice, and send it to the buyer's terminal.
The EDI data management system according to claim 3. A computer system comprising storage means for storing addresses on a network of a seller side system used by a buyer side terminal, and managing transmission data of an EDI system related to merchandise sales;
Processing for receiving product order information from the buyer side terminal via the network and searching for the address of the seller side system in the storage means based on information included in the order information;
The check data including the order information received from the buyer side terminal is transmitted to the searched seller side system address together with the check request, and the check data by the data check program held by the seller side system is related to the check data Receiving data check results from the seller's system;
If the database check result is satisfactory, the EDI data management method is characterized in that: processing for transmitting order transmission data including the relevant order information to the relevant seller side system is executed. A computer system comprising storage means for storing addresses on the network of the seller side system used by the buyer side terminal, and managing transmission data of the EDI system related to merchandise sales.
Processing for receiving product order information from the buyer side terminal via the network and searching for the address of the seller side system in the storage means based on information included in the order information;
The check data including the order information received from the buyer side terminal is transmitted to the searched seller side system address together with the check request, and the check data by the data check program held by the seller side system is related to the check data Receiving data check results from the seller's system;
If the database check result is not a problem, processing for transmitting order transmission data including the corresponding order information to the corresponding seller side system,
An EDI data management program that is executed.

Images