SAP BBP_EV_INTERNAL_MESSAGE_GET Function Module for API to get an internal error
BBP_EV_INTERNAL_MESSAGE_GET is a standard bbp ev internal message 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 an internal error 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 internal message get FM, simply by entering the name BBP_EV_INTERNAL_MESSAGE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_EV_INTERNAL
Program Name: SAPLBBP_EV_INTERNAL
Main Program: SAPLBBP_EV_INTERNAL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_EV_INTERNAL_MESSAGE_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_INTERNAL_MESSAGE_GET'"API to get an internal error.
EXPORTING
IV_GUID = "ID for the Application LOG
IMPORTING
ET_MESSAGES = "Error Message for Procurement Document Methods
IMPORTING Parameters details for BBP_EV_INTERNAL_MESSAGE_GET
IV_GUID - ID for the Application LOG
Data type: BBP_GUIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BBP_EV_INTERNAL_MESSAGE_GET
ET_MESSAGES - Error Message for Procurement Document Methods
Data type: BBPT_PD_MESSAGESOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_EV_INTERNAL_MESSAGE_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_iv_guid | TYPE BBP_GUID, " | |||
| lv_et_messages | TYPE BBPT_PD_MESSAGES. " |
|   CALL FUNCTION 'BBP_EV_INTERNAL_MESSAGE_GET' "API to get an internal error |
| EXPORTING | ||
| IV_GUID | = lv_iv_guid | |
| IMPORTING | ||
| ET_MESSAGES | = lv_et_messages | |
| . " BBP_EV_INTERNAL_MESSAGE_GET | ||
ABAP code using 7.40 inline data declarations to call FM BBP_EV_INTERNAL_MESSAGE_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.Search for further information about these or an SAP related objects