JP6557987B2 - Output control program, output control method, and output control apparatus - Google Patents

Description

  The present invention relates to an output control program, an output control method, and an output control apparatus.

  As a system for realizing electronic commerce, a system using Web-electronic Data Interchange (WebEDI) is used. As a related technique, a technique related to a data management system using EDI has been proposed (see, for example, Patent Document 1).

  In the technique of Patent Document 1, a column management table that preliminarily specifies and statically stores a data item name of a record to be managed and a column ID that uniquely indicates the data item name, and a row ID that uniquely indicates the record And a row management table for storing. The technique of Patent Document 1 includes a value management table that is dynamically created by combining a column management table and a row management table.

JP 2007-213551 A

  A screen provided by WebEDI is displayed on the terminal operated by the supplier. Based on this screen, the supplier operates the terminal and performs a transaction with the buyer. The screen provided by WebEDI differs depending on the buyer.

  When a supplier performs transactions with a plurality of buyers, the supplier operates the terminal to switch the screen for each buyer. Therefore, since the supplier needs to perform this switching operation, convenience when the supplier uses WebEDI is lowered.

  Further, when information related to transactions of a plurality of buyers is collectively displayed on one screen, many items are displayed on the screen if items of information used in the transaction differ depending on the buyers. For this reason, the visibility and operability of the screen are lowered, and convenience when the supplier uses WebEDI is lowered.

  As one aspect, an object of the present invention is to improve convenience when using a system for realizing electronic commerce.

In one aspect, the output control program is definition information corresponding to each of the plurality of business partners in an application used for business transactions with a plurality of business partners, and is included in the data related to the business transactions. The process of obtaining the definition information , which is information defining the item name and order for each of the items used in the commercial transaction, the definition of the item name and the order in the definition information is the same for all the items A process for collecting and outputting output information relating to a business partner to be executed.

  According to one aspect, convenience when using a system for realizing electronic commerce can be improved.

It is a figure which shows an example of a system. It is a functional block diagram which shows an example of an EDI server. It is a functional block diagram which shows an example of a supplier terminal. It is FIG. (1) which shows an example of various tables. It is FIG. (2) which shows an example of various tables. It is a figure explaining an example of aggregation of transaction information. It is a figure explaining an example of the call of a specific function. It is a screen example (the 1) which shows an example of a supplier selection screen. It is a screen example (the 1) which shows an example of a transaction list screen. It is a screen example (the 2) which shows an example of a supplier selection screen. It is a screen example (the 2) which shows an example of a transaction list screen. It is a screen example which shows the other example of a transaction list screen. It is a figure (the 1) which shows an example of the printed order form. It is FIG. (2) which shows an example of the printed order form. It is a flowchart which shows an example of a data storage process. It is a flowchart which shows an example of an information output process. It is a flowchart which shows an example of a determination process. It is a flowchart which shows an example of a function execution process. It is a figure which shows an example of the hardware constitutions of an EDI server. It is a figure which shows an example of the hardware constitutions of a supplier terminal.

<Example of system using WebEDI>
Hereinafter, embodiments will be described with reference to the drawings. In the embodiment, an example in which a WebEDI system is applied as a system for realizing electronic commerce will be described. However, the system for realizing electronic commerce is not limited to WebEDI.

  In the embodiment, it is assumed that electronic commerce using WebEDI (hereinafter also simply referred to as transaction) is a purchase operation. However, transactions are not limited to purchasing operations. Transactions take place between buyers and suppliers.

  A supplier is a supplier that supplies a target for a transaction. The buyer is the purchaser who purchases the object of the transaction. From the perspective of the supplier, the buyer becomes the supplier's business partner. Hereinafter, a buyer may be referred to as a supplier and a supplier as a business partner.

  FIG. 1 shows an example of a system 1 to which WebEDI is applied. In the system 1, the buyer terminals 2 </ b> A to 2 </ b> C (hereinafter sometimes collectively referred to as the buyer terminal 2) and the EDI server 3 are connected by a first network 5. The first network 5 may be an Internet network, for example.

  The EDI server 3 and the supplier terminals 4 </ b> A to 4 </ b> C (hereinafter collectively referred to as supplier terminal 4) are connected by the second network 6. The second network 6 may be an internet network, for example. The first network 5 and the second network 6 may be the same network.

  The buyer terminal 2 is a terminal used when a buyer makes a transaction. The number of buyer terminals 2 is not limited to three. In the embodiment, the description will be made assuming that the buyer terminal 2 corresponds to one company, but one company may correspond to a plurality of buyer terminals 2.

  The EDI server 3 is a computer that implements WebEDI. The EDI server 3 executes an application that realizes the WebEDI function. By executing this application, electronic commerce using WebEDI is performed between the buyer terminal 2 and the supplier terminal 4.

  The supplier terminal 4 is a terminal used when the supplier conducts a transaction. The number of supplier terminals 4 is not limited to three. The embodiment will be described assuming that the supplier terminal 4 corresponds to one company, but one company may correspond to a plurality of supplier terminals 4.

