Ansicht
Dokumentation

ISHMED_APCN_CHG_OUTP - BAdI: Controlling Appointment Templates

ISHMED_APCN_CHG_OUTP - BAdI: Controlling Appointment Templates

ABAP Short Reference   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

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

The system will automatically create appointment templates for individual processes in which appointments are planned.

You can use the BAdI to change or enhance the appointment templates created by the system from a programming point of view. You can therefore individually adjust the guide values for appointment planning to suit your processes.

Appointment templates are guide values for appointment planning. Appointment templates determine properties which an appointment to be planned, should have. These can include:

  • The organizational unit where the appointment should take place
  • The date on which the appointment should take place

In the clinical order dependencies can exist between appointment templates, which define an order of the appointment templates.
In each case you can define a minimum or maximum gap as an attribute.

During a global search in the Clinical Work Station this BAdI enables you to change this sequence of appointment templates, by changing or removing existing dependencies or adding new ones.

The BAdI is not active as standard.

The BAdI cannot be used multiple times.

The BAdI is not filter-dependent.

If, in a view of the Outpatient Clinic/Service Facility view type, you execute the Find Appointment for Initial Visit function in the Clinical Work Station, the system will create an appointment template with the following properties:

  • Visit type = Initial visit
  • Appointment search should be after current day

You execute the implementation guide activity and implement the CHG_APP_CONSTR method of the business add-in 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.

At the earliest, follow-up visits in the outpatient clinic should take place two weeks after the current date. It should only be possible to plan those appointments which are suitable for the follow-up visit visit type.

To enable this, you use the BAdI N_APP_CONSTR_CHG to orient the corresponding fields of the appointment template towards this scenario.

Methods

CHG_APP_CONSTR






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

Length: 4740 Date: 20240607 Time: 095753     sap01-206 ( 81 ms )