SAP ABAP IMG Activity SIMG_CFMENUORKEKE4A (Define Condition Tables)
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_CFMENUORKEKE4A Define Condition Tables  
Transaction Code S_ALR_87005724   IMG Activity: SIMG_CFMENUORKEKE4A 
Created on 19981222    
Customizing Attributes SIMG_CFMENUORKEKE4A   Define Condition Tables 
Customizing Activity SIMG_CFMENUORKEKE4A   Define Condition Tables 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUORKEKE4A    

In this step you define condition tables for Profitability Analysis (CO-PA).

Condition records in CO-PA are stored in CO-PA-specific condition tables whose key consists of specific combinations of characteristic values. Each condition table represents a different combination of characteristics and can be used by any number of conditions. (Different conditions may depend on the same characteristics, such as customer and product, in the same system.)

The key of the condition table consists of those characteristics that make up the key of the condition record.

To create a condition table, proceed as follows:

  1. Specify a number between 501 and 999.
  2. Enter a name for the condition table and double-click on the characteristics you want to use for the key.
  3. Generate the table.

If desired, you can limit the period of validity of the condition table. If you do, all the condition records in this table are stored with this period of validity. The table must be a transparent table (table type "T").

Examples

  1. You want to use the condition type KPRA, which grants a price reduction for certain combinations of customer and product, in a costing sheet. In this case, you would select the fields "Customer" and "Product" from the CO-PA field catalog for Table 501 (technical name: "A501"). If you wanted the price reduction to depend on the customer group, you would create a new condition table, 502 ("A502"), and enter the field "Customer group" from the field catalog.
  2. You want to calculate a percentage value based on the value of the characteristic "Material group". However, for certain materials a different value percentage rate should be used. Only if the material sold is not one of these materials should the percentage be based on the material group.

    To do this, you first need to create two condition tables: table 503 for the characteristic "Material" and table 504 for the characteristic "Material group". Then you can define an access sequence ZZ01 that accesses these tables -- first table 503 (since the material should have higher priority), and then table 504. Once you have then assigned this access sequence to a condition type, you can define condition records in these tables for that condition type.

          Access sequence               Condition tables
               ZZ01                     1. 503 ("Material")
                                        2. 504 ("Material group") 

Actions

Create your CO-PA-specific condition tables.

Additional information

You can use all the characteristics in Profitability Analysis -- in all operating concerns -- in the keys for condition tables. Thus if you have different characteristics that have the same text in different operating concerns, both of these characteristics appear in the field catalog. The fact that they have the same texts suggests that a double entry exists.

You should only use characteristics from the same operating concern in a condition table. You can use the function "Field attributes" to display the corresponding data element for a characteristic in the field catalog. By comparing this data element with the data element stored in table CE1xxxx (xxxx = operating concern) for that characteristic, you can see which operating concern the field belongs to.

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_CFMENUORKEKE4A 0 HLA0100169 Valuation 
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
KE4A T - Individual transaction object KE4A 01 Change Condition Tables 
History
Last changed by/on SAP  19981222 
SAP Release Created in