RTP_US_DB_BP_PLAN_READ_MULT SAP Function module - Reads the db table rtp_us_bp_plan

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

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

Pattern for FM RTP_US_DB_BP_PLAN_READ_MULT - RTP US DB BP PLAN READ MULT

CALL FUNCTION 'RTP_US_DB_BP_PLAN_READ_MULT' "Reads the db table rtp_us_bp_plan
* EXPORTING
*   i_bkkrs =                   " rtp_us_bp_plan-bkkrs  Bank Area
*   i_plan_number =             " rtp_us_bp_plan-plan_number  Plan number of a retirement plan
*   i_partner =                 " rtp_us_bp_plan-partner  Business Partner Number
*   i_rltyp =                   " rtp_us_bp_plan-rltyp  BDT: Object part
* TABLES
*   t_bp_plan =                 " rtp_us_bp_plan  Business partners associated with a retirement plan
  EXCEPTIONS
    NOT_FOUND = 1               "
    .  "  RTP_US_DB_BP_PLAN_READ_MULT

ABAP code example for Function Module RTP_US_DB_BP_PLAN_READ_MULT

The ABAP code below is a full code listing to execute function module RTP_US_DB_BP_PLAN_READ_MULT 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_t_bp_plan  
 
 TYPE STANDARD TABLE OF RTP_US_BP_PLAN,"TABLES PARAM
wa_t_bp_plan
 
 LIKE LINE OF it_t_bp_plan
.

 

SELECT single BKKRS 
  FROM RTP_US_BP_PLAN 
  INTO @DATA(ld_i_bkkrs).

 

SELECT single PLAN_NUMBER 
  FROM RTP_US_BP_PLAN 
  INTO @DATA(ld_i_plan_number).

 

SELECT single PARTNER 
  FROM RTP_US_BP_PLAN 
  INTO @DATA(ld_i_partner).

 

SELECT single RLTYP 
  FROM RTP_US_BP_PLAN 
  INTO @DATA(ld_i_rltyp).

 

"populate fields of struture and append to itab
append wa_t_bp_plan to it_t_bp_plan.
.

CALL FUNCTION 'RTP_US_DB_BP_PLAN_READ_MULT'
* EXPORTING
*   i_bkkrs =                    ld_i_bkkrs
*   i_plan_number =              ld_i_plan_number
*   i_partner =                  ld_i_partner
*   i_rltyp =                    ld_i_rltyp
* TABLES
*   t_bp_plan =                  it_t_bp_plan
  EXCEPTIONS
    NOT_FOUND =                  1
    .  "  RTP_US_DB_BP_PLAN_READ_MULT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_i_bkkrs
 
 TYPE RTP_US_BP_PLAN-BKKRS ,
it_t_bp_plan
 
 TYPE STANDARD TABLE OF RTP_US_BP_PLAN ,
wa_t_bp_plan
 
 LIKE LINE OF it_t_bp_plan,
ld_i_plan_number
 
 TYPE RTP_US_BP_PLAN-PLAN_NUMBER ,
ld_i_partner
 
 TYPE RTP_US_BP_PLAN-PARTNER ,
ld_i_rltyp
 
 TYPE RTP_US_BP_PLAN-RLTYP .



SELECT single BKKRS 
  FROM RTP_US_BP_PLAN 
  INTO ld_i_bkkrs.
 

"populate fields of struture and append to itab
append wa_t_bp_plan to it_t_bp_plan.

SELECT single PLAN_NUMBER 
  FROM RTP_US_BP_PLAN 
  INTO ld_i_plan_number.


SELECT single PARTNER 
  FROM RTP_US_BP_PLAN 
  INTO ld_i_partner.


SELECT single RLTYP 
  FROM RTP_US_BP_PLAN 
  INTO ld_i_rltyp.

SAP Documentation for FM RTP_US_DB_BP_PLAN_READ_MULT