Results for “as_statuses_tl”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AS_STATUSES_TL is the translated (multi-language support, or MLS) child table of AS_STATUSES_B within the Oracle E-Business Suite Sales Foundation (AS) product. It resides in the OSM schema and is marked VALID in the ETRM 12.2.2 physical schema. The table stores language-specific textual attributes — primarily the displayable MEANING and DESCRIPTION for each sales status code — while the base table AS_STATUSES_B retains language-independent columns such as flags, dates, and identifiers. In Oracle EBS 12.1.1 and 12.2.2, every MLS-enabled lookup or reference entity follows this base-plus-translation pattern, allowing the application to render status names in the user's session language without duplicating non-translatable data.
Under the heuristic Data Vault classification derived from its foreign-key structure, AS_STATUSES_TL is satellite-leaning. A translation table naturally behaves as a descriptive satellite attached to its base entity: it carries no independent business identity of its own, is keyed by the parent business key plus LANGUAGE, and holds descriptive attributes that change when translations are maintained. Modelers building a Data Vault representation from EBS would treat AS_STATUSES_B.STATUS_CODE as the hub business key and AS_STATUSES_TL as a multi-active satellite keyed by STATUS_CODE and LANGUAGE.
Key Information Stored
The table contains 12 documented columns. The most operationally significant are:
- STATUS_CODE — the business identifier of the sales status; also the foreign key to AS_STATUSES_B.STATUS_CODE, making it a component of the unique index AS_STATUSES_TL_U1.
- LANGUAGE — the NLS language code identifying the translation; part of the primary key AS_STATUSES_TL_PK and the unique index AS_STATUSES_TL_U1.
- MEANING — the translated, user-visible name of the status; the primary column retrieved by concurrent programs and forms.
- DESCRIPTION — the translated long description of the status.
- SOURCE_LANG — the language in which the row was originally authored, used by the MLS translation maintenance screens.
- ZD_EDITION_NAME — the editioning column introduced for EBS 12.2 online patching; part of the unique index AS_STATUSES_TL_U1 and used to isolate editions during upgrade.
- SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, controlling which security group (operating unit context) may access the row.
- Standard WHO audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — record row provenance and change history.
The surrogate primary key AS_STATUSES_TL_PK uniquely identifies each translation row, while AS_STATUSES_TL_U1 (STATUS_CODE, LANGUAGE, ZD_EDITION_NAME) acts as the principal business-key candidate, ensuring one translation per status code, language, and edition.
Common Use Cases and Queries
The dominant use case is joining translations to the base table so that status codes are displayed with human-readable names in the caller's language. A typical query filters by LANGUAGE and falls back to the base meaning when no translation exists:
- Reporting on sales status distribution:
SELECT b.status_code, t.meaning, COUNT(*) FROM as_statuses_b b, as_statuses_tl t WHERE b.status_code = t.status_code AND t.language = USERENV('LANG') GROUP BY ... - Validating translation completeness across all installed languages by comparing row counts in AS_STATUSES_TL against the distinct LANGUAGE values in FND_LANGUAGES.
- Extracting localized lookup values into a data warehouse or OBIEE repository, where the MEANING column becomes the conformed status dimension attribute.
- Upgrade and patching auditing during 12.1.1 to 12.2.2 migration, checking ZD_EDITION_NAME values to confirm translations were copied into the run edition.
Because the table is small and read-mostly, queries should always be constrained by LANGUAGE to avoid returning redundant rows.
Related Objects
The following objects are most significant to AS_STATUSES_TL, based on documented primary and foreign key relationships:
- AS_STATUSES_B — the base table; joined on AS_STATUSES_TL.STATUS_CODE = AS_STATUSES_B.STATUS_CODE. This is the mandatory parent.
- FND_SECURITY_GROUPS — referenced via AS_STATUSES_TL.SECURITY_GROUP_ID; governs row-level access by security group.
- FND_LANGUAGES — the reference source for the LANGUAGE column values and the driver for MLS translation coverage checks.
- AS_STATUSES_VL — where defined, the MLS view that joins AS_STATUSES_B and AS_STATUSES_TL and is the preferred access point for forms and reports.
- AS_STATUSES_TL_PK / AS_STATUSES_TL_U1 — the primary key and unique index that enforce translation uniqueness and support join performance.
Together these objects form the complete sales status reference model within the Sales Foundation module.
-
For MLS, Translated columns of AS_STATUSES_B
-
For MLS, Translated columns of AS_STATUSES_B
-
SYNONYM: APPS.AS_STATUSES_TL 12.1.1
-
TABLE: OSM.AS_STATUSES_TL 12.2.2
-
SYNONYM: APPS.AS_STATUSES_TL 12.2.2
-
TABLE: OSM.AS_STATUSES_TL 12.1.1
-
VIEW: OSM.AS_STATUSES_TL# 12.2.2
-
View: AS_STATUSES_VL 12.1.1
MLS view to join as_statuses_b and as_statuses_tl
APPS.AS_STATUSES_VL·↳ AS_STATUSES_B·↳ AS_STATUSES_TL·Explore AS module →
-
View: AS_STATUSES_VL 12.2.2
MLS view to join as_statuses_b and as_statuses_tl
APPS.AS_STATUSES_VL·↳ AS_STATUSES_B·↳ AS_STATUSES_TL·Explore AS module →
-
View: AST_SALES_LEAD_UWQ_V 12.1.1
APPS.AST_SALES_LEAD_UWQ_V·↳ AS_SALES_LEADS·↳ AS_STATUSES_B·↳ AS_STATUSES_TL·Explore AST module →
-
View: AST_SALES_LEAD_UWQ_V 12.2.2
APPS.AST_SALES_LEAD_UWQ_V·↳ AS_SALES_LEADS·↳ AS_STATUSES_B·↳ AS_STATUSES_TL·Explore AST module →
-
View: AS_SALES_LEAD_UWQ_V 12.2.2
This view is used for Universal Work Queue
APPS.AS_SALES_LEAD_UWQ_V·↳ AS_SALES_LEADS·↳ AS_STATUSES_B·↳ AS_STATUSES_TL·Explore AS module →
-
View: AS_SALES_LEAD_UWQ_V 12.1.1
This view is used for Universal Work Queue
APPS.AS_SALES_LEAD_UWQ_V·↳ AS_SALES_LEADS·↳ AS_STATUSES_B·↳ AS_STATUSES_TL·Explore AS module →
-
APPS.AST_LM_OPP_QUICK_CAMP_V·↳ AMS_SOURCE_CODES·↳ AS_LEADS_ALL·↳ AS_SALES_STAGES_ALL_TL·Explore AST module →
-
APPS.AST_LM_OPP_QUICK_RESULTS_V·↳ AS_LEADS_ALL·↳ AS_SALES_STAGES_ALL_TL·↳ AS_STATUSES_TL·Explore AST module →
-
View: BIL_DIMV_OPTY_STATUSES 12.1.1
Opportunity Statuses view
APPS.BIL_DIMV_OPTY_STATUSES·↳ AS_STATUSES_B·↳ AS_STATUSES_TL·↳ FND_GLOBAL·Explore BIL module →
-
APPS.AST_OPPORTUNITIES_BALI_V·↳ AMS_ACT_OFFERS·↳ AMS_SOURCE_CODES·↳ AS_LEADS_ALL·Explore AST module →
-
APPS.AST_LM_OPP_QUICK_SREP_V·↳ AS_ACCESSES_ALL·↳ AS_LEADS_ALL·↳ AS_SALES_STAGES_ALL_TL·Explore AST module →
-
APPS.AST_LM_OPP_QUICK_SGRP_V·↳ AS_ACCESSES_ALL·↳ AS_LEADS_ALL·↳ AS_SALES_STAGES_ALL_TL·Explore AST module →
-
APPS.AST_LM_LEADS_QUICK_CAMPAIGN_V·↳ AMS_ACT_OFFERS·↳ AMS_SOURCE_CODES·↳ AS_LOOKUPS·Explore AST module →
-
APPS.AST_LM_OPP_QUICK_RESULTS_V·↳ AS_LEADS_ALL·↳ AS_SALES_STAGES_ALL_TL·↳ AS_STATUSES_TL·Explore AST module →
-
View: AST_LM_LEADS_QUICK_V 12.1.1
APPS.AST_LM_LEADS_QUICK_V·↳ AMS_ACT_OFFERS·↳ AMS_SOURCE_CODES·↳ AS_LOOKUPS·Explore AST module →
-
View: AST_LM_LEADS_QUICK_V 12.2.2
APPS.AST_LM_LEADS_QUICK_V·↳ AMS_ACT_OFFERS·↳ AMS_SOURCE_CODES·↳ AS_LOOKUPS·Explore AST module →
-
View: AST_SALES_OPP_UWQ_V 12.2.2
APPS.AST_SALES_OPP_UWQ_V·↳ AS_ACCESSES_ALL·↳ AS_FORECAST_PROB_ALL_TL·↳ AS_LEADS_ALL·Explore AST module →
-
APPS.AST_LM_LEADS_QUICK_GROUP_V·↳ AMS_ACT_OFFERS·↳ AMS_SOURCE_CODES·↳ AS_LOOKUPS·Explore AST module →
-
APPS.AST_LM_LEADS_QUICK_INTEREST_V·↳ AMS_ACT_OFFERS·↳ AMS_SOURCE_CODES·↳ AS_LOOKUPS·Explore AST module →
-
APPS.AST_OPPORTUNITIES_BALI_V·↳ AMS_ACT_OFFERS·↳ AMS_SOURCE_CODES·↳ AS_LEADS_ALL·Explore AST module →
-
APPS.AST_LM_LEADS_QUICK_INTEREST_V·↳ AMS_ACT_OFFERS·↳ AMS_SOURCE_CODES·↳ AS_LOOKUPS·Explore AST module →
-
APPS.AST_LM_OPP_QUICK_CAMP_V·↳ AMS_SOURCE_CODES·↳ AS_LEADS_ALL·↳ AS_SALES_STAGES_ALL_TL·Explore AST module →