SAP ABAP Data Element N1PLNOE (Planning Organizational Units)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NORD (Package) R/3MED: Services processing EDV-G
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NORD (Package) R/3MED: Services processing EDV-G
Basic Data
Data Element | N1PLNOE |
Short Description | Planning Organizational Units |
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 | OU Plann. |
Medium | 14 | Planning OU |
Long | 20 | Planning Org. Units |
Heading | 10 | OU Plann. |
Documentation
Definition
An organizational unit which allocates appointments for patients, is classified as a planning organizational unit. In principle, each organizational unit can plan for itself or for other organizational units within the hierarchy.
The following applies when planning visit appointments:
Using the planning authority you can define which planning objects and time periods a planning organizational unit may plan for. The planning authority is defined as static detail information for the day program. You can also override the static definition in specific applications on a day-related basis.
History
Last changed by/on | SAP | 20050409 |
SAP Release Created in |