JP3475172B2 - Travel product reservation system for travel agencies and travel product reservation method - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a travel product reservation system for travel agents and a travel product reservation method for making a reservation for a travel product from a terminal arranged at a travel agency or the like.

[0002]

2. Description of the Related Art Conventionally, in the case of sponsored travel, travel products planned and developed by a major travel agency are mainly sold by the major travel agency, but small and medium-sized travel contracted with these major travel agencies. Often sold by traders (travel agencies). In this way, sales of travel products
Since a major travel agency that develops and sells travel products and a travel agency that is an outsourced / contracted sales contract partner are associated with each other, conventionally, a dedicated line was connected between a major travel agency and a major travel agency.
By accessing a host through a dedicated line from a dedicated terminal arranged at a travel agency, a travel agency reserves a travel product to a major travel agency and issues a coupon ticket or the like for the travel product. Further, a travel agency that does not have a dedicated terminal makes a reservation for travel products or issues a coupon ticket or the like to a major travel agency mainly by telephone contact. In addition, the travel agent reserves travel products from a travel agency to a major travel agency by connecting an internet line between the terminal provided at the travel agency and the server and communicating between the terminal and the host via this server. A system has been proposed.

[0003]

However, in the reservation / ticketing system in which the host is directly accessed through the conventional dedicated line as described above, the line usage fee is high and communication between the terminal and the host is possible. There is a problem that the cost required for introducing the system is high because it is necessary to develop a dedicated program for doing so and use a dedicated terminal incorporating this dedicated program. In addition, in the conventional method of reserving travel products and issuing coupons by telephone, it is necessary for the major travel agency, which develops and sells travel products, to have a staff member who is always available for telephone calls. There was a problem that the cost required for the work increased. Furthermore, when the travel product reservation system that communicates between the terminal and the host through the server as described above is used to issue a ticket such as a coupon ticket, a communication error or the like may occur during the ticket issuing process. When a failure occurs, the host cannot know how far the ticketing process has been completed, so there is a possibility that a coupon ticket or the like will be issued twice. Also, if you issue a ticket by any of the above methods,
The major travel agents had to visually check, for untrustworthy travel agents, whether the total ticketing amount for each month of the agency exceeded the ticketing limit. The labor required to manage the store was great.

The present invention solves the above-mentioned problems, and it is possible to issue a coupon ticket or the like for a travel product by a terminal arranged at a travel agency or the like without using a dedicated line or a dedicated terminal. In this way, it is possible to reduce the cost required to install and maintain the system, and to prevent double ticketing even if a failure occurs in the process of issuing a coupon ticket, etc. The purpose is to provide a reservation system and a travel product reservation method. In addition, it automatically checks whether the total ticket amount issued by each travel agency within the specified period exceeds the ticket issuance limit, and based on the result of this check, it is determined whether coupon tickets, etc. can be issued for each travel agency. An object of the present invention is to provide a travel product reservation system for travel companies and a travel product reservation method capable of facilitating the management of each travel agency by a major travel company by making a determination.

[0005]

In order to achieve the above object, the invention of claim 1 is a host computer (hereinafter referred to as "host") for managing reservation of travel products, and a server connected to the host. And a server and a terminal that can communicate with the server via an internet line, which is a travel product reservation system for a travel agent for making reservations for travel products. Ticket issuing is connected to the terminal and prints the print data transmitted from the terminal. In addition to managing travel product reservations, the host manages ticketing, creates ticketing data based on instructions from the terminal via the server, and sends the ticketing data to the server. Is stored in the database in the server, and when the terminal receives a ticketing instruction from the user ,
Read the ticketing data from the database in the server via the Internet line, and based on this ticketing data
The edited print data is sent to the ticket issuing device, and the ticket issuing data stored in the server and the ticket issuing data read in the terminal both include management information of the ticket issuing state for each ticket issuing data. Depending on the result of printing by the device,
The management information of the ticketing status on the terminal side and the server side is updated, and the server issues the ticketing data on the server side in response to the instruction from the terminal.
The management information on the ticketing status is
The management information of the ticket status for ticket data, as well as again updated according to the management information of the ticket status of the terminal, the terminal
Is a program for controlling the ticketing screen and a ticketing device control
And a program for controlling the ticket issuing device
Prints sent from the ticketing screen control program
The ticketing result message for data is displayed on the ticketing screen.
Return to your program to control the ticket issuing device
Accepts ticketing instructions for the ticketing data from the user
Communication line failure between the ticket issuing device and the terminal
If a printing error occurs and the printing process ends abnormally, a ticket is output.
Whether the ticket is issued or not
Page to the program for controlling the ticketing screen, and the ticketing screen
The control program of the shows that it is in an undefined state
When the message of ticketing result is received,
Management information on the ticketing status of the relevant ticketing data on the server side
Indicates that it is uncertain whether or not a ticket has been output.
Program for controlling ticketing screen
Is when a ticketing instruction for ticketing data is received from the user
, The tube of the ticketing state of the relevant ticketing data on the server side
The management information is referred to as "undefined" content.
If the ticket is issued, print data corresponding to the ticket issuing data is output.
The power is not allowed .

[0006]

[0007]

In addition, the terminal is connected via the Internet line.
Ticketing data read from the database in the server is
It is desirable that it has been encoded .

[0009]

[0010]

[0011]

[0012]

[0013]

[0014]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A travel product reservation system for travel agents according to an embodiment of the present invention will be described below with reference to the drawings. FIG. 1 shows a travel product reservation ticketing system for a travel agency according to this embodiment (hereinafter referred to as a reservation ticketing system).
1 shows the configuration of No. 1. This reservation ticket issuing system 1 includes a center-side system 7 arranged in a center 2 of a major travel agency and a reservation / ticket issuing store side arranged in an agent (hereinafter referred to as a reservation / ticket issuing store) 4 that performs a reservation / ticket issuing business. System 8 and agents that only perform reservations (hereinafter referred to as reservation-only stores) 5
And a reservation terminal 22 arranged in the. The reservation / ticket issuing store side system 8 and the reservation terminal 22 are connected to the center side system 7 via the Internet line 3.

The center system 7 is a host / FEP 1
1. Host gateway (abbreviated as host G / W below)
12, a WEB server 13, a ticket issuing DB server 14, and a router 15, and these respective devices are connected by a LAN 16. The host / FEP 11 is a host computer (hereinafter referred to as a host) that manages travel product reservation / ticketing operations and an FE that speeds up host processing.
P (Front End Processor). Host G / W
Reference numeral 12 denotes a server for an interface between the host / FEP 11 and the WEB server 13, and the WEB server 13
The conversion of the data format between the data used by the host and the data used by the host / FEP 11 is performed. WEB
The server 13 receives the reservation or ticketing request message transmitted from the reservation / ticketing store side system 8 via the Internet line 3, and transmits the information to the host G / W 12. Further, the ticket issuing DB server 14 receives the ticket issuing data created by the host based on the content requested from the reservation / ticket issuing store side system 8 via the host G / W 12, and stores this ticket issuing data in an internal database. A combination of the three types of servers, the host G / W 12, the WEB server 13, and the ticket issuing DB server 14 corresponds to the server in the claims. The router 15 includes the LAN 16 of the center-side system 7 and another LAN (for example, reservation /
It is for mutual connection with the LAN 20) of the ticket issuing store side system 8.

The reservation / ticket issuing system 8 is a ticket issuing machine control terminal 1 capable of performing both reservation and ticket issuing operations.
7, a ticket issuing device 18 that prints ticket issuing data sent from the ticket issuing machine control terminal 17, a reservation terminal 19 that can only perform reservation operations, and a router 21 for connecting to the LAN 16 of the center-side system 7. The respective devices are connected by the LAN 20.

