Results for “sales_methodology_name”

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

Overview

The AS_SALES_METHODOLOGY_TL table resides in the OSM schema and belongs to the AS – Sales Foundation product family within Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2. It is the multi-language (MLS) translation companion to the base table AS_SALES_METHODOLOGY_B, storing language-specific descriptive text for each sales methodology record. Every row in the TL table is anchored to a corresponding row in the base table by the shared SALES_METHODOLOGY_ID, qualified by a LANGUAGE code, so a single sales methodology can carry one translated name and description per installed language.

From a Data Vault modeling perspective, the metadata presents a satellite-leaning classification. This is a heuristic suggestion, not an enforced schema claim: the table hangs off AS_SALES_METHODOLOGY_B as a descriptive, context-dependent child rather than an independent business hub, and its composite key of (LANGUAGE, SALES_METHODOLOGY_ID) makes it a natural candidate for a satellite keyed to the parent hub. Because it also carries an editioning column (ZD_EDITION_NAME) and audit columns, it functions as a mutable attribute holder for translated content.

Key Information Stored

Relating to the user's search term as_sales_methodology_tl_pk, the primary key of this table is a composite defined formally as AS_SALES_METHODOLOGY_TL_PK (LANGUAGE, SALES_METHODOLOGY_ID). This is the surrogate/uniqueness key guaranteeing one translation row per language per methodology. The most important columns documented are:

• SALES_METHODOLOGY_ID — the foreign key to AS_SALES_METHODOLOGY_B; the parent identifier that groups all language rows for a single methodology.
• LANGUAGE — the ISO/NLS language code identifying which translation this row carries; part of the primary key.
• SOURCE_LANG — the original source language of the record, used by MLS utilities when determining translations.
• SALES_METHODOLOGY_NAME — the translated, user-facing name of the sales methodology.
• DESCRIPTION — the longer translated text describing the methodology.
• ZD_EDITION_NAME — the editioning column supporting EBS online patching (Edition-Based Redefinition); it appears in the business-key candidate index AS_SALES_METHODOLOGY_TL_U1 (SALES_METHODOLOGY_ID, LANGUAGE, ZD_EDITION_NAME).
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group data segregation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO audit columns recording insert and update provenance.

The distinction is important: AS_SALES_METHODOLOGY_TL_PK is the database primary key (uniqueness for the translation row), while AS_SALES_METHODOLOGY_TL_U1 is the documented unique index acting as a business-key candidate, extended by the editioning column.

Common Use Cases and Queries

The table is primarily consumed for language-specific reporting and for displaying methodology names in the user's session language. A typical query joins the base table to its translation, filtering on the session language:

• Resolve a translated name: SELECT b.sales_methodology_id, tl.sales_methodology_name FROM as_sales_methodology_b b, as_sales_methodology_tl tl WHERE b.sales_methodology_id = tl.sales_methodology_id AND tl.language = USERENV('LANG');
• List all translations: select rows from the TL table for a given SALES_METHODOLOGY_ID to audit which languages are populated.
• Security-group scoping: add WHERE tl.security_group_id = :org_id to restrict results to the caller's security group.
• MLS maintenance: use the SOURCE_LANG column to identify untranslated or fallback rows.

Related Objects

• AS_SALES_METHODOLOGY_B — the base (non-translated) table; joined on SALES_METHODOLOGY_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data segregation.
• FND_LANGUAGES — sources the LANGUAGE values used in the composite key.
• AS_SALES_METHODOLOGY_TL_PK / _U1 — the primary key constraint and unique index enforcing row identity.
• MLS views — Oracle EBS commonly exposes a _VL view that union-selects the base plus TL rows using session language for simplified querying.

Because the object is proprietary Oracle ETRM documentation, customizations should avoid altering the composite primary key or the editioning column, as both participate in the core MLS and online-patching mechanisms.