General Attribute Maintenance
You can use general attribute maintenance to attribute data (attributes) to organizational units, when creating your sales and distribution or service structure. You always maintain these attributes specifically for a scenario (Sales or Service).
CRM distinguishes between organizational and business attributes:
organizational attributes define the type of organizational unit, for example, whether it is a sales organization or a service group.
business attributes define the responsibility of an organizational unit, for example, for which distribution channels or product groups an organizational unit is responsible.
Attributes can have one or more values. For some attributes, you can also enter areas (for example, partner numbers 001 to 300).
Example
You maintain the following attributes for organizational unit Office
Manchester
:

The organizational unit Office Manchester
is
therefore responsible for distribution channel 10 - direct sales – and the
regions Cheshire
, Greater Manchester
and Lancashire
.
For service transactions, on the other hand, the organizational
unit does not have access to the attribute Region
;
it is responsible for the whole of Great Britain.
Attributes are generally passed onto the subordinate organizational unit. You can find further information under attribute inheritance.
The values of the attributes in the organizational model can be read from the system, and can be used, for example, to find the organizational units responsible for processing a particular transaction.
Attribute maintenance can be seen in info type 1222 from the basis
component Organizational Management
. Info type
1222 (general attribute maintenance) is only used in CRM.
Each scenario corresponds to a sub type from info type 1222. All
modules required for reading the attributes are summarized in the function
group RHOMATTRIBUTES
.
General attribute maintenance is used for generic data filing in the form of a key value (or value area). Using the so-called scenarios, data can be sub-divided logically.
Each attribute (key/value pair) has certain characteristics, for example
a reference to the Data Dictionary
specific F4 help
specific types of inheritance
Predefined attributes are delivered for Sales and Service scenarios and for Enterprise Buyer.
You maintain the attributes for organizational units immediately when creating your organizational model in Customizing for Organizational Management under or when maintaining your organizational model in the SAP Menu under .
In the detail screen, choose the Attribute
tab
page and enter the required attribute values. You can find a list of attributes
for the Sales and Service Scenarios and their most important characteristics
under Attributes
for Sales and Service Scenarios.
You can maintain organizational attributes that correspond to your
sales and distribution or service structure in the R/3 system (sales organization,
sales office, sales group or service organization) on the Function
tab
page (Type tab page in the Human Resources System).
In the enhanced
backend integration version of the CRM organizational model, there
is a grid table on the Function
tab page in
which you maintain multiple
assignments for the organizational units. This table is not in
the standard
backend integration version as you do not maintain multiple assignments
in this version.
You can find more information on processing the organizational model under displaying/editing objects.
Restrictions
You cannot maintain attributes for the following organizational objects in CRM:
Positions
Positions inherit the attributes of the higher-level organizational unit.
Holders (employees and users)