I_TranspIATALocationCode
Obsolete Transp IATA Location Codes
I_TranspIATALocationCode is a Basic CDS View that provides data about "Obsolete Transp IATA Location Codes" in SAP S/4HANA. It reads from 1 data source (/scmtms/c_iatac) and exposes 8 fields with key field LocationIATACode. It has 1 association to related views.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| /scmtms/c_iatac | /scmtms/c_iatac | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | I_TranspIATALocationCodeText | _Text | $projection.LocationIATACode = _Text.LocationIATACode |
Annotations (15)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | IIATALOCC | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| AccessControl.personalData.blocking | #NOT_REQUIRED | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.dataClass | #MASTER | view | |
| ObjectModel.representativeKey | LocationIATACode | view | |
| VDM.viewType | #BASIC | view | |
| VDM.lifecycle.contract.type | #NONE | view | |
| EndUserText.label | Obsolete Transp IATA Location Codes | view | |
| VDM.lifecycle.status | #DEPRECATED | view | |
| VDM.lifecycle.successor | I_TranspIATALocationCode_2 | view |
Fields (8)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | LocationIATACode | iatac | IATA: Location | |
| Country | country | Venue: Ctry/Reg | ||
| Region | region | Venue Region | ||
| OrganizationalUnitExternalID | exec_org_id | Plan. Exec. Org. | ||
| Longitude | xpos | Longitude | ||
| Latitude | ypos | Latitude | ||
| LocationTimeZone | tzone | Time Zone Difference | ||
| _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_TranspIATALocationCode.
-- 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: IIATALOCC
CREATE VIEW I_TranspIATALocationCode AS
SELECT
iatac AS LocationIATACode,
Country,
Region,
exec_org_id AS OrganizationalUnitExternalID,
xpos AS Longitude,
ypos AS Latitude,
tzone AS LocationTimeZone
FROM /scmtms/c_iatac
LEFT OUTER JOIN I_TranspIATALocationCodeText AS _Text ON LocationIATACode = _Text.LocationIATACode -- association [0..*]
;Learn More
- S/4HANA CDS View Deprecation: What You Need to Know
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- 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
- 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