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 | PAPCFLAGOVERWRITE |
| Short Description | Read cost estimate: overwrite target value |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KEDRFLAG | |
| 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 | Overwrite |
| Medium | 15 | Overwrite |
| Long | 22 | Overwrite target value |
| Heading | 22 | Overwrite target value |
Documentation
Definition
By maintaining the field attributes of target fields, you can determine how the system should react when determining costing keys if the assignment strategy contains more than one assignment rule for determining the costing key.
In valuation using product cost estimates, the system first determines which costing keys to use, then it uses these to access the costing data.
When determining the costing keys, the syste processes all the assignment rules in the specified. In the standard system, values already stored in the target fields 'KALAW1', 'KALAW2', ..., 'KALAW6' are not overwritten by subsequent assignment rules.
Using this function, you can change or delete the costing keys entered in the fields 'KALAW1', 'KALAW2', ..., 'KALAW6' by the first assignment rule with the value found by a subsequent assignment rule.
Example:
An assignment strategy uses two assignment rules to assign costing keys. Both rules contain the field 'KALAW1' as the only target field. Normally, if the first assignment rule finds a value for the field 'KALAW1', this value is not overwritten or changed by the second assignment rule.
You can only overwrite existing costing keys here if the field 'KALAW1' in the second assignment table has the field attribute "Overwrite target value".
History
| Last changed by/on | SAP | 19970923 |
| SAP Release Created in |
