Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KE (Package) Profitability Analysis
Basic Data
| Data Element | KEDR_VALUE_FIELD_1 |
| Short Description | CO-PA: value field that is reset |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KEDR_CHAR_10 | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Val. field |
| Medium | 15 | Value field |
| Long | 20 | Value field |
| Heading | 8 | Val. fld |
Documentation
Definition
In the field "VALUE_FLD1", you can enter a CO-PA value field.
When the system finds a product cost estimate in Product Cost Planning, the system resets this value field to "0".
The value field is not reset until after all valuation steps in the relevant valuation strategy have been carried out.
Example
Your CO-PA valuation strategy calls for valuation using product costing. For materials that do not have a product cost estimate, you want the system to read the standard price from the material master record. You define a costing sheet in CO-PA that contains a condition type that does this.
If you want to prevent the system from using the price found with this costing sheet for materials that already have been valuated using a product cost estimate, you can create an assignment table with the target field "VALUE_FLD1" to ensure that the value field assigned to the condition type is reset before the line item is updated in CO-PA.
History
| Last changed by/on | SAP | 19971028 |
| SAP Release Created in |
