Automatic association of transfer baggage on connection segments
Data on the availability of transfer passenger baggage is added to the check-in system from a BTM telegram if the first segment of a route of a passenger was serviced not in DCS Amber or, on the basis of the check-in system if the route of the passenger is fully checked in within DCS Amber.
The automatic association of transfer baggage with a passenger in DCS Amber is carried out during check-in of the passenger on a connection segment.
After selecting a passenger /group of passengers, it is required to click Check-in/F9 (the availability of transfer baggage of the passenger/group of passengers is checked at this moment). If there is some transfer baggage, then the Inbound transfer baggage window will be presented.
The example presents one passenger:
The window contains information about baggage: from which flight the baggage is (an airline code, a flight number and its route), a number of baggage pieces and bag tags. The agent should click Continue/F9. After that, the baggage will be associated with the passenger automatically and the passenger will be checked in.
The example presents a group of passengers:
If a passenger/group of passengers has no transfer baggage, then when clicking Check-in /F9, the passenger will be checked in and the bottom part of the window will be opened. It is possible to enter information on baggage and hand luggage in this area.
Resolving conflict situations when associating transfer baggage
Duplicating data of passengers on inbound flights
The given conflict occurs if information on inbound transfer contains two passengers with the same surnames.
To resolve the conflict, it is required:
1. To specify which baggage belongs to the passenger who is passing check-in.
2. In the row containing a number of a bag tag belonging to the passenger, specify YES in the Reg column by pressing the Space key.
3. To specify No in the row with a number of a bag tag not belonging to the passenger by pressing the Space key.
4. Click Continue/F9.
The system controls a number of the confirmed baggage.
If the agent confirms a number of baggage pieces which is more than belongs to the passenger, then the system will present the notification. In this case, a new confirmation will be required.
Duplicating data of passengers on outbound flights
The given conflict occurs if the passenger list of a transfer flight contains two passengers with the same full names.
To resolve the conflict, it is required:
- To specify whether the baggage belongs to the passenger who is passing checkin.
- In the row containing a number of a bag tag of the passenger, in the Reg column, specify YES if the baggage belongs to the passenger or NO if it does not belongs to the passenger by pressing the Space key.
- Click Continue /F9.
Different routes of inbound transfer
The given conflict occurs if a group of passengers with different transfer baggage routes is passing check-in:
MOWKB1H
.DMEKB1H 150945
BTM
.V/1TVOZ
.I/СУ111/16APR/DME
.F/YQ222/16APR/ULY/Y
.N/0342054633001
.W/K/1/15/10
.O/YQ333/16APR/AER/Y
.P/VOKOLOVA/ANNA
.N/0342054633001
.W/K/1/15/10
.O/YQ333/16APR/СУР/Y
.P/FOKOLOVA/ANNA
ENDBTM
To resolve the conflict, it is required either to confirm the check-in of the transfer baggage (YES) or refuse (NO). Click Continue /F9.
Different transfer routes of inbound baggage and a checked group
The given conflict occurs if a further transfer route of a passenger/group of passengers differs from a transfer route of his/her baggage:
MOWKB1H
.DMEKB1H 150939
BTM
.V/1TVOZ
.I/СУ111/16APR/DME
.F/YQ222/16APR/ULY/Y
.N/0342054633001
.W/K/1/15/10
.O/YQ333/16APR/AER/Y
.P/SOKOLOVA/ANNA
ENDBTM
The route of the transfer baggage is to AER in the BTM telegram but in the "Passenger check-in" module, the СУР destination point is specified in the connection flight of the passenger.
To resolve the conflict, it is required either to confirm the check-in of the transfer baggage (YES) or refuse (NO). Click Continue/F9.
Unknown weight of transfer baggage
The given conflict occurs if a BTM telegram in which there is no .W element (data on baggage) came:
MOWKB1H
.DMEKB1H 111359
BTM
.V/1TVOZ
.I/ЮТ111/12APR/DME
.F/YQ222/12APR/УЛК/Y
.N/0342054632501
.P/MOSIN/ANDREY
ENDBTM
To resolve the conflict, it is required to confirm data by clicking Confirm/Enter, specify weight of baggage in the column and click Continue/F9.
The notification "Unassociated transfer baggage" is added. If at least one piece of baggage is not associated, then the notification is appeared from the beginning of the Check-in closing step. If all transfer baggage was associated during the check-in, then the notification is not appeared.
See also:
- Working with the module
- Monitoring of passenger check-in. List of checked in passengers
- Unaccompanied baggage
- Check-in closing and flight documentation printing
- Through check-in
- Check-in of passengers with PNR ID1/2, RG1/2,DG1/2, WL statuses
- Check-in for codeshare flights in DCS Amber
- Input of passport data to form APIS telegram
- Working with EMD in the "passenger Check-in" module
- Check-in of a crew in the "passenger Check-in" module
- Appendix 1. Ways of describing baggage NORMS
- Appendix 2. Check-in request format
Other sections:
- Boarding module
- Seasonal Schedule Management Module
- Check-in Preparation Module
- Documentation module
- Statistics module
- History module
- EMDA Module
- Messages Module
- Access Module
- Baggage Payment Module
- Transportation Module
- Weight and Balance Module
- Web Check-in at a Cost Service
- Alarms Designations
- Self Check-in Kiosk Software
- Administration module