SAP PFL_ACTIVATE_PROFILE Function Module for









PFL_ACTIVATE_PROFILE is a standard pfl activate profile 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 activate profile FM, simply by entering the name PFL_ACTIVATE_PROFILE 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_ACTIVATE_PROFILE 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_ACTIVATE_PROFILE'"
EXPORTING
PROFILE_NAME = "
PROFILE_VERSION = "
FULLY_QUALIFIED_PROFILENAME = "
PROFILE_TYPE = "

EXCEPTIONS
PFL_DOESNT_EXIST = 1 PFL_IS_EMPTY = 2 PFL_OPEN_ERROR = 3 UNKNOWN_ERROR_OCCURED = 4 PFL_HEADER_UPDATE_ERROR = 5 INVALID_PROFILE_TYPE = 6 VERSION_IS_NOT_YOUNGEST = 7 AUTHORIZATION_MISSING = 8 FILE_IS_NO_PROFILE = 9
.



IMPORTING Parameters details for PFL_ACTIVATE_PROFILE

PROFILE_NAME -

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

PROFILE_VERSION -

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

FULLY_QUALIFIED_PROFILENAME -

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

PROFILE_TYPE -

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

EXCEPTIONS details

PFL_DOESNT_EXIST -

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

PFL_IS_EMPTY -

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

PFL_OPEN_ERROR -

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

UNKNOWN_ERROR_OCCURED -

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

PFL_HEADER_UPDATE_ERROR -

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

INVALID_PROFILE_TYPE -

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

VERSION_IS_NOT_YOUNGEST -

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

AUTHORIZATION_MISSING -

Data type:
Optional: No
Call by Reference: Yes

FILE_IS_NO_PROFILE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PFL_ACTIVATE_PROFILE 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:
lv_profile_name  TYPE TPFHT-PFNAME, "   
lv_pfl_doesnt_exist  TYPE TPFHT, "   
lv_pfl_is_empty  TYPE TPFHT, "   
lv_profile_version  TYPE TPFHT-VERSNR, "   
lv_pfl_open_error  TYPE TPFHT, "   
lv_fully_qualified_profilename  TYPE TPFHT-PFFILE, "   
lv_profile_type  TYPE BTCH0000-CHAR1, "   
lv_unknown_error_occured  TYPE BTCH0000, "   
lv_pfl_header_update_error  TYPE BTCH0000, "   
lv_invalid_profile_type  TYPE BTCH0000, "   
lv_version_is_not_youngest  TYPE BTCH0000, "   
lv_authorization_missing  TYPE BTCH0000, "   
lv_file_is_no_profile  TYPE BTCH0000. "   

  CALL FUNCTION 'PFL_ACTIVATE_PROFILE'  "
    EXPORTING
         PROFILE_NAME = lv_profile_name
         PROFILE_VERSION = lv_profile_version
         FULLY_QUALIFIED_PROFILENAME = lv_fully_qualified_profilename
         PROFILE_TYPE = lv_profile_type
    EXCEPTIONS
        PFL_DOESNT_EXIST = 1
        PFL_IS_EMPTY = 2
        PFL_OPEN_ERROR = 3
        UNKNOWN_ERROR_OCCURED = 4
        PFL_HEADER_UPDATE_ERROR = 5
        INVALID_PROFILE_TYPE = 6
        VERSION_IS_NOT_YOUNGEST = 7
        AUTHORIZATION_MISSING = 8
        FILE_IS_NO_PROFILE = 9
. " PFL_ACTIVATE_PROFILE




ABAP code using 7.40 inline data declarations to call FM PFL_ACTIVATE_PROFILE

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 PFNAME FROM TPFHT INTO @DATA(ld_profile_name).
 
 
 
"SELECT single VERSNR FROM TPFHT INTO @DATA(ld_profile_version).
 
 
"SELECT single PFFILE FROM TPFHT INTO @DATA(ld_fully_qualified_profilename).
 
"SELECT single CHAR1 FROM BTCH0000 INTO @DATA(ld_profile_type).
 
 
 
 
 
 
 


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!