UMC_BDS_DOC_UPDATE SAP Function module

UMC_BDS_DOC_UPDATE 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 UMC_BDS_DOC_UPDATE into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM UMC_BDS_DOC_UPDATE - UMC BDS DOC UPDATE

CALL FUNCTION 'UMC_BDS_DOC_UPDATE' "
  EXPORTING
    i_class = GC_CPM_CLASSNAME  " bds_clsnam
    i_doc_id =                  " bds_docid
    i_doc_ver_no =              " bds_dverno
    i_doc_var_id = GC_CPM_DOC_VAR_ID  " bds_dvarid
    it_content =                " sbdst_content
  EXCEPTIONS
    NO_DOCUMENT_FOUND = 1       "
    BDS_ERROR = 2               "
    .  "  UMC_BDS_DOC_UPDATE

ABAP code example for Function Module UMC_BDS_DOC_UPDATE

The ABAP code below is a full code listing to execute function module UMC_BDS_DOC_UPDATE 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_i_class) = 'Check type of data required'.

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

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

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

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

CALL FUNCTION 'UMC_BDS_DOC_UPDATE'
  EXPORTING
    i_class =                    ld_i_class
    i_doc_id =                   ld_i_doc_id
    i_doc_ver_no =               ld_i_doc_ver_no
    i_doc_var_id =               ld_i_doc_var_id
    it_content =                 ld_it_content
  EXCEPTIONS
    NO_DOCUMENT_FOUND =          1
    BDS_ERROR =                  2
    .  "  UMC_BDS_DOC_UPDATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
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_i_class
 
 TYPE BDS_CLSNAM ,
ld_i_doc_id
 
 TYPE BDS_DOCID ,
ld_i_doc_ver_no
 
 TYPE BDS_DVERNO ,
ld_i_doc_var_id
 
 TYPE BDS_DVARID ,
ld_it_content
 
 TYPE SBDST_CONTENT .


ld_i_class = 'Check type of data required'.
ld_i_doc_id = 'Check type of data required'.
ld_i_doc_ver_no = 'Check type of data required'.
ld_i_doc_var_id = 'Check type of data required'.
ld_it_content = 'Check type of data required'.