SAP ABAP Data Element N1PLANOE (Planned OU)
Hierarchy
IS-H (Software Component) SAP Healthcare
   IS-H-PM (Application Component) Patient Management
     N1BASE (Package) IS-H: Basic Functionality; TSA Development
Basic Data
Data Element N1PLANOE
Short Description Planned OU  
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 Planned OU 
Medium 14 Planned OU 
Long 20 Planned OU 
Heading Plan. OU 
Documentation

Definition

Organizational unit where the planned appointment will take place.

Supplementary Documentation - N1PLANOE 0001

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 choosing the case line in the case list..
    • Inpatient/Day Patient Case:
    • For extended service, 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 have entered a start date for the service, the system will search for the inpatient movement which matches the time of the start of the service.
      If, however, an outpatient visit exists at the time of admission or the start of the service, the service will propose the treatment OU of the outpatient visit. If several outpatient visits exist at the time of admission, the system will not propose the 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 choosing movement, for which you wish to enter 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 have 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 for the visit date.
      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 proposal value. However, you should note that the 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 the validity data of the service. You should therefore make any changes in the movements concerned. The system will automatically transfer changed data to the service entry.

Examples

Dependencies

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