SAP Function Modules

comments icon Comments

OLR3_RFC_CHECK_EXISTENCE SAP Function module







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

Associated Function Group: OLR3_RFC
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM OLR3_RFC_CHECK_EXISTENCE - OLR3 RFC CHECK EXISTENCE 





CALL FUNCTION 'OLR3_RFC_CHECK_EXISTENCE' "
  EXPORTING
    ev_proxy_class =            " olr3_r3_tv_proxy_class
    ev_tabname =                " olr3_r3_tv_ddic_table
    ev_tabname_desc =           " olr3_r3_tv_ddic_table
    et_ext_id =                 " olr3_r3_tt_id_split
    et_int_id =                 " olr3_r3_tt_id_split
    et_desc =                   " olr3_r3_tt_id_split
  IMPORTING
    iv_return =                 " bapireturn1
    it_ext_id =                 " olr3_r3_tt_id_split
    it_int_id =                 " olr3_r3_tt_id_split
    it_desc =                   " olr3_r3_tt_id_split
    .  "  OLR3_RFC_CHECK_EXISTENCE

ABAP code example for Function Module OLR3_RFC_CHECK_EXISTENCE





The ABAP code below is a full code listing to execute function module OLR3_RFC_CHECK_EXISTENCE 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_iv_return    TYPE BAPIRETURN1
,
ld_it_ext_id    TYPE OLR3_R3_TT_ID_SPLIT
,
ld_it_int_id    TYPE OLR3_R3_TT_ID_SPLIT
,
ld_it_desc    TYPE OLR3_R3_TT_ID_SPLIT
.




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

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

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

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

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

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

CALL FUNCTION 'OLR3_RFC_CHECK_EXISTENCE'
  EXPORTING
    ev_proxy_class =             ld_ev_proxy_class
    ev_tabname =                 ld_ev_tabname
    ev_tabname_desc =            ld_ev_tabname_desc
    et_ext_id =                  ld_et_ext_id
    et_int_id =                  ld_et_int_id
    et_desc =                    ld_et_desc
  IMPORTING
    iv_return =                  ld_iv_return
    it_ext_id =                  ld_it_ext_id
    it_int_id =                  ld_it_int_id
    it_desc =                    ld_it_desc
    .  "  OLR3_RFC_CHECK_EXISTENCE

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_iv_return  TYPE BAPIRETURN1 ,
ld_ev_proxy_class  TYPE OLR3_R3_TV_PROXY_CLASS ,
ld_it_ext_id  TYPE OLR3_R3_TT_ID_SPLIT ,
ld_ev_tabname  TYPE OLR3_R3_TV_DDIC_TABLE ,
ld_it_int_id  TYPE OLR3_R3_TT_ID_SPLIT ,
ld_ev_tabname_desc  TYPE OLR3_R3_TV_DDIC_TABLE ,
ld_it_desc  TYPE OLR3_R3_TT_ID_SPLIT ,
ld_et_ext_id  TYPE OLR3_R3_TT_ID_SPLIT ,
ld_et_int_id  TYPE OLR3_R3_TT_ID_SPLIT ,
ld_et_desc  TYPE OLR3_R3_TT_ID_SPLIT .




ld_ev_proxy_class = 'Check type of data required'.
ld_ev_tabname = 'Check type of data required'.
ld_ev_tabname_desc = 'Check type of data required'.
ld_et_ext_id = 'Check type of data required'.
ld_et_int_id = 'Check type of data required'.
ld_et_desc = 'Check type of data required'.

SAP Documentation for FM OLR3_RFC_CHECK_EXISTENCE


In cProjects an object link is created for an SAP R/3 object category. If the existence check is activated in the corresponding object type ...See here for full SAP fm documentation

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


   
 

OLR3_RFC_CHECK_EXISTENCE - 
OLR3_RFC_CHECK_CONSISTENCY - 
OLR3_DMS_WORK_GET_CV_CONSTANT - 
OLR3_DMS_WORK_CALL_DPR_SHLP - 
OLR3_DMS_RFC_USE_ASYNC_UPDMODE - 
OLR3_DMS_RFC_UPDATE_BOM_ITEM -