RM_BPS_FOR_NODE_GET SAP Function module - RM: ermittelt BPs (phys. od. log.) für PH-Knoten

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

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

Pattern for FM RM_BPS_FOR_NODE_GET - RM BPS FOR NODE GET

CALL FUNCTION 'RM_BPS_FOR_NODE_GET' "RM: ermittelt BPs (phys. od. log.) für PH-Knoten
  EXPORTING
    i_rmda =                    " rmlv_rmda     Risikomanagementbereich
    i_ph_tree_t =               " rmphtree_t    Baumtabelle Portfoliohierarchie
    i_ph_bp_map_t =             " rmphbpmap_t   Zuordnungstabelle Blatt<>phys. BP
    i_node =                    " jbrphbaum-name  Knoten
  IMPORTING
    e_bp_t =                    " rmlv_bp_t     Basisportfolien zu Knoten
  EXCEPTIONS
    INTERNAL_ERROR = 1          "               Fehler in der Verarbeitung
    .  "  RM_BPS_FOR_NODE_GET

ABAP code example for Function Module RM_BPS_FOR_NODE_GET

The ABAP code below is a full code listing to execute function module RM_BPS_FOR_NODE_GET 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_bp_t  
 
 TYPE RMLV_BP_T
.


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

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

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


DATA(ld_i_node) = some text here
.

CALL FUNCTION 'RM_BPS_FOR_NODE_GET'
  EXPORTING
    i_rmda =                     ld_i_rmda
    i_ph_tree_t =                ld_i_ph_tree_t
    i_ph_bp_map_t =              ld_i_ph_bp_map_t
    i_node =                     ld_i_node
  IMPORTING
    e_bp_t =                     ld_e_bp_t
  EXCEPTIONS
    INTERNAL_ERROR =             1
    .  "  RM_BPS_FOR_NODE_GET

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_e_bp_t
 
 TYPE RMLV_BP_T ,
ld_i_rmda
 
 TYPE RMLV_RMDA ,
ld_i_ph_tree_t
 
 TYPE RMPHTREE_T ,
ld_i_ph_bp_map_t
 
 TYPE RMPHBPMAP_T ,
ld_i_node
 
 TYPE JBRPHBAUM-NAME .


ld_i_rmda = 'Check type of data required'.
ld_i_ph_tree_t = 'Check type of data required'.
ld_i_ph_bp_map_t = 'Check type of data required'.

ld_i_node = some text here