SAP CM_DE_CALL_DETAIL Function Module for Call up the detail screen for a material component allocation









CM_DE_CALL_DETAIL is a standard cm de call detail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call up the detail screen for a material component allocation 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 cm de call detail FM, simply by entering the name CM_DE_CALL_DETAIL into the relevant SAP transaction such as SE37 or SE38.

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



Function CM_DE_CALL_DETAIL 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 'CM_DE_CALL_DETAIL'"Call up the detail screen for a material component allocation
  EXPORTING
   DYNNR =  "Screen number
*  WINX1 = 0 "X-coordinate 1 (left) of window
*  WINX2 = 0 "X-coordinate 2 (right) of window
*  WINY1 = 0 "Y-coordinate 1 (above) of window
*  WINY2 = 0 "Y-coordinate 2 (below) of window
*  FLG_DUMMY =  "Indicator: allocations to an operation
   PLKOD_IMP =  "I/O table for task list headers
*  MAST_IMP =  "Material to BOM Link
*  KDST_IMP =  "Sales Order to BOM Link
*  PRST_IMP =  "Project - BOM link
   FBLDGR =  "Subsequent screen group
   FPANEL =  "Description of the subsequent screen
   PLMZD_IMP =  "I/O structure for material component alloctions
   PLPOD_IMP =  "I/O table for task list operations and network activities
   RC29P_IMP =  "EATAB BOM Items
   RCM01_IMP =  "Global fields of material component assignment
*  RCR01_IMP = ' ' "View of Work Center from Task Lists
   STKO_IMP =  "BOM Header

 IMPORTING
   OK_CODE =  "Function Code
   PLMZD_EXP =  "I/O structure for material component alloctions
.



IMPORTING Parameters details for CM_DE_CALL_DETAIL

DYNNR - Screen number

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

WINX1 - X-coordinate 1 (left) of window

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

WINX2 - X-coordinate 2 (right) of window

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

WINY1 - Y-coordinate 1 (above) of window

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

WINY2 - Y-coordinate 2 (below) of window

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

FLG_DUMMY - Indicator: allocations to an operation

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

PLKOD_IMP - I/O table for task list headers

Data type: PLKOD
Optional: No
Call by Reference: Yes

MAST_IMP - Material to BOM Link

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

KDST_IMP - Sales Order to BOM Link

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

PRST_IMP - Project - BOM link

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

FBLDGR - Subsequent screen group

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

FPANEL - Description of the subsequent screen

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

PLMZD_IMP - I/O structure for material component alloctions

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

PLPOD_IMP - I/O table for task list operations and network activities

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

RC29P_IMP - EATAB BOM Items

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

RCM01_IMP - Global fields of material component assignment

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

RCR01_IMP - View of Work Center from Task Lists

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

STKO_IMP - BOM Header

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

EXPORTING Parameters details for CM_DE_CALL_DETAIL

OK_CODE - Function Code

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

PLMZD_EXP - I/O structure for material component alloctions

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

Copy and paste ABAP code example for CM_DE_CALL_DETAIL 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_dynnr  TYPE T185V-DYNNR, "   
lv_ok_code  TYPE T185-FCODE, "   
lv_winx1  TYPE T185V-WINX1, "   0
lv_winx2  TYPE T185V-WINX2, "   0
lv_winy1  TYPE T185V-WINY1, "   0
lv_winy2  TYPE T185V-WINY2, "   0
lv_flg_dummy  TYPE RCM01-FLG_PROV, "   
lv_plkod_imp  TYPE PLKOD, "   
lv_mast_imp  TYPE MAST, "   
lv_kdst_imp  TYPE KDST, "   
lv_prst_imp  TYPE PRST, "   
lv_fbldgr  TYPE T185-FBLDGR, "   
lv_plmzd_exp  TYPE PLMZD, "   
lv_fpanel  TYPE T185-FPANEL, "   
lv_plmzd_imp  TYPE PLMZD, "   
lv_plpod_imp  TYPE PLPOD, "   
lv_rc29p_imp  TYPE RC29P, "   
lv_rcm01_imp  TYPE RCM01, "   
lv_rcr01_imp  TYPE RCR01, "   SPACE
lv_stko_imp  TYPE STKO. "   

  CALL FUNCTION 'CM_DE_CALL_DETAIL'  "Call up the detail screen for a material component allocation
    EXPORTING
         DYNNR = lv_dynnr
         WINX1 = lv_winx1
         WINX2 = lv_winx2
         WINY1 = lv_winy1
         WINY2 = lv_winy2
         FLG_DUMMY = lv_flg_dummy
         PLKOD_IMP = lv_plkod_imp
         MAST_IMP = lv_mast_imp
         KDST_IMP = lv_kdst_imp
         PRST_IMP = lv_prst_imp
         FBLDGR = lv_fbldgr
         FPANEL = lv_fpanel
         PLMZD_IMP = lv_plmzd_imp
         PLPOD_IMP = lv_plpod_imp
         RC29P_IMP = lv_rc29p_imp
         RCM01_IMP = lv_rcm01_imp
         RCR01_IMP = lv_rcr01_imp
         STKO_IMP = lv_stko_imp
    IMPORTING
         OK_CODE = lv_ok_code
         PLMZD_EXP = lv_plmzd_exp
. " CM_DE_CALL_DETAIL




ABAP code using 7.40 inline data declarations to call FM CM_DE_CALL_DETAIL

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 DYNNR FROM T185V INTO @DATA(ld_dynnr).
 
"SELECT single FCODE FROM T185 INTO @DATA(ld_ok_code).
 
"SELECT single WINX1 FROM T185V INTO @DATA(ld_winx1).
 
"SELECT single WINX2 FROM T185V INTO @DATA(ld_winx2).
 
"SELECT single WINY1 FROM T185V INTO @DATA(ld_winy1).
 
"SELECT single WINY2 FROM T185V INTO @DATA(ld_winy2).
 
"SELECT single FLG_PROV FROM RCM01 INTO @DATA(ld_flg_dummy).
 
 
 
 
 
"SELECT single FBLDGR FROM T185 INTO @DATA(ld_fbldgr).
 
 
"SELECT single FPANEL FROM T185 INTO @DATA(ld_fpanel).
 
 
 
 
 
DATA(ld_rcr01_imp) = ' '.
 
 


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!