GET_SAML_MDATA SAP Function module - SAML Keytype, Version, Confirmation Method based on UI settings

GET_SAML_MDATA 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 GET_SAML_MDATA into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM GET_SAML_MDATA - GET SAML MDATA

CALL FUNCTION 'GET_SAML_MDATA' "SAML Keytype, Version, Confirmation Method based on UI settings
  EXPORTING
    iv_tg_method =              " string
    iv_selected_token_issuer =   " wss_sts_id
  IMPORTING
    ev_sv_enabled =             " boolean
    ev_prot_enabled =           " boolean
    ev_sts_enabled =            " boolean
    ev_key_type_text =          " string
    ev_saml_version_text =      " string
    ev_sts_mex_url =            " string
    ev_sts_url =                " string
    ev_saml1_trust =            " string
    ev_saml1_trust_txt =        " string
    .  "  GET_SAML_MDATA

ABAP code example for Function Module GET_SAML_MDATA

The ABAP code below is a full code listing to execute function module GET_SAML_MDATA 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_ev_sv_enabled  
 
 TYPE BOOLEAN
,
ld_ev_prot_enabled  
 
 TYPE BOOLEAN
,
ld_ev_sts_enabled  
 
 TYPE BOOLEAN
,
ld_ev_key_type_text  
 
 TYPE STRING
,
ld_ev_saml_version_text  
 
 TYPE STRING
,
ld_ev_sts_mex_url  
 
 TYPE STRING
,
ld_ev_sts_url  
 
 TYPE STRING
,
ld_ev_saml1_trust  
 
 TYPE STRING
,
ld_ev_saml1_trust_txt  
 
 TYPE STRING
.


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

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

CALL FUNCTION 'GET_SAML_MDATA'
  EXPORTING
    iv_tg_method =               ld_iv_tg_method
    iv_selected_token_issuer =    ld_iv_selected_token_issuer
  IMPORTING
    ev_sv_enabled =              ld_ev_sv_enabled
    ev_prot_enabled =            ld_ev_prot_enabled
    ev_sts_enabled =             ld_ev_sts_enabled
    ev_key_type_text =           ld_ev_key_type_text
    ev_saml_version_text =       ld_ev_saml_version_text
    ev_sts_mex_url =             ld_ev_sts_mex_url
    ev_sts_url =                 ld_ev_sts_url
    ev_saml1_trust =             ld_ev_saml1_trust
    ev_saml1_trust_txt =         ld_ev_saml1_trust_txt
    .  "  GET_SAML_MDATA

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_ev_sv_enabled
 
 TYPE BOOLEAN ,
ld_iv_tg_method
 
 TYPE STRING ,
ld_ev_prot_enabled
 
 TYPE BOOLEAN ,
ld_iv_selected_token_issuer
 
 TYPE WSS_STS_ID ,
ld_ev_sts_enabled
 
 TYPE BOOLEAN ,
ld_ev_key_type_text
 
 TYPE STRING ,
ld_ev_saml_version_text
 
 TYPE STRING ,
ld_ev_sts_mex_url
 
 TYPE STRING ,
ld_ev_sts_url
 
 TYPE STRING ,
ld_ev_saml1_trust
 
 TYPE STRING ,
ld_ev_saml1_trust_txt
 
 TYPE STRING .


ld_iv_tg_method = 'Check type of data required'.
ld_iv_selected_token_issuer = 'Check type of data required'.