SAP ABAP Data Element MDM_GX_SQL_CONSTRAINT (SQL Constraint)
Hierarchy
☛
PI_BASIS (Software Component) Basis Plug-In
⤷
MDM-CLT (Application Component) Client-System Adapter
⤷
MDM_GX_CORE_RI (Package) MDM Generic Extractor: Release-Independant Core Objects
⤷
⤷
Basic Data
| Data Element | MDM_GX_SQL_CONSTRAINT |
| Short Description | SQL Constraint |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TEXT255 | |
| Data Type | CHAR | Character String |
| Length | 255 | |
| Decimal Places | 0 | |
| Output Length | 255 | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 20 | SQL Constraint |
| Heading | 30 | SQL Constraint |
Documentation
Definition
The SQL constraint or the selection criteria for selecting data from the check table concerned. The definition format is the any normal ABAP where condition confirming to the syntax allowed by ABAP language. Each FIELD_NAME in the where clause or sql constraint must be appended with <TABLE_NAME>~ at the beginning. Example:
( <TABLE_NAME>~<FIELD_NAME> = 'XYZ' AND <TABLE_NAME1>~<FIELD_NAME2> = 'PQR' ) OR <TABLE_NAME1>~<FIELD_NAME3> = 0
History
| Last changed by/on | SAP | 20080415 |
| SAP Release Created in | 2006_1_620 |