smith80678

Married Segments" have to do with inventory on connecting flights being different on the origin to destination than on the individual legs.

Introduction
Married Segment Logic allows participating airlines to control inventory on a trip or related segment basis. When air segments are booked, a marriage is established by the airlines between two or more segments, requiring them to be processed as a unit.

When air segments are booked, if the airlines chooses to marry the segments, marriage indicators are appended to the segments to identify them as a single unit:



Marriage Indicator Explanation
J Married segment indicator

01-99 Two-digit marriage number



Example - Married Indicators

1 NW1062Y 15SEP MO MCIMSP HK1 400P 516P/O J01 E
2 NW 355Y 15SEP MO MSPSFO HK1 625P 831P/X J01 E

The two-digit number is assigned sequentially as marriages are booked. This number identifies segments that are married to each other. Since segments might not be sold in order, it is possible to have numbers that are not sequential while updating the PNR. Upon End Transaction (ET) the marriages are renumbered sequentially.

When the Worldspan Direct Access link is not available, airlines advise via teletype messages of new or changed married segments. Worldspan® places the PNRs involved on Q102 category 3. This queue is reserved for additions, changes and/or deletions to married segments.

If individually sold segments are not married, the airlines marries the segments after ET. If this occurs, the PNR is queued to Q102 category 3.

If a claim PNR airline participant also participates in married segment logic, marriage indicators are returned in the transfer claim responses. The PNR is updated to reflect the indicators once it is created in Worldspan.

If a waitlist segment clears and the cleared segment is replacing one or more segments in a marriage, the following cancel/change segment status entry must be used: X2#.1HK. This entry notifies the airlines you are replacing the married segment with a cleared waitlisted segment. Once the entry is made, the airline remarries the remaining segments and assigns the next available indicator or deletes the marriage and removes the indicators from the PNR. If the airline remarries the segment, the next available marriage indicator is assigned. Upon ET all married segments are renumbered sequentially.

top of page


Display Married Segments
The two options listed in the table below displays Married Segments.


Explanation Entry
Displays all marriages in a PNR
*IJ
Displays all marriages for a specific airline in a PNR
*IJ-CC (CC = airline code)



The error response NO MARRIED SEGMENTS displays if no Married Segments exist in the PNR or the requested airline is not a Married Segment participant.

When a Married Segment is added to or canceled from a PNR, history includes the Married Segment indicator.

NOTE: NW can manually create or delete a marriage which shows in history with the
following history codes:

NJ - New Married Segment
DJ - Delete Married Segment
Any existing Married Segment that is being married to or deleted from contains the history code of:

EJ - Existing Married Segment
top of page


Documentation Restrictions
Segment select will not be allowed on part of a marriage when issuing a ticket. When issuing other documents like Itinerary/Invoice and credit memos, the system will not try to price the segment that is being separated from the Marriage. The @B option must be included in the entry or the following error response will be displayed.


MARRIED SEGMENT 1 - USE @B TO PRINT AIRFARE

When adding the NU option to an EZI entry, the fare stored in the Ticketing Record is shipped to the interface system. If segment selection of a portion of a Married Segment is included in the entry, the same error response above will be displayed.
Married Segment restrictions will not apply to MCO documentation since a @B option must always be included.
EZP, EZD, EZN, and EZB will not be affected by Married Segment Logic.
4A entries will not be affected by Married Segment Logic.


top of page


History of Married Segments
There are several history codes related to Married Segments:


NJ - New Married Segment

DJ - Deleted/Canceled Married Segment

EJ - Existing Married Segment
When a Married Segment is added to or canceled from a PNR the history includes the Married Segment Indicator.


XS NW459Y 15AUG MSPMEM HK1 445P 647P J01
AS NW515Y 15AUG MSPMEM HK1 450P 651P J01

Participating airlines may create or modify a marriage via a teletype message at anytime without taking any inventory type action on the segment. A host airline can manually create or delete a marriage that shows in history with the following history codes.


NJ NW1576Y 23FEB SU MCIDTW HK1 435P 720P/O J01
DJ NW1576Y 23FEB SU MCIDTW HK1 435P 720P/O J01


History Codes Explanation
NJ
New Married Segment

DJ
Delete a Married Segment


Any existing Married Segments that the segment is being married to or deleted from contains the history code of EJ.


NJ NW 1527Y 15AUG FR MSNMSP HK1 245P 247P J01
EJ NW 459Y 15AUG FR MSPMEM HK1 445P 647P J01
EJ NW 661Y 15AUG FR MEMPHX HK1 750P 922P J01


