JP2014089707A - Transaction processing system and terminal device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce load on a user and load on a system when business resumes after the occurrence of an abnormal stop.SOLUTION: A transaction processing system comprises: a display unit configured to sequentially display, on a display device, transaction screens concerning a series of transactions included in one business flow; and a control unit configured such that before the input of transaction data is completed on each transaction screen, the transaction data input on the transaction screen is stored in a storage unit. The display unit re-displays a transaction screen in which a common data extracted as a commonly used one is set in a plurality of transactions of transaction data stored by the storage unit before the completion of input on a transaction screen that is abnormally stopped after an abnormal stop caused during the display of one of the transaction screens, and transaction data whose input has completed on another transaction screen before the abnormal stop.

Description

  The present invention relates to a transaction processing system and a terminal device.

  In business and other applications, information systems that digitize transaction documents such as purchase orders and invoices and process them on a computer screen are widely used. When such an information system is used, transaction data contained in electronic transaction documents can be transmitted / received via a network, transaction data can be managed using a database, etc. It is expected that office work efficiency and cost reduction will be realized (for example, see Patent Document 1 below).

Japanese Patent Laid-Open No. 2002-7954

  However, in general, in an information system, it is difficult to eliminate the possibility of an abnormal stop caused by a hardware failure, an increase in processing load, exception handling in software, or an erroneous operation by a user. If an information system that handles transaction documents or transaction data electronically stops before the transaction is completed, the data entered on the screen by the user will be lost and the user must re-enter the data once entered. I must. The burden of re-inputting transaction data after an abnormal stop is particularly large for the user when transaction data is continuously input on a screen for a plurality of transactions in one office work.

  Moreover, re-input of data after an abnormal stop is accompanied by a problem of an increase in input mistakes in addition to being a burden on the user. In order to reduce input mistakes at the time of re-inputting data, for example, it is conceivable to perform re-input while referring to data of related transactions that have already been completed. However, for example, in a transaction processing system in which transaction data is managed in an integrated manner by servers connected to a plurality of terminal devices, if a plurality of users try to refer to the transaction data after an abnormal stop of the system, data storage, etc. The associated load on system resources becomes a problem.

  Therefore, the present invention is intended to provide a new and improved mechanism that can reduce the burden on the user and the load on the system when resuming office work after an abnormal stop occurs.

  According to an embodiment of the present invention, a display unit that sequentially displays a transaction screen on a display device for a series of transactions included in one business flow, and before input of transaction data on each transaction screen is completed. A control unit that stores the transaction data input on the transaction screen in a storage unit, and the display unit is a transaction screen that has abnormally stopped after an abnormal stop that occurred during display of any of the transaction screens The transaction data stored by the storage unit before completion of the input on the transaction screen and the transaction data input completed on the other transaction screen before the abnormal stop are commonly used in a plurality of transactions. Provided is a transaction processing system for redisplaying the transaction screen in which common data extracted as a result is set.

  According to this configuration, when an abnormal stop occurs during the display of any of the transaction screens for a series of transactions included in one business flow, the transaction screen displayed at the time of the abnormal stop is displayed by the user. Transaction data that has been input and is temporarily stored in the storage unit, and common data that is used in common among multiple transactions among transaction data that has been input before the abnormal stop are regenerated after the abnormal stop. It is automatically set on the displayed transaction screen.

  The transaction processing system includes a terminal device capable of communicating with an information processing device via a communication network, the transaction screen is generated by the information processing device, and the terminal device includes the display unit. You may prepare.

  The terminal device may further include a communication unit that transmits the transaction data input on the transaction screen to the information processing device when the input of the transaction data on each transaction screen is completed. .

  The common data may be extracted by the information processing apparatus.

  The terminal device further includes the control unit, and the control unit deletes the transaction data stored in the storage unit when the transmission of transaction data to the information processing device by the communication unit is completed. May be.

  According to another embodiment of the present invention, a terminal device capable of communicating with an information processing apparatus via a communication network, the information processing apparatus regarding a series of transactions included in one business flow Display the transaction screen generated by the display device in sequence on the display device, and when the transaction data input on each transaction screen is completed, the transaction data input on the transaction screen is transmitted to the information processing device And a controller that stores the transaction data input on the transaction screen in the storage unit before the input of the transaction data on each transaction screen is completed. After the abnormal stop that occurred during the display of the transaction screen, the transaction screen that is abnormally stopped, the transaction data stored in the storage unit and the transaction data transmitted to the information processing device by the communication unit Redisplay plurality of the transaction screen common data extracted by the information processing apparatus as the one used commonly is set in a transaction, the terminal device is provided.

  Moreover, the said control part may delete the transaction data memorize | stored in the said memory | storage part, when transmission of the transaction data to the said information processing apparatus by the said communication part is completed

  According to the technology according to the present disclosure, it is possible to reduce the burden on the user and the load on the system when resuming office work after an abnormal stop occurs.

It is a schematic diagram which shows the outline | summary of the transaction processing system which concerns on 1st Embodiment. It is explanatory drawing for demonstrating the relationship between a business flow and transaction. It is a block diagram which shows an example of a structure of the terminal device which concerns on 1st Embodiment. It is explanatory drawing for demonstrating an example of a transaction screen. It is explanatory drawing for demonstrating an example of transaction data in execution. It is a block diagram which shows an example of a structure of the transaction processing server which concerns on 1st Embodiment. It is explanatory drawing which shows an example of the data structure in the memory | storage part of the transaction processing server which concerns on 1st Embodiment. It is explanatory drawing for demonstrating an example of a common data definition. It is explanatory drawing which shows a mode that common data is memorize | stored as an example. It is explanatory drawing for demonstrating the timing at which common data are produced | generated and deleted. It is the 1st part of the sequence figure showing an example of the flow of transaction processing concerning a 1st embodiment. It is a 2nd part of the sequence diagram which shows an example of the flow of the transaction processing which concerns on 1st Embodiment. It is a block diagram which shows an example of a structure of the transaction processing server which concerns on 2nd Embodiment. It is explanatory drawing for demonstrating an example of transaction history data. It is a sequence diagram which shows an example of the flow of the transaction processing which concerns on 2nd Embodiment. It is a block diagram which shows an example of a structure of a general purpose computer.

  Exemplary embodiments of the present invention will be described below in detail with reference to the accompanying drawings. In addition, in this specification and drawing, about the component which has the substantially same function structure, duplication description is abbreviate | omitted by attaching | subjecting the same code | symbol.

The order of explanation is as follows.
1. 1. Description of First Embodiment 1-1. Overview of transaction processing system 1-2. Configuration example of terminal device 1-3. Configuration example of transaction processing server 1-4. Flow of processing 2. Description of Second Embodiment 2-1. Configuration example of transaction processing server 2-2. Process flow

<1. First Embodiment>
[1-1. Overview of transaction processing system]
FIG. 1 is a schematic diagram showing an outline of a transaction processing system 1 according to the first embodiment of the present invention. Referring to FIG. 1, transaction processing system 1 includes terminal devices 100 a and 100 b and transaction processing server 200. The terminal devices 100 a and 100 b and the transaction processing server 200 are connected to each other via the network 3.

  The terminal devices 100a and 100b are terminal devices used when a user of the transaction processing system 1 performs a transaction electronically. The terminal devices 100a and 100b have an integral or external display device, and display a transaction screen on the display device. In this embodiment, the user performs a series of transactions along a predefined business flow. Accordingly, the terminal devices 100a and 100b sequentially display a transaction screen on the display device for a series of transactions included in one business flow. In the example of FIG. 1, PCs (Personal Computers) are shown as the terminal devices 100a and 100b. However, the terminal devices 100a and 100b are not limited to such examples, and may be other types of terminal devices such as mobile phone terminals or PDAs (Personal Digital Assistants), or specialized for transaction purposes. A dedicated computer may be used.

  In the following description of the present specification, the terminal devices 100a and 100b are collectively referred to as the terminal device 100 by omitting the alphabet at the end of the reference sign, unless it is necessary to distinguish the terminal devices 100a and 100b from each other.

  The transaction processing server 200 is an information processing device that can communicate with the terminal device 100 via the network 3. In the present embodiment, the transaction processing server 200 generates a transaction screen along a predetermined business flow and sequentially displays the transaction screen on the display device of the terminal device 100. And transaction processing server 200 receives transaction data inputted on each transaction screen from terminal unit 100, and performs transaction electronically. The transaction handled by the transaction processing server 200 is not limited to electronic commerce that can include contract conclusion, sale, settlement, or the like, and is generally a unit of some information processing that requires user input (also referred to as a transaction). ). Further, the terminal device 100 may have a function of generating a transaction screen instead of the transaction processing server 200.

  The network 3 is a communication network that connects between the terminal device 100 and the transaction processing server 200. The network 3 may be any communication network such as the Internet, an IP-VPN (Internet Protocol-Virtual Private Network), a dedicated line, a LAN (Local Area Network), or a WAN (Wide Area Network). It does not matter whether the network 3 is wired or wireless.

  FIG. 2 is an explanatory diagram for explaining the relationship between the business flow and the transaction in the present embodiment. Referring to FIG. 2, transaction screens S1 to Sn corresponding to individual transactions included in one business flow are shown. In starting the transaction, first, one of the transaction screens S1 to Sn is displayed on the display device of the terminal device 100. When the input of the transaction data by the user on the displayed transaction screen is completed, the transaction data is transmitted to the transaction processing server 200, and the transaction is performed electronically in the transaction processing server 200. That is, the transaction in the present embodiment, from the start to the end, (1) display of transaction screen, (2) input of transaction data, (3) transmission of transaction data (from terminal device 100 to transaction processing server), (4) It may include four stages: execution of a transaction. The business flow associates a series of transaction screens S1 to Sn related to one business (or business) in a predetermined order, and the user inputs transaction data on the transaction screens S1 to Sn along the business flow. Thus, the user can perform a group of office work.

  Next, the configurations of the terminal device 100 and the transaction processing server 200 for reducing the burden on the user and the load on the system when resuming office work after an abnormal stop has occurred in the transaction processing system 1 described above are more specifically described. explain.

