SAP ISM_FIRST_BE_AND_IKO_GET Function Module for IS-M/AM: Determine First Booking Unit, Content Component and Other Data









ISM_FIRST_BE_AND_IKO_GET is a standard ism first be and iko 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 IS-M/AM: Determine First Booking Unit, Content Component and Other Data 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 ism first be and iko get FM, simply by entering the name ISM_FIRST_BE_AND_IKO_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_FIRST_BE_AND_IKO_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 'ISM_FIRST_BE_AND_IKO_GET'"IS-M/AM: Determine First Booking Unit, Content Component and Other Data
EXPORTING
PV_AVM_NR = "IS-M: Order
PV_POS_NR = "IS-M: Order Item Number
PT_RJHABPZ = "
PT_RJHAIKZ = "

IMPORTING
PS_RJHAIKZ = "IS-M/AM: Structure of Item/Booking Unit/Cont.Comp.Assignment
PS_RJHABPZ = "IS-M/AM: Booking Unit OPM_ITEM Assignment

CHANGING
* PV_BELEGEINH = "IS-M/AM: Booking Unit
* PV_SUM_KONTAKTZAHL = "
* PV_BE_KURZ = "IS-M: Short Text
* PV_INHK_TECH1 = "IS-M: Technical content component (positioning view)
* PV_INHKT_TEXT = "IS-M: Short Text
* PV_SOLL_KONTAKTZAHL = "IS-M/AM: Target Gross Impressions for Online Advertising
* PV_UNIT_OL = "IS-M/AM: Unit of Measure for Online Advertising
* PV_PLAZ_ONL = "IS-M: Online Positioning Instruction
* PV_PLZONL_TEXT = "IS-M: Short Text
* PV_XBEIKOZUO = "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLJHPA_001 IS-M/AM: Set Status Characteristics for an Ad Item
EXIT_SAPLJHPA_002 IS-M/AM: Set Status Characteristics for an Ad Insert Item
EXIT_SAPLJHPA_003 IS-M/AM: Set Status Characteristics for a Service Item
EXIT_SAPLJHPA_004 IS-M/AM: Box Number Assignment
EXIT_SAPLJHPA_006 IS-M/AM: Check Completeness and Plausibility of an Item
EXIT_SAPLJHPA_007 IS-M/AM: Define Default Item
EXIT_SAPLJHPA_008 IS-M/AM: Check Completeness and Plausibility of Date Information
EXIT_SAPLJHPA_009 IS-M/AM: Modification of F4 Help for Content Components
EXIT_SAPLJHPA_010 IS-M/AM: Modify Advertiser Assignment
EXIT_SAPLJHPA_011 IS-M/AM: Menu Exit OPM Item Details
EXIT_SAPLJHPA_012 IS-M/AM: Set Status Characteristics for a Commercial Item
EXIT_SAPLJHPA_013 IS-M/AM: Define Default Item Category
EXIT_SAPLJHPA_014 IS-M/AM: Represent Dependencies for Item Characteristics
EXIT_SAPLJHPA_015 IS-M/AM: Set Status Characteristics for a Distribution Item
EXIT_SAPLJHPA_016 IS-M/AM: Set Status Characteristics for an Online Item
EXIT_SAPLJHPA_017 IS-M/AM: Trigger Billing Dataset Generation
EXIT_SAPLJHPA_018 IS-M/AM: Check Completeness and Plausibility of an Item
EXIT_SAPLJHPA_019 IS-M/AM: Trigger Schedule Line Generation
EXIT_SAPLJHPA_020 IS-M/AM: Set Status Characteristics for a Package Item

IMPORTING Parameters details for ISM_FIRST_BE_AND_IKO_GET

PV_AVM_NR - IS-M: Order

Data type: RJHAP-AVM_NR
Optional: No
Call by Reference: Yes

PV_POS_NR - IS-M: Order Item Number

Data type: RJHAP-POS_NR
Optional: No
Call by Reference: Yes

PT_RJHABPZ -

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

PT_RJHAIKZ -

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

EXPORTING Parameters details for ISM_FIRST_BE_AND_IKO_GET

PS_RJHAIKZ - IS-M/AM: Structure of Item/Booking Unit/Cont.Comp.Assignment

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

PS_RJHABPZ - IS-M/AM: Booking Unit OPM_ITEM Assignment

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

CHANGING Parameters details for ISM_FIRST_BE_AND_IKO_GET

PV_BELEGEINH - IS-M/AM: Booking Unit

Data type: RJHAIKZ-BELEGEINH
Optional: Yes
Call by Reference: Yes

PV_SUM_KONTAKTZAHL -

Data type: RJHAIKZ-SOLL_KONTAKTZAHL
Optional: Yes
Call by Reference: Yes

PV_BE_KURZ - IS-M: Short Text

Data type: RJHAIKZ-BE_KURZ
Optional: Yes
Call by Reference: Yes

PV_INHK_TECH1 - IS-M: Technical content component (positioning view)

Data type: RJHAIKZ-INHK_TECH1
Optional: Yes
Call by Reference: Yes

PV_INHKT_TEXT - IS-M: Short Text

Data type: RJHAIKZ-INHKT_TEXT
Optional: Yes
Call by Reference: Yes

