Ansicht
Dokumentation

ISHMED_BADI_ADM_CSLS - BAdI: "Caseless Objects" Selection Window at Create Admission/Visit

CPI1466 during Backup   General Data in Customer Master  
This documentation is copyright by SAP AG.

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.

The Business Add-In is not active as standard.

The BAdI can be used multiple times.

The BAdI is not filter-dependent.

After you have called the IMG activity, proceed as follows:

1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

Method

EXECUTE

PERFORM Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4750 Date: 20240523 Time: 185408     sap01-206 ( 67 ms )