JP3276735B2 - Input assist method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to office work such as slip processing in a computer. In particular, the present invention relates to an input assisting method in a slip data input process. The present invention also relates to a money amount management method in which budget diversion processing between subjects is correctly performed. The present invention also relates to a simple and high-speed decision making method.

[0002]

[Prior art]

Conventional example 1. 2. Description of the Related Art Conventionally, when operations such as registration, correction, inquiry, and deletion are performed on data on a file stored in a storage unit of a computer, a code list is displayed on a screen for coded items. FIG. 48 is an example of a screen showing an input assisting method in the conventional code input in Japanese Patent Application Laid-Open No. Hei 4-241819. The input screen includes a code input area and a code list table display area. In the figure, reference numeral 901 denotes a main screen including the names of three items (subsection, item, and item) and an input area in which three codes corresponding to the names can be input; 912, a code for displaying a list of codes that can be currently input; It is a list. When the code of the clause is input, a code list of the clause is displayed on a part of the screen. The user looks at the code list, and inputs 01 from the keyboard when selecting civil engineering expenses. In the following, for items and items, look at the code list in the same way as the clause and enter the code from the keyboard.

[0003] Next, the operation of the conventional input assist system in code input will be described with reference to the flowchart of the conventional code input system shown in FIG. First, 95
In step 4, a code master that holds the code and its description is opened. Next, at 955, the code master is read. next,
At 970, the screen display position of the code list is calculated, and at 957 the code list is displayed at the calculated position. Finally, at 956, the code master is closed.

[0004] The operations of the input assisting method shown in 954 to 956 are executed every time corresponding to each item. For example, when the cursor is located at the section, a code list for the section is always displayed, and the user must input the code of the section while viewing the code list. When the code input of the clause is completed, the code list for the item is always displayed, and the user inputs the item. The user must enter the code of the item by looking at the code list.

A menu display method is an example of a conventional input assist method. In a word processor or a spreadsheet program, when performing a desired operation, a menu display method for specifying a desired operation by displaying a pull-down menu or a pop-up menu and selecting the displayed items hierarchically. Used. Such a menu display method is for specifying an operation prepared in advance by a word processor or a spreadsheet program, and the menu to be displayed and each hierarchical item are fixed,
The display contents are always constant. In addition, when accessing the hierarchical menu display, it is always performed in a top-down order, so that a desired operation cannot be obtained unless the hierarchical branch is always traced from the root.

Conventional example 2. Conventionally, in the process of diverting the budget between subjects when the budget is insufficient, whether the amount of the remaining budget of the diverted source and the diverted destination is updated at the same time when the diversion slip is generated (hereinafter referred to as a method for updating at the time of generation), The budget balances of the diversion source and the diversion destination were simultaneously updated at the time of approving the diversion slip (when the diversion amount was determined) (hereinafter referred to as the update method at the time of approval).

FIG. 50 is a diagram showing a conventional budget management system in the case of the update system at the time of approval. In the figure, 1 is a slip issuing function, 2 is a slip approval function, 411, 412, 413, 4
21, 422, 423 are the remaining budgets of the amount data holding the various amounts at the present time for each subject. 411,412,
Reference numeral 413 denotes the remaining budget of the former subject,
Reference numeral 2,423 denotes the remaining budget of the diverted subject. 411,4
Reference numeral 21 denotes the remaining budget before the slip invoicing function 1 is activated.
Reference numerals 412 and 422 denote budget balances after the slip invoicing function 1 is activated and before the slip invoicing function 2 is activated. 413,4
Reference numeral 23 denotes the remaining budget after the slip approval function 2 is activated.

Next, the operation will be described. here,
50,000 yen from the diversion-existing subject with a budget balance of 2 million yen
A case of diversion to a diversion-destination subject having a budget balance of 100,000 yen will be described. The decision update method updates the remaining budget on the computer when making a decision on a diversion slip. The slip issuing function 1 may be processed manually or may be operated from a terminal. In both cases, the slip drafting function 1
Does not update the amounts of the remaining budgets 411 and 421. Slip settlement function 2 reduces the original budget from 412 to 2 million yen to 41
3 to 1,950,000 yen, and divert the budget to 422 to 100
It will increase from 10,000 yen to 423 million yen.

Next, FIG. 51 shows a conventional budget management method based on a draft update method. In the figure, 1 is a slip issuing function, 2
Is the slip approval function, 411, 412, 413, 421, 4
Reference numerals 22 and 423 denote budget remaining amounts of amount data holding various amounts at the present time for each subject. Reference numerals 411, 412, and 413 denote budget balances of the divert-existing subjects.
Is the budget balance of the diversion-destination subject. Reference numerals 411 and 421 denote budget remaining amounts before the chit invoicing function 1 is activated. 412,4
22 is a slip approval process 2 after the slip invoicing function 1 is activated.
Represents the remaining budget before the is activated. Reference numerals 413 and 423 denote the remaining budget after the slip approval process 2 is activated.

Next, the operation will be described. The draft update method updates the remaining budget on a computer when a divert slip is drafted. Slip original function to reduce the original budget to 411-2
The budget will be reduced from 1,000,000 yen to 195,000 yen from 412,000 yen, and the diverted budget will be increased from 1,000,000 yen from 421 to 1,050,000 yen from 422. The slip approval function 2 does not update the remaining budget amounts 412 and 422.

Conventional example 3. 2. Description of the Related Art Conventionally, it has been considered to improve the method of processing a voucher that becomes effective only after the approval of the voucher. FIG. 52 is a principle configuration diagram showing a conventional decision processing system disclosed in, for example, Japanese Patent Application Laid-Open No. 2-281369. In the figure, reference numeral 1 denotes a slip issuing function for creating slip data using the user-related data 8 and organizational structure data 20 based on the user code of the drafter, and 11 denotes a slip type, which is based on the input slip type. A decision right determining means for determining a decider based on the decision scenario data 6 and forming a template of the form data specifying the decider, and 19 is a form transmitting means for finding and transmitting a partner to which the form should be transmitted from the user-related data 8. is there.

[0012] As shown in FIG. 53, the decision scenario data 6 defines the positions requiring decision processing and the decision order in each decision document format, that is, for each slip type. For example, it is stipulated that, for the slip type D1, a decision is required in the order of a section manager, a section manager, and a factory manager as positions requiring approval processing. Similarly, for the slip type D2,
It stipulates that approval processing is required in the order of section manager and department manager.

Next, FIG. 54 shows an example of the organization structure data 20. FIG. 54 shows the hierarchical structure of the organization, such as the manager of the department A, the manager of the department B, and the manager of the department C under the manager of the factory, the manager of the section X and the manager of the section Y under the manager A. One node, such as a factory manager, a department manager, a section manager, or the like, constitutes one record, and a pointer between records indicates a hierarchical relationship, forming a hierarchical structure (tree structure). As described above, the organizational structure data 20 is data representing the hierarchical structure of the organization, such as the inclusive relation between departments and sections, the command, and the upper and lower relation of command supervision rights.

Next, the conventional decision making method shown in FIG. 53 will be described. When creating a slip requiring approval, the user first inputs the type of the slip. For example, when D2 is input as the type of the slip, the right to determine
Reference numeral 1 refers to the decision scenario data, retrieves the decision scenario data corresponding to the slip type D2, and creates a template 21 of the slip data. Next, the slip data creation means 22 determines the organization to which the user belongs based on the workplace code, post, etc. of the user stored in the user-related data 8, and converts the organization configuration data 20 from the organization to which the user belongs. By performing the search, the template 21 of the slip data is converted into the actual slip data 3. In this example, it is determined from the user-related data 8 that the drafter belongs to section X, the section manager section of the template 21 of the slip data is converted into the section X section manager, and the section manager of the template 21 of the slip data is converted. Is converted to A section length. The slip data 3 created in this manner is transmitted to the slip transmitting means 1.
9 to the X section manager and the A section manager in order to ask for a decision.

[0015]

The input assisting method in the conventional code input is configured as described above.
There is a problem that the code list is displayed on the screen, but the user must input the code from the keyboard while watching the code list.

A code list is always displayed even if the user remembers the contents of the code. As described above, there is a problem that the display speed of the computer becomes slow when the code list is always displayed.

Further, when the code list is displayed on the main screen, an area for displaying the code list occupies the area of the main screen layout, so that information that can be displayed on the main screen is reduced.

Further, since the conventional approval processing method is configured as described above, in the update method at the time of approval, if all of the remaining budget of the diversion source is spent between the time when the slip is issued and the time when the slip is approved, the diversion is performed. There was a problem that the budget balance of the former subject became negative by the amount diverted. For example, assuming that the budget balance of the former subject is 2 million yen, and a slip is issued with a diversion amount of 50,000 yen, and a payment of 2 million yen is made in the former subject, the original budget is used at the time of approval of the slip. The balance is 0 yen,
Due to the slip approval, the remaining budget of the divert source will be minus 50,000 yen. Since a negative budget is not allowed, it takes more time to adjust the budget.

Further, in the update method at the time of invoicing, when all the budget remaining of the diverted subject is spent between the invoicing of the slip and the settlement of the voucher, when the approval is not approved, the remaining budget of the diverted subject is reduced. There was a problem that the amount diverted was negative. For example, assuming that the remaining budget of the diverted subject is 1 million yen and a slip is issued with the diverted amount of 50,000 yen, the remaining budget of the diverted subject is 1.05 million yen. At this time, 1
If the payment of 050,000 yen is made, the remaining budget of the diverted subject will be 0 yen. When the diverted slip is returned and the diverted slip is deleted, the amount of the slip is returned to the remaining budget, and the budget amount of the diverted subject is minus 50,000 yen.

The same problem occurs not only in diversion but also in subject correction processing, transfer processing, and yearly carryover.

Further, since the conventional approval processing method is configured as described above, in order to create the slip data, it is necessary to follow the data defining the organization such as the organizational structure data. However, since the number of times of data input / output to perform the operation increases, a sufficient response speed cannot be obtained.

Further, when the decision-making scenario defining the decision-maker and the order of the decision-making depends on the amount or the subject, the definition of the decision-making scenario data increases, and it takes time to create the decision-making scenario data.

The present invention has been made in order to solve the above problems, and has as its object to provide an input assisting system capable of efficiently selecting a code from a code list.

It is another object of the present invention to provide an input assisting method that can perform high-speed input processing for a user who does not need to display a code list, such as a user who is familiar with the system.

Another object of the present invention is to display the code list in a window separate from the main screen, thereby obtaining an input assisting method having a large amount of information that can be displayed on the main screen.

The present invention has been made in order to solve the above-mentioned problems, and a method for managing an amount of money in which a scheduled diversion amount of a diversion source is secured even if a decision is delayed, and the remaining budget does not become negative. The purpose is to get.

It is another object of the present invention to provide an amount management system that allows a diversion slip to be deleted without reducing the remaining budget amount even if the approval is not approved.

The present invention has been made in order to solve the above-mentioned problems, and has as its object to obtain an efficient decision-making system capable of determining a decider without tracing structural data of an organization. I have.

It is another object of the present invention to obtain a decision making method that reduces the definition amount of the decision making scenario.

[0030]

According to the first aspect of the present invention , a code and a data item content indicated by the code are paired.
A master for storing hierarchical data in a display means for displaying a data entry screen having a list instruction unit for instructing the display of the input field and the input candidate list for inputting the hierarchical code data based on the fact the instruction to display the input candidate list indicated by said list instruction unit, the data item indicating the available input code in the input field of the code and the code searching from the master
Display the list of contents in the list window and select data from the displayed list to enter the above input field
And an input means for inputting a code, the input means,
List window corresponding to each layer of hierarchical data
Has a plurality of hierarchical input means for displaying
Input means for each layer operates input means for each lower layer
In this way, the data list of hierarchical lower data
List window to make selections, and
The stratified input means operates the upper stratified input means.
To display the data list of the hierarchical data
It is displayed on a window and selected.

[0031]

Also, in the input assisting method according to the present invention, the display means may include, as the list indicating section, a plurality of hierarchical list indicating sections for instructing display of an input candidate list corresponding to the plurality of hierarchical input sections. Is displayed, and based on an instruction from a hierarchical list instructing unit for a certain hierarchy, the corresponding hierarchical input means is operated.

Further, the input assisting method according to the present invention comprises:
When the hierarchical input means is operated by a higher hierarchical input means, the hierarchical hierarchical input means includes a notifying means for notifying the upper hierarchical hierarchical input means that data selection has been completed, and a lower hierarchical input means. Is operated, when the notification by the notifying means is performed, a data input to the input field is determined, the list window is deleted, and the input operation is completed.

[0034]

[0035]

[0036]

[0037]

[0038]

[0039]

[0040]

[0041]

