Select language:
Entering content frame!--a11y-->

Function documentation 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 the CRM System you have the following options for determining organizational data in the document. 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 document.

·  automatic determination

The system determines organizational data using the data available in the document, for example, the business partner number, region, product, or using the user assignments for the organizational unit (using the position).


No automatic determination


  1.  You have created an organizational data profile in Customizing, in which no determination rules have been entered.

  2.  You have assigned this organizational data profile to the required transaction type.

Automatic determination


  1.  You have created a determination rule in Customizing for each determination path with the corresponding rule type.

  2.  You have defined one or two determination rules in the organizational data profile for evaluating the organizational data profile of a transaction.

  3.  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.


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 the document 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.

·  Structure linkDefining rules using organizational data

·  Structure linkDefining rules using function to be executed

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 document, 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 organizational data screen)

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

Specifics of Channel Management

In activities and leads in the partner portal of Channel Management, the channel partner does not have access to organizational data, in partner created documents. Consequently, organizational data can only be set using the automatic organizational data determination procedure. You need to set your system so that automatic organizational data determination occurs correctly in leads and activities, for the channel partner. In other words, the organization data determination procedure must find only one correct sales area for an organizational unit and enter this in the document. This is necessary because the channel partner cannot change, or display, the organizational data in documents. You can also use this organizational data determination procedure for channel management documents created on the channel manager’s side.

SAP delivers a sample organizational data determination profile for leads, opportuinities, and activities in channel management which is used in the transaction types LDPO, LDCP, OPPO, OPPC, ACPO, and ACCP.

The related organizational data determination procedure provides one possibility for the brand owner to specify a certain sales area as channel management relevant. Determination is enabled using the transaction type attribute in the organizational model, which is connected to an organizational data determination procedure. The system uses the procedure to check if the document’s transaction type is maintained as a transaction type attribute in the organizational model. 

The transaction type attributes are standard attributes delivered by SAP in the organizational model. You must maintain the attribute value for the transaction type used for the channel document, that is LDPO, LDCP, OPPO, OPPC; ACPO, or ACCP in the SAP standard delivery. If you use different transaction types you must set the attribute accordingly.

It may happen that organizational data determination cannot determine the division because more than one division has been assigned to a certain organizational unit. In this case the system displays all assigned divisions in a dialog box and requests the partner to select one.

The partner cannot display or change the selected division in this case, because partner applications do not support organizational data access.

To stop the system display in such a dialog box, you can set automatic division determination using a BAdI. For further information see the IMG for Customer Relationship Management under:

Customer Relationship Management -> Master Data -> Organizational Management.



  1.  The system determines the responsible organizational unit

  2.  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.



Leaving content frame