<Example of EDI server>
Next, an example of the EDI server 3 will be described with reference to FIG. The EDI server 3 is a computer that includes a first control unit 11, a first communication unit 12, an application storage unit 13, a function storage unit 14, and a database 15. The EDI server 3 is an example of an output control device.

  The first control unit 11 performs various processes of the EDI server 3. The first communication unit 12 communicates with the first network 5 and the second network 6. The application storage unit 13 stores an application that realizes the function of the EDI server 3.

  The first control unit 11 executes an application stored in the application storage unit 13. An output control program for realizing the processing of the embodiment is included in the application.

  The function storage unit 14 stores various functions defined by the application. The function storage unit 14 stores a common function 21 common to each buyer and unique functions 22A to 22C unique to each buyer. Hereinafter, the unique functions 22A to 22C may be collectively referred to as the unique function 22.

  Examples of the common function 21 include functions such as screen calling and form creation. These functions are common to each buyer terminal 2. The common function 21 is an example of a first function. The common function 21 is realized by predetermined information. For example, the common function 21 is represented by source code. The common function 21 is an example of first control information.

  The unique function 22 is predetermined information defined for each buyer. The unique function 22 is an example of a second function. For example, the unique function 22 is represented by source code. The unique function 22 is an example of second control information.

  For example, when the transaction is an order, the order changing method may differ depending on the buyer. In addition, when the transaction is shipment, the shipping method may differ depending on the buyer. Further, when creating a form, the form form may differ depending on the buyer.

  It is assumed that the common function 21 calls the unique function 22 when the first control unit 11 is executing the common function 21 defined in the application. The first control unit 11 executes the called unique function 22.

  For example, when the first control unit 11 is executing a form creation function as the common function 21, the common function 21 calls the unique function 22. Since the first control unit 11 recognizes the information of the buyer who is processing the transaction, the first control unit 11 calls the specific function 22 in the form format corresponding to the buyer. As a result, a form in a form corresponding to the buyer who is processing the transaction is created.

  Therefore, when the first control unit 11 executes the unique function 22, different controls can be performed for each buyer.

  In the embodiment, it is assumed that the source code of the common function 21 and the source code of each unique function 22 for each buyer are separated. That is, in the embodiment, the source code of the common function 21 and the source code of each unique function 22 are stored in different storage areas of the function storage unit 14.

  For this reason, since the common function 21 and each unique function 22 are developed as separate source codes, the maintainability of development is improved.

  Next, the database 15 will be described. The database 15 stores various tables. The database 15 stores a purchase data table 31, a format table 32, a transaction record table 33, a definition information table 34, and a definition information identification table 35.

  The purchase data table 31 stores each purchase data that the EDI server 3 receives from the buyer terminal 2. The purchase data is data relating to a transaction that the buyer terminal 2 transmits to the EDI server 3.

  The format table 32 stores information specifying the unique function 22 for each buyer. In the embodiment, the format table 32 stores the name of the unique function 22 specified by the buyer and the transaction type.

  The transaction record table 33 stores information on buyers who have transaction records for each supplier. The EDI server 3 recognizes transactions that take place between the supplier and the buyer. For example, when the EDI server 3 recognizes that a new transaction has occurred between the supplier and the buyer, the first control unit 11 updates the contents of the transaction record table 33.

  The definition information table 34 stores definition information for each buyer. The definition information is information defining items used for the transaction. The definition information is also referred to as a data layout. Purchase data is based on definition information.

  The definition information identification table 35 stores a correspondence relationship between buyers, definition information, and IDs. ID is an abbreviation for Identification. The correspondence relationship of the definition information identification table 35 is stored in the database 15 in advance.

<Example of supplier terminal>
Next, an example of the supplier terminal 4 will be described with reference to FIG. The supplier terminal 4 includes a second control unit 41, a second communication unit 42, a screen control unit 43, a screen unit 44, an operation recognition unit 45, and a print control unit 46.

  The second control unit 41 performs overall control of the supplier terminal 4. The second communication unit 42 communicates with the EDI server 3 via the second network 6. The screen control unit 43 controls the screen displayed on the screen unit 44.

  The operation recognition unit 45 is connected to the operation device 220. The operation device 220 is, for example, a mouse or a keyboard. The operation recognition unit 45 receives an operation by the operation device 220. In the embodiment, it is assumed that the operation device 220 is a mouse.

  The print control unit 46 is connected to the print device 221. The printing device 221 is, for example, a printer. For example, when the operation recognition unit 45 receives an operation for printing a form, the print control unit 46 controls the printer to print the form.

<Examples of various tables>
Next, examples of various tables will be described with reference to FIGS. 4 and 5. FIG. 4 shows an example of the purchase data table 31, the format table 32, and the transaction performance table 33.

  The buyer operates the buyer terminal 2 and inputs information for performing a transaction using WebEDI. The buyer terminal 2 receives the input information. The buyer terminal 2 stores the definition information described above, and generates purchase data according to the definition information. The buyer terminal 2 outputs purchase data to the EDI server 3 via the first network 5.

  The first communication unit 12 of the EDI server 3 inputs purchase data. The first control unit 11 stores purchase data in the purchase data table 31 of the database 15. The first control unit 11 sequentially stores the input purchase data in the purchase data table 31 each time purchase data is input from each buyer terminal 2.

  FIG. 4 shows an example in which the purchase data table 31 stores purchase data input from the buyer terminals 2A, 2B, and 2C. For example, the purchase data output by the buyer terminal 2A and the buyer terminal 2B includes items of a sender, a receiver, an order number, an order quantity, and a unit price. This purchase data includes other items.

  The purchase data of the buyer terminal 2C has items of From, To, order number, delivery date, and purchaser. This purchase data includes other items. Of the purchase data of the buyer terminal 2C, From corresponds to the sender, To corresponds to the receiver, and the order number corresponds to the order number.

  Accordingly, the purchase data of the buyer terminal 2A and the purchase data of the buyer terminal 2B all match. On the other hand, the purchase data of the buyer terminals 2A and 2B and the purchase data of the buyer terminal 2C are different in terms of delivery date and purchase charge.

  Purchase data is based on definition information for each buyer. Accordingly, the definition information stored in the buyer terminal 2A and the definition information of the buyer terminal 2B all match. On the other hand, the definition information stored in the buyer terminal 2C is different from the definition information stored in the buyer terminals 2A and 2B.

  Next, the format table 32 will be described. The format table 32 has items of buyer, transaction type, and unique logic class name. The item of buyer indicates the name of the buyer.

  The transaction type indicates the type of transaction. Examples of transaction types include orders, shipments, and delivery date responses. The unique logic class name indicates the name of the unique function 22. Therefore, the unique function 22 is specified by the buyer and transaction type of the format table 32.

  Note that the format table 32 may not have an item of transaction type. In this case, the unique function 22 is specified by the buyer. The unique logic class name of the format table 32 may be other information as long as the unique function 22 can be specified. For example, the unique logic class name may be an identifier for identifying the unique function 22.

  Next, the transaction performance table 33 will be described. The transaction record table 33 stores information on buyers with transaction records for each supplier. When the EDI server 3 recognizes that a new transaction has occurred between the supplier and the buyer, the first control unit 11 stores the correspondence relationship of the new transaction in the transaction record table 33.

  Next, the definition information table 24 will be described with reference to FIG. The definition information table 24 stores definition information items for each buyer. Definition information for each buyer is stored in advance in the definition information table 24.

  For example, when the definition information is standardized, a plurality of buyers use the standardized definition information. In this case, among the definition information for each buyer stored in the definition information table 24, a plurality of definition information in which all items match may be stored in the definition information table 24.

  In the embodiment, it is assumed that buyer A and buyer B use standardized definition information. For this reason, the definition information of buyer A and the definition information of buyer B all match. On the other hand, it is assumed that buyer C uses unique definition information. In this case, the definition information of buyer C does not match the items of definition information of buyer A and buyer B.

  Next, the definition information identification table will be described. The definition information identification table has items of buyer, definition information name, and ID. The ID specifies the buyer and the definition information name. In the example of FIG. 5, the definition information name includes “standard order”. This indicates standardized definition information whose transaction type is “order”.

  “Standard shipment” indicates standardized definition information whose transaction type is “shipment”. Therefore, standardized definition information may differ depending on the transaction type. For this reason, the buyer A and the buyer B are assigned different IDs for the standardized definition information of “order” and the definition information of “shipment”.

<Example of aggregation of transaction information>
Next, an example of aggregation of transaction information will be described with reference to FIG. The transaction information is information related to the transaction that the EDI server 3 outputs to the supplier terminal 4 based on the purchase data. This transaction information is an example of output information.

  The first control unit 11 of the EDI server 3 identifies a buyer and a supplier based on purchase data, and generates transaction information to be output to the supplier terminal 4. The supplier terminal 4 displays the transaction information on the display unit 44 by inputting the transaction information. Thereby, the supplier recognizes the transaction from the buyer.

  FIG. 6A shows a first example of aggregation of transaction information. The first control unit 11 refers to the definition information table and identifies a buyer who uses definition information that matches all items. For example, buyer A and buyer B use definition information whose items all match. Accordingly, the first control unit 11 collects transaction information between the buyer A and the buyer B. On the other hand, the buyer C includes items for delivery date and purchasing staff in the definition information.

  These two items are items that are not included in the definition information of buyer A and buyer B. Therefore, the 1st control part 11 does not collect the transaction information of buyer C. If there is definition information of another buyer who matches all items of definition information of buyer C, the first control unit 11 aggregates the transaction information of buyer C and the transaction information of the other buyer.

  FIG. 6B shows a second example of aggregation of transaction information. In the second example, the definition information of buyer A and buyer B matches the definition information of buyer D in all items. However, the order of items of the definition information is different between the buyer A, the buyer B, and the buyer D. Hereinafter, the order of items may be simply referred to as an order.

  In the example of FIG. 6B, the order of “unit price” and “order quantity” differs between the definition information of buyer A and buyer B and the definition information of buyer D. In the embodiment, even if all items of the definition information match, if the order is different, the first control unit 11 does not aggregate the transaction information.

  This is because if the order of the definition information is different, the first control unit 11 performs a process of changing the order of the transaction information when a transaction is performed between the buyer and the supplier. For example, when the number of items of definition information increases, a lot of time is spent on the process of changing the order.

  For this reason, in the embodiment, the first control unit 11 does not aggregate the transaction information of buyers whose definition information is different in order. As a result, the processing for changing the order can be omitted. However, the first control unit 11 may aggregate buyer information for definition information having different orders. In this case, the first control unit 11 performs the above-described order changing process.

<Example of calling unique functions>
Next, an example of calling the unique function 22 will be described with reference to FIG. In the example of FIG. 7, the basic function is a basic function of an application executed by the first control unit 11. This basic function is described in, for example, source code.

  The basic function of the example of FIG. 7 includes a business logic function that indicates the flow of business logic processing. For example, the business logic indicates a flow of processing executed in a transaction. The business logic function is assumed to be the source code of the common function 21 described above. In addition, the business logic function includes an instruction for calling the unique logic.

  The specific logic is assumed to be the source code of the specific function 22 described above. When the first control unit 11 calls the unique logic, the specific logic to be called is specified with reference to the format table 32.

  For example, it is assumed that the first control unit 11 is processing purchase data related to an order transaction of buyer A. The first control unit 11 recognizes the buyer and the transaction type based on the purchase data. Thereby, the first control unit 11 recognizes the unique logic class name “Class.A.logic” and calls the buyer A unique function 22A.

  As described above, the unique function 22 is a source code. Accordingly, the first control unit 11 calls the source code of the buyer A specific function 22 in the function storage unit 14 and executes processing of the source code.

<Example of various screen examples>
Next, various screen examples will be described. The screen example described below is an example of a screen displayed on the supplier terminal 4A. The supplier A operates the supplier terminal 4 </ b> A so that the supplier terminal 4 </ b> A accesses the EDI server 3. Thereby, a transaction using the EDI server 3 is performed. The same applies to the suppliers 4B and 4C.

  The supplier terminal 4 </ b> A receives the operation of the supplier A and transmits information related to the received operation to the EDI server 3. The EDI server 3 performs a predetermined process based on the input information and outputs the predetermined information to the supplier terminal 4A. Then, the supplier terminal 4 </ b> A displays predetermined information on the screen unit 44.

  In WebEDI, a browser is displayed on the screen 44 of the supplier terminal 4A, and various information provided by the EDI server 3 is displayed in the browser. Various information provided by the EDI server 3 may be displayed on the screen unit 44 of the supplier terminal 4A by a method other than the browser.

  In the embodiment, when the supplier operates the supplier terminal 4A to use the service of the EDI server 3, the EDI server 3 requests the supplier terminal 4A for an ID, a password, and the like.

