JP2009110197A - Purchasing practice system, purchasing practice processing method, and purchasing practice processing program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To achieve definition and use of a settlement rule for individual user assuming that a common program resource is used among users of a purchasing practice system. <P>SOLUTION: The purchasing practice system 100 comprises: a settlement route setting reception means 110 for receiving settlement route data associating a transaction attribute with a settler attribute from each user terminal or the like to store it in a storage device in units of users; a settlement route control means 111 for selecting settlement route data for which transaction request data matches an attribute of transaction of the settlement route data and for performing internal settlement processing; and a transaction mediation execution means 112 for transmitting, to a terminal of a transaction partner, data of ordering or order reception of a transaction as a settlement target when necessary settlement by a settler is achieved. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a purchasing business system, a purchasing business processing method, and a purchasing business processing program. Specifically, in an environment (ASP or the like) that can be used jointly by a plurality of companies or organizations with different approval standards, each company or organization The present invention relates to a technology that can use a common program resource and can set and use an approval route for each company or organization.

For example, in a purchasing business system of a company, it is common for a plurality of purchasing companies or organizations to use the same system for the purpose of reducing operation costs or joint purchasing. The purchasing business system that realizes them has a format (ASP or the like) in which a plurality of purchasing companies or organizations can logically divide and use resources of one system, and program resources are common. The approval function of such a purchase business system is limited based on the approval rules of about 2 or 3 final approval stages depending on the purchase amount and the like, which are determined in advance in the purchase business system. When using the approval rules of the purchasing company or organization to be used without using the approval rules determined in advance by the system, import the data of purchased products into the system operated by each purchasing company or organization and Approval work is carried out in the system of the company or organization, and a method such as linking only order data is adopted.
http://www.withkaunet.com/top/info13.html http://www.withkaunet.com/top/info03.html https://www.webmethods.co.jp/pdf/Biz.pdf

  As described above, in a conventional purchasing business processing environment (an environment in which resources in a system such as ASP are logically divided) that can be used jointly by a plurality of companies or organizations with different approval criteria, each company or organization Use common program resources. In such an environment, when individual approval criteria for each company or organization are individually realized on the purchasing business system, the versatility of the functions and services provided by the purchasing business system is impaired, and Cost burden due to individual development accompanying the countermeasures will be incurred every time, and the burden of costs etc. at each company or organization will increase. On the other hand, in order to avoid such a problem, even when a linkage method as shown in non-patent literatures is used, development costs and operation costs are incurred in the system of each company or organization.

  The present invention has been made in view of such points, and realizes the definition and use of individual user approval rules on the premise that a common program resource is used among users of a purchasing business system. For the purpose.

  The purchasing business system of the present invention is used in a purchasing business system that jointly uses between users such as companies and organizations and performs transaction mediation processing of goods and services between the users. Approval that associates the attributes of the transaction to be approved with the attributes of the approver required for the approval as data of the approval route in the internal approval required for each user from the user terminal Accepting route data for each user and storing the decision route data in the storage device, and accepting route setting accepting means, accepting the transaction request data of the product / service from the user terminal, the transaction request data and the decision making The user who issued the transaction request data in the storage device with the approval route data matching the transaction attribute of the route data An approval route control means for selecting from among the approval route data associated with the last user, and executing internal approval processing in the user based on the approval route data selected here, and the internal approval processing As a result, a transaction mediation execution means is provided for transmitting the order or order data of the transaction that was the object of approval to the terminal of the user's counterpart when the necessary approval is obtained.

  According to this, it is possible to realize an original approval standard of each company or organization on the purchasing business system on the premise that a common program resource is used among users of the purchasing business system. Since the premise of using common program resources among users of purchasing business systems is maintained, the versatility of functions and services provided by purchasing business systems is impaired in order to achieve approval processing for each user. The conventional problem that the cost burden due to the individual development accompanying the measures corresponding to each approval standard occurs every time is solved. Therefore, it is possible to realize the definition and use of individual user approval rules on the assumption that a common program resource is used among users of the purchasing business system.

In the purchasing business system, the approval route setting reception means transmits data of an input reception screen of the approval route data to a user terminal or an input interface, and the user terminal or the input interface It is for receiving the approval route data input on the input reception screen, and the input reception screen data includes an interface for receiving the setting of the approval authority level of each approval person included in the approval route, and the number of approval stages included in the approval route. And an interface for accepting the setting of the required approval authority level of the approver.
According to this, it is possible to set an authorizer having an appropriate authority level as the approval route data as the approval route data, and the effect of the present invention in which an approval route can be set for each user is This is further enhanced in terms of improving the flexibility of setting another approval route.

Further, the purchasing business system stores a candidate for authorizer for each user and data of an authorization authority level in a storage device, and the authorization route setting accepting means is a user terminal via the input accepting screen. Alternatively, if the setting of the required approval authority level for each number of approval steps is accepted from the input interface, the finalizer candidate having an approval authority level equal to or higher than the required approval authority level received here is specified in the storage device and approved. It is also possible to generate a candidate candidate list, transmit data of the candidate list of authorizers to the user terminal or the input interface, and accept an instruction for selecting an authorizer from the candidate list of authorizers.
According to this, as a user who sets the approval route, the processing efficiency when determining the approver increases, and the possibility of setting the approver who has insufficient approval authority level in the approval route data is solved.

In the purchasing business system, the approval route setting reception means transmits data of an input reception screen of the approval route data to a user terminal or an input interface, and the user terminal or the input interface It is for receiving the approval route data input on the input reception screen. The input reception screen data includes an interface for accepting the attribute setting of the order item or the order received for the transaction to be approved by the approval route, accounting processing, etc. Interface for accepting cost burden source information that is information for receiving, interface for accepting setting of transaction amount range for transactions that are subject to approval processing by the approval route, and attributes related to users who issue transaction request instructions for products and services on user terminals An interface for accepting settings, It may be.
According to this, it becomes possible to set specific transaction contents as the transaction attributes that serve as a reference when automatically selecting an approval route as the approval route data, improving the flexibility of setting an approval route for each user. The effect of increases.

Further, in the purchasing business system, the approval route control means accepts transaction request data of goods / services from a user terminal, and from this transaction request data, attribute data of ordered items or received orders of transactions, transaction transactions Amount data and attribute data related to the user who has instructed the transaction request are read, the data read from the transaction request data, and the attributes of the order item or the order item set in the settlement route data, the transaction amount range, and the cost The settlement route data that matches the burden source information and the user attribute is selected from among the settlement route data associated with the user of the user terminal that issued the transaction request data in the storage device, Based on the selected approval route data, the user may execute an internal approval process.
According to this, it becomes possible to set specific transaction contents as the transaction attributes that serve as a reference when automatically selecting an approval route as the approval route data, improving the flexibility of setting an approval route for each user. In addition, it is possible to select an appropriate settlement route according to the specific content of the transaction.

Further, the purchasing business system stores common approval route data across users in a storage device, and the approval route control means includes the transaction request data and transaction attributes of the approval route data, and When selecting settlement route data that matches, the transaction request data and transaction attributes match in the settlement route data associated with the user of the user terminal that issued the transaction request data in the storage device. If there is no approval route data to be selected, the common approval route data may be selected from the storage device.
According to this, it is possible to set individual approval route data for each user, while suppressing the physical capacity of the approval route data registered in the storage device or various master data for setting the approval route data, The data maintenance / management in the storage device can be simplified, and the operation cost can be reduced as a system.

Further, in the purchasing business system, the settlement route data common across the users is set for each of one or a plurality of transaction attributes, and the settlement route control means includes the transaction request data and the transaction request data. In selecting the approval route data that matches the transaction attribute of the approval route data, in the approval route data associated with the user of the user terminal that issued the transaction request data in the storage device, If there is no settlement route data that matches the transaction request data and the transaction attribute, the common settlement route data in the storage device is selected for the predetermined attribute data of the transaction included in the transaction request data. It may be a thing.
According to this, the physical capacity of the decision route data registered in the storage device or various master data for setting the decision route data is suppressed, and the data maintenance and management in the storage device can be simplified. It is also possible to automatically select a decision route according to the attribute, and it is possible to optimize decision making route selection while simplifying data maintenance and management.

Further, the purchasing business system stores a network address of an authorizer terminal used by an authorizer, which is set in the approval route data, in a storage device, and the approval route control means is configured to select the selected approval route. When executing the internal approval process based on the data, the approval request data is transmitted together with the transaction request data to the address of the approver terminal included in the approval route data, and whether or not approval is allowed by the approver from the approver terminal. Input data is acquired, it is determined whether the approval of all the authorizers specified in the approval route data is obtained, and it is determined that the approval of all the authorizers specified in the approval route data is obtained by the determination. If so, the transaction execution means may be notified.
According to this, the purchasing business system automatically selects the approval route according to the transaction attribute, and also automatically acquires the approval data and the subsequent processing by the approver along the automatically selected approval route. Need not separately perform internal approval processing along the approval route.

Further, according to the purchasing business processing method of the present invention, a computer that performs joint mediation among users such as companies and organizations, and performs transaction mediation processing of goods and services between the users is an input interface or the user's As the data of the approval route in the internal approval required for each user from the user terminal used in the transaction of goods / services, the attributes of the transaction to be approved and the attributes of the approver required for approval are associated with each other. Accepting approval route data for each user, storing the approval route data in a storage device, accepting transaction request data for goods / services from a user terminal, and transacting the transaction request data and the approval route data In the storage device, the approval route data that matches the attribute of the user is associated with the user of the user terminal that issued the transaction request data. A process for executing internal decision processing by the user based on the decision route data selected here, and a result of the internal decision process, a necessary decision by the author is obtained. In this case, a process of transmitting order data or order data of a transaction that has been approved is transmitted to the terminal of the user's trading partner.
According to this, it is possible to realize an original approval standard of each company or organization on the purchasing business system on the premise that a common program resource is used among users of the purchasing business system. Since the premise of using common program resources among users of purchasing business systems is maintained, the versatility of functions and services provided by purchasing business systems is impaired in order to achieve approval processing for each user. The conventional problem that the cost burden due to the individual development accompanying the measures corresponding to each approval standard occurs every time is solved. Therefore, it is possible to realize the definition and use of individual user approval rules on the assumption that a common program resource is used among users of the purchasing business system.

In addition, the purchasing operation processing program of the present invention can be shared between each user such as a company or organization, and can be used in a computer that performs transaction mediation processing of goods, services, etc. between the users. As the data of the approval route in the internal approval required for each user from the user terminal used in the transaction of goods / services, the attributes of the transaction to be approved and the attributes of the approver required for approval are associated with each other. Accepting approval route data for each user, storing the approval route data in a storage device, accepting transaction request data of goods / services from a user terminal, and transacting the transaction request data and the approval route data To the user of the user terminal that issued the transaction request data in the storage device. A step of executing the internal approval process in the user based on the selected approval route data is selected from the attached approval route data, and as a result of the internal approval process, a necessary approval person's approval is determined. If obtained, the step of transmitting the order or order data of the transaction to be approved to the terminal of the user's trading partner is executed.
According to this, it is possible to realize an original approval standard of each company or organization on the purchasing business system on the premise that a common program resource is used among users of the purchasing business system. Since the premise of using common program resources among users of purchasing business systems is maintained, the versatility of functions and services provided by purchasing business systems is impaired in order to achieve approval processing for each user. The conventional problem that the cost burden due to the individual development accompanying the measures corresponding to each approval standard occurs every time is solved. Therefore, it is possible to realize the definition and use of individual user approval rules on the assumption that a common program resource is used among users of the purchasing business system.

  In addition, the problems disclosed by the present application and the solutions thereof will be clarified by the embodiments of the present invention and the drawings.

  According to the present invention, it is possible to define and use an approval rule for each user on the assumption that a common program resource is used among users of a purchasing business system.

--- System configuration ---
Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a configuration diagram of a purchasing business system 100 in the present embodiment. A purchase business system 100 (hereinafter, system 100) in the present embodiment is a computer system that is jointly used among users such as companies and organizations, and performs transaction mediation processing of products and services between the users. This system 100 can be said to be a computer that provides an environment in which a plurality of purchasing companies 2 or organizations with different approval criteria can be jointly purchased (an environment in which resources in a system such as ASP are logically divided). And its business partner 3 can be used simultaneously via the network 140 such as the Internet.

  Therefore, the system 100 is connected to a large number of user terminals 300 (preferably also to the authorizer terminal 400) via the network 140, and is used on the network as an electronic market for transaction processing of goods and services between the user terminals. It is possible to assume a server device that provides a place for product search, data processing for orders, order / order reception, transaction history management, and approval processing. The user terminal 300 is used by the purchasing company terminal 350 that is used by the purchasing company 2 that purchases goods / services, and is used by the customer company 3 that receives the orders from the purchasing company 2 and delivers the products / services. A business partner terminal 360 is assumed.

  Further, the system 100 includes a login program 4, a request source program 5, and a supplier program 6 in the storage device 101. The request source program 5 includes a product search function 10 for searching for products that the purchasing company 2 wants to order, an order request function 11 for receiving and processing orders from the purchasing company 2, and a user-specific decision route. An approval function 12 for performing the approval process and an order performance management function 13 for managing history data of orders placed by users are realized. Further, in the supplier program 6, an order receiving function 14 for receiving and processing an order from the purchasing company 2, and a shipment for registering data when the supplier company 3 performs shipping processing of the corresponding product or the like according to the order. The registration function 15 and the like are realized.

  It is assumed that the user authority related to the purchasing business is “requester” or “finalizer”. In the purchasing process, a user having the authority of “requester” belonging to each purchasing company 2 (hereinafter referred to as “requester user”) logs in to the system 100 using the login program 4, and the request source program 5 Approval request data is generated using the product search function 10 and the order request function 11. On the other hand, a user who has the authority of “authorizer” (hereinafter referred to as “authorizer user”) logs in to the system 100 using the login program 4 and uses the approval function 12 of the request source program 5 to perform an approval process. I do.

  At this time, the system 100 stores in the storage device 101 the network address of the authorizer terminal 400 used by the authorizer set in the approval route data. Then, the approval function 12 (the approval route control unit 111) transmits an approval request together with an order request (transaction request data) to the address of the approver terminal 400 included in the approval route data. The approval request data is, for example, screen data including an interface for accepting an approval approval / disapproval input. Then, the approval function 12 obtains input data indicating whether or not approval by the authorizer is obtained from the authorizer terminal 400, determines whether the approval of all the authorizers specified in the approval route data is obtained, and the determination determines the If it is determined that the approval of all the approvers specified in the approval route data is obtained, this is notified to the order request function 11 (transaction executing means).

  Since the authorizer can set a plurality of approval requests for one approval request item, it becomes an official order item to the business partner company 3 when all the set approval persons complete the approval.

  A user who has the authority of “contact person in charge” at the supplier company 3 logs in to the system 100 by using the login program 4, and uses the supplier program 6 for the official order item created by the purchasing company 2. The order receiving function 14 and the shipping registration function 15 are used to perform order receipt / shipment processing. For each user's attribute information, purchase results, product information, and other information required for use, in the database 7 common to all users in the storage device 101 in the system, for each purchasing company 2 or supplier company, etc. Are stored in a logically divided space.

  In addition, the system 100 according to the present embodiment includes a WEB server 8 and a DB server 9. The WEB server 8 includes the login program 4, the request source program 5, and the supplier program 6 in a storage device as business applications. The DB server 9 also includes a user attribute master 125, product data as a list of products / services exchanged by the system 100, order data of products / services handled by the system 100, order record data, approval route data (application of approval route) The condition master 126 and the decision route control master 127) are stored in the storage device 101 as the database 7. When each function in the business application is executed, the WEB server 8 extracts / writes each information in the database 7 of the DB server 9 via the network 140.

  Such a system 100 reads out a program 102 stored in a storage device 101 such as a non-volatile memory into the memory 103 and executes it by the CPU 104 which is an arithmetic device in order to realize a function of executing the purchase transaction processing method. In addition, the system 100 is responsible for communication with various input buttons 105, a keyboard, and other input interfaces 105 that are generally included in computer devices, an output interface 106 such as an LED and a display, and the user terminal 300 and the authorizer terminal 400. A communication device 107 is included.

  Next, functional units that are configured and held by the system 100 based on the program 102 will be described. As described above, each functional unit may be integrally provided in one server device or the like. However, an example in which each functional unit is distributed and arranged in a plurality of computers on the network 140 and cooperates under the initiative of a predetermined server device. It may be assumed.

  The system 100 uses the input interface 105 or the user terminal 300 used by the user to determine the attribute of the transaction to be approved as the data of the approval route in the internal approval required for each user in the transaction of goods / services. And an approval route setting receiving means 110 for receiving approval route data that associates the attributes of the approver necessary for approval with each user and storing the approval route data in the storage device 101. This approval route setting accepting unit 110 can be assumed to be realized by the request source program 5 described above.

  In addition, the system 100 receives transaction request data for goods / services from the user terminal 300, and sets the approval route data in which the transaction request data matches the transaction attribute of the approval route data in the storage device 101. Selecting from among the settlement route data associated with the user of the user terminal 300 that issued the transaction request data, and executing the internal settlement process in the user based on the selected settlement route data. An approval route control unit 111 is provided. This approval route control means 111 can be assumed to be realized by the request source program 5.

  In addition, when the necessary final approval is obtained as a result of the internal approval process, the system 100 transmits the order or order data of the transaction to be approved to the terminal of the transaction partner of the user. The transaction mediation execution means 112 is provided. This transaction mediation execution means 112 can be assumed to be realized by the request source program 5 and the supplier program.

  The approval route setting reception means 110 transmits the input data of the approval route data to the user terminal 300 or the input interface 105, and the input is performed from the user terminal 300 or the input interface 105. It receives the approval route data input on the reception screen, and the input reception screen data includes an interface for accepting the setting of the approval authority level of each approval person included in the approval route, and the approval in each approval step number included in the approval route. And an interface for accepting the setting of the mandatory approval authority level of the user.

  Further, the system 100 stores the authorizer candidate for each user and the data of the authorization authority level in the storage device 101, and the authorization route setting accepting unit 110 receives the user via the input acceptance screen. If the setting of the required approval authority level for each number of approval stages is received from the terminal 300 or the input interface 105, the finalizer candidates having the approval authority level equal to or higher than the required approval authority level received here are stored in the storage device 101. A final decision candidate list is generated by specifying, and data of the final decision candidate list is transmitted to the user terminal 300 or the input interface 105, and an instruction for selecting a final decision person from the final decision candidate list is received. It is good also as.

  Further, the approval route setting receiving means 110 transmits the input data of the approval route data input screen to the user terminal 300 or the input interface 105, and the input from the user terminal 300 or the input interface 105 is performed. The receiving route data input on the receiving screen is received, and the input receiving screen data includes an interface for accepting attribute settings of an order item or an ordered item of a transaction to be approved by the approval route, and an accounting process, etc. Interface for accepting cost-bearing source information, the interface for accepting the setting of the transaction amount range for transactions that are subject to the approval process by the approval route, and attribute settings for users who issue product / service transaction request instructions on the user terminal And an interface for receiving It may be.

  Further, the approval route control means 111 accepts transaction request data of goods / services from the user terminal 300, and from this transaction request data, attribute data of ordered items or received orders of transactions, transaction amount data of transactions, Read the attribute data related to the user who issued the transaction request instruction, the data read from the transaction request data, the attributes of the order item or the order item set in the approval route data, the transaction amount range, the cost burden source information, and The settlement route data that matches the user attribute is selected from among the settlement route data associated with the user of the user terminal 300 that issued the transaction request data in the storage device 101, and is selected here. The user may execute internal approval processing based on approval route data.

  Further, the system 100 stores common settlement route data across users in the storage device 101, and the settlement route control means 111 includes the transaction request data and the transaction attributes of the settlement route data. When selecting the settlement route data that matches, the settlement request data and transaction attributes are included in the settlement route data associated with the user of the user terminal 300 that issued the transaction request data in the storage device 101. If there is no decision route data that matches, the common decision route data may be selected from the storage device 101.

  Further, the common settlement route data across the users is set for each of one or a plurality of transaction attributes, and the settlement route control means 111 includes the transaction request data and the settlement route data. When selecting the settlement route data that matches the transaction attribute, the transaction request data is included in the settlement route data associated with the user of the user terminal 300 that issued the transaction request data in the storage device 101. If there is no settlement route data that matches the transaction attribute, the common settlement route data in the storage device 101 is selected for the predetermined attribute data of the transaction included in the transaction request data. There may be.

  Further, the system 100 stores in the storage device 101 the network address of the authorizer terminal 400 used by the authorizer set in the approval route data, and the approval route control unit 111 selects the selected address. When executing the internal approval process based on the approval route data, the approval request data is transmitted together with the transaction request data to the address of the approver terminal 400 included in the approval route data. The input data of approval / disapproval by is obtained, it is determined whether the approval of all the authorizers specified in the approval route data is obtained, and the approval of all the authorizers specified in the approval route data is obtained by the determination If it is determined, this may be notified to the transaction execution means.

  The functional units 110 to 112 in the system 100 described so far may be realized as hardware, or as a program stored in an appropriate storage device such as a memory or an HDD (Hard Disk Drive). Also good. In this case, the CPU of the system 100 reads the corresponding program from the storage device into the memory in accordance with the program execution, and executes it.

--- Example of table structure ---
Next, the structure of the table used by the purchasing business system 100 in this embodiment will be described. FIG. 2 is a diagram showing examples of data structures of (a) the user attribute master 125, (b) the approval route application condition master 126, and (c) the approval route control master 127 in the present embodiment.

  The user attribute master 125 stores attributes relating to a user who issues a product / service transaction request instruction at the user terminal 300. For example, the user ID is used as a key to identify the company code of the company to which the user belongs, This is a collection of records in which data such as codes, department codes, approval authority types, and approval authority levels are associated. Here, “user” refers to a person who actually operates the user terminal 300 such as an employee or employee belonging to “user” (= company or organization) in the claims of the present invention.

  The approval route application condition master 126 describes the selection conditions when the system 100 selects the approval route data according to the transaction attributes. For example, the approval route definition ID as the ID of the approval route is used as a key. Can adopt this decision route, company code, business location code, department code, standard unit price range (transaction amount range), priority (order to be preferentially selected under the condition that multiple decision route data can be selected) It is a collection of records that associate such data.

  Further, the approval route control master 127 stores the definition contents of each approval route data for each user (company or organization). For example, the number of approved approval steps (the number of approval steps) using the approval route definition ID as a key. , Authorizer company code, authorizer office code, authorizer department code, authorizer code, address of authorizer terminal 400 used by the authorizer, authorizer's authority to approve the number of decision stages This is a set of records in which data such as a required approval authority level as a level and a required flag indicating the required number of approval steps are associated with each other.

  In the approval route application condition master 126 and the approval route control master 127, common application conditions and approval route data may be set across users. In this case, as shown in the figure, as one of the application conditions ("WF5" in the figure) stored in the approval route application condition master 126, the company code, the office code, the department code, the type of approval authority For example, “@” is set in each data item such as the approval authority level. This “@” is a mark indicating that the attributes of all users who use the system 100 are replaced therewith and applied. Similarly, as one of the approval route data stored in the approval route control master 127 (“WF5” in the figure), an authorizer company code, an authorizer office code, and an authorizer department as attribute information of the authorizer For example, “@” is set in each data item such as a code. The common approval route data across the users may be set for each of one or a plurality of transaction attributes. For example, common approval route data corresponding to company codes “K1” to “K3”, common approval route data corresponding to transaction amounts “100,000 yen” to “500000 yen”, and so on.

