SAP SLAD_DOMVALUES_GET Function Module for









SLAD_DOMVALUES_GET is a standard slad domvalues get 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 slad domvalues get FM, simply by entering the name SLAD_DOMVALUES_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function SLAD_DOMVALUES_GET 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 'SLAD_DOMVALUES_GET'"
EXPORTING
NAME = "
* LANGU = SY-LANGU "
* TEXTS_ONLY = ' ' "

TABLES
DD07V_TAB = "

EXCEPTIONS
ILLEGAL_INPUT = 1
.



IMPORTING Parameters details for SLAD_DOMVALUES_GET

NAME -

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

LANGU -

Data type: SY-LANGU
Default: SY-LANGU
Optional: No
Call by Reference: Yes

TEXTS_ONLY -

Data type: DDBOOL_D
Default: ' '
Optional: No
Call by Reference: Yes

TABLES Parameters details for SLAD_DOMVALUES_GET

DD07V_TAB -

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

EXCEPTIONS details

ILLEGAL_INPUT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SLAD_DOMVALUES_GET 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_name  TYPE DDOBJNAME, "   
lt_dd07v_tab  TYPE STANDARD TABLE OF DD07V, "   
lv_illegal_input  TYPE DD07V, "   
lv_langu  TYPE SY-LANGU, "   SY-LANGU
lv_texts_only  TYPE DDBOOL_D. "   ' '

  CALL FUNCTION 'SLAD_DOMVALUES_GET'  "
    EXPORTING
         NAME = lv_name
         LANGU = lv_langu
         TEXTS_ONLY = lv_texts_only
    TABLES
         DD07V_TAB = lt_dd07v_tab
    EXCEPTIONS
        ILLEGAL_INPUT = 1
. " SLAD_DOMVALUES_GET




ABAP code using 7.40 inline data declarations to call FM SLAD_DOMVALUES_GET

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 LANGU FROM SY INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
DATA(ld_texts_only) = ' '.
 


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!