Search Results as_funds_b




Overview
Explore in AI Chat

Overview

AS_FUNDS_B is the base table in the Oracle E-Business Suite Sales Foundation (AS) product that stores fund records. It resides in the OSM schema and is documented as a VALID object in ETRM for Oracle EBS 12.1.1 and 12.2.2. Funds represent pools of capital or financial resources that are associated with issues, issue groups, and the parties that manage or own them. In the Sales Foundation data model, AS_FUNDS_B serves as the anchor table for tracking fund strategy, capital targets, and managed asset positions, and it links those funds to the broader issue and security structures maintained by the AS module.

The ETRM metadata classifies AS_FUNDS_B, using a heuristic Data Vault assessment mined from its foreign key structure, as a standalone object. As a modeling suggestion, this implies the table functions primarily as a hub-like entity: it holds the fund identifier and its descriptive attributes and does not itself act as a junction or link table between two other hubs. Its foreign keys to AS_ISSUES_B, AS_ISSUE_GROUPS_B, and FND_SECURITY_GROUPS establish optional references rather than the multi-parent structure typical of a link table.

Key Information Stored

AS_FUNDS_B contains 30 documented columns in the 12.2.2 physical schema. The surrogate primary key, enforced by the AS_FUNDS_B_PK constraint, is FUND_ID. A unique index, AS_FUNDS_B_U1, also exists on FUND_ID, marking it as the documented business-key candidate for the table.

  • FUND_ID — the primary key and unique business identifier for each fund record.
  • STRATEGY — the investment or business strategy associated with the fund.
  • TARGET_CAP — the target capitalization amount defined for the fund.
  • MANAGEMENT_ASSETS — the assets under management attributed to the fund.
  • PARTY_ID — reference to the party associated with the fund.
  • ISSUE_ID — foreign key to AS_ISSUES_B, tying the fund to a specific issue.
  • ISSUE_GROUP_ID — foreign key to AS_ISSUE_GROUPS_B, tying the fund to an issue group.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, used for access control.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the framework for concurrent update control.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield columns reserved for customer-defined extensions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "Who" columns capturing audit and row-level change history.

Common Use Cases and Queries

AS_FUNDS_B is used when reporting on fund composition, capital targets, and the relationships between funds, issues, and issue groups. A typical query retrieves funds joined to their issue for a given fund identifier driven from an interface or concurrent program.

SELECT f.FUND_ID, f.STRATEGY, f.TARGET_CAP, f.MANAGEMENT_ASSETS, i.ISSUE_ID
FROM OSM.AS_FUNDS_B f
LEFT JOIN OSM.AS_ISSUES_B i ON f.ISSUE_ID = i.ISSUE_ID
WHERE f.FUND_ID = :fund_id;

Other common patterns include aggregating MANAGEMENT_ASSETS and TARGET_CAP by STRATEGY, auditing changes through the LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER columns, and applying the SECURITY_GROUP_ID constraint to enforce row-level access when the module's security model is enabled. Because the table carries the standard ATTRIBUTE columns, extract and interface processes frequently read ATTRIBUTE_CATEGORY along with the corresponding ATTRIBUTE1–15 values.

Related Objects

The most significant related objects are those referenced by the documented foreign keys and the parent that owns the primary key relationship.

  • AS_ISSUES_B — referenced via AS_FUNDS_B.ISSUE_ID; the base table for issues with which funds are associated.
  • AS_ISSUE_GROUPS_B — referenced via AS_FUNDS_B.ISSUE_GROUP_ID; groups funds at the issue-group level.
  • FND_SECURITY_GROUPS — referenced via AS_FUNDS_B.SECURITY_GROUP_ID; the Oracle Application Object Library table that drives row-level security filtering.

Because the ETRM relationship data lists AS_FUNDS_B as standalone with no documented child tables or views in the excerpt, additional dependent objects should be confirmed against the specific 12.1.1 or 12.2.2 instance. The primary-key constraint AS_FUNDS_B_PK and unique index AS_FUNDS_B_U1 on FUND_ID are the authoritative access paths for joins and lookups against this table.