SAP DYN_FIELD_CATALOG_F4 Function Module for NOTRANSL: Dynamische Felder: Feldkatalog als F4-Hilfe bringen









DYN_FIELD_CATALOG_F4 is a standard dyn field catalog f4 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: Dynamische Felder: Feldkatalog als F4-Hilfe bringen 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 dyn field catalog f4 FM, simply by entering the name DYN_FIELD_CATALOG_F4 into the relevant SAP transaction such as SE37 or SE38.

Function Group: V56M
Program Name: SAPLV56M
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DYN_FIELD_CATALOG_F4 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 'DYN_FIELD_CATALOG_F4'"NOTRANSL: Dynamische Felder: Feldkatalog als F4-Hilfe bringen
CHANGING
* C_TABLE = "DE-EN-LANG-SWITCH-NO-TRANSLATION
C_FIELD = "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
FIELD_CATALOG_EMPTY = 1
.




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_SAPLV56M_001 Collective Processing for Shipment: Enhancement of Field Catalog
EXIT_SAPLV56M_002 Collective Processing Shipment: Assign Deliveries to Shipments
EXIT_SAPLV56M_003 Collective Processing Shipment: Filling Generated Shipment Docs with Data

CHANGING Parameters details for DYN_FIELD_CATALOG_F4

C_TABLE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: DFIES-TABNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

C_FIELD - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: DFIES-FIELDNAME
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

FIELD_CATALOG_EMPTY - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for DYN_FIELD_CATALOG_F4 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_c_table  TYPE DFIES-TABNAME, "   
lv_field_catalog_empty  TYPE DFIES, "   
lv_c_field  TYPE DFIES-FIELDNAME. "   

  CALL FUNCTION 'DYN_FIELD_CATALOG_F4'  "NOTRANSL: Dynamische Felder: Feldkatalog als F4-Hilfe bringen
    CHANGING
         C_TABLE = lv_c_table
         C_FIELD = lv_c_field
    EXCEPTIONS
        FIELD_CATALOG_EMPTY = 1
. " DYN_FIELD_CATALOG_F4




ABAP code using 7.40 inline data declarations to call FM DYN_FIELD_CATALOG_F4

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 TABNAME FROM DFIES INTO @DATA(ld_c_table).
 
 
"SELECT single FIELDNAME FROM DFIES INTO @DATA(ld_c_field).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!