LDAP_MAP_IN SAP Function module

LDAP_MAP_IN is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name LDAP_MAP_IN into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FSLDAP_MAP
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM LDAP_MAP_IN - LDAP MAP IN

CALL FUNCTION 'LDAP_MAP_IN' "
  EXPORTING
    serverid =                  " ldapserver-serverid  Symbolic Name of LDAP Server
    attributes =                " hybrastab     Table with Structure Names, Field Names and Types
    data_ldap =                 " ldapaltab     Table with Attribute Names and Types with Values
  IMPORTING
    data =                      " hybraltab     Table with Structure Names, Field Names + Types with Values
    datasys =                   " hybraltab     Table with Structure Names, Field Names + Types with Values
    return =                    " bapirettab    Table with BAPI Return Information
    .  "  LDAP_MAP_IN

ABAP code example for Function Module LDAP_MAP_IN

The ABAP code below is a full code listing to execute function module LDAP_MAP_IN including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_data  
 
 TYPE HYBRALTAB
,
ld_datasys  
 
 TYPE HYBRALTAB
,
ld_return  
 
 TYPE BAPIRETTAB
.

 

SELECT single SERVERID 
  FROM LDAPSERVER 
  INTO @DATA(ld_serverid).


DATA(ld_attributes) = 'Check type of data required'.

DATA(ld_data_ldap) = 'Check type of data required'.
.

CALL FUNCTION 'LDAP_MAP_IN'
  EXPORTING
    serverid =                   ld_serverid
    attributes =                 ld_attributes
    data_ldap =                  ld_data_ldap
  IMPORTING
    data =                       ld_data
    datasys =                    ld_datasys
    return =                     ld_return
    .  "  LDAP_MAP_IN

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_data
 
 TYPE HYBRALTAB ,
ld_serverid
 
 TYPE LDAPSERVER-SERVERID ,
ld_datasys
 
 TYPE HYBRALTAB ,
ld_attributes
 
 TYPE HYBRASTAB ,
ld_return
 
 TYPE BAPIRETTAB ,
ld_data_ldap
 
 TYPE LDAPALTAB .



SELECT single SERVERID 
  FROM LDAPSERVER 
  INTO ld_serverid.

ld_attributes = 'Check type of data required'.
ld_data_ldap = 'Check type of data required'.