ISM_BU_SELECTION_CHECK SAP Function module - IS-M: Check Selection According to Booking Units

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

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

Pattern for FM ISM_BU_SELECTION_CHECK - ISM BU SELECTION CHECK

CALL FUNCTION 'ISM_BU_SELECTION_CHECK' "IS-M: Check Selection According to Booking Units
  EXPORTING
    pv_belegeinh =              " jhabpz-belegeinh  IS-M/AM: Booking Unit
    pv_seldat_von =             " jhap-seldat_von  IS-M: Start Date for Item
    pv_pos_art =                " jhap-pos_art  IS-M: Order-Publishing-Media - Item Type
    pv_item_search_bu =         " ism_way_item_search_per_bu  IS-M/AM: Search Type for Booking Unit Selection
  IMPORTING
    pt_jhabpz =                 " jha1_yjhabpz_tab
  CHANGING
    pt_item =                   " table
  EXCEPTIONS
    BELEGEINH_NOT_FOUND = 1     "
    .  "  ISM_BU_SELECTION_CHECK

ABAP code example for Function Module ISM_BU_SELECTION_CHECK

The ABAP code below is a full code listing to execute function module ISM_BU_SELECTION_CHECK 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_pt_jhabpz  
 
 TYPE JHA1_YJHABPZ_TAB
.


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

SELECT single BELEGEINH 
  FROM JHABPZ 
  INTO @DATA(ld_pv_belegeinh).

 

SELECT single SELDAT_VON 
  FROM JHAP 
  INTO @DATA(ld_pv_seldat_von).

 

SELECT single POS_ART 
  FROM JHAP 
  INTO @DATA(ld_pv_pos_art).


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

CALL FUNCTION 'ISM_BU_SELECTION_CHECK'
  EXPORTING
    pv_belegeinh =               ld_pv_belegeinh
    pv_seldat_von =              ld_pv_seldat_von
    pv_pos_art =                 ld_pv_pos_art
    pv_item_search_bu =          ld_pv_item_search_bu
  IMPORTING
    pt_jhabpz =                  ld_pt_jhabpz
  CHANGING
    pt_item =                    ld_pt_item
  EXCEPTIONS
    BELEGEINH_NOT_FOUND =        1
    .  "  ISM_BU_SELECTION_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_pt_item
 
 TYPE TABLE ,
ld_pt_jhabpz
 
 TYPE JHA1_YJHABPZ_TAB ,
ld_pv_belegeinh
 
 TYPE JHABPZ-BELEGEINH ,
ld_pv_seldat_von
 
 TYPE JHAP-SELDAT_VON ,
ld_pv_pos_art
 
 TYPE JHAP-POS_ART ,
ld_pv_item_search_bu
 
 TYPE ISM_WAY_ITEM_SEARCH_PER_BU .


ld_pt_item = 'Check type of data required'.

SELECT single BELEGEINH 
  FROM JHABPZ 
  INTO ld_pv_belegeinh.


SELECT single SELDAT_VON 
  FROM JHAP 
  INTO ld_pv_seldat_von.


SELECT single POS_ART 
  FROM JHAP 
  INTO ld_pv_pos_art.

ld_pv_item_search_bu = 'Check type of data required'.