Introduction
4CHLD* command is now made available to automatically generate the SSR CHLD associated with the corresponding passenger in the PNR and thus inform other airlines on the itinerary of the existence of minors in the reservation.
This implementation does not change the current way of entering minors in the name field, which must be added with the command: -SURNAME/FIRST NAME CHD
4CHLD* Command - Manual Entry
In a PNR with 1 or more CHD passengers, the SSRs can be entered manually.
When there is only 1 CHD passenger:
4CHLD* |
|---|
When there is more than 1 passenger CHD in the PNR, these must be entered individually:
4CHLD*/P2 | SSR CHD is entered to passenger 2 |
|---|
Otherwise it will return error:
The command checks:
The passenger must have a DOB loaded in the name field in SSR DOCS, otherwise the command returns the error INVALID DATE OF BIRTH
The SSR cannot be duplicated / entered twice for same passenger.
Behavior when manually adding 4CHLD*
Associating SSR 4CHLD to passenger ADT
If an SSR CHLD is associated to an ADT passenger, the system changes the passenger type to CHD, in the name field of that passenger.
As the passenger change process has many possible actions associated with it ( fare deletion, ssr removals, disassociation of tickets), the system returns a warning message when the SSR is added with command 4 or when 4CHLD* is used
PASSENGER NAME MODIFIED - SSRS/SEATS/FARE MAY BE DELETED AND TKTS/EMDS DISASSOCIATED |
|---|
Example:
SSR 4CHLD Removal
When a SSR CHLD is deleted in the PNR, the system changes the corresponding associated passenger type to *ADT. As the passenger change process has many possible actions associated with it ( faredeletion, ssr removals, disassociation of tickets, etc.), the system returns a warning message when the SSR is added with command 4 or when 4CHLD* is used:
PASSENGER NAME MODIFIED - SSRS/SEATS/FARE MAY BE DELETED AND TKTS/EMDS DISASSOCIATED |
|---|
Example:
Attempt to associate SSR 4CHLD to other PTCs (SRC, STU, MIL)
The SSR CHLD cannot be associated with other PTCs such as SRC (Senior Citizen), STU (Stundent), MIL (Military) among others.
Example:
Attempt to associate SSR 4CHLD to other PTCs (SRC, STU, MIL)
SSR 4CHLD entry control in PNR (JJAIR)
The JJAIR table can be set up so that, when CHD passengers are added to the PNR name field, after ending the reservation with E or ER, the system autogenerates and adds the corresponding CHLD SSR to each traveler.
The option that controls this set up in JJAIR Table is [AGC] Autogenerate Child SSR
This configuration only applies to HOST at this moment.
JJAIR set ups are done by KIU Support.
The options are the following:
JJAIR Option AGC with value “YES” | Autogeneration of 4CHLD SSR on PNR Active |
|---|
JJAIR Option AGC with value “NO” | Autogeneration of 4CHLD SSR on PNR Inactive |
|---|
In order to succesufully autogenerate the 4CHLD SSR, the DOB (Date of Birth) of the passenger must be included in the name field or as DOCS SSR, otherwise the process will be ignored and the SSRs will not be added.
4CHLD SSR control upon Ticketing (JJETKT)
Additionally, a control can be set up in the JJETKT table to prevent ticketing from happeing in the absence of 4CHLD SSRs.
Once the 4CHLD SSRs are addede to the corresponding passengers of the reservation, tickets can be issued.
The option that controls this set up is [CSR] - Child SSR Control
This configuration can be applied to HOST and / or Agency.Environments.
The JJETKT set ups must be requested to KIU Support.
Set Up Options: :
JJETKT Option CSR Value “H” | 4CHLD SSR Control at Ticketing Active for HOST only |
|---|---|
JJETKT Option CSR Value “HA” | 4CHLD SSR Control at Ticketing Active for HOST and Agency |
JJETKT Option CSR Value “N” | 4CHLD SSR Control Inactive |
Example of Ticket Issue:
Attempt to issue ticket when no SSR CHLD in PNR and Token CSR on JJETKT is active: (tickets are not issued)
If SSRs are added, tickets may be issued:
