Features of Org Data Profile :
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 scenariocan 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 organizational data screen) | Do not assign the organizational data profile to the item category. |
Note: You can find more information about the header division in the implementation Guide (SAP IMG) Under CRM Master Data Organizational Management Division Settings.
Activities
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.
No comments:
Post a Comment