SAP ABAP IMG Activity SIMG_ISHMED_CAIBADI (BadI: File Formatting File Interface Device Data)
Hierarchy
☛ IS-H (Software Component) SAP Healthcare
   ⤷ IS-HMED (Application Component) Clinical System
     ⤷ NMED_DS (Package) Departmental Solutions
IMG Activity
ID SIMG_ISHMED_CAIBADI BadI: File Formatting File Interface Device Data  
Transaction Code S_PRI_97000076   (empty) 
Created on 20061215    
Customizing Attributes SIMG_ISHMED_CAIBADI   BAdI for File Formatting 
Customizing Activity SIMG_ISHMED_CAIBADI   BAdI for File Formatting 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISHMED_DS_PMDDEVICES    

Use

The BAdI ISHMED_DS_PMDDEVICES is part of the file interface for the transfer of examination data from devices into parameterized medical documents.

It must be implemented for each device type, in order to format the concrete data structure.

Requirements

The technical settings for file processing in the interface should be made before the BAdI is implemented.

In particular, table TXCOM must contain an entry for the data receipt.

Standard settings

The BAdI is filter-dependent.

The filter value is the symbolic destination for the data receipt (TXCOM entry).

If no active implementation exists for the filter value, a relevant message is transferred to the message table and the results table is empty.

Activities

When you call the IMG activity you first access a dialog box where you enter a name for the implementation.

If implementations have already been created for this BAdI, you access a dialog box which displays the existing implementations. In this dialog box, select Create and continue as follows:

  1. In the dialog box, fill the Implementation field with a name for the implementation of the BAdI and then selectCreate.

    You access the initial screen for creating BAdI implementations.

  2. On the initial screen use the Short Text for Implementation field to enter a short text for the implementation.
  3. For the Filter Value field select the interface for which this implementation should be executed.
  4. In the tab page index, select Interface.

    On this tab page, the Name of Implementing Class field is automatically filled, as the system assigns a class name using the name of your implementation.

  5. Save your entries and make the assignment to a development package.
  6. Position the cursor on the method and double-click to branch to method processing.
  7. Between the commands method <Interface Name>~<Name of Method>. and endmethod. enter your desired source code for the implementation.
  8. Save and activate your source code and navigate back to the Change Implementation screen.
  9. On the Change Implementation screen, execute a save.

    Note: It is also possible to create an implementation for a BAdI and activate this later. In this case complete processing now.

  10. Select Activate.

    During the execution of the application program the source code stored in the method is run.

Example

An example implementation is available for the preparation of text files from the cardiac catheter measuring station "Siemens Sensis®".

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