Information processing device, information processing system, information processing method, and program

Abstract

To reduce a work burden for generating a document corresponding to data outputted by an external system.SOLUTION: An information processing device includes: a reception section for receiving selection of a first external system that is out of multiple external systems for outputting data including multiple items each; a setting information specification section for specifying setting information related to a first external system from among setting information that is stored in advance while being related to the external system each and generates document data from data outputted by the external system; and a document generation section for generating document data corresponding to first data outputted by the first external system by using the specified setting information.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to an information processing device, an information processing system, an information processing method, and a program. [Background technology]

[0002] There are systems (hereinafter referred to as "document generation systems") that generate documents such as invoices from data output by external systems such as sales management systems.

[0003] Patent Document 1 discloses a technique for importing billing data created by sales management software or a business system, creating an invoice, and sending it to the billing recipient. Summary of the Invention [Problem to be solved by the invention]

[0004] Data output by an external system (hereinafter referred to as "external data") does not necessarily correspond to a form that the report generation system can generate. For example, the item names contained in the external data do not necessarily match the item names of the report. Therefore, the user has had to perform complicated settings (for example, setting the correspondence between the item names contained in the external data and the item names in the report) on the report generation system for each external system in order to be able to generate reports based on external data.

[0005] The present invention has been made in consideration of the above-mentioned points, and has an object to reduce the workload required to generate a form in accordance with data output by an external system. [Means for solving the problem]

[0006] In order to solve the above problem, the information processing device has a reception unit that receives a selection of a first external system which is one of a plurality of external systems each outputting data including a plurality of items, a setting information identification unit that identifies setting information associated with the first external system from setting information for generating report data from data output by the external system, the setting information being associated with each of the external systems and pre-stored, and a report generation unit that uses the identified setting information to generate report data corresponding to the first data output by the first external system. Effect of the Invention

