Hierarchy

⤷

⤷

⤷

IMG Activity
ID | ISH_SERVICE_MOVEMENT | BAdI: Determine Corresponding Movement for a Service |
Transaction Code | S_KK4_96000571 | IMG Activity: ISH_SERVICE_MOVEMENT |
Created on | 20020423 | |
Customizing Attributes | ISH_SERVICE_BADIS | IS-H: BAdIs in Service Entry Environment |
Customizing Activity | ISH_SERVICE_MOVEMENT | BAdI: Determine Corresponding Movement for a Service |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ISH_SERVICE_MOVEMENT |
Use
When you enter a new service, the system must first determine a movement to be able to transfer particular data you have not entered (e.g. organizational unit, start date) from this movement into the service. The default algorithm basically makes use of the entered service date. Problems can arise in particular if several relevant movements exist at this date. In such cases, this BAdI lets you implement your own criteria to decide which movement is appropriate for the current service.
You can also determine the organizational units to be assigned to the service. This is important since, for example, for immediate services the requesting organizational unit is determined from the inpatient movement and the performing organizational unit may be determined from an outpatient visit.
In addition to when new services are entered, this BAdI is therefore processed when the system checks if a service is to be modified on account of changed movements.
You'll find further information about this BAdI in the interface documentation and the
method documentation.
Requirements
Standard settings
Activities
Example
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 3 | Nonrequired 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 | 20020423 |
SAP Release Created in | 463B |