Overview of SAP Organisation Model concept

This blog post covers what every SAP technical and functional consultant must know about the SAP Org Model concept. It presents a summary of what is important to know about the Org Model composition, ways of accessing it and setting up organization determination.

Organisation Management in SAP CRM displays a company's organisational structure relevant for its sales and service related processes.

Each organisation has its own organisation structure laid in the form of a hierarchy based on the company's different units, its positions (designations) based on functions of its employees and the position holders/employees.

What is Org Model composed of?

The org model is composed of:

1. Org Unit:

• Org Units are functional units of a company. For e.g. Departments, group, project teams.
• An Org unit is technically a Business Partner with 'Org Unit' role. Creating an org unit automatically creates a business partner with the Org Unit role.
• The object type key is 'O'.

2. Position:

• Positions are assigned to an org unit to specify the role of its holders within the org unit and represent the reporting structure in the org model.
• The object type key is 'S'.
• You can define a Chief Position within an org unit. To this position, all other positions in the org unit report.
• A position inherits the attributes of the org unit to which it is assigned. So, you cannot assign it any attributes explicitly.

3. Holder:

• A holder is the occupier of the position within an org unit.
• It can be an Employee (BP with the employee role) of the Org. or a CRM User.
• The object type key may be 'CP'(Central Person in case of Employee) or 'US'(in case of user).

Ways to access Org Model in SAP CRM

1. SPRO IMG ->  Customer Relationship Management -> Master Data -> Organisational Management -> Org Model
2. T-Code : PPOMA_CRM
3. WEB UI: Depends on business role. For e.g. In Sales Professional Business Role, it can be accessed from Sales Operations -> Org Model

A few must-know facts about the Org Model

• The Org Model in SAP CRM can be different from the ERP Org Structure.
• An Org Model can have any number of levels in the hierarchy.
• Org Units can be assigned validity periods.
• For any changes in the org model, no delta load of the org data happens from ECC to CRM.
• Same Organisation can be used as a sales org and a service org at the same time.
• Matrix structure of an organisation cannot be displayed in SAP CRM.

Attributes of Organisation Unit

There are 2 type of attributes an organisation unit can have:

1. Org. Attributes

2. Business Attributes

1. Org. Attributes

Organizational attributes define the type of organizational unit, for example, whether it is a sales organization or a service group.

2. Business Attributes

Business attributes define the responsibility of an organizational unit, for example, for which distribution channels or product groups an organizational unit is responsible.

A really good example of the use of attributes is explained here.

Org Data Determination

Ways of Org Determination

SAP CRM offers the following ways to determine org data in the transaction:
1. No determination: This means that the org data has to be manually entered in the transaction.
2. Automatic Determination: This means that the system will automatically determine the org data using the available data in that transaction. For e.g. region, product etc.

Setting up Org Determination

1. First, you have to create a determination rule (in case of auto determination).
2. Then, you have to assign the determination rule to an Org Data Profile.
3. Finally, assign the Org Data Profile to a transaction type.

SPRO Setting
SAP IMG -> Master Data -> Organisational Management -> Org Data Determination

Rule Types
1. Rule Type Responsibilities
2. Rule Type Org Model

I have covered Organization data determination using both the rules and with examples in a little more detail here.

Buffering the attributes

To improve the performance of any query that is accessing the org data, the report HRBCI_ATTRIBUTES_BUFFER_UPDATE is used to buffer the generic attributes.

To make the reading of the Org data faster, all the Org data is stored in buffer table INDX (cluster table) and temporary table CRMD_ORGMAN_TEMP.

When this report is run, it deletes the data in buffer table INDX and temporary table CRMD_ORGMAN_TEMP and fills it again.

Select what to buffer
View cluster T770MATTR consists of the scenarios for which the buffering can be activated. Just go to SM30 to maintain table T770MATTR and indicate the scenario for which you want to activate buffering.

Precaution
Please make sure that when the report is running in the background, no other program - dialog or background, tries to access the Org data as it might create locking issues for the buffer table INDX.