SAP ABAP IMG Activity SIMG_ISHMED_O_DIALOG (BAdI - Process Control of Medication Order)
Hierarchy
☛ IS-H (Software Component) SAP Healthcare
   ⤷ IS-HMED (Application Component) Clinical System
     ⤷ NMED_ME (Package) IS-H*MED: Medication
IMG Activity
ID SIMG_ISHMED_O_DIALOG BAdI - Process Control of Medication Order  
Transaction Code S_ANI_98000229   (empty) 
Created on 20050314    
Customizing Attributes SIMG_ISHMED_O_DIALOG   BAdI Implementation - Control of Order Framework 
Customizing Activity SIMG_ISHMED_O_DIALOG   BAdI Implementation - Control of Order Framework 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name N1ME_ORDER_DIALOG    

Use

This BAdI serves the process of creating, changing and displaying medication orders and enhancing drug templates with customer-specific actions. For more information, consult the documentation of the individual methods of this BAdI.

Since almost all methods of this BAdI are used for medication orders and for maintaining order templates, it is important to differentiate between both these objects. For this you can use the IS_TEMPLATE() method which has both the process class and the order class.

You should note that the following rules must be adhered to:

  • COMMIT WORK/ROLLBACK WORK are not allowed. The process executes a COMMIT WORK itself after the update function module is called. If you need to execute actions before or directly after, there is the N1ME_COMMIT_WORK BAdI especially for this.
  • Direct updates using UPDATE table or MODIFY table are not permitted. Only execute UPDATE, INSERT and DELETE in encapsulated update function modules which you execute with CALL FUNCTION ... IN UPDATE TASK (this asynchronous).
  • You can only make changes to standard tables (such as N1MEORDER, N1MEEVENT etc) by using the data classes intended for this purpose (e.g. CL_ISHMED_ME_ORDER, CL_ISHMED_ME_EVENT etc) and never directly by calling the relevant update function module.
  • You have to handle dialog calls very carefully. The process class was developed in such a way that it can be used even without the dialog - e.g. for batch processing or for customer-specific dialogs. This means that if you want to call dialogs or dialog boxes in the BAdI's methods, you should only do it if the method returns IS_DIALOG_MODE() ON . This tells you that the process itself is running in dialog mode and that dialog boxes are permitted.

Requirements

Standard settings

No active standard delivery exists for this BAdI.

Activities

Details for Implementing a BAdI

Example

See also

The following methods are available for this BAdI:

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050603 
SAP Release Created in 600