WO2013098897A1 - 携帯端末管理サーバ、および携帯端末管理プログラム - Google Patents
携帯端末管理サーバ、および携帯端末管理プログラム Download PDFInfo
- Publication number
- WO2013098897A1 WO2013098897A1 PCT/JP2011/007344 JP2011007344W WO2013098897A1 WO 2013098897 A1 WO2013098897 A1 WO 2013098897A1 JP 2011007344 W JP2011007344 W JP 2011007344W WO 2013098897 A1 WO2013098897 A1 WO 2013098897A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- process flow
- flow data
- mobile terminal
- update
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06316—Sequencing of tasks or work
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
Definitions
- 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.
- the form inquiry system that provides information such as forms to the mobile communication terminal as described above has the convenience of being able to obtain information while away from home or on the move, but there is a risk of information leakage There was a problem that increased. Therefore, a form inquiry system that provides information such as a form to a mobile communication terminal is required to have high safety.
- 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). is doing. 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. 18 is an explanatory diagram for explaining an example of a table configuration in a conventional ERP system.
- a business flow composed of a plurality of business processes indicates “inventory sales”
- the table for storing the data related to the process flow of “inventory sales” is, for example, as shown in FIGS. 18 (A) to 18 (E), for each input process, an order table, a shipping instruction table, and a delivery table. , An acceptance table, and a sales table.
- the table to be updated is different for each input process. Therefore, the correspondence between a plurality of business processes belonging to the same process flow is an identifier (in FIG. 18, the order number and order details in the shipping instruction table, and the delivery table in the data related to each business process). The shipping instruction number and the shipping instruction details, etc.) are given.
- 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.
- the same data for example, orders, quantity, amount, etc.
- the process data identifier is searched to search for necessary process data, and each is separately Therefore, when the process flow includes a large number of business processes, there is a problem that the processing load required to output a form related to the process flow becomes excessive.
- the mobile terminal management server of the present invention is 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.
- Process flow data storage means for storing process flow data including various data relating to the process flow including the process flow, and a process flow for updating the process flow data stored in the process flow data storage means in accordance with the progress of the process flow
- the portable terminal When there is a log-in request from the data updating unit, the portable terminal, a login determining unit that determines whether or not to permit the login to the portable terminal, and the login determining unit determines that the login is permitted Login processing means for performing login processing in the case
- the browsing request receiving unit receives a browsing request for the process flow data from the portable terminal in the logged-in state where the login processing is executed by the login processing unit, and the process flow Process flow data providing means for providing the process flow data stored in the data storage means to the portable terminal, and the process flow data is
- the status data is data indicating the progress 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.
- the unique data is the same process.
- Process flow data storage means for storing, in a temporary storage database, data satisfying a predetermined condition among the process flow data stored in the process flow data storage means, and the process flow data providing means is provided in the process flow data storage means.
- the process flow data stored in the temporary storage database may be provided to the portable terminal.
- An update request accepting unit that accepts an update request for process flow data from a logged-in portable terminal, an update content of the update request accepted by the update request accepting unit, and terminal information indicating the portable terminal that has made the update request;
- Update related information accumulating means for accumulating update related information including the process flow data update means according to the update related information accumulated by the update related information accumulating means at a predetermined timing.
- the process flow data stored in the process flow data storage unit may be updated.
- the mobile terminal may be configured to include a login determination unit that permits login only when a predetermined regular login operation is accepted.
- Time measurement means for measuring a time during which information is not exchanged with the portable terminal in the logged-in state, and process flow data for the portable terminal when the measurement time of the time measurement means reaches a predetermined time It may be configured to include history information deletion request means for requesting deletion of communication history information related to the provision of information.
- 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 process according to the progress status of the process flow in the portable terminal management server comprising a process flow data storage means for storing process flow data including various data relating to a process flow including a plurality of business processes.
- a process flow data update process for updating the process flow data stored in the flow data storage means and a login request from the portable terminal, it is determined whether or not the portable terminal is permitted to log in.
- Login determination process and login allowed in the login determination process A login process execution process for performing a login process when it is determined, a browsing request reception process for receiving a browsing request for process flow data from the portable terminal in the login state in which the login process is executed in the login process execution process;
- the process flow data providing process for providing the mobile terminal with the process flow data stored in the process flow data storage unit is executed, and the process flow data Is data including status data, common data, and process-specific data, and the status data is data indicating the progress of each of a plurality of business processes included in the process flow, and the common data is 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, and the status data according to the update status of the process-specific data in the process flow data update process Is to execute the process of updating.
- the present invention in a business system that provides information related to a form to a mobile communication terminal, it is possible to improve safety and reduce processing load required for data update and search in an ERP system.
- FIG. 1 is a block diagram showing a configuration example of a form inquiry system 500 according to an embodiment of the present invention.
- 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.
- communication networks 51, 52, and 53 such as a LAN (Local Area Network) and a dedicated communication line, respectively. Is done.
- LAN Local Area Network
- 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.
- 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.
- 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.
- 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.
- OS Operating System
- relational DB relational DB
- the form is a general term for books and slips.
- the books are items in which items relating to the receipt and payment of money and goods are entered, and the slips are data that is the basis for creating books and are evidence of business transactions.
- 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.
- 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 has a function of registering various data in a predetermined storage area (a business related data DB 101b described later) by converting a CSV file transferred from the core business server 110 into a predetermined data format.
- a predetermined storage area a business related data DB 101b described later
- 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.
- 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.
- the core business server 110 transfers a data file in CSV format by FTP (File Transfer Protocol) to the mobile terminal management server 10.
- FTP File Transfer Protocol
- 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.
- the mobile terminal management server 10 includes a process flow data management unit 11 that performs processing related to process flow data management, a login management unit 12 that performs processing related to login management, and mobile terminals 31 to 3N.
- a process flow data provision processing unit 13 that executes processing for providing process flow data
- a process flow data update processing unit 14 that executes processing for updating process flow data in response to a request from the mobile terminals 31 to 3N, and the like.
- a customer information management unit 15 that performs processing related to management of customer information
- a process flow data temporary storage DB 16 that performs processing related to management of customer information
- a business application program DB 17 that performs processing related to management of customer information
- a process flow DB 18 Various data (for example, business application pro
- Various programs stored in the ram DB17 is a World DB19 storing data) to be utilized.
- the other DB 19 is a part not particularly related to the present invention, and a detailed description thereof will be omitted.
- 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 18 is a storage medium that stores 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.
- 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 18.
- the mobile terminal management server 10 centrally manages process flow data generated for each process flow using one process flow table PT.
- 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.
- the slip number includes the order number, order number, shipping number, entry / exit number, invoice inquiry, billing number, Account number etc. are included)).
- FIG. 3 is an explanatory diagram showing an example of the storage state of process flow data in the process flow DB 18.
- the process flow data in this example includes a main key part, a reference key part, a type part, a status part, a common data part, and a process specific data part.
- Each item corresponding to each part of the process flow data indicates the type of process data constituting the process flow data.
- data relating to each business process constituting the process flow is allocated and stored in each part constituting the process flow data.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the process number and process flow detail number of other process flows related to the process flow are stored in the reference number and the reference detail number, respectively.
- 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.
- 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 which type data that is a type of process flow, such as inventory sales and sample shipment, is stored in the process flow data.
- the type part is updated when the process flow data is registered for the first time.
- the type of process flow is not limited to inventory sales or sample shipment.
- 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.
- 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 process flow DB 18 is provided with an update condition table UT in which update condition data indicating an update condition of the process flow data (or process flow table PT) is registered.
- FIG. 4 is an explanatory diagram showing an example of the storage state of the update condition data stored in the update condition table UT in the process flow DB 18.
- the update condition data in this example includes a business process name, a process flow type, and a process flow data update condition.
- the “process flow data update condition” indicates the process data registration condition corresponding to the process flow type.
- the process flow data update condition is defined as the type of process data that the process flow data should have as a prerequisite when process data related to a certain business process is added to the process flow data (that is, in the process flow). Indicates the type of business process that should be completed). That is, when the update condition table UT is as shown in FIG.
- the update condition table UT may be configured to be created by the administrator of the form inquiry system 500, or may be configured to be created by the users of the mobile terminals 31 to 3N.
- the mobile terminal management server 10 stores various data stored in the process flow DB 18 and other DBs 19 in response to requests from predetermined external devices, in this example, the mobile terminals 31 to 3N and the integrated core business system 100, 200, 300. Have the function to provide. 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.
- 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 transferred to, for example, a predetermined Web application (Web browser). ) Etc., and the function of outputting to the display unit.
- a predetermined Web application Web browser
- processing for updating the process flow data stored in the process flow data temporary storage DB 16 will be described.
- 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 provided process flow DB 18 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.
- the update of the process flow data stored in the process flow DB 18 will be described in detail later.
- FIG. 5 is a flowchart showing an example of process flow data provision processing executed by the mobile terminal management server 10 or the like in the form inquiry system 500 of this example.
- 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.
- the mobile terminal 31 receives a login request by the login operation of the user X (step S101).
- a login operation for example, a password input operation set in advance may be considered.
- various operations for using various functions installed in the mobile terminal 31 are permitted.
- 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.
- predetermined information for example, an electronic certificate issued to the user X
- the login management unit 12 of the mobile terminal 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.
- the login management unit 12 determines that login is permitted (Y in step S103)
- the login management unit 12 sets the mobile terminal 31 to the login state.
- the process flow data provision processing unit 13 of the mobile terminal management server 10 transmits data search screen information indicating a data search screen to the mobile terminal 31 (step S104).
- the login management unit 12 ends the process flow data providing process without setting the mobile terminal 31 to the login state. If it is determined that login is not permitted, the login management unit 12 performs a process of notifying the mobile terminal 31 to that effect.
- the mobile terminal 31 displays the data search screen indicated by the received data search screen information on the display unit included in the mobile terminal 31 (step S105).
- FIG. 6 is an explanatory diagram showing an example of a data search screen.
- the user X operates an operation unit (for example, a keyboard displayed on a display unit provided with a touch panel) provided in the mobile terminal 31, inputs a search item and a search word, and clicks the search button B2. Press.
- Items for example, order slips, inventory, business partners, product names
- search button B2 Clicks the search button B2. Press.
- Items for example, order slips, inventory, business partners, product names
- search word a character string related to the process flow data (for example, a supplier name or a product name) is input.
- step S106 When the search button B2 is pressed while the search item and the search word are input, the mobile terminal 31 presents the input search item and the search word as a search condition to the mobile terminal management server 10, A process flow data provision request is made (step S106).
- search condition is an example, and any other condition may be used as long as it can search for arbitrary process flow data (or process data constituting the process flow data).
- the mobile terminal management server 10 When the mobile terminal management server 10 receives the process flow data provision request, the mobile terminal management server 10 refers to the process flow data temporary storage DB 16 and searches the process flow data according to the search condition presented by the accepted provision request (step S107).
- the mobile terminal management server 10 transmits search result screen information indicating a search result screen for displaying the searched process flow data as a search result to the mobile terminal 31 (step S108).
- the mobile terminal 31 displays the search result screen indicated by the received search result screen information on the display unit included in the mobile terminal 31 (step S109).
- the portable terminal 31 makes a logout request to the portable terminal management server 10 ( Step S111). If an operation for continuing access such as pressing the return button B1 is performed (N in step S110), the portable terminal 31 proceeds to the process in step S105 and displays the data search screen (see FIG. 6). indicate.
- the login management unit 12 starts measuring the time (waiting time) during which no information is exchanged with the mobile terminal 31, and this waiting time is a predetermined time (for example, It is monitored whether or not 5 minutes, 10 minutes, 30 minutes, etc.) have elapsed (reached a predetermined time) (step S112).
- a predetermined time for example, It is monitored whether or not 5 minutes, 10 minutes, 30 minutes, etc.
- the login management unit 12 When a logout request is received during the measurement of the standby time (Y in step S113), the login management unit 12 stops the measurement of the standby time, and the history information (communication history information, operation by the current communication) with respect to the portable terminal 31. A request for erasing the history information or the like is issued (step S114), and a logout process for canceling the login state is performed (step S115).
- step S112 If it is determined that the predetermined time has elapsed (Y in step S112), the login management unit 12 ends the measurement of the standby time, and the mobile terminal 31 performs history information ( A request to delete communication history information, operation history information, etc. is issued (step S114), and a logout process for canceling the login state is performed (step S115).
- the portable terminal 31 when the portable terminal 31 receives a request for deleting history information, the portable terminal 31 performs a process of deleting the history information accumulated by the current communication with the portable terminal management server 10 (step S116).
- the process flow search target is the process flow data temporary storage DB 16, so that the mobile terminal 31 functions as a core business server in the mobile terminal management server 10 (specifically, Since it is possible to eliminate the need to access the business application program DB 17 and the process flow DB 18), it is possible to improve the safety when providing the process flow data to the portable terminal 31.
- FIG. 8 is a flowchart showing an example of process flow data update processing executed by the mobile terminal management server 10 and the mobile terminal 31.
- process flow data is updated in response to a request from the mobile terminal 31 used by the user X.
- Steps S201 to S209 in the process flow data update process are the same as steps S101 to S109 (see FIG. 5) in the process flow data provision process described above, and steps S219 to S225 in the business data update process are the process flow data described above. Since the process is the same as steps S110 to S116 (see FIG. 5) in the providing process, detailed description of steps S201 to S209 and S219 to S225 in the business data update process is omitted.
- FIG. 9 is an explanatory diagram illustrating an example of an editing screen. As shown in FIG. 9, in the edit screen, an edit area 901 for displaying the search result in an editable manner, a return button B1 pressed when returning to the previous screen, and the edit result are saved on the mobile terminal management server 10 side. And an update button B4 that is pressed when reflecting in the processed process flow data.
- the mobile terminal 31 makes an information rewrite request for requesting the mobile terminal management server 10 to reflect the edited result (step S210).
- the editing content for example, the mobile terminal management server information related to the mobile terminal management server 10 (for example, the electronic certificate issued to the mobile terminal management server 10), the user information related to the user X (for example, to the user X) For example, an electronic certificate issued).
- the mobile terminal management server 10 accesses the process flow DB 18 and performs a predetermined process before login (pre-login process) (step S211).
- pre-login process the mobile terminal management server 10 uses predetermined information (login determination information used for login determination, for example, an electronic certificate issued to the mobile terminal management server 10, a user X Processing for confirming the electronic certificate issued to the other).
- the mobile terminal management server 10 determines whether or not to permit login (step S212). This determination may be made based on, for example, an ID, a password, or an electronic certificate.
- the mobile terminal management server 10 sets the mobile terminal 31 to a login state (here, access to the process flow DB 18 is permitted) with respect to acceptance of information from the mobile terminal 31. (Step S213).
- the portable terminal management server 10 When the information stored in the process flow DB 18 is rewritten, the portable terminal management server 10 similarly executes a process of rewriting the corresponding process flow data stored in the process flow data temporary storage DB 16 (step S216). And the portable terminal management server 10 transmits the rewriting notification for notifying that it rewritten according to the edit content with respect to the portable terminal 31 (step S217).
- the mobile terminal 31 Upon receiving the rewrite notification, the mobile terminal 31 displays a rewrite reflection notification for notifying the user X that the editing result has been reflected in the predetermined area of the editing screen (step S218).
- step S219 is executed in the same manner as the above-described process flow data provision processing (see FIG. 5).
- step S203 it is determined whether or not to permit the login to the portable terminal management server 10 in response to the login request from the portable terminal 31 that can be operated by the login process.
- a process of accepting a data rewrite request step S210), performing a pre-login process on the process flow DB 18 when a rewrite request is accepted (step S211), and rewriting the process flow data in the process flow DB 18 if permitted. Is performed (step S214). And the process which rewrites process flow data is performed also to process flow data temporary storage DB16.
- step S201 By performing the process flow data rewriting process as described above, it is possible to perform triple authentication in step S201, step S203, and step S212, so that the process flow data is received in response to a request from the portable terminal 31. It is possible to improve safety when updating.
- rewriting information data
- the process flow DB 18 performs login determination, and when login is permitted, the process of rewriting data is performed.
- the mobile terminal management server 10 receives a rewrite request from the mobile terminals 31 to 3N, it stores the editing contents and information (information necessary for authentication) regarding the mobile terminals 31 to 3N that are the source of the rewrite request.
- the process flow DB 18 may be rewritten by batch processing at a predetermined timing (for example, every day at 23:00).
- the mobile terminal management server 10 receives an update request (information rewrite request) for process flow data from a mobile terminal in a logged-in state, the update content (edit content) of the received update request, and the mobile that made the update request.
- Update related information including terminal information (for example, an electronic certificate) indicating the terminal is stored (for example, stored in a storage medium included in the mobile terminal management server 10), and a predetermined timing (for example, every day at 23:00) is reached.
- Update the process flow data in batches using the update related information accumulated, and batch update processing (information rewriting) in response to the update requests received from each mobile terminal that was in the login state It is good also as a structure to perform. With this configuration, the number of accesses to the process flow DB 18 can be greatly reduced, and safety can be further improved.
- FIG. 10 is a flowchart showing an example of database update processing executed by the mobile terminal management server 10.
- a process for updating the process flow data stored in the process flow DB 18 is executed by the mobile terminal management server 10.
- the mobile terminal management server 10 uses various process data and process flow data collected and organized by various information processing using various programs stored in the business application program DB 17 at a predetermined timing.
- the database update process described below is different from the case of updating in response to an update request from the mobile terminals 31 to 3N (for example, the process flow data update process described above, see FIG. 8).
- the mobile terminal management server 10 determines whether or not new process flow data (new process flow data) has been acquired (step S301). If it is determined that new process flow data has not been acquired (N in step S301), the mobile terminal management server 10 proceeds to the process in step S303 described later.
- the mobile terminal management server 10 registers the acquired process flow data in the process flow table PT (step S302).
- the mobile terminal management server 10 determines whether or not process data corresponding to the registered process flow data (that is, data relating to a business process constituting the process flow) has been acquired (step S303).
- process data acquired by the mobile terminal management server 10 is registered process data is determined based on whether the process flow data having a combination of the process flow number and the process flow detail number included in the acquired data is a process flow. This is done by determining whether or not it is stored in the table PT. Therefore, in this example, the data (that is, the process that forms the main key part) in the data (data input by the business executor or data created by the business application program) acquired by the mobile terminal management server 10. (Flow number and process flow detail number) are required to be included.
- the mobile terminal management server 10 determines whether or not the process flow data satisfies the update condition indicated by the specified update condition data (step S306). That is, the mobile terminal management server 10 determines whether or not to register the acquired process data as part of the process flow data in the process flow table PT based on the process flow data and the update condition data. In this example, the mobile terminal management server 10 compares the status part of the process flow data corresponding to the acquired process data with the update condition data, and the business process for which “1” is set in the update condition data is in the status. If all of the sections are set to “1”, it is determined that the process flow data satisfies the update condition.
- step S307 If it is determined that the process flow data does not satisfy the update condition indicated by the specified update condition data (N in step S306), the mobile terminal management server 10 executes a predetermined error process (step S307), The process proceeds to step S301.
- the “error processing” is not particularly limited as long as the process flow data is not updated. For example, even if the process data is temporarily stored in a predetermined storage area until the update condition is satisfied, Yes, processing to investigate the cause of acquiring process data that does not satisfy the update conditions (that is, the process of notifying the administrator of the error or the contents of the update condition that is not satisfied) Or the like).
- the mobile terminal management server 10 updates the process flow data registered in the process flow table PT. (Step S308). That is, the mobile terminal management server 10 registers the acquired process data in the process flow table PT.
- the mobile terminal management server 10 determines whether or not a predetermined status change condition related to the process flow data is satisfied by updating the process flow data (step S309). If it is determined that the predetermined status change condition is not satisfied in response to the process flow data being updated (N in step S309), the mobile terminal management server 10 proceeds to step S301.
- the mobile terminal management server 10 determines the process flow based on the satisfied status change condition.
- the status data included in the data is updated (step S310), and the process proceeds to step S301.
- the database update process in this example is terminated by an end operation by the administrator of the mobile terminal management server 10, for example.
- the database update process may be a process executed in real time, or may be a batch process executed every specific unit time.
- a process having a part of real time property such as performing a real time process only for a specified period may be used.
- FIG. 11 is a flowchart illustrating an example of a form output process executed by the mobile terminal management server 10 and the mobile terminal 31.
- the mobile terminal management server 10 provides process flow data (a part or all of the process flow data) to the mobile terminal 31 to display the form on the display screen of the mobile terminal 31. Processing is executed.
- the login management is the same as the process flow data providing process (see FIG. 5) described above, and thus the description thereof is omitted here.
- the form output process is different from the process flow data providing process in that a form in a predetermined format is output.
- the process flow DB 18 update process described here (that is, the process flow DB 18 update process in the form output process) is an example of the database update process (see FIG. 10).
- the mobile terminal 31 transmits a process flow data update request input screen request to the mobile terminal management server 10 in response to, for example, an operation input by the user X of the mobile terminal 31 (step S501).
- the mobile terminal management server 10 transmits a process flow data update request input screen corresponding to the received process flow data update request input screen request (step S401).
- FIG. 12 is an explanatory diagram showing an example of a process flow data update request input screen.
- the process flow data update request input screen includes identification information to be updated (in this example, data corresponding to the main key portion of the process flow data. That is, the process flow number and the process flow detail number). .)), A business process input area 1202 for receiving an input of the type of the business process indicated by the process data by the user X, and a detailed data input area for receiving the input of the contents of other process data.
- the user X operates an operation unit (for example, a display area or a button displayed on the display unit on which the touch panel is arranged) included in the mobile terminal 31. That is, for example, when each input area is pressed by the finger of the user X, the portable terminal 31 starts accepting input of text data (including numbers and characters) for the pressed input area. And the portable terminal 31 displays a keyboard (not shown) on the display part in which the touch panel is arrange
- an operation unit for example, a display area or a button displayed on the display unit on which the touch panel is arranged
- the portable terminal 31 when receiving the selection of the business process input area 1202, the portable terminal 31 displays a predetermined business process name in a pull-down format so that it can be selected.
- the method of accepting input of process data is not limited to this, and for example, the portable terminal 31 may accept a plurality of process data collected in a predetermined data format at a time.
- the portable terminal 31 determines that it has accepted an update request for process flow data based on process data constituted by data input to each input area (step S503).
- the mobile terminal 31 transmits the received update request to the mobile terminal management server 10 (step S504).
- the mobile terminal management server 10 acquires the update condition data corresponding to the update request (step S403).
- the update condition data corresponding to the update request is acquired by the business process indicated by the update request and the type of the process flow data (that is, the business process input in the business process input area 1202 and the processing in step S402). This means update condition data that can be specified by the type indicated by the process flow data (see FIG. 4).
- the mobile terminal management server 10 compares the acquired process flow data with the update condition data (step S404) and determines whether or not the process flow data update condition is satisfied (step S405). ).
- the update condition of the process flow data is satisfied because one or more of the items set to “1” in the update condition data is not set to “1” in the status part of the process flow data. If it is determined that there is no change (N in step S405), the mobile terminal management server 10 creates an update error notification and transmits it to the mobile terminal 31 (step S406), and ends the processing here.
- the mobile terminal 31 displays the update error notification display screen on the display screen of the display unit included in the mobile terminal 31 based on the received update error notification (step S506).
- FIG. 13 is an explanatory diagram showing an example of an update error notification display screen.
- the update error notification display screen is provided with an update error notification display area 1301 that is displayed superimposed on the process flow data update request input screen.
- a detail display button 1302 for receiving a request to display details of the update condition
- a close button 1303 for receiving a request for deleting the update error notification display area 1301 from the display screen is provided.
- the mobile terminal 31 can recognize, for example, the comparison result between the process flow data and the update condition data in the mobile terminal management server 10 (see FIG. For example, a comparison table indicating the status part of the process flow data and the process flow data update condition of the update condition data is displayed.
- the mobile terminal management server 10 transmits the updated process flow data to the mobile terminal 31 (step S408), and ends the processing here.
- the mobile terminal 31 displays a form display screen on the display screen of the display unit included in the mobile terminal 31 based on the received process flow data (step S507).
- FIG. 14 is an explanatory diagram showing an example of a form display screen.
- the form display screen includes a form display area 1401 for displaying a form based on the process flow data, a form status display area 1402, a back button 1403, and a change button 1404.
- the mobile terminal 31 changes the scale of the form displayed in the form display area 1401 in accordance with, for example, an operation of a keyboard or the like provided in the mobile terminal 31.
- part or all of the process flow data is displayed in a predetermined display form in the form display area 1401.
- information for displaying a part or all of the process flow data in a predetermined display form is created by the mobile terminal management server 10 and, for example, at the timing of step S408 in the form output process, It is assumed that it is transmitted to the terminal 31.
- the portable terminal 31 may be configured to display a part or all of the received process flow data in the form display area 1401 in a predetermined display format based on information stored in a storage device included in the mobile terminal 31.
- the form status display area 1402 is an area for displaying the type (or status, hereinafter referred to as status) of the form displayed in the form display area 1401.
- status As the status of the form, various forms such as an order slip, a delivery slip, an inspection slip, and an invoice can be considered.
- the return button 1403 is a button for accepting a request to return the display screen to the process flow data update request input screen.
- the mobile terminal 31 In response to the selection of the return button 1403 by the user X, the mobile terminal 31 not only returns the display screen to the process flow data update request input screen but also sends an update request to the mobile terminal management server 10. A request for canceling the update of the process flow data based on the above may be transmitted.
- the portable terminal 31 is input to each input area (in this example, the primary key data input area 1201, the business process input area 1202, and the detailed data input area 1203) according to the selection of the return button 33.
- the process flow data update request input screen may be displayed in a state indicating the text data (the business process selected in the business process input area 1202). With such a configuration, it is possible to easily confirm the input content by the user X.
- the change button 1404 is a button for accepting a request to change the display contents of the form display area 1401.
- a process for changing the display contents of the form display area 1401 will be described.
- the mobile terminal 31 determines whether a form status change request from the user X has been received (step S508).
- the mobile terminal 31 first accepts selection of the form status display area 1402 by the user X.
- the portable terminal 31 displays a list of form status names indicating the forms of the forms that can be displayed, for example, in a pull-down manner.
- FIG. 15 is an explanatory diagram for explaining the transition of the form status based on the state of the process flow data.
- images 1501 to 1504 are in the form of forms (specifically slips) that can be displayed in the form display area 1401 based on the process flow data.
- the images 1501 to 1504 are explanatory diagrams for explaining the transition of the form status, and do not show specific description examples for playing a role as various forms.
- an area 1511 indicates a form status name
- an area 1512 indicates a process flow type
- an area 1513 indicates a business process name of process data included in the process flow data. It is assumed that it is an area to be shown (in this example, a character string display area).
- the form status name corresponding to the type of process data included in the process flow data is displayed in the area 1511.
- the form status name (that is, the process The types of forms that can be displayed based on flow data will increase. This is not "whether or not there is the next type of form", but "the form status increases according to the state of the process flow data (that is, the types of forms that can be displayed increase)" means.
- the portable terminal 31 receives process flow data including business processes “orders”, “shipping instructions”, “shipping”, and “shipping inspection” before the processing of step S507 in the form output processing.
- the portable terminal 31 includes the business process “order received”, “shipment instruction”, “shipping”, “shipping inspection” in the process flow indicated by the received process flow data.
- the form corresponding to the form status name “order received slip” corresponding to the business process “order received” positioned at the top is displayed in the form display area 1401 (see FIG. 14).
- the mobile terminal 31 may be configured to display a form corresponding to the business process according to the process data newly added to the process flow data in the process of step S407 in the form display area 1401.
- step S508 If it is determined in the document status change request acceptance determination process (step S508) that the form status change request by the user X is not accepted (N in step S508), the portable terminal 31 proceeds to the process of step S510 described later.
- the portable terminal 31 displays a form corresponding to the received change request in the form display area 1401 (step S509).
- the mobile terminal 31 accepts the selection of the form status name “issue slip” corresponding to the business process “issue” by the user X, and displays the form (issue slip) corresponding to the business process “issue”. It is assumed that it is displayed in the area 1401. In this case, the mobile terminal 31 displays the form status name “issue slip” in the form status display area 1402.
- the ERP is a server that runs various types of 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 DB 18 for storing process flow data including various data related to a process flow including a plurality of business processes, and the process flow data stored in the process flow DB according to the progress of the process flow , And when there is a login request from the mobile terminals 31 to 3N (hereinafter referred to as the mobile terminal 31), it is determined whether or not the mobile terminal 31 is permitted to log in (eg, step S203, FIG. 8). If you decide to allow login, perform login processing and execute login processing.
- the process flow data browsing request from the logged-in portable terminal 31 is received (for example, the provision request is received in step S106; see FIG. 5), and the process stored in the process flow DB 18 is received in response to the received browsing request.
- Flow data is provided to the portable terminal 31 (for example, step S108; see FIG. 5).
- the process flow data is data including status data, common data, and process specific data. Data indicating the progress of each business process included in the process flow (for example, orders, shipping instructions, shipping, shipping inspection, sales). Common data is shared 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 (for example, order date or order text), and the status data is updated when the process-specific data is updated. (For example, the corresponding status data is changed from “0” to “1” in accordance with the addition of process-specific data.) Since it is configured, a business system that provides information related to a form to a mobile communication terminal (For example, a form inquiry system.) In addition to improving safety, it is necessary to update and search data in an ERP system (for example, a part functioning as a core business server in the mobile terminal management server 10) (in a business system). The processing load can be reduced.
- ERP for example, a part functioning as a core business server in the mobile terminal management server 10
- the process flow data stored in the process flow DB 18 is associated with update condition data indicating an update condition of the process flow data, and the mobile terminal management server 10 updates the process flow data. Since the process flow data is updated based on the update condition data associated with the process flow data (for example, step S405, see FIG. 11), the safety when updating the business data is improved. Is possible. That is, for the convenience of data management, for example, “shipping inspection”, which is a type of business process, must be registered only after the data related to the business processes “order”, “shipping instruction”, and “shipping” are registered. When the user desires, the update of the process flow data can be restricted as the user desires only by setting the update condition data.
- the mobile terminal management server 10 has a predetermined condition (for example, the process flow data stored in the process flow DB 18 stored in the process flow DB 18).
- Processes stored in the process flow DB 18 are stored in a temporary storage database (for example, the process flow data temporary storage DB 16) satisfying the condition that the particularly important information is not stored in the process flow data temporary storage DB 18.
- the process flow data stored in the temporary storage database may be provided to the portable terminal 31 (for example, step S107; see FIG. 5).
- the mobile terminal management server 10 performs logout processing for releasing the login state in response to a logout request from the mobile terminals 31 to 3N, and the logout processing is executed.
- the mobile terminal 31 to 3N is configured to request the communication history information related to the provision of slip data to be deleted (for example, step SS114; see FIG. 5). It becomes possible to prevent information leakage due to loss of the portable terminals 31 to 3N.
- the mobile terminal management server 10 measures the time during which information is not exchanged with the mobile terminals 31 to 3N in the login state, and the measured time reaches a predetermined time. (For example, step S112, refer to FIG. 5.) Since the mobile terminal 31 to 3N are requested to delete the communication history information related to the provision of the process flow data, the communication history information can be deleted. Thus, it is possible to prevent information from leaking due to loss of the mobile terminals 31 to 3N.
- FIG. 16 is an explanatory diagram for explaining the usefulness of the database update process (see FIG. 10) executed by the mobile terminal management server 10 described above.
- FIG. 16A is a table showing a comparison result of the data update amount when the first process data is input.
- the type of process data to be input first that is, the type of business process
- “conventional” means a database provided with a table for each business process, as shown in FIG.
- the “data amount difference” does not indicate an exact numerical value, but a case where the data stored in the conventional table is updated and a new type process flow table (that is, the process flow table PT, see FIG. 3).
- the case where the amount of data handled by the new type increases is + ( Plus)
- the case where the amount of data handled by the new type is smaller is ⁇ (minus)
- the case where the amount of data handled by the new type and the conventional type can be regarded as the same is “0”.
- the new type handles more data as much as the status part needs to be updated.
- the data amount of the status portion is small, it can be said that there is substantially no difference in the amount of I / O data (input data and output data) between the conventional type and the new type.
- FIG. 16B is a table showing a comparison result of data update amounts when the process data after the second process is input. That is, for example, the main key part, the reference key part, the type part, the status part, the common data part, and a part of the process specific data part (for example, process specific data “reception date”, “ “Order received text”) is a table showing a comparison result of the data update amount when the process data is input according to the business process included in the process flow already input in the process flow table PT.
- “conventional type” defines other process data (for example, business process “shipment” corresponding to the process data (order data) registered in the order table, for example, in order to define the correspondence with the input process data.
- the main key part, reference key part, type part, common data part, and process specific data part in this example are supported as the shipping instruction data.
- the new type has a smaller amount of I / O data than the conventional type, which is advantageous in terms of system performance.
- database I / O can be reduced, it is possible to reduce the amount of writing, reduce the capacity of the entire database, and reduce the processing load required for data search processing. .
- one of the factors for reducing the processing load required for the search process is that the process (process data) does not extend over a plurality of tables.
- the new type has the advantage that the input order of the process data can be made somewhat random. That is, for example, in the case of the type “inventory sales”, in the case of the conventional type, the order of the process flow is limited to the order of orders, shipping instructions, delivery, delivery inspection, and sales, and the order cannot be changed.
- the relationship between business processes is expressed by assigning the primary key of the previous business process to the data of the subsequent business process (for example, in the shipping instruction table). “Order number” and “Order details” (see FIG. 18).
- the new type table structure the data of related business processes is stored in the same entry (that is, the same column of the same table).
- the order of business processes can be flexibly rearranged. That is, for example, when the actual business order is “order received after shipping instruction”, the process data input order can be made to conform to the actual business order. Therefore, it is advantageous over the conventional type in progress management (in other words, in internal control). Specifically, the current business order in the wholesale industry is “order received after shipping instruction”.
- the contents of the update condition data can be set by, for example, a system administrator or a user, thereby preventing unauthorized process data from being input.
- the update condition data for example, it is limited to the order in which there is a problem in internal control, such as "can record sales without a record of delivery" Can be provided, and the reliability of the database can be improved.
- the load required to inquire about the progress of the process flow can be reduced. That is, when confirming how far the process flow has progressed, in the conventional table structure, it is necessary to confirm the registration status of all the tables from the start slip table to the final slip table. For example, when the type “inventory sales” is taken as an example, it is necessary to confirm five tables of orders, shipping instructions, delivery, delivery inspection and billing. On the other hand, since the new table structure has the progress status of the process flow as a “status part”, the progress can be confirmed only by querying one table and one entry. This is advantageous when using or developing a progress inquiry screen.
- a database for example, process flow DB 18
- a process flow data management server for example, mobile terminal management server 10
- process flow data management server for example, mobile terminal management server 10.
- client for example, the mobile terminals 31 to 3N or the integrated core business system 100, 200, 300
- the business flow It is possible to construct a system in which the processing load required for providing data related to data (for example, process flow data indicating form information necessary for creating a form) is reduced as compared with the related art.
- the update not satisfied when the process flow data management server determines not to register the process data.
- An unsatisfied update condition that is a condition is specified, and the specified unsatisfied update condition is notified to a client (for example, the mobile terminals 31 to 3N or the integrated core business system 100, 200, 300), and is not satisfied at a predetermined timing. It is determined whether the update condition specified as the update condition is satisfied, and the process data corresponding to the update condition is registered in the process flow table PT when it is determined that the update condition specified as the unsatisfied update condition is satisfied. It is good also as a structure.
- the client it is possible to prevent the client from having to input the same data a plurality of times. That is, the user who is notified of the unsatisfied update condition inputs the process flow data again because the already input process data is registered in the process flow table if an operation for satisfying the unsatisfied condition is performed. There is no need.
- the server side that manages the process flow data does not need to perform the process necessary for identifying the process flow data corresponding to the received process data and determining whether the update condition is satisfied. The number of times can be reduced.
- the process flow data management server (for example, the mobile terminal management server 10) includes a condition table, and status data (for example, data stored in the status portion of the process flow table PT based on the progress determination condition, see FIG. 3). .) Determines whether or not the progress determination condition is satisfied, and indicates the progress according to the progress determination condition determined to be satisfied by the client (for example, the mobile terminals 31 to 3N and the integrated core business systems 100, 200, and 300). ) May be notified.
- the process flow type includes sample shipment, service sales, name change (sales), name change (shipment), sales return (with original transaction reference), sales return (original transaction reference) None), sales amount adjustment (plus), sales amount adjustment (minus), etc.
- the “progress status determination condition” indicates a criterion for determining the progress status of the process flow.
- a business process for example, order, shipping instruction, delivery, etc.
- the mobile terminal management server 10 has the process flow data entry in the “completed” state when the status portion of the process flow data stored in the process flow table PT matches the progress determination condition data. (That is, it is determined that the process flow indicated by the process flow data is completed), and a process (notification process) for notifying a predetermined client to that effect is performed.
- a process notification process
- start timing of the progress status determination processing or notification processing may be when a request is made from a client, or may be a preset timing.
- the progress status determination condition data is configured to include a completion condition for determining whether the process flow has been completed.
- a system can be constructed.
- the progress status determination condition data is not limited to data for determining that the process flow is in the “completed” state, and includes, for example, data for determining that the process flow is in the “50% complete” state. It is good also as a structure.
- the progress status determination condition data may be configured to indicate the type of process data that should be input before a predetermined time elapses from the input of the first process data.
- a configuration may be adopted in which restrictions such as a password to be input and conditions to be satisfied when the user changes the contents of the common data portion are added.
- 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. 8, 10, and 11).
- INDUSTRIAL APPLICABILITY in a business system (particularly, an ERP system) that provides information on a form to a mobile communication terminal, it is useful for improving safety and reducing the processing load required for data update and search. .
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
図1は、本発明の一実施の形態に係る帳票照会システム500の構成例を示すブロック図である。図1に示すように、帳票照会システム500は、携帯端末管理サーバ10と、中継機20と、複数の携帯端末31~3N(Nは任意の正の整数)と、統合基幹業務システム100と、統合基幹業務システム200と,統合基幹業務システム300とを含む。携帯端末管理サーバ10と各携帯端末31~3Nとは、それぞれ、インターネットなどの通信ネットワーク40及び中継機20を介して接続される。携帯端末管理サーバ10は、統合基幹業務システム100、統合基幹業務システム200、統合基幹業務システム300と、それぞれLAN(Local Area Network)や専用通信回線などの通信ネットワーク51,52,53を介して接続される。なお、携帯端末同士や統合基幹業務システム同士は、携帯端末管理サーバを介して通信可能な構成としてもよいし、通信不能な構成としてもよい。
(Comma Separated Values)形式に変換して携帯端末管理サーバ10に送信する機能を有する。なお、本例においては、基幹業務サーバ110は、FTP(File Transfer Protocol)によりCSV形式にしたデータファイルを携帯端末管理サーバ10に転送する。
20 中継機
31~3N 携帯端末
40 通信ネットワーク
51,52,52 通信ネットワーク
100,200,300 統合基幹業務システム
110,310 基幹業務サーバ
120,220 DWHサーバ
500 帳票照会システム
Claims (8)
- ERPが稼動するサーバであって、ユーザが使用する携帯端末からの要求に応じて通信ネットワークを介して各種データを提供する携帯端末管理サーバにおいて、
複数の業務プロセスを含むプロセスフローに関する各種データを含むプロセスフローデータを記憶するプロセスフローデータ記憶手段と、
前記プロセスフローの進捗状況に応じて前記プロセスフローデータ記憶手段に記憶されているプロセスフローデータを更新するプロセスフローデータ更新手段と、
前記携帯端末からのログイン要求があったときに、当該携帯端末に対してログインを許可するか否か判定するログイン判定手段と、
該ログイン判定手段によってログインを許可すると判定された場合にログイン処理を行うログイン処理手段と、
該ログイン処理手段によってログイン処理が実行されたログイン状態の前記携帯端末からのプロセスフローデータの閲覧要求を受け付ける閲覧要求受付手段と、
該閲覧要求受付手段によって受け付けられた閲覧要求に応じて、前記プロセスフローデータ記憶手段に記憶されているプロセスフローデータを前記携帯端末に提供するプロセスフローデータ提供手段とを含み、
前記プロセスフローデータは、ステータスデータと、共通データと、プロセス固有データとを含むデータであり、
前記ステータスデータは、前記プロセスフローに含まれる複数の業務プロセスそれぞれの進捗状況を示すデータであり、
前記共通データは、同一のプロセスフローに含まれる業務プロセス間で共通するデータであり、
前記プロセス固有データは、同一のプロセスフローに含まれる各業務プロセスに固有のデータであり、
前記プロセスフローデータ更新手段は、前記プロセス固有データの更新状況に応じて前記ステータスデータを更新する
ことを特徴とする携帯端末管理サーバ。 - 前記プロセスフローデータ記憶手段に記憶されているプロセスフローデータには、プロセスフローデータの更新条件を示す更新条件データが対応付けされており、
前記プロセスフローデータ更新手段は、更新するプロセスフローデータに対応付けされている更新条件データに基づいてプロセスフローデータを更新する
請求項1記載の携帯端末管理サーバ。 - 前記プロセスフローデータ記憶手段に記憶されたプロセスフローデータのうち所定条件を満たすデータを一時保管データベースに保存するプロセスフローデータ保存手段を含み、
前記プロセスフローデータ提供手段は、前記プロセスフローデータ記憶手段に記憶されているプロセスフローデータのうち、前記一時保管データベースに保存されているプロセスフローデータを前記携帯端末に提供する
請求項1または請求項2記載の携帯端末管理サーバ。 - ログイン状態の携帯端末からのプロセスフローデータの更新要求を受け付ける更新要求受付手段と、
該更新要求受付手段によって受け付けられた更新要求の更新内容と、当該更新要求を行った携帯端末を示す端末情報とを含む更新関連情報を蓄積する更新関連情報蓄積手段とを含み、
前記プロセスフローデータ更新手段は、所定のタイミングとなったときに、前記更新関連情報蓄積手段によって蓄積されている更新関連情報に従って前記プロセスフローデータ記憶手段に記憶されているプロセスフローデータを更新する
請求項1から請求項3のうち何れかに記載の携帯端末管理サーバ。 - 前記携帯端末は、予め定められた正規のログイン操作を受け付けた場合にのみログインを許可するログイン判定手段を有する
請求項1から請求項4のうちいずれかに記載の携帯端末管理サーバ。 - 前記携帯端末からのログアウト要求があったことに応じて、ログイン状態を解除するログアウト処理を行うログアウト処理手段と、
該ログアウト処理手段によってログアウト処理が実行されたことに応じて、前記携帯端末に対してプロセスフローデータの提供に関わる通信履歴情報を削除するよう要求する履歴情報削除要求手段とを含む
請求項1から請求項5のうちいずれかに記載の携帯端末管理サーバ。 - ログイン状態の前記携帯端末との情報のやりとりが行われていない時間を計測する時間計測手段と、
該時間計測手段の計測時間が所定時間に達した場合に、前記携帯端末に対してプロセスフローデータの提供に関わる通信履歴情報を削除するよう要求する履歴情報削除要求手段とを含む
請求項1から請求項6のうちいずれかに記載の携帯端末管理サーバ。 - ERPを稼動させ、ユーザが使用する携帯端末からの要求に応じて通信ネットワークを介して各種データを提供する処理を携帯端末管理サーバに実行させる携帯端末管理プログラムであって、
複数の業務プロセスを含むプロセスフローに関する各種データを含むプロセスフローデータを記憶するプロセスフローデータ記憶手段を備えた前記携帯端末管理サーバに、
前記プロセスフローの進捗状況に応じて前記プロセスフローデータ記憶手段に記憶されているプロセスフローデータを更新するプロセスフローデータ更新処理と、
前記携帯端末からのログイン要求があったときに、当該携帯端末に対してログインを許可するか否か判定するログイン判定処理と、
該ログイン判定処理にてログインを許可すると判定した場合にログイン処理を行うログイン処理実行処理と、
該ログイン処理実行処理にてログイン処理が実行されたログイン状態の前記携帯端末からのプロセスフローデータの閲覧要求を受け付ける閲覧要求受付処理と、
該閲覧要求受付処理にて受け付けた閲覧要求に応じて、前記プロセスフローデータ記憶手段に記憶されているプロセスフローデータを前記携帯端末に提供するプロセスフローデータ提供処理とを実行させ、
前記プロセスフローデータは、ステータスデータと、共通データと、プロセス固有データとを含むデータであり、
前記ステータスデータは、前記プロセスフローに含まれる複数の業務プロセスそれぞれの進捗状況を示すデータであり、
前記共通データは、同一のプロセスフローに含まれる業務プロセス間で共通するデータであり、
前記プロセス固有データは、同一のプロセスフローに含まれる各業務プロセスに固有のデータであり、
前記プロセスフローデータ更新処理において、前記プロセス固有データの更新状況に応じて前記ステータスデータを更新する処理を
実行させるための携帯端末管理プログラム。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013529473A JP5597769B2 (ja) | 2011-12-28 | 2011-12-28 | 携帯端末管理サーバ、および携帯端末管理プログラム |
CN201180070524.2A CN103703477A (zh) | 2011-12-28 | 2011-12-28 | 便携终端管理服务器及便携终端管理程序 |
EP11878456.0A EP2682904A1 (en) | 2011-12-28 | 2011-12-28 | Portable terminal management server and portable terminal management program |
US14/007,054 US20140089034A1 (en) | 2011-12-28 | 2011-12-28 | Portable terminal management server and portable terminal management program |
PCT/JP2011/007344 WO2013098897A1 (ja) | 2011-12-28 | 2011-12-28 | 携帯端末管理サーバ、および携帯端末管理プログラム |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2011/007344 WO2013098897A1 (ja) | 2011-12-28 | 2011-12-28 | 携帯端末管理サーバ、および携帯端末管理プログラム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013098897A1 true WO2013098897A1 (ja) | 2013-07-04 |
Family
ID=48696470
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2011/007344 WO2013098897A1 (ja) | 2011-12-28 | 2011-12-28 | 携帯端末管理サーバ、および携帯端末管理プログラム |
Country Status (5)
Country | Link |
---|---|
US (1) | US20140089034A1 (ja) |
EP (1) | EP2682904A1 (ja) |
JP (1) | JP5597769B2 (ja) |
CN (1) | CN103703477A (ja) |
WO (1) | WO2013098897A1 (ja) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016099952A (ja) * | 2014-11-26 | 2016-05-30 | 株式会社アイ・ピー・エス | 帳票データ管理装置、帳票データ管理プログラム、および帳票データ管理方法 |
JP2017102777A (ja) * | 2015-12-03 | 2017-06-08 | 富士通株式会社 | 負荷分散処理サーバ、負荷分散処理方法、及び、システム |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10214113A (ja) * | 1996-05-15 | 1998-08-11 | Hitachi Ltd | 掲示板型データベースを用いた業務処理システム及びその処理方法 |
JP2002312208A (ja) | 2001-04-11 | 2002-10-25 | Mitsubishi Electric Corp | データウェアハウスシステム |
JP2003323582A (ja) | 2002-04-30 | 2003-11-14 | Nec System Technologies Ltd | 携帯電話を使用した電子帳票システム |
JP2006285914A (ja) * | 2005-04-05 | 2006-10-19 | Casio Comput Co Ltd | データ検索処理装置及びプログラム |
JP2007200136A (ja) | 2006-01-27 | 2007-08-09 | Fuji Xerox Co Ltd | 業務支援システム、業務支援プログラムおよび業務支援方法 |
WO2008032393A1 (en) * | 2006-09-15 | 2008-03-20 | Fujitsu Limited | Information processing method and device for work process analysis |
WO2011148565A1 (ja) * | 2010-05-25 | 2011-12-01 | 株式会社アイ・ピー・エス | データベース、管理サーバ、および管理プログラム |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0807896A3 (en) * | 1996-05-15 | 2000-08-30 | Hitachi, Ltd. | Business processing system employing a notice board business system database and method of processing the same |
US7107240B1 (en) * | 1999-10-06 | 2006-09-12 | Goldman Sachs & Co. | Order centric tracking system and protocol for communications with handheld trading units |
US7711694B2 (en) * | 2002-12-23 | 2010-05-04 | Sap Ag | System and methods for user-customizable enterprise workflow management |
EP1684171A4 (en) * | 2003-10-27 | 2009-03-18 | Panasonic Corp | SYSTEM FOR SUPPORTING THE INTRODUCTION OR BZW. OPERATING INTEGRATED JOB SOFTWARE |
CN101763570A (zh) * | 2008-11-14 | 2010-06-30 | 镇江雅迅软件有限责任公司 | 一种企业信息化数据的整合方法 |
CN102193792A (zh) * | 2010-12-24 | 2011-09-21 | 东莞市高明企业服务有限公司 | 基于soa的服务企业协同管理***开发方法及*** |
-
2011
- 2011-12-28 CN CN201180070524.2A patent/CN103703477A/zh active Pending
- 2011-12-28 EP EP11878456.0A patent/EP2682904A1/en not_active Withdrawn
- 2011-12-28 JP JP2013529473A patent/JP5597769B2/ja not_active Expired - Fee Related
- 2011-12-28 WO PCT/JP2011/007344 patent/WO2013098897A1/ja active Application Filing
- 2011-12-28 US US14/007,054 patent/US20140089034A1/en not_active Abandoned
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10214113A (ja) * | 1996-05-15 | 1998-08-11 | Hitachi Ltd | 掲示板型データベースを用いた業務処理システム及びその処理方法 |
JP2002312208A (ja) | 2001-04-11 | 2002-10-25 | Mitsubishi Electric Corp | データウェアハウスシステム |
JP2003323582A (ja) | 2002-04-30 | 2003-11-14 | Nec System Technologies Ltd | 携帯電話を使用した電子帳票システム |
JP2006285914A (ja) * | 2005-04-05 | 2006-10-19 | Casio Comput Co Ltd | データ検索処理装置及びプログラム |
JP2007200136A (ja) | 2006-01-27 | 2007-08-09 | Fuji Xerox Co Ltd | 業務支援システム、業務支援プログラムおよび業務支援方法 |
WO2008032393A1 (en) * | 2006-09-15 | 2008-03-20 | Fujitsu Limited | Information processing method and device for work process analysis |
WO2011148565A1 (ja) * | 2010-05-25 | 2011-12-01 | 株式会社アイ・ピー・エス | データベース、管理サーバ、および管理プログラム |
Non-Patent Citations (1)
Title |
---|
KAZUO KIMURA: "Keitai Denwa o Katsuyo shita Kigyo System Keitai Denwa o Gyomu Tanmatsu e, Mobile CRM Solution no Field Service Gyomu eno Tekiyo Jirei", TOSHIBA SOLUTION TECHNICAL NEWS, 2007 NEN (SHUNKI GO), vol. 9, 15 March 2007 (2007-03-15), pages 6 - 7 * |
Also Published As
Publication number | Publication date |
---|---|
EP2682904A1 (en) | 2014-01-08 |
US20140089034A1 (en) | 2014-03-27 |
CN103703477A (zh) | 2014-04-02 |
JPWO2013098897A1 (ja) | 2015-04-30 |
JP5597769B2 (ja) | 2014-10-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5386639B2 (ja) | データベース、データ管理サーバ、およびデータ管理プログラム | |
WO2013114440A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
JP5502251B1 (ja) | 帳票データ管理サーバ、および帳票データ管理プログラム | |
JP5479598B2 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
US20150081365A1 (en) | Mobile terminal management server and mobile terminal management program | |
US20150120354A1 (en) | Mobile terminal management server and mobile terminal management program | |
JP5597769B2 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
WO2013114441A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
WO2013114448A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
WO2014002138A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
WO2013114439A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
WO2013114449A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
JP5451885B2 (ja) | データベース、データ管理サーバ、およびデータ管理プログラム | |
WO2013114438A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
JP5558571B2 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
EP3007118A1 (en) | Cooperation server, non-transitory computer-readable storage medium storing cooperation program, and EC system | |
JPWO2013114445A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
WO2013114443A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
WO2013114445A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
JPWO2013114438A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
JPWO2013114439A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
JP2002189842A (ja) | ワークフロー管理制御システムとその方法並びにワークフロー管理制御プログラムを記録した記録媒体 | |
JPWO2013114441A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
JPWO2013114440A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム | |
JPWO2013114443A1 (ja) | 携帯端末管理サーバ、および携帯端末管理プログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2013529473 Country of ref document: JP Kind code of ref document: A |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11878456 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011878456 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14007054 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |