Connecting the Cost Collector to Claims (SAP Library

Connecting the Cost Collector to Claims

Use

When you carry out a project, changes are often made which cause additional costs to be incurred.

Claim Management enables you to save the data relevant to the changes in a claim and estimate the additional planned costs relevant for Controlling, which these changes cause.

Using this function you can transfer the costs of this claim to a cost collector (internal order) and then settle these for the assigned WBS element.

Integration

You must implement Claim Management and internal orders.

Prerequisites

To be able to use this function, you must fulfill the following prerequisites:

You must be using SAP R/3 Enterprise PLM Extension 1.10 (EA_APPL 110) presently.

To activate this function you must implement the Business Add-In Customer-Specific Check Before Creating Cost Collector (NOTIF_COST_CUS_CHECK) and set the E_CREATE_COST_COLLECTOR to 'X‘. For more information, see the Implementation Guide (IMG) for Project System under Claim ® Settings for Claims ® Business Add-In: Customer-Specific Check Before Creating Cost Collector

So that the system creates a cost collector when you create a claim, you must assign a Controlling scenario to the claim’s notification type. To define these assignments, carry out the following IMG activities in Customizing for Project System:

Claim ® Settings for Claims ® Controlling Scenario for Claims

Claim ® Settings for Claims ® Assignment of Controlling Scenario for Notification Type

For more information, refer to the IMG.

Features

The system creates the cost collector automatically when you save. The estimated costs are transferred to a cost collector linked to the same WBS element as the claim. The estimated costs are now relevant for Controlling and are taken into account by the corresponding reports.

You see the WBS element and the claim number in the cost collector. The status MKOS (cost collector created) indicates that a cost collector is assigned to the claim. Maintain the data in the claim. The cost collector data and the claim data are synchronized (see Updating the Cost Collector).

Creating a Cost Collector

The system creates the cost collector automatically when you save if:

You carried out costing for the claim
The claim does not have to be approved or was already approved
You entered a WBS element in the claim
This WBS element is an account assignment element
This WBS element has been released or partially released
A profit center is entered for this WBS element or a dummy profit center can be determined, if Profit Center Accounting is activated
A business area is entered for this WBS element, if business area financial statements should be created for the company code of the WBS element
There are no customer-specific checks to prevent creation (Business Add-In NOTIF_COST_CUS_CHECK)

Note

The system assigns the automatically created internal order (cost collector) the order type CL01. You should not change the settings for this order type. The only exception is if you enter a different status profile.

The following data is transferred to the cost collector:

WBS element
Controlling area, company code (derived from the WBS element)
Business area (derived from the WBS element)
WBS element profit center or dummy profit center
A key word (in English "notification") plus the claim description create the cost collector description.

The estimated costs for the claim are defined as planned costs in the cost collector. The system recalculates the costs in the claim (for technical reasons) before creating the cost collector.

Note

If you changed the claim costing without transferring these changes manually, and if you want to create or change a cost collector, the system automatically transfers the changes when you save the claim.

Once the cost collector has been created, the system sets the status MKOS (cost collector created) in the notification.

The system displays the claim number in the internal order (KO03).

Updating the Cost Collector

The WBS element is reconciled in the claim and in the cost collector if the WBS element fulfills the same conditions necessary for when you create the cost collector. You can change data dependent upon the WBS element, such as the profit center, only if you change the WBS element as well.

Note

You can change the Description, WBS Element, Profit Center, and Business Area fields directly in the cost collector. However, inconsistencies between the claim and the internal order could result. To avoid this, you must hide these fields in the internal order field selection, or set them so that they cannot be changed.

If you change the estimated costs for the claim, the planned costs for the cost collector are changed automatically.

You can change the planned costs for the internal order manually. If you want to prevent this, you must set a user status in the internal order that does not allow the business activities Unit Costing Planning (KSTE) and Primary Cost Planning (RKP1). The business activity Primary Unit Costing (KEKP) is used for the claim.

If a deletion indicator is set for the claim, a deletion indicator is set for the cost collector as well. If the deletion indicator for the claim is deleted, then the deletion indicator for the cost collector is deleted as well. You can change the status of the claim only if you change the status of the cost collector.

Otherwise there are no other relationships between the claim and the cost collector. If the claim is completed (for example, it is no longer approved) the cost collector is not affected in any way.

Changing the WBS Element

You can change the WBS element that was assigned to the claim. The following prerequisites must be fulfilled:

The new WBS element must be an account assignment element.
This WBS element must be released or partially released.
If Profit Center Accounting is active, you must have specified a profit center or the system must be able to determine a dummy profit center.
A business area must be specified for this WBS element, if business area financial statements should be created for the company code of the WBS element.

Application Log

If errors occur when you create or change the cost collector, the system saves the error messages in the application log and you can view them after saving. Once you leave the claim you can no longer view the messages. The system saves the claim in all cases.

Activities

There are no special activities for using this function, since the system creates the cost collector in the background when you create a claim.

See also:

Claim Management

Creating and Processing Claims