SAP REEX_CB_CHECK_SINGLE_OBJ Function Module for









REEX_CB_CHECK_SINGLE_OBJ is a standard reex cb check single obj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for reex cb check single obj FM, simply by entering the name REEX_CB_CHECK_SINGLE_OBJ into the relevant SAP transaction such as SE37 or SE38.

Function Group: REEX_CALLBACK_RE_CLASSIC
Program Name: SAPLREEX_CALLBACK_RE_CLASSIC
Main Program: SAPLREEX_CALLBACK_RE_CLASSIC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function REEX_CB_CHECK_SINGLE_OBJ pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'REEX_CB_CHECK_SINGLE_OBJ'"
EXPORTING
* ID_OBJNR = "Object Number
* ID_RECNNR = "Contract Number
* ID_ACTIVITY = ' ' "Business Transaction
* ID_BUKRS = "Company Code
* ID_SWENR = "Business Entity Number
* ID_SGRNR = "Land Number for BE
* ID_SGENR = "Building Number
* ID_SMENR = "Number of Rental Object
* D_SNKSL = "Service Charge Key
* ID_SEMPSL = "Settlement Unit
* ID_DABRBEZ = "Reference date for settlement

EXCEPTIONS
OBJECT_NOT_FOUND = 1 ACTIVITY_NOT_ALLOWED = 2
.



IMPORTING Parameters details for REEX_CB_CHECK_SINGLE_OBJ

ID_OBJNR - Object Number

Data type: RECAOBJNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_RECNNR - Contract Number

Data type: RECNNUMBER
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_ACTIVITY - Business Transaction

Data type: TJ01-VRGNG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_BUKRS - Company Code

Data type: BUKRS
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_SWENR - Business Entity Number

Data type: SWENR
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_SGRNR - Land Number for BE

Data type: SGRNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_SGENR - Building Number

Data type: SGENR
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_SMENR - Number of Rental Object

Data type: REBDRONO
Optional: Yes
Call by Reference: No ( called with pass by value option)

D_SNKSL - Service Charge Key

Data type: RESC_SETTL_UNIT-SNKSL
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_SEMPSL - Settlement Unit

Data type: RESC_SETTL_UNIT-SEMPSL
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_DABRBEZ - Reference date for settlement

Data type: DABRBEZ
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

OBJECT_NOT_FOUND - Object Does Not Exist

Data type:
Optional: No
Call by Reference: Yes

ACTIVITY_NOT_ALLOWED - Activity Not Allowed for Object

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for REEX_CB_CHECK_SINGLE_OBJ Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_id_objnr  TYPE RECAOBJNR, "   
lv_object_not_found  TYPE RECAOBJNR, "   
lv_id_recnnr  TYPE RECNNUMBER, "   
lv_id_activity  TYPE TJ01-VRGNG, "   SPACE
lv_id_bukrs  TYPE BUKRS, "   
lv_activity_not_allowed  TYPE BUKRS, "   
lv_id_swenr  TYPE SWENR, "   
lv_id_sgrnr  TYPE SGRNR, "   
lv_id_sgenr  TYPE SGENR, "   
lv_id_smenr  TYPE REBDRONO, "   
lv_d_snksl  TYPE RESC_SETTL_UNIT-SNKSL, "   
lv_id_sempsl  TYPE RESC_SETTL_UNIT-SEMPSL, "   
lv_id_dabrbez  TYPE DABRBEZ. "   

  CALL FUNCTION 'REEX_CB_CHECK_SINGLE_OBJ'  "
    EXPORTING
         ID_OBJNR = lv_id_objnr
         ID_RECNNR = lv_id_recnnr
         ID_ACTIVITY = lv_id_activity
         ID_BUKRS = lv_id_bukrs
         ID_SWENR = lv_id_swenr
         ID_SGRNR = lv_id_sgrnr
         ID_SGENR = lv_id_sgenr
         ID_SMENR = lv_id_smenr
         D_SNKSL = lv_d_snksl
         ID_SEMPSL = lv_id_sempsl
         ID_DABRBEZ = lv_id_dabrbez
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        ACTIVITY_NOT_ALLOWED = 2
. " REEX_CB_CHECK_SINGLE_OBJ




ABAP code using 7.40 inline data declarations to call FM REEX_CB_CHECK_SINGLE_OBJ

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
"SELECT single VRGNG FROM TJ01 INTO @DATA(ld_id_activity).
DATA(ld_id_activity) = ' '.
 
 
 
 
 
 
 
"SELECT single SNKSL FROM RESC_SETTL_UNIT INTO @DATA(ld_d_snksl).
 
"SELECT single SEMPSL FROM RESC_SETTL_UNIT INTO @DATA(ld_id_sempsl).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!