Cat3 - Seasonality
In order to validate the Seasonality Category, it is essential to know the following:
Departure/arrival date for all flights within the fare component, pricing unit and journey. (The inclusion of a Travel Segment Indicator (TSI) and the setting of the Assumption Override Tag in this category can modify the application of the assumption from departure of the originating flight of the pricing unit to the departure of the originating flight of the fare component or journey).
It is important to know whether each portion is Outbound or Inbound, this is especially important when selecting a TSI
Review all fare break points within the pricing unit and measure each of those points from the point of origin of the pricing unit to determine the furthest geographical fare break point (point of turnaround).
Outbound = All fare components within the pricing unit prior to the furthest geographical fare break point.
Inbound = All fare components within the pricing unit after the furthest geographical fare break point are considered Inbound.
All fare components within the pricing unit that are selected in the opposite direction of the passenger's travel is INBOUND travel”
Assumptions
In the absence of Category 3 (Record 2 does not exist, or no Record is applicable), the system assumption is that there are no seasonal date(s) restrictions that apply for the fare.
When the Seasonality Category is applicable, the assumption is:
-
“The date of departure of the originating flight of the pricing unit’ determines the seasonality of the fare component being validated.”
Please check category 3 data application “2.2 Assumptions” for further details in https://my.atpco.net/system/files?file=document_nodes/2021-06/Cat3_dapp_C.pdf.
Why is Seasonal Application not applying correct seasons when coded for "each" segment?
Category 3 - Seasonal Application defaults to a pricing unit.
This can be overridden with the use of a fare component TSI such as TSI 3 - "Each Trip" however you must also code the override tag.