JP3244171B2 - Fiscal year information access system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an annual information access system, and more particularly to an annual information access system in which a settlement month can be set to a desired month.

[0002]

2. Description of the Related Art For example, in a store selling electric products, monthly sales and profits are stored in a database in which monthly information is stored every month, and a predetermined year-end (for example, March every year) is stored. In general, the settlement process is performed. Monthly information for one year stored in this database is referred to as “year record”.

FIG. 4A shows an example of a conventional year record. In this year record, April is the beginning of a certain year (starting year), and March of the following year (second year) is the end of the year. Information (not shown) such as sales is stored for each month.

In a conventional system for accessing year records (year record access system or year information access system), a predetermined record format shown in FIG.
1996) from April to December, and the following year (1997)
Month) from January to March) is acquired as a "year record" (a record of the year, a group of records).

[0005]

However, this prior art has the following problems. The first problem is that the settlement month (for example, March) cannot be arbitrarily changed on a program. The reason is that in the conventional annual record access system, the record format is fixed in advance (fixed to the state shown in FIG. 4A), and the settlement month is fixed (in this case, settlement in March). It is.

A second problem is that when the settlement month is changed (for example, the March settlement is changed to the December settlement), a database migration operation is required [from the state of FIG. Transition to state B)]. The reason is that the change of the settlement month is not taken into account.

[0007] Therefore, the object of the present invention is to settle the settlement month (base month)
Is to provide an annual information access system that can be set to a desired month.

[0008]

In order to solve the above-mentioned problems, the present invention relates to a year-by-year and month-by-year information storing means for storing monthly information for a plurality of years for each month for 12 months. ,
For each year / month information stored in the year / month information storage means, a reference year / base month designating means for designating a desired year and a reference month, and the respective year / month information storing means, Year information editing means for editing the year information of the year corresponding to the base year / base month based on the base year / base month specified by the base year / base month specifying means.

In this way, when the desired year and the reference month are specified from the information stored in each year / month information storage means by the reference year / month reference specifying means, the year information editing means is provided. Edit to the year information of the year corresponding to the desired base year / base month. Therefore, it is possible to easily access year information for a desired reference month (final month).

[0010]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to the drawings by dividing it into (1) a concept of the present invention and (2) an embodiment.

(1) Concept of the Present Invention The present invention uses a calendar year as a key in advance to store monthly information (for example, monthly sales, etc.) for one year (for 12 months from January to December). In a database system that collectively stores data as one record, by specifying a settlement month and year, information on all months belonging to the specified year is acquired as if it were one record (collective record). It is a system that can.

In FIG. 1, for example, monthly information from January to December 1996 is stored in a database 20 as a starting year record 21, and as a next year record 22, a 1997 year is recorded.
Monthly information from January to December is stored. here,
The starting year record is the starting year (for example, 1996).
The records of sales and the like are recorded in order from the month to December. The next-year record is a record of sales and the like in the order from January to December of the next year (for example, 1997, which is the year following the starting year of 1996). It is. That is, the “year record” means that the sales amount is 1
It is simply recorded from the month to December, and is not regarded as a “year record” (for example, a record from April this year to March of the following year).

In this state, for example, "year" is 19
When March is designated as the “financial month” in 1996, the information of the starting year record 21 for April to December and the information of the next year record 22 for January to March are transferred to the (From April to March of the following year) is stored in the year record return area 10 which is an area for storing information.

By doing so, the designated year [for example, 19
The information of all the months included in the fiscal year 1996 (April 1996 to March 1997) is stored in the annual record return area 10 as if it were one record (collective record). Can be handled.

(2) Embodiment Referring to FIGS. 2 (A) and 2 (B), this embodiment uses a calendar year as a key to store monthly information for one year (12 months from January to December). ), A database device 70 which is “each year / month information storage means” storing one record (hereinafter, referred to as year record), and two years for the starting year and the next year. And a data processing device 60 that is an "year information editing means" for reading the "year record" and editing the "year record" (for example, from April this year to March of the following year).
A user program 50 that is a "base year / base month designating means" that uses the "year record".

The database device 70 includes "year records" for each year. In particular, as the “year record” which dynamically changes according to the designated year and holds information for each month of the designated year, the starting year record 7
1 and a runner-up year record 72.

The starting year record 71 holds an "year record" for one year of the starting year, and the next year record 72 also holds an "year record" for one year of the starting year (FIG. 2B). ]. The data processing device 60 includes a starting year record acquisition unit 61,
A next-year record acquisition unit 62 and a year record editing unit 63 are provided.

The starting year record obtaining means 61 obtains the starting year (in this case, 1996) based on the year (for example, 1996) designated by the user program 50,
The starting year record 71 stored in the database device 70 is acquired using the starting year as a key.

The next-year record acquisition means 62 stores the year designated by the user program 50 (in this case, 1996).
The next year is obtained based on the (year), and the next year record 72 stored in the database device 70 is acquired using the next year as a key.

The year record editing means 63 includes a start year record 71 obtained by the start year record obtaining means 61 and a next year obtained by the next year record obtaining means 62 based on the settlement month specified by the user program 50. Record 72
The year record is edited from the information of each month, and is returned to the user program 50.

Next, the operation of this embodiment will be described in detail with reference to FIGS.

The user program 50 has a year (for example, 1
996) and the settlement month (for example, March) are given to the data processing device 60. In the data processing device 60, the starting year record obtaining means 61 reads the starting year (in this case, 1996) from the given year (in this case, 1996).
Is calculated, and a starting year record 71 (FIG. 2B) is obtained from the database device 70 using the starting year as a key (step A1). It is determined whether the acquisition is successful or unsuccessful (step A2).
N (step A3), and a starting year record 71 is stored in a starting year record temporary storage area (not shown) (step A4). If it fails, the starting point flag is turned off (step A5), and the starting year record temporary storage area is initialized (step A6).

The next-year record obtaining means 62 calculates the start month of the year from the given settlement month (step A7).
If the year start month is January (Step A8: =), the next point flag is turned off (Step A13), and the next point year record temporary storage area is initialized (Step A14).

If the start month of the fiscal year is not January (step A8: $), the next year is calculated from the starting year obtained by the starting year record obtaining means 61, and the next year is used as a key from the database device 70. Then, the second-year record 72 is acquired (step A9). It is determined whether the acquisition was successful or unsuccessful (step A10). If the acquisition was successful, the next point flag is turned on (step A11), and the next point record is temporarily stored in the next year record temporary storage area (not shown). The year record 72 is stored (step A12). If it fails, the next point flag is turned off (step A13), and the next year record temporary storage area is initialized (step A14).

The year record editing means 63 determines the starting point flag and the next point flag (step A15), and at least one of the starting point flag and the next point flag is ON.
In this case, the year record is edited from the starting year record temporary storage area and the next year record temporary storage area (step A16), and the year record is returned to the user program 50 (step A17). When both the start point flag and the next point flag are OFF, a state value indicating that the year record cannot be obtained is returned (step A18).

In the present embodiment, the settlement month is March (see FIG. 1), but it is needless to say that the settlement month may be December, for example.

It is needless to say that the program described in the present embodiment can be provided to a third party while being stored in a recording medium (for example, a floppy disk).

[0028]

As described above, according to the present invention, the following effects can be obtained. That is, the database stores information for each month for one year (for 12 months from January to December) and stores it as one record. Since it can be returned as an annual record, it is possible to return an annual record corresponding to any type of year only by specifying the year and the settlement month. As a result, even if the settlement month is changed, the transfer can be performed without changing the format of the records stored in the database, and the cost for the transfer operation can be reduced.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating the concept of the present invention.

FIG. 2 is a block diagram of an embodiment of the present invention,
(A) is an overall configuration diagram, (B) is a diagram showing the recording status of the database device.

FIG. 3 is an operation flowchart of the embodiment.

4A and 4B are diagrams for explaining a recording state of a conventional database, wherein FIG. 4A shows a recording state when March is set as a settlement month;
(B) shows the recording status when December is shifted to the settlement month.

[Explanation of symbols]

 10 year record return area 20 database 50 user program 60 data processing device 61 starting year record obtaining means 62 second year record obtaining means 63 year record editing means 70 database device 71 starting year record 72 next year record

Claims (4)

(57) [Claims] Claims: 1. An information storage means for each year and month storing information for each month over a plurality of years for 12 months for each year, and an information storage means for each year stored in the information storage means for each year and month. For the monthly information, a base year / base month specifying means for specifying a desired year and a base month, and a base year / base specified by the base year / base month specifying means from the respective year / month information storing means. An annual information access system comprising: year information editing means for editing year information of a base year and a year corresponding to the base month based on the month. 2. The yearly information access system according to claim 1, wherein the reference month is a settlement month in which settlement is performed for each year. 3. The year information access system according to claim 1, wherein said year information editing means edits the year information for 12 months by calculating backward a designated base month. 4. A recording medium storing a program for accessing information stored in a database by a computer, the program storing, in a computer, information for each month over a plurality of years for each year. For 12 months in the database, and for each year / month information stored in the database, specify the desired year and the base month. Based on the specified base year / base month, this base year -A recording medium recording a system for accessing year information, wherein the year information of the year corresponding to the base month is edited.