SAP TP_1W_FLIGHT_FARE_NOTES Function Module for

Search SAP Function Modules

TP_1W_FLIGHT_FARE_NOTES is a standard tp 1w flight fare notes SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for tp 1w flight fare notes FM, simply by entering the name TP_1W_FLIGHT_FARE_NOTES into the relevant SAP transaction such as SE37 or SE38.

Function Group: FITP_SABRE_GENERAL
Program Name: SAPLFITP_SABRE_GENERAL
Main Program: SAPLFITP_SABRE_GENERAL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TP_1W_FLIGHT_FARE_NOTES pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'TP_1W_FLIGHT_FARE_NOTES'"
  EXPORTING
   CONTEXT_NUMBER =  "Plan variant number
*  FARE_BASIS =  "Complete basis code of rate component
*  CARRIER_CODE =  "Carrier code
*  DEPARTURE_LOCATION =  "Departure Location
*  ARRIVAL_LOCATION =  "Flight arrival location
*  FIRST_TRAVEL_DATE =  "First travel date
*  TICKETING_DATE =  "Last ticketing date. If n/a, date of last pricing

 IMPORTING
   VP_RETURN =  "

TABLES
   T_FARE_NOTES =  "Rate Rules

EXCEPTIONS
   FFE_BAD_CLIENT_INPUT = 1    ERROR_NO_PNR = 10    ERROR_PROCESSING = 11    ERROR_SABRE_FAILURE = 12    ERROR_BAD_CITYPAIR = 13    ERROR_BAD_DATE = 14    ERROR_INVALID_CARRIER = 15    NO_DESTINATION = 16    INVALID_CONTEXT = 17    CONNECTION_ERROR = 18    RFC_ERROR = 19    FFE_BAD_COLUMN = 2    FFE_BAD_COLUMN_LIST = 3    FFE_BAD_DB_OUTPUT = 4    FFE_BAD_SABRE_OUTPUT = 5    FFE_INVALID_IN_ROWLIST = 6    ERROR_FARE_DOES_NOT_EXIST = 7    ERROR_FARE_BASIS_REQUIRED = 8    ERROR_FARE_BASIS = 9 

.

IMPORTING Parameters details for TP_1W_FLIGHT_FARE_NOTES

CONTEXT_NUMBER - Plan variant number

Data type: VARIANT_NR
Optional: No
Call by Reference: Yes

FARE_BASIS - Complete basis code of rate component

Data type: FARE_BASIS_CODE
Optional: Yes
Call by Reference: Yes

CARRIER_CODE - Carrier code

Data type: FLIGHT_AIRLINE
Optional: Yes
Call by Reference: Yes

DEPARTURE_LOCATION - Departure Location

Data type: FLIGHT_SLOC_DEP
Optional: Yes
Call by Reference: Yes

ARRIVAL_LOCATION - Flight arrival location

Data type: FLIGHT_SLOC_ARR
Optional: Yes
Call by Reference: Yes

FIRST_TRAVEL_DATE - First travel date

Data type: SYDATUM
Optional: Yes
Call by Reference: Yes

TICKETING_DATE - Last ticketing date. If n/a, date of last pricing

Data type: SYDATUM
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for TP_1W_FLIGHT_FARE_NOTES

VP_RETURN -

Data type: I
Optional: No
Call by Reference: Yes

TABLES Parameters details for TP_1W_FLIGHT_FARE_NOTES

T_FARE_NOTES - Rate Rules

Data type: FTPT_FARE_NOTE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

FFE_BAD_CLIENT_INPUT - message - bad client input

Data type:
Optional: No
Call by Reference: Yes

ERROR_NO_PNR - message - no pnr

Data type:
Optional: No
Call by Reference: Yes

ERROR_PROCESSING - message - error procesing

Data type:
Optional: No
Call by Reference: Yes

ERROR_SABRE_FAILURE - message - Sabre failure

Data type:
Optional: No
Call by Reference: Yes

ERROR_BAD_CITYPAIR - message - bad city pair

Data type:
Optional: No
Call by Reference: Yes

ERROR_BAD_DATE - message - bad date

Data type:
Optional: No
Call by Reference: Yes

ERROR_INVALID_CARRIER - message - invalid carrier

Data type:
Optional: No
Call by Reference: Yes

NO_DESTINATION -

Data type:
Optional: No
Call by Reference: Yes

INVALID_CONTEXT - Invalid context

Data type:
Optional: No
Call by Reference: Yes

CONNECTION_ERROR - Connection Error

Data type:
Optional: No
Call by Reference: Yes

RFC_ERROR - RFC Connection Error

Data type:
Optional: No
Call by Reference: Yes

FFE_BAD_COLUMN - message - bad column

Data type:
Optional: No
Call by Reference: Yes

FFE_BAD_COLUMN_LIST - message - bad column list

Data type:
Optional: No
Call by Reference: Yes

FFE_BAD_DB_OUTPUT - message - bad DB output

Data type:
Optional: No
Call by Reference: Yes

FFE_BAD_SABRE_OUTPUT - message - bad Sabre output

Data type:
Optional: No
Call by Reference: Yes

FFE_INVALID_IN_ROWLIST - message - invalid data in rowlist

Data type:
Optional: No
Call by Reference: Yes

ERROR_FARE_DOES_NOT_EXIST - message - fare does not exist

Data type:
Optional: No
Call by Reference: Yes

ERROR_FARE_BASIS_REQUIRED - message - fare basis code required

Data type:
Optional: No
Call by Reference: Yes

ERROR_FARE_BASIS - message - fare basis

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TP_1W_FLIGHT_FARE_NOTES Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM TP_1W_FLIGHT_FARE_NOTES

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects