SAP ABAP IMG Activity N2MV_BADI_CONV (BAdI Document Conversion)
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_CONV BAdI Document Conversion  
Transaction Code S_AIR_98000325   (empty) 
Created on 20060601    
Customizing Attributes N2MV_BADI_CONV   BAdI Document Conversion 
Customizing Activity N2MV_BADI_CONV   Document Dispatch Control: BAdI Document Conversion 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name N2MV_BADI_CONV    

Use

This BAdI is used in the section Document Dispatch of the component Clinical Documentation (IS-HMED-DO). This BadI enables you to convert document content into another output format. Dispatch control selects the conversion with the highest priority. You can store the priorities in the customizing activity Prioritize Conversion Methods.

Requirements

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

  • If you want to prioritize your own conversions in the customizing, you have to create your own implementation for each filter.
  • 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.
  • The converted document content must be returned to the recipient data. In order to do so, you use the recipient data reference transferred as an import parameter in the method IF_EX_ISHMED_MV_CONVERTER~CONVERT_DOCUMENT. The public method IR_DISPATCH_REQUEST->STORE_CONVERTED_CONTENT( ) enables you to return the converted document content to dispatch control.
  • 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).

Standard settings

The BAdI is active by default. A standard implementation is shipped in PDF format for Business Communication Services (BCS).

The BAdI can be used several times and is filter dependent. The filter value matches the filter stored in the customizing.

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

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 2   Non-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_CONV 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