SAP Function Modules

CHECK_DOCUMENT SAP Function module







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

Associated Function Group: SKTM
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM CHECK_DOCUMENT - CHECK DOCUMENT





CALL FUNCTION 'CHECK_DOCUMENT' "
  EXPORTING
    id =                        " dokhl-id
    object =                    " dokhl-object  Documentation Object
*   source_lang =               " sy-langu
    target_lang =               " sy-langu
*   detail_errlist = 'X'        " c
*   displ_status =              " c
  IMPORTING
    retcode =                   " i
  TABLES
    errorlist =                 " errorslist
*   linklist =                  " errorslist
    .  "  CHECK_DOCUMENT

ABAP code example for Function Module CHECK_DOCUMENT





The ABAP code below is a full code listing to execute function module CHECK_DOCUMENT 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_retcode  TYPE I ,
it_errorlist  TYPE STANDARD TABLE OF ERRORSLIST,"TABLES PARAM
wa_errorlist  LIKE LINE OF it_errorlist ,
it_linklist  TYPE STANDARD TABLE OF ERRORSLIST,"TABLES PARAM
wa_linklist  LIKE LINE OF it_linklist .


SELECT single ID
FROM DOKHL
INTO @DATA(ld_id).


SELECT single OBJECT
FROM DOKHL
INTO @DATA(ld_object).

DATA(ld_source_lang) = 'Check type of data required'.
DATA(ld_target_lang) = 'Check type of data required'.
DATA(ld_detail_errlist) = 'Check type of data required'.
DATA(ld_displ_status) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_errorlist to it_errorlist.

"populate fields of struture and append to itab
append wa_linklist to it_linklist. . CALL FUNCTION 'CHECK_DOCUMENT' EXPORTING id = ld_id object = ld_object * source_lang = ld_source_lang target_lang = ld_target_lang * detail_errlist = ld_detail_errlist * displ_status = ld_displ_status IMPORTING retcode = ld_retcode TABLES errorlist = it_errorlist * linklist = it_linklist . " CHECK_DOCUMENT
IF SY-SUBRC EQ 0. "All OK 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_retcode  TYPE I ,
ld_id  TYPE DOKHL-ID ,
it_errorlist  TYPE STANDARD TABLE OF ERRORSLIST ,
wa_errorlist  LIKE LINE OF it_errorlist,
ld_object  TYPE DOKHL-OBJECT ,
it_linklist  TYPE STANDARD TABLE OF ERRORSLIST ,
wa_linklist  LIKE LINE OF it_linklist,
ld_source_lang  TYPE SY-LANGU ,
ld_target_lang  TYPE SY-LANGU ,
ld_detail_errlist  TYPE C ,
ld_displ_status  TYPE C .


SELECT single ID
FROM DOKHL
INTO ld_id.


"populate fields of struture and append to itab
append wa_errorlist to it_errorlist.

SELECT single OBJECT
FROM DOKHL
INTO ld_object.


"populate fields of struture and append to itab
append wa_linklist to it_linklist.
ld_source_lang = 'Check type of data required'.
ld_target_lang = 'Check type of data required'.
ld_detail_errlist = 'Check type of data required'.
ld_displ_status = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CHECK_DOCUMENT or its description.