Search Results fund_issue_sector

Overview

AS_FUND_DETAILS_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AS – Sales Foundation product family. The view consolidates fund master data, fund issue data, issue group translations, and trading party information into a single flattened result set, allowing reporting and integration layers to retrieve fund-level attributes without repeatedly joining the underlying transactional tables. Because the view resolves multilingual (TL) tables using USERENV('LANG'), it returns descriptions and names in the language of the active session, which makes it suitable for concurrent programs, OAF pages, and BI Publisher reports operating under a defined language context. The view is documented in ETRM 12.2.2 metadata with a status of VALID and the same definition applies to the 12.1.1 code line.

Underlying Base Objects

The view is defined over six base objects, all accessed through APPS synonyms: AS_FUNDS_B, AS_FUNDS_TL, AS_ISSUES_B, AS_ISSUES_TL, AS_ISSUE_GROUPS_TL, and HZ_PARTIES. AS_FUNDS_B supplies the core fund record (FUND_ID, STRATEGY, TARGET_CAP, MANAGEMENT_ASSETS, ISSUE_GROUP_ID, PARTY_ID, ISSUE_ID, and audit columns). AS_FUNDS_TL is joined on FUND_ID and the session language to return FUND_NAME. AS_ISSUES_B provides the fund-linked issue (ISSUE_ID, SECTOR, PARTY_ID, ISSUE_TYPE), while AS_ISSUES_TL supplies the translated issue name. AS_ISSUE_GROUPS_TL provides the issue group name. HZ_PARTIES joins on PARTY_ID to return the managing organization's party name and party type. Notably, the join between AS_FUNDS_B and AS_ISSUES_B is an outer join (IB.ISSUE_ID(+) = FB.ISSUE_ID), meaning funds without an associated fund issue still appear in the result set; however, the subsequent inner join to AS_ISSUES_TL on IB.ISSUE_ID effectively restricts the final result set to funds that do have a matching issue translation row.

Key Columns

• FUND_ID – Primary key of the fund; the standard join key back to AS_FUNDS_B.
• FUND_NAME – Translated fund description from AS_FUNDS_TL.
• STRATEGY, TARGET_CAP, MANAGEMENT_ASSETS – Fund-level investment attributes.
• ISSUE_GROUP_ID / ISSUE_GROUP_NAME – The issue group to which the fund belongs, and its translated name.
• MANAGING_ORG_PARTY_ID / MANAGING_ORG_PARTY_NAME / MANAGING_ORG_PARTY_TYPE – Trading partner details for the managing organization, sourced from HZ_PARTIES.
• FUND_ISSUE_ID – Identifier of the fund issue (aliased from IB.ISSUE_ID); this is the column most commonly referenced when searches are made for the term "fund_issue_id". It links the fund to its associated issue record.
• FUND_ISSUE_NAME, FUND_ISSUE_SECTOR, FUND_ISSUE_TYPE – Descriptive attributes of the linked issue.
• FUND_ISSUER_PARTY_ID – Party identifier of the fund issuer.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – Standard audit columns inherited from AS_FUNDS_B.

Common Use Cases and Queries

The view is typically queried to list funds alongside their issue and managing organization details, to drive LOV queries in fund setup forms, or to feed downstream reporting on fund holdings. A representative query retrieving fund issue information follows:

SELECT fund_id, fund_name, fund_issue_id, fund_issue_name, fund_issue_sector, managing_org_party_name FROM apps.as_fund_details_v WHERE fund_issue_id IS NOT NULL ORDER BY fund_name;

Because the view depends on USERENV('LANG'), callers should ensure the session language (FND_LANGUAGE) is initialized before querying; running under a language with no matching TL rows will suppress results. For performance, filters on FUND_ID or ISSUE_GROUP_ID are preferable, and creating a custom index or materialized view on top of AS_FUNDS_B may help where large volumes of funds exist. The view should be treated as read-only; DML must target the base tables directly.