SAP UMM_DOCUMENT_UPDATE Function Module for









UMM_DOCUMENT_UPDATE is a standard umm document 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 umm document update FM, simply by entering the name UMM_DOCUMENT_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function UMM_DOCUMENT_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 'UMM_DOCUMENT_UPDATE'"
EXPORTING
I_OBJTYPE = "
I_OBJNAME = "
IT_CONTENT = "

EXCEPTIONS
NO_DOCUMENT_FOUND = 1 BDS_ERROR = 2
.



IMPORTING Parameters details for UMM_DOCUMENT_UPDATE

I_OBJTYPE -

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

I_OBJNAME -

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

IT_CONTENT -

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

EXCEPTIONS details

NO_DOCUMENT_FOUND -

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

BDS_ERROR -

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

Copy and paste ABAP code example for UMM_DOCUMENT_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_i_objtype  TYPE UMM_Y_OBJTYPE, "   
lv_no_document_found  TYPE UMM_Y_OBJTYPE, "   
lv_bds_error  TYPE UMM_Y_OBJTYPE, "   
lv_i_objname  TYPE UMM_Y_OBJNAME, "   
lv_it_content  TYPE SBDST_CONTENT. "   

  CALL FUNCTION 'UMM_DOCUMENT_UPDATE'  "
    EXPORTING
         I_OBJTYPE = lv_i_objtype
         I_OBJNAME = lv_i_objname
         IT_CONTENT = lv_it_content
    EXCEPTIONS
        NO_DOCUMENT_FOUND = 1
        BDS_ERROR = 2
. " UMM_DOCUMENT_UPDATE




ABAP code using 7.40 inline data declarations to call FM UMM_DOCUMENT_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.

 
 
 
 
 


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!