Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VA (Package) Application development R/3 Sales
Basic Data
| Data Element | MNTKAL |
| Short Description | Generate Sales Order Cost Estimate |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | MNTKAL | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Ord.cost. |
| Medium | 15 | Order costing |
| Long | 22 | Sales order costing |
| Heading | 2 | PC |
Documentation
Definition
This indicator controls whether
- the preliminary costing for the manufacturing order should be used for assembly processing
- a sales order cost estimate can be created
Use
This indicator is only relevant if you are using assembly type 2 ("production order, network or service (stat. processing)").
- If you don't set this indicator ("Copy preliminary cost estimate from production order"), the system copies the planned costs, which are calculated using the preliminary cost estimate for the production order, to the SD conditions. You are then unable to create a sales order costing for the sales document item.
- If you do set this indicator ("Do not copy cost estimate from production order"), you can create a sales order costing for the sales document item, which is then copied to the conditions. The planned costs, created using the preliminary cost estimate for the production order, are not copied into the SD conditions.
Dependencies
The following examples explain where it is appropriate to create a sales order costing for assembly type 2:
- A cost component split has ben stored for sales order costing using the product costing method but it is not available for the preliminary costing estimate of a production order (because the system only creates a cost component split dynamically for the production order display).
Copying the cost component split based on sales order costing to Profitability Analysis (CO-PA) is useful if you are working with a valuated sales order stock and the standard price is based on the sales order costing (also see without valuation strategy).
You can control the transfer of a component cost split based on a sales order costing in Customizing for Profitability Analysis (Controlling) in the Define Keys for Accessing Material Cost Estimate IMG activity.
- When you use the nonvaluated sales order stock, the preliminary cost estimate does not deliver the complete planned costs to the assembly order. To receive the complete planned costs, it makes sense to calculate the sales order costing and transfer this to the SD conditions.
When you use assembly types 1, 3 and 4 you can always create a sales order costing.
You can find more detailed information about valuated and nonvaluated sales order stocks in the Sales Order Controlling documentation.
History
| Last changed by/on | SAP | 20000120 |
| SAP Release Created in |
