SAP ISH_CASE_PARALLEL_EXIST Function Module for









ISH_CASE_PARALLEL_EXIST is a standard ish case parallel exist 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 case parallel exist FM, simply by entering the name ISH_CASE_PARALLEL_EXIST into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_CASE_PARALLEL_EXIST 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_CASE_PARALLEL_EXIST'"
EXPORTING
I_EINRI = "Institution
I_PATNR = "
* I_PATNR_2 = "
* I_FALNR_EXCL = "
* I_VISIT_DATE = "
* I_VISIT_TIME = "
I_MODE = "Call Mode
* I_DIALOG = ON "
* I_ACTION = 'C' "

IMPORTING
E_RETMAXTYPE = "Most Severe Message Type -> F2
E_STAY_ON_SCREEN = "
E_PARALLEL_CASE_EXIST = "

CHANGING
* T_RETURN = "Table with Error Messages
.



IMPORTING Parameters details for ISH_CASE_PARALLEL_EXIST

I_EINRI - Institution

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

I_PATNR -

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

I_PATNR_2 -

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

I_FALNR_EXCL -

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

I_VISIT_DATE -

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

I_VISIT_TIME -

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

I_MODE - Call Mode

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

I_DIALOG -

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

I_ACTION -

Data type: TNPOL-ACTIO
Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISH_CASE_PARALLEL_EXIST

E_RETMAXTYPE - Most Severe Message Type -> F2

Data type: NPDOK-BAPIRETMAXTY
Optional: No
Call by Reference: No ( called with pass by value option)

E_STAY_ON_SCREEN -

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

E_PARALLEL_CASE_EXIST -

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

CHANGING Parameters details for ISH_CASE_PARALLEL_EXIST

T_RETURN - Table with Error Messages

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

Copy and paste ABAP code example for ISH_CASE_PARALLEL_EXIST 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_i_einri  TYPE NFAL-EINRI, "   
lv_t_return  TYPE ISH_BAPIRET2_TAB_TYPE, "   
lv_e_retmaxtype  TYPE NPDOK-BAPIRETMAXTY, "   
lv_i_patnr  TYPE NPAT-PATNR, "   
lv_e_stay_on_screen  TYPE ISH_TRUE_FALSE, "   
lv_i_patnr_2  TYPE NPAT-PATNR, "   
lv_e_parallel_case_exist  TYPE ISH_TRUE_FALSE, "   
lv_i_falnr_excl  TYPE NFAL-FALNR, "   
lv_i_visit_date  TYPE NBEW-BWIDT, "   
lv_i_visit_time  TYPE NBEW-BWIZT, "   
lv_i_mode  TYPE CHAR1, "   
lv_i_dialog  TYPE ISH_ON_OFF, "   ON
lv_i_action  TYPE TNPOL-ACTIO. "   'C'

  CALL FUNCTION 'ISH_CASE_PARALLEL_EXIST'  "
    EXPORTING
         I_EINRI = lv_i_einri
         I_PATNR = lv_i_patnr
         I_PATNR_2 = lv_i_patnr_2
         I_FALNR_EXCL = lv_i_falnr_excl
         I_VISIT_DATE = lv_i_visit_date
         I_VISIT_TIME = lv_i_visit_time
         I_MODE = lv_i_mode
         I_DIALOG = lv_i_dialog
         I_ACTION = lv_i_action
    IMPORTING
         E_RETMAXTYPE = lv_e_retmaxtype
         E_STAY_ON_SCREEN = lv_e_stay_on_screen
         E_PARALLEL_CASE_EXIST = lv_e_parallel_case_exist
    CHANGING
         T_RETURN = lv_t_return
. " ISH_CASE_PARALLEL_EXIST




ABAP code using 7.40 inline data declarations to call FM ISH_CASE_PARALLEL_EXIST

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 EINRI FROM NFAL INTO @DATA(ld_i_einri).
 
 
"SELECT single BAPIRETMAXTY FROM NPDOK INTO @DATA(ld_e_retmaxtype).
 
"SELECT single PATNR FROM NPAT INTO @DATA(ld_i_patnr).
 
 
"SELECT single PATNR FROM NPAT INTO @DATA(ld_i_patnr_2).
 
 
"SELECT single FALNR FROM NFAL INTO @DATA(ld_i_falnr_excl).
 
"SELECT single BWIDT FROM NBEW INTO @DATA(ld_i_visit_date).
 
"SELECT single BWIZT FROM NBEW INTO @DATA(ld_i_visit_time).
 
 
DATA(ld_i_dialog) = ON.
 
"SELECT single ACTIO FROM TNPOL INTO @DATA(ld_i_action).
DATA(ld_i_action) = 'C'.
 


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!