Hierarchy
IS-H (Software Component) SAP Healthcare⤷
IS-H-PM (Application Component) Patient Management⤷
N1APMG (Package) IS-H: Appointment Management; TSA Development
IMG Activity
| ID | ISH_PLANNING_PREALLO | BAdI: Preset Appointment |
| Transaction Code | S_P7C_98000347 | (empty) |
| Created on | 20070813 | |
| Customizing Attributes | ISH_PLANNING_PREALLO | BAdI: Preset Appointment |
| Customizing Activity | ISH_PLANNING_PREALLO | BAdI: Preset Appointment |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISH_PLANNING_PREALLOC |
Use
This Business Add-In (BAdI) is used in the Patient Management (IS-H-PM) component.
You can use this BAdI to implement presettings for an appointment during the appointment planning process.
Requirements
Standard settings
In the standard system, there is no activated BAdI implementation. The standard code is executed automatically.
The Business Add-In can be used more than once.
The BAdI is not filter-dependent.
BAdI Implementations
The BAdI implementation is instantiated depending on the context. This means that the same BAdI implementation is always used for each internal session and appointment.
Sample code (example for presetting the appointment OU in a coordinating scenario) is available for this BAdI (see Example section):
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
Example 1:
You have attached an append structure to NTMN or NAPP in which you want to save additional fields.
You can use this BAdI to implement customer-specific presettings for these fields.
Example 2:
You want to create customer-specific data that belongs to the appointment but should be saved in customer-specific tables.
You can use this BAdI to create this data and include it as an attribute in the implementation class.
Since this BAdI is instantiated for an appointment in a specific context, the data is retained in the attributes.
You should note that, if you also wish to check and save this data, you must use a joint implementation class for this BAdI and for the BAdIs for checking, for checking for changes and for saving.
You should also note also that you no longer have access to this data if the planning process is terminated.
To display sample code, call the BAdI Builder (transaction code SE18) for this BAdI. On the Enh. Spot Element Definitions double-click on the BAdI implementation. Select the example class in the Implementation Examples group box and choose Display Example Class (pushbutton). Double-click on the method.
Further information
This BAdI uses the interface IF_EX_ISH_PLANNING_PREALOC. For more information, display the interface in the Class Builder.
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 |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20070814 |
| SAP Release Created in |