According to the input assisting method of the present invention, since the list is not displayed to the user who does not request the list, the screen display speed is high. Further, since the list waits for an item selection after being displayed, and the data selected from the displayed list is transferred to the main screen, there is no need to input the data from the keyboard.

[0042]

[0043]

[0044]

[0045]

【Example】

Embodiment 1 FIG. An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a configuration diagram according to the present embodiment. 1 is a slip issuing function, 2 is a slip approval function, 3 is slip data, 4 is amount data, 5 is a code master, 6 is a decision scenario data,
7 is the right of definition data, 8 is user related data, 9 is code input means, 10 is amount updating means, 11 is right determination means, 12 is form registration means, 13 is form determination means,
14 is an amount updating means, and 15 is a slip updating means.

Next, the relationship between the components 1 to 15 will be described. The slip is issued by the slip invoicing function 1 and is approved by the slip invoicing function 2. 3 to 8 are various data. The slip data 3 and the amount data 4 are data that the system registers and updates. The code master 5, decision scenario data 6, decision right definition data 7, and user-related data 8 are read-only data for this system.

In the slip generation function 1, first, a slip is created on a screen using the code input means 9. The code input means 9 inputs a previously created code master 5.
When the slip is created, the amount updating means 10 updates the amount data 4 holding the current amount of each item for each subject. Based on the information on the type, the amount, and the subject of the slip, the decision making right judging means 11 judges the decision making person from the decision making scenario data 6, the decision making right definition data 7, and the user-related data 8. Finally, slip registration means 12
Is registered in the slip data 3.

In the slip approval function 2, first, the approval slip specification means 13 is used to specify the slip to be settled by the user.
The approval slip designating means 13 uses the approval right definition data 7 and the user-related data 8 to detect an approval target slip from the slip data 3. When the user gives a decision, the price data 4 is updated using the price update means 14. Finally, the slip updating means 15 changes the slip in the slip data 3 to "completed".

FIG. 2 shows a computer system diagram of this embodiment. 16 is a server computer, 17 is a client computer such as a personal computer, and 18 is a LAN cable. The slip data 3, the price data 4 for each subject, the code master 5, the decision scenario data 6, the decision right definition data 7, and the user-related data 8 are held in the server computer 16. The person making the slip,
A slip is issued using the client computer 17. The slip approver uses the client computer 17 to approve the slip.

FIG. 3 shows an example of a screen layout of the diverted slip draft. Reference numeral 1 denotes a main screen of the slip issuing function, and 17 denotes a client computer. The main screen 1 shows the name of the drafter, the affiliation of the drafter, the diversion source and diversion destination subjects (accounting, clause (kan), section,
Eye), the remaining budget of the subject, the amount diverted, and the classification of the slip.

FIG. 4 shows an example of a subject code to be input. 4 is the code master 5. The accounting code 01 represents general accounting. When the accounting is 01, the clause 01 represents the civil engineering cost. If the accounting is 01 and the clause is 01, item 01 represents a bridge. Even if the code is the same term, its higher code, that is,
If accounting and clauses change, the meaning changes. For example, if the item is 01 but the accounting is 01 and the clause is 02, it represents a public hall. Hereinafter, such a code is referred to as a code having a hierarchical relationship.

Next, in order to explain the code input means 9, FIG. 5 shows a partial screen for inputting a diversion source subject code of the screen layout of FIG. The screen shows the account, clause,
It has four item names, item and eye, and four input areas corresponding to them. In addition, four buttons having the names of an accounting list, a clause list, an item list, and an item list are provided on the right of the input area. When a button is designated by clicking with a mouse or the like, a designated code list is displayed.

Next, the function of the code input means 9 will be described with reference to FIG. The code input unit 9 monitors whether the four buttons of the accounting list, the clause list, the item list, and the item list have been designated. If an accounting list is specified,
The accounting code input means 9a is operated. When the clause list is designated, the clause code input means 9b is operated. When the item list is designated, the item code input means 9c is operated. When the eye list is designated, the eye code input means 9d is operated. Each code input means 9
a, 9b, 9c, and 9d display corresponding code list windows, respectively, and allow the user to select a desired item. Each code input means 9a, 9b, 9c, 9d
Perform the same operation, but the accounting code input means 9a can be activated by using the code input means 9b as the code input means of the lower window. Similarly, the clause code input means 9b can activate the term code input means 9c as the code input means of the lower window.
Further, the term code input means 9c is provided with an eye code input means 9d.
Can be activated as code input means for the lower window.

Hereinafter, in order to describe the operation of the code input means 9 in more detail, screen development will be described with reference to FIGS.
This will be described with reference to FIG. In the figure, reference numeral 901 denotes a main screen for inputting codes, 911 denotes a code list window for accounting codes, 912 denotes a code list window for clause codes, 913 denotes a code list window for item codes, and 914 denotes a code list window for eye codes. is there.

When an accounting list is specified in FIG. 6, FIG.
Code list window 91 for accounting code like
1 is displayed. The code list window 911 for the accounting code includes a table showing the correspondence between the accounting code and its name, and three buttons having the names of “fix”, “cancel”, and “fix” (no matter the clause). In the figure, the hatched items represent the currently selected items. In FIG. 7, 01 general account is selected. The selected item can be changed by, for example, using arrow keys (up, down) or a mouse click. Since accounting is the highest code, the contents of the code list are always constant. When the confirm button is designated, a code is selected, and if there is a lower code, the display moves to a code list window of the lower code. If there is no lower code such as an eye code, the process is terminated and the display shifts to the main screen. When the cancel button is designated, the program returns to the upper code list window without selecting a code. Alternatively, when the code list window is displayed from the main screen, the display shifts to the main screen. When the confirm (do not select lower code) button is specified, the code selected in the code list window is selected, and the display shifts to the main screen.

When the enter button is designated in FIG. 7, a code list window 91 for the article code is displayed as shown in FIG.
2 is displayed. When codes have a hierarchical relationship as shown in FIG. 4, the contents of the list of lower codes change depending on the value of the upper code. Code list window 9 for clause codes
Reference numeral 12 denotes a list of clauses when the accounting is 01.

When the enter button is designated in FIG. 8, a code list window 91 for the item code is displayed as shown in FIG.
3 is displayed. The code list window 913 for the item code is a list of items when the accounting is 01 and the clause is 01.

When the confirm button is designated in FIG. 9, the code list window 9 for the eye code is displayed as shown in FIG.
14 is displayed. The code list window 914 for the eye code is a list of eyes when the accounting is 01, the clause is 01, and the item is 01.

When the confirm button is designated in FIG.
As shown in FIG. 11, code list windows 911, 912,
913 and 914 disappear, and only the main screen 901 for inputting a code is displayed. In the input area, the selected code accounting is set to 01, the clause is set to 01, the item is set to 01, and the item is set to 01.

Next, the operation of each of the code input means 9a to 9d will be described with reference to the flowcharts of FIGS. This flowchart shows each of the code input means 9a to 9d.
5 is a flowchart common to FIG. When a list button is specified on the main screen, or when the confirmation is specified in the code list window and there is a lower code, one of the corresponding code input means 9a to 9d operates.

In step 951, the upper code is read from the main screen or the upper code list window. Next, 952
Then, when there is a higher code such as a clause, an item, or an eye, it is determined whether or not a higher code is designated. If not specified, an error is displayed at 953 and the process ends. 95 if the upper code is set correctly
4 opens the code master. Next, at 955, a necessary code master is read. Next, at 956, the code master is closed. Then, at 957, a code list window is displayed.

When the code list window is displayed, 95
The control flow loops until the state of 8,960,961,962 is reached. At 958, it is detected that the confirm button has been designated. At 960, it is detected that the confirm (no lower code is selected) button is designated. In step 961, a notification from the lower code list window that the confirm button or the confirm (no lower code is selected) button is specified in the code list window corresponding to the lower code is detected. At 962, it is detected that the cancel button has been designated.

When the confirm button is designated in 958, 9
At 59, it is determined whether there is a lower code. If there is a lower code, the code input means of the lower code list window is started at 963. Next, the process returns to the loop at 964, and waits for the state of 961. If there is no lower code at 959, if a confirm button or a confirm (no lower code is selected) button is designated at 960, and
If a notification from the lower code list window indicating that the confirm button or the confirm (not select lower code) button is specified in the code list window corresponding to the lower code is detected in 961, the code is transferred to the main screen in 965. Forward. Next, at 966, it is determined whether or not there is an upper window. If there is an upper window, the upper window is notified at 967 that "the lower code has been determined", and the upper window detects the state of 961. Then 96
Proceed to 8. Even if there is no upper window in 966, 96
Proceed to 8. 96 when the cancel button is specified in 962
Proceed to 8. At 968, the window is deleted, and the process ends.

Next, a case will be described in which the user notices a wrong selection during the code selection. The code list window according to the present embodiment has a feature that the code list window can be traced back from a lower code list to a higher code list. In FIG. 10, if the user notices that he or she has mistakenly selected the previous item, the user selects the cancel button to display the screen shown in FIG. Therefore, when an item code to be selected, for example, 02 road is designated, the state shown in FIG. 14 is obtained.

When the confirm button is designated in FIG.
A code list window 914 for the eye code is displayed as shown in FIG. The code list window 914 for the eye code is a list of eyes when the accounting is 01, the clause is 01, and the item is 02.

Next, a case will be described in which the user has completed the code selection but later notices a wrong selection. The main screen of this embodiment is characterized in that the list displayed first may be a code for data other than the top data. In FIG. 16, when the user notices that the selection of an item has been mistaken, the screen of FIG. 17 is displayed by specifying the item list button. Therefore, the item code to be selected, for example, 01 bridge is designated.

When the enter button is designated in FIG.
A code list window 914 for the eye code is displayed as shown in FIG. The code list window 914 for the eye code is a list of eyes when the accounting is 01, the clause is 01, and the item is 01. Here, 02 Higashi Ohashi is designated.

When the confirm button is designated in FIG.
As shown in FIG. 19, the code list window 914 disappears, and only the main screen 901 for inputting a code is displayed.
In the input area, the selected code accounting is set to 01, the clause is set to 01, the item is set to 01, and the item is set to 02.

As described above, in this embodiment, the data structure is hierarchized, and each item of the hierarchy is coded. In the code input processing for performing registration correction, inquiry, deletion, and the like with this code, In particular, (a) a main screen for inputting codes, (b) a code master that holds codes and data item contents, (c) codes and data items of each layer are displayed on the main screen in a superimposed manner, and a keyboard and the like are displayed. The input processing is performed using a code list window in which the code selected by the operator by the input means is reflected on the main screen. Further, when the data represented by the code list window has lower data in the data hierarchy, when the code selection in the code list window is completed, the code list window displays a lower code list. In addition, a code list window is provided which goes back from a lower code list window to a higher code list window. Further, the code list window displayed from the main screen may be a code list window for data of the highest order first, or may be a code list window for data other than the highest order.
Further, it is characterized by having a code list window that can correspond to at least two or more layers.

The office work processing system having an input assisting method for code input according to this embodiment is characterized in that the code list is displayed as a separate screen (window) after receiving a code list display request from a user. It is.
Therefore, when the code list is not required, the code list is not displayed, and the screen display and input processing can be performed at high speed. When a code list is displayed, the code selected by the user is transferred as an input code, so that the user does not need to input the code, and the code can be input simply by selecting the code. In this embodiment, the code to be displayed on the main screen is registered in the code master. By freely rewriting the contents of the code master, the user can change the contents to be displayed in the code list. In the case of the menu display method described in the conventional example, the items to be displayed are predetermined and fixed, but in this embodiment, the items to be displayed can be freely set by rewriting the contents of the code master. The major feature is that it can be done. Further, in the conventional menu display method, it is impossible to finally specify the operation unless the menu is selected hierarchically. In this embodiment, however, there is provided a button for performing a code list for each layer. Since it is prepared, the user can display a code list indicating codes to be input from the middle of the hierarchy. Further, in this embodiment,
When the code list windows are displayed hierarchically, they are displayed on different screens (windows) in an overlapping manner, so that the influence on the display area of the main screen is minimized. Also, when designing the display layout of the main screen, it is not necessary to secure a code list area in the main screen.

Next, a description will be given below of an amount management method in which the remaining budget does not contradict. As described above, the code input means designates a diversion source subject and a diversion destination subject.
FIG. 22 is a screen transition diagram of the slip draft shown in FIG. Since the subject has been decided, the remaining budget of each subject is displayed. In the example of FIG. 20, the remaining budget at the diversion source is 2 million yen, and the remaining budget at the diversion destination is 1 million yen.

Next, the user inputs a diversion amount. In the example of FIG. 21, the diversion amount is 50,000 yen. As a result of the input, the diverted budget remaining amount of the diverted source is reduced to 1.95 million yen. In addition, at the time of determining the diversion amount, the approval classification is automatically determined from the slip type, the subject, and the diversion amount. In the example of FIG. 21, the section manager's decision is determined.

The remaining budget for each subject is stored in the amount data 4. FIG. 22 shows an example of the amount data. The remaining budget of accounting 01, clause 01, item 01, item 01, which is the diversion source, is 20
It is ¥ 100,000, accounting 01, clause 01, item 0
The remaining budget of the first item is 02,000 yen.

FIGS. 23 to 25 show screen transition diagrams of the slip approval. In FIG. 23, a slip waiting for a decision that the user has to make a decision is displayed. Here, the slip number 0000
If one slip is selected, the process proceeds to FIG.

FIG. 24 shows a main screen of the slip approval function. You can see information on the items on the slip, the amount diverted this time, and the remaining budget. In the initial state, the remaining budget after diversion of the former subject is 1.95 million yen with the remaining budget of 2 million yen deducted by 50,000 yen, but the remaining budget after diversion of the previous subject is 1 million yen. Is 100 which is not deducted for the amount diverted
It is 10,000 yen. When the user specifies the approval, the process moves to FIG.

FIG. 25 shows a screen after the approval. here,
The post-diversion budget balance at the diversion destination is 1.05 million yen, which is the sum of the budget balance of 1 million yen and the diversion amount of 50,000 yen.

FIG. 26 shows a transition diagram of the diverted amount data. In the figure, 1 is a slip creation function, 2 is a slip decision function, 411, 412, 413, 421, 422, 423
Is a budget remaining amount of amount data holding various amounts at the present time for each subject. Reference numerals 411, 412, and 413 denote budget balances of the divert-existing subject, and reference numerals 412, 422, and 423 denote budget balances of the divert-destination subject. Reference numerals 411 and 421 denote budget remaining amounts before the chit invoicing function 1 is activated. Reference numerals 412 and 422 denote budget remaining amounts after the slip invoicing function 1 is activated and before the slip approval process 2 is activated. Reference numerals 413 and 423 denote the remaining budget after the slip approval process 2 is activated.

Next, the operation will be described. here,
50,000 yen from the diversion-existing subject with a budget balance of 2 million yen
A case will be described where an attempt is made to divert to a diversion-destination subject having a budget balance of 100,000 yen. The slip invoicing function 1 reduces the diverted original budget from 411 million yen to 412 million yen. The slip approval function 2 sets the diverted destination budget to 422-1.
The amount will increase from 100,000 yen to 423,500,000 yen.

FIG. 27 shows a flowchart of the slip generation function 1. If the remaining budget at the diversion source is smaller than the diversion amount at 101, an error is displayed at 102 and the process ends. In other cases, the diversion original budget balance is reduced by the diversion amount at 10 and the diversion slip is registered at 12.

FIG. 28 shows a flowchart of the slip approval function 2. At 14, add the diversion amount to the remaining budget at the diversion destination, and
In 5, the diversion slip is settled.

As described above, according to this embodiment, in the paperwork for changing the amount of money across subjects,
(A) Slip data having information on the subject, the amount, the person making the claim, etc., described in the voucher; (b) Amount data holding the amount for each subject; and (c) Amount data of the subject whose amount is to be reduced is reduced. And (d) a slip approval function for increasing the amount data of the item on the side where the amount of money increases.

In the paperwork processing system having the money amount management system according to this embodiment, when processing a slip that crosses subjects, when the amount of money is reduced, the bill is increased at the time of voucher submission, and when the amount of money is increased, the amount of the money is increased at the time of voucher approval. Update.

Next, a decision making method in this embodiment will be described. Here, a description will be given of a case of a slip taking-out type in which a decision maker takes out a corresponding slip when operating a personal computer. FIG. 29 shows a principle configuration diagram of the slip taking out type decision processing. In the figure, 1 is a slip issuing function, 2 is a slip approval function, 3 is slip data, 6 is a decision scenario data, 7 is a decision right definition data, 8 is user related data, 1
Reference numeral 1 denotes a decision authority, and 13 denotes a decision slip designating means.

FIG. 30 shows an example of the decision scenario data 6. The approval scenario data includes a slip type, a subject, an amount (less than), an amount (more than), and an approval category. The approval classification is detected using the slip type, the subject, and the current amount (the amount diverted in the example) as keys. The ANY subject in the subject means a decision category used when omitted.

FIG. 31 shows an example of the user-related data 8.
The user-related data includes a user code, a name of the user, an organization code to which the user belongs, and a user's decision category.
Here, the organization code has a meaning given by the number of characters of the code, for example, as shown in FIG. For example, here, an organization code in which the first and second characters of the organization code are factory codes, the third and fourth characters of the organization code are department codes, and the fifth and sixth characters of the organization code are section codes. Shall be used.

FIG. 33 shows an example of the decision right definition data 7.
The decision right data includes a decision category, a decision name, and an organization character length.

Next, the relationship between the components will be described.
The decision-making right determining means 11 operates at the time of issuing a slip, determines the decision-making division of the drafted slip from the decision-making scenario data 6, and adds it to the slip. The approval slip designating means 13 operates at the time of slip approval, and uses the user-related data 8 and the approval right definition data 7 to detect and provide a slip to be settled from the slip data 3 to the settler.

Next, the operation will be described. In the example of FIG. 21, the slip type is diverted, and the diverted subject (accounting and subsection) is 010.
1. The amount is $ 50,000. FIG. 34 shows a flowchart of the decision making right judging means 11. In 1101, FIG.
The settlement scenario data 6 is read using the slip type, the subject, and the amount shown in 1 as search conditions. That is, the slip type is diverted and the subject is 010 for the decision scenario data 6 in FIG.
1. Search for an item whose amount (less than) is less than 50,000 yen and whose amount (or more) is 50,000 yen or more. At 1102, it is determined whether the search is successful. In this case, the record 60 in FIG.
1 can be detected. It can be seen that the decision code is 01. If the search is successful, the search ends. If the search fails, the process proceeds to 1103. 1103 sets the subject to ANY and detects again. In this case, since the record 602 in FIG. 30 can be detected, the determination 1104 is YES. If the decision category is determined by the slip type and amount without depending on the subject,
If there is no NY, the definition for the same decision division must be expanded by the number of subjects. With the introduction of ANY, the amount of description of the decision scenario data can be reduced.

