Search Results as_issue_listing_idfr




Overview

The AS_ISSUE_LISTING_IDFR table resides in the OSM schema and belongs to the AS – Sales Foundation product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold issue listing identifiers — that is, the external listing references (listing schemes, values, and search codes) associated with securities issues tracked by the ETRM (Enterprise Trading and Risk Management) component of Oracle EBS. Each row ties a specific issue to a specific exchange and captures the identifier value under a given listing scheme, making the table a critical cross-reference between internal issue records and external marketplace identifiers.

The metadata classifies this object heuristically as standalone under a Data Vault modeling lens. In practice, this suggests the table functions as an independent identifier registry rather than a pure hub, link, or satellite. It carries its own surrogate key and business-key uniqueness but references parent entities (issues, exchanges, security groups) without itself being a junction table in the strict Data Vault sense.

Key Information Stored

The table contains 31 documented columns in the 12.2.2 physical schema. The most operationally significant are:

The distinction between the surrogate key (ISSUE_LISTING_IDFR_ID) and the unique business-key index is notable; the unique index is defined on the same column, meaning no separate natural business key is enforced beyond the surrogate.

Common Use Cases and Queries

Typical scenarios include retrieving all listing identifiers for a given issue, resolving an external listing value back to an internal issue, and reporting issues by exchange. Sample patterns:

  • List all identifiers for an issue: SELECT scheme, value, search_code, country_code FROM as_issue_listing_idfr WHERE issue_id = :p_issue_id;
  • Resolve a listing value: SELECT issue_id, exchange_id FROM as_issue_listing_idfr WHERE scheme = :p_scheme AND value = :p_value;
  • Report active listings by exchange: SELECT i.issue_id, l.scheme, l.value FROM as_issue_listing_idfr l, as_issues_b i WHERE l.listing_flag = 'Y' AND l.issue_id = i.issue_id AND l.exchange_id = :p_exchange_id;

Reporting use cases center on security master maintenance, exchange listing reconciliation, and downstream market-data mapping.

Related Objects

  • AS_ISSUES_B — joined on ISSUE_ID; the parent issue definition.
  • AS_EXCHANGES_B — joined on EXCHANGE_ID; the exchange master.
  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; row-level security.
  • AS_ISSUES_TL — translated issue names for reporting joins.
  • AS_ISSUE_LISTING_IDFR_U1 — unique index supporting identifier lookups.

These relationships confirm the table’s role as a linking registry between the security master and exchange reference data within Sales Foundation.