SAP BBP_IMS_GET_EXCP_TYPE_TEXT Function Module for Ausnahmetext lesen
BBP_IMS_GET_EXCP_TYPE_TEXT is a standard bbp ims get excp type text SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Ausnahmetext lesen 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 ims get excp type text FM, simply by entering the name BBP_IMS_GET_EXCP_TYPE_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_IV_IMS
Program Name: SAPLBBP_IV_IMS
Main Program: SAPLBBP_IV_IMS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_IMS_GET_EXCP_TYPE_TEXT 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_IMS_GET_EXCP_TYPE_TEXT'"Ausnahmetext lesen.
EXPORTING
IV_EXCEPTION_TYPE = "Ereignis
* IV_LANGUAGE = "R/3 System, current language
IMPORTING
EV_EXCEPTION_TYPE_TEXT = "Ereignistext
IMPORTING Parameters details for BBP_IMS_GET_EXCP_TYPE_TEXT
IV_EXCEPTION_TYPE - Ereignis
Data type: BBP_EVENTOptional: No
Call by Reference: Yes
IV_LANGUAGE - R/3 System, current language
Data type: SY-LANGUOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_IMS_GET_EXCP_TYPE_TEXT
EV_EXCEPTION_TYPE_TEXT - Ereignistext
Data type: BBP_EVENT_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_IMS_GET_EXCP_TYPE_TEXT 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_exception_type | TYPE BBP_EVENT, " | |||
| lv_ev_exception_type_text | TYPE BBP_EVENT_T, " | |||
| lv_iv_language | TYPE SY-LANGU. " |
|   CALL FUNCTION 'BBP_IMS_GET_EXCP_TYPE_TEXT' "Ausnahmetext lesen |
| EXPORTING | ||
| IV_EXCEPTION_TYPE | = lv_iv_exception_type | |
| IV_LANGUAGE | = lv_iv_language | |
| IMPORTING | ||
| EV_EXCEPTION_TYPE_TEXT | = lv_ev_exception_type_text | |
| . " BBP_IMS_GET_EXCP_TYPE_TEXT | ||
ABAP code using 7.40 inline data declarations to call FM BBP_IMS_GET_EXCP_TYPE_TEXT
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.| "SELECT single LANGU FROM SY INTO @DATA(ld_iv_language). | ||||
Search for further information about these or an SAP related objects