Attributes for Sales and Service
Scenarios 
Use
You can assign attributes to your organizational units in the organizational model. The system evaluates these attributes, if it uses the organizational model determination rule in transaction documents of organizational units. There is further information on this type of organizational data determination under rule resolution using organizational model.
The following list displays which attributes are available in CRM and describes the most significant default characteristics.
Prerequisites
You have become familiar with the concept of general attribute maintenance.
Features
As a rule, attributes that you have assigned to an organizational unit are passed onto the subordinate organizational units. Inherited attributes can be overwritten. If the standard system deviates from this inheritance type, there is a note below.
Some attributes are not only used in the standard for organizational data determination; they are read by the system of this organizational unit and entered into the transaction document (for example, distribution channel) after the determination of the organizational unit (Service and Sales) in the document.
Note that default settings for attributes should not be changed.
Business Attributes for Both Scenarios (Sales and Service)
|
Attribute |
Technical Name |
Characteristics |
... Read in Document from … |
|
Country |
COUNTRY |
Multiple-value |
Address of main partner |
|
Region |
REGION |
Multiple-value areas permitted |
Address of main partner |
|
P.O. Box |
POSTBOX |
Multiple-value areas permitted |
Address of main partner |
|
Postal Code |
POSTCODE_1 |
Multiple-value areas permitted |
Address of main partner |
|
District (Sales District) |
DISTRICT |
Multiple-value |
Address of main partner |
|
Activity Reason |
ACT_REAS |
Multiple-value |
“Activity Reason” field in transaction |
|
Last Name (of Contact Person) |
NAME_LAST |
Multiple-value areas permitted |
Contact person of main partner entered in document |
|
Partner Number |
PARTNER |
Multiple-value areas permitted |
Main partner |
|
Function of Contact Person |
PARTNERFKT |
Multiple-value |
Function description in contact person master data (for example, janitor) |
|
VIP Partner |
PARTNERVIP |
Multiple-value |
Relationship of contact person to main partner from master data of main partner (for example, supervisor of…) |
|
Branch |
IND_SECTOR |
Multiple-value |
Main partner master record |
|
Product Group |
PRODGRP |
Multiple-value |
From product master (only at item level) |
|
Product Number |
PRODUCT |
Multiple-value areas permitted |
From product master (only at item level) |
|
Correspondence Language |
LANGU_CORR |
Multiple-value |
Contact person master record |
|
Text Module - Footer |
TXT_FOOTER |
|
Not
used in determination; |
|
Text Module - Header |
TXT_HEADER |
|
|
|
Text Module - Sender |
TXT_SENDER |
|
|
|
Text Module - Signature |
TXT_SIGN |
|
Business Attributes for Sales Scenarios Only
|
Attribute |
Technical Name |
Characteristics |
... Read in Document from … Comments |
|
Distribution Channel |
D_CHANNEL |
Multiple-value |
Sales data of main partner master record; Not only used for determination, but also derived from the organizational unit (Sales) of document |
|
Division |
DIVISION |
Multiple-value |
Either: Product (at header level), if you are not using a header division Or: Organizational data of main partner master record, if you are using a header division.
Not only used for determination, but also · for creation of Sales areas in CRM · to check whether product divisions of document item fit to Sales divisions in the Organization Model. |
|
Combination of Division and Distribution Channel |
CHAN_DIV |
Multiple-value |
Serves to limit combination possibilities from Division and Distribution Channel fields |
|
Reference Currency of Document |
CURRENCY |
Cannot be overwritten |
Is not used for determination, but is derived from the sales organization and taken over in the document |
|
Telephone Number for Call Center |
DNIS |
|
Is transferred by Computer Telephony Integration (CTI) system to the system |
|
Status |
STATUS |
Multiple-value |
Transaction status |
|
Order Net Value |
NET_VALUE |
Areas permitted |
Transaction price data |
|
Item Quantity |
QUANTITY |
Areas permitted |
Total quantity (confirmed quantity) of product in transaction |
|
Is Hosting Organization |
IS_HOS_ORG |
|
Indicates an organizational unit which acts on behalf of another organizational unit. For example the hosting organization is responsible for carrying out processes for another partner. The hosting organization is derived from the responsible organizational unit in a business transaction. For further information about Channel Management, please see SAP Library -> Customer Relationship Management -> Channel Management. |
The attributes listed below are used exclusively in partner determination using determination rules of the Responsibilities rule type. It is therefore not useful to store values for organizational units for these attributes.
Attributes for Partner Determination Only
|
Attribute |
Technical Name |
Characteristics |
Comments |
|
Organizational Unit (Sales) |
SA_RESPORG |
Multiple-value areas permitted |
Not
used in Organizational Model; |
|
Organization Unit (Service) |
SE_RESPORG |
Multiple-value areas permitted |