SAP ABAP IMG Activity SIMG_ISHMED_RAD_BA03 (BAdI: Selectively Send Worklist Entries)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NMED (Package) R/3MED: Medical documentation GSD
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NMED (Package) R/3MED: Medical documentation GSD
IMG Activity
ID | SIMG_ISHMED_RAD_BA03 | BAdI: Selectively Send Worklist Entries |
Transaction Code | S_KK4_96000396 | IMG |
Created on | 20010306 | |
Customizing Attributes | SIMG_ISHMED_RAD_BA03 | IS-H*MED RAD BAdI: Send the DICOM Wokrklist for Patient |
Customizing Activity | SIMG_ISHMED_RAD_BA03 | IS-H*MED RAD BAdI: Send the DICOM Wokrklist for Patient |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ISHMED_RAD_SPWL |
The BAdI ISHMED_RAD_SPWL (Single Patient Worklist) enables the device-specific supply, of non-DICOM-compatible modalities with filled-in Worklist entries.
The shipped active standard implementation sends worklist entries to the MITRA PACS Broker in the method SEND_WORKLIST via MSI.
You can read more information in the following documentation:
Example
Requirements
Standard settings
Recommendation
Activities
- If you implement the MITRA PACS Broker and the modality contains the worklist from the Broker, then you can use the shipped standard BAdI implementation. There is no activity required for this.
- If you require a different BAdI implementation, then you must execute the following activities:
Using the IMG activity, you create an implementation of the BAdI in the customer name space. Each one does not yet contain a program code for the method(s). You can use the Standard BAdI implementation as a template for your individual development purposes.
You must make sure that the customized enhancements are activated. Only one implementation can be active.
Further notes
In the standard BAdI, the transfer to the MITRA PACS Broker is only executed with the active MSI Protocol (General Parameter MSI = X).
You must coordinate with the person responsible for the MITRA project whether PACS broker will supply the modality with worklist entries or a device-specific customer enhancement must be implemented.
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 3 | Nonrequired 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 | 20010806 |
SAP Release Created in | 463 |