History Codes Explanation
EJ
Existing Married Segment


Below is an example of how history will appear after a partial cancellation. Segment three of this itinerary was canceled and the PNR ended.


1 AA 61Q 30NOV SU MCODFW SS2 754A 955A/O $
2 AA 395Q 30NOV SU DFWSEA SS2 1050A 128P/O $
3 NW 958H 05DEC FR MEMMCO SS2 825P 1120P/X E

Notice that there is no longer a marriage indicator on NW958.

Entry: *HF


R-1P P/
CKC SU DB 1819Z/28JUL97
XS NW 988H 05DEC SEAMEM HK2 100P 700P J01 E
DJ NW 958H 05DEC MEMMCO HK2 825P 1120P J01 E
R-P/ -CR- CKC/1P SU dB 28JUL97 1853Z FEF78D ***
AS AA 61Q 30NOV MCODFW SS2 754A 955A $
AS AA 395Q 30NOV DFWSEA SS2 1050A 128P $
AS NW 988H 05DEC SEAMEM SS2 100P 700P J01 E
AS NW 958H 05DEC MEMMCO SS2 825P 1120P J01 E
RP/ -CR- CKC/1P SU dB 28JUL97 1819Z FEF78D ***

History indicates that NW988 was completely canceled, which divorced the two NW segments. Therefore, the history code of DJ for NW958 appears in history to account for the removal of the J01 marriage indicator from that segment.

History also updates with any marriages or divorces that are initiated by the airline.

Guidelines:


Each airline is given the opportunity to customize the program to their needs. Therefore, the policy for each airline should be access for detailed processing information.


Since segments can be added to a PNR in any order, the marriage numbers may not appear sequentially; upon End Transaction (ET) the marriages are renumbered.


Ticketing/Pricing is inhibited if only a portion of the marriage is selected.


Queue 102, category 3 is used for airline updates to the married segments.
top of page


Married Segment Indicators
Indicators are appended to two or more itinerary segments that are to be treated as a single unit. A two digit numeric follows the J (Marriage Indicator) to indicate the number of the marriage in the PNR. Up to 99 marriages can appear in a PNR.


Indicators Explanation
J
Married (joined) Segment Indicator

01
Marriage number, a two digit numeric up to 99



Example - Married Segment Indicators

1 AA 61Q 30NOV SU MCODFW SS2 754A 955A/O $
2 AA 395Q 30NOV SU DFWSEA SS2 1050A 128P/O $
3 NW 988H 05DEC FR SEAMEM SS2 100P 700P/O J01 E
4 NW 958H 05DEC FR MEMMCO SS2 825P 1120P/X J01 E

In the above itinerary, the J represents a marriage and the 01 indicates the marriage number. Therefore, segments 3 and 4 are processed as a unit and can be inhibited from being canceled separately.


top of page


Married Segment Logic Guidelines
The guidelines for Married Segment Logic includes:

Segments sold individually are not married, but the airline can marry the segment after End Transaction. In this case, the PNR is queued to Q102/C3.


Waitlisted and confirmed segments can be married, at the airlines discretion.


If more than 99 marriages have been added or deleted in the same transaction, a warning message appears.


Participating airlines can create or modify marriages at any time without changing the status of the segment.


Married Segments between different airlines are not be supported.


The User Update Table provides a list of all airlines participating in Married Segment Logic. The entry to see this table is KRM*.


Married Segment Logic does not apply to Code Share Flights.


Married Segment Logic does not apply to Worldspan WorldGroup® segments.
top of page


Married Segment Queue Processing
Participating airlines may send a message to establish a new marriage or delete an existing marriage. Next, Worldspan places the PNR on the customers Q102/C3. This queue is reserved for additions, changes/deletions to Married Segments.




top of page


Pricing Married Segments
Segment select for pricing, including agent assisted, Low Fare Finder, Power and SecuRate pricing is allowed when a portion of a marriage is selected. Any segment select pricing entry on a Married Segment produces a price display with an advisory message indicating the display is for informational purposes only and not valid for storing or ticketing.

Segment select pricing on Married Segments does not apply to entries used to rebook, store fares or issue tickets.

When adding the #NU (no update - interface only) option to an EZI entry, the fare stored in the Ticket Record is sent to the interface system. If segment selection of a portion of a Married Segment is included in the entry, the following error response is displayed:

MARRIED SEGMENT 1 - SEGMENT SELECT NOT ALLOWED

Married Segment restrictions does not apply to MCO documentation since @B option must always be included

EZP, EZD, EZN and EZB is not affected by Married Segment logic.

top of page