SALERT_GET_CONTAINER_API SAP Function module

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

Associated Function Group: SALERT_CATEGORY_API
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM SALERT_GET_CONTAINER_API - SALERT GET CONTAINER API

CALL FUNCTION 'SALERT_GET_CONTAINER_API' "
* EXPORTING
*   ip_category =               " salrtdcat
*   ip_alias =                  " salertdalias
*   ip_string_encoding = 'UTF-8'  " abap_encod
  IMPORTING
    et_values =                 " swconttab
    et_definition =             " swbconttab
    ep_xml_scheme_string =      " string
    ep_xml_scheme_xstring =     " xstring
  EXCEPTIONS
    CATEGORY_UNKNOWN = 1        "
    ALIAS_UNKNOWN = 2           "
    NO_CONTAINER_DEFINITION = 3  "
    INTERNAL_ERROR = 4          "
    .  "  SALERT_GET_CONTAINER_API

ABAP code example for Function Module SALERT_GET_CONTAINER_API

The ABAP code below is a full code listing to execute function module SALERT_GET_CONTAINER_API 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_et_values  
 
 TYPE SWCONTTAB
,
ld_et_definition  
 
 TYPE SWBCONTTAB
,
ld_ep_xml_scheme_string  
 
 TYPE STRING
,
ld_ep_xml_scheme_xstring  
 
 TYPE XSTRING
.


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

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

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

CALL FUNCTION 'SALERT_GET_CONTAINER_API'
* EXPORTING
*   ip_category =                ld_ip_category
*   ip_alias =                   ld_ip_alias
*   ip_string_encoding =         ld_ip_string_encoding
  IMPORTING
    et_values =                  ld_et_values
    et_definition =              ld_et_definition
    ep_xml_scheme_string =       ld_ep_xml_scheme_string
    ep_xml_scheme_xstring =      ld_ep_xml_scheme_xstring
  EXCEPTIONS
    CATEGORY_UNKNOWN =           1
    ALIAS_UNKNOWN =              2
    NO_CONTAINER_DEFINITION =    3
    INTERNAL_ERROR =             4
    .  "  SALERT_GET_CONTAINER_API

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
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_et_values
 
 TYPE SWCONTTAB ,
ld_ip_category
 
 TYPE SALRTDCAT ,
ld_et_definition
 
 TYPE SWBCONTTAB ,
ld_ip_alias
 
 TYPE SALERTDALIAS ,
ld_ep_xml_scheme_string
 
 TYPE STRING ,
ld_ip_string_encoding
 
 TYPE ABAP_ENCOD ,
ld_ep_xml_scheme_xstring
 
 TYPE XSTRING .


ld_ip_category = 'Check type of data required'.
ld_ip_alias = 'Check type of data required'.
ld_ip_string_encoding = 'Check type of data required'.