Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
CK (Package) R/3 Application development: PP Product Costing
Basic Data
| Data Element | CK_RNDKZ |
| Short Description | Rounding Indicator in Cost Estimate with Quantity Structure |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CK_RNDKZ | |
| 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 | Rounding |
| Medium | 19 | Rounding Indicator |
| Long | 20 | Rounding Indicator |
| Heading | 5 | RI |
Documentation
Definition
When costing a material, this specifies whether the required quantity of a BOM component with a unit of measure that can only assume whole number values (such as "piece") is rounded up in cases where the calculation of scrap-adjusted quantities produces a required quantity that is not a whole number.
Use
Procedure
- If you select " ", the required quantity is rounded up to the next whole number. In the example below, this would result in 2 pieces being costed.
- If you select "1", the quantities are not rounded up. In the example below, this would result in 1.1 pieces being costed.
In the itemization of the cost estimate, the quantities that, by definition, do not have decimal places (such as "piece") are only displayed as whole numbers. However, the costs are calculated on the basis of quantities entered with 3 decimal places. You can display the quantities that were not rounded in your own report (user exit).
Examples
- BOM for material A with a base quantity of 100 kg. BOM component material B with a required quantity of 1 piece.
Costing material A with a costing lot size of 120 kg would result in a required quantity of 1.2 pieces. Since the unit of measure "piece" can only assume whole number values, the system rounds up the number of pieces of the required material to 2, and when calculating the costs for 120 kg of material A, costs 2 pieces of material B.
- BOM for material A with a base quantity of 100 kg. BOM component material B with a required quantity of one piece and component scrap of 10%.
The same thing happens if planned scrap (such as component scrap) is included in the cost estimate. Costing material A with a costing lot size of 100 kg means costing 1.1 pieces of material B because of the 10% scrap. The system rounds up the number of pieces required of material B to 2, and then costs 2 pieces.
Dependencies
Rounding differences can occur if you are working with poorly chosen price units, costing lot sizes and/or base units of measure in the BOM or routing. Costing uses normal fields for currency. If the system encounters values with more decimal places than are allowed in these currency fields, it rounds them up or down as appropriate. This can lead to small rounding errors, which you can minimize or eliminate by choosing the correct price unit, costing lot size and base units of measure.
If you set the indicator to "1" (no rounding), this may result in quantity variances between product costing and costing for the production order when the variances are calculated.
History
| Last changed by/on | SAP | 19970910 |
| SAP Release Created in |
