Results for “as_issue_group_issues_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AS_ISSUE_GROUP_ISSUES_V is a seeded Oracle E-Business Suite view owned by the APPS schema and classified under the AS – Sales Foundation product. It exposes the complete set of financial issues (instruments) that are members of one or more issue groups. The view flattens the many-to-many relationship between issue groups and issues, joining group-level metadata to issue-level attributes and mapping-level transactional attributes such as target price, holding, net change, and last interest date. Because both the group and the issue descriptive columns are resolved through their respective translation tables using the session language, the view is suitable for direct end-user reporting without additional language joins. In EBS reporting and integration scenarios, it serves as the canonical source for answering questions such as which issues belong to a given group, what the current holding and target price are for each member, and how an issue is characterized by its ISSUE_TYPE.

Underlying Base Objects

The view is defined over five documented base objects, referenced through APPS synonyms:

• AS_ISSUE_GROUPS_B — the issue group base table (ISSUE_GROUP_ID, ISSUE_GROUP_TYPE_CODE).
• AS_ISSUE_GROUPS_TL — the translated group name (NAME), joined on LANGUAGE = USERENV('LANG').
• AS_GROUP_ISSUE_MAP — the association table linking groups to issues and carrying mapping-level attributes.
• AS_ISSUES_B — the issue base table (ISSUE_ID, ISSUE_TYPE, SECTOR, PARTY_ID).
• AS_ISSUES_TL — the translated issue name (NAME), also joined on the session language.

The join sequence is driven by ISSUE_GROUP_ID across the group base, group translation, and mapping tables, and by ISSUE_ID across the issue base, issue translation, and mapping tables. The result is one row per issue-per-group combination.

Key Columns

• ISSUE_GROUP_ID / ISSUE_GROUP_NAME / ISSUE_GROUP_TYPE_CODE — group identity, translated name, and classification.
• ISSUE_ID / ISSUE_NAME / ISSUE_TYPE — issue identity, translated name, and the search term of interest, ISSUE_TYPE, which classifies the instrument (for example, bond, equity, or money-market type).
• SECTOR / ISSUER_PARTY_ID — sector classification and the party identifier of the issuer.
• TARGET_PRICE, HOLDING, NET_CHANGE, BUY_SEL_INDICATOR, CURRENCY_CODE, LAST_INTEREST_DATE — mapping-level attributes describing position, target and currency of the group-to-issue assignment.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns inherited from the mapping record.

Common Use Cases and Queries

Typical uses include group composition reporting, issue-type analysis across groups, and feeds into downstream portfolio or settlement processes. The following query lists all issues of a given type within a group:

• SELECT ig.issue_group_name, ig.issue_id, ig.issue_name, ig.issue_type, ig.sector, ig.target_price, ig.holding FROM apps.as_issue_group_issues_v ig WHERE ig.issue_type = 'BOND' AND ig.issue_group_id = :p_group_id ORDER BY ig.issue_name;

To review holdings and net change for a group in a specific currency:

• SELECT ig.issue_name, ig.currency_code, ig.holding, ig.net_change, ig.last_interest_date FROM apps.as_issue_group_issues_v ig WHERE ig.issue_group_name = :p_group_name AND ig.currency_code = :p_currency;

Because translations are resolved inside the view, these queries require no additional _TL joins and return names in the session language. Note that the view does not expose a BUY_SELL_INDICATOR column; the underlying mapping attribute is projected under the documented alias BUY_SEL_INDICATOR, so queries should reference that exact column name.