WO2014199416A1

WO2014199416A1 - Form data management server and form data management program

Info

Publication number: WO2014199416A1
Application number: PCT/JP2013/003711
Authority: WO
Inventors: 敏文秋田
Original assignee: 株式会社アイ・ピー・エス
Priority date: 2013-06-13
Filing date: 2013-06-13
Publication date: 2014-12-18

Abstract

The present invention provides, through a simple process, data desired by a user in a business system (ERP system) which provides information relating to forms. A search condition specification screen (slip search screen) is provided with a data storage area selection region (cube selection region (601)) for selecting a business-associated form data storage area and an item selection region (mesh selection region (602)) for selecting one or more of pre-selected form items and/or one or more of pre-selected groups of form items as a unit for aggregation, wherein a form data management server (10) searches the form data stored in the selected business-associated form data storage area, for form data including the selected one or more form items and form data including the form items indicated by the selected one or more groups of form items, and generates search result data formed by aggregating the searched-for form data on a per aggregation unit basis.

Description

Form data management server and form data management program

The present invention is a server on which an ERP operates, a form data management server that provides various data via a communication network in response to a request from a user terminal used by a user, and a form mounted on the form data management server It relates to a data management program.

Conventionally, what is called ERP (Enterprise Resource Planning) has become the mainstream as package software for building a core business system in a company. The mission-critical business system (integrated mission-critical business system, ERP system) equipped with this ERP is often built on a relational database, and application programs that focus on business processing are designed. In many cases, the form output is operated without any focus.

Under these circumstances, various data warehouses that play a complementary role in mission-critical business systems for the purpose of processing large amounts of business data at high speed, analyzing business data in various ways, and outputting forms A system has been provided (see Patent Document 1).

Japanese Patent Laid-Open No. 2002-312208

In the system for managing information such as forms as described above, many types of forms are managed, and vast amounts of form data are managed, so simple processing that does not impose complicated selection operations. It has become a big problem to be able to provide data desired by the user.

An object of the present invention is to solve the above-described problems and provide data desired by a user through a simple process in a business system (ERP system) that provides information on a form.

The form data management server of the present invention is a server on which ERP operates, and forms generated for each business unit in a business process with respect to the user terminal via a communication network in response to a request from the user terminal used by the user. A form data management server for providing data, wherein the form data storage means includes a plurality of business-compatible form data storage areas each storing form data corresponding to the contents of each business in the business process; and the user A search condition designation screen providing means for providing a search condition designation screen for designating a search condition in response to a request from a terminal, and a search condition for receiving and receiving the search condition designated on the search condition designation screen from the user terminal Receiving form and form data satisfying the search condition received by the search condition receiving means; Form data search means for searching with reference to the data storage means, search result data generation means for generating search result data obtained by aggregating the form data searched by the form data search means, and generated by the search result data generation means A search result providing means for providing the user terminal with the search result data as a search result. The search condition designation screen includes a data storage area selection area for selecting the business correspondence form data storage area and a prepared in advance. An item selection area for selecting one or more of the form items and the form item group as a total unit, and the form data search means is stored in the selected business correspondence form data storage area. Among the form items of the form data, the form data including the selected form item and the form item indicated by the selected form item group. Searching data, the retrieval result data generating means, and generating a search result data aggregated by the count unit to form data retrieved by the form data retrieval means.

With the above configuration, the business system (ERP system) that provides information on the form can provide the data desired by the user with a simple process.

The search condition designation screen further includes a time range selection area for selecting a time range at the time of aggregation, and the search result data generation means selects the form data searched by the form data search means. It may be configured to generate search result data aggregated in the set time range.

The search result data generating means generates, for example, a form list as search result data.

The search condition specification screen further includes a detailed setting request reception area for receiving a request for detailed setting of the search condition, in response to the reception of the request for the detailed setting of the search condition from the user terminal. A detailed setting screen providing means for providing a detailed setting screen for performing detailed setting of the search condition, wherein the search condition receiving means receives the search condition including the detailed setting contents set in detail on the detailed setting screen It may be said.

