BBP_EV_API_EXCEPT_OBJ_GET SAP Function module - API to read current exceptions to an object via the Event Framework

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

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

Pattern for FM BBP_EV_API_EXCEPT_OBJ_GET - BBP EV API EXCEPT OBJ GET

CALL FUNCTION 'BBP_EV_API_EXCEPT_OBJ_GET' "API to read current exceptions to an object via the Event Framework
* EXPORTING
*   iv_object_key =             " bbp_guid      Globally Unique Identifier in 32-Character Display
*   iv_object_type =            " bbp_bus_object_type  Object type
*   iv_object_node_key =        " bbp_guid      Globally Unique Identifier in 32-Character Display
*   iv_object_node_type =       " bbp_bus_object_type  Object type
*   iv_event_key =              " bbp_guid      Globally Unique Identifier in 32-Character Display
  IMPORTING
    et_events =                 " bbpt_events   table of persistent exceptions
  EXCEPTIONS
    NO_ENTRY_FOUND = 1          "               no entry found
    .  "  BBP_EV_API_EXCEPT_OBJ_GET

ABAP code example for Function Module BBP_EV_API_EXCEPT_OBJ_GET

The ABAP code below is a full code listing to execute function module BBP_EV_API_EXCEPT_OBJ_GET 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_events  
 
 TYPE BBPT_EVENTS
.


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

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

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

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

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

CALL FUNCTION 'BBP_EV_API_EXCEPT_OBJ_GET'
* EXPORTING
*   iv_object_key =              ld_iv_object_key
*   iv_object_type =             ld_iv_object_type
*   iv_object_node_key =         ld_iv_object_node_key
*   iv_object_node_type =        ld_iv_object_node_type
*   iv_event_key =               ld_iv_event_key
  IMPORTING
    et_events =                  ld_et_events
  EXCEPTIONS
    NO_ENTRY_FOUND =             1
    .  "  BBP_EV_API_EXCEPT_OBJ_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_events
 
 TYPE BBPT_EVENTS ,
ld_iv_object_key
 
 TYPE BBP_GUID ,
ld_iv_object_type
 
 TYPE BBP_BUS_OBJECT_TYPE ,
ld_iv_object_node_key
 
 TYPE BBP_GUID ,
ld_iv_object_node_type
 
 TYPE BBP_BUS_OBJECT_TYPE ,
ld_iv_event_key
 
 TYPE BBP_GUID .


ld_iv_object_key = 'Check type of data required'.
ld_iv_object_type = 'Check type of data required'.
ld_iv_object_node_key = 'Check type of data required'.
ld_iv_object_node_type = 'Check type of data required'.
ld_iv_event_key = 'Check type of data required'.