SAP BM_PHASSIGN_MODIFY Function Module for AFWBM: Write and Delete Benchmark Attributes









BM_PHASSIGN_MODIFY is a standard bm phassign modify SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for AFWBM: Write and Delete Benchmark Attributes 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 modify FM, simply by entering the name BM_PHASSIGN_MODIFY 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_MODIFY 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_MODIFY'"AFWBM: Write and Delete Benchmark Attributes
  EXPORTING
   I_MODE =  "Mode 'NEW',  'UPD'  ,'DEL'
*  I_TAB_NODE_BMID =  "Table Type for Table Parameters for Composite Benchmark
*  I_TAB_AFWBM_REASON =  "Table Type for AFWBM_REASON
*  I_FLAG_HISTORY =  "X = Edit History
*  I_FLAG_VERSION =  "E = dependent data, do not delete old version
*  I_OLD_VERSION =  "Old Version

CHANGING
   C_STR_AFWBMPH =  "AFWBM: Work Structure for Benchmark

EXCEPTIONS
   WRONG_PARAM = 1    ERROR_CREATE = 2    ERROR_MODIFY = 3    ERROR_DELETE = 4
.



IMPORTING Parameters details for BM_PHASSIGN_MODIFY

I_MODE - Mode 'NEW', 'UPD' ,'DEL'

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

I_TAB_NODE_BMID - Table Type for Table Parameters for Composite Benchmark

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

I_TAB_AFWBM_REASON - Table Type for AFWBM_REASON

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

I_FLAG_HISTORY - X = Edit History

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

I_FLAG_VERSION - E = dependent data, do not delete old version

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

I_OLD_VERSION - Old Version

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

CHANGING Parameters details for BM_PHASSIGN_MODIFY

C_STR_AFWBMPH - AFWBM: Work Structure for Benchmark

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

EXCEPTIONS details

WRONG_PARAM - Combination of parameters in call is invalid

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_CREATE - Error when creating data

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_MODIFY - Change Error

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_DELETE - Error while deleting

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BM_PHASSIGN_MODIFY 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_mode  TYPE SYCHAR03, "   
lv_wrong_param  TYPE SYCHAR03, "   
lv_c_str_afwbmph  TYPE AFWBMPH_STR, "   
lv_error_create  TYPE AFWBMPH_STR, "   
lv_i_tab_node_bmid  TYPE AFWBM_NODE_BMID_T, "   
lv_error_modify  TYPE AFWBM_NODE_BMID_T, "   
lv_i_tab_afwbm_reason  TYPE AFWBM_REASON_T, "   
lv_error_delete  TYPE AFWBM_REASON_T, "   
lv_i_flag_history  TYPE AFWCH_FLAG, "   
lv_i_flag_version  TYPE AFWCH_FLAG, "   
lv_i_old_version  TYPE AFW_TIMESTP. "   

  CALL FUNCTION 'BM_PHASSIGN_MODIFY'  "AFWBM: Write and Delete Benchmark Attributes
    EXPORTING
         I_MODE = lv_i_mode
         I_TAB_NODE_BMID = lv_i_tab_node_bmid
         I_TAB_AFWBM_REASON = lv_i_tab_afwbm_reason
         I_FLAG_HISTORY = lv_i_flag_history
         I_FLAG_VERSION = lv_i_flag_version
         I_OLD_VERSION = lv_i_old_version
    CHANGING
         C_STR_AFWBMPH = lv_c_str_afwbmph
    EXCEPTIONS
        WRONG_PARAM = 1
        ERROR_CREATE = 2
        ERROR_MODIFY = 3
        ERROR_DELETE = 4
. " BM_PHASSIGN_MODIFY




ABAP code using 7.40 inline data declarations to call FM BM_PHASSIGN_MODIFY

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!