SAP ABAP IMG Activity ISHMED_APP_BADI_CAN (BAdI for Checking when Canceling an Appointment)
Hierarchy
☛ IS-H (Software Component) SAP Healthcare
   ⤷ IS-HMED-SC (Application Component) Planning
     ⤷ N1APMG_MED (Package) IS-H*MED: Appointment Management
IMG Activity
ID ISHMED_APP_BADI_CAN BAdI for Checking when Canceling an Appointment  
Transaction Code S_KK4_98000066   (empty) 
Created on 20031125    
Customizing Attributes ISHMED_APP_BADI_CAN   BAdI for Checking when Canceling an Appointment 
Customizing Activity ISHMED_APP_BADI_CAN   BAdI for Checking when Canceling an Appointment 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name N1_CANCEL    

Use

This Business Add-In (BAdI) is used in all components of the clinical system i.s.h.med.

Using the methods of this Business Add-In you can enhance the cancellation of i.s.h.med objects by adding your own checks and the cancellation of your own data.

You should note that you can also cancel customer-specific data together with the i.s.h.med data. You cannot, however, display the customer-specific data in the i.s.h.med cancellation dialog box.

Requirements

You must adhere to the following rules when programming your customer enhancements:

  • You must execute the retention, further processing, checking, and storage of your additionally selected data yourself.

    You can, for example, create a function group in which you store the additional data as global data. In the various BAdI methods you can call function modules of your new function group to select data accordingly and store, check, and cancel in the global data of your function group. You can either create a separate function module for each BAdI method, or use only one function module, which has a corresponding switch in the interface, which can be used to control the further processing in the function module.

  • If you wish to update customer-specific data (in customer-specific tables) in addition to the i.s.h.med standard data, you can only execute this in the method EXIT_CANCEL_SAVE .
  • Under no circumstances should you execute a COMMIT WORK or a ROLLBACK WORK. This could create serious data inconsistencies in i.s.h.med or. SAP Patient Management (IS-H).
  • You can only update data asynchronously.
  • As these methods are also called from APIs, i.e. only processing function modules, you cannot call dialog boxes or display messages independently.
  • When conceiving your source code, you must consider that this BAdI and its methods is not connected to the cancellation dialog in i.s.h.med, but is also called if the cancellation function is called without a dialog.

Standard settings

This BAdI is not active as standard.

The BAdI cannot be used multiple times.

The BAdI is country-specifically 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:

  1. 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.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. 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.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. 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:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

Access to data objects in i.s.h.med (use of method IS_INHERITED_FROM):

DATA: l_cancel_data type rn1cancel_datas,
        l_obj type ish_object,
        l_is_inherited_from type c,

LOOP AT it_cancel_data INTO l_cancel_data.
LOOP AT l_cancel_data-t_obj into l_obj.
* In this example only the following services are of interest
CALL METHOD l_obj-object->('IS_INHERITED_FROM')
EXPORTING
I_OBJECT_TYPE = cl_ish_objectbase=>co_type_med_service
RECEIVING
R_IS_INHERITED_FROM = l_is_inherited_from.
if l_is_inherited_from = 'X'.
* Here the processing of services
endif.
ENDLOOP.
ENDLOOP
....

See also

Methods

EXIT_CANCEL_COLLECT

EXIT_CANCEL_CHECK

EXIT_CANCEL_SAVE

Interfaces

IF_EX_N1_CANCEL

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 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20031125 
SAP Release Created in 472