SAP PFL_CHECK_PARAMETER_NAME Function Module for









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

Function Group: SPFL
Program Name: SAPLSPFL
Main Program: SAPLSPFL
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function PFL_CHECK_PARAMETER_NAME 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 'PFL_CHECK_PARAMETER_NAME'"
EXPORTING
PARAMETER_NAME = "
PARAMETER_TYPE = "
* PARAMETER_NR = 0 "

IMPORTING
PARAMETERNAME_VALID = "
PARAMETERTYPE_VALID = "

TABLES
PROTOCOL = "

EXCEPTIONS
INVALID_PARAMETER_TYPE = 1 PARAMETER_NAME_MISSING = 2
.



IMPORTING Parameters details for PFL_CHECK_PARAMETER_NAME

PARAMETER_NAME -

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

PARAMETER_TYPE -

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

PARAMETER_NR -

Data type: TPFET-PARNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for PFL_CHECK_PARAMETER_NAME

PARAMETERNAME_VALID -

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

PARAMETERTYPE_VALID -

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

TABLES Parameters details for PFL_CHECK_PARAMETER_NAME

PROTOCOL -

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

EXCEPTIONS details

INVALID_PARAMETER_TYPE -

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

PARAMETER_NAME_MISSING -

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

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

DATA:
lt_protocol  TYPE STANDARD TABLE OF TPFCKPROT, "   
lv_parameter_name  TYPE TPFET-PARNAME, "   
lv_parametername_valid  TYPE BTCH0000-CHAR1, "   
lv_invalid_parameter_type  TYPE BTCH0000, "   
lv_parameter_type  TYPE BTCH0000-CHAR1, "   
lv_parametertype_valid  TYPE BTCH0000-CHAR1, "   
lv_parameter_name_missing  TYPE BTCH0000, "   
lv_parameter_nr  TYPE TPFET-PARNR. "   0

  CALL FUNCTION 'PFL_CHECK_PARAMETER_NAME'  "
    EXPORTING
         PARAMETER_NAME = lv_parameter_name
         PARAMETER_TYPE = lv_parameter_type
         PARAMETER_NR = lv_parameter_nr
    IMPORTING
         PARAMETERNAME_VALID = lv_parametername_valid
         PARAMETERTYPE_VALID = lv_parametertype_valid
    TABLES
         PROTOCOL = lt_protocol
    EXCEPTIONS
        INVALID_PARAMETER_TYPE = 1
        PARAMETER_NAME_MISSING = 2
. " PFL_CHECK_PARAMETER_NAME




ABAP code using 7.40 inline data declarations to call FM PFL_CHECK_PARAMETER_NAME

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.

 
"SELECT single PARNAME FROM TPFET INTO @DATA(ld_parameter_name).
 
"SELECT single CHAR1 FROM BTCH0000 INTO @DATA(ld_parametername_valid).
 
 
"SELECT single CHAR1 FROM BTCH0000 INTO @DATA(ld_parameter_type).
 
"SELECT single CHAR1 FROM BTCH0000 INTO @DATA(ld_parametertype_valid).
 
 
"SELECT single PARNR FROM TPFET INTO @DATA(ld_parameter_nr).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!