Assign costing keys to other characteristics

The steps

Assign costing key to product and

Assign costing key to material type

let you assign costing keys to individual materials or material types.

If this assignment is not flexible enough to meet your requirements, you can also define your own assignment tables to determine which costing key should be used.

As with the predefined assignment tables for products and material types, these user-defined tables let you assign costing keys separately for each point of valuation, record type and plan version. In addition to these source fields, which are automatically contained in each assignment table, you can specify up to three characteristics in your operating concern as source fields for determining the costing key. Thus you can assign costing keys not only to certain products or materials types, but to any combination of values of any characteristics. For example, you could define an assignment table to assign costing keys to specific combinations of company code, plant and product group.

When creating your own assignment tables, observe the following:

1. You can also choose from other source fields in addition to the characteristics in your operating concern. For details, see the F1 field help in the transaction for creating assignment tables.
2. By specifying multiple costing keys as
target fields , you can valuate your data using up to six cost estimates in parallel.
3. In addition, you can specify a special
valuation plant that should be used to access the cost estimate from product costing. This means that the plant found in the CO-PA line item does not always need to be the plant used for costing purposes.
4. You can specify a special control flag as a target field in an assignment table to avoid receiving an error message during valuation whenever the system cannot find a cost estimate from product costing. Note that by default, the system always displays an error message when this occurs.
5. In the can select the "Display error message" flag to specify that the system should automatically display an error message if no valid assignment rule entry is found in this table when the system tries to find the costing key.
6. You may want to avoid a material already successfully valuated using product costing from being valuated again with a price found using a costing sheet. If so, you can define an assignment rule with a target field " VALUE_FLD1" to ensure that the value field assigned to the condition type is cleared before the CO-PA line item is updated.

Example

You want to access cost estimates from product costing by company code and material type. You want to valuate using four costing keys, while explicitly specifying the plant that the system should use for finding the cost estimate. In addition, you want to be able to define whether an error message should be displayed if no cost estimate is found. All assignment rule entries should be valid for a specific period of time.

Call up the function:

"Flexible Assignment of Costing Keys: Change Strategy"

Choose Edit --> Create step to reach the screen

"Flexible Assignment of Costing Keys: Change Rule".

On this screen, enter a name for the assignment rule. Then add the fields "Company code" (CO-PA-BUKRS ) and "Material type" 'GLOBAL-MTART') to the existing fixed source fields "Point of valuation" ( GLOBAL-BWFKT), "Record type" (GLOBAL-VRGAR), and "Plan version" GLOBAL-VERSI).

For the target fields, you can specify, in addition to the "First costing key (CO-PA)" field ( GLOBAL-KALAW1) the fields GLOBAL-KALAW2, GLOBAL-KALAW3 and GLOBAL-KALAW4, plus the "Valuation plant" ( GLOBAL-WERKS) and "Error handling" ( GLOBAL-XMES_FLG ) fields. Select the

"Entries should be maintained for specific dates"

indicator, and then save.

Once you have saved, you can maintain the assignment entries by choosing "Maintain rule entries ". Or you can leave the "Change Rules" screen and maintain the entries later from the "Display Strategy" screen.

Activities

First define the assignment tables you require. If you define more than one assignment table, note that the system processes these in the order in which you enter them, from top to bottom. Once you have defined the necessary tables, you can maintain assignment rule entries for each assignment table.

Further notes

Before you can valuate using a

cost estimate for a material from Product Cost Planning, the valuation strategy you are using for a given point of valuation must be defined to allow this.

If you are valuating your data using more than one costing key, note that the system only fills value fields that are blank. Consequently, each value field can only be filled once, and existing values are never overwritten.

The system proceeds as follows to read the cost estimate:

1. First, it checks whether one or more costing keys have been assigned explicitly to the product being valuated. If this is the case, the system uses these explicitly assigned costing keys for the valuation.
2. If no costing key has been assigned to the product, the system checks whether the any costing keys have been assigned to the material class to which the product belongs. If this is the case, it reads these costing keys only to valuate the line item.
3. If no costing keys have been assigned to the product or the material class, the system tries to find a costing key assigned to a combination of other characteristics. If no costing key is found here either, the system cannot valuate the product using a cost estimate.
Likewise, no valuation can take place if an entry exists in the corresponding assignment tables for the product or material class but no costing key has been assigned.