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 | COPALFNR |
| Short Description | Sequence in costing sheet for CO-PA valuation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM2 | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | Seq. no. |
| Medium | 15 | Sequence |
| Long | 20 | Sequence |
| Heading | 2 | Sq |
Documentation
Definition
Each individual valuation step in a CO-PA valuation strategy is assigned a number. This number determines the order in which the valuation steps are processed.
Once a value field has been supplied with a value in one valuation step, the system can use that value to calculate values for other fields in later valuation steps.
Once a value field has been supplied with a value in one valuation step, this value cannot be overwritten in a later valuation step. The only exceptions to this are steps which use a CO-PA user exit to fill a value field.
When you set up the transfer of condition types from Sales and Distribution (SD) to CO-PA, note that if you assign several condition types to one value field, the system adds the values of these condition types. This also holds true when the condition types come from different pricing procedures.
History
| Last changed by/on | SAP | 19971028 |
| SAP Release Created in |
