BM_PHASSIGN_INSERT SAP Function module - Insert History/Version of Assignment Variant

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

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

Pattern for FM BM_PHASSIGN_INSERT - BM PHASSIGN INSERT

CALL FUNCTION 'BM_PHASSIGN_INSERT' "Insert History/Version of Assignment Variant
  EXPORTING
    i_str_afwbmph =             " afwbmph_str   TRM: Auxiliary Structure for Transaction AFWBMPH
    i_tab_node_bmid =           " afwbm_node_bmid_t  Table Type for Internal Table for BM_PHASSIGN_GET
    i_tab_afwbm_reason =        " afwbm_reason_t  Table Type for AFWBM_REASON
  EXCEPTIONS
    ENTRY_EXIST = 1             "               Entry already exists
    ERROR_INSERT = 2            "               Error when creating data
    WRONG_PARAM = 3             "               Parameter Error
    .  "  BM_PHASSIGN_INSERT

ABAP code example for Function Module BM_PHASSIGN_INSERT

The ABAP code below is a full code listing to execute function module BM_PHASSIGN_INSERT 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_i_str_afwbmph) = 'Check type of data required'.

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

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

CALL FUNCTION 'BM_PHASSIGN_INSERT'
  EXPORTING
    i_str_afwbmph =              ld_i_str_afwbmph
    i_tab_node_bmid =            ld_i_tab_node_bmid
    i_tab_afwbm_reason =         ld_i_tab_afwbm_reason
  EXCEPTIONS
    ENTRY_EXIST =                1
    ERROR_INSERT =               2
    WRONG_PARAM =                3
    .  "  BM_PHASSIGN_INSERT

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_i_str_afwbmph
 
 TYPE AFWBMPH_STR ,
ld_i_tab_node_bmid
 
 TYPE AFWBM_NODE_BMID_T ,
ld_i_tab_afwbm_reason
 
 TYPE AFWBM_REASON_T .


ld_i_str_afwbmph = 'Check type of data required'.
ld_i_tab_node_bmid = 'Check type of data required'.
ld_i_tab_afwbm_reason = 'Check type of data required'.