SAP CATS_CONVERT_LONGTEXT Function Module for NOTRANSL: Konvertierung des Langtextes in gängige Textformate
CATS_CONVERT_LONGTEXT is a standard cats convert longtext 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: Konvertierung des Langtextes in gängige Textformate 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 cats convert longtext FM, simply by entering the name CATS_CONVERT_LONGTEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CATS
Program Name: SAPLCATS
Main Program: SAPLCATS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CATS_CONVERT_LONGTEXT 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 'CATS_CONVERT_LONGTEXT'"NOTRANSL: Konvertierung des Langtextes in gängige Textformate.
EXPORTING
CATS_TEXT_FORMAT = "Text Format for Long Text
DIRECTION = "
* TEXT_HEADER = "SAPscript: Text Header
TABLES
IT_LONGTEXT_ITF = "SAPscript: Text Lines
IT_LONGTEXT_FOR = "SAPscript: Text Lines
EXCEPTIONS
WRONG_DIRECTION = 1 WRONG_TEXT_FORMAT = 2
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_SAPLCATS_001 CATS: Set Up Worklist
EXIT_SAPLCATS_002 CATS: Supplement Recorded Data
EXIT_SAPLCATS_003 CATS: Validate Recorded Data
EXIT_SAPLCATS_004 CATS: Deactivate Functions in the User Interface
EXIT_SAPLCATS_005 CATS: Export Data to Customer Dialog Box
EXIT_SAPLCATS_006 CATS: Validate Entire Time Sheet
EXIT_SAPLCATS_007 CATS: Determine Workflow Recipients for Approval
EXIT_SAPLCATS_008 CATS: Import Data from Customer Dialog Box
EXIT_SAPLCATS_009 CATS: Customer-Specific Text Fields in Data Entry Section
EXIT_SAPLCATS_010 CATS: Customer-Specific Text Fields in Worklist
EXIT_SAPLCATS_011 CATS: Customer Functions in Initial Screen/Data Entry Screen Menus
EXIT_SAPLCATS_012 CATS: Export Data to Customer Subscreen for Header Information
EXIT_SAPLCATS_MY_003 Supplement Offline Time Data
EXIT_SAPLCATS_MY_004 Influence Messages from Synchronization
IMPORTING Parameters details for CATS_CONVERT_LONGTEXT
CATS_TEXT_FORMAT - Text Format for Long Text
Data type: CATS_TEXT_FORMATOptional: No
Call by Reference: No ( called with pass by value option)
DIRECTION -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TEXT_HEADER - SAPscript: Text Header
Data type: THEADOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CATS_CONVERT_LONGTEXT
IT_LONGTEXT_ITF - SAPscript: Text Lines
Data type: TLINEOptional: No
Call by Reference: Yes
IT_LONGTEXT_FOR - SAPscript: Text Lines
Data type: TLINEOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_DIRECTION -
Data type:Optional: No
Call by Reference: Yes
WRONG_TEXT_FORMAT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CATS_CONVERT_LONGTEXT 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_it_longtext_itf | TYPE STANDARD TABLE OF TLINE, " | |||
| lv_wrong_direction | TYPE TLINE, " | |||
| lv_cats_text_format | TYPE CATS_TEXT_FORMAT, " | |||
| lv_direction | TYPE C, " | |||
| lt_it_longtext_for | TYPE STANDARD TABLE OF TLINE, " | |||
| lv_wrong_text_format | TYPE TLINE, " | |||
| lv_text_header | TYPE THEAD. " |
|   CALL FUNCTION 'CATS_CONVERT_LONGTEXT' "NOTRANSL: Konvertierung des Langtextes in gängige Textformate |
| EXPORTING | ||
| CATS_TEXT_FORMAT | = lv_cats_text_format | |
| DIRECTION | = lv_direction | |
| TEXT_HEADER | = lv_text_header | |
| TABLES | ||
| IT_LONGTEXT_ITF | = lt_it_longtext_itf | |
| IT_LONGTEXT_FOR | = lt_it_longtext_for | |
| EXCEPTIONS | ||
| WRONG_DIRECTION = 1 | ||
| WRONG_TEXT_FORMAT = 2 | ||
| . " CATS_CONVERT_LONGTEXT | ||
ABAP code using 7.40 inline data declarations to call FM CATS_CONVERT_LONGTEXT
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.Search for further information about these or an SAP related objects