SAP SALU_GET_NAME_OF_ACT_CUSTSET Function Module for Get Name of Active Customizing Set









SALU_GET_NAME_OF_ACT_CUSTSET is a standard salu get name of act custset SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Name of Active Customizing Set processing and below is the pattern details for this FM, 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 salu get name of act custset FM, simply by entering the name SALU_GET_NAME_OF_ACT_CUSTSET into the relevant SAP transaction such as SE37 or SE38.

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



Function SALU_GET_NAME_OF_ACT_CUSTSET 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 'SALU_GET_NAME_OF_ACT_CUSTSET'"Get Name of Active Customizing Set
IMPORTING
CUST_SETNAME = "

EXCEPTIONS
NO_ACTIVE_SET_FOUND = 1
.



EXPORTING Parameters details for SALU_GET_NAME_OF_ACT_CUSTSET

CUST_SETNAME -

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

EXCEPTIONS details

NO_ACTIVE_SET_FOUND -

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

Copy and paste ABAP code example for SALU_GET_NAME_OF_ACT_CUSTSET 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_cust_setname  TYPE ALCUSTSET-SETNAME, "   
lv_no_active_set_found  TYPE ALCUSTSET. "   

  CALL FUNCTION 'SALU_GET_NAME_OF_ACT_CUSTSET'  "Get Name of Active Customizing Set
    IMPORTING
         CUST_SETNAME = lv_cust_setname
    EXCEPTIONS
        NO_ACTIVE_SET_FOUND = 1
. " SALU_GET_NAME_OF_ACT_CUSTSET




ABAP code using 7.40 inline data declarations to call FM SALU_GET_NAME_OF_ACT_CUSTSET

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 SETNAME FROM ALCUSTSET INTO @DATA(ld_cust_setname).
 
 


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!