--- Processing flow example 1 ---
Hereinafter, the actual procedure of the purchase transaction processing method in the present embodiment will be described with reference to the drawings. Note that various operations corresponding to the purchase transaction processing method described below are realized by programs that the system 100 reads into the memory and executes. And this program is comprised from the code | cord | chord for performing the various operation | movement demonstrated below.

  FIG. 3 is a diagram illustrating a processing procedure example 1 of the purchasing operation processing method according to the present embodiment. Here, a processing flow when a client user belonging to each purchasing company 2 purchases a product will be described. When a client user who logs in to the system 100 accesses the login program 4 of the WEB server 8 via the network 140, the login program 4 has a user ID and password for the purchasing company terminal 350 used by the client user. Sends data for a screen that can be entered (hereinafter referred to as the login screen).

  On the other hand, the requester user inputs the user ID and password on the login screen of the purchasing company terminal 350 and presses the login button. Then, input information is transmitted from the purchasing company terminal 350 to the login program 4 of the WEB server 8 via the network 140.

  The login program 4 of the WEB server 8 refers to the user attribute master 125 of the DB server 9 via the network 140 and determines that the password transmitted from the purchasing company terminal 350 is correct. The company identification category, company code, business office code, department code (hereinafter referred to as client user affiliation information), approval level, and authority data are extracted (S301).

  Next, the login program 4 determines the authority of the requester user extracted in step S301 (S302), and if it is the “requester” authority, executes the product search function 10 and the order request function 11. Data of a screen (hereinafter referred to as a client menu screen) on which a button that can be used is displayed is transmitted to the purchasing company terminal 350 used by the client user (S303). On the other hand, if the authority of the requester user is other than the “requester” authority, screen data on which a button for executing a function that can use each other authority is displayed is transmitted to the purchasing company terminal 350.

  When the client user executes the product search button displayed on the client menu screen at the purchasing company terminal 350, an execution request is sent from the purchasing company terminal 350 to the product search function 10 of the WEB server 8 via the network 140. Is transmitted (S304).

  Upon receiving the execution request, the product search function 10 of the WEB server 8 transmits data on a screen (hereinafter referred to as a product search screen) on which a condition for searching for a product can be input to the purchasing company terminal 350 of the requester user. (S305).

  When the requester user inputs a search condition on the product search screen displayed on the purchasing company terminal 350 and executes a search button, the search condition is sent from the purchasing company terminal 350 via the network 140 to the product of the WEB server 8. It is transmitted to the search function 10 (S306).

  The product search function 10 of the WEB server 8 extracts product data that matches the search condition from the product data of the DB server 9 based on the search condition transmitted from the purchasing company terminal 350. Then, data of a screen on which the extraction result is displayed (hereinafter referred to as a search result screen) is transmitted to the purchasing user terminal 350 of the requester user (S307).

  When the requester user selects a product to be ordered from the search result screen displayed on the purchasing company terminal 350 and executes the order request creation button, the execution request is transmitted from the purchasing company terminal 350 via the network 140 to the WEB. It is transmitted to the order request function 11 of the server 8 (S308).

  When the order request function 11 of the WEB server 8 receives the execution request from the purchasing company terminal 350, the delivery destination information of the product selected by the requesting user to the purchasing company terminal 350 of the requesting user via the network 140. Then, data of an order request creation screen (hereinafter referred to as an order request creation screen) capable of input relating to expense burden source information and authorizer information (hereinafter referred to as order request information) is transmitted (S309). When the requester user inputs order request information on the order request creation screen and designates an authorizer by a processing method to be described later and executes an order request button (S310), product information, delivery via the network 140 is executed. The destination information and cost burden source information are transmitted from the purchasing company terminal 350 to the order request function 11 of the WEB server 8. When the order request function 11 receives the order request information from the purchasing company terminal 350, the order request function 11 writes the order data and performance data of the DB server 9 as an approval request case via the network 140 (S311).

  Prior to step S311, the internal approval process is executed based on the approval route data automatically selected by the order request function 11 and designated by the requester user. In this process, the order request function 11 transmits the approval request data together with the order request information (transaction request data) to the address of the approver terminal 400 of the approver included in the automatically selected approval route data. Then, input data indicating whether or not the authorizer is authorized is obtained from the authorizer terminal 400, and it is determined whether the approval of all the authorizers specified in the approval route data has been obtained, and is determined in the approval route data by the determination. If it is determined that the approval of all the authorizers has been obtained, step S311 is executed.

--- Processing flow example 2 ---
Next, detailed processing when performing automatic selection of a decision route and setting of a decision maker in steps S308 to S311 of the processing flow example 1 will be described. FIG. 4 is a diagram illustrating a processing procedure example 2 of the purchasing operation processing method according to the present embodiment. The order request function 11 of the request source program 5 includes an order request screen display module 5a, an authorizer setting screen display module 5b, an authorizer list screen display module 5c, and an order request creation module 5d.

  In step S308 of the processing flow example 1, the requester user presses the order request creation button. After the web server 8 receives an execution request via the network 140 in step S309 (S501), the order request screen display module 5a. Transmits the order request creation screen G601 shown in FIG. 5 to the purchasing company terminal 350 of the requester user (S502).

  In step S310, the requester user inputs the expense burden source information G602 of each product to be purchased on the order request creation screen G601, and executes the approver setting button G603. Then, the execution request is transmitted from the purchasing company terminal 350 to the approver setting screen display module 5b of the WEB server 8 via the network 140 (S503).

  After receiving the execution request, the approver setting screen display module 5b, the affiliation information of the requester user acquired in step S301, the information on the product selected by the requester user in step S308, Using the expense burden source information G602 specified on the order request creation screen G601 as an application condition, an approval route definition ID that matches the application condition is extracted from the approval route application condition master 126 of the DB server 6 via the network 140. At this time, if there is no decision route definition ID that matches the application condition, error processing is performed. On the other hand, if there is an approval route definition ID that matches the application condition, all the applicable approval route data is extracted from the approval route control master 127 using the extracted approval route definition ID as a key (S504).

  The approver setting screen display module 5b extracts the required flag of each setting approval step number and the maximum value of the setting approval step number in each approval route data extracted from the approval route control master 127, and the number of setting person setting fields corresponding to that number. Then, the authorizer setting screen G701 (see FIG. 6) in which “mandatory designation” and “optional designation” are displayed for each setting step number and the authorizer search button G702 is displayed on the purchasing user terminal 350 of the requester user, and the network 140 is connected. (S505).

  When the requester user executes the authorizer search button G702 for each number of stages on the authorizer setting screen G701 displayed on the purchasing company terminal 350, the execution request and the data of the number of settlement stages G703 for which the search button has been executed are obtained. Then, the data is transmitted from the purchasing company terminal 350 to the approver list screen display module 5c of the WEB server 8 via the network 140 (S506).

  The approver list screen display module 5 c receives the execution request from the purchasing company terminal 350. Then, by referring to the approval route definition ID extracted in step S504 and the data of the approval step number G703 transmitted from the purchasing user terminal 350 of the client user, the corresponding data is referred to from the approval route control master 127 of the DB server 9. To do. Also, specify the number of steps from the user attribute master 125 using the authorizer company code, authorizer office code, authorizer department code, required authorisation level, and authorizer code set in the data referenced here as keys. Information on possible authorizer users is extracted (S507). At this time, the extracted authorizer must be a user having an approval level higher than the required approval level.

  Subsequently, the order request function 11 transmits the information on the approver user extracted by the approver list screen display module 5c as the approver list screen G801 shown in FIG. S508). When the requester user selects an authorizer to be set from the authorizer list transmitted from the order request function 11 on the authorizer screen G801 and presses the selection button G802, the authorizer setting screen of FIG. As shown in G704, the approver (“USER2” in the example in the figure) is set to the corresponding step number (“1” in the example in the figure) on the authorizer setting screen (S509).

  Steps S506 to S509 are repeated until the requester user has set the finalizer for all the number of finalization stages for which the finalist designation is required. When the requester user executes the apply button G705 on the approver setting screen of the purchasing company terminal 350 after setting is completed for all the approvers, the requester user has set as shown in the order request creation screen G604. A series of authorizers (that is, the authoritative route) is displayed.

  When the requester user repeatedly executes the necessary processing in steps S503 to S509 for the purchased product, the requester user presses the order request creation button on the order request creation screen. At this time, the purchasing company terminal 350 checks the final requester's required settings for the order request corresponding to each product, and checks the consistency between the authorizer's organization information and the approval route. The order request creation data is transmitted to the order request creation module 5d. The order request creation module sends the data received from the purchasing company terminal 350 to the DB server 9 as an order request item and registers it as order request data and performance data (S510).

