SAP DX_SEP_TAB_FLD_NAME Function Module for
DX_SEP_TAB_FLD_NAME is a standard dx sep tab fld name 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 dx sep tab fld name FM, simply by entering the name DX_SEP_TAB_FLD_NAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: DX_TOOLS_MAP
Program Name: SAPLDX_TOOLS_MAP
Main Program: SAPLDX_TOOLS_MAP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DX_SEP_TAB_FLD_NAME 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 'DX_SEP_TAB_FLD_NAME'".
EXPORTING
FIELDNAME = "Field name
IMPORTING
TABLE_NAME = "Table Name
FIELD_NAME = "Field name
EXCEPTIONS
ERROR_SPLITING_FIELD = 1
IMPORTING Parameters details for DX_SEP_TAB_FLD_NAME
FIELDNAME - Field name
Data type: BDCDF-FIELDNAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for DX_SEP_TAB_FLD_NAME
TABLE_NAME - Table Name
Data type: DCOBJDEF-NAMEOptional: No
Call by Reference: Yes
FIELD_NAME - Field name
Data type: DFIES-FIELDNAMEOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_SPLITING_FIELD -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DX_SEP_TAB_FLD_NAME 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_fieldname | TYPE BDCDF-FIELDNAME, " | |||
| lv_table_name | TYPE DCOBJDEF-NAME, " | |||
| lv_error_spliting_field | TYPE DCOBJDEF, " | |||
| lv_field_name | TYPE DFIES-FIELDNAME. " |
|   CALL FUNCTION 'DX_SEP_TAB_FLD_NAME' " |
| EXPORTING | ||
| FIELDNAME | = lv_fieldname | |
| IMPORTING | ||
| TABLE_NAME | = lv_table_name | |
| FIELD_NAME | = lv_field_name | |
| EXCEPTIONS | ||
| ERROR_SPLITING_FIELD = 1 | ||
| . " DX_SEP_TAB_FLD_NAME | ||
ABAP code using 7.40 inline data declarations to call FM DX_SEP_TAB_FLD_NAME
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.| "SELECT single FIELDNAME FROM BDCDF INTO @DATA(ld_fieldname). | ||||
| "SELECT single NAME FROM DCOBJDEF INTO @DATA(ld_table_name). | ||||
| "SELECT single FIELDNAME FROM DFIES INTO @DATA(ld_field_name). | ||||
Search for further information about these or an SAP related objects