[0007] This reduces the workload required to generate reports based on data output by external systems. [Brief description of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of a configuration of an information processing system 1 according to an embodiment of the present invention. [Diagram 2] FIG. 11 is a diagram illustrating an example of captured data. [Diagram 3] 1 is a diagram illustrating an example of a hardware configuration of a transaction management device 10 according to an embodiment of the present invention. [Figure 4] 2 is a diagram for explaining the functional configuration of the terminal device 20 and the transaction management device 10. FIG. [Diagram 5] 11 is a sequence diagram for explaining an example of a processing procedure for registering an external system 30 to be linked to the transaction management device 10. FIG. [Figure 6] FIG. 13 is a diagram showing a display example of a link setting screen. [Figure 7] 2 is a diagram illustrating an example of the configuration of an external system information storage unit 121. FIG. [Figure 8] 2 is a diagram illustrating an example of the configuration of a tenant information storage unit 122. FIG. [Figure 9] 13 is a diagram illustrating an example of the configuration of an import setting information storage unit 123. FIG. [Figure 10]13 is a diagram showing an example of a default association definition stored in a default association definition storage unit 124. FIG. [Figure 11] 13 is a diagram showing an example of a default format definition stored in a default format definition storage unit 125. FIG. [Figure 12] 13 is a diagram showing an example of a tenant association definition stored in a tenant association definition storage unit 126. FIG. [Figure 13] 13 is a diagram illustrating an example of a tenant format definition stored in a tenant format definition storage unit 127. FIG. [Figure 14] 13 is a diagram illustrating an example of a tenant extension item definition stored in a tenant extension item definition storage unit 128. FIG. [Figure 15] FIG. 11 is a sequence diagram illustrating an example of a process for generating form data. [Figure 16] FIG. 13 is a diagram showing a display example of an external system list screen. [Figure 17] FIG. 13 is a diagram showing a display example of an import data registration screen. [Figure 18] 13 is a diagram showing an example of form information stored in a form information storage unit 129. FIG. [Figure 19] 11 is a flowchart illustrating an example of a process procedure for generating and registering form information. [Figure 20] 13A and 13B are diagrams showing examples of screens relating to adding, deleting, or editing extended items. [Figure 21] FIG. 13 is a diagram showing a display example of an import setting information editing screen. [Figure 22] FIG. 4 is a diagram for explaining template data. [Figure 23] FIG. 13 is a diagram illustrating an example of adding import setting information. [Figure 24] 13 is a diagram illustrating an example of adding a tenant association definition and a tenant format definition. [Diagram 25] FIG. 11 is a diagram illustrating an example of captured data in the second embodiment. [Figure 26]13 is a diagram illustrating an example of a tenant extension item definition stored in a tenant extension item definition storage unit 128 according to the second embodiment. FIG. [Figure 27] 13 is a diagram showing an example of association between added extension items and added import items; FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the configuration of an information processing system 1 in an embodiment of the present invention. In FIG. 1, an external system 30 is a computer system used in company X. For example, the external system 30 may be a sales management system. A terminal device 20 is a terminal used by an employee of company X, and is connected to the external system 30 via a network N2 within company X.

[0010] Company X is one of the tenants of the service (hereinafter referred to as the "document management service") provided by the transaction management device 10. A tenant refers to a company, an individual, or the like that has concluded a contract to use the document management service.

[0011] The terminal device 20 is used to use the document management service, and is connected to the transaction management device 10 via a network N1 such as the Internet. The terminal device 20 downloads (acquires) data (e.g., data related to sold goods or services) output by the external system 30 via the network N2, and uploads (transmits) the data to the transaction management device 10 via the network N1. The data output by the external system 30 is, for example, data generated and managed by the external system 30, and includes an item name and a value for each of a plurality of items.

[0012] The transaction management device 10 is one or more computers that provide a form management service. The form management service may be a cloud service provided as a Web-based service. For example, the transaction management device 10 imports data including values ​​for each item that constitutes a form, formats the data into a form format, and generates electronic data that represents the form (hereinafter referred to as "form data"). The form data may be data that can display a form, or data that can print a form. In this embodiment, the transaction management device 10 imports data uploaded from the terminal device 20 and generates a form related to the data (hereinafter referred to as "imported data"). Specifically, the transaction management device 10 assigns the values ​​of each item included in the imported data to each item that constitutes a form based on preset setting information to generate form data. In this way, each tenant of the form management service can obtain a form based on data output by each external service that the tenant uses. The form is, for example, an estimate, a purchase order, a delivery note, an invoice, etc.

[0013] FIG. 2 is a diagram showing an example of imported data. In FIG. 2, each column in the first row indicates an item name. Each column from the second row onward contains a value for the item name corresponding to the column. One row of imported data corresponds to one form. In FIG. 2, it is not important what item names the imported data contains. This is because the item names contained in the imported data differ depending on the external system 30.

[0014] In this way, the imported data is data including a value for each item name. In FIG. 2, the imported data is expressed in a table format, but the format of the imported data is not limited to a table format. The format of the imported data may be a CSV format or an XML (eXtensible Markup Language) format. The imported data may have another format as long as it is a format capable of expressing the correspondence between the item names and the values.

[0015] The item names (hereinafter referred to as "import item names") of each item (hereinafter referred to as "import items") included in the import data do not necessarily match the item names (hereinafter referred to as "form item names") of each item (hereinafter referred to as "form items") pre-registered in the transaction management device 10 as items constituting a form (planned by the transaction management device 10). Furthermore, even if a certain import item name and a certain form item name have the same character string, the meaning of the two does not necessarily remain the same. Based on setting information pre-registered regarding the correspondence between form item names and import item names, the transaction management device 10 identifies which form item name the value for each import item name in the import data corresponds to, and generates form data.

[0016] In FIG. 1, company X has one external system 30, but company X may have multiple external systems 30. In this case, the transaction management device 10 may generate a form for imported data of different formats output by each of the multiple external systems 30. The generated form may be different for each external system 30. There may also be multiple tenants of the form management service. In this case, the external services used by each tenant may be different. In this embodiment, a case will be described in which each of the multiple tenants uses one or more external services.

[0017] 3 is a diagram showing an example of the hardware configuration of transaction management device 10 according to an embodiment of the present invention. Transaction management device 10 in FIG. 3 includes drive device 100, auxiliary storage device 102, memory device 103, CPU 104, and interface device 105, all of which are interconnected via bus B.

[0018] The program that realizes the processing in the transaction management device 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed from the recording medium 101 via the drive device 100 into the auxiliary storage device 102. However, the program does not necessarily have to be installed from the recording medium 101, but may be downloaded from another computer via a network. The auxiliary storage device 102 stores the installed program as well as necessary files, data, etc.

[0019] When an instruction to start a program is received, the memory device 103 reads out the program from the auxiliary storage device 102 and stores it. The CPU 104 executes functions related to the transaction management device 10 in accordance with the program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network.

[0020] The terminal device 20 and the external system 30 may also have the same hardware configuration as that shown in FIG.

[0021] Fig. 4 is a diagram for explaining the functional configuration of the terminal device 20 and the transaction management device 10. In Fig. 4, the terminal device 20 has a display control unit 21, a request unit 22, a response receiving unit 23, etc. Each of these units is realized by a process executed by the CPU of the terminal device 20 by one or more programs installed in the terminal device 20.

[0022] The display control unit 21 displays a screen for receiving input from a user. For example, the display control unit 21 displays a screen based on screen data transmitted from the transaction management device 10. The screen data may be data in HTML format or data in another format.

[0023] The request unit 22 transmits to the transaction management device 10 a request corresponding to an input on the screen displayed by the display control unit 21.

[0024] Response receiving unit 23 receives a response from transaction management device 10 in response to the request sent by request unit 22. If the response includes screen data, display control unit 21 displays a screen based on the screen data.

[0025] The transaction management device 10 includes a reception unit 11, a registration unit 12, a linkage target specification unit 13, a setting information specification unit 14, a form generation unit 15, a screen generation unit 16, and a response transmission unit 17. Each of these units is realized by a process executed by the CPU 104 of one or more programs installed in the transaction management device 10. The transaction management device 10 also uses an external system information storage unit 121, a tenant information storage unit 122, an import setting information storage unit 123, a default correspondence definition storage unit 124, a default format definition storage unit 125, a tenant correspondence definition storage unit 126, a tenant format definition storage unit 127, a tenant extension item definition storage unit 128, and a form information storage unit 129. Each of these storage units can be realized, for example, by using the auxiliary storage device 102, or a storage device that can be connected to the transaction management device 10 via a network.

[0026] The reception unit 11 receives a request from the terminal device 20. When the request from the terminal device 20 is a request for registering various information, the registration unit 12 registers information in various storage units. When the request from the terminal device 20 is a request for generating a form related to certain captured data (hereinafter referred to as "target captured data"), the linkage target identification unit 13 identifies one or more external systems 30 that the tenant requesting the generation has linked to the transaction management device 10. The tenant can link one or more external systems 30 to the transaction management device 10. The external system 30 corresponding to the captured data that is the target for generating the form (hereinafter referred to as "target external system 30") is selected by the user from among the external systems 30 identified by the linkage target identification unit 13. The setting information identification unit 14 identifies the capture setting information associated with the target external system 30 from the setting information (hereinafter referred to as "capture setting information") for generating form data from the captured data output by the external system 30 that is associated with each external system 30 and stored in advance. A certain piece of import setting information is setting information for generating a certain type of form data. By using different import setting information for the same import data, different form data can be generated.

[0027] The form generation unit 15 converts the import item names and their values ​​included in the target import data into information indicating form item names and their values ​​(hereinafter referred to as "form information") using the import setting information identified by the setting information identification unit 14. The form generation unit 15 generates form data corresponding to the target import data based on the form information. The screen generation unit 16 generates screen data for a screen to be displayed on the terminal device 20. The response transmission unit 17 transmits a response to a request from the terminal device 20 to the terminal device 20.

[0028] The external system information storage unit 121 stores default import setting information prepared in advance by a provider of a form management service (hereinafter simply referred to as a "service provider") for each external system 30. For example, the service provider creates the default import setting information based on the characteristics of the import data output by the external system 30.

[0029] The tenant information storage unit 122 stores attribute information of each tenant, information indicating the external system 30 linked to each tenant, and the like.

[0030] The import setting information storage unit 123 stores, for each tenant and for each external system 30 linked to the tenant, import setting information used (applied) for import data output by the external system 30. A plurality of pieces of import setting information may be associated with one external system 30. The import setting information stored in the import setting information storage unit 123 is import setting information that is actually used in generating a form. Meanwhile, the default import setting information stored in the external system information storage unit 121 is import setting information that is the copy source (template) of the import setting information stored in the import setting information storage unit 123. By copying the default import setting information to the import setting information storage unit 123 for each tenant, it is possible to change the import setting information for each tenant.

[0031] The default correspondence definition storage unit 124 stores a default correspondence definition, which is one of the components of the default import setting information. The correspondence definition constituting certain import setting information is information that defines which of a plurality of form item names contained in a form related to the import setting information corresponds to a plurality of import item names contained in import data output by the external system 30 corresponding to the import setting information. The default correspondence definition refers to a correspondence definition prepared in advance by the service provider.

[0032] The default format definition storage unit 125 stores a default format definition, which is one of the components of the default import setting information. The format definition constituting a certain import setting information is information that defines the placement position of values ​​for each form item name included in the form related to the import setting information. The default format definition refers to a format definition prepared in advance by the service provider.

[0033] The tenant association definition storage unit 126 stores association definitions for each tenant (that is, association definitions constituting the import setting information stored in the import setting information storage unit 123).

[0034] The tenant format definition storage unit 127 stores a format definition for each tenant (that is, a format definition constituting the import setting information stored in the import setting information storage unit 123).

[0035] The tenant extended item definition storage unit 128 stores, for each tenant, the form item names that are uniquely defined by the tenant.

[0036] The form information storage unit 129 stores the form information generated by the form generation unit 15 .

[0037] The processing procedure executed in the information processing system 1 will be described below. FIG. 5 is a sequence diagram for explaining an example of the processing procedure of the registration processing of the external system 30 to be linked to the transaction management device 10. A tenant who starts using the form management service must first register the external system 30 to be linked to the transaction management device 10 in the information processing system 1. FIG. 5 shows an example of the processing procedure of the registration processing for this purpose. The external system 30 to be linked to the transaction management device 10 refers to an external system 30 that outputs import data that causes the transaction management device 10 to generate a form. In other words, a state in which the transaction management device 10 is capable of generating a form related to import data output by a certain external system 30 is a state in which the external system 30 is linked to the transaction management device 10.

[0038] In step S101, the display control unit 21 of the terminal device 20 accepts an input by the user to the link setting screen.

[0039] Fig. 6 is a diagram showing a display example of a link setting screen 510. As shown in Fig. 6, a link setting screen 510 includes a check button group 511, a cost display area 512, a register button 513, and the like.

[0040] The check button group 511 is a collection of check buttons for selecting an external system 30 to be linked to the transaction management device 10, and includes a check button for each external system 30. The name (external system name) and monthly fee of the external system 30 corresponding to each check button included in the check button group 511 are identified by referring to the external system information storage unit 121.

[0041] Fig. 7 is a diagram showing an example of the configuration of the external system information storage unit 121. As shown in Fig. 7, the external system information storage unit 121 stores, for each external system 30, an external system ID, an external system name, a monthly fee, import setting information, and the like.

[0042] The external system ID is identification information used by the transaction management device 10 to identify each external system 30. The external system name is the name of the external system 30 (for example, the software name if the external system 30 is a package software). The monthly fee is the cost per month borne by the tenant to link the external system 30 to the transaction management device 10. The monthly fee differs for each external system 30 because the variation (completeness) of the default (prepared in advance) import setting information differs depending on the external system 30. When linking an external system 30 with a wide variety of default import setting information, it is relatively likely that the tenant can use the default import setting information as is or change part of the default import setting information to cause the transaction management device 10 to generate the form desired by the tenant. On the other hand, if the variation of the default import setting information is small, it is relatively likely that the tenant cannot cause the transaction management device 10 to generate the form desired by the tenant unless the tenant significantly changes the default import setting information or generates new import setting information. In other words, the burden on the tenant side differs depending on the variation of the import setting information. Therefore, the monthly fee is set according to the external system 30. In the example of Fig. 7, there are three pieces of import setting information for external system A, one piece of import setting information for external system B, and two pieces of import setting information for external system C. Therefore, the monthly fees are in order of external system A>external system C>external system B.

[0043] The external systems 30 registered in the external system information storage unit 121 may be all external systems 30 used in the market, or may be external systems 30 selected by the service provider based on market share, name recognition, etc.

[0044] When the user selects one or more check buttons in check button group 511 on cooperation setting screen 510 in FIG. 6, the monthly total corresponding to the selected check button is displayed in expense display area 512.

[0045] The linkage setting screen 510 is displayed in response to a predetermined operation after the user logs in to the transaction management device 10 using the terminal device 20. When logging in, the tenant ID of the tenant to which the user belongs (hereinafter referred to as the "target tenant"), the user's user ID, password, etc. are input. Therefore, at this point in time, the tenant ID of the target tenant ("T0001" in the example of FIG. 6) has been identified.

[0046] When the user selects a check button corresponding to the external system 30 to be linked and presses the registration button 513, step S101 is executed.

[0047] Next, the request unit 22 transmits a registration request for the external system 30 to be linked to the transaction management device 10 (S102). The registration request includes the tenant ID of the target tenant (hereinafter, referred to as the "target tenant ID") and the external system ID of each external system 30 selected as a link target (in the example of FIG. 6, the external system ID of external system A and the external system ID of external system C).

[0048] When the reception unit 11 of the transaction management device 10 receives the registration request, the registration unit 12 updates various setting information based on the registration request (S103). Specifically, the registration unit 12 updates the tenant information storage unit 122.

[0049] Fig. 8 is a diagram illustrating a configuration example of the tenant information storage unit 122. As illustrated in Fig. 8, the tenant information storage unit 122 stores tenant information including a tenant ID, a name, an address, a person in charge, an email address, a linked external system ID, and the like for each tenant.

[0050] The tenant ID is as described above. The name is the name of the tenant (e.g., a company name, etc.). The address is the address of the tenant (e.g., a head office address, etc.). The person in charge is, for example, a person who will be a user of the transaction management device 10 in the tenant. The email address is the email address of the person in charge. The linked external system ID is the external system ID of the external system 30 (hereinafter referred to as the "linked external system 30") that the tenant has registered to be linked with the transaction management device 10. In step S103, the registration unit 12 adds all external system IDs included in the registration request to the linked external system ID of the tenant information corresponding to the target tenant.

[0051] The registration unit 12 also updates the import setting information storage unit 123 .

[0052] FIG. 9 is a diagram showing a configuration example of the import setting information storage unit 123. The import setting information storage unit 123 stores an import setting information table including import setting information for each linked external system 30 for each tenant. FIG. 9 shows the import setting information table for the target tenant (tenant with tenant ID=T0001). At the time of step S103, the registration unit 12 copies the external system ID, external system name, and import setting information of each external system 30 selected by the target tenant as a linked external system 30 from the information stored for each external system 30 in the external system information storage unit 121 (FIG. 7) to the import setting information table corresponding to the target tenant. FIG. 9 shows an example of the import setting information table when the target tenant selects external system A and external system C as linked external systems 30.

[0053] 7 and 9, the import setting information includes an import setting information ID, an import setting information name, a correspondence definition ID, a format definition ID, an item value reading definition, an automatic calculation definition, and a delimiter definition.

[0054] The import setting information ID is identification information for the transaction management device 10 to identify multiple import setting information. The import setting information name is the name of the import setting information and is used as a character string for display. The correspondence definition ID is identification information of the correspondence definition belonging to the import setting information. The format definition ID is identification information of the format definition belonging to the import setting information. The item value import definition is a definition regarding the rules for absorbing the specifications of the import data output by the external system 30. The illustrated "Ignore lines containing '0'" means that lines of the imported data that contain 0 as the value of any of the imported item names will not be converted into a report. This is because there exists an external system 30 that outputs imported data so that a line of the imported data contains 0 as one of the item values ​​to indicate that the line is meaningless. For example, if there exists an external system 30 that outputs imported data according to the rule that lines beginning with '#' are comment lines, then an item value import definition of "Ignore lines beginning with '#'" may be set. The automatic calculation definition is a setting regarding whether or not the result of adding up the values ​​of multiple items of the imported data (for example, the sum of the unit price x quantity of the details that make up an invoice) may be automatically calculated as the value of a specific item (for example, the value of "total amount"). ON indicates that automatic calculation is permitted, and OFF indicates that automatic calculation is not permitted. The delimiter definition is a definition that indicates the delimiter between the item name and the item value in the imported data.

[0055] The import setting information may include other definitions. For example, the import setting information may include a definition indicating whether to use the "yen" or the "dollar" as the "currency unit definition."

[0056] Note that one or more pieces of import setting information can be registered for one external system 30. In the example of FIG. 7 and FIG. 9, three pieces of import setting information are registered for external system A, and two pieces of import setting information are registered for external system C. The reason why multiple pieces of import setting information can be registered for one external system 30 is to enable the generation of multiple types of reports from the import data output by the external system 30. In addition, the type of import data output by one external system 30 is not necessarily one. In FIG. 7 and FIG. 9, among the three pieces of import setting information corresponding to the external system A, the import setting information with the import setting information name "external system A_basic items" is import setting information for generating a report based on some items of the import data output by the external system A. The import setting information with the import setting information name "external system A_all items" is import setting information for generating a report based on all items included in the import data output by the external system A. The import setting information whose name is "External system A_all items_Construction industry" is import setting information for generating a report based on all items contained in the import data that external system A outputs for the construction industry.

[0057] Among the definitions constituting the default import setting information (Figure 7), the default correspondence definition corresponding to the correspondence definition ID and the default format definition corresponding to the format definition ID are stored in the default correspondence definition memory unit 124 and the default format definition memory unit 125, respectively.

[0058] FIG. 10 is a diagram showing an example of a default correspondence definition stored in the default correspondence definition storage unit 124. FIG. 10 shows one default correspondence definition (a correspondence definition with a correspondence definition ID of "A03"). As shown in FIG. 10, the correspondence definition includes a correspondence definition ID, and a form item ID, a form item name, and an import item name for each form item that may be included in a form corresponding to the correspondence definition. The form item ID is identification information for the transaction management device 10 to identify multiple form items. The form item name is the form item name corresponding to the form item ID. The import item name is the import item name corresponding to the form item name. In this way, a (default) correspondence relationship between the form item name and the import item name is set in the default correspondence definition.

[0059] Note that the value of a certain form item is not necessarily the value of a certain import item itself. For example, the value of a certain form item may be a character string obtained by combining the values ​​of multiple import items, or a numerical value obtained by substituting the values ​​of one or multiple import items into a predetermined calculation formula. In the correspondence definition, as an "import item name" corresponding to a certain "form item name", a derivation method based on the values ​​of one or multiple import items can be defined using the import item name of the import item. For example, FIG. 10 shows that the form item name "Address" is associated with the form item name "Address1<Combined>Address2". This indicates that the character string obtained by concatenating the value of the import item name "Address1" (e.g. prefecture name) and the value of the import item name "Address2" (e.g. address after city / town / village name) is the value of the form item name "Address" (e.g. prefecture name after address). Such definitions also differ depending on the external system 30, so it is very time-consuming for the user to set them by themselves. In this embodiment, such definitions are also prepared in advance in the default association definitions, so that the workload of the user can be reduced.

[0060] The correspondence definition also includes the item type of each report item. The value of the item type is "standard item" or "extended item." A "standard item" is a report item that is registered in the transaction management device 10 from the beginning as a basic or general-purpose report item. An "extended item" is a report item that is added to the transaction management device 10 through customization or the like. For example, a report item that corresponds to an item unique to a certain external system 30 (hereinafter, "unique item") is not registered as a standard item. Therefore, a report item prepared to correspond to a unique item is added and registered as an extended item.

[0061] Although it is assumed that the extension items are registered on the tenant side, in this embodiment, the service provider investigates in advance what kind of unique items each external system 30 registered in the external system information storage unit 121 (FIG. 7) has, and the form items corresponding to each unique item are added in advance to the default association definition. Therefore, it is possible to reduce the need for the tenant to add extension items.

[0062] Fig. 11 is a diagram showing an example of a default format definition stored in the default format definition storage unit 125. Fig. 11 shows one default format definition (a format definition having a format definition ID of "A13"). As shown in Fig. 11, the format definition includes a format definition ID and a format definition name, and for each form item included in a form corresponding to the format definition, an item type, a form item ID, a form item name, coordinates, a layout method, a font size, and the like.

[0063] The format definition name is the name of the format definition, and is used, for example, as a character string for display. The item type, form item ID, and form item name are as described above.

[0064] The coordinates are the coordinates of the reference position (e.g., the upper left coordinates) of the rectangle corresponding to the placement area of ​​the form item in the form corresponding to the format definition. The placement method is the placement method (left-justified / center-justified / right-justified) of the value (character string) of the form item within the rectangle. The font size is the font size of the value (character string).

[0065] Regarding the format definition, not only the standard items but also the definitions regarding the extended items are set in advance as default format definitions by the service provider.

[0066] In addition, in step S103, the registration unit 12 also records (copies) a default association definition and a default format definition related to the import setting information corresponding to each external system 30 selected as a link target in association with the target tenant in the tenant association definition storage unit 126 or the tenant format definition storage unit 127. That is, the association definition and the format definition are managed for each tenant. This is to enable the association definition and the format definition to be changed (customized) for each tenant. Hereinafter, the association definition for each tenant is referred to as a "tenant association definition" and the format definition for each tenant is referred to as a "tenant format definition."

[0067] Fig. 12 is a diagram showing an example of a tenant correspondence definition stored in the tenant correspondence definition storage unit 126. Fig. 12 shows one tenant correspondence definition (a tenant correspondence definition corresponding to a tenant ID="0001" and a correspondence definition ID="A03").

[0068] The tenant association definition differs from the default association definition (FIG. 10) in that it further includes the tenant ID of the tenant corresponding to the tenant association definition. Although omitted in FIG. 12, in step S103, not only the tenant association definition in which the target tenant ID is assigned to the default association definition in FIG. 10, but also the tenant association definition in which the target tenant ID is assigned to each default association definition related to the import setting information corresponding to each external system 30 selected as a linkage target are added to the tenant association definition storage unit 126.

[0069] Fig. 13 is a diagram showing an example of a tenant format definition stored in the tenant format definition storage unit 127. Fig. 13 shows one tenant format definition (tenant format definition corresponding to tenant ID = "0001" and format definition ID = "A13"). Although omitted in Fig. 13, in step S103, not only the tenant format definition in which a target tenant ID is assigned to the default format definition in Fig. 11, but also the tenant format definition in which a target tenant ID is assigned to each default format definition related to the import setting information corresponding to each external system 30 selected as a link target are added to the tenant format definition storage unit 127.

[0070] The correspondence definition ID and the format definition ID of each piece of import setting information stored in the import setting information storage unit 123 shown in FIG. 9 are identification information for the tenant correspondence definition ID and the tenant format definition ID, respectively. That is, each piece of import setting information stored in the import setting information storage unit 123 is associated with a tenant correspondence definition and a tenant format definition. In this embodiment, the correspondence definition ID of a certain tenant correspondence definition is the same as the correspondence definition ID of the default correspondence definition of the copy source of the tenant correspondence definition, and the format definition ID of a certain tenant format definition is the same as the format definition ID of the default format definition of the copy source of the tenant format definition. However, when the ID is changed between the copy source and the copy destination, the ID of the copy destination is set in each piece of import setting information stored in the import setting information storage unit 123.

[0071] Furthermore, in step S103, if the tenant correspondence definition (Figure 12) recorded in the tenant correspondence definition memory unit 126 includes a report item (i.e., an extended item) whose item type is "extended item," the registration unit 12 registers the report item ID and report item name of the extended item in the tenant extended item definition memory unit 128 in association with the target tenant ID.

[0072] Fig. 14 is a diagram illustrating an example of a tenant extension item definition stored in the tenant extension item definition storage unit 128. Fig. 14 illustrates a tenant extension item definition corresponding to a target tenant. That is, the tenant extension item definition storage unit 128 stores a tenant extension item definition for each tenant.

[0073] A tenant extension item definition corresponding to one tenant stores the form item ID and the form item name for all extension items set in the default correspondence definition (FIG. 10) and extension items added uniquely by the tenant. When step S103 is executed for a certain tenant for the first time, the contents of the tenant extension item definition corresponding to the tenant are the contents related to all extension items set in the default correspondence definition (FIG. 10). When step S103 is executed for a certain tenant for the second or subsequent time, information related to the extension items already registered in the tenant extension item definition corresponding to the tenant does not need to be registered again.

[0074] This completes the preparation for the tenant to use transaction management device 10. Next, a process procedure executed when a tenant causes transaction management device 10 to generate form data corresponding to certain input data will be described.

[0075] Fig. 15 is a sequence diagram for explaining an example of a processing procedure for generating form data. The processing procedure in Fig. 15 is executed, for example, when the terminal device 20 downloads import data output from a certain external system 30 (hereinafter referred to as "target external system 30") and causes the transaction management device 10 to generate form data of the import data (hereinafter referred to as "target import data").

[0076] When the display control unit 21 of the terminal device 20 receives a predetermined operation from a user indicating an instruction to display an external system list screen (S111), the request unit 22 transmits an acquisition request for the external system list screen to the transaction management device 10 (S112). The acquisition request includes the target tenant ID. When the reception unit 11 of the transaction management device 10 receives the acquisition request, the linkage target identification unit 13 refers to the tenant information storage unit 122 (FIG. 7) to identify a list of external systems 30 that the target tenant has linked to the transaction management device 10 (S113). Specifically, the linkage target identification unit 13 acquires the linked external system ID stored in the tenant information storage unit 122 (FIG. 7) in association with the target tenant ID.

[0077] Next, the screen generating unit 16 generates screen data for an external system list screen based on the linked external system ID and the external system information storage unit 121 (FIG. 7) (S114). Specifically, the screen generating unit 16 acquires the external system name corresponding to each of the linked external system IDs from the external system information storage unit 121 (FIG. 7), and generates the screen data including the acquired character string as a label of an option corresponding to each external system 30. Next, the response transmitting unit 17 transmits a response including the screen data to the terminal device 20 (S115).

[0078] When the response receiving unit 23 of the terminal device 20 receives the response, the display control unit 21 displays the external system list screen based on the screen data included in the response.

[0079] Fig. 16 is a diagram showing a display example of an external system list screen. As shown in Fig. 16, an external system list screen 520 includes a selection area 521. The selection area 521 includes buttons corresponding to options for each external system 30 that the target tenant has linked to the transaction management device 10. In Fig. 16, "External System A" and "External System C" are the options.

[0080] When the user selects one option corresponding to the target external system 30 (S117), the request unit 22 of the terminal device 20 transmits a request to acquire the import data registration screen to the transaction management device 10 (S118). The request includes the external system ID of the selected external system 30 (hereinafter, referred to as the "target external system 30"), and also serves as notification information of the selection result of the external system 30.

[0081] The reception unit 11 of the transaction management device 10 receives the acquisition request and thereby accepts the selection of the external system 30. In response to the reception unit 11 receiving the acquisition request, the setting information identification unit 14 identifies (acquires) the import setting information corresponding to the target tenant ID and the external system ID included in the acquisition request from among the import setting information stored in the import setting information storage unit 123 (FIG. 9) (S119). Note that multiple pieces of import setting information may be registered in one external system 30. In step S119, all of the applicable import setting information may be identified (acquired).

[0082] Next, the screen generator 16 generates screen data for an import data registration screen based on the one or more pieces of specified import setting information (S120). Next, the response transmitter 17 transmits a response including the screen data to the terminal device 20 (S121). When the response receiver 23 of the terminal device 20 receives the response, the display controller 21 displays the import data registration screen based on the screen data included in the response (S122).

[0083] 17 is a diagram showing a display example of the import data registration screen 530. As shown in FIG. 17, the import data registration screen 530 includes a display area 531, a list box 532, a button 533, a display area 534, and a registration button 535.

[0084] Display area 531 includes a message prompting the user to select the name of the import setting information and the CSV file (import data).

[0085] The list box 532 is an area for selecting import setting information to be applied (used currently) to the target import data from one or more import setting information for the target external system 30, and includes options labeled with the import setting information name of each import setting information for the target external system 30.

[0086] Button 533 is a button for receiving an instruction to display a dialog (hereinafter referred to as a "file dialog") for selecting a file for storing the target import data from among the files saved in the file system of terminal device 20. Display area 534 displays the file name of the file selected via the file dialog. Register button 535 is a button for receiving an instruction to register the import data whose file name is displayed in display area 534.

[0087] When the user selects the import setting information to be applied to the target import data via list box 532, selects the target import data (the file that stores it) using button 533, and then presses registration button 535 (S123), the request section 22 of the terminal device 20 sends a registration request to the transaction management device 10 including the import setting information ID (hereinafter referred to as the "target import setting information ID") of the selected import setting information (hereinafter referred to as the "target import setting information") and the target import data (S124).

[0088] When the reception unit 11 of the transaction management device 10 receives the registration request, the report generation unit 15 generates report information by converting each item of the target import data into an item of a report related to the target import setting information based on the tenant correspondence definition related to the target import setting information (Figure 12), and registers the report information in the report information storage unit 129 (S125).

[0089] Fig. 18 is a diagram showing an example of form information stored in the form information storage unit 129. As shown in Fig. 18, one piece of form information includes a tenant ID, and a form item name and value for each form item. The value for a certain form item name is the value of an imported item name that corresponds to the form item name in the imported data, or a value derived based on the value.

[0090] Next, the report generation unit 15 generates report data (e.g., PDF data) in which the values ​​of each report item name of the report information are arranged at the placement position (coordinates and placement method) and font size defined in the tenant format definition (Figure 13) related to the target import setting information (S126).

[0091] Thereafter, the user designates a destination of the form data and requests transaction management device 10 to send a form based on the form data to the destination.

[0092] 15 shows an example in which the target capture data output by the target external system 30 is transmitted to the transaction management device 10 via the terminal device 20, but the target capture data may be transmitted from the target external system 30 to the transaction management device 10 without passing through the terminal device 20. For example, the transaction management device 10 may acquire (download) the target capture data from the target external system 30 in response to a predetermined instruction from a user.

[0093] Next, a detailed description will be given of step S125. Fig. 19 is a flowchart for explaining an example of a process procedure relating to generation and registration of form information.

[0094] In step S201, the form generation unit 15 acquires target import setting information corresponding to the target tenant ID and the target import setting information ID from the import setting information storage unit 123 (FIG. 9). Next, the form generation unit 15 reads each line of the target import data (S202).

[0095] Next, the form generation unit 15 executes a loop process L1 for each row that has been read in. The row that is the target of processing in the loop process L1 is hereinafter referred to as the "target row." The loop process L1 includes steps S203, S204, a loop process L2, and a step S208.

[0096] In step S203, the report generation unit 15 divides the target row into units of item name or value (item value) according to the delimiter definition in the target import setting information (FIG. 9). Next, the report generation unit 15 determines whether the target row is not one of the rows to be ignored (S204) based on the item value reading definition in the target import setting information (FIG. 9). For example, if the item value reading definition is "ignore rows containing '0'", the report generation unit 15 determines whether any item value in the target row is '0'. If the target row corresponds to a row to be ignored (No in S204), the report generation unit 15 does not execute loop process L2 and step S208 for the target row.

[0097] If the target row is not a row to be ignored (Yes in S204), the form generation unit 15 executes loop processing L2 for each form item name associated with the import item name among the form item names included in the tenant association definition (FIG. 12) (hereinafter referred to as the "target association definition") related to the target import setting information. The form item name to be processed in loop processing L2 is hereinafter referred to as the "target form item name." Loop processing L2 includes steps S205 to S207.

[0098] In step S205, the form generating unit 15 judges whether the import item name (hereinafter referred to as the "target import item name") associated with the target form item name in the target correspondence definition is expressed by only one item name. If the target import item name is expressed by only one item name (Yes in S205), the form generating unit 15 stores the value corresponding to the target import item name in the target row as the value for the target form item name (S206).

[0099] If the target import item name is not an expression of only one item name, such as an expression indicating a formula or a join (No in S205), the report generation unit 15 stores the value obtained as a result of the formula or the join as the value for the target report item name (S207).

[0100] When the loop process L2 is executed for all the form item names included in the target association definition, the form generation unit 15 generates form information (FIG. 23) including the value of each form item name and the target tenant ID stored in step S206 or S207 for the target row, and registers the form information in the form information storage unit 129 (S208). The form information registered by one execution of step S208 is form information for one row of the form information in the format shown in FIG.

[0101] When the loop process L1 has been executed for all rows of the target capture data, the process of FIG. 19 ends.

[0102] A certain tenant can add a new extension item to the tenant extension item definition (FIG. 14) associated with the tenant ID of the tenant, and can delete or edit an existing extension item.

[0103] FIG. 20 is a diagram showing an example of a screen for adding, deleting, or editing an extended item. In FIG. 20, a screen 540 on the left side is an example of a screen used when adding an extended item. The screen 540 includes an input area 541, an input area 542, a button 543, and the like. The input area 541 is an area for accepting input of a form item name of a form item to be added as an extended item. The input area 542 is an area for accepting input of a form item ID of the form item. The button 543 is a button for accepting an instruction to add an extended item. When the button 543 is pressed, the request unit 22 of the terminal device 20 transmits an extended item registration request to the transaction management device 10. The extended item registration request includes a tenant ID, and the form item name and form item ID entered in the input area 541 or the input area 542.

[0104] When the registration unit 12 of the transaction management device 10 receives an extended item registration request, it adds the report item name and report item ID included in the extended item registration request to the tenant extended item definition (Figure 14) corresponding to the tenant ID included in the extended item registration request.

[0105] 20 is an example of a screen used when editing or deleting an extension item that has been copied from existing (default) import setting information or that has been added in the past using screen 540. Screen 550 includes a display area 551 and an operation area 552.

[0106] The display area 551 includes the item names (form item names) and item IDs (form item IDs) of all extension items included in the tenant extension item definition ( FIG. 14 ) associated with a pre-input tenant ID and stored in the tenant extension item definition storage unit 128. The operation area 552 includes an edit button and a delete button for each extension item.

[0107] When an edit button corresponding to any of the extended items is pressed in the operation area 552, the item name and item ID of the extended item can be edited. The user can change the item name or the item ID in the display area 551. When a delete button corresponding to any of the extended items is pressed in the operation area 552, the extended item is deleted from the display area 551. When the user performs a predetermined operation after editing or deleting the extended item via the screen 550, the request unit 22 of the terminal device 20 transmits an extended item update request to the transaction management device 10. The extended item update request includes the tenant ID and the input result on the screen 550. The input result is the result of editing or deletion. For an extended item whose item name has been edited, the input result includes the item ID (form item ID) and the item name after editing (extended item name). For an extended item whose item ID has been edited, the input result includes the item ID before editing (form item ID) and the item ID after editing (form item ID). For deleted extension items, the item ID (form item ID) of the extension item is included.

[0108] When the registration unit 12 of the transaction management device 10 receives an extended item update request, it reflects the input result contained in the extended item update request (change of item name or item ID, or deletion of item) to the tenant extended item definition (Figure 14) corresponding to the tenant ID contained in the extended item update request.

[0109] Furthermore, a certain tenant can generate new import setting information (FIG. 9) corresponding to any of the external systems 30 (hereinafter referred to as the "target external system 30") associated with the tenant ID of the tenant (hereinafter referred to as the "target tenant"). In other words, a tenant can generate and use not only the import setting information provided as default, but also its own unique import setting information.

[0110] Fig. 21 is a diagram showing a display example of an import setting information editing screen. As shown in Fig. 21, an import setting information editing screen 600 includes a list box 601, an input area 602, a check box 603, a check box 604, a list box 605, a button 607, a display area 608, a list box 609, a standard item matching area 610, an extended item matching area 620, and a registration button 630. Screen data of the import setting information editing screen 600 is generated by the screen generating unit 16. The display control unit 21 of the terminal device 20 displays the import setting information editing screen 600 based on the screen data.

[0111] The list box 601 is an area for selecting the import setting information to be edited from the tenant ID of the target tenant and the import setting information corresponding to the target external system 30, and includes the transaction setting information name of the import setting information corresponding to the target external system 30 as an option.

[0112] The input area 602 is an area for receiving input of the import setting information name of the edited (newly generated) import setting information. The import setting information related to the edited import setting information name is hereinafter referred to as "target import setting information". The initial value of the target import setting information is a copy of the import setting information to be edited. The tenant association definition (hereinafter referred to as "target association definition") and the tenant format definition (hereinafter referred to as "target format definition") belonging to the target import setting information are also copies of the tenant association definition or the tenant format definition belonging to the import setting information to be edited. Therefore, the user can generate the target import setting information by inputting only the difference with respect to the import setting information to be edited. As a result, the workload for adding new import setting information can be reduced.

[0113] The check box 603 is a check box for receiving a selection regarding the item value read definition of the target import setting information. The initial state of the check box 603 conforms to the item value read definition of the import setting information to be edited.

[0114] The check box 604 is a check box for receiving a selection regarding the automatic calculation definition of the target import setting information. The initial state of the check box 604 follows the automatic calculation definition of the import setting information to be edited.

[0115] The list box 605 is a list box for receiving a selection regarding the delimiter definition of the target import setting information. In addition to "comma delimiter", the list box 605 may include options such as "space delimiter" and "TAB delimiter". The initial state of the list box 605 follows the delimiter definition of the import setting information to be edited.

[0116] Button 607 is a button for receiving an instruction to display a file dialog for selecting a file in which to store the import data from among the files stored in the file system of terminal device 20. The import data (hereinafter referred to as "target import data") is the source from which import item names that are candidates for association with form item names are extracted. Therefore, the item values ​​of the target import data are not used.

[0117] A display area 608 displays the filename of the file selected via the file dialog.

[0118] The list box 609 is a list box that selects the format definition name of the tenant format definition to be associated with the target import setting information. The format definition name that can be selected is, for example, a file name that stores data (hereinafter referred to as "template data") that is the source of the format definition and is prepared in advance in the terminal device 20.

[0119] Fig. 22 is a diagram for explaining template data. Template data 700 shown in Fig. 22 is data for setting the layout of a certain form, and may be created, for example, using general spreadsheet software or the like.

[0120] In template data 700, form item IDs are input in cells 701 to 712. The position of each form item ID is the arrangement position of a value for the form item name that corresponds to each form item ID in the form to which template data 700 corresponds.

[0121] Returning to FIG. 21, the standard item correspondence area 610 and the extended item correspondence area 620 are areas for editing the target correspondence definition. Specifically, in the standard item correspondence area 610, an area 611 includes a list of form item names of all form items whose item type is "standard item" in the target correspondence definition. An area 612 includes a list box for selecting an import item name to be associated with each form item name arranged in the area 611. The options of each list box are the item names (import item names) included in the target import data whose file names are displayed in the display area 608. An area 613 includes an add button for each form item name arranged in the area 611. The add button corresponding to a certain form item name is used when two or more import item names are to be associated with the certain form item name. When the add button corresponding to a certain form item name is pressed, the display control unit 21 adds a new list box below the list box corresponding to the certain form item name. At this time, it may be possible to input a calculation formula or a combination method based on each import item name selected from two or more list boxes corresponding to the form item name.

[0122] The area 621 in the extension item correspondence area 620 includes a list of form item names of all form items whose item type is "extended item" in the target correspondence definition. The area 621 further includes a form item name (hereinafter referred to as "added item name") that is not included in the list among the form item names included in the tenant extended item definition (FIG. 14) associated with the tenant ID of the target tenant, if there is such a form item name. This allows the extension items added uniquely to the tenant to be associated with the imported item names. The functions of the areas 622 and 623 are the same as those of the areas 612 and 613. Note that a predetermined mark indicating that the added item name is newly added may be added to the added item name. Based on the mark, the user can recognize the newly added extended item among the extended items in the extension item correspondence area 620.

[0123] The initial state of the list boxes in area 612 and area 622 may follow the association definition belonging to the import setting information to be edited.

[0124] Of the form item names displayed in area 611 or area 621 (i.e., form item names included in the target correspondence definition), only those form item names that correspond to form items included in the template data whose file name (format definition name) is displayed in display area 608 need to be associated with the import item name. In other words, there may be form item names that cannot be associated with import item names. In particular, there may be cases where some or all of the added item names do not need to be associated with import item names. Form item names that cannot be associated with import item names are associated with a symbol (in this embodiment, "<empty>") indicating that there is no corresponding import item name.

[0125] When editing on the import setting information editing screen 600 is completed and the registration button 630 is pressed, the request unit 22 of the terminal device 20 transmits the editing results on the import setting information editing screen 600 to the transaction management device 10. The editing results include the tenant ID of the target tenant, the external system ID of the target external system 30, the name of the edited import setting information entered in the input area 602, the item value reading definition entered in the check box 603, the automatic calculation definition entered in the check box 604, the delimiter definition selected in the list box 605, the format definition name selected in the list box 609 and the template data related to the format definition name, the correspondence definition set in the standard item correspondence area 610 and the extended item correspondence area 620, and the like.

[0126] When the reception unit 11 of the transaction management device 10 receives the editing result, the registration unit 12 adds new import setting information corresponding to the tenant ID and external system ID contained in the editing result to the import setting information memory unit 123 (Figure 9).

[0127] Fig. 23 is a diagram showing an example of adding import setting information. Comparing Fig. 23 with Fig. 9, in Fig. 23, a fourth import setting information has been added to external system A. When adding new import setting information, the registration unit 12 generates an import setting information ID for the import setting information. The registration unit 12 registers values ​​contained in the editing result in the import setting information name, item value reading definition, automatic calculation definition, and delimiter definition of the import setting information (target import setting information). The registration unit 12 assigns new values ​​to the correspondence definition ID and format definition ID of the target import setting information.

[0128] The registration unit 12 associates the association definition included in the edit result with the tenant ID and the new association definition ID ("A04" in the example of FIG. 23), and registers the association definition included in the edit result in the tenant association definition storage unit 126. An example of the registration result is shown in FIG. 24(1).

[0129] The registration unit 12 also registers a tenant format definition based on the template data included in the editing result in the tenant format definition storage unit 127 in association with the tenant ID, the format definition ID ("A14" in the example of FIG. 23), and the format definition name included in the editing result. An example of the registration result is shown in FIG. 24(2). Specifically, the registration unit 12 specifies, for each form item ID included in the template data, the coordinates (for example, the coordinates of the upper left vertex) of a cell that stores the form item ID in the template data and a method of arranging the form item ID in the cell, and generates the tenant format definition based on the specified result.

[0130] As described above, according to this embodiment, import setting information is prepared in advance for each external system 30. When a user wishes to generate a form for import data output from one of the external systems 30, the user can cause the transaction management device 10 to generate a form based on the import setting information corresponding to the external system 30 with a simple operation of specifying (selecting) the external system 30. This reduces the workload of generating a form according to the data output by the external system 30. When the same import setting information is applied to import data with different item values, a form of the same format with only different item values ​​can be generated.

[0131] Next, a second embodiment will be described. In the second embodiment, differences from the above embodiment will be described. Therefore, the points not specifically mentioned may be the same as the first embodiment.

[0132] In the second embodiment, an example will be described in which detailed information (hereinafter referred to as "destination detailed information") of the destination of the form (the business partner that issued the form) is added to the import items. If the form is an invoice, the destination of the form is the destination of the invoice.

[0133] Fig. 25 is a diagram showing an example of the imported data in the second embodiment. In Fig. 25, it is assumed that imported data including imported items such as organization, office, homepage, logo, business card, SNS_ID, size, registration number, etc. related to the delivery destination of the form are output from the external system 30 in addition to the imported data shown in Fig. 2. Note that the SNS_ID is, for example, an ID in a message exchange application or the like. Also, the registration number is, for example, a registration number of the National Tax Agency.

[0134] The configuration of the delivery destination details information to be included in the form may differ depending on the delivery destination of the form. Therefore, the import items that make up the delivery destination details information (hereinafter referred to as "additional import items") may be registered as extended items in the transaction management device 10.

[0135] Specifically, the user first uses screen 540 in FIG. 20 to register an extension field corresponding to the import field (hereinafter, referred to as an "added extension field") in the tenant extension field definition corresponding to the tenant to which the user belongs.

[0136] Fig. 26 is a diagram illustrating an example of a tenant extension item definition stored in the tenant extension item definition storage unit 128 in the second embodiment. Comparing Fig. 26 with Fig. 14, information corresponding to an additional extension item is further added in Fig. 26.

[0137] Thereafter, the user can use the import setting information editing screen 600 (Figure 21) to generate new import setting information (target import setting information) corresponding to the external system 300 (hereinafter referred to as the "target external system 30") that outputs import data such as that shown in Figure 25.

[0138] Specifically, the user operates button 607 to select a file that stores import data including the additional import items as shown in FIG. 25 (hereinafter referred to as "target import data") from among the files stored in the file system of terminal device 20. By doing so, a line including the form item name of the additional extension item is also displayed in area 621 of extension item association area 620. Also, the list box in area 622 includes the import item names of the additional import items as options. Therefore, as shown in FIG. 27, the user can associate the additional import items with each additional extension item.

[0139] Fig. 27 is a diagram showing an example of the association between the added extension items and the added import items. Note that Fig. 27 shows an excerpt of the extension item association area 620 of the import setting information editing screen 600 (Fig. 21).

[0140] The user also operates the list box 609 to select the format definition name of the tenant format definition to be associated with the target import setting information. Note that the template data (FIG. 22) that is the source of the format definition of the format definition name is created in advance. The layout positions of each additional extension item are also set in the template data.

[0141] Thereafter, when the user presses the registration button 630, new import setting information including the association definition set in the extended item association area 620 is added to the import setting information storage unit 123 (FIG. 9). As a result, it becomes possible to generate a form corresponding to the added import item.

[0142] Each function of the above-described embodiment can be realized by one or more processing circuits. In this specification, the term "processing circuit" includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and a device such as an ASIC (Application Specific Integrated Circuit), a DSP (digital signal processor), an FPGA (field programmable gate array), or a conventional circuit module designed to execute each function described above.

[0143] In this embodiment, transaction management device 10 is an example of an information processing device.

[0144] Although the embodiment of the present invention has been described in detail above, the present invention is not limited to such specific embodiment, and various modifications and variations are possible within the scope of the gist of the present invention described in the claims.

[0145] For example, aspects of the present invention are as follows. <1> A reception unit that receives a selection of a first external system which is one of a plurality of external systems each outputting data including a plurality of items; A setting information identification unit that identifies setting information associated with the first external system from setting information for generating form data from data output by each of the external systems, the setting information being associated with each of the external systems and pre-stored; a form generating unit that generates form data corresponding to the first data output by the first external system using the specified setting information; 13. An information processing device comprising: <2> The setting information includes a correspondence definition that defines which of a plurality of item names included in a form related to the setting information corresponds to which of a plurality of item names included in data output by the external system corresponding to the setting information, the form generation unit identifies, based on the correspondence definition included in the setting information associated with the first external system, which item name among a plurality of item names included in a form related to the first external system a value for a plurality of item names included in the first data corresponds to; Characterized by <1> The information processing device described. <3> The setting information includes a format definition in which a position where a value is arranged for each item name included in a form related to the setting information is defined; the form generation unit specifies a placement position in the form for a value corresponding to each item name included in the form related to the setting information based on the format definition included in the setting information associated with the first external system; Characterized by <2> The information processing device described. <4> The correspondence definition includes a definition in which two or more item names included in the data output by the external system corresponding to the correspondence definition correspond to one item name. Characterized by <2> or <3> The information processing device described. <5> An information processing system including a terminal device and an information processing device, The information processing device includes: a reception unit that receives, from the terminal device, a selection of a first external system which is any one of a plurality of external systems each outputting data including a plurality of items; a setting information identification unit that identifies setting information associated with the first external system from setting information for generating form data from data output by each of the external systems, the setting information being associated with each of the external systems and stored in advance; a form generating unit that generates form data corresponding to the first data output by the first external system using the specified setting information; An information processing system comprising: <6> A reception step of receiving a selection of a first external system which is one of a plurality of external systems each outputting data including a plurality of items; a setting information identification step of identifying setting information associated with the first external system from setting information for generating form data from data output by each of the external systems, the setting information being associated with each of the external systems and stored in advance; a form generation step of generating form data corresponding to the first data output by the first external system using the specified setting information; An information processing method characterized by being executed by a computer. <7> A reception step of receiving a selection of a first external system which is one of a plurality of external systems each outputting data including a plurality of items; a setting information identification step of identifying setting information associated with the first external system from setting information for generating form data from data output by each of the external systems, the setting information being associated with each of the external systems and stored in advance; a form generation step of generating form data corresponding to the first data output by the first external system using the specified setting information; A program characterized by causing a computer to execute the above. [Explanation of symbols]

[0146] 1. Information Processing Systems 10. Transaction Management Device 11 Reception 12 Registration Department 13 Collaboration Target Identification Department 14 Setting information identification part 15 Report generation section 16 Screen generation section 17 Response sender 20 Terminal Equipment 21 Display control unit 22 Request part 23 Response receiver 30 External Systems 100 Drive device 101 Recording media 102 Auxiliary storage 103 Memory device 104 CPU 105 Interface device 121 External system information storage unit 122 Tenant information storage unit 123 Import setting information storage unit 124 Default mapping definition storage section 125 Default format definition storage section 126 Tenant mapping definition storage unit 127 Tenant format definition storage unit 128 Tenant extension item definition storage section 129 Document information storage unit B Bus [Prior art documents] [Patent documents]

[0147] [Patent Document 1] JP 2012-022417 A

Claims

1. a reception unit that receives a selection of a first external system which is one of a plurality of external systems each outputting data including a plurality of items; a setting information identification unit that identifies setting information associated with the first external system from setting information for generating form data from data output by each of the external systems, the setting information being associated with each of the external systems and stored in advance; a form generating unit that generates form data corresponding to the first data output by the first external system using the specified setting information; 13. An information processing device comprising:

2. The setting information includes a correspondence definition that defines which of a plurality of item names included in a form related to the setting information corresponds to which of a plurality of item names included in data output by the external system corresponding to the setting information, the form generation unit identifies, based on the correspondence definition included in the setting information associated with the first external system, which item name among a plurality of item names included in a form related to the first external system a value for a plurality of item names included in the first data corresponds to; 2. The information processing apparatus according to claim 1,

3. The setting information includes a format definition in which a position where a value is arranged for each item name included in a form related to the setting information is defined; the form generation unit specifies a position in the form for a value corresponding to each item name included in the form related to the setting information based on the format definition included in the setting information associated with the first external system; 3. The information processing apparatus according to claim 2.

4. The correspondence definition includes a definition in which two or more item names included in the data output by the external system corresponding to the correspondence definition correspond to one item name.

3. The information processing apparatus according to claim 2.

5. An information processing system including a terminal device and an information processing device, The information processing device includes: a reception unit that receives, from the terminal device, a selection of a first external system which is one of a plurality of external systems each outputting data including a plurality of items; a setting information identification unit that identifies setting information associated with the first external system from setting information for generating form data from data output by each of the external systems, the setting information being associated with each of the external systems and stored in advance; a form generating unit that generates form data corresponding to the first data output by the first external system using the specified setting information; An information processing system comprising:

6. A reception step of receiving a selection of a first external system which is one of a plurality of external systems each outputting data including a plurality of items; a setting information identification step of identifying setting information associated with the first external system from setting information for generating form data from data output by each of the external systems, the setting information being associated with each of the external systems and stored in advance; a form generating step of generating form data corresponding to the first data output by the first external system using the specified setting information; An information processing method characterized by being executed by a computer.

7. A reception step of receiving a selection of a first external system which is one of a plurality of external systems each outputting data including a plurality of items; a setting information identification step of identifying setting information associated with the first external system from setting information for generating form data from data output by each of the external systems, the setting information being associated with each of the external systems and stored in advance; a form generating step of generating form data corresponding to the first data output by the first external system using the specified setting information; A program characterized by causing a computer to execute the above.

Images