JP4054545B2 - File management system, accounting system, and file management program - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a file management system, an accounting system, and a file management program. More specifically, the present invention relates to a file management system, an accounting system, and a file management program that link and manage various kinds of information about a transaction partner.
[0002]
[Prior art and problems to be solved by the invention]
The journal data created when performing accounting management in a company includes an account item, and an auxiliary item for supplementing the account item is added to the account item. In general, sub-accounts are often recorded in the sub-accounts, and information management such as the name, address, representative, and telephone number of the counterparts recorded in the sub-accounts has traditionally been account items. Was performed for each category (customer, supplier, customer, etc.). For example, it is managed in each master file such as a customer master file that manages the customer as a customer, a supplier master file that manages a customer as a supplier, and a customer master file that manages a customer as a customer. Was.
[0003]
However, there are various transaction modes with the other party, and there are many cases where the other party belongs to a plurality of categories. For example, there are many cases where one partner is a customer and a supplier, and the partner is registered in a plurality of master files. In this case, there is a problem in that the partner's window and the department in contact with the partner are different for each transaction mode, and the same partner's information is managed independently at multiple locations and cannot be managed centrally. . For this reason, changes in information regarding the other party are difficult to manage in common within the company, and there has also been a problem that changes in the other party's information are recognized only in some departments and not in other departments.
[0004]
The present invention has been made to solve the above problems, and an object of the present invention is to provide a file management system, an accounting system, and a file management program capable of centrally managing information on a partner in a company. And
[0005]
[Means for Solving the Problems]
In order to achieve the above object, a file management system according to a first aspect of the present invention provides a destination file having destination information relating to a destination of a transaction and a destination ID corresponding to each of the destination information, the destination information. A classification file having classification content data indicating a plurality of classification contents and a classification ID corresponding to each of the classification contents data, and a plurality of classification IDs corresponding to each of the classification contents data, An extended information file having an extended information ID uniquely provided for each destination information and a classification ID, a destination ID, and an extended information ID are provided corresponding to each category content. A storage means storing a table, an extension information ID specified in the extension information file and the extension information ID based on the table and the destination file Zhang information searching party information corresponding to the classification ID corresponding to the file is configured to include a search means for displaying on the display means the retrieved destination information.
[0006]
A file management program according to a second aspect of the present invention provides a destination file having destination information relating to a destination of a transaction and a destination ID corresponding to each of the destination information, the destination information as the destination information. A classification file having a plurality of classification contents for classification according to each of a plurality of departments to be used, and a classification ID corresponding to each of the classification contents data, corresponding to each of the plurality of classification contents And an extended information file having an extended information ID uniquely provided for each destination information, and a table in which the classification ID, the destination ID, and the extended information ID are associated with each other. In the storage means, based on the table and the destination file, the extension information ID specified in the extension information file and the extension information file in which the extension information ID is specified. Search for destination information corresponding to the classification ID corresponding to Le, those causing a computer to function so as to display on the display means the retrieved destination information.
[0007]
According to the first and second aspects of the invention, various types of information about the other party of the transaction are recorded separately in the other party file and the extended information file classified for each department. Therefore, information that should be managed in common, such as the name, address, and telephone number of the transaction partner, can be centrally managed, and information that differs for each transaction form can be managed independently for each management department. Also, the counterpart information recorded in the counterpart file is associated with the information recorded in the extended information file by a table, and the extended information ID specified in the extended information file and the extended information file specifying the extended information ID are supported. Since the partner information corresponding to the classification ID to be searched is searched and displayed, the extended information managed for each management department can be referred to together with the partner information managed centrally.
[0008]
The file management system according to the first aspect of the invention can predetermine a file for updating each of the destination information. As a result, when there are multiple destination information linked to the extended information file managed independently by each department, the extended information file used mainly by the department having the management right for the destination information can be used. It is possible to determine in advance that only the partner information can be updated.
[0009]
In addition, each of the departments suitable for being subject to centralized management by making the destination information of the file management system of the first invention only information that is commonly used by a plurality of departments for the same destination. It becomes common information.
[0010]
In addition, the classification contents include at least one item of customer, supplier, customer, borrower, lender, partner employee, employee, and trading account. It can be classified appropriately for each management department.
[0011]
In addition, the file management system of the present invention can be incorporated into an accounting system, and partner management can be performed within the accounting system. In this accounting system, a journal file having an account item, an amount, a partner ID, and a classification ID is stored in the storage means, and the journal file is linked to the partner file and the extended information file via the table. You can also
[0012]
DETAILED DESCRIPTION OF THE INVENTION
Embodiments of the present invention will be described below with reference to the drawings.
[0013]
As shown in FIG. 1, the accounting system 10 according to the present embodiment includes a personal computer (hereinafter referred to as a personal computer) 12 and various input / output devices connected to an input / output port 12 </ b> D of the personal computer 12. .
[0014]
The personal computer 12 includes a CPU (Central Processing Unit) 12A, a ROM (Read Only Memory) 12B, a RAM (Random Access Memory) 12C, and an input / output port 12D, which are connected to each other by a bus.
[0015]
A hard disk drive (hereinafter referred to as “HD”) including a magnetic head and a hard disk (hereinafter referred to as “HD”) for writing an accounting management program, which will be described later, as well as a later-described accounting management program and the like as input / output devices. , HDD) 14, floppy disk drive (hereinafter referred to as FDD) 16 for reading and writing data to a floppy disk (hereinafter referred to as FD) 26, and CD-ROM for reading programs and data from the CD-ROM 30. A drive (hereinafter referred to as CDD) 28, a keyboard 18 for inputting data by a user, a mouse 20, a display 22 for displaying an input screen and processing results, and a laser beam printer 24 for printing the processing results are connected. .
[0016]
In the CD-ROM 30, master data registration / update for newly registering extended information master data and destination master data, and updating each master data when the contents of these master data are updated A processing program and the like are stored. The master data registration / update processing program is installed in the HDD 14 of the personal computer 12 by the personal computer 12 reading these processing programs through the CDD 28 and writing the read processing program in the HDD 14.
[0017]
As shown in FIG. 2, the HDD 14 has a partner master file 42, an auxiliary table 44, an auxiliary classification master file 46, an extended information master file 48, a partner employee created by a master data registration / update processing program to be described later. A master file 50, a journal data file 52, and various data for performing other accounting processing (not shown) are recorded. The extended information master file 48 includes a plurality of different extended information master files created for each classification item registered in the auxiliary classification master file 46. In this embodiment, the extended information master file 48 is already a customer master file 48A, a supplier master file 48B, a customer master file 48C, a borrower master file 48D, a loan master file 48E, an employee master file 48F, etc. The extended information master file in which the classification items are defined and at least one user definition master file 48G in which the user can freely define the classification items are configured.
[0018]
As shown in FIG. 3, the destination master file 42 contains destination data common to all the destinations of all transactions recorded in the auxiliary item, which is one item of journal data used for accounting processing. Is recorded. This destination data includes data corresponding to each item such as destination ID, destination name, destination location, representative, employee personal name and contact, and financial status. Data common to all of the above. In the auxiliary classification master file 46, the relationship of the transaction partner recorded in the auxiliary item with the company such as the customer, the supplier, the customer, the borrower, and the lender is related to the transaction. Classification data including data corresponding to each item of the classification content to be classified and the classification ID corresponding thereto is recorded. Customer master file 48A, supplier master file 48B, customer master file 48C, borrower master file 48D, loan master file 48E, employee master file 48F, and extended information master file 48 for user definition master file 48G Corresponds to each item of the extended information ID, the partner code uniquely added to identify the business partner in the department that manages each extended information, and the items related to the detailed information of the business with the business partner Extended information master data including data to be recorded is recorded. For example, in the customer master file 48A, necessary information such as the extended information ID, the partner code, the purchase price of the product, and the deadline date uniquely given by the department that uses this file is used as the extended information master data. It is recorded. The counterpart employee master file 50 records the title of the counterpart employee and other personal information excluding the employee's personal name and contact information registered in the counterpart master file 42. . In the journal data file 52, journal data including each item of account item, amount, debit, credit, partner ID, and classification ID is recorded. The counterpart ID identifies the counterpart for each transaction indicated by the journal data, and serves as an auxiliary subject that assists the account item.
[0019]
In the auxiliary table 44, a record is provided for each extended information master data registered in the extended information master file 48. In each record, data about an auxiliary ID, a classification ID, a partner ID, and an extended information ID are recorded. Has been. The data registered in each of the partner master file 42, the auxiliary classification master file 46, the journal data file 52, and the extended information master file 48 are associated with each other by the auxiliary table 44. For example, the extended information master data with the extended information ID 1 recorded in the customer master file 48A in FIG. 3 has the classification ID 1 (customer) and the extended information ID 1 and corresponds to the auxiliary table 44. The record is a record whose auxiliary ID is 1. Therefore, by referring to the record with the auxiliary ID 1, it is understood that the counterpart master data corresponding to the extended information master data is data of ABC company with the counterpart ID 1.
[0020]
Next, master data registration / update processing when registering or updating partner data and extended information master data recorded in the partner master file 42 according to the present embodiment will be described.
[0021]
The master data registration / update process shown in FIG. 4 is started when a user in a department managing each extended information master file issues a registration / update instruction from the keyboard 18 and mouse 20. When newly registering extended information master data, the user inputs the classification ID of the extended information master data desired to be registered from a search information input screen (not shown) and instructs the registration process by clicking the new registration button. . When updating already registered extended information master data, enter the classification ID and partner code of the target extended information master data from the search information input screen, and update the latest information to display the latest information. Click the button to instruct the update process.
[0022]
In step 70, it is determined whether the user instruction is new registration or update of the extended information master data.
[0023]
In the case of updating, the registration / update screen display process shown in FIG. 5 is performed in step 72, and the registration / update screen shown in FIG. 7 is displayed. In the registration / update screen display process, as shown in FIG. 5, in step 120, the extended information master data corresponding to the input classification ID and partner code is read. In step 122, the record in the auxiliary table 44 corresponding to the extended information ID of the read extended information master data is read, and the partner ID of the partner master data corresponding to this extended information master data is confirmed. In step 124, the destination master data having the confirmed destination ID in the destination master file 42 is read, and in step 126, based on the read destination master data and the extended information master data of the input destination code. The registration / update screen is displayed on the display 22. As shown in FIG. 7, this registration / update screen includes a usage period, a code indicating a master ID, distinction between corporations and individuals, destination information such as company name / branch name / abbreviation, postal code, address, telephone number. An input window for displaying FAX, WEB, person in charge, etc. is arranged, and buttons for registration, deletion and reset are arranged at the top of the update screen. In addition, various buttons such as a latest information button for reading the latest information and an update reference date button for setting an update reference date are arranged on the outer upper portion of the registration / update screen. Each input window displays the contents of each master data based on the read destination master data and the extended information master data of the input destination code.
[0024]
When updating the destination master data, the user directly inputs the updated destination master data information into the input window for the item desired to be updated, and deletes the destination master data before the update. When the extension information master data is updated, the updated extension information master data is directly input to the input window for the item desired to be updated, and the extension information master data before the update is deleted. Then, after completing the input of the update, click the registration button to instruct the update.
[0025]
In step 74, the process waits until an update instruction is given. If there is an update instruction, it is determined in step 76 whether or not an update input of the partner master data has been received. If there is no update input of the partner master data, the process proceeds to step 80. If there is an update input of the partner master data, in step 78, the partner master data is updated based on the input contents from the user. The update of the partner master data is performed by using the partner master data newly created by rewriting only the data that has been updated and input among the data corresponding to each item of the partner master data read in step 122 described above. This is done by adding to the file 42.
In step 80, it is determined whether or not the extension information master data has been updated. If there is no update input of the extended information master data, this process ends. If there is an update input of the extended information master data, the extended information master data is updated by rewriting the data corresponding to the corresponding extended information master data item in step 82 based on the input contents from the user. This process ends.
[0026]
On the other hand, if the extended information master data is newly registered, it is determined in step 84 whether or not the corresponding counterpart master data already exists. This determination is made based on the user's input instruction, but if there is no corresponding destination master data, the user clicks the new registration button (not shown) to indicate that the corresponding destination master data already exists The user inputs the company name of the destination master data in the destination information window and clicks the latest information button.
[0027]
If the corresponding destination master data already exists, steps 120 to 124 of the update screen display process shown in FIG. 6 are executed in the same manner as described above in step 86, and the destination destination read in step 128 is executed. Based on the master data, a registration / update screen for the designated classification ID is displayed on the display 22. In each input window arranged on the registration / update screen, the contents of the partner master data are displayed based on the read partner master data, and the contents of the extended information master data are displayed blank.
[0028]
When the user inputs the extended information master data from the corresponding input window and updates the destination master data, the updated destination master data information is directly input to the input window of the item desired to be updated. While inputting, delete the master data before updating. Then, after completing the registration / update input, the registration button is clicked to instruct registration / update.
[0029]
In step 88, the process waits until a registration / update instruction is issued. If there is a registration / update instruction, it is determined in step 90 whether or not an update input of the partner master data has been received. If there is no update input of the partner master data, the process proceeds to step 94. If there is an update input of the partner master data, in step 92, the partner master data is updated based on the input contents from the user. The updating of the partner master data is performed in the same manner as in step 78 described above.
[0030]
In step 94, extension information master data is created based on the input contents from the user and registered in the extension information master file of the designated classification ID. In step 96, auxiliary table record creation processing A shown in FIG. 8 is performed. As shown in FIG. 8, the auxiliary table record creation processing A creates an auxiliary table record with a new auxiliary ID in step 130. In step 132, the partner ID of the partner master data read in step 124 is written in the portion of the auxiliary table record where the data of the partner ID item is recorded. In step 134, the classification ID of the extended information master data read in step 120 is written in the portion for recording the data of the classification ID item of the auxiliary table record. In step 136, the extended information ID item of the auxiliary table record is written. The extension information ID of the extension information master data read out in the above-described step 120 is written in the portion where the data is recorded, and this process ends.
[0031]
If the corresponding extension master data does not yet exist in the new registration of extended information master data, a new registration screen for extended information master data corresponding to the input classification ID is displayed on the display 22 in step 98. The This new registration screen is displayed in blank in each input window of the registration / update screen shown in FIG.
[0032]
The user inputs the extended information master data from each corresponding input window and inputs the destination master data from each corresponding input window, and after completing the input, clicks the registration button to instruct registration.
[0033]
In step 100, the process waits until there is a registration instruction. If there is a registration instruction, in step 102, the other party master data is created and registered in the other party master file. In step 104, extension information master data is created based on the input contents and registered in the extension information master file. In step 106, auxiliary table record creation processing B shown in FIG. 9 is performed. In the auxiliary table record creation process B, as shown in FIG. 9, in step 130, an auxiliary table record is created with a new auxiliary ID. In step 132, the partner ID of the partner master data registered in step 102 is written in the portion of the auxiliary table record where the data of the partner ID item is recorded. The processing in step 134 and step 136 is performed in the same manner as the auxiliary table record creation processing A in step 96 described above, and this processing is terminated.
[0034]
According to the present embodiment, in the partner master file, the partner master data, which is information common to the partner regardless of the transaction form with the partner such as the customer or the supplier, is sent to one partner. In each extended information file 18, extended information master data, which is different information for each transaction mode, is stored in a separate file for each partner as many as the number of transaction modes with that partner. sign up. Then, the partner master data and the extended information master data are linked via the auxiliary table, and the extension information master data is referred to together with the corresponding partner master data.
[0035]
Also, registration and update of the partner master data is performed together with registration and update of the linked extended information master data.
[0036]
Therefore, there is no need to update multiple data for the same partner, management of information common to the partner is centrally managed within the company, and information updates common to the partner are commonly recognized internally. be able to. In addition, it is possible to prevent information correction omission and occurrence of time lag. In addition, information on a different party for each transaction mode can be managed independently for each department in charge in the company, and can be managed according to the purpose of use for each department in charge.
[0037]
In addition, since the auxiliary master data and the extended information master data are linked by providing an auxiliary table, the same code or the like is assigned to each extended information master data for the same counterpart, and the same counterpart is established. There is no need to specify this, and various tabulations on the same counterpart can be easily performed.
[0038]
It is also possible to set a main management department for each counterpart in the company, and to give only the management department the right to update the counterpart master data. Thereby, it is possible to ensure the reliability of the destination master data.
[0039]
In addition, for private information such as employee addresses and other information that only specific departments want to refer to, mask the information unit so that it cannot be referenced by departments other than specific departments. You can also.
[0040]
In addition, since the master data registered in the master file can be reused as the address book of the business partner, the latest information can be used for addressing direct mails such as New Year's cards and campaigns. The partner master data can be used efficiently.
[0041]
Further, by providing the auxiliary classification master file, it is possible to arbitrarily classify the destination and set the classification contents. In this embodiment, each transaction mode is classified into customer, supplier, customer, etc., but other categories such as other companies in the same industry, rotary clubs, etc. are also used for managing the other party. You can also.
[0042]
In addition, by providing a partner employee master file to centrally manage information about the partner employee and linking it with the extended information master data, it is possible to make a smooth contact with the person in charge of the partner.
[0043]
In addition, information such as the name and address of the partner employee is registered as partner master data in the partner master file. Therefore, when the partner employee becomes a customer or a borrower, the data It can be reused and flexible support is possible.
[0044]
【The invention's effect】
As described above, according to the first and second inventions, the various information about the transaction partner recorded in the supplementary subjects is divided into the partner file and the extended information file classified by department. Record. Therefore, information that should be managed in common, such as the name, address, and telephone number of the transaction partner, can be centrally managed, and information that differs for each transaction form can be managed independently for each management department. Also, the counterpart information recorded in the counterpart file is associated with the information recorded in the extended information file by a table, and the extended information ID specified in the extended information file and the extended information file specifying the extended information ID are supported. Since the partner information corresponding to the classification ID to be searched is searched and displayed, the extended information managed for each management department can be referred to together with the partner information managed in a centralized manner.
[Brief description of the drawings]
FIG. 1 is a schematic diagram of a file management system of the present invention.
FIG. 2 is a part of a database according to the present embodiment.
FIG. 3 is a schematic relation diagram of each master file.
FIG. 4 is a flowchart of a master data registration / update process.
FIG. 5 is a flowchart of an update screen display process.
FIG. 6 is a flowchart of a registration / update screen display process.
FIG. 7 is an example of a master data registration / update screen.
FIG. 8 is a flowchart of auxiliary table creation processing A.
FIG. 9 is a flowchart of auxiliary table creation processing B;
[Explanation of symbols]
10 Accounting system
12 PC
14 HDD (storage means)
26 FD
30 CD-ROM
42 Destination master file
44 Auxiliary table
46 Auxiliary classification master file
48 Extended information master file
52 Journal data file

Claims (7)

A destination file having destination information on the destination of the transaction and a destination ID corresponding to each of the destination information;
A classification file having classification content data indicating a plurality of classification contents for classifying the destination information according to each of a plurality of departments using the destination information, and a classification ID corresponding to each of the classification contents data ,
An extended information file provided corresponding to each of the plurality of classification contents and having an extended information ID uniquely provided for each destination information, and
A table in which a classification ID, a partner ID, and an extended information ID are associated with each other;
Means for storing
Based on the table and the destination file, the destination information corresponding to the extension information ID specified in the extension information file and the classification ID corresponding to the extension information file specifying the extension information ID is searched and searched. Search means for displaying the partner information on the display means;
File management system with The file management system according to claim 1, wherein a file for updating each of the destination information is predetermined. 3. The file management system according to claim 1, wherein the destination information includes only information commonly used by the plurality of departments for the same destination. 4. The file management system according to claim 1, wherein the classification content includes at least one item of a customer, a supplier, a customer, a borrower, a lender, a counterparty employee, an employee, and a trading account. . An accounting system comprising the file management system according to claim 1. A journal file having an account item, an amount, a partner ID, and a classification ID is stored in the storage means, and the journal file is linked to the partner file and the extended information file via the table. 5. Accounting system according to 5. A destination file having destination information on the destination of the transaction and a destination ID corresponding to each of the destination information;
A classification file having classification content data indicating a plurality of classification contents for classifying the destination information according to each of a plurality of departments using the destination information, and a classification ID corresponding to each of the classification contents data ,
An extended information file provided corresponding to each of the plurality of classification contents and having an extended information ID uniquely provided for each destination information, and
A table in which a classification ID, a partner ID, and an extended information ID are associated with each other;
Is stored in the storage means storing the counterpart information corresponding to the extension information ID specified in the extension information file and the classification ID corresponding to the extension information file specifying the extension information ID based on the table and the destination file. A file management program that causes a computer to search for destination information and display the searched destination information on a display means.

Images