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

Function FDM_COM_TEXTIDS_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 'FDM_COM_TEXTIDS_READ'".
EXPORTING
* I_LANGU = SY-LANGU "Language Key
I_CASE_TYPE = "FSCM-DM: Case Type
IMPORTING
ET_TEXT_ID = "
IMPORTING Parameters details for FDM_COM_TEXTIDS_READ
I_LANGU - Language Key
Data type: LANGUDefault: SY-LANGU
Optional: No
Call by Reference: Yes
I_CASE_TYPE - FSCM-DM: Case Type
Data type: BDM_CASE_TYPEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FDM_COM_TEXTIDS_READ
ET_TEXT_ID -
Data type: BDM_T_TEXT_IDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FDM_COM_TEXTIDS_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: | ||||
| lv_i_langu | TYPE LANGU, " SY-LANGU | |||
| lv_et_text_id | TYPE BDM_T_TEXT_ID, " | |||
| lv_i_case_type | TYPE BDM_CASE_TYPE. " |
|   CALL FUNCTION 'FDM_COM_TEXTIDS_READ' " |
| EXPORTING | ||
| I_LANGU | = lv_i_langu | |
| I_CASE_TYPE | = lv_i_case_type | |
| IMPORTING | ||
| ET_TEXT_ID | = lv_et_text_id | |
| . " FDM_COM_TEXTIDS_READ | ||
ABAP code using 7.40 inline data declarations to call FM FDM_COM_TEXTIDS_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.| DATA(ld_i_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects