JP3900268B2 - Form processing device for ERP package - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a form processing apparatus that outputs a form based on data stored in a storage device, and more particularly to an ERP (Enterprise Resource Planning) form processing apparatus.
[0002]
[Prior art]
The form processing apparatus is an apparatus that outputs a form based on data stored in a storage device. FIG. 8 is an explanatory diagram of an example of a conventional form creation device described in Japanese Patent Publication No. 2000-99595. This form creation device is a standard form creation device that allows electronic data exchange of created forms, and also allows the form data to be added and changed when the form is created. Device.
[0003]
FIG. 8 is a diagram showing the data flow of the form creation process executed by this form creation apparatus. When creating a form, a form format to be created is selected and a form database creation program is started. The CPU (not shown) reads the form definition 300 corresponding to the form from the storage device (not shown), further determines the reference source database 100 based on the view definition 310 included in the form definition 300, and the reference source database The necessary field (item) data is extracted from the data and converted into a simple record format, and then stored in the form database 200.
[0004]
The form definition 300 includes a view definition 310 and a layout definition 320. The view definition 310 represents information for extracting from the database 100 a field in which data necessary for this form is described corresponding to a desired form. That is, the view definition 310 is a definition of a data reference method of which table in which database is used to extract detailed data of a field, and the CPU defines a reference source defined based on the view definition 310. Necessary fields are extracted from the database 100.
[0005]
The layout definition 320 is set with information necessary for editing and outputting the layout of the print element, such as the output format and output position of the print data for each print element, and the print data attribute. If the output form is electronic data instead of a print form, the data set by the layout definition 320 is sent to the output destination.
[0006]
In the creation of data in the form database 200, first, all data that can be referred to from the reference source database 100 defined in the view definition 310 is retrieved in record units, and the retrieved data is defined as an extraction condition defined in the form definition 300 ( Whether or not the data is in accordance with the conditions specified by which table in the reference source database 100, the field from which the data is extracted, the relationship between the tables from which the data is extracted, etc. If the data is within the range satisfying the extraction condition, the data is extracted and stored as detailed data in each corresponding field of the form database 200.
[0007]
As described above, the CPU extracts necessary fields from a plurality of fields included in the records of the database 100 based on the view definition 310, and creates a form database 200 corresponding to a desired form constituted by the extracted fields. Based on the created form database 200 and the layout definition 320, the form 201 is output.
[0008]
It is necessary to consider the following when applying the above-described form creation apparatus to an ERP system. As described in the form creation device in FIG. 9 described later, data stored in the database is generally classified into master data and other disposable data (hereinafter referred to as transaction data). Both types of data are required in the processing device. In recent years, in ERP packages (business integration packages) that have been rapidly used in enterprise core business, it is common for master data of an ERP system to have a complicated data structure. The reason is that the form format required by the business processing unit such as a company or business office integrated with the business is different. Therefore, it is impossible to output a form directly from the ERP database. For this reason, when a form process is performed, a pre-process for outputting a form is required in advance, and an ERP package form processing apparatus capable of reducing the pre-processing time is required.
[0009]
FIG. 9 is a block diagram illustrating a flow of a form process using an ERP package assumed when the form creation apparatus illustrated in FIG. 8 is applied to an ERP system. The form processing apparatus in FIG. 9 (hereinafter referred to as a conventional form processing apparatus) includes an activation unit 1 that activates a form preprocessing apparatus, a form preprocessing apparatus 92 that creates form data, an ERP database 3 that stores data, A form database 94 for storing form data and a form output device 95 for outputting forms from the form database are provided. The form preprocessing device 92 includes an extraction unit 91, a conversion unit 102, a generation unit 93, and a conversion rule 104. The ERP database 3 stores master data 31 and transaction data 32. The form database 94 includes form data 90. The form output device 95 includes form output means 96.
[0010]
The extraction unit 91 receives parameter information such as an effective date from the activation unit 1, and extracts data based on the parameter information from the master data 31 and the transaction data 32. The conversion rule 104 (corresponding to the view definition in FIG. 8) defines the relationship between the data structure of the ERP database 3 and the data structure of the form database 94. Based on the conversion rule 104, the conversion unit 102 combines the master data 31 and the transaction data 32 into data suitable for form output. The generation unit 93 generates the form data 90 in the form database 94 based on the conversion result of the conversion unit 102. The form output means 96 outputs a form based on the form data 90.
[0011]
[Problems to be solved by the invention]
The above-described conventional form processing apparatus is roughly divided into two problems.
The first problem is that the processing time of the form pre-processing device depends on the data to be processed. Generally, transaction data has a much larger amount of information than master data, so that the form processing time increases as the transaction data increases.
The second problem is that the form pre-processing device required by the ERP package differs for each user (company, office, etc. in the target company). Since the form format differs for each user, the data format generated by the form pre-processing apparatus also differs for each user. For this reason, it is difficult for a package vendor to provide a general-purpose form processing apparatus.
[0012]
An object of the present invention is to provide a general-purpose form pre-processing apparatus that can reduce the processing time of the form pre-processing apparatus and can realize form output that flexibly responds to different requests for each user. There is.
[0013]
[Means for Solving the Problems]
In order to solve the above problems, in the ERP package form processing apparatus of the present invention,
When the ERP package form processing program starts, the form pre-processing apparatus extracts master data to be output to the form from the ERP database, and converts the extracted master data according to a conversion rule defined only for the master data. Generate the form master data described in the form format, store it in the ERP database as form data,
The form output device combines the form master data with the business process general data stored in the ERP database, sets the necessary data for output to the combined data, and outputs it as a form To do.
[0014]
In this way, in the form pre-processing, the general data for business processing with a large amount of information is not converted into form data, but only the master data is converted into form master data, so the pre-processing time of the form can be shortened. it can.
Data connection between the form master data and the business process general data can be made by logical connection.
[0015]
The form pre-processing apparatus has a dimension information means for holding a table of master data key information and dimension information corresponding to the key information. Can have. Conversion rules are The code that specifies the item of the master data for the form to which the master data specified by the key information corresponding to the dimension information should be written is associated with the key information of the master data. The The dimension information is information that specifies an attribute of master data specified by key information.
[0016]
The correspondence between the master data key information in this conversion rule and the code that specifies the item of the form master data can be set by arbitrarily adapting the form required by the business processing unit such as a company or office. Therefore, it is possible to provide a general-purpose form pre-processing apparatus that can flexibly respond to different requests for each user.
[0017]
The conversion rule includes an unconditional conversion rule that associates one key information of master data with one code, and a condition conversion rule that associates one key information of master data with one of the plurality of codes. The condition conversion rule can be set so that the key information of the master data and a predetermined one of the plurality of codes are associated with each other on the assumption that the conversion is performed according to a predetermined unconditional conversion rule.
[0018]
By defining the conversion conditions of the conversion rule with flexibility in this way, it is possible to realize a form output that flexibly responds to different requests for each user.
[0019]
The ERP database is The master data that was added, updated, or deleted since the last generation of the master data for forms was stored as differential data. The form pre-processing device A difference manager that manages the form master data generated last time based on the difference data and the difference data generated this time Step The form pre-processing apparatus can be configured to change the previously generated form master data based on the difference data generated this time to generate the current form master data.
[0020]
In principle, master data is data that does not change frequently. Therefore, when the form master data is changed, most of them are changed in most cases. Therefore, the form preprocessing can be simplified and the form preprocessing time can be shortened by changing the form master data based on the difference data.
[0021]
The general data for business processing can be transaction data.
[0024]
As described above, in the present invention, by using the conversion rule that defines the relationship between the master data specific to the ERP package and the form master data, the transaction data is not converted during the form pre-processing, and only the master data is the form master. Convert to data.
A system for combining the form master data and the transaction data when the form is output is provided. With this mechanism, it is possible to reduce the processing time of the form pre-processing device, and as a result, it is possible to provide a general-purpose form pre-processing device, realizing a form output that can be flexibly adapted to user requests. It becomes possible to do.
[0025]
DETAILED DESCRIPTION OF THE INVENTION
The present invention intends to provide a form processing apparatus capable of outputting a form that flexibly adapts to a user's request by converting ERP master data into data suitable for the form before outputting the form. ing.
FIG. 1 is a block diagram showing the flow of form processing according to the first embodiment of the ERP package form processing apparatus of the present invention.
[0026]
The form processing apparatus of this embodiment includes an activation unit 1, a form pre-processing apparatus 2, an ERP database 3, and a form output apparatus 4.
The form pre-processing device 2 includes a master conversion unit 21, a dimension key 22, and a conversion rule 23. The dimension key 22 is information for specifying an attribute of master data specified by the master data key. The conversion rule 23 is a rule that defines the association between master data and form master data. The dimension key 22 and the conversion rule 23 will be described later with reference to FIG.
The master conversion means 21 receives parameter information such as an effective date from the activation means 1 and converts the master data 31 extracted from the ERP database 3 into form master data 32 based on the conversion rules 23. Here, “converting” means “corresponding” or “corresponding to generate corresponding data”.
[0027]
The ERP database 3 stores master data (master data of the ERP system) 31, transaction data 33, and form master data 32 generated by the master conversion means 21.
[0028]
The form output device 4 includes a data combining unit 41 and a form output unit 42.
The data combining means 41 logically combines the form master data 32 and the transaction data 33. The form output unit 42 sets information necessary for the form output for the processing result of the data combination unit 41 and outputs the form as print output or electronic data.
[0029]
FIG. 2 shows the configuration of an embodiment of the conversion rule 23. The logical data of a master data key, a dimension key, and an item (field) code of a form master data having an attribute specified by the dimension key. The correspondence and conversion conditions are shown. As shown in the figure, master data keys M1 and M2 are keys for designating master data company master data and department master data (hereinafter referred to as company master and department master respectively). These correspond to the field code 10 (in-form code number for writing the company master) and the field code 20 (in-form code number for writing the department master) of the form master data, respectively. Therefore, the master data specified by the master data keys M1 and M2 are always written in the fields specified by the code 10 and the code 20 (see the account code (FIG. 4) described later).
[0030]
The master data key M3 is a dimension key for specifying account master data (hereinafter referred to as account master). This key is a field code for writing the account master data of the form master data (see the item code in FIG. 4). Corresponding to 30, 40, 50. The form master data is given different field codes depending on the contents of the account item. The above 30, 40 and 50 are account item field codes for different business partners TP1, cost center CC1 and business partners TP2. In the following description, the business partner TP1, the cost center CC1, and the business partner TP2 are collectively referred to as business partners.
[0031]
The key M4 of the master data is a key for identifying the supplier master and the cost center master from other master data, and corresponds to the field code value that differs depending on the trading partner as described above. When M3 = 30, the trading partner field code in the form master data is the first trading partner TP1. When M3 = 40, the counterparty field code in the form master data is the cost center CC1. When M3 = 50, the trading partner field code in the form master data is the second trading partner TP2.
[0032]
In this way, FIG. 2 associates the key of the master data with the field code in the form master data. In this specification, this association rule is referred to as a conversion rule.
[0033]
Some conversion rules, such as master data keys M1 and M2, are uniquely converted into field codes in the form master data without being constrained by other conversion rules. In addition, there are some which are converted into any of a plurality of predetermined field codes, such as a master data key M3. There is also a conversion rule for converting a conversion rule for another key as a conversion condition, such as a conversion rule for the key M4 of the master data. As the conversion condition in FIG. 2, “unconditional conversion” indicates that the conversion is performed independently from the conversion rules of other keys.
In this way, the master data can be converted in advance into form master data having a data structure unique to ERP, and a form output that can be flexibly adapted to the user's request can be realized. .
[0034]
Next, the operation of this embodiment will be described.
In FIG. 1, the master conversion unit 21 receives parameter information such as an effective date from the activation unit 1, and converts the master data 31 into form master data 32 based on the dimension key 22 and the conversion rule 23. The data combining means 41 logically combines the form master data 32 and the transaction data 33. The form output means 42 outputs a form using the result of the data combining means.
[0035]
FIG. 3 is a flowchart for explaining an operation example of the master conversion means 21. FIG. 4 is a diagram showing an account form of one embodiment of form master data generated based on the conversion rule of FIG.
Referring to FIG. 3, first, an effective date or the like, which is a master data extraction condition, is acquired from the activation means 1 (step A1). The effective date consists of a start date and an end date.
Next, the master data is read for the master data created between the start date and the end date input in step A1 (steps A2 and A3). Next, a conversion process is performed on the collected data group (steps 4 and 5). The conversion process is performed by sequentially processing the master data.
[0036]
In the first loop, the first master data is targeted. Referring to the account code in FIG. 4 as an example, the target form master data is 10-20-30-TP1. That is, it is master data written in the account codes 10, 20, 30, and TP1 of FIG.
As is apparent from the conversion rule of FIG. 2, the keys of the master data converted into the field codes 10 and 20 of the form master data are M1 and M2, and the master data converted into the field code 30 of the form master data The key of the master data converted to the field code TP1 of the form master data at that time is M4. Therefore, M1, M2, M3, and M4 are set as master data keys (step A2), and the master data designated by these keys is set as a conversion target.
[0037]
Referring to FIG. 2, the dimension keys corresponding to the master data keys M1, M2, M3, and M4 are a company master, a department master, a subject master, and a supplier master. Therefore, the master conversion means 21 collects data using the company master, department master, subject master, and supplier master as dimension keys as data for the account code 10-20-30-TP1 (step A3). Next, the master data is converted based on the conversion rule shown in FIG. 2 (step A4). Next, based on the converted master data, data in the first row of FIG. 4 is generated (step A5).
[0038]
The data generation in step A5 is performed as follows. Based on the conversion rule shown in FIG. 2, the key M1 of the master data is assigned to the company code of the form master data to be “10”. Therefore, the code “10” in FIG. 4 is the code of the key M1 of the master data in the form master data. The company name is acquired from the company master and is designated as “head office”.
Similarly, the key M2 of the master data is assigned to the department code and is set to “20”. The department name is acquired from the department master data and is referred to as “sales department”. The key M3 of the master data is assigned to the subject code and is set to “30”. The course name is obtained from the course master data and is called “Accounts receivable”. Since the key M3 is 30, the master data key M4 is assigned to the first supplier code and is set to “TP1”. The supplier name is acquired from the supplier master and is assumed to be “customer 1”.
[0039]
Since the process on the first line of the account in FIG. 4 is completed, it is determined whether or not there is master data to be executed next for the pre-form process (step A6). In this embodiment, since there is a process on the second line, the loop enters the second time.
[0040]
In the second loop, since the target data is 10-20-50-TP2 and the master data key M3 is 50, the master data keys M1, M2, M3, and M4 are converted. Data related to 10-20-50-TP2 is collected (step A3), and data on the second line in FIG. 4 is generated based on the conversion rule (steps A4 and A5).
[0041]
In the data generation in step A5, the company code 10 and the department code 20 are the same as in the case of the account code 10-20-30-TP1 described above. However, the key M3 of the master data is assigned to the course code as “50”, and the course name is acquired from the course master data as “accrued”. Since the key M3 is 50, the key M4 of the master data is assigned to the second customer code and is set to “TP2”. The supplier name is acquired from the supplier master, and is set to “supplier 2”.
[0042]
In the third loop, since the target data is 10-20-40-CC1 and the master data key M3 is 40, the master data keys M1, M2, M3, and M4 are targeted. The related data for 10-20-40-CC1 is collected (step A3), and the data in the third row of FIG. 4 is generated based on the conversion rule (steps A4 and A5).
[0043]
In the data generation in step A5, the company code 10 is the same as the case of the account code 10-20-30-TP1 described above. However, the department code 20 is acquired from the department master and is designated as “General Affairs Department”. Also, the master data key M3 is assigned to the subject code as “40”, and the subject name is obtained from the subject master data as “communication fee”. Since the key M3 is 40, the key M4 of the master data is assigned to the cost center and is set to “CC1”. The cost center name is acquired from the cost center master and is set to “center 1”.
[0044]
At the end of the loop, the converted data is stored in the form master data 32 (step A7).
[0045]
FIG. 5 shows an embodiment of data combination of the form master data 32 and the transaction data 33. Each block indicates one of the form master data 32 and the transaction data 33. The lines connecting the blocks indicate the data connection relationship. Any combination is a logical combination. The source of the arrow indicates transaction data, and the tip of the arrow indicates form master data. The balance represented by reference number 51 is transaction data. Reference numbers 52, 53, and 54 are form master data. Necessary data can be acquired by combining the balance 51 with the account 52, the period 53, and the currency 54 by the data combining means.
[0046]
The currency 54 is master data that holds a currency code (for example, “01”), a currency name (for example, “Japanese yen”), and other information related to the currency. The account 52 is master data that holds an account code (for example, 10-20-30-TP1 shown in FIG. 4) and other information related to the account. The period 53 is master data having information regarding a period code (for example, “2001-01”), a period name (for example, January 2001), and other periods.
[0047]
On the other hand, the balance 51 includes a balance code, a currency code (eg, “01”), an account code (eg, 10-20-30-TP1), a period code (eg, “2001-01”), a balance name (eg, "January 2001"), transaction data holding other information.
[0048]
Accordingly, the balance 51 can be combined with the currency 54 via the currency code, combined with the account 52 via the account code, and combined with the period 53 via the period code. The form output means 42 outputs a form based on the combined data.
[0049]
In the ERP system, for example, the data structure of the form required by the user is different as in the account codes 10-20-30-TP1, 10-20-50-TP2, 10-20-40-CC1 in FIG. Is normal. Thus, it is a feature of the ERP system form that a form having a different data structure is required.
[0050]
In the present invention, by using a conversion rule that defines the relationship between the master data and the form master data so as to conform to the characteristics of the ERP system form, the form pre-processing device does not convert the transaction data. Instead, only master data is converted into form master data, and a form is provided that combines the form master data and transaction data when the form is output. With this mechanism, the processing time of the form pre-processing device can be reduced, and as a result, a general-purpose form pre-processing device can be provided, and a form output that can be flexibly adapted to the application is realized. Can do.
[0051]
FIG. 6 is a block diagram showing the configuration of the second exemplary embodiment of the present invention. The ERP package form processing apparatus of the present embodiment is obtained by adding difference management means 24 to the form preprocessing apparatus 2 of the embodiment shown in FIG. 1 and adding difference data 34 to the ERP database 3. 6, blocks having the same reference numerals as those in FIG. 1 have the same functions as the corresponding blocks in FIG.
[0052]
The difference data 34 stores master data that has been added, updated, or deleted after the previous master conversion process. The difference management means 26 manages the master data processed last time and the current difference data based on the difference data 34. Since the master conversion means 21 uses the difference management means 26 to read only the difference data in step A3 in FIG. .
[0053]
With this device, it is possible to execute the form pre-processing in a short processing time using only the difference master data from the previous time without explicitly specifying the conditions for creating the form.
[0054]
Next, the operation of the form processing apparatus of this embodiment will be described.
FIG. 7 is a process flowchart of the master conversion means 21.
[0055]
When the form creation process is activated, the master conversion unit 21 checks the difference data 34 in the ERP database 3 via the difference management unit, and master data that has been added, updated, or deleted after the previous master conversion process, that is, The presence or absence of difference data is inspected (step S1). If there is no difference data, the form preprocessing is terminated. If there is difference data, the difference data is read (step S2), the previous form master data is read via the difference management means (step S3), and the difference data is converted based on the obtained data. The previous form master data is changed to create the current form master data (step S4), the created form master data is stored in the ERP database 3 (step S5), and the form creation process is terminated. .
[0056]
【The invention's effect】
As described above, the first ERP package form processing apparatus of the present invention defines the conversion rule that defines the relationship between the master data specific to the ERP package and the form master data. Without conversion, only the master data is converted into form master data based on the conversion rule, and when the form is output, the form master data and the transaction data are combined to provide the following effects.
1) In the form pre-processing, the processing time of the form pre-processing apparatus can be shortened by converting only the master data into the form master data without converting the transaction data.
2) By arbitrarily defining the conversion rule so as to conform to the data structure of the ERP system form, it is possible to realize a form output that can be flexibly adapted to the application, and as a result, a general-purpose form. A pre-processing device can be provided.
[0057]
Furthermore, the second ERP package form processing apparatus according to the present invention, when the master data is added, updated, or deleted after the last generation of the form master data, is generated last time based on the difference data. By changing the form master data and generating the current form master data, the processing time of the form preprocessing device can be shortened.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a flow of form processing according to a first embodiment of a form processing apparatus for an ERP package of the present invention.
FIG. 2 is a diagram illustrating a configuration of an example of a conversion rule.
FIG. 3 is a flowchart illustrating an operation example of a master conversion unit.
FIG. 4 is a diagram illustrating an example of form master data generated based on the conversion rule of FIG. 2;
FIG. 5 is a diagram showing an example of data combination of form master data and transaction data.
FIG. 6 is a block diagram showing a configuration of a second exemplary embodiment of the present invention.
7 is a process flowchart of the master conversion unit of FIG. 6;
FIG. 8 is an explanatory diagram of an example of a conventional form creation device.
FIG. 9 is a block diagram illustrating a flow of form processing by an ERP package assumed when the form creation apparatus illustrated in FIG. 8 is applied to an ERP system.
[Explanation of symbols]
1 Starting means
2 Form pre-processing equipment
3 ERP database
4 Form output device
21 Master conversion means
22 dimensional key
23 Conversion rules
24 Difference management means
31 Master data
32 Master data for forms
33 Transaction data
34 Difference data
41 Data combination means
42 Form output means
51 Balance
52 accounts
53 periods
54 Currency
90 Form data
91 Extraction means
92 Form pre-processing device
93 Generating means
94 Form database
95 Form output device
96 Form output means
100 Reference database
102 Conversion means
104 Conversion rules
200 form database
201 Output form
300 Form definition
310 View definition
320 Layout definition

