SAP ABAP Data Element ADFLD (Additional Field)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBAS (Package) FI-SL Customizing / integration / Basis
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
| Data Element | ADFLD |
| Short Description | Additional Field |
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 | AField |
| Medium | 15 | Addit. Field |
| Long | 20 | Additional Field |
| Heading | 10 | Add. Field |
Documentation
Definition
When you use a value field, it might in some cases be necessary to check an additional field.
The name of the field is stored in field T804B-ADFLD, while the value to be checked is stored in field T804B-ADVAL.
Example:
Actual/plan data is distinguished in table GLTI via the key field RRCTY (0=actual, 1=plan). If you now want to define a "Transaction currency/ plan" entry, you must check the field RRCTY against the value 1.
The following entries are then required for the field group "TSL++":
T804B-ADFLD = "RRCTY"
T804B-ADVAL = "1"
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
