Hierarchy
⤷ BC-CFG-RT (Application Component) Business Configuration Tools: Runtime
⤷ SC2_IDE (Package) C2 Development Environment
Basic Data
Data Element | SC2_BCO_PROPVALUE_FLD_IS_TERM |
Short Description | Flag: Field Contains Term |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | 5 | Term |
Medium | 10 | Term |
Long | 15 | Contains Term |
Heading | 40 | Field Contains Term |
Documentation
Definition
Attribute which states whether a field contains a term.
Use
Terms show complex configuration relationships simply.
If a configuration object has 10 attributes, but only 3 combinations of their values are delivered in a solution, these 10 attributes can be replaced in the target object by a new configuration object with one attribute for the 3 source object value combinations.
The attribute in the source object is a term. If the term is changed in the source object, a previously-prepared value profile which is linked to the term field, can get the values for the target object, in the background exit method.
The possible values of the term must be in the configuration object SC2_PROFILE_DEFINITION, where you can assign it to... Otherwise, the data must be provided in the "Term Change" exit by implementing the interface IFC2SEXIT_TERM_CHANGE.
Dependencies
Not every field can be a term field:
- Key fields and text fields cannot be flagged as terms
- Term fields must have a data element in the generated proxy structure. If the type is specified directly, not as a data element, in the data structure, the field cannot be flagged as a term.
- Time-dependent configuration object nodes cannot contain terms
The source and target object nodes must be associated
Example
A hi-fi has an equalizer, in which you can assign amplitudes to frequency ranges, instead of selecting frequency profiles for musical styles, such as Jazz, Rock, Pop or Classical.
There are the associated example configuration objects SC2TEST_EQUAL ( target object containing amplitudes), and SC2TEST_EQ_MUSIC (source object, SC2TEST_MUSIC_STYLE). They are associated.
If you now put a device in SC2TEST_EQ_MUSIC, and assign a musical style,e.g. "Jazz" to it, it is automatically created in the target object, or if it already exists, the frequency profile is adjusted.
History
Last changed by/on | SAP | 20050204 |
SAP Release Created in | 700 |