JP2003216803A - Display method for electronic approval item, and program therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To clearly discriminate and present current items (e.g. items of this year) and past items (e.g. items of the last year) when item data on objects of approval are presented to an approver of electronic slips. <P>SOLUTION: The year for an approval object and the personal ID of the approver are inputted to obtain the attribute and position of the approver by reference to a personal attribute table and retrieval from an item approval duty table is carried out (step 31); and item data are extracted (step 33) by retrieval from an item data table based upon an item ID as a retrieval result and extracted item data are listed and displayed (step 34). Further, it is judged whether there are past items of the year right before the inputted year (step 32). <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an electronic approval system for approving electronic vouchers, and more particularly to a technology for extracting and displaying approved cases at fixed management periods such as year, year, first half and second half.

[0002]

2. Description of the Related Art When voucher approval is managed in units of a fixed period such as a year, a voucher approval that occurs at the end of the fiscal year may be processed across the boundaries of the year.
In the case where a voucher process is performed by a workflow by the electronic decision system, there is a case where the case data cannot be sent to an appropriate decision maker when the decision maker is transferred or promoted due to the processing over a period. As a method for solving this problem, Japanese Patent Application Laid-Open No.
As described in Japanese Patent Application Laid-Open No. 001-195468, a method has been proposed in which a decision-making item is managed by date information, and a decision-maker is identified based on personnel information and organization information corresponding to a slip issue date when defining the decision-making item. There is.

[0003]

In the above-mentioned prior art, attention is paid to the date of the decision-making case, and all the present cases (for example, the current term) and the past cases (for example, the previous term) are extracted and the resulting cases are set. Since it is sent to the approver of the management period to which the vote date belongs, there was a problem that the approver could not clearly judge whether it is the present case or the past case. In addition, if the recognition of the case is insufficient, there is a possibility that the past authority, which should not be approved by the current authority, may be mistakenly approved.

An object of the present invention is to clearly present the present case and the past case and present them to the approver.

[0005]

The present invention is a system for displaying the case data subject to the electronic approval of the logged-in authorizer, and accepts the input of the index indicating the management period and the individual identifier of the login user. , The affiliation and post of the login user is acquired based on the index and the personal identifier that are input by referring to the first table, and the index input based on the second table and the acquired affiliation and post are handled. It is characterized by the method of acquiring the item data and displaying the acquired item data in a list.

[0006]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram of the electronic settlement system of this embodiment. The system includes an electronic approval server 10 and terminal devices 51 and 52 connected to the electronic approval server 10 via a network 90. Electronic approval server 10
Stores the case data table 20, the case decision job table 30, and the personal attribute table 40 on the storage device. The case data table 20 is a table that stores each case data. The personal attribute table 40 stores the affiliation and post corresponding to each year of each individual. The item approval position table 30 stores the type, year, affiliation, and position for each item data.

The drafter 60 is the drafter of the electronic slip, and the terminal device 51 is the terminal used. The authorizer 71 and the like are authorizers, and the terminal device 52 is the terminal used. The terminal devices 51 and 52 are not only computers but also function as client terminals for the electronic approval server 10, and mainly transmit the input data to the electronic approval server 10 and display the data received from the electronic approval server 10. Execute a program that has a user interface function.

The electronic approval server 10 is a computer and executes the application program installed therein to register the case data input from the terminal device 51 in the case data table 20, and to execute the case approval entered for the case. Job data for the job approval table 30
Register with. Further, the electronic approval server 10 searches the case approval job table 30 when the approver 71 logs in, sends a list of the cases in the case data table 20 that should be approved by the approver 71 to the terminal device 52, and Device 52 displays this. Also, the case decision job table 30 is searched to check whether the decision-maker 71 has a past case to be decided, and the result is notified to the terminal device 52.

FIG. 2 is a diagram showing the data structure of the case data table 20. The case record of the case data table 20 has data items of case ID, type, case name, and case content. The case ID (identifier) is a unique identifier that distinguishes each case. The type is a flag for distinguishing the type of item and has a value of 0 or 1. Type 0 indicates a case that can be approved by the approver after moving the case of the previous year when there is a personnel change due to the year change. Type 1 indicates a case in which the person who decided in the previous year should approve the case in the previous year when there is a personnel change due to the change in the year.

FIG. 3 is a view showing the data structure of the case decision job table 30. The case decision record of the case decision table 30 has data items of case ID, type, year, affiliation and post. The case ID and type are the same as the case ID and type in the case data table 20. The year, affiliation, and post indicate the personal attributes that should or should be approved for the case. Since the case records of the case data table 20 and the case decision job table 30 have a common case ID, they may be merged into one case record. In the present embodiment, for the convenience of erasing the case-approved case decision job record, it is separated from the corresponding case record in the case data table 20.

FIG. 4 is a diagram showing a data structure of the personal attribute table 40. Each individual attribute record of the individual attribute table 40 includes an individual ID (identifier), year, affiliation, post,
It has data items such as name. The personal attribute record is set for each year. In this example, Mr. A, who was the head of the accounting department in 2000, was transferred to the director of the general affairs department in 2001. In addition, Mr. B, who was the head of the accounting section in 2000, has the same position in 2001 and has not moved.

FIG. 5 is a flow chart showing the processing procedure of the case drafting and settlement processing. The year 60 to be processed is selected and input through the login screen displayed by the drafter 60 or the authorizer 71 of the terminal device 51, 52 (step 1
1) When the personal ID and password are input (step 12), the personal ID and password are sent to the electronic approval server 1
Sent to 0. If you do not select a year, it is regarded as the year to which the processing date belongs. The electronic approval server 10 refers to a security management database (not shown) to check the login data (step 13). If the login data is valid (step 13OK), the personal attribute table 40 is searched based on the personal ID, and the affiliation and post of the designated year of the login user is acquired (step 1
4), the terminal devices 51 and 52 display the slip processing menu. When the case draft process is selected (step 15, draft), the terminal device 51 and the electronic approval server 10 execute the case draft process (step 16). When the approval process is selected (step 15, approval), the terminal device 52 and the electronic approval server 10 execute the electronic approval process (step 1).
7).

FIG. 6 is a flow chart showing the processing procedure of the case draft processing in step 16. The terminal device 51 is
A guide screen for inputting case data is displayed on the display device. Issuer 60, slip type,
When the case name and case content are input, the terminal device 51 transmits the input data to the electronic approval server 10. The electronic approval server 10 registers the received data in the case data table 20. At this time, the “type” of the item is determined by the slip type.

Next, the electronic approval server 10 extracts personal information of the approver candidate for the selected fiscal year corresponding to the slip type from the personal attribute table 40 and transmits it to the terminal device 51, and the terminal device 51 receives this approver. A candidate list is displayed (step 21). Each piece of personal information includes an individual ID, affiliation, post, name, and the like. When the individual ID to be the authorizer is selected by the drafter 60 (step 22), the individual ID is sent to the electronic authorization server 10. The electronic approval server 10 searches the individual attribute table 40 and acquires the year, affiliation, and post of the corresponding individual (step 23). Next, the electronic approval server 10 stores the acquired year, affiliation, and post in the case approval job table 30 together with the case ID and type of the case (step 24), and ends the process.

FIG. 7 is a flow chart showing the processing procedure of the approval processing shown in step 17. When the approval process is selected, the electronic approval server 10 searches the case approval job table 30 according to the previously acquired year, affiliation, and position.
If there is a corresponding case, all the case IDs are acquired (step 31). Next, a process for checking whether there is a past case is performed (step 32). Since the approval processing of the past matter will be performed at the next login, the logoff is performed here when the approval processing of the past matter is performed. If you do not log off to process the past case, the electronic approval server 10
The case data table 20 is searched, all case data corresponding to the case ID extracted in step 31 are extracted, and transmitted to the terminal device 52 (step 33). Terminal device 52
Displays a list of the extracted matter data (step 3
4).

FIG. 9 shows a display example of such a case data list. When it is determined in the process of step 32 that a past matter exists, the past matter existence is displayed as shown in the figure,
Warn the approver.

When the previous year is designated as the year at the time of login, the case decision job table 30 is searched according to the affiliation and post of the login person in the previous year, and all applicable case data are displayed regardless of the type. Among them, it is preferable to display the item data of type 1 by highlighting it or displaying it in another display section so that the logged-in user can pay attention. This highlighting or the like may be highlighted only in the previous year or may be highlighted regardless of the year.

