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
Basic Data
| Data Element | RFIELD |
| Short Description | Necessary field for master data calculation |
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 | Sup. field |
| Medium | 20 | Superior field |
| Long | 30 | Superior field |
| Heading | 10 | Sup. field |
Documentation
Definition
For validation, it is important to know whether the field to be validated is dependent on other fields. If this is the case, you must specify these superior fields here.
Example: the account is dependent on the company code.
Note
You must always enter the field name of the summary table field (such as RBUKRS) in the superior field.
When validating master data using value tables, the field name of the superior field in the summary table and in the value table must be the same (example: GLT1-BUKRS and SKB1-BUKRS for the validation of GLT1-RACCT using value table SKB1).
If the field does not exist in the value table, the system tries to find a suitable field in the value table using the domain of the summary table field. With this logic, an entry such as GLFUNCT-RBUKRS (defined as SKB1-BUKRS in the value table, the common domain is BUKRS) would be accepted as a valid entry and checked as correct.
If a suitable field in the value table is not found using the domain, an error message appears.
Note for global tables
The RCOMP superior field (global company) respresents an exceptional case with global tables: If the superior field in the value table has the domain BUKRS, the system also accepts this entry. In this case the master data company code is determined from the global company and a master data validation is carried out using this master data company code.
With this logic, an entry such as FILCT-RCOMP (defined as SKB1-BUKRS in the value table) would be accepted as a valid entry and checked as correct.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
