JP2018136606A - Business shop work system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve business processing performance and availability in a business shop work system.SOLUTION: A business shop work system according to an embodiment of the present invention has a plurality of terminals provided in a business shop, and a business shop server installed at a place different from the business shop. An applicant terminal reads a list on a transaction case by a scanner, stores image data of the list in a storage device, and stores a copy of the image data of the list in a copied terminal, when receiving an input of information of the transaction case. Then, the applicant terminal transmits an approval request of the transaction case including a file name of the image data of the list to the business shop server. On the other hand, a responsible person terminal acquires information on the transaction case from the business shop server, at the time of approval of the transaction case, acquires the image data of the list from the applicant terminal, displays these on a display device of the responsible person terminal, and receives an approval instruction from a responsible person.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a business system of a branch office such as a financial institution.

  In recent years, business processing in a company or the like has been electronically performed by a computer on a network or the like. For example, Patent Document 1 discloses an example of a system used in a sales office of a financial institution and a flow of business processing using this system. In this system, for example, when a person in charge at a sales office conducts a transaction that requires approval of a manager such as a branch manager, the person in charge from the person in charge terminal, a transaction type indicating a transaction type (withdrawal transaction, etc.) Transaction acceptance information composed of customer account information and withdrawal amount is transmitted to the server. On the other hand, in the officer's terminal used by the officer, the transaction acceptance information is acquired from the server and the information is displayed on the display means. The officer in charge confirms the displayed transaction acceptance information.

  In this transaction, the person in charge receives a slip such as a withdrawal request form from the customer, causes the scanner to read the image data of the slip, and transmits the image data of the slip together with the transaction acceptance information to the server. The board terminal also acquires image data of the slip together with the transaction reception information, and displays the image data of the slip on the display unit in addition to the transaction reception information.

JP 2007-272377 A

  Depending on the system, the server may be installed at a location different from the store where the terminal is located. For example, a server may be installed in a data center or the like that is away from the sales office. When the distance between the server and the terminal is long, the time required for transmission of transaction acceptance information and image data increases, and system performance is likely to deteriorate. Therefore, it is required to reduce the amount of information exchanged between the server and the terminal.

  A sales office business system according to an embodiment of the present invention includes a plurality of terminals provided in a sales office, and a sales office server installed at a location different from the sales office. The plurality of terminals are communicably connected to each other via a local area network (LAN) and are connected to a branch office server via a wide area network (WAN). Each terminal includes a scanner that reads a form and a storage device that stores an image file of the form read by the scanner.

  The applicant terminal that accepts the transaction case approval request from the applicant, when receiving the input of the transaction case information, reads the form related to the transaction case with the scanner, stores the image data of the form in the storage device, A copy of the image data of the form is stored in a copy terminal which is one of a plurality of terminals. Thereafter, a transaction case approval request including the file name of the image data of the form relating to the transaction case is transmitted to the sales office server. On the other hand, when the responsible person's terminal used by the responsible person approves the transaction item, it receives the transaction item information from the sales office server, acquires the image data of the form from the terminal that sent the approval request, Display and accept the approval instruction from the person in charge.

  According to the disclosed store business system, the performance of various application processes can be improved.

It is a block diagram of the shop business system which concerns on one Embodiment of this invention. It is a figure which shows the hardware structural example of a terminal. It is a figure which shows the hardware structural example of a branch office server. It is an example of a transaction matter table. It is an example of an approval matter status table. It is an example of an approval information table. It is an example of a terminal information table. It is an example of a terminal operation status table. It is a sequence diagram (1) of approval processing. It is a sequence diagram (2) of approval processing. It is an example of an error message display screen. It is another example of an error message display screen. It is an example of a display screen of a person in charge terminal. It is an example of a display screen of a person in charge terminal. It is a flowchart of an image file deletion process. It is an example of an image list.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

