You can pass train booking to the global distribution system (GDS) for air rail travel using passive segments. A passive segment is a set of trip information entered into the GDS that does not cause a ticket to be issued by the GDS. For example, a traveler may be taking a train between cities, and although you do not use the GDS to issue the train ticket, you may want all of the trip information to be in one place for the traveler's benefit, and so that agents can generate itineraries or make notes. By default, no information is saved in the GDS unless you decide to enable passive segments.
Processing a passive segment requires knowledge of JavaScript. In addition, you must enable passive segments as described in Adding or Changing Agency Settings.
If passive segments are enabled, the default documentation will be added to the R-field of the PNR. These remarks cannot be masked or modified.
The following are examples of the default remarks when passive segments are enabled:
5R‡RC RAIL BOOKING
5R‡AMTRAK REC LOC A1B2C3
...
The following shows how passive segments are passed to the GDS. PNR Remark Documentation is found on the Custom PNR Editor Script Samples for Train Service page.
The last column provides a breakdown of each portion of the example. At this time, Sabre, Worldspan and Apollo passive segments are supported.
Note: Amadeus functionality does not currently support GDS write back of rail segments. If rail is enabled on an Amadeus site, the reservation is only viewable online; no GDS PNR is created.
GDS | Segment Example | Breakdown |
Sabre |
|
|
Apollo |
|
|
Worldspan |
|
|