Next, the hardware configurations of the ticket issuing DB server 14 and the ticket issuing machine control terminal 17 will be described with reference to FIG. The ticket issuing DB server 14 internally has a CPU 31 for controlling the entire apparatus, a memory 32 for loading various applications when the apparatus is activated, and a CD-R.
OM drive 33 and FDD (Floppy Disk Drive) 3
4 and data DAT (Data Digital Audio Taperecorde
r) 35 and disk array type disk 36
And a LAN board 37 compatible with the 10BASE-T and 100BASE-T standards. Further, the ticket issuing machine control terminal 17 is a general personal computer, and includes a TFT monitor or a CRT (hereinafter referred to as a monitor) 38 and a CP for controlling the ticket issuing machine control terminal 17 as a whole.
U39, memory 40 for loading various applications, CD-ROM drive 41, FDD4
2, HDD (Hard Disk Drive) 43, and 10 BAS
LAN compatible with ET and 100BASE-T standards
It consists of a board 44.

Next, with reference to FIG. 3, the software configurations of the three types of servers 12 to 14 on the center side system 7 side and the ticket issuing machine control terminal 17 on the reservation / ticketing store side system 8 side will be described. Center side system 7 host G /
W12 is a ticketing DB writing AP (Application Progra
m) Host system interlocking middleware 51 including 50,
The middle software 52 that is a tool for the server, and the OS for the server (for example, Microsoft Windows NT 4.0
Server) 53 and the like. Also, WEB server 1
3 is a ticketing data list display ASP (Acti) for displaying a list screen of ticketing information on the monitor of the ticket issuing machine control terminal 17.
ve Server Pages: Web server script execution environment)
54, ticket-issuing DB server communication ASP 55 for communicating with the ticket-issuing DB server 14, business ASP group 56, Internet / Intranet server tool (for example, Microsoft's Internet Information Server) 57, SQL
It has an ODBC 58 for accessing the Server, a server OS 53, and the like. Also, the ticket issuing DB server 1
4 is a database tool for inputting / outputting with the ticket issuing DB 60 (for example, SQL Server of Microsoft Corporation).
7.0) 59, and server OS 53, etc.

The ticket issuing machine control terminal 17 on the side of the reservation / ticket issuing system 8 is a content on the WEB server 13 (materials such as images and sounds necessary for creating a multimedia application, and the multimedia application itself). And WEB (including services provided by multimedia applications)
The programs in the ticket issuing machine control terminal 17 downloaded from the browser 61 and the center side system 7 are remotely controlled.
Limomen AP62 for maintenance, ticketing DB server communication ActiveX for communicating with ticketing DB server 14
(Ticketing content) 63, ticketing device control AP (Ticketing process) 64, middle software 65 that is an application such as a reservation service, and OS for client (for example, Microsoft Windows NT 4.0 Workstation)
It has 62 and the like. Further, the reservation terminal 19 is a WEB browser for browsing the content on the WEB server 13 (for example, Internet Explorer 5.
0) 61 and so on.

Next, with reference to FIG. 4, the process from the reservation to the printing of the coupon ticket in the reservation ticket issuing system 1 will be described. In the following description, the case where the user requests the reservation process and the ticket issuing instruction process from the reservation terminal 19 to the host / FEP 11 will be described as an example. However, even if the user requests these processes from the ticket issuing machine control terminal 17. Good. When the user of the reservation / ticketing store 4 shown in FIG. 1 makes a reservation for a travel product from the reservation terminal 19 and then issues a coupon ticket 75 from the ticketing operation screen 80, W on the reservation terminal 19 side
As shown by, the EB browser 61 sends the host / FEP 1 via the WEB server 13 and the host G / W 12.
The reservation message and the ticket issuing message are transmitted to 1. Host / FEP
Upon receiving these telegrams, the 11 creates response telegrams corresponding to these telegrams, and the host G / W 12 and the WEB
It is transmitted to the reservation terminal 19 via the server 13. At this time, the host / FEP 11 creates a telegram addressed to the ticket issuing printer (ticket issuing device) as shown in, and issues this telegram to the ticket issuing D on the ticket issuing DB server 14 via the host G / W 12.
The information is stored in B60, and at the same time, the information indicating that the ticket issuing process for the corresponding reservation information is completed is written in the management data on the host side.

After the above processing, the user of the reservation / ticketing store 4 uses the WEB browser 61 of the ticket issuing machine control terminal 17 to access the WEB.
When the server 13 is requested to transmit the ticketing data for the store, the WEB server 13 reads the ticketing data of the store from the ticketing DB 60 and displays a screen of a list of ticketable data ( The ticket issuing status list screen) 81 is displayed on the monitor of the ticket issuing machine control terminal 17. Then, when the user selects the ticketing target data from the ticketing status list screen 81 of the ticket issuing machine control terminal 17 and clicks the ticketing button on the ticketing status list screen 81, WE
The B server 13 rewrites the ticket issuing flag in the ticket issuing data corresponding to the selected data to “ticket issuing”, and
As shown in, the ticket issuing data corresponding to the selected data is encrypted and downloaded to the ticket issuing machine control terminal 17. The ticket issuing machine control terminal 17 decrypts the downloaded ticket issuing data, edits it into print data for a coupon ticket, and sends the edited print data to the ticket issuing device 18. The ticket issuing device 18 prints the coupon ticket 75 based on the print data. Further, the ticket issuing machine control terminal 17
When the printing of the coupon ticket 75 is completed normally, the ticket issuing DB 60 is accessed through the WEB browser 61 to issue the ticket issuing D.
Read the ticketing data record from B60,
The ticket issuing flag in the corresponding record is rewritten to "ticket issued". However, when the printing of the coupon ticket 75 ends abnormally, the ticket issuing flag in the ticket issuing data record is rewritten to "error" or "undefined". In addition, “indefinite” refers to a state in which it is unclear whether or not the coupon ticket 75 has been output, and after the coupon ticket 75 is instructed to be printed from the ticket issuing status screen 81, the coupon ticket 75 is printed due to a failure such as a LAN. Occurs when is abnormally terminated.

Next, the processing of the host G / W 12 when making a reservation for a travel product from the reservation terminal 19 to the center side system 7 will be described with reference to FIG. Host G /
W12 is a store master DB 7 on the ticket issuing DB server 14.
The data of the current month's ticketing amount, monthly collateral amount, and new reservation stop sign of each store, which are stored in 0, are referred to, and it is determined whether or not a new reservation can be made for each store based on these data. That is, as shown in FIG.
When the reservation information is input from the EB browser 61 (S
1) After receiving this reservation information via the WEB server 13, the host G / W 12 refers to the store master DB 70 on the ticket issuing DB server 14 (S2), and the reservation terminal 1
The data of the current month's ticketing amount and monthly collateral amount of the store where 9 is arranged is read. Then, the host G / W 12 compares the ticket issuing amount of the current month with the monthly collateral amount (S
3) If the ticketing amount for the current month has already exceeded the monthly collateral amount (YES in S3), refer to the new reservation stop sign in the store master DB 70 (S4), and if the new reservation stop sign is ON (YES in S5), the message "No new reservation can be made" is displayed on the WEB browser 61 of the reservation terminal 19 (S6).