(1) System Configuration FIG. 1 is a configuration diagram of a branch office business system according to the first embodiment. The sales office business system includes a plurality of terminals 4 and a sales office server 2 (hereinafter also abbreviated as “server 2”). A plurality of terminals 4 are provided in each branch office 3 of the financial institution, and the branch office server 2 is installed in the computer center 1 in a different location from the branch office 3. Each terminal 4 in the store 3 is connected to an in-store local area network 5 (also referred to as “in-store LAN 5”), and the terminals 4 in the store 3 can communicate with each other. The in-store LAN 5 is connected to a WAN 6 that connects the sales office 3 and the computer center 1, and each terminal 4 can communicate with the sales office server 2 in the computer center 1 via the wide area network (WAN) 6. is there.

  The terminal 4 is installed at the counter of each sales office 3 of the financial institution and used by a bank employee (called “applicant” in this embodiment) at the financial institution's counter to process a transaction requested by a customer. To do. Some of the terminals 4 are placed in the seats of officers (also called “responsible persons” in this embodiment) who perform the approval process of the case. In the present embodiment, the terminal 4 used by the responsible person is referred to as “responsible person terminal 4b”, and the terminal used by the applicant of the financial institution is referred to as “applicant terminal 4a”. In FIG. 1, there is also a “duplicate terminal 4c”, which will be described later. Further, there may be devices other than the terminal 4 in the sales office 3, but in the present embodiment, description of these devices is omitted. These devices may also be connected to the in-store LAN 5.

  The sales office server 2 manages information on transaction items performed at each sales office 3, and controls the approval process performed between the applicant and the person in charge. The computer center 1 may include a device other than the sales office server 2 for business processing of a financial institution. However, in the present embodiment, description of devices other than the sales office server 2 is omitted.

  The archive system 7 is a system for storing information on transaction items for a predetermined period (for example, a period determined by law). For example, the archive system 7 includes a server computer and a large-capacity storage device. Information on the transaction items processed by the terminal 4 and the sales office server 2 is periodically sent to the archive system 7 and stored in the archive system 7 for a predetermined period. The archive system 7 may be installed anywhere, but is generally installed at a location different from the sales office 3 and the computer center 1. The archive system 7 is connected to the WAN 6, and transaction item information is sent to the archive system 7 via the WAN 6.

  FIG. 2 shows the hardware configuration of the terminal 4. The terminal 4 communicates with a CPU (Central Processing Unit) 41, an auxiliary storage device 44 that is a nonvolatile storage device such as a hard disk, and an in-store LAN 5 in addition to a memory 42 formed of a volatile storage medium such as a DRAM. Peripheral devices such as a communication interface (communication I / F) 45, a display device 46 such as a liquid crystal display, an input device 47 such as a keyboard and a mouse, a scanner 48 for reading paper documents such as a form, and a printer 49 Prepare. These peripheral devices are connected to the CPU 41 via an I / O interface (I / O I / F) 43.

  In the present embodiment, an example in which various functions of the terminal 4 (for example, a function of receiving an input of transaction item information from the applicant and issuing an approval request) is implemented by software (program) will be described. In other words, the CPU 41 of the terminal 4 executes the programs stored in the memory 42 to execute various processes related to the approval request described below while using various peripheral devices such as the scanner 48 of the terminal 4. However, the various processes described below do not necessarily have to be implemented by software. Part or all of the processing described below may be implemented by hardware such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit).

  The memory 42 is a storage device for holding a program executed by the CPU 41 and information used when the program is executed, and is configured by a volatile storage medium such as a DRAM. The auxiliary storage device 44 is a nonvolatile storage device such as a hard disk drive (HDD). The auxiliary storage device 44 is used not only to store a program executed by the CPU 41 but also to store image data of a form read by the scanner 48 (or may be referred to as “image file”).

  The communication I / F 45 is a device for performing communication between the terminal 4 and another device (for example, the sales office server 2). The display device 46 is a device for displaying information to a terminal operator (applicant or responsible person of a financial institution) such as a liquid crystal display. On the other hand, the input device 47 is a device used by a terminal operator for information input, and is a device such as a keyboard or a mouse. Further, instead of providing the display device 46 and the input device 47, a device capable of both displaying and inputting information, such as a touch screen, may be provided.

  The scanner 48 is an optical reading device for reading a paper document such as a withdrawal request form. In this embodiment, the terminal 4 (the CPU 41) stores the paper document read by the scanner 48 in the auxiliary storage device 44 as an image file. It also has an OCR (Optical Character Reader) function for recognizing information such as the amount of money described in a paper document (as described above, this function is realized by the CPU 41 executing a program).

  Note that the terminal 4 may include peripheral devices other than those shown in FIG. Further, all the terminals 4 may not have the same hardware configuration. For example, the number or types of peripheral devices included in the person-in-charge terminal 4b and the applicant terminal 4a may be different. Further, installed programs (programs executed by the CPU 41) may be different between the person-in-charge terminal 4b and the other terminals 4. For example, the responsible person terminal 4b is a terminal used by the responsible person (person who performs the approval process), and the other terminals 4 are terminals used by the applicant in principle. Therefore, the responsible person terminal 4b has a program for the approval process. It is preferable that an approval request program is installed in the other terminal 4. Of course, conversely, the same program may be installed in all the terminals 4. That is, both the approval processing program and the approval request program may be installed in all the terminals 4.

  Also, in the following explanation, there will be explained an example in which there are a plurality of applicant terminals 4a in the sales office 3 and only one person in charge terminal 4b in the sales office 3, but the number of applicant terminals 4a and the persons in charge The number of terminals 4b is not necessarily limited to this number.

  FIG. 3 shows the hardware configuration of the server 2. The server 2 is a general-purpose computer such as a personal computer (PC) or a PC server. In addition to the CPU 21 and the memory 22, the server 2 performs communication via the auxiliary storage device 24, which is a nonvolatile storage device such as a hard disk, and the WAN 6. Peripheral devices such as a communication interface (communication I / F) 25 for performing, a display device 26 such as a liquid crystal display, and an input device 27 such as a keyboard and a mouse are provided. These peripheral devices are connected to the CPU 41 via an I / O interface (I / O I / F) 23.

  In this embodiment, the function of the server 2 is implemented by software (program). That is, when the CPU 21 of the server 2 executes the program stored in the memory 22, a request such as an approval request received from the terminal 4 is processed by the server 2. However, the various processes described below do not necessarily have to be implemented by software. Part or all of the processing described below may be implemented by hardware such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit).

