Handling Costs in Assembly Processing 

Use

The planned and actual costs of a project or a network can be handled in different ways in assembly processing.

Features

As described in Account Assignment, the controlling object for assembly processing with the Project System can be either the sales order or the project.

The account assignment category is specified in the requirements class (see Material Requirements in Assembly Processing).

If you select the project as the cost object (account assignment category D), you can see the costs from the network in the sales order on the Pricing tab page. Here the costs form the basis for price determination. However the project not the sales order is used in controlling.

For more information about price determination and conditions, refer to Pricing and Conditions in the Sales and Distribution (SD-BF-PR) component.

 

Activities

Header/Activity Assigned Networks

Activity Assigned Networks

If you use an activity assigned network, you have more options for structuring your costs in the project. Since each activity can be assigned to a different WBS element, more detailed cost information is available.

In this case the cost object for assembly processing is the project. If you use activity assigned networks for assembly processing, the sales order has to be account assigned to the project (account assignment category D).

Header Assigned Networks

In this case the costs are passed directly to the network header. You can use either the sales order or the project as the cost object. If you are working only with a network, you have to use header assigned networks, since activity-assigned networks cannot have a sales order as a cost object and no project exists.

Valuated/Non-Valuated Stock

If you use valuated stock, every goods movement produces a corresponding posting in financial accounting (FI). This does not happen with non-valuated stock. For more information, see Valuated Project Stock and Non-valuated project stock.

You can only use valuated sales order stock together with header assigned networks that are not assigned to a WBS element. For more details, see Account Assignment.

Restrictions

If you use the sales document as the cost object, the system only transfers those costs that originate directly in the network to the sales order. This means that costs that originate from a subnetwork or directly on a WBS element are not transferred to the sales order. This means that you should be careful how you structure your project, if you use the sales order as the cost object.

If you use projects as cost objects, this problem does not arise.