Claims (5)

A storage device having an ERP database, a form pre-processing device and a form output device;
The ERP database includes master data for integrated business processing of the ERP system, general business processing data other than the master data, and information extracted from the master data and general business processing data for output to a form. Accumulate form data that has been converted into a predetermined form format according to a predetermined conversion rule,
The form pre-processing device extracts data for output to the form from the ERP database, converts the extracted data according to the conversion rule, and generates form data described in the form format Accumulated in the ERP database,
The form output device is an ERP package form processing device that sets data necessary for output to the form data and outputs the form as a form.
When the ERP package form processing program is activated, the form pre-processing apparatus extracts master data for outputting to the form from the ERP database, and the extracted master data is subjected to a conversion rule defined for only the master data. Convert to generate form master data described in the form format, and store it in the ERP database as the form data,
The form output device combines the form master data and the business processing general data stored in the ERP database, sets data necessary for output to the combined data, and forms the form. Output as
An ERP package form processing apparatus characterized by the above.   When the information specifying the attribute of the master data specified by the key information is defined as dimension information, the form pre-processing device is a dimension that holds a table of key information of the master data and dimension information corresponding to the key information. The conversion rule includes, as the key information of the master data, a code set to specify an item of the form master data to which the master data specified by the key information corresponding to the dimension information is to be written. The apparatus of claim 2, which is associated.   The conversion rule includes an unconditional conversion rule that associates one key information of master data with one code, and a condition conversion rule that associates one key information of master data with one of the plurality of codes. The apparatus according to claim 2, wherein the condition conversion rule associates key information of master data with a predetermined one of the plurality of codes on the assumption that conversion is performed according to a predetermined unconditional conversion rule. The ERP database stores, as differential data, master data that has been added, updated, or deleted since the last generation of master data for forms,
The form pre-processing device has a difference management means for managing the form master data generated last time based on the difference data and the difference data generated this time,
The form pre-processing apparatus according to any one of claims 1 to 3, wherein the form pre-processing apparatus generates the current form master data by changing the previously generated form master data based on the currently generated difference data. .   The apparatus according to any one of claims 1 to 4, wherein the business processing general data is transaction data.

Images