SAP ABAP Data Element RKE_TERKRS (Operating concern)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KE (Package) Profitability Analysis

Basic Data

Data Element	RKE_TERKRS
Short Description	Operating concern

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	RKE_TERKRS
Data Type	CHAR	Character String
Length	4
Decimal Places	0
Output Length	4
Value Table	TKEBB

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID	ERB
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Op.concern
Medium	15	Op. concern
Long	20	Operating concern
Heading	4	OpCo

Documentation

Definition

From a technical viewpoint, an operating concern consists of:

1. objects valid in all clients
   These include the data structures and the environment of the operating concern.
2. client-specific objects
   These include the attributes, PA transfer structures, forms, reports, and so on.

Note that any changes you make to the data structures affect all the clients in your system.

Further notes

The operating concern is locked while you maintain the data structures. This means that no transactions can be carried out for the operating concern. Before you start maintaining the data structures, though, you must make sure that all the processes accessing the operating concern have finished. Otherwise your data may be inconsistent.

History

Last changed by/on	SAP	19971104
SAP Release Created in