Define User-Defined Characteristics

In this step you can create characteristics that you can use in addition to the reference characteristics for the following purposes:

For more information on types of characteristics and their usage possibilities, see Order hierarchy and selection

User-defined characteristics are generally not required in Cost Object Controlling. The following information is applicable only when the available reference charactreristics do not meet your requirements.

In contrast to the reference characteristics, user-defined characteristics do not reference fields in the order master record. Instead, you must manually enter the values for user-defined characteristics during the maintenance of an order master record.

Once you have created a user-defined characteristic and assigned it to the class SAP_KKR_CLASS (class type 013), this characteristic is offered for maintenance with all orders.

If you want to have certain characteristics offered for maintenance not for every order but only for a certain order type or object class, you must also define dependencies with reference to the relevant order types or object classes and assign them to the characteristic.

Example of a user-defined characteristic

You can use the characteristic INVEST_CAT (investment category) to classify your orders by the size of the investment. This characteristic has the following values:

Characteristic value Designation
<10000 Investments up to 10,000
<50000 Investments up to 50,000
<100000 Investments up to 100,000

Example of a dependency

You have created the following characteristics:

Characteristic Designation
INVEST_CAT Investment category
SERVICE_TYPE Service type
SERVICE_CATEGORY Service category

You must do the following:

These dependencies must have the dependency type "Precondition", and as the condition reference the characteristic SAP_KKR_ORAUART (order type).


Decide whether the orders that cannot be represented by the available reference characteristics should be summarized according to certain characteristics or selected.

To be able to use the criteria, go to Classification and create user-defined characteristics that correspond to these criteria as follows:

1. Create the characteristics.
a) Enter the name of the characteristic. Conform to the naming convention for characteristics.
b) Select the areas for which you want to enter data, and confirm your entry.
c) Specify the following under Basic data:
The data type
The value assignment (single-value)
The status (1 = released)
Whether a value must always be assigned to the characteristic in classification
d) Maintain the corresponding language-dependent designations and headers for your characteristic.
e) Maintain the values allowed for your characteristic.
f) Define the interface control for the entry of the characteristic value in master data maintenance.
g) If appropriate, limit the use of your characteristic to class type 013 (CO orders).
2. Assign the characteristic or the characteristics to class SAP_KKR_CLASS (class type 013).
3. If appropriate, create dependencies as follows:
a) Enter the name of the dependency.
b) Specify the following under Basic data:
The designation of the dependency
The status of the dependency (1 = released)
The dependency type "Precondition"
c) Edit the dependency by choosing Goto -> Dependency editor.
4. Assign these dependencies to the relevant characteristics by choosing Extras -> Object dependencies -> Allocations when changing the characteristic.

Additional information

For more information on defining characteristics, see the Implementation Guide for Classification (Cross-Application Components).

To enable characteristics for creating a hierarchy to be used, the characteristics must meet the following conditions:

Notes on transport

Characteristics and classes are transported in the ALE concept (Application Link Enabling) for distributed R/3 applications. This concept is explained in detail in the document "CA - ALE Consultant's Handbook".

Before transporting, you must carry out the following steps:

The following objects are used:

Object Designation
CHRMAS Characteristic
CLSMAS Classes

Then you must use transaction BALE to select the master data for the characteristics and classes and specify the interval for the objects to be distributed.

Object dependencies are not transported.

Otherwise you must carry out all activities listed here in each client in which you want to work.