Hierarchy
⤷ IS-B-PA-STC (Application Component) Single Transaction Costing
⤷ JBTC (Package) Customizing IS-B Transaction Costing
IMG Activity
ID | SIMG_CFJB08JB49 | Create Condition Table |
Transaction Code | S_KK4_13000045 | IMG Activity: SIMG_CFJB08JB49 |
Created on | 19990830 | |
Customizing Attributes | SIMG_CFJB08JB49 | Create Condition Table |
Customizing Activity | SIMG_CFJB08JB49 | Create Condition Table |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFJB08JB49 |
In this step you choose the characteristics to be used as a key (condition) when the condition records are determined.
Example
For the costing component risk costs, for example, you can create three condition tables:
Condition table Condition
Risk costs dep.on rating class Rating class
Risk costs dep.on industry + prod.group Industry, product group
Risk costs dep.on cust.grp + rating cl. Customer grp, rating class
In the first table, the risk costs are determined on the basis of the rating class transferred with the single transaction. The second table uses the industry and product group etc.
Recommendation
If, when selecting "permitted fields" you discover that you have forgotten certain characteristics when generating the operating concern, you can generate them retrospectively.
Once a characteristic is qualifed as a condition, after the condition table has been generated, it can not be deleted. Your only option is to delete the entire condition table.
You can only change the sequence of the characteristics in the list of "selected fields" before the condition table is generated.
Requirements
You must define the characteristics in the operating concern in which you want to use the characteristics as conditions.
Standard settings
If you qualify several characteristics as a condition, the values for the last listed characteristic (usually the last selected characteristic) in the list of selected fields is used as a basis. This characteristic appears as a Line item in condition record maintenance. All other characteristics appear in the Header.
Example:
First you want to combine value 'A' for the characteristic 'Customer group' with all values for the characteristic 'Rating class' and store condition records for the resulting combinations. You then want to combine value 'B' for the characteristic 'Customer group' with all values for the characteristic 'Rating class'. In this case you define the condition 'Rating class' as a line item and the characteristic 'Customer group' as a header.
You can change the Line item or Header of the characteristic even after generating the condition table (see Activities). This excludes the last characteristic in the list of "Selected fields". This last characteristic is preset as line item.
Activities
- The initial screen displays the table number assigned by the system. Confirm this number. If a table with this number already exists, delete the number and confirm the empty field. Also confirm the default settings in the dialog box which now appears.
- Enter an appropriate name for your table. You will use this name to access the condition tables in the next steps.
- Select the conditions for this condition table. All the characteristics in your operating concern which you can qualify as a condition are listed. Select the required characteristic and choose Select field. You can also double-click on the characteristic.
- Change the sequence of the characteristics in the list if required. To do this, select the characteristic you want to move and choose Select block . Now select the characteristic in front of the one where you want to insert the characteristic and choose Move. Once you have generated the condition table you can no longer change the sequence.
- Change the criterion Line item or Header if required (see the standard settings)
- To do this choose Technical view and in the next screen select the Line field of the characteristic which you want to appear as a line item in condition record maintenance. You can change the criterion Line item or Header after generation as well.
- Once you have selected all the characteristics, generate the table using Generate.
Additional information
You can use a condition table for several costing components (e.g. the costing components provision costs and equity costs may depend on the product group qualified as a condition in one condition table) that is, a condition table may be included in several access sequences.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-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_CFJB08JB49 | 0 | I070004701 | Profitability Analysis |
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 |
V_T681F | V - View | JB49 | IS-B | Field Catalog (&1 &2) |
History
Last changed by/on | SAP | 19990830 |
SAP Release Created in |