SAP ISH_EXPORT_PATIENT_RECORD Function Module for
ISH_EXPORT_PATIENT_RECORD is a standard ish export patient record 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 export patient record FM, simply by entering the name ISH_EXPORT_PATIENT_RECORD into the relevant SAP transaction such as SE37 or SE38.
Function Group: N030
Program Name: SAPLN030
Main Program: SAPLN030
Appliation area: N
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISH_EXPORT_PATIENT_RECORD 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_EXPORT_PATIENT_RECORD'".
EXPORTING
SS_EINRI = "Institution
* SS_FALAR = '1' "Case type for case
* SS_FALNR = ' ' "Case no.
* SS_ORGFA = ' ' "Departmental OU
* SS_ORGPF = ' ' "Treatment OU
SS_PATNR = "Patient number
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_SAPLN030_001 IS-H: Create Sort String when Generating Worklists in MRM
EXIT_SAPLN030_002 IS-H: Create an External Document ID when Creating a Medical Record
EXIT_SAPLN030_003 IS-H: Prevent Automatic Creation of Medical Records by Movement
IMPORTING Parameters details for ISH_EXPORT_PATIENT_RECORD
SS_EINRI - Institution
Data type: NBEW-EINRIOptional: No
Call by Reference: No ( called with pass by value option)
SS_FALAR - Case type for case
Data type: NFAL-FALARDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SS_FALNR - Case no.
Data type: NFAL-FALNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SS_ORGFA - Departmental OU
Data type: NBEW-ORGFADefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SS_ORGPF - Treatment OU
Data type: NBEW-ORGPFDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SS_PATNR - Patient number
Data type: NPAT-PATNROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISH_EXPORT_PATIENT_RECORD 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_ss_einri | TYPE NBEW-EINRI, " | |||
| lv_ss_falar | TYPE NFAL-FALAR, " '1' | |||
| lv_ss_falnr | TYPE NFAL-FALNR, " SPACE | |||
| lv_ss_orgfa | TYPE NBEW-ORGFA, " SPACE | |||
| lv_ss_orgpf | TYPE NBEW-ORGPF, " SPACE | |||
| lv_ss_patnr | TYPE NPAT-PATNR. " |
|   CALL FUNCTION 'ISH_EXPORT_PATIENT_RECORD' " |
| EXPORTING | ||
| SS_EINRI | = lv_ss_einri | |
| SS_FALAR | = lv_ss_falar | |
| SS_FALNR | = lv_ss_falnr | |
| SS_ORGFA | = lv_ss_orgfa | |
| SS_ORGPF | = lv_ss_orgpf | |
| SS_PATNR | = lv_ss_patnr | |
| . " ISH_EXPORT_PATIENT_RECORD | ||
ABAP code using 7.40 inline data declarations to call FM ISH_EXPORT_PATIENT_RECORD
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 NBEW INTO @DATA(ld_ss_einri). | ||||
| "SELECT single FALAR FROM NFAL INTO @DATA(ld_ss_falar). | ||||
| DATA(ld_ss_falar) | = '1'. | |||
| "SELECT single FALNR FROM NFAL INTO @DATA(ld_ss_falnr). | ||||
| DATA(ld_ss_falnr) | = ' '. | |||
| "SELECT single ORGFA FROM NBEW INTO @DATA(ld_ss_orgfa). | ||||
| DATA(ld_ss_orgfa) | = ' '. | |||
| "SELECT single ORGPF FROM NBEW INTO @DATA(ld_ss_orgpf). | ||||
| DATA(ld_ss_orgpf) | = ' '. | |||
| "SELECT single PATNR FROM NPAT INTO @DATA(ld_ss_patnr). | ||||
Search for further information about these or an SAP related objects