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 | KEDRTMPVAL2 |
| Short Description | 2nd temporary field for determining costing keys |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KEDRVALUE | |
| Data Type | CHAR | Character String |
| Length | 32 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| 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 | Work Field |
| Medium | 20 | 2nd temporary field |
| Long | 23 | 2nd temporary field |
| Heading | 23 | 2nd temporary field |
Documentation
Using temporary fields when determining costing keys
The fields "USERTEMP1" through "USERTEMP6" can be used both as source fields and as target fields when you create assignment tables, table lookups or enhancements for assigning costing keys flexibly to CO-PA characteristics.
- You can use a table lookup or an enhancement to fill the fields "USERTEMP1" through USERTEMP6" with data, and these fields can then be used as source fields for an assignment table.
- The fields "USERTEMP1" through USERTEMP6" let you set up a series of assignment tables to find costing keys as a function of more than three different characteristics of your operating concern.
Example:
You want to assign costing keys to the characteristics "Company code", "Plant", "Material type", and "Division" for point of valuation "01" and record type "F".
To do this, you first need to create an assignment table with the source fields "Company code", "Plant", and "Material type" and the target field "USERTMP1". Then you create a second table with the source fields "Division" and "USERTEMP1" and the desired costing keys as target fields.
In the first table, enter any unique value for the field "USERTMP1" for point of valuation "01", record type "F", and valid combinations of the characteristics "Company code", "Plant", and "Material type". Then enter costing keys in second table for point of valuation "01", record type "F", and valid combinations of "USERTMP1" and "Division".
When the system tries to find the appropriate costing keys, it first looks in the first assignment table to find the appropriate value for "USERTMP1" based on the "Company code", "Plant", and "Material type". Then it uses that value for "USERTMP1" along with the "Division" to find the relevant costing keys.
History
| Last changed by/on | SAP | 19970827 |
| SAP Release Created in |
