Management device, electronic commerce system, management method, and management program

Abstract

To allow many users of an e-commerce transaction system to easily and accurately handle data in accordance with a right of each user.SOLUTION: A communication control unit controls a communication unit so as to mediate transmitting / receiving various kinds of data between terminal devices of clients which conduct e-commerce transactions over a network. A user type determination unit determines whether a log-in user is a user of a management company of an e-commerce transaction system or a user of a client which uses the e-commerce transaction system. A display screen generation unit generates, when a result of the determination indicates that the log-in user is a user of a client, a display screen including unique information of the client which is used as a search key for searching a storage unit for information related to the client, the unique information being an unmodifiable fixed value, and generates, when the log-in user is a user of the management company, a display screen including unique information of the client to be used as a search key for searching the storage unit for information related to the client, the unique information being input by the user of the management company and being a modifiable variable value.SELECTED DRAWING: Figure 30

Description

Technical Field

[0001] The present invention relates to a management device, an e-commerce system, a management method, and a management program.

Background Art

[0002] Today, a WebEDI system (EDI: Electronic Data Interchange) is known in which an e-commerce system is constructed on a server device on the Web (World Wide Web), and each trading partner conducts e-commerce by transmitting and receiving data via a web browser of a terminal device.

[0003] As background art related to such a WebEDI system, Patent Document 1 (Japanese Patent Application Laid-Open No. 2003-091658) discloses an e-commerce system aimed at efficiently realizing transactions between a buyer and a seller.

[0004] In this e-commerce system, one trading entity is made to establish a trading place as an owner, and participation of a plurality of trading entities in the trading place is permitted in accordance with the requirements of the owner. In this trading place, setting of a group for trading a specific product or a group composed of specific trading entities is accepted, and an environment is formed in which only members within the group conduct transactions in accordance with the purpose of setting the group.

[0005] Thereby, trading entities can freely establish places such as a sales-type market, a purchase-type market, a trading company-type market, and a general market as desired, and can also flexibly set a group for a specific product.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0007] However, for an e-commerce system, in addition to the administrators and persons in charge of the operating company that operates the e-commerce system, data handling control according to the authority of each user is required for a very large number of users such as the administrators and persons in charge of each trading partner who conducts e-commerce through the e-commerce system.

[0008] The present invention has been made in view of the above problems, and an object thereof is to provide a management device, an e-commerce system, a management method, and a management program that enable accurate and easy data handling control according to the authority of each user for many users of the e-commerce system.

Means for Solving the Problems

[0009] In order to solve the above problems and achieve the object, a management device according to the present invention includes a communication control unit that controls a communication unit so as to mediate transmission and reception of various data between terminal devices of each trading partner that conducts e-commerce via a network, and a user type determination unit that determines whether a logged-in user is a user of an operating company that operates a system for conducting e-commerce or a user of a trading partner that uses the e-commerce system, and when a determination result indicating that the user is a trading partner user is obtained, a display screen is generated in which unique information of the trading partner, which is used as a search key for searching for information related to the trading partner from a storage unit, is displayed as a fixed value that cannot be changed, and when a determination result indicating that the user is a user of the operating company is obtained, a display screen is generated in which unique information of the trading partner, which is used as a search key for searching for information related to the trading partner from a storage unit and is input by the user of the operating company, is displayed as a variable value that can be changed.

[0010] Also, in order to solve the above problems and achieve the object, an e-commerce system according to the present invention includes a first storage unit, and communicates with a terminal device of each trading partner that conducts e-commerce via a network, and a network with a terminal device of a user of an operating company that operates a system for conducting e-commerce. A first communication device that performs communication via the Internet, a second storage unit, a second communication device that communicates with a terminal device of a user of the operating company via a network, and data stored in the first storage unit and the second storage unit at a predetermined timing. A cooperation device for synchronizing the data, the first communication device includes a communication control unit that controls a communication unit so as to mediate transmission and reception of various data between terminal devices of each trading partner that conducts e-commerce via a network, and a logged-in user. A user type determination unit that determines whether the user is a user of an operating company that operates a system for conducting e-commerce or a user of a trading partner that uses the e-commerce system, and a determination result indicating that the user is a trading partner user. When obtained, a display screen is generated in which unique information of the trading partner, which is used as a search key for retrieving information related to the trading partner from the storage unit, is displayed as a fixed value that cannot be changed, and a determination result indicating that the user is a user of the operating company is obtained. A display screen generation unit that generates a display screen in which unique information of the trading partner, which is used as a search key for retrieving information related to the trading partner from the storage unit and is input by the user of the operating company, is displayed as a variable value that can be changed.

[0011] Also, in order to solve the above-described problems and achieve the object, a management method according to the present invention includes a communication control step in which a communication control unit controls a communication unit to mediate transmission and reception of various data between terminal devices of each trading partner that conducts e-commerce via a network, a user type determination step in which a user type determination unit determines whether a logged-in user is a user of an operating company that operates a system for conducting e-commerce or a user of a trading partner that uses the e-commerce system, and a display screen generation step in which a display screen generation unit generates a display screen that displays, as an unchangeable fixed value, unique information of a trading partner used as a search key for retrieving information related to the trading partner from a storage unit when a determination result indicating that the user is a trading partner user is obtained, and generates a display screen that displays, as a changeable variable value, unique information of a trading partner used as a search key for retrieving information related to the trading partner from the storage unit, which is input by the user of the operating company, when a determination result indicating that the user is a user of the operating company is obtained.

[0012] Also, in order to solve the above-described problems and achieve the object, a management program according to the present invention causes a computer to function as a communication control unit that controls a communication unit to mediate transmission and reception of various data between terminal devices of each trading partner that conducts e-commerce via a network, a user type determination unit that determines whether a logged-in user is a user of an operating company that operates a system for conducting e-commerce or a user of a trading partner that uses the e-commerce system, and a display screen generation unit that generates a display screen that displays, as an unchangeable fixed value, unique information of a trading partner used as a search key for retrieving information related to the trading partner from a storage unit when a determination result indicating that the user is a trading partner user is obtained, and generates a display screen that displays, as a changeable variable value, unique information of a trading partner used as a search key for retrieving information related to the trading partner from the storage unit, which is input by the user of the operating company, when a determination result indicating that the user is a user of the operating company is obtained.

Effects of the Invention

[0013] The present invention can accurately and easily control the handling of data according to the authority of each user for many users of an e-commerce transaction system.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37

Figure 38

Figure 39

Figure 40

Figure 41

Figure 42

Figure 43

Figure 44

Figure 45

Figure 46

Figure 47

Figure 48

Figure 49

Figure 50

Figure 51

Figure 52

Figure 53

Figure 54

Figure 55

Figure 56

Figure 57

Embodiments for Carrying Out the Invention

[0015] Hereinafter, embodiments to which the present invention is applied will be described. Note that such embodiments are merely examples of the present invention, and the present invention is not limited to these embodiments.

[0016] [System Configuration] FIG. 1 is a diagram showing the system configuration of an electronic commerce transaction system (EDI system, EDI: Electronic Data Interchange) in which the management device 1 of the embodiment mediates and manages electronic commerce transactions. As shown in FIG. 1, the EDI system includes a management system of an operating company including the management device 1 of the embodiment, a customer terminal device 100 of a customer who conducts business transactions, and a supplier terminal device 200 of a supplier. As illustrated in FIG. 1, the management system of the operating company mediates inventory confirmation, order input from the customer terminal device 100, and orders, order requests, etc. from the supplier terminal device 200 by the management device 1 of the embodiment and the like. Note that the customer and the supplier are examples of business partners.

[0017] (System configuration of the operating company) FIG. 2 is a configuration diagram of the management system of the operating company. As shown in FIG. 2, the management system of the operating company includes a front environment (an example of a first communication device) configured by the management device 1 of the embodiment, a back-yard environment (an example of a second communication device) configured by the management terminal device 80 of the operating company, and a cooperation tool 90 which is a terminal device for cooperating the front environment and the back-yard environment.

[0018] The front environment is connected to the terminal devices of the users of the operating company, as well as the terminal devices of the users of the customers and suppliers via a wide area network such as the Internet 8. This front environment is an environment in which users of business partners (customers and suppliers) and users of the operating company log in and use.

[0019] In addition, the front-end environment is publicly available on the Internet and can be accessed and used by users of the operating company and users having a business relationship with the operating company. Specifically, the storage unit 2 of the management device 1 of the embodiment included in the front-end environment of the operating company stores user information of users of the operating company, users of providers (customers) of products or services, etc., and users of procurement sources (suppliers) of products or services, etc. Further, the storage unit 2 temporarily stores business data resulting from commercial transactions between customers and suppliers. Users of the operating company and users having a business relationship with the operating company can access the management device 1 and use the user data (such as names and email addresses) in the storage unit 2 and the temporarily stored business data (= commercial transaction data).

[0020] In addition, when the number of trading partners is small, the front-end environment may be publicly available with restrictions on the source of connection. Thereby, the front-end environment can be publicly available under higher security.

[0021] The back-end environment is an environment configured by a terminal device 80 that does not permit connections from external companies of trading partners, etc., and can be logged in and used only by users authorized by the operating company. Therefore, the terminal device 80 of this back-end environment is preferably connected to the terminal device of a user authorized by the operating company via a network 9 such as a private network that is not connected to a wide area network such as the Internet or a dedicated line.

[0022] A user authorized by the operating company can access a storage unit (commercial transaction business data management database) 82 in which business data (commercial transaction data) for data management is stored via the communication interface unit 81 of the terminal device 80 of this back-end environment.

[0023] The cooperation tool 90 accesses the storage unit 2 in the front-end environment and the storage unit 82 in the back-yard environment regularly or irregularly, and synchronizes the temporary business data stored in the storage unit 2 in the front-end environment with the business data for data management stored in the storage unit 82 in the back-yard environment. In other words, the cooperation tool 90 attempts to cooperate between the two regularly or irregularly so that the temporary business data in the storage unit 2 and the business data for data management in the storage unit 82 become the same data.

[0024] By separating the front-end environment and the back-yard environment in this way, even if one of the environments goes down, the business can continue in the other environment. Also, for example, since the front-end environment has a large number of users, it is constructed with high-spec terminal devices, and the back-yard environment only needs to be accessible by a limited number of users, so it can be constructed with low-spec terminal devices. Each environment can be constructed with specifications according to the number of users assumed for each environment, and resources can be optimized.

[0025] Also, for example, since the personal information of users of each business partner is registered in the storage unit 2 (database) of the front-end environment, it can be operated according to the nature of the data stored in the database (storage unit 2 or storage unit 82) of each environment, such as by performing special encryption processing before registration.

[0026] Also, by permitting only specific communications (synchronization of the above-mentioned data) by the cooperation tool 90, an infrastructure boundary can be provided and segmented between the front-end environment and the back-yard environment, and security can be enhanced.

[0027] (Hardware Configuration of the Management Device) Next, FIG. 3 shows the hardware configuration of the management device 1 of the operating company. As described above, this management device 1 is connected to the customer terminal device 100 and the supplier terminal device 200 via a wide area network such as the Internet 8. Such a management device 1 includes a storage unit 2, a control unit 3, and a communication interface unit 4. The communication interface unit 4 is connected to the customer terminal device 100 and the supplier terminal device 200 via the network 8. Further, the communication interface unit 4 is connected to the terminal device 80 in the back-end environment via the network 8 and the cooperation tool 90.

[0028] As the storage unit 2, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be used. The storage unit 2 stores a Web EDI trading partner classification master 11, a Web EDI trading partner master 12, a Web EDI user group master 13, and a Web EDI user master 14. Further, the storage unit 2 stores a customer master 15, a product master 16, a product configuration master 17, a customer product configuration master 18, a customer-specific target warehouse master 19, and a warehouse master 20.

[0029] Further, the storage unit 2 stores a customer delivery destination master 55, a delivery destination master 56, a transaction classification master 57, and a display target transaction classification master 58. Further, in addition to the management program for performing e-commerce transaction management, the above-mentioned user data and temporary storage business data (commercial transaction data) are stored in the storage unit 2. Further, the storage unit 2 is provided with an order data storage area 59 for storing the order data of each trading partner.

[0030] Figure 4 is a diagram showing an example of the WebEDI trading partner classification master 11. As shown in this Figure 4, in the WebEDI trading partner classification master 11, an example of trading partners, "customers" and "suppliers", are stored as trading partner classifications. Although not shown in the figure, in the WebEDI trading partner classification master 11, "bill recipients" and "payment recipients" are stored as trading partner classifications.

[0031] Figure 5 is a diagram showing an example of the WebEDI trading partner master 12. As shown in this Figure 5, in the WebEDI trading partner master 12, for each trading partner classification and the company serving as the trading partner, the upper limit value of the number of users that can be registered by users, and status information indicating whether the company serving as the trading partner can use the EDI system are stored. The example in this Figure 5 shows an example where Company A, which is a customer, has an upper limit value of "3 people" for the number of users that can be registered, and the status information indicating whether to use the EDI system is set to "valid".

