The Change Segment Task changes the segment description.
Transaction Name:
PNRBFManagement_32
Can any other transaction perform this same task?
Previous versions of PNRBFManagement, PNRBFBuildModify, and AirChangeSegmentStatus transactions can also perform this task.
Can this task be performed in a sessionless environment?
No.
Are the request and response identical on both the Apollo and Galileo systems?
Yes.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
Not applicable.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
You can change the class for multiple segments, in the same request, as long as it is the same class. For example, you can change segments 01, 04, 05 to class Y. However, you cannot change segment 01 to B and 03 to Y in the same request; you must submit multiple requests for this type of change.
One or more segments must exist in the itinerary before a change can be made.
Request:
Unless otherwise specified, use ALL CAPS in any request data.
A typical request within the <DateClassMods> (1070 Data Record) includes the following:
Prerequisite tasks:
One of the following prerequisite tasks must be completed for an itinerary segment to exist:
Expected response:
Description: Flight Data
|
|
Error and warning responses:
<TextMsg> tag/<ErrText> tag: number of arrays, delimiter character, level number, version number, <Err>, <KlrInErr>, <Text>.
1. Scenario: Processing error.
2. Scenario: Processing error.
3. Scenario: No itinerary exists.
4. Scenario: Attempting change to a partial marriage.
5. Scenario: Vendor denies cancel.
6. Scenario: Unable to find segment to change.
7. Scenario: Inactive/flown segment.
8. Scenario: If booking is in ‘file record’ mode and it is an IMAGE booking file.
9. Scenario: If booking is in ‘file record’ mode and it is a REMAINDER booking file.
10. Scenario: ASR/SELL inhibited.
11. Scenario: If folder retrieved, no active items exist, and not FARES entry.
12. Scenario: Air segments not present in the itinerary.
13. Scenario: Attempting to change an Atraxis-booked segment.
14. Scenario: No selling agreement with vendor.
15. Scenario: Vendor is schedule level participant.
16. Scenario: Schedule change is active.
17. Scenario: Segment in the booking has expired.
18. Scenario: Traffic restriction.
19. Scenario: Booking date out of range.
20. Scenario: Date not valid.
21. Scenario: Waitlist closed.
22. Scenario: Invalid class.
23. Scenario: Flight not available.
24. Scenario: Attempted sell to Cuban city.
25. Scenario: Flight past departure time.
26. Scenario: Attempted to change to/from OPEN segment.
27. Scenario: Invalid class modifier.
28. Scenario: Invalid class.
29. Scenario: Error finding segment.
30. Scenario: Attempting to update booking when it is already being held.
Flight Information messages:
Note: Those with * before and after the message are directly from the vendor.
NOTE CLASS MODIFIER CHANGED BY AIRLINE
NOTE CLASS MODIFIER REMOVED BY AIRLINE
NOTE CLASS MODIFIER ADDED BY AIRLINE
SUPER GUARANTEED/GUARANTEED SELL NOT ACHIEVED
GROUND TRANSPORTATION - SECURED SELL NOT AVAILABLE
CLASS NOT FOUND - WILL REQUEST FROM VENDOR
SECURED SELL NOT AVAILABLE
ENTER G/NAME - GROUP BOOKING REQUIRED
SEAT DATA CANCELLED
SSR DATA MODIFIED
ASSOCIATED COSTS CANCELLED
COSTS EXIST - CHECK IF CHANGES REQUIRED
INVOICED COSTS - CHECK IF ADJUSTMENT REQUIRED
CANCEL REQUEST COMPLETED
Follow-on requests:
There are no required follow-on requests.
|
<DateClassMods> |
Terminal Equivalents: |
Apollo: Xn/0… |
Galileo: @1/… |
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
|
|
SQSL |
1-1 |
<AvailSourceInfo> |
|
|
|
SQD1 |
1-1 |
<DateClassInfo> |
|
<DateClass> |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
|
|
SRD1 |
1-99 (1G) 1-99 cancel (1V) 1-8 rebook (1V) |
<AirSellChange> |