SAP ISH_SE_HANDLE_PATIENT Function Module for IS-H: Patient für SeviceEnabling
ISH_SE_HANDLE_PATIENT is a standard ish se handle patient 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-H: Patient für SeviceEnabling 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 ish se handle patient FM, simply by entering the name ISH_SE_HANDLE_PATIENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: N_API_SE_PATENC_PATIENT
Program Name: SAPLN_API_SE_PATENC_PATIENT
Main Program: SAPLN_API_SE_PATENC_PATIENT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISH_SE_HANDLE_PATIENT 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_SE_HANDLE_PATIENT'"IS-H: Patient für SeviceEnabling.
EXPORTING
I_EINRI = "IS-H: Einrichtung
* I_PATNR = "IS-H: Patientennummer
* IS_PAT_DATA = "IS-H: Patientendaten
* I_TESTRUN = 'X' "Testmodus (ON/OFF)
* I_CALL_FROM_BAPI = 'X' "Aufruf aus BAPI (ON/OFF)
IMPORTING
ET_RETURN = "Returntabelle
E_RETMAXTYPE = "IS-H: Maximal (schlimmster) aufgetretener Nachrichtentyp
E_PATNR = "IS-H: Patientennummer
ES_NPAT = "IS-H: Stammdaten Patient (allgemein)
ES_NPAE = "IS-H: Stammdaten Patient (einrichtungsbezogen)
ES_NADR = "IS-H: Adressen (zentrale Adreßverwaltung)
IMPORTING Parameters details for ISH_SE_HANDLE_PATIENT
I_EINRI - IS-H: Einrichtung
Data type: EINRIOptional: No
Call by Reference: No ( called with pass by value option)
I_PATNR - IS-H: Patientennummer
Data type: NPAT-PATNROptional: Yes
Call by Reference: No ( called with pass by value option)
IS_PAT_DATA - IS-H: Patientendaten
Data type: NPATIENTSEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TESTRUN - Testmodus (ON/OFF)
Data type: ISH_ON_OFFDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CALL_FROM_BAPI - Aufruf aus BAPI (ON/OFF)
Data type: ISH_ON_OFFDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISH_SE_HANDLE_PATIENT
ET_RETURN - Returntabelle
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
E_RETMAXTYPE - IS-H: Maximal (schlimmster) aufgetretener Nachrichtentyp
Data type: NPDOK-BAPIRETMAXTYOptional: No
Call by Reference: No ( called with pass by value option)
E_PATNR - IS-H: Patientennummer
Data type: NPAT-PATNROptional: No
Call by Reference: No ( called with pass by value option)
ES_NPAT - IS-H: Stammdaten Patient (allgemein)
Data type: NPATOptional: No
Call by Reference: No ( called with pass by value option)
ES_NPAE - IS-H: Stammdaten Patient (einrichtungsbezogen)
Data type: NPAEOptional: No
Call by Reference: No ( called with pass by value option)
ES_NADR - IS-H: Adressen (zentrale Adreßverwaltung)
Data type: NADROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISH_SE_HANDLE_PATIENT 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 EINRI, " | |||
| lv_et_return | TYPE BAPIRET2_T, " | |||
| lv_i_patnr | TYPE NPAT-PATNR, " | |||
| lv_e_retmaxtype | TYPE NPDOK-BAPIRETMAXTY, " | |||
| lv_e_patnr | TYPE NPAT-PATNR, " | |||
| lv_is_pat_data | TYPE NPATIENTSE, " | |||
| lv_es_npat | TYPE NPAT, " | |||
| lv_i_testrun | TYPE ISH_ON_OFF, " 'X' | |||
| lv_es_npae | TYPE NPAE, " | |||
| lv_i_call_from_bapi | TYPE ISH_ON_OFF, " 'X' | |||
| lv_es_nadr | TYPE NADR. " |
|   CALL FUNCTION 'ISH_SE_HANDLE_PATIENT' "IS-H: Patient für SeviceEnabling |
| EXPORTING | ||
| I_EINRI | = lv_i_einri | |
| I_PATNR | = lv_i_patnr | |
| IS_PAT_DATA | = lv_is_pat_data | |
| I_TESTRUN | = lv_i_testrun | |
| I_CALL_FROM_BAPI | = lv_i_call_from_bapi | |
| IMPORTING | ||
| ET_RETURN | = lv_et_return | |
| E_RETMAXTYPE | = lv_e_retmaxtype | |
| E_PATNR | = lv_e_patnr | |
| ES_NPAT | = lv_es_npat | |
| ES_NPAE | = lv_es_npae | |
| ES_NADR | = lv_es_nadr | |
| . " ISH_SE_HANDLE_PATIENT | ||
ABAP code using 7.40 inline data declarations to call FM ISH_SE_HANDLE_PATIENT
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 PATNR FROM NPAT INTO @DATA(ld_i_patnr). | ||||
| "SELECT single BAPIRETMAXTY FROM NPDOK INTO @DATA(ld_e_retmaxtype). | ||||
| "SELECT single PATNR FROM NPAT INTO @DATA(ld_e_patnr). | ||||
| DATA(ld_i_testrun) | = 'X'. | |||
| DATA(ld_i_call_from_bapi) | = 'X'. | |||
Search for further information about these or an SAP related objects