Show TOC

Valuation Strategies

The valuation strategy contains the methods used for valuating value fields in costing-based CO-PA.

It determines the methods used to fill different value fields and the order in which these methods are processed.

You can valuate data using the following methods:

CO-PA-specific condition types

Material cost estimates

User-programmed valuation routines

Transfer prices

In CO-PA planning, you can also valuate data using condition types and pricing procedures from the Sales and Distribution (SD) application component. Valuation using transfer prices is likewise only possible in planning.

Example

The following valuation strategy calls for valuation using product costing, then using a CO-PA costing sheet ("ACT001" ), then using a user-programmed valuation routine ("U01").


 Sequence    Appl. Cstg sheet  Name       Mat.cstg Qty field  Exit no.


    10                                        X       VVIQT


    20       KE     ACT001                            VVIQT


    30                                                          U01

Valuation using material costing is used primarily to determine the cost of goods manufactured of the products sold in billing documents that are transferred to CO-PA. It allows you to add the fixed and variable cost of goods manufactured to the CO-PA line item in order to compare them to the sales revenues and sales deductions transferred with the original billing document.

The conditions technique lets you calculate values that are required for analyzing contribution margins in CO-PA but are not yet known at the time the original document is posted. In particular, this make it possible for you to calculate such values as sales commission, cash discounts, sales deductions, or freight costs.

You can use your own valuation routines to calculate any values that cannot be determined using either of the above methods.

Activities

First, define the valuation strategies you want to use. Then assign these strategies to the desired points of valuation.

Further Notes

Each valuation step contained in a CO-PA valuation strategy is assigned a number. This number determines the order in which the system processes the steps in that strategy.

Value fields that are filled using a previous valuation step are not overwritten by subsequent steps. The only exception to this is when you use a user exit. Once a value has been calculated in one step, you can use that value to calculate other values in subsequent steps.

As a rule, value fields that are filled before valuation is carried out in CO-PA -- regardless of whether they were transferred from SD or entered manually -- can only be changed or overwritten in valuation by a user exit. The only exception to this are values entered manually in CO-PA planning. Here the values found using automatic valuation always take priority over values entered manually in the planning layout.

Plan valuation using pricing procedures from Sales and Distribution (SD)

When you define a valuation strategy to be used solely in CO-PA planning, you can also use prcing procedures from Sales and Distribution (SD) (application class "V" in the field "Application"). Note that this is not allowed for valuation of actual data , since there the SD conditions are transferred directly from the billing document or sales order as defined in the value field assignments of the SD interface.

If you use an SD pricing procedure for valuation in planning, the system transfers the values of the conditions to the value fields as assigned in the SD interface.

Under certain circumstances, it may not be possible to use all conditions from SD to valuate data in CO-PA. For example, the access sequences used in the SD pricing procedures may contain condition tables with fields that are not defined as CO-PA characteristics. Consequently, before using an SD pricing procedure, be sure to check whether the fields required by the access sequence are defined as characteristics in your operating concern. Otherwise the system will not find the condition records, even if they have been maintained in SD.