SAP MCS_DYNPRO_PLAN2_GENER Function Module for NOTRANSL: Generiert bei Bedarf die Dynpros für die Planung









MCS_DYNPRO_PLAN2_GENER is a standard mcs dynpro plan2 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: Generiert bei Bedarf die Dynpros für die Planung 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 dynpro plan2 gener FM, simply by entering the name MCS_DYNPRO_PLAN2_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_DYNPRO_PLAN2_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_DYNPRO_PLAN2_GENER'"NOTRANSL: Generiert bei Bedarf die Dynpros für die Planung
EXPORTING
* I_DYNTYPEN = ' ' "Type of screen (see MCS_CENTRAL_DYNPRO_GENER)
I_GSTRU = "Table for info structure
I_MCINF = "Info structure
I_PROGNAME = "Program Name
.



IMPORTING Parameters details for MCS_DYNPRO_PLAN2_GENER

I_DYNTYPEN - Type of screen (see MCS_CENTRAL_DYNPRO_GENER)

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

I_GSTRU - Table for info structure

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

I_MCINF - Info structure

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

I_PROGNAME - Program Name

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

Copy and paste ABAP code example for MCS_DYNPRO_PLAN2_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_i_dyntypen  TYPE MCDYNTYPEN-MCDYTYP, "   SPACE
lv_i_gstru  TYPE TMC1-GSTRU, "   
lv_i_mcinf  TYPE TMC4-MCINF, "   
lv_i_progname  TYPE MCDYNUM-PROGNAME. "   

  CALL FUNCTION 'MCS_DYNPRO_PLAN2_GENER'  "NOTRANSL: Generiert bei Bedarf die Dynpros für die Planung
    EXPORTING
         I_DYNTYPEN = lv_i_dyntypen
         I_GSTRU = lv_i_gstru
         I_MCINF = lv_i_mcinf
         I_PROGNAME = lv_i_progname
. " MCS_DYNPRO_PLAN2_GENER




ABAP code using 7.40 inline data declarations to call FM MCS_DYNPRO_PLAN2_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 MCDYTYP FROM MCDYNTYPEN INTO @DATA(ld_i_dyntypen).
DATA(ld_i_dyntypen) = ' '.
 
"SELECT single GSTRU FROM TMC1 INTO @DATA(ld_i_gstru).
 
"SELECT single MCINF FROM TMC4 INTO @DATA(ld_i_mcinf).
 
"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!