[0032] Also, the example in this Figure 5 shows an example where Company X, which is a supplier, has an upper limit value of "8 people" for the number of users that can be registered, and the status information indicating whether to use the EDI system is set to "invalid". As will be described later, the management device 1 in the embodiment updates the expiration date of the user ID of each user of a company whose status information is set to "invalid" to the date of expiration. Thus, by setting the status information for a company to "invalid", it becomes possible to collectively restrict the use of the EDI system by each user of that company.

[0033] Figure 6 is a diagram showing an example of the WebEDI user group master 13. Trading partner classification, user group, operation company management permission information, and trading partner management permission information are stored.

[0034] Among these, the user groups indicate each user of the business (duties) of the operating company, customers, and suppliers. That is, the user group of "operating company administrators" indicates a group composed of each user who conducts management work in the operating company. Also, the user group of "customer representatives" indicates a group composed of each user who serves as a representative at the customer.

[0035] Also, the user group of "purchasing supplier estimator" indicates a group composed of each user who is in charge of the estimation work at the purchasing supplier. Also, the user group of "purchasing supplier actual work operator" indicates a group composed of each user who is in charge of the actual work at the purchasing supplier.

[0036] The operating company management permission information is information indicating a user group for which the operating company can manage user registration. In the case of the example in FIG. 6, the operating company can manage user registration (user registration authority) for all user groups of the operating company itself, customers, and suppliers.

[0037] Also, in the management device 1 of the embodiment, the authority for user registration can be entrusted (set) to desired user groups of customers and suppliers. Information indicating the presence or absence of this entrustment of the user registration authority is the trading partner management permission information. The example in FIG. 6 shows an example in which the operating company side entrusts (sets) the authority for user registration to each user group of "customer administrators" and "customer representatives" of the customer via the management device 1. That is, the user having the registration authority in this case is the customer administrator, indicating that user registration is possible only for each user group of "customer administrators" and "customer representatives".

[0038] Also, the example in FIG. 6 shows an example in which the operating company side entrusts (sets) the authority for user registration to the purchasing supplier administrator of the purchasing supplier for the user group of "purchasing supplier actual work operator" of the purchasing supplier. That is, the user having the registration authority in this case is the purchasing supplier administrator, indicating that the purchasing supplier administrator can perform user registration only for the user group of "purchasing supplier actual work operator".

[0039] In this example, the description will be given on the assumption that the authority for user registration is set for each user group of the business partners. However, the authority for user registration may be set for each business partner.

[0040] FIG. 7 is a diagram showing an example of the WebEDI user master 14 in which the above-described user data is registered. As shown in this FIG. 7, the WebEDI user master 14 stores user identification information (user ID), user name, and user ID expiration date of each user belonging to the user groups of the operating company and each business partner. The user ID expiration date is information indicating the date when the EDI system can be used.

[0041] In the example of this FIG. 7, the user ID expiration dates of the user with the user ID of "UK01" (i.e., "Operating Company Administrator UK1") belonging to the user group of "Operating Company Administrator" of the operating company and the user with the user ID of "UK02" (i.e., "Operating Company Administrator UK2") are both "March 31, 2030". Further, in the example of this FIG. 7, the user ID expiration dates of the user with the user ID of "AT01" (i.e., "A Company Person in Charge AT1") belonging to the user group of "Customer Responsible Person" of Company A and the user with the user ID of "AT03" (i.e., "A Company Person in Charge AT3") are both "March 31, 2030", but the user ID expiration date of the user with the user ID of "AT02" (i.e., "A Company Person in Charge AT2") is shown as having expired on "January 1, 2010".

[0042] Similarly, in the example of this FIG. 7, it is shown that the user ID expiration dates of the users of "Company X Administrator XK1" and "Company X Quotation Responsible Person XMT1" of Company X have both expired on "March 1, 2022".

[0043] Next, FIG. 8 is a diagram showing various screens provided from the management device 1 to users of the user groups of the operating company and each business partner. As shown in this FIG. 8, for each user in the user group of "operating company administrator", a "business partner master maintenance screen", an "operating company user master maintenance screen", and an "operating company business partner user master maintenance screen" are provided from the management device 1. Also, for each user in the user group of "operating company staff", an "operating company business screen" is provided from the management device 1.

[0044] Also, for users in the user group of "customer administrator", a "customer business partner user master maintenance screen" is provided, and for users in the user group of "customer staff", a "customer business screen" is provided, respectively, from the management device 1.

[0045] Also, for users in the user group of "supplier administrator", a "supplier business partner user master maintenance screen" is provided, for users in the "supplier quotation staff" user group, a "supplier quotation business screen" is provided, and for users in the "supplier actual work staff" user group, a "supplier actual work screen" is provided, respectively, from the management device 1.

[0046] More specifically, FIG. 9 is a diagram showing an example screen of the "business partner master maintenance screen" provided for each user in the user group of "operating company administrator". The "business partner master maintenance screen" shown in this FIG. 9 is a screen for registering business partners who use the EDI system. The operating company side registers business partner classification, business partner name, upper limit of the number of users, and status via this "business partner master maintenance screen".

[0047] As the customer classification, either "supplier" or "customer" is selected and registered. As the customer name, for example, a customer name such as "Company X" is registered. As the upper limit of the number of users, the upper limit value of the number of users who can use the EDI system is registered. As the status, status information indicating whether the EDI system can be used (valid or invalid) is registered. The example in this Figure 9 shows the case where the status information of Company X is "invalid" and Company X is not allowed to use the EDI system.

[0048] Figure 10 is a diagram showing an example of the "Operating Company User Master Maintenance Screen" provided for each user in the user group of "Operating Company Administrator". As shown in this Figure 10, the "Operating Company User Master Maintenance Screen" is a screen for classifying "users on the operating company side" into user groups and registering user information. Users on the operating company side register user groups (operating company administrator or operating company staff), user ID, user name, initial password, and user ID expiration date via this "Operating Company User Master Maintenance Screen".

[0049] Figure 11 is a diagram showing an example of the "Trading Partner User Master Maintenance Screen for Operating Company" provided for each user in the user group of "Operating Company Administrator". As shown in this Figure 11, the "Trading Partner User Master Maintenance Screen for Operating Company" is a screen for classifying "users of trading partners on the operating company side" into user groups and registering user information. Users on the operating company side register trading partner classification, trading partner name, user group, user ID, user name, initial password, and user ID expiration date via this "Trading Partner User Master Maintenance Screen for Operating Company". For the trading partner classification, either "supplier" or "customer" is selected. As the trading partner name, for example, a trading partner name such as "Company X" or "Company Y" is selected. For the user group, for example, the above-mentioned user groups such as "supplier staff" or "customer administrator" are selected.

[0050] FIG. 12 is a diagram showing an example of a "Customer Transaction User Master Maintenance Screen" provided to each user in the user group of "Customer Manager" or "Supplier Manager". Among them, FIG. 12(a) is an example of the "Customer Transaction User Master Maintenance Screen" provided to the "Customer Manager", and FIG. 12(b) is an example of the "Customer Transaction User Master Maintenance Screen" provided to the "Supplier Manager".

[0051] As shown in FIG. 12(a), the "Customer Manager" selects the user group to which the company's users belong via the "Customer Transaction User Master Maintenance Screen", and registers the user ID, user name, initial password, and user ID expiration date.

[0052] Similarly, as shown in FIG. 12(b), the "Supplier Manager" selects the user group to which the company's users belong via the "Customer Transaction User Master Maintenance Screen", and registers the user ID, user name, initial password, and user ID expiration date. Note that the example of FIG. 12(b) is an example in which the user group of "Supplier Actual Operation Staff" is selected as the user group.

[0053] (Functional Configuration of the Management Device) Next, the control unit 3 of the management device 1 shown in FIG. 3 functions as a communication control unit 21, a user management authority setting unit 22, a data generation unit 23, a determination unit 24 (an example of a user type determination unit), a storage control unit 25, a display screen generation unit 26, and a status setting unit 27 by executing the management program stored in the storage unit 2.

[0054] The communication control unit 21 controls the communication interface unit 4, which is an example of a communication unit, to mediate the transmission and reception of various commercial transaction data between the terminal devices 100 and 200 of each trading partner that conducts e-commerce via the network 8. The user management authority setting unit 22 sets, for the trading partner, a user management authority for registering or editing predetermined user information including expiration date information indicating the expiration date of a regular user authority. "Editing" is a concept that includes acts such as changing and deleting the content of data such as modifying and deleting user information.

[0055] When a new registration or editing (including deletion) of a user is requested via the terminal devices 100 and 200 of the trading partner, the display screen generation unit 26 generates a user registration screen (the trading partner user master maintenance screen for the trading partner shown in FIGS. 12(a) and 12(b)) for performing a new registration or the like of the user, which is transmitted to the terminal device of the trading partner that requested the new registration or the like of the user via the communication interface unit 4.

[0056] The determination unit 24 determines whether the trading partner that requested a new registration or the like of the user is a trading partner for which a user management authority is set. When the determination result indicating that the trading partner that requested a new registration or the like of the user is a trading partner for which a user management authority is set is obtained from the determination unit 24, the storage control unit 25 stores, in the WebEDI user master 14 of the storage unit 2 in which user information including the expiration date information (user ID expiration date information) of each user set for each trading partner is stored, the user information including the user ID expiration date information of the user for which a new registration or the like has been performed.

[0057] Note that the user management authority setting unit 22 sets a user management authority for each user group composed of administrators or persons in charge of each trading partner. Also, the user management authority setting unit 22 sets, for each trading partner, an upper limit on the number of registrable users.

[0058] In addition, the status setting unit 27 sets a status indicating whether a transaction with each trading partner is valid or invalid. The storage control unit 25 stores, for each trading partner, status information indicating the status set by the status setting unit 27 in the Web EDI trading partner master 12 of the storage unit 2, together with the user information of the user of each trading partner and the user ID expiration date information.

[0059] In addition, when the status setting unit 27 sets an "invalid" status for a trading partner, the storage control unit 25 updates the status information of the trading partner whose transaction has been set to invalid and is stored in the Web EDI trading partner master 12 to the "invalid" status information. At the same time, the storage control unit 25 updates the user ID expiration date information of the user of the trading partner whose transaction has been set to "invalid" and is stored in the Web EDI user master 14 to the expiration date.

[0060] The data generation unit 23 generates user data including a user group, a user ID, an initial password, a user ID expiration date, etc. input via the various screens described with reference to FIGS. 8 to 12.

[0061] In addition, the discrimination unit 24 also functions as a user type discrimination unit, and discriminates whether the logged-in user is a user of an operating company that operates a system for conducting e-commerce transactions or a user of a trading partner that uses the e-commerce system, based on the user ID input at the time of login.

[0062] When a discrimination result indicating that the user is a trading partner user is obtained, the display screen generation unit 26 generates a display screen that displays the unique information of the trading partner (for example, the customer code and the customer name), which is used as a search key for retrieving information related to the trading partner from the storage unit 2, as a non-changeable fixed value. When a discrimination result indicating that the user is an operating company user is obtained, the display screen generation unit 26 generates a display screen that displays the unique information of the trading partner, which is used as a search key for retrieving information related to the trading partner input by the operating company user from the storage unit, as a changeable variable value.

[0063] Further, when a discrimination result indicating that the user is a trading partner is obtained, the display screen generation unit 26 generates a display screen in which an input field for the unique information of the desired trading partner serving as a search key (for example, an input field for the customer code) is hidden. Further, when a discrimination result indicating that the user is an operating company is obtained, the display screen generation unit 26 generates a display screen in which an input field for the unique information of the desired trading partner serving as a search key (for example, an input field for the customer code) is displayed.

[0064] The search unit 28 searches the storage unit 2 for data (for example, product code, warehouse code, delivery destination code, order data, etc.) associated with and stored in the unique information of the trading partner (for example, customer code, etc.). The display screen generation unit 26 generates a display screen including the searched data.

[0065] Further, the search unit 28 searches for at least one of the order history, delivery destination, handled products or services, inventory products, and warehouse data associated with the unique information of the trading partner. The display screen generation unit 26 generates a display screen including the searched data.

[0066] (Registration operation of a new user of the operating company) Next, the registration operation of a new user of the operating company in such an operating company management device 1 will be described with reference to the flowchart of FIG. 13. Hereinafter, the "registration" of a new user will be described as an example, but when "editing" such as modification or deletion of user information is performed, the same operation as described below will be performed. For this reason, please also refer to the following description for the operation during editing such as modification or deletion of user information. Each process in the flowchart of FIG. 13 is executed by the control unit 3 of the management device 1 based on the management program stored in the storage unit 2. That is, a user who registers a new user of the operating company makes a login request to the management device 1 via the administrator terminal device. As a result, the flowchart of FIG. 13 starts, and the processes are executed in order from step S1.

