HRDSYS_EXIST_DOCU SAP Function module

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

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

Pattern for FM HRDSYS_EXIST_DOCU - HRDSYS EXIST DOCU

CALL FUNCTION 'HRDSYS_EXIST_DOCU' "
  EXPORTING
*   client = SY-MANDT           " sy-mandt
*   searchlvec = '*'            " c
*   molga = SPACE               " c
    oname =                     " c
    otype =                     " c
  IMPORTING
    foundlvec =                 " c
  EXCEPTIONS
    NOT_FOUND = 1               "
    WRONG_OTYPE = 2             "
    INTERNAL_ERROR = 3          "
    .  "  HRDSYS_EXIST_DOCU

ABAP code example for Function Module HRDSYS_EXIST_DOCU

The ABAP code below is a full code listing to execute function module HRDSYS_EXIST_DOCU 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_foundlvec  
 
 TYPE C
.


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

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

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

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

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

CALL FUNCTION 'HRDSYS_EXIST_DOCU'
  EXPORTING
*   client =                     ld_client
*   searchlvec =                 ld_searchlvec
*   molga =                      ld_molga
    oname =                      ld_oname
    otype =                      ld_otype
  IMPORTING
    foundlvec =                  ld_foundlvec
  EXCEPTIONS
    NOT_FOUND =                  1
    WRONG_OTYPE =                2
    INTERNAL_ERROR =             3
    .  "  HRDSYS_EXIST_DOCU

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
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_foundlvec
 
 TYPE C ,
ld_client
 
 TYPE SY-MANDT ,
ld_searchlvec
 
 TYPE C ,
ld_molga
 
 TYPE C ,
ld_oname
 
 TYPE C ,
ld_otype
 
 TYPE C .


ld_client = 'Check type of data required'.
ld_searchlvec = 'Check type of data required'.
ld_molga = 'Check type of data required'.
ld_oname = 'Check type of data required'.
ld_otype = 'Check type of data required'.