SAP CORRESPONDENCE_TEXT Function Module for
CORRESPONDENCE_TEXT is a standard correspondence text SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 correspondence text FM, simply by entering the name CORRESPONDENCE_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: F022
Program Name: SAPLF022
Main Program: SAPLF022
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CORRESPONDENCE_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 'CORRESPONDENCE_TEXT'".
EXPORTING
I_BUKRS = "Company code
I_EVENT = "Correspondence
I_SPRAS = "Language key
IMPORTING
E_FUNCTION = "Indicator: processing status
E_TDNAME = "Text name
E_TDSPRAS = "Language key
E_THEAD = "SAPscript: text header
TABLES
LINES = "SAPscript: lines
EXCEPTIONS
NO_EVENT_FOUND = 1 NO_SPRAS = 2
IMPORTING Parameters details for CORRESPONDENCE_TEXT
I_BUKRS - Company code
Data type: T048B-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_EVENT - Correspondence
Data type: T048B-EVENTOptional: No
Call by Reference: No ( called with pass by value option)
I_SPRAS - Language key
Data type: RF022-SPRASOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CORRESPONDENCE_TEXT
E_FUNCTION - Indicator: processing status
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_TDNAME - Text name
Data type: THEAD-TDNAMEOptional: No
Call by Reference: No ( called with pass by value option)
E_TDSPRAS - Language key
Data type: THEAD-TDSPRASOptional: No
Call by Reference: No ( called with pass by value option)
E_THEAD - SAPscript: text header
Data type: THEADOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CORRESPONDENCE_TEXT
LINES - SAPscript: lines
Data type: TLINEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_EVENT_FOUND - No allowed correspondence type exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SPRAS - No allowed language
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CORRESPONDENCE_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: | ||||
lt_lines | TYPE STANDARD TABLE OF TLINE, " | |||
lv_i_bukrs | TYPE T048B-BUKRS, " | |||
lv_e_function | TYPE T048B, " | |||
lv_no_event_found | TYPE T048B, " | |||
lv_i_event | TYPE T048B-EVENT, " | |||
lv_e_tdname | TYPE THEAD-TDNAME, " | |||
lv_no_spras | TYPE THEAD, " | |||
lv_i_spras | TYPE RF022-SPRAS, " | |||
lv_e_tdspras | TYPE THEAD-TDSPRAS, " | |||
lv_e_thead | TYPE THEAD. " |
  CALL FUNCTION 'CORRESPONDENCE_TEXT' " |
EXPORTING | ||
I_BUKRS | = lv_i_bukrs | |
I_EVENT | = lv_i_event | |
I_SPRAS | = lv_i_spras | |
IMPORTING | ||
E_FUNCTION | = lv_e_function | |
E_TDNAME | = lv_e_tdname | |
E_TDSPRAS | = lv_e_tdspras | |
E_THEAD | = lv_e_thead | |
TABLES | ||
LINES | = lt_lines | |
EXCEPTIONS | ||
NO_EVENT_FOUND = 1 | ||
NO_SPRAS = 2 | ||
. " CORRESPONDENCE_TEXT |
ABAP code using 7.40 inline data declarations to call FM CORRESPONDENCE_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 BUKRS FROM T048B INTO @DATA(ld_i_bukrs). | ||||
"SELECT single EVENT FROM T048B INTO @DATA(ld_i_event). | ||||
"SELECT single TDNAME FROM THEAD INTO @DATA(ld_e_tdname). | ||||
"SELECT single SPRAS FROM RF022 INTO @DATA(ld_i_spras). | ||||
"SELECT single TDSPRAS FROM THEAD INTO @DATA(ld_e_tdspras). | ||||
Search for further information about these or an SAP related objects