The terminal device 52 transmits the case ID of the case for which a decision has been given by the decision-maker 71 to the electronic decision server 10. The electronic approval server 10 deletes the case approval job data instructed to be approved from the case approval job table 30 and erases the data (step 35). This is to remove the approved case from the case data list at the next login. Therefore, other deletion means may be used instead of deleting, such as setting a flag for the approved case.

FIG. 8 is a flow chart showing the processing procedure of the past case check processing in step 32. The electronic approval server 10 searches the personal attribute table 40 based on the individual ID of the logged-in person and the designated year −1, and acquires the affiliation and post of the previous year (step 41). Next, the electronic approval server 10 searches the matter approval job table 30 based on the year, affiliation, and job title acquired as the first embodiment,
The case decision job data of type 1 is acquired (step 42). If there is a past case (step 43YE
S), and notifies the terminal device 52 to that effect, and the terminal device 52 displays a message indicating that there is a past case (step 4).
4). An object indicating the existence of a past matter may be displayed instead of the message. FIG. 10 shows an example of this message display.

When the logoff is instructed for the processing of the past matter (YES at step 45), the approval processing is finished,
Move on to the logoff procedure. When it is instructed to continue the process without logging off (NO in step 45), the terminal device 52 notifies the electronic decision server 10 to that effect, and the past case check process is ended. If no past matter exists (step 43)
Similarly, in the case of (NO), the past matter check processing ends.

The type 0 case of the previous year may be approved by the authorizer of the previous year or by the authorizer of the present year. For example, when the year changes, the authorizer of the previous year may log in with the affiliation and post of the previous year to obtain the item data. In addition, when the year changes, electronic approval server 1
0 may search the case decision job table 30 to find a case of type 0, and mechanically change the year of the case from the previous year to the current year. Alternatively, the slip issuer may change the year of some of the case decision job data to a new year depending on the circumstances of the approver, and leave the year of other case decision job data unchanged.

The electronic settlement process of this embodiment will be described below with reference to a specific example. FIG. 11 is a diagram showing an example of personnel changes. In this example, the authorizer 71 who was the manager of the accounting section in 2000 became the manager of the general affairs department in 2001. It also shows that the authorizer 81 who was the general manager of the general affairs department in 2000 became the manager of the accounting department in 2001.

When the type of item is 0 and the fiscal year 2000 has changed, the fiscal year change data is 2
If it is changed to 001 job approval data,
This matter is extracted at the time of login as the matter data to be decided by the decision-maker 71 after the change rather than the decision-maker 71 before the change due to the year change. Also, the case type is 1,
In 2000, the accounts of the accounting section and the section manager are extracted at the time of login as a past case to be decided by the deciding person 71 before the change instead of the deciding person 81 after the change when the year changes.

Next, the case where there is no personnel change will be described.
In this case, the authorizer 71 who was the accounting section and section chief in 2000 is registered with the individual attributes of accounting section and section manager in 2001 as well. Therefore, the case type is 0,
When the fiscal year changes, the matter of the accounting section and section manager's matter decision-making job data is changed to the fiscal year 2001 in the accounting section and section manager's matter decision-making job data. . The case type is 1 and 2
In the fiscal year 2000, the accounting section and the section manager's case, the authorizer 7 of the previous year
1, that is, the same person as the authorizer 71 is extracted as a past matter to be approved.

In the first embodiment, in step 42, the item decision job data of the previous year whose item type is 1 is searched based on the affiliation and post of the logged-in person in the previous year. In the second embodiment, instead of this, in step 42, the matter types 0, 1
Search both the previous year's case approval job data and extract the corresponding case data. In the second embodiment as well, if the previous year is specified as the year at the time of login, in step 34, the case decision table 3 is selected according to the login user's previous year's affiliation and post.
The point that 0 is searched and all the relevant item data are displayed as a list regardless of the type is the same as in step 34, and remains the same. Regarding the approval of the case of the case type 0, it may be decided by the operation as described above.

