SAP COM_TEXT_READ_PROC_ALL_API Function Module for
COM_TEXT_READ_PROC_ALL_API is a standard com text read proc all api 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 com text read proc all api FM, simply by entering the name COM_TEXT_READ_PROC_ALL_API into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_TEXT_API
Program Name: SAPLCOM_TEXT_API
Main Program: SAPLCOM_TEXT_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COM_TEXT_READ_PROC_ALL_API 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 'COM_TEXT_READ_PROC_ALL_API'".
EXPORTING
IV_OBJECT = "TextObject
IV_PROCEDURE = "Text Determination Procedure
IV_TDNAME = "Text Name
* IT_PKEY1 = "Table for Text Name(s) and Language(s)
* IT_COMSTRUC_FIELDTAB = "Table with Field/Value for Communication
* IV_KEY_IS_NEW = "
* IT_TEXTDATA = "Text Keys and Line(s)
* IV_HIST = "
* IV_CONTROLLER = "
IMPORTING
ET_TEXTDATA = "Text Keys and Line(s)
ET_ERROR = "
ET_TTXIT = "
TABLES
* ET_TEXT_DEL = "
IMPORTING Parameters details for COM_TEXT_READ_PROC_ALL_API
IV_OBJECT - TextObject
Data type: COMT_TEXT_TEXTOBJECTOptional: No
Call by Reference: Yes
IV_PROCEDURE - Text Determination Procedure
Data type: COMT_TEXT_DET_PROCEDUREOptional: No
Call by Reference: Yes
IV_TDNAME - Text Name
Data type: TDOBNAMEOptional: No
Call by Reference: Yes
IT_PKEY1 - Table for Text Name(s) and Language(s)
Data type: COMT_TEXT_PKEY1_TOptional: Yes
Call by Reference: Yes
IT_COMSTRUC_FIELDTAB - Table with Field/Value for Communication
Data type: COMT_TEXT_FIELD_VALUE_TABOptional: Yes
Call by Reference: Yes
IV_KEY_IS_NEW -
Data type: BOOLE_DOptional: Yes
Call by Reference: Yes
IT_TEXTDATA - Text Keys and Line(s)
Data type: COMT_TEXT_TEXTDATA_TOptional: Yes
Call by Reference: Yes
IV_HIST -
Data type:Optional: Yes
Call by Reference: Yes
IV_CONTROLLER -
Data type:Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for COM_TEXT_READ_PROC_ALL_API
ET_TEXTDATA - Text Keys and Line(s)
Data type: COMT_TEXT_TEXTDATA_TOptional: No
Call by Reference: Yes
ET_ERROR -
Data type: COMT_TEXT_ERROR_TOptional: No
Call by Reference: Yes
ET_TTXIT -
Data type: COMT_TEXT_TTXIT_TABOptional: No
Call by Reference: Yes
TABLES Parameters details for COM_TEXT_READ_PROC_ALL_API
ET_TEXT_DEL -
Data type: TCATALOGOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for COM_TEXT_READ_PROC_ALL_API 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_iv_object | TYPE COMT_TEXT_TEXTOBJECT, " | |||
| lv_et_textdata | TYPE COMT_TEXT_TEXTDATA_T, " | |||
| lt_et_text_del | TYPE STANDARD TABLE OF TCATALOG, " | |||
| lv_et_error | TYPE COMT_TEXT_ERROR_T, " | |||
| lv_iv_procedure | TYPE COMT_TEXT_DET_PROCEDURE, " | |||
| lv_et_ttxit | TYPE COMT_TEXT_TTXIT_TAB, " | |||
| lv_iv_tdname | TYPE TDOBNAME, " | |||
| lv_it_pkey1 | TYPE COMT_TEXT_PKEY1_T, " | |||
| lv_it_comstruc_fieldtab | TYPE COMT_TEXT_FIELD_VALUE_TAB, " | |||
| lv_iv_key_is_new | TYPE BOOLE_D, " | |||
| lv_it_textdata | TYPE COMT_TEXT_TEXTDATA_T, " | |||
| lv_iv_hist | TYPE COMT_TEXT_TEXTDATA_T, " | |||
| lv_iv_controller | TYPE COMT_TEXT_TEXTDATA_T. " |
|   CALL FUNCTION 'COM_TEXT_READ_PROC_ALL_API' " |
| EXPORTING | ||
| IV_OBJECT | = lv_iv_object | |
| IV_PROCEDURE | = lv_iv_procedure | |
| IV_TDNAME | = lv_iv_tdname | |
| IT_PKEY1 | = lv_it_pkey1 | |
| IT_COMSTRUC_FIELDTAB | = lv_it_comstruc_fieldtab | |
| IV_KEY_IS_NEW | = lv_iv_key_is_new | |
| IT_TEXTDATA | = lv_it_textdata | |
| IV_HIST | = lv_iv_hist | |
| IV_CONTROLLER | = lv_iv_controller | |
| IMPORTING | ||
| ET_TEXTDATA | = lv_et_textdata | |
| ET_ERROR | = lv_et_error | |
| ET_TTXIT | = lv_et_ttxit | |
| TABLES | ||
| ET_TEXT_DEL | = lt_et_text_del | |
| . " COM_TEXT_READ_PROC_ALL_API | ||
ABAP code using 7.40 inline data declarations to call FM COM_TEXT_READ_PROC_ALL_API
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