[1-2. Example of terminal device configuration]
FIG. 3 is a block diagram showing an example of the configuration of the terminal device 100 according to the first embodiment of the present invention. Referring to FIG. 3, the terminal device 100 includes a display unit 110, a communication unit 120, a storage unit 130, and a control unit 140.

  The display unit 110 functions as a display unit for displaying a screen on a display device (integrated or externally attached) of the terminal device 100. More specifically, the display unit 110 sequentially displays the transaction screens S <b> 1 to Sn described above with reference to FIG. 2 on the screen of the display device in accordance with an instruction from the control unit 140.

  FIG. 4 is an explanatory diagram for explaining an example of the screen content of the transaction screen displayed by the display unit 110. Referring to FIG. 4, the transaction screen 112 as an example includes a transaction data input column 114 and a transmission button 116 in addition to a display column such as a screen title (“transaction screen”), a transaction type, and a processing date. Further, the transaction data input field 114 includes input items for a store number, a subject, an account number, and an amount. In such a transaction screen 112, for example, the user clicks a transmission button 116 after completing the input (or selection) of transaction data for each input item of store number, item, account number, and amount. Then, the input transaction data is transmitted to the transaction processing server 200, and an electronic transaction is performed.

  Returning to FIG. 3, the description of the configuration of the terminal device 100 is continued.

  The communication unit (terminal communication unit) 120 functions as a communication unit for performing communication with the transaction processing server 200 via the network 3 illustrated in FIG. For example, the communication unit 120 receives each transaction screen generated in the transaction processing server 200 and outputs it to the display unit 110. In addition, when the input of transaction data by the user on each transaction screen is completed (for example, when the transmission button 116 is clicked on the transaction screen 112 in FIG. 4), the communication unit 120 inputs on the transaction screen. The processed transaction data is transmitted to the transaction processing server 200.

  The storage unit 130 functions as a storage unit in the terminal device 100 using a storage medium such as a hard disk or a semiconductor memory. For example, in this embodiment, the memory | storage part 130 memorize | stores the transaction data 132 in execution, before the input of transaction data on each transaction screen is completed. The ongoing transaction data 132 is data for storing transaction data input on each transaction screen in association with a screen identifier for identifying the transaction screen.

  FIG. 5 is an explanatory diagram for explaining an example of the ongoing transaction data 132. Referring to FIG. 5, an example of a transaction screen 112 in the middle of a user inputting transaction data is shown on the left side of the drawing. Further, on the right side of the figure, an example of the ongoing transaction data 132 stored in the storage unit 130 at that time is shown.

  First, on the transaction screen 112, the user inputs transaction data “1234XXX” in the account number column and “1,000,000” in the amount column among the input items in the input column 114. However, the user has not clicked the transmission button 116 at this time, and therefore the input transaction data has not been transmitted to the transaction processing server 200 yet.

  At this time, for example, the control unit 140 described later detects a user input to the input field 114 of the transaction screen 112 and outputs the input transaction data and a screen identifier for identifying the transaction screen 112 to the storage unit 130. . Then, the storage unit 130 stores the data input from the control unit 140 as the running transaction data 132. In the example of FIG. 15, the data “office flow number = F1”, “screen identifier = S1”, “input data 01 = account number, 1234XXX”, and “input data 02 = money amount, 1,000,000” are executed. It is stored as medium transaction data 132. It should be noted that the expression “input data 01 = account number, 1234XXX” in the ongoing transaction data 132 indicates that the data item name of the first transaction data input by the user on the transaction screen (screen identifier = S1) is “account number”. , The data value is “1234XXX”.

  Returning to FIG. 3, the description of the configuration of the terminal device 100 is further continued.

  The control unit 140 controls the overall operation of each unit of the terminal device 100 using a processing device such as a CPU (Central Processing Unit). For example, as described above, the control unit 140 stores the transaction data input on the transaction screen in the storage unit 130 before the input of the transaction data on each transaction screen displayed by the display unit 110 is completed. It is stored as transaction data 132 during execution. Here, before completion of input of transaction data, for example, when the user clicks the transmission button 116 on the transaction screen 112 illustrated in FIG. 4, the input transaction data is transferred from the terminal device 100 to the transaction processing server 200. Can be equivalent to before being transmitted.

  Further, for example, when the input of transaction data on each transaction screen is completed, the control unit 140 causes the transaction data input on the transaction screen to be transmitted from the communication unit 120 to the transaction processing server 200.

  Further, for example, when the transmission of the transaction data input from the communication unit 120 to the transaction processing server 200 is completed, the control unit 140 deletes the ongoing transaction data 132 stored in the storage unit 130. Thereby, the system resources can be used efficiently without the storage capacity for the transaction data 132 being executed in the storage unit 130 increasing as the business flow proceeds.

  Further, for example, the control unit 140 transfers the running transaction data 132 stored in the storage unit 130 from the communication unit 120 to the transaction processing server 200 after an abnormal stop that occurred during display of any transaction screen. Send it. The in-execution transaction data 132 includes the screen identifier of the transaction screen that has stopped abnormally and the transaction data that has already been input on the transaction screen at the time of abnormal stop. Therefore, the transaction processing server 200 that has received the in-execution transaction data 132 can regenerate the abnormally stopped transaction screen and display it on the terminal device 100, as will be described later, and the transaction data that has already been input. Can be automatically set on the transaction screen.

[1-3. Example of transaction processing server configuration]
FIG. 6 is a block diagram showing an example of the configuration of the transaction processing server 200 according to the first embodiment of the present invention. Referring to FIG. 6, the transaction processing server 200 includes a communication unit 210, a storage unit 220, and a transaction processing unit 230.

  The communication unit 210 functions as a communication unit for performing communication with the terminal device 100 via the network 3 illustrated in FIG. For example, the communication unit 210 transmits each transaction screen generated in the transaction processing unit 230 described later to the terminal device 100. For example, the communication unit 210 receives transaction data transmitted from the terminal device 100 when input of transaction data on each transaction screen is completed, and outputs the transaction data to the transaction processing unit 230. Furthermore, the communication unit 210 receives the ongoing transaction data 132 transmitted from the terminal device 100 after an abnormal stop that occurred during the display of any transaction screen, and outputs it to the transaction processing unit 230.

  The storage unit 220 functions as a storage unit in the transaction processing server 200 using a storage medium such as a hard disk or a semiconductor memory. More specifically, in the present embodiment, the storage unit 220 stores a work flow definition 222, a common data definition 224, execution status data 226, and common data 228 as shown in FIG. Note that the storage unit 220 does not necessarily have to be physically realized as one storage medium. That is, the data stored in the storage unit 220 may be distributed and stored in different storage media (such as a file system or a database) that are built into the transaction processing server 200 or externally connected.

  FIG. 7 is an explanatory diagram showing a simplified example of the data configuration in the storage unit 220.

  Of the data stored in the storage unit 220, the business flow definition 222 is data set in the transaction processing server 200 in advance. The business flow definition 222 includes a business flow number and a plurality of screen identifiers (screen identifier 01, screen identifier 02,...) Corresponding to the transaction screen of each transaction included in the business flow represented by the business flow number. With such a business flow definition 222, it is possible to define which transaction screens should be displayed in order along the business flow.

  The common data definition 224 is data set in the transaction processing server 200 in advance, like the business flow definition 222. The common data definition 224 includes a business flow number for identifying a business flow, and a plurality of common data information related to the business flow represented by the business flow number. Common data information is information relating to individual data items that are commonly used across a plurality of transaction screens in one business flow. In the example of FIG. 7, each common data information includes a common data name (such as common data name 01 or common data name 02), and a plurality of sets of screen identifiers and item names (screen identifier 01, item name 01, screen identifier). 02 and item name 02 ...).

  FIG. 8 is an explanatory diagram for explaining an example of the data of the common data definition 224. In the upper part of FIG. 8, transaction screens S1, S2, S3, S4 and S5 are shown in order along the business flow represented by the business flow identifier = F1. Among these, the screen items of the transaction screen S1 are “account number”, “amount”, “store number”, and “subject”. The screen items of the transaction screen S2 are “account” and “communication column”. The screen item of the transaction screen S3 is “name”. The screen items of the transaction screen S4 are “account NO” and “balance”. The screen item of the transaction screen S5 is “cash”. Here, among these screen items, “account number” on the transaction screen S1, “account” on the transaction screen S2, and “account NO” on the transaction screen S4, which have different item names, are substantially input. The data is common. Similarly, the “money amount” on the transaction screen S1 and the “cash” on the transaction screen S5 have different item names, but have substantially the same input data. The common data definition 224 defines data items that are commonly used across a plurality of such transaction screens.

  Referring to the lower part of FIG. 8, as common data definition of the office flow number = F1, two pieces of common data information are defined in which common data name 01 = transaction account and common data name 02 = transaction amount, respectively. Among these, common data name 01 = common data information on trading accounts includes (screen identifier 01 = S1, item name 01 = account number), (screen identifier 02 = S2, item name 02) according to the above screen items. = Account) and (screen identifier 03 = S4, item name 03 = account NO), three sets of screen identifiers and item names are included. Thereby, the common data of the item name “transaction account” is handled by the item name “account number” on the transaction screen S1, “account” on the transaction screen S2, and “account NO” on the transaction screen S4. It is recognized. Similarly, in the common data information about the common data name 02 = transaction amount, (screen identifier 01 = S1, item name 01 = amount) and (screen identifier 02 = S5, item name 02 = in accordance with the screen item) Two sets of screen identifiers and item names (cash) are included. Accordingly, it is recognized that the common data of the item name “transaction amount” is handled by the item name “amount” on the transaction screen S1 and “cash” on the transaction screen S5.

  Returning to FIG. 7, the description of an example of the data configuration in the storage unit 220 is continued.

  The execution status data 226 is data generated when a transaction is performed using the terminal device 100. The execution status data 226 includes an office flow number for identifying the office flow currently being executed, a screen identifier for identifying a transaction screen in which the current transaction data is input, and a terminal on which the transaction screen is operated. Including a terminal identifier for identifying. Among these, the business flow number and the terminal identifier are newly registered when the first transaction screen included in the business flow is displayed on the terminal device 100. The screen identifier is generated and updated sequentially when each transaction screen included in the business flow is displayed on the terminal device 100. Then, when all the transactions included in the business flow are completed, the execution status data 226 is deleted.

  The common data 228 is data generated while a transaction is performed using the terminal device 100. The common data 228 includes a business flow number corresponding to the business flow currently being executed, and a set of item names and values of each common data associated with the business flow number in the common data definition 224.

  FIG. 9 is an explanatory diagram illustrating, as an example, how the common data 228 is stored in the storage unit 220. The left side of FIG. 9 shows a state of the transaction screen 112 in which the input of transaction data by the user is completed. In the transaction screen 112, transaction data of account number = “1234XXX”, amount = “1,000,000”, store number = “999”, item = “normal” is input or selected. These transaction data are transmitted from the terminal device 100 when the user clicks the transmission button 116, and are received by the communication unit 210 of the transaction processing server 200.

  On the right side of FIG. 9, transaction data received by the communication unit 210 and common data 228 extracted from the transaction data are shown. In addition to the input transaction data described above, the received data includes a business flow number (= F1) and a screen identifier (= S1) representing the transaction target. From such received data, the common data 228 having two data items of transaction account = 1234XXX and transaction amount = 1,000,000 is extracted in accordance with the common data definition 224 illustrated in FIG. Can be done.

  Returning to FIG. 6, the description of the configuration of the transaction processing server 200 is continued.

  The transaction processing unit 230 controls electronic transaction processing by the transaction processing server 200 using a processing device such as a CPU, for example. For example, when receiving a business flow start request from the terminal device 100 via the communication unit 210, the transaction processing unit 230 refers to the business flow definition 222 and specifies the first transaction screen included in the requested business flow. . Then, the transaction processing unit 230 stores the business flow number and the screen identifier of the first transaction screen in the storage unit 220 as the execution status data 226, and generates the first transaction screen and transmits it to the terminal device 100.

  Further, for example, when the transaction processing unit 230 receives the transaction data input by the user from the terminal device 100 via the communication unit 210, the transaction processing unit 230 performs transaction processing based on the transaction data (for example, electronic trading or settlement). Do. Further, the transaction processing unit 230 extracts the common data 228 in the office flow currently being executed from the received transaction data, and stores it in the storage unit 220.

  Then, when there is a subsequent transaction included in the same business flow, the transaction processing unit 230 generates a transaction screen for the subsequent transaction. At this time, the transaction processing unit 230 determines data that can use the same value for each transaction screen among the common data 228 stored in the storage unit 220 according to the common data definition 224 described with reference to FIG. The value is set in advance on the transaction screen. Thereby, it is possible to reduce a burden of the user again inputting data commonly used in a plurality of transactions.

  Thereafter, the transaction processing unit 230 updates the screen identifier included in the execution status data 226 to the screen identifier of the new transaction screen, and transmits the generated new transaction screen to the terminal device 100. Instead, the transaction processing unit 230 deletes the execution status data 226 and the common data 228 stored in the storage unit 220 when the subsequent transaction included in the same business flow does not exist, and ends the business flow. Let

  Further, the transaction processing unit 230 may delete data that is not used in subsequent transactions from the common data 228 stored in the storage unit 220. For example, the transaction processing unit 230 determines which common data is not used in subsequent transactions based on the common data definition 224 that defines the correspondence between each transaction screen and the common data input or displayed on the transaction screen. Can be determined.

  FIG. 10 is an explanatory diagram for explaining the timing at which the common data 228 is generated and deleted. Here, it is assumed that a common data definition 224 similar to the content illustrated in FIG. 8 is defined. Referring to FIG. 10, “transaction account” in the common data 228 is generated when data of “account number” input in the transaction screen S 1 is received according to the common data definition 224. Then, when the transaction screen S2 is displayed, the value of “transaction account” stored in the transaction processing server 200 as the common data 228 is set as the value of the “account” on the transaction screen S2. Similarly, when the transaction screen S4 is displayed, the value of “transaction account” stored as the common data 228 is set as the value of “account NO” in the transaction screen S4. Thereafter, the transaction processing unit 230 refers to the common data definition 224 and determines that the “transaction account” is not used in the subsequent transaction screen. Then, transaction processing unit 230 deletes the “transaction account” data from common data 228 stored in storage unit 220. On the other hand, the “transaction amount” in the common data 228 is generated when the “amount” data input on the transaction screen S 1 is received according to the common data definition 224. Thereafter, when the transaction screen S5 is displayed, the value of “transaction amount” stored as the common data 228 is set as the value of “cash” on the transaction screen S5. Thus, by temporarily storing individual common data only within the period used in the transaction screen, it is possible to avoid an increase in storage capacity to be secured for the common data.

  Returning to FIG. 6, the transaction processing unit 230 further receives, for example, a screen identifier from the terminal device 100 after an abnormal stop that occurred during display of any transaction screen, and the received screen identifier and execution status data. It may be determined whether or not the screen identifier stored as 226 matches. Then, the transaction processing unit 230 may generate a transaction screen identified by the screen identifier and re-display it on the terminal device 100 only when it is determined that the two screen identifiers match. Thereby, it is possible to appropriately and safely resume the transaction that was in progress with respect to the terminal device 100 that performed the transaction at the time of the abnormal stop.

  At this time, the transaction processing unit 230 may set common data that has already been input in another transaction in the same business flow in the redisplayed transaction screen. For example, the transaction processing unit 230 can determine the common data to be set on the transaction screen to be redisplayed using the common data definition 224 and the screen identifier received from the terminal device 100. As a result, among the screen items of the transaction screen displayed at the time of the abnormal stop, even if the screen items that are not input by the user before the abnormal stop are items that can use the common data, the user It is not necessary to input again.

  The flow of transaction processing performed using the terminal device 100 and the transaction processing server 200 will be described with reference to a sequence diagram in the next section.

