SAP REEX_CB_MATCHCODE_FOR_OBART Function Module for









REEX_CB_MATCHCODE_FOR_OBART is a standard reex cb matchcode for obart 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 matchcode for obart FM, simply by entering the name REEX_CB_MATCHCODE_FOR_OBART 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: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function REEX_CB_MATCHCODE_FOR_OBART 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_MATCHCODE_FOR_OBART'"
EXPORTING
I_OBART = "
* I_BUKRS = "

IMPORTING
E_EMPGE = "
E_OBJNR = "

EXCEPTIONS
OBART_NOT_VALID = 1
.



IMPORTING Parameters details for REEX_CB_MATCHCODE_FOR_OBART

I_OBART -

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

I_BUKRS -

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

EXPORTING Parameters details for REEX_CB_MATCHCODE_FOR_OBART

E_EMPGE -

Data type: DKOBR-EMPGE
Optional: No
Call by Reference: No ( called with pass by value option)

E_OBJNR -

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

EXCEPTIONS details

OBART_NOT_VALID -

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

Copy and paste ABAP code example for REEX_CB_MATCHCODE_FOR_OBART 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_e_empge  TYPE DKOBR-EMPGE, "   
lv_i_obart  TYPE RECAOBJTYPE, "   
lv_obart_not_valid  TYPE RECAOBJTYPE, "   
lv_e_objnr  TYPE RECAOBJNR, "   
lv_i_bukrs  TYPE BUKRS. "   

  CALL FUNCTION 'REEX_CB_MATCHCODE_FOR_OBART'  "
    EXPORTING
         I_OBART = lv_i_obart
         I_BUKRS = lv_i_bukrs
    IMPORTING
         E_EMPGE = lv_e_empge
         E_OBJNR = lv_e_objnr
    EXCEPTIONS
        OBART_NOT_VALID = 1
. " REEX_CB_MATCHCODE_FOR_OBART




ABAP code using 7.40 inline data declarations to call FM REEX_CB_MATCHCODE_FOR_OBART

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 EMPGE FROM DKOBR INTO @DATA(ld_e_empge).
 
 
 
 
 


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!