--- Example of automatic selection control of approval route 1 ---
FIG. 8 shows a setting example of the user attribute master 125, the approval route application condition master 126, and the approval route control master 127, and an example of automatic selection control of the approval route. In this example, the decision route definition ID is defined in three ways: WF1 (D911), WF2 (D912), and WF3 (D913). In addition, for the data of the approval route definition IDs WF1 (D911) and WF2 (D912), the requester user who belongs to the company code “K1”, the office code “001”, and the department code “A” makes an approval request. It is a description extracted when doing. Further, when the unit price of the purchased product is 10,000 yen or more, the data of the approval route definition ID is WF2 (D912), and in other cases, the data of WF1 (D911) is adopted.

  In addition, when the client user belongs to the company with the company code “K2”, it is described that the data of the approval route definition ID WF3 (D913) is adopted. In the approval route control master 127, the application conditions of the approver who can make an approval are set for the number of approval stages whose approval route definition IDs are WF1 to WF3 (D911 to D913). In this setting example, the approval route definition ID is set to 1 step for WF1 (D921), and similarly to 2 steps for WF2 (D922 to D923) and WF3 (D924 to D925).

  For example, the first-stage authorizer with the approval route definition ID WF1 (D911) must be an authorizer with the company code “K1”, the establishment code “001”, and the approval level “1” or higher. In addition, when the approval route definition ID is WF2 (D912), the setting of the authorizer is the same as when the approval route definition ID is WF1 (D921) in the first step in the approval route (D923) of the approval route control master 127. In addition, in the second stage, an authorizer who has approval level 2 or higher and belongs to department code B is essential. In the case where the approval route definition ID is WF3 (D913), the company code “K2”, the office code “111”, and the department code “B” at the first stage in the approval route (D924) of the approval route control master 127. , An authorizer with an approval level of “1” or higher is essential. In addition, in the approval route (D925), for the second stage, an approver having the same company, office code, department code “C”, and approval level “2” or higher can be arbitrarily set.

  For example, when USER1 (D901) issues an approval request for a 100 yen product (example 1), when the approver setting button is pressed in step S503, the order request function 11 requests in step S504. Applying the approval route definition ID of the corresponding approval route with the company code “K1”, the office code “001”, the department code “A” and the purchase unit price “100 yen” as the application conditions Extracted from the condition master 126. At this time, the approval route definition ID corresponding to “WF1” (D911) and “WF2” (D912) including the company code “K1” as an application condition is that the purchased product is smaller than 10,000 yen. The condition “WF1” (D911) is extracted.

  The order request function 11 extracts the corresponding data (D921) from the approval route control master 127 using the approval route definition ID “WF1” as a key. Since the extracted approval route data D921 has only the setting approval stage number 1 (required), in the step S505, the requester user's purchasing company terminal displays the approval person setting screen displaying the approval person designation field for only one stage. 350.

  Further, when the requester user executes the decision-maker search button of the decision step number “1” in step S506, the order request function 11 determines the decision route definition ID “WF1” and the setting approval step number “1” in step S507. As the authorizer who has the mandatory approval level “1” or higher with the processor company code “K1”, processor office code “001”, authority “authorizer” set in the approval route data D921 extracted using Data of USER3 (D903) and USER4 (D904) are extracted.

  In step S508, the order request function 11 transmits the extracted data of USER3 (D903) and USER4 (D904) to the purchasing company terminal 350 of the requester user as a list screen. In step S509, the requester user selects and sets an authorizer from the list screen.

  Similarly, when a product whose USER1 (D901) is 20,000 yen is purchased (example 2), the approval route definition ID extracted in step S504 is “WF1” (D911), “WF2” (D912). Both match the conditions, but “WF2” (D912) having a higher priority is adopted. The order request function 11 extracts corresponding approval route data (D922) and (D923) from the approval route control master 127 using the approval route definition ID “WF1” as a key. Since the data to be extracted is the set approval stage numbers “1” and “2”, the approver designation screen displaying the approval stage number designation column in two stages is displayed by the order request function 11 in step S505 by the requesting user's purchasing company terminal. 350.

  The requester user designates the authorizer by repeating the processing of steps S506 to S509 for each of the first and second stages of approval. At this time, in the processing of step S507, the first stage is the same as USER3 (D903) or USER4 (D904), and the second stage is the company code “K1”, the office code “001”, and the department. Since it is necessary to set an authorizer who belongs to the code “B” and the approval level is “2” or higher, only USER4 (D904) can be set as the authorizer.

  The approval level required in the approval route can also be set for the requester user. For example, when the client user: USER2 (D902) whose approval level is 1 purchases a product of 20,000 yen (example 3), the approval route definition ID extracted in step S504 is (example 2). Similarly, “WF2” (D912) is obtained. However, since the approval level of the requester user: USER2 (D902) is 1, it is determined that the approval authority of the first stage (D922) having the required approval level “1” is also used. For this reason, in step S505, the decision-maker designation field for the first decision stage is hidden, and the decision-maker designation screen displaying the decision-maker designation column for the second decision stage is displayed on the purchasing company terminal 350 of the requester user. Sent. The requester user designates the authorizer by the same process as the second stage designation in Example 2.

  In addition, when the requester user belonging to the company code “K2”: “USER5” (D905) purchases a product (example 4), the order request function 11 in step S504 determines the decision route definition ID “WF3” (D913). (Establishment code and department code are not set in the applicable conditions, so all users belonging to the company code “K2” are extracted as “WF3” (D913)). Further, the order request function 11 extracts the approval route data (D924) and (D925) from the approval route control master 127 using the approval route definition ID “WF3” as a key. Since the decision route data (D925), which is the definition of the second-level finalizer, is an arbitrary setting, the order request function 11 sets the first-level finalizer designation field to “required setting”, 2 in step S505. The column is set to “arbitrary setting”, and the approver setting screen is transmitted to the purchasing user terminal 350 of the requester user.

  When the requester user designates the authorizer in steps S506 to S509, designation of the authorizer of the first approval stage number (the authorizer extracted in the process of step S507 is “USER6” (D906)) Although it is indispensable, the setting of the second-stage finalist is arbitrary, and is set as necessary. In the case of setting, the processes in steps S506 to S509 are performed in the same manner as in the first stage, and the authorizer is set (the authorizer extracted in the process of step S507 is “USER7” (D907)).

