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
IMG Activity
| ID | ISHMED_CDOKU_RELEASE | BAdI: Release Surgical Documentation |
| Transaction Code | S_KK4_96000651 | IMG Activity: ISHMED_CDOKU_RELEASE |
| Created on | 20020621 | |
| Customizing Attributes | ISHMED_CDOKU_RELEASE | BAdI: Release Surgical Documentation |
| Customizing Activity | ISHMED_CDOKU_RELEASE | BAdI: Release Surgical Documentation |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISHMED_CDOKU_RELEASE |
Use
This Business Add-In (BAdI) is used to implement a customer-specific connection for releasing the surgical documentation.
You can find further information under:
This BAdI replaces the user exit which was used until now to release the surgical documentation.
Import Interface
Application-specific data, for example the surgery anchor service, case data, and surgery movement data, are available via the import interface of the BAdI for use in further actions after the surgical documentation has been released.
You will find a more precise description of the import interface in the Data Dictionary for the database tables NBEW and NFAL.
The NFAL table is already locked by the surgical documentation. You must not lock or unlock the case within the customer implementation of the BAdI.
You can use the surgery anchor service to determine surgery-specific data, for example diagnoses, procedures, surgical team members or complications.
Requirements
Standard settings
Activities
Implementing the User Exit for Releasing Surgical Documentation
You must implement the BAdI in order to be able to use the user exit to release surgical documentation. You should proceed as follows:
- When you perform this activity you create an implementation of the BAdI in the customer namespace. However, this implementation will not yet contain program code for the method. If an example implementation was delivered you can access its program code using the menu option Goto -> Sample Code. You can then copy this program code into your implementation via the clipboard. You then make any adjustments to suit your requirements. The interface of your implementation contains the CHIRDOKU_RELEASE method. By double-clicking, you can access the code of the method, where you can then transfer the sample code.
Once you have implemented your customer-specific enhancements, you must then activate them. You should note that only one implementation may be active at any time.
Further notes
This Business Add-In for releasing surgical documentation replaces the previous customer exit of SAP enhancement SAPLN2OP (function module EXIT_SAPLN2OP_001). You should transfer your customer-specific enhancements to the BAdI.
The database commit occurs in the program of the surgical documentation immediately after the BAdI has been executed. A database commit within the customer implementation of the BAdI is not necessary.
Example
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional 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 | ISHMED_CDOKU_RELEASE | 0 | I010004313 | OR Documentation |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020621 |
| SAP Release Created in | 471 |