(2) Overview of Approval Processing In the branch office business system according to the present embodiment, the contents of the process performed by the applicant of the financial institution using the terminal 4 are once sent to the branch office server 2. For example, when an applicant of a financial institution inputs the contents of a transaction item requested by a customer to the terminal 4 (applicant terminal 4a) and makes an approval request, the contents of the transaction item are sent to the sales office server 2. And stored in the store server 2. The transaction item information stored in the sales office server 2 includes, for example, a transaction state (whether approval is completed or the like).

  Subsequently, the branch office server 2 notifies the terminal (responsible person terminal 4b) of the person in charge of the transaction item (the officer who performs the approval) that there is a transaction item (approval item) to be approved. The person in charge uses the person-in-charge terminal 4b to carry out transaction transaction approval processing. When the approval process is performed, the person-in-charge terminal 4b notifies the sales office server 2 that the transaction item has been approved. Upon receiving the notification, the branch office server 2 changes the state of the transaction item managed in the branch office server 2 (for example, changes to a state where the approval is completed).

  In addition, when a person in charge approves a transaction case, for example, it confirms the contents of a paper document such as a deposit / withdrawal slip written by a customer (hereinafter referred to as “form”) and approves it. There are also projects that should be done. When such a case is processed in the sales office business system according to the present embodiment, the applicant reads the form using the scanner 48 of the applicant terminal 4a and creates the image data of the form. One form is generated as one file. In this embodiment, the generated file is referred to as an “image file”. The image file is stored in the auxiliary storage device 44 of the applicant terminal 4a.

  When the applicant transmits a transaction case approval request using the applicant terminal 4 a, the file name of the image file is also transmitted to the sales office server 2. However, the entity of the image file is not transmitted to the sales office server 2. In the sales office business system according to this embodiment, the image file itself is not transmitted / received between the sales office 3 and the computer center 1, thereby suppressing an increase in traffic of the WAN 6.

  When it is notified from the sales office server 2 that there is an approval case to the responsible person terminal 4b, the responsible person terminal 4b acquires information on the approval target case from the sales office server 2. The information acquired here includes the file name of the form image file attached to the transaction item. The person-in-charge terminal 4b acquires the image file of the form accompanying the transaction item to be approved from the applicant terminal 4a via the in-store LAN 5, and displays the contents of the image file on the display device 46 of the person-in-charge terminal 4b. To do. As a result, the person in charge can confirm the contents of the form on the screen of the person in charge terminal 4b, and there is no need to exchange paper documents (forms) with the applicant. Further, since the image file is exchanged only in the sales office 3 and does not pass through the sales office server 2, the load on the system can be reduced.

  However, when the responsible person terminal 4b acquires the image file of the form from the applicant terminal 4a, the image file is acquired due to a failure of the applicant terminal 4a (terminal 4 storing the image file). There are cases where it is not possible. The applicant terminal 4a stores a copy of the image file in another terminal 4 before making an approval request so that the approval process can be continued even in such a case. In the present embodiment, the terminal 4 in which a copy of the image file is stored is referred to as a “replication terminal 4c”. If the person-in-charge terminal 4b cannot acquire the image file of the form from the applicant terminal 4a, the person-in-charge terminal 4b acquires a copy of the image file from the copy terminal 4c.

(3) Management Information Next, the management information that the sales office server 2 has will be described. FIG. 4 shows an example of a transaction item table 150 for storing information on transaction items accepted from the applicant terminal 4a. Each row (record) in the transaction item table 150 represents information corresponding to one transaction item.

  The date 151 stores information on the date of accepting the transaction case approval request from the applicant terminal 4a, the station number 152 is the identification number of the branch office 3 where the transaction case approval request is issued, and the station name 154 is This is the name of the sales office 3.

  The process serial number 153 is a unique number assigned to each transaction item, and is assigned by the store server 2 when the store server 2 receives a request for approval of the transaction item. The transaction content 155 stores the content of the transaction item received from the applicant terminal 4a. For example, in the case of a withdrawal process request, information indicating that the type of transaction is a withdrawal transaction, and the details of the withdrawal transaction (a withdrawal amount, the number of an account for withdrawal, etc.) are stored. The image data file name 158 is the file name of the form image file for the transaction item.

  The application user ID 156 is identification information (ID) of an applicant who has requested transaction approval from the applicant terminal 4a.

  Next, the approval case status table 120 will be described with reference to FIG. The approval matter status table 120 is a table for storing information about the processing status of the transaction matter.

  In the date 121, the station number 122, and the processing sequence number 123, the same information as the date 151, the station number 152, and the processing sequence number 153 of the transaction case table 150 is stored. Of the records in the transaction item table 150 and the records in the approved item state table 120, the records having the same processing sequence number 153 (processing sequence number 123) are information on the same transaction item.

  The case status 126 indicates whether the transaction case is being processed or has been processed. When the case state 126 is 0, it indicates that the transaction case is being processed. Further, when the case status 126 is 1, it indicates that the processing is completed, and the date and time when the transaction case processing is completed is stored in the case completion date and time 130. The approval state 127 is information indicating whether or not the transaction case has been approved by the person in charge. If the approval state 127 is 1, it indicates that the transaction case has been approved.

  FIG. 6 shows an example of the approval information table 100. The approval information table 100 is a table for managing the location of the image file attached to the transaction item. The date 101, the station number 102, and the processing serial number 103 are the same information as the date 151, the station number 152, and the processing serial number 153 of the transaction case table 150 (or the date 121, the station number 122, and the processing serial number 123 of the approved case status table 120). Is stored. The applicant terminal IP address 106 is the IP address of the applicant terminal 4 a that has requested the transaction case approval, and represents that the image file is stored in the terminal 4 specified by the applicant terminal IP address 106. ing. The image data file name 107 is the file name of the image file, and stores the same contents as the image data file name 158 of the transaction item table 150. The responsible person approval execution user ID 108 is a user ID of a person who approves the transaction case.

  FIG. 7 shows a configuration example of the terminal information table 300. The terminal information table 300 is a table storing information about the duplicating terminal 4c, and is used to specify the duplicating terminal 4c when the applicant terminal 4a duplicates the image file to another terminal (duplicating terminal 4c). As shown in FIG. 7, the terminal information table 300 includes columns of a station number 301, a terminal number 302, a terminal IP address 303, and a duplicate IP address 304.

  Among these columns, the terminal IP address 303 represents the IP address of the applicant terminal 4a, and the terminal machine number 302 is an identification number assigned to the applicant terminal 4a. The station number 301 is the store number of the store where the applicant terminal 4a is located. The duplicate IP address 304 is the IP address of the duplicate terminal 4c.

  In this embodiment, as shown in the example of FIG. 7, one copy terminal 4c (its IP address) is associated with one applicant terminal 4a (its IP address). Note that the copy terminal 4c does not only serve to store a copy of the image file, but the terminal 4 used as the applicant terminal 4a or the responsible person terminal 4b is also used as the copy terminal 4c.

  In the example of FIG. 7, when the record on the first line is referred to, the terminal IP address 303 (that is, the IP address of the applicant terminal 4a) is 100.100.100.1. A duplicate IP address 304 is also registered. That is, it means that the terminal 4 with the IP address 100.100.100.1 is used as the replication terminal 4c of another terminal 4 (the terminal 4 with the IP address 100.100.100.3). In the present embodiment, the information shown in FIG. 7 is stored in advance in the terminal information table 300 (that is, the correspondence between the applicant terminal 4a and the copy terminal 4c is determined in advance). Describes an example that is fixed.

(4) Flow of Approval Process Next, the flow of the approval process performed in the sales office business system according to the present embodiment will be described with reference to FIG. 9 and subsequent drawings. In FIG. 9 and subsequent drawings, the letter “S” added before the reference number means “step”.

  Step 1001: Here, the applicant terminal 4a accepts information input about a transaction item such as a withdrawal transaction from the applicant. The applicant terminal 4a displays a screen for inputting information on a transaction item on the display device 46, and allows the applicant to input information. Further, the applicant terminal 4 a displays a message or the like on the display device 46 instructing the reading of the form regarding the transaction item, thereby causing the applicant to set the form in the reading unit of the scanner 48. When the form is set on the scanner 48, the applicant terminal 4 a uses the scanner 48 to acquire image data of the form. After the image data is acquired, the applicant terminal 4 a stores the image data (image file) in the auxiliary storage device 44. At this time, the file name of the image file may be determined by the applicant terminal 4a according to its own rules.

  Step 1002: The applicant terminal 4a requests the sales office server 2 to obtain the IP address of the duplicate terminal 4c of the applicant terminal 4a. In response to this request, the applicant terminal 4a passes the IP address of the duplicate terminal 4c of the applicant terminal 4a to the sales office server 2 (this process will be described in step 1003 below).

  Step 1003: The sales office server 2 refers to the terminal information table 300 and searches for a line in which the terminal IP address 303 matches the IP address of the applicant terminal 4a (the IP address passed from the applicant terminal 4a). The duplicate IP address 304 is returned to the applicant terminal 4a. Thereby, the applicant terminal 4a can specify its own copy terminal 4c.

  Step 1004: The applicant terminal 4a transmits the image file created in Step 1001 to the duplication terminal 4c. At this time, the file name of the image file is also passed to the replication terminal 4c.

  Step 1005: The duplication terminal 4c that has received the image file from the applicant terminal 4a stores the image file in the auxiliary storage device 44 of the duplication terminal 4c. The duplicating terminal 4c does not change the file name of the image file passed from the applicant terminal 4a. Therefore, the file names of the image file stored in the applicant terminal 4a and the image file stored in the copy terminal 4c are the same.

  Step 1006: The applicant terminal 4a transmits an approval request to the sales office server 2. The approval request includes the contents of the transaction item and the file name of the form image file stored in the auxiliary storage device 44 in step 1001. Specifically, it is stored in the station number 152, the station name 154, the transaction content 155, and the image data file name 158 (or the image data file name 107 of the approval information table 100) of the transaction case table 150 of the sales office server 2. It should contain information that should be included. Further, here, the user ID of the applicant and the IP address of the applicant terminal 4a are also transmitted to the sales office server 2, and in the sales office server 2, the user ID of the applicant is the application user ID (156) of the transaction case table 150. The IP address of the applicant terminal 4 a is stored in the applicant terminal IP address 106 of the approval information table 100.

  Step 1007: The store server 2 registers the information received together with the approval request from the applicant terminal 4a in the management information held by itself. Specifically, here, the store server 2 creates a record in each of the transaction item table 150, the approval item state table 120, and the approval information table 100. The current date is stored in the date field of the created record, and the new processing sequence number is stored in the processing sequence number field. The sales office server 2 stores the information received together with the approval request in the record created here. Note that 0 is stored in the case state 126 and the approval state 127 of the approval case state table 120.

  Thereafter, the branch office server 2 notifies the person in charge terminal 4b that the applicant has requested approval. This notification includes the transaction serial number of the transaction item. Further, in the present embodiment, it is assumed that there is only one responsible person terminal 4b in each branch 3 and the branch server 2 knows the IP address of the responsible terminal 4b. Therefore, the sales office server 2 notifies the manager terminal 4b in the sales office 3 where the applicant terminal 4a that has transmitted the approval request is present that the approval request has been made.

  Step 1008: The person-in-charge terminal 4b acquires information on the transaction item requested for approval from the sales office server 2 and displays it on the display device 46. The person-in-charge terminal 4b requests the sales office server 2 to transmit information on the transaction case corresponding to the processing serial number notified from the sales office server 2 in step 1007. get. In the present embodiment, the person-in-charge terminal 4b obtains the records of the transaction item table 150 and the approval information table 100 (the process serial number is the same as the process serial number passed from the sales office server 2).

  Step 1009: The person-in-charge terminal 4b refers to the applicant terminal IP address 106 and the image data file name 107 in the information acquired in Step 1008, and the file name and image of the form image file for the transaction case. It recognizes the IP address of the terminal 4 storing the file (this is the terminal 4 used when the applicant issues an approval request, that is, the applicant terminal 4a). The person-in-charge terminal 4b requests the applicant terminal 4a to acquire an image file. This request includes the file name of the image file (image data file name 107). The applicant terminal 4a requested to acquire the image file returns the image file having the file name specified in the request to the responsible person terminal 4b.

  Step 1010: When acquisition of the image file is successful (Step 1010: Success), the person-in-charge terminal 4b displays a screen (window) displaying the transaction item information and the form image as shown in FIG. The information is displayed on the screen, and then step 1020 is performed. Conversely, if acquisition of the image file has failed (step 1010: failure), step 1011 is executed next. When the acquisition of the image file has failed, a failure occurs in the hardware of the applicant terminal 4a, for example, the case where the applicant terminal 4a cannot be accessed from the branch office server 2 due to a failure of the communication I / F 45, or an auxiliary memory There may be a case where the image file cannot be read due to a failure of the device 44. Alternatively, there may be a case where the image file stored in the applicant terminal 4a cannot be accessed from the sales office server 2 due to a malfunction of the program executed by the CPU 41 of the applicant terminal 4a.

  Step 1011: The responsible person terminal 4b displays on the display device 46 that the acquisition of the image file has failed. An example of the display is shown in FIG. The responsible person terminal 4 b displays a dialog box as shown in FIG. 11 on the screen of the display device 46. In this dialog box, “Reacquire” and “Cancel” buttons are prepared, and when the person in charge presses the “Reacquire” button using the input device 47, the person in charge terminal 4b executes Step 1009 again, An attempt is made to acquire an image file from the applicant terminal 4a. On the other hand, when “Cancel” is pressed, the person-in-charge terminal 4b executes step 1012 next.

  Step 1012 and Step 1013: The responsible person terminal 4b requests the sales office server 2 to obtain the IP address of the duplicating terminal 4c of the applicant terminal 4a. This process is the same as in step 1002, and the responsible person terminal 4 b passes the IP address of the applicant terminal 4 a to the sales office server 2. In step 1013, the branch office server 2 specifies the IP address of the duplicating terminal 4c based on the IP address (of the applicant terminal 4a) received from the responsible person terminal 4b, and returns it to the responsible person terminal 4b.

  Step 1014: The responsible person terminal 4b requests the copy terminal 4c to acquire an image file. This process is the same as step 1009, and the copy terminal 4c that has received the image file acquisition request returns the image file having the file name specified in the request to the responsible person terminal 4b.

  Step 1015: When the acquisition of the image file is successful (Step 1015: Success), the person-in-charge terminal 4b displays a screen (window) displaying the transaction item information and the form image as shown in FIG. The information is displayed on the screen, and then step 1020 is performed. Conversely, if acquisition of the image file has failed (step 1015: failure), step 1016 is executed next.

  Step 1016: The responsible person terminal 4b outputs an error message on the screen of the display device 46. For example, as shown in FIG. 12, a message instructing to read the form image at the responsible person terminal 4b is output. When the person in charge presses the “OK” button in the dialog box of FIG. 12, step 1017 is executed next.

  Step 1017: The person-in-charge terminal 4b displays a screen such as that shown in FIG. 13 on the screen of the display device 46, and makes the person in charge select whether to continue the transaction item approval process or not to approve the transaction item. . If the person in charge has pressed the “unapproved” button, then step 1018 is performed. Conversely, when continuing the approval process, the person in charge presses the “capture” button. When the “take in” button is pressed, the responsible person terminal 4 b next performs step 1019.

  Step 1018: The responsible person terminal 4b notifies the sales office server 2 that the transaction number of the transaction item and the approval of the transaction item have been rejected. Upon receiving this notification, the branch office server 2 is notified of the processing sequence number 123 from the responsible person terminal 4b in the record of the approved case status table 120 in order to set the status of the corresponding processing sequence number to the processing completed status. For the record that matches the process serial number, the case status 126 is set to “1”. In addition, the record in which the process sequence number 103 matches the process sequence number notified from the person-in-charge terminal 4b is deleted from the approval information table 100.

  Step 1019: When continuing the approval process, the responsible person reads the form at the responsible person terminal 4b. When the person in charge sets the form in the reading unit of the scanner 48 of the person-in-charge terminal 4 b and presses the “load” button on the screen of FIG. 13, the person in charge terminal 4 b reads the form using the scanner 48. A form image file is created and stored in the auxiliary storage device 44. When the creation of the form image file is completed, the person-in-charge terminal 4b displays a screen (for example, FIG. 14) on which the transaction item information and the form image are displayed on the screen of the display device 46, as in Step 1010 and the like.

  Step 1020: As a result of the person in charge confirming the contents of the form, the transaction case may not be approved. For example, this is a case where the items described in the form do not match the contents of the transaction case entered by the applicant (for example, displayed in the “■ transaction information” area of the screen in FIG. 13). When the transaction case is not approved (step 1020: N), the person in charge presses the “non-approval” button on the screen of FIG. 14 and performs the process of rejecting the approval. As a result, the person-in-charge terminal 4b and the branch office server 2 perform Step 1017 and Step 1018 described above. In the case of approval (step 1020: Y), the responsible person presses an “approval” button on the screen of FIG. As a result, the person-in-charge terminal 4b executes step 1021 next.

  In step 1020, the person-in-charge terminal 4b displays on the display device 46 a screen on which the person in charge can approve (a screen on which an “approval” button is displayed as shown in FIG. 14). In step 1017, as shown in FIG. 13, the person-in-charge terminal 4b displays a screen in which the “approval” button is inactive and cannot be pressed. At the time of step 1017, since the person in charge has not yet confirmed the contents of the form (image data), it is not preferable that the person in charge performs the approval process at this point. Therefore, the responsible person terminal 4b prevents the responsible person from approving until the acquisition of the image file is successful and the image of the form can be displayed on the display device 46. As another embodiment, the responsible person terminal 4b may display a screen without an “approval” button in step 1017.

  Step 1021: The responsible person terminal 4b notifies the sales office server 2 that the transaction item has been approved. At this time, the responsible person terminal 4b notifies the transaction number of the transaction item, the file name of the form image file, the fact that the transaction item has been approved, and the IP address of the terminal 4 that acquired the form image file. However, other information may be notified to the sales office server 2.

  For example, when the form image file is acquired from the copy terminal 4c, the responsible person terminal 4b notifies the sales office server 2 of the IP address of the copy terminal 4c in step 1021. Conversely, when step 1019 is executed, that is, when the person in charge reads the form with his / her own terminal (responsible person terminal 4b), the IP address of the person in charge terminal 4b is notified to the sales office server 2. . Of course, when the form image file is acquired from the applicant terminal 4a, the responsible person terminal 4b notifies the sales office server 2 of the IP address of the applicant terminal 4a.

  Step 1022: Upon receiving notification from the responsible person's terminal 4b that the transaction case has been approved, the sales office server 2 sets the state of the corresponding process serial number to the approval completed state, so that the approval case state table 120 Among the records, the approval state 127 is set to “1” for the record whose processing sequence number 123 matches the processing sequence number notified from the person-in-charge terminal 4b. Also, among the records in the approval information table 100, the applicant terminal IP address 106 of the record whose processing sequence number 103 matches the processing sequence number notified from the responsible person terminal 4b and the contents of the image data file name 107 are respectively shown in the responsible person terminal. Rewrite the IP address and image file name sent from 4b. In addition, the image data file name 158 of the transaction item table 150 is also rewritten to the image file name sent from the responsible person terminal 4b.

  Since the processing performed thereafter is not related to the handling of the image file, only the outline will be described. The branch office server 2 notifies the terminal 4 that the transaction item has been approved (step 1023). Note that FIG. 10 shows an example in which the notification of approval completion is performed to the applicant terminal 4a. However, in this embodiment, the branch office server 2 determines the applicant terminal IP address of the approval information table 100 in step 1022. The terminal 4 having the IP address stored in 106 is notified that the approval is completed. Therefore, when the responsible terminal 4b cannot acquire the image file from the applicant terminal 4a and acquires the image file from the copy terminal 4c, the copy terminal 4c is notified that the approval is completed.

  Upon receiving the notification, the terminal 4 executes the remaining processing to complete the transaction case processing, and after the transaction case processing is completed, a notification that the processing of the case has been completed is sent from the terminal 4 to the sales office server 2. (Step 1025). The sales office server 2 that has received the notification updates the transaction state 126 of the transaction item to 1 to record that the processing for the transaction item has been completed (step 1026). In addition, between step 1024-step 1025, the communication (information exchange) may be performed once or more between the terminal 4 and the sales office server 2. For example, when the transaction item is a withdrawal process, communication for instructing the update of the amount of the account of the customer managed by the sales office server 2 is performed.

(5) Image File Deletion Processing In the sales office business system according to this embodiment, the image file stored in the terminal 4 is deleted after the business of the sales office is completed. This process is called an image file deletion process. Since the form image file (and transaction item information) needs to be stored for a predetermined period, it is not possible to delete all the form image files. However, as described above, in the branch office business system according to the present embodiment, one form image file is stored redundantly in a plurality of terminals 4. Therefore, in the image file deletion process, the image file stored redundantly in the sales office business system is deleted, and only one image file for one form is stored in the sales office business system. Thereby, it is possible to prevent a useless file from remaining in the auxiliary storage device 44.

  Further, the image file deletion process is performed, for example, at night after the end of the window service of the financial institution. For example, it may be performed as part of a batch process performed at night. The flow of the image file deletion process will be described with reference to FIG.

  Step 2001: The branch office server 2 creates an image list based on the approval information table 100. A method of creating an image list will be described with reference to FIG.

  The image list 600 is a list of image files as shown in FIG. More precisely, a list of file names of image files that may be left in the auxiliary storage device 44 of each terminal 4 is created for each terminal 4 by the process of step 2001, and this is called an image list in this embodiment. .

  First, the sales office server 2 creates a table in which only the columns of the applicant terminal IP address 106 and the image data file name 107 are extracted from the columns of the approval information table 100. Subsequently, the branch office server 2 divides each record included in the table created here using the applicant terminal IP address 106 as a key. An example is shown in FIG. Here, for simplification of explanation, an example in which the table includes only a record with the applicant terminal IP address 106 of 100.100.100.1 or 200.200.200.1 is included. To do. In this case, the sales office server 2 includes a table including only a record in which the applicant terminal IP address 106 is 100.100.100.1 and a record in which the applicant terminal IP address 106 is 200.200.200.1. Divide into tables that contain it.

  Next, the branch office server 2 creates the image list 600 by extracting only the image data file name 107 from the divided table. Since the image list 600 is created in such a procedure, if the IP addresses of all the terminals 4 are stored in the applicant terminal IP address 106 of the approval information table 100, the image list 600 is created for each terminal 4. Will be.

  Step 2002: The branch office server 2 transmits the image list 600 created in step 2001 to each terminal 4. As described above, the image list 600 is created for each terminal 4. Then, for example, the image list 600 created from the table including only the record whose applicant terminal IP address 106 is 100.100.100.1 is transmitted to the terminal 4 whose IP address is 100.100.100.1.

  Step 2003: Upon receiving the image list 600, if there is an image file having a file name not included in the image list 600 among the image files in the auxiliary storage device 44, the terminal 4 deletes the file. As a result, only the image file whose file name is included in the image list 600 remains in the auxiliary storage device 44 of each terminal 4.

  Step 2004: The terminal 4 notifies the sales office server 2 that the processing in Step 2003 (that is, file deletion) has been completed.

  Step 2005: When the sales office server 2 receives a notification that the file deletion has been completed from all the terminals 4 that have transmitted the image list 600 in step 2002, it ends the processing.

  In the example of the image file deletion process described above, the image file to be left in each terminal 4 is determined based on the information stored in the applicant terminal IP address 106 and the image data file name 107 in the approval information table 100. Is done. The applicant terminal IP address 106 records the IP address of the terminal 4 from which the person-in-charge terminal 4b has acquired the image file (because the processing in steps 1021 and 1022 is performed). Therefore, the image file stored in the terminal 4 from which the responsible terminal 4b has acquired the image file is left without being deleted, and the image files stored in the other terminals 4 are deleted. For example, when the person in charge terminal 4b acquires an image file from the copy terminal 4c, the image file stored in the copy terminal 4c is left, and the image file in the other terminal 4 (that is, the applicant terminal 4a) is deleted. .

  Note that the image file of the terminal 4 recorded in the applicant terminal IP address 106 does not necessarily have to remain. As long as one of the same image files is deleted and the remaining files are deleted, an arbitrary method may be adopted as a method for determining an image file to be deleted (or a target to be deleted). However, since the terminal 4 recorded in the applicant terminal IP address 106 is the terminal 4 from which the responsible person terminal 4b can obtain the image file, the terminal 4 recorded in the applicant terminal IP address 106 If the image file included in the image file is left, there is a low possibility that the image file cannot be read in the subsequent archiving process.

  After the image file deletion process, the sales office server 2 transmits the transaction item information and the image file pair recorded in the transaction item table 150 to the archive system 7. In this embodiment, this processing is called archive processing. The transaction item information and the image file transmitted to the archive system 7 are stored for a predetermined period. Each terminal 4 deletes the image file from the auxiliary storage device 44 after the image file is transmitted to the archive system 7. The frequency of information transmission to the archive system 7 may be different from the execution frequency of the image file deletion process. For example, the image file deletion process may be executed once a day, and the information transmission to the archive system 7 may be executed once a month.

  As described above, in the sales office business system according to the embodiment of the present invention, since the image file is exchanged only between terminals in the sales office, large-size data such as image data at the time of transaction transaction approval processing. Is not transmitted between the computer center and the sales office. Therefore, data traffic related to various application processes can be reduced, and the performance of the system can be improved.

  When the form is read and an image file is created, the terminal (applicant terminal) creates a duplicate on another terminal (duplicate terminal). If the person-in-charge terminal cannot acquire the image file from the applicant terminal, the person-in-charge terminal can acquire the image file from the terminal storing the copy (copy terminal).

  In the branch office business system according to the first embodiment, the duplication terminal corresponding to the applicant terminal is fixedly determined. However, as another embodiment, the duplicate terminal may be dynamically determined according to the operation status of the terminal. Example 2 describes such an example.

  Since the hardware configuration of the sales office business system according to the second embodiment is the same as that of the sales office business system according to the first embodiment, the description thereof is omitted here. The management information of the sales office server 2 is the same as that described in the first embodiment except for the terminal operation status table 350 described below. Also, since the processing flow when the approval processing is performed in the sales office business system is the same as that described in the first embodiment, the description is omitted here, and a part of the approval processing flow (part of the approval processing in the following description). ) Will be described with reference to FIGS. 9 and 10 used in the first embodiment.

  FIG. 8 is a configuration example of the terminal operation status table 350 included in the branch office server 2 according to the second embodiment. The station number 351 and the terminal number 352 are the same information as the station number 301 and the terminal number 302 in the terminal information table 300 described in the first embodiment. The terminal state 353 represents whether or not the terminal 4 specified by the station number 351 and the terminal number 352 is in operation. The store server 2 periodically checks the operating status of each terminal 4 and updates the contents of the terminal status 353 in the terminal operating status table 350. For example, the branch office server 2 periodically receives an operating state (notifying that it is operating, etc.) from each terminal 4, and when receiving a notification of the operating state from the terminal 4, the terminal state 353 of the terminal 4 is received. Is set to “in operation”, and if the notification of the operation state cannot be received for a certain time or more, the terminal state 353 of the terminal 4 may be set to “stop”.

  On the other hand, the second embodiment also has a terminal information table 300. However, the IP address 304 is not initially stored in the duplicate IP address 304 of the terminal information table 300. The duplicate IP address 304 stores an IP address during the approval process.

  Since the flow of the approval process performed in the branch office business system according to the second embodiment is almost the same as that described in the first embodiment, it will be described with reference to FIGS. However, the contents of the processing performed by the sales office server 2 in step 1003 of FIG. 9 are different between the first and second embodiments. Hereinafter, processing performed by the branch office server 2 according to the second embodiment in step 1003 will be described.

  When the sales office server 2 is requested to acquire the IP address of the replication terminal 4c from the terminal 4 (applicant terminal 4a) in step 1003, the sales office server 2 first refers to the terminal information table 300, and the terminal IP address 303 is obtained. Search for a line that matches the IP address of the applicant terminal 4a (IP address passed from the applicant terminal 4a). This is the same as the processing described in the first embodiment. Subsequently, the branch office server 2 determines whether or not an IP address is stored in the duplicate IP address 304 of the row, and when the IP address is stored, returns the IP address to the applicant terminal 4a. Conversely, when the IP address is not stored, the branch office server 2 identifies the duplicate terminal 4c.

  First, the sales office server 2 uses the IP address of the applicant terminal 4a passed from the applicant terminal 4a in step 1002, and the station number of the sales office where the applicant terminal 4a is installed and the applicant terminal 4a. Specify the terminal number. This can be specified by referring to the station number 301 and the terminal number 302 in the terminal information table 300. Subsequently, the sales office server 2 refers to the terminal operation status table 350 and selects the same row as the station number of the sales office 3 where the station number 351 is located. However, at this time, the line where the terminal number 352 is the same as the terminal number of the applicant terminal 4a is excluded.

  Then, the branch office server 2 determines one row in which the terminal state 353 is “in operation” from the selected row (s). In addition, the determination method at this time may be arbitrary, for example, the branch office server 2 may determine one line at random. The terminal 4 identified by the terminal number 352 in the row determined here is the duplicate terminal 4c.

  Finally, the branch office server 2 specifies the IP address of the terminal 4 corresponding to the terminal number 352 of the determined row (this becomes the IP address of the duplicate terminal 4c) by referring to the terminal information table 300, The identified IP address is stored in the duplicate IP address 304 of the terminal information table 300. Further, the sales office server 2 returns the identified IP address to the applicant terminal 4a.

  By performing such processing, the duplicating terminal 4c is always selected to be in operation, so that when the applicant terminal 4a stores a copy of the image file in the duplicating terminal 4c, the duplicating terminal 4c is operating. It is possible to avoid a situation in which a copy cannot be stored because there is not.

  As mentioned above, although the Example of this invention was described, these are illustrations for description of this invention, Comprising: It is not the meaning which limits the scope of the present invention only to these Examples. The present invention can be implemented in various other forms.

  For example, in the embodiment described above, an example in which the responsible person terminal 4b is one in the sales office 3 has been described, but a plurality of responsible person terminals 4b may exist in the sales office 3. In this case, when the sales office server 2 receives an approval request from the applicant (applicant terminal 4a), the responsible person (responsible person terminal 4b) is identified based on the user ID of the applicant and the identified responsible person A notification that there is an approval request may be transmitted to the terminal 4b. Alternatively, when a person in charge is provided for each type of transaction item, the sales office server 2 identifies and specifies the person in charge terminal 4b based on the type of transaction item received from the applicant (applicant terminal 4a). A notification that an approval request has been made may be transmitted to the responsible person terminal 4b.

  1: computer center, 2: sales office server, 3: sales office, 4 (4a, 4b, 4c): terminal, 5: in-store LAN, 6: WAN, 7: archive system

Claims (13)

Multiple terminals in the store,
A store server installed in a different location from the store, and managing the information and status of transaction items;
A sales office business system having
Each of the terminals includes a scanner that reads a form, a storage device that stores an image file of the form read by the scanner, and a display device.
The plurality of terminals are also communicatively connected to each other via a local area network (LAN) and connected to the branch office server via a wide area network (WAN),
Among the plurality of terminals, an applicant terminal that accepts an approval request for a transaction case from an applicant,
While accepting the input of information on the transaction item, by reading the form related to the transaction item with the scanner, the image data of the form is stored in the storage device,
A copy of the image data of the form is stored in a copy terminal that is one of the plurality of terminals,
Including the file name of the image data of the form related to the transaction item, and sending an approval request for the transaction item to the sales office server,
Among the plurality of terminals, the responsible person terminal used by the responsible person who approves the transaction item, when approving the transaction item,
Receiving information on the transaction item from the branch server,
Request the applicant terminal to obtain image data of the form,
When the image data of the form is successfully acquired from the applicant terminal, the transaction item information and the image data of the form are displayed on the display device, and the transaction case approval instruction is received from the responsible person.
Sales office business system characterized by that. The branch office server manages the information of the duplicate terminal in which the terminal stores a duplicate of the image data of the form for each terminal.
The applicant terminal specifies a duplicate terminal of the applicant terminal by inquiring to the sales office server,
The sales office operation system according to claim 1, wherein: If the responsible person terminal could not obtain the image data of the form from the applicant terminal,
By inquiring to the sales office server, the copy terminal of the applicant terminal is specified, and the image data of the form is acquired from the copy terminal.
The sales office operation system according to claim 2, wherein: If the responsible person terminal could not obtain the image data of the form from the duplicate terminal,
The form is read by the scanner of the responsible person terminal, and the image data of the read form is displayed on the display device of the responsible person terminal.
The sales office operation system according to claim 3, wherein: The responsible person terminal does not accept the transaction case approval instruction until the image data of the form is displayed on the display device of the responsible person terminal,
The sales office operation system according to claim 3, wherein: If the same image data is stored repeatedly in a plurality of the terminals after the processing related to the transaction item is completed, the sales office business system deletes the redundantly stored image data.
The sales office operation system according to claim 1, wherein: The branch office server manages the file name of the image data of the form in association with the information of the terminal from which the responsible terminal acquired the image data of the form,
The branch office server creates a list of file names of the image data of the form acquired from the terminal by the responsible person terminal for each terminal, and sends it to each terminal.
The terminal that has received the list of file names deletes the image data of the form that does not exist in the list of file names from the image data of the form stored in the terminal.
The sales office operation system according to claim 6, wherein: Multiple terminals in the store,
A business processing method in a business system for business offices, which is installed at a location different from the business office and has a business office server that manages information and status of transaction items,
Each of the terminals includes a scanner that reads a form, a storage device that stores an image file of the form read by the scanner, and a display device.
The plurality of terminals are also communicatively connected to each other via a local area network (LAN) and connected to the branch office server via a wide area network (WAN),
Among the plurality of terminals, an applicant terminal that accepts an approval request for a transaction case from an applicant,
Receiving an input of information on a transaction item, and reading a form related to the transaction item with the scanner;
Storing the image data of the form in the storage device;
Storing a copy of the image data of the form in a copy terminal which is one of the plurality of terminals;
Including a file name of image data of the form relating to the transaction item, and sending an approval request for the transaction item to the sales office server;
Run
Among the plurality of terminals, a responsible person terminal used by a responsible person who approves the transaction item,
Receiving information on the transaction item from the store server;
Requesting the applicant terminal to obtain image data of the form;
When the acquisition of the image data of the form from the applicant terminal is successful, displaying the transaction item information and the image data of the form, and receiving an approval instruction for the transaction item from the responsible person,
A business processing method characterized by that. The branch office server manages the information of the duplicate terminal in which the terminal stores a duplicate of the image data of the form for each terminal.
The applicant terminal specifies a duplicate terminal of the applicant terminal by inquiring to the sales office server,
The business processing method according to claim 8, wherein: If the responsible person terminal cannot acquire the image data of the form from the applicant terminal, it identifies the duplicating terminal of the applicant terminal by inquiring to the sales office server, and the image of the form from the duplicating terminal. Perform steps to get data,
The business processing method according to claim 9, wherein: When the responsible person terminal cannot acquire the image data of the form from the duplicating terminal, the responsible person terminal reads the form with a scanner included in the responsible person terminal, and displays the read image data of the form on the responsible person terminal. Perform the steps displayed on the device,
The business processing method according to claim 10, wherein: The responsible person terminal is configured not to accept the transaction case approval instruction until the image data of the form is displayed on the display device of the responsible person terminal.
The business processing method according to claim 10, wherein: When the same image data is stored in duplicate in a plurality of the terminals after the processing related to the transaction item, the step of deleting the image data stored in duplicate is executed.
The business processing method according to claim 8, wherein: