SAP Function Modules

RH_CDOC_READ SAP Function module







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

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


Pattern for FM RH_CDOC_READ - RH CDOC READ





CALL FUNCTION 'RH_CDOC_READ' "
* EXPORTING
*   client = SY-MANDT           " cdhdr-mandant
*   plvar =                     " plvar
*   otype =                     " otype
*   objid =                     " hrobjid
*   it_object =                 " hrtb_objkey
*   istat =                     " istat_d
*   infty =                     " infotyp
*   subty =                     " subtyp
*   langu =                     " langu
*   sclas =                     " sclas
*   sobid =                     " sobid
*   version = '00'              " hrbas_cdoc_version
*   date_of_change = '00000000'  " cdhdr-udate
*   time_of_change = '000000'   " cdhdr-utime
*   date_until = '99991231'     " cddatum
*   time_until = '235959'       " cdtime
*   username = SPACE            " cdhdr-username
*   read_from_db = 'X'          " flag
*   read_from_archive =         " flag
  IMPORTING
    et_cdhdr =                  " cdhdr_tab
    et_cdpos =                  " cdpos_tab
  EXCEPTIONS
    NO_POSITION_FOUND = 1       "
    ACTION_CANCELED = 2         "
    .  "  RH_CDOC_READ

ABAP code example for Function Module RH_CDOC_READ





The ABAP code below is a full code listing to execute function module RH_CDOC_READ 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_et_cdhdr  TYPE CDHDR_TAB ,
ld_et_cdpos  TYPE CDPOS_TAB .


SELECT single MANDANT
FROM CDHDR
INTO @DATA(ld_client).

DATA(ld_plvar) = 'Check type of data required'.
DATA(ld_otype) = 'Check type of data required'.
DATA(ld_objid) = 'Check type of data required'.
DATA(ld_it_object) = 'Check type of data required'.
DATA(ld_istat) = 'Check type of data required'.
DATA(ld_infty) = 'Check type of data required'.
DATA(ld_subty) = 'Check type of data required'.
DATA(ld_langu) = 'Check type of data required'.
DATA(ld_sclas) = 'Check type of data required'.
DATA(ld_sobid) = 'Check type of data required'.
DATA(ld_version) = 'Check type of data required'.

SELECT single UDATE
FROM CDHDR
INTO @DATA(ld_date_of_change).


SELECT single UTIME
FROM CDHDR
INTO @DATA(ld_time_of_change).

DATA(ld_date_until) = 'Check type of data required'.
DATA(ld_time_until) = 'Check type of data required'.

SELECT single USERNAME
FROM CDHDR
INTO @DATA(ld_username).

DATA(ld_read_from_db) = 'Check type of data required'.
DATA(ld_read_from_archive) = 'Check type of data required'. . CALL FUNCTION 'RH_CDOC_READ' * EXPORTING * client = ld_client * plvar = ld_plvar * otype = ld_otype * objid = ld_objid * it_object = ld_it_object * istat = ld_istat * infty = ld_infty * subty = ld_subty * langu = ld_langu * sclas = ld_sclas * sobid = ld_sobid * version = ld_version * date_of_change = ld_date_of_change * time_of_change = ld_time_of_change * date_until = ld_date_until * time_until = ld_time_until * username = ld_username * read_from_db = ld_read_from_db * read_from_archive = ld_read_from_archive IMPORTING et_cdhdr = ld_et_cdhdr et_cdpos = ld_et_cdpos EXCEPTIONS NO_POSITION_FOUND = 1 ACTION_CANCELED = 2 . " RH_CDOC_READ
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_et_cdhdr  TYPE CDHDR_TAB ,
ld_client  TYPE CDHDR-MANDANT ,
ld_et_cdpos  TYPE CDPOS_TAB ,
ld_plvar  TYPE PLVAR ,
ld_otype  TYPE OTYPE ,
ld_objid  TYPE HROBJID ,
ld_it_object  TYPE HRTB_OBJKEY ,
ld_istat  TYPE ISTAT_D ,
ld_infty  TYPE INFOTYP ,
ld_subty  TYPE SUBTYP ,
ld_langu  TYPE LANGU ,
ld_sclas  TYPE SCLAS ,
ld_sobid  TYPE SOBID ,
ld_version  TYPE HRBAS_CDOC_VERSION ,
ld_date_of_change  TYPE CDHDR-UDATE ,
ld_time_of_change  TYPE CDHDR-UTIME ,
ld_date_until  TYPE CDDATUM ,
ld_time_until  TYPE CDTIME ,
ld_username  TYPE CDHDR-USERNAME ,
ld_read_from_db  TYPE FLAG ,
ld_read_from_archive  TYPE FLAG .


SELECT single MANDANT
FROM CDHDR
INTO ld_client.

ld_plvar = 'Check type of data required'.
ld_otype = 'Check type of data required'.
ld_objid = 'Check type of data required'.
ld_it_object = 'Check type of data required'.
ld_istat = 'Check type of data required'.
ld_infty = 'Check type of data required'.
ld_subty = 'Check type of data required'.
ld_langu = 'Check type of data required'.
ld_sclas = 'Check type of data required'.
ld_sobid = 'Check type of data required'.
ld_version = 'Check type of data required'.

SELECT single UDATE
FROM CDHDR
INTO ld_date_of_change.


SELECT single UTIME
FROM CDHDR
INTO ld_time_of_change.

ld_date_until = 'Check type of data required'.
ld_time_until = 'Check type of data required'.

SELECT single USERNAME
FROM CDHDR
INTO ld_username.

ld_read_from_db = 'Check type of data required'.
ld_read_from_archive = '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 RH_CDOC_READ or its description.