Kontakt

Ansicht
Dokumentation

N2MV_BADI_DISP - BAdI Dispatch Routes

N2MV_BADI_DISP - BAdI Dispatch Routes

Fill RESBD Structure from EBP Component Structure   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

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 methods when sending and displaying clinical documents.

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.
  • You call the initialization method IF_ISHMED_MV_BADI~INITIALIZE 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.
  • Perform absolutely no COMMIT WORK or ROLLBACK WORK in the 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 to obtain the converted document content or the recipient data, for example. You can adjust the status of the dispatch order according to your processing.

The BAdI is active by default.

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

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

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.

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






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 4429 Date: 20240523 Time: 200427     sap01-206 ( 66 ms )