[0067] In step S1, the display screen generation unit 26 of the management device 1 generates a login screen illustrated in FIG. 14(a). The communication control unit 21 transmits this login screen to the administrator terminal device of the user of the operating company where the login request was made. The user of the operating company that made the login request inputs a user ID and a password to the login screen displayed on the display screen of the administrator terminal device. The input user ID and password are transmitted to the management device 1.

[0068] The discrimination unit 24 of the management device 1 refers to the user ID expiration date of the WebEDI user master 14 illustrated in FIG. 14(b) based on the user ID input via the login screen (step S2). Then, the discrimination unit 24 discriminates whether the input user ID has expired by discriminating whether the date of today exceeds the date set as the user ID expiration date (step S3). If it is discriminated by the discrimination unit 24 that the input user ID has expired (step S3: Yes), since that user has no authority to perform user registration, the processing of the flowchart in FIG. 13 ends as it is.

[0069] On the other hand, if it is discriminated that the input user ID is within the expiration date (step S3: No), the discrimination unit 24 discriminates whether there is a request to activate the operating company user master maintenance screen (step S4). And when a request to activate the operating company user master maintenance screen is detected (step S4: Yes), in step S5, the discrimination unit 24 refers to the WebEDI user master 14 shown in FIG. 14(c) based on the user ID to discriminate whether the user is a user in the user group of "operating company administrator" who has the authority to register a new user. If the user is not a user in the user group of "operating company administrator" (step S5: No), since that user has no authority to perform user registration, the processing of the flowchart in FIG. 13 ends as it is.

[0070] If the user belongs to the user group of "operation company manager" (step S5: Yes), the process proceeds to step S6. In step S6, as shown in FIG. 15(a), the discrimination unit 24 refers to the WebEDI user group master 13 and identifies user groups for which the business partner classification is not set and which can be managed by the operation company.

[0071] That is, a user group for which the business partner classification is not set means a user group of the operation company, rather than a user group of either a customer or a supplier. Therefore, the discrimination unit 24 detects a user group of the operation company for which the business partner classification is not set. Then, the discrimination unit 24 refers to the operation company management permission information in the WebEDI user group master 13 to identify a user group (a user group for which user management within the operation company is possible) for which user registration is possible among the user groups of the operation company for which the business partner classification is not set. The example in FIG. 15(a) is an example in which new user registration is permitted for each of the user groups of "operation company manager" and "operation company staff".

[0072] Next, in step S7, the display screen generation unit 26 generates an operation company user master maintenance screen illustrated in FIG. 15(b), and the communication control unit 21 transmits this operation company user master maintenance screen to the administrator terminal device.

[0073] The user of the administrator terminal device selects either the user group of "operation company manager" or "operation company staff", which is a user group for which user registration is permitted, based on the operation company user master maintenance screen illustrated in FIG. 15(b). Also, the user of the administrator terminal device inputs the user ID, user name, initial password, and user ID expiration date of the user for whom new user registration is to be performed and performs a registration operation on the operation company user master maintenance screen illustrated in FIG. 15(b).

[0074] As a result, information such as user group, user ID, user name, initial password, and user ID expiration date entered via the operator company user master maintenance screen is transmitted from the administrator terminal device to the management device 1 and a registration request is made. When this registration request is received by the management device 1, the data generation unit 23 of the management device 1 determines that a registration operation has been performed (step S8: Yes), and generates detail data (records) of the WebEDI user master 14 including the user group, user ID, user name, initial password, and user ID expiration date received from the administrator terminal device.

[0075] In step S9, the memory control unit 25 adds the detail data (records) generated by the data generation unit 23 to the WebEDI user master 14 and stores it as shown in FIG. 15(c). As a result, for example, a user with a user ID of "UT99" and a user name of "Operator Company Person in Charge UT99" is newly registered in the user group of "Operator Company Person in Charge" of the operator company with "December 31, 2030" as the user ID expiration date.

[0076] (Registration operation of a new supplier user by an operator company user) Next, the registration operation of a new supplier user by an operator company user in the management device 1 of such an operator company will be described using the flowchart of FIG. 16. Each process of the flowchart of FIG. 16 is executed by the control unit 3 of the management device 1 based on the management program stored in the storage unit 2.

[0077] That is, a user of the operator company who registers a new supplier user makes a login request to the management device 1 via the administrator terminal device. As a result, the flowchart of FIG. 16 starts, but the operations in steps S1 to S3 until it is determined whether the user ID expiration date has been exceeded based on the user ID entered on the login screen are the same as the operations in steps S1 to S3 of the flowchart of FIG. 13. Therefore, for a detailed description of the operations in steps S1 to S3, refer to the description of the operations in steps S1 to S3 of the flowchart of FIG. 13.

[0078] Next, when it is determined in step S3 that the user ID has not expired (step S3: No), the process proceeds to step S11 in the flowchart of FIG. 16. In step S11, the determination unit 24 determines whether there is a request from the user of the operating company to start the trading partner user master maintenance screen for the operating company, as illustrated in FIG. 17(a).

[0079] When a request to start the trading partner user master maintenance screen for the operating company is detected (step S11: Yes), the determination unit 24, in step S5, refers to the WebEDI user master 14 based on the user ID and determines whether the user belongs to the user group of "operating company administrator" who has the right to register new users. If the user does not belong to the user group of "operating company administrator" (step S5: No), since the user does not have the right to perform user registration, the process of the flowchart in FIG. 16 ends as it is.

[0080] If the user belongs to the user group of "operating company administrator" (step S5: Yes), the process proceeds to step S12. In step S12, the display screen generation unit 26 generates the trading partner user master maintenance screen for the operating company as illustrated in FIG. 17(a), and the communication control unit 21 transmits this trading partner user master maintenance screen for the operating company to the administrator terminal device.

[0081] The user of the administrator terminal device selects a trading partner classification such as "supplier" based on the trading partner user master maintenance screen for the operating company as shown in FIG. 17(b). Also, the user of the administrator terminal device inputs a trading partner name such as "Company Y" based on the trading partner user master maintenance screen for the operating company as shown in FIG. 17(c). Further, the user of the administrator terminal device inputs the user group, user ID, user name, initial password, and user ID expiration date based on the trading partner user master maintenance screen for the operating company as shown in FIG. 17(d) and performs a registration operation.

[0082] As a result, each piece of information including the business partner classification, business partner, user group, user ID, user name, initial password, and user ID expiration date entered via the business partner user master maintenance screen for the operating company is sent from the administrator terminal device to the management device 1, and a registration request is made. When this registration request is received by the management device 1, the discrimination unit 24 of the management device 1 discriminates that a registration operation has been performed (step S13: Yes). Then, in step S14, the discrimination unit 24 refers to the WebEDI business partner master 12 shown in FIG. 18(a) and detects the upper limit value of the number of users for the entered business partner. In the example of FIG. 18(a), the upper limit value of the number of users is set to "10 people".

[0083] Also, the discrimination unit 24 refers to the WebEDI user master 14 shown in FIG. 18(b) to detect the current number of valid users of the business partner for which new user registration is currently being attempted. The example of FIG. 18(b) shows that the business partner for which new user registration is currently being attempted is Company Y, and the current number of valid users of Company Y is "3 people".

[0084] And in this example, since the upper limit value of the number of users of Company Y is "10 people" and the current number of valid users is "3 people", even if a new user is registered, the upper limit value of the number of users of Company Y will not be exceeded. Therefore, the discrimination unit 24 discriminates that the upper limit value of the number of users will not be exceeded (step S14: No). As a result, the data generation unit 23 generates detailed data (records) of the WebEDI user master 14 including the business partner classification, business partner, user group, user ID, user name, initial password, and user ID expiration date received from the administrator terminal device.

[0085] Incidentally, as will be described later, when a new user is registered and the upper limit value of the number of users set for a business partner is exceeded (step S14: Yes), the display screen generation unit 26 generates, as shown in Fig. 23(a), an operation company's business partner user master maintenance screen that displays an error message such as "Users cannot be added beyond the upper limit of the number of users". Then, the communication control unit 21 transmits this operation company's business partner user master maintenance screen with the error message displayed to the operation administrator terminal device. As a result, the user of the operation administrator terminal device recognizes that no further new user registration is possible and will perform operations such as deleting unnecessary users or adding and expanding the upper limit value of the number of users.

[0086] Next, in step S9, the storage control unit 25 adds and stores the detail data (record) generated by the data generation unit 23 to the WebEDI user master 14 as shown in Fig. 18(c). As a result, for example, a user with a user ID of "YJT99" and a user name of "Company Y's actual operation person in charge YJT99" is newly registered in the user group of "Purchasing destination's actual operation person in charge" of Company Y with "December 31, 2030" as the user ID expiration date.

[0087] (Operation of the business partner registering a new user of its own company) Next, the operation of the management device 1 when a purchasing company, which is an example of a business partner, registers a new user of its own company will be described using the flowchart of Fig. 19. Each process in the flowchart of Fig. 19 is executed by the control unit 3 of the management device 1 based on the management program stored in the storage unit 2. That is, the user of the purchasing company that registers a new user makes a login request to the management device 1 via the purchasing terminal device 200. As a result, the flowchart of Fig. 19 starts, and the processes are executed in order from step S21.

[0088] In step S21, the display screen generation unit 26 of the management device 1 generates a login screen illustrated in Fig. 20(a). The communication control unit 21 transmits this login screen to the purchasing destination terminal device 200 of the user of the purchasing destination company where the login request has been made. The user of the purchasing destination company that has made the login request inputs the user ID and password to the login screen displayed on the display screen of the purchasing destination terminal device 200. The input user ID and password are transmitted to the management device 1.

[0089] The discrimination unit 24 of the management device 1 refers to the user ID expiration date of the WebEDI user master 14 illustrated in Fig. 20(b) based on the user ID input via the login screen (step S22). Then, the discrimination unit 24 discriminates whether the input user ID of the user of the purchasing destination company has expired by discriminating whether the date of today exceeds the date set as the user ID expiration date (step S23). If the discrimination unit 24 determines that the input user ID has expired (step S23: Yes), the user of that purchasing destination company has no authority to perform user registration, and thus the processing of the flowchart in Fig. 19 ends as it is.

[0090] On the other hand, if it is determined that the input user ID is within the expiration date (step S23: No), the discrimination unit 24 discriminates whether there is a request to activate the transaction destination trading partner user master maintenance screen (step S24). When a request to activate the transaction destination trading partner user master maintenance screen is detected (step S24: Yes), in step S25, the discrimination unit 24 refers to the WebEDI user master 14 shown in Fig. 20(c) based on the user ID to discriminate whether the user of that purchasing destination company is a user in the user group of "purchasing destination administrator" who has the authority to register new users. If the user is not a user in the user group of "purchasing destination administrator" (step S25: No), the user of that purchasing destination company has no authority to perform user registration, and thus the processing of the flowchart in Fig. 19 ends as it is.

[0091] If the user is a member of the user group of "Supplier Manager" (step S25: Yes), the process proceeds to step S26. In step S26, the discrimination unit 24 refers to the WebEDI trading partner master 12 shown in FIG. 21(a) and confirms that the status information of Supplier Y is "valid". Also, the discrimination unit 24 refers to the WebEDI user group master 13 shown in FIG. 21(b) to identify the user group whose trading partner classification is the same as that of the logged-in user, i.e., "Supplier", and for which the trading partner is manageable. In the case of the example in FIG. 21(b), the discrimination unit 24 identifies the user group of "Supplier actual operation staff" as the user group for which user registration is possible.

[0092] Next, in step S27, the display screen generation unit 26 generates a trading partner user master maintenance screen illustrated in FIG. 21(c), and the communication control unit 21 transmits this trading partner user master maintenance screen to the supplier terminal device 200.

[0093] The supplier manager of the supplier terminal device 200 selects the user group of "Supplier actual operation staff" for which user registration is permitted based on the trading partner user master maintenance screen illustrated in FIG. 21(c). Also, the supplier manager of the supplier terminal device 200 inputs the user ID, user name, initial password, and user ID expiration date of the user for whom new user registration is to be performed on the trading partner user master maintenance screen illustrated in FIG. 21(c) and performs a registration operation.

[0094] Thereby, the information on the user group, user ID, user name, initial password, and user ID expiration date input via the trading partner user master maintenance screen is transmitted from the supplier terminal device 200 to the management device 1 and a registration request is made. When this registration request is received by the management device 1, the discrimination unit 24 of the management device 1 determines that a registration operation has been performed (step S28: Yes), and the process proceeds to step S29.