The supplier terminal 4A outputs the input ID, password, and the like to the EDI server 3.
When the EDI server 3 authenticates the ID, password, and the like and the authentication is successful, the supplier terminal 4A logs into the EDI server 3.

  The first control unit 11 of the EDI server 3 acquires information on a buyer who has a transaction record with the supplier A corresponding to the logged-in supplier terminal 4 </ b> A from the transaction record table 33. As described above, the buyers corresponding to the supplier A in the transaction record table 33 are the buyers A to C.

  The first control unit 11 performs control to output information on the buyers A to C to the supplier terminal 4A. For example, the 1st control part 11 performs control which outputs the information regarding each transaction classification of buyer AC to supplier terminal 4A. The first communication unit 12 outputs the information to the supplier terminal 4A. The supplier terminal 4A inputs the information.

  The screen shown in FIG. 8 is an example of a screen on which a supplier selects a buyer (hereinafter, also referred to as a supplier selection screen). The transaction selection screen is a screen that the EDI server 3 provides to the supplier terminal 4. A supplier selection screen is displayed on the screen 44 of the supplier terminal 4A. In the supplier selection screen, a display area is divided for each buyer.

  However, the screen control unit 43 performs control to display the buyers for which the transaction information is collected in the same display area of the supplier selection screen. As described above, the EDI server 3 aggregates the transaction information of the buyer A and the transaction information of the buyer B and outputs them to the supplier terminal 4A.

  For this reason, as shown in the example of FIG. 8, the screen control unit 43 aggregates and displays the buyer A and the buyer B in the same display area on the supplier selection screen. Thereby, the supplier can recognize that the transaction information of buyer A and the transaction information of buyer B are aggregated based on the supplier selection screen.

  The transaction type in each display area of the supplier selection screen can be selected. For example, the operation recognition unit 45 of the supplier terminal 4A recognizes a mouse operation. The example of FIG. 8 shows a state where the mouse pointer P of the mouse selects “Order” of the buyer A.

  The second control unit 41 receives an operation of selecting “order” of the buyer A. The second communication unit 42 outputs, to the EDI server 3, a request for acquiring transaction information for orders from the buyer A to the supplier A.

  The first control unit 11 of the EDI server 3 identifies the supplier A and the buyer A based on the input request. The first control unit 11 refers to the definition information table 34 to determine whether there is a supplier that uses definition information whose items and order all match those of the buyer A.

  As described above, items and order of definition information of buyer A and buyer B all match. The first control unit 11 aggregates transaction information of buyer A and transaction information of buyer B. The 1st control part 11 performs control which outputs the collected transaction information of buyer A, and the transaction information of buyer B to supplier terminal 4A.

  The first communication unit 12 outputs the aggregated transaction information of the buyer A and the buyer B to the supplier terminal 4A via the second network 6. The second communication unit 42 of the supplier terminal 4A inputs transaction information.

  FIG. 9 is an example of a screen (hereinafter referred to as a transaction list screen) based on output information input by the second communication unit 42 of the supplier terminal 4A. As described above, the supplier terminal 4A accepts an operation of selecting “order”. Therefore, the screen example of FIG. 9 is a list screen regarding orders. The transaction list screen is an example of a specific output screen.

  The example of the transaction list screen in FIG. 9 includes items of number, information type, orderer name, order number, order quantity, and unit price. The transaction list screen shows the input transaction information. The transaction information includes information regarding a plurality of transactions. The second control unit 41 assigns a number to each transaction.

  The information type indicates the type of data transmitted by the company. Based on the information type, the operation recognition unit 45 can change the operation. For example, in the example of FIG. 9, confirmation, change, and cancellation are included as information types. However, the information types are not limited to the above three.

  For example, when the first control unit 11 receives an operation for selecting confirmation in the first transaction, the first transaction is confirmed. Moreover, when the 1st control part 11 receives operation which selects a change by 4th transaction, the content of the 4th transaction is changed. Moreover, when the 1st control part 11 receives operation which selects cancellation with the 5th transaction, the content of the 5th transaction is canceled.

  The transaction list screen includes a check box CK corresponding to each transaction. The first control unit 11 receives an operation for checking the check box CK. In the case of the example in FIG. 9, the check boxes CK for the first, fourth, and fifth transactions are checked.

  The transaction list screen includes a confirmation button 44A and a form creation button 44B. When the first control unit 11 receives an operation of pressing the confirmation button 44 </ b> A, the screen control unit 43 displays a screen for confirming the content of the transaction for which the check box CK is checked on the screen unit 44.

  When the first control unit 11 receives an operation of pressing the form creation button 44B, the first control unit 11 creates a form of a transaction in which the check box CK is checked. The screen control unit 43 may display the created form image on the screen unit 44. In addition, when the first control unit 11 receives an operation to print, the print control unit 46 may control the printing device 221 so that the created form is printed.

  The second communication unit 42 of the supplier terminal 4A inputs transaction information in which the transaction information of the buyer A and the transaction information of the buyer B are aggregated. Therefore, as shown in the screen example of FIG. 9, the transaction list screen includes information on both transaction information from buyer A and transaction information from buyer B. FIG. 9 shows an example in which transaction information related to ordering is displayed on the screen unit 44.

  Accordingly, on one transaction list screen, the supplier A can browse the information related to the order from the buyer A and the information related to the order from the buyer B together. This is because the EDI server 3 aggregates and outputs the transaction information of buyers whose definition information items and orders all match.

  For example, when the first control unit 11 of the EDI server 3 does not collect buyer transaction information, the first communication unit 12 individually outputs the transaction information of each buyer to the supplier terminal 4. Therefore, a transaction list screen for each buyer is displayed on the screen unit 44 of the supplier terminal 4.

  For example, when the transaction list screen is displayed from the supplier selection screen, the EDI server 3 may request a login operation. In this case, in order to perform a login operation, the supplier inputs an ID, a password, and the like to the supplier terminal 4.

  Then, the supplier terminal 4 outputs the received ID, password, etc. to the EDI server 3 and authenticates with the EDI server 3. The EDI server 3 outputs transaction information for displaying a transaction list screen to the supplier terminal 4 when the authentication is successful.

  For example, when the transaction list screen of the buyer A is displayed on the screen unit 44 of the supplier terminal 4A and the transaction list screen of the buyer B is displayed on the screen unit 44, a switching operation of the transaction list screen is requested to the supplier A. Is done.

  For this reason, supplier A performs a logout operation from the transaction list screen of buyer A, and performs a login operation again from the supplier selection screen. Therefore, in order to display a transaction list screen of different buyers, a login operation and a logout operation are requested for the buyer terminal 4A. These operations are requested every time a transaction list screen switching operation is performed.

  For this reason, the convenience when a supplier uses the service which the EDI server 3 provides falls. Even when the login operation and the logout operation are not requested, when the transaction list screen is an individual screen for each buyer, the supplier terminal 4 requests the supplier to perform a screen switching operation.

  Therefore, convenience when the supplier uses the service provided by the EDI server 3 is lowered. On the other hand, in the embodiment, since the EDI server 3 aggregates transaction information of buyers whose definition information items and order are all the same, the aggregated buyer transactions are displayed on the screen unit 44 of the supplier terminal 4. Information is displayed at once.

  This eliminates the need to switch the transaction list screen for a plurality of buyers displayed on the transaction list screen. For this reason, the convenience when a supplier uses the service which the EDI server 3 provides improves.

  Next, with reference to FIG. 10, a case where “Order” of buyer C is selected on the supplier selection screen will be described. The second control unit 41 receives this selection operation, and the second communication unit 42 outputs a request for acquiring the transaction content ordered by the buyer C from the supplier A to the EDI server 3.

  The definition information table 34 does not store definition information of other buyers whose items and order all match the definition information of the buyer C. Accordingly, the first control unit 11 of the EDI server 3 does not aggregate the transaction information of the buyer C with the transaction information of other buyers, and outputs the transaction information of the buyer C to the supplier terminal 4A individually.

  FIG. 11 shows an example of a transaction list screen of buyer C. The first control unit 11 of the EDI server 3 does not aggregate the transaction information of buyer C with the transaction information of other buyers. For this reason, the orderer name on the transaction list screen is all buyer C. Accordingly, the screen example of FIG. 11 is a screen displaying transaction information specialized for the buyer C.

  Here, it is also conceivable that the first control unit 11 of the EDI server 3 aggregates and outputs information on a plurality of buyers to the supplier terminal 4 regardless of whether the items of the definition information are the same. FIG. 12 shows an example.

  The transaction list screen of FIG. 12 displays all of buyer A, buyer B, and buyer C all at once. In this case, the number of items displayed on the transaction list screen increases. For example, the definition information of buyer C does not include items of order quantity and unit price.

  Accordingly, no information is displayed in the order quantity and unit price fields of buyer C on the transaction list screen. Similarly, the definition information of buyer A and buyer B does not include items for delivery date and purchasing personnel. Therefore, in the transaction list screen displayed on the screen unit 44, no information is displayed in the delivery date and purchase person fields of buyer A and buyer B.

  As the number of items in the definition information increases, the number of items that do not match in the definition information for each buyer increases. For this reason, regardless of whether or not the definition information is the same, when multiple buyer information is collectively displayed on the transaction list screen of the screen unit 44, the number of items displayed increases.

  And information is no longer displayed in many fields of the transaction list screen displayed on the screen part 44, and the visibility of the supplier who operates the supplier terminal 4 falls. Further, when the number of items on the transaction list screen increases, for example, an operation of scrolling the screen is requested from the supplier. For this reason, the operability of the supplier is also lowered.

  Therefore, convenience when the supplier uses the service provided by the EDI server 3 is lowered. In the embodiment, the first control unit 11 of the EDI server 3 does not aggregate buyer transaction information of definition information having different items and order, and outputs the buyer transaction information to the supplier terminal 4 individually.

  Thereby, the number of items on the transaction list screen is minimized. Therefore, since the visibility and operability of the supplier are suppressed from decreasing, the convenience when the supplier uses the service provided by the EDI server 3 is improved.

