Rule Resolution Using Responsibilities

You would use the responsibilities rule type if you

want to determine organizational data for individual responsibilities
have not created an organizational model but want to create one
have a lot of organizational units and must only assign a few attributes

For the system to determine organizational data using the responsibilities rule type, you need to use organizational units. However, these do not need to be linked. Therefore you do not need to create an organizational model for this determination path. The attributes are defined directly in the rule container.

If you use rule resolution using responsibilities, you do not have to assign attributes in the organizational model, other than the attributes distribution channel and division; these are necessary for showing the sales area.

Prerequisites

You have transferred the required organizational units to SAP CRM or have created them in Customizing. You can find information for creating organizational units under creating objects.

You have created a determination rule with the responsibility rule type in Customizing and assigned it via the organizational data profile to the required transaction type.

Process

This graphic is explained in the accompanying text.

Determination of organizational data using the responsibility rule type:

Default Settings

You have defined the organizational units:

O 50002300 – Service Organization M
O 50002320 – Service Group M2

You have assigned a determination rule to the Service Order transaction type. This defines the following responsibility: Service Group M2 (O 50002320) is responsible for Partner Numbers 3000 to 4999.

Process Flow

You receive a service order from Customer 3001 – Becker Manchester
You create a service order.
The system uses the determination rule, which has been assigned to the transaction type Service Order in Customizing, to find the organizational unit responsible for an evaluated attribute in the transaction.
The system finds the attribute Partner number, reads the value 3001 in the transaction and uses this to determine the organizational unit responsible for it, in this case, Service Group M2.
The system reads the other attributes assigned to (or passed onto) the organizational unit Service Group Manchester and determines the data which is necessary to complete the organizational data of the transaction. In this case, Service Organization 50002300 (or in sales transactions, sales organization and distribution channel).

Result

The organizational data is in the transaction. If required, you can change this data manually.

Using organizational data, the system determines further data for the transaction, for example, involved partners, prices and terms of delivery.