--- Example of automatic selection control of decision route 2 ---
Next, with reference to FIG. 9, a method for defining an approval route and an automatic selection process when a plurality of purchasing companies 2 use a common approval route (an approval rule) will be described. When a plurality of purchasing companies 2 use a common approval route, setting approval route data having the same content for each purchasing company in the approval route application condition master 126 and the approval route control master 127 is time-consuming for master revision / elimination. Increase. Further, in step S504, in order to avoid executing error processing when there is no approval route definition to be adopted, there is a wide range of purchasing companies 2 that are adopted when they do not match the individually determined approval route data. It is desirable to set the available definitions in advance.

  In such a case, as shown in FIG. 9, by setting “@” in each item of the approval route application condition master 126 and the approval route control master 127, the adoption condition of the approval route is changed to various attribute information of the requester user. It is possible to replace it (described above with reference to FIG. 2). For example, in FIG. 9, the approval route definition ID “WF4” (D1011) is an individual definition of the company code “K3”, and “WF5” (D1012) is “@” in the company code, the office code, and the department code. This is the definition of the approval route common to all purchasing companies.

  Requester user belonging to the company code “K3”: “USER8” (D1001) purchases a product with a unit price of 100 yen (example 5). Decision route definition ID extracted by the order request function 11 in step S504 Includes “WF5” (D1012) in addition to “WF4” (D1011) individually defined for the company with the company code “K3”. At this time, with respect to the approval route definition ID “WF5” (D1012), the order request function 11 replaces “@” set in the company code, the office code, and the department code with the “USER8” (D1001). The affiliation information “K3”, “001”, and “A” are extracted.

  In this example, the client user: “USER8” (D1001) purchases a product with a unit price of 100 yen, and the approval definition route ID “WF4” (D1011) has a unit price of 10,000 yen or more. Since it is adopted, “WF5” (D1012) for which the purchase unit price condition is not set is extracted.

  The order request function 11 extracts corresponding approval route data (D1023) from the approval route control master 127 using the approval route definition ID “WF5” (D1012) as a key. Further, when the order request function 11 extracts a list of authorizers having the number of decision stages “1” from the user attribute master 125 in step S507, the decision route data (D1023) is the authorizer company code “@”, the authorizer business. Since the office code is “@” and the approver department code is “@”, they are read as the company code “K3”, the office code “001”, and the department code “A” of the requester user. The authorizer user “USER9” (D1002) belonging to the same organization as the user is extracted from the user attribute master 125.

  Although omitted in this example, the “company identification classification” of the user attribute master 125 is a definition for grouping a plurality of companies (affiliated companies, etc.). Similar to codes, etc., it can be used as an application standard when applying a decision route.

  According to the present embodiment, even in an environment where a plurality of companies or organizations with different approval standards can be used jointly (an environment in which resources in a system such as ASP are logically divided), the approval rules for each company or organization are individual. (Admission route) can be adopted. In addition, when a plurality of companies or organizations adopt a common approval standard, the amount of setting of various data such as a master is suppressed by standardizing the approval rule, thereby simplifying data maintenance and management. With these effects, while maintaining the versatility of the functions provided in the purchasing business system, it is possible to reduce the number of development and operation man-hours for the approval processing program, etc. Can be realized.

  Therefore, it is possible to define and use approval rules for individual users on the assumption that common program resources are used among users of the purchasing business system.

  Note that the present invention has been exemplified by an indirect material or direct material purchasing business system connected to a network. However, all business operations that use an approval workflow in which organizational information of the user exists and the approval route changes depending on the content. It can also be used for systems, for example, approval approval work within the same organization or across organizations, and internal report circulation work.

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

It is a whole block diagram of the purchase business system in this embodiment. It is a figure which shows each data structure example of (a) user attribute master in this embodiment, (b) approval route application condition master, and (c) approval route control master. It is a flowchart which shows the process procedure 1 of the purchasing operation processing method of this embodiment. It is a flowchart which shows the process procedure 2 of the purchase business processing method of this embodiment. It is a figure which shows the example of an order request creation screen in this embodiment. It is a figure which shows the example of an authorizer setting screen in this embodiment. It is a figure which shows the example of an authorizer list screen in this embodiment. It is a figure which shows the automatic selection control example 1 of the decision route | root in this embodiment. It is a figure which shows the automatic selection control example 2 of the decision route in this embodiment.

Explanation of symbols

2 purchasing company 3 supplier company 4 login program 5 requester program 6 supplier program 7 database 8 WEB server 9 DB server 10 product search function 11 order request function 12 decision function 13 order performance management function 14 order acceptance function 15 shipping registration function 100 Purchasing Business System 101 Storage Device 102 Program 103 Memory 104 CPU
105 Input Interface 106 Output Interface 107 Communication Device 110 Approval Route Setting Accepting Unit 111 Approval Route Control Unit 112 Transaction Mediation Execution Unit 125 User Attribute Master 126 Approval Route Application Condition Master 127 Approval Route Control Master 140 Network 300 User Terminal 350 (User Of the terminal) Purchasing company terminal 360 (Of the user terminal) Supplier company terminal 400 Finalist terminal

