JP5144974B2 - Module management method, module management apparatus, and module management program - Google Patents

Description

  The present invention relates to a module management method for managing data and modules in a business processing system that may change a data processing method in units of a fiscal year or a specific period.

  Business processes such as finance / accounting, tax, sales / purchase management, and salary management are often changed in units of fiscal years or specific periods due to changes in related laws. In recent years, these business processes are often performed on a computer system, and various application systems such as an accounting system, a report creation system, a sales purchase management system, a payroll system, and a financial statement creation system are used for these business processes. It is used. When the processing method changes, it is necessary to update the program (module) used in the application system in accordance with the change. Since not only the processing method is changed but also the update is performed by improving the module, various versions of the module exist.

  The data created by these modules is created and managed individually in each application system. On the other hand, data managed by application systems such as finance / accounting, tax, sales / purchase management, and salary management often have common items and items related to each other. Therefore, from the viewpoint of improving the efficiency of data management and preventing inconsistencies, it is desirable that related data is stored on the same computer and can be diverted and referred to each other.

  However, in order to store and refer to each other stored on the same computer, it is desirable to manage all data by matching the information, but not only the data types are diverse, but also As described above, there is data created by various versions of modules, and it is necessary to manage the version of the data created, which makes management very complicated. Here, the version means generation identification information that can identify the update of a program or module and the data created by which program or module.

  As a conventional management method for maintaining the consistency between data and modules, there is a method of adding version information to data and storing it. In this method, when a business process is performed using data created with an old version module created in the past with a new version module, the data processed with the old version is converted into a new version. In this way, by converting the data processed in the old version into the new version, the old data is gradually reduced, and only the new version of the module and the corresponding data are obtained, making it easy to achieve matching.

  Further, as another technique for maintaining the consistency between the module and the data, for example, a technique described in Patent Document 1 below is disclosed. In the technique described in Patent Document 1 below, the program and data are easily matched by storing the program and data in different exchangeable storage media for each version.

  In addition, when there are multiple versions of modules as described above, when an operator performs business processing, first, the operator determines which version of the module is to be used for processing and selects the module based on the determination. It is common to start a version of a module. In this method, the operator himself / herself needs to know information about each version. Therefore, for example, even when it is appropriate to process with a new version, there is a possibility that an operator may accidentally start an old version of a module.

  In order to reduce the burden on the operator, a technique described in Patent Document 2 below is disclosed as a method for selecting a program to be automatically started. In the following Patent Document 2, the old program before update and the new program after update have the same name. Then, if a change date is defined and the operator performs an operation to start the program, the new program is automatically started if the date is after the change date, and the old program if the date is before the change date. Is automatically started.

JP-A-5-303488 Japanese Patent Publication No. 5-50772

  However, in the above conventional version management method, the new version of the module and the data processed by the module are unified, so that the old version of the module cannot be used for processing. Even when a module is upgraded due to a revision of the law, for example, in the process of preparing a revised report, it is necessary to process with an old version of the module in accordance with the regulations at that time. For this reason, it is necessary for the new version of the module to include the functions of the old version of the module, and there has been a problem that the program becomes enlarged and the process control within the program becomes complicated each time it is updated.

  In the technique described in Patent Document 1, the program and data are managed on different media for each version. For this reason, it is difficult to refer to different versions of data at the same time, and when performing processing for multiple years, it is very troublesome because processing is performed while searching for media and exchanging media. There was a problem.

  In the technique described in Patent Document 2, only the old and new programs are managed. For this reason, there is a problem that it is difficult to manage three or more versions. In addition, there is a problem that there are many operational restrictions such as the need to make the old and new programs have the same name.

  In the above-described technique, module and data are managed for one type of module processing. For this reason, there is a problem that data created by a plurality of types of related modules cannot be matched.

  The present invention has been made in view of the above, and an operator can start a module with a simple operation without being aware of the version, and can process a plurality of versions of the module without enlarging the module. An object of the present invention is to obtain a module management method, a module management device, a module management system, and a module management program that can be realized and can correctly maintain the consistency of data created by a plurality of types of modules.

In order to solve the above-described problems and achieve the object, the module management method according to the present invention is a module having a different application period defined for each regulation, and creates processing target data that is data to be processed. or more modules to be updated, the module management method in the business processing system comprising a business application having the processed data selection unit, the processing of the object data type and tries to process represents the time to be processed period including conditions The condition setting step for acquiring setting information and the module determination unit store the module identifier and module version for identifying the plurality of modules in association with each other for each data type and module application period. reads the module management information are from the storage unit, the read module tube A module determining step of extracting a module identifier corresponding to the condition setting information from the information, the module linkage unit is, the module corresponding to the extracted module identifier from the storage unit, and the module activation step of activating the module , module linkage unit is, data that the activation modules created, the data information including the type and the processing period and version, seen including a data management step of storing in the storage unit, and in said module determining step, When newly creating processing target data, the module management information in the storage unit is searched, and if there is module management information for storing the data type and application period corresponding to the condition setting information as a search result, this module management Extract module identifier from information and use it as search result If there is no module management information that stores the data type corresponding to the recording condition setting information and the application period, the module management information that stores the data type that matches the type of data to be processed is searched and obtained by the search. If the module identifier is extracted from one module management information determined based on the size of the version included in the module management information and the processing target data is not newly created, the stored data corresponding to the condition setting information is stored. Acquire data information, search for module management information in the storage unit, acquire module management information for storing the data type and application period corresponding to the condition setting information, the version of the version included in the acquired data information One module determined based on the size and the size of the version included in the acquired module management information The module identifier is extracted from the module management information .

Module management method according to the next invention is the different modules of application period determined for each regulations, a plurality of modules to create or update a processing target data is data to be processed, the business application with in the module management method in the business processing system including processing data selection section includes a condition setting step of the process period representing a period to be the type and processing of the processing target data to acquire including conditions setting information, application period management The module reads the module management information stored in association with the module identifier for identifying the plurality of modules and the module version for each data type and module application period , and reads the module management information . module corresponding to the condition setting information from the module management information A module determining step of extracting Le identifier, module linkage unit is, reads the module corresponding to the extracted module identifier from the storage unit, and the module activation step of activating the module, the module linkage unit is, and the activation data module creates the data information containing the type and the processing period and version, a data management step of storing in the storage unit, only contains, in the module determination step, the processed data to create new Searches for module management information in the storage unit, and if there is module management information for storing the data type and application period corresponding to the condition setting information as a search result, extracts the module identifier from this module management information and searches As a result, the data type corresponding to the condition setting information and the appropriate If there is no module management information that stores the period, the module management information that stores the type of data that matches the type of data to be processed is searched, and the size of the version included in the module management information obtained by the search The module identifier is extracted from one module management information determined based on the above, and when the processing target data is not newly created, the stored data information corresponding to the condition setting information is acquired, and the module management in the storage unit is acquired. Information is retrieved to obtain module management information for storing the data type and application period corresponding to the condition setting information, and the size of the version included in the acquired data information and the version of the version included in the acquired module management information are acquired. A module identifier is extracted from one module management information determined based on the size. , Characterized in that.

The module management apparatus according to the next invention, a different modules of application period determined for each regulations, a plurality of modules to create or update a processing target data is data to be processed, the business application with in module management unit in the business processing system including, the type of the processing target data and the processed data selection unit that processes the I and processing period representing a period for try to acquire including conditions setting information, application period of the data types and modules Each time module management information in which module identifiers for identifying the plurality of modules and module versions are associated and stored is read from the storage unit, and the condition setting information is associated with the read module management information. A module determination unit for extracting a module identifier; Reads the module corresponding to the extracted module identifier from the storage unit, store and launch the module, the data generated activated the module, the data information including the type and the processing period and version, the storage unit A module linking unit, and the module determination unit searches the module management information in the storage unit when newly creating the processing target data, and the data type corresponding to the condition setting information as a search result If there is module management information for storing the application period, a module identifier is extracted from this module management information, and there is no module management information for storing the data type and application period corresponding to the condition setting information as a search result The module management information that stores the data type that matches the type of data to be processed If the module identifier is extracted from one module management information determined based on the size of the version included in the module management information obtained by searching and the processing target data is not newly created, the condition setting information Is stored, the module management information in the storage unit is searched, module management information for storing the data type and application period corresponding to the condition setting information is acquired, and the acquired data A module identifier is extracted from one module management information determined based on the version size included in the information and the version size included in the acquired module management information .

