SAP ABAP Data Element KALKU_D (Control of Costing)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
     ⤷ VZ (Package) Application development R/3 RV central functions
Basic Data
Data Element KALKU_D
Short Description Control of Costing  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type KALKU    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Costing 
Medium 15 Costing 
Long 20 Costing required 
Heading 3 Cst 
Documentation

Definition

Controls whether costing a sales document item is:

  • Required
  • Simulated
  • Allowed
  • Not permitted

Use

You set this indicator depending on how you want to plan and update the costs in sales-order-related production.

Procedure

  • Enter X if you want the sales document item to be costed.

    Create a sales order so that the sales order item receives status ZKAL (to be costed). This means that you must create a sales order cost estimate. Subsequent functions such as delivery and billing are only allowed when costing has been carried out with no errors. If there were errors during costing, the sales document item is given status ZKAL again.

  • Enter A if you want costing to be simulated.

    Costing the sales document item is only simulated. The simulation is not saved in the system. The status is not updated. Subsequent functions such as delivery and billing can be carried out at any time.

  • Enter nothing if costing is allowed and the status can be updated.

    Costing is not necessary but is allowed. If you do cost the sales document item, then subsequent functions such as delivery and billing are only allowed if there were no errors during costing. If there were errors, the sales order item receives the status ZKAL.

  • Enter B if you do not want the sales document to be costed.

Dependencies

Performance

Before making costing mandatory for a sales document item, remember that this may adversely affect performance.

Standard Pricing Determination for Valuated Sales Order Stock

If you are using a valuated sales order stock, determine whether you are in a complex make-to-order production environment or in a sales order-related mass production environment. In the latter case, costing is not necessary to determine the standard price for each individual sales document item. You can control this in the requirements class with the indicator Val. strategy.

See also: Valuation strategy for valuated sales order stock

Results Analysis for Nonvaluated Sales Order Stock

Sales order costing must be set up if you work with nonvaluated sales order stock and if you want to carry out the results analysis for stock valuation taking into account the planned costs determined using sales order costing.

See also: Indicator Profit basis under Define Valuation Methods for Results Analysis

Create Sales Order Cost Estimate Automatically

You can use indicator Costing to define whether the sale order item is costed automatically or both costed automatically and marked.

See also: Automatic costing of sales document items

History
Last changed by/on SAP  19970812 
SAP Release Created in