[0109] The generated slip is stored in the slip data 3 by the slip registration means 12. An example of the slip data 3 is shown in FIG. The slip data includes a slip number, a decision section, a drafting party organization, and the like. The feature here is that a decision section is added to the slip data. Decision category is 01,0
.., Etc.

FIG. 36 shows a flowchart of the settlement slip designating means 13. The approval slip designating means 13 is activated by an approver who intends to approve the slip. The settlement slip designating means 13 detects a slip to be settled for the settler from the slip data 3 and provides it to the setter.

At 1301, the organization code A of the authorizer who activated the approval slip designating means 13 from the user-related data 8,
Obtain decision code B. As shown in FIGS. 23 to 25,
In the case where the approver is Hiroshi Yamada, the user-related information 8 in FIG.
Record 801 is detected, and the organization code A = 503
000, the decision code B = 01 is obtained. Next, the organization character length C is obtained from the decision right definition data 7 in 1302 based on the decision code B = 01. In the example of FIG. 32, the decision code B = 0.
1 is detected, and the organization character length C = 4 is obtained. Here, the organization code character length indicates the character length from the beginning of the organization code described above. In the case of the approval right definition data of FIG. 33, the organization character length is set when the approval code of the approval category is 01. If the decision code is 02, the organization character length is 2, and if the decision code is 03, the organization character length is 0. As described above, the organization character length differs according to the approval code entered in the approval category. The organization code is searched based on the organization character length. For example, as shown in FIG. 32, by giving a meaning to the organization code, "the form that can be decided by the factory manager is the form in which the first two characters of the organization code match." Is a slip whose first four characters of the organization code match. "And" a slip that the section manager can approve is a slip whose first six characters of the organization code match. " In this example, the approver Hiroshi Yamada has a decision category 0
1 and a section manager. Therefore, a slip in which the first four characters of the organization code match can be determined. In this way, at 1303, from the slip data 3, the decision category is B (= 01), and the leading C (= 4) character is A (= 5).
03000) is searched for. As a result, the record 301 and the record 302 in FIG. 35 are detected.

As described above, this embodiment relates to a decision processing method in which a decision processing of a slip is performed by a computer.
User-related data that holds information such as the name, affiliation, and approval authority of the computer user; (b) slip data having information such as the subject, amount, and invoicing person described in the slip; Scenario information that holds data for determining the approval category of a voucher, (d) the name of each approval category, the organization code of the invoicing party and the organization code of the approver to check whether the voucher can be approved (E) a slip invoicing function having a judging right judging means, and (f) a slip invoicing function having a judging slip designating means for specifying a to-be-decided slip. It is characterized by the following. In addition, the decision scenario information holding data for determining the decision classification of the generated slip has an omission definition.

In the business processing system having a decision processing method according to this embodiment, the number of characters to be matched from the beginning of the organization code is specified for the decision (organization character length), and the organization code of the authorizer and the decision code are set. This is to determine the authorizer by matching the organization code of the drafter of the target slip by the organization character length and sharing the approval category.

Further, in this embodiment, the definition of default interpretation is included in the decision scenario data, and the definition is used to determine the decision right.

Embodiment 2 FIG. In the above-described embodiment, the hierarchical code is related to the subject. However, the hierarchical code may be related to a hierarchical address code, a product code, or the like, and is not limited to a special code. FIG.
Shows an example where the address code or the product code is hierarchized. In the above-described embodiment, the case where data is input using a code has been described. However, a case where a name or an attribute is directly input without using a code may be used. For example, when a country name or a prefecture name is input and is not coded, a list of country names or a list of prefecture names may be displayed and selected. That is, the present invention is not limited to the case of using a code, but may be a case of inputting hierarchical data using a name or a name.

Embodiment 3 FIG. Further, in the above-described embodiment, the code list of a plurality of windows is superimposed on the code having a hierarchical relationship. However, the display contents of the code list in one window are determined based on operations such as determination and cancellation. May change sequentially.

Embodiment 4 FIG. Further, in the above embodiment, FIG.
In FIG. 34 and FIG. 34, the subject of setting the subject to ANY is shown, but the subject of the omission may be not the subject but the slip type or the amount. FIG. 38 is a diagram showing an example of the decision scenario data of this embodiment. Reference numeral 601 shows a case where the slip type is set to ANY. Reference numeral 603 indicates a case where the amount is set to ANY. Reference numeral 604 denotes a case where both the type of the slip and the subject are set to ANY. As described above, by using the omitted object for the slip type, the subject, and the amount, or by using them in combination, it is possible to further reduce the amount of the definition of the approval scenario data.

Embodiment 5 FIG. In the above embodiment, the organization character string length is stored in the decision right definition data 7, but the organization character string length may be stored in the user-related information. FIG. 39 is a diagram showing an example of the user-related data in this embodiment. The difference from FIG. 31 described above is that the organization character length is added to each record. For example, for record 801, the decision category is 0
Since it is 1, 4 is held as the organization character length.

As described above, in this embodiment, in the decision processing method in which the decision processing of the slip is performed by the computer, in particular, (a)
User-related data that holds information on the code length that should be matched with the invoicing party code of the voucher and the organization code of the voucher to check whether the voucher can be approved along with the computer user's name, affiliation, approval authority, etc. (B) slip data having information such as the subject of the slip described in the slip, the amount of the slip, and the invoicing party, etc .; (c) decision scenario information holding data for determining the decision category of the slip which has been drafted; d) decision right definition information that holds the name of each decision division, (e) a form initiating function having decision right judging means, and (f) a form decision function having decision form designating means for specifying the form to be decided. It is characterized by being.

Embodiment 6 FIG. In the above embodiment, the input code areas are arranged vertically, but the input areas may be arranged horizontally as shown in FIG.

Embodiment 7 FIG. Also, this method is effective even when a code having a hierarchical structure is input as one code as shown in FIG. In this case, from the input code length, which item (for example, a clause or a clause)
Can be realized even if the subject list button is laid out as shown in FIG. 42.

Embodiment 8 FIG. In the above embodiment, the case where the slip approval process does not synchronize the budget amount update process has been described. As a result, the total amount of the budget becomes smaller than it should be. When the total amount of the budget is required, the budget which cannot be seen due to the non-synchronization of the update of the budget may be managed as the reserved amount.

FIG. 43 shows a transition diagram (reservation amount method) of the diverted amount data. In the figure, 1 is a slip issuing function, 2 is a slip decision function, 411, 412, 413, 421, 42
Reference numeral 2423 denotes a budget remaining amount and a reserved amount of the amount data holding various amounts at the present time for each subject. 411,412,
Reference numeral 413 denotes the budget balance and reserved amount of the former subject.
Reference numerals 2,422 and 423 denote budget balances and reservations of the diverted subjects. Reference numerals 411 and 421 denote budget remaining amounts and reserved amounts before the slip invoicing function 1 is activated, and reference numerals 412 and 422 denote budget remaining amounts and reserved amounts before the slip invoicing process 2 is activated after the slip invoicing function 1 is activated. And 413 and 423 are slip approval processing 2
Represents the remaining budget and reserves after is activated.

Next, the operation will be described. here,
50,000 yen from the diversion-existing subject with a budget balance of 2 million yen
A case will be described where an attempt is made to divert to a diversion-destination subject having a budget balance of 100,000 yen. The slip invoicing function 1 reduces the diverted original budget from 2 million yen in 411 to 1.95 million yen in 412, and reserves the diverted amount of 50,000 yen as a reserve amount. The slip approval function 2 reduces the diverted budget from 1 million yen of 422 to 42
3 to 1.05 million yen.

Embodiment 9 FIG. Although the diversion slip processing is described in the above embodiment, it can also be used for processing of a correction slip for correcting later when a mistake is made in a subject, a transfer slip connecting expenditure and income, and a rollover slip for transferring a budget to the next fiscal year. .

FIG. 44 shows a principle configuration diagram for a correction slip. In the figure, 1 is a slip creation function, 2 is a slip decision function, 411, 412, 413, 421, 422, 423
Is the budget remaining amount and the accumulated expenditure of the amount data holding the various amounts at the present time for each subject. 411,412,413
Is the budget balance and the accumulated expenditure of the previous course.
2,422,423 are the budget remaining amount and the accumulated expenditure of the correction original subject. Reference numerals 411 and 421 denote budget remaining amounts and accumulated expenditures before the slip invoicing function 1 is activated, and reference numerals 412 and 422 denote budget remaining amounts and accumulated amounts before the slip invoicing process 2 is activated after the slip invoicing function 1 is activated. The expenditures 413 and 423 represent the remaining budget and the accumulated expenditure after the slip approval process 2 is activated.

Next, the operation will be described. here,
The reimbursement amount of 50,000 yen is being corrected from a revising subject having a budget balance of 700,000 yen to a revising subject having a budget balance of 1.8 million yen. The slip invoicing function 1 reduces the reimbursement budget from 1.81 million yen in 411 to 1.75 million yen in 412. The slip approval function 2 reduces the revised original budget from 700,000 yen of 422 to 423
To 750,000 yen.

Embodiment 10 FIG. In the above-described embodiment, the case of the slip taking out type in which the deciding person takes out the corresponding slip at the time of operating the personal computer has been described. However, the deciding person may be determined from the decision status and the slip may be transmitted by e-mail or the like. FIG. 45 shows the principle configuration diagram of the decision making process (slip transmission type). In the figure, 1 is a slip drafting function, 6
Is a decision scenario data, 7 is a decision right definition data, 8 is user related data, 11 is a decision right judging means, and 19 is a slip transmitting means. The slip is transmitted to the next authorizer in order from the first authorizer.

Next, the overall schematic operation will be described with reference to the slip configuration processing diagram of FIG. The decision right determining means 11 creates the slip data 3 from the decision scenario data 6 and the user-related data 8 based on the slip type and the like. Next, the slip transmission 19 finds a partner to whom the slip is to be transmitted from the decision right definition data 7 and the user-related data 8 and transmits the same.

A more detailed operation of the decision making right judging means 11 will be described with reference to FIG. The approval right determination means 11 searches the approval scenario data 6 using the slip type, the subject, and the amount of money issued by the slip invoicing function 1, and determines the approval category. In this example, the record 603 of the decision scenario data corresponds, and the decision codes of the decision category are 01 and 02.
It is assumed that In this manner, the right to determine decision 11
Adds to the slip data 3 that the decision categories are 01 and 02.

Next, a more detailed operation of the slip transmitting means 19 will be described with reference to the flowchart of the slip transmitting means of FIG. In 1901, the organization character length C is obtained from the decision definition data 7 based on the decision section of the slip data 3. Now, the decision codes of the decision category are 01 and 02. For record 01, a record 701 is detected from the decision right definition data 7 in FIG. This organization character length is 4 (C = 4). Next, in 1902, based on the user-related data 8, the person who has the decision code of 01 in the decision category is the first C (=
4) Search for a character that matches the drafting party organization (= 503010). As a result, since the organization code of the record 801 of the user-related data in FIG. 31 is 503000, the first four characters match 503010, and it is detected that the record 801 of the user-related data is the authorizer. Finally, in 1903, the slip is transmitted to the approver (user code = 0000002) for the record 801.

The same processing is performed for the manager (decision code = 02) of the slip data 3 in FIG. By using the decision section in this way, it becomes possible to transmit the slip to the decider by e-mail or the like.

In this embodiment, the process of following the organizational structure data is unnecessary, and the judgment on the organization is determined simply by matching the organization code of the slip data with the organization code of the authorizer by the length of the organization character. Therefore, high-speed processing can be achieved.

As described above, in this embodiment, in the decision processing method for performing the decision processing of a slip, in particular, (a) user-related data holding information such as the name, affiliation, and decision-making authority of a computer user; b) slip data including information on the subject, amount, and invoicing person described in the slip, (c) decision scenario information holding data for determining the decision classification of the draft slip, and (d) each decision. Decision authority definition information that holds the code name to be matched between the invoicing party organization code of the voucher and the authorizer's organization code to determine the name of the division and the authorizer,
(E) It is provided with a slip invoicing function having a decision right information creating means and a decision status information transmitting / receiving means.

Embodiment 11 FIG. In the above embodiment, the case where the set code is matched from the beginning using the organization character length has been described. However, this organization character length is an example for designating the matching for comparing the organization codes. For example, not only the case where the organization codes are compared from the beginning, but also the case where the organization codes are compared from the back may be used. Alternatively, the characters constituting the organization code may be compared discretely. In such a case, a flag corresponding to each character is provided, and characters whose flags are turned on are matched. For example, if the organization code consists of 8 characters,
By providing a 1-byte (8-bit) flag, associating each character of the organization code with each bit, and making a bit having 1 as a comparison target, the same processing as in the above-described embodiment can be performed.

[0116]

