SAP UMR_DM_CATEGORY_UPDATE Function Module for









UMR_DM_CATEGORY_UPDATE is a standard umr dm category update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 umr dm category update FM, simply by entering the name UMR_DM_CATEGORY_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function UMR_DM_CATEGORY_UPDATE 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 'UMR_DM_CATEGORY_UPDATE'"
EXPORTING
* I_ACTION = 'CHANGE' "
* IR_RBTREE = "
* IT_BDS = "
* I_BDS_UFLG = ' ' "

IMPORTING
ET_BDS = "

CHANGING
CS_CATEGORY = "

EXCEPTIONS
INVALID_PARAMETER = 1 FAILED = 2
.



IMPORTING Parameters details for UMR_DM_CATEGORY_UPDATE

I_ACTION -

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

IR_RBTREE -

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

IT_BDS -

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

I_BDS_UFLG -

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

EXPORTING Parameters details for UMR_DM_CATEGORY_UPDATE

ET_BDS -

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

CHANGING Parameters details for UMR_DM_CATEGORY_UPDATE

CS_CATEGORY -

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

EXCEPTIONS details

INVALID_PARAMETER -

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

FAILED -

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

Copy and paste ABAP code example for UMR_DM_CATEGORY_UPDATE 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_et_bds  TYPE SBDST_CONTENT, "   
lv_i_action  TYPE SBDST_CONTENT, "   'CHANGE'
lv_cs_category  TYPE UMR_YS_RCATG, "   
lv_invalid_parameter  TYPE UMR_YS_RCATG, "   
lv_failed  TYPE UMR_YS_RCATG, "   
lv_ir_rbtree  TYPE CL_UMR_RISK_TREE, "   
lv_it_bds  TYPE SBDST_CONTENT, "   
lv_i_bds_uflg  TYPE UMC_Y_YES_NO. "   SPACE

  CALL FUNCTION 'UMR_DM_CATEGORY_UPDATE'  "
    EXPORTING
         I_ACTION = lv_i_action
         IR_RBTREE = lv_ir_rbtree
         IT_BDS = lv_it_bds
         I_BDS_UFLG = lv_i_bds_uflg
    IMPORTING
         ET_BDS = lv_et_bds
    CHANGING
         CS_CATEGORY = lv_cs_category
    EXCEPTIONS
        INVALID_PARAMETER = 1
        FAILED = 2
. " UMR_DM_CATEGORY_UPDATE




ABAP code using 7.40 inline data declarations to call FM UMR_DM_CATEGORY_UPDATE

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.

 
DATA(ld_i_action) = 'CHANGE'.
 
 
 
 
 
 
DATA(ld_i_bds_uflg) = ' '.
 


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!