SAP IBAPI_Z_LONGTEXT_READ Function Module for NOTRANSL: Liest den Langtext zu einem Auftragsobjekt
IBAPI_Z_LONGTEXT_READ is a standard ibapi z longtext read 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: Liest den Langtext zu einem Auftragsobjekt 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 ibapi z longtext read FM, simply by entering the name IBAPI_Z_LONGTEXT_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: IBAPI_Z
Program Name: SAPLIBAPI_Z
Main Program: SAPLIBAPI_Z
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IBAPI_Z_LONGTEXT_READ 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 'IBAPI_Z_LONGTEXT_READ'"NOTRANSL: Liest den Langtext zu einem Auftragsobjekt.
EXPORTING
* IV_SPRAS = SYST-LANGU "SAP System, Current Language
* IV_AUFNR = "Order Number
* IV_VORNR = "Operation Number
* IV_UVORN = "Suboperation
* IV_RSNUM = "Number of Reservation / Dependent Requirement
* IV_RSPOS = "Item Number of Reservation/Dependent Requirement
* IV_RSART = "Record Type
IMPORTING
ES_HEADER = "SAPscript: Text Header
TABLES
ET_LINES = "Lines of ITF
EXCEPTIONS
OBJECT_HAS_NO_LONGTEXT = 1 TEXT_NOT_FOUND = 2 READ_ERROR = 3
IMPORTING Parameters details for IBAPI_Z_LONGTEXT_READ
IV_SPRAS - SAP System, Current Language
Data type: SYST-LANGUDefault: SYST-LANGU
Optional: Yes
Call by Reference: Yes
IV_AUFNR - Order Number
Data type: CAUFVD-AUFNROptional: Yes
Call by Reference: Yes
IV_VORNR - Operation Number
Data type: AFVGD-VORNROptional: Yes
Call by Reference: Yes
IV_UVORN - Suboperation
Data type: AFVGD-UVORNOptional: Yes
Call by Reference: Yes
IV_RSNUM - Number of Reservation / Dependent Requirement
Data type: RESBD-RSNUMOptional: Yes
Call by Reference: Yes
IV_RSPOS - Item Number of Reservation/Dependent Requirement
Data type: RESBD-RSPOSOptional: Yes
Call by Reference: Yes
IV_RSART - Record Type
Data type: RESBD-RSARTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for IBAPI_Z_LONGTEXT_READ
ES_HEADER - SAPscript: Text Header
Data type: THEADOptional: No
Call by Reference: Yes
TABLES Parameters details for IBAPI_Z_LONGTEXT_READ
ET_LINES - Lines of ITF
Data type: TLINETABOptional: No
Call by Reference: Yes
EXCEPTIONS details
OBJECT_HAS_NO_LONGTEXT -
Data type:Optional: No
Call by Reference: Yes
TEXT_NOT_FOUND - Long text not found
Data type:Optional: No
Call by Reference: Yes
READ_ERROR - Error Reading the Object
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IBAPI_Z_LONGTEXT_READ 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: | ||||
| lt_et_lines | TYPE STANDARD TABLE OF TLINETAB, " | |||
| lv_iv_spras | TYPE SYST-LANGU, " SYST-LANGU | |||
| lv_es_header | TYPE THEAD, " | |||
| lv_object_has_no_longtext | TYPE THEAD, " | |||
| lv_iv_aufnr | TYPE CAUFVD-AUFNR, " | |||
| lv_text_not_found | TYPE CAUFVD, " | |||
| lv_iv_vornr | TYPE AFVGD-VORNR, " | |||
| lv_read_error | TYPE AFVGD, " | |||
| lv_iv_uvorn | TYPE AFVGD-UVORN, " | |||
| lv_iv_rsnum | TYPE RESBD-RSNUM, " | |||
| lv_iv_rspos | TYPE RESBD-RSPOS, " | |||
| lv_iv_rsart | TYPE RESBD-RSART. " |
|   CALL FUNCTION 'IBAPI_Z_LONGTEXT_READ' "NOTRANSL: Liest den Langtext zu einem Auftragsobjekt |
| EXPORTING | ||
| IV_SPRAS | = lv_iv_spras | |
| IV_AUFNR | = lv_iv_aufnr | |
| IV_VORNR | = lv_iv_vornr | |
| IV_UVORN | = lv_iv_uvorn | |
| IV_RSNUM | = lv_iv_rsnum | |
| IV_RSPOS | = lv_iv_rspos | |
| IV_RSART | = lv_iv_rsart | |
| IMPORTING | ||
| ES_HEADER | = lv_es_header | |
| TABLES | ||
| ET_LINES | = lt_et_lines | |
| EXCEPTIONS | ||
| OBJECT_HAS_NO_LONGTEXT = 1 | ||
| TEXT_NOT_FOUND = 2 | ||
| READ_ERROR = 3 | ||
| . " IBAPI_Z_LONGTEXT_READ | ||
ABAP code using 7.40 inline data declarations to call FM IBAPI_Z_LONGTEXT_READ
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 SYST INTO @DATA(ld_iv_spras). | ||||
| DATA(ld_iv_spras) | = SYST-LANGU. | |||
| "SELECT single AUFNR FROM CAUFVD INTO @DATA(ld_iv_aufnr). | ||||
| "SELECT single VORNR FROM AFVGD INTO @DATA(ld_iv_vornr). | ||||
| "SELECT single UVORN FROM AFVGD INTO @DATA(ld_iv_uvorn). | ||||
| "SELECT single RSNUM FROM RESBD INTO @DATA(ld_iv_rsnum). | ||||
| "SELECT single RSPOS FROM RESBD INTO @DATA(ld_iv_rspos). | ||||
| "SELECT single RSART FROM RESBD INTO @DATA(ld_iv_rsart). | ||||
Search for further information about these or an SAP related objects