SAP ABAP IMG Activity N2MV_BADI_DISP (BAdI Dispatch Routes)
Hierarchy
☛ IS-H (Software Component) SAP Healthcare
   ⤷ IS-HMED (Application Component) Clinical System
     ⤷ NMED_DOC_DISTR (Package) i..s.h.med: Dispatch Control (Document Distribution)
IMG Activity
ID N2MV_BADI_DISP BAdI Dispatch Routes  
Transaction Code S_AIR_98000322   (empty) 
Created on 20060601    
Customizing Attributes N2MV_BADI_DISP   BAdI Dispatch Routes 
Customizing Activity N2MV_BADI_DISP   Document Dispatch Control: BAdI Dispatch Routes 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name N2MV_BADI_DISP    

Use

This BAdI is used in the section Document Dispatch of the component Clinical Documentation (IS-HMED-DO ). This BAdI enables you to define the behavior of your own dispatch routes when sending and displaying clinical documents.

Requirements

Please note the following rules when you program your customer enhancements:

  • You have to perform the technical realization for dispatching and displaying document content. For example, you can create a function group in which you keep the dispatch data as global data. You can then process this data in the corresponding BAdI methods IF_EX_ISHMED_MV_DISPATCHER~SEND_DOCUMENT and IF_EX_ISHMED_MV_DISPATCHER~PREVIEW_DOCUMENT by calling function modules belonging to your new function group.
  • The initialization method IF_ISHMED_MV_BADI~INITIALIZE is called at the beginning of the BAdl processing. This transfers the document API and an error handler to the BAdI class.
  • After the BAdl processing in the method IF_ISHMED_MV_BADI~FREE release the resources used.
  • Do not perform any COMMIT WORK or ROLLBACK WORK in these methods. You could create serious data errors in i.s.h.med or in SAP Patient Management (IS-H).
  • In the send and preview method the dispatch order is transferred as a reference. Use its public methods, in order, for example, to obtain the converted document content or the recipient data. You can adjust the status of the dispatch order according to your processing.

Standard settings

The BAdI is active by default.

The BAdI can be used several times and is filter-dependent for institution and dispatch route.

If there is no suitable implementation for the filter, the dispatch route Printer (default implementation) is used.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

For the Business Communication Service (BCS) there is a default implementation CL_EXM_IM_ISHMED_MV_DISP_BCS requiring a license. The dispatch routes fax, email and SAP office mail are already implemented

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG N2MV_BADI_DISP 0 I010004303 Clinical Documentation 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20060619 
SAP Release Created in 700