UMC_BDS_DOC_CREATE SAP Function module

UMC_BDS_DOC_CREATE 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_CREATE 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_CREATE - UMC BDS DOC CREATE

CALL FUNCTION 'UMC_BDS_DOC_CREATE' "
  EXPORTING
    i_class = GC_CPM_CLASSNAME  " bds_clsnam
    is_ok =                     " umc_ys_objectkey
    i_description =             " bds_propva
*   i_langu = SY-LANGU          " sy-langu
*   i_multiple_doc = ''         " as4flag
    it_content =                " sbdst_content
  IMPORTING
    e_doc_id =                  " bds_docid
  EXCEPTIONS
    DOCUMENT_ALREADY_EXISTS = 1  "
    BDS_ERROR = 2               "
    .  "  UMC_BDS_DOC_CREATE

ABAP code example for Function Module UMC_BDS_DOC_CREATE

The ABAP code below is a full code listing to execute function module UMC_BDS_DOC_CREATE 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_e_doc_id  
 
 TYPE BDS_DOCID
.


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

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

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

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

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

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

CALL FUNCTION 'UMC_BDS_DOC_CREATE'
  EXPORTING
    i_class =                    ld_i_class
    is_ok =                      ld_is_ok
    i_description =              ld_i_description
*   i_langu =                    ld_i_langu
*   i_multiple_doc =             ld_i_multiple_doc
    it_content =                 ld_it_content
  IMPORTING
    e_doc_id =                   ld_e_doc_id
  EXCEPTIONS
    DOCUMENT_ALREADY_EXISTS =    1
    BDS_ERROR =                  2
    .  "  UMC_BDS_DOC_CREATE

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_e_doc_id
 
 TYPE BDS_DOCID ,
ld_i_class
 
 TYPE BDS_CLSNAM ,
ld_is_ok
 
 TYPE UMC_YS_OBJECTKEY ,
ld_i_description
 
 TYPE BDS_PROPVA ,
ld_i_langu
 
 TYPE SY-LANGU ,
ld_i_multiple_doc
 
 TYPE AS4FLAG ,
ld_it_content
 
 TYPE SBDST_CONTENT .


ld_i_class = 'Check type of data required'.
ld_is_ok = 'Check type of data required'.
ld_i_description = 'Check type of data required'.
ld_i_langu = 'Check type of data required'.
ld_i_multiple_doc = 'Check type of data required'.
ld_it_content = 'Check type of data required'.