SAP ABAP IMG Activity SIMG_CFJB08JB46 (Define Costing Sheet)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ IS-B-PA-STC (Application Component) Single Transaction Costing
     ⤷ JBTC (Package) Customizing IS-B Transaction Costing
IMG Activity
ID SIMG_CFJB08JB46 Define Costing Sheet  
Transaction Code S_KK4_13000054   IMG Activity: SIMG_CFJB08JB46 
Created on 19990830    
Customizing Attributes SIMG_CFJB08JB46   Define Costing Sheet 
Customizing Activity SIMG_CFJB08JB46   Define Costing Sheet 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFJB08JB46    

In this step you combine several condition types in a costing sheet. At the same time, you create the dependencies which exist between the condition types in value determination.

In addition to that, you establish the following in the costing sheet:

  • In which order the condition values are to be determined
  • How the system is to calculate percentage markups and markdowns
  • Which requirements need to be met for a particular condition type to be taken into account
  • Which subtotals are to be determined

Example

Level    Cond. type    Ref. step    Condition    Formula    Subtotal

10    CT1       

20    CT2       

30    CT3    10        386

40    CT4    20        387

50    CT5    30        386

60    CT6    40        387

70    CT7        304                    2

80    CT8                            1

90    CT9        306    383

100    CT10        304    384

110    CT11    10        386

120    CT12    20        387

130    CT13    110        386

140    CT14    120        387

Requirements

You must:

  • Have defined condition types

Activities

  1. Assign a name and a description.
  2. Choose 'Navigation -> Levels', and the detailed settings screen appears.

    Here you set the condition types used in costing. At the same time, you define the order in which the condition types are determined, represented by levels. You can also decide which subtotals should be calculated, and how the system calculates percentage markups and markdowns.

    For every level, that is, for every condition type, the following settings are very important:

    1. From level/To level
      2. For a condition type with a markup (markup valuation), you need to specify a base value. Using this indicator, you set a level ('From level') or an interval ('From level' and 'To level'). If you only enter one level, the condition value for this level is the base value for the markup. If you specify an interval, the total of the condition values for these levels is the base value for the markup.
    2. Conditions
      3. Conditions specify under which circumstances the system will access this level, and thus the condition type.
      A possible condition would be, for example, that the condition type is only accessed in the reporting period in which the transaction term begins.
      If you do not specify a restriction, condition valuation will be carried out in every period. Different predefined conditions that are available to you in SAP Banking are described later. The conditions refer to the entries in the fields 'Transaction begin' and 'Transaction end' in the profitability analysis part of the financial object.
    3. Formula
      4. A formula refers to a non-standard valuation procedure used for determining condition values. There are several predefined formulas, which are described in detail in Additional Information.
  3. Save your entries.

Additional Information

  1. Conditions:

  • Condition 304 (first period)

    'Condition 304' is fulfilled when the current period is the first period of the transaction. That is, when the term of the transaction starts within the current reporting period.

    Use: For condition types which only occur in the first period of a transaction.

  • Condition 305 (last period)

    'Condition 305' is fulfilled when the current period is the last period of the transaction. That is, when the term of the transaction ends within the current reporting period.

    Use: For condition types which only occur in the last period of a transaction, such as unit deletion costs.

  • Condition 306 (first or last period)

    'Condition 306' is fulfilled when the current period is the first or the last period.

    Use: For condition types which only occur in the first and last period of a transaction, such as transaction charges.

  1. Formulas:

  • Formula 381 (periodization using the interest calculation method actual/actual)

    Using this formula, the condition record is split into periods according to the number of days lapsed in the reporting period and the fiscal year.

    For example, periodization of risk costs: If the risk cost rate for a condition table is stored annually, this is broken down for the current reporting period to the exact day using the flexible procedures for this formula.

  • Formula 382 (equal distribution)

    Using this formula, the condition value is distributed to whole periods according to the term of the transaction.

    For example, the distribution of a unit cost contribution: The formula calculates the number of reporting periods that fall between the term start and end. In doing so, the system interprets the periods in which the transaction starts and ends as whole reporting periods. The interest conditions contribution is divided by the number of reporting periods and displayed proportionally in each period. In addition, the condition value before distribution is totalled on buffer 2. This enables the NPV of the interest conditions contribution to be calculated.

  • Formula 383 (total 1)

    This formula makes it possible to include unit costs which occur at the end of the transaction term in the calculation of total unit costs at the start of the transaction. The unit cost contributions are determined using condition types. You also need to enter 'Condition 306' for these condition types. This ensures that the condition types are only determined at the start and at the end of the transaction.

    To ensure that unit cost contributions do not appear in period values at the start of the transaction term, but are only included when calculating the total, you need to enter 'Formula 383'.

    To calculate the total use 'Formula 384'.

  • Formula 384 (total 2)

    This formula, when used with a condition type with control 'IBB' and condition '304' makes it possible to calculate the total of the unit costs. Individual unit cost contributions are determined using separate condition types. Note the following to ensure that the unit cost contributions are calculated correctly:

    • 'Start': The condition value has to be added up in clipboard (buffer) 2 (enter the value '2' in the conditions subtotal field). Choose condition '304' (condition determination only at start of transaction).
    • 'End': Choose 'Condition 306' (condition determination at start and end of transaction) and formula '383'.
    • 'Current': Add the condition value up in clip board (buffer) '1' (in the field 'condition subtotal' (SubTot), choose '1').
    • 'Distribution': Enter formula '382'.
  • Formula 385 (subtotal 3)

    This formula makes it possible to calculate a total in conjunction with a condition type with control 'IBB'. The required condition types have to be set in subtotal '3'. Afterwards, subtotal '3'is deleted, which means that using this formula, all condition types with the entry '3' in the field 'Subtotal' are totalled and stored in the condition type.

  • Formula 386 (percentage rate in accordance with subtotal 4)

    This formula makes it possible to have a percentage rate as a subtotal.

    This ensures that the condition value can be reused. If a percentage rate is needed more than once in a costing sheet, then it only has to be read once from the conditions table. The subtotal field remains empty.

  • Formula 387 (percentage rate from subtotal 4)

    This formula makes it possible to reuse a percentage rate which was stored in subtotal '4' using formula '386'. This is done in conjunction with a condition type with control 'IAA'.

    Subtotal '4' is deleted after condition valuation.

  • Formula 388 (summation)

    This formula makes it possible to add together the condition values from several condition types by entering an interval in the fields 'FromLev' and 'ToLev'. The valuation result can be assigned to a value field and be displayed there as a total.

    You can achieve the same result by assigning the condition types you want summated to the same value field. If more than one condition type is assigned to a field, the system will add them up.

  • Formula 389 (periodization using interest calculation method actual/360)

    Using this formula, the condition value is distributed over periods according to the number of lapsed calendar days (current) for the reporting period and fiscal ye

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_CFJB08JB46 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
ISB_KSCHM C - View cluster SM34 IS-B Procedures 
History
Last changed by/on SAP  19991124 
SAP Release Created in