JP3818449B2 - Business management apparatus and method, and business management program - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a business management apparatus for managing business related to application and approval in an organization, and further relates to a business management method and a business management program.
[0002]
[Prior art]
Conventionally, a business management apparatus for managing business related to application and approval in an organization has been used.
However, the conventional business management apparatus cannot flexibly cope with a change in the person having the authorization authority due to personnel changes, organizational changes, or the like.
[0003]
[Problems to be solved by the invention]
Accordingly, in view of the above points, an object of the present invention is to provide a business management apparatus that can flexibly cope with personnel changes and the like. It is another object of the present invention to provide such a business management method and business management program.
[0004]
[Means for Solving the Problems]
In order to solve the above problems, a business management device according to the present invention is a device for managing business related to application and approval in an organization, and includes a plurality of members constituting the organization and a plurality of approval authorities. A first table including a plurality of records each storing information relating to a first group of nodes corresponding to a first person, wherein each record uniquely identifies a plurality of constituent members or a first group of nodes A first field for storing an identifier, and a second identifier representing an order in the organization of a plurality of constituent members or a first group of nodes, Of any one of multiple members Second identifier Delete a value of a certain length at least once from the end of Calculation Do By Any one of multiple members of High in the organization and Has approval authority for the application At least one person The first group of nodes corresponding to Obtain a second identifier of at least one node in A first recording means for recording a first table having a second field for storing a second identifier capable of being stored, and a first identifier for uniquely identifying a first group of nodes Record a second table having a first field and a second field for storing a first identifier for uniquely identifying a plurality of members as persons having approval authority related to the first group of nodes. A second recording means, a third table relating to the application, a first field for storing a first identifier for uniquely identifying a person who has made an application among a plurality of constituent members; A third recording means for recording a third table having a second group of fields each storing a plurality of data indicating whether or not approval has been obtained; and a third table Records to be processed By searching the first table based on the first identifier in , Of the person who applied for the record to be processed among multiple constituents The second identifier is extracted, and the extracted second identifier Delete a value of a certain length at least once from the end of Calculation Do Obtained by At least one The value as the second identifier At least one storing By retrieving records from the first table , At least one node identifying at least one node of the first group of nodes corresponding to at least one person who has the authorization to approve an application related to the record to be processed The first identifier was extracted and extracted At least one By searching the second table based on the first identifier, For applications related to records to be processed among multiple members Have authorization At least one person Specified by the first processing means for specifying the person and the first processing means For applications related to records to be processed Have authorization At least one person Indicates that the application has been approved or rejected in response to an approval or rejection instruction from the person At least one piece of data The Record to be processed And second processing means for writing into the second group of fields.
[0005]
Here, the first table may further include a plurality of records each storing information related to the second group of nodes corresponding to a plurality of departments in the organization, and the information in the records becomes effective. It is good also as having a field which stores data showing a day or a valid day.
In addition, the third table may further include a field for storing data representing the date when the information related to the application is input, the date when the case related to the application is performed, or the date when the application is performed.
[0007]
The business management method according to the present invention is a method for managing business related to application and approval in an organization, and is a first corresponding to a plurality of members constituting an organization and a plurality of people having approval authority. A first table containing a plurality of records each storing information relating to a group of nodes, each record storing a first identifier uniquely identifying a plurality of constituents or a first group of nodes And a second identifier representing a rank in the organization of the plurality of constituent members or the first group of nodes, Of any one of multiple members Second identifier Delete a value of a certain length at least once from the end of Calculation Do By Any one of multiple members of High in the organization and Has approval authority for the application At least one person The first group of nodes corresponding to Obtain a second identifier of at least one node in (A) recording a first table having a second field for storing a second identifier that can be stored, and a first table for storing a first identifier for uniquely identifying a first group of nodes. Recording a second table having a first field and a second field storing a first identifier for uniquely identifying a plurality of members as persons having an authorization authority related to the first group of nodes (B), a third table relating to an application, a first field for storing a first identifier for uniquely identifying a person who has made an application among a plurality of constituent members, and an approval for the application A step (c) of recording a third table having a second group of fields each storing a plurality of data indicating whether or not it has been obtained; Records to be processed By searching the first table based on the first identifier in , Of the person who applied for the record to be processed among multiple constituents Extracting a second identifier (d); In step (d) The extracted second identifier Delete a value of a certain length at least once from the end of Calculation Do Obtained by At least one The value as the second identifier At least one storing By retrieving records from the first table , At least one node identifying at least one node of the first group of nodes corresponding to at least one person who has the authorization to approve an application related to the record to be processed The first identifier is extracted in step (e) and extracted in step (e) At least one By searching the second table based on the first identifier, For applications related to records to be processed among multiple members Have authorization At least one person Specified in step (f) and step (f) For applications related to records to be processed Have authorization At least one person Indicates that the application has been approved or rejected in response to an approval or rejection instruction from the person At least one piece of data The Record to be processed Writing to the second group of fields (g).
[0008]
Here, the first table may further include a plurality of records each storing information related to the second group of nodes corresponding to a plurality of departments in the organization, and the information in the records becomes effective. It is good also as having a field which stores data showing a day or a valid day.
In addition, the third table may further include a field for storing data representing the date when the information related to the application is input, the date when the case related to the application is performed, or the date when the application is performed.
[0010]
Furthermore, a business management program according to the present invention is a program for managing business related to application and approval in an organization, and is a first corresponding to a plurality of members constituting an organization and a plurality of people having approval authority. A first table containing a plurality of records each storing information relating to a group of nodes, each record storing a first identifier uniquely identifying a plurality of constituents or a first group of nodes And a second identifier representing a rank in the organization of the plurality of constituent members or the first group of nodes, Of any one of multiple members Second identifier Delete a value of a certain length at least once from the end of Calculation Do By Any one of multiple members of High in the organization and Has approval authority for the application At least one person The first group of nodes corresponding to Obtain a second identifier of at least one node in (A) recording a first table having a second field for storing a second identifier capable of being stored and a first identifier for uniquely identifying a first group of nodes Procedure for recording a second table having a first field and a second field for storing a first identifier for uniquely identifying a plurality of members as persons having approval authority related to the first group of nodes (B), a third table relating to an application, a first field for storing a first identifier for uniquely identifying a person who has made an application among a plurality of constituent members, and an approval for the application A procedure (c) for recording a third table having a second group of fields each storing a plurality of data indicating whether or not it has been obtained; and a third table Records to be processed By searching the first table based on the first identifier in , Of the person who applied for the record to be processed among multiple constituents A procedure (d) for extracting a second identifier; In step (d) The extracted second identifier Delete a value of a certain length at least once from the end of Calculation Do Obtained by At least one The value as the second identifier At least one storing By retrieving records from the first table , At least one node identifying at least one node of the first group of nodes corresponding to at least one person who has the authorization to approve an application related to the record to be processed Extracted in step (e) for extracting the first identifier and in step (e) At least one By searching the second table based on the first identifier, For applications related to records to be processed among multiple members Have authorization At least one person Specified in step (f) and step (f) For applications related to records to be processed Have authorization At least one person Indicates that the application has been approved or rejected in response to an approval or rejection instruction from the person At least one piece of data The Record to be processed The procedure (g) of writing to the second group of the fields is executed by the CPU.
[0011]
Here, the first table may further include a plurality of records each storing information related to the second group of nodes corresponding to a plurality of departments in the organization, and the information in the records becomes effective. It is good also as having a field which stores data showing a day or a valid day.
In addition, the third table may further include a field for storing data representing the date when the information related to the application is input, the date when the case related to the application is performed, or the date when the application is performed.
[0013]
According to the above configuration, even if personnel changes or the like occur, it can be flexibly handled.
[0014]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing a system using a business management apparatus according to an embodiment of the present invention. In the present embodiment, the present invention is applied to a system for managing application and approval work in a company. As shown in FIG. 1, a system 10 includes a server 1 as one embodiment of the present invention and client terminals 11 to 1n, which are connected to each other via a network.
FIG. 2 is a diagram showing a configuration of the server 1 of FIG. As shown in FIG. 2, the server 1 includes an application table recording unit 21, an employee table recording unit 22, an approver table recording unit 23, an organization table recording unit 24, a post table recording unit 25, and application data. A creation processing unit 26, an approval route determination processing unit 27, an approval / rejection processing unit 28, and an approval route creation / update processing unit 29 are provided.
[0015]
FIG. 3 is a diagram illustrating an example of an application table recorded in the application table recording unit 21. As shown in FIG. 3, the application table has fields for storing information regarding the contents of the application and information regarding the approval status. The information regarding the contents of the application includes a slip name (for example, vacation notice, direct report, etc.), an implementation date (for example, vacation day, direct date, etc.), and a user ID that uniquely identifies the applicant. Moreover, the information regarding the approval status includes a first approval (for example, section manager approval), a second approval (for example, manager approval), and so on, and a completion flag indicating whether all approvals have been completed. The record in the application table shown in FIG. 3 is a record relating to an application for an employee whose user ID is “Takada” to take leave on May 1, 2003, and this application has not yet been approved. It means not.
[0016]
Referring to FIG. 2 again, the employee table recording unit 22 records an employee table that stores data relating to employees. FIG. 4 is a diagram illustrating an example of an employee table. As shown in FIG. 4, the employee table has fields for storing a user ID for uniquely identifying an employee, an employee number for uniquely identifying the employee, and the employee's name.
[0017]
Referring to FIG. 2 again, the approver table recording unit 23 records an approver table that stores data relating to a person who has approval authority. FIG. 5 is a diagram illustrating an example of the approver table. As shown in FIG. 5, the approver table includes a name of a node corresponding to a person having approval authority, a user ID for uniquely identifying a node corresponding to a person having approval authority, and a person having approval authority. It has a field for storing the user ID of the employee. In the approver table shown in FIG. 5, a node having the name “completion box” is a person who has authority to manage or process application data for which approval has been completed (for example, a general affairs department manager, a general affairs department manager, a human resource, etc. Equivalent to section manager, human resources manager, etc.). Specifically, in the present embodiment, a person who has the authority to manage or process application data for which approval has been completed is an employee whose user ID is “Taro” (here, the name “Taro Sogo” (FIG. 4 )) And an employee whose user ID is “Jiro” (here, the name “Jiro Joso” (see FIG. 4)).
[0018]
Referring to FIG. 2 again, the organization table recording unit 24 records an organization table that stores data related to the organization. FIG. 6 is a diagram illustrating an example of the organization table. As shown in FIG. 6, the organization table stores a record number (No.), a revision date, a user ID, an organization division that is an organization division of the record, an organization affiliation name, a name, and an organization sequence number. Has a field.
[0019]
In the organization table shown in FIG. 6, the revision date represents the date when the data stored in the record becomes valid or the date when it becomes valid.
The organization classification can take values from 1 to 3. Here, the organization classification “1” indicates that the record is a record relating to a node corresponding to a department. The organization classification “2” represents that the record is a record related to a node corresponding to a person who has the authorization authority, and the organization classification “3” represents that the record is a record related to an employee.
[0020]
The organization rank number is a number representing a node in the organization, a node corresponding to a department, a node corresponding to a person having approval authority, or an employee (hereinafter referred to as “employee etc.”). In the present embodiment, the organization order number is a 4n (n is a natural number) digit number, and the organization order number of a certain employee or the like is the organization order number of the most recent employee or the like of the employee or the like. This is a number with a 4-digit number added to the end of the number. For example, in the organization table shown in FIG. 6, the organization record number “0001” is stored in the first record (organization affiliation name “Tokyo head office”), and is positioned below the node represented by the first record. In the second record as the node (organization affiliation name “Tokyo head office”, name “completion box”), the organization order number “00010001” is obtained by adding “0001” to the end of the organization order number “0001” in the first record. Is stored. Further, for example, the employee immediately above the employee “Yumiko Takada” (corresponding to the 14th record) has the value “00010001000100020002000200020002” obtained by deleting the last 4 digits of the organization sequence number “000100010001000200020002000100020002” in the 14th record. It is an employee or the like (here, a node “sales department 1 section 1G approver” corresponding to a person having an approval authority) represented by a record (here, the 12th record) stored as an order number.
[0021]
Referring again to FIG. 2, the post table recording unit 25 records a post table that stores data relating to the post of the employee. FIG. 7 is a diagram illustrating an example of the post table. As shown in FIG. 7, the post table has a field for storing a user ID, a date when the record becomes valid or a revision date indicating a valid date, and a post. In FIG. 7, for example, an employee whose user ID is “Taro” (in this embodiment, the name “Taro Goro” (see FIG. 4)) becomes a general employee on April 1, 1983, and is 1993. It represents that he became General Affairs Division Manager on April 1, 1998, and General Manager Department on April 1, 1998.
[0022]
Referring again to FIG. 2, the application data creation processing unit 26 creates application data in response to a request from an employee who uses the client terminals 11 to 1 n and records the application data in the application table recording unit 21.
The approval route determination processing unit 27 performs a process of determining an employee who should approve an application related to application data in the application table recorded in the application table recording unit 21.
[0023]
The approval / rejection processing unit 28 performs approval or rejection processing in accordance with an instruction from the employee determined by the approval route determination processing unit 27.
The approval route creation / update processing unit 29 creates or updates the approver table or the organization table.
[0024]
The application data creation processing unit 26, the approval route determination processing unit 27, the approval / rejection processing unit 28, and the approval route creation / update processing unit 29 shown in FIG. 2 can be configured by a CPU and software (program). This program, application table, employee table, approver table, organization table, and post table are recorded on a recording medium such as a hard disk, flexible disk, MO, MT, RAM, CD-ROM, or DVD-ROM. can do.
[0025]
FIG. 8 is a flowchart showing an outline of the application data creation process of the server 1. Hereinafter, the application data creation process of the server 1 will be described with reference to FIG. Here, it is assumed that the employee “Yumiko Takada” creates application data related to a vacation notice.
First, an employee (here, “Yumiko Takada”) using a client terminal (here, referred to as client terminal 11) receives information about the contents of the application (here, slip name “notification of vacation” and vacation). The date desired to be acquired “2003/05/01”) is input, and the application data creation processing unit 26 of the server 1 receives this condition (step S101).
[0026]
Next, the application data creation processing unit 26 creates application data having a slip name “Notification of vacation”, an implementation date “2003/05/01”, and a user ID “Takada” (see FIG. 3), and an application table recording unit 21 (step S102).
[0027]
FIG. 9 is a flowchart showing an outline of the approval / rejection process of the server 1. Hereinafter, the approval / rejection process of the server 1 will be described with reference to FIG.
First, the approval route determination processing unit 27 extracts a user ID (here, “Takada”) in a record (see FIG. 3) in the application table recorded in the application data recording unit 21 (step S201).
[0028]
Next, the approval route determination processing unit 27 uses the user ID (here, “Takada”) extracted in step S201 from the organization table (see FIG. 6) recorded in the organization table recording unit 24. The stored record is searched, and the organization sequence number (here, “000100010001000200020002000100020002”) in the record is extracted (step S202). At this time, if there are a plurality of records storing the user ID extracted in step S201, a record effective on the system date is selected.
Then, the approval route determination processing unit 27 calculates a value (here, “00010001000100020002000200010002”) obtained by deleting the lower 4 digits of the organization order number extracted in step S202 (here, “000100010001000200020002000200020002”) (step S203). ).
[0029]
Next, the approval route determination processing unit 27 stores the value calculated in step S203 (here, “00010001000100020002000200010002”) from the organization table (see FIG. 6) recorded in the organization table recording unit 24. The record (here, the twelfth record) stored as the order number is searched, and the user ID (here, “Eigyo_B_1K_1G”) in the record is extracted (step S204). At this time, if there are a plurality of records storing the values calculated in step S203 as organization order numbers, records that are valid on the system date are selected.
The approval route determination processing unit 27 then extracts the user ID (here, “Eigyo_B_1K_1G”) extracted in step S204 from the approver table (see FIG. 5) recorded in the approver table recording unit 23. Is retrieved as a user ID of a node corresponding to a person who has the authorization authority (here, the fifth record), and the employee's user ID as the person having the authorization authority stored in the record (Here, “Mori”) is extracted (step S205). At this time, if there are a plurality of records storing the user ID extracted in step S204, a record effective on the system date is selected. Thereby, it is possible to determine an employee (in this case, an employee with the user ID “Mori” and the name “Yuji Mori”) who should first perform approval or rejection processing on the application data (see FIG. 3). The approval route determination processing unit 27 outputs this user ID to the approval / rejection processing unit 28.
[0030]
Next, the approval / rejection processing unit 28 uses a client terminal (here, “Yuji Mori”) having the user ID (here, “Mori”) extracted in step S205. The contents of the application data are displayed on the client terminal 12 (step S206).
Then, the approval / rejection processing unit 28 responds to an instruction from the employee (here, “Yuji Mori”) having the user ID extracted in step S205 (here, the employee “Yuji Mori”) An instruction to approve is input), and the value of one approval column (here, the first approval column) among the plurality of approval columns in the application data is rewritten (step S207). FIG. 10 is a diagram showing application data after rewriting.
[0031]
Next, the approval route determination processing unit 27 checks whether or not all approvals are completed. If it is determined that all approvals are completed, the process is terminated. If not, The process returns to step S203 (step S208).
[0032]
FIG. 11 is a flowchart showing an outline of the approval route creation / update process of the server 1. Hereinafter, the approval route creation / update process of the server 1 will be described with reference to FIG.
The approval route creation / update processing unit 29 adds, deletes, or changes an employee as an authorized person from an employee who is using a client terminal (here, the client terminal 13). For this purpose, the approver table recorded in the approver table recording unit 23 or the organization table recorded in the organization table recording unit 24 is created or updated (step S301).
[0033]
As described above, in the present embodiment, the information on the organization, the information on the person having the approval authority, and the information on the application are separated and stored in the organization table, the approver table, and the application table, respectively. The information in each table can be easily updated, and it is possible to respond flexibly even when personnel changes or the like occur.
[0034]
【The invention's effect】
As described above, according to the present invention, it is possible to respond flexibly even when personnel changes or the like occur.
[Brief description of the drawings]
FIG. 1 is a diagram showing a configuration of a system using a business management apparatus according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating a configuration of the server 1 in FIG. 1;
FIG. 3 is a diagram illustrating an example of an application table recorded in an application table recording unit 21 in FIG. 2;
4 is a diagram illustrating an example of an employee table recorded in the employee table recording unit 22 of FIG. 2;
5 is a diagram showing an example of an approver table recorded in the approver table recording unit 23 of FIG. 2; FIG.
6 is a diagram showing an example of a organization table recorded in the organization table recording unit 24 of FIG.
7 is a diagram illustrating an example of a post table recorded in the post table recording unit 25 in FIG. 2; FIG.
8 is a flowchart showing application data creation processing of the server 1 of FIG.
FIG. 9 is a flowchart showing approval / rejection processing of the server 1 of FIG. 1;
10 is a diagram illustrating an example of an application table recorded in an application table recording unit 21 in FIG. 2;
11 is a flowchart showing approval route creation / update processing of the server 1 in FIG. 1;
[Explanation of symbols]
1 server
10 system
11 to 1n client terminal
21 Application Table Recording Department
22 Employee table recording department
23 Approver table recording section
24 organization table recording section
25 Title table recording department
26 Application data creation processing department
27 Approval route decision processing section
28 Approval / Rejection Processing Department
29 Approval Route Creation / Update Processing Department

