SAP BBP_EV_API_EXCEPT_WORKLIST_GET Function Module for API to get a list of exception via the Event Framework
BBP_EV_API_EXCEPT_WORKLIST_GET is a standard bbp ev api except worklist 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 API to get a list of exception via the Event Framework 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 bbp ev api except worklist get FM, simply by entering the name BBP_EV_API_EXCEPT_WORKLIST_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_EV_API
Program Name: SAPLBBP_EV_API
Main Program: SAPLBBP_EV_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_EV_API_EXCEPT_WORKLIST_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 'BBP_EV_API_EXCEPT_WORKLIST_GET'"API to get a list of exception via the Event Framework.
EXPORTING
* IT_OBJECT_KEY = "Globally Unique Identifier in 32-Character Display
* IT_EVENT_PROCESSOR = "1: single + processor, 2: empty, 3: not empty
* IT_EVENT = "Filter: Events
* IT_EVENT_STATUS_APP = "Filer: Event status
* IV_READ_MESSAGES = 'X' "X (read, default value), otherwise space
* IV_READ_INTERNAL_ERRORS = ' ' "X (read), otherwise ignore (default)
* IV_OBJECT_TYPE = "Objekt Typ
* IV_CREATE_DATE = "Aktuelles Datum des Applikationsservers
IMPORTING
ET_EVENTS = "Table of events
EXCEPTIONS
NO_ENTRY_FOUND = 1
IMPORTING Parameters details for BBP_EV_API_EXCEPT_WORKLIST_GET
IT_OBJECT_KEY - Globally Unique Identifier in 32-Character Display
Data type: BBPT_EXCEPTION_SEL_OBJECT_KEYOptional: Yes
Call by Reference: Yes
IT_EVENT_PROCESSOR - 1: single + processor, 2: empty, 3: not empty
Data type: BBPT_EXCEPTION_SEL_PROCESSOROptional: Yes
Call by Reference: Yes
IT_EVENT - Filter: Events
Data type: BBPT_EXCEPTION_SEL_EVENTOptional: Yes
Call by Reference: Yes
IT_EVENT_STATUS_APP - Filer: Event status
Data type: BBPT_EXCEPTION_SEL_STATUSOptional: Yes
Call by Reference: Yes
IV_READ_MESSAGES - X (read, default value), otherwise space
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_READ_INTERNAL_ERRORS - X (read), otherwise ignore (default)
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
IV_OBJECT_TYPE - Objekt Typ
Data type: BBP_BUS_OBJECT_TYPEOptional: Yes
Call by Reference: Yes
IV_CREATE_DATE - Aktuelles Datum des Applikationsservers
Data type: SYDATUMOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_EV_API_EXCEPT_WORKLIST_GET
ET_EVENTS - Table of events
Data type: BBPT_EVENTSOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRY_FOUND - no entry found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_EV_API_EXCEPT_WORKLIST_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_et_events | TYPE BBPT_EVENTS, " | |||
| lv_it_object_key | TYPE BBPT_EXCEPTION_SEL_OBJECT_KEY, " | |||
| lv_no_entry_found | TYPE BBPT_EXCEPTION_SEL_OBJECT_KEY, " | |||
| lv_it_event_processor | TYPE BBPT_EXCEPTION_SEL_PROCESSOR, " | |||
| lv_it_event | TYPE BBPT_EXCEPTION_SEL_EVENT, " | |||
| lv_it_event_status_app | TYPE BBPT_EXCEPTION_SEL_STATUS, " | |||
| lv_iv_read_messages | TYPE XFELD, " 'X' | |||
| lv_iv_read_internal_errors | TYPE XFELD, " ' ' | |||
| lv_iv_object_type | TYPE BBP_BUS_OBJECT_TYPE, " | |||
| lv_iv_create_date | TYPE SYDATUM. " |
|   CALL FUNCTION 'BBP_EV_API_EXCEPT_WORKLIST_GET' "API to get a list of exception via the Event Framework |
| EXPORTING | ||
| IT_OBJECT_KEY | = lv_it_object_key | |
| IT_EVENT_PROCESSOR | = lv_it_event_processor | |
| IT_EVENT | = lv_it_event | |
| IT_EVENT_STATUS_APP | = lv_it_event_status_app | |
| IV_READ_MESSAGES | = lv_iv_read_messages | |
| IV_READ_INTERNAL_ERRORS | = lv_iv_read_internal_errors | |
| IV_OBJECT_TYPE | = lv_iv_object_type | |
| IV_CREATE_DATE | = lv_iv_create_date | |
| IMPORTING | ||
| ET_EVENTS | = lv_et_events | |
| EXCEPTIONS | ||
| NO_ENTRY_FOUND = 1 | ||
| . " BBP_EV_API_EXCEPT_WORKLIST_GET | ||
ABAP code using 7.40 inline data declarations to call FM BBP_EV_API_EXCEPT_WORKLIST_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_iv_read_messages) | = 'X'. | |||
| DATA(ld_iv_read_internal_errors) | = ' '. | |||
Search for further information about these or an SAP related objects