I_GteeMLegislativeDistrict
Legislative District
I_GteeMLegislativeDistrict is a Basic CDS View that provides data about "Legislative District" in SAP S/4HANA. It reads from 1 data source (gmldc) and exposes 2 fields with key field GranteeMgmtLegislativeDistrict. It has 1 association to related views. It is exposed through 4 OData services (ASQL_F4182, ASQL_F6588, ASQL_F7321, ...). Part of development package PSM_S4C_GM_MD.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| gmldc | gmldc | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | I_GteeMLegislativeDistrictText | _Text | $projection.GranteeMgmtLegislativeDistrict = _Text.GranteeMgmtLegislativeDistrict |
Annotations (12)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Legislative District | view | |
| VDM.viewType | #BASIC | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| ObjectModel.representativeKey | GranteeMgmtLegislativeDistrict | view | |
| ObjectModel.usageType.dataClass | #CUSTOMIZING | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.buffering.status | #ACTIVE | view | |
| AbapCatalog.buffering.type | #FULL | view | |
| AbapCatalog.sqlViewName | IGMLDCODE | view |
OData Services (4)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| ASQL_F4182 | ASQL_F4182 | C2 | NOT_RELEASED | |
| ASQL_F6588 | ASQL_F6588 | C2 | NOT_RELEASED | |
| ASQL_F7321 | ASQL_F7321 | C2 | NOT_RELEASED | |
| ASQL_F7335 | ASQL_F7335 | C2 | NOT_RELEASED |
Fields (2)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | GranteeMgmtLegislativeDistrict | ld_code | LD Code | |
| _Text | _Text |
Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.
-- Derived SQL interpretation of CDS view I_GteeMLegislativeDistrict.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.
-- SQL view name: IGMLDCODE
CREATE VIEW I_GteeMLegislativeDistrict AS
SELECT
ld_code AS GranteeMgmtLegislativeDistrict
FROM gmldc
LEFT OUTER JOIN I_GteeMLegislativeDistrictText AS _Text ON GranteeMgmtLegislativeDistrict = _Text.GranteeMgmtLegislativeDistrict -- association [0..*]
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- OData Services in SAP S/4HANA Explained
- Service Bindings and Service Definitions in SAP S/4HANA
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- CDS View Field Mapping and Associations
- Understanding the SAP S/4HANA Data Model
- CDS View Extensions and Custom Fields in SAP S/4HANA
- Released APIs and Stability Contracts in SAP S/4HANA
- BSEG to ACDOCA: The Universal Journal Migration
- Business Partner Migration: KNA1/LFA1 to BUT000
- Material Document Migration: MSEG/MKPF to MATDOC
- How to Find the Right CDS View for an SAP Table
- BW Extractor to CDS View Migration Guide
- S/4HANA CDS View Deprecation: What You Need to Know
- ABAP CDS View Tutorial — From Basics to Real-World Examples
- RAP and CDS Views — Building Transactional Apps in SAP S/4HANA
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA