Define segment level characteristics

With this function you can influence your system's performance in CO-PA directly by specifying which characteristics should be used for creating profitability segments.

CO-PA performance is largely dependent on the number of profitability segments. One or more records are kept in the segment table for each profitability segment and fiscal year.

Consequently, repetitive manufacturers with a large number of customer orders each day should not use the sales order number as a characteristic for forming profitability segments. This would only make sense for order-related manufacturing, where the number of sales orders per period is small. Either way, the sales order number is still stored and displayed the line item in costing-based CO-PA.

For the same reason, you also should not use the origin objects CO order, project and cost object as characteristics for profitability reports or planning. These fields are likewise displayed in the line item.

When you create a new operating concern, the relevant table is automatically set so that the fields

- sales order (KAUFN)

- sales order item (KDPOS)

- CO order (RKAUFNR)

- project (PSPNR)

- cost object (KSTRG)

are not used to form profitability segments, while all other characteristics - including the customer and the product - are used and therefore are available for profitability reports, planning and account assignments to profitability segments. If you need to make a setting other than the default ones, change the entries accordingly. The fields which are not contained in the table are used to form profitability segments (indicator is set to "X" by default).

For technical reasons, the field "Sender cost center" currently cannot be used as a characteristic for profitability reports and planning.

Additional information

If you do not need the individual customer or product in your profitability report or in planning, you can perform profitability analysis at the customer group or product group level by setting the table accordingly. This improves the system performance substantially.

For more information on the use of characteristics, see the F1 online help for the field "Characteristic".


Specify which characteristics of your operating concern should be used to form profitability segments.

Notes on transporting

You can transport the settings you made to your productive system using the CO-PA transport tool.

Note that the generated ABAP Repository objects are valid for all clients. Conflicting name in the target system can also lead to problems in other applications. Therefore you should make all Customizing settings in one (source) system. You can then transport these settings to your other (target) systems. This technique helps you avoid inconsistencies.

If you cannot use this technique for some reason, be sure to observe the following:

1. Characteristics and value fields with the same name must have the same text, the same attributes (type, length), the same check table and the same origin table in each system.
2. For characteristics which were defined manually, enter the number for the check table manually as well. Each characteristic must have the same number in all systems. The assignment of the number to the characteristic must be unique.

In order to ensure that Customizing settings are consistent in the target system, the transport tool always transports larger objects, such as reports, key figure schemes, or the operating concern itself. Consequently, some activities are not automatically recorded in transport requests, since that would lead to inconsistencies.

The settings you process in this section are transported together with the operating concern.

On the selection screen of the transport tool, select the object operating concern , and then choose the desired dependent object types.

You can transport the following dependent objects:

The following settings are transported as well:

The system creates a transport request which contains the objects you want to transport.