The module management apparatus according to the next invention, a different modules of application period determined for each regulations, a plurality of modules to create or update a processing target data is data to be processed, the business application with in module management unit in the business processing system including, the type of the processing target data and the processed data selection unit that processes the I and processing period representing a period for try to acquire including conditions setting information, application period of the data types and modules Each time module management information in which module identifiers for identifying the plurality of modules and module versions are associated and stored is read from the storage unit, and the condition setting information is associated with the read module management information. An application period management unit for extracting a module identifier; Reads the module corresponding to the serial extracted module identifier from the storage unit, store and launch the module, the data generated activated the module, the data information including the type and the processing period and version, the storage unit The application period management unit searches the module management information in the storage unit when creating new processing target data, and the type of data corresponding to the condition setting information as a search result If there is module management information for storing the application period and the module management information, the module identifier is extracted from this module management information, and there is no module management information for storing the data type and application period corresponding to the condition setting information as a search result Search for module management information that stores the type of data that matches the type of data to be processed If the module identifier is extracted from one module management information determined based on the size of the version included in the module management information obtained by the search, and the processing target data is not newly created, it corresponds to the condition setting information. The stored data information is acquired, the module management information in the storage unit is searched, the module management information for storing the data type and the application period corresponding to the condition setting information is acquired, and the acquired data information A module identifier is extracted from one module management information determined based on the size of the included version and the version included in the acquired module management information .

  A module management program according to a next invention causes a computer to execute the module management method according to any one of claims 1 to 14.

  The module management method, the module management apparatus, the module management system, and the module management program according to the present invention are based on the input target period (processing data) based on the correspondence between the application period stored in the application period management table and the module to be activated. The module corresponding to the target period) can be started, so that the module can be started with a simple operation without the operator being aware of the version, and multiple versions of the module can be processed without enlarging the module. And the consistency of data created by a plurality of types of modules can be maintained correctly.

  Embodiments of a module management method, a module management apparatus, a module management system, and a module management program according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

  FIG. 1 shows a configuration example of a computer system having a function as a module management apparatus for realizing the module management method according to the first embodiment of the present invention and capable of executing the module management program according to the present embodiment. FIG. This computer system includes, for example, a control unit 1, an input unit 2, a storage unit 3, a display unit 4, a communication unit 5, and a printing unit 6, which are connected via a system bus 7.

  In FIG. 1, the control unit 1 executes a module management program according to the present invention. The input unit 2 is composed of, for example, a keyboard and a mouse, and is used by a computer system user to input various information. The storage unit 3 includes various memories such as a RAM and a ROM and a storage device such as a hard disk, and stores programs to be executed by the control unit 1 and necessary data obtained in the course of processing. The storage unit 3 is also used as a temporary storage area for programs. The display unit 4 is composed of a CRT, LCD (liquid crystal display panel), etc., and displays various screens for the user of the computer system.

  Here, an operation example of the computer system until the module management program according to the present invention becomes executable will be described. In the computer system having the above-described configuration, for example, a module management program is installed in the storage unit 3 from a CD-ROM set in a CD-ROM drive (not shown). When the module management program is executed, the module management program read from the storage unit 3 is stored in a predetermined location in the storage unit 3. In this state, the control unit 1 executes module management processing according to the program stored in the storage unit 3.

  In the present embodiment, a program describing the module management process is provided using a CD-ROM as a recording medium. However, the present invention is not limited to this, and it depends on the configuration of the computer system, the capacity of the provided program, and the like. For example, a recording medium such as a magnetic disk such as a floppy (registered trademark) disk, a magneto-optical disk, or a magnetic tape may be used. Moreover, it is good also as using the program provided by transmission media, such as an email and the internet.

  FIG. 2 is a block diagram illustrating a functional configuration example of the module management apparatus according to the present embodiment. The module management processing unit 10 is a control unit of the module management apparatus of this embodiment and is included in the control unit 1. The module management processing unit 10 includes a processing data selection unit 11, a module determination unit 12, an update propagation management unit 13, and a module cooperation unit 14. The module management processing unit 10 according to the present embodiment operates using a database management unit 20 that manages a relational database, an input unit 2, a storage unit 3, a display unit 4, and a module processing unit 30. The database management unit 20 is a common function of the entire computer system that manages a relational database, such as a SQL (Structured Query Language) server function. Moreover, the process data selection part 11, the module determination part 12, the update propagation management part 13, and the module cooperation part 14 are contained in the control part 1 of FIG.

  The module processing unit 30 on the control unit 1 is a control unit for applications such as finance / accounting, tax, sales purchase management, and salary management. The module management processing unit 10 according to the present embodiment is activated from a module program group that is a program of each module of applications such as finance / accounting, tax, sales purchase management, and salary management stored in the storage unit 3. The module program corresponding to the target module is read and stored in a predetermined location in the storage unit 3. The module processing unit 30 executes processing according to a program stored at a predetermined location in the storage unit 3.

  Here, the database of the present embodiment will be described. In this embodiment, the module processing unit 30 unifies the data generated by executing the processing of each application such as finance / accounting, tax, sales purchase management, salary management, etc. as one database via the database management unit 20. to manage. For example, when the module processing unit 30 executes a report creation application, report data is generated. In FIG. 2, report data as an example of data generated by the application, a subject master to be used / referenced by the application, and various data are described.

  The subject master is master data for managing subjects. FIG. 3 is a diagram illustrating an example of a subject master. As shown in FIG. 3, the subject master includes, for example, a code (subject code), a subject name, a loan classification, a consumption tax classification, and the like. Examples of the various data include salary data, accounting data (journal data), company information data, asset data, sales management data, and the like. FIG. 4 is a diagram illustrating an example of salary data, which is an example of various data. As shown in FIG. 4, salary data includes, for example, employee number, basic salary, payment 1 (amount of payment for the first payment item), payment 2 (amount of payment for the second payment item), deduction 1 (the first payment item) Deduction amount of deduction item), deduction 2 (deduction amount of second deduction item), etc. are included. 3 and 4 are examples, and the data format and items are not limited to this, and any data may be used as long as it is generated by the application.

  Further, the subject master, report data, and various data have the same identification information (version) as the identification information (version) that can be identified by the module that created each data. In addition to the data created by these applications, a management table group used for processing by the module management processing unit 10 is also stored on the database.

  Subsequently, the overall operation procedure of the module management process of this embodiment will be described. FIG. 5 is a flowchart illustrating an example of the procedure of the overall operation of the module management process according to this embodiment. The module management processing of this embodiment is started when the operator operates the input unit 2 when the operator performs processing such as finance / accounting, tax, sales purchase management, salary management, and the like. Here, the case where a report preparation process is performed is demonstrated as an example. First, the processing data selection unit 11 displays a screen for prompting input of condition settings on the display unit 4.

  At this time, the items that require input include the type of data (corporate tax return, consumption tax return, etc.), classification (final return, intermediate return, etc.), and target period (target period of the data to be created). And In addition, a list of existing created data may be displayed so that the operator can select data to be edited from the list, and input of data type, category, and target period may be omitted.

FIG. 6 is a diagram illustrating an example of the data management table of the present embodiment. The data management table is one of the management table groups on the database. As shown in FIG. 6, the data management table of the present embodiment includes a data ID (Identifier), a data type, a classification, a target period, and a version (Ver). In this embodiment, it is managed by the item data management table as shown in FIG. 6, in the display of the list of existing creation data described above, the type of data from the data management table, the matching record sections The read result is displayed. The data ID is an identifier assigned by the module cooperation unit 14 when data is newly created by the module processing unit 30 described later. For each record in the data management table, when the module processing unit 30 generates or updates data, the module cooperation unit 14 acquires the data type, classification, and target period related to the data from the module processing unit 30, and Add a version and register it in the data management table. In this embodiment, the module cooperation unit 14 assigns the data ID and registers the data management table. However, the module processing unit 30 assigns the data ID and includes the version in the data management table. Registration may be performed. In the example of FIG. 6, the type is only one column. However, when there are a large number of types, a classification in which the types are grouped is added, and the processing data selection unit 11 operates when displaying on the display unit 4. Display may be easy to select.

  The processing data selection unit 11 receives input of condition settings including the type, classification, and target period of data by the operation of the input unit 2 by the operator, and refers to a data management table described later based on the input condition settings. It is determined whether or not the data is already registered. If the data is already registered, the creation category is set to “edit”, and if it is not registered, the creation category is set to “new”. Then, the input condition setting information and creation classification are output to the module determination unit 12 (step S1). In addition, the designation by the creation category may be instructed from the input unit 2.

  The module determination unit 12 determines the module and version to be activated based on the condition setting information, and notifies the module cooperation unit 14 of the module to be activated together with the process data condition setting information (step S2). In this embodiment, the module for executing the report creation process is generated for each data type, and the module to be activated can be determined when the data type and version are determined. Specific processing for module determination will be described later.

  Then, the module cooperation unit 14 reads out the program corresponding to the notified module from the module program group in the storage unit 3 and stores it in a predetermined location in the storage unit 3, and the module processing unit 30 operates according to the stored program. Is started (module activation: step S3).

  When referring to past data, the module processing unit 30 reads various data and reference target data via the database management unit 20, and follows the editing by the operation of the input unit 2 by the operator based on both read data. A predetermined report is created (step S4). If past data is not referred to, various data are read out via the database management unit 20, and a predetermined report creation process is performed according to the information input by the operator (step S4). Then, the module processing unit 30 stores the created report data in the database via the database management unit 20 (step S4).

  When the report data is updated (created) in step S4, the module processing unit 30 updates the updated data type (for example, subject master data, report data, accounting data, etc.) and version. 13 and the update transmission management unit 13 reflects the update of the report data in the related data (step S5). Then, the module management process of the present embodiment ends. The process of reflecting related data will be described later.

  Next, the module determination process described in step S2 of FIG. 5 will be described. FIG. 7 is a flowchart illustrating an example of a module determination process procedure according to this embodiment. First, the module determination unit 12 acquires condition setting information (step S11). Then, based on the creation category, it is determined whether or not the process data is newly created (step S12). If it is determined that the data is newly created (step S12 Yes), the module management table is searched to determine whether there is a record having a data type and an application period corresponding to the condition setting information (step S12). S13). FIG. 8 is a diagram illustrating an example of a module management table according to the present embodiment. As shown in FIG. 8, the module management table of this embodiment includes a version, a data type, an application period, and a module (module name). The module (module name) may be any information as long as it can distinguish the module to be activated, such as a name and an identifier.

  When it is determined that there is a record having the data type and application period corresponding to the condition setting information in the module management table (Yes in step S13), the module determination unit 12 is stored in the corresponding record. The module is determined as a module to be activated, and the module cooperation unit 14 is notified of the determined module together with the process data condition setting information (step S14).

  If it is determined that there is no record having the data type and application period corresponding to the condition setting information in the module management table (No in step S13), the data type is the data type of the condition setting information. Among the matching module management table records, the record having the largest version is searched. Then, the module stored in the searched record is determined as the module to be activated, and the determined module is notified to the module cooperation unit 14 together with the condition setting information of the processing data (step S15).

  On the other hand, when it is determined in step S12 that it is not a new creation (No in step S12), the module determination unit 12 searches the data management table, acquires data corresponding to the condition setting information, and uses it as data information. . Further, the module management table is searched to determine whether or not there is a record having a data type and an application period corresponding to the condition setting information (step S16). If it is determined that there is a record having the data type and application period corresponding to the condition setting information in the module management table (Yes in step S16), the version of the record searched in step S16 is determined from the data information version. It is determined whether or not it is larger (step S17).

If it is determined that the version of the record searched in step S16 is larger than the version of the data information (Yes in step S17), the module determination unit 12 may process even if the data and the module versions are different. A screen prompting selection of whether or not to be displayed is displayed on the display unit 4, and an input by the operator's operation of the input unit 2 is received, and it is determined whether or not the received input is an instruction to process (step S <b> 17-1). ). Then, if it is determined that the instruction not to process (step S17-1 No), the module determination section 12 searches the module management table, the data type matches the data type of information conditions setting In addition, it is determined whether there is a record whose version corresponds to the version of the data information (step S18).

  When the module management table is searched and it is determined that “a record whose data type matches the data type of the condition setting information and whose version corresponds to the version of the data information” exists (Yes in step S18). Then, the module stored in the record is determined as a module to be activated, and the determined module is notified to the module cooperation unit 14 together with information on condition setting of the processing data (step S19).

  When the module management table is searched and it is determined that there is no “record whose data type matches the data type of the condition setting information and whose version corresponds to the version of the data information” (No in step S18). The module determination unit 12 displays a screen indicating an error on the display unit 4 (step S22).

  On the other hand, if it is determined in step S17 that the version of the record searched in step S16 is not greater than the version of the data information (No in step S17), the module determination unit 12 further determines the version of the data information. It is determined whether the versions of the records searched in step S16 are equal (step S20). If it is determined that the version of the data information and the version of the record searched in step S16 are equal (Yes in step S20), the module stored in the record is determined as a module to be activated, and the determined module is processed. The module cooperation unit 14 is notified together with the data condition setting information (step S21).

  If it is determined in step S20 that the version of the data information is not equal to the version of the record searched in step S16 (No in step S20), the process proceeds to step S22. If it is determined in step S17-1 that the received input is an instruction to process (Yes in step S17-1), the module stored in the record searched in step S16 is determined as the module to be activated. Then, the determined module is notified to the module cooperation unit 14 together with the process data condition setting information (step S21).

  Subsequently, the reflection process (update propagation process) to the related data performed in step S5 of FIG. 5 will be described. In this embodiment, when data on a database is updated by module processing, data to be propagated is managed using an update propagation management table so that related data can be propagated and updated. FIG. 9 is a diagram illustrating an example of the update propagation management table. As shown in FIG. 9, the update transmission management table of the present embodiment should be updated by spreading the data type, update version (updated data version), and transmission destination version (update version data). Version) and ripple processing module (name of the module that performs ripple processing from the updated version to the ripple destination version). The ripple processing module includes a program in the module program group of the storage unit 3 like other modules.

  FIG. 10 is a flowchart illustrating an example of the procedure of the update propagation process according to this embodiment. When the update propagation process is started in step S5 of FIG. 5, first, the update propagation management unit 13 searches the update propagation management table via the database management unit 20, and the type and version of the updated data is the module processing unit 30. It is determined whether there is a record that matches the information notified from (step S31). When it is determined that there is a record whose updated data type and version match the information notified from the module processing unit 30 (Yes in step S31), the update transmission management unit 13 performs the transmission processing of all the matching records. The module is read out and selected as a ripple processing module to be activated (step S32). However, the already selected ripple processing module is excluded.

  Then, the program of the ripple processing module selected in step S32 is read from the module program group, the ripple processing module is activated, and the ripple processing module performs the ripple processing (step S33). At this time, if there are a plurality of selected ripple processing modules, this operation is sequentially repeated to process all the selected ripple processing modules. Then, the data generated by the spreading process is set as newly updated data (step S34), the process returns to step S31, and the processes from step S31 to step S34 are repeated.

  If it is determined in step S31 that there is no record whose updated data type and version match the information notified from the module processing unit 30 (No in step S31), the process ends.

In the above description, the report creation process, which is an example of a financial application, has been explained. However, this application is implemented for other applications such as a financial application, a tax application other than the report creation process, a sales purchase management application, and a salary management application. When the example data management process is applied, the condition setting information in step S1 is changed to an input item necessary for the process of the application except for the target period. Furthermore, depending on the application, a date input as data may be set as the target period, or a date at the time of execution may be used as the target period. Then, the processing of each module may be changed to that of the application, and each data may be changed to data used by the application. For other applications, the version of the module to be activated can be automatically determined by comparing the input target period and the application period ( module management table ) of each module, as in the report creation process.

As described above, in this embodiment, based on the correspondence between the application period stored in the module management table and the module to be activated, the module corresponding to the input target period (the process data target period) is activated. did. Therefore, the module can be activated with a simple operation without the operator being aware of the version. In addition, it is possible to process a plurality of versions of modules without enlarging the modules.

  FIG. 11 is a block diagram illustrating a functional configuration example of the module management apparatus according to the second embodiment of the present invention. The module management processing unit 10a of the present embodiment is a control unit of the module management apparatus of the present embodiment and is included in the control unit 1. The configuration example of the computer system in which the module management apparatus of this embodiment operates is the same as that of FIG. 1 described in the first embodiment. The module management processing unit 10a of the present embodiment adds a data information acquisition processing unit 15, an application period management unit 16, and a conversion management unit 17 to the module management processing unit 10 of the first embodiment, and performs module management processing of the first embodiment. Although the module determination unit 12 of the unit 10 is deleted, the rest is the same as the module management processing unit 10 of the first embodiment. The module management processing unit 10a according to the present embodiment operates using the database management unit 20, the input unit 2, the storage unit 3, the display unit 4, and the module processing unit 30 as in the first embodiment. To do. Components having the same functions as those of the first embodiment are denoted by the same reference numerals and description thereof is omitted. Further, the data information acquisition processing unit 15, the application period management unit 16, and the conversion management unit 17 are included in the control unit 1 of FIG.

  The module processing unit 30 of this embodiment is the same as that of the first embodiment, and is a control means for applications such as finance / accounting, tax, sales purchase management, and salary management. The database in the storage unit 3 of this embodiment is the same as that of the first embodiment.

  Subsequently, the overall operation procedure of the module management process of this embodiment will be described. FIG. 12 is a flowchart illustrating an example of the procedure of the overall operation of the module management process according to this embodiment. As in the first embodiment, the module management processing of this embodiment is performed by the operator operating the input unit 2 when the operator performs processing such as finance / accounting, tax, sales purchase management, and salary management. It is activated. Here, the case where a report preparation process is performed is demonstrated as an example. First, the processing data selection unit 11 displays a screen for prompting input of condition settings on the display unit 4.

  At this time, the items that require input include the type of data (corporate tax return, consumption tax return, etc.), classification (final return, intermediate return, etc.), and target period (target period of the data to be created). And In addition, a list of existing created data may be displayed so that the operator can select data to be edited from the list, and input of data type, category, and target period may be omitted.

  The processing data selection unit 11 accepts an input of condition setting including the type, classification, and target period of data by the operator's operation of the input unit 2, and sets the creation classification based on the condition setting as in step S1 of the first embodiment. The condition setting information and the creation classification are output to the data information acquisition processing unit 15 (step S1a). Then, the data information acquisition processing unit 15 requests the application period management unit 16 to acquire data information about the processing data. If necessary, the application period management unit 16 requests the conversion management unit 17 to convert various data to be used (step S6). Specific processing for acquiring data information will be described later.

  The application period management unit 16 determines the module and version to be activated based on the condition setting information and the data information by the application period management process, notifies the data information acquisition processing unit 15, and the data information acquisition processing unit 15 The module to be activated is notified to the module cooperation unit 14 together with the process data condition setting information (step S2a). Here, in the present embodiment, it is assumed that a module for executing the report creation process is generated for each data type as in the first embodiment. Specific processing of the application period management unit 16 in step S2a will be described later.

  And the module cooperation part 14 reads the program corresponding to the notified module from the module program group of the memory | storage part 3, and stores it in the predetermined | prescribed place of the memory | storage part 3 similarly to step S3 of Example 1, and module processing The unit 30 starts to operate according to the stored program (step S3). Then, the module processing unit 30 designates the type of various data (for example, subject master, accounting data, etc.) used for creating the report, and obtains data information of the data (step S7). At this time, even when the processing data is newly created, when the created data is created by referring to the created data, the data information is also acquired for the reference target data received by the operation of the input unit 2 by the operator. Further, when only a specific version of data is referred to, the version is fixed to the data information acquisition processing unit 15 so that the information can be acquired with a fixed version. Whether information is acquired with a fixed version is determined in advance for each type of data, and the module processing unit 30 holds the information.

  Hereinafter, the various data to be used and the data to be referred to are collectively referred to as data to be referred to. In step S7, specifically, the module processing unit 30 sets the creation category to “reference”, and the data type, category, target period, and version of the data to be referred to are fixed together with the creation category. Outputs the version to the data information acquisition processing unit 15 to acquire the data information of the data to be referred to. The data information acquisition process will be described later. In step S7, data information is acquired by selecting whether or not to fix the version. However, if data information is acquired in step S6, the version is not fixed. When acquiring data information, the column of the version output to the data information acquisition processing unit 15 is not necessary (becomes blank).

  When referring to past data, the module processing unit 30 reads the data to be referred to via the database management unit 20 based on the data information acquired in step S7, and inputs the operator based on the data to be referenced. A predetermined report is created according to the editing by the operation of the unit 2 (step S4a). If past data is not referred to, various data are read out via the database management unit 20, and a predetermined report is created according to information input by the operator (step S4a). The module processing unit 30 stores the created report data in the database via the database management unit 20 (step S4a).

  When the report data is updated (created) in step S4a, the module processing unit 30 updates the updated data type (for example, subject master, report data, accounting data, etc.) and version. 13 and the update propagation management unit 13 reflects the update on the related data (step S5). The update reflection process in step S5 is the same as step S5 in the first embodiment. Then, the module management process of the present embodiment ends.

  Subsequently, the data information acquisition process of the process data described in step S6 of FIG. 12 will be described. FIG. 13 is a flowchart illustrating an example of a processing procedure of data information acquisition processing. The data information acquisition process is performed in two scenes: acquisition of process data information in step S6 and acquisition of data information of data referenced by each module in step S7. In step S6 and step S7, the creation classification (new, edit, reference) is passed to the data information acquisition processing unit 15 so that the data information acquisition processing unit 15 can determine which processing is performed.

  In step S6 or step S7, the data information acquisition processing unit 15 displays the creation category, the type of data, the category, the target period, and the specified version (a fixed version if the version is fixed, and a blank if the version is not fixed). Upon receipt, it is determined whether or not processing data information is acquired (creation category is new or edited) based on the creation category (step S41). In the case of processing data information acquisition (Yes in step S41), the data information acquisition processing unit 15 passes the data type, classification, target period, and creation classification of the processing data to the application period management unit 16, and applies the application period. The management process is requested to start (step S42). Although processing of the application period management unit 16 will be described later, it is processing for acquiring version information that conforms to the conditions of data (in this case, processing data).

  When version information (information on the version to be processed is processed) is obtained by the application period management process of the application period management unit 16 (step S42: acquisition of version information), the data information acquisition processing unit 15 performs module cooperation. The module 14 is requested to start the module corresponding to the version information (step S43). The data information acquisition processing unit 15 notifies the module processing unit 30 of the version information as data information (step S51). If version information is not obtained in step S42 (no target in step S42), the module to be activated cannot be selected and the module cannot be activated, and the module management process is terminated (step S44).

  On the other hand, if it is determined in step S41 that the processing data is not acquired (refer to the creation category) (No in step S41), the data information acquisition processing unit 15 further performs data acquisition with a fixed version (specified). It is determined whether or not the version is not blank (step S45). If it is determined that the data acquisition is not fixed version (No in step S45), the data information acquisition processing unit 15 receives the data type, classification, and target period from the data management table via the database management unit 20. Data corresponding to is searched (step S46).

  If there is corresponding data as a result of the search (step S46: applicable), the searched record is read, and the target period received as the target period is set for data without the concept of the period (for example, subject master). (Step S47). Then, the read information (data type, category, target period, version) and creation category are passed to the application period management unit 16 to request an application period management process corresponding to the data to be referred to, and a processing result is acquired. (Step S48). When the version information is obtained by the application period management process (step S48, version information acquisition), the process proceeds to step S51, and the version information is notified to the module processing unit 30.

When version information is not obtained in step S48 (step S48 no target)
In this case, the module processing unit 30 is notified that the information of the data to be referenced cannot be obtained, and the data information acquisition process is terminated (step S50).

  If it is determined in step S45 that the data acquisition is performed with a fixed version (Yes in step S45), the conversion management unit 17 sets the specified version and the data type, category, and target period of the data to be referred to. And requests data management processing (step S49). The data management process will be described later.

  If the data management process in step S49 has acquired the information of the data to be referred to (step S49 information acquisition), the process proceeds to step S51, the data information is notified to the module processing unit 30, and the data information acquisition process is performed. The process ends (step S51). In step S49, when the information of the data to be referred cannot be acquired (step S49, no target), the process proceeds to step S50.

  Next, the application period management process described in steps S42 and S48 in FIG. 13 (corresponding to the process of the application period management unit 16 described in step S2a in FIG. 12) will be described. FIG. 14 is a flowchart illustrating an example of the procedure of an application period management process according to this embodiment. First, the application period management unit 16 determines whether or not application period management processing for new data has been created based on the creation category (step S61).

  When it is determined that the creation category is new (Yes in step S61), the application period management unit 16 stores the data corresponding to the specified data information (information on the condition setting input to the application period management unit 16). It is determined whether or not a record having a type and an application period exists in the application period management table (step S62). FIG. 15 is a diagram illustrating an example of an application period management table according to the present embodiment. As shown in FIG. 15, the application period management table of the present embodiment includes a version (Version), data type, application period (showing the end date of the process target period as a range), and module (module name). ing. The module (module name) may be any information as long as it can distinguish the module to be activated, such as a name and an identifier. FIG. 15 includes a remarks column, but the remarks column is not essential.

  When it is determined that a record having the data type and application period corresponding to the specified data information exists in the application period management table (Yes in step S62), the application period management unit 16 stores the information of the application period record. The data information acquisition processing unit 15 is notified (step S63). At this time, if there are a plurality of corresponding records, the maximum version may be notified, or the information of the plurality of records may be displayed on the display unit 4 to be selected by the operator. It may be.

  When it is determined that the record having the data type and application period corresponding to the specified data information does not exist in the application period management table (No in step S62), the application period management unit 16 records the record in the application period management table. Among them, the information of the record having the maximum version corresponding to the designated data type is notified to the data information acquisition processing unit 15 (step S64).

  If it is determined in step S61 that the creation category is not new (No in step S61), the application period management unit 16 determines the data type and data corresponding to the specified data information (data type, category, target period). It is determined whether or not a record having an application period exists in the application period management table (step S65). When it is determined that a record having the data type and application period corresponding to the specified data information exists in the application period management table (Yes in step S65), the application period management unit 16 determines the version of the specified data information. Thus, it is determined whether or not the version of the corresponding record in the application period management table is larger (step S66).

  If it is determined that the version of the corresponding record in the application period management table is greater than the version of the specified data information (Yes in step S66), the application period management unit 16 is designated by the conversion management unit 17. The data information and the version of the corresponding record in the application period management table are notified, the data management processing is requested to the conversion management unit 17, and the processing result is received (step S67). If the data management processing result of the conversion management unit 17 is a result of no target data (step S67, no target data), the application period management unit 16 corresponds to the data type and version of the specified data information. It is determined whether or not the record to be present exists in the application period management table (step S68).

  When it is determined that the record corresponding to the data type and version of the specified data information exists in the application period management table (Yes in step S68), the application period management unit 16 converts the information of the corresponding record to the version information. Is notified to the data information acquisition processing unit 15 and the application period management process is terminated (step S69). When it is determined that the record corresponding to the data type and version of the specified data information does not exist in the application period management table (No in step S68), the application period management unit 16 indicates that there is no target application period information. Is notified to the data information acquisition processing unit 15 and the application period management process is terminated (step S70).

If no record having the data type and the application period corresponding to the designated data information exists in the application period management table (No in step S65), the process proceeds to step S68.

  If it is determined in step S66 that the version of the corresponding record in the application period management table is not larger than the version of the specified data information (No in step S66), the application period management unit 16 is designated. It is further determined whether or not the version of the data information is equal to the version of the corresponding record in the application period management table (step S71). If it is determined that the version of the specified data information is equal to the version of the corresponding record in the application period management table (Yes in step S71), the data type and the data type of the specified data information are determined from the application period management table. The record corresponding to the target period is searched, the information of the searched record is notified to the data information acquisition processing unit 15 as version information, and the application period management process is terminated (step S72).

  If it is determined that the version of the specified data information is not equal to the version of the corresponding record in the application period management table (No in step S71), the data information acquisition processing unit 15 is notified that there is no target application period information. Then, the application period management process ends (step S73). If the result of the data management process is obtained in step S67, the application period management unit 16 notifies the data information acquisition processing unit 15 of the obtained process result as version information, and ends the application period management process. (Step S72).

  Next, the data management process of this embodiment will be described. FIG. 16 is a flowchart illustrating an example of a procedure of data management processing according to this embodiment. The data management process is a process executed in step S49 of FIG. 13 and step S67 of FIG. 14. The data management process outputs information on the data to be subjected to the data management process, and if the data needs to be converted, the data is updated. This is a process of converting to a version and outputting information on the converted data. First, the conversion management unit 17 searches the data management table via the database management unit 20 and matches the data type, category, target period, and version notified from the data information acquisition processing unit 15 or the application period management unit 16. It is determined whether there is data to be processed (step S81). If matching data is obtained as a result of the search (step S81 Yes), the data management table information related to the data is notified to the data information acquisition processing unit 15 or the application period management unit 16 (execution of step S49). In this case, the data information acquisition processing unit 15 is notified, and in the case of execution of step S67, the application period management unit 16 is notified: step S82).

  If no matching data is obtained as a result of the search in step S81 (No in step S81), the conversion management unit 17 determines whether or not to perform the process with a fixed version (step S83). Specifically, when it is executed in step S49 of FIG. 13, it is determined that the process is performed with the version fixed. If it is executed in step S67 of FIG. 14, it is determined that the process is not performed with the version fixed.

  If it is determined in step S83 that the process is not performed with the version fixed (No in step S83), the data management table is searched via the database management unit 20 and matches the notified data type, category, and target period. It is determined whether or not there is data with an older version (step S84). If it is determined that there is an old version of the data (Yes in step S84), the conversion management table is searched from the old version to the notified version (step S85).

  FIG. 17 is a diagram illustrating an example of the conversion management table of the present embodiment. As shown in FIG. 17, the conversion management table of this embodiment has a type (= data type), a conversion source version (Version), a conversion destination version, and a method (whether conversion is performed automatically or an operator gives an instruction. Or conversion module (module for performing conversion). Note that the items of the method may not be included in the conversion management table when the conversion may always be automatically performed or when the instruction from the operator is always requested. Also, for example, if a major version difference is automatically converted and a minor version difference is not converted, a rule is determined so that the conversion is performed by referring to the rule. You may make it do. In addition, FIG. 17 shows a case where the conversion source version and the conversion destination version are continuous. It may be included in the conversion management table. The conversion module is stored in the storage unit 3 as other modules in the same manner as a module program group.

  In step S85, the conversion management table is searched for whether there is a conversion step from the old version searched in step S84 to the notified version (step S85). Then, it is determined whether or not conversion from the old version searched in step S84 to the notified version is possible (step S86). Specifically, if the data type, the conversion source version, and the conversion destination version have records that respectively match the notified type (= data type), the old version searched in step S84, and the notified version, The conversion module of the record becomes a conversion step as it is and can be converted. If the type, conversion source version, and conversion destination version do not match all of the notified type, the old version searched in step S84, and the notified version, the conversion desired by performing stepwise conversion It is determined whether or not it is possible.

For example, assume that the old version is version 1 and the notified version is version 3. At this time, if the record whose type matches the notified type includes a record of conversion from version 1 to version 2 and conversion from version 2 to version 3, the conversion is performed by executing in two steps. These two steps become conversion steps.

  Next, the conversion management unit 17 refers to the conversion management table method corresponding to the converted conversion step, and determines whether or not there is a conversion step whose method is “instruction” (step S87). When it is determined that there is a conversion step whose method is “instruction” (Yes in step S87), the conversion management unit 17 displays a screen for prompting selection on whether or not to perform the conversion process on the display unit 4, The input by the operator's operation of the input unit 2 is accepted (step S88). Then, the conversion management unit 17 determines whether or not an instruction to perform the conversion process has been input (step S89).

  If it is determined that an instruction to perform the conversion process has been input (Yes in step S89), the module cooperation unit 14 is sequentially requested to start the conversion process in accordance with the conversion step searched in step S85, and is created after the conversion process. Data is registered in the data management table (step S90). Then, the information registered in the data management table is notified to the data information acquisition processing unit 15 or the application period management unit 16 (in the case of execution of step S49, to the data information acquisition processing unit 15, in the case of execution of step S67). Each is notified to the application period management part 16: step S82).

  If it is determined in step S87 that there is no conversion step whose method is “instruction” (No in step S87), the process proceeds to step S90. In step S83, when the process is executed in step S49 in FIG. 13 (processing is performed with a fixed version) (Yes in step S83), the data information acquisition processing unit 15 is notified that the target data does not exist (step S83). S91).

  If it is determined in step S84 that there is no old version data (No in step S84), if it is determined in step S86 that conversion from the old version to the notified version is not possible (step S86 No), conversion is performed in step S89. If it is determined that an instruction not to perform processing has been input (No in step S89), the process proceeds to step S91, and the data information acquisition processing unit 15 or the application period management unit 16 is notified that the target data does not exist (step S91). In the case of execution of S49, the data information acquisition processing unit 15 is notified, and in the case of execution of step S67, the application period management unit 16 is notified).

  In the above description, the report creation process has been described. However, when the data management process of this embodiment is applied, such as a financial application, a tax application other than the report creation process, a sales purchase management application, and a salary management application. In step S1a, the condition setting information is changed to an input item necessary for processing of the application except for the target period. Furthermore, depending on the application, a date input as data may be set as the target period, or a date at the time of execution may be used as the target period. Then, the processing of each module may be changed to that of the application, and each data may be changed to data used by the application. For other applications, the version of the module to be activated can be automatically determined by comparing the input target period and the application period (application period management table) of each module, as in the report creation process. . Further, the conversion process can be similarly performed by comparing the version of the data to be referenced and the data to be edited with the application period.

  As described above, in this embodiment, the module corresponding to the input target period (the target period of the processing data) is started based on the correspondence between the application period stored in the application period management table and the module to be started. I made it. In addition, when data that has been created is read and processed, the read data can be automatically converted to a version corresponding to the application period management table. Therefore, the module can be activated with a simple operation without the operator being aware of the version. Further, it is possible to realize processing of a plurality of versions of modules without enlarging the modules, and to correctly maintain the consistency of data created by a plurality of types of modules.

  FIG. 18 is a diagram illustrating an example of an application period management table according to the third embodiment of the present invention. The configuration of the module management apparatus of this embodiment is the same as that of the first embodiment. In the first embodiment and the second embodiment, only the end date of the target period is managed as the application period of the application period management table, but in this embodiment, the start side and end of the target period are shown in FIG. To manage both sides.

  The applicable fiscal years to which the laws and regulations are actually applied are not only “applicable from the fiscal year ended after XX month XX in XX”, but also “applied from the fiscal year beginning after XX month XX in XX” or “XX There are various cases such as “Applicable to the fiscal year including the year XX month XX day”. The business year is usually one year, but it may be less than one year due to a change in the settlement date. In the first embodiment, as a representative example, the definition of “applicable from the end of the XX year, XX month, XX day and later” can be dealt with. By managing this, it is possible to flexibly handle various cases.

  FIG. 19 is a diagram illustrating another example of the application period management table. FIG. 18 shows an example corresponding to a request to start after 18.5.1. The application period (start side) of version 1 in FIG. 18 is up to 18.4.30, and the application period (start side) of version 2 starts from 18.5.1. Version 2 of this corresponds to this requirement. On the other hand, FIG. 19 corresponds to the case where there is a law that is required to be applied in the year including 18.5.1. Version 1 in the first row includes 18.5.1 on both the start side and the end side. Managed. In this way, it is possible to respond to requests for various application periods so that the start side and the end side are managed separately. When processing with reference to the application period management table is performed, it is determined that the start date of the processing target data is within the application period of the start side and the end date is within the application period of the end side. . Similarly, both the start side and the end side are managed for the application period of the module management table.

  In this example, the start and end application periods are stored separately in the same table, but the start and end sides are stored in separate tables or managed as a single character string. The management method is not limited to this, and any method may be used as long as the application period of the start side and the end side can be managed.

  In addition, transitional measures may be provided for the application of laws and regulations. If a transitional measure is provided, it can be applied before the original application period (hereinafter referred to as early application), or it can be applied even after the original application period has ended (hereinafter referred to as extended application). There is a case. FIG. 20 is a diagram illustrating an example of an application period management table corresponding to such a transitional measure. As shown in FIG. 20, in addition to the application period (end side), by managing the early application period and the extended application period together, it is possible to cope with a case where a transitional measure is provided. In the example of FIG. 20, the application period for 2006 is until the end of March 31, 2007, but it can be extended until the end of April 2007. In addition, for the fiscal year 2007, the application period after the end of April 1st, 2007 can be applied early from the fiscal year ended March 2007.

  Further, in the example of FIG. 20, the start side and the end side may be managed separately as in FIGS. 18 and 19. FIG. 21 is a diagram illustrating an example of an application period management table that individually manages a start side and an end side corresponding to a transitional measure.

  In this way, when early application or extended application is taken into consideration, there may be a plurality of modules that can be applied when creating data for a certain period. In such a case, the module determination and application period management processing described in the first embodiment can select the module to be used by the operator when searching for the application period management table or the application period of the module management table. do it. FIG. 22 is an example of a module selection screen displayed on the display unit 4 when there are a plurality of applicable modules. In the case of the module determination process, the module determination unit 12 displays this screen in the case of the application period management process, and receives the selection by the operation of the input unit 2 of the operator. Process. In the example of FIG. 22, the case where the module of the regular application period of 2007 and the module of the early application correspond is shown. Here, the selected module is indicated by black circles and diagonal lines, and the operator This is an example in which a module having a regular application period of 2007 is selected by operating the input unit 2.

  On the other hand, after filing for early application, return to the law of the previous regular application period, or conversely, use the extended application of the old law after finishing the extended application and filing in accordance with the new law. In principle, it cannot be declared. Therefore, when referring to existing data, the ID (Indetifier) of the data referred to in the reference data management table is registered. The reference data management table is one of the management table groups on the database. FIG. 23 is a diagram illustrating an example of the reference data management table. In this way, when existing data is referenced when creating certain data, the ID of the referenced data is registered in the reference destination data ID, and the ID of the data to be created is registered in the reference source data. deep.

  The data ID is a value that is uniquely assigned to each registered data, and is a value that is assigned when data is newly created and is managed by the data management table. In the present embodiment, this reference data management is performed when searching for a record whose data type and application period coincide with the data to be read from the data management table in order to read out the data to be referenced for the process of creating certain data. Restricts the version of data to be referenced using a table. In this way, by restricting the data to be referred to, it is possible to prevent the old law from being applied by mistake.

  FIG. 24 is a flowchart illustrating an example of a procedure for version restriction processing. The data information acquisition processing unit 15 performs this version of restriction processing before step S41 of the data information acquisition processing. The version restriction process is not limited to this, and may be performed at any timing as long as the information of the data to be referenced or the data to be edited is not acquired.

  First, the data information acquisition processing unit 15 searches the data management table via the database management unit 20, and extracts the data ID of the data whose processing data and data type are the same and whose target period is old (step S101). When the corresponding data ID is extracted (corresponding to step S101), the reference data management table is searched, and the record in which the data ID extracted in step S101 matches the reference source data ID is searched and searched. In step S102, the record is extracted.

  Next, the data information acquisition processing unit 15 searches the data management table via the database management unit 20 and extracts the data ID of the data whose data type is the same as the data to be referred to (step S103). When the corresponding data ID is extracted (corresponding to step S103), the reference data ID that matches the data ID extracted in step S103 is extracted from the record extracted in step S102 (step S104).

  When the reference destination data ID is extracted in step S104 (corresponding to step S104), the data management table is searched to obtain the maximum version of the data corresponding to the extracted reference destination data ID (step S104). S105). Then, a read restriction is set after the acquired version (step S106). As the read restriction information, for example, read restriction information is stored in the storage unit 3, and when the data information of the data to be referred to is acquired in the data information acquisition process, the read restriction information is referred to. Data that has restrictions is not acquired as information of data to be referenced.

  If it is determined in step S101 that the data type is the same as the process data and the target period has not been extracted (not applicable in step S101), the process is terminated without limiting the version (step S107). If no record having a reference source ID is extracted in step S102 (not applicable to step S102), or if a data ID is not extracted in step S103 (not applicable to step S103), a reference destination data ID is determined in step S104. If no is extracted (not applicable in step S104), the process proceeds to step S107 in the same manner. Other operations of the present embodiment are the same as those of the first or second embodiment.

  In addition, if the version is constrained, it cannot be created in a simulation, so that a warning message may be displayed instead of being automatically constrained.

  As described above, in this embodiment, both the start side and the end side of the application period can be set individually, and the application period can be set in consideration of the transitional measure. For this reason, business processing reflecting the transitional measure can be performed. In this embodiment, the version of the data to be referred to can be further restricted. For this reason, it is possible to prevent accidental application of old regulations.

  FIG. 25 is a block diagram illustrating a functional configuration example of the module management apparatus according to the present embodiment. In the first embodiment, one computer system performs module management processing. However, in this embodiment, module management processing is performed in a client and server system. The client computer system has the same configuration as that shown in FIG. The server computer system includes a control unit 1a, a storage unit 3a, and a communication unit 5a having the same functions as the control unit 1, the storage unit 3, and the communication unit 5 of FIG.

  In this embodiment, the server includes a database, and the server includes a database management unit 20a instead of the database management unit 20 of the first embodiment. The client is the same as the computer system of the first embodiment except that the database management unit 20 is deleted from the control unit 1 of the first embodiment and the database is deleted from the storage unit 3.

  In the present embodiment, the processing performed through the database management unit 20 in the first embodiment is performed through the communication unit 5, the communication unit 5a of the server, and the database management unit 20a. Same as 1.

  In FIG. 25, one client and one server are shown. However, the present invention is not limited to this, and a system having a plurality of clients may be used. FIG. 26 is a diagram illustrating a configuration example of a system when a plurality of clients are provided. As shown in FIG. 26, the server 41, the clients 42-1 to 42-3, and the clients 43-1 and 43-2 are connected via a LAN (Local Area Network) 50 and the Internet 60. Each of the clients 42-1 to 42-3 and the clients 43-1 and 43-2 has the same configuration as the client shown in FIG. The server 41 has the same configuration as the server shown in FIG. Then, module management processing can be executed from each client.

  Also, the server may have a distributed server configuration. FIG. 27 is a diagram illustrating a configuration example of a system in the case of a distributed server. In the system of FIG. 27, each distributed server has the same database, thereby enhancing durability. Each of the servers 41-1 and 41-2 has the same configuration as that of the server of FIG. 25, and the component having the same function as that of FIG. 41-2 is assigned branch number 2. Further, the present invention is not limited to this, and the data stored in the distributed server may be distributed to distribute the load.

  In the present embodiment, the client includes the module management processing unit 10 described in the first embodiment. However, the client includes the module management processing unit 10a described in the second embodiment. The processing performed via the management unit 20 may be performed via the communication unit 5, the server communication unit 5a, and the database management unit 20a.

  As described above, in this embodiment, the module management process is executed in the client server system. Thereby, even when a large number of users perform business processing using the same data, the database can be centrally managed.

  As described above, the module management method, the module management device, the module management system, and the module management program according to the present invention are useful for a business processing system, and particularly for a business system in which a processing method is updated every specific period. Is suitable.

1 is a diagram illustrating a configuration example of a computer system that has a function as a module management apparatus for realizing a module management method according to a first embodiment and can execute a module management program according to the first embodiment of the present invention. FIG. 3 is a block diagram illustrating a functional configuration example of the module management apparatus according to the first embodiment. It is a figure which shows an example of a subject master. It is a figure which shows an example of salary data. 3 is a flowchart illustrating an example of a procedure of overall operation of module management processing according to the first exemplary embodiment. It is a figure which shows an example of a data management table. It is a flowchart which shows an example of the procedure of the process of module determination. It is a figure which shows an example of a module management table. It is a figure which shows an example of an update propagation management table. It is a flowchart which shows an example of the procedure of an update propagation process. It is a block diagram which shows the function structural example of the module management apparatus of Example 2. FIG. 10 is a flowchart illustrating an example of a procedure of overall operation of module management processing according to the second exemplary embodiment. It is a flowchart which shows an example of the process sequence of a data information acquisition process. It is a flowchart which shows an example of the process sequence of an application period management process. It is a figure which shows an example of an application period management table. It is a flowchart which shows an example of the procedure of a data management process. It is a figure which shows an example of a conversion management table. It is a figure which shows an example of the application period management table of Example 3. FIG. It is a figure which shows another example of an application period management table. It is a figure which shows an example of the application period management table corresponding to a transitional measure. It is a figure which shows an example of the application period management table which manages separately the start side and end side corresponding to a transitional measure. It is a figure which shows the example of the selection screen of the module displayed on a display part, when multiple modules which can be applied exist. It is a figure which shows an example of a reference data management table. It is a flowchart which shows an example of the procedure of a version restriction process. It is a block diagram which shows the function structural example of the module management apparatus of Example 3. FIG. It is a figure which shows the structural example of the system at the time of using multiple clients. It is a figure which shows the structural example of the system at the time of setting it as a distributed server.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1, 1a Control part 2 Input part 3, 3a Storage part 4 Display part 5, 5a, 5a-1, 5a-2 Communication part 6 Printing part 7 System bus 10, 10a Module management process part 11 Process data selection part 12 Module determination Unit 13 Update transmission management unit 14 Module cooperation unit 15 Data information acquisition processing unit 16 Application period management unit 17 Conversion management unit 20, 20a, 20a-1, 20a-2 Database management unit 30 Module processing unit 41, 41-1, 41 -2 server 42-1 to 42-3, 43-1, 43-2 client 50 LAN
60 Internet

Claims (29)

A different modules of application period determined for each regulations, a plurality of modules to create or update a processing target data is data to be processed, the module management method in the business processing system comprising a business application with,
Processed data selection unit, and a condition setting step of the process period representing a period to be the type and processing of the processing target data to acquire including conditions setting information,
The module determination unit reads out module management information stored in association with module identifiers and module versions for identifying the plurality of modules for each data type and module application period from the storage unit, A module determining step for extracting a module identifier corresponding to the condition setting information from the read module management information ;
Module linkage unit is, the module corresponding to the extracted module identifier from the storage unit, and the module activation step of activating the module,
A data management step in which the module linkage unit stores data information including a type, a processing target period, and a version of the data created by the activated module in a storage unit;
Only including,
In the module determining step,
When newly creating processing target data, the module management information in the storage unit is searched, and if there is module management information for storing the data type and application period corresponding to the condition setting information as a search result, this module management If there is no module management information that extracts the module identifier from the information and stores the data type corresponding to the condition setting information and the application period as a search result, the data type that matches the type of data to be processed is stored The module identifier is extracted from one module management information determined based on the size of the version included in the module management information obtained by the search.
If the data to be processed is not newly created, the stored data information corresponding to the condition setting information is acquired, the module management information in the storage unit is searched, and the data type and application corresponding to the condition setting information Module management information for storing a period is acquired, and a module identifier is extracted from one module management information determined based on the version size included in the acquired data information and the version size included in the acquired module management information To
A module management method. A different modules of application period determined for each regulations, a plurality of modules to create or update a processing target data is data to be processed, the module management method in the business processing system comprising a business application with,
Processed data selection unit, and a condition setting step of the process period representing a period to be the type and processing of the processing target data to acquire including conditions setting information,
The application period management unit reads out module management information stored in association with module identifiers and module versions for identifying the plurality of modules for each data type and module application period from the storage unit. A module determining step for extracting a module identifier corresponding to the condition setting information from the read module management information ;
Module linkage unit is, the module corresponding to the extracted module identifier from the storage unit, and the module activation step of activating the module,
A data management step in which the module linkage unit stores data information including a type, a processing target period, and a version of the data created by the activated module in a storage unit;
Only including,
In the module determining step,
When newly creating processing target data, the module management information in the storage unit is searched, and if there is module management information for storing the data type and application period corresponding to the condition setting information as a search result, this module management If there is no module management information that extracts the module identifier from the information and stores the data type corresponding to the condition setting information and the application period as a search result, the data type that matches the type of data to be processed is stored The module identifier is extracted from one module management information determined based on the size of the version included in the module management information obtained by the search.
If the data to be processed is not newly created, the stored data information corresponding to the condition setting information is acquired, the module management information in the storage unit is searched, and the data type and application corresponding to the condition setting information Module management information for storing a period is acquired, and a module identifier is extracted from one module management information determined based on the version size included in the acquired data information and the version size included in the acquired module management information To
A module management method. If the data to be processed is not newly created,
The application period management unit, and the first version acquisition step in which the extracted version contained in the acquired module management information as a result of searching the module management information, obtains the extracted version by the first version,
A second version acquisition step in which the application period management unit extracts a version included in stored data information corresponding to the processing target data, and acquires the extracted version as a second version;
A version comparison step in which the application period management unit compares the second version with the first version;
A notification step of notifying the conversion management unit of the module management information and the data information when the application period management unit determines that the second version is older than the first version in the version comparison step;
The conversion management unit determines whether to convert the processing target data into the first version based on the information notified in the notification step, and notifies the application period management unit of the determination result. A conversion judgment step;
When it is determined that the conversion is performed in the conversion determination step, the conversion management unit converts the processing target data into the first version; and
Further seen including,
If it is determined that the conversion is not performed in the conversion determination step, the application period management unit determines the type of data included in the data information in the module determination step based on the information notified in the notification step. And the module management information corresponding to the version is extracted, the module identifier is extracted from the module management information,
If the first version and the second version are equal as a result of the comparison in the version comparison step, the application period management unit acquires the module management information as a result of searching the module management information in the module determination step. Extracting the module identifier from
The module management method according to claim 2. In the conversion step,
Stored is conversion information in which a conversion identifier indicating an instruction as to whether or not the conversion management unit automatically performs conversion corresponding to the combination of the conversion source version and the conversion destination version is recorded for each type of processing target data. Refer to the storage unit,
When converting, if the conversion identifier corresponding to the combination of the conversion source version and the conversion destination version is a value indicating an instruction to be automatically performed, the conversion is automatically performed.
On the other hand, when the conversion is performed, if the conversion identifier corresponding to the combination of the conversion source version and the conversion destination version is not a value indicating an instruction to be automatically performed, a screen prompting the user to select whether or not to convert is displayed on the display unit. 4. The module management method according to claim 3, wherein conversion is performed when an instruction to perform conversion is received via an input unit. If the activation modules has generated or updated subject data, update-extension processing unit, the type and version of the processing target data, the type of data of interest to spread the updates for that version of the processing target data and Update update information stored in association with the version and the identifier of the propagation module that performs the propagation process is read from the storage unit, and the update corresponding to the type and version of the updated processing target data is propagated. and characterized in that extracts the identifier of the target data of the type and version of spillover module updates the type and version of data for data that has been extracted on the start spreading module the extracted The module management method according to any one of claims 1 to 4.   6. The module management method according to claim 1, wherein the application period is defined as an application period with respect to the end of the processing target period.   The module management method according to claim 1, wherein the application period is defined as both a period with respect to a start time of a process target period and a period with respect to an end time.   The module management method according to claim 1, wherein the application period is a regular application period and a transitional measure application period.   The module management method according to claim 8, wherein the transitional measure application period is an early application period and an extended application period. Version of the module associated with the application period corresponding to the processing target period when there is a plurality, of claim 8 or 9, characterized by providing a constrained version of Lud over data to reference Module management method.   The module management method according to claim 1, wherein the business processing application is a financial accounting application.   The module management method according to claim 1, wherein the business processing application is a tax application.   The module management method according to claim 1, wherein the business processing application is a sales purchase management application.   The module management method according to claim 1, wherein the business processing application is a salary management application. A different modules of application period determined for each regulations, a plurality of modules to create or update a processing target data is data to be processed, the module management unit in the business processing system including a business application with,
And processing the data selection unit processing period representing a period to be the type and processing of the processing target data to acquire including conditions setting information,
Module management information in which module identifiers for identifying the plurality of modules and module versions are stored in association with each other for each data type and module application period is read from the storage unit, and the read module management information A module determining unit for extracting a module identifier corresponding to the condition setting information from
Reads the module corresponding to the extracted module identifier from the storage unit, store and launch the module, the data generated activated the module, the data information including the type and the processing period and version, the storage unit A module linkage unit that
Equipped with a,
The module determining unit
When newly creating processing target data, the module management information in the storage unit is searched, and if there is module management information for storing the data type and application period corresponding to the condition setting information as a search result, this module management If there is no module management information that extracts the module identifier from the information and stores the data type corresponding to the condition setting information and the application period as a search result, the data type that matches the type of data to be processed is stored The module identifier is extracted from one module management information determined based on the size of the version included in the module management information obtained by the search.
If the data to be processed is not newly created, the stored data information corresponding to the condition setting information is acquired, the module management information in the storage unit is searched, and the data type and application corresponding to the condition setting information Module management information for storing a period is acquired, and a module identifier is extracted from one module management information determined based on the version size included in the acquired data information and the version size included in the acquired module management information To
A module management device. A different modules of application period determined for each regulations, a plurality of modules to create or update a processing target data is data to be processed, the module management unit in the business processing system including a business application with,
And processing the data selection unit processing period representing a period to be the type and processing of the processing target data to acquire including conditions setting information,
Module management information in which module identifiers for identifying the plurality of modules and module versions are stored in association with each other for each data type and module application period is read from the storage unit, and the read module management information An application period management unit for extracting a module identifier corresponding to the condition setting information from
Reads the module corresponding to the extracted module identifier from the storage unit, store and launch the module, the data generated activated the module, the data information including the type and the processing period and version, the storage unit A module linkage unit that
Equipped with a,
The application period management unit
When newly creating processing target data, the module management information in the storage unit is searched, and if there is module management information for storing the data type and application period corresponding to the condition setting information as a search result, this module management If there is no module management information that extracts the module identifier from the information and stores the data type corresponding to the condition setting information and the application period as a search result, the data type that matches the type of data to be processed is stored The module identifier is extracted from one module management information determined based on the size of the version included in the module management information obtained by the search.
If the data to be processed is not newly created, the stored data information corresponding to the condition setting information is acquired, the module management information in the storage unit is searched, and the data type and application corresponding to the condition setting information Module management information for storing a period is acquired, and a module identifier is extracted from one module management information determined based on the version size included in the acquired data information and the version size included in the acquired module management information To
A module management device. If the data to be processed is not newly created,
The application period management unit extracts the version included in the module management information acquired as a result of searching the module management information, acquires the extracted version as a first version,
The application period management unit extracts a version included in stored data information corresponding to the processing target data, acquires the extracted version as a second version,
When the application period management unit compares the second version with the first version and determines that the second version is older than the first version, the module management information and the data information are output.
further,
Based on the output module management information and the data information, it is determined whether or not to convert the processing target data into the first version, the determination result is notified to the application period management unit, and the conversion is performed. A conversion management unit for converting the data to be processed into the first version when it is determined to be performed ;
Bei to give a,
As a result of the determination, when it is determined that conversion is not performed, the application period management unit sets the data type and version included in the data information based on the output module management information and the data information. Search for the corresponding module management information, extract the module identifier from the module management information,
If the first version and the second version are equal as a result of the comparison, the application period management unit extracts a module identifier from module management information acquired as a result of searching for the module management information;
The module management apparatus according to claim 16. The conversion management unit
Refer to the storage unit that stores conversion information in which conversion identifiers indicating whether to perform conversion corresponding to the combination of the conversion source version and the conversion destination version automatically are recorded for each type of data to be processed . ,
When converting, if the conversion identifier corresponding to the combination of the conversion source version and the conversion destination version is a value indicating an instruction to be automatically performed, the conversion is automatically performed.
On the other hand, if the conversion identifier corresponding to the combination of the conversion source version to be converted and the conversion destination version is not a value indicating an instruction to be automatically performed, a screen prompting selection of whether or not to perform conversion is displayed on the display unit, 18. The module management apparatus according to claim 17, wherein conversion is performed when an instruction to perform conversion is received via the input unit. If the activation modules has generated or updated subject data, update-extension processing unit, the type and version of the processing target data, the type of data of interest to spread the updates for that version of the processing target data and Update update information stored in association with the version and the identifier of the propagation module that performs the propagation process is read from the storage unit, and the update corresponding to the type and version of the updated processing target data is propagated. and characterized in that extracts the identifier of the target data of the type and version of spillover module updates the type and version of data for data that has been extracted on the start spreading module the extracted The module management device according to any one of claims 15 to 18.   The module management apparatus according to claim 15, wherein the application period is defined as an application period with respect to the end of the processing target period.   The module management apparatus according to any one of claims 15 to 19, wherein the application period is defined as both a period with respect to a start time of a process target period and a period with respect to an end time.   The module management apparatus according to any one of claims 15 to 21, wherein the application period is a regular application period and a transitional measure application period.   The module management apparatus according to claim 22, wherein the transitional measure application period is an early application period and an extended application period. Version of the module associated with the application period corresponding to the processing target period when there are a plurality of claim 22 or 23 characterized by providing a restriction to the version of Lud over data to reference Module management device.   25. The module management apparatus according to claim 15, wherein the business processing application is a financial accounting application.   The module management apparatus according to any one of claims 15 to 25, wherein the business processing application is a tax application.   27. The module management apparatus according to claim 15, wherein the business processing application is a sales purchase management application.   The module management apparatus according to any one of claims 15 to 27, wherein the business processing application is a salary management application.   A module management program causing a computer to execute the module management method according to claim 1.

Images