SAP ABAP IMG Activity ISHMED_BADI_ADM_CSLS (Create Admission/Visit: BAdI for "Caseless Objects" Dialog Box)
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 ISHMED_BADI_ADM_CSLS Create Admission/Visit: BAdI for "Caseless Objects" Dialog Box  
Transaction Code S_KK4_96000658   (empty) 
Created on 20020916    
Customizing Attributes ISHMED_BADI_ADM_CSLS   BAdI: Dialog Box for Caseless Objects at Admission 
Customizing Activity ISHMED_BADI_ADM_CSLS   BAdI: Dialog Box for Caseless Objects at Admission 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISHMED_BADI_ADM_CSLS    

Use

This Business Add-In (BAdI) is used in the Clinical Patient Management (IS-HMED-CP) component.

When saving an admission or a visit, the system will check whether the patient has other caseless clinical orders, appointments, or service requests in addition to the appointment for which the admission or visit was created. If this is the case, users will receive a dialog box where they can assign these clinical orders, appointments, or service requests to the case for which the patient was admitted, or the visit was created.

You can activate or deactivate the dialog box using the OU-related parameter N1VKCHKFAL. The system will check the parameter value for the admitting organizational unit which the user entered in the admission or the visit.

With this BAdI you can control which caseless clinical orders, appointments and requests should appear in the dialog box. This is helpful if you wish to define a process, in addition to the admitting facility, which determines which clinical orders, appointments, and requests the user should receive.

The BAdI can also determine which clinical orders, appointments, and requests are already selected to be assigned to the case.

Interaction with SAP Enhancement SAPLN1OK

In addition to this BAdI the SAP enhancement SAPLN1OK provides the function exit EXIT_SAPLN1OK_001, which classifies the caseless objects for processing as:

  • Objects, which should not be connected to the case
  • Objects, which should automatically be connected to the case, i.e. without user interaction
  • Objects, which should be offered to the user in a selection window

The BAdI ISHMED_SEL_FOR_FALLB enhances the exit EXIT_SAPLN1OK_001 and allows you to configure or select the quantity of objects in the selection window.

Requirements

Standard settings

The Business Add-In is not active as standard.

The BAdI can be used multiple times.

The BAdI 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:

  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

See also

Method

EXECUTE

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_BADI_ADM_CSLS 0 I041002041 Planning 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20070912 
SAP Release Created in 471