<Example of printed matter>
FIG. 13 shows an example of an order form printed by the printing device 221 under the control of the print control unit 46. A purchase order is an example of a form. When the supplier terminal 4 receives an operation for printing an order form for the selected transaction, the print control unit 46 controls the printing device 221 to print the order form. Further, as shown in FIG. 14, the print control unit 46 may output a form having different definition information for each buyer, according to the buyer's unique logic.

<Examples of various processes>
Next, the data storage process will be described with reference to FIG. Each buyer terminal 2 receives a buyer's operation, generates purchase data, and outputs the purchase data via the first network 5.

  The first communication unit 12 of the EDI server 3 inputs the purchase data output from the buyer terminal 2 (step S1). The first control unit 11 stores the input purchase data in the purchase data table 31 (step S2).

  Next, the information output process will be described with reference to FIG. As described above, the supplier terminal 4 accepts the supplier's operation and logs in to the EDI server 3. The first control unit 11 recognizes the supplier based on the logged-in supplier terminal 4 (step S11).

  The 1st control part 11 recognizes the recognized supplier and the buyer with a transaction performance with reference to the transaction performance table 33 (step S12). The first control unit 11 refers to the definition information table 34 and acquires the definition information of the recognized buyer (step S13).

The first control unit 11 determines whether there is a buyer using the same definition information in the acquired buyer definition information (step S14 ). The first control unit 11 may perform the determination in step S14 based on whether or not there is definition information whose items and order all match in the acquired buyer definition information.

