Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NORD (Package) R/3MED: Services processing EDV-G
IMG Activity
| ID | SIMG_ISHMED_CLINWPUX | BAdI: Enhancements in Clinical Order View Type |
| Transaction Code | S_KK4_96000373 | (empty) |
| Created on | 20000901 | |
| Customizing Attributes | SIMG_ISHMED_CLINWPUX | Maintenance BADI Implement. - View Type for Requests in Clin. Work Station |
| Customizing Activity | ISHMED_CLINWPUX | Maintenance BADI Implement. - View Type for Requests in Clin. Work Station |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISHMED_CLINWPUX |
Use
This Business Add-In (BAdI) is used in the Clinical Work Station component (IS-HMED-BD-CWS).
This BAdI enables you to carry out the following tasks for views of the Clinical Orders view type in the clinical work station:
- Override functions (function codes) (method EXIT_FUNCTION)
- Implement customer-specific functions; function codes +004, +005 and +006 (method EXIT_FUNCTION)
- Manipulate all displayed data of the view (method EXIT_DISPLAY)
Requirements
Standard settings
The Business Add-In is not active in standard.
The BAdI cannot be used multiple times and is not filter-dependent.
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:
- 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. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- 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.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.andendmethod.statements. - 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: - Choose Activate.
When the application program is executed, the code you created is run through.
You should note that there are no checks linked to the modifications to displayed data with the Method EXIT_DISPLAY. Within the implementation of methods, you must make sure that the system returns only correct data.
For all standard function codes that should not be overridden in the method EXIT_FUNCTION, the system must return the exception FCODE_NOT_IMPLEMENTED.
Example
See also
Methods
EXIT_FUNCTION
EXIT_DISPLAY
Interfaces
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 | 20040224 |
| SAP Release Created in | 462 |