[0095] In step S29, the determination unit 24 refers to the WebEDI master 12 shown in Fig. 22(a) and detects the "upper limit of the number of users" of the company that is currently the target of user registration. In the case of this example, as shown in Fig. 22(a), the determination unit 24 detects the upper limit of the number of users of Company Y, which is the supplier that is the target of new user registration, as "10 people".

[0096] In addition, the determination unit 24 refers to the WebEDI user master shown in Fig. 22(b) and detects the current number of valid users in the supplier that is the target of new user registration. In the case of the example in Fig. 22(b), the determination unit 24 detects the current number of valid users as "3 people" in Company Y, which is the supplier that is the target of new user registration.

[0097] Then, in step S29, the determination unit 24 determines whether or not the number of valid users exceeds the upper limit value of the number of users when a new user registration is performed. If the number of valid users exceeds the upper limit of the number of users by performing a new user registration (step S29: Yes), since the number of user registrations will exceed the specified number, as shown in Fig. 23(a), the display screen generation unit 26 generates a transaction-use supplier user master maintenance screen that displays an error message such as "Users cannot be added beyond the upper limit of the number of users", and transmits it to the supplier terminal device 200 to end the processing of the flowchart in Fig. 19. As a result, the person in charge of the supplier at the supplier terminal device 200 recognizes that no further new user registrations can be made, and will perform operations such as deleting unnecessary users or adding and expanding the upper limit of the number of users.

[0098] On the other hand, when the number of valid users does not exceed the upper limit value of the number of users (step S29: No), the data generation unit 23 of the management device 1 generates detail data (records) of the WebEDI user master 14 including the user group, user ID, user name, initial password, and user ID expiration date received from the supplier terminal device 200.

[0099] In step S30, the memory control unit 25 adds and stores the detail data (record) generated by the data generation unit 23 to the WebEDI user master 14 as shown in Fig. 23(b). As a result, for example, a user with a user ID of "YJT99" and a user name of "Y Company's actual work operator YJT99" is newly registered in the user group of "Vendor's actual work operator" of Company Y, which is the vendor, with "December 31, 2030" as the user ID expiration date.

[0100] (Invalid operation of the trading partner) Next, the operation of batch invalidation of the users of a trading partner by the operation company administrator setting the status of the trading partner to "invalid" will be described using the flowchart of Fig. 24. Each process in the flowchart of Fig. 24 is executed by the control unit 3 of the management device 1 based on the management program stored in the storage unit 2.

[0101] That is, the user who sets the status of the trading partner to "invalid" makes a login request to the management device 1 via the administrator terminal device. As a result, the flowchart of Fig. 24 starts, but the operations in steps S1 to S3 until it is determined whether the user ID expiration date has expired based on the user ID input on the login screen are the same as the operations in steps S1 to S3 of the flowchart of Fig. 13. Therefore, for a detailed description of the operations in steps S1 to S3, refer to the description of the operations in steps S1 to S3 of the flowchart of Fig. 13.

[0102] Next, when it is determined that the user ID expiration date is within the expiration date (step S3: No) and the process proceeds to step S11, the display screen generation unit 26 determines whether there is a request to start the trading partner master maintenance screen exemplified in Fig. 9 from the administrator terminal device. Then, when a request to start the trading partner master maintenance screen is made from the administrator terminal device (step S11: Yes), the discrimination unit 24 determines in step S5 whether the user who is currently making a request to start the trading partner master maintenance screen is a user in the user group of "operation company administrator" based on the user ID at the time of the login request.

[0103] If the user who is currently requesting to start the customer master maintenance screen is not a user in the "operation company administrator" user group (Step S5: No), since the user does not have the authority to set the status of the customer to "invalid", the processing of the flowchart in FIG. 24 ends as it is.

[0104] On the other hand, if the user who is currently requesting to start the customer master maintenance screen is a user in the "operation company administrator" user group (Step S5: Yes), the display screen generation unit 26 generates the customer master maintenance screen illustrated in FIG. 9, and the communication control unit 21 transmits this customer master maintenance screen to the administrator terminal device (Step S12).

[0105] The "operation company administrator" user designates the customer classification, customer name, and user limit based on the customer master maintenance screen illustrated in FIG. 9, and sets the status to "invalid". In step S41 of the flowchart in FIG. 24, the status setting unit 27 determines whether there is such an invalid operation. Then, when the status setting unit 27 detects an invalid operation (Step S41: Yes), in step S42, it generates status information for setting the status of the customer designated on the customer master maintenance screen to "invalid" (= sets the status of the customer to "invalid").

[0106] When the "invalid" status information is generated, the memory control unit 25 updates the status information of, for example, Company X, which was a supplier as shown in FIG. 25(a), to "invalid". As a result, the use of the EDI system by Company X is restricted.

[0107] At the same time, in step S43, the status setting unit 27 generates, as the user ID expiration date for all users belonging to all user groups of Company X, which is the trading partner whose status information is set to "invalid", the user ID expiration date of the expired date. The memory control unit 25 inputs the generated user ID expiration date of the expired date as the user ID expiration date of all users in all user groups of Company X, as shown in Fig. 25(b).

[0108] As a result, the user ID expiration dates of all users in all user groups of Company X whose status is set to "invalid" can be collectively updated to expired, thereby restricting the use of the EDI system. If, even when the operating company invalidates a transaction with a trading partner, each user belonging to the trading partner is not invalidated, there will be a problem that users who should not be able to use the EDI system can still use it. However, the management device 1 of the embodiment can prevent such problems and restrict the use of the EDI system by each user of the trading partner whose status is set to "invalid".

[0109] (Data handling control according to user authority) Here, in the e-commerce transaction system, multiple trading partners log in and perform operations. Similarly, the administrator of the operating company, which is an enterprise introducing the front-end environment, also logs in to monitor or investigate trading partners. Therefore, it is necessary to control the handling of data according to the authority of each user for a very large number of users. Also, if users with administrator authority are arranged for each trading partner, the management cost of user IDs and passwords will increase.

[0110] Therefore, the management device 1 of the EDI system according to the embodiment determines whether the logged-in user is a user of the operating company or a user of the trading partner from the above-described Web EDI user master 14, and controls the data that enables the administrator of the operating company and the trading partner to control or acquire input items. That is, when the logged-in user is a user of the trading partner, the management device 1 makes the input items used in the jobs in the front-end environment unavailable or non-displayable, and enables the use of various masters according to the permission settings assigned to each trading partner. In addition, when the logged-in user is an administrator of the operating company, the management device 1 enables the input items used in the jobs in the front-end environment to be freely inputtable or displayed and freely inputtable. As a result, cross-cutting operations become possible (all operations of the system become possible).

[0111] (Association of data of each master) In the case of the management device 1 according to the embodiment, as illustrated in FIGS. 26 to 29, the data of each master are associated with each other. FIG. 26 is a diagram showing a state in which the data of the product master 16, the product configuration master 17, the customer product configuration master 18, and the customer master 15 are associated with each other. That is, as shown in FIG. 26(a), the product master 16 stores data such as a product code (product CD) and a product name. Correspondingly, as shown in FIG. 26(b), the product configuration master 17 stores component codes (configuration PT codes) corresponding to each product code, associated with the product code of the product master 16. Thereby, each product and the configuration PTCD of each product are associated with each other.

[0112] Similarly, as shown in FIG. 26(c), in the customer product configuration master 18, each configuration PTCD of the product configuration master 17 is associated with and stored for each customer code (customer CD). Thereby, the components of each product and each customer are associated with each other.

[0113] Similarly, as shown in FIG. 26(d), the customer master 15 stores each customer code and customer name. Thereby, the "customer code and customer name" of the customer master 15 and each configuration PTCD of the customer product configuration master 18 are associated with each other respectively.

[0114] Figure 27 is a diagram showing how the customer master 15, the customer-specific target warehouse master 19, and the warehouse master 20 are associated. Each customer code in the customer master 15 shown in Figure 27(a) is associated with each warehouse code in the customer-specific target warehouse master 19 as shown in Figure 27(b). Thereby, each customer and each warehouse are associated. Also, each warehouse code in the customer-specific target warehouse master 19 is associated with the warehouse name in the warehouse master 20 shown in Figure 27(c). Thereby, each customer, each warehouse code, and the warehouse name are associated.

[0115] Figure 28 is a diagram showing how the customer master 15, the customer supplier master 55, and the supplier master 56 are associated. Each customer code in the customer master 15 shown in Figure 28(a) is associated with each supplier code in the customer supplier master 55 as shown in Figure 28(b). Also, each warehouse code in the customer supplier master 55 is associated with the supplier name in the supplier master 56 shown in Figure 28(c). Thereby, each customer, each supplier code, and the supplier name are associated.

[0116] Figure 29 is a diagram showing how the transaction category master 57 and the display target transaction category master 58 are associated. As shown in Figure 29(a), the transaction category master 57 stores data categories corresponding to transaction categories such as warehouse shipment order, discount, and sales, and user transaction categories. The display target transaction category master 58 shown in Figure 29(b) is a master that stores the transaction categories to be displayed as the business partner, and stores the data categories and user transaction categories of the transaction category master 57.

[0117] (Screen Control) (Display Control of Order History List Screen for Business Partner Users) Next, the management device 1 of the embodiment controls the display mode of the operation screen and the like according to each master thus associated and the authority of the logged-in user. FIG. 30(a) is a diagram showing an example of an order history list screen displayed when a trading partner user with the user ID "U001" logs in and specifies the display of the order history. In this case, as shown in FIG. 30(a), the display screen generation unit 26 generates an order history list screen including a data grid for displaying a list of order histories together with input fields for the customer code, customer name, order date, and shipment date.

[0118] Also, the search unit 28 refers to the WebEDI user master 14 shown in FIG. 30(b) based on the user ID such as "U001" input at the time of login, and detects the operating company user flag of "FALSE" or "TRUE" and the trading partner code such as "T001". Further, the search unit 28 refers to the customer master 15 based on the detected trading partner code, and detects the customer name such as "Customer 1" associated with the trading partner code of "T001".

[0119] In this case, the operating company user flag for the user with the user ID of "U001" is "FALSE", which means that this user is not an operating company user but a trading partner user. Therefore, the display screen generation unit 26 automatically inputs the trading partner code of "T001" of the logged-in user into the input field of the customer code in the order history list screen, and automatically inputs the customer name of "Customer 1" into the input field of the customer name. Then, the display screen generation unit 26 sets the customer code and the customer name as fixed values that cannot be changed. In other words, the display screen generation unit 26 makes the input operations for the customer code and the customer name unavailable.

[0120] In this state, the search unit 28 searches for the order data shown in FIG. 30(c) stored in the order data storage area 59 of the storage unit 2 using the customer code of "T001" as the search key, and detects the order data corresponding to the customer code of "T001". The display screen generation unit 26 displays the detected order data in a list in the data grid. In this way, by setting it as a fixed value so that the customer cannot be changed and extracting and displaying only the order data corresponding to this fixed customer, only the order data corresponding to the user authority of the user of the customer of "U001" can be displayed (limitation of the display mode according to the user authority), and the security of the EDI system can be maintained.

[0121] The order history list screen generated in this way is transmitted by the communication control unit 21 to the terminal device of the user of the customer of "U001" and displayed. Hereinafter, the description of the operation explanation that the screen generated by the display screen generation unit 26 is transmitted by the communication control unit 21 to the terminal device of the customer user or the terminal device of the user of the operating company and displayed is omitted. The description of "the display screen generation unit 26 generates and displays a screen" should be understood to mean that "the screen generated by the display screen generation unit 26 is transmitted to a predetermined terminal device and displayed".

[0122] (Display control of the delivery destination search screen for the customer user) FIG. 31(a) is a diagram showing an example of the delivery destination search screen displayed when the user of the customer with the user ID of "U001" logs in and specifies a delivery destination search. On the delivery destination search screen, an input field for the customer code of the customer to perform the search, an input field for the delivery destination code, an input field for the delivery destination name, an input field for the delivery destination kana name, and a data grid for displaying a list of delivery destinations are displayed. However, as described with reference to FIG. 30(b), when the user who specifies the delivery destination search is a customer user (= the operating company user flag is FALSE), the display screen generation unit 26 controls the input field for entering the customer code to be hidden. Thereby, it is possible to disable the input of the customer code and make it impossible to search for delivery destinations of customers other than the customer of the user with the user ID of "U001".

[0123] In this case, the search unit 28 refers to the WebEDI user master 14 based on the user ID such as "U001" entered at the time of login, and detects the trading partner code such as "T001". Further, the search unit 28 refers to the trading partner master 15 shown in Fig. 31(b), the trading partner delivery destination master 55 shown in Fig. 31(c), and the delivery destination master 56 shown in Fig. 31(d) based on the detected trading partner code, and detects the delivery destination code such as "N001" and the delivery destination name such as "Delivery destination 1" of the delivery destination associated with the trading partner code of "T001".

[0124] In this case, the display screen generation unit 26 lists and displays the delivery destination with the delivery destination name of "Delivery destination 1" and the delivery destination code of "N001" detected based on the trading partner code of "T001" in the data grid of the delivery destination search screen as shown in Fig. 31(a).

[0125] (Display control of the order history list screen for users with administrator authority of the operating company) Next, Fig. 32(a) is a diagram showing an example of an order history list screen displayed when a user with administrator authority of the operating company with the user ID "U004" logs in and specifies the display of the order history. The search unit 28 refers to the WebEDI user master 14 shown in Fig. 32(b) based on the user ID such as "U004" entered at the time of login, and refers to the operating company user flag. In this case, the operating company user flag for the user ID of "U004" is "TRUE". Therefore, the display screen generation unit 26 recognizes this user as a user of the operating company, and generates an order history list screen in which the input fields for the trading partner code, trading partner name, order date, and shipping date on the order history list screen shown in Fig. 32(a) are input fields where any desired value can be freely input.

[0126] For such an order history list screen, assume that, for example, a customer code of "T001" is entered by a user of the operating company with the user ID of "U004". In this case, the search unit 28 searches the order data storage area 59 shown in Fig. 32(c) stored in the order data storage area 59 of the storage unit 2 using the customer code of "T001" as a search key, and detects order data corresponding to the customer code of "T001". The display screen generation unit 26 displays the detected order data in a data grid in a list as shown in Fig. 32(a).

[0127] As described above, when the logged-in user is a user of the operating company, the display screen generation unit 26 displays the input fields such as the customer as input fields with variable values where desired customers and the like can be freely input and changed. Thereby, the user of the operating company can freely monitor or investigate business partners and the like.

[0128] (Display control of the supplier search screen for a user having the administrator authority of the operating company) Fig. 33(a) is a diagram showing an example of the supplier search screen displayed when a user who is an administrator of the operating company with the user ID of "U004" logs in and specifies a search for a supplier. When the logged-in user is a user of a business partner, as described above, the input field for the customer code on the supplier search screen is made non-displayed and restricted to a state where input is not allowed. However, when the logged-in user is a user of the operating company, the display screen generation unit 26 displays all the input fields on the supplier search screen, namely, the input field for the customer code, the input field for the supplier code, the input field for the supplier name, and the input field for the supplier kana name, and enables free input of desired values for each input field. Thereby, the user of the operating company can freely input a desired customer code or the like, obtain a list of suppliers corresponding to the input customer code, and monitor or investigate business partners and the like.

[0129] For example, as shown in Fig. 33(a), assume that the customer code "T001" is entered in the input field of "greater than or equal to ≧" of the customer code, and the customer code "T002" is entered in the input field of "less than or equal to ≦" of the customer code. In this case, the search unit 28 refers to the customer master 15 shown in Fig. 33(b), the customer delivery destination master 55 shown in Fig. 33(c), and the customer master 56 shown in Fig. 33(d), and detects the delivery destinations corresponding to the customer code "T001" with the delivery destination code "N001" and the delivery destination name "Delivery destination 1", and the delivery destinations corresponding to the customer code "T002" with the delivery destination code "N002" and the delivery destination name "Delivery destination 2". The display screen generation unit 26 displays the delivery destination data of the detected delivery destinations in a data grid as shown in Fig. 33(a).

[0130] (Display control of the order history list screen when the customer is not entered for a user with the administrator authority of the operating company) Fig. 34(a) is a diagram showing an example of the order history list screen displayed when a user who is an administrator of an operating company with the user ID "U004" logs in and no customer for which the display of the order history is desired is entered. Whether the user is an administrator of the operating company is determined by the search unit 28 based on the operating company user flag in the WebEDI user master 14 as shown in Fig. 34(b).

[0131] When the display of the order history list screen is specified by a user who is an administrator of the operating company and no customer is entered, the search unit 28 detects all the order data of all customers from the order data storage area 59 as shown in Fig. 34(c). The display screen generation unit 26 displays all the detected order data of all customers in the data grid of the order history list screen as shown in Fig. 34(a).

[0132] (Display control of the delivery destination search screen when the customer is not entered for a user with the administrator authority of the operating company) Figure 35(a) is a diagram showing an example of a delivery destination search screen that is displayed when a user who is an administrator of an operating company with a user ID of "U004" logs in and no customer to be searched for as a delivery destination is entered. Whether the user is an administrator of the operating company is determined by the search unit 28 based on the operating company user flag in the WebEDI user master 14, as described with reference to Figure 34(b).

[0133] When the display of the delivery destination search screen is specified by a user who is an administrator of the operating company and no customer to be searched for as a delivery destination is entered, the search unit 28 refers to the customer master 15 shown in Figure 35(b), the customer delivery destination master 55 shown in Figure 35(c), and the delivery destination master 56 shown in Figure 35(d), and detects delivery destination data such as the delivery destination code and delivery destination name of all customers from the storage unit 2. The display screen generation unit 26 displays the detected delivery destination data of all delivery destinations in a data grid on the delivery destination search screen as shown in Figure 35(a).

[0134] (Display control of order registration screen and product search screen at the time of order registration for customer users) Figure 36(a) is a diagram showing an example of an order registration screen that is displayed when a customer user with a user ID of "U001" logs in and specifies the registration of a product to be ordered. On the order registration screen, an input field for the customer code of the customer, an input field for the delivery destination code, an input field for the warehouse code of the warehouse where the product is stored, and input fields for the product code and product name are displayed. In this case, since the user with a user ID of "U001" is a customer user, the display screen generation unit 26 automatically enters and displays the customer code of "T001" and the customer name of "Customer 1" stored in the WebEDI user master 14 as fixed values in the input field for the customer on the order registration screen. As a result, it becomes impossible for the customer user to change the customer code, etc., and the products for which order registration is to be performed can be limited (restricted) to the products handled by the customer with the customer code of "T001".

[0135] In this state, the customer user inputs the product code of the product for which order registration is to be performed on the order registration screen. The example in Fig. 36(a) is an example where the product code "S003" is input. Here, the search unit 28 detects the product corresponding to the input product code by referring to the product master 16 shown in Fig. 36(c), the product configuration master 17 shown in Fig. 36(d), the customer product configuration master 18 shown in Fig. 36(e), and the customer master 15 shown in Fig. 36(f).

[0136] However, when referring to the masters 15 to 18 based on the product code "S003" and the customer code "T001" shown in Fig. 36(a), the product with the product code "S003" is mainly a product handled by the customer with the customer code "T002" as shown in Figs. 36(d) and 36(e). For this reason, the search unit 28 gives a notice (unregistered notice) to the display screen generation unit 26 that the product with the product code "S003" cannot be searched. When this unregistered notice is given, the display screen generation unit 26 generates an order registration screen displaying an error message such as "not registered in the product master" as shown in Fig. 36(a). In this case, the customer user will re-enter a product code such as "S001".

[0137] On the other hand, when product codes such as "S001" and "S002" are input by the customer user, the search unit 28 refers to the product configuration master 17 shown in Fig. 36(d), the customer product configuration master 18 shown in Fig. 36(e), and the customer master 15 shown in Fig. 36(f). Then, the search unit 28 determines that the products with the product codes "S001" and "S002" are products handled by the customer with the customer code "T001" (= products registered in the product master 16). When the display screen generation unit 26 obtains a determination result from the search unit 28 indicating that the product is a product handled by the customer, it reads out the product codes and product names of "S001" and "S002" from the product master 16 shown in Fig. 36(c) and displays them in a list on the product search screen as shown in Fig. 36(b).

[0138] (Display control of inventory inquiry screen for customer users) FIG. 37(a) is a diagram showing an example of an inventory inquiry screen displayed when a user of a customer with a user ID of "U001" logs in and specifies an inventory inquiry for a warehouse. On the inventory inquiry screen, there are an input field for the warehouse code of the warehouse for which the inventory inquiry is to be made, input fields for the product code, product name, and product kana name of the products stored in the warehouse, and a data grid in which the searched inventory data is displayed in a list.

[0139] In this case, the user who makes the inventory inquiry is a user of a customer with a user ID of "U001" and a customer code of "T001". Therefore, the search unit 28 sequentially refers to the customer master 15 shown in FIG. 37(e), the customer product configuration master 18 shown in FIG. 37(d), the product configuration master 17 shown in FIG. 37(c), and the product master 16 shown in FIG. 37(b) to detect the product code and product name corresponding to the customer code of "T001". In the case of this example, as products handled by the customer of "T001", a product with a product code of "S001" and a product name of "Product 1", and a product with a product code of "S002" and a product name of "Product 2" are detected.

[0140] Also, the search unit 28 refers to the warehouse master 20 via the customer-specific target warehouse master 19 shown in FIG. 27(b) based on the customer code of "T001" of the customer, and detects the warehouse code and warehouse name of the warehouse of the customer with the customer code of "T001".

[0141] The display screen generation unit 26 displays the warehouse code, warehouse name, product code, and product name detected by the search unit 28 in a list in the data grid of the inventory inquiry screen shown in FIG. 37(a).

[0142] (Display control of order registration screen and product search screen at the time of order registration for other customer users) FIG. 38(a) is a diagram showing an example of an order registration screen displayed when a user of a business partner with a user ID of "U003" logs in and specifies the registration of a product to be ordered. In this case, since the user with the user ID of "U003" is a business partner user, the display screen generation unit 26 automatically inputs and displays the business partner code of "T003" and the business partner name of "Customer 3" stored in the Web EDI user master 14 as fixed values in the input field for the business partner on the order registration screen. As a result, it becomes impossible for the business partner user to change the business partner code or the like, and the products for which order registration is to be performed can be limited (restricted) to the products handled by the business partner with the business partner code of "T003".

[0143] In this state, the business partner user inputs the product code of the product for which order registration is to be performed on the order registration screen. If the product code is not input, the search unit 28 sequentially refers to the business partner master 15 shown in FIG. 38(f), the business partner product configuration master 18 shown in FIG. 38(e), the product configuration master 17 shown in FIG. 38(d), and the product master 16 shown in FIG. 38(c) based on the business partner code of "T003". Then, the search unit 28 detects the product code and product name of the products handled by the business partner with the business partner code of "T003".

[0144] The display screen generation unit 26 displays the detected product code and product name in a list in the data grid of the product search screen as products handled by the business partner with the business partner code of "T003", as shown in FIG. 38(b).

[0145] (Display control of inventory inquiry screen for other business partner users) FIG. 39(a) is a diagram showing an example of an inventory inquiry screen displayed when a user of a business partner with a user ID of "U003" logs in, specifies an inventory inquiry of a warehouse, and the warehouse code of the warehouse to be searched and the product code of the product to be searched are not specified.

[0146] In this case, the user who makes the inventory inquiry is a user of the customer with the user ID "U003" and the customer code "T003". Therefore, the search unit 28 sequentially refers to the customer master 15 shown in FIG. 39(e), the customer product configuration master 18 shown in FIG. 39(d), the product configuration master 17 shown in FIG. 39(c), and the product master 16 shown in FIG. 39(b) to detect the product codes and product names corresponding to the customer code "T003". In the case of this example, as products handled by the customer with "T003", products with product code "S001" and product name "Product 1", products with product code "S002" and product name "Product 2", products with product code "S003" and product name "Product 3", and products with product code "S004" and product name "Product 4" are respectively detected.

[0147] Also, the search unit 28 refers to the warehouse master 20 via the customer-specific target warehouse master 19 shown in FIG. 27(b) based on the customer code "T003" of the customer, and detects the warehouse code and warehouse name of the warehouse of the customer with the customer code "T003". In this case, as the warehouse of the customer with the customer code "T003", the warehouse code of "SO001" and the warehouse name of "Warehouse 1" are detected.

[0148] The display screen generation unit 26 displays the warehouse code, warehouse name, product code, and product name detected by the search unit 28 in a list in the data grid of the inventory inquiry screen shown in FIG. 39(a).

[0149] (Display control of the order registration screen and product search screen for users with administrator authority of the operating company) FIG. 40(a) is a diagram showing an example of an order registration screen displayed when a user who is an administrator of an operating company with the user ID "U004" logs in and designates product order registration. When the logged-in user is a user of the operating company, as shown in FIG. 40(a), if the product code and product name of the product for which order registration is to be performed are not input on the order registration screen, the search unit 28 detects all the products registered in the product master 16 shown in FIG. 40(c).

[0150] Then, the display screen generation unit 26 displays a list of the product codes and product names of all the detected products in the data grid of the product search screen shown in Fig. 40(b).

