JP2023177546A - Management apparatus, e-commerce transaction system, management method, and management program - Google Patents

Abstract

To appropriately manage an e-commerce transaction system on the basis of a valid period assigned to 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 notification control unit issues a warning that an authorized user right is to be expired, from a date, which is a predetermined number of days before an expiration date of the authorized user right, on the basis of valid period information indicating a valid period of a user right to officially use an e-commerce transaction, the valid period information being included in user information stored in a storage unit. An e-commerce transaction system can be properly managed on the basis of the valid period assigned to each user, thereby enabling smooth and sound operation of the e-commerce transaction system.SELECTED DRAWING: Figure 26

Description

The present invention relates to a management device, an electronic commerce system, a management method, and a management program.

Today, electronic commerce systems are built on server devices on the Web (World Wide Web), and each business partner uses the WebEDI (Electronic Data Interchange) system to conduct electronic commerce by sending and receiving data via a web browser on a terminal device. )It has been known.

As a background technology related to such a WebEDI system, Patent Document 1 (Japanese Unexamined Patent Publication No. 2003-091658) discloses an electronic commerce system aimed at efficiently realizing transactions between buyers and sellers. .

This electronic commerce system allows one trading entity to establish a trading venue as the owner, and allows multiple trading entities to participate in the trading venue in accordance with the owner's requests. This trading venue accepts the setting of a group for trading specific products or a group consisting of specific trading entities, and creates an environment in which only members within the group can conduct transactions in line with the group's objectives. Form.

This allows trading entities to freely establish sales-type markets, purchasing-type markets, trading company-type markets, general markets, etc. as they wish, and allows them to flexibly set up groups for specific products. Can be done.

JP2003-091658A

Here, a user who uses an electronic commerce system is often given an expiration date indicating the authority to use the electronic commerce system. If the electronic commerce system is not operated properly based on the expiration date, a user who needs to continue using the electronic commerce system, for example, will be unable to use the electronic commerce system after the expiration date. Furthermore, a user who has lost legitimate authority to use the electronic commerce system due to transfer or retirement may continue to be able to use the electronic commerce system even after the expiration date. When such inconveniences occur, the smooth and sound operation of the electronic commerce system is hindered.

The present invention has been made in view of the above-mentioned problems, and provides a management device, an electronic commerce system, a management method, and a management method that can appropriately operate an electronic commerce system based on the expiration date given to each user. The purpose is to provide management programs.

In order to solve the above-mentioned problems and achieve the purpose, a management device according to the present invention has a communication unit that mediates the transmission and reception of various data between the terminal devices of each business partner conducting electronic commerce via a network. and the date on which the authorized user authority expires, based on the expiration date information indicating the expiration date of the user authority to legitimately use electronic commerce, which is included in the user information stored in the storage unit. and a notification control unit for notifying a warning indicating that regular user authority will expire from a date a predetermined number of days before.

In addition, in order to solve the above-mentioned problems and achieve the purpose, an electronic commerce system according to the present invention includes a first storage unit, and provides communication between terminal devices of each business partner that conducts electronic commerce via a network. and a first communication device that performs communication via a network with a terminal device of a user of an operating company that operates an electronic commerce system, and a second storage unit, and is operated via a network. A second communication device that performs communication with a terminal device of a user in the company, and data stored in the first storage unit and data stored in the second storage unit at a predetermined timing. the first communication device controls the communication unit to mediate the transmission and reception of various data between the terminal devices of each business partner conducting electronic commerce via the network. A communication control unit and a predetermined number of days before the expiration date of the authorized user authority based on the expiration date information indicating the expiration date of the user authority to legitimately use electronic commerce included in the user information stored in the storage unit. and a notification control unit for notifying a warning indicating that regular user authority will expire from a previous date.

In addition, in order to solve the above-mentioned problems and achieve the purpose, the management method according to the present invention includes a communication control unit that transmits and receives various data between terminal devices of each business partner conducting electronic commerce via a network. a communication control step for controlling a communication unit to mediate the above, and a communication control step in which the communication control unit controls the communication unit based on expiration date information indicating the expiration date of the user authority to legitimately use electronic commerce included in the user information stored in the storage unit. and a notification control step of notifying a warning indicating that the regular user authority will expire from a predetermined number of days before the date on which the regular user authority will expire.

In addition, in order to solve the above-mentioned problems and achieve the purpose, the management program according to the present invention uses a computer to mediate the transmission and reception of various data between the terminal devices of each business partner conducting electronic commerce via the network. The communication control unit controls the communication unit to ensure that the legitimate user authority is valid based on the expiration date information indicating the expiration date of the user authority to legitimately use e-commerce, which is included in the user information stored in the storage unit. It functions as a notification control unit that notifies a warning indicating that regular user authority will expire from a predetermined number of days before the expiration date.

The present invention can appropriately operate an electronic commerce system based on the expiration date given to each user. Therefore, the electronic commerce system can be operated smoothly and soundly.

FIG. 1 is a system configuration diagram of an electronic commerce system (EDI system) in which a management device according to an embodiment mediates electronic commerce. FIG. 2 is a system configuration diagram of an operating company equipped with a management device. FIG. 3 is a block diagram showing the hardware configuration of the management device according to the embodiment. FIG. 4 is a diagram showing an example of a WebEDI customer classification master. FIG. 5 is a diagram showing an example of a WebEDI customer master. FIG. 6 is a diagram showing an example of a WebEDI user group master. FIG. 7 is a diagram showing an example of a WebEDI user master. FIG. 8 is a diagram for explaining a screen displayed to each administrator or person in charge of a user group. FIG. 9 is a diagram showing an example of a customer master maintenance screen. FIG. 10 is a diagram illustrating an example of an operating company user master maintenance screen. FIG. 11 is a diagram illustrating an example of an operating company customer user master maintenance screen. Figure 12 shows the customer user master maintenance screen for business partners that is displayed when activated by a customer administrator user, and the customer user master maintenance screen for business partners that is displayed when activated by a supplier administrator user. It is a figure showing an example. FIG. 13 is a flowchart showing the flow of registration operations when an operating company administrator newly registers an operating company user. FIG. 14 is a diagram showing an example of a login screen and data referenced by the WebEDI user master. FIG. 15 is a diagram showing data referenced in the WebEDI user group master, an example of an operating company user master maintenance screen, and records additionally registered in the WebEDI user master. FIG. 16 is a flowchart showing the flow of registration operations when the operating company administrator newly registers a supplier representative user. FIG. 17 is a diagram illustrating an example of selection and an example of input on the operating company customer user master maintenance screen at the time of new user registration. FIG. 18 is a diagram showing data referenced in the WebEDI business partner master, data referenced in the WebEDI user master, and records additionally registered in the WebEDI user master. FIG. 19 is a flowchart showing the flow of registration operations when a business partner manager newly registers a user of his company. FIG. 20 is a diagram showing an example of the login screen and data referenced by the WebEDI user master. FIG. 21 is a diagram showing an example of data referenced in the WebEDI business partner master, data referenced in the WebEDI user group master, and a business partner user master maintenance screen for business partners. FIG. 22 is a diagram showing data referenced in the WebEDI business partner master and data referenced in the WebEDI user master. FIG. 23 shows an example of an error message displayed on the operating company customer user master maintenance screen or the customer user master maintenance screen for business partners when an attempt is made to register users exceeding the maximum number of users that can be registered, and the WebEDI It is a figure which shows the record additionally registered to a user master. FIG. 24 is a flowchart showing the flow of a batch invalidation operation in which the operating company administrator invalidates the status of transactions for a business partner, thereby disabling the authority of users of that business partner to use the EDI system. be. FIG. 25 is a diagram showing how the user ID expiration date of a business partner whose transaction status has been invalidated by the operating company administrator and each user of the business partner whose transaction has been invalidated has been updated to expire. be. Figure 26 shows the operation of detecting a user whose expiration date is about to expire at the operating company or business partner and notifying the operating company administrator as a warning when the operating company administrator logs into the management device. It is a flowchart showing a flow. FIG. 27 is a diagram showing an example of a login screen. FIG. 28 is a diagram showing an example of a menu screen displaying a predetermined warning message (a message prompting the user to confirm that the expiration date is about to expire). FIG. 29 is a diagram showing an example of a screen listing user information of each user such as a business partner. FIG. 30 is a diagram showing an example of a user master details screen. FIG. 31 is a diagram for explaining the operation of registering an extension of the expiration date. FIG. 32 is a diagram illustrating an example of an error message displayed when an expiration date exceeding the set upper limit is specified. FIG. 33 is a diagram for explaining invalidation of the expiration date warning. FIG. 34 is a flowchart showing the flow of operations for issuing a warning indicating the existence of a user whose expiration date has passed. FIG. 35 is a diagram showing an example of a menu screen. FIG. 36 is a diagram showing an example of a list screen. FIG. 37 is a diagram illustrating an example of a user master details screen for a user whose expiration date has expired. FIG. 38 is a diagram for explaining registration of an extension of the expiration date for a user whose expiration date has expired. FIG. 39 is a diagram for explaining invalidation of a warning of an expiration date to a user whose expiration date has expired. FIG. 40 is a schematic diagram showing the warning form of warning pattern 1. FIG. 41 is a schematic diagram showing the warning form of warning pattern 2. FIG. 42 is a schematic diagram showing the warning form of warning pattern 3. FIG. 43 is a schematic diagram showing the warning form of warning pattern 4. FIG. 44 is a flowchart showing the flow of warning operation for warning pattern 0. FIG. 45 is a flowchart showing the flow of the warning operation of warning pattern 1. FIG. 46 is a diagram illustrating an example of a WebEDI user group master. FIG. 47 is a diagram illustrating an example of a WebEDI user master. FIG. 48 is a flowchart showing the flow of warning operations for warning pattern 3 and warning pattern 4. FIG. 49 is a diagram showing an example of a WebEDI customer classification master. FIG. 50 is a flowchart showing the flow of warning operations for warning pattern 2 and warning pattern 4.

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

[System configuration]
FIG. 1 is a diagram showing the system configuration of an electronic commerce system (EDI system, EDI: Electronic Data Interchange) in which electronic commerce is brokered and managed by a management device 1 according to an embodiment. As shown in FIG. 1, the EDI system includes a management system of an operating company including a management device 1 according to the embodiment, a customer terminal device 100 of a customer conducting commercial transactions, and a supplier terminal device of a supplier. 200. As illustrated in FIG. 1, the management system of the operating company uses the management device 1 of the embodiment to check inventory from a customer terminal device 100, input orders, and input orders from a supplier terminal device 200. , and acts as an intermediary for orders and requests. Note that customers and suppliers are examples of business partners.

(System configuration of 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) comprising the management device 1 of the embodiment, and a terminal device 80 for managing the operating company. This includes a backyard environment (an example of a second communication device), and a collaboration tool 90 that is a terminal device that coordinates the front environment and the backyard environment.

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

Further, the front environment is published on the Internet and can be used by users of the operating company and users who have a business partner relationship with the operating company. Specifically, in the storage unit 2 of the management device 1 of the embodiment included in the front environment of the operating company, users of the operating company, users of customers to whom products or services are provided, and users of products or services, etc. User information of users of suppliers (suppliers) of services, etc. is stored. Furthermore, the storage unit 2 temporarily stores business data from commercial transactions between customers and suppliers. Users of the operating company and users who have a business partner relationship with the operating company can access the management device 1 and access user data in the storage unit 2 (an example of user information such as name and email address) and temporarily stored business data. (= commercial transaction data) is now available.

Note that if the number of business partners is small, the front environment may be made public by restricting connection sources. This allows the front environment to be made public with higher security.

The backyard environment is an environment made up of terminal devices 80 that do not permit connections from external companies, such as business partners, and that only authorized users of the operating company can log in and use. Therefore, the terminal device 80 in this backyard environment is connected to the terminal device of an authorized user of 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. It is preferable that

An authorized user of the operating company uses the communication interface section 81 of the terminal device 80 in this backyard environment to access the storage section (commerce business data management database) 82 in which business data (commerce data) for data management is stored. is accessible.

The collaboration tool 90 accesses the storage unit 2 of the front environment and the storage unit 82 of the backyard environment regularly or irregularly, and stores business data for temporary storage stored in the storage unit 2 of the front environment and the storage unit 82 of the backyard environment. synchronization with business data for data management stored in the storage unit 82 of In other words, the collaboration tool 90 periodically or irregularly attempts to coordinate the business data for temporary storage in the storage unit 2 and the business data for data management in the storage unit 82 so that they are the same data. ing.

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

In addition, for example, since the personal information of users of each business partner is registered in the storage unit 2 (database) of the front environment, the database (storage unit 2) of each environment may be registered with special encryption processing. The operation can be carried out according to the nature of the data stored in the storage section 2 or the storage section 82).

Further, by allowing only specific communication (synchronization of data as described above) by the cooperation tool 90, an infrastructure-like boundary can be established and separated between the front environment and the backyard environment, and security can be strengthened.

(Hardware configuration of management device)
Next, FIG. 3 shows the hardware configuration of the management device 1 of the operating company. As described above, the 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, for example. Such a management device 1 includes a storage section 2, a control section 3, and a communication interface section 4. The communication interface section 4 is connected to a customer terminal device 100 and a supplier terminal device 200 via a network 8 . Further, the communication interface section 4 is connected to a terminal device 80 in a backyard environment via a network 8 and a cooperation tool 90.

As the storage unit 2, 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 WebEDI business partner classification master 11, a WebEDI business partner master 12, a WebEDI user group master 13, and a WebEDI user master 14. The storage unit 2 also stores the above-mentioned user data and temporary storage business data (commerce data) in addition to a management program for managing commercial transactions.

FIG. 4 is a diagram showing an example of the WebEDI customer classification master 11. As shown in FIG. 4, in the WebEDI customer classification master 11, "customer" and "supplier" are stored as customer classifications.

FIG. 5 is a diagram showing an example of the WebEDI business partner master 12. As shown in FIG. As shown in FIG. 5, the WebEDI business partner master 12 contains the upper limit of the number of users that can be registered for each business partner classification and business partner company, and the number of users that can be registered by the business partner company using the EDI system. Status information indicating whether or not it is possible is stored. The example in Figure 5 is an example in which the upper limit of the number of users that can be registered for company A, which is a customer, is "3" and the status information indicating whether or not the EDI system can be used is set to "valid". It shows.

In addition, in the example shown in FIG. 5, the upper limit of the number of users that can be registered for company X, which is a supplier, is "8", and the status information indicating whether or not the EDI system can be used is set to "invalid". An example is shown below. As will be described later, the management device 1 of the embodiment updates the user ID expiration date of each user of the company whose status information is set as "invalid" to the expiration date. As a result, by setting the status information for a company to "invalid", it is possible to collectively restrict the use of the EDI system by each user of that company.

FIG. 6 is a diagram showing an example of the WebEDI user group master 13. Stored are customer classification, user group, management company management availability information, and customer management availability information.

Among these, the user group indicates each user of the operations (jobs) of the operating company, customers, and suppliers. That is, the user group of "operating company managers" indicates a group made up of users who perform management work at the operating company. Further, the user group of "customer person in charge" indicates a group consisting of users who are in charge at the customer.

Further, the user group "Supplier Estimator" indicates a group consisting of users who are in charge of estimation work at a supplier. Furthermore, the user group of "persons in charge of actual work at the supplier" indicates a group made up of users who are in charge of actual work at the supplier.

The operating company management availability information is information indicating a user group whose user registration can be managed by the operating company. In the example of FIG. 6, the operating company is able to manage user registration (user registration authority) for all user groups of the operating company itself, customers, and suppliers.

Furthermore, in the management device 1 of the embodiment, user registration authority can be entrusted (set) to desired user groups of customers and suppliers. Information indicating whether or not the authority for user registration is delegated is client management availability information. The example in FIG. 6 shows an example in which the operating company entrusts (sets) user registration authority to the customer's user groups of "customer administrator" and "client person in charge" via the management device 1. It shows. In other words, the user with registration authority in this case is the customer administrator, and this indicates that user registration is only possible for the user groups of "customer administrator" and "customer person in charge". .

In addition, in the example in Figure 6, the operating company entrusts (sets) the authority for user registration for the user group of "supplier actual work staff" to the supplier administrator of the supplier. An example is shown below. In other words, the user with registration authority in this case is the supplier administrator, and this supplier administrator can only register users for the user group of "supplier actual work personnel". It shows.

In this example, the user registration authority will be explained as being set for each customer group, but the user registration authority may be set for each customer.

FIG. 7 is a diagram showing an example of the WebEDI user master 14 in which the above-mentioned user data is registered. As shown in FIG. 7, the WebEDI user master 14 stores user identification information (user ID), user name, and user ID expiration date of each user who belongs to the user group of the operating company and each business partner. ing. The user ID expiration date is information indicating the date on which the EDI system can be used.

In the example of FIG. 7, the user "Operating Company Administrator UK1" whose user ID is "UK01" and the "Operating Company Administrator" user group whose user ID is "UK02" belong to the user group "Operating Company Administrator" of the operating company. The user ID expiration date of the user "Company Administrator UK2" is "March 31, 2030". In addition, in the example of FIG. 7, the user "A company representative AT1" whose user ID is "AT01" who belongs to the "customer representative" user group of company A, and the user "AT1" whose user ID is "AT03" The user ID expiration date of the user "A company representative AT3" is "March 31, 2030", but the user ID expiration date of the user "A company representative AT2" whose user ID is "AT02" indicates that the validity period has expired on "January 1, 2010".

Similarly, in the example of FIG. 7, the user IDs of the users "X company administrator XK1" and "X company estimator XMT1" of company X will both expire on "March 1, 2022." It shows that.

Next, FIG. 8 is a diagram showing a list of various screens provided by the management device 1 to users of user groups of the operating company and each business partner. As shown in FIG. 8, for each user in the "operating company administrator" user group, there is a "client master maintenance screen," "operating company user master maintenance screen," and "operating company user master maintenance screen." is provided from the management device 1. Furthermore, the management device 1 provides an “operating company business screen” to each user in the user group of “operating company personnel.”

Additionally, for users in the "Customer Administrator" user group, the "Customer User Master Maintenance Screen for Customers" is available, and for users in the Customer Contact User Group, the "Customer Business Screen" is available. are provided by the management device 1, respectively.

Additionally, for users in the "Supplier Manager" user group, the "Business Partner User Master Maintenance Screen for Business Partners" is available, and for users in the "Supplier Estimator" group, the "Supplier User Master Maintenance Screen" The management device 1 provides the "supplier's actual work screen" to the user who is the "supplier's actual work person" on the "estimation work screen".

To explain more specifically, FIG. 9 is a diagram showing an example of a "supplier master maintenance screen" provided to each user of the "operating company manager" user group. The "business partner master maintenance screen" shown in FIG. 9 is a screen for registering business partners who use the EDI system. The operating company side registers the customer classification, customer name, upper limit on the number of users, and status via this "client master maintenance screen."

As the business partner classification, "supplier" or "customer" is selected and registered. As the business partner name, for example, a business partner name such as "X Company" is registered. As the upper limit on the number of users, the upper limit value of the number of users who can use the EDI system is registered. The status registers status information indicating whether the EDI system can be used (valid or invalid). The example shown in FIG. 9 is an example in which the status information of company X is set to "invalid" and company X is not allowed to use the EDI system.

FIG. 10 is a diagram illustrating an example of the "operating company user master maintenance screen" provided to each user in the "operating company administrator" user group. As shown in FIG. 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. The operating company user registers the user group (operating company administrator or operating company representative), user ID, user name, initial password, and user ID expiration date via this "operating company user master maintenance screen". .

FIG. 11 is a diagram illustrating an example of the "operating company customer user master maintenance screen" provided to each user in the "operating company administrator" user group. As shown in FIG. 11, the "operating company business partner user master maintenance screen" is a screen for classifying "users of business partners on the operating company side" into user groups and registering user information. Users at the operating company register the client classification, client name, user group, user ID, user name, initial password, and user ID expiration date via this "Operating Company Client User Master Maintenance Screen" . As the business partner classification, either supplier or customer is selected. As the business partner name, a business partner name such as "X Company" or "Y Company" is selected, for example. As the user group, for example, the above-mentioned user groups such as "supplier person in charge" or "customer manager" are selected.

FIG. 12 is a diagram illustrating an example of a "client user master maintenance screen for business partners" provided to each user in the "client manager" or "supplier manager" user group. Of these, Figure 12(a) is an example of the ``Supplier User Master Maintenance Screen for Suppliers'' provided to the ``Customer Manager'', and Figure 12(b) is an example of the ``Supplier Management This is an example of a screen of a "customer user master maintenance screen for business partners" provided to the customer.

As shown in Figure 12(a), the "customer administrator" selects the user group to which the company's users will belong via the "client user master maintenance screen for business partners", and selects the user group with the user ID, user name, Register the initial password and user ID expiration date.

Similarly, as shown in Figure 12(b), the "supplier administrator" selects the user group to which the company's users belong via the "supplier user master maintenance screen" and enters the user ID. , register the user name, initial password, and user ID expiration date. Note that the example shown in FIG. 12(b) is an example in which the user group of "supplier actual work personnel" is selected as the user group.

(Functional configuration of management device)
Next, by executing the management program stored in the storage unit 2, the control unit 3 of the management device 1 shown in FIG. 24, a storage control section 25, a display screen generation section 26, a status setting section 27, and a notification control section 28.

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 business partner that conducts electronic commerce via the network 8. . The user management authority setting unit 22 sets user management authority for registering or editing predetermined user information including expiration date information indicating the expiration date of the authorized user authority to the business partner. "Editing" is a concept that includes acts of changing and deleting data contents, such as modifying and deleting user information.

When new registration or editing (including deletion) of a user is requested via the terminal device 100 or 200 of a business partner, the display screen generation unit 26 sends a message to the terminal device of the business partner that requested the new registration, etc. of the user. , generates a user registration screen (the customer user master maintenance screen for the customer shown in FIGS. 12(a) and 12(b)), which is transmitted via the communication interface section 4, for performing new user registration, etc. .

The determination unit 24 determines whether or not the business partner that has made the request for new user registration, etc. is a business partner for which user management authority has been set. When the determination unit 24 obtains a determination result indicating that the business partner that made the request for new user registration, etc. is a business partner for which user management authority has been set, the storage control unit 25 stores information for each business partner. The user ID of the user who has performed new registration etc. is valid for the WebEDI user master 14 of the storage unit 2 in which user information including expiration date information (user ID expiration date information) of each user is stored. Store user information including deadline information.

Note that the user management authority setting unit 22 sets user management authority for each user group composed of managers or persons in charge of each business partner. Further, the user management authority setting unit 22 sets the upper limit of the number of users that can be registered for each business partner.

Further, the status setting unit 27 sets a status indicating whether the transaction with respect to each business partner is valid or invalid. The storage control unit 25 adds status information indicating the status set by the status setting unit 27 for each customer, along with the user information and user ID expiration date information of the users of each customer, and records the WebEDI transaction in the storage unit 2. It is stored in the destination master 12.

Furthermore, when the status setting unit 27 sets a status of “invalid” for a business partner, the storage control unit 25 stores information about the business partner whose transaction is invalidated, which is stored in the WebEDI business partner master 12. Update the status information to "invalid" status information. At the same time, the storage control unit 25 updates the user ID expiration date information of the user of the business partner whose transaction has been invalidated, which is stored in the WebEDI user master 14, to the date of expiration.

The data generation unit 23 generates user data including the user group, user ID, initial password, user ID expiration date, etc. input through the various screens described using FIGS. 8 to 12.

The notification control unit 28 determines whether or not the user is authorized to use e-commerce, based on expiry date information (user ID expiry date information) that indicates the expiry date of the user's authority to legitimately use electronic commerce, which is included in the user data stored in the storage unit 2. A warning indicating that the authorized user authority will expire from a predetermined number of days before the expiration date is sent. The "date a predetermined number of days ago" is preset, for example, 30 days before the expiration date.

Further, as the "warning notification", a warning message may be displayed on the display unit, or an audio output such as an electronic sound or a voice message indicating that the expiration date is near may be used. Further, as the "warning notification", an electronic text such as an e-mail or a short message may be sent, which includes a text indicating that the expiration date is near.

Below, a "warning notification" indicating the expiration of the user's authority to legally use e-commerce is a warning message indicating that there is a user whose expiration date is near, or a warning message indicating that there is a user whose expiration date is near, or a warning message indicating that the expiration date of the user's authority is approaching The explanation will proceed assuming that a warning message is displayed to indicate the existence of the message.

In addition to the warning message that the validity period has expired, the notification control unit 28 also generates a warning invalidation selection object ( 30) is displayed. At this time, the notification control unit 28 displays the warning invalidation selection object from a preset number of days, such as 30 days before, the date on which the regular user authority expires. Furthermore, if the user who is the target of a warning is registered for an extension of its expiration date, the notification control unit 28 hides the warning invalidation selection object for a predetermined period of time, such as until the next year's warning period. shall be.

In addition, when invalidation of the warning is specified via the warning invalidation selection object, the storage control unit 25 stores the warning information included in the user information of the user who is the target of the warning, which is stored in the storage unit 2. The warning information indicating whether or not to issue a warning is updated to "invalid" indicating that no warning will be issued in the future.

In addition, when registering an extension of the expiration date of the user who is the target of the warning, if an expiration date exceeding a predetermined upper limit such as "365 days" is input, the notification control unit 28 will notify the user of the "User ID A predetermined error notification (display of an error message) such as "The upper limit set for the expiration date has been exceeded" is performed. Note that the predetermined error notification may be an electronic sound or a voice message as described above.

Further, the notification control unit 28 notifies a warning that there is a user whose validity period has expired without being registered for extension, and displays the above-mentioned warning invalidation selection object. Then, the notification control unit 28 hides the warning invalidation selection object when the expiration date of the user who is the target of the warning is registered for extension. If invalidation of the warning is specified via the warning invalidation selection object without registering an extension of the expiration date, the storage control unit 25 stores the warning target stored in the storage unit 2. Warning information included in the user's user information indicating whether or not to issue a warning is updated to "invalid" indicating that no warning will be issued in the future.

In addition, the notification control unit 28 may provide, as a warning notification,
(Warning pattern 0) Notification to users whose regular user privileges will expire;
(Warning pattern 1) Notification to the administrator of the user whose regular user privileges will expire;
(Warning pattern 2) If the user whose regular user authority expires is a user at a business partner, a notification is sent to the business partner's administrator,
(Warning pattern 3) If the user whose regular user authority expires is a user of a business partner, a notification is sent to the management company administrator of the management company that manages all business partners;
(Warning pattern 4) If the user whose regular user authority expires is a user of a business partner, a notification is sent to the business partner's administrator and the operating company administrator of the operating company that manages all business partners. ,
Notification of one or more of the warning patterns is performed. One or more of these warning patterns are set in advance, and the notification control unit 28 issues a warning of the set warning pattern based on this setting information.

In addition, the notification control unit 28 determines whether or not an expiration date is set, which indicates whether or not it is mandatory to set an expiration date for regular user authority, which is included in the user information of the operating company administrator of the operating company that manages all business partners. If the information indicates that the expiration date is not set, the warning is not notified. If this expiration date setting presence/absence information (expiration date mandatory flag) is set to "FALSE", settings can be made to allow user registration without setting an expiration date. In addition, since it is normally assumed that the operating company will perform business partner management and user management operations indefinitely, it is possible to choose an operation of turning off the information on whether or not an expiration date is set (the expiration date required flag). becomes. Note that if no expiration date is set, the expiration date of the WebEDI user master 14 will be "NULL" (see FIG. 47).

In addition, the user information stored in the storage unit 2 includes the expiration date information indicating the expiration date of the authorized user, as well as the warning period, which is the period during which the warning notification is to be made, and the entire e-commerce system. The information includes warning period information that is uniquely set for each user, or set for each predetermined group, or set for each user. The storage control unit 25 includes expiration date information indicating the specified expiration date and warning period information indicating the specified warning period in the user information of the target user, and stores the information in the storage unit 2 .

(Registration operation of new users of the company by the operating company)
Next, the operation of registering a new user of the company by the management company in the management device 1 of the management company will be explained using the flowchart of FIG. 13. Note that the following explanation will be given using "registration" of a new user as an example, but when "editing" user information such as correcting or deleting it, the operation is similar to that described below. For this reason, please refer to the following explanation regarding operations during editing such as modifying or deleting 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. Thereby, the flowchart of FIG. 13 is started, and the processing is executed in order from step S1.

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 who made the login request. The user of the operating company who has made the login request enters the user ID and password on the login screen displayed on the display screen of the administrator terminal device. The input user ID and password are sent to the management device 1.

The determination 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 determination unit 24 determines whether or not the input user ID has expired by determining whether or not today's date exceeds the date set as the user ID expiration date. (Step S3). If the determination unit 24 determines that the input user ID has expired (step S3: Yes), the user does not have the authority to perform user registration, so the process of the flowchart in FIG. 13 ends. .

On the other hand, if it is determined that the input user ID is within the expiration date (Step S3: No), the determining unit 24 determines whether there is a request to start the operating company user master maintenance screen (Step S4). . If a request to start the operating company user master maintenance screen is detected (step S4: Yes), the determination unit 24 refers to the WebEDI user master 14 shown in FIG. 14(c) based on the user ID in step S5. Then, it is determined whether the user is a user of the "operating company administrator" user group who has the authority to register new users. If the user is not in the "Operating Company Manager" user group (step S5: No), the user does not have the authority to perform user registration, and the process of the flowchart in FIG. 13 ends.

If the user is in the "operating company administrator" user group (step S5: Yes), the process proceeds to step S6. In step S6, the determining unit 24 refers to the WebEDI user group master 13, as shown in FIG. 15(a), and identifies user groups that have no customer classification and can be managed by the operating company.

In other words, a user group whose business partner classification has not been set means that it is not a user group of customers or suppliers, but a user group of an operating company. Therefore, the determining unit 24 detects user groups of operating companies whose business partner classification is not set. Then, by referring to the management company management availability information in the WebEDI user group master 13, the determination unit 24 determines whether user registration can be performed among the user groups of the management company whose business partner classification has not been set. Identify user groups (user groups that can be managed within the operating company). The example in FIG. 15A is an example in which registration of new users is permitted for each user group of "Operating Company Manager" and "Operating Company Personnel."

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

The user of the administrator terminal device is an "operating company administrator" or "operating company representative" who is a user group for which user registration is permitted, based on the operating company user master maintenance screen illustrated in FIG. 15(b). Select one of the user groups. The user of the administrator terminal device also enters the user ID, user name, initial password, and user ID expiration date of the user who is newly registering on the operating company user master maintenance screen illustrated in FIG. 15(b). Enter and perform the registration operation.

As a result, the information such as the user group, user ID, user name, initial password, and user ID expiration date entered through the operating company user master maintenance screen is transmitted from the administrator terminal device to the management device 1 and a registration request is sent. will be held. 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 the user group received from the administrator terminal device, Detailed data (record) of the WebEDI user master 14 is generated, including the user ID, user name, initial password, and user ID expiration date.

In step S9, the storage control unit 25 adds and stores the detailed data (record) generated by the data generation unit 23 in the WebEDI user master 14 as shown in FIG. 15(c). As a result, for example, a user with a user ID of "UT99" and a user name of "Management company representative UT99" in the "Management company representative" user group of the management company can enter "December 31, 2030" as a user ID. It will be newly registered as the expiration date.

(Registration operation of new user of supplier by user of operating company)
Next, the operation of registering a new user of a supplier by a user of the operating company in the management device 1 of the operating company will be described using the flowchart of FIG. 16. Each process in 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.

That is, a user of an operating company who is registering a new user of a supplier makes a login request to the management device 1 via the administrator terminal device. This starts the flowchart in FIG. 16, but the operations in steps S1 to S3 until it is determined whether or not the user expiration date has expired based on the user ID input on the login screen are as shown in the flowchart in FIG. This is the same operation as steps S1 to S3. Therefore, for a detailed explanation of the operations in steps S1 to S3, please refer to the explanation of the operations in steps S1 to S3 in the flowchart of FIG.

Next, if it is determined in step S3 that the user ID has not expired (step S3: No), the process proceeds to step S11 of the flowchart in FIG. In step S11, the determining unit 24 determines whether there is a request from a user of the operating company to start the operating company customer user master maintenance screen illustrated in FIG. 17(a).

When detecting a request to start the operating company business partner user master maintenance screen (step S11: Yes), the determination unit 24 refers to the WebEDI user master 14 based on the user ID in step S5, and determines whether the user is a new user. It is determined whether the user is in the user group of "operating company managers" who have registration authority. If the user is not in the "Operating Company Manager" user group (step S5: No), the user does not have the authority to perform user registration, and the process of the flowchart in FIG. 16 ends.

If the user belongs to the "operating company administrator" user group (step S5: Yes), the process advances to step S12. In step S12, the display screen generation unit 26 generates the operating company customer user master maintenance screen illustrated in FIG. Send to device.

The user of the administrator terminal device selects a customer classification such as "supplier" based on the customer user master maintenance screen for the operating company, as shown in FIG. 17(b). Further, the user of the administrator terminal device inputs a business partner name such as "Y Company" based on the business partner user master maintenance screen for the operating company, as shown in FIG. 17(c). In addition, the user of the administrator terminal device can input the user group, user ID, user name, initial password, and user ID expiration date based on the operating company customer user master maintenance screen, as shown in FIG. Enter and perform the registration operation.

As a result, the information such as the customer classification, customer, user group, user ID, user name, initial password, and user ID expiration date entered through the management company customer user master maintenance screen will be saved on the administrator terminal. The information is sent from the device to the management device 1, and a registration request is made. When this registration request is received by the management device 1, the determination unit 24 of the management device 1 determines that a registration operation has been performed (step S13: Yes). Then, in step S14, the determination unit 24 refers to the WebEDI business partner master 12 shown in FIG. 18(a) and detects the upper limit of the number of users for the input business partner. In the example of FIG. 18(a), the upper limit of the number of users is set to "10".

Further, the determining unit 24 detects the current number of valid users of the business partner who is currently attempting to register a new user by referring to the WebEDI user master 14 shown in FIG. 18(b). The example in FIG. 18(b) shows that the business partner who is currently trying to register a new user is company Y, and the current number of valid users of company Y is "3." There is.

In this example, the upper limit of the number of users of company Y is "10" and the current number of valid users is "3", so even if a new user is registered, the user of company Y The upper limit of the number will not be exceeded. Therefore, the determining unit 24 determines that the upper limit of the number of users is not exceeded (step S14: No). Thereby, the data generation unit 23 generates details of the WebEDI user master 14 including the customer classification, customer, user group, user ID, user name, initial password, and user ID expiration date received from the administrator terminal device. Generate data (records).

As will be described later, if registering a new user exceeds the upper limit of the number of users set for the business partner (step S14: Yes), the display screen generation unit 26 As shown in a), for example, a customer user master maintenance screen for the operating company is generated that displays an error message such as "Users cannot be added because the number of users exceeds the upper limit." Then, the communication control unit 21 transmits the operating company customer user master maintenance screen displaying this error message to the operating manager terminal device. As a result, the user of the operation administrator terminal device recognizes that no more new users can be registered, and can perform operations such as deleting unnecessary users or adding and expanding the upper limit of the number of users. Become.

Next, in step S9, the storage control unit 25 adds and stores the detailed data (record) generated by the data generation unit 23 in the WebEDI user master 14 as shown in FIG. 18(c). As a result, for example, a user with the user ID "YJT99" and the user name "YJT99, the person in charge of actual work at company Y" will be added to the user group of "supplier actual work staff" of company Y. The user ID will be newly registered with the expiration date set to ``Day''.

(Registration behavior of new users of the company by business partners)
Next, the operation of the management device 1 when a supplier company, which is an example of a business partner, registers a new user of the 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, a user of the supplier's company who is registering a new user makes a login request to the management device 1 via the supplier terminal device 200. As a result, the flowchart of FIG. 19 is started, and the processing is sequentially executed from step S21.

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 supplier terminal device 200 of the user of the supplier's company that has made the login request. A user of the supplier's company that has made the login request enters a user ID and password on a login screen displayed on the display screen of the supplier terminal device 200. The input user ID and password are sent to the management device 1.

The determination 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 determination unit 24 determines whether or not today's date exceeds the date set as the user ID expiration date, so that the user ID of the user of the input supplier company is valid. It is determined whether the time limit has expired (step S23). If the determination unit 24 determines that the input user ID has expired (step S23: Yes), the user of the supplier's company does not have the authority to perform user registration, so the flowchart of FIG. 19 continues. The process ends.

On the other hand, if it is determined that the input user ID is within the expiration date (step S23: No), the determination unit 24 determines whether there is a request to start the customer user master maintenance screen for the customer ( Step S24). If a request to start the customer user master maintenance screen for the customer is detected (step S24: Yes), the determination unit 24 selects the WebEDI user master 14 shown in FIG. 20(c) based on the user ID in step S25. By referring to it, it is determined whether the user of the supplier's company is a user of the "supplier manager" user group who has the authority to register new users. If the user is not in the "supplier administrator" user group (step S25: No), the user of the supplier's company does not have the authority to perform user registration, so the process of the flowchart in FIG. 19 ends. Become.

If the user belongs to the "supplier manager" user group (step S25: Yes), the process advances to step S26. In step S26, the determination unit 24 refers to the WebEDI customer master data 12 shown in FIG. 21(a) and confirms that the status information of company Y, which is the supplier, is "valid". Furthermore, by referring to the WebEDI user group master 13 shown in FIG. 21(b), the determination unit 24 identifies a user group whose business partner classification is "supplier", which is the same as the logged-in user, and who can be managed by the business partner. do. In the case of the example shown in FIG. 21(b), the determining unit 24 specifies the user group of "supplier actual work personnel" as a user group in which user registration is possible.

Next, in step S27, the display screen generation unit 26 generates the customer user master maintenance screen for the customer as illustrated in FIG. 21(c), and the communication control unit 21 generates the customer user master maintenance screen for the customer. It is transmitted to the supplier terminal device 200.

The supplier administrator of the supplier terminal device 200 selects the "supplier actual work person" who is permitted to register based on the supplier user master maintenance screen for suppliers illustrated in FIG. 21(c). Select the user group. The supplier administrator of the supplier terminal device 200 also displays the user ID, user name, Enter the initial password and user ID expiration date to perform the registration operation.

As a result, information such as the user group, user ID, user name, initial password, and user ID expiration date entered through the customer user master maintenance screen for customers is transferred from the supplier terminal device 200 to the management device 1. A registration request is sent to . When this registration request is received by the management device 1, the determination 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.

In step S29, the determination unit 24 refers to the WebEDI master 12 shown in FIG. 22(a) and detects the "upper limit on the number of users" of the company that is currently the target of user registration. In 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 targeted for new user registration, as "10 people."

Further, the determining unit 24 refers to the WebEDI user master shown in FIG. 22(b) and detects the current number of valid users at the supplier that is the target of new user registration. In the example of FIG. 22(b), the determination unit 24 detects the number of effective users of "3" as the current number of effective users in company Y, which is the supplier targeted for new user registration.

Then, in step S29, the determining unit 24 determines whether or not the number of valid users exceeds the user upper limit when a new user is registered. If the number of valid users exceeds the upper limit of the number of users by newly registering a user (step S29: Yes), the number of user registrations will exceed the specified number, so the display screen generation unit 26 However, as shown in FIG. 23(a), a customer user master maintenance screen for the customer is generated that displays an error message such as "User cannot be added because the number of users exceeds the upper limit", and the customer terminal device 200 The process of the flowchart in FIG. 19 is completed. In this case, the supplier person in charge of the supplier terminal device 200 recognizes that no more new users can be registered, and performs operations such as deleting unnecessary users or adding and expanding the upper limit on the number of users. Make a request to the operating company. When such a request is made, the operating company side performs changes such as increasing the upper limit number of users of the WebEDI master 12. This allows the supplier person in charge to register a new user.

On the other hand, if the number of valid users does not exceed the user upper limit (step S29: No), the data generation unit 23 of the management device 1 generates the user group, user ID, user name, and information received from the supplier terminal device 200. Generate detailed data (record) of the WebEDI user master 14, including the initial password and user ID expiration date.

In step S30, the storage control unit 25 adds and stores the detailed data (record) generated by the data generation unit 23 in the WebEDI user master 14 as shown in FIG. 23(b). As a result, for example, a user with the user ID "YJT99" and the user name "YJT99, the person in charge of actual work at company Y" will be added to the user group of "supplier actual work person" of company Y, which is the supplier. The user ID will be newly registered with "December 31, 2030" as its expiration date.

(Invalid behavior of business partner)
Next, an explanation will be given of an operation in which the operating company administrator disables the users of a business partner all at once by setting the status of the business partner to "invalid" 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.

That is, a user who wants to set the status of a business partner to "invalid" makes a login request to the management device 1 via the administrator terminal device. As a result, the flowchart in FIG. 24 starts, but the operations in steps S1 to S3 until it is determined whether or not the user expiration date has expired based on the user ID input on the login screen are performed in the flowchart in FIG. 13. This is the same operation as steps S1 to S3. Therefore, for a detailed explanation of the operations in steps S1 to S3, please refer to the explanation of the operations in steps S1 to S3 in the flowchart of FIG.

Next, when it is determined that the user ID expiration date is within the expiration date (step S3: Yes) and the process proceeds to step S11, the display screen generation unit 26 generates a message from the administrator terminal device as shown in FIG. Determine whether there is a request to start the customer master maintenance screen illustrated in . Then, when a request to start the customer master maintenance screen is made from the administrator terminal device (step S11: Yes), in step S5, the determination unit 24 determines whether the customer master maintenance screen is currently displayed based on the user ID at the time of the login request. It is determined whether the user making the screen startup request is a user of the "operating company administrator" user group.

If the user who is currently requesting the startup of the business partner master maintenance screen is not a user in the "operating company administrator" user group (step S5: No), has the authority to set the business partner's status to "invalid". Since the user is not a user, the process of the flowchart in FIG. 24 ends.

On the other hand, if the user who is currently requesting the start-up of the customer master maintenance screen is a user of the "operating company administrator" user group (step S5: Yes), the display screen generation unit 26 9 is generated, and the communication control unit 21 transmits this client master maintenance screen to the administrator terminal device (step S12).

The "operating company administrator" user specifies the client classification, client name, and user limit based on the client master maintenance screen illustrated in FIG. 9, and sets the status to "invalid." In step S41 of the flowchart of FIG. 24, the status setting unit 27 determines whether or not 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 that sets the status of the business partner specified on the business partner master maintenance screen to "invalid" (=transaction setting the destination status to "Disabled").

When the status information of "invalid" is generated, the storage control unit 25 updates the status information of company X, which is a supplier, to "invalid" as shown in FIG. 25(a). As a result, Company X is restricted from using the EDI system.

In addition, in step S43, the status setting unit 27 sets the expiration date as the user ID expiration date for all users belonging to all user groups of company Generate a user ID expiration date for . The storage control unit 25 inputs the user ID expiration date of the generated expiration date as the user ID expiration date of all users in all user groups of company X, as shown in FIG. 25(b).

This makes it possible to collectively update the user ID expiration dates of all users in all user groups of company X whose status is "invalid" to expire, thereby restricting the use of the EDI system. Even if the operating company invalidates transactions for a business partner, if each user belonging to the business partner is not invalidated, this causes an inconvenience in that users who should not originally be able to use the EDI system continue to be able to do so. However, the management device 1 of the embodiment can prevent such inconveniences and restrict the use of the EDI system by each user of the "invalid" business partner.

(Problems caused by the user ID expiration being overlooked)
Here, if the user information of the user who was transferred or retired is stored in the storage unit 2 in a valid state, the user who was transferred or retired uses the user account that remains in a valid state. There are concerns that fraud may occur, such as logging into the EDI system and illegally obtaining data. This is not desirable from a security standpoint.

In particular, when the user management operation level of the business partner to whom user management authority has been entrusted is low as described above, such security problems become more prominent. For this reason, the management device 1 of the embodiment manages the period during which each user has legitimate user authority based on the user ID expiration date information included in the user information of each user, and An expiration warning is issued a predetermined number of days before the date. The administrator registers an extension of the expiration date for users who will continue to be able to use the EDI system.

As a result, users who have registered for an extension of their expiration date will be able to continue using the EDI system, and users who have not registered for an extension of their expiration date will be able to continue using the EDI system. It is possible to disable the use of the EDI system. Therefore, the security of the EDI system can be maintained, and the troublesome work of regularly checking users registered in the EDI system to determine whether or not they are using the system legally can be eliminated.

