SAP ABAP Data Element CHIP_NAME_PROVIDER (CHIP: Provider-Specific CHIP Name)
Hierarchy
☛
SAP_UI (Software Component) User Interface Technology
⤷
BC-WD-ABA-PB (Application Component) WD ABAP Page Builder
⤷
SWDP_CCP_API (Package) Web Dynpro ABAP: CCP Integration API
⤷
⤷
Basic Data
| Data Element | CHIP_NAME_PROVIDER |
| Short Description | CHIP: Provider-Specific CHIP Name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHIP_NAME | |
| Data Type | SSTR | Short Character String of Variable Length |
| Length | 300 | |
| Decimal Places | 0 | |
| Output Length | 0 | |
| 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 | 4 | Name |
| Medium | 9 | CHIP Name |
| Long | 31 | Provider-speific CHIP Name |
| Heading | 37 | CHIP: Provider-Specific CHIP Name |
Documentation
Definition
A CHIP provider, for instance, BCV (Business Context Viewer) or Web Dynpro ABAP, provides a set of CHIPs. The provider-specific CHIP name points uniquely to one CHIP within this set.
CHIPs are accessed on a cross-provider basis by setting a provider-specific prefix in front of the CHIP name (for example, x-sap-bcv-chip).
Use
Dependencies
Example
If a CHIP was created in Web Dynpro ABAP uniquely as a configuration MYCHIP_1 of Web Dynpro component WD_CHIP_DESCRIPTION the provider-specific CHIP name is MYCHIP_1.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 720 |