In SAP SD Training you might have seen that as soon as you enter the Customer Master during the creation of the Sales Document, all the associated Sales Areas that the customer master has been extended for will come up automatically in the pop-up and you can manually choose the one in which you wanted to create the transaction.
This is about the utmost amount of flexibility that ECC gives us when dynamically determining the org elements. However, SAP CRM gives a much more sophisticated way to determine the Org Units automatically based on certain criteria. Let’s just get started with the simplest case – Manually entering the Org Unit data in the SAP CRM Transaction.
For example, when creating a quotation (Say Transaction Type -AG ), if a dummy Organizational Data Profile (one with no rule types attached – We will talk about them in a bit ) is assigned to the Transaction type in SAP CRM Transaction Type Customization, then you can enter the org data like Sales Organization, Sales Office etc in the ‘Organization’ tab of the quotation.
We are however interested in a more sophisticated role based/attribute based, automatic way of determining the Org units. Before going any further into the different rule types, lets understand how this helps businesses.
For example, imagine the Call center receiving a call from a Customer calling from (732) 600-0000 . If we can write a rule in such a way that depending on the area code ( 732 in this case is the area code for Edison, NJ ), the sales office would be automatically determined as the New Jersey Office. Subsequently, through the course of taking the call if a sales opportunity comes up and the Customer requests for a quotation, the org units can automatically be determined through the area code of the customer. You can extend this scenario to many other parameters – Zipcode, Partner Number Range and so on.
Simple scenarios can be configured directly using the in-built org determination rules like ORGMAN_1, ORGMAN_10, PARTNER_1 etc. More complicated scenarios can be configured using customized coding ( Function Modules ). These rules can be assigned to Org Data Profile and in turn the org data profile is assigned to the Transaction Type.
There are mainly 2 different types of automatic org determination in SAP CRM. There are other more sophisticated rules that require a knowledge of ABAP to understand, but nevertheless are used extensively as well.
Method 1 : Responsibility Rule Type
In this type of rule, based on the values of the chosen parameter/s, the set of org unit/s will be determined.
Method 2 : Organizational Model Rule Type
This type of rule is based on matching the attributes associated with the org units with the data in the transaction.
Follow the link for a detailed discussion on SAP CRM Organizational Model vs Responsibility rule type and examples on when to use each of them.