As described above, according to the present invention, a high-speed screen display is performed for a user who has memorized code contents, and a user who does not know the code contents can use a keyboard. This has the effect of making code input unnecessary.

[0117]

[0118]

[Brief description of the drawings]

FIG. 1 is a configuration diagram according to the present invention.

FIG. 2 is a computer system diagram according to the present invention.

FIG. 3 is a screen layout diagram of a diversion slip draft according to the present invention.

FIG. 4 is a diagram of a subject code according to the present invention.

FIG. 5 is a partial layout diagram of subject designation according to the present invention.

FIG. 6 is an explanatory diagram of the operation of the code input means according to the present invention.

FIG. 7 is a screen development diagram (part 1) according to the present invention.

FIG. 8 is a screen development diagram (part 2) according to the present invention.

FIG. 9 is a screen development diagram (part 3) according to the present invention.

FIG. 10 is a screen development diagram (No. 4) according to the present invention.

FIG. 11 is a screen development diagram (part 5) according to the present invention.

FIG. 12 is a flowchart (part 1) of a code input unit according to the present invention.

FIG. 13 is a flowchart (part 2) of the code input means according to the present invention.

FIG. 14 is a screen development diagram (part 6) according to the present invention.

FIG. 15 is a screen development diagram (part 7) according to the present invention.

FIG. 16 is a screen development diagram (No. 8) according to the present invention.

FIG. 17 is a screen development diagram (No. 9) according to the present invention.

FIG. 18 is an expanded view of a screen according to the present invention (part 10).

FIG. 19 is a screen development diagram (No. 11) according to the present invention.

FIG. 20 is a screen transition diagram (1) of a slip draft according to the present invention.

FIG. 21 is a screen transition diagram (2) of a voucher draft according to the present invention.

FIG. 22 is a diagram of money amount data according to the present invention.

FIG. 23 is a screen transition diagram (1) of a slip approval according to the present invention.

FIG. 24 is a screen transition diagram (2) of a slip approval according to the present invention.

FIG. 25 is a screen transition diagram (3) of a slip approval according to the present invention.

FIG. 26 is a transition diagram of diverted own money data according to the present invention.

FIG. 27 is a flowchart of a slip issuing function according to the present invention.

FIG. 28 is a flowchart of a slip issuing function according to the present invention.

FIG. 29 is a diagram showing the principle configuration of a settlement process according to the present invention (slip retrieval type).

FIG. 30 is a diagram of decision scenario data according to the present invention.

FIG. 31 is a diagram of user-related data according to the present invention.

FIG. 32 is a diagram showing an organization code according to the present invention.

FIG. 33 is a diagram of decision right definition data according to the present invention.

FIG. 34 is a flowchart of a decision making right judging means according to the present invention.

FIG. 35 is a diagram of slip data according to the present invention.

FIG. 36 is a flowchart of a settlement slip designating means according to the present invention.

FIG. 37 is a diagram of an address code and a product code according to the present invention.

FIG. 38 is a diagram of decision scenario data according to the present invention.

FIG. 39 is a diagram of user-related data according to the present invention.

FIG. 40 is an input screen layout diagram according to the present invention.

FIG. 41 is an input screen layout diagram according to the present invention.

FIG. 42 is an input screen layout diagram according to the present invention.

FIG. 43 is a transition diagram of a divested amount according to the present invention (retained amount method).

FIG. 44 is a transition diagram of correction amount data according to the present invention.

FIG. 45 is a view showing the principle configuration of a settlement process according to the present invention (slip transmission type).

FIG. 46 is a diagram showing the principle configuration of a slip invoice according to the present invention (slip transmission type).

FIG. 47 is a flowchart of a slip transmission unit according to the present invention.

FIG. 48 is a screen view of a conventional code input method.

FIG. 49 is a flowchart of a conventional code input method.

FIG. 50: Budget control method of the present invention (update method at the time of approval)
Figure.

FIG. 51 is a budget management method (update method at the time of invoicing) of the conventional invention.
Figure.

FIG. 52 is a diagram showing the principle configuration (decision processing) of the conventional invention.

FIG. 53 is a diagram showing a decision making method according to the conventional invention.

FIG. 54 is a diagram showing organization configuration data of a decision making method according to the related art.

[Explanation of symbols]

 DESCRIPTION OF REFERENCE NUMERALS 1 Slip invoicing function 2 Slip approval function 3 Slip data 4 Amount data 5 Code master 6 Decision scenario data 7 Decision right definition data 8 User related data 9 Code input means 10 Amount updating means 11 Decision right judgment means 12 Slip registration means 13 Approval slip designating means 14 Amount updating means 15 Slip updating means 16 Server computer 17 Client computer 18 LAN cable 19 Slip transmitting means

──────────────────────────────────────────────────続 き Continued on the front page (58) Fields surveyed (Int. Cl. ⁷ , DB name) G06F 3/00 601-658 G06F 3/02-3/027 G06F 3/14-3/153 G06F 19/00

Claims (3)

(57) [Claims] 1. A code and data item contents indicated by the code.
A display for displaying a data input screen having a master storing hierarchical data paired with the above, an input field for inputting a code of the hierarchical data , and a list instruction unit for instructing display of a list of input candidates. means and, based on the instruction to display the input candidate list indicated by said list indication portion, which can be input into the input field
Search for the code from the above master and find the code and code
Bei and input means for inputting a code into the input field by displaying a list of data field contents in the list window, to select data from the list displayed shown
For example, the input means corresponds to each layer of the hierarchical data
Input by hierarchy that displays the list window
Means, and the input means according to the upper hierarchy is input according to the lower hierarchy.
By operating the means, hierarchical lower data
When the data list is displayed in the list window and selected
In both cases, the input means according to the lower hierarchy is the input means according to the upper hierarchy
By operating the
Data list in the list window and let the user select it.
Characteristic input assist method. 2. The display device according to claim 1, wherein the display means is a list indicating unit.
And a list of input candidates corresponding to the plurality of hierarchical input means.
Display multiple hierarchical list instructing sections to instruct the display of
Based on the instruction from the hierarchical list instruction section
Operating the corresponding hierarchical input means.
The input assisting method according to claim 1, wherein 3. The hierarchy-based input means includes an upper hierarchy-based input.
Input by upper layer when operated by force
Notification to the means that the data selection has been completed
Means and operate the input means according to the lower hierarchy.
If the user has input the
Confirm the data entry to the field, clear the list window and enter
A contracting means for terminating the force operation.
The input assisting method according to claim 2.