The form data management program according to the present invention is a form data management program that causes the form data management server to execute a process of operating ERP and providing various data via a communication network in response to a request from a user terminal used by a user. The form data management server comprising a form data storage unit configured by a plurality of work-corresponding form data storage areas each storing form data corresponding to the contents of each business in the business process, A search condition designation screen providing process for providing a search condition designation screen for designating a search condition in response to a request from the user terminal, and a search for receiving and accepting the search condition designated on the search condition designation screen from the user terminal Condition reception process and form data that satisfies the search condition received in the search condition reception process A form data search process for referring to the form data storage means, a search result data generation process for generating search result data obtained by aggregating the form data searched in the form data search process, and the search result data generation A data storage area selection area for executing search result providing processing for providing the search result data generated in the process as a search result to the user terminal, and selecting the business correspondence form data storage area on the search condition designation screen And an item selection area for selecting one or more of the prepared form items and the form item group as an aggregation unit, and in the form data search process, the selected business correspondence form data storage area is provided. Among the form items of the form data stored in, the selected form item and the book including the form item indicated by the selected form item group A process for searching for data is executed, and the search result data generation process executes a process for generating search result data obtained by tabulating the form data searched in the form data search process in the tabulation unit. .

According to the present invention, data desired by a user can be provided by a simple process in a business system that provides information on a form.

It is a block diagram which shows the structural example of a form inquiry system. It is a block diagram which shows the structural example of a form data management server. It is a flowchart which shows the example of a slip data provision process. It is explanatory drawing which shows the example of a menu screen. It is explanatory drawing which shows the example of a slip search screen. It is a flowchart which shows the example of search condition reception processing. It is explanatory drawing which shows the example of a slip search screen. It is explanatory drawing which shows the example of a detailed setting reception screen. It is explanatory drawing which shows the example of a detailed setting reception screen. It is explanatory drawing which shows the example of a detailed setting reception screen. It is explanatory drawing which shows the example of a detailed setting reception screen. It is explanatory drawing which shows the example of a search result list display screen.

Hereinafter, an example of an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram showing a configuration example of a form inquiry system 500 according to an embodiment of the present invention. As shown in FIG. 1, the form inquiry system 500 includes a form data management server 10, a relay device 20, a plurality of user terminals 31 to 3N (N is an arbitrary positive integer), and an integrated core business system 100. Including.

The form data management server 10 and each of the user terminals 31 to 3N are connected to each other via a communication network 40 such as the Internet and the relay device 20. The form data management server 10 is connected to the integrated core business system 100 via a communication network 51 such as a LAN (Local Area Network) or a dedicated communication line. Note that user terminals may be configured to communicate with each other via a form data management server, or may be configured to be incapable of communication.

The integrated core business system 100 includes a core business server 110, a data warehouse server (DWH server) 120, and a slip data DB 101.

The integrated core business system 100 exhibits functions as an integrated core business system by communicating with the form data management server 10 (transmission and reception of various information) as necessary. A well-known technique is used for the core business server 110 provided in the core business system 100.

It is assumed that the core business server 110 and the DWH server 120 are connected by a dedicated communication line.

The core business server 110 is a server managed by, for example, the administrator of the form inquiry system 500, and has various functions for managing form information related to various kinds of work (for example, creation, update, storage, etc. of information). . The core business server 110 is configured by a general information processing apparatus including an OS (Operating System) and a relational DB.

Here, the form is a general term for books and slips. In addition, a book is a field in which items relating to cash and goods are entered, and a slip is data that is the basis for creating a book and is evidence of business transactions. In this example, the case where the core business server 110 handles only slip data as form data will be described as an example.

The core business server 110 executes various processes according to the business application program. Examples of the business application program include a sales business management program, a sales business management program, a production management program, a financial accounting management program, and a management accounting management program.

The DWH server 120 is a server managed by a system administrator of this system, for example, and has various functions for realizing a data warehouse. Here, the data warehouse refers to a system that analyzes the relationship between items from business data such as form data accumulated in time series. The DWH server 120 also has a function of registering various data in a predetermined storage area by converting a CSV file transferred from the core business server 110 into a predetermined data format. Note that the DWH server 120 may be configured to extract data corresponding to each storage area from the CSV format state without converting the data format.

The slip data DB 101 stores various form data collected and organized by various information processing using various business application programs (programs stored in a business application program DB (not shown) included in the integrated core business system 100). It is a medium. In the slip data DB 101, for example, the slip data corresponding to the order slip is associated with the order slip header information, the order slip detail information, the delivery date schedule, etc., and has a structure that can be searched based on the key such as the slip number. Remembered.

In addition, the core business server 110 converts various data stored in the slip data DB 101 to CSV according to predetermined extraction conditions.
(Comma Separated Values) has a function of converting to a form data management server 10 and transmitting it to the form data management server 10. In this example, the core business server 110 transfers a data file in the CSV format by FTP (File Transfer Protocol) to the form data management server 10.

The form data management server 10 is a server on which ERP operates, and is a server that provides various data via a communication network in response to requests from user terminals 31 to 3N used by users. The form data management server 10 is configured by an information processing apparatus such as a WWW server, for example, and is managed by a system administrator of the form inquiry system 500.

FIG. 2 is a block diagram illustrating a configuration example of the form data management server 10. As shown in FIG. 2, the form data management server 10 realizes functions as a control unit 11 that performs various controls, a business application program DB 17, a slip data DB 18, a DWHDB 19, and a general core business server. And other DB 10X for storing various data necessary for the data (for example, data used by various programs stored in the business application program DB 17). Since the other DB 10X is not particularly related to the present invention, detailed description thereof is omitted. The control unit 11 includes a slip data provision processing unit 11a that executes processing for providing slip data to the user terminals 31 to 3N.

The business application program DB 17 is a storage medium that stores programs used for various businesses. Programs stored in the business application program DB 17 include a sales business management program, a purchasing business management program, a production management program, a financial accounting management program, and a management accounting management program.

The slip data DB 18 is a storage medium for storing various form data collected and organized by various information processing using various programs stored in the business application program DB 17. In this example, the slip data DB 18 is a database that stores the slip data transferred from the core business server 110 in a predetermined format, and includes a plurality of cubes.

Each cube stores form data according to the contents of each business for each business unit in the business process according to the business application program. That is, for each cube, for example, form data corresponding to the contents of each business such as order slip details, shipping slip details, delivery slip details, order slip details is stored.

It should be noted that a cube may be provided in which form data corresponding to the related business content for each related business that is shown by integrating the content of a predetermined related business across a plurality of business units is stored. In other words, for example, a cube may be provided in which form data indicating integrated contents of predetermined related tasks (orders related to orders, shipments, and deliveries) such as order shipment and delivery is stored.

In other words, each cube contains form data corresponding to the contents of each work for each work unit in the work process, and related work contents for each related work shown by integrating the contents of predetermined related work across multiple work units. The form data of each classification classified according to the business contents, such as the corresponding form data, is stored.

In each cube, items generally provided for the corresponding form data (for example, for the slip data corresponding to the order slip, items such as order slip header information, order slip detail information, and delivery schedule). It is stored in a structure in which each item is associated so that it can be searched based on the key such as the slip number, etc. The order number, order number, shipping number, receipt / exit number, invoice inquiry, billing number, Data including accounting number etc.) is stored.

The form data management server 10 provides various data stored in the slip data DB 18 and other DB 10X in response to requests from predetermined external devices, in this example, the user terminals 31 to 3N and the integrated core business system 100. Have That is, the form data management server 10 has a function as a core business server. In other words, the form data management server 10 includes an ERP engine.

Although not shown, in this example, the form data management server 10 has a function as a DWH server having various functions for realizing a data warehouse. The form data management server 10 includes an ERP engine and a configuration for functioning as a DWH server, so that an integrated core business system having different configurations (for example, an integrated core business having both a core business server and a DWH server) In addition to the system 100, for example, an integrated core business system having only a DWH server and an integrated core business system having only a DWH server) can be provided with information required for the integrated core business system. become.

Each of the user terminals 31 to 3N is an information processing apparatus such as an Ipad (registered trademark) including a CPU (Central Processing Unit), a ROM, a RAM, and a display unit. In this example, it is assumed that each of the user terminals 31 to 3N has various applications that can be used for handling the form data, such as a Web browser. Further, in this example, each of the user terminals 31 to 3N receives, for example, a query for acquiring necessary form data (process flow data in this example) from the form data management server 10 in response to an operation input by the user. (Search items, search keys, extraction keys, etc.) are defined and transmitted to the form data management server 10. In addition, the user terminals 31 to 3N have QR codes (Quick
It is assumed that code readers (or code reader functions) 31a to 3Na for reading various codes such as (Response Code) are provided.

In this example, each of the user terminals 31 to 3N communicates with the form data management server 10 via the relay device 20 and the communication network 40, and the data acquired from the form data management server 10 is, for example, a predetermined web application (web browser). ) Etc., and the function of outputting to the display unit.

Next, the operation of the form inquiry system 500 of this example will be described with reference to the drawings. Note that the contents of operations and processes not particularly related to the present invention may be omitted.

FIG. 3 is a flowchart showing an example of slip data providing processing executed by the form data management server 10 or the like in the form inquiry system 500 of this example. Here, a case will be described as an example where the form data management server 10 provides slip data in response to a request from the user terminal 31 used by the user X.

