SAP Tables

RH_CHECK_OBJECT_FOR_OUTBOUND SAP Function module




RH_CHECK_OBJECT_FOR_OUTBOUNDis a standard SAP function module available within R/3 SAPsystems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import/export parameters, exceptions etc as well as any documentation contributions specific to the object. See here to view full function module documentation and code listing, simply by entering the name RH_CHECK_OBJECT_FOR_OUTBOUND into the relevant SAP transaction such as SE37 or SE80.

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_CHECK_OBJECT_FOR_OUTBOUND or its description.


Pattern for FM RH_CHECK_OBJECT_FOR_OUTBOUND - RH CHECK OBJECT FOR OUTBOUND
Associated Function Group: RHA0
Released Date: Not Released
CALL FUNCTION 'RH_CHECK_OBJECT_FOR_OUTBOUND' "
  EXPORTING
    plvar =                     " plvar         Plan Version
    otype =                     " otype         Object Type
    objid =                     " hrobjid       Object ID
*   check_enqueue = 'X'         " flag
*   check_original = 'X'        " flag
  EXCEPTIONS
    OBJECT_IS_ENQUEUED = 1      "               Object is locked
    OBJECT_IS_NOT_ORIGINAL = 2  "
    OBJECT_IS_NOT_EXISTING = 3  "               Object Does Not Exist
    OBJECT_IS_NOT_REGISTERED = 4  "
    CUSTOMER_REJECTED = 5       "
    CUSTOMER_REJECTED_NO_MESSAGE = 6  "
    .  "  RH_CHECK_OBJECT_FOR_OUTBOUND

ABAP code example for Function Module RH_CHECK_OBJECT_FOR_OUTBOUND

The ABAP code below is a full code listing to execute function module RH_CHECK_OBJECT_FOR_OUTBOUND including all data declarations. The code uses the latest in-line data declaration syntax but I have included an abap code snipet 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_plvar) = 'Check type of data required'.
DATA(ld_otype) = 'Check type of data required'.
DATA(ld_objid) = 'Check type of data required'.
DATA(ld_check_enqueue) = 'Check type of data required'.
DATA(ld_check_original) = 'Check type of data required'.. CALL FUNCTION 'RH_CHECK_OBJECT_FOR_OUTBOUND' EXPORTING plvar = ld_plvar otype = ld_otype objid = ld_objid * check_enqueue = ld_check_enqueue * check_original = ld_check_original EXCEPTIONS OBJECT_IS_ENQUEUED = 1 OBJECT_IS_NOT_ORIGINAL = 2 OBJECT_IS_NOT_EXISTING = 3 OBJECT_IS_NOT_REGISTERED = 4 CUSTOMER_REJECTED = 5 CUSTOMER_REJECTED_NO_MESSAGE = 6 . " RH_CHECK_OBJECT_FOR_OUTBOUND
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 ELSEIF SY-SUBRC EQ 6. "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_plvar TYPE PLVAR ,
ld_otype TYPE OTYPE ,
ld_objid TYPE HROBJID ,
ld_check_enqueue TYPE FLAG ,
ld_check_original TYPE FLAG .

ld_plvar = 'Check type of data required'.
ld_otype = 'Check type of data required'.
ld_objid = 'Check type of data required'.
ld_check_enqueue = 'Check type of data required'.
ld_check_original = 'Check type of data required'..