Claims (10)

In a purchasing business system that performs joint mediation among users such as companies and organizations and performs transaction mediation processing of products and services between the users,
From the input interface or the user terminal used by the user, as the data of the approval route in the internal approval required for each user in the transaction of goods / services, the attributes of the transaction to be approved and the approver required for the approval An approval route setting receiving means for receiving approval route data associated with the attributes of each user and storing the approval route data in a storage device;
Accepting transaction request data for a product / service from a user terminal, and using the transaction request data and the transaction route data of the approval route data matching the transaction route data in the storage device An approval route control means for selecting from among the approval route data associated with the user of the user terminal, and executing internal approval processing in the user based on the approval route data selected here;
As a result of the internal approval process, when a necessary approval person's approval is obtained, a transaction mediation execution means for transmitting the order or order data of the transaction to be approved to the terminal of the user's counterpart,
Purchasing business system characterized by comprising The approval route setting receiving means
Sending the data of the acceptance route data input acceptance screen to the user terminal or the input interface, and receiving the decision route data input on the input acceptance screen from the user terminal or the input interface. ,
The input acceptance screen data includes an interface for accepting the setting of the authorization authority level of each authorizer included in the settlement route, and an interface for accepting the setting of the mandatory authorization authority level of the authorizer in each number of settlement stages included in the settlement route. is there,
The purchasing business system according to claim 1, wherein: The purchasing business system stores a candidate for authorizer for each user and data of an authority level for authorization in a storage device,
If the approval route setting reception means receives the setting of the required approval authority level in each approval step number from the user terminal or the input interface via the input reception screen, the approval route setting reception means exceeds the required approval authority level received here. An authorizer candidate having an authorization authority level is specified in the storage device to generate an authorizer candidate list, and data of the authorizer candidate list is transmitted to the user terminal or the input interface. Accepts the decision-maker's selection instructions from
The purchasing business system according to claim 2, wherein: The approval route setting receiving means
Sending the data of the acceptance route data input acceptance screen to the user terminal or the input interface, and receiving the decision route data input on the input acceptance screen from the user terminal or the input interface. ,
The input acceptance screen data includes an interface for accepting attribute settings of an order item or an order received for a transaction that is subject to a settlement process, an interface for receiving cost burden source information that is information for accounting processing, and the like. An interface for accepting a setting of a transaction amount range of a transaction to be approved, and an interface for accepting an attribute setting relating to a user who makes a transaction request instruction for a product / service on a user terminal,
The purchasing business system according to claim 2 or 3, characterized by the above-mentioned. The approval route control means includes:
Accepts transaction request data for products / services from user terminals, and from this transaction request data, conducts order / order attribute data for transactions, transaction transaction amount data, cost burden source information, and transaction request instructions User attribute data
The settlement route data in which the data read from the transaction request data matches the attributes of the order item or the order item set in the settlement route data, the transaction amount range, the cost burden source information, and the user attribute, In the storage device, the user selects from among the approval route data associated with the user of the user terminal that issued the transaction request data, and executes the internal approval processing in the user based on the approval route data selected here To do,
The purchasing business system according to claim 4, wherein: The purchasing business system stores common approval route data in a storage device across users,
The approval route control means includes:
When selecting the settlement route data in which the transaction request data matches the transaction attribute of the settlement route data, the settlement route data associated with the user of the user terminal that issued the transaction request data in the storage device Among them, when there is no settlement route data matching the transaction request data and the transaction attribute, the common settlement route data is selected from the storage device.
The purchasing business system according to any one of claims 1 to 5. The common settlement route data across the users is set for each of one or more transaction attributes,
The approval route control means includes:
When selecting the settlement route data in which the transaction request data matches the transaction attribute of the settlement route data, the settlement route data associated with the user of the user terminal that issued the transaction request data in the storage device If there is no settlement route data in which the transaction request data and the transaction attribute match, among the common settlement route data in the storage device, the predetermined attribute data of the transaction included in the transaction request data is set. To choose
The purchasing business system according to claim 6 characterized by things. The purchasing business system stores the address on the network of the authorizer terminal used by the authorizer set in the approval route data in a storage device,
The approval route control means, when executing the internal approval processing based on the selected approval route data, transmits the approval request data together with the transaction request data to the address of the authorizer terminal included in the approval route data, The input data on whether or not the approval is accepted by the authorizer is obtained from the authorizer terminal, it is determined whether the approval of all the authorizers specified in the approval route data is obtained, and all the approvals specified in the approval route data by the determination If it is determined that the person's approval has been obtained, this is notified to the transaction execution means.
The purchasing business system according to any one of claims 1 to 7. A computer that performs joint mediation among users such as companies and organizations and performs transaction mediation processing of products and services between the users,
From the input interface or the user terminal used by the user, as the data of the approval route in the internal approval required for each user in the transaction of goods / services, the attributes of the transaction to be approved and the approver required for the approval A process for receiving approval route data associated with the attribute of each user and storing the approval route data in a storage device;
Accepting transaction request data for a product / service from a user terminal, and using the transaction request data and the transaction route data of the approval route data matching the transaction route data in the storage device Selecting from among the approval route data associated with the user of the user terminal, and executing internal approval processing in the user based on the approval route data selected here,
As a result of the internal approval process, when a necessary approval person's approval is obtained, a process of transmitting the order or order data of the transaction to be approved to the terminal of the user's transaction partner;
Purchasing business processing method characterized by executing In a computer that is used jointly among users such as companies and organizations and performs transaction mediation processing of products and services between the users,
From the input interface or the user terminal used by the user, as the data of the approval route in the internal approval required for each user in the transaction of goods / services, the attributes of the transaction to be approved and the approver required for the approval Accepting the approval route data associated with the attribute of each user, and storing the approval route data in the storage device;
Accepting transaction request data for a product / service from a user terminal, and using the transaction request data and the transaction route data of the approval route data matching the transaction route data in the storage device Selecting from among the approval route data associated with the user of the user terminal, and executing internal approval processing in the user based on the approval route data selected here;
As a result of the internal approval process, when the approval of the required approver is obtained, the order of the transaction that was the object of approval or the data of the order received is transmitted to the terminal of the transaction partner of the user;
Purchasing business processing program to execute.

Images