Task: Change Segment Details

The Change Segment Task changes the segment description.

Section 1: Short Answer

Transaction Name:

AirChangeSegmentStatus_1_0_1

Can any other transactions(s) perform this same task?

No.

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.

Not applicable.

Section 2: Detailed Description

Change of times, stopover indicator (1G only), status code and day change.

Request:

Unless otherwise specified, use ALL CAPS in any request data.

Reference Sell via General Display and via Flight Specific Display:

Required Data:

<DispSeqNum>

One or a combination of the following (See NOTE below):

<Status>

<StartTm>

<EndTm>

<DtChg>

<StopoverIgnoreInd> (1G only)

NOTE: The Galileo host issues an error when a stopover/ignore indicator is present with any of the required data, listed above. Stopover/ignore indicator is mutually exclusive to the other fields. Also, the host issues an error if a 'change of day' is issued without timings.

Prerequisite tasks:

One or more segments need to exist before a change can be made.

Expected response:

No data is returned. The <SegmentDetail> tag (Data Record 1067) is returned with the return code and PROC code set to zero.

Error and warning responses:

The <ErrText> tag is returned in the <SegmentDetail> tag (Data Record 1067).

1. Scenario: System error.

Error: SYSTEM ERROR – IGNORE TRANSACTION RECOMMENDED n (1G)
Error: UNABLE TO PROCESS (1G)
Error: *SYSTEM ERROR* (1G)
Error: UNA PROC (1V)
Error: SYS ERROR OCCURRED (1V)

2. Scenario: Booking is in ‘file record’ mode and it is a REMAINDER booking file.

Error: BF MODIFICATION RESTRICTION – RECEIVE AND END TRANSACT. (1G)

3. Scenario: Booking is in ‘file record’ mode and it is an IMAGE booking file.

Error: BF MODIFICATION RESTRICTED – FILE RECORD (1G)

4. Scenario: ASR/SELL inhibited.

Error: RESTRICTED (1G and 1V)

5. Scenario: Manual fares in progress.

Error: MANUAL FARES IN PROGRESS-FINISH OR IGNORE (1G)

6. Scenario: Folder exists in the booking file(1G).

Error: INPUT RESTRICTED – IGNORE SUMMARY FOLDER (1G)

7. Scenario: Attempting to change non active or ‘flown’ segment.

Error: ** ERROR **; SEGMENT n NOT ACTIVE (1G)
Error: CHECK STATUS FOR THIS SEGMENT (1V)

8. Scenario: Segment is Atraxis booked segment (1G only).

Error: RESTRICTED (1G)

9. Scenario: Stopover indicator not exclusive (1G only).

Error: SYNTAX ERROR IN KLR (1G)

10. Scenario: Itinerary not present.

Error: NO ITINERARY PRESENT (1G)
Error: CK SGMT NBR (1V)

11. Scenario: Segment number does not exist.

Error: SEGMENT n CHECK SEGMENT NUMBER
Error: CK SGMT NBR (1V)

12. Scenario: Time of ‘2400’ or ‘0000’ entered.

Error: CHECK TIMINGS (1G)

13. Scenario: Only arrival time entered.

Error: CHECK STATUS CODE (1G)
Error: INVALID TIME (1V)

14. Scenario: Only departure time entered.

Error: INVALID TIME (1V)

15. Scenario: Incorrect status code entered.

Error: ** ERROR **; SEGMENT n CHECK SEGMENT NUMBER (1G)
Error: CHECK STATUS FOR THIS SEGMENT (1V)

16. Scenario: Attempting to cancel a new segment.

Error: CHECK STATUS FOR THIS SEGMENT (1V)

17. Scenario: Invalid duty code.

Error: ** ERROR **; SEGMENT n CHECK SEGMENT NUMBER (1G)
Error: RESTRICTED (1V)

18. Scenario: Invalid status code entered.

Error: CHECK STATUS CODE (1G)

19. Scenario: Incorrect ‘Change of Date’ entered.

Error: CHECK DATE DISCREPANCY (1G)

20. Scenario: ‘Change of Date’ entered without times.

Error: SYNTAX ERROR IN KLR (1G)

21. Scenario: Incorrect Stopover/Ignore indicator used (i.e.: not I/X/S) (1G only).

Error: CHECK STATUS CODE

Follow-on requests:

There are no follow-on requests.

Section 3: Tables

Request (Input) Tags

<SegmentDetailMods>

Terminal Equivalents:

Apollo .nT/… or .n(status)/

Galileo @n/… or @n(status)

Ordering	KLR	Min/Max	XML Tag
A	SQC1	1-1	<SegmentDetailInfo>
B	SQC2	1-1	<SequenceNumber>

Response (Output) Tags

<SegmentDetail>

	Ordering	KLR	Min/Max	XML Tag
	A	EROR	1-1	<ErrText>

Related Samples

AirChangeSegmentStatus_1_0_1_2