In the slip data providing process, first, the user terminal 31 accepts a login request by the login operation of the user X (step S101). As this login operation, for example, a password input operation set in advance may be considered. When login to the user terminal 31 is permitted, various operations for using various functions installed in the user terminal 31 are permitted.

When a predetermined login operation is executed by the user X while the user X is logged in the user terminal 31, the user terminal 31 accesses the form data management server 10 and obtains a login screen. Then, a login request is made by designating information necessary for login (for example, a preset user ID and password) on the login screen (step S102). This login request is made, for example, by presenting predetermined information (for example, an electronic certificate issued to the user X) used for predetermined login determination in addition to the user ID and password. In addition, when logging in to the form data management server 10, the user X may specify a group (for example, Japanese) used in a group to which the user belongs and various screens.

When the form data management server 10 receives the login request, the form data management server 10 determines whether or not to permit the login (step S103). This determination may be made based on, for example, an ID, a password, or an electronic certificate.

If the form data management server 10 determines that login is permitted (Y in step S103), the form data management server 10 sets the user terminal 31 to the login state. When the login state is set, the form data management server 10 transmits menu screen information indicating the menu screen to the user terminal 31 (step S104). If it is determined that login is not permitted (N in step S103), the form data management server 10 ends the slip data providing process without setting the user terminal 31 in the login state. If it is determined that login is not permitted, the form data management server 10 performs processing to notify the user terminal 31 to that effect.

When the menu screen information is received, the user terminal 31 displays the menu screen indicated by the received menu screen information on the display unit included in the user terminal 31 (step S105).

FIG. 4 is an explanatory diagram showing an example of a menu screen. As shown in FIG. 4, the menu screen displays a menu layout circle MC on which menu buttons M1 to M6 each displaying names of a plurality of selectable menus are arranged on a substantially circumference. A display area 501 is provided. Further, as shown in FIG. 4, the menu arrangement circle display area 501 is provided with a title display area MA arranged in the center area of the circle formed by the menu arrangement circle MC and displaying the title of the menu arrangement circle MC. Yes. Here, as menu buttons M1 to M6, slip search button M1 that is pressed when searching for slips, new slip button M2 that is pressed when creating new slips, and expense that is pressed when inputting expenses. An input button M3, a master registration button M4 that is pressed when registering a master, a DWH button M5 that is pressed when registering data in the DWHDB 19, and an inventory inquiry button M6 that is pressed when inquiring about inventory information Is provided.

On the menu screen displayed on the display unit of the user terminal 31 on which the touch panel is arranged, the user X presses one of the menu buttons M1 to M6 by a touch operation (operation touching with a finger). In this example, it is assumed that the slip search button M1 is pressed. The processing when the other menu buttons M2 to M6 are pressed is omitted here.

When the slip search button M1 is pressed on the menu screen, the user terminal 31 transmits to the form data management server 10 that the slip search button M1 has been pressed to the form data management server 10 as a menu selection result ( Step S106).

When the menu selection result indicating that the slip search button M1 is pressed is received, the slip data provision processing unit 11a of the form data management server 10 displays slip search screen information indicating a slip search screen for specifying a slip search condition as a user terminal. 31 (step S107).

When the slip search screen information is received, the user terminal 31 displays the slip search screen indicated by the received slip search screen information on the display unit provided therein (step S108), and executes search condition reception processing (step S200).

FIG. 5 is an explanatory diagram showing an example of a slip search screen. As shown in FIG. 5, on the slip search screen, a cube selection area 601 for selecting a cube or cube group to be searched, and a mesh indicating a form data item or a group of items predetermined as an aggregation unit are selected. A mesh selection area 602 for selecting, a time range selection area 603 for selecting a time axis (time range) as a totaling unit, a detailed setting area 604 for setting a detailed search condition or a totaling condition, and pressing when making a search request An execution button 605 to be executed and a specification button 606 to be pressed when specification is performed are provided. “Specification” means that each slip data is uniquely assigned to the data in the search result list in order to specify the original slip (slip data that has not been tabulated) for the data shown in the search result list that is aggregated in mesh units. This means that an added identification number (for example, a slip number) is added. In this example, since it has a specification function, it is necessary to analyze the list of search results aggregated in mesh units and check the details (such as abnormal values, large differences between schedules and actual results, etc. Data) can be easily confirmed on the original slip.

In the cube selection area 601, as shown in FIG. 5, a sales system selection button for selecting a cube in which sales form data is stored, a purchasing system selection button for selecting a cube in which purchasing form data is stored, Manufacturing system selection button that selects a cube that stores manufacturing form data, Payment system selection button that selects a cube that stores receiving form data, and Accounting that selects a cube that stores accounting form data Various selection buttons such as a system selection button are provided.

