Task: Payment Calculator

The Payment Calculator task enables the user to validate commission information for a specified filed fare.

Section 1: Short Answer

Transaction Name:

DocProdFareManipulation_4_2

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

No other transaction can perform this task.

Can this task be performed in a sessionless environment?

This task must be used in a sessioned environment.

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

The request and response are available on the Galileo system only.

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

A knowledge of Reservation, Ticketing and Pricing would be beneficial for this task.

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

A PNR with filed fare information must be retrieved before initiating the Payment Calculator.

Section 2: Detailed Description

Request:

The <PaymentCalculatorMods> (4046 1.0) is used to request the Payment Calculator.  The <FareNumInfo> tag is used to supply the filed fare for the commission to be validated.

Prerequisite tasks:

The PNR should be present in AAA.

Expected response:

The <PaymentCalculator> (4047 1.0) is used to return the Payment Calculator commission data.

If the Payment Calculator transaction completes successfully:

Error and warning responses:

When the Payment Calculator task encounters an error, the error is returned in the <ErrText> tag.  The following error messages may be received:

0011 - SYSTEM ERROR OCCURRED

8822 - INVALID FORMAT DATA

8408 - BPC_NO_BF_CREATE_OR_RETRIEVE_ FIRST

8409 - BPC_INVALID_FILED_FARE_NUMBER_DO_TPC_FIRST

8410 - BPC_FILED_FARE_NOT_FOUND

8411 - BPC_ERROR_READING_SEGMENTS_IN_FILED_FARE   

8412 - BPC_PLATING_CARRIER_REQUIRED_IN_FILED_FARE

8413 - BPC_ERROR_READING_AGENCY_FILE_S70S7

8414 - BPC_ERROR_READING_FARE_IN_BOOKING_FILE

8415 - BPC_ERROR_READING_ITINERARY

8416 - BPC_COMMISSION_NOT_FOUND_IN_TABLES

8417 - BPC_OUTPUT_IS_TOO_LARGE_FOR_DISPLAY

8418 - BPC_NO_VALID_ERROR_MSG_FOUND

Follow-on requests:

No follow-on requests exist.

Section 3: Tables

Request (Input) Tags

<PaymentCalculatorMods>

Terminal Equivalents:

Not applicable on Apollo

Galileo: TPC

 

 

Ordering

KLR

Min/Max

XML Tag

 

 

DPFI

1-1

<FareNumInfo>

Response (Output) Tags – Normal Response

<PaymentCalculator>

 

 

 

Ordering

KLR

Min/Max

XML Tag

    DP10 1-1 <CommissionMod>

 

 

DPIR

0-1

<InvoiceRmk> (Itinerary / Invoice)

Response (Output) Tags – Error Response

<PaymentCalculator>

 

 

 

Ordering

KLR

Min/Max

XML Tag

 

 

EROR

1-1

<ErrText>