Task: Update Separate Itineraries

Updates a specific stored fare within the itinerary, such that the one itinerary is printed per passenger.

Section 1: Short Answer

Transaction Name:

DocProdFareRequote_8

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

No, only DocProdFareRequote_8 can perform this task.

Can this task be performed in a sessionless environment?

No. A PNR/booking file must exist. A fare must exist.

Are the request and response identical on both the Apollo and Galileo systems?

The Galileo system will need the AAT field NSET set to No for the IS modifier to work.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

A fare must exist.
A PNR/booking file must exist.
The task is available through structured data and Focalpoint (terminal emulation).

Explain any special limits or distinct restrictions to the input data that may not be readily apparent.

A PNR/booking file must exist.

Update Separate Itinerary task is not valid with the following modifiers:

Request:

Prerequisite tasks:

Expected response:

The response <UpdateModifiers> will include <FareNumInfo> and <DPOK>.

Error and warning responses:

If there is an error, it is sent back in <ErrText> in the <UpdateModifiers> response.

On the Galileo system, if the NSET in the AAT is set to yes the following error message is used:

ERROR 4368 – MODIFIER NOT ALLOWED

Follow-on requests:

None.