Hierarchy
SAP_UI (Software Component) User Interface Technology⤷
BC-WD-CMP-FPM (Application Component) Floorplan Manager Web Dynpro ABAP⤷
APB_FPM_CORE (Package) Floorplan Manager (Framework)
Basic Data
| Data Element | FPM_SUPPRESS_FIELD_MERGING |
| Short Description | Suppress Field Merging |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WDY_BOOLEAN | |
| 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 | 10 | Merge |
| Medium | 20 | Suppress Merging |
| Long | 35 | Suppress Field Merging |
| Heading | 35 | Suppress Field Merging |
Documentation
Determines whether field merging occurs in Display mode at runtime.
With the Form GL2 component, the FPM framework merges certain form fields together at runtime for appearance purposes. These are known as melting groups.
Typical examples of a melting group include Street and House Number, phone numbers with an area code, and fields displaying a monetary amount along with a currency. In this last example, the field displaying the currency is moved closer to the field displaying a monetary amount. The space between the two fields on the screen at runtime is reduced.
In this way, the system displays the information in a more readable manner to the end-user.
Note that the fields are merged only in Display mode at runtime, and not in Edit mode. Therefore, the arrangement of fields on the form at runtime may look different in each mode.
History
| Last changed by/on | SAP | 20141120 |
| SAP Release Created in | 740 |
