SAP ABAP IMG Activity SIMG_CFMENUORKEKEA0 (Maintain Operating Concern)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KE0C (Package) Customizing for Profitability Analysis
IMG Activity
ID SIMG_CFMENUORKEKEA0 Maintain Operating Concern  
Transaction Code S_ALR_87005737   IMG Activity: SIMG_CFMENUORKEKEA0 
Created on 19981222    
Customizing Attributes SIMG_CFMENUORKEKEA0   Maintain Operating Concern 
Customizing Activity SIMG_CFMENUORKEKEA0   Maintain Operating Concern 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUORKEKEA0    

In this activity, you define and maintain the operating concerns you are going to use in your system.

If you want to create a new operating concern, you need to create the subobjects data structure and attribute and to activate the environment:

Data structure

The data structure determines the structure of the profitability segments that you can analyze and how costs and revenues are organized. All information in the data structure definition is valid for all clients. If you use the operating concern in more than one client, you still only need to define the data structure once. You then need to set the attributes in each client individually.

One of the specifications you make for the data structure is the type of Profitability Analysis. You can only activate the operating concern for the types you specify here.

The structure of the operating concern is defined by the characteristics and - in costing-based Profitability Analysis - by the value fields as well:

  • Characteristics

    Characteristics are the segments of your organization for which you want to analyze your data in CO-PA.

    Several fundamental characteristics are predefined in every operating concern. These are called "fixed characteristics". You can display a list of the fixed characteristics by choosing Extras -> Fixed fields.

    In addition to these predefined fields, you can define up to 50 of your own characteristics in each operating concern. You can select these from a list of additional predefined characteristics, or you can create your own using the Customizing function Maintain Characteristics.

  • Value fields

    Value fields are the fields in costing-based CO-PA in which the system stores the amounts and quantities. They thus determine the structure of your costs and revenues.

    An operating concern can contain up to 120 value fields. The standard system contains a list of predefined value fields (such as "Sales quantity" or "Sales revenue").

    If you want to define additional value fields, you can do this using the Customizing function Maintain Value Fields.

To add fields (characteristics or value fields) to your operating concern, select the desired fields on the Edit Data Structure screen (right side of the screen). Then use the function Transfer fields to copy these fields to the data structure. You can only transfer fields with an active status. AN operating concern cannot contain two fields for which the meaning, the short text, or the field title overlap.

Once you have defined your data structures, you need to activate them. When you activate the data structures, the system creates the tables for plan and actual data in the database system.

If you choose to add new characteristics or value fields at a later stage, you should note that these do not work retroactively. However, you can supply new value fields with existing planning data using the "Automatic planning" function or the "Periodic valuation" function. To fill new characteristics retroactively, you need to perform the "Realignments" function.

Deleting characteristics/value fields from an operating concern
You can delete characteristics and value fields retrospectively from an operating concern that you have already activated. However, you should only use this deletion function for operating concerns that have not yet been used productively. You should also note that some database systems require the operating concern tables to be converted (database conversion) after the deletion has taken place if data had already been posted to the operating concern. Depending on the data volumes involved, the database conversion can take a matter of seconds or indeed several hours. Moreover, you cannot post data or run reports during the conversion. Due to integration, other applications are also affected when data is postedwith an assignment to profitability segments (such as settlement and direct assignment from FI/MM). If the operating concern has been transported to another system (such as the productive system), then the database conversion must also occur in that target system.

Depending on the fields that were deleted, the following tables need to be converted (where xxxx = operating concern):

  • Characteristics: CE1xxxx, CE2xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
  • Amount fields: CE1xxxx, CE2xxxx and CE3xxxx
  • Quantity fields: CE1xxxx, CE2xxxx, CE3xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC

Before deleting fields from an operating concern with a large data volume (more that 10 000 records in a table), you should refer to the section "The Database Utility" in the ABAP dictionary documentation. This section describes the database conversion process.

For database systems that do not require conversion (such as DB2 for AS/400, Informix, MSSQL), it can still take a considerable amount of time for the operating concern to be activated.

To delete characteristics or value fields, perform the following activities:

  1. Delete the corresponding characteristics and value fields from Customizing in all clients (this includes forms, reports, planning layouts, and so forth). To locate characteristics and value fields, use the appropriate where-used list in the Customizing Monitor. You can access it by choosing Tools -> Analysis -> Check Customizing Settings. You can jump directly from the where-used list to the relevant Customizing transaction and then delete the appropriate field there.
  2. Switch to the screen for maintaining the data structure of an operating concern (Maintain operating concern).
  3. If you need to effect other changes to the datastucture for the operating concern before making any deletions, effect those changes and save the data structure.
  4. In order to be able to select the fields of the data structure, choose Extras -> Characteristics (or Value fields) -> Unlock.
  5. Select the characteristics and value fields to be deleted and remove them from the data structure with the "Reset fields" function.
  6. Reactivate the operating concern. The system starts by checking whether the operating concern contains any data and whether the fields to be deleted are still being used in any Customizing settings.
  7. If none of the fields are still in use, the system then starts the re-activation. If the operating concern does not contain any data or does not require the database system to be converted, the tables are activated. You are then able to activate the environment for the operating concern. In this case, the following activities no longer apply.
    If the operating concern already contains data, a system message tells you that the database needs to be converted. If you proceed, an activation log appears (at the top of the list).
  8. Analyze the activation log. If it only contains error messages telling you to convert the tables, proceed with the next activity.
    You must otherwise remove the cause of the errors before the tables can be converted. In this case, you should answer "No" to the next prompt, which asks whether the conversion transaction should start.
  9. If you still only receive error messages telling you to convert the tables, choose "Back" and start the conversion.
  10. Plan a job for the conversion. A list of the tables to be converted is shown for this. If the tables only contain a small amount of data (less than 10 000 records), then all the tables can be converted in one job. In that case, you can select all the tables.
    For larger tables, conversion should take place in several jobs. However, you should ensure that table CE4xxxx (where xxxx = operating concern) is the last table to be converted.
    Warning. No other changes can be made to the operating concern during the conversion.
    A copy of the table is generated during the conversion. The database system should have sufficient memory available for this copy.
    To schedule conversion as a job, use the "Schedule selections" function. You can display the current status of the conversion by selecting the "Refresh" icon. Tables disappear from the list once they have been converted sucessfully. If a conversion is taking a while, it is also possible to leave the transaction. You can then continue the conversion using DB requests -> Mass processing in one of the following ways:
    With the job overview. You access this by choosing System -> Services -> Jobs.
    Using the database utility transaction. You access this by choosing Utilities -> Database Utility in the ABAP Dictionary menu.
    You can use the status function to call up the status of the operating concern during operating concern maintenance. You need to activate all tables after conversion.
  11. To analyze errors that have occurred during the c
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_CFMENUORKEKEA0 0 HLA0100152 Structures 
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
KEA0 T - Individual transaction object KEA0 01 CO-PA: Maintain Operating Concern 
History
Last changed by/on SAP  19990208 
SAP Release Created in