SAP ABAP Data Element N1OP_OPOE (Operating Organizational Unit)
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 | N1OP_OPOE |
Short Description | Operating Organizational Unit |
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 | Oper. OU |
Medium | 14 | Operating OU |
Long | 30 | Operating Organizational Unit |
Heading | 8 | Oper. OU |
Documentation
Definition
The operating organizational unit decides which surgeries the system should be displayed in the worklist if the OR plan. The OR plan itself always displays all surgeries which have an appointment in one of the resources entered.
This field supports multiple selection and you can also enter a department. If you enter a department, the system will include all operating service facilities of this department.
If the operating OU is left blank, the system will select all surgeries of all service facilities of the institution.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20050409 |
SAP Release Created in | 471 |