Results for “as_issues_vl”

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

Overview

AS_ISSUES_VL is a Multi-Lingual Support (MLS) compliant view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is documented under the AS – Sales Foundation product family. The view exposes issue records that are stored across a pair of underlying tables: a base table (AS_ISSUES_B) holding the language-independent attributes, and a translation table (AS_ISSUES_TL) holding the language-dependent descriptive text. The "VL" suffix denotes a "View Language" object, which resolves translated columns to the session language at query time rather than persisting translated values in a single physical table. Status is documented as VALID, and the object is classified as a VIEW under the APPS owner. In EBS reporting and integration, AS_ISSUES_VL serves as the query-facing abstraction for issue data, allowing forms, concurrent programs, and external interfaces to read issue details without directly joining the _B and _TL tables or manually applying the language predicate.

Underlying Base Objects

The ETRM metadata states the documented referenced base objects are AS_ISSUES_B and AS_ISSUES_TL, both exposed as SYNONYM objects. The view definition joins the two on the ISSUE_ID column and restricts the translation rows with the condition TL.LANGUAGE = USERENV('LANG'). This is the standard MLS pattern: AS_ISSUES_B stores the functional columns that are identical across all installed languages, while AS_ISSUES_TL stores the NAME and DESCRIPTION columns per language. Because the join filters TL.LANGUAGE to the current session language, a query against AS_ISSUES_VL returns exactly one row per issue identifier, with the translated NAME and DESCRIPTION appropriate to the caller's environment. The USERENV('LANG') call resolves the language of the database session, so behavior can differ depending on client locale settings.

Key Columns

• ISSUE_ID — Primary identifier for the issue; the join key between AS_ISSUES_B and AS_ISSUES_TL.
• NAME and DESCRIPTION — Translated, language-dependent descriptive text sourced from AS_ISSUES_TL.
• ISSUE_TYPE — Classification of the issue; this is the column most directly associated with the search term "issue_type" and is sourced from the base table AS_ISSUES_B.
• SECTOR — Sector designation associated with the issue.
• PARTY_ID — Reference to the party (customer or organization) linked to the issue.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking record creation and change history.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The DFF (Descriptive Flexfield) context and segment columns for extensible issue attributes.
• SECURITY_GROUP_ID — Security grouping identifier used for data partitioning or access control.

Common Use Cases and Queries

The view is the recommended read interface for issue data in reporting and integration because it encapsulates the language join and returns a single logical row. A frequent scenario is filtering issues by type, sector, or party. For example, to retrieve issues of a particular type:

• SELECT ISSUE_ID, NAME, ISSUE_TYPE, SECTOR, PARTY_ID FROM APPS.AS_ISSUES_VL WHERE ISSUE_TYPE = :p_issue_type;
• SELECT ISSUE_ID, NAME, DESCRIPTION FROM APPS.AS_ISSUES_VL WHERE PARTY_ID = :p_party_id ORDER BY CREATION_DATE DESC;
• SELECT ISSUE_ID, ATTRIBUTE_CATEGORY, ATTRIBUTE1 FROM APPS.AS_ISSUES_VL WHERE ATTRIBUTE_CATEGORY = :p_category;

Because the OBJECTIVE is an MLS view, it must be qualified with the APPS schema, and callers should expect NAME and DESCRIPTION to be returned in the session language. Direct queries against the underlying _B and _TL tables should be avoided in custom code, since they bypass the language resolution that AS_ISSUES_VL provides.