(Operation to warn the administrator of the operating company of users whose expiration date is about to expire at the operating company or business partner)
A specific example will be explained below. The flowchart in FIG. 26 shows that when the administrator of the operating company logs in to the management device 1, a user of the operating company or a business partner whose expiration date is about to expire is detected, and a warning notification is sent to the administrator of the operating company. It is a flowchart showing the flow of operations to be performed. The control unit 3 of the management device 1 executes the process shown in the flowchart of FIG. 26 by operating based on the management program stored in the storage unit 2.

That is, when the administrator of the operating company makes a login request via the administrator terminal device, the display screen generation unit 26 of the management device 1 generates the login screen illustrated in FIG. The information is sent to the user terminal device. The administrator of the operating company enters the user ID and password on the login screen displayed on the administrator terminal device and transmits them to the management device 1. Thereby, the control unit 3 of the management device 1 performs user authentication processing based on the input user ID and password. In this user authentication process, when it is authenticated that the user making the login request is an authorized user (in this example, the administrator of the operating company), the flowchart of FIG. 26 starts.

In step S51, the notification control unit 28 detects the user ID expiration dates of all users of the operating company and business partners stored in the WebEDI user master 14 shown in FIG. Then, in step S52, the notification control unit 28 determines whether there is a user whose expiration date is near (the presence or absence of a user whose expiration date corresponds to the warning period). The warning period is set, for example, from 30 days before the expiration date to the expiration date. Therefore, the notification control unit 28 determines whether there is a user whose login date is within the warning period and whose user ID expiration date is included. If there is no user whose user ID expiration date is included in the warning period, the process of the flowchart of FIG. 26 is terminated.

If there is a user whose login date is within the warning period and whose user ID expiration date is present, the notification control unit 28 sends a predetermined warning message (for a user whose expiration date is about to expire) as illustrated in FIG. 28 in step S53. A menu screen displaying a message prompting for confirmation is generated via the display screen generation section 26 and transmitted to the administrator terminal device via the communication control section 21. As shown in FIG. 28, the menu screen includes selection items such as order entry, order inquiry, user maintenance, etc., which is just one example. In step S53, a warning message such as "Among the users belonging to company A, there is one user whose expiration date is approaching. Please check on the user master maintenance menu" is displayed on this menu screen. do.

When confirming a user whose expiration date is approaching, the administrator of the operating company selects and operates the user master maintenance selection item on the menu screen shown in FIG. 28. As a result, selection data indicating that the user master maintenance selection item on the menu screen has been selected is transmitted from the administrator terminal device to the management device 1. The notification control unit 28 of the management device 1 determines whether or not the user master maintenance selection item has been selected by monitoring the presence or absence of this selection data (step S54). If the user master maintenance selection item is not selected (step S54: No), the process of the flowchart of FIG. 26 is ended.

If the user master maintenance selection item is selected (step S54: Yes), the notification control unit 28 displays a list of all users of the operating company and all users of each business partner on the administrator terminal device, and The details (record) of the user whose expiration date is about to expire is displayed in a predetermined display format indicating that the expiration date is about to expire, and is also displayed with a predetermined icon attached (step S55).

Note that in this example, the notification control unit 28 displays a list, but more precisely, the notification control unit 28 generates a list screen via the display screen generation unit 26, and uses this list screen in communication. By transmitting the information to the administrator terminal device via the control unit 21, the list screen is displayed on the administrator terminal device. Although such detailed explanation will be omitted hereafter, the statement "the notification control unit 28 displays a screen" refers to the screen generation operation in the display screen generation unit 26 and the communication control unit 21. It should be understood that the sending operation is included.

FIG. 29 is an example in which all users of XXX Corporation are specified and displayed in a list. The notification control unit 28 may display a list of all users of the operating company and each business partner, or, as shown in FIG. 29, may specify a business partner company and display only the users of the business partner. is also possible. As shown in Figure 29, the list screen displays each user's "status", "user group", "affiliated business partner", user ID, user name, "warning status", and "user ID expiration date (expiration date)". " is displayed.

In this list screen, the "status" is determined and displayed by the notification control unit 28 based on the expiration date of each user, and if today's date ≦ the expiration date, "valid" is displayed. , if today's date > expiration date, "expired" is displayed. Further, "warning" is information indicating whether issuing a warning of expiration date is "valid" or "invalid". In the case of the example shown in FIG. 29, all users are set to "valid" indicating that the expiration warning will be issued.

Further, in FIG. 29, the expiration date for the user whose user ID is "X004" and whose user name is "person in charge R" is "March 31, 2022." Assuming that the date on which this list screen was displayed (= the date on which the administrator of the operating company logged in) was "March 1, 2022," and the above-mentioned warning period was set to "30 days," this "person in charge" The date on which the administrator of the operating company logged in will be included in the warning period for user "R".

Therefore, as shown in FIG. 29, the notification control unit 28 displays the expiration date display column or characters of the user "person in charge R" in red or yellow, for example, to display the expiration date of the other users. Display in a display format different from that of the deadline display field. Further, the notification control unit 28 displays a predetermined icon indicating that the expiration date is approaching in the expiration date display field of the user "person in charge R". The example shown in FIG. 29 is an example in which an icon with a ``!'' drawn inside a △ mark is displayed. The administrator of the operating company recognizes a user whose expiration date display column has an icon attached in this display format as a user whose expiration date is approaching.

Note that in this example, the expiration date display field for users whose expiration date is approaching is displayed in a different format from the others, and a warning is given by attaching a predetermined icon, but a predetermined message is also displayed. The warning may be given by an electronic sound or an audio message.

Next, the administrator of the operating company performs an operation to instruct display of the user master details screen in order to extend the expiration date of the user to whom such a warning has been issued or to disable the warning. As an example, in the case of the management device 1, by double-clicking the details (record) of a desired user among the users on the list screen shown in FIG. 29, the desired user can be specified and the user master details It is designed to display the screen. In this case, the administrator of the operating company double-clicks the details (record) of the user to whom the warning has been issued. In step S56 of the flowchart of FIG. 26, the notification control unit 28 determines whether or not there is an operation to instruct display of the user master details screen. When the user master details screen display instruction operation is detected (step S56: Yes), the notification control unit 28 generates a user master details screen via the display screen generation unit 26, and operates the user master details screen via the communication control unit 21. Send to the company's administrator terminal device. As a result, the user master details screen illustrated in FIG. 30 is displayed on the administrator terminal device (step S57).

As shown in FIG. 30, the user master details screen displays the user group name, user ID, user name, and user ID expiration date (expiration date). In addition, in this example, since the user master details screen is for a user whose expiration date is near, the expiration date display field is displayed in red or yellow text, etc., and a predetermined icon is added, as in the case above. be done.

Further, the notification control unit 28 displays, on the user master details screen, a warning invalidation selection object for specifying invalidation of the warning, whether or not the warning will be unnecessary in the future, via the display screen generation unit 26. Control. As an example, the text "Disable warning" and a check box are displayed as the warning disable selection object.

Next, when setting an extension of the expiration date based on such a user master details screen, the administrator of the operating company should enter, for example, " Enter the extended expiration date, such as "March 31, 2023." In step S58 of the flowchart of FIG. 26, the notification control unit 28 determines whether such an extension of the expiration date is set. If the extension setting of the expiration date is detected (step S58: Yes), the process proceeds to step S59.

Here, if it is possible to register a long date, such as a date 100 years in the future, as the expiration date, security management of the EDI system becomes difficult. For this reason, in the management device 1 of the embodiment, an upper limit value (maximum expiration date) of the expiration date that can be entered, such as "365 days", is determined in advance. In step S59, the notification control unit 28 determines whether the input expiration date is a date after "today's date + maximum user validity period". That is, in step S59, the notification control unit 28 determines whether the input expiration date Determine whether the expiration date exceeds the maximum expiration date.

If the input expiration date exceeds the maximum expiration date (step S59: Yes), the notification control unit 28, in step S63, displays, for example, "Exceeds the set upper limit of user ID expiration date" in step S63. (Maximum user ID expiration date: 365 days).'' is displayed.

On the other hand, if the input expiration date is within the maximum expiration date (step S59: No), the notification control unit 28 displays the list screen in step S60, as illustrated in FIG. 31(b). (See FIG. 29), the details (records) of users whose expiration date has been extended are updated and displayed based on the input expiration date. In this example, the expiration date of a user whose user ID is "X004" and whose user name is "person in charge R" is updated and displayed as "March 31, 2023." Furthermore, when the expiration date is extended in this way, the storage control unit 28 changes the user ID expiration date of the WebEDI user master 14 to the extended date "2023", as shown in FIG. 31(c). March 31st, 2017” and store it.

Furthermore, if the input expiration date is outside the warning period (step S59: No), the notification control unit 28 displays the text "Disable warning" and the Hides the warning invalid selection object that is a checkbox. As a result, even after registering the expiration date extension, while the warning invalid selection object continues to be displayed, the user may accidentally check the checkbox of the warning invalid selection object, and from then on, the expiration date for that user will be changed. This can prevent the inconvenience of not receiving a warning.

On the other hand, if the administrator of the operating company looks at the list screen shown in FIG. 29 and determines that the users who have been warned that the expiration date is about to expire are users who can be allowed to expire as they are, then As shown in (a), an input operation is performed to check the checkbox of the warning invalidation selection object without inputting an extension of the expiration date. When an input operation is performed to check the check box of this warning invalid selection object, the process proceeds to step S62 via step S58 and step S61.

In step S62, the notification control unit 28, as illustrated in FIG. 33(b), updates the details (records) of the users whose checkboxes for the warning invalidation selection objects are checked on the list screen (see FIG. 29). Update the "Warning" input field from "Enabled" to "Disabled" and display it. Thereby, the administrator of the operating company can recognize through the list screen that expired warnings for users who have checked the checkbox of the warning invalidation selection object will be invalidated from now on.

Further, the WebEDI user master 14 stores a warning invalidation flag as well as a user ID expiration date and the like. This warning invalidation flag is information indicating whether to invalidate an expired warning (=do not issue a warning = TRUE) or not invalidate an expired warning (= issue a warning = FALSE). . The default setting of this warning invalidation flag is "FALSE" which means that a warning is issued without invalidating an expired warning.

Therefore, when an input operation is performed to check the check box of the warning invalidation selection object, the storage control unit 23 sets the warning invalidation flag of the user as " "FALSE" is updated to "TRUE" and stored in the WebEDI user master 14. As a result, from this point on, the user is not warned that the expiration date is near, and the authority to use the EDI system expires on the preset expiration date.

(Operation that alerts the administrator of the operating company about users whose expiration date has expired at the operating company or business partner)
The above example was an example of warning a user who is about to expire, but the example below warns that there is a user whose validity has actually expired by passing the expiration date. This is an example. The flowchart in FIG. 34 shows the flow of such operations. The control unit 3 of the management device 1 executes the process shown in the flowchart of FIG. 34 by operating based on the management program stored in the storage unit 2.

In the flowchart of FIG. 34, when the administrator of the operating company makes a login request via the administrator terminal device, based on the user ID and password input via the login screen illustrated in FIG. A user authentication process is performed, and the process proceeds to step S71.

In step S71, the notification control unit 28 detects the user ID expiration dates of all users of the operating company and trading companies stored in the WebEDI user master 14 shown in FIG. Then, in step S72, the notification control unit 28 determines whether there is a user whose ID has expired by comparing the login date and the user ID expiration date of each user. If there is no user whose expiration date has expired (step S72: No), the process of the flowchart of FIG. 34 ends.

If there is a user whose expiration date has expired (step S72: Yes), the notification control unit 28 sends a predetermined warning message (message prompting confirmation of the user whose expiration date has expired) as illustrated in FIG. 35 in step S73. Displays the menu screen displaying on the administrator terminal device. Figure 35 is an example of a warning message displayed on the menu screen saying, "Among the users belonging to company C, one user has expired. Please check on the user master maintenance menu." .

When confirming users whose validity period has expired, the administrator of the operating company selects and operates the user master maintenance selection item on the menu screen shown in FIG. 35. Thereby, in step S74, the notification control unit 28 of the management device 1 monitors whether or not there is a selection operation for the user master maintenance selection item. If the user master maintenance selection item is not selected (step S74: No), the process of the flowchart of FIG. 34 is directly ended.

If the user master maintenance selection item is selected (step S74: Yes), the notification control unit 28 displays a list of all users of the operating company and all users of each business partner on the administrator terminal device, and The details (records) of users whose expiration date has expired are displayed in a predetermined display format indicating that the expiration date has expired, and are also displayed with a predetermined icon attached (step S75).

FIG. 36 is an example in which all users of XXX Corporation are specified and displayed in a list. The notification control unit 28 may display a list of all users of the operating company and each business partner, or, as shown in FIG. 36, may specify a business partner company and display only the users of the business partner. is also possible. As shown in Figure 36, the list screen includes each user's "status", "user group", "affiliated business partner", "user ID", "user name", "warning status", and "user ID expiration date". (Expiry date)" is displayed.

In this list screen, the "status" is determined and displayed by the notification control unit 28 based on the expiration date of each user, and if today's date ≦ the expiration date, "valid" is displayed. , if today's date > expiration date, "expired" is displayed. Further, "warning" is information indicating whether issuing a warning of expiration date is "valid" or "invalid". In the example of FIG. 36, all users are "valid" indicating that they are subject to the expiration warning.

In addition, in FIG. 36, the user whose user ID is "X003" and whose user name is "person in charge Q" is nearing the expiration date, so a warning indicating that the expiration date is nearing is displayed using the display format and icon described above. It is being done.

Additionally, if the login date is "April 1, 2022," the expiration date for the user whose user ID is "X004" and user name is "Rep. R" is "March 31, 2022." Therefore, it has expired. Therefore, since today's date>expiration date, the notification control unit 28 displays "expired" as the "status".

In addition, as shown in FIG. 36, the notification control unit 28 displays the expiration date of other users by displaying the expiration date display field or text of the user "person in charge R" in red or yellow, for example. It is displayed in a display format that is different from the display field of and uses a color different from the color used to warn the user that the expiration date is about to expire. Furthermore, the notification control unit 28 displays an icon in the display column of the expiration date for the user "person in charge R" indicating that the expiration date has expired, and which is different from the icon used in the above-mentioned warning for the user whose expiration date is about to expire. Display. The example shown in FIG. 36 is an example in which the expiration date is displayed with an x mark icon. The administrator of the operating company recognizes a user whose expiration date display column has an icon attached in this display format as a user whose expiration date has expired.

Note that in this example, the above-mentioned display format and icon are used to warn of the presence of an expired user, but the warning may also be given by displaying a message, or by using an electronic sound or a voice message. It's okay.

Next, the administrator of the operating company performs an operation to instruct display of the user master details screen in order to extend the expiration date of the user to whom such a warning has been issued or to disable the warning. As described above, in the case of the management device 1, by double-clicking the details (record) of a desired user among the users on the list screen shown in FIG. 36, the desired user can be specified and the user master details displayed. It is designed to display the screen. In this case, the administrator of the operating company double-clicks the details (record) of the user of "person in charge R" whose expiration date has expired. In step S76 of the flowchart in FIG. 34, the notification control unit 28 determines whether or not there is an operation to instruct display of the user master details screen. Then, when detecting an operation instructing the display of the user master details screen (step S76: Yes), the notification control unit 28 displays the user master details screen illustrated in FIG. 37 on the administrator terminal device (step S77).

As shown in FIG. 37, the user master details screen displays the user group name, user ID, user name, and user ID expiration date (expiration date). In addition, in this example, since it is a user master details screen of a user whose expiration date has expired, the expiration date display field is displayed with characters indicating expiration of the expiration date, and a predetermined icon such as "x" is added. The expiration date will be displayed.

The notification control unit 28 also allows the user to input a warning invalidation selection object via the display screen generation unit 26 to specify whether or not such expired warnings will be unnecessary in the future. Control the display on the master details screen. As an example, the text "Disable warning" and a check box are displayed as the warning disable selection object.

Next, when setting an extension of the expiration date based on such a user master details screen, the administrator of the operating company should enter, for example, " Enter the extended expiration date, such as "March 31, 2023." In step S78 of the flowchart of FIG. 34, the notification control unit 28 determines whether such an extension of the expiration date is set. If the extension setting of the expiration date is detected (step S78: Yes), the process proceeds to step S79.

In step S79, as explained in step S59 above, the notification control unit 28 determines whether the input expiration date is set to exceed the maximum expiration date. If the input expiration date exceeds the maximum expiration date (step S79: Yes), the notification control unit 28, in step S83, displays the message "Exceeds the set upper limit of user ID expiration date" in step S83. (Maximum user ID expiration date: 365 days).'' is displayed.

On the other hand, if the input expiration date is within the maximum expiration date (step S79: No), the notification control unit 28 displays the list screen in step S80, as illustrated in FIG. 38(b). (See FIG. 36) The details (records) of users whose expiration date has been extended are updated and displayed based on the input expiration date. The example shown in FIG. 38(b) is an example in which the expiration date of a user whose user ID is "X004" and whose user name is "person in charge R" is updated and displayed as "March 31, 2023." Further, the notification control unit 28 updates the "status" of the user "person in charge R" from "expired" to "valid" and displays it on the list screen. When the expiration date is extended in this way, the storage control unit 28 changes the user ID expiration date of the WebEDI user master 14 to the extended date "March 2023," as shown in FIG. 38(c). Updated and memorized on the 31st of the month.

Further, if the input expiration date is outside the warning period (step S79: No), the notification control unit 28 displays the text "Disable warning" and Hides the warning invalid selection object that is a checkbox. As a result, even after registering the expiration date extension, while the warning invalid selection object continues to be displayed, the user may accidentally check the checkbox of the warning invalid selection object, and from then on, the expiration date for that user will be changed. This can prevent the inconvenience of not receiving a warning.

On the other hand, if the administrator of the operating company looks at the list screen shown in Figure 36 and determines that the users who have been warned about expiration of the expiration date are users who can be allowed to expire as they are, then As shown, an input operation is performed to check the checkbox of the warning invalidation selection object without inputting an extension of the expiration date. When an input operation is performed to check the check box of this warning invalid selection object, the process proceeds to step S82 via step S78 and step S81.

In step S82, the notification control unit 28, as illustrated in FIG. 39(b), updates the details (records) of the users whose checkboxes for the warning invalidation selection objects are checked on the list screen (see FIG. 36). Update the "Warning" input field from "Enabled" to "Disabled" and display it. Thereby, the administrator of the operating company can recognize through the list screen that expired warnings for users who have checked the checkbox of the warning invalidation selection object will be invalidated from now on.

Further, when an input operation is performed to check the checkbox of the warning invalidation selection object, the storage control unit 23 sets the warning invalidation flag of the user to "FALSE" in step S82, as shown in FIG. 33(c). " is updated to "TRUE (no warning is issued)" and stored in the WebEDI user master 14. As a result, from this point on, no warning of expiration of the expiration date is given to this user, and the authority to use the EDI system expires on the preset expiration date.

(Warning pattern type)
Next, in the case of a normal system, it is preferable to perform user management using the same policy for all users. However, in the case of an EDI system, since the entrustment of user management authority and business relationships differ for each business partner, it is preferable to perform user management using different policies for each business partner. This is a major difference between normal systems and EDI systems. Therefore, in the management device 1 of the embodiment, warning patterns 0 to 4, which will be described below, can be selected and set for each operating company or business partner. Thereby, a warning notifier (=user who notifies a warning) can be set for each operating company or business partner, and the above-mentioned warning can be given to users whose expiration date is about to expire or whose validity period has expired.

Warning pattern information indicating the set warning pattern is stored in the storage unit 2. The notification control unit 28 issues the above-mentioned warning at a predetermined timing using a warning pattern indicated by the warning pattern information stored in the storage unit 2.

(Warning pattern 0)
First, "warning pattern 0" is a warning pattern that warns the logged-in user when the expiration date is approaching. When this warning pattern 0 is set, when a user whose expiration date is about to expire logs in, the notification control unit 28 will notify the user, for example, "User expiration date is approaching. Please contact the administrator. Please send a warning that the expiration date is near, such as "Expiry date: {XX year/XX month/XX day}".

Note that when this warning pattern 0 is set, the notification control unit 28 issues a warning to all users, regardless of whether they are the administrator or the person in charge. Further, when warning pattern 0 is set, the user whose validity period has expired cannot log in, and therefore the notification control unit 28 does not issue the above-mentioned warning.

(Warning pattern 1)
Next, "warning pattern 1", as shown in FIG. 40, is a warning pattern for issuing a warning to the administrator of the operating company when there is a warning target among the users of the operating company. In this case, the notification control unit 28 targets the administrator himself as well. That is, when warning pattern 1 is set, the notification control unit 28 warns the administrator and all users of the operating company that the expiration date is about to expire and that the expiration date has expired.

(Warning pattern 2)
Next, as shown in FIG. 41, "warning pattern 2" is used to alert the manager of a business partner, for example, if there is a warning target among the manager and person in charge of the business partner, such as a customer. This is a warning pattern that issues a warning. In this warning pattern 2, the notification control unit 28 also targets the administrator himself. FIG. 41 is an example in which there are two warning target persons in company A, which is a customer. In this case, the notification control unit 28 sends a warning message to Company A, for example, "Among the users belonging to Company A, there are two users whose expiration date is approaching. Please check with user master maintenance." notification to the administrator's terminal device.

Further, FIG. 41 is an example in which there are three people who are subject to warning in company B, which is a customer. In this case, the notification control unit 28 sends a warning message such as "Among the users belonging to company B, there are three users whose expiration date is approaching. Please check with user master maintenance." Notification is sent to the company administrator's terminal device.
(Warning pattern 3)
Next, in "warning pattern 3", as shown in Figure 42, the operating company manages all personnel at business partners such as suppliers, and some of the personnel at the business partner This is a warning pattern that warns the administrator of the operating company if the target person exists. FIG. 42 is an example in which there are three warning target persons in company C, which is a supplier. In this case, the notification control unit 28 sends a warning message to the operating company, such as "Among the users belonging to company C, there are three users whose expiration date is approaching. Please check with user master maintenance." notification to the administrator terminal device.

(Warning pattern 4)
Next, as shown in FIG. 43, "warning pattern 4" is used, for example, if there is a person to be warned among the managers and persons in charge of the company that is the This is a warning pattern that issues a warning to both the administrator of the operating company. FIG. 43 is an example in which there are three people who are subject to warning in company C, which is 〇〇. In this case, the notification control unit 28 sends a warning message to the operating company, such as "Among the users belonging to company C, there are three users whose expiration date is approaching. Please check with user master maintenance." The notification is sent to the administrator terminal device of the administrator of C and the administrator of Company C, respectively.

