SAP ABAP Data Element N1WP11ERBOE (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
Basic Data
Data Element N1WP11ERBOE
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 PERFORM_OU   
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 20 Operating OU 
Heading 8 Oper. OU 
Documentation

Definition

The operating organizational unit is the department to which the surgery request or the surgery preregistration is sent and which will perform the surgery. All services which are performed with a main surgery are contained in the range of the operating organizational unit.

The operating organizational unit can be, but must not be, the planning OU of the OR plan.

Example:

Surgical procedures in a procedure room directly in the department -> organizational units are identical.

Surgeries in a central OR used by several departments -> operating OU and planning OU are different.

Supplementary Documentation - N1WP11ERBOE0001

Use

If you enter a service without entering the performing organizational unit (OU), the system will determine the performing OU from the movement, to which the service is assigned.

Depending on whether you called the service entry function as case-related or movement-related, the system will determine the performing OU as follows:

  • You call the service entry function as case-related, by selecting the case line in the case list.
    • Inpatient/Day Patient Case:
      • For extended services, the system will propose the nursing OU to which the case is assigned in the admission and in subsequent inpatient movements.
      For immediate services, the system will propose the nursing OU of the admission, if you have not entered a service date. If you entered the service with a start date, the system will search for the inpatient movement which is valid at the start of the service.
      If, however, an outpatient visit exists at the time of admission or the start of the service, the system will propose the treatment OU of the outpatient visit. If several outpatient visits exist at the time of admission, the system will not propose a performing OU.
    • Outpatient Case:
      • The system will propose the treatment OU of the first outpatient visit as the performing OU.
  • You call the service entry function as movement-related, by selecting the movement, for which you wish to create services, in the case list.
    • Inpatient/Day Patient Case:
      • For extended services, the system will propose the nursing OU of the selected movement. If you selected an outpatient visit, the system will not propose the treatment OU of the outpatient visit, but the nursing OU of the movement which is valid at the time of the visit.
      For immediate services, the system will propose the nursing or treatment OU of the selected movement.
    • Outpatient Case:
      • The system will propose the treatment OU of the selected outpatient visit as the performing OU.

Procedure

You enter the service and confirm your entries. The system will automatically determine the performing OU.

You can change the proposed value. However, you should note that the system can no longer automatically adapt entered services to suit changed movement data, if you have manually changed the performing and requesting OU data or data concerning the validity of the service. You should therefore make any changes in the relevant movements. The system will automatically transfer the changed data to the service entry.

Examples

Dependencies

History
Last changed by/on SAP  20050301 
SAP Release Created in 471