[1-4. Process flow]
11 and 12 are sequence diagrams illustrating an example of the flow of transaction processing according to the first embodiment. Among these, FIG. 11 shows the flow of transaction processing until the system abnormally stops during the transaction using the transaction screen S2 in a series of transactions. On the other hand, FIG. 12 shows the flow of transaction processing that is resumed after the system is restored after an abnormal stop.

  In FIG. 11, first, a business flow start request (business flow number = F1) is transmitted from the control unit 140 of the terminal device 100 to the transaction processing unit 230 of the transaction processing server 200 (S102). The office flow start request includes, for example, the office flow number of the office flow selected by the user and the terminal identifier of the terminal device 100.

  Next, the transaction processing unit 230 of the transaction processing server 200 that has received the business flow start request generates execution status data 226 including the requested business flow number and terminal identifier (S104). Then, the transaction processing unit 230 generates the first transaction screen (transaction screen S1) according to the business flow definition 222 and displays it on the terminal device 100 (S106). Further, the transaction processing unit 230 updates the screen identifier of the execution status data 226 generated in step S104 with the screen identifier of the first transaction screen (S108).

  Next, in the terminal device 100 on which the transaction screen S1 is displayed, transaction data is input by the user (S110). Then, the control unit 140 of the terminal device 100 stores the input transaction data in the storage unit 130 of the terminal device 100 as the ongoing transaction data 132 (S112). Such processing is repeated until transaction data is input to all necessary input items on the transaction screen by the user.

  When the transaction data input by the user is completed, a transaction data input completion notification is transmitted from the terminal device 100 to the transaction processing server 200 (S114). The transaction data input completion notification includes, for example, the business flow number, the screen identifier of the transaction screen, and the input individual transaction data. Further, when the transmission of the input completion notification is completed, the control unit 140 of the terminal device 100 deletes the ongoing transaction data 132 (S116).

  Next, the transaction processing unit 230 of the transaction processing server 200 that has received the transaction data input completion notification refers to the common data definition 224 (S120). Then, the transaction processing unit 230 extracts common data from the received transaction data based on the common data definition 224 (S122). Here, when new common data is extracted, the transaction processing unit 230 stores the extracted common data in the storage unit 220 as the common data 228 (S124). Further, when the common data that is not used in the subsequent transaction is determined, the transaction processing unit 230 deletes the common data that is not used from the storage unit 220.

  Furthermore, the transaction processing unit 230 refers to the common data 228 that has been updated in step S124 (S128). Then, the transaction processing unit 230 sets the value of the common data already input on the previous transaction screen in the next transaction screen (transaction screen S2) generated according to the business flow definition 222 (step S130). And transaction processing part 230 displays on terminal device 100 transaction screen S2 which set up a value of common data (S132). Further, the transaction processing unit 230 updates the screen identifier of the execution status data 226 with the screen identifier of the transaction screen S2 (S134).

  Next, in the terminal device 100 on which the transaction screen S2 is displayed, transaction data is input by the user (S136). Then, the control unit 140 of the terminal device 100 stores the input transaction data in the storage unit 130 of the terminal device 100 as the ongoing transaction data 132 (S138). This process is repeated until the transaction data is input to all necessary input items on the transaction screen by the user. In this scenario, before the transaction data input by the user is completed, for example, a system failure Causes the transaction screen S2 to stop abnormally.

  At the time of the abnormal stop described above, the storage unit 130 of the terminal device 100 stores the transaction data input by the user on the transaction screen S2 as the ongoing transaction data 132 in association with the screen identifier of the transaction screen S2. ing. Further, the storage unit 220 of the transaction processing server 200 stores execution status data 226 including the screen identifier of the transaction screen S2 and common data 228 including common data included in the transaction data input on the transaction screen S1. ing.

  In FIG. 12, when the system recovers after an abnormal stop, the control unit 140 of the terminal device 100 refers to the transaction data 132 being executed and recognizes that the transaction screen S2 is displayed at the time of the abnormal stop (S202). ). Then, the control unit 140 acquires the business flow number (= F1), the screen identifier (= S2), and the transaction data that has been input from the ongoing transaction data 132. And the control part 140 transmits the restart request | requirement of a business flow to the transaction processing server 200 via the communication part 120 (S204). The request for resuming the business flow includes, for example, the business flow number of the business flow to be resumed, the screen identifier of the transaction screen displayed at the time of the abnormal stop, and the transaction data that has been input.

  Next, the transaction processing unit 230 of the transaction processing server 200 that has received the request for resuming the business flow collates the received business flow number and screen identifier with the business flow number and screen identifier stored in the execution status data 226. (S206). Then, when the business flow number and the screen identifier match, the transaction processing unit 230 determines to resume the business flow from the transaction screen represented by the screen identifier (S208).

  When the transaction processing unit 230 determines to resume the business flow, first, the transaction processing unit 230 refers to the common data definition 224 (S212). Further, the transaction processing unit 230 refers to the common data 228 (S214). If the common data 228 includes common data that can be used in the transaction screen S2 displayed at the time of the abnormal stop, the value of the common data is set in the newly generated transaction screen S2 (S216). . Further, the transaction processing unit 230 sets the input transaction data included in the business flow restart request received in step S204 in the transaction screen S2 (S218). And transaction processing part 230 displays transaction screen S2 on terminal unit 100 (S220).

  Next, in the terminal device 100 on which the transaction screen S2 is displayed, transaction data is input by the user. In this case, since the transaction data S2 has already been set in the transaction screen S2, the burden of re-input of the transaction data by the user is reduced. Moreover, the user can restart the input of transaction data without referring again to transaction data on another transaction screen that has been input in the past. The flow of processing from the input of transaction data by the user to the transmission of transaction data is the same as that from step S110 to step S116 shown in FIG.

  Thereafter, after the transaction data is input on each transaction screen and the transaction data input on the last transaction screen S5 included in the business flow F1 is completed, the input of the last transaction data is completed from the terminal device 100 to the transaction processing server 200. A notification is transmitted (S224). Further, when the transmission of the input completion notification is completed, the control unit 140 of the terminal device 100 deletes the ongoing transaction data 132 (S226).

  Next, the transaction processing unit 230 of the transaction processing server 200 that has received the transaction data input completion notification deletes the common data 228 (S228). Further, the transaction processing unit 230 deletes the execution status data 226 (S230). Then, the transaction processing unit 230 notifies the terminal device 100 of the end of the office flow F1 (S232). Thereby, the transaction processing by the terminal device 100 and the transaction processing server 200 ends.

  Up to this point, the first embodiment of the present invention has been described with reference to FIGS. According to the present embodiment, even if an abnormal stop occurs due to a hardware failure, an increase in processing load, an exception process in software, or an erroneous operation by a user in the transaction processing system 1, the transaction processing system 1 can be restarted after the system is restored. On the displayed transaction screen, the transaction data that has been input before the abnormal stop and the common data that has been input in the already completed transaction are automatically set. Thereby, the burden on the user due to re-input of data after an abnormal stop is reduced, and input mistakes due to re-input of data are prevented.

  Further, the transaction data for setting the transaction screen to be redisplayed is stored only while each transaction screen is used in the terminal device 100. Similarly, the common data to be set in the redisplayed transaction screen is stored only while the subsequent unprocessed transaction screen in which each common data is used remains in the business flow in the transaction processing server 200. Is done. Thereby, the storage capacity of data required for resuming the business flow is reduced as a whole in the transaction processing system 1. As a result, system resources can be used efficiently, and the load on the system can be reduced.