[0151] (Display control of the inventory inquiry screen for users with administrator authority of the operating company) Fig. 41(a) is a diagram showing an example of an inventory inquiry screen displayed when a user who is an administrator of an operating company with a user ID of "U004" logs in and specifies an inventory inquiry for the products stored in each warehouse. When the logged-in user is a user of the operating company, as shown in Fig. 41(a), if the warehouse and product code for which the inventory inquiry is to be made are not entered in the inventory inquiry screen, the search unit 28 detects all the products registered in the product master 16 shown in Fig. 41(b). Also, the search unit 28 refers to the warehouse master 20 shown in Fig. 27(c) and detects the warehouse code and warehouse name of the warehouse in which each product is stored.

[0152] Then, the display screen generation unit 26 displays a list of the product codes and product names of all the detected products, together with the warehouse code and warehouse name of the warehouse in which each product is stored, in the data grid of the inventory inquiry screen shown in Fig. 41(a).

[0153] (Display control of the warehouse search dialog at the time of order registration for trading partner users) Fig. 42(a) is a diagram showing an order registration screen generated and displayed by the display screen generation unit 26 when a trading partner user with a user ID of "U001" logs in and specifies product order registration. In this case, since the logged-in user is a trading partner user, the display screen generation unit 26 automatically inputs and displays, for example, the trading partner code of "T001" and the trading partner name of "Customer 1" as fixed values that cannot be changed, on the order registration screen.

[0154] Also, in FIG. 42(a), assume that the user of the customer with the customer code of "T001" inputs the warehouse code of "SO003". Thereby, the search unit 28 refers to the customer master 15 shown in FIG. 42(c), the customer-specific target warehouse master 19 shown in FIG. 42(b), and the warehouse master 20 shown in FIG. 42(c) based on the customer code of "T001". Then, the search unit 28 detects the warehouse code of "SO001" and the warehouse name of "Warehouse 1" as the warehouse code and warehouse name corresponding to the customer code of "T001", and also detects the warehouse code of "SO002" and the warehouse name of "Warehouse 2".

[0155] Here, as shown in FIG. 42(a), in this case, the warehouse code input by the user of the customer with the customer code of "T001" is "SO003", but the warehouse codes corresponding to the customer code of "T001" retrieved by the search unit 28 are "SO001" and "SO002". That is, the warehouse with the input warehouse code of "SO003" is not the warehouse where the products handled by the customer with the customer code of "T001" are stored. For this reason, as shown in FIG. 42(a), the display screen generation unit 26 displays an error message such as "The warehouse master is not registered." on the order registration screen.

[0156] Also, at the same time, as shown in FIG. 42(b), the display screen generation unit 26 displays a warehouse search dialog in the input field of the warehouse code on the order registration screen. In the case of this example, the warehouse codes corresponding to the customer code of "T001" detected by the search unit 28 are "SO001" and "SO002". For this reason, the display screen generation unit 26 displays the warehouse search dialogs of "SO001" and "SO002". The user of the customer selects and inputs the desired warehouse code from among the warehouse codes of "SO001" and "SO002". Thereby, as illustrated in FIG. 36(b), the display screen generation unit 26 displays a list of products stored in the warehouse with the selected warehouse code.

[0157] (Display control of the inventory inquiry screen for the customer user) FIG. 43(a) is a diagram showing an example of an inventory inquiry screen displayed when a user of a business partner with a user ID of "U001" logs in and specifies an inventory inquiry for products stored in each warehouse. When the logged-in user is a business partner user, as shown in FIG. 43(a), if the warehouse for which the inventory inquiry is to be made and the product code of the product are not entered on the inventory inquiry screen, the search unit 28 refers to the customer master 15 shown in FIG. 43(b), the customer-specific target warehouse master 19, and the warehouse master 20 based on the customer code "T001" of the business partner of the user with the user ID of "U001". Then, the search unit 28 detects the warehouse code "SO001" and the warehouse name "Warehouse 1" corresponding to the customer code "T001", and also detects the warehouse code "SO002" and the warehouse name "Warehouse 2".

[0158] Also, as described with reference to FIG. 39, the search unit 28 sequentially refers to the customer master 15 shown in FIG. 39(e), the customer product configuration master 18 shown in FIG. 39(d), the product configuration master 17 shown in FIG. 39(c), and the product master 16 shown in FIG. 39(b) to detect the product code and product name corresponding to the customer code "T001". In the case of this example, as products handled by the customer with the customer code "T001", a product with a product code of "S001" and a product name of "Product 1" and a product with a product code of "S002" and a product name of "Product 2" are each detected.

[0159] The display screen generation unit 26 displays the warehouse code, warehouse name, product code, and product name detected by the search unit 28 in a list in the data grid of the inventory inquiry screen shown in FIG. 43(a).

[0160] (Display control of the warehouse search dialog at the time of order registration for other business partner users) FIG. 44(a) is a diagram showing an order registration screen generated and displayed by the display screen generation unit 26 when a user of a business partner with a user ID of "U003" logs in and specifies order registration for a product. In this case, since the logged-in user is a user of the business partner, the display screen generation unit 26 automatically inputs and displays, for example, the business partner code of "T003" and the business partner name of "Customer 3" as fixed values that cannot be changed, on the order registration screen.

[0161] Also, in the order registration screen shown in FIG. 44(a), it is assumed that the user of the business partner with the business partner code of "T003" did not input the warehouse code of the desired warehouse and the product code of the desired product. In this case, the search unit 28 refers to the business partner master 15 shown in FIG. 44(c), the business partner-specific target warehouse master 19 shown in FIG. 44(b), and the warehouse master 20 shown in FIG. 44(c) based on the business partner code of "T003". Then, the search unit 28 detects the warehouse code of "SO001" and the warehouse name of "Warehouse 1" as the warehouse code and warehouse name corresponding to the business partner code of "T003".

[0162] At the same time, as shown in FIG. 44(b), the display screen generation unit 26 displays a warehouse search dialog with the warehouse code of "SO001" and the warehouse name of "Warehouse 1" searched by the search unit 28 in the input field for the warehouse code on the order registration screen. When the warehouse search dialog with the warehouse code of "SO001" and the warehouse name of "Warehouse 1" is selected and operated by the user, the display screen generation unit 26 displays a list of products stored in the warehouse with the selected warehouse code, as exemplified in FIG. 36(b).

[0163] (Display control of inventory inquiry screen for users of other business partners) FIG. 45(a) is a diagram showing an example of an inventory inquiry screen that is displayed when a user of a business partner with a user ID of "U003" logs in and specifies an inventory inquiry for the products stored in each warehouse. When the logged-in user is a business partner user, as shown in FIG. 45(a), if the warehouse and product code for the product for which the inventory inquiry is to be made are not entered on the inventory inquiry screen, the search unit 28 refers to the customer master 15 shown in FIG. 45(b), the customer-specific target warehouse master 19, and the warehouse master 20 based on the business partner code "T003" of the business partner of the user with the user ID of "U003". Then, the search unit 28 detects the warehouse code "SO001" and the warehouse name "Warehouse 1" corresponding to the business partner code "T003".

[0164] Also, as described with reference to FIG. 39, the search unit 28 sequentially refers to the customer master 15 shown in FIG. 39(e), the customer product configuration master 18 shown in FIG. 39(d), the product configuration master 17 shown in FIG. 39(c), and the product master 16 shown in FIG. 39(b) to detect the product code and product name corresponding to the business partner code "T003".

[0165] The display screen generation unit 26 displays the warehouse code, warehouse name, product code, and product name detected by the search unit 28 in a list in the data grid of the inventory inquiry screen shown in FIG. 45(a).

[0166] (Display control of the warehouse search dialog at the time of order registration for a user having the administrator authority of the operating company) FIG. 46(a) is a diagram showing an order registration screen generated and displayed by the display screen generation unit 26 when a user who is an administrator of an operating company with a user ID of "U004" logs in and specifies product order registration. Also, the example of FIG. 46(a) shows a case where the warehouse code of a desired warehouse and the product code of a desired product are not entered by the user who is an administrator of the operating company.

[0167] In this case, the display screen generation unit 26 refers to the warehouse master 20 shown in FIG. 46(c), and as shown in FIG. 46(b), displays a warehouse search dialog for all warehouses from "SO001 (Warehouse 1)" to "SO005 (Warehouse 5)" on the order entry screen. Then, the display screen generation unit 26 displays a list of products stored in the warehouse with the warehouse code selected based on this warehouse search dialog.

[0168] (Other display controls for the inventory inquiry screen for users with administrator privileges of the operating company) FIG. 47(a) is a diagram showing another example of the inventory inquiry screen displayed when a user with the administrator privilege of the operating company with the user ID "U004" logs in and specifies an inventory inquiry showing the products stored in each warehouse. When the logged-in user is a user of the operating company, as shown in FIG. 47(a), if the warehouse and product code of the product for which the inventory inquiry is to be made are not entered on the inventory inquiry screen, the search unit 28 detects the warehouse codes and warehouse names of all warehouses registered in the warehouse master 20 shown in FIG. 47(b).

[0169] Also, as described with reference to FIG. 39, the search unit 28 sequentially refers to the customer master 15 shown in FIG. 39(e), the customer product configuration master 18 shown in FIG. 39(d), the product configuration master 17 shown in FIG. 39(c), and the product master 16 shown in FIG. 39(b) to detect the product codes and product names of all products.

[0170] The display screen generation unit 26 displays the warehouse codes, warehouse names, product codes, and product names detected by the search unit 28 in a list on the data grid of the inventory inquiry screen shown in FIG. 47(a).

[0171] (Display control for the delivery destination search screen for customers' users) FIG. 48(a) is a diagram showing the order entry screen in a state where a customer user with the user ID "U001" logs in and the delivery destination for which a search is desired is entered. Since the logged-in user is a customer user, the display screen generation unit 26 displays, for example, the customer code "T001" as a fixed value on the order entry screen as described above.

[0172] In this state, assume that, for example, a user with the customer code of "T001" inputs the supplier code of "N002". The search unit 28 refers to the customer master 15 shown in FIG. 48(c), the customer-supplier master 55 shown in FIG. 48(d), and the supplier master 56 shown in FIG. 48(e) based on the customer code of "T001". Then, the search unit 28 detects the supplier corresponding to the customer code of "T001".

[0173] Here, as shown in FIGS. 48(d) and 48(e), the supplier corresponding to the customer code of "T001" is "Supplier 1" with the supplier code of "N001". However, as shown in FIG. 48(a), the supplier code of the supplier input on the order registration screen as the supplier for which the search is desired is "N002". For this reason, the display screen generation unit 26 displays an error message such as "The supplier master is not registered." as shown in FIG. 48(a), and restricts the data to be disclosed to the customer user. Thereby, it is possible to prevent the inconvenience of disclosing the suppliers of other customers to the customer user and maintain the security of the EDI system.

[0174] The customer user for whom such an error message is displayed re-enters the supplier code of their own supplier, for example, "N001" or the like. Thereby, the search unit 28 refers to the customer master 15 shown in FIG. 48(c), the customer-supplier master 55 shown in FIG. 48(d), and the supplier master 56 shown in FIG. 48(e), and detects the supplier code of "N001" and the supplier name of "Supplier 1". The display screen generation unit 26 displays the supplier code and supplier name of the detected supplier in a list in the data grid of the supplier search screen shown in FIG. 48(b).

[0175] (Display control of the supplier search screen for users of other customers) Fig. 49(a) is a diagram showing an order registration screen in a state where a user of a business partner with a user ID of "U003" logs in and does not enter a delivery destination for which a search is desired. Since the logged-in user is a user of the business partner, the display screen generation unit 26 displays, on the order registration screen, for example, the business partner code of "T003" as a fixed value as described above.

[0176] In this case, since the delivery destination for which a search is desired is not entered, the search unit 28 refers to the customer master 15 shown in Fig. 49(c), the customer delivery destination master 55 shown in Fig. 49(d), and the delivery destination master 56 shown in Fig. 49(e) based on the business partner code of "T003", which is the business partner code of the user with the user ID of "U003". Then, the search unit 28 detects a delivery destination with a delivery destination code of "N003" and a delivery destination name of "Delivery Destination 3" as the delivery destination corresponding to the business partner code of "T003".

[0177] The display screen generation unit 26 displays the delivery destination code and the delivery destination name of the delivery destination detected by the search unit 28 in a data grid on the delivery destination search screen shown in Fig. 49(b).

[0178] (Display control of the delivery destination search screen for a user having the administrator authority of the operating company) Fig. 50(a) is a diagram showing an order registration screen in a state where a user having the administrator authority of the operating company with a user ID of "U004" logs in and does not enter a delivery destination for which a search is desired. Since the logged-in user is a user having the administrator authority of the operating company, the display screen generation unit 26 displays the input field for the business partner code on the order registration screen in a state where a desired business partner code can be input as described above.

[0179] In this case, since the logged-in user is a user with administrator authority of the operating company and the delivery destination for which a search is desired is not entered, the search unit 28 refers to the customer master 15 shown in Fig. 49(c) to detect all customer codes and customer names, and refers to the customer delivery destination master 55 shown in Fig. 50(c) to detect the delivery destinations corresponding to each customer. The display screen generation unit 26 displays in a data grid of the delivery destination search screen shown in Fig. 50(b) a list of the customer code, customer name, delivery destination code, and delivery destination name detected by the search unit 28.

[0180] (Display control of the order history list screen for the customer's user) Next, the display control of the order history list screen for the customer's user will be described. First, Fig. 51(a) shows an example of order data stored in the order data storage area 59 of the storage unit 2. As shown in Fig. 51(a), the order data storage area 59 stores order data including a slip number, data classification, user transaction classification, and transaction classification name. Also, Fig. 51(b) shows an example of the display target transaction classification master 58. As shown in Fig. 51(b), the display target transaction classification master 58 stores the data classification and the user transaction classification.

[0181] The data classification and customer classification added to this transaction classification master 57 and the order data indicate whether the order data can be displayed and used. For example, for the customer's user, the display and use of order data with a data classification of "10" and a user transaction classification of "10", and order data with a data classification of "20" and a user transaction classification of "10" are permitted. Also, for the customer's user, the display and use of order data with a data classification of "10" and a user transaction classification of "20" are not permitted.

[0182] Therefore, when a user of a customer with a user ID of "U003" logs in and specifies the display of the order history, for example, the search unit 28 refers to the order data storage area 59 in Fig. 51(a), and detects the order data with the slip number of "D001" where the data classification is "10", the user transaction classification is "10", and the customer classification name is "warehouse-out order", and the order data with the slip number of "D003" where the data classification is "20", the user transaction classification is "10", and the customer classification name is "sales". The display screen generation unit 26 displays the order data with the slip numbers of "D001" and "D003" detected by the search unit 28 in the data grid of the order history list screen shown in Fig. 51(c).

[0183] (Display control of the order history list screen for a user with the administrator authority of the operating company) On the contrary, when a user with the administrator authority of the operating company with a user ID of "U004" logs in and specifies the display of the order history, for example, the search unit 28 refers to the display target transaction classification master 58 in Fig. 52(b) and the order data storage area 59 in Fig. 52(a), and detects the order data of all slip numbers. The display screen generation unit 26 displays all the order data with the slip numbers of "D001" to "D003" detected by the search unit 28 in the data grid of the order history list screen shown in Fig. 52(c).

[0184] (Display control according to user authority) Next, the flow of the above-described display control according to user authority in the management device 1 of the embodiment will be described. The flowcharts in Figs. 53 to 57 are a series of flowcharts, which show the flow of the above-described display control according to user authority in the management device 1 of the embodiment. First, in step S51 of Fig. 53, the control unit 3 performs user authentication processing based on the user ID and password of the logged-in user, and when it is authenticated that the user is a regular user such as a user with the administrator authority of the operating company or a customer user, the process proceeds to step S52.

[0185] In step S52, the search unit 28 refers to the operator company user flag in the Web EDI user master 14 shown in FIG. 30(b) etc. based on the user ID of the logged-in user, and determines whether the logged-in user is an operator company administrator user. If it is determined that the logged-in user is an operator company administrator user (step S52: Yes (TRUE)), the process proceeds to step S54 of the flowchart in FIG. 54.

[0186] On the other hand, if it is determined that the logged-in user is a trading partner user (step S52: No (FALSE)), the process proceeds to step S53. In step S53, the search unit 28 acquires the trading partner code of the Web EDI user master 14. Thereby, the process proceeds to step S60 of the flowchart in FIG. 55.

[0187] Next, in step S54 of the flowchart in FIG. 54, the search unit 28 determines the keys and masters used for the management purpose corresponding to the startup screen and processing content. That is, in the case of the product management purpose (settings associated with product control), the search unit 28 advances the process to step S55 and determines the keys and masters to be used.

[0188] Keys and masters to be used determined in step S55 <Key subject to permission> Product configuration PT code / Product code <Search dialog target> <Master subject to permission control> Product master 16

[0189] Also, in the case of the warehouse management purpose (settings associated with warehouse control), the search unit 28 advances the process to step S56 and determines the keys and masters to be used.

[0190] Keys and masters to be used determined in step S56 <Key subject to permission> Warehouse code <Search dialog target> <Master subject to permission control> Warehouse Master 20

[0191] Also, when the search unit 28 is for the purpose of supplier management (settings associated with supplier control), the process proceeds to step S57, and the keys and masters to be used are determined.

[0192] The keys and masters to be used, determined in step S57 <Key subject to permission> Supplier code <Search dialog target> <Master subject to permission control> Supplier master 56

[0193] Also, when the search unit 28 is for the purpose of transaction content management (settings associated with transaction category control), the process proceeds to step S58, and the keys and masters to be used are determined.

[0194] The keys and masters to be used, determined in step S58 <Key subject to permission> Data category + User transaction category <Search dialog target> <Master subject to permission control> Transaction category master 59

[0195] Next, in step S59, in this case, since the logged-in user is an administrator user of the operating company, the search unit 28 determines that all "keys subject to permission" are permitted, and the process proceeds to step S70 of the flowchart in FIG. 56.

[0196] On the other hand, when it is determined that the logged-in user is a customer user, and the supplier code is acquired in step S53 and the process proceeds to step S60 of the flowchart in FIG. 55, the search unit 28 branches the process to step S61 or step S62 according to the transaction relationship of the customer corresponding to the startup screen.

[0197] That is, when the business relationship of the trading partner corresponding to the startup screen is a sales relationship of goods (or services), the search unit 28 proceeds to step S61 and recognizes the trading partner code as the customer code. On the other hand, when the business relationship of the trading partner corresponding to the startup screen is a procurement relationship of goods (or services), the search unit 28 proceeds to step S62 and recognizes the trading partner code as the supplier code.

[0198] Next, in step S63, the search unit 28 branches the process for the management purpose corresponding to the startup screen and the processing content. That is, when it is for the purpose of product management (settings associated with product control), the search unit 28 proceeds to step S64 and determines the keys and masters to be used.

[0199] Keys and masters to be used determined in step S64 <Key subject to permission> Product configuration PT code / Product code <Key master subject to permission by trading partner> Customer product configuration master 18 <Search dialog target> <Master subject to permission control> Product master 16

[0200] Also, when it is for the purpose of warehouse management (settings associated with warehouse control), the search unit 28 proceeds to step S65 and determines the keys and masters to be used.

[0201] Keys and masters to be used determined in step S65 <Key subject to permission> Warehouse code <Key master subject to permission by trading partner> Customer-specific target warehouse master 19 <Search dialog target> <Master subject to permission control> Warehouse master 20

[0202] Also, when it is for the purpose of consignee management (settings associated with consignee control), the search unit 28 proceeds to step S66 and determines the keys and masters to be used.

[0203] The key and master to be used, determined in step S66 <Key to be permitted> Destination code <Customer-specific key master to be permitted> Customer destination master 55 <Search dialog target> <Master subject to permission control> Destination master 56

[0204] Also, in the case of the purpose of transaction content management (settings associated with transaction category control), the search unit 28 proceeds to step S67 and determines the key and master to be used.

[0205] The key and master to be used, determined in step S67 <Key to be permitted> Data category + user transaction category <Customer-specific key master to be permitted> Display target transaction category master 58 <Search dialog target> <Master subject to permission control> Transaction category master 59

[0206] Next, in step S68, the search unit 28 obtains a list of "keys to be permitted", such as product configuration PT codes / product codes, warehouse codes, or destination codes, based on the customer code from the "customer-specific key master to be permitted", such as the above-mentioned customer product configuration master 18 or customer-specific target warehouse master 19. Then, in step S69, the search unit 28 determines that the obtained "keys to be permitted" are permitted. As a result, the process proceeds to step S81 of the flowchart in FIG. 57.

[0207] Next, when the logged-in user is an administrator user of the operating company, when the process proceeds from step S59 of the flowchart in FIG. 54 to step S70 of the flowchart in FIG. 56, the search unit 28 determines that all "keys to be permitted" are permitted in step S70 and proceeds to step S71.

[0208] In step S71, the search unit 28 determines whether there is an extraction condition item for the code corresponding to the business partner code on the screen. If there is an extraction condition item for the code corresponding to the business partner code on the screen (step S71: Yes), the search unit 28 proceeds to step S72 and determines whether the condition of "code corresponding to the business partner code" on the screen is specified.

[0209] If the condition of "code corresponding to the business partner code" on the screen is specified (step S72: Yes), the process proceeds to step S73, and the search unit 28 adds the specified business partner code to the "code corresponding to the business partner code" as an acquisition condition for the target data.

[0210] On the other hand, if it is determined in step S71 that there is no extraction condition item for the "code corresponding to the business partner code" on the screen (step S71: No), and if it is determined in step S72 that the condition of "code corresponding to the business partner code" on the screen is not specified (step S72: No), the process proceeds to step S78. In step S78, the search unit 28 proceeds to step S74 with the "code corresponding to the business partner code" being "no condition" as an acquisition condition for the target data.

[0211] In step S74, the search unit 28 determines whether there is an extraction condition item for the "permission target key" for the "master subject to permission control" on the screen. If there is an extraction condition item for the "permission target key" for the "master subject to permission control" on the screen (step S74: Yes), the search unit 28 branches the process according to the specification method of the "permission target key" in step S75. That is, if the specification method of the "permission target key" is "direct input", the search unit 28 proceeds to step S76 and adds the condition of the specified "permission target key" as an acquisition condition for the target data. Then, in step S77, the search unit 28 extracts the target data according to the conditions of the "code corresponding to the business partner code" and the "permission target key" set as acquisition conditions, and ends the processing of the series of flowcharts.

[0212] Also, in step S75, when the designation method of the "permission target key" is the "search dialog", the search unit 28 proceeds to step S80, and as the acquisition condition of the data targeted by the search dialog, it sets the display of all items and enables designation, and then proceeds to step S76. In step S76, the search unit 28 adds the condition of the designated "permission target key" as the acquisition condition of the target data as described above. Then, in step S77, the search unit 28 extracts the target data according to the conditions of the "code corresponding to the customer code" and the "permission target key" set as the acquisition conditions, and ends the processing of the series of flowcharts.

[0213] On the other hand, in step S74 described above, when it is determined that there is no extraction condition item for the "permission target key" for the "master subject to permission control" on the screen (step S74: No), the search unit 28 proceeds to step S79. In step S79, the search unit 28 sets the "permission target key" as "no condition" as the acquisition condition of the target data, and proceeds to step S77. Then, in step S77, the search unit 28 extracts the target data according to the conditions of the "code corresponding to the customer code" and the "permission target key" set as the acquisition conditions, and ends the processing of the series of flowcharts.

[0214] Next, in step S69 of the flowchart in FIG. 55, when it is determined that the acquired "permission target key" is permitted, the search unit 28 proceeds to step S82 via step S81 of the flowchart in FIG. 57. In step S82, the search unit 28 determines whether there is an extraction condition item for the code corresponding to the customer code on the screen. When there is an extraction condition item for the code corresponding to the customer code on the screen (step S82: Yes), the search unit 28 proceeds to step S83 and determines whether to continue displaying the customer code on the screen. Also, when there is no extraction condition item for the code corresponding to the customer code on the screen (step S82: No), the search unit 28 proceeds to step S85.

[0215] When the display of the customer code on the screen continues (Step S83: Yes), in Step S84, the search unit 28 sets the customer code acquired in Step S53 to the "code corresponding to the customer code" on the screen and makes it unchangeable, and proceeds to Step S85.

[0216] When the display of the customer code on the screen does not continue (Step S83: No), in Step S91, the search unit 28 hides the "code corresponding to the customer code" on the screen and proceeds to Step S85.

[0217] In Step S85, the search unit 28 adds the customer code acquired in Step S53 to the "code corresponding to the customer code" as a condition for acquiring target data, and proceeds to Step S86.

[0218] In Step S86, the search unit 28 determines whether there is an extraction condition item for the "permission target key" for the "master subject to permission control" on the screen. When there is an extraction condition item for the "permission target key" for the "master subject to permission control" on the screen (Step S86: Yes), the search unit 28 proceeds to Step S87 and branches the process according to the specification method of the "permission target key". On the contrary, when there is no extraction condition item for the "permission target key" for the "master subject to permission control" on the screen (Step S86: No), the search unit 28 proceeds to Step S94, adds the "permission target key" acquired in Step S69 as a condition for acquiring target data, and proceeds to Step S90. Then, in Step S90, the search unit 28 extracts target data according to the conditions of the "code corresponding to the customer code" and the "permission target key" set as acquisition conditions, and ends the processing of the series of flowcharts.

[0219] That is, when the method for specifying the "permission target key" is "direct input", the search unit 28 proceeds to step S88 and determines whether it is the content included in the "permission target key" acquired in step S69. If it is the content included in the "permission target key" acquired in step S69 (step S88: Yes), the search unit 28 adds, in step S89, the condition of the "permission target key" specified as the acquisition condition of the target data, and in step S90, extracts the target data according to the conditions of the "code corresponding to the trading partner code" and the "permission target key" set as the acquisition conditions, and ends the processing of the series of flowcharts.

[0220] On the contrary, if it is determined in step S88 that it is not the content included in the "permission target key" acquired in step S69 (step S88: No), as described with reference to FIG. 42(a) etc., the display screen generation unit 26 performs a predetermined error display (step S93) and ends the series of flowcharts.

[0221] Next, in step S87 described above, if it is determined that the method for specifying the "permission target key" is "search dialog", the search unit 28 proceeds to step S92 and enables only the display or specification of the "permission target key" acquired in step S69 as the acquisition condition of the data of the "search dialog target". After that, the search unit 28 proceeds to step S89 and adds the condition of the "permission target key" specified as the acquisition condition of the target data. Then, the search unit 28 extracts the target data according to the conditions of the "code corresponding to the trading partner code" and the "permission target key" set as the acquisition conditions in step S90, and ends the processing of the series of flowcharts.

[0222] (Effects of the Embodiment) An operating company that provides an EDI system via the management device 1 needs to manage not only trading partners but also users belonging to the trading partners, and the management cost of the operating company is very high. In addition, when a trading partner needs to add, modify, or delete a user, it has to request this from the operating company, and there are problems with the accuracy and real-time nature of user settings.

[0223] Also, if each user belonging to a trading partner is not invalidated even when the operating company invalidates the status of the trading partner, there will be a problem that users who should not be able to use the EDI system can still be used. In addition, if a user registration is associated with a trading partner different from the trading partner that should originally be registered due to a setting mistake of the operating company, this user will have a problem that he / she can view the trading partner information of the trading partner to which he / she does not belong.

[0224] Here, since it is difficult for one operating company to manage, it is considered to entrust each trading partner with user management authority. However, if the user management authority is unconditionally entrusted to the trading partner, the entrusted trading partner will have no restrictions on the user management authority, resulting in a problem that it can manage even the users of other trading partners. In addition, since the entrusted trading partner can register users without limitation, there will be a problem that many unregistered users will be registered over time, increasing the security risk. Therefore, it is necessary to entrust the trading partner with restricted user management authority.

[0225] For these reasons, the management device 1 of the embodiment sets the user management authority for registering or editing user information including expiration date information indicating the expiration date of having a regular user authority to the trading partner. Thereby, the user management authority can be entrusted to each trading partner, and the management cost of the e-commerce trading system managed by the operating company of the management device 1 can be reduced. In addition, since the user management authority can be entrusted to a trustworthy trading partner, the distribution of the management cost can be safely performed. In addition, since the trading partner entrusted with the user management authority can perform user management by itself, the user management can be performed accurately and in real time.

[0226] In addition, the user management authority can be set for each administrator or person in charge of a desired user group of each trading partner. Thereby, the user management authority can be entrusted to the administrator or person in charge of the desired user group, and the detailed distribution setting of the management cost and the further improvement of the security can be achieved.

[0227] In addition, since the upper limit of the number of newly registrable users can be set for each trading partner, for example, if a trading partner registers users without limit, over time, many unregistered users may be registered, preventing the inconvenience of increased security risks.

[0228] In addition, for each trading partner, a status indicating "valid" or "invalid" for the right to use the EDI system is attached and managed. When the status of a trading partner is set to "invalid", the expiration date of the user ID of each user belonging to this trading partner is updated to "expired" to invalidate the right to use the EDI system. As a result, by setting the status of a trading partner to "invalid", the rights of each user belonging to this trading partner to use the EDI system can be invalidated all at once, further reducing the management cost. Also, even if a user management mistake occurs in the operating company, the security risk can be reduced.

[0229] In addition, the management device 1 of the embodiment determines whether the user who has logged in to the EDI system is the operating company or a trading partner that is a front-end environment introduction company based on the user ID at the time of login (judges user rights) from the WebEDI user master 14. Then, based on this user right, the control of input items or the data that can be acquired is controlled. As a result, for many users using the EDI system, it is possible to accurately and easily control the handling of data according to the rights of each user, reducing the management cost.

[0230] Specifically, when the logged-in user is a user of a trading partner, the input items used in the front-end environment job are made non-inputtable or non-displayable. As a result, the disclosure of data, etc. can be controlled according to the permission settings assigned to each trading partner. Also, when the logged-in user is a user of the administrator of the operating company, the input items used in the front-end environment job can be freely input or displayed. As a result, it is possible to conduct business across the board without being limited to the rights of trading partners (it is possible to conduct all businesses).

[0231] [Contribution to the United Nations Sustainable Development Goals (SDGs)] According to the present embodiment, since it is possible to contribute to promoting business efficiency and appropriate business judgment of a company, it is possible to contribute to Goals 8 and 9 of the SDGs.

[0232] In addition, according to the present embodiment, since it is possible to contribute to reducing waste loss and promoting paperless and digitization, it is possible to contribute to Goals 12, 13, and 15 of the SDGs.

[0233] In addition, according to the present embodiment, since it is possible to contribute to strengthening control and governance, it is possible to contribute to Goal 16 of the SDGs.

[0234] [Other Embodiments] The present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims, in addition to the above-described embodiments.

[0235] For example, among the processes described in the embodiment, all or part of the processes described as being automatically performed may be manually performed, or all or part of the processes described as being manually performed may be automatically performed by a known method.

[0236] In addition, regarding the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and the drawings, they can be arbitrarily changed unless otherwise specified.

[0237] Regarding the management device 1, each component shown in the figure is a functional concept, and it is not necessarily physically configured as shown in the figure.

[0238] For example, regarding the processing functions provided by the management device 1, particularly each processing function performed by the control unit 3, all or any part thereof may be realized by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. The program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing the information processing device to execute the processing described in each embodiment, and is mechanically read by the management device 1 as necessary. That is, in a storage unit such as a ROM or an HDD, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM, and constitutes the control unit 3 or the control unit 43 in cooperation with the CPU.

[0239] In addition, the management program of this management device 1 may be stored in another server device connected to the management device 1 via an arbitrary network, and all or part of it can be downloaded as necessary.

[0240] Also, the management program for executing the processing described in each embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical Disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0241] In addition, a "program" is a data processing method described in any language or description method, regardless of the form such as source code or binary code. Note that the "program" is not necessarily limited to being configured in a single form, and also includes those that are distributed and configured as a plurality of modules or libraries, or those that achieve their functions in cooperation with separate programs typified by an OS. Regarding the specific configuration, reading procedure, and installation procedure after reading for the recording medium in the management device 1 shown in the embodiment, well-known configurations and procedures can be used.

[0242] The storage unit 2 is a storage means such as a memory device such as a RAM or a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and stores various programs, tables, databases, and web page files used for various processes and website provision.

[0243] In addition, the management device 1 may be configured by an information processing device such as a known personal computer device or a workstation, or may be configured by an information processing device to which an arbitrary peripheral device is connected. Further, the information processing device may be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

[0244] Furthermore, the specific forms of distribution and integration of the devices are not limited to those illustrated, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various additions or function additions. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Industrial Applicability

[0245] The present invention is applicable to any industry as long as it is an industry that conducts e-commerce via a network.

Explanation of Signs

[0246] 1 Management device of the operating company 2 Memory unit 3 Control unit 4 Communication interface unit 5 Input / output interface unit 6 Input device 7 Output device 8 Network 9 Network 11 WebEDI trading partner classification master 12 WebEDI trading partner master 13 WebEDI user group master 14 WebEDI user master 15 Customer master 16 Product master 17 Product configuration master 18 Customer product configuration master 19 Target warehouse master by customer 20 Warehouse master 21 Communication control unit 22 User management authority setting unit 23 Data generation unit 24 Discrimination unit 25 Memory control unit 26 Display screen generation unit 27 Status setting unit 28 Search unit 55 Customer delivery destination master 56 Delivery destination master 57 Transaction type master 58 Display target transaction type master 59 Order data storage area 80 Terminal device constituting the back-yard environment of the operating company 81 Communication interface unit 82 Memory unit for business data for data management 90 Collaboration tool connecting the front-end environment and the back-yard environment of the operating company 100 Customer's terminal device 200 Supplier's terminal device

Claims

1. A communication control unit that controls a communication unit to mediate the transmission and reception of various data between terminal devices of each trading partner that conducts e-commerce via a network, A user type determination unit that determines whether the logged-in user is a user of an operating company that operates the system for conducting the e-commerce or a user of the trading partner that uses the e-commerce system, When a determination result indicating that the user is a user of the trading partner is obtained, a display screen is generated that displays the unique information of the trading partner used as a search key for retrieving information related to the trading partner from the storage unit as an unchangeable fixed value. When a determination result indicating that the user is a user of the operating company is obtained, a display screen is generated that displays the unique information of the trading partner used as a search key for retrieving information related to the trading partner from the storage unit, which is input by the user of the operating company, as a changeable variable value. A display screen generation unit, A management device having the above.

2. When the display screen generation unit obtains a determination result indicating that the user is a user of the trading partner, the display screen generation unit generates the display screen in which the input field for the unique information of the desired trading partner serving as the search key is not displayed. When the display screen generation unit obtains a determination result indicating that the user is a user of the operating company, the display screen generation unit generates the display screen in which the input field for the unique information of the desired trading partner serving as the search key is displayed, The management device according to claim 1, characterized in that.

3. Further provided with a search unit that searches the storage unit for data stored in association with the unique information of the trading partner, The display screen generation unit generates the display screen including the searched data, The management device according to claim 1 or claim 2, characterized in that.

4. The search unit searches for at least one of the data of the order history, delivery destination, handled goods or services, inventory goods, and warehouse associated with the unique information of the trading partner, The display screen generation unit generates the display screen including the retrieved data. The management device according to claim 3, characterized in that.

5. A first storage unit, a first communication device that communicates with a terminal device of each trading partner that conducts an e-commerce transaction via a network, and communicates with a terminal device of a user of an operating company that operates the system for conducting the e-commerce transaction via the network, A second storage unit, a second communication device that communicates with the terminal device of the user of the operating company via the network, A cooperation device that synchronizes the data stored in the first storage unit and the data stored in the second storage unit at a predetermined timing, The first communication device, A communication control unit that controls a communication unit so as to mediate transmission and reception of various data between terminal devices of each trading partner that conducts an e-commerce transaction via a network, A user type determination unit that determines whether a logged-in user is a user of an operating company that operates the system for conducting the e-commerce transaction or a user of the trading partner that uses the e-commerce system, When a determination result indicating that the user is a user of the trading partner is obtained, a display screen is generated in which the unique information of the trading partner, which is used as a search key for retrieving information related to the trading partner from the storage unit, is displayed as a fixed value that cannot be changed. When a determination result indicating that the user is a user of the operating company is obtained, a display screen is generated in which the unique information of the trading partner, which is used as a search key for retrieving information related to the trading partner from the storage unit and is input by the user of the operating company, is displayed as a variable value that can be changed. A display screen generation unit, An e-commerce system characterized by having.

6. A communication control step in which a communication control unit controls a communication unit so as to mediate transmission and reception of various data between terminal devices of each trading partner that conducts an e-commerce transaction via a network, A user type discrimination step in which a user type discrimination unit discriminates whether the logged-in user is a user of the operating company that operates the system for the electronic commerce or a user of the trading partner that uses the electronic commerce system, A display screen generation step in which, when a discrimination result indicating that the user is the trading partner is obtained, a display screen is generated in which the unique information of the trading partner, which is used as a search key for searching the storage unit for information related to the trading partner, is displayed as a fixed value that cannot be changed, and when a discrimination result indicating that the user is a user of the operating company is obtained, a display screen is generated in which the unique information of the trading partner, which is used as a search key for searching the storage unit for information related to the trading partner input by the user of the operating company, is displayed as a variable value that can be changed. A management method having the above.

7. A computer, A communication control unit that controls a communication unit so as to mediate the transmission and reception of various data between terminal devices of each trading partner that conducts electronic commerce via a network, A user type discrimination unit that discriminates whether the logged-in user is a user of the operating company that operates the system for the electronic commerce or a user of the trading partner that uses the electronic commerce system, When a discrimination result indicating that the user is the trading partner is obtained, causing the computer to function as a display screen generation unit that generates a display screen in which the unique information of the trading partner, which is used as a search key for searching the storage unit for information related to the trading partner, is displayed as a fixed value that cannot be changed, and when a discrimination result indicating that the user is a user of the operating company is obtained, generating a display screen in which the unique information of the trading partner, which is used as a search key for searching the storage unit for information related to the trading partner input by the user of the operating company, is displayed as a variable value that can be changed. A management program characterized by the above.

Images