SAP OBJECT_TEXT_GET_QB Function Module for NOTRANSL: Objekttext ermitteln für Sofortmaßnahme
OBJECT_TEXT_GET_QB is a standard object text get qb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Objekttext ermitteln für Sofortmaßnahme 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 object text get qb FM, simply by entering the name OBJECT_TEXT_GET_QB into the relevant SAP transaction such as SE37 or SE38.
Function Group: BOQB
Program Name: SAPLBOQB
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OBJECT_TEXT_GET_QB 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 'OBJECT_TEXT_GET_QB'"NOTRANSL: Objekttext ermitteln für Sofortmaßnahme.
EXPORTING
I_IONRA = "
* I_DATUM = SY-DATLO "
IMPORTING
E_TEXT = "
IMPORTING Parameters details for OBJECT_TEXT_GET_QB
I_IONRA -
Data type: IONRAOptional: No
Call by Reference: Yes
I_DATUM -
Data type: SY-DATLODefault: SY-DATLO
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for OBJECT_TEXT_GET_QB
E_TEXT -
Data type: SY-MSGLIOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OBJECT_TEXT_GET_QB 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_e_text | TYPE SY-MSGLI, " | |||
| lv_i_ionra | TYPE IONRA, " | |||
| lv_i_datum | TYPE SY-DATLO. " SY-DATLO |
|   CALL FUNCTION 'OBJECT_TEXT_GET_QB' "NOTRANSL: Objekttext ermitteln für Sofortmaßnahme |
| EXPORTING | ||
| I_IONRA | = lv_i_ionra | |
| I_DATUM | = lv_i_datum | |
| IMPORTING | ||
| E_TEXT | = lv_e_text | |
| . " OBJECT_TEXT_GET_QB | ||
ABAP code using 7.40 inline data declarations to call FM OBJECT_TEXT_GET_QB
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 MSGLI FROM SY INTO @DATA(ld_e_text). | ||||
| "SELECT single DATLO FROM SY INTO @DATA(ld_i_datum). | ||||
| DATA(ld_i_datum) | = SY-DATLO. | |||
Search for further information about these or an SAP related objects