Hierarchy
⤷ IS-H-PM (Application Component) Patient Management
⤷ N1APMG (Package) IS-H: Appointment Management; TSA Development
IMG Activity
ID | ISH_APCN_CHG_CORD | BAdI for Controlling Appointment Templates |
Transaction Code | S_KK4_98000162 | (empty) |
Created on | 20040210 | |
Customizing Attributes | ISH_APCN_CHG_CORD | BAdI for Controlling Appointment Templates |
Customizing Activity | ISH_APCN_CHANGE | BAdI for Controlling Appointment Templates |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ISH_APCN_CHG_CORD |
Use
This Business Add-In (BAdI) is used in the Patient Management component (IS-H-PM).
When you enter a clinical order, the system automatically creates appointment templates for the items of the clinical order. You can use the N_APP_CONSTR_CHG BAdI to change or enhance the appointments created by the system from a programming perspective. 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
- The scheduling type, with which the appointment should be planned.
Requirements
Standard settings
The BAdI is not active by default.
Not a multiple use BAdI.
The BAdI is not filter-dependent.
Activities
Perform the IMG activity and implement the CHG_APP_CONSTR method of the N_APP_CONSTR_CHG Business Add-In.
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:
- 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. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- 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.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - 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: - Choose Activate.
When the application program is executed, the code you created is run through.
Example
See also
Methods: CHG_APP_CONSTR
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 | ISH_APCN_CHG_CORD | 0 | KK4H000031 | Planning |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20040210 |
SAP Release Created in | 472 |