Professional Documents
Culture Documents
PM Day 1 Workshop
Organizational Structure
0. Prior to the session - Workshop
Preparation
Prior to the session, MIKA team is expected to prepare the below items:
Note: Reports will be reviewed in two specific sessions, one for PA reports and
the other to review the PM ones.
1. Workshop Agenda
ABYOR 2016 /
2. Workshop Expectation settings
The workshops:
KEY POINTS
Several institutions can exist in one client. Each is identified by means of a unique key
comprising up to four digits.
You can assign a different company code to each institution. However, the same company
code can be assigned to a number of institutions. Accordingly, a separate company code also
requires a separate institution.
You can assign several company codes to one or more controlling areas.
0001 0001
0010
002A
0002
002B
4.2. Client/Institution
Example:
- House Address
- Communication
- Organization/Assignments
- FI Company Code
- FI Business Area
- FI Sales Organization
- CO Area (only
maintaned if internal
financial statement
for business areas are
required)
- MM Plant
5. Technical Number Ranges
Technical number ranges are required in SAP at the time of creation of many several objects.
The code for the corresponding object will be asssigned based on this number ranges.
You have the option of using internal number ranges (number or alphanumeric is
automatically assigned by the system) or external number ranges (number or alphanumeric is
assigned by the user).
(Action Item 2)
6.1. System Parameters
Note:
These parameters are not strictly related to Institution. If relevant, will be discussed
in the corresponding related sessions (e.g. Patient accounting, Patient
Management,)
6.5. System Parameters
- Number of levels to be
displayed by default in
Org.Struct.tree.
- Automatic creation of FI
Customer when creating
Customer BP.
6.6. System Parameters
Note:
These parameters are not strictly related to Institution. If relevant, will be discussed
in the corresponding related sessions (e.g. Patient accounting, Patient
Management,)
7. Hospital Structure
Costs
Revenue
Medical orders (clinical process)
Service performance
Material management storage locations
Planning objects
7. Hospital Structure
SAP divides the Hospital Structure into two different configurations items:
Organizational Units
Departments
Todays workshop
Clinics (optional)
Wards
Building Units:
Buildings
Alleys Next workshop
Rooms
Bedplaces
7.1. Use of Organizational Structure (1)
A service (e.g. departmental per diem) can be generated on the basis of this
assignment
Organizational units that do not share a direct hierarchical relationship can assign
beds to each other.
Institution Hospital
Hospital11 Hospital 2
...
Surgery
- Clinic clinic
Organizational Units
Departmental
Institution
...
Hierarchy of Categories
7.5.1. Organizational Unit Categories
DA This indicator controls whether an organizational unit can be departmentally responsible for a case.
NA This indicator specifies that an organizational unit can have nursing responsibility for an inpatient or
day patient case.
OV Outpatient visit allowed. If this indicator is set, outpatient visits can be assigned to this organizational
unit.
Int This indicator specifies that an organizational unit outside of the hierarchy can be on a lower-level with
regard to another organizational unit within that hierarchy.
Asg OU May Assign Patients to Beds on OU of Other Dept. Example: A department assigns patients to beds
on a care unit which "belongs" to another department.
MRA Medical Record Archive Indicator
Req By means of this indicator, you can determine whether service requests regarding service processing
can be made to the organizational unit.
Pln The indicator specifies that the organizational unit manages a patient waiting list relative to service
processing.
Prf The indicator specifies that the organizational unit is functional for performing services regarding
processing of services.
7.6. OU Category Hierarchy
Before you create organizational units, you have to define the underlying
components of the organizational structure. You need to define which
organizational unit categories can be located above which other organizational
unit categories in the structure: (Action Item 5)
7.7. OU Specialties
1 General Medicine
2 General Surgery
3 Dermatology
4 Neurology
5 Urology
6 Opthalmology
7 ENT Medicine
8 Rehabilation Medicine
9 OTH: others
8. Organizational Unit Master Data
Nursing OU (Ward)
/
Bangsal
Outpatient:
Outpatient Dept. OU
Treatment OU (Outpatient Clinic)
Building Units
(Treatment Rooms)
8. Organizational Unit Master Data
Considerations:
OU Cost Center Assignment
OU MM Plant and Storage Location Assignment
Note:
These two topics are going to be discussed in the MM and FI Integration specific
sessions but should be considered at the time of defining the Org.Structure.
9. Authorizations
MIKA to provide the list of users and roles following the defined Basis Matrix
format. The mentioned roles will include the corresponding authorization objects
to create/change/display Organizational and Building structure units.
(Action Item 8)
10. Action Items
Action Item 2:
Technical Number Ranges (Section 5) (Internal or External No. range)
Action Item 4:
Organizational Unit Categories (section 7.5.1. - Use Config template attached in section
8, tab OU Categories)
Action Item 5:
OU Categories Hierarchy (section 7.6 - Use Config template attached in section 8, tab
OU Categories)
Action Item 6:
Specialties (section 7.7 Use Config template attached in section 8, tab ISH Config
Data)
Action Item 7:
OU Master Data (Use Config template attached in section 8)
Action Item 8:
Authorization Roles (section 12 - Use Authorization Matrix provided by Basis team)