SAP MCS_CENTRAL_DYNPRO_GENER Function Module for NOTRANSL: Zentraler Funktionsbaustein zur Dynprogenerierung









MCS_CENTRAL_DYNPRO_GENER is a standard mcs central dynpro gener 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: Zentraler Funktionsbaustein zur Dynprogenerierung 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 mcs central dynpro gener FM, simply by entering the name MCS_CENTRAL_DYNPRO_GENER into the relevant SAP transaction such as SE37 or SE38.

Function Group: MCSA
Program Name: SAPLMCSA
Main Program: SAPLMCSA
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MCS_CENTRAL_DYNPRO_GENER 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 'MCS_CENTRAL_DYNPRO_GENER'"NOTRANSL: Zentraler Funktionsbaustein zur Dynprogenerierung
  EXPORTING
   I_FLG_PROT =  "Log is to be displayed
   I_GSTRU =  "Table for info structure
   I_MCDYTYP =  "Type of screen, see View V_AKVER
   I_MCGEVERS =  "Current value of time stamp
   I_MCMUDYNNR =  "Number of sample screen
   I_MUPG4 =  "Program for sample screen
   I_PROGNAME =  "Program for which the screen is to be generated

TABLES
   T_MCDYNUM =  "Table of entries from MCDYNUM

EXCEPTIONS
   LOCKED = 1
.



IMPORTING Parameters details for MCS_CENTRAL_DYNPRO_GENER

I_FLG_PROT - Log is to be displayed

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

I_GSTRU - Table for info structure

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

I_MCDYTYP - Type of screen, see View V_AKVER

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

I_MCGEVERS - Current value of time stamp

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

I_MCMUDYNNR - Number of sample screen

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

I_MUPG4 - Program for sample screen

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

I_PROGNAME - Program for which the screen is to be generated

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

TABLES Parameters details for MCS_CENTRAL_DYNPRO_GENER

T_MCDYNUM - Table of entries from MCDYNUM

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

EXCEPTIONS details

LOCKED -

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

Copy and paste ABAP code example for MCS_CENTRAL_DYNPRO_GENER 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_locked  TYPE STRING, "   
lt_t_mcdynum  TYPE STANDARD TABLE OF MCDYNUM, "   
lv_i_flg_prot  TYPE XFLAG, "   
lv_i_gstru  TYPE TMC4-GSTRU, "   
lv_i_mcdytyp  TYPE MCDYNTYPEN-MCDYTYP, "   
lv_i_mcgevers  TYPE SYSAPRL, "   
lv_i_mcmudynnr  TYPE MCDYNTYPEN-MCMUDYNNR, "   
lv_i_mupg4  TYPE MCDYNTYPEN-MUPG4, "   
lv_i_progname  TYPE MCDYNUM-PROGNAME. "   

  CALL FUNCTION 'MCS_CENTRAL_DYNPRO_GENER'  "NOTRANSL: Zentraler Funktionsbaustein zur Dynprogenerierung
    EXPORTING
         I_FLG_PROT = lv_i_flg_prot
         I_GSTRU = lv_i_gstru
         I_MCDYTYP = lv_i_mcdytyp
         I_MCGEVERS = lv_i_mcgevers
         I_MCMUDYNNR = lv_i_mcmudynnr
         I_MUPG4 = lv_i_mupg4
         I_PROGNAME = lv_i_progname
    TABLES
         T_MCDYNUM = lt_t_mcdynum
    EXCEPTIONS
        LOCKED = 1
. " MCS_CENTRAL_DYNPRO_GENER




ABAP code using 7.40 inline data declarations to call FM MCS_CENTRAL_DYNPRO_GENER

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 GSTRU FROM TMC4 INTO @DATA(ld_i_gstru).
 
"SELECT single MCDYTYP FROM MCDYNTYPEN INTO @DATA(ld_i_mcdytyp).
 
 
"SELECT single MCMUDYNNR FROM MCDYNTYPEN INTO @DATA(ld_i_mcmudynnr).
 
"SELECT single MUPG4 FROM MCDYNTYPEN INTO @DATA(ld_i_mupg4).
 
"SELECT single PROGNAME FROM MCDYNUM INTO @DATA(ld_i_progname).
 


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!