SAP ISH_BADI_API_PREREQUISITS_CALL Function Module for









ISH_BADI_API_PREREQUISITS_CALL is a standard ish badi api prerequisits call SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ish badi api prerequisits call FM, simply by entering the name ISH_BADI_API_PREREQUISITS_CALL into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_BADI_API_PREREQUISITS_CALL 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 'ISH_BADI_API_PREREQUISITS_CALL'"
  EXPORTING
   I_INSTITUTION =  "Institution
   I_FCODE =  "Function Code
*  I_DIALOG_NOT_ALLOWED = ' ' "Dialog Screen not Allowed (ON) / Allowed (OFF) in BAdI
   I_STRUCTURE_NAME =  "Name of Structure for the API/BAPI Data
   I_PATNR =  "Patient
*  I_FALNR =  "Case
*  I_LFDNR =  "Sequence Number of the Movement

 IMPORTING
   E_ACTIV =  "

CHANGING
   C_DATA =  "Structure with Data for the API/BAPI
   C_MESSAGE =  "Message Table
   C_WORST_MESSAGE_TYPE =  "Worst Message Type Returned
.



IMPORTING Parameters details for ISH_BADI_API_PREREQUISITS_CALL

I_INSTITUTION - Institution

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

I_FCODE - Function Code

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

I_DIALOG_NOT_ALLOWED - Dialog Screen not Allowed (ON) / Allowed (OFF) in BAdI

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

I_STRUCTURE_NAME - Name of Structure for the API/BAPI Data

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

I_PATNR - Patient

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

I_FALNR - Case

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

I_LFDNR - Sequence Number of the Movement

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

EXPORTING Parameters details for ISH_BADI_API_PREREQUISITS_CALL

E_ACTIV -

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

CHANGING Parameters details for ISH_BADI_API_PREREQUISITS_CALL

C_DATA - Structure with Data for the API/BAPI

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

C_MESSAGE - Message Table

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

C_WORST_MESSAGE_TYPE - Worst Message Type Returned

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

Copy and paste ABAP code example for ISH_BADI_API_PREREQUISITS_CALL 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_c_data  TYPE ANY, "   
lv_e_activ  TYPE ISH_ON_OFF, "   
lv_i_institution  TYPE EINRI, "   
lv_i_fcode  TYPE ISH_API_PRG_FUNC, "   
lv_c_message  TYPE ISH_BAPIRET2_TAB_TYPE, "   
lv_c_worst_message_type  TYPE ISH_BAPIRETMAXTY, "   
lv_i_dialog_not_allowed  TYPE ISH_ON_OFF, "   ' '
lv_i_structure_name  TYPE CHAR30, "   
lv_i_patnr  TYPE PATNR, "   
lv_i_falnr  TYPE FALNR, "   
lv_i_lfdnr  TYPE LFDBEW. "   

  CALL FUNCTION 'ISH_BADI_API_PREREQUISITS_CALL'  "
    EXPORTING
         I_INSTITUTION = lv_i_institution
         I_FCODE = lv_i_fcode
         I_DIALOG_NOT_ALLOWED = lv_i_dialog_not_allowed
         I_STRUCTURE_NAME = lv_i_structure_name
         I_PATNR = lv_i_patnr
         I_FALNR = lv_i_falnr
         I_LFDNR = lv_i_lfdnr
    IMPORTING
         E_ACTIV = lv_e_activ
    CHANGING
         C_DATA = lv_c_data
         C_MESSAGE = lv_c_message
         C_WORST_MESSAGE_TYPE = lv_c_worst_message_type
. " ISH_BADI_API_PREREQUISITS_CALL




ABAP code using 7.40 inline data declarations to call FM ISH_BADI_API_PREREQUISITS_CALL

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_i_dialog_not_allowed) = ' '.
 
 
 
 
 


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!