Ansicht
Dokumentation

ISHMED_APCN_CHG_CORD - BAdI: Controlling Appointment Templates

ISHMED_APCN_CHG_CORD - BAdI: Controlling Appointment Templates

BAL_S_LOG - Application Log: Log header data   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Planning (IS-HMED_SC) component.

When you enter a clinical order or a service ordering order, the system automatically creates appointment templates for the items of the clinical order or the service ordering order within Smart UI.

You can use this BAdI to change or supplement the appointment templates created by the system. You can therefore individually adjust the guide values for appointment planning to suit your processes.

Appointment templates determine the properties which the appointment to be planned should have. These can include:

  • the date for which the appointment should be planned

You can also define dependencies between the appointment templates, in order to put the appointment templates into a certain order. In each case you can define a minimum or maximum interval as an attribute.

You can change the sequence of the appointment templates by changing existing dependencies or removing or adding dependencies.

This BAdI is not active as standard.

The BAdI cannot be used multiple times.

The BAdI is not filter-dependent.

Sample code (example for presetting the appointment OU in a coordinating scenario) is available for this BAdI (see Example section):

Execute the IMG activity and implement the method CHG_APP_CONSTR of the BAdI N_APP_CONSTR_CHG.

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.

From the inpatient occupancy, you request services from the ECG service facility using a clinical order . The ECG organizational unit plans the examination appointments itself, but should receive a desired examination date from the care units. This desired date can be the current day for all orders sent before 12:00 o'clock. For all orders which are sent later, the date of the next workday should be entered as the desired date.

Using the BAdI N_APP_CONSTR_CHG you can set the desired date depending on the current time and the status of the order item.

Method

CHG_APP_CONSTR






PERFORM Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 4837 Date: 20240523 Time: 200235     sap01-206 ( 72 ms )