On the other hand, in S3, if the ticket issuing amount in the current month has not exceeded the monthly collateral amount (NO in S3) and the new reservation stop sign is OFF (NO in S5), the host G / W 12 , Store confirmation D on ticketing DB server 14
Items such as the transmission time, the input serial number, and the terminal ID are written in the B71 and the answer confirmation DB 72 (S7). Then, based on the reservation information input from the WEB browser 61 of the reservation terminal 19 in S1, a reservation telegram for transmission to the host / FEP 11 is created, and this reservation telegram is transmitted to the host / FEP 11 (S8). Then, when the host G / W 12 receives the reply from the host / FEP 11 (S9), it issues the ticket D
Store confirmation DB71 and answer confirmation DB7 on B server 14
After writing the answer items in 2 (S10), the reservation terminal 1
The reply from the host / FEP 11 is transmitted to the WEB browser 61 of 9 (S11). The above-mentioned travel product reservation can be made not only from the reservation terminal 19 but also from the ticket issuing machine control terminal 17 or the reservation terminal 22. This point is related to the ticket issuing instruction, the change, described in FIGS. 6 to 10 below.
The same applies to each processing of change instruction, cancellation, and reissue ticket. The new reservation stop sign and the monthly collateral amount of each store in the store master DB 70 are set by the administrator of the center-side system 7 according to the sales record and credit of each store.

Next, with reference to FIG. 6, the processing of the host G / W 12 when issuing an instruction to issue the coupon ticket 75 from the reservation terminal 19 to the center side system 7 will be described. It should be noted that here, only the process of creating ticket issuing data based on the ticket issuing instruction from the reservation terminal 19 will be described, and the process related to the printing of the coupon ticket 75 will not be described. As shown in the figure, the user has the reservation terminal 19 shown in FIG.
If you enter a reservation number etc. from the ticketing business screen 80 (S2
1), the WEB browser 61 on the reservation terminal 19 side sends information such as the reservation number to the host G / via the WEB server 13.
Send to W12. Upon receiving these pieces of information, the host G / W 12 checks whether or not the coupon ticket 75 corresponding to the inputted reservation number can be issued. That is, when the host G / W 12 receives the information such as the reservation number, the host G / W 12 refers to the store confirmation DB 71 on the ticket issuing DB server 14 (S22), and has a record having the same reservation number as the received reservation number in the store confirmation DB 71. Check if exists. Then, if there is no record having the same reservation number (NO in S23), W of the reservation terminal 19
The message "The reservation number does not exist in your store." Is displayed on the EB browser 61 (S24). On the other hand, when the record having the same reservation number exists in the store confirmation DB 71 (YES in S23), the host G
/ W12 refers to the ticket-issuing DB 60 on the ticket-issuing DB server 14 (S25), and checks whether or not there is a record having the same reservation number as the received reservation number in the ticket-issuing DB 60. Then, if a record having the same reservation number exists in the ticket issuing DB 60 (YES in S26), it can be determined that the ticket issuing data of the coupon ticket 75 corresponding to the received reservation number has already been created. Do not create ticketing data. Then, referring again to the relevant ticketing data in the ticketing DB 60 (S27), if the ticketing flag is "ticketing completed" (YES in S28), the "reservation in question" is displayed on the WEB browser 61 of the reservation terminal 19. Has been issued. ”(S29), and if the ticketing flag is“ waiting for ticketing ”,“ in ticketing ”,“ error ”or“ undefined ”(NO in S28), the WEB browser 61. A message "Please make a ticket import operation for the reservation" is displayed above (S30).

Next, the host G / W 12 refers to the data of the current month's ticketing amount, monthly collateral amount, and new ticketing stop sign of each store stored in the store master DB 70 on the ticketing DB server 14 and refers to these data. Whether to issue a new ticket at each store is determined based on the data. That is, host G / W
12 is a store master DB 70 on the ticket issuing DB server 14
Referring to (S31), the reservation terminal 1 that transmitted the reservation information
The data of the current month's ticketing amount and monthly collateral amount of the store where 9 is arranged is read. Then, the current month's ticketing amount and the monthly collateral amount are compared (S32), and if the current month's ticketing amount exceeds the monthly collateral amount (YE in S32).
S) Referring to the new ticketing stop sign in the store master DB 70 (S33), if the new ticketing stop sign is ON (YES in S34), the "new ticket issuance" is displayed on the WEB browser 61 of the reservation terminal 19. The message "Cannot" is displayed (S35). On the other hand, in S32, when the ticket issuing amount in the current month has not exceeded the monthly collateral amount (N in S32,
O) and the new ticketing stop sign is OFF (S3
4 is NO), the host G / W 12 is the ticket issuing DB server 14
Items such as the transmission time, the input serial number, and the terminal ID are written in the store confirmation DB 71 and the response confirmation DB 72 (S3).
6). Then, the host G / W 12 creates a ticketing telegram for transmission to the host / FEP 11 based on the information such as the reservation number input from the WEB browser 61 of the reservation terminal 19 in S21, and the ticketing telegram is sent to the host. -Send to FEP11 (S37).

The host G / W 12 is a host / FEP 11
When the reply from is received (S38), the ticket issuing DB server 1
The answer items are written in the store confirmation DB 71 and the answer confirmation DB 72 on the above 4 (S39), and at the same time, the ticket issuing data of the corresponding reservation number is written in the ticket issuing DB 60 based on the answer message from the host / FEP 11. This ticketing data is stored for 6 months from the date of departure. After that, the host G / W 12 displays the host / FEP 1 on the WEB browser 61 of the reservation terminal 19.
The reply message from 1 is sent (S40) and the host
The ticketing amount in the reply message from FEP 11 is added to the ticketing amount for the current month in the record of the store master DB 70 read in the process of S31, and this record is added to the store master DB.
It rewrites (rewrites) 70 (S42). In addition,
The new ticket issuing stop sign of each store in the store master DB 70 is set by the administrator of the center-side system 7 according to the sales record and credit of each store.

Next, the processing of the host G / W 12 when the reservation terminal 19 requests the center side system 7 to change the reservation content will be described with reference to FIG. When the user inputs reservation change information from the WEB browser 61 of the reservation terminal 19 (S51), the WEB browser 61 sends this reservation change information to the host G / via the WEB server 13.
Send to W12. Upon receiving the reservation change information, the host G / W 12 checks whether the reservation information corresponding to the input reservation number is changeable. That is, when the host G / W 12 receives the reservation change information,
By referring to the store confirmation DB 71 on the ticket issuing DB server 14 (S52), it is checked whether or not there is a record having the same reservation number as the reservation change information received in the store confirmation DB 71. Then, if there is no record having the same reservation number (NO in S53), the message "The reservation number does not exist in your store" is displayed on the WEB browser 61 of the reservation terminal 19 (S54). ). On the other hand, when the record having the same reservation number exists in the store confirmation DB 71 (YES in S53), the host G / W 12 issues the ticket issuing DB 60 on the ticket issuing DB server 14.
(S55), it is checked whether or not there is a record having the same reservation number as the reservation number received in the ticket issuing DB 60. Then, a record having the same reservation number exists in the ticket issuing DB 60 (YES in S56), and
As a result of referring to the record (S57), if the ticket issuing flag is "ticket waiting", "ticketing", "error" or "undefined" (NO in S58), the host G / W 12
The change of the corresponding reservation information is not permitted, and the message "The ticketing operation for the reservation is not completed. Please complete the ticketing operation." Is displayed (S59). Because,
If the ticket issuing flag for the corresponding reservation information is "waiting for ticketing", "during ticketing", "error" or "undefined", the ticket issuing data in the unissued state for the applicable reservation information is stored in the ticket issuing DB 60. Since it is highly likely that the coupon information has been accumulated, if the content of the reservation information is changed in this state, when the coupon ticket 75 with the corresponding reservation number is subsequently issued, the issued coupon ticket 75 will be either before or after the change. This is because it cannot be determined whether the reservation information is based on the reservation information.

On the other hand, if no record having the same reservation number exists in the ticket issuing DB 60 in S56 (S56).
NO), and if the ticketing flag is “ticketing completed” in S58 (YES in S58), the host G / W 12 determines the store confirmation DB 71 and the answer confirmation D on the ticketing DB server 14.
Items such as the transmission time, the input serial number, and the terminal ID are written in B72 (S60). Then, in S51, the WE of the reservation terminal 19
Based on the reservation change information input from the B browser 61, a reservation change message for transmission to the host / FEP 11 is created, and this reservation change message is transmitted to the host / FEP 11 (S61). Host G / W12 is host / FEP
When the reply message from 11 is received (S62), ticketing DB
Store confirmation DB71 and answer confirmation DB72 on the server 14
After writing the answer items in (S63), the reservation terminal 19
The reply message from the host / FEP 11 is transmitted to the WEB browser 61 (S64).

Next, with reference to FIG. 8, the processing of the host G / W 12 when the reservation terminal 19 requests the center side system 7 to change the reservation contents and issue the changed ticket at the same time will be described. In the following description, the reservation content changing process and the ticket issuing process are collectively referred to as a changed ticket issuing process. As shown in the figure, the host G / W 12 inputs (S
71) When the modified ticket issuing information is received via the WEB browser 61 and the WEB server 13, after performing the same processing as S52 to S62 in FIG. 7 described above (S72 to S8).
2), based on the answer message received from the host / FEP 11, write the answer items in the store confirmation DB 71 and the answer confirmation DB 72 on the ticket issuing DB server 14, and issue the ticket issuing DB
The corresponding ticket issuing data in 60 is rewritten (S83).
Then, the WEB browser 61 of the reservation terminal 19 hosts
After sending the reply message from FEP11 (S84),
Store master DB 70 according to the changed ticketing data
Correct the ticket issue amount for the current month's record in the corresponding store. Specifically, the host G / W 12 checks whether or not there is a record of the reservation number to be changed in the ticket issuing DB 60 (S85, S86), and the record of the corresponding reservation number exists (S86). (YES) and if the old ticket issuing date in the record is the current month (YES in S87), refer to the record of the store in the store master DB 70, and issue amount of the current month in the store master DB record. Modify according to the changes. Specifically, store master D
After subtracting the old ticket issuing amount on the ticket issuing DB record from the current month issuing ticket amount on the B record, the changed ticket issuing amount in the reply message from the host / FEP 11 is added to the current month ticket issuing amount after subtraction. Then, the calculated store master DB record is rewritten (rewritten) in the store master DB 70 (S89).

Next, the processing of the host G / W 12 when the reservation terminal 19 requests the center side system 7 to cancel (cancel) the reservation content will be described with reference to FIG. As shown in the figure, the host G / W 12
When the cancellation information input by the user (S91) is received via the WEB browser 61 and the WEB server 13, the host / FEP 11 is executed after performing the same processing as S52 to S62 in FIG. 7 (S92 to S102). Based on the response telegram received from, the response item is written in the store confirmation DB 71 and the response confirmation DB 72 on the ticket issuing DB server 14 (S103). At this time, the content written in the response confirmation DB 72 also includes a flag indicating that the reservation information has been canceled. Then, after sending the reply message from the host / FEP 11 to the WEB browser 61 of the reservation terminal 19 (S104), according to the cancellation information input by the user in S91, the ticket is issued in the month of the record of the corresponding store in the store master DB 70. Correct the amount. Specifically, host G
/ W12 checks whether or not the record of the reservation number to be changed exists in the ticket issuing DB 60 (S10).
5, S106), and the record of the corresponding reservation number exists (S
(YES at 106) and if the old ticket issuing date in the record is the current month (YES at S107), refer to the record of the store in the store master DB 70 to issue the current month on the store master DB record. Correct the amount according to the cancellation information. Specifically, after subtracting the old ticket-issuing amount in the ticket-issuing DB record from the current month ticket-issuing amount in the dealer master DB record, the host / FEP1
Add the new ticket amount in the response message from 1 (S10)
8). Then, the calculated store master DB record is rewritten (rewritten) in the store master DB 70 (S).
109).

Next, with reference to FIG. 10, the processing of the host G / W 12 in the case where the reserving terminal 19 instructs the center side system 7 to reissue the coupon ticket 75 will be described. It should be noted that here, the description will be made up to the point where the ticket issuing data for the reissue ticket is created based on the reissue ticket instruction from the reservation terminal 19, and not the processing related to the printing of the coupon ticket 75. When the user on the reservation terminal 19 side inputs the reservation number or the like corresponding to the reservation information for the reissue ticket from the ticket issuing operation screen 80 shown in FIG. 4 (S121), the WEB browser 61 on the reservation terminal 19 side, the reservation number or the like. Information on WEB
It is transmitted to the host G / W 12 via the server 13. Upon receiving these pieces of information, the host G / W 12 checks whether or not the coupon ticket 75 corresponding to the inputted reservation number can be reissued. That is, the host G / W 12
When the information such as the reservation number is received, the ticket issuing DB server 1
4 is referred to (S122), and it is checked whether or not there is a record having the same reservation number as the received reservation number in the shop confirmation DB 71. And
If no record with the same reservation number exists,
(NO in S123), WEB browser 6 of the reservation terminal 19
The message "The relevant reservation number does not exist in your store." Is displayed on the screen 1 (S124). On the other hand, when the record having the same reservation number exists in the store confirmation DB 71 (YES in S123), the host G / W 12
Refers to the ticket-issuing DB 60 on the ticket-issuing DB server 14 (S125) and checks whether or not there is a record having the same reservation number as the received reservation number in the ticket-issuing DB 60. If there is no record with the same reservation number in the ticket issuing DB 60 (NO in S126), the message "The reservation is not issued yet. Please perform ticketing operation" on the WEB browser 61 of the reservation terminal 19. Is displayed (S127). If there is a record with the same reservation number in the ticket issuing DB 60 (YES in S126).
S), the host G / W 12 reads the corresponding record from the ticket issuing DB 60 (S128), and when the ticket issuing flag in the record is "waiting for ticket issuing", "during ticket issuing", "error" or "undefined". (NO in S129), "The ticketing operation for the reservation is not completed on the WEB browser 61."
Please complete the ticketing operation. Message is displayed (S130).

On the other hand, if the ticket issuing flag of the record in the ticket issuing DB 60 is "ticket issued" (S129).
YES), the host G / W 12 determines that the ticket issuing DB server 14
Items such as transmission time, input serial number, and terminal ID are written in the store confirmation DB 71 and the response confirmation DB 72 (S13).
1). Then, based on the information such as the reservation number input from the WEB browser 61 of the reservation terminal 19 in S121, a reissue ticket telegram for transmission to the host / FEP 11 is created,
This reissue ticket message is sent to the host / FEP 11 (S1
32). The host G / W 12 is a host / FEP.
When the reply message from 11 is received (S133), ticket issuance D
Store confirmation DB71 and answer confirmation DB7 on B server 14
Write the answer items in 2 (S134), and at the same time, the host
The ticket issuing data of the corresponding reservation number is written in the ticket issuing DB 60 based on the reply message from the FEP 11. After this, Host G
/ W12 transmits the reply message from the host / FEP 11 to the WEB browser 61 of the reservation terminal 19 (S13).
5) Display the contents on the monitor of the reservation terminal 19.

Next, the ticket issuing status list screen 81 shown in FIG. 4 will be described with reference to FIG. As shown in the figure, ticket issuing buttons 82 corresponding to various reservation information in the store are displayed on the ticket issuing status list screen 81, and the user clicks these buttons 82 to issue a coupon ticket. It is possible to issue 75 tickets or display error contents. That is, as shown in the figure, when the user clicks on the ticketing button 82a in the "ticketing waiting" state, the ticketing message 83 is displayed on the monitor of the ticket issuing machine control terminal 17 to correspond to the selected ticketing data. Issuance of the coupon ticket 75 is started. Then, the ticket issuing message 83 is displayed on the monitor of the ticket issuing machine control terminal 17 until the ticket issuing of the coupon ticket 75 is completed. Also, as shown in the figure, the user may get an "error"
When the ticket issuing button 82b in the state or the ticket issuing button 82c in the "indefinite" state is clicked, the error content display screen 84 is displayed on the monitor of the ticket issuing machine control terminal 17.

FIG. 12 shows the format of the ticket issuing status screen 81. Ticketing DB 60 is displayed on the ticketing status list screen 81.
A plurality of ticket-issuing buttons 82 created based on ticket-issuing data belonging to the relevant store are displayed. These ticketing buttons 82 are displayed such that the ticketing date and time displayed on the upper left button in the drawing is the oldest, and the ticketing date and time is new in the order along the arrow in the drawing. Further, as shown in the drawing, the number column 69 in the upper right part of the screen 81 displays the number of ticketing data of the corresponding store stored in the ticketing DB 60. The number of ticketing data and the number of ticketing buttons 82 that can be displayed on the ticketing status list screen 81 differ depending on which button is selected by the state selection button 86, and, for example, the “waiting for ticketing” button is selected. In this case, the ticket issuing flag in the ticket issuing DB 60 is "waiting for ticket issuing".
Only the ticket issuing data button 82 in the state of is displayed.

FIG. 13 shows the format of the error content display screen 84. On this screen, the date and time of occurrence of a ticketing error, the error state, etc. of the ticketing data of the reservation number corresponding to the ticketing buttons 82b and 82c selected by the user from the ticketing status list screen 81 are displayed.

FIG. 14 shows the ticket issuing message 83. The in-ticket issuing message 83 is superimposed and displayed on the issuance status list screen 81. While the ticket issuing message 83 is displayed, the operation of the ticket issuing status screen 81 is locked. When the printing process of the coupon ticket 75 is completed, the message 83 automatically disappears from the monitor and the control returns to the ticket issuing status screen 81.

Next, a device for preventing double generation of the coupon ticket 75 when the printing process of the coupon ticket 75 adopted in the reservation ticket issuing system 1 is abnormally terminated (see the above-mentioned paragraph 0021) will be described. . Coupon voucher 75
When the printing of “No” is abnormally ended, the ticket issuing device 18 accesses the ticket issuing DB 60 and rewrites the ticket issuing flag in the ticket issuing data record to “error” or “indefinite”.
When the ticketing flag is in the "error" or "undefined" state, the program for controlling the ticketing status list screen 81 (corresponding to the ticketing DB server communication ActiveX 63 in FIG. 3) corresponds to the ticketing data. Printing of the coupon ticket 75 is not permitted. In order to cancel this state and print the coupon ticket 75 again, it is necessary to rewrite the ticket issuing flag in the ticket issuing data record from "error" or "undefined" to "waiting for ticket issuing". In this reservation ticket issuing system 1, the ticket issuing flag can be rewritten only from the monitoring center to prevent double issue of the coupon ticket 75. That is, even when a failure occurs during printing of the coupon ticket 75 and the ticket issuing flag in the ticket issuing data record is in the “error” or “indeterminate” state, for example, the time when the failure occurs is that of the coupon ticket 75. If printing is completed, there is no need to reissue the coupon ticket 75,
If the coupon ticket 75 is permitted to be reissued in such a case, the coupon ticket 75 will be issued twice.
Therefore, if the printing of the coupon ticket 75 ends abnormally, the coupon of the coupon must be sent after the user of each store has contacted the monitoring center to confirm the error state and rewrite the ticket issuing flag by the monitoring center. The ticket 75 cannot be reprinted.

Next, referring to FIG. 15, the coupon ticket 7 for the ticket issuing data in which the ticket issuing flag is in the "undefined" state
A process for reprinting 5 will be described. When the user sends a request to display the ticketing status list screen 81 from the ticket issuing machine control terminal 17 to the WEB server 13, the ticketing data list display ASP 54 of the WEB server 13 is an ActiveX for displaying the ticketing status list screen on the ticket issuing machine control terminal 17. The ticket issuing data of the corresponding store in the ticket issuing DB 60 is transmitted. Ticket issuing machine control terminal 17
Receives these data by the WEB browser 61 and displays the ticket issuing status screen 81 based on these data. At this time, when the ticket issuing DB 60 has ticket issuing data in which the ticket issuing flag is in the “undefined” state, the ticket issuing machine control terminal 17 indicates that the ticket issuing flag is displayed on the ticket issuing situation list screen 81 as indicated by. It is displayed that there is ticket data of "undefined". Based on this display, the user of each store confirms that there is ticket issuing data in which the ticket issuing flag is "indeterminate".
In order to cancel the above condition, contact the staff at the monitoring center by telephone. Upon receipt of the notification, the staff of the monitoring center gives an instruction from the terminal 77 of the monitoring center to the ticket issuing indefinite state releasing program 67 on the WEB server 13 as indicated by, and the ticket issuing indefinite state releasing program 67 issues a ticket D.
The ticket issuing flag in B60 is rewritten. Specifically, the clerk of the monitoring center selects the button 88 of the ticket issuing data from the status change button 88 displayed on the ticket issuing status list screen 87 for status change, and the coupon ticket 75 for the ticket issuing data 75 If the printing of the coupon ticket has already been completed, the ticket issuing flag of this ticket issuing data is rewritten from "undetermined" to "ticket issued", and if the printing of the coupon ticket 75 is not completed, the ticket issuing flag is changed from "undetermined". Rewrite as "Waiting for ticketing". Then, when the printing of the coupon ticket 75 is not completed, the user of each store prints the coupon ticket again.

FIG. 16 shows the format of the status change ticket issuing status list screen 87. On this screen 87, a plurality of state change buttons 88 created based on the ticket issuing data belonging to the relevant store in the ticket issuing DB 60 are displayed, and these ticket issuing buttons 82 are displayed on the upper left button in the figure. The issued date and time of the issued ticket are the oldest, and in the following, the issued date and time are displayed in a new order in the order of the arrows in the figure. Further, as shown in the drawing, the terminal ID of the ticket issuing machine control terminal 17 of the store is displayed in the terminal ID column 68 at the upper left portion of the screen 87. Furthermore, the number-of-cases column 90 and the state selection button 91 in the figure are the number-of-cases column 69 and the state selection button 8 in the ticketing status list screen 81 shown in FIG. 12, respectively.
Equivalent to 6.

FIG. 17 shows the status change screen 89. The state change screen 89 is displayed on the state change ticketing situation list screen 87 in an overlapping manner when the state change button 88 displayed on the state change ticketing situation list screen 87 is clicked. On the status change screen 89, the reservation number, the business name, and the status information (of the ticket issuing flag) are displayed from the ticket issuing data information corresponding to the selected status change button 88. The staff at the monitoring center can use this status change screen 89
By inputting the state of the new ticket issuing flag from the upper state column 94 and clicking the change button 95, the state of the ticket issuing flag in the ticket issuing data displayed on the state changing screen 89 can be rewritten. Therefore, even if the user of each store has the status of the ticketing flag displayed on the status change button 88 on the status change ticketing status list screen 87 is "error" or "undefined", the user of the monitoring center By requesting the clerk to change the state of the ticket issuing flag to the “ticket waiting” state, the coupon ticket 75 for the relevant ticket issuing data can be re-output. But,
When the staff at the monitoring center determines that the output of the coupon ticket 75 for the relevant ticketing data has already been completed based on the error occurrence state or the like, it notifies the user of each store to that effect and informs about the relevant ticketing data. Do not change the ticket issuing flag. Thereby, even if a failure occurs during the printing process of the coupon ticket 75, it is possible to prevent the user of each store from accidentally issuing the coupon ticket 75 twice.

As described above, in the reservation ticket issuing system 1, the ticket issuing state of each ticket issuing data is managed based on the ticket issuing flag of each ticket issuing data stored in the ticket issuing DB 60 on the ticket issuing DB server 14. By making it possible to print only the ticketing data in the "waiting for ticketing" state, double issuance of the coupon ticket 75 is prevented. That is, ticket issuing D
By locking the print data (ticket issuing data) of the coupon ticket 75 stored in the B server 14, the coupon ticket 7
Prevents double ticketing of 5. By adopting such a double ticketing prevention method, it is not limited to the case where a failure occurs during the printing of the coupon ticket 75 as described above, but the user is placed in the same ticket issuing machine control terminal 17 or the same store. In addition, it is possible to prevent the data of the same reservation number from being issued twice by mistake from different ticket issuing machine control terminals 17.

However, when the ticketing state of each ticketing data is managed based only on the ticketing flag of each ticketing data stored in the ticketing DB server 14, the following problems occur. That is, when the ticket issuing machine control terminal 17 updates the ticket issuing flag of each ticket issuing data stored in the ticket issuing DB server 14 during the printing process of the coupon ticket 75, the ticket issuing flag fails to be updated for some reason. In this case, the ticketing state of the ticketing data managed by the ticket issuing machine control terminal 17 side is “ticketing completed”, “error”, or “undefined”, but the ticketing data on the ticketing DB server 14 side The ticket issuing flag remains as "Ticketing". At this time, ticketing DB
Since the print data (ticketing data) is locked based on the ticketing flag on the server 14 side, double ticketing of the coupon ticket 75 can be prevented, but even if the corresponding coupon ticket 75 is not output, the coupon is not output. The ticket 75 cannot be output again. Further, when the ticket issuing machine control terminal 17 side user has the ticket issuing flag of the ticket issuing data on the ticket issuing DB server 14 side in the “error” or “indefinite” state, some error is displayed on the ticket issuing status screen 81. Although it is possible to know that an error has occurred, it is not possible to immediately know that an error has occurred if the ticket issuing flag remains "ticketing". Therefore, the coupon ticket 75 corresponding to the print data (ticket issuing data) in which the error has occurred may be forgotten to be issued.

In order to prevent the above situation from occurring, in the reservation ticket issuing system 1, the ticket issuing machine control terminal 17 holds detailed information on the ticket issuing status and issues the ticket issuing status screen 81.
At the initial display of, the WEB browser 61 of the ticket issuing machine control terminal 17 manages the ticket issuing flag on the ticket issuing machine control terminal 17 side only for the ticket issuing data for which the ticket issuing flag on the ticket issuing DB server 14 side is "ticketing". The WEB server 13 is requested to update according to the detailed information of the issued ticket status. The WEB server 13 issues a ticketing DB in response to this request.
The ticket issuing flag on the server 14 side is updated. By performing such control, the ticket-issuing machine control terminal 17 causes the ticket-issuing DB server 1 for some reason during the printing process of the coupon ticket 75.
Even if the ticket issuing flag on the 4th side fails to be updated, the ticket issuing DB
It is possible to prevent the ticket-issuing flag of the ticket-issuing data on the server 14 side from remaining in the "ticket issuing" state.

Next, three types of obstacles that can occur when the ticket issuing machine control terminal 17 updates the ticket issuing flag of each ticket issuing data stored in the ticket issuing DB server 14 will be described.
These three types of failures are an inter-module communication failure, server inaccessibility, and ticketing machine control terminal power down. Among them, the communication error between the modules means that the communication between the modules by the socket (the mechanism used by the network application for inter-process communication in the Windows environment) cannot be performed, and the server inaccessibility means the internet connection 3 Server side (center side system 7 side) due to disconnection of various servers, down of various servers 12, 13, 14 etc.
Access to the ticket issuing machine control terminal 17 means that the ticket issuing machine control terminal 17 has been powered off.

Next, the above-mentioned inter-module communication abnormality will be described with reference to FIG. Ticketing DB server communication Acti
Communication between veX (abbreviated as ticket issuing ActiveX) 63 and the ticket issuing module 98 (corresponding to the ticket issuing device control AP 64 in FIG. 3) is performed by a socket. Further, as shown in the figure, the ticket issuing module 9 responds to the transmission of one print data (ticket issuing data) 99 from the ticket issuing ActiveX 63.
Inter-module communication is performed in a format in which one ticketing result message 100 from 8 is returned. At this time, if the ticket issuing module 98 does not return the ticket issuing result message 100 even if 3 minutes or more have elapsed after the print data 99 was transmitted, the ticket issuing ActiveX 63 determines that an error relating to socket communication has occurred. Then, the process ends. Such a failure is called inter-module communication abnormality.

Next, with reference to FIG. 19, an outline of printing and issuing processing of the coupon ticket 75 performed on the ticket issuing machine control terminal 17 side will be described. When the user of the ticket issuing machine control terminal 17 instructs the display of the ticketing business screen 80 from the terminal 17, the WEB browser 61 of the terminal 17 sends the URL of the ticketing business screen 80 to the WEB server 13 (S121). At this time, the WEB server 13 checks the version of the ticket issuing ActiveX 63 stored in the terminal 17 at that time, and if the version is not the latest, issues the latest version of the ticket issuing ActiveX 63 to the ticket issuing machine control terminal. 1
7 is downloaded (S122). Further, the WEB server 13 does not accept the request for displaying the ticketing business screen 80 from the terminal 17 when the time when the URL of the ticketing business screen 80 is received from the terminal 17 is outside the operation time of the center side system 7. On the other hand, from the terminal 17 to the above UR
If the time when L is received is within the operation time of the system 7 on the center side (corresponding to “normal” in the figure), ticketing ActiveX
63 is activated (S123). Next, when the user of the terminal 17 gives an instruction to move the screen to the ticketing status list screen 81, the ticketing ActiveX 63 of the terminal 17 sends the URL of the ticketing status list screen 81 to the WEB server 13 via the WEB browser 61.
Is transmitted (S124). Upon receiving the URL of this screen 81, the ticket issuing data list display ASP 54 on the WEB server 13 acquires the ticket issuing data (print data) for list display from the ticket issuing DB 60 on the ticket issuing DB server 14,
This ticketing data is transmitted to the terminal 17. Ticketing for terminal 17
The ActiveX 63 displays the ticket issuing status list screen 81 based on the ticket issuing data (S125). Then, when the user selects and inputs the reservation number of the ticketing data to be ticketed from the ticketing status list screen 81 (S126), ticketing Active
The X63 and the ticket issuing module 98 perform ticket issuing (printing) processing of ticket issuing data corresponding to the input reservation number (S12).
7). Then, when the user issues the ticket printing process for the next ticket data, the user returns to the process of S124 again to perform the ticket printing process for the next ticket data, and does not perform the ticket printing process for the next ticket data. Closes the screen of the WEB browser 61 and terminates the program of the WEB browser 61 (S128).

20 to 22 show the details of the ticket issuing process in S127. With reference to these figures, coupon ticket 7
If various troubles occur during the printing process of No. 5, issue D
The state of the ticket issuing flag on the B server 14 side will be described. When the user selects and clicks the ticketing button 82 on which the reservation number of the ticketing data to be printed is displayed on the ticketing status list screen 81 (S131).
The ticket issuing ActiveX 63 of the terminal 17 downloads all print data corresponding to the reservation number selected from the ticket issuing DB 60 on the ticket issuing DB server 14 via the WEB browser 61 and the ticket issuing data list display ASP 54 on the WEB server 13. S132). At this time, ticketing ActiveX63
If the print data acquisition from the ticket issuing DB 60 fails, an error dialog indicating that the print data acquisition failed is displayed on the monitor of the terminal 17 (S13).
8) If the print data corresponding to the selected reservation number does not exist in the ticket issuing DB 60, a dialog indicating that there is no corresponding print data is displayed on the monitor of the terminal 17 (S140).