Claims (12)

A device for managing work related to application and approval in an organization,
A first table including a plurality of records each storing information related to a first group of nodes corresponding to a plurality of members constituting an organization and a plurality of persons having approval authority, each record being the plurality of the plurality of records A first field that stores a first identifier that uniquely identifies the constituent or the first group of nodes, and a second identifier that represents an order in the organization of the plurality of constituents or the first group of nodes. Any one of the plurality of constituents by performing an operation of deleting a value of a predetermined length from the end of the second identifier of any one of the plurality of constituents at least once . upper and and and capable Rukoto obtain the second identifier of the at least one node in said first group of nodes corresponding to at least one person having approval authority to apply the on the organization's First First recording means for recording said first table and a second field for storing an identifier,
A first field for storing the first identifier for uniquely identifying the first group of nodes, and the plurality of members as persons having an authorization authority for the first group of nodes are uniquely identified. Second recording means for recording a second table having a second field for storing the first identifier;
A third table relating to an application, wherein a first field for storing the first identifier for uniquely identifying a person who made an application among the plurality of constituent members, and whether approval for the application has been obtained A third recording means for recording the third table having a second group of fields each storing a plurality of data indicating whether or not;
The first table is searched based on the first identifier in the processing target record of the third table, and an application related to the processing target record among the plurality of constituents is made. extracts the second identifier of person, said at least one value obtained by the extracted end of the second identifier performs an operation to remove at least one value of said predetermined length the By searching at least one record stored as an identifier of 2 from the first table , the first group corresponding to at least one person who has approval authority for the application related to the record to be processed wherein based on at least one of said first identifier at least one extracting the first identifier, the extracted identifying at least one node in the node By searching the second table, the first processing means for identifying at least one of a person having approval authority for application according to the processing target record in said multiple configurator,
The application has been approved or rejected in response to an approval or rejection instruction from at least one person who has the authority to approve the application related to the processing target record specified by the first processing means. Second processing means for writing at least one data representing the second group field in the record to be processed;
A business management device comprising:   The business management apparatus according to claim 1, wherein the first table further includes a plurality of records each storing information on a second group of nodes corresponding to a plurality of departments in the organization.   The business management apparatus according to claim 1 or 2, wherein the first table further includes a field for storing data representing a date when the information in the record is valid or a date when the information is valid.   The third table according to any one of claims 1 to 3, further comprising a field for storing data representing a date on which information relating to an application is input, a date on which a case relating to an application is performed, or a date on which the application is performed. The business management device described. A method for managing work related to application and approval in an organization,
A first table including a plurality of records each storing information related to a first group of nodes corresponding to a plurality of members constituting an organization and a plurality of persons having approval authority, each record being the plurality of the plurality of records A first field that stores a first identifier that uniquely identifies the constituent or the first group of nodes, and a second identifier that represents an order in the organization of the plurality of constituents or the first group of nodes. Any one of the plurality of constituents by performing an operation of deleting a value of a predetermined length from the end of the second identifier of any one of the plurality of constituents at least once . upper and and and capable Rukoto obtain the second identifier of the at least one node in said first group of nodes corresponding to at least one person having approval authority to apply the on the organization's First And step (a) for recording the first table and a second field for storing the identifier,
A first field for storing the first identifier for uniquely identifying the first group of nodes, and the plurality of members as persons having an authorization authority for the first group of nodes are uniquely identified. Recording a second table having a second field storing said first identifier (b);
A third table relating to an application, wherein a first field for storing the first identifier for uniquely identifying a person who made an application among the plurality of constituent members, and whether approval for the application has been obtained Recording the third table having a second group of fields each storing a plurality of data indicating whether or not;
The first table is searched based on the first identifier in the processing target record of the third table, and an application related to the processing target record among the plurality of constituents is made. Extracting said second identifier of the person ;
Step storing at least one value obtained by the end of the second identifier extracted in (d) performing an operation to remove at least one value of the predetermined length as the second identifier At least one record in the first group of nodes corresponding to at least one person who has an authorization to approve the application related to the record to be processed by searching the at least one record from the first table. Extracting at least one said first identifier identifying one node (e);
Approval authority for an application related to the record to be processed among the plurality of constituents by searching the second table based on at least one of the first identifiers extracted in step (e) Identifying at least one person having
That the application has been approved or rejected in accordance with an approval or rejection instruction from at least one person who has the authorization to approve the application related to the processing target record identified in step (f). Writing (g) at least one data representing into the second group of fields in the record to be processed ;
A business management method comprising: The business management method according to claim 5 , wherein the first table further includes a plurality of records each storing information on a second group of nodes corresponding to a plurality of departments in the organization. The business management method according to claim 5 or 6 , wherein the first table further has a field for storing data representing a date when the information in the record becomes valid or a date when the information becomes valid. The third table, further comprising a field storing data representing a date on which cases according to the entered date or application information regarding application is performed a day or performed, in any one of claims 5-7 The business management method described. A program for managing the business related to application and approval in the organization,
A first table including a plurality of records each storing information related to a first group of nodes corresponding to a plurality of members constituting an organization and a plurality of persons having approval authority, each record being the plurality of the plurality of records A first field that stores a first identifier that uniquely identifies the constituent or the first group of nodes, and a second identifier that represents an order in the organization of the plurality of constituents or the first group of nodes. Any one of the plurality of constituents by performing an operation of deleting a value of a predetermined length from the end of the second identifier of any one of the plurality of constituents at least once . upper and and and capable Rukoto obtain the second identifier of the at least one node in said first group of nodes corresponding to at least one person having approval authority to apply the on the organization's First The procedure for recording the first table and a second field for storing an identifier (a),
A first field for storing the first identifier for uniquely identifying the first group of nodes, and the plurality of members as persons having an authorization authority for the first group of nodes are uniquely identified. A step (b) of recording a second table having a second field for storing the first identifier;
A third table relating to an application, wherein a first field for storing the first identifier for uniquely identifying a person who made an application among the plurality of constituent members, and whether approval for the application has been obtained A step (c) of recording the third table having a second group of fields each storing a plurality of data indicating whether or not;
The first table is searched based on the first identifier in the processing target record of the third table, and an application related to the processing target record among the plurality of constituents is made. (D) extracting the second identifier of the person ;
Storing the procedure at least one value obtained by performing the operation from the end of the second identifier extracted at least remove once the value of the predetermined length in (d) as the second identifier At least one record in the first group of nodes corresponding to at least one person who has an authorization to approve the application related to the record to be processed by searching the at least one record from the first table. A step (e) of extracting at least one said first identifier specifying one node ;
Approval authority for an application related to the processing target record among the plurality of constituents by searching the second table based on at least one of the first identifiers extracted in step (e) (F) identifying at least one person having
The application has been approved or rejected in accordance with an approval or rejection instruction from at least one person who has the authorization to approve the application related to the record to be processed identified in step (f). A step (g) of writing at least one data to be represented into the second group of fields in the record to be processed ;
Management program for causing CPU to execute. The business management program according to claim 9 , wherein the first table further includes a plurality of records each storing information on a second group of nodes corresponding to a plurality of departments in the organization. The business management program according to claim 9 or 10 , wherein the first table further includes a field for storing data representing a date when the information in the record becomes valid or a date when the information becomes valid. The said 3rd table further has the field which stores the data which represent the date which input the information regarding an application, the day when the case concerning an application was performed, or the date when it is performed, In any one of Claims 9-11 The business management program described.

Images