SAP FITV_RD_CHECK_INPUT Function Module for

Search SAP Function Modules

FITV_RD_CHECK_INPUT is a standard fitv rd check input 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 fitv rd check input FM, simply by entering the name FITV_RD_CHECK_INPUT into the relevant SAP transaction such as SE37 or SE38.

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

Function FITV_RD_CHECK_INPUT 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 'FITV_RD_CHECK_INPUT'"
  EXPORTING
   ORT01 =  "
*  ACT_HEAD =  "Structure of Travel Expenses Table PTRV_HEAD
*  ACT_PERIO =  "Structure of Transp. Table PTRV_PERIO

TABLES
   ZIEL =  "Stopover

EXCEPTIONS
   NO_ADRESS_FIRST_DEST = 1    NO_ADRESS_FURTHER_DEST = 2    ADRESS_INCOMPLETE_FIRT_DEST = 3    ADRESS_INCOMPLETE_FURTHER_DEST = 4    MAIN_DEST_TO_SHORT = 5    DEST_TO_SHORT = 6    ADDRESS_GKZ_INVALID = 7 

.

IMPORTING Parameters details for FITV_RD_CHECK_INPUT

ORT01 -

Data type: PTP02-ZORT1
Optional: No
Call by Reference: Yes

ACT_HEAD - Structure of Travel Expenses Table PTRV_HEAD

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

ACT_PERIO - Structure of Transp. Table PTRV_PERIO

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

TABLES Parameters details for FITV_RD_CHECK_INPUT

ZIEL - Stopover

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

EXCEPTIONS details

NO_ADRESS_FIRST_DEST -

Data type:
Optional: No
Call by Reference: Yes

NO_ADRESS_FURTHER_DEST -

Data type:
Optional: No
Call by Reference: Yes

ADRESS_INCOMPLETE_FIRT_DEST -

Data type:
Optional: No
Call by Reference: Yes

ADRESS_INCOMPLETE_FURTHER_DEST -

Data type:
Optional: No
Call by Reference: Yes

MAIN_DEST_TO_SHORT -

Data type:
Optional: No
Call by Reference: Yes

DEST_TO_SHORT -

Data type:
Optional: No
Call by Reference: Yes

ADDRESS_GKZ_INVALID -

Data type:
Optional: No
Call by Reference: Yes

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

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