<2. Description of Second Embodiment>
In the first embodiment described above, after the system recovery after the abnormal stop of the transaction processing system 1, the user does not refer to the transaction data on other transaction screens that have been input in the past again, Input can be resumed. However, the user may wish to refer to other transaction screens that have been entered in the past, for example, when the transaction data to be newly entered after system recovery is determined depending on the entered transaction data. It is done. Therefore, as a second embodiment of the present invention, an alternative configuration of a transaction processing server for enabling a user to easily refer to other transaction screens that have been input in the past will be described.

[2-1. Example of transaction processing server configuration]
FIG. 13 is a block diagram showing an example of the configuration of the transaction processing server 400 according to the second embodiment of the present invention. Referring to FIG. 13, the transaction processing server 400 includes a communication unit 210, a storage unit 420, and a transaction processing unit 430.

    The storage unit 420 functions as a storage unit in the transaction processing server 400 using a storage medium such as a hard disk or a semiconductor memory. More specifically, in the present embodiment, the storage unit 420 stores the business flow definition 222, the common data definition 224, the execution status data 226, the common data 228, and the transaction history data 421 as shown in FIG. To do.

  The transaction processing unit 430 has the function of the transaction processing unit 230 according to the first embodiment described above, and the transaction history having the transaction data input to each transaction screen as individual histories as the business flow progresses Data 421 is stored in the storage unit 420.

  FIG. 14 is an explanatory diagram for explaining an example of the transaction history data 421. Referring to FIG. 14, each history of the transaction history data 421 is generated by the transaction processing unit 430 each time the transaction processing server 400 receives transaction data from the terminal device 100 that has finished inputting transaction data by the user. For example, when transaction data is received from the terminal device 100 that has finished inputting transaction data by the user on the transaction screen S1, the transaction processing unit 430 generates transaction history data H1. The transaction history data H1 includes, for example, the business flow number, the screen identifier of each transaction screen, and the individual transaction data that were input, which were included in the transaction data input completion notification described in step S114 of FIG. It is. Similarly, when transaction data is received from the terminal device 100 that has finished inputting transaction data by the user on the transaction screen S2, the transaction processing unit 430 generates transaction history data H2. In this way, the storage unit 420 stores the transaction history data 421 in which the history of transaction data transmitted from the terminal device 100 is accumulated.

  The transaction processing unit 430 further sets the transaction data included in the transaction history data 421 on the transaction screen on which the input of the transaction data has been completed after the abnormal stop that occurred during the display of any of the transaction screens, and the transaction screen Is displayed again on the terminal device 100. For example, it is assumed that an abnormal stop occurs during the input of transaction data on the transaction screen S3 among the transaction screens S1 to S5. In that case, first, the transaction processing unit 430 sets the transaction data on the transaction screen S1 using the transaction history data 421 illustrated in FIG. Moreover, when the notification that the user has completed the confirmation of the transaction screen S1 is received from the terminal device 100, the transaction processing unit 430 similarly sets transaction data on the transaction screen S2 and causes the terminal device 100 to redisplay the transaction data. Then, when the notification that the user has completed the confirmation of the transaction screen S2 is received from the terminal device 100, the transaction processing unit 430 is inputting the transaction screen S3 using the method described in the first embodiment. The transaction data and the common data are set and displayed on the terminal device 100 again.

[2-2. Process flow]
FIG. 15 is a sequence diagram illustrating an example of a flow of transaction processing according to the second embodiment. FIG. 15 shows, as an example, the flow of transaction processing after system restoration after an abnormal stop occurs during the input of transaction data on transaction screen S2 in office flow F1 having transaction screens S1 to S5. .

  In FIG. 15, when the system recovers after an abnormal stop, the control unit 140 of the terminal device 100 refers to the transaction data 132 being executed and recognizes that the transaction screen S2 is displayed at the time of the abnormal stop (S402). ). Then, the control unit 140 acquires the business flow number (= F1), the screen identifier (= S2), and the transaction data that has been input from the ongoing transaction data 132. And the control part 140 transmits the restart request | requirement of a business flow to the transaction processing server 400 via the communication part 120 (S404). The request for resuming the business flow includes, for example, the business flow number of the business flow to be resumed, the screen identifier of the transaction screen displayed at the time of the abnormal stop, and the transaction data that has been input.

  Next, the transaction processing unit 430 of the transaction processing server 400 that has received the request for resuming the business flow collates the received business flow number and screen identifier with the business flow number and screen identifier stored in the execution status data 226. (S406). Then, when the business flow number and the screen identifier match, the transaction processing unit 430 determines to resume the business flow (S408).

  When the transaction processing unit 430 determines to resume the business flow, first, the transaction processing unit 430 refers to the transaction history data 421 (S412). And transaction processing part 430 generates transaction screen S1 which is the first transaction screen of an office flow, and transaction data contained in the history corresponding to transaction screen S1 among the history contained in transaction history data 421 is shown. The transaction screen S1 is set (S414). And transaction processing part 430 displays transaction screen S1 on terminal unit 100 (S416).

  Next, in the terminal device 100, the redisplayed transaction screen S1 is confirmed by the user (S416). When it is detected that the user has completed the confirmation by clicking a predetermined button or the like, a confirmation completion notification is transmitted from the control unit 140 of the terminal device 100 to the transaction processing server 400 (S420). The confirmation completion notification includes, for example, the screen identifier of the confirmed transaction screen.

  Next, the transaction processing unit 430 of the transaction processing server 400 that has received the confirmation completion notification first refers to the common data definition 224 (S422). Further, the transaction processing unit 430 refers to the common data 228 (S424). If the common data 228 includes common data that can be used on the transaction screen S2 displayed at the time of the abnormal stop, the value of the common data is set in the newly generated transaction screen S2 (step S426). ). Furthermore, the transaction processing unit 430 sets the input transaction data included in the business flow restart request received in step S404 in the transaction screen S2 (step S428). And transaction processing part 430 displays transaction screen S2 on terminal unit 100 (S430). The subsequent transaction processing flow is the same as that after step S220 shown in FIG. 12 in the first embodiment, and a description thereof will be omitted.

  Up to this point, the second embodiment of the present invention has been described with reference to FIGS. According to the present embodiment, even when an abnormal stop occurs in the system, the transaction screen of transactions completed before the abnormal stop is redisplayed based on the transaction history data after the system is restored. As a result, the user must use another means (such as a dedicated transaction inquiry screen) when, for example, determining transaction data to be newly input after system recovery depending on past transaction data. It is possible to easily refer to past transaction data.

  Note that each process of the terminal device 100 and the transaction processing server 200 according to the first embodiment described in this specification and the transaction processing server 400 according to the second embodiment typically uses software. Executed. When each process is executed using software, a program constituting the software is executed using a computer incorporated in dedicated hardware, for example, the general-purpose computer 900 shown in FIG.

  Referring to FIG. 16, in general-purpose computer 900, CPU 902 controls the overall operation of general-purpose computer 900. A ROM (Read Only Memory) 904 stores a program describing a part or all of a series of processes, control data, and the like. A RAM (Random Access Memory) 906 temporarily stores programs, data, and the like used by the CPU 902 when processing is executed.

  The CPU 902, ROM 904, and RAM 906 are connected to each other via a bus 910. An input / output interface 912 is further connected to the bus 910. The input / output interface 912 connects the CPU 902, the ROM 904, and the RAM 906 to the input device 920, the display device 922, the storage medium 924, and the communication interface 926.

  The input device 920 receives an instruction and data input from a user via input means such as buttons, switches, levers, a mouse, and a keyboard. The display device 922 displays a screen to the user using, for example, a CRT (Cathode Ray Tube), a liquid crystal display, an OLED (Organic Light Emitting Diode), or the like.

  The storage medium 924 may be, for example, a hard disk, an optical disk, or a semiconductor memory such as a flash memory, and is used for storing programs and data. The communication interface 926 mediates communication processing via the network 3.

  When each process according to the first and second embodiments is executed by software, for example, a program stored in the ROM 904 or the storage medium 924 is read into the RAM 906 at the time of execution and executed by the CPU 902.

  The preferred embodiments of the present invention have been described in detail above with reference to the accompanying drawings, but the present invention is not limited to such examples. It is obvious that a person having ordinary knowledge in the technical field to which the present invention pertains can come up with various changes or modifications within the scope of the technical idea described in the claims. These are naturally understood to belong to the technical scope of the present invention.

DESCRIPTION OF SYMBOLS 1 Transaction processing system 100 Terminal device 110 Display part 112 Transaction screen 114 Transaction data input column 116 Send button 120 Communication part (terminal communication part)
130 storage unit 132 executing transaction data 200, 400 transaction processing server (information processing apparatus)
210 Communication unit 220, 420 Storage unit 222 Business flow definition 224 Common data definition 226 Execution status data 228 Common data 421 Transaction history data 230, 430 Transaction processing unit

Claims (7)

A display unit for sequentially displaying a transaction screen on a display device for a series of transactions included in one business flow;
A control unit that stores the transaction data input on the transaction screen in the storage unit before completing the input of the transaction data on each transaction screen;
With
The display unit is an abnormally stopped transaction screen after an abnormal stop that occurred during display of any transaction screen, and the transaction data stored by the storage unit before completion of input on the transaction screen and Redisplay the transaction screen in which common data extracted as commonly used in a plurality of transactions among transaction data input completed on other transaction screens before the abnormal stop is set,
Transaction processing system. The transaction processing system includes a terminal device capable of communicating with an information processing device via a communication network,
The transaction screen is generated by the information processing apparatus,
The terminal device includes the display unit,
The transaction processing system according to claim 1.   The terminal device further includes a communication unit that, when input of transaction data on each transaction screen is completed, transmits the transaction data input on the transaction screen to the information processing device. The transaction processing system described.   The transaction processing system according to claim 3, wherein the common data is extracted by the information processing apparatus. The terminal device further includes the control unit,
The control unit deletes the transaction data stored in the storage unit when transmission of transaction data to the information processing apparatus by the communication unit is completed.
The transaction processing system according to claim 4. A terminal device capable of communicating with an information processing device via a communication network:
A display unit for sequentially displaying a transaction screen generated by the information processing device on a display device for a series of transactions included in one business flow;
A communication unit that, when input of transaction data on each transaction screen is completed, transmits the transaction data input on the transaction screen to the information processing apparatus;
A control unit that stores the transaction data input on the transaction screen in the storage unit before completing the input of the transaction data on each transaction screen;
With
The display unit is a transaction screen that is abnormally stopped after an abnormal stop that occurred during display of any transaction screen, and is transmitted to the information processing device by the transaction data stored in the storage unit and the communication unit Redisplaying the transaction screen in which the common data extracted by the information processing apparatus is set as one commonly used in a plurality of transactions among the transaction data
Terminal device. The terminal device according to claim 6, wherein the control unit deletes the transaction data stored in the storage unit when transmission of transaction data to the information processing apparatus by the communication unit is completed.

Images