Further, the first control unit 11 may perform the determination in step S14 based on whether or not there is a buyer having the same ID in the definition information of the recognized buyer with reference to the definition information identification table 35. .

  If it is determined that there is a buyer who uses the same definition information (YES in step S14), the first control unit 11 acquires purchase data of the buyer who uses the same definition information from the purchase data table 31. Then, the first control unit 11 generates transaction information based on the acquired purchase data, and aggregates the generated transaction information (step S15). The first communication unit 12 outputs the aggregated buyer information to the supplier terminal 4 (step S16).

  If it is determined that there is no buyer who uses the same definition information (NO in step S14), the first control unit 11 does not collect buyer information. The first control unit 11 acquires buyer purchase data from the purchase data table 31, and individually generates buyer transaction information based on the acquired purchase data (step S17). The first communication unit 12 outputs the individually acquired buyer transaction information to the supplier terminal 4 (step S18).

  The second communication unit 42 of the supplier terminal 4 inputs buyer transaction information. The screen control unit 43 performs control to display a transaction list screen on the screen unit 44 based on the input buyer transaction information.

  FIG. 17 shows an example of the determination process in step S16. This determination process is referred to as a definition information determination process. The first control unit 11 determines whether or not there is a buyer that uses definition information that matches all items in the acquired buyer definition information (step S16-1).

  If the first control unit 11 determines that there is a buyer that uses definition information that matches all items (YES in step S16-1), the first control unit 11 determines whether the order of all items matches ( Step S16-2).

  When it is determined that the order of all items is the same (YES in step S16-2), the first control unit 11 determines that there is a buyer who uses the same definition information (step S16-3).

  On the other hand, if the first control unit 11 determines that there is no buyer that uses definition information that matches all items (NO in step S16-1), the first control unit 11 determines that there is no buyer that uses the same definition information (step S16-1). S16-4). If the first control unit 11 determines that the order of all items does not match (NO in step S16-2), the process proceeds to step S16-4.

  Next, function execution processing will be described with reference to FIG. The first control unit 11 executes an application. When the first control unit 11 executes the business logic function, the common function stored in the function storage unit 14 is executed (step S31).

  When the buyer-specific function is set in the business logic function (YES in step S32), the first control unit 11 refers to the format table 32 (step S33). The first control unit 11 specifies the unique logic class name based on the buyer information and the transaction type information in the format table 32.

  Based on the identified unique logic class name, the first control unit 11 calls one of the unique functions 22 stored in the function storage unit 14 (step S34). Then, the first control unit 11 executes the source code of the called unique function 22 (Step S35).

  Therefore, the 1st control part 11 performs the specific function according to a buyer. For example, when the business logic such as change of order or shipment differs depending on the buyer, the first control unit 11 executes the source code of the specific function 22. Thereby, the EDI server 3 can perform different control depending on the buyer.

<Example of hardware configuration of EDI server>
Next, an example of the hardware configuration of the EDI server 3 will be described with reference to the example of FIG. As illustrated in the example of FIG. 19, a processor 111, a RAM 112, a ROM 113, an auxiliary storage device 114, a medium connection unit 115, and a communication interface 116 are connected to the bus 100.

  The processor 111 is an arbitrary processing circuit. The processor 111 executes a program expanded in the RAM 112. As a program to be executed, a program for performing the processing of the embodiment may be applied. The ROM 113 is a non-volatile storage device that stores programs developed in the RAM 112.

  The auxiliary storage device 114 is a storage device that stores various types of information. For example, a hard disk drive or a semiconductor memory may be applied to the auxiliary storage device 114. The medium connection unit 115 is provided so as to be connectable to the portable recording medium 118.

  As the portable recording medium 118, a portable memory or an optical disk (for example, Compact Disk (CD), Digital Versatile Disk (DVD), etc.) may be applied. A program for performing the processing of the embodiment may be recorded on the portable recording medium 118.

  The first control unit 11 of the EDI server 3 may be realized by the processor 111. The first communication unit 12 may be realized by the communication interface 116. The application storage unit 13, the function storage unit 14, and the database 15 may be realized by the RAM 112 or the auxiliary storage device 114.

  The RAM 112, the ROM 113, the auxiliary storage device 114, and the portable recording medium 118 are all examples of a tangible storage medium that can be read by a computer. These tangible storage media are not temporary media such as signal carriers.

<Example of hardware configuration of supplier terminal>
Next, an example of the hardware configuration of the supplier terminal 4 will be described with reference to the example of FIG. As illustrated in the example of FIG. 20, a processor 211, a RAM 212, a ROM 213, an auxiliary storage device 214, a medium connection unit 215, a communication interface 216, and an input / output interface 217 are connected to the bus 200.

  Each part other than the input / output interface 217 is the same as the hardware configuration of the EDI server described above. The input / output interface 217 is connected to the display 219, the operation device 220, and the printing device 221.

  The second control unit 41, the screen control unit 43, the operation recognition unit 45, and the print control unit 46 may be realized by the processor 211. The second communication unit 42 may be realized by the communication interface 216. The screen unit 44 may be realized by the display 219. The operation device 220 and the print device 221 are the operation device 220 and the print device 221 described above.

  The RAM 212, the ROM 213, the auxiliary storage device 214, and the portable recording medium 118 are all examples of a tangible storage medium that can be read by a computer. These tangible storage media are not temporary media such as signal carriers.

<Others>
The present embodiment is not limited to the above-described embodiment, and various configurations or embodiments can be taken without departing from the gist of the present embodiment.

DESCRIPTION OF SYMBOLS 1 System 2 Buyer terminal 3 EDI server 4 Supplier terminal 11 1st control part 12 1st communication part 13 Application storage part 14 Database 15 Function storage part 21 Common function 22 Specific function 31 Purchasing database 32 Format table 33 Transaction performance table 34 Definition information Table 35 Definition information identification table 111 Processor 112 RAM
113 ROM

Claims (5)

On the computer,
Item name for each of the items used for the commercial transaction, which is definition information corresponding to each of the multiple business partners in an application used for a commercial transaction with a plurality of business partners. And processing for obtaining the definition information , which is information defining the order and
A process of collecting and outputting output information related to suppliers whose definitions of the item names and the order in the definition information match for all the items ;
An output control program characterized by causing In the computer,
Storage that stores first control information for controlling a first function common to the plurality of business partners and second control information for controlling a second function specific to each of the business partners in different storage areas A process for performing different control for each of the suppliers with reference to the second control information in the unit,
The output control program according to claim 1, wherein: In the computer,
When the second control information is set in the first control information, the first control information reads the second control information from the storage unit, and performs a different control for each supplier.
The output control program according to claim 2, wherein: Computer
Item name for each of the items used for the commercial transaction, which is definition information corresponding to each of the multiple business partners in an application used for a commercial transaction with a plurality of business partners. And processing for obtaining the definition information , which is information defining the order and
A process of collecting and outputting output information related to suppliers whose definitions of the item names and the order in the definition information match for all the items ;
The output control method characterized by performing. Item name for each of the items used for the commercial transaction, which is definition information corresponding to each of the multiple business partners in an application used for a commercial transaction with a plurality of business partners. The definition information that is information defining the order and the order is acquired, and the output information on the business partners in which the definitions of the item name and the order in the definition information match for all the items are collected and output. Control unit to perform,
An output control device comprising:

Images