SAP DDIF_ENQU_GET Function Module for DD: Interface for reading a lock object from the ABAP Dictionary









DDIF_ENQU_GET is a standard ddif enqu get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DD: Interface for reading a lock object from the ABAP Dictionary 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 ddif enqu get FM, simply by entering the name DDIF_ENQU_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: SDIF
Program Name: SAPLSDIF
Main Program: SAPLSDIF
Appliation area: S
Release date: 29-Apr-1999
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DDIF_ENQU_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 'DDIF_ENQU_GET'"DD: Interface for reading a lock object from the ABAP Dictionary
  EXPORTING
   NAME =  "Name of the Lock Object to be Read
*  STATE = 'A' "Read Status of the Lock Object
*  LANGU = ' ' "Language in which Texts are Read

 IMPORTING
   GOTSTATE =  "Status in which Reading took Place
   DD25V_WA =  "Header of the Lock Object

TABLES
*  DD26E_TAB =  "Base Tables of the Lock Object
*  DD27P_TAB =  "Lock Parameter of the Lock Object
*  DDENA_TAB =  "Lock Arguments of the Lock Object

EXCEPTIONS
   ILLEGAL_INPUT = 1
.



IMPORTING Parameters details for DDIF_ENQU_GET

NAME - Name of the Lock Object to be Read

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

STATE - Read Status of the Lock Object

Data type: DDOBJSTATE
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGU - Language in which Texts are Read

Data type: SY-LANGU
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for DDIF_ENQU_GET

GOTSTATE - Status in which Reading took Place

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

DD25V_WA - Header of the Lock Object

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

TABLES Parameters details for DDIF_ENQU_GET

DD26E_TAB - Base Tables of the Lock Object

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

DD27P_TAB - Lock Parameter of the Lock Object

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

DDENA_TAB - Lock Arguments of the Lock Object

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

EXCEPTIONS details

ILLEGAL_INPUT - Value not Allowed for Parameter

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

Copy and paste ABAP code example for DDIF_ENQU_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, "   
lv_gotstate  TYPE DDGOTSTATE, "   
lt_dd26e_tab  TYPE STANDARD TABLE OF DD26E, "   
lv_illegal_input  TYPE DD26E, "   
lv_state  TYPE DDOBJSTATE, "   'A'
lv_dd25v_wa  TYPE DD25V, "   
lt_dd27p_tab  TYPE STANDARD TABLE OF DD27P, "   
lv_langu  TYPE SY-LANGU, "   ' '
lt_ddena_tab  TYPE STANDARD TABLE OF DDENA. "   

  CALL FUNCTION 'DDIF_ENQU_GET'  "DD: Interface for reading a lock object from the ABAP Dictionary
    EXPORTING
         NAME = lv_name
         STATE = lv_state
         LANGU = lv_langu
    IMPORTING
         GOTSTATE = lv_gotstate
         DD25V_WA = lv_dd25v_wa
    TABLES
         DD26E_TAB = lt_dd26e_tab
         DD27P_TAB = lt_dd27p_tab
         DDENA_TAB = lt_ddena_tab
    EXCEPTIONS
        ILLEGAL_INPUT = 1
. " DDIF_ENQU_GET




ABAP code using 7.40 inline data declarations to call FM DDIF_ENQU_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.

 
 
 
 
DATA(ld_state) = 'A'.
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_langu).
DATA(ld_langu) = ' '.
 
 


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!