SAP BM_PHASSIGN_GET Function Module for Reads the benchmarks assigned to a portfolio hierarchy









BM_PHASSIGN_GET is a standard bm phassign get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reads the benchmarks assigned to a portfolio hierarchy processing and below is the pattern details for this FM, 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 bm phassign get FM, simply by entering the name BM_PHASSIGN_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: AFWBM_SERVICES
Program Name: SAPLAFWBM_SERVICES
Main Program: SAPLAFWBM_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BM_PHASSIGN_GET 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 'BM_PHASSIGN_GET'"Reads the benchmarks assigned to a portfolio hierarchy
  EXPORTING
   I_SICHTID =  "View of an Analysis Structure
   I_PHID =  "Portfolio Hierarchy
   I_ASS_VARI =  "Assignment Variant
*  I_VALDATE =  "Validity Date
*  I_VERSION =  "Time Stamp
*  I_VALDATE_BACK =  "Indicator
*  I_KEYDATE =  "Evaluation Date
*  I_BYPASS_BUFFER =  "Always Read Current Definitions

 IMPORTING
   E_STR_AFWBMPH =  "TRM: Auxiliary Structure for Transaction AFWBMPH
   E_TAB_NODE_BMID =  "Portfolio Hierarchy Tree Table for Benchmarking
   E_TAB_AFWBM_REASON =  "PH node properties for Text Determination
   E_TAB_BM =  "TRM: Table Type for GET_TAB_BM_PER_PH_VAR

EXCEPTIONS
   WRONG_PARAM = 1    NOT_FOUND = 2    HIST_NOT_FOUND = 3    VERSION_NOT_FOUND = 4
.



IMPORTING Parameters details for BM_PHASSIGN_GET

I_SICHTID - View of an Analysis Structure

Data type: JBRSICHTID
Optional: No
Call by Reference: Yes

I_PHID - Portfolio Hierarchy

Data type: JBRPHID
Optional: No
Call by Reference: Yes

I_ASS_VARI - Assignment Variant

Data type: AFWBM_ASSVARI
Optional: No
Call by Reference: Yes

I_VALDATE - Validity Date

Data type: AFWBM_VALDATE
Optional: Yes
Call by Reference: Yes

I_VERSION - Time Stamp

Data type: AFW_TIMESTP
Optional: Yes
Call by Reference: Yes

I_VALDATE_BACK - Indicator

Data type: AFWCH_FLAG
Optional: Yes
Call by Reference: Yes

I_KEYDATE - Evaluation Date

Data type: AFW_KEYDATE
Optional: Yes
Call by Reference: Yes

I_BYPASS_BUFFER - Always Read Current Definitions

Data type: AFWCH_FLAG
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BM_PHASSIGN_GET

E_STR_AFWBMPH - TRM: Auxiliary Structure for Transaction AFWBMPH

Data type: AFWBMPH_STR
Optional: No
Call by Reference: Yes

E_TAB_NODE_BMID - Portfolio Hierarchy Tree Table for Benchmarking

Data type: AFWBM_NODE_BMID_T
Optional: No
Call by Reference: Yes

E_TAB_AFWBM_REASON - PH node properties for Text Determination

Data type: AFWBM_REASON_T
Optional: No
Call by Reference: Yes

E_TAB_BM - TRM: Table Type for GET_TAB_BM_PER_PH_VAR

Data type: AFWBM_BM_CATE_T
Optional: No
Call by Reference: Yes

EXCEPTIONS details

WRONG_PARAM - Parameter Error

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND - Variant Not Found

Data type:
Optional: No
Call by Reference: Yes

HIST_NOT_FOUND - Unable to find history

Data type:
Optional: No
Call by Reference: Yes

VERSION_NOT_FOUND - History version was not found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BM_PHASSIGN_GET 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_i_sichtid  TYPE JBRSICHTID, "   
lv_wrong_param  TYPE JBRSICHTID, "   
lv_e_str_afwbmph  TYPE AFWBMPH_STR, "   
lv_i_phid  TYPE JBRPHID, "   
lv_not_found  TYPE JBRPHID, "   
lv_e_tab_node_bmid  TYPE AFWBM_NODE_BMID_T, "   
lv_i_ass_vari  TYPE AFWBM_ASSVARI, "   
lv_hist_not_found  TYPE AFWBM_ASSVARI, "   
lv_e_tab_afwbm_reason  TYPE AFWBM_REASON_T, "   
lv_e_tab_bm  TYPE AFWBM_BM_CATE_T, "   
lv_i_valdate  TYPE AFWBM_VALDATE, "   
lv_version_not_found  TYPE AFWBM_VALDATE, "   
lv_i_version  TYPE AFW_TIMESTP, "   
lv_i_valdate_back  TYPE AFWCH_FLAG, "   
lv_i_keydate  TYPE AFW_KEYDATE, "   
lv_i_bypass_buffer  TYPE AFWCH_FLAG. "   

  CALL FUNCTION 'BM_PHASSIGN_GET'  "Reads the benchmarks assigned to a portfolio hierarchy
    EXPORTING
         I_SICHTID = lv_i_sichtid
         I_PHID = lv_i_phid
         I_ASS_VARI = lv_i_ass_vari
         I_VALDATE = lv_i_valdate
         I_VERSION = lv_i_version
         I_VALDATE_BACK = lv_i_valdate_back
         I_KEYDATE = lv_i_keydate
         I_BYPASS_BUFFER = lv_i_bypass_buffer
    IMPORTING
         E_STR_AFWBMPH = lv_e_str_afwbmph
         E_TAB_NODE_BMID = lv_e_tab_node_bmid
         E_TAB_AFWBM_REASON = lv_e_tab_afwbm_reason
         E_TAB_BM = lv_e_tab_bm
    EXCEPTIONS
        WRONG_PARAM = 1
        NOT_FOUND = 2
        HIST_NOT_FOUND = 3
        VERSION_NOT_FOUND = 4
. " BM_PHASSIGN_GET




ABAP code using 7.40 inline data declarations to call FM BM_PHASSIGN_GET

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!