Search Results as_funds_tl




Overview
Explore in AI Chat

Overview

AS_FUNDS_TL is the multilingual support (MLS) translation table for the Funds entity within the AS – Sales Foundation product family in Oracle E-Business Suite, owned by the OSM schema. In Oracle EBS, a base (_B) or primary table stores language-independent attributes, while its corresponding _TL table stores the language-dependent, translatable columns keyed by language. AS_FUNDS_TL therefore holds the translated descriptive text — principally the fund name — for each Funds record, allowing the same fund to present different display values across the installed languages of the application.

From a heuristic Data Vault modeling perspective (as mined from the documented foreign key structure), AS_FUNDS_TL is classified as standalone. This means it does not itself behave as a hub or link; it is best modeled as a satellite-like structure that carries descriptive, language-qualified attributes attached to the parent Funds business key. This classification is a modeling suggestion only and should be validated against the actual integration and reporting requirements.

Key Information Stored

The table is documented with ten columns in ETRM 12.2.2. The most significant of these are:

  • FUND_ID — the identifier of the parent Funds record. Together with LANGUAGE it forms the composite primary key and the unique business-key candidate.
  • LANGUAGE — the NLS language code identifying which translation row applies. This is the second component of the composite key.
  • NAME — the translated display name of the fund in the given language; this is the primary translatable attribute carried by the _TL table.
  • SOURCE_LANG — the language from which the translation was derived, used to track translation provenance and to support the MLS fallback mechanism.
  • SECURITY_GROUP_ID — the security grouping used for multi-org/row-level access control; documented as a foreign key to FND_SECURITY_GROUPS.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO audit columns recording record creation and modification metadata.

The surrogate primary key is AS_FUNDS_TL_PK, defined on (FUND_ID, LANGUAGE). A unique index, AS_FUNDS_TL_U1, is documented on the same (FUND_ID, LANGUAGE) pair, confirming that combination as the business-key candidate and enforcing uniqueness of one translation row per fund per language.

Common Use Cases and Queries

Typical reporting and integration scenarios join AS_FUNDS_TL back to the base Funds table to resolve the correct translated name for the session or target language. A representative query pattern filters on the language code and pulls the name for a set of funds:

  • Resolving translated fund names for a specific language: SELECT FUND_ID, NAME FROM AS_FUNDS_TL WHERE LANGUAGE = :p_lang AND FUND_ID IN (...).
  • Auditing translation coverage: identifying funds that lack a row for a given language to detect missing translations.
  • Reporting on translation provenance using SOURCE_LANG, and enforcing security visibility via SECURITY_GROUP_ID.
  • Tracking changes over time through the LAST_UPDATE_DATE and LAST_UPDATED_BY audit columns.

Related Objects

AS_FUNDS_TL relates to the following significant objects, based on the documented relationship data:

  • AS_FUNDS (parent/base table) — joined on FUND_ID to obtain language-independent fund attributes.
  • FND_SECURITY_GROUPS — referenced via the SECURITY_GROUP_ID foreign key for access control.
  • AS_FUNDS_TL_U1 — the documented unique index enforcing business-key uniqueness.
  • AS_FUNDS_TL_PK — the primary key constraint on (FUND_ID, LANGUAGE).

Collectively these relationships establish AS_FUNDS_TL as the language-dependent companion to the core Funds entity, central to any multilingual reporting on sales foundation funds data.