SAP ISMAM_ORDER_ITEM_BP_ASS_MAINT Function Module for IS-M/AM: Edit Business Partner Assignment to Item
ISMAM_ORDER_ITEM_BP_ASS_MAINT is a standard ismam order item bp ass maint SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/AM: Edit Business Partner Assignment to Item 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 ismam order item bp ass maint FM, simply by entering the name ISMAM_ORDER_ITEM_BP_ASS_MAINT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JHA12
Program Name: SAPLJHA12
Main Program: SAPLJHA12
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISMAM_ORDER_ITEM_BP_ASS_MAINT 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 'ISMAM_ORDER_ITEM_BP_ASS_MAINT'"IS-M/AM: Edit Business Partner Assignment to Item.
EXPORTING
* PV_TRTYP = 'V' "Transaction Type
PT_RJHAPA = "IS-M/AM: Sales Document - Ad Item
PT_RJHAPS = "IS-M/AM: Sales Document - Ad Insert Item
PT_RJHAPW = "IS-M/AM: Sales Document - Commercial Item
PT_RJHAE = "IS-M/AM: Sales Document - Schedule Line
PT_RJHAEA = "IS-M/AM: Sales Document - Ad Schedule Line
PT_RJHAES = "IS-M/AM: Sales Document - Ad Insert Schedule Line
PT_RJHAEW = "IS-M/AM: Sales Document - Commercial Schedule Line
PT_RJHAISZ = "IS-M/AM: Sales Document - Advertiser Assignment
PT_RJHAGPZX = "
PT_RJHAISZX = "IS-M/AM: Advertiser Assignment Processing Information
PS_RJHALLG = "
PS_RJHAK = "
PS_RJHAP = "IS-M/AM: Order-Publishing-Media Item Structure
* PS_RJHAPA = "IS-M: Order-Publishing-Media Item Ad Structure
* PS_RJHAPS = "IS-M/AM: Order-Publishing-Media Ad Insert Item Structure
* PS_RJHAPW = "IS-PAM: Structure of OPM Commercial Item
PS_RJHAKX = "IS-M/AM: Sales Document Header Processing Information
PT_RJHAP = "IS-M/AM: Sales Document - Item
CHANGING
PT_RJHAGPZ = "IS-M/AM: Sales Document - Business Partner Assignment
PT_RJGTSADR = "IS-M: Address
* PT_RETURN = "Return Table
IMPORTING Parameters details for ISMAM_ORDER_ITEM_BP_ASS_MAINT
PV_TRTYP - Transaction Type
Data type: TRTYPDefault: 'V'
Optional: Yes
Call by Reference: Yes
PT_RJHAPA - IS-M/AM: Sales Document - Ad Item
Data type: RJHAPA_TABOptional: No
Call by Reference: Yes
PT_RJHAPS - IS-M/AM: Sales Document - Ad Insert Item
Data type: RJHAPS_TABOptional: No
Call by Reference: Yes
PT_RJHAPW - IS-M/AM: Sales Document - Commercial Item
Data type: RJHAPW_TABOptional: No
Call by Reference: Yes
PT_RJHAE - IS-M/AM: Sales Document - Schedule Line
Data type: RJHAE_TABOptional: No
Call by Reference: Yes
PT_RJHAEA - IS-M/AM: Sales Document - Ad Schedule Line
Data type: RJHAEA_TABOptional: No
Call by Reference: Yes
PT_RJHAES - IS-M/AM: Sales Document - Ad Insert Schedule Line
Data type: RJHAES_TABOptional: No
Call by Reference: Yes
PT_RJHAEW - IS-M/AM: Sales Document - Commercial Schedule Line
Data type: RJHAEW_TABOptional: No
Call by Reference: Yes
PT_RJHAISZ - IS-M/AM: Sales Document - Advertiser Assignment
Data type: RJHAISZ_TABOptional: No
Call by Reference: Yes
PT_RJHAGPZX -
Data type: RJHAGPZX_TABOptional: No
Call by Reference: Yes
PT_RJHAISZX - IS-M/AM: Advertiser Assignment Processing Information
Data type: RJHAISZX_TABOptional: No
Call by Reference: Yes
PS_RJHALLG -
Data type: RJHALLGOptional: No
Call by Reference: Yes
PS_RJHAK -
Data type: RJHAKOptional: No
Call by Reference: Yes
PS_RJHAP - IS-M/AM: Order-Publishing-Media Item Structure
Data type: RJHAPOptional: No
Call by Reference: Yes
PS_RJHAPA - IS-M: Order-Publishing-Media Item Ad Structure
Data type: RJHAPAOptional: Yes
Call by Reference: Yes
PS_RJHAPS - IS-M/AM: Order-Publishing-Media Ad Insert Item Structure
Data type: RJHAPSOptional: Yes
Call by Reference: Yes
PS_RJHAPW - IS-PAM: Structure of OPM Commercial Item
Data type: RJHAPWOptional: Yes
Call by Reference: Yes
PS_RJHAKX - IS-M/AM: Sales Document Header Processing Information
Data type: RJHAKXOptional: No
Call by Reference: Yes
PT_RJHAP - IS-M/AM: Sales Document - Item
Data type: RJHAP_TABOptional: No
Call by Reference: Yes
CHANGING Parameters details for ISMAM_ORDER_ITEM_BP_ASS_MAINT
PT_RJHAGPZ - IS-M/AM: Sales Document - Business Partner Assignment
Data type: RJHAGPZ_TABOptional: No
Call by Reference: Yes
PT_RJGTSADR - IS-M: Address
Data type: RJGTSADR_TABOptional: No
Call by Reference: Yes
PT_RETURN - Return Table
Data type: BAPIRET2_TOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ISMAM_ORDER_ITEM_BP_ASS_MAINT 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_pv_trtyp | TYPE TRTYP, " 'V' | |||
| lv_pt_rjhagpz | TYPE RJHAGPZ_TAB, " | |||
| lv_pt_rjhapa | TYPE RJHAPA_TAB, " | |||
| lv_pt_rjhaps | TYPE RJHAPS_TAB, " | |||
| lv_pt_rjhapw | TYPE RJHAPW_TAB, " | |||
| lv_pt_rjhae | TYPE RJHAE_TAB, " | |||
| lv_pt_rjhaea | TYPE RJHAEA_TAB, " | |||
| lv_pt_rjhaes | TYPE RJHAES_TAB, " | |||
| lv_pt_rjhaew | TYPE RJHAEW_TAB, " | |||
| lv_pt_rjhaisz | TYPE RJHAISZ_TAB, " | |||
| lv_pt_rjhagpzx | TYPE RJHAGPZX_TAB, " | |||
| lv_pt_rjhaiszx | TYPE RJHAISZX_TAB, " | |||
| lv_ps_rjhallg | TYPE RJHALLG, " | |||
| lv_pt_rjgtsadr | TYPE RJGTSADR_TAB, " | |||
| lv_ps_rjhak | TYPE RJHAK, " | |||
| lv_pt_return | TYPE BAPIRET2_T, " | |||
| lv_ps_rjhap | TYPE RJHAP, " | |||
| lv_ps_rjhapa | TYPE RJHAPA, " | |||
| lv_ps_rjhaps | TYPE RJHAPS, " | |||
| lv_ps_rjhapw | TYPE RJHAPW, " | |||
| lv_ps_rjhakx | TYPE RJHAKX, " | |||
| lv_pt_rjhap | TYPE RJHAP_TAB. " |
|   CALL FUNCTION 'ISMAM_ORDER_ITEM_BP_ASS_MAINT' "IS-M/AM: Edit Business Partner Assignment to Item |
| EXPORTING | ||
| PV_TRTYP | = lv_pv_trtyp | |
| PT_RJHAPA | = lv_pt_rjhapa | |
| PT_RJHAPS | = lv_pt_rjhaps | |
| PT_RJHAPW | = lv_pt_rjhapw | |
| PT_RJHAE | = lv_pt_rjhae | |
| PT_RJHAEA | = lv_pt_rjhaea | |
| PT_RJHAES | = lv_pt_rjhaes | |
| PT_RJHAEW | = lv_pt_rjhaew | |
| PT_RJHAISZ | = lv_pt_rjhaisz | |
| PT_RJHAGPZX | = lv_pt_rjhagpzx | |
| PT_RJHAISZX | = lv_pt_rjhaiszx | |
| PS_RJHALLG | = lv_ps_rjhallg | |
| PS_RJHAK | = lv_ps_rjhak | |
| PS_RJHAP | = lv_ps_rjhap | |
| PS_RJHAPA | = lv_ps_rjhapa | |
| PS_RJHAPS | = lv_ps_rjhaps | |
| PS_RJHAPW | = lv_ps_rjhapw | |
| PS_RJHAKX | = lv_ps_rjhakx | |
| PT_RJHAP | = lv_pt_rjhap | |
| CHANGING | ||
| PT_RJHAGPZ | = lv_pt_rjhagpz | |
| PT_RJGTSADR | = lv_pt_rjgtsadr | |
| PT_RETURN | = lv_pt_return | |
| . " ISMAM_ORDER_ITEM_BP_ASS_MAINT | ||
ABAP code using 7.40 inline data declarations to call FM ISMAM_ORDER_ITEM_BP_ASS_MAINT
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.| DATA(ld_pv_trtyp) | = 'V'. | |||
Search for further information about these or an SAP related objects