Determining Organizational Data
When processing a business transaction, certain organizational data is mandatory depending on the transaction type. In a service order, for example, the service organization that is responsible for processing is a determining factor. The distribution channel in a sales order is as important as the responsible sales organization, as price and delivery data can depend on the distribution channel.
In SAP CRM you have the following options for determining organizational data in the transaction. You can set these in Customizing depending on the transaction type:
no determination
In this case, enter the organizational data (for example, sales area) manually in the transaction.
automatic determination
The system determines organizational data using the data available in the transaction, for example, the business partner number, region, product, or using the user assignments for the organizational unit (using the position).
Prerequisites
No automatic determination
You have created an organizational data profile in Customizing, in which no determination rules have been entered.
You have assigned this organizational data profile to the required transaction type.
Automatic determination
You have created a determination rule in Customizing for each determination path with the corresponding rule type.
You have defined one or two determination rules in the organizational data profile for evaluating the organizational data profile of a transaction.
You have assigned the organizational data profile to a transaction type.
You carry out the settings in Customizing for CRM. Choose 
Master Data
Organizational Management
Organizational Data Determination
.
You can find further information in the documentation there.
Features
When determining organizational data, the system takes the organizational data profile defined in Customizing and the determination rules from this profile. These determination rules specify which fields are taken into account when the system determines organizational data from transaction data (for example, business partner number, telephone number). Determining organizational data can be set by assigning the organizational data profile for the business process type so that it is dependent on the business process type.
There are two determination paths provided in the CRM system that have been characterized for the two rule types:
Rule type Responsibilities
Rule type Organizational Model
The basis rule types Organizational Data
and Function
Module
are available in CRM, but to use them you must have
ABAP/4 knowledge. You can find information on these rule types in the basis
documentation.
If you define two determination rules in the organizational data profile, the system creates the intersection from the resulting quantity of the two rule resolutions.
Determining organizational data can differ according to the scenario,
because an organizational unit in the Sales scenario
can
have different attributes with different values to an organizational unit
in the Service scenario
.
Organizational data at item level
If you do not use a header
division in business transactions, the Division
attribute
only exists at item level. In this case the division is derived from the product
and all of the organizational data at item level of a transaction, except
for the division, may not differ from that in the header. There is therefore
no individual organizational data determination at item level. The following
options for organizational data at item level are possible. You can set these
in Customizing. They are dependent on the item category.
Settings for Organizational Data at Item Level
Organizational data at item level |
Settings you must make in Customizing |
|---|---|
Without header division: The organizational data is copied from the document header. The division is derived from the product. |
Assign an organizational data profile without a determination rule to the item category. |
With header division: The organizational data is copied from the document header. The division is derived from the document header. |
Assign an organizational data profile without a determination rule to the item category. |
There is no organizational data at item level (no |
Do not assign the organizational data profile to the item category. |
You can find more information about the header division
in
the Implementation Guide (IMG) under CRM Master
Data
Organizational Management
Division Settings
Activities
The system determines the responsible organizational unit
The system reads the other attribute values for this organizational unit, and, if necessary, uses them to determine other data, for example, the distribution channel.
If the system determines more than one responsible organizational unit or determines several attribute values for the responsible organizational unit, a selection screen appears.
More Information
Specifics for Partner Channel Management