SAP ISH_CM_ALE_PATIENT_CHANGE Function Module for









ISH_CM_ALE_PATIENT_CHANGE is a standard ish cm ale patient change 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 cm ale patient change FM, simply by entering the name ISH_CM_ALE_PATIENT_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_CM_ALE_PATIENT_CHANGE 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_CM_ALE_PATIENT_CHANGE'"
  EXPORTING
   IO_APPL_OBJ =  "
   IP_PREVIEW =  "
   IP_LOG_HANDLE =  "
   IP_WITH_ISH_KEY =  "

EXCEPTIONS
   WRONG_APPL_OBJ_TYPE = 1
.



IMPORTING Parameters details for ISH_CM_ALE_PATIENT_CHANGE

IO_APPL_OBJ -

Data type: OBJECT
Optional: No
Call by Reference: Yes

IP_PREVIEW -

Data type: CHAR1
Optional: No
Call by Reference: Yes

IP_LOG_HANDLE -

Data type: BALLOGHNDL
Optional: No
Call by Reference: Yes

IP_WITH_ISH_KEY -

Data type: ISH_ON_OFF
Optional: No
Call by Reference: Yes

EXCEPTIONS details

WRONG_APPL_OBJ_TYPE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISH_CM_ALE_PATIENT_CHANGE 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_io_appl_obj  TYPE OBJECT, "   
lv_wrong_appl_obj_type  TYPE OBJECT, "   
lv_ip_preview  TYPE CHAR1, "   
lv_ip_log_handle  TYPE BALLOGHNDL, "   
lv_ip_with_ish_key  TYPE ISH_ON_OFF. "   

  CALL FUNCTION 'ISH_CM_ALE_PATIENT_CHANGE'  "
    EXPORTING
         IO_APPL_OBJ = lv_io_appl_obj
         IP_PREVIEW = lv_ip_preview
         IP_LOG_HANDLE = lv_ip_log_handle
         IP_WITH_ISH_KEY = lv_ip_with_ish_key
    EXCEPTIONS
        WRONG_APPL_OBJ_TYPE = 1
. " ISH_CM_ALE_PATIENT_CHANGE




ABAP code using 7.40 inline data declarations to call FM ISH_CM_ALE_PATIENT_CHANGE

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.

 
 
 
 
 


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!