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 | PA2PCTARGETFIELD |
| Short Description | Target field for assignment rule / table callup / enhancemnt |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FDNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | DD03L |
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 | Target Fld |
| Medium | 15 | Target Field |
| Long | 20 | Target Field |
| Heading | 30 | Target Field |
Documentation
Definition
You can use the following fields as target fields in an assignment rule:
An assignment rule can have up to six target fields. Thus, using an assignment rule with all six costing keys KALAW1, KALAW2, ..., KALAW6 as target fields, you can assign up to six costing keys at the same time.
If you use an assignment rule to determine the valuation plant (field GLOBAL-WERKS) or error handling rule (field GLOBAL-XMES_FLAG), this reduces the number of KALAW(1-6) fields you can include in that assignment rule accordingly.
With table lookups, you can only use target fields of the type USERTEMP (work fields) and Plant used for reading cost estimates (valuation plant).
With enhancements, you can also supply the field Valuation type ( the field GLOABL-BWTAR).
To maintain the field attributes of the target fields, choose the "==>..." pushbutton.
History
| Last changed by/on | SAP | 19990520 |
| SAP Release Created in |