As shown in FIG. 5, the mesh selection area 602 is provided with various selection buttons for selecting a large classification mesh, an item mesh, a supplier mesh, and an organization mesh. A plurality of various selection buttons provided in the mesh selection area 602 can be selected simultaneously.

In the time range selection area 603, as shown in FIG. 5, various selection buttons for selecting day, week, month, and year as a time axis are provided.

The detail setting area 604 includes a mesh detail button that is pressed when setting the mesh details for narrowing the search condition for the mesh selected in the mesh selection area 602, and detailed search conditions for various numeric items in the slip data. Numerical value button that is pressed when setting, Date definition button that is pressed when setting detailed search conditions for various date items in the slip data, and pressed when setting other detailed search conditions The extraction condition button is provided.

By selecting three types of cubes, meshes, and time axes as main selection targets for determining search conditions, the selection targets can be displayed in a compact manner as shown in FIG. Depending on the display screen size of the display device, all selection targets can be displayed on one screen. The selection items arranged in each selection area are examples, and other selection items may be included, for example.

On the slip search screen, the user X selects one of the cubes arranged in the cube selection region 601 by a touch operation, and selects one or more meshes among the meshes arranged in the mesh selection region 602. To do.

Specifically, the user X depresses one of the selection buttons arranged in the cube selection area 601 to select a search target cube, and one of the selection buttons arranged in the mesh selection area 602. Alternatively, two or more selection buttons are pressed to select which form item is searched and extracted in the form data (determined by selecting the cube) to be searched.

Then, on the slip search screen, the user X selects one of the time axes arranged in the time range selection area 603 as necessary. Specifically, the user X selects a time axis at the time of aggregation by pressing any of the selection buttons arranged in the time range selection area 603.

In the search condition receiving process (step S200), as shown in FIG. 6, the user terminal 31 receives selection of a cube by the touch operation of the user X (step S201), and at least one or more by the touch operation of the user X A mesh selection is accepted (step S202).

Next, the user terminal 31 accepts selection of a time axis by the touch operation of the user X (step S203). Note that this time axis may not be accepted at the request of the user X. In this case, it is only necessary that the user X does not select the time axis. Further, the time range selection area 603 may not be provided on the slip search screen.

FIG. 7 is an explanatory diagram showing an example of a slip search screen in a state where a cube or the like is selected. In the example illustrated in FIG. 7, a sales result is selected as a cube, an item and an order-receiving party are selected as a mesh, and a week is selected as a time axis.

In this example, more detailed settings can be made. On the slip search screen, the user X presses any one of the mesh detail button, numerical value detail button, date definition button, and extraction condition button provided in the detail setting area 604 as necessary.

When the mesh detail button is pressed, the user terminal 31 displays a detail setting reception screen as shown in FIG. 8, for example. As shown in FIG. 8, in the detailed setting reception screen (mesh details), a selection area 701 for selecting a detailed item to be searched and a display area in which the detailed item selected in the selection area 701 is displayed. 702, a change button 703 that is pressed when executing detailed settings, and a cancel button 704 that is pressed when canceling detailed settings are provided.

FIG. 8 shows a detail setting reception screen that is displayed in response to pressing of the mesh detail button when an item and an order-receiving party are selected as a mesh (see FIG. 7). On the detail setting reception screen, the user X performs a setting operation for setting details about items and business partners. Then, the user X presses the change button 703 when executing the detailed setting. When the change button 703 is pressed, the user terminal 31 accepts detailed settings (step S204).

When the numerical detail button is pressed, the user terminal 31 displays a detailed setting reception screen as shown in FIG. 9, for example. As shown in FIG. 9, the detailed setting reception screen (numerical details), as shown in FIG. 9, a selection area 801 for selecting a detailed item to be searched, and a display area in which the detailed items selected in the selection area 801 are displayed. 802, a change button 803 that is pressed when executing detailed settings, and a cancel button 804 that is pressed when canceling detailed settings are provided.

On the detailed setting reception screen (numerical value details), the user X performs a setting operation for setting details about the numerical values. Then, the user X presses the change button 803 when executing the detailed setting. When the change button 803 is pressed, the user terminal 31 receives detailed settings (step S204).

When the date definition button is pressed, the user terminal 31 displays a detailed setting reception screen as shown in FIG. 10, for example. In the detailed setting reception screen (date definition), as shown in FIG. 10, a selection area 901 for selecting a detailed item to be searched, a change button 903 to be pressed when executing detailed setting, and a detail A cancel button 904 that is pressed when the setting is canceled is provided.

