SAP ISHMED_ME_GENERATE_EVENTS Function Module for









ISHMED_ME_GENERATE_EVENTS is a standard ishmed me generate events 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 ishmed me generate events FM, simply by entering the name ISHMED_ME_GENERATE_EVENTS into the relevant SAP transaction such as SE37 or SE38.

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



Function ISHMED_ME_GENERATE_EVENTS 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 'ISHMED_ME_GENERATE_EVENTS'"
  EXPORTING
*  IR_ORDER =  "IS-H*MED: Medication Order
*  I_CHECK_ORDER = 'X' "
*  I_FLG_PREVENT = 'X' "
*  I_CHECK_EVT_EXIST = 'X' "
*  I_ENQUEUE = ' ' "'X': Set Locks
*  I_UCOMM = SY-UCOMM "Function Code that Triggered PAI
*  I_CALLER =  "Calling Program
*  I_MAKE_SNAPSHOT = 'X' "
*  I_MEORDID =  "IS-H*MED: Medication, Order - Order ID
*  I_GENTYPE =  "IS-H*MED: Medication - Type for Generating Events
*  I_DATE_FROM =  "
*  I_TIME_FROM =  "
*  I_DATE_TO =  "Date and Time, Current (Application Server) Date
*  I_TIME_TO =  "Date and Time, Current Application Server Time
*  IR_ENVIRONMENT =  "IS-H: Class for Collecting All Objects in Memory
*  I_SAVE = 'X' "

 IMPORTING
   ET_EVENTS =  "IS-H: Table with Object References
   ET_N1MEEVENT =  "IS-H*MED: Medication Event, Table Type for N1MEEVENT
   ET_N1EDRUG =  "IS-H*MED: Medication Event, Table Type for N1EDRUG
   ET_CYCLE_DOSE =  "IS-H*MED: Cycle Appointments with Dose
   E_RC =  "IS-H: Return Code for Method Calls

CHANGING
*  CS_LOCK =  "i.s.h.med: Medication; Transfer Locks Between Programs
*  CR_ERRORHANDLER =  "ISHMED: Class for Error Handling
.



IMPORTING Parameters details for ISHMED_ME_GENERATE_EVENTS

IR_ORDER - IS-H*MED: Medication Order

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

I_CHECK_ORDER -

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

I_FLG_PREVENT -

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

I_CHECK_EVT_EXIST -

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

I_ENQUEUE - 'X': Set Locks

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

I_UCOMM - Function Code that Triggered PAI

Data type: SYUCOMM
Default: SY-UCOMM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CALLER - Calling Program

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

I_MAKE_SNAPSHOT -

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

I_MEORDID - IS-H*MED: Medication, Order - Order ID

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

I_GENTYPE - IS-H*MED: Medication - Type for Generating Events

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

I_DATE_FROM -

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

I_TIME_FROM -

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

I_DATE_TO - Date and Time, Current (Application Server) Date

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

I_TIME_TO - Date and Time, Current Application Server Time

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

IR_ENVIRONMENT - IS-H: Class for Collecting All Objects in Memory

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

I_SAVE -

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

EXPORTING Parameters details for ISHMED_ME_GENERATE_EVENTS

ET_EVENTS - IS-H: Table with Object References

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

ET_N1MEEVENT - IS-H*MED: Medication Event, Table Type for N1MEEVENT

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

ET_N1EDRUG - IS-H*MED: Medication Event, Table Type for N1EDRUG

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

ET_CYCLE_DOSE - IS-H*MED: Cycle Appointments with Dose

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

E_RC - IS-H: Return Code for Method Calls

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

CHANGING Parameters details for ISHMED_ME_GENERATE_EVENTS

CS_LOCK - i.s.h.med: Medication; Transfer Locks Between Programs

Data type: RN1ME_LOCK_PASS
Optional: Yes
Call by Reference: Yes

CR_ERRORHANDLER - ISHMED: Class for Error Handling

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

Copy and paste ABAP code example for ISHMED_ME_GENERATE_EVENTS 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_cs_lock  TYPE RN1ME_LOCK_PASS, "   
lv_ir_order  TYPE CL_ISHMED_ME_ORDER, "   
lv_et_events  TYPE ISH_OBJECTLIST, "   
lv_i_check_order  TYPE ISH_ON_OFF, "   'X'
lv_i_flg_prevent  TYPE ISH_ON_OFF, "   'X'
lv_i_check_evt_exist  TYPE ISH_ON_OFF, "   'X'
lv_i_enqueue  TYPE ISH_ON_OFF, "   ' '
lv_i_ucomm  TYPE SYUCOMM, "   SY-UCOMM
lv_i_caller  TYPE SY-CPROG, "   
lv_i_make_snapshot  TYPE ISH_ON_OFF, "   'X'
lv_i_meordid  TYPE N1ME_MEORDID, "   
lv_et_n1meevent  TYPE ISHMED_T_N1MEEVENT, "   
lv_cr_errorhandler  TYPE CL_ISHMED_ERRORHANDLING, "   
lv_i_gentype  TYPE N1ME_GENTYPE, "   
lv_et_n1edrug  TYPE ISHMED_T_N1EDRUG, "   
lv_i_date_from  TYPE SY-DATUM, "   
lv_et_cycle_dose  TYPE ISHMED_T_CYCLE_DOSE, "   
lv_e_rc  TYPE ISH_METHOD_RC, "   
lv_i_time_from  TYPE SY-UZEIT, "   
lv_i_date_to  TYPE SY-DATUM, "   
lv_i_time_to  TYPE SY-UZEIT, "   
lv_ir_environment  TYPE CL_ISH_ENVIRONMENT, "   
lv_i_save  TYPE ISH_ON_OFF. "   'X'

  CALL FUNCTION 'ISHMED_ME_GENERATE_EVENTS'  "
    EXPORTING
         IR_ORDER = lv_ir_order
         I_CHECK_ORDER = lv_i_check_order
         I_FLG_PREVENT = lv_i_flg_prevent
         I_CHECK_EVT_EXIST = lv_i_check_evt_exist
         I_ENQUEUE = lv_i_enqueue
         I_UCOMM = lv_i_ucomm
         I_CALLER = lv_i_caller
         I_MAKE_SNAPSHOT = lv_i_make_snapshot
         I_MEORDID = lv_i_meordid
         I_GENTYPE = lv_i_gentype
         I_DATE_FROM = lv_i_date_from
         I_TIME_FROM = lv_i_time_from
         I_DATE_TO = lv_i_date_to
         I_TIME_TO = lv_i_time_to
         IR_ENVIRONMENT = lv_ir_environment
         I_SAVE = lv_i_save
    IMPORTING
         ET_EVENTS = lv_et_events
         ET_N1MEEVENT = lv_et_n1meevent
         ET_N1EDRUG = lv_et_n1edrug
         ET_CYCLE_DOSE = lv_et_cycle_dose
         E_RC = lv_e_rc
    CHANGING
         CS_LOCK = lv_cs_lock
         CR_ERRORHANDLER = lv_cr_errorhandler
. " ISHMED_ME_GENERATE_EVENTS




ABAP code using 7.40 inline data declarations to call FM ISHMED_ME_GENERATE_EVENTS

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.

 
 
 
DATA(ld_i_check_order) = 'X'.
 
DATA(ld_i_flg_prevent) = 'X'.
 
DATA(ld_i_check_evt_exist) = 'X'.
 
DATA(ld_i_enqueue) = ' '.
 
DATA(ld_i_ucomm) = SY-UCOMM.
 
"SELECT single CPROG FROM SY INTO @DATA(ld_i_caller).
 
DATA(ld_i_make_snapshot) = 'X'.
 
 
 
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_date_from).
 
 
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_i_time_from).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_date_to).
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_i_time_to).
 
 
DATA(ld_i_save) = 'X'.
 


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!