Ansicht
Dokumentation

ISHMED_CDOKU_SAVE - BAdI: Save Surgical Documentation

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Data in Customer Master  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used to implement a customer-specific connection for calling additional functions immediately after saving the surgical documentation.

You will find further information under:

• Interface documentation

• Method 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 table NFAL 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.

Implementing the User Exit for Saving Surgical Documentation

You must implement the BAdI in order to be able to use the user exit to save surgical documentation. You should proceed as follows:

• When you perform this implementation guide 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_SAVE method. By double-clicking, you can access the code of the method, where you can then transfer the sample code or complete your own implementations

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.

The program of the surgical documentation will perform a database commit directly before and after the BAdI is executed. A database commit within the customer implementation of the BAdI is not necessary.

BAL_S_LOG - Application Log: Log header data   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 2773 Date: 20240607 Time: 014831     sap01-206 ( 59 ms )