TB_LIMIT_CALL_PARTNER SAP Function module - Display Business Partner (from ALV List)

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

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

Pattern for FM TB_LIMIT_CALL_PARTNER - TB LIMIT CALL PARTNER

CALL FUNCTION 'TB_LIMIT_CALL_PARTNER' "Display Business Partner (from ALV List)
  EXPORTING
    rs_selfield =               " slis_selfield  Information Cursor Position ALV
    i_tabname =                 " slis_tabname  Table Name
  TABLES
    it_vtblvi0 =                " lmalv_t_vtblvi02  Limit Utilizations and Limits
    t_vtblsp =                  " trlm_t_vtblsp  Limits: Logical/Physical Keys
  EXCEPTIONS
    NO_PARTNER = 1              "               No Partner Found
    WRONG_CSPOS = 2             "               Incorrect Cursor Position
    INTERNAL_ERR = 3            "               Internal Error
    .  "  TB_LIMIT_CALL_PARTNER

ABAP code example for Function Module TB_LIMIT_CALL_PARTNER

The ABAP code below is a full code listing to execute function module TB_LIMIT_CALL_PARTNER 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:
it_it_vtblvi0  
 
 TYPE STANDARD TABLE OF LMALV_T_VTBLVI02,"TABLES PARAM
wa_it_vtblvi0
 
 LIKE LINE OF it_it_vtblvi0
,
it_t_vtblsp  
 
 TYPE STANDARD TABLE OF TRLM_T_VTBLSP,"TABLES PARAM
wa_t_vtblsp
 
 LIKE LINE OF it_t_vtblsp
.


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

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

"populate fields of struture and append to itab
append wa_it_vtblvi0 to it_it_vtblvi0.
 

"populate fields of struture and append to itab
append wa_t_vtblsp to it_t_vtblsp.
.

CALL FUNCTION 'TB_LIMIT_CALL_PARTNER'
  EXPORTING
    rs_selfield =                ld_rs_selfield
    i_tabname =                  ld_i_tabname
  TABLES
    it_vtblvi0 =                 it_it_vtblvi0
    t_vtblsp =                   it_t_vtblsp
  EXCEPTIONS
    NO_PARTNER =                 1
    WRONG_CSPOS =                2
    INTERNAL_ERR =               3
    .  "  TB_LIMIT_CALL_PARTNER

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_rs_selfield
 
 TYPE SLIS_SELFIELD ,
it_it_vtblvi0
 
 TYPE STANDARD TABLE OF LMALV_T_VTBLVI02 ,
wa_it_vtblvi0
 
 LIKE LINE OF it_it_vtblvi0,
ld_i_tabname
 
 TYPE SLIS_TABNAME ,
it_t_vtblsp
 
 TYPE STANDARD TABLE OF TRLM_T_VTBLSP ,
wa_t_vtblsp
 
 LIKE LINE OF it_t_vtblsp.


ld_rs_selfield = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_it_vtblvi0 to it_it_vtblvi0.
ld_i_tabname = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_t_vtblsp to it_t_vtblsp.