SAP ABAP IMG Activity SIMG_CFMENUOKCMKCD0 (Edit aspect)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KC (Package) Cost Accounting Controlling EIS

IMG Activity

ID	SIMG_CFMENUOKCMKCD0	Edit aspect
Transaction Code	S_ALR_87000351	IMG Activity: SIMG_CFMENUOKCMKCD0
Created on	19981222
Customizing Attributes	SIMG_CFMENUOKCMKCD0	Edit aspect
Customizing Activity	SIMG_CFMENUOKCMKCD0	Edit aspect

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	SIMG_CFMENUOKCMKCD0

In this step, you can process EC-EIS or EC-BP aspects, their data structures, environments and master data modules online.

Maintaining the data structure for an aspect is the major part of creating, modifying and deleting an aspect. The data structure is stored as a table in the ABAP dictionary.

The components of the data structure are the individual fields which are divided up into aspect-specific characteristics and basic key figures. The characteristics represent the objects which can be evaluated using key figures and displayed in presentation.

You can enter the aspect-specific fields either during the maintenance of the data structure or directly in the field catalog (see below)

When creating an aspect you allot a number between 500-999. The aspect numbers between 001-449 are reserved for delivered aspects.

Aspect attributes

When creating a new aspect you must enter certain properties.

• The fiscal year variant controls the number of periods of a fiscal year and is determined per aspect.
• You can define the characteristic 'data area' (VERSO) as an alternative to the fiscal year variant, as a FYV-bearing characteristic. The fiscal year variant is attached to this characteristic and is valid for the aspect. This possibility is only used for aspects that were created up to and including Release 3.1. For new aspects, it it is recommended that you directly enter a fiscal year variant.
• The aspect currency is assigned to all basic key figures of the aspect, for which no other currency has been established, by default.

Field catalog

The field catalog contains the fields of all aspects that have already been defined. Fields from the field catalog can be transferred with the definition of the aspect data structure.

If a field is in the field catalog once that it can no longer be changed, up to report-based attributes.

Fixed characteristics of the aspect

Each aspect contains the fixed characteristics

• Plan / actual indicator
• fiscal year
• period
• version You do not need to enter these fixed characteristics because they are automatically generated when you save the data structure. Check tables for these characteristics are delivered with the system and the contents can be maintained by the user. Fixed characteristics are explained in further detail under section 'Master data' in the EC-EIS and EC-BP online documentation.

Definition of the characteristics for an aspect

You can find information on the definition of characteristics in the section Creating characteristics.

After you have created your characteristics, assign them to your aspect. Proceed as follows for this:

1. Select a field group if applicable. As default all the fields in the field catalog will be offered. With filter conditions you can use certain criteria, data element, description, data structure, to search for fields within a field group.
2. Highlight the desired characteristic in the template. (You can display the definition of a field by highlighting the field and selecting 'Extras -> Characteristics -> Detail info.')
3. Select 'Transfer fields'. The field appears at once in the data structure.

The characteristics appear in the data structure of the aspect after the saving, as a series of fields, in the sequence in which they were entered. Using the functions 'Edit -> Edit -> Cut / set', you can change the sequence of the fields. After you have saved the aspect you can no longer change the sequence.

Definition of basic key figures for an aspect

You can find information on the definition of basic key figures in the section Creating basic key figures. After you have created your basic key figures, assign them to your aspect. You do this in the same way as the transfer of the characteristics.

With the function 'Change view', you can get a view of the most important attributes and fields of the data structure.

Saving/activating the data structure

The function "Save" creates or changes the aspect's data structure in the ABAP dictionary.

When you choose "Activate" all the dictionary objects are activated with the help of the mass activation program; the tables that correspond to the ABAP Dictionary description are created or modified on the database. The aspect cannot be posted to nor analyzed in the info system until it has been set to 'active'.

Deletion of the database table

With the function 'Data structure -> Delete DB table(s)' the aspect table can be deleted on the database and (optionally) recreated. The aspect's transaction data are then, of
course, lost.

The function can be used to:

• delete fields from the structure table (only possible when the CM table
  does not exist);
• delete test data and prepare the aspect for productive start.
  

View aspects (only in EC-EIS)

A view aspect enables you to evaluate data over more than one table. When you define a view aspect, you must choose the aspects to be included in it. Then you can choose the characteristics and basic key figures which interest you from the fields of these aspects.

When creating a view aspect, note the following:

• The affected aspects must possess the same fiscal year variant.
• When you select transaction data for reporting a database inquiry is generated for each 'physical' aspect attached to the view aspect if certain conditions are fulfilled (see below).
• If, when you defined the report, you did not choose any key figures from the 'physical' aspect, a database inquiry is not generated.
• The selection conditions for these database inquiries contain the conditions for the characteristics contained in the 'physical' aspect. What happens if you choose a characteristic in a report which does not exist in a 'physical' aspect? If the characteristic is based on one characteristic value for the whole report, a database inquiry for this 'physical' aspect will not be generated and therefore, no records will be read. Otherwise, a database inquiry for this 'physical' aspect will be generated and the transaction data will be classified as not assigned as soon as you drill down this characteristic.
• If a basic key figure is contained in more than one 'physical' aspect, it will be read for each 'physical' aspect as soon as a database inquiry has been generated. This can lead to the totaling of the key figures from the affected aspects and should be avoided.
• You can create key figures for a view aspect.

View aspects are useful because the number of fields in relational databases is limited. This means that, in particular, the number of basic key figures was insufficient for certain applications. View aspects are especially useful if they use aspects which have many similar characteristics and differing basic key figures .

Generating the aspect environment

You can generate the environment for an active data structure. The environment includes update programs for data entry and a program for displaying raw transaction data. These objects are generated automatically. The environment must have been generated before you can maintain the transaction data.

Deleting an aspect

You can delete an aspect as a unit. This function deletes the data structure, database table, data structure (ABAP dictionary table) and aspect environment.

The fields of the aspect remain in the field catalog as individual objects. If you wish to delete fields which are no longer referenced from the field catalog, you can do this in the characteristic or basic key figure maintenance.

When you delete an aspect, remember to delete objects such as key figures and reports which are no longer of relevance if the aspect table no longer exists. However, while you are setting up a new aspect, you can store these objects for reference.

Activities

Configure the EC-EIS or EC-BP data basis according to your informational needs. Proceed as follows:

1. Transfer the desired characteristics.
2. Transfer the desired key figures.
3. Save the aspect data structure.
4. Activate the aspect data structure.
5. Generate the environment objects

Further notes
Currency concept
Technical hints
Transport of settings

Business Attributes

ASAP Roadmap ID	203	Establish Master Data
Mandatory / Optional	1	Mandatory activity
Critical / Non-Critical	1	Critical
Country-Dependency	A	Valid for all countries

Assigned Application Components

Documentation Object Class	Documentation Object Name	Current line number	Application Component	Application Component Name
SIMG	SIMG_CFMENUOKCMKCD0	0	HLA0009491	Data Collection

Maintenance Objects

Maintenance object type

C

Customizing Object

Assigned objects
Customizing Object	Object Type	Transaction Code	Sub-object	Do not Summarize	Skip Subset Dialog Box	Description for multiple selections
KCA0	T - Individual transaction object	KCA0	EIS	☐	☐	SAP-EIS: Edit aspect

History

Last changed by/on	SAP	19981222
SAP Release Created in