Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
SD-SLS (Application Component) Sales⤷
ERP_SLS_LO_GAF_EWB (Package) GAF Enhancement WB for the LO OIF application
Basic Data
| Data Element | TDV_EWB_FIELD_ID |
| Short Description | Field Identifier |
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 | Field ID |
| Medium | 15 | Field ID |
| Long | 20 | Field Identifier |
| Heading | 30 | Field Identifier |
Documentation
Definition
The field identifier is the unique field name with which this enhancing field is being adressed within the LO API. It is used as key in the LO API property table, in the LO API append structures and within the field catalogue of the FPM UI configuratior.
When creating the field properties for a backend field, the enhancement workbench proposes a 'next new field ID' ZZSAP_xyz as default field ID where xyz represents a running number internally determined.
The field ID can be changed before saving the field properties for the very first time. As this field ID deals as key in several DDIC objects, it hence cannot be renamed once the according field properties have been saved.
Each field ID points to exactly one backend field (origin is shown via source table and source field).
Use
An object type supports several origin tables as input sources for the LO Enhancement Workbench. From these tables, the set of available enhancing fields is determined. Bearing in mind we deal with several source tables, field names across tables might be identical. Thus, the concerning field names cannot automatically deal as identification for the LO API enhancement. Instead, the field identifier uniquely addresses the backend field within the LO API.
Dependencies
Example
Object type HEAD supports the source tables VBAK, VBUK and VBKD. Given there exist the following source fields that potentially can enhance the LO API:
- ZZVALUE01 in table VBAK, proposed field ID ZZSAP_0000000001
- ...
- ZZVALUE01 in table VBUK, proposed field ID ZZSAP_0000000005
- ZZVALUE01 in table VBKD, proposed field ID ZZSAP_0000000006
The combination of source table and source field shows the complete origin key of the enhancing field.
As the source field in general is not necessarily be unique (in fact, in our example ZZVALUE01 is not unique), the field ID deals as unique field name within the LO API.
As long as the field properties have not yet been saved, the field ID can be renamed to another allowed identifier.
In the example above, the field properties for the backend fields VBAK-ZZVALUE01 and VBUK-ZZVALUE01 have already been saved and their field ID's ZZSAP_0000000001 and ZZSAP_0000000005 can hence no longer be changed.
The field properties for backend field VBKD-ZZVALUE01 are about to be created and not yet saved. Here, the field ID still can be changed, e.g.towards YYVBUK_ZZVALUE01.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 605 |
