Search Results hz_stock_markets




Overview
Explore in AI Chat

Overview

HZ_STOCK_MARKETS is a reference table owned by the AR (Receivables) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the master list of stock exchanges — the regulated marketplaces where financial instruments such as equities, bonds, and other securities are bought and sold. Within the broader Oracle Trading Community Architecture and the HZ (Trading Community) entity model, this table functions as a static lookup that qualifies the venue on which a security is traded. Each row describes a single stock exchange, identified by a surrogate primary key and contextualized by country and exchange codes.

The table carries a status of VALID in the ETRM repository and is delivered as part of standard Receivables functionality, reflecting its role in supporting customer and counterparty financial profiling rather than transactional postings. A heuristic Data Vault classification suggests this object behaves as a hub-leaning entity: its primary key STOCK_EXCHANGE_ID is a stable, unique business identifier that anchors dependent records, which is characteristic of a hub in a Data Vault model. No link or satellite classification is asserted, so this should be treated as a modeling suggestion rather than a documented fact.

Key Information Stored

The table contains 14 documented columns. The most significant are:

The surrogate STOCK_EXCHANGE_ID is distinct from the descriptive business attributes STOCK_EXCHANGE_CODE and STOCK_EXCHANGE_NAME; only STOCK_EXCHANGE_ID is formally documented as a unique key, while the code and name serve as the practical business identifiers.

Common Use Cases and Queries

The table is primarily consumed as a lookup when populating or validating the stock exchange associated with an issued security. Typical scenarios include rendering a list of values for exchange selection, resolving an exchange ID to its name for reporting, and joining exchange data to securities for financial profiling.

A common retrieval pattern selects the exchange identity and country:

  • SELECT stock_exchange_id, stock_exchange_code, stock_exchange_name, country_of_residence FROM hz_stock_markets ORDER BY stock_exchange_name;
  • To resolve a security to its exchange, join via the foreign key column: SELECT s.security_id, m.stock_exchange_name FROM hz_security_issued s, hz_stock_markets m WHERE s.stock_exchange_id = m.stock_exchange_id;
  • To list exchanges by country: SELECT country_of_residence, COUNT(*) FROM hz_stock_markets GROUP BY country_of_residence;

Because the table is reference data, it is frequently queried directly, cached in list-of-values components, and extracted into reporting warehouses using the WH_UPDATE_DATE watermark.

Related Objects

The most significant dependent object is the security master. The documented foreign-key relationship shows that HZ_SECURITY_ISSUED references HZ_STOCK_MARKETS through the column STOCK_EXCHANGE_ID, meaning each issued security points back to the exchange on which it trades. This is the primary join path and the principal consumer of the table.

Other relevant objects in the same HZ model include the surrounding Trading Community and financial-profile tables (for example, security and customer financial-instrument entities) that either reference exchanges or are referenced alongside them. Because the documented metadata identifies only HZ_SECURITY_ISSUED as an explicit foreign-key dependent, that table should be treated as the authoritative related object, with adjacent HZ security tables understood as part of the same financial-instrument domain.