JPWO2013114449A1 - Mobile terminal management server and mobile terminal management program - Google Patents

Abstract

In a business system that provides information on a form to a mobile communication terminal, the processing load required for data retrieval is reduced, and effective information is output quickly. The mobile terminal management server 10 on which the ERP operates receives the specified search condition from the mobile terminal 31 and receives it, and stores the stock related data including the items related to the stock management of the product indicated by the received search condition in the process flow data table PT. The inventory management information extracted from the stored process flow data, including the inventory transition of the product indicated by the specified search condition based on the inventory related data is generated, and the generated inventory management information is provided to the portable terminal 31.

Description

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

  Conventionally, what is called ERP (Enterprise Resource Planning) has become 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).

  In such a form inquiry system for the purpose of outputting a form, one that provides information such as a form to a mobile communication terminal (mobile terminal) has been proposed (see Patent Document 2-3).

Japanese Patent Laid-Open No. 2002-312208 Japanese Patent Laid-Open No. 2003-323582 JP 2007-2001136 A

  In a conventional ERP system, data acquired in each business process (including data input by a user and data calculated from various data) is registered and managed in a dedicated data table (table). Yes. That is, in the conventional ERP system, the table to be updated is different for each input process such as an order or a shipping instruction. The “input process” means a process of inputting various data acquired (or determined) by an ERP system administrator or the like in each business process to each table.

  FIG. 14 is an explanatory diagram for explaining an example of a table configuration in a conventional ERP system. For example, when a business flow (process flow) composed of a plurality of business processes indicates “inventory sales”, there are five input processes: order receipt, shipping instruction, delivery, inspection, and sales. In this case, the table for storing the data related to the process flow of “inventory sales” is, for example, as shown in FIG. 14A to FIG. , An acceptance table, and a sales table.

  That is, in the conventional ERP system, the table to be updated is different for each input process. For this reason, the correspondence between a plurality of business processes belonging to the same process flow is an identifier (in FIG. 14, the order number and order details in the shipping instruction table, the delivery table, and the like). The shipping instruction number and the shipping instruction details, etc.) are given.

  Therefore, in the conventional ERP system, for one input process, it is necessary to specify a table according to the type of the input process and input an identifier of another corresponding process data. That is, for example, in the case shown in FIG. 14, the process data specified by the order number “A00001” and the order detail number “0010” (that is, the same column as the order number “A00001” and the order detail number “0010” in the order table). When the process data related to the business process “shipment instruction” related to the various data stored in the ERP system is registered in the database included in the ERP system, the shipping instruction for specifying the process data as the process data related to the business process “shipment instruction” The order number “A00001” and the order received together with the number, the shipping instruction detail number, the type indicating the type of the business process, and the data indicating the contents of the business process (for example, the order recipient, quantity, amount, shipping instruction date, shipping text, etc.) Register the item number “0010” in the shipping instruction table. There was a need. This has a problem from the viewpoint of efficient data processing, for example, the same data (for example, orders, quantity, amount, etc.) is registered in a plurality of tables.

  As in the case of data registration, in the conventional ERP system, when trying to search various data stored in various tables in response to a user request, for example, the necessary process data is traced by tracing the identifier of the process data. Since it is necessary to search and acquire data that matches the search conditions separately from various tables, there is a problem that the processing load required for the search becomes excessive.

  As described above, in the conventional ERP system, the processing load when searching for various data stored in various tables becomes large. Therefore, when various data is extracted and various information processing is performed, Since the processing load becomes excessive, there is a problem that effective information cannot be quickly output by information processing.

  In particular, when providing information in response to a request from a mobile communication terminal (mobile terminal), the speed of the response speed is required, and thus the above problem becomes significant.

  The present invention eliminates the above-described problems, reduces the processing load required for data processing in the business system and provides effective information in a business system (ERP system) that provides information related to forms to a mobile communication terminal (mobile terminal). The purpose is to enable quick output.

  The mobile terminal management server of the present invention is a server on which ERP operates, and is a mobile terminal management server that provides various data via a communication network in response to a request from a mobile terminal used by a user. Process flow data storage means for storing process flow data including various data relating to the process flow including the process, the process flow data being data including status data, common data, and process specific data, and the status The data is data indicating the progress status of each of a plurality of business processes included in the process flow, the common data is data common to business processes included in the same process flow, and the process-specific data is , Each business professional included in the same process flow The process flow data includes inventory-related data including quantity data indicating the quantity related to the product inventory, and the search condition is set in response to a request from the mobile terminal. A condition specifying screen providing means for providing a condition specifying screen to be specified, a search condition receiving means for receiving and receiving a search condition specified on the condition specifying screen from the portable terminal, and the search condition receiving means Inventory-related data extracting means for extracting inventory-related data including items relating to product inventory management indicated by the search conditions from process flow data stored in the process flow data storage means, and specified based on the inventory-related data Inventory management information generating means for generating inventory management information including the inventory transition of the product indicated by the search condition, and the inventory management information generation And inventory management information providing means for providing the inventory management information generated by the means to the portable terminal.

  With the above configuration, it is possible to reduce the processing load required for data processing in the business system and to output effective information quickly in a business system that provides information related to forms to mobile communication terminals. become.

  Quantity to be registered in the process flow data by specifying the quantity data related to the relevant business process when registering the form data for the business process of production receipt, production delivery, receipt, or delivery in the process flow data The data registration unit may be included.

  The quantity data may be configured to include a scheduled receipt quantity, a scheduled delivery quantity, an actual receipt quantity, and an actual delivery quantity.

  The inventory management information may be configured to include an item, a required date, a planned receipt quantity, a planned delivery quantity, an actual receipt quantity, an actual delivery quantity, and an inventory transition.

  Also, the mobile terminal management program of the present invention operates the ERP, and makes the mobile terminal management server execute processing for providing various data via a communication network in response to a request from the mobile terminal used by the user. The portable terminal management server includes a process flow data storage unit that stores process flow data including various data related to a process flow including a plurality of business processes, and the process flow data includes status data, , Common data and process specific data, the status data is data indicating the progress of each of the plurality of business processes included in the process flow, and the common data is in the same process flow. Data common to the business processes involved The process-specific data is data specific to each business process included in the same process flow, and the process-flow data includes inventory-related data including quantity data indicating a quantity related to product inventory. , A condition designation screen providing process for providing a condition designation screen for designating a search condition in response to a request from the portable terminal to the portable terminal management server, and a search condition designated on the condition designation screen. Process flow data stored in the process flow data storage means including search condition reception processing received and received from the product, and inventory related data including items relating to product inventory management indicated by the search conditions received in the search condition reception processing Inventory-related data extracting means for extracting from the inventory-related data and a search condition designated based on the inventory-related data Inventory management information generation processing for generating inventory management information including inventory transition of goods, and inventory management information provision processing for providing the mobile terminal with the inventory management information generated by the inventory management information generation processing Is.

  ADVANTAGE OF THE INVENTION According to this invention, in the business system which provides the information regarding a form to a mobile communication terminal, the processing load required for the data processing in a business system can be reduced, and effective information can be output rapidly. .

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 portable terminal management server. It is explanatory drawing which shows the example of the storage state of process flow data. It is explanatory drawing which shows the example of stock related data. 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 explanatory drawing which shows the example of a slip search screen. It is explanatory drawing which shows the example of the whole structure of the selection item arrangement | positioning circle displayed on a slip search screen. It is explanatory drawing which shows the example of a search result list display screen. It is a flowchart which shows the example of a stock management information provision process. It is explanatory drawing which shows the example of a condition designation | designated screen. It is explanatory drawing which shows the example of a stock management information display screen. It is explanatory drawing for demonstrating the example of the table structure in the conventional ERP system.

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 mobile terminal management server 10, a relay device 20, a plurality of mobile terminals 31 to 3N (N is an arbitrary positive integer), an integrated core business system 100, The integrated core business system 200 and the integrated core business system 300 are included.

  The mobile terminal management server 10 and the mobile terminals 31 to 3N are connected to each other via a communication network 40 such as the Internet and the relay device 20, respectively. The mobile terminal management server 10 is connected to the integrated core business system 100, the integrated core business system 200, and the integrated core business system 300 via communication networks 51, 52, and 53 such as a LAN (Local Area Network) and a dedicated communication line, respectively. Is done. In addition, it is good also as a structure which can communicate between portable terminals and integrated core business systems via a portable terminal management server, and is good also as a structure which cannot communicate.

  The integrated core business system 100 includes a core business server 110, a data warehouse server (DWH server) 120, and a process flow DB 101. The integrated core business system 200 includes a DWH server 220 and a process flow DB 201. The integrated core business system 300 includes a core business server 310 and a process flow DB 301.

  A plurality of integrated core business systems 100, 200, and 300 having different configurations are integrated by performing communication (transmission and reception of various types of information) with the mobile terminal management server 10 as necessary (that is, according to the functions of each). Demonstrate functions as a core business system. In other words, in the form inquiry system, even if the system 200 does not have a mission-critical server or the system 300 does not have a DWH server, by communicating with the mobile terminal management server 10, The function of can be demonstrated. Although not shown, even a system that does not have a process flow DB can exhibit functions as an integrated core business system by storing process flow data in the mobile terminal management server 10. Since a well-known technique is used for the core business server provided in each core business system, the integrated core business system 100 will be described below as an example.

  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 process data indicating 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 process flow DB 101 includes various process data (or form data) collected and organized by various information processing using various programs stored in the business application program DB (not shown) of the core business server 110. This is a storage medium for storing process flow data. The process flow data will be described later in detail. Also, in this example, the integrated core business system 100 includes a business related data DB (not shown) managed by the DWH server 120, and the core business server 110 stores process data stored in the process flow DB 101, CSV according to predetermined extraction conditions
(Comma Separated Values) A function of converting to a format and transmitting to the mobile terminal management server 10 is provided. In this example, the core business server 110 transfers the data file in CSV format by FTP (File Transfer Protocol) to the mobile terminal management server 10.

  The mobile terminal 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 a request from a mobile terminal used by a user. The mobile terminal 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 mobile terminal management server 10. As shown in FIG. 2, the mobile terminal management server 10 includes a control unit 11 that performs various controls, a process flow data temporary storage DB 16, a business application program DB 17, a process flow DB 18a, a project DB 18b, a DWHDB 19, and a general And other DB 10X for storing various data necessary for realizing a function as a basic mission-critical server (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 process flow data to the portable terminals 31 to 3N, and inventory management information that performs processing for providing inventory management information to the portable terminals 31 to 3N. And a processing unit 11b.

  The process flow data temporary storage DB 16 is a storage medium for temporarily storing the process flow data acquired from the integrated core business system 100 side and the process flow data stored in the process flow DB 18a. The process flow data stored in the process flow data temporary storage DB 16 is updated periodically (every day, every third day, every 12 hours, etc.), for example.

  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 process flow DB 18a is a storage medium for storing process flow data including various process data (or form data) collected and organized by various information processing using various programs stored in the business application program DB 17. is there. In this example, a case will be described in which process flow data including various data related to a process flow including a plurality of business processes is stored in the process flow table PT in the process flow DB 18a. In this example, a case will be described in which the mobile terminal management server 10 centrally manages process flow data generated for each process flow using one process flow table PT. In this example, the process flow data includes generally used slip data (for example, for the slip data corresponding to the order slip, the order slip header information, the order slip detail information, the delivery date schedule, etc. Is stored in a structure that can be searched based on the key such as the slip number, etc. Note that the slip number includes the order number, order number, shipping number, entry / exit number, invoice inquiry, billing number, Account number etc. are included)).

  Note that the mobile terminal management server 10 manages the process flow data in a plurality of tables, for example, for each type described later, or for each piece of common data (for example, an order recipient) described later. It is good also as composition to do.

  FIG. 3 is an explanatory diagram showing an example of the storage state of process flow data in the process flow DB 18a. As shown in FIG. 3, the process flow data in this example includes a main key part, a project specific data part, a reference key part, a type part, a status part, a common data part, and a process specific data part. Including. Each item corresponding to each part of the process flow data (that is, each column item in the process flow table PT) indicates the type of process data constituting the process flow data. In other words, data relating to each business process constituting the process flow is allocated and stored in each part constituting the process flow data. Note that process data related to one process flow (for example, a series of process flows from order receipt to delivery from a certain company) is stored in the same entry (that is, the same row in the process table PT) in the process flow table PT. With such a configuration, it is possible to define the correspondence between the process data.

  Here, the “primary key part” is a part of the process flow data in which main key data, which is data for uniquely identifying the process flow data, is stored. In this example, the main key part is composed of a process flow number and a process flow detail number. That is, in this example, a combination of a process flow number and a process flow detail number becomes an identifier (ID) of each process flow data. The main key part is updated when the process flow data is registered for the first time. Here, “when first registering process flow data” means that when an entry (data row) is added to the process flow data, for example, process data belonging to a certain process flow and corresponding other processes It shall mean the time when unregistered process data is registered. The “update” here includes addition of data.

  The “process flow number” is an identifier for specifying one process flow data (that is, one column in the process flow table PT shown in FIG. 3). The process flow number is assigned to each process data having the same predetermined item. In this example, the same number is assigned to the process flow number of the process flow number that has the same type and the order-receiving party in the process flow data.

  Further, the “process flow detail number” is an identifier for identifying specific process flow data from among the process flow data assigned with the same process flow number. That is, for example, the process flow table PT shown in FIG. 3 indicates that the business process “order received” in the process flow type “inventory sales” has received orders for the amounts “1200” and “2600” from the order recipient “T001”. The process flow data including the process data to be shown can be uniquely identified by the combination of the process flow number “000001” and the process flow detail number “0010” or “0020”, respectively.

  The “project specifying data part” is a part of the process flow data in which primary key data that is data for specifying a project is stored. In this example, the project specific data part is composed of a project number and a project detail number. In other words, in this example, the project and its details can be specified by the combination of the project number and the project detail number. In this example, when an entry (data row) is added to the process flow data, it is possible to specify which project item belongs to which project by receiving the specification of the project number and project item number. Will be added.

  The “project number” is an identifier for specifying one project. If they belong to the same project, the same project number is used. The “project detail number” is an identifier for specifying the details of each business unit constituting the project. Therefore, each project detail number associated with the same project number is used to specify the details of each business unit (for example, exterior, power generation facility) that constitutes the same project (for example, dam construction). It becomes an identifier. Moreover, data (data on the same line) such as a common data section associated with the same project detail number is data for specifying the details of the same business.

  Next, the “reference key part” is data for specifying other process flow data (or other process data) related to the process flow, such as the original transaction for sales returns, among the process flow data. This is the part where key data is stored. In this example, the reference key part is composed of a reference number and a reference specification number. The reference key part is updated when the process flow data is registered for the first time.

  Note that the reference number and the reference detail number respectively store the process flow number and the process flow detail number of another process flow related to the process flow. However, when there is no other process flow related to the process flow, such as in the case of a new transaction, the reference key portion contains data indicating the same value as the primary key portion of the same entry (that is, the reference number is a process) A flow number is stored, and a process flow item number is stored in the reference item number. Further, when the reference key part indicates other process data related to the process flow, the reference key part is further provided with data for specifying the type of the process data.

  The “type part” is a part in the process flow data in which type data, which is data indicating the type of process flow, such as inventory sales and sample shipment, is stored. The type part is updated when the process flow data is registered for the first time. Note that the type of process flow is not limited to inventory sales or sample shipment. Also, it is assumed that which process is required for each type of process flow is determined in advance (that is, the type and number of business processes included in each type of process flow are different). A plurality of other types of process flows will be presented later (see FIG. 17).

  In addition, the “status part” stores status data that is data indicating the progress of the process flow (that is, data indicating the progress of each of a plurality of business processes included in the process flow) among the process flow data. Part. In this example, the status data indicates the progress of each business process by setting “0” for the unfinished business process and “1” for the completed business process for the business process required by the process flow. Show. That is, for example, as shown in FIG. 3, the process flow of “inventory sales”, and the business processes included in the process flow are “order receipt”, “shipment”, “shipping”, “shipping inspection”, and “sales”. In this case, it is assumed that process specific data (for example, order date) related to the business process “order received” is registered. In this case, in the status data, the portion corresponding to “sales” is “1”, and the other portions remain in the initial state (ie, the state in which “0” is set).

  That is, the status part in this example is updated for each business process. In other words, the status part is updated when process-specific data to be described later is input, specifically, when it is determined that each business process is completed because a predetermined status change condition is satisfied. Although the status change condition is not particularly limited, in this example, “all process specific data corresponding to one business process is input” is stored in a predetermined storage area of the mobile terminal management server 10 as a status change condition. It shall be remembered.

  In this example, since different types of process flows are stored in the same table, a part of the items (column items) constituting the table stores unnecessary process data in a specific process flow. In some cases. In this case, in the process flow table, a part for storing unnecessary process data is empty data, and “0” is stored in status data corresponding to the empty data.

  In addition, the “common data part” is data that does not depend on the business process such as the order receiving party and the shipping destination among the process flow data (that is, common data between business processes included in the same process flow). This is the part where data is stored. The common data part is updated when the process flow data is registered for the first time.

  In addition, the “process specific data part” is a text that indicates precautions such as the order date and data registered in each business process in the process flow data (for example, “delivery deadline” and “breaker”) Data), etc., is a part in which process-specific data that is data unique to each business process included in the same process flow is stored. The process specific data part is updated for each business process. Therefore, in this example, it can be said that the process flow data based on the business process is “process-specific data” and the data not based on the business process is “common data”.

  The above is the description of the process flow data in this example. Here, the definitions of various terms shown in FIG. 3 will be briefly described.

  First, “order received” means a state in which an order is received from a customer and a contract with the customer is concluded. The “shipment instruction” means a state in which an instruction to ship a product is given to a warehouse company or a logistics person. In addition, “shipping” means a state in which goods are shipped from the warehouse and movement is started. “Inspection” means a state in which the inspection of the customer is completed and the ownership of the product is transferred to the customer. “Sales” means a state in which the customer's acceptance is confirmed, and the amount of receivables from the customer is finalized (= the receivable is recorded).

  In addition, the term “acceptance” means “business to inspect whether the delivered product or service has the specifications as ordered (= quantity, color, shape, quality as ordered)” or “ It is also used to mean “ownership is transferred”. Note that, in financial accounting (or institutional accounting) and the ERP system, in order to clarify the timing of asset ownership transfer, an event “acceptance” is defined separately from shipping.

  FIG. 4 is an explanatory diagram showing an example of inventory-related data in which items related to inventory management are extracted from the process flow data. Inventory related data includes process flow number, process flow item number, sales order, ordering, production receipt schedule, production receipt schedule, receipt, delivery, item, required date, quantity, planned receipt quantity, planned delivery quantity, actual receipt quantity, and This is the data associated with the actual delivery quantity. In this example, when the slip data of a business process related to a production receipt schedule, a production delivery schedule, a receipt, or a delivery is registered in the process flow data, the mobile terminal management server 10 performs the expected receipt quantity, the expected delivery quantity, and the actual receipt result. It is assumed that the quantity data of the quantity or the actual delivery quantity is specified, and the process is performed for registering the specified incoming planned quantity, expected delivery quantity, actual delivery quantity, or quantity data of the actual delivery quantity in the process flow data.

  The project DB 18b is a storage medium that stores project schedule data indicating the work schedule of each project. In this example, project schedule data indicating the work schedule of each project is stored in the project table PJT in the project DB 18b. Although not shown in the project table PJT, for example, information indicating a work schedule (for example, a budget, a purchase, an order, an order, etc.) for achieving the corresponding business in the project number and the project detail number. It is assumed that project schedule data associated with is registered.

  The mobile terminal management server 10 stores various data stored in the process flow DB 18a, the project DB 18b, the DWHDB 19 and the other DB 10X into predetermined external devices, in this example, the mobile terminals 31 to 3N and the integrated core business system 100, 200, 300. It has a function to provide according to the request from. That is, the mobile terminal management server 10 has a function as a core business server. In other words, the mobile terminal management server 10 includes an ERP engine.

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

  Each of the mobile 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 mobile terminals 31 to 3N has various applications such as a Web browser that can be used to handle the form data. Further, in this example, each of the mobile terminals 31 to 3N obtains necessary form data (in this example, process flow data and project schedule data) from the mobile terminal management server 10 in response to an operation input by the user, for example. A function for defining a query (search item, search key, extraction key, etc.) to be transmitted to the mobile terminal management server 10. The portable terminals 31 to 3N include code readers (or code reader functions) 31a to 3Na that read various codes such as QR codes (Quick Response Code: registered trademark).

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

  Here, processing for updating the process flow data stored in the process flow data temporary storage DB 16 will be described. In this example, when the mobile terminal management server 10 reaches a data update timing (for example, when updating every day, a predetermined time (such as 2:00 at midnight)), the mobile terminal management server 10 The process flow data (the latest data) stored in the process flow DB 18a provided is read, and the process flow data is stored in a predetermined storage area of the process flow data temporary storage DB 16 (new storage or overwriting storage). The stored information in the process flow data temporary storage DB 16 is updated. In this way, the storage information of the process flow data temporary storage DB 16 is updated by batch processing.

  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. 5 is a flowchart showing an example of slip data providing processing executed by the mobile terminal management server 10 or the like in the form inquiry system 500 of this example. Here, a case where the mobile terminal management server 10 provides process flow data in response to a request from the mobile terminal 31 used by the user X will be described as an example.

  In the slip data providing process, first, the mobile terminal 31 receives 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 mobile terminal 31 is permitted, various operations for using various functions installed in the mobile terminal 31 are allowed.

  When a predetermined login operation is executed by the user X while the user X is logged in to the mobile terminal 31, the mobile terminal 31 accesses the mobile terminal 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. Note that when logging in to the mobile terminal management server 10, the user X may designate a group (for example, Japanese) used in a group to which the user belongs and various screens.

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

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

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

  FIG. 6 is an explanatory diagram illustrating an example of a menu screen. As shown in FIG. 6, on the menu screen, a menu arrangement circle on which menu buttons M1 to M6 each displaying names of a plurality of selectable menus are arranged on a substantially circumference is displayed. A display area 501 is provided. Further, as shown in FIG. 6, 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, an inventory management button M5 that is pressed when requesting provision of inventory management information, and an inventory question that is pressed when inquiring about inventory information A combination button M6 is provided.

  On the menu screen displayed on the display unit of the mobile 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 to touch 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 mobile terminal 31 transmits to the mobile terminal management server 10 that the slip search button M1 has been pressed as a menu selection result to the mobile terminal management server 10 ( 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 mobile terminal management server 10 displays the slip search screen information indicating the slip search screen for specifying the slip search condition on the mobile terminal. 31 (step S107).

  When the slip search screen information is received, the mobile terminal 31 displays the slip search screen indicated by the received slip search screen information on the display unit that the mobile terminal 31 includes (step S108).

  FIG. 7 is an explanatory diagram showing an example of a slip search screen. As shown in FIG. 7, the slip search screen displays a plurality of selection item arrangement circles DC, SC, and PC in which a plurality of selection items that can be selected for specifying the search condition are arranged on a substantially circumference. A plurality of selection item arrangement circle display areas 601, 602, and 603 and a keyword input area 604 for inputting a keyword as a narrowing condition are provided. In this example, as the selected item arrangement circles DC, SC, and PC, the processed voucher type selection item arrangement circle DC that displays the type of processed voucher in a selectable manner and the titles of detailed items for narrowing down can be selected. There are provided a detailed selection type selection item arrangement circle SC and a process type selection item arrangement circle PC for displaying the type of business process in a selectable manner. Then, as the selection item arrangement circle display areas 601, 602, and 603, the processed slip type selection item arrangement circle display area 601 for displaying the processed slip type selection item arrangement circle DC and the detailed selection type selection item arrangement circle SC are displayed. A detailed selection type selection item arrangement circle display area 602 and a process type selection item arrangement circle display area 603 for displaying the process type selection item arrangement circle PC are provided.

  In the processed slip type selection item arrangement circle DC, an order button D1 for specifying an order slip as a search condition, an order button D2 for specifying an order slip as a search condition, and a receipt slip as a search condition. A receipt button D3, a delivery button D4 for designating a delivery slip as a search condition, a sales button D5 for designating a sales slip as a search condition, a billing button D6 for designating a billing slip as a search condition, and a receipt slip Selection items (selection item buttons) capable of selecting seven types of slips of a deposit button D7 for specifying as a search condition are arranged on a substantially circumference. In the center area of the processed slip type selection item arrangement circle DC, a classification display button DA displaying the classification name “processed slip” is arranged. In this example, the corresponding type of slip can be searched by selecting the selection items (selection item buttons) D1 to D7 (single selection or multiple selections).

  In the detailed selection type selection item arrangement circle SC, a customer button S1 for specifying a customer as a search condition, a supplier button S2 for specifying a supplier as a search condition, and an organization are specified as a search condition. Selection items (selection item buttons) capable of selecting four types of detailed narrowing condition items, that is, an organization button S3 for specifying items and an item button S4 for specifying items as search conditions, are arranged on a substantially circumference. In the center area of the detailed selection type selection item arrangement circle SC, a classification display button SA displaying a classification name “detail selection” is arranged. In this example, when selection items (selection item buttons) S1 to S4 are selected (a single selection or a plurality of selections), a detailed narrowing down that specifies a specific narrowing condition. A condition designation screen (not shown) is displayed, and when a specific narrow-down condition (for example, when the customer button S1 is selected), the supplier company name and the item button S4 are displayed. When selected, item number or the like is applicable). By selecting specific narrowing conditions (single or multiple selections), it becomes possible to search for slips with designated narrowing conditions.

  The process type selection item arrangement circle PC includes a production button P1 for designating “production” in the business process as a search condition, a sales button P2 for designating “sales” in the business process as a search condition, and a business process. Selection items (selection item buttons) capable of selecting three types of business processes, a purchase button P3 for designating “purchase” as a search condition, are arranged on a substantially circumference. In the center area of the process type selection item arrangement circle PC, a classification display button PA on which the classification name “process” is displayed is arranged. In this example, the selection of selection items (selection item buttons) P1 to P3 (single selection or multiple selections) can be used to search for slips related to the corresponding type of business process. Become.

  In this example, when the classification display buttons DA, SA, PA are pressed, an effect of rotating the corresponding selection item arrangement circles DC, SC, PC is executed. That is, in this example, the selection item arrangement circle display areas 601, 602, and 603 on the slip search screen correspond to a predetermined rotation instruction operation of the mobile terminal 31 by the user X (pressing of the classification display buttons DA, SA, and PA). Thus, the selection item rotation effect setting (setting by the computer program) is performed so that the selection item rotation effect in which a plurality of selection items in the corresponding selection item arrangement circles DC, SC, and PC move and rotate on the circumference is executed. ing. Specifically, in the screen state shown in FIG. 7, for example, when the classification display button DA is pressed, a plurality of selection items in the selection item arrangement circle DC are rotated counterclockwise on the circumference (in FIG. 8). A selection item rotation effect rotating in direction A) is executed. In this case, a predetermined rotation direction changing operation by the user X (an operation of sliding the finger in a new rotation direction by touching the vicinity of a portion where the circle formed by the selection item arrangement circle DC on the screen is displayed) ), The rotation direction may be changed. Note that when the classification display buttons DA, SA, PA are pressed again, the selection item rotation effect may be ended.

  Since the selection item rotation effect is configured as described above, the selection item arrangement circles DC, SC, and PC are arranged without being included in the screen as shown in FIG. Even if some of the selection items arranged in the circles DC, SC, and PC do not appear on the screen, all the selection items are sequentially selected by rotating the selection item arrangement circles DC, SC, and PC. It is possible to display. In addition, since it is not necessary to display all the selection items arranged in the selection item arrangement circles DC, SC, and PC simultaneously on one screen, the display size of each selection item can be increased. When the screen size is large, all the selection items may be displayed simultaneously on one screen.

  The selection items arranged in the selection item arrangement circles DC, SC, and PC are displayed in a circular frame in this example, but some or all of the selection items are quadrangular, triangular, or star-shaped. It may be displayed in a frame having another shape. Moreover, each selection item arrange | positioned at each selection item arrangement | positioning circle DC, SC, PC is an example, and another selection item may be sufficient.

  In the example shown in FIG. 7, three selection item arrangement circle display areas 601, 602, and 603 are provided on the slip search screen, but one selection item arrangement circle display area may be provided, Two or more selection item arrangement circle display areas may be provided.

  Further, in the example shown in FIG. 7, it is assumed that some of the selection item arrangement circle display areas 601, 602, and 603 are overlapped and set in the selection item arrangement circle display areas 601, 602, and 603. The selection items (selection item buttons) arranged in the selection item arrangement circles DC, SC, and PC respectively displayed are configured in different display modes (for example, different colors) for the selection item arrangement circles DC, SC, and PC. It shall be. Note that any method may be used as long as it is a different display mode, and the display mode may be made different by changing the shape or pattern.

  On the slip search screen, the user X selects each selection item arranged in each selection item arrangement circle DC, SC, PC by a touch operation. Specifically, the type of slip to be searched is selected by selecting one of the selection items (selection item buttons) D1 to D7 arranged in the processed slip type selection item arrangement circle DC. Also, on the slip search screen, the user X selects the titles of the detailed items for narrowing down by selecting the selection items (selection item buttons) S1 to S4 arranged in the detailed selection type selection item arrangement circle SC. To do. When the selection items (selection item buttons) S1 to S4 are selected, a specific narrowing condition is input on the detailed narrowing condition designation screen, and the detailed search condition is designated. In addition, on the slip search screen, the user X selects one of the selection items (selection item buttons) P1 to P3 arranged in the process type selection item arrangement circle PC to thereby select the type of business process to be searched. Select. Further, on the slip search screen, the user X inputs a keyword as a narrowing condition in the keyword input area 604 and designates the search keyword.

  In this example, when the item X4 is selected from the selection items (selection item buttons) S1 to S4 arranged in the detailed selection type selection item arrangement circle SC by the user X on the slip search screen, the mobile phone The terminal 31 displays a detailed narrowing condition designation screen on which the item input area is provided on its display unit. When the mobile terminal 31 reads a code (for example, a QR code or a barcode) attached to the article by a code reader (or a code reader function) 31a provided in the mobile terminal 31 by an operation of the user X, the mobile terminal 31 reads the code. The item number indicated by the code is displayed in the item input area. In this example, as described above, the item number can be easily input using the code reader (or code reader function) 31a.

  On the slip search screen, the user X may select and specify any one of the slip type, the detailed search conditions, the business process to be searched, and the search keyword, May be selected and designated. On the slip search screen, the user X may select and designate a plurality of slip types, detailed search conditions, and business processes to be searched.

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

  When the search button 605 is pressed while the search condition is selected / designated, the mobile terminal 31 makes a search request by presenting the selected / designated search condition to the mobile terminal management server 10 ( Step S109).

  When receiving the search request, the mobile terminal management server 10 refers to the process flow data stored in the process flow data temporary storage DB 16 and searches for slip data that matches the search conditions presented by the received provision request. (Step S110).

  When the slip data is searched according to the search condition, the mobile terminal management server 10 generates search result list display screen information indicating a search result list display screen that displays a list of the searched slip data as a search result, and transmits the search result list display screen information to the mobile terminal 31. (Step S111).

  When the search result list display screen information is received, the mobile terminal 31 displays the search result list display screen indicated by the received search result list display screen information on the display unit included in the mobile terminal 31 (step S112).

  FIG. 10 is an explanatory diagram illustrating an example of a search result list display screen. As shown in FIG. 10, on the search result list display screen, a display area 701 for displaying the search results, a return button B1 that is pressed when returning to the previous screen, and a press when editing the search results are displayed. An edit button B3 is provided. When a process flow type (such as inventory sales, direct sales) on the search result list display screen is selected by a touch operation, the mobile terminal 31 transmits an acquisition request for the corresponding slip data to the mobile terminal management server 10. To do. In response to the slip data acquisition request, the mobile terminal management server 10 refers to the process flow data stored in the process flow data temporary storage DB 16 and transmits the corresponding slip data to the mobile terminal 31. Then, the portable terminal 31 displays the received slip data on the display screen of the display unit.

  In the search result list display screen, when an operation for ending access such as an operation for ending the browser by the user X is performed (Y in step S113), the mobile terminal 31 sends a response to the mobile terminal 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 portable terminal 31 proceeds to the process in step S108 and displays a slip search screen (see FIG. 7). indicate.

  When the search result list display screen information is transmitted in step S111, the mobile terminal management server 10 starts measuring the time (standby time) during which no information is exchanged with the mobile terminal 31, and this standby 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 a logout request is received during the measurement of the standby time (Y in step S116), the mobile terminal management server 10 stops the measurement of the standby time and performs logout processing for releasing the login state (step S117).

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

  As described above, it is determined whether or not login to the mobile terminal management server 10 is permitted in response to a login request from the mobile terminal 31 that can be operated by the login process. And the process of providing process flow data according to the request is executed.

  As described above, in the slip data providing process, the search target is the process flow data temporary storage DB 16, so that the mobile terminal 31 functions as the core business server in the mobile terminal management server 10 (specifically, the business data Since it is possible to eliminate the need to access the application program DB 17 and the process flow DB 18a), it is possible to improve safety when providing slip data to the portable terminal 31. Note that the process flow DB 18a may be a search target.

  In the above embodiment, the process flow data is retrieved by referring to the process flow table PT that stores the process flow data including various data related to the process flow including a plurality of business processes, and the process flow data is , Status data, common data, and process-specific data. Status data is data indicating the progress of each of the plurality of business processes included in the process flow, and the common data is the same process flow. The process-specific data is data that is unique to each business process included in the same process flow, so the processing load required to search for data in the business system is reduced. It becomes possible to reduceIn the conventional business system, the form data is managed in a separate data table for each business process. Therefore, when performing a search, it is necessary to refer to all of the data tables for the related business processes. For this reason, in a business system that handles an enormous amount of data, the processing load required for the search processing has become enormous. In the above-described embodiment, the process flow data including the status data, the common data, and the process specific data is constructed, and the search is performed with reference to the process data table. There is no need to refer to the data table, the processing load required for data retrieval in the business system can be greatly reduced, and the processing program creation load for data retrieval can be greatly reduced. Become.

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

  In the production management information providing process, the processes in steps S201 to S205 are the same processes as steps S101 to S105 in the slip data providing process described above, and thus the description thereof is omitted here.

  On the menu screen (see FIG. 6) displayed on the display unit of the mobile terminal 31 in step S205, 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 inventory management button M5 is pressed. The processing when the other menu buttons M1 to M4 and M6 are pressed is omitted here.

  When the inventory management button M5 is pressed on the menu screen, the mobile terminal 31 transmits, to the mobile terminal management server 10, the fact that the stock management button M5 has been pressed to the mobile terminal management server 10 as a menu selection result ( Step S206).

  When the menu selection result indicating that the stock management button M5 is pressed is received, the stock management information processing unit 11b of the mobile terminal management server 10 sends to the mobile terminal 31 condition specifying screen information indicating a condition specifying screen for specifying a search condition. Transmit (step S207).

  When the condition designation screen information is received, the mobile terminal 31 displays the condition designation screen indicated by the received condition designation screen information on the display unit provided therein (step S208).

  FIG. 12 is an explanatory diagram illustrating an example of a condition designation screen. As shown in FIG. 12, the condition designation screen is pressed when an item input area 801 for inputting a product item as a search condition and a search condition for an item input in the item input area 801 are determined. A decision button B5 is provided.

  On the condition designation screen, the user X operates, for example, an input unit such as a keyboard displayed on the screen by touching the item input area 801 to search for one or more items in the item input area 801. Enter. When the input of the item is completed, the user X presses the decision button B5 by a touch operation. As described above, the user X specifies a product item as a search condition.

  When the enter button B5 is pressed after the item is input, the mobile terminal 31 designates the product to be searched by presenting the item to the mobile terminal management server 10, and requests to provide inventory management information (Step S209).

  When the portable terminal management server 10 receives the provision request for the inventory management information, it refers to the process flow data stored in the process flow data temporary storage DB 16 and is associated with the item presented by the accepted provision request. The inventory data (see FIG. 4) extracted from the retrieved inventory data is extracted from the retrieved inventory data (step S210). The inventory related data includes each quantity data for inventory management registered in advance in the process flow data.

  When the inventory-related data is extracted, the mobile terminal management server 10 generates inventory management information (see FIG. 13) including predetermined items based on the extracted inventory-related data (step S211). In this example, the mobile terminal management server 10 includes items, required dates, scheduled warehousing quantities, scheduled warehousing quantities, actual warehousing quantities, and actual warehousing quantities among the items constituting the inventory-related data. Stock management information (see FIG. 13) is generated by sorting as key items, totaling the quantities using the same key items, and adding an inventory transition item that calculates the transition of the inventory quantity based on the aggregation result.

  When the inventory management information is generated, the mobile terminal management server 10 generates inventory management information display screen information indicating an inventory management information display screen for displaying the generated inventory management information, and transmits it to the mobile terminal 31 (step S212).

  When the inventory management information display screen information is received, the mobile terminal 31 displays the inventory management information display screen indicated by the received inventory management information display screen information on the display unit that the mobile terminal 31 includes (step S213).

  FIG. 13 is an explanatory diagram showing an example of the inventory management information display screen. As shown in FIG. 13, the inventory management information display screen is provided with an inventory management information display area 901 for displaying inventory management information, and a return button B6 that is pressed when returning to the previous screen. In this example, as shown in FIG. 13, the inventory management information display area 901 includes, as inventory management information, items, required dates, scheduled warehousing quantities, scheduled warehousing quantities, actual warehousing quantities, and actual warehousing quantities. And inventory transition.

  In the inventory management information display screen, when an operation for ending access such as an operation for ending the browser by the user X is performed (Y in step S214), the mobile terminal 31 sends a response to the mobile terminal management server 10 A logout request is made (step S215). When an operation for continuing access such as pressing the return button B6 is performed (N in step S214), the portable terminal 31 proceeds to the process in step S208 and displays the condition designation screen (see FIG. 12). indicate.

  When the inventory management information display screen information is transmitted in step S212, the mobile terminal management server 10 starts measuring the time (standby time) during which no information is exchanged with the mobile terminal 31, and this standby time is predetermined. It is monitored whether or not a time (for example, 5 minutes, 10 minutes, 30 minutes, etc.) has passed (a predetermined time has been reached) (step S216).

  When a logout request is received during the measurement of the standby time (Y in step S217), the mobile terminal management server 10 stops the measurement of the standby time and performs logout processing for releasing the login state (step S218).

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

  As described above, it is determined whether or not login to the mobile terminal management server 10 is permitted in response to a login request from the mobile terminal 31 that can be operated by the login process. And a process of providing inventory management information according to the request is executed.

  In the above example, in the inventory management information providing process, the search target of the slip data is the process flow data temporary storage DB 16, but the process flow DB 18a may be the search target.

  As described above, in the above-described embodiment, the ERP is a server that provides various data via the communication network 40 in response to requests from the mobile terminals 31 to 3N used by the user. The terminal management server 10 includes a process flow data table PT that stores process flow data including various data related to a process flow including a plurality of business processes. The process flow data includes status data, common data, process specific data, Status data is data indicating the progress of each of the plurality of business processes included in the process flow, common data is data common to the business processes included in the same process flow, Process-specific data is included in the same process flow It is data unique to each business process, and the process flow data includes inventory related data including quantity data indicating the quantity related to the inventory of the product, and the search condition is set according to the request from the portable terminal 31. Provides a condition specification screen to be specified, receives the search condition specified on the condition specification screen from the portable terminal 31, accepts it, and processes inventory related data including items related to inventory management of the product indicated by the received search condition as process flow data Extracted from the process flow data stored in the table PT, generates inventory management information including the inventory transition of the product indicated by the specified search condition based on the inventory related data, and stores the generated inventory management information in the portable terminal 31. In the business system for providing information related to forms to mobile communication terminals (mobile terminals 31 to 3N) It is possible to reduce the processing load required for data processing in the business system, it is possible to output a valid information (inventory information) quickly.

  That is, it is configured to search for form data satisfying the search condition with reference to the process flow table PT storing process flow data including various data related to process flows including a plurality of business processes, and the process flow data includes status data, Data including common data and process-specific data. Status data is data indicating the progress of each of the plurality of business processes included in the process flow. Common data is a business process included in the same process flow. Since the process-specific data is data common to each business process and is unique to each business process included in the same process flow, data search in the business system necessary to generate inventory management information To reduce the processing load required It's is possible. In the conventional business system, the form data is managed in a separate data table for each business process. Therefore, when performing a search, it is necessary to refer to all of the data tables for the related business processes. For this reason, in a business system that handles an enormous amount of data, the processing load required for the search processing has become enormous. In the above-described embodiment, process flow data including status data, common data, and process specific data is constructed, and information necessary for generating inventory management information with reference to the process data table is stored. Because it is configured to search, it is not necessary to refer to multiple data tables, it is possible to greatly reduce the processing load required to search for data in the business system required for generating inventory management information In addition, it is possible to significantly reduce the processing program creation load for data retrieval.

  In addition, because the inventory related data registered in advance is extracted from the process flow data stored in the process flow data table PT, the processing load on the business system necessary for generating inventory management information is further increased. Can be reduced.

  Further, in the above-described embodiment, when the mobile terminal management server 10 registers the form data for the business process of manufacturing receipt, production delivery, receipt, or delivery in the process flow data, the corresponding business process Since the quantity data related to the product is specified and registered in the process flow data, it is possible to register the inventory related data in the process flow data table in advance, and the inventory related data is generated when the inventory management information is generated. Therefore, it is possible to further greatly reduce the processing load on the business system necessary for generating the inventory management information.

  In the embodiment described above, the database (for example, the process flow DB 18a) is provided in the process flow data management server (for example, the portable terminal management server 10) that manages the process flow data generated for each process flow. In response to a request from the client (for example, the mobile terminals 31 to 3N or the integrated core business system 100, 200, 300), the process flow data management server sends the form data searched with reference to the process flow data to the client. Since the configuration is provided, it is possible to construct a system in which the processing load required for providing the form data is reduced.

  Although not particularly mentioned in the above-described embodiment, the mobile terminal management server 10 performs each of the above-described processes (FIG. 5, FIG. 5) according to a processing program (mobile terminal management program) stored in a storage medium included in the mobile terminal management server 10. 11).

  INDUSTRIAL APPLICABILITY According to the present invention, in a business system that provides information related to a form to a mobile communication terminal (particularly, an ERP system), it is useful for reducing processing load required for data retrieval and outputting effective information quickly. .

DESCRIPTION OF SYMBOLS 10 Mobile terminal management server 20 Relay machine 31-3N Mobile terminal 40 Communication network 51,52,52 Communication network 100,200,300 Integrated core business system 110,310 Core business server 120,220 DWH server 500 Report inquiry system

Claims (5)

A server on which ERP operates and a mobile terminal management server that provides various data via a communication network in response to a request from a mobile terminal used by a user,
Including process flow data storage means for storing process flow data including various data relating to a process flow including a plurality of business processes,
The process flow data is data including status data, common data, and process specific data,
The status data is data indicating a progress status of each of a plurality of business processes included in the process flow,
The common data is data common between business processes included in the same process flow,
The process specific data is data specific to each business process included in the same process flow,
The process flow data includes inventory related data including quantity data indicating the quantity related to the inventory of the product,
further,
Condition specifying screen providing means for providing a condition specifying screen for specifying a search condition in response to a request from the mobile terminal;
Search condition receiving means for receiving and receiving the search condition specified on the condition specifying screen from the mobile terminal;
Inventory-related data extracting means for extracting inventory-related data including items related to inventory management of products indicated by the search conditions received by the search condition receiving means from process flow data stored in the process flow data storage means;
Inventory management information generating means for generating inventory management information including the inventory transition of the product indicated by the specified search condition based on the inventory related data;
A portable terminal management server comprising: inventory management information providing means for providing the portable terminal with inventory management information generated by the inventory management information generating means. Quantity to be registered in the process flow data by specifying the quantity data related to the relevant business process when registering the form data for the business process of production receipt, production delivery, receipt, or delivery in the process flow data The mobile terminal management server according to claim 1, further comprising data registration means. The portable terminal management server according to claim 1, wherein the quantity data includes a scheduled receipt quantity, a scheduled delivery quantity, an actual receipt quantity, and an actual delivery quantity. The portable terminal management server according to claim 3, wherein the inventory management information includes an item, a required date, a scheduled receipt quantity, a scheduled delivery quantity, an actual receipt quantity, an actual delivery quantity, and an inventory transition. A mobile terminal management program that operates an ERP and causes a mobile terminal management server to execute a process of providing various data via a communication network in response to a request from a mobile terminal used by a user.
The portable terminal management server includes process flow data storage means for storing process flow data including various data related to a process flow including a plurality of business processes,
The process flow data is data including status data, common data, and process specific data,
The status data is data indicating a progress status of each of a plurality of business processes included in the process flow,
The common data is data common between business processes included in the same process flow,
The process specific data is data specific to each business process included in the same process flow,
The process flow data includes inventory related data including quantity data indicating the quantity related to the inventory of the product,
In the portable terminal management server,
A condition designation screen providing process for providing a condition designation screen for designating a search condition in response to a request from the mobile terminal;
A search condition receiving process for receiving and receiving a search condition specified on the condition specifying screen from the mobile terminal;
Inventory-related data extracting means for extracting inventory-related data including items relating to product inventory management indicated by the search conditions received in the search condition receiving process from process flow data stored in the process flow data storage means;
Inventory management information generation processing for generating inventory management information including the inventory transition of the product indicated by the specified search condition based on the inventory related data;
A portable terminal management program for executing an inventory management information providing process for providing the inventory management information generated in the inventory management information generating process to the portable terminal.

Images