婴儿出票（Baby ticket）.docVIP

婴儿出票（Baby ticket） Common problems with operating instructions for airline baby tickets 2010-08-15 11:04:49| classification: classification | name default subscription Airlines requiring agents to issue their own baby tickets are: CZ, CA, SC, ZH, MU, 3U, FM, MF, EU, HU (infant tickets must be issued with adult counterparts, not at the airport counter to fill the baby ticket) Whats the usual procedure for getting a baby ticket?: First, the adult ticket comes out with the baby ticket. 1, reservation: AV, SD, adult NM, adult contact group C, documents, FC, FN, FP and other information input 2. Enter the name for the baby: XN:IN/ baby name INF (birth month, year) /PN Example: XN:IN/ Li Li INF (MAR07) /P1 *PN indicates the N adult followed by the baby Next, enter SSR INFT...... The application order. 3, sealing. 4, again mention coding, at this time, SSR INFT item NN1 into KK1, with PAT:A*IN for infant input freight rates FC, FN, FP items 5, ETDZ tickets, adult tickets and baby tickets came out together. Two, adult ticket already finished, make up the baby ticket. 1, the extraction of adult ticket code, for the baby to enter the name XN:IN/, baby name INF (birth month, year) /PN, and then enter SSR INFT item, seal @. 2, re encoding, see the SSR INFT item of NN change KK. Cancel your adult price, FN, FC, and then enter the baby ticket at PAT:A*IN. 3, ETDZ: ticket machine, INF. Just get out the baby ticket. Some agents follow the steps of the babys papers, but they still cant get tickets. Then we must carefully check your input instruction is not a problem or a ticket which links operating out of the question. The problems that are common to the agents when they give birth to babies are summarized as follows: 1, baby name input. Command: XN IN/ INF (a month of birth year) between /PN XN and IN in this directive is best to use spacebar to replace the original baby name here:; when the input is Chinese; after INF month of birth year as long as the input months and years, atte