Task: Assumed City Processing – HMCT

This task sets the tariff display default to a new city code as specified in the request.

Section 1: Short Answer

Transaction Name:

PNRBFManagement_38

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

Previous versions of PNRBFManagement, PNRBFBuildModify_7_7_1 and FareQuoteReprice_6_0 also contain the ability to perform assumed city processing.

Can this task be performed in a sessionless environment?

Yes.

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

Request:

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

An <AssumedPtMods> element must be sent to change the assumed city, if necessary. This request sets the default Tariff display to the city code specified. This entry is equivalent to the terminal emulation entry HMCT-ccc/I.  The city code entered is validated before it is used in the PNR/BF processing path.

Prerequisite tasks:

There are no prerequisite tasks. 

Expected response:

The response is a blank <AssumedPt>. The response block does contain any data at this time, so no error codes are returned.

Error and warning responses:

None

Follow-on requests:

There are no follow on requests.

Section 3: Tables

Request (Input) Tags

<AssumedPtMods>

Terminal Equivalents:

Apollo HMCT-ccc/I______

Galileo HMCT-ccc/I______

Ordering

KLR

Min/Max

KLR Name

 

1440

0 – 1

<AssumedPtMods>

 

Response (Output) Tags

 

Ordering

KLR

Min/Max

KLR Name

 

1441

0-1

Related Samples

PNRBFManagement_38_s54