(Warning action for warning pattern 0)
Next, the warning operation of each warning pattern will be explained. First, FIG. 44 is a flowchart showing the flow of the warning operation of warning pattern 0 in which a warning is issued to a logged-in user when the expiration date of the user is approaching. The control unit 3 of the management device 1 executes and controls the warning operation shown in the flowchart of FIG. 44 based on the management program stored in the storage unit 2. That is, the flowchart of FIG. 44 starts when the control section 3 recognizes that "warning pattern 0" is set in the warning pattern information stored in the storage section 2, and the process starts from step S91. executed.

In step S91, the notification control unit 28 refers to the WebEDI user master 14 illustrated in FIG. 47 based on the user ID input on the login screen illustrated in FIG. Detects the expiration date and warning disable flag. Further, in step S92, the notification control unit 28 refers to the WebEDI user group master 13 illustrated in FIG. 46 based on the user ID, and detects the warning period set for the user group to which the logged-in user belongs. do.

In step S93, the notification control unit 28 determines whether the following conditions are satisfied.

Condition=
"FLG to disable warning" = "FALSE" and "Expiry date" ≠ "NULL" and "Expiry date" ≤ "Today's date" + "Warning period set for the user group to which the user belongs"

If this condition is met, in step S94, the notification control unit 28 notifies the logged-in user of a warning indicating that the expiration date is approaching (=notification of warning pattern 0).

(Warning action of warning pattern 1)
Next, FIG. 45 is a flowchart showing the flow of the warning operation of warning pattern 1 in which a warning is issued to the administrator of the operating company when there is a warning target among the operating company users. The control unit 3 of the management device 1 executes and controls the warning operation shown in the flowchart of FIG. 45 based on the management program stored in the storage unit 2. That is, the flowchart of FIG. 45 starts when the control section 3 recognizes that "warning pattern 1" is set in the warning pattern information stored in the storage section 2, and the process starts from step S101. executed.

In step S101, the notification control unit 28 refers to the WebEDI user master 14 illustrated in FIG. 47 based on the user ID input on the login screen illustrated in FIG. 27 at the time of login, and the details of the user ( record). Further, in step S102, the notification control unit 28 refers to the WebEDI user group master 13 illustrated in FIG. 46 based on the user ID, and records details (records) of each user in the user group to which the logged-in user belongs. get.

In step S103, the notification control unit 28 refers to the WebEDI user group master 13 shown in FIG. 46, and determines whether the belonging user warning target flag set for the user group to which the logged-in user belongs is "FALSE". Determine whether or not. If the belonging user warning target flag is "FALSE" (step S103: Yes), this means that the user group to which the logged-in user belongs is not a warning target, so the process of the flowchart in FIG. 45 is continued. finish.

On the other hand, if the belonging user warning target flag is "TRUE" (step S103: No), it means that the user group to which the logged-in user belongs is a warning target. Therefore, in step S104, the notification control unit 28 refers to the WebEDI user master 14 shown in FIG. It is determined whether the administrator or the person in charge is the administrator or not.

To explain the operation of step S104 in detail, first, the notification control unit 28 refers to the WebEDI user master 14 and obtains the user group to which the logged-in user belongs. Next, the notification control unit 28 refers to the WebEDI user group master 13 based on the acquired user group and acquires the operating company group flag. If the acquired operating company group flag is "TRUE", the notification control unit 28 determines that the logged-in user is the administrator of the operating company (step S104: Yes). Note that if the logged-in user is not the administrator of the operating company (step S104: No), the process of the flowchart of FIG. 45 is directly terminated because the user is not the user to be notified of the warning in this warning pattern 1.

On the other hand, if the logged-in user is the administrator of the operating company (step S104: Yes), the notification control unit 28, in step S105, refers to the WebEDI user group master 13 shown in FIG. TRUE" user group details. Further, in step S106, the notification control unit 28 refers to the WebEDI user master 14 shown in FIG. 47 and obtains the details of the user group whose operating company group flag is "TRUE".

Then, in step S107, the notification control unit 28 determines whether all users of the operating company satisfy the following conditions.

Condition=
"FLG to disable warning" = "FALSE" and "Expiry date" ≠ "NULL" and "Expiry date" ≤ "Today's date" + "Warning period set for the user group to which the user belongs"

Since a user who satisfies this condition is a user whose expiration date is approaching, the notification control unit 28 notifies the administrator of the operating company of the above-mentioned warning in step S108 (=notification of warning pattern 1).

(Warning operation of warning pattern 3 and warning pattern 4)
Next, Figure 48 shows warning pattern 3 in which a warning is notified to the manager of the operating company when the person in charge of the business partner is the target of the warning, and the person in charge of the business partner (or 〇〇) 12 is a flowchart showing the flow of the warning operation of warning pattern 4, in which a warning is notified to both the manager of the operating company and the manager of the business partner (or XX company) when the person is the target of the warning.

The control unit 3 of the management device 1 executes and controls the warning operation shown in the flowchart of FIG. 48 based on the management program stored in the storage unit 2. That is, the flowchart of FIG. 48 starts when the control section 3 recognizes that "warning pattern 3" or "warning pattern 4" is set in the warning pattern information stored in the storage section 2. , the process is executed from step S101.

In step S101, similarly to the above, the notification control unit 28 refers to the WebEDI user master 14 illustrated in FIG. 47 based on the user ID input on the login screen illustrated in FIG. Get user details (records). Further, in step S102, the notification control unit 28 refers to the WebEDI user group master 13 illustrated in FIG. 46 based on the user ID, and records details (records) of each user in the user group to which the logged-in user belongs. get.

In step S103, the notification control unit 28 refers to the WebEDI user group master 13 shown in FIG. 46, and determines whether the belonging user warning target flag set for the user group to which the logged-in user belongs is "FALSE". Determine whether or not. If the belonging user warning target flag is "FALSE" (step S103: Yes), this means that the user group to which the logged-in user belongs is not a warning target, so the process of the flowchart in FIG. 48 is continued. finish. Through the process of step S103, the user who will be notified of the warning can be limited to the administrator, excluding the person in charge.

On the other hand, if the belonging user warning target flag is "TRUE" (step S103: No), it means that the user group to which the logged-in user belongs is a warning target. Therefore, in step S111, the notification control unit 28 refers to the WebEDI user master 14 shown in FIG. It is determined whether the administrator or the person in charge is the administrator or not.

To explain the operation of step S111 in detail, first, the notification control unit 28 refers to the WebEDI user master 14 and obtains the user group to which the logged-in user belongs. Next, the notification control unit 28 refers to the WebEDI user group master 13 based on the acquired user group and acquires the operating company group flag. If the acquired operating company group flag is "TRUE", the notification control unit 28 determines that the logged-in user is the administrator of the operating company (step S111: Yes). Note that if the logged-in user is not the administrator of the operating company (step S111: No), the process of the flowchart of FIG. 45 is directly ended.

On the other hand, if the logged-in user is the administrator of the operating company (step S111: Yes), the notification control unit 28 refers to the WebEDI business partner classification master 11 shown in FIG. The details of the business partner classification in which the operating company notification flag indicating that a warning will be notified to the operating company is "TRUE (notify the administrator of the operating company)" are obtained. Further, in step S113, the notification control unit 28 refers to the WebEDI user group master 13 shown in FIG. 46 and obtains the details of the user group of the business partner that requires a warning notification to the operating company.

Next, in step S114, the notification control unit 28 determines whether all users of the business partner satisfy the following conditions.

Condition=
"FLG to disable warning" = "FALSE" and "Expiry date" ≠ "NULL" and "Expiry date" ≤ "Today's date" + "Warning period set for the user group to which the user belongs"

Since a user who satisfies this condition is a user whose expiration date is approaching, the notification control unit 28 notifies the administrator of the operating company of the above-mentioned warning in step S115 (=warning pattern 3 or warning pattern 4). notice).

(Warning operation of warning pattern 2 and warning pattern 4)
Next, Figure 50 shows warning pattern 2 in which a warning is notified to the administrator of the business partner when the person in charge of the business partner is the person to whom the warning is issued, and the person in charge of the business partner (or 〇〇) 12 is a flowchart showing the flow of the warning operation of warning pattern 4, in which a warning is notified to both the manager of the operating company and the manager of the business partner (or XX company) when the person is the target of the warning.

The control unit 3 of the management device 1 executes and controls the warning operation shown in the flowchart of FIG. 50 based on the management program stored in the storage unit 2. That is, the flowchart of FIG. 50 starts when the control section 3 recognizes the setting of "warning pattern 2" or "warning pattern 4" from the warning pattern information stored in the storage section 2, and starts from step S101. Processing is executed.

In step S101, similarly to the above, the notification control unit 28 refers to the WebEDI user master 14 illustrated in FIG. 47 based on the user ID input on the login screen illustrated in FIG. Get user details (records). Further, in step S102, the notification control unit 28 refers to the WebEDI user group master 13 illustrated in FIG. 46 based on the user ID, and records details (records) of each user in the user group to which the logged-in user belongs. get.

In step S103, the notification control unit 28 refers to the WebEDI user group master 13 shown in FIG. 46, and determines whether the belonging user warning target flag set for the user group to which the logged-in user belongs is "FALSE". Determine whether or not. If the belonging user warning target flag is "FALSE" (step S103: Yes), this means that the user group to which the logged-in user belongs is not a warning target, so the process of the flowchart in FIG. 50 is continued. finish. Through the process of step S103, the user who will be notified of the warning can be limited to the administrator, excluding the person in charge.

On the other hand, if the belonging user warning target flag is "TRUE" (step S103: No), it means that the user group to which the logged-in user belongs is a warning target. Therefore, in step S120, the notification control unit 28 refers to the WebEDI user master 14 shown in FIG. 47 based on the user ID of the logged-in user, and determines whether the logged-in user is the administrator of the customer's user group. Determine whether or not.

To explain the operation of step S120 in detail, first, the notification control unit 28 refers to the WebEDI user master 14 and obtains the user group to which the logged-in user belongs. Next, the notification control unit 28 refers to the WebEDI user group master 13 based on the acquired user group and acquires the operating company group flag. If the acquired operating company group flag is "FALSE", the notification control unit 28 determines that the logged-in user is the administrator of the customer's user group (step S120: Yes). Note that if the logged-in user is not the administrator of the customer's user group (step S120: No), the process of the flowchart of FIG. 50 is directly ended.

On the other hand, if the logged-in user is the administrator of the business partner (step S120: Yes), the notification control unit 28 refers to the WebEDI user master 14 shown in FIG. Get details of users.

Next, in step S122, the notification control unit 28 determines whether all users of the business partner satisfy the following conditions.

Condition =
"FLG to disable warning" = "FALSE" and "Expiry date" ≠ "NULL" and "Expiry date" ≤ "Today's date" + "Warning period set for the user group to which the user belongs"

Since a user who satisfies this condition is a user whose expiration date is approaching, the notification control unit 28 notifies the administrator of the business partner of the above-mentioned warning in step S123 (=warning pattern 2 or warning pattern 4). notice).

(Effects of embodiment)
The operating company that provides the EDI system via the management device 1 needs to manage the users who belong to the clients at the same time as managing the clients, and the management cost for the operating company is very high. Furthermore, when a business partner adds, modifies, or deletes a user, it is necessary to request this from the operating company, which poses problems in the accuracy and real-time performance of user settings.

Further, even if the operating company invalidates the status of a business partner, if each user belonging to the business partner is not invalidated, there will be an inconvenience that users who should not originally be able to use the EDI system will continue to be able to use it. In addition, if the operating company makes a setting error and registers as a user by linking it to a different business partner than the one that was originally supposed to be registered, this user will be unable to view business partner information of a business partner to which he or she does not belong. This causes the inconvenience that it becomes possible.

Here, since it is difficult for a single operating company to perform management, consider entrusting user management authority to each business partner. However, if user management authority is unconditionally entrusted to a business partner, the entrusted business partner has no restrictions on user management authority, which causes the inconvenience that users of other business partners can also be managed. Furthermore, since the entrusted business partner can register an unlimited number of users, as time passes, many users who are no longer registered become registered, resulting in the inconvenience of increased security risks. Therefore, it is necessary to entrust limited user management authority to business partners.

For this reason, 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 for which the user has regular user authority to the business partner. Thereby, user management authority can be entrusted to each business partner, and the management cost of the electronic commerce system managed by the operating company of the management device 1 can be reduced. Furthermore, since user management authority can be entrusted to trusted business partners, management costs can be safely distributed. Further, since the business partner to whom user management authority has been entrusted can manage the users themselves, it is possible to perform user management accurately and in real time.

Further, user management authority can be set for each administrator or person in charge of a desired user group of each business partner. As a result, user management authority can be entrusted to the administrator or person in charge of a desired user group, making it possible to finely distribute management costs and further improve security.

In addition, the upper limit on the number of new users that can be registered can be set for each business partner, so for example, if a business partner registers an unlimited number of users, many users who are no longer registered may become registered over time. Therefore, inconveniences that increase security risks can be prevented.

In addition, each business partner is managed with a status indicating whether the authority to use the EDI system is "valid" or "invalid". When the status of a business partner is set to "invalid", the user ID expiration date of each user belonging to this business partner is updated to "expired" to invalidate the authority to use the EDI system. As a result, by setting the status of a business partner to "invalid", the authority of each user belonging to this business partner to use the EDI system can also be invalidated all at once, and management costs can be further reduced. Additionally, even if the operating company makes a user management mistake, security risks can be reduced.

Moreover, when the management device 1 of the embodiment registers user information, the user ID is registered with a user ID expiration date. When each user logs into the system, a warning is sent to the user whose expiration date is approaching, the administrator of the operating company, or the administrator of the business partner to which the user belongs, and the user's expiration date is reviewed. encourage. Then, the administrator registers an extension of the expiration date for users who are allowed to continue using the EDI system, and does not register an extension of the expiration date for users who are not allowed to use the EDI system.

As a result, users who have not registered for extension of the expiration date can be prohibited from using the EDI system after the expiration date. Therefore, the security of the EDI system can be maintained, and the troublesome work of regularly checking users registered in the EDI system to determine whether or not they are using the system legally can be eliminated.

Therefore, the security of the EDI system can be maintained even if the operational level of user management at the business partner to whom user management authority has been entrusted is low.

Furthermore, as explained using FIG. 33(a), if the expiration date is not registered for extension, it is possible to specify that the expiration date warning will not be given to the user in the future using the warning invalidation selection object. can. Thereby, the expiration date warning can be suppressed from now on, and it is possible to prevent the inconvenience of users who do not register the expiration date extension from continuing to be notified of the warning.

[Contribution to the Sustainable Development Goals (SDGs) led by the United Nations]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions of companies, so it is possible to contribute to Goal 8 and Goal 9 of the SDGs.

Furthermore, this embodiment can contribute to reducing waste loss and promoting paperless and electronic systems, making it possible to contribute to Goal 12, Goal 13, and Goal 15 of the SDGs.

Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

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

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or the processes described as being performed manually can be performed manually. All or part of the process can also be performed automatically using known methods.

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

Further, regarding the management device 1, each illustrated component is functionally conceptual, and does not necessarily need to be physically configured as illustrated.

For example, the processing functions provided by the management device 1, especially each processing function performed by the control unit 3, may be implemented in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU. Alternatively, it may be realized as hardware using wired logic. Note that the program is recorded in a non-temporary computer-readable recording medium containing programmed instructions for causing an information processing device to execute the processing described in each embodiment, and is stored in a management device as necessary. 1 mechanically read. That is, a storage unit such as a ROM or an HDD stores a computer program that cooperates with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into the RAM, and constitutes the control section 3 or the control section 43 in cooperation with the CPU.

Further, the management program of this management device 1 may be stored in another server device connected to the management device 1 via any network, and all or part of it may be downloaded as necessary. It is also possible.

Further, the management program for executing the processes described in each embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" refers to a memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical Disk), DVD (Digital Versatile Disk), Blu-ray (registered trademark) Disc, etc. shall include any “portable physical medium”.

Furthermore, a "program" is a data processing method written in any language or writing method, and does not matter in the form of source code or binary code. Note that a "program" is not necessarily limited to a unitary structure, but may be distributed as multiple modules or libraries, or may work together with separate programs such as an OS to achieve its functions. Including things. Note that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in the management device 1 shown in the embodiment, the installation procedure after reading, and the like.

The storage unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and the like used for various processing and website provision. , stores files for web pages, etc.

Further, the management device 1 may be configured with an information processing device such as a known personal computer device or a workstation, or may be configured with an information processing device to which arbitrary peripheral devices are connected. Further, the information processing device may be implemented by implementing software (including programs, data, etc.) that implements the processing described in this embodiment.

Furthermore, the specific form of dispersion/integration of devices is not limited to what is shown in the diagram, and all or part of the devices can be functionally or physically divided into arbitrary units according to various additions or additions of functions. It can be configured in a distributed/integrated manner. That is, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively.

The present invention is applicable to any type of industry as long as it conducts commercial transactions via a network.

1 Management device of the operating company 2 Storage 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 business partner classification master 12 WebEDI business partner master 13 WebEDI user group master 14 WebEDI user Master 21 Communication control unit 22 User management authority setting unit 23 Data generation unit 24 Discrimination unit 25 Storage control unit 26 Display screen generation unit 27 Status setting unit 28 Notification control unit 80 Terminal device that constitutes the operating company's backyard environment 81 Communication interface Section 82 Business data storage section for data management 90 Collaboration tool that connects the operating company's front environment and backyard environment 100 Client's terminal device 200 Supplier's terminal device

Claims (13)

a communication control unit that controls the communication unit to mediate the transmission and reception of various data between terminal devices of each business partner conducting electronic commerce via the network;
From a predetermined number of days before the expiration date of the authorized user authority, based on expiration date information indicating the expiration date of the user authority to legitimately use the e-commerce, which is included in the user information stored in the storage unit. , a notification control unit that notifies a warning indicating that the regular user authority is about to expire;
A management device with The notification control unit displays a warning invalidation selection object for displaying the warning that the expiration date is reached, and designating invalidation of the warning as to whether or not the warning will be unnecessary in the future. to control the display,
The management device according to claim 1, characterized in that: The notification control unit displays the warning invalidation selection object from a predetermined number of days before the expiration date of the regular user authority;
The management device according to claim 2, characterized in that: The notification control unit is configured to hide the warning invalidation selection object for a predetermined period when the expiration date of the user who is the target of the warning is registered for extension.
The management device according to claim 3, characterized in that: further comprising a storage control unit that stores or updates the user information in the storage unit,
When invalidation of the warning is specified via the warning invalidation selection object, the storage control unit stores information about the user who is the target of the warning, which is stored in the storage unit. updating the warning information indicating whether or not to issue the warning to "invalid" indicating that the warning will not be issued in the future;
The management device according to claim 4, characterized by: The notification control unit may issue a predetermined error notification if an expiration date exceeding a predetermined upper limit is input when registering an extension of the expiration date of the user who is the target of the warning;
The management device according to claim 5, characterized in that: The notification control unit notifies the user of the existence of a user whose validity period has expired without the extension registration being performed, and displays the warning invalidation selection object, and the user is the target of the warning. When the user registers for extension of the expiration date, hides the warning invalid selection object,
When invalidation of the warning is specified via the warning invalidation selection object without registering an extension of the expiration date, the storage control unit stores information about the warning target stored in the storage unit. updating the warning information included in the user information of the user whose warning information is included in the user information indicating whether or not to issue the warning to "invalid" indicating that the warning will not be issued in the future;
The management device according to claim 6, characterized in that: As the notification of the warning, the notification control unit:
notification to users whose regular user privileges are about to expire;
notification to the administrator of the user whose regular user privileges are about to expire;
Notifying an administrator of a business partner if the user whose regular user privileges are to expire is a user of the business partner;
If the user whose regular user privileges expire is a user of a business partner, notification to the operating company administrator of the operating company that manages all business partners;
If the user whose regular user authority expires is a user of a business partner, notification to the administrator of the business partner and the operating company administrator of the operating company that manages all business partners;
Notifying one or more of the following:
The management device according to claim 1, characterized in that: This is information included in the user information of the operating company administrator of the operating company that manages all business partners, and sets the expiration date setting presence/absence information indicating whether or not it is necessary to set the expiration date of regular user authority. further comprising a setting section;
The management device according to claim 1, characterized in that: The user information stored in the storage unit includes the expiration date information indicating the expiration date of the authorized user, as well as the warning period during which the warning notification is to be made, and the entire e-commerce system Contains warning period information that is uniquely set, set for a predetermined group, or set for each user,
further comprising a storage control unit that stores or updates the user information in the storage unit,
The storage control unit includes the expiration date information indicating the specified expiration date and the warning period information indicating the specified warning period in the user information of the target user, and stores the information in the storage unit. to remember,
The management device according to claim 1, characterized in that: The network includes a first storage unit, and communicates with the terminal devices of each business partner who conducts electronic commerce via the network, and with the terminal devices of users of the operating company that operates the electronic commerce system. a first communication device that performs communication via;
a second communication device that includes a second storage unit and performs communication 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 includes:
a communication control unit that controls the communication unit to mediate the transmission and reception of various data between terminal devices of each business partner conducting electronic commerce via the network;
From a predetermined number of days before the expiration date of the authorized user authority, based on expiration date information indicating the expiration date of the user authority to legitimately use the e-commerce, which is included in the user information stored in the storage unit. , having a notification control unit that notifies a warning indicating that the regular user authority is about to expire;
An electronic commerce system featuring: a communication control step in which the communication control unit controls the communication unit to mediate the transmission and reception of various data between terminal devices of each business partner conducting electronic commerce via the network;
The communication control unit determines a predetermined date on which the regular user authority expires based on expiration date information indicating the expiration date of the user authority to legitimately use the electronic commerce, which is included in the user information stored in the storage unit. a notification control step for notifying a warning indicating that regular user privileges will expire from a date several days in advance;
A management method that has computer,
a communication control unit that controls the communication unit to mediate the transmission and reception of various data between terminal devices of each business partner conducting electronic commerce via the network;
From a predetermined number of days before the expiration date of the authorized user authority, based on expiration date information indicating the expiration date of the user authority to legitimately use the e-commerce, which is included in the user information stored in the storage unit. , to function as a notification control unit that notifies a warning indicating that regular user privileges are about to expire;
A management program featuring:

Images