
The prerequisite for creating a multilevel material cost estimate without quantity structure is a material master with costing view.

Multilevel unit costing is a highly flexible function that allows the hierarchical structure editing of multiple materials. Single-level unit costing only supports the editing of a single material.
Multilevel unit costing can be used in the following scenarios:
- Scenario 1: New product
- You want to create new material masters or cost estimates for new materials. As a rule, you create the structure from top to bottom by making further refinements.
- Scenario 2: Similar product
- You want to cost a new product that is similar to an existing one. You can copy the subordinate costing structure to the new product and make changes to the new (copied) structure.
- Scenario 3: Product changes
- You want to make changes to an existing product. Copy the existing costing structure and make changes to the copy.
Multilevel Material Cost Estimate Without Quantity Structure

The prerequisite for creating a multilevel material cost estimate without quantity structure is a material master with costing view.
To create a multilevel material cost estimate, choose a costing variant.
When a costing variant is selected, the valuation strategy for costing items is established. For material costing, the costing variant is maintained in customizing. You have to enter the costing lot size to use it as a base.
A cost estimate header is created automatically.
When you insert (through drag and drop) an existing cost estimate from the worklist, you specify if you want to insert the original cost estimate or make a copy. If you choose to copy, any subsequent changes to the copied structure do not affect the original cost estimate.
Enter the missing quantity in the List screen of the unit cost estimate.
If you are going to edit anything from the copied cost estimate, you re-evaluate the whole structure as any change makes it mandatory to create a new cost estimate.
After saving, the system updates the cost estimate in the database.