If the corresponding print data exists in the process of S132 and the corresponding print data can be downloaded, the ticket issuing ActiveX 63 determines that the print data of the platen serial number "*****" is included in the downloaded print data. Is checked (S13)
3). This is because the host / FEP 11 completes the transfer of all print data corresponding to the reservation number that is the target of ticket printing to the ticket issuing DB 60 on the ticket issuing DB server 14, and then creates the corresponding reservation number separately from the original print data. This is because the print data of the corresponding platen serial number "*****" is stored in the ticket issuing DB 60. Therefore, ticketing DB
Platen serial number "**" corresponding to the corresponding reservation number in 60
If there is no print data for "**", issue ticket Ac
The tiveX 63 judges that the transfer of all print data corresponding to the corresponding reservation number from the host / FEP 11 to the ticket issuing DB 60 has not been completed, and displays a dialog indicating that there is no corresponding print data on the monitor of the terminal 17. It is displayed (S140). On the other hand, in S133, the platen serial number "*" is included in the print data corresponding to the corresponding reservation number.
If the print data of "***" exists, it is checked whether or not the print data of which the ticket issuing flag is "waiting for ticket issuing" exists in the print data corresponding to the reservation number (S134). And ticketing ActiveX63,
If there is no print data waiting for ticketing,
A dialog is displayed on the monitor of the terminal 17 to notify that the corresponding print data has already been issued or is being issued (S141). On the other hand, if the print data corresponding to the reservation number includes print data whose ticket issuing flag is "waiting for ticket issue", the ticket issuing Acti
The veX63 extracts print data whose ticket issuing flag is "waiting for ticket issuing" (S135), and the WEB browser 61 and the WEB.
Ticketing D on the ticketing DB server 14 via the server 13
The ticket issuing flag of the corresponding print data in B60 is changed to "ticket issuing" (S136). Ticketing ActiveX63,
When the change of the ticket issuing flag is unsuccessful, a dialog indicating that the contents of the ticket issuing DB 60 cannot be changed is displayed on the monitor of the terminal 17 (S142). When the user presses the confirmation OK button on the dialog displayed in the processes of S138, S140, S141, and S142, the ticket issuing ActiveX 63 displays the ticket issuing status screen 81 (S139). , S143).

In the process of S136, the ticket issuing DB 6
If the ticketing flag of the corresponding print data in 0 is successfully changed to "Ticketing", ticketing ActiveX
63 retrieves the corresponding print data from the ticket issuing DB 60 again (S137), and opens the file for socket communication with the ticket issuing module 98 (S14).
4). When the opening is successful, the corresponding print data is transmitted to the ticket issuing module 98 (S1
45) If the print data is successfully transmitted, the ticket issuing result message is received (S146). Then, when the ticket issuing ActiveX 63 succeeds in receiving the ticket issuing result message from the ticket issuing module 98, it closes the file for socket communication (S147). Above S
If the opening of the socket communication file fails in the process of 144, the ticket issuing ActiveX 63 determines in S14.
The process proceeds to step 9 to perform processing when the socket communication is abnormal. Also,
In the processing of S145 and S146, if a socket communication disconnection, a timeout, etc. occur, the ticket issuing Active
The X63 closes the file for socket communication (S148), then proceeds to the processing of S149, and performs processing when the socket communication is abnormal. Then, after outputting the log information when the socket communication error occurs from the printer of the terminal 17 (S
149), on the monitor of the terminal 17, a dialog indicating that the error content and the need to restart is displayed (S15).
0). On the other hand, when the user presses the restart button of the terminal 17, the OS 62 of the terminal 17 shown in FIG.
The restart module stored in the terminal 17 is started (S151). As a result, the terminal 17 is restarted (S
152).

When all the socket communication processes of S144 to S147 have been normally completed, the ticket issuing ActiveX 63
Checks the message type code in the ticket issuing result message 100 received from the ticket issuing module 98 (S
153). If the message type code is “CB”, it is determined that the coupon ticket is issued successfully (print data output is completed), and the ticket issuing DB is issued.
The ticket issuing flag of the corresponding print data in the ticket issuing DB 60 on the server 14 is changed to "ticket issued" (S154).
If the ticket issuing ActiveX 63 fails to change the ticket issuing flag, the ticket issuing ActiveX 63 proceeds to the error process shown in FIG. 22. If the ticket issuing flag is successfully changed, the ticket issuing ActiveX 63 prints the print data corresponding to the reservation number. It is checked whether or not there is print data that has not been issued (unsent to the ticket issuing module 98). Then, if such print data exists, the process returns to S137 to perform the output process of the next print data.
Display the ticket issuing status list screen 81 again (S156),
It returns to the processing of S131.

In the process of determining the message type code in the ticket issuing result message 100 in S153,
If the type code is "CC", ticketing ActiveX
Reference numeral 63 determines that an error has occurred in the ticket issuing processing by the ticket issuing module 98, and the output of print data is in an incomplete state, and performs the error processing shown in FIG.
If the type code is “CE”, it is determined that an unrecoverable error has occurred in the ticket issuing processing by the ticket issuing module 98, and the process proceeds to S162 in FIG.

Next, the processing when the ticket issuing result shown in FIG. 21 is an error will be described. Ticketing ActiveX63
Determines the serial number status in the ticket issuing result message 100 (S157), and if the serial number status is "5", determines that an error (sense NG) due to a line failure or the like has occurred, and issues the ticket issuing result. The detailed status END code in the message 100 is determined (S158). If this code is an error that can be reissued such as "2" (busy), "4" (intervention request), "6" (LAN failure / power off), "10" (command execution impossible) Displays a dialog to the effect that it is necessary to check the error content and printer on the monitor of the terminal 17 (S
159). If the user clicks the OK button in this dialog, the ticket issuing ActiveX 63 will be shown in FIG.
Returning to the processing of S137, the reissue ticket of the same print data is issued. On the other hand, when the user clicks the cancel button, in order to cancel the ticket issuing process for the corresponding print data, the ticket issuing flag is set to "ticket issuing" from the print data in the ticket issuing DB 60 extracted in the process of S135. Only for the print data of “”, the ticket issuing flag of these print data is changed to “waiting for ticket issuing” (S160). Then, the ActiveX 63 executes the error processing shown in FIG. 22 when the change of the ticket issuing flag fails, and displays the ticket issue status screen 81 when the change of the ticket issuing flag succeeds. (S161),
It returns to the processing of S131.

On the other hand, the detailed status END code in the ticket issuing result message 100 in the determination processing of S158 is a reissue ticket such as "1" (command reject), "3" (data error), "5" (alarm). If the error is impossible, the ActiveX 63 changes the ticket issuing flag of the corresponding print data to "error" (S16).
2). If the change process is successful, the printer of the terminal 17 outputs the log information when the error occurs (S163), and then the error content and the monitoring center need to be notified on the monitor of the terminal 17. Is displayed (S164). If the user clicks the OK button on this dialog, the ticket issuing ActiveX 63 displays the ticket issuing status screen 81 (S165),
It returns to the processing of S131. Further, in the ticket issuing flag changing process of S162, if the ticket issuing flag changing fails, the error process shown in FIG. 22 is executed.

On the other hand, if the serial number status in the ticket issuing result message 100 is "7" in the determination processing of S157, the ActiveX 63 causes an editing error (a type of non-reissue ticket error) during the ticket issuing processing. Is determined to have occurred, and the same processing as S162 to S165 described above is performed.

If the serial number status in the ticket issuing result message 100 is "6" in the determination processing of S157, the ActiveX 63 is in an uncertain state as to whether or not the output of the corresponding coupon ticket is completed. After making a determination (S166) to change the ticket issuing flag of the corresponding print data to "undefined", the above-mentioned steps S163 to S165 are performed.
The same processing is performed (S167 to S169).

