STATEMENT_HASH in TMO_HPT_RECORDS
Statement Hash
STATEMENT_HASH is a field in SAP table TMO_HPT_RECORDS (TMO-HPT: Records). It represents "Statement Hash". Data element: TMO_HPT_V_STATEMENT_HASH. Available in 3 CDS view(s) as StatementHash.
Business Meaning
| Data Element | TMO_HPT_V_STATEMENT_HASH |
|---|---|
| Key Field | No |
CDS Views & Technical Names (3)
TMO_HPT_RECORDS.STATEMENT_HASH is exposed in CDS views under the following technical name. Views reading the table directly are listed first; "via" marks views that pass the field on through intermediate views.
StatementHash
(3 views)
| View | Access | VDM | Release | Description |
|---|---|---|---|---|
| TMO_HPT_I_RECORDS_R | direct | TMO-HPT: Records | ||
| TMO_HPT_C_RECORDS_R | via 2 level | TMO-SQL: HANA Plan Trace Records | ||
| TMO_SQL_C_RECORDS_R | via 2 level | TMO-SQL: HANA Plan Trace Records |
Other Tables with Field STATEMENT_HASH (3)
| Table | Data Element | Key | Description |
|---|---|---|---|
| KSR_TA_SQL_STMT | KSR_CR_V_STATEMENT_HASH | KEY | KSR: Tenant SQL Statements (basic metrics) |
| KSR_XM_SQL_STMT | KSR_CR_V_STATEMENT_HASH | KEY | KSR: SQL Statements |
| TMO_HTS_M_STS | KSR_CR_V_STATEMENT_HASH | TMO_HTS: Replic.+Enriched Data from M_SERVICE_THREAD_SAMPLES |
Learn More
- Understanding Data Lineage in SAP S/4HANA
- SAP Tables vs CDS Views — Key Differences
- Understanding the SAP S/4HANA Data Model
- 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
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA