SAP TP_1G_CAR_AVAILABILITY Function Module for

Search SAP Function Modules

TP_1G_CAR_AVAILABILITY is a standard tp 1g car availability 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 1g car availability FM, simply by entering the name TP_1G_CAR_AVAILABILITY into the relevant SAP transaction such as SE37 or SE38.

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

Function TP_1G_CAR_AVAILABILITY 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_1G_CAR_AVAILABILITY'"
  EXPORTING
   CONTEXT_NUMBER =  "Context
   INPUT_PARAMETER =  "

 IMPORTING
   CAR_AVAIL_OUT =  "Rental Car Availability: Output

TABLES
*  T_CAR_OPTION_IN =  "
   T_CAR_PROVIDER_OUT =  "Rental car vendor output
   T_CAR_OUT =  "Rental car price list

EXCEPTIONS
   INVALID_SYSTEM = 1    INVALID_PROVIDER_OR_CAR = 10    INVALID_LOCATION = 11    RATE_NOT_AVAILABLE = 12    GENERAL_API_ERROR = 13    INVALID_CONTEXT = 2    NO_CARS_AVAILABLE = 3    RFC_ERROR = 4    CONNECTION_ERROR = 5    NO_DESTINATION = 6    UNEXPECTED_RESPONSE = 7    PARAMETER_ERROR = 8    INVALID_DATE_TIME = 9 

.

IMPORTING Parameters details for TP_1G_CAR_AVAILABILITY

CONTEXT_NUMBER - Context

Data type: FTPT_VARIANT-VARIANT
Optional: No
Call by Reference: No ( called with pass by value option)

INPUT_PARAMETER -

Data type: FTPS_CAR_AVAIL_IN
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for TP_1G_CAR_AVAILABILITY

CAR_AVAIL_OUT - Rental Car Availability: Output

Data type: FTPS_CAR_AVAIL_INFO_OUT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for TP_1G_CAR_AVAILABILITY

T_CAR_OPTION_IN -

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

T_CAR_PROVIDER_OUT - Rental car vendor output

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

T_CAR_OUT - Rental car price list

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

EXCEPTIONS details

INVALID_SYSTEM -

Data type:
Optional: No
Call by Reference: Yes

INVALID_PROVIDER_OR_CAR -

Data type:
Optional: No
Call by Reference: Yes

INVALID_LOCATION -

Data type:
Optional: No
Call by Reference: Yes

RATE_NOT_AVAILABLE -

Data type:
Optional: No
Call by Reference: Yes

GENERAL_API_ERROR - General API error

Data type:
Optional: No
Call by Reference: Yes

INVALID_CONTEXT -

Data type:
Optional: No
Call by Reference: Yes

NO_CARS_AVAILABLE -

Data type:
Optional: No
Call by Reference: Yes

RFC_ERROR - RFC Error

Data type:
Optional: No
Call by Reference: Yes

CONNECTION_ERROR - Error when setting up connection

Data type:
Optional: No
Call by Reference: Yes

NO_DESTINATION -

Data type:
Optional: No
Call by Reference: Yes

UNEXPECTED_RESPONSE -

Data type:
Optional: No
Call by Reference: Yes

PARAMETER_ERROR - Errors in passing parameters

Data type:
Optional: No
Call by Reference: Yes

INVALID_DATE_TIME -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TP_1G_CAR_AVAILABILITY 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_1G_CAR_AVAILABILITY

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