SCMS_R3DB_EXPORT SAP Function module

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

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

Pattern for FM SCMS_R3DB_EXPORT - SCMS R3DB EXPORT

CALL FUNCTION 'SCMS_R3DB_EXPORT' "
  EXPORTING
*   mandt = SY-MANDT            " sy-mandt
    crep_id =                   " c
*   doc_id =                    " c
*   phio_id =                   " sdok_phid     Physical Document
*   doc_prot = SPACE            " c
*   overwrite = '-'             " c             Overwrite ("X" Without Log, " " with Log, "-" Never)
*   crea_time =                 " sdok_crtst    Creation time (UTC)
*   vscan_profile = '/SCMS/KPRO_CREATE'  " vscan_profile
  IMPORTING
    doc_id_out =                " c
* TABLES
*   access_info =               " scms_acinf
*   content_txt =               " sdokcntasc
*   content_bin =               " sdokcntbin    Line for binary document contents, length for upload
  EXCEPTIONS
    ERROR_EXPORT = 1            "
    ERROR_IMPORT = 2            "
    ERROR_PARAMETER = 3         "
    FORBIDDEN = 4               "
    BLOCKED_BY_POLICY = 5       "
    .  "  SCMS_R3DB_EXPORT

ABAP code example for Function Module SCMS_R3DB_EXPORT

The ABAP code below is a full code listing to execute function module SCMS_R3DB_EXPORT 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_doc_id_out  
 
 TYPE C
,
it_access_info  
 
 TYPE STANDARD TABLE OF SCMS_ACINF,"TABLES PARAM
wa_access_info
 
 LIKE LINE OF it_access_info
,
it_content_txt  
 
 TYPE STANDARD TABLE OF SDOKCNTASC,"TABLES PARAM
wa_content_txt
 
 LIKE LINE OF it_content_txt
,
it_content_bin  
 
 TYPE STANDARD TABLE OF SDOKCNTBIN,"TABLES PARAM
wa_content_bin
 
 LIKE LINE OF it_content_bin
.


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

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

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

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

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

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

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

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

"populate fields of struture and append to itab
append wa_access_info to it_access_info.
 

"populate fields of struture and append to itab
append wa_content_txt to it_content_txt.
 

"populate fields of struture and append to itab
append wa_content_bin to it_content_bin.
.

CALL FUNCTION 'SCMS_R3DB_EXPORT'
  EXPORTING
*   mandt =                      ld_mandt
    crep_id =                    ld_crep_id
*   doc_id =                     ld_doc_id
*   phio_id =                    ld_phio_id
*   doc_prot =                   ld_doc_prot
*   overwrite =                  ld_overwrite
*   crea_time =                  ld_crea_time
*   vscan_profile =              ld_vscan_profile
  IMPORTING
    doc_id_out =                 ld_doc_id_out
* TABLES
*   access_info =                it_access_info
*   content_txt =                it_content_txt
*   content_bin =                it_content_bin
  EXCEPTIONS
    ERROR_EXPORT =               1
    ERROR_IMPORT =               2
    ERROR_PARAMETER =            3
    FORBIDDEN =                  4
    BLOCKED_BY_POLICY =          5
    .  "  SCMS_R3DB_EXPORT

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
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "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_doc_id_out
 
 TYPE C ,
ld_mandt
 
 TYPE SY-MANDT ,
it_access_info
 
 TYPE STANDARD TABLE OF SCMS_ACINF ,
wa_access_info
 
 LIKE LINE OF it_access_info,
ld_crep_id
 
 TYPE C ,
it_content_txt
 
 TYPE STANDARD TABLE OF SDOKCNTASC ,
wa_content_txt
 
 LIKE LINE OF it_content_txt,
ld_doc_id
 
 TYPE C ,
it_content_bin
 
 TYPE STANDARD TABLE OF SDOKCNTBIN ,
wa_content_bin
 
 LIKE LINE OF it_content_bin,
ld_phio_id
 
 TYPE SDOK_PHID ,
ld_doc_prot
 
 TYPE C ,
ld_overwrite
 
 TYPE C ,
ld_crea_time
 
 TYPE SDOK_CRTST ,
ld_vscan_profile
 
 TYPE VSCAN_PROFILE .


ld_mandt = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_access_info to it_access_info.
ld_crep_id = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_content_txt to it_content_txt.
ld_doc_id = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_content_bin to it_content_bin.
ld_phio_id = 'Check type of data required'.
ld_doc_prot = 'Check type of data required'.
ld_overwrite = 'Check type of data required'.
ld_crea_time = 'Check type of data required'.
ld_vscan_profile = 'Check type of data required'.