PV_SOLL_KONTAKTZAHL - IS-M/AM: Target Gross Impressions for Online Advertising

Data type: RJHAIKZ-SOLL_KONTAKTZAHL
Optional: Yes
Call by Reference: Yes

PV_UNIT_OL - IS-M/AM: Unit of Measure for Online Advertising

Data type: RJHAIKZ-UNIT_OL
Optional: Yes
Call by Reference: Yes

PV_PLAZ_ONL - IS-M: Online Positioning Instruction

Data type: RJHAIKZ-PLAZ_ONL
Optional: Yes
Call by Reference: Yes

PV_PLZONL_TEXT - IS-M: Short Text

Data type: RJHAIKZ-PLZONL_TEXT
Optional: Yes
Call by Reference: Yes

PV_XBEIKOZUO -

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

Copy and paste ABAP code example for ISM_FIRST_BE_AND_IKO_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_pv_avm_nr  TYPE RJHAP-AVM_NR, "   
lv_ps_rjhaikz  TYPE RJHAIKZ, "   
lv_pv_belegeinh  TYPE RJHAIKZ-BELEGEINH, "   
lv_pv_sum_kontaktzahl  TYPE RJHAIKZ-SOLL_KONTAKTZAHL, "   
lv_pv_pos_nr  TYPE RJHAP-POS_NR, "   
lv_ps_rjhabpz  TYPE RJHABPZ, "   
lv_pv_be_kurz  TYPE RJHAIKZ-BE_KURZ, "   
lv_pt_rjhabpz  TYPE JHA1_RJHABPZ_TAB, "   
lv_pv_inhk_tech1  TYPE RJHAIKZ-INHK_TECH1, "   
lv_pt_rjhaikz  TYPE JHA1_RJHAIKZ_TAB, "   
lv_pv_inhkt_text  TYPE RJHAIKZ-INHKT_TEXT, "   
lv_pv_soll_kontaktzahl  TYPE RJHAIKZ-SOLL_KONTAKTZAHL, "   
lv_pv_unit_ol  TYPE RJHAIKZ-UNIT_OL, "   
lv_pv_plaz_onl  TYPE RJHAIKZ-PLAZ_ONL, "   
lv_pv_plzonl_text  TYPE RJHAIKZ-PLZONL_TEXT, "   
lv_pv_xbeikozuo  TYPE XFELD. "   

  CALL FUNCTION 'ISM_FIRST_BE_AND_IKO_GET'  "IS-M/AM: Determine First Booking Unit, Content Component and Other Data
    EXPORTING
         PV_AVM_NR = lv_pv_avm_nr
         PV_POS_NR = lv_pv_pos_nr
         PT_RJHABPZ = lv_pt_rjhabpz
         PT_RJHAIKZ = lv_pt_rjhaikz
    IMPORTING
         PS_RJHAIKZ = lv_ps_rjhaikz
         PS_RJHABPZ = lv_ps_rjhabpz
    CHANGING
         PV_BELEGEINH = lv_pv_belegeinh
         PV_SUM_KONTAKTZAHL = lv_pv_sum_kontaktzahl
         PV_BE_KURZ = lv_pv_be_kurz
         PV_INHK_TECH1 = lv_pv_inhk_tech1
         PV_INHKT_TEXT = lv_pv_inhkt_text
         PV_SOLL_KONTAKTZAHL = lv_pv_soll_kontaktzahl
         PV_UNIT_OL = lv_pv_unit_ol
         PV_PLAZ_ONL = lv_pv_plaz_onl
         PV_PLZONL_TEXT = lv_pv_plzonl_text
         PV_XBEIKOZUO = lv_pv_xbeikozuo
. " ISM_FIRST_BE_AND_IKO_GET




ABAP code using 7.40 inline data declarations to call FM ISM_FIRST_BE_AND_IKO_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.

"SELECT single AVM_NR FROM RJHAP INTO @DATA(ld_pv_avm_nr).
 
 
"SELECT single BELEGEINH FROM RJHAIKZ INTO @DATA(ld_pv_belegeinh).
 
"SELECT single SOLL_KONTAKTZAHL FROM RJHAIKZ INTO @DATA(ld_pv_sum_kontaktzahl).
 
"SELECT single POS_NR FROM RJHAP INTO @DATA(ld_pv_pos_nr).
 
 
"SELECT single BE_KURZ FROM RJHAIKZ INTO @DATA(ld_pv_be_kurz).
 
 
"SELECT single INHK_TECH1 FROM RJHAIKZ INTO @DATA(ld_pv_inhk_tech1).
 
 
"SELECT single INHKT_TEXT FROM RJHAIKZ INTO @DATA(ld_pv_inhkt_text).
 
"SELECT single SOLL_KONTAKTZAHL FROM RJHAIKZ INTO @DATA(ld_pv_soll_kontaktzahl).
 
"SELECT single UNIT_OL FROM RJHAIKZ INTO @DATA(ld_pv_unit_ol).
 
"SELECT single PLAZ_ONL FROM RJHAIKZ INTO @DATA(ld_pv_plaz_onl).
 
"SELECT single PLZONL_TEXT FROM RJHAIKZ INTO @DATA(ld_pv_plzonl_text).
 
 


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!