SAP TEXT_INTERFACE_ADDON Function Module for Correspondence: Create Document (Loans)
TEXT_INTERFACE_ADDON is a standard text interface addon SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Correspondence: Create Document (Loans) 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 text interface addon FM, simply by entering the name TEXT_INTERFACE_ADDON into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVDD_ADDON
Program Name: SAPLFVDD_ADDON
Main Program: SAPLFVDD_ADDON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TEXT_INTERFACE_ADDON 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 'TEXT_INTERFACE_ADDON'"Correspondence: Create Document (Loans).
EXPORTING
* ADRTYP = ' ' "Address Category
* RANTYP = '1' "Contract Type
* STICHTAG = SY-DATUM "Datum für Ermittlung der Partner-Daten
* SUBANWDG = ' ' "Subapplication
* BRFNM = ' ' "Brief-Name
* BRIEFDATUM = SY-DATUM "Datum, das im Briefkopf gedruckt wird
* BUKRS = '0001' "Company Code
* DIALOG = ' ' "Anwender-Dialog Druckoptionen: 'X' = JA
* DRUPARM = ' ' "Print Parameters
* FPROTOKOLL = ' ' "
* PARTNR = ' ' "Partner-Nr. für Anschr.findung und Archivierung
* P_USER_EXIT = ' ' "freier Parameter für Customer Function
IMPORTING
ERGEBNIS = "Druck-Ergebnis
EXCEPTIONS
ADRESS = 1 CANCELED = 2 ELEMENT = 3 FORM = 4 OPTIONS = 5
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLFVDD_ADDON_001 User Exit for FB TEXT_INTERFACE
EXIT_SAPLFVDD_ADDON_002 User Exit for Document Selection
EXIT_SAPLFVDD_ADDON_003 User Exit for Selecting Correspondence Activities
IMPORTING Parameters details for TEXT_INTERFACE_ADDON
ADRTYP - Address Category
Data type: BU_ADRKINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
RANTYP - Contract Type
Data type: TTXBF-RANTYPDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
STICHTAG - Datum für Ermittlung der Partner-Daten
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
SUBANWDG - Subapplication
Data type: TTXBF-SUBANWDGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
BRFNM - Brief-Name
Data type: TTXBF-BRFNMDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
BRIEFDATUM - Datum, das im Briefkopf gedruckt wird
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
BUKRS - Company Code
Data type: T001-BUKRSDefault: '0001'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DIALOG - Anwender-Dialog Druckoptionen: 'X' = JA
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DRUPARM - Print Parameters
Data type: ITCPODefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FPROTOKOLL -
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
PARTNR - Partner-Nr. für Anschr.findung und Archivierung
Data type: BU_PARTNERDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
P_USER_EXIT - freier Parameter für Customer Function
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TEXT_INTERFACE_ADDON
ERGEBNIS - Druck-Ergebnis
Data type: ITCPPOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ADRESS - Partner-Anschrift nicht gefunden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANCELED - Cancelled by user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ELEMENT - Textelement oder -baustein nicht gefunden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FORM - ungültiges Formular
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OPTIONS - ungültige Druckoptionen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TEXT_INTERFACE_ADDON 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_adress | TYPE STRING, " | |||
| lv_adrtyp | TYPE BU_ADRKIND, " SPACE | |||
| lv_ergebnis | TYPE ITCPP, " | |||
| lv_rantyp | TYPE TTXBF-RANTYP, " '1' | |||
| lv_stichtag | TYPE SY-DATUM, " SY-DATUM | |||
| lv_subanwdg | TYPE TTXBF-SUBANWDG, " ' ' | |||
| lv_brfnm | TYPE TTXBF-BRFNM, " ' ' | |||
| lv_canceled | TYPE TTXBF, " | |||
| lv_element | TYPE TTXBF, " | |||
| lv_briefdatum | TYPE SY-DATUM, " SY-DATUM | |||
| lv_form | TYPE SY, " | |||
| lv_bukrs | TYPE T001-BUKRS, " '0001' | |||
| lv_dialog | TYPE T001, " SPACE | |||
| lv_options | TYPE T001, " | |||
| lv_druparm | TYPE ITCPO, " SPACE | |||
| lv_fprotokoll | TYPE ITCPO, " ' ' | |||
| lv_partnr | TYPE BU_PARTNER, " SPACE | |||
| lv_p_user_exit | TYPE BU_PARTNER. " ' ' |
|   CALL FUNCTION 'TEXT_INTERFACE_ADDON' "Correspondence: Create Document (Loans) |
| EXPORTING | ||
| ADRTYP | = lv_adrtyp | |
| RANTYP | = lv_rantyp | |
| STICHTAG | = lv_stichtag | |
| SUBANWDG | = lv_subanwdg | |
| BRFNM | = lv_brfnm | |
| BRIEFDATUM | = lv_briefdatum | |
| BUKRS | = lv_bukrs | |
| DIALOG | = lv_dialog | |
| DRUPARM | = lv_druparm | |
| FPROTOKOLL | = lv_fprotokoll | |
| PARTNR | = lv_partnr | |
| P_USER_EXIT | = lv_p_user_exit | |
| IMPORTING | ||
| ERGEBNIS | = lv_ergebnis | |
| EXCEPTIONS | ||
| ADRESS = 1 | ||
| CANCELED = 2 | ||
| ELEMENT = 3 | ||
| FORM = 4 | ||
| OPTIONS = 5 | ||
| . " TEXT_INTERFACE_ADDON | ||
ABAP code using 7.40 inline data declarations to call FM TEXT_INTERFACE_ADDON
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.| DATA(ld_adrtyp) | = ' '. | |||
| "SELECT single RANTYP FROM TTXBF INTO @DATA(ld_rantyp). | ||||
| DATA(ld_rantyp) | = '1'. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_stichtag). | ||||
| DATA(ld_stichtag) | = SY-DATUM. | |||
| "SELECT single SUBANWDG FROM TTXBF INTO @DATA(ld_subanwdg). | ||||
| DATA(ld_subanwdg) | = ' '. | |||
| "SELECT single BRFNM FROM TTXBF INTO @DATA(ld_brfnm). | ||||
| DATA(ld_brfnm) | = ' '. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_briefdatum). | ||||
| DATA(ld_briefdatum) | = SY-DATUM. | |||
| "SELECT single BUKRS FROM T001 INTO @DATA(ld_bukrs). | ||||
| DATA(ld_bukrs) | = '0001'. | |||
| DATA(ld_dialog) | = ' '. | |||
| DATA(ld_druparm) | = ' '. | |||
| DATA(ld_fprotokoll) | = ' '. | |||
| DATA(ld_partnr) | = ' '. | |||
| DATA(ld_p_user_exit) | = ' '. | |||
Search for further information about these or an SAP related objects