SAP ISH_MR_REQUEST_FOR_APP Function Module for









ISH_MR_REQUEST_FOR_APP is a standard ish mr request for app 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 mr request for app FM, simply by entering the name ISH_MR_REQUEST_FOR_APP into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_MR_REQUEST_FOR_APP 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_MR_REQUEST_FOR_APP'"
EXPORTING
I_EINRI = "Einrichtung
I_PATNR = "Patientennummer
I_TMNID = "ID eines Termins
I_ORGFA = "fachl. OrgEinheit für den Termin
* I_ORGFA_OLD = "vorherige fachl. OrgEinheit für den Termin
I_ORGPF = "behandelnde OrgEinheit für den Termin
* I_ORGPF_OLD = "vorherige behandelnde. OrgEinheit für den Termin
I_VCODE = "Verarbeitungsmodus
.




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_MR_REQUEST_FOR_APP

I_EINRI - Einrichtung

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

I_PATNR - Patientennummer

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

I_TMNID - ID eines Termins

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

I_ORGFA - fachl. OrgEinheit für den Termin

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

I_ORGFA_OLD - vorherige fachl. OrgEinheit für den Termin

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

I_ORGPF - behandelnde OrgEinheit für den Termin

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

I_ORGPF_OLD - vorherige behandelnde. OrgEinheit für den Termin

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

I_VCODE - Verarbeitungsmodus

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

Copy and paste ABAP code example for ISH_MR_REQUEST_FOR_APP 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_i_patnr  TYPE PATNR, "   
lv_i_tmnid  TYPE ISH_TMNID, "   
lv_i_orgfa  TYPE NAPP-ORGFA, "   
lv_i_orgfa_old  TYPE NAPP-ORGFA, "   
lv_i_orgpf  TYPE NAPP-ORGPF, "   
lv_i_orgpf_old  TYPE NAPP-ORGPF, "   
lv_i_vcode  TYPE ISH_VCODE. "   

  CALL FUNCTION 'ISH_MR_REQUEST_FOR_APP'  "
    EXPORTING
         I_EINRI = lv_i_einri
         I_PATNR = lv_i_patnr
         I_TMNID = lv_i_tmnid
         I_ORGFA = lv_i_orgfa
         I_ORGFA_OLD = lv_i_orgfa_old
         I_ORGPF = lv_i_orgpf
         I_ORGPF_OLD = lv_i_orgpf_old
         I_VCODE = lv_i_vcode
. " ISH_MR_REQUEST_FOR_APP




ABAP code using 7.40 inline data declarations to call FM ISH_MR_REQUEST_FOR_APP

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 ORGFA FROM NAPP INTO @DATA(ld_i_orgfa).
 
"SELECT single ORGFA FROM NAPP INTO @DATA(ld_i_orgfa_old).
 
"SELECT single ORGPF FROM NAPP INTO @DATA(ld_i_orgpf).
 
"SELECT single ORGPF FROM NAPP INTO @DATA(ld_i_orgpf_old).
 
 


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!