SAP FMCA_GET_TTYPENAMES Function Module for Get DDIC table typenames with a certain rowtype
FMCA_GET_TTYPENAMES is a standard fmca get ttypenames SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get DDIC table typenames with a certain rowtype 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 fmca get ttypenames FM, simply by entering the name FMCA_GET_TTYPENAMES into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_BRFPLUS_REMOTE
Program Name: SAPLFMCA_BRFPLUS_REMOTE
Main Program: SAPLFMCA_BRFPLUS_REMOTE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FMCA_GET_TTYPENAMES 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 'FMCA_GET_TTYPENAMES'"Get DDIC table typenames with a certain rowtype.
EXPORTING
IV_ROWTYPE = "Name of row type for table types
IMPORTING
ET_TTYPENAMES = "Typename
IMPORTING Parameters details for FMCA_GET_TTYPENAMES
IV_ROWTYPE - Name of row type for table types
Data type: TTROWTYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FMCA_GET_TTYPENAMES
ET_TTYPENAMES - Typename
Data type: FMCA_TTYPENAME_TOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FMCA_GET_TTYPENAMES 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_rowtype | TYPE TTROWTYPE, " | |||
| lv_et_ttypenames | TYPE FMCA_TTYPENAME_T. " |
|   CALL FUNCTION 'FMCA_GET_TTYPENAMES' "Get DDIC table typenames with a certain rowtype |
| EXPORTING | ||
| IV_ROWTYPE | = lv_iv_rowtype | |
| IMPORTING | ||
| ET_TTYPENAMES | = lv_et_ttypenames | |
| . " FMCA_GET_TTYPENAMES | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_GET_TTYPENAMES
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