Show TOC
Check
Requirements Classes
In this step you check the requirements classes
to make sure that they meet the requirements of
Cost Object Controlling.
In this step you view or change the parameters
in the requirements class that are relevant to cost accounting. You create the
requirements class in Customizing for Sales and Distribution.
You do this in Customizing for Sales and
Distribution under
Define requirements classes.
Costing
The
Costing indicator in the requirements class controls for a sales
order item whether:
The
Costing ID indicator controls whether a sales order cost estimate
is automatically costed, or automatically costed and marked.
The requirements class contains additional
default values for costing:
The costing method
determines whether the sales order cost estimate is created using the
functions of or
unit costing. If you don't enter a costing method in the
requirements class, then you specify the costing method in the
application.
The costing variant
contains control parameters for product costing and unit costing. If you don't
enter a costing variant, you must select a costing variant in cost
estimate.
The costing sheet
contains control parameters for the calculation of overhead. It determines the
following:
- Which direct costs (such as direct material
costs) the overhead is allocated to
- The conditions (such as by controlling area or
plant) under which overhead is calculated
- The amount of the percentage or quantity-based
overhead rate depending on these conditions
- Which object (such as cost center or order) is
credited during actual postings, and under what cost element
- Which template should be selected for the
sales order item
The Copy costing
sheet indicator controls whether the costing sheet in the sales
order item is transferred to all assigned production orders.
In the requirements class for product costing,
you can use the Pass on costing sheet indicator to
specify that the costing sheet in the sales order item is used for calculating
overhead for subordinate materials from individual requirements. The costing
type is selected through the costing variant.
The field
CndTypLineItems (condition type for transferring costs from line
items) allows you to control which condition type the results of a sales order
item are written under. This condition type is valid for all sales document
items of this requirements class. Entering condition types in the requirements
class allows you to use different condition types for different sales document
items in the same sales document.
The field
CondTypIndItFx (condition type for fixed cost transfer from line
items) allows you to specify that the fixed costs of the results of the sales
order item are transferred separately. This transfer of fixed costs is in
addition to the transfer of costs from line items. The fixed cost transfer is
statistical and improves analysis of the contribution margin.
Account
Assignment
The requirements class also contains the
following parameters that are relevant to Cost Object Controlling:
- Account assignment category
The requirements
class specifies an account assigment category. The account assignment category
determines the following:
- Whether the material is carried in
the
- Whether the sales order item carries costs and
revenues
- You control the following in the requirements
class with the indicator
Valuation:
- Whether the sales order stock is
valuated (entry: M and
A)
- Whether the sales order stock is
nonvaluated (no entry)
With a sales order
item that carries costs and revenues, the costs are handled as
follows:
- With the valuated sales order stock, the costs
are assigned to the sales order item at the time of delivery to the
customer.
- With a nonvaluated sales order stock, the
costs are collected on production orders and settled at the end of the period
to the sales order item or - for externally procured trading goods - assigned
directly to the sales order item.
- The W/o val. strat.
indicator controls the following:
- Whether the sales order stock is valuated with
the standard price on the basis of a predefined strategy sequence
In this case you
don't set the indicator. For information on the strategy sequence, see the
field help for W/o val. strat..
- Whether the sales order stock is valuated with
the standard price of the non-customer stock.
The settlement
profile determines the following:
- The settlement receiver (for example,
profitability segment or G/L account) to which the results analysis data
calculated for the sales order item (such as the
cost of sales,
reserves for imminent loss) or the costs and revenues on the
sales order item can be settled
- Whether the settlement share should be
calculated as a percentage or in equivalence numbers
- For more information on the functional area,
see the SAP Library under FI -> Cost of Sales Accounting
Other
Settings
The following parameters can also be applicable
to Cost Object Controlling:
In assembly
processing, a manufacturing order, network, service order, or planned order is
generated together with the sales order. You can perform assembly processing
with two different methods: static (a manufacturing order or planned order is
generated for a sales order item) or dynamic (multiple manufacturing orders or
planned orders can be generated for a sales order item). You select the method
of assembly processing in the assembly type.
In static assembly processing with
manufacturing orders, you can transfer the planned costs for the manufacturing
order or the costs calculated on the basis of the sales order cost estimate
into SD pricing. You control this with the Sales order costing
indicator.
Activities
Check the requirements classes.
Further
Notes
For more information, see
Define Requirements Classes.
The requirements class is determined through
the requirements type. You can choose the requirements type as
follows:
- Through the item category group in the Sales
view of the material master record the order type of the SD document (inquiry,
quotation, sales order)
- Through the MRP group or the strategy group in
the MRP view of the material master record
See also:
Check control of requirements type determination