RECS_PARTNER_SELECT SAP Function module

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

Associated Function Group: RECS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM RECS_PARTNER_SELECT - RECS PARTNER SELECT

CALL FUNCTION 'RECS_PARTNER_SELECT' "
* EXPORTING
*   i_bukrs =                   " vicn01-bukrs
*   i_recnnr =                  " vicn01-recnnr
*   i_intreno =                 " vicn01-intreno
*   i_date = SY-DATUM           " sy-datum
*   i_mode = '#'                " c
  IMPORTING
    e_cnt_kunnr =               " sy-dbcnt
    e_cnt_lifnr =               " sy-dbcnt
    e_kunnr =                   " kunnr
    e_lifnr =                   " lifnr
  EXCEPTIONS
    NO_SELECTION = 1            "
    NO_CUSTOMER = 2             "
    NO_VENDOR = 3               "
    .  "  RECS_PARTNER_SELECT

ABAP code example for Function Module RECS_PARTNER_SELECT

The ABAP code below is a full code listing to execute function module RECS_PARTNER_SELECT 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_e_cnt_kunnr  
 
 TYPE SY-DBCNT
,
ld_e_cnt_lifnr  
 
 TYPE SY-DBCNT
,
ld_e_kunnr  
 
 TYPE KUNNR
,
ld_e_lifnr  
 
 TYPE LIFNR
.

 

SELECT single BUKRS 
  FROM VICN01 
  INTO @DATA(ld_i_bukrs).

 

SELECT single RECNNR 
  FROM VICN01 
  INTO @DATA(ld_i_recnnr).

 

SELECT single INTRENO 
  FROM VICN01 
  INTO @DATA(ld_i_intreno).


DATA(ld_i_date) = '20210129'.

DATA(ld_i_mode) = '20210129'.
.

CALL FUNCTION 'RECS_PARTNER_SELECT'
* EXPORTING
*   i_bukrs =                    ld_i_bukrs
*   i_recnnr =                   ld_i_recnnr
*   i_intreno =                  ld_i_intreno
*   i_date =                     ld_i_date
*   i_mode =                     ld_i_mode
  IMPORTING
    e_cnt_kunnr =                ld_e_cnt_kunnr
    e_cnt_lifnr =                ld_e_cnt_lifnr
    e_kunnr =                    ld_e_kunnr
    e_lifnr =                    ld_e_lifnr
  EXCEPTIONS
    NO_SELECTION =               1
    NO_CUSTOMER =                2
    NO_VENDOR =                  3
    .  "  RECS_PARTNER_SELECT

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
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_e_cnt_kunnr
 
 TYPE SY-DBCNT ,
ld_i_bukrs
 
 TYPE VICN01-BUKRS ,
ld_e_cnt_lifnr
 
 TYPE SY-DBCNT ,
ld_i_recnnr
 
 TYPE VICN01-RECNNR ,
ld_e_kunnr
 
 TYPE KUNNR ,
ld_i_intreno
 
 TYPE VICN01-INTRENO ,
ld_e_lifnr
 
 TYPE LIFNR ,
ld_i_date
 
 TYPE SY-DATUM ,
ld_i_mode
 
 TYPE C .



SELECT single BUKRS 
  FROM VICN01 
  INTO ld_i_bukrs.


SELECT single RECNNR 
  FROM VICN01 
  INTO ld_i_recnnr.


SELECT single INTRENO 
  FROM VICN01 
  INTO ld_i_intreno.

ld_i_date = '20210129'.
ld_i_mode = '20210129'.