Show TOC
Check Costing
Variants for Product Costing
A
costing variant contains the necessary control parameters for
calculating the planned costs for a sales document item. With
product costing you can calculate the planned costs for the
following sales documents:
You can use the costing variant defined in for
bothsales order costing and
order BOM cost estimates.
Product costing is performed using the
following information in the sales document:
The material can be
a stockable material or a configurable material.
Product costing creates a
quantity structure using the BOM and routing and possibly the
object dependencies for the material ordered.
This quantity structure is valuated using the
valuation variant.
The costing variant controls the
following:
- Which prices are used to valuate materials,
internal activities, external activities, and
subcontracting
- The date on which the BOM and routing are
selected
- The date on which the prices for the
materials, internal activities, and so forth, are selected
The costing data is transferred into the sales
document as a condition value and can be used for pricing in SD. Which
condition type the costing data is transferred into is controlled in the
requirements class.
See also:
Check Requirements Class
The costing variant forms the link between the
application and Customizing, since costing is carried out and saved with
reference to a costing variant.
The costing variant also determines the
following:
- Whether a log containing the system messages
is generated
You have the
following options:
Messages are shown
in the status bar individually. The Log function is
inactive in costing.
- Collect/save messages/Mail active
Messages are logged
and can be sent to the employee responsible for correcting the
error.
Messages are logged
and the log can be saved.
Messages are logged,
but the log cannot be saved.
- Whether and how the costing lot size is passed
on
You have the
following options:
The costing lot size
in the material master record is used as a basis for costing all materials in
a low-level code. If materials such as semifinished products are used in
materials such as finished products of the next-highest low-level code, the
costs for the finished product are calculated by converting the costing
results to the costing lot size of the material costed (in this case, the
finished product).
This function is
mainly used in costing runs.
- Pass on lot size only with individual
requirements
In the MRP 1 view of
the material master record you can define that a material is planned as
individual requirements . If a material with this
requirements type is used in another material, costing is carried out using
the costing lot size of the highest material.
In this case the
costs for all materials in a multilevel BOM are calculated using the costing
lot size of the highest material.
The
cost component split is always saved. You must specify whether
the following values are also saved:
You can specify
whether the user can change the update parameters and the parameters for
transfer control.
- Whether you can postprocess a product cost
estimate with unit costing
Note that order BOM cost estimates are only
transferred if they were created with the same costing variant. You should
therefore use the same costing variant for sales order cost estimates as for
order BOM cost estimates.
Requirements
If you want to use your own parameters, you
must carry out the following steps:
If you want to use the log, you must already
have carried out the following steps:
If you want to postprocess a product cost
estimate for the sales order cost estimate with unit costing, carry out the
following step:
Check costing variants for unit costing
Standard
Settings
The standard system contains the predefined
costing variant "PPC4 / Sales Order Costing".
Costing variant "PPC4 / Sales Order Costing"
specifies that the system should use the lot size of the order when costing
materials from individual requirements. This costing variant points to the
following parameters:
- Costing type "18 / Sales Order
Costing"
Parameters for the
calculation of overhead surcharges are entered in the costing
type.
- Valuation variant "001 / Planned Valuation for
Material"
- Transfer control "PC03 / Sales
Order"
The strategies in
this transfer control only apply to materials from collective
requirements.
The standard system provides costing variant
"PC04 / Sales Document" in costing variant "PPC4 / Sales Order Costing" for
postprocessing a product cost estimate with unit costing.
Recommendation
You should assign a different valuation variant
to each costing variant with which you intend to save cost
estimates.
This one-to-one assignment enables you to
change the valuation strategies later as required.
Activities
Decide whether the costing variant provided in
the standard system meets your requirements.
To create a new costing variant:
1. Enter an
alphanumerical key and a name for the costing variant.
2. Assign a
costing type and a valuation variant to the costing variant.
3. Specify the
following:
- How error messages on costing are to be
issued
- Whether the lot size of the highest assembly
should be used to cost the material components below it
4. Specify the
following:
- Whether the costing results should be
saved
- The default values for the update
parameters
- Whether the system should use a cost estimate
without quantity structure for a particular single-level BOM
- Whether the parameters for transfer control
can be changed manually when you carry out costing
5. Assign the
costing variant to a requirements class if necessary.
This ensures that
costing for sales documents with this requirements class always uses this
costing variant.
Further
Notes
In the requirements class, you can specify
whether the costing method is product costing or
unit costing. To check what costing method is used, carry out the
following step:
Check requirements classes