In the first embodiment, especially when there is a type 1 past case, the authorizer of the previous year is warned. But type 0
The above operation is necessary because the warning is not issued only for the past cases. In the second example, the authorizer of the previous year is warned when there is a past case regardless of the case type. Instead, the warning for the type 1 past matter may be weakened, so it is desirable to display a warning for the type 1 matter data when displaying the past matter data list at the time of login.

The period for approval has been described above in terms of the fiscal year.
The present invention can be applied according to the same idea even if the approval period changes such as year, period (first half, second half) or month instead of the year, as long as it is a constant management period. In this case, 2001
The second half of 2001 and December 2001 are indicators showing the management period.

[0029]

As described above, according to the present invention, since only the approval case for the management period designated by the approver is extracted and displayed, the case of the present period and the case of the previous period are clearly distinguished. The decision-maker does not confuse the two. Further, even if the personal attribute table is modified due to personnel changes, the matter can be sent to the correct authorizer without being affected by it. Furthermore, by limiting the management period and highlighting a specific case, the past case data that the logged-in authorizer should approve can be clearly distinguished, and the mistake that the past authority is approved by the present authority can be avoided. It can be prevented.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an electronic approval system according to an embodiment.

FIG. 2 is a diagram showing a data structure of a case data table 20 according to the embodiment.

FIG. 3 is a diagram showing a data structure of a case approval job table 30 of the embodiment.

FIG. 4 is a diagram showing a data structure of a personal attribute table 40 of the embodiment.

FIG. 5 is a flowchart showing a processing procedure of a case drafting process and a settlement process according to the embodiment.

FIG. 6 is a flowchart showing a processing procedure of case draft processing according to the embodiment.

FIG. 7 is a flowchart illustrating a processing procedure of a settlement process according to the embodiment.

FIG. 8 is a flowchart showing a processing procedure of past matter check processing according to the embodiment.

FIG. 9 is a diagram showing a display example of a case data list.

FIG. 10 is a diagram showing a display example of a message indicating the existence of a past matter.

FIG. 11 is a diagram showing an example of personnel changes.

[Explanation of symbols]

10: electronic approval server, 20: case data table,
30: case decision table, 40: personal attribute table,
51, 52: Terminal devices.

Claims (5)

[Claims] 1. A method of displaying, for a logged-in authorizer, item data to be subject to the electronic authorisation, by inputting an index indicating a management period and a personal identifier of the login person, and referring to the first table. The affiliation and post of the login user is acquired based on the index and the personal identifier that are input as described above, and the index input based on the second table and the case data corresponding to the acquired affiliation and post And displaying the acquired case data in a list. 2. The item data displayed in a list is divided into item data to be approved by the login user and item data that can be approved by another authorizer, and in particular, the item data to be approved by the login user. The method for displaying an electronically approved matter according to claim 1, wherein the method is a method of highlighting. 3. The case data displayed in a list is divided into case data to be approved by the login user and case data that can be approved by another approver, and is managed by referring to the first table. The affiliation and post of the login user is acquired based on the index indicating the management period immediately preceding the index indicating the period and the personal identifier, and the management period immediately before is acquired based on the second table. 2. The indicator according to claim 1, wherein it is judged whether or not there is matter data corresponding to the index, the acquired affiliation and the post, and if there is, the presence is indicated to the login person by a display. How to display electronic decision items. 4. A program for displaying, for a decision-maker who has logged in to a computer, item data to be subject to electronic decision-making, a function for accepting an index indicating a management period and an input of the login-person's personal identifier, a first table. Function for acquiring the affiliation and post of the login user based on the index and the personal identifier input with reference to the index, the index input based on the second table, the obtained affiliation and post Program for realizing the function to acquire the matter data corresponding to the above for displaying the list. 5. The item data displayed in a list is divided into item data to be approved by the login user and item data that can be approved by another authorizer, and is managed by referring to the first table. A function for acquiring the affiliation and post of the login user based on the index indicating the management period immediately preceding the index indicating the period and the personal identifier, and the management period immediately before based on the second table. A feature that is characterized in that the index indicating, a function of determining whether or not the matter data corresponding to the acquired affiliation and the post exists, and if there is, notify the login user that the matter exists for display. The program according to claim 4, wherein