In the detailed setting reception screen (date definition), user X performs a setting operation for setting details about the date. Then, the user X presses the change button 903 when executing the detailed setting. When the change button 903 is pressed, the user terminal 31 receives detailed settings (step S204).

When the extraction condition button is pressed, the user terminal 31 displays a detailed setting reception screen as shown in FIG. 11, for example. As shown in FIG. 11, the detailed setting reception screen (extraction condition) has an input area 1001 for setting and inputting details of the search (extraction) condition, and a selection area 1002 for inputting a detailed item to be searched. A change button 1003 that is pressed when executing the detailed setting, and a cancel button 1004 that is pressed when canceling the detailed setting.

In the detailed setting reception screen (extraction condition), the user X performs a setting operation for setting details about the extraction condition. Then, the user X presses the change button 1003 when executing the detailed setting. When the change button 1003 is pressed, the user terminal 31 accepts detailed settings (step S204).

It should be noted that the detailed setting is arbitrarily set according to the desire of the user X, and the processing and operation regarding the detailed setting may not be performed. If the detailed setting is executed, the screen returns to the slip search screen (see FIG. 7).

When the selection / setting of the search condition is completed on the slip search screen, the user X presses the execution button 605 by a touch operation.

When the search button 605 is pressed with the search condition selected / set, the user terminal 31 accepts the search execution selection (step S205), presents the selected / designated search condition, and the form data management server A search request is made to 10 (step S109).

When the form data management server 10 receives the search request, the form data management server 10 refers to the slip data stored in the slip data DB 18 and searches for slip data that matches the search conditions presented by the received search request (step S110). .

When the slip data is searched according to the search condition, the form data management server 10 generates search result list display screen information indicating a search result list display screen for displaying a list of searched slip data as a search result (step S110a). In step S110a, the form data management server 10 aggregates the retrieved slip data in the aggregation unit indicated by the mesh specified as the search condition, and if the time axis is specified as the search condition, the specified time axis The search result list display screen information indicating the search result list display screen aggregated in step S is generated.

When the search result list display screen information is generated, the form data management server 10 transmits the generated search result list display screen information to the user terminal 31 (step S111).

When the search result list display screen information is received, the user terminal 31 displays the search result list display screen indicated by the received search result list display screen information on the display unit provided therein (step S112).

FIG. 12 is an explanatory diagram showing an example of a search result list display screen. As shown in FIG. 12, the search result list display screen is provided with a display area 1101 for displaying search results and a return button B1 that is pressed when returning to the previous screen. When the slip number on the search result list display screen is selected by a touch operation, the user terminal 31 transmits an acquisition request for the corresponding slip data to the form data management server 10. The form data management server 10 refers to the slip data DB 18 in response to the slip data acquisition request and transmits the corresponding slip data to the user terminal 31. Then, the user terminal 31 displays the received slip data on the display screen of the display unit.

When an operation for ending access such as an operation for ending the browser by the user X is performed on the search result list display screen (Y in step S113), the user terminal 31 makes a request to the form data management server 10. A logout request is made (step S114). If an operation for continuing access such as pressing the return button B1 is performed (N in step S113), the user terminal 31 proceeds to the process in step S108 and displays a slip search screen (see FIG. 7). indicate. In this case, the user terminal 31 is configured to display a slip search screen in a state where the previous search condition is selected and designated, and the user terminal 31 accepts a change in part or all of the search criteria by the operation of the user X on the slip search screen. It may be. When a search condition that has been partially or wholly changed is received, the user terminal 31 makes a search request by presenting the search condition by the same process as described above.

When the search result list display screen information is transmitted in step S111, the form data management server 10 starts measuring the time (waiting time) during which no information is exchanged with the user terminal 31, and this waiting time is predetermined. It is monitored whether or not a time (for example, 5 minutes, 10 minutes, 30 minutes, etc.) has elapsed (a predetermined time has been reached) (step S115).

When the logout request is received during the measurement of the standby time (Y in step S116), the form data management server 10 stops the measurement of the standby time and performs a logout process for releasing the login state (step S117).

If it is determined that the predetermined time has elapsed (Y in step S115), the form data management server 10 ends the measurement of the standby time and performs logout processing for releasing the login state (step S117). ).

As described above, the form data management server 10 receives a request for providing a list of slip data from the user terminal 31, and executes a process of providing a list of slip data extracted and aggregated according to the request. Is done.

In the above example, the case where an item and an order-receiving party are selected as a mesh has been described as an example. However, as another specific example, a case where a project is selected as a mesh will be described. When a project that is classified as a mesh is selected, the slip data (the project item is included in the slip data, and any project (project name) is included in the slip data). Search result list information indicating a search result list in which the set slip data) is tabulated for each project is generated (see step S110a), and the generated search result list is displayed (step S110a). (See S112). For example, when the sales record is selected as a cube, the sales record data is aggregated for each project and displayed in the search result list. For example, when purchase results are selected as cubes, purchase result data is aggregated for each project and displayed in a search result list.

“Project” is a code that is assigned to a plan or work to achieve some goal, and it is possible to browse a search result list that summarizes costs and progress in this aggregation unit. This is a great advantage for users.

As described above, in the above-described embodiment, a server on which ERP operates, and a business process is performed on the user terminal 31 via the communication network 40 in response to a request from the user terminal 31 used by the user. The form data management server 10 that provides the form data generated for each business unit in the system is composed of a plurality of business-compatible form data storage areas (cubes) in which the form data corresponding to the contents of each business in the business process is stored. A search condition specification screen (slip search screen) for specifying a search condition in response to a request from the user terminal 31, and the search condition specified on the search condition specification screen from the user terminal 31. The form data that is received and accepted, and that satisfies the accepted search conditions is detected with reference to the slip data DB 18. Then, search result data (search result list display screen information) obtained by tabulating the searched form data is generated, and the generated search result data is provided to the user terminal 31 as a search result. , A data storage area selection area (cube selection area 601) for selecting a business correspondence form data storage area, and an item selection area (mesh) for selecting one or more of the previously prepared form items and form item groups as aggregation units A selection area 602), and includes a selected form item and a form item indicated by the selected form item group among the form items of the form data stored in the selected business-compatible form data storage area. Since it is configured to search for form data and generate search result data obtained by aggregating the searched form data in the aggregation unit, In business system (ERP system) that provides that information, the user will be able to provide a desired data by a simple process.

In other words, the search condition designation screen includes a data storage area selection area (cube selection area 601) for selecting a business-compatible form data storage area, and one or more of the previously prepared form items and form item groups as aggregation units. An item selection area (mesh selection area 602) to be selected is provided, and the form data management server 10 selects one of the form data of the form data stored in the selected business correspondence form data storage area. It is configured to search for form data including form items and form items indicated by the selected form item group, and to generate search result data obtained by aggregating the searched form data in an aggregation unit. The search result data (search result list display screen information) aggregated in the aggregation unit desired by the user is easily generated and provided. So that it is able to. For the user, by specifying the business-related form data storage area in the data storage area selection area (cube selection area 601), the type of form data (business type in the business process) to be searched is specified, and the item is selected. The search result data in which the desired form data is aggregated in the desired aggregation unit can be obtained by a simple operation of simply specifying the form item or the form item group as the aggregation unit in the area (mesh selection area 602). become.

In particular, since the item selection area (mesh selection area 602) for selecting one or more of the form items and the form item group as the aggregation unit is provided on the search condition designation screen, the user needs to consider the aggregation unit. Therefore, it is possible to obtain search result data aggregated in a desired aggregation unit with a simple operation of simply selecting a preset aggregation unit. In addition, the user terminal 31 accepts a change in part or all of the search conditions by the operation of the user X on the search screen (see step S200), and presents the changed search conditions and makes a re-search request (see step S109). The form data management server 10 searches for data as necessary under the changed search conditions (see step S110: if the previously searched data can be used, the data is used without searching again). If the search result list display screen information is generated and transmitted (see steps S110a and S111), the search result list searched and aggregated according to the changed search condition is displayed (step S112). See). For example, after the search result list is displayed, it is possible to easily change the mesh selection and display the search result list aggregated in another aggregation unit for the same cube. That is, for example, a user can easily obtain and view a list of search results tabulated in various tabulation units by a simple operation of selecting a mesh again and pressing an execution button 605. Data useful for analyzing contents can be easily obtained.

In the same way, it is possible to change the cube selection at the same time as the mesh, and it is also possible to change only the cube selection. It is possible to easily display the search result list. In this case as well, useful data can be easily obtained for the user in order to analyze the business content.

In the above-described embodiment, the search condition designation screen is further provided with a time range selection area (time axis selection area 603) for selecting a time range at the time of tabulation. If the search result data is generated by collecting the searched form data in the selected time range, the search result data (search result list display screen information) collected in the time range desired by the user is used. It can be easily generated and provided.

In the above-described embodiment, the form data management server 10 is configured to generate a form list as search result data, so that the form is composed of items desired by the user and aggregated in the aggregation unit desired by the user. A list (search result list) can be easily generated and provided.

In the above-described embodiment, the search condition designation screen is further provided with a detailed setting request reception area for receiving a request for detailed setting of the search condition, and the form data management server 10 sets the detailed setting of the search condition. Is configured to provide a detailed setting screen for performing detailed setting of the search condition in response to the notification of acceptance of the user's request from the user terminal 31, and to accept the search condition including the detailed setting content set in detail on the detailed setting screen Therefore, detailed search conditions desired by the user can be easily specified, and various search result data desired by the user can be generated and provided.

Although not particularly mentioned in the above-described embodiment, the form data management server 10 performs each of the above-described processes (see FIG. 3) according to a processing program (form data management program) stored in a storage medium provided in the form data management server 10. ). Further, the user terminals 31 to 3N execute the above-described processes (see FIGS. 3 and 6) in accordance with a processing program (form data management program) stored in a storage medium included in the user terminals 31 to 3N.

According to the present invention, in a business system (ERP system) that provides information on a form, it is useful for providing data desired by a user through simple processing.

DESCRIPTION OF SYMBOLS 10 Form data management server 20 Relay machine 31-3N User terminal 40 Communication network 51 Communication network 100 Integrated core business system 110 Core business server 120 DWH server 500 Form inquiry system

Claims

A form data management server that is an ERP server and provides form data generated for each business unit in a business process to a user terminal via a communication network in response to a request from a user terminal used by a user. There,
Form data storage means configured by a plurality of business-compatible form data storage areas each storing form data corresponding to the contents of each business in the business process;
A search condition designation screen providing means for providing a search condition designation screen for designating a search condition in response to a request from the user terminal;
Search condition receiving means for receiving and receiving the search condition specified on the search condition specifying screen from the user terminal;
Form data search means for searching for form data satisfying the search condition received by the search condition reception means with reference to the form data storage means;
Search result data generating means for generating search result data obtained by tabulating form data searched by the form data searching means;
Search result providing means for providing the search result data generated by the search result data generating means to the user terminal as a search result;
The search condition designation screen includes a data storage area selection area for selecting the business-compatible form data storage area, and an item selection area for selecting one or more of the previously prepared form items and form item groups as an aggregation unit. And is provided,
The form data search means searches for form data including the selected form item and the form item indicated by the selected form item group among the form items of the form data stored in the selected business correspondence form data storage area. And
The form data management server, wherein the search result data generation means generates search result data obtained by counting the form data searched by the form data search means in the total unit.
The search condition designation screen further includes a time range selection area for selecting a time range at the time of aggregation,
The form data management server according to claim 1, wherein the search result data generation unit generates search result data obtained by aggregating the form data searched by the form data search unit in a selected time range.
The form data management server according to claim 1, wherein the search result data generation unit generates a form list as search result data.
The search condition designation screen further includes a detailed setting request receiving area for receiving a request for detailed setting of the search condition.
A detailed setting screen providing means for providing a detailed setting screen for performing detailed setting of a search condition in response to notification of reception of a request for detailed setting of a search condition from the user terminal;
The form data management server according to any one of claims 1 to 3, wherein the search condition accepting unit accepts a search condition including detailed setting contents set in detail on the detailed setting screen.
A form data management program for operating a ERP and causing a form data management server to execute processing for providing various data via a communication network in response to a request from a user terminal used by a user,
In the form data management server provided with form data storage means configured by a plurality of work-corresponding form data storage areas each storing form data corresponding to the contents of each work in the business process,
A search condition designation screen providing process for providing a search condition designation screen for designating a search condition in response to a request from the user terminal;
A search condition receiving process for receiving and receiving a search condition specified on the search condition specifying screen from the user terminal;
A form data search process for searching for form data satisfying the search condition received in the search condition reception process with reference to the form data storage unit;
A search result data generation process for generating search result data obtained by tabulating the form data searched in the form data search process;
A search result providing process for providing the search result data generated in the search result data generating process to the user terminal as a search result;
The search condition designation screen includes a data storage area selection area for selecting the business-compatible form data storage area, and an item selection area for selecting one or more of the previously prepared form items and form item groups as an aggregation unit. And is provided,
In the form data search process, the form data including the selected form item and the form item indicated by the selected form item group is searched from the form data of the form data stored in the selected business correspondence form data storage area. Execute the process to
In the search result data generation process, a form data management program for executing a process of generating search result data obtained by tabulating the form data searched in the form data search process in the total unit.