Hierarchy

⤷

⤷

⤷

Basic Data
Data Element | NWPLANOE |
Short Description | Planning/Initiating OU in Work Environment |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ORGID | |
Data Type | CHAR | Character String |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 8 | |
Value Table | NORG |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Plan. OU |
Medium | 19 | Plan./Initiating OU |
Long | 30 | Planning/Initiating OU |
Heading | 8 | Pl./I OU |
Documentation
Definition
The functions
- Appointment - Initial Visit
- Appointment - Follow-Up Visit
- Schedule Appointment
- Service Scheduling with Planning Grid
are executed from an organizational unit and determine planning authorities and available time slots for which this organizational unit can schedule appointments.
If you have set up the views in which you use these functions for individual care units, outpatient clinics or service facilities, this planning organizational unit is specified by the care unit, outpatient clinic or service facility of the respective view.
If you use a view for several organizational units - for example, a collective view of all appointments and outpatient visits of three outpatient clinics - the system cannot clearly identify which organizational unit is the planning organizational unit when you create a new appointment.
In the Planning/Initiating Organizational Unit field at work environment level, you can specify an organizational unit that assumes the role of the planning organizational unit. The system then determines the planning authorities and available time slots that are available to this planning organizational units when you schedule an appointment.
A similar situation arises with the Create Preregistration function.
It is also possible to create a preregistration for a patient who is not displayed in the current view. If the current view shows patients from several organizational units in parallel, the system cannot clearly identify which organizational unit is initiating the preregistration. The system cannot then construct the selection list of all preregistration types that are available to this organizational unit.
The system again uses the value specified in the Planning/Initiating Organizational Unit field in the work environment.
History
Last changed by/on | SAP | 20050409 |
SAP Release Created in | 463B |