Next, the error processing shown in FIG. 22 will be described. When the process of changing the ticket issuing flag shown in (B) of FIG. 20 and (C) to (E) of FIG. 21 fails, the ActiveX 63 enters this error process and the printer of the terminal 17 logs when an error occurs. After outputting the information (S
170), error content and ticket issuing D on the monitor of the terminal 17
A dialog indicating that the ticket issuing flag in B60 cannot be changed is displayed (S171). Ticketing ActiveX63, when the user clicks the OK button in this dialog,
The ticketing status list screen 81 is displayed (S172), and FIG.
Proceed to the processing of S131.

23 and 24 show management information of the ticket issuing state on the terminal 17 side and the ticket issuing DB server 14 side, respectively. The management information on the ticket issuing DB server 14 side shown in FIG. 24 means the ticket issuing flag of the print data in the ticket issuing DB 60. Further, by holding the management information of the ticket issuing state as shown in FIG. 23 on the terminal 17 side from the start to the end of the ticket issuing print process, even if an error occurs during the ticket issuing print process, the ActiveX 63 The degree of error that has occurred can be determined based on the management information of the ticket issuing state on the terminal 17 side, and the subsequent processing can be changed according to the degree of error. As a result, when the degree of error is minor (for example, S158 in FIG. 21).
When such an error occurs), the print data can be automatically reissued.

The present invention is not limited to the above embodiment, but various modifications can be made. For example, in the above embodiment, the host system G / W 12, WE
Although three servers, the B server 13 and the ticket issuing DB server 14, are arranged, one server may be arranged in the center side system 7, and this server may also have the functions of each server in the above-described embodiment. Further, in the above embodiment, the check of the ticketing limit amount in each store is performed based on the total issue amount of money in each store within a month, but this check is performed based on, for example, the quarterly issue amount in each store. You can go.

[0059]

As described above, according to the invention of claim 1 ,
The program for controlling the ticketing screen is
When the server's ticketing instruction is accepted,
Refer to the ticketing status management information in the ticketing data
Indicates that the management information is uncertain whether a ticket has been output
If the content is "undefined", it corresponds to the ticketing data.
The output of the specified print data is not allowed . As a result, it is possible to prevent the double ticketing.

[0060]

[0061]

[0062]

[0063]

[0064]

[Brief description of drawings]

FIG. 1 is a configuration diagram of a travel product reservation ticket issuing system for a travel agency according to an embodiment of the present invention.

FIG. 2 is a hardware configuration diagram of a ticket issuing DB server and a ticket issuing machine control terminal in the above system.

FIG. 3 is a software configuration diagram of three types of servers and a ticket issuing machine control terminal in the above system.

FIG. 4 is a diagram showing an outline of processing from reservation to printing of a coupon ticket in the system.

FIG. 5 is a flowchart of a travel product reservation process in the above system.

FIG. 6 is a flowchart of ticket issuing instruction processing in the above system.

FIG. 7 is a flowchart of a reservation content change process in the above system.

FIG. 8 is a flowchart of a modified ticket issuing process in the above system.

FIG. 9 is a flowchart of cancellation processing in the above system.

FIG. 10 is a flowchart of reissue ticket processing in the above system.

FIG. 11 is an explanatory diagram of specifications of a ticketing status list screen in the above system.

FIG. 12 is a diagram showing a format of a ticketing status list screen in the above system.

FIG. 13 is a diagram showing a format of an error content display screen in the above system.

FIG. 14 is a diagram showing a message during ticketing in the system.

FIG. 15 is an explanatory diagram of a process for enabling re-output of the ticket issuing data in which the ticket issuing flag is “indeterminate” in the above system.

FIG. 16 is a diagram showing a format of a status change ticketing status list screen in the above system.

FIG. 17 is a diagram showing a status change screen in the above system.

FIG. 18 is an explanatory diagram of communication abnormality between the ticket issuing ActiveX and the ticket issuing module in the ticket issuing machine control terminal in the system.

FIG. 19 is an overall flowchart of print ticket issuing processing performed on the ticket issuing machine control terminal side.

FIG. 20 is a flowchart of detailed processing of ticket issuing processing in the ticket issuing machine control terminal.

FIG. 21 is a flowchart of processing when a ticket issuing error occurs in the ticket issuing machine control terminal.

FIG. 22 is a flowchart of error processing when the ticket issuing flag is changed in the ticket issuing machine control terminal.

FIG. 23 is a diagram showing management information of a ticket issuing state on the ticket issuing machine control terminal side.

FIG. 24 is a diagram showing the contents of a ticket issuing flag on the ticket issuing DB server side in the system.

[Explanation of symbols]

1 Travel product reservation ticketing system for travel agents 3 Internet lines 11 Host FEP (Host computer) 12 Host G / W 13 WEB server 14 Ticketing DB server 17 Ticketing machine control terminal (terminal) 18 ticket issuing device 60 Ticketing DB (database) 89 Status change screen (change means)

─────────────────────────────────────────────────── ─── Continuation of front page (56) References JP-A-5-266048 (JP, A) JP-A-4-149691 (JP, A) JP-A-2001-123203 (JP, A) International Publication 99/03029 ( WO, A1) Nobuyuki Oshima, 1 new information system in Hitachi's network era-New information system utilizing distributed object technology, Hitachi Review, May 1, 1998, Volume 80, No. 5, p. ． 4-8 (58) Fields surveyed (Int.Cl. ⁷ , DB name) G06F 17/00 G07B 1 / 00,5 / 00

Claims (2)

(57) [Claims] 1. A host computer for managing reservations for travel products.
Computer (hereinafter referred to as "host") and the host
Connected server, said server and internet line
With a terminal that can communicate via
A travel product reservation system for travel agents, Connected to the terminal and sent from the terminalPrint data
Equipped with a ticket issuing device that prints In addition to managing travel product reservations, the host also manages ticketing
Based on instructions from the terminal via the server.
Create ticket issuing data and send it to the server, The server sends this ticketing data to the database in the server.
Accumulated in the The terminal isFrom the userWhen you receive the ticketing instruction,
The database in the server is connected via the internet line.
Read ticketing data fromBased on this ticketing data
Print data editedSent to the ticket issuing device, Ticketing data stored in the server and read by the terminal
The ticketing data included in the ticketing data will be included in each ticketing data.
State management information is included, The terminal, according to the result of printing by the ticket issuing device,
Update the management information of ticket issuing status on the terminal side and the server side.
new, The server isIn response to the instruction from the terminal, the server
Among the ticketing data on the B side, the ticketing status management information is being issued
About ticketing dataTicketing status management information
To,According to the ticketing status management information on the terminal sideReChange
With the newThe terminal has a program for controlling the ticket issuing screen and a ticket issuing device.
And a program for position control, The program for controlling the ticket issuing device controls the ticket issuing screen.
About print data sent from your program
The ticketing result message is displayed on the ticketing screen control program.
Return to Ram, The program for controlling the ticket issuing device is issued by the user.
The ticket issuing device after receiving a ticket issuing instruction of ticket issuing data
Printing when a communication line failure has occurred between the terminal and the terminal
It is uncertain whether or not a ticket is output when the processing ends abnormally.
The state of Issuing a message indicating the ticketing result indicating
Return to the program for controlling the ticket screen, The program for controlling the ticket issuing screen is in the indefinite state.
When the message of ticketing result indicating that is
The relevant ticket issuing device on the terminal side and the server side.
Whether the ticket was output or not
Rewrite to the content of "indefinite" to indicate that it is constant, The program for controlling the ticketing screen is issued by the user.
When the data ticketing instruction is accepted, the server side
Refer to the ticketing status management information of the ticketing data
If this management information has "undefined" content,
The output of print data corresponding to the ticket issuing data
The travel product reservation system for travel agencies characterized by the above
Stem. 2. The terminal is connected via an internet line
Ticketing data read from the database in the server
Is encrypted, claim 1
Travel products reservation system for the travel agents.