SAP ABAP IMG Activity ISHMED_CASE_VALID (BAdI: Validity Check for Completed/Billed Case)
Hierarchy
☛ IS-H (Software Component) SAP Healthcare
   ⤷ IS-H-PM (Application Component) Patient Management
     ⤷ N1BASE (Package) IS-H: Basic Functionality; TSA Development
IMG Activity
ID ISHMED_CASE_VALID BAdI: Validity Check for Completed/Billed Case  
Transaction Code S_P7C_98000363   IMG Activity 
Created on 20070911    
Customizing Attributes ISHMED_CASE_VALID   Validity Check for Completed or Billed Case 
Customizing Activity ISHMED_CASE_VALID   Validity Check for Completed or Billed Case 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISHMED_CHECK_CASE_VALID    

Use

i.s.h.med uses caseless objects for appointment planning and clinical orders. You must assign the caseless objects to a case for the patient at a certain time. You can assign a caseless object to a case at different points in i.s.h.med processing:

  • "Assign Case" function at clinical work station
  • "Save Admission" function, inpatient or outpatient
  • Start surgery
  • Assign case in clinical order

You can use this BAdI to check the case to which a caseless appointment or clinical order is linked. Based on this check, you can decide whether linking is to be allowed when a case is assigned to a completed or billed case. You have the following options:

  • Warning
  • Error message
  • No message

You cannot display messages or perform other interface-relevant actions in this BAdI. See the instructions further on in this documentation.

Requirements

This Business Add-In is active in the standard system.

This is not a multiple-use BAdI.

The BAdI is filter-dependent.

When implementing the BAdI, please note that interface-relevant actions are not allowed. This means it is not possible to display messages or dialog boxes.

The BAdI is used to determine whether or not a caseless object can be attached to a completed or final billed case, using a logic other than the standard logic. Please see the BAdI interface.

Standard settings

A fallback class is provided with the standard implementation for this BAdI. This means that if there is no active implementation, the system runs the standard implementation. The system evaluates the system parameters N1CHKABR and N1ANFNST, which define the message category in Customizing, in the standard implementation.

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

To display the fallback class, call the BAdI Builder (SE18). Double-click the BAdI implementation on the Enh. Spot Element Definitions tab page. Choose Display for the fallback class (pushbutton). Double-click the method.

This BAdI uses the interface IF_EX_ISHMED_CHECK_CASE_VALID. For more information, display the interface in the Class Builder.

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  20070912 
SAP Release Created in