What is I_MX_TransactionType in SAP S/4HANA?

I_MX_TransactionType is a basic CDS view in SAP S/4HANA. Mexico Transaction Type It contains 2 fields.

Which tables does I_MX_TransactionType read from?

I_MX_TransactionType reads data from: dd07l.

What VDM layer is I_MX_TransactionType?

I_MX_TransactionType is classified as a Basic (interface) view providing a 1:1 representation of a database table.

I_MX_TransactionType

DDL: I_MX_TRANSACTIONTYPE SQL: IMXTRANSTYPE Type: view BASIC Package: GLO_FIN_IS_VAT_MX

2 Fields 1 Data Sources 1 Associations

Mexico Transaction Type

I_MX_TransactionType (Basic)

Package: Explore, extend and adapt the SAP S/4HANA Cloud Public Edition with built-in and side-by-side extension capabilities.

Business Transaction Type · Country or Region-Specific Functions for Finance

I_MX_TransactionType is a Basic CDS View (Dimension) that provides data about "Mexico Transaction Type" in SAP S/4HANA. It reads from 1 data source (dd07l) and exposes 2 fields with key field BusinessTransactionType. It has 1 association to related views. Part of development package GLO_FIN_IS_VAT_MX.

SAP API Hub

Category	Basic
State	C1
Line of Business	Country or Region-Specific Functions for Finance
Application Component	FI-LOC-FI-MX
Capabilities	Data Source for Data Extraction,Data Source in SQL Select,Data Source for Defining CDS Entities,Association Target for Defining CDS Entities
Extensible (Key User)	No
Extensible (Developer)	No
Release State (Key User)	Released
Release State (Developer)	Released
Package	Country/Region-Specific Functions for Finance for SAP S/4HANA Cloud Public Edition

Documentation

Analytics with CDS Views — Build Analytics for S/4HANA Cloud Public Edition ABAP CDS views replicated to SAP Cloud Platform
CDS Views on SAP Business Accelerator Hub — Explore SAP S/4HANA Cloud Public Edition CDS Views on SAP Business Accelerator Hub
Create CDS View as API — Create CDS views in SAP S/4HANA Cloud Public Edition and consume them as APIs
Custom CDS Views — Access data using a Custom Core Data Service view (Custom CDS view)
Custom Communication Scenarios — Create custom communication scenarios to configure custom communication arrangement
Key User Extensibility Tools — The Key User Extensibility Tools of S/4HANA
SAP S/4HANA Extensibility — SAP S/4HANA Extensibility Tutorial
VDM View Types — The Virtual Data Model in SAP S/4HANA Cloud Public Edition
View Browser — Search, browse and tag CDS Views

Data Sources (1)

Source	Alias	Join Type
dd07l	dd07l	from

Associations (1)

Cardinality	Target	Alias	Condition
[0..*]	I_MX_TransactionTypeText	_Text	`$projection.BusinessTransactionType = _Text.BusinessTransactionType`

Annotations (15)

Name	Value	Level
AbapCatalog.sqlViewName	IMXTRANSTYPE	view
EndUserText.label	Mexico Transaction Type	view
VDM.viewType	#BASIC	view
AbapCatalog.compiler.compareFilter	true	view
AbapCatalog.preserveKey	true	view
ClientHandling.algorithm	#SESSION_VARIABLE	view
Analytics.dataCategory	#DIMENSION	view
Analytics.dataExtraction.enabled	true	view
AccessControl.authorizationCheck	#NOT_REQUIRED	view
Metadata.ignorePropagatedAnnotations	true	view
ObjectModel.representativeKey	BusinessTransactionType	view
ObjectModel.usageType.serviceQuality	#A	view
ObjectModel.usageType.sizeCategory	#S	view
ObjectModel.usageType.dataClass	#CUSTOMIZING	view
ObjectModel.sapObjectNodeType.name	BusinessTransactionType	view

Fields (2)

Key	Field	Source Table	Source Field	Description
KEY	BusinessTransactionType			Transaction Type
	_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_MX_TransactionType.
-- 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: IMXTRANSTYPE

CREATE VIEW I_MX_TransactionType AS
SELECT
  cast(domvalue_l as transaction_type) AS BusinessTransactionType
FROM dd07l
LEFT OUTER JOIN I_MX_TransactionTypeText AS _Text ON BusinessTransactionType = _Text.BusinessTransactionType  -- association [0..*]
;

Depth:

I_MX_TransactionType view

dd07l