MEDCMM_CREATE_REVISION_MANAGER SAP Function module

MEDCMM_CREATE_REVISION_MANAGER is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name MEDCMM_CREATE_REVISION_MANAGER into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: MEDCMM
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM MEDCMM_CREATE_REVISION_MANAGER - MEDCMM CREATE REVISION MANAGER

CALL FUNCTION 'MEDCMM_CREATE_REVISION_MANAGER' "
  EXPORTING
    im_bstyp =                  " bstyp_dcm     DCM Purchasing document category
    im_bsart =                  " esart         Purchasing Document Type
*   im_ekorg =                  " ekorg         Purchasing Organization
    im_edokn =                  " edokn         DCM Object number in Purchasing
    im_persistent = MMPUR_YES   " mmpur_bool    In Database
    im_activity =               " aktyp         Activity
*   im_edokp =                  " edokp
*   im_dcm_adapter =            " if_dcm_adapter  Links Business Object to DCM
*   im_preisanz = MMPUR_YES     " preisanz      Indicator: Authorization to display price data
*   im_complete =               " complete_dcm  Version always completed
*   im_version =                " revno         Version Number in Purchasing
*   im_external =               " extreq        Externally Generated Purchase Requisition
*   im_estkz =                  " estkz         Creation Indicator (Purchase Requisition/Schedule Lines)
  IMPORTING
    ex_instance =               " if_revision_manager_dcm  DCM  Purchasing Version Management
    .  "  MEDCMM_CREATE_REVISION_MANAGER

ABAP code example for Function Module MEDCMM_CREATE_REVISION_MANAGER

The ABAP code below is a full code listing to execute function module MEDCMM_CREATE_REVISION_MANAGER including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ex_instance  
 
 TYPE IF_REVISION_MANAGER_DCM
.


DATA(ld_im_bstyp) = 'Check type of data required'.

DATA(ld_im_bsart) = 'Check type of data required'.

DATA(ld_im_ekorg) = 'Check type of data required'.

DATA(ld_im_edokn) = 'Check type of data required'.

DATA(ld_im_persistent) = 'Check type of data required'.

DATA(ld_im_activity) = 'Check type of data required'.

DATA(ld_im_edokp) = 'Check type of data required'.

DATA(ld_im_dcm_adapter) = 'Check type of data required'.

DATA(ld_im_preisanz) = 'Check type of data required'.

DATA(ld_im_complete) = 'Check type of data required'.

DATA(ld_im_version) = 'Check type of data required'.

DATA(ld_im_external) = 'Check type of data required'.

DATA(ld_im_estkz) = 'Check type of data required'.
.

CALL FUNCTION 'MEDCMM_CREATE_REVISION_MANAGER'
  EXPORTING
    im_bstyp =                   ld_im_bstyp
    im_bsart =                   ld_im_bsart
*   im_ekorg =                   ld_im_ekorg
    im_edokn =                   ld_im_edokn
    im_persistent =              ld_im_persistent
    im_activity =                ld_im_activity
*   im_edokp =                   ld_im_edokp
*   im_dcm_adapter =             ld_im_dcm_adapter
*   im_preisanz =                ld_im_preisanz
*   im_complete =                ld_im_complete
*   im_version =                 ld_im_version
*   im_external =                ld_im_external
*   im_estkz =                   ld_im_estkz
  IMPORTING
    ex_instance =                ld_ex_instance
    .  "  MEDCMM_CREATE_REVISION_MANAGER

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ex_instance
 
 TYPE IF_REVISION_MANAGER_DCM ,
ld_im_bstyp
 
 TYPE BSTYP_DCM ,
ld_im_bsart
 
 TYPE ESART ,
ld_im_ekorg
 
 TYPE EKORG ,
ld_im_edokn
 
 TYPE EDOKN ,
ld_im_persistent
 
 TYPE MMPUR_BOOL ,
ld_im_activity
 
 TYPE AKTYP ,
ld_im_edokp
 
 TYPE EDOKP ,
ld_im_dcm_adapter
 
 TYPE IF_DCM_ADAPTER ,
ld_im_preisanz
 
 TYPE PREISANZ ,
ld_im_complete
 
 TYPE COMPLETE_DCM ,
ld_im_version
 
 TYPE REVNO ,
ld_im_external
 
 TYPE EXTREQ ,
ld_im_estkz
 
 TYPE ESTKZ .


ld_im_bstyp = 'Check type of data required'.
ld_im_bsart = 'Check type of data required'.
ld_im_ekorg = 'Check type of data required'.
ld_im_edokn = 'Check type of data required'.
ld_im_persistent = 'Check type of data required'.
ld_im_activity = 'Check type of data required'.
ld_im_edokp = 'Check type of data required'.
ld_im_dcm_adapter = 'Check type of data required'.
ld_im_preisanz = 'Check type of data required'.
ld_im_complete = 'Check type of data required'.
ld_im_version = 'Check type of data required'.
ld_im_external = 'Check type of data required'.
ld_im_estkz = 'Check type of data required'.