Results for “ahl_subscriptions_vl”

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

Overview

The AHL_SUBSCRIPTIONS_VL view belongs to the AHL (Complex Maintenance Repair and Overhaul) product family in Oracle E-Business Suite and is owned by the APPS schema. It is a "VL" (translated view) construct, the standard Oracle EBS pattern that couples a multilingual (_TL) translation table with the language-independent base (_B) table so that descriptive, translatable columns are returned in the session's language. This view presents subscription records — for example subscriptions to service bulletins, technical publications, or maintenance documentation distributed to a customer or receiving party — together with their translated comments.

Because it is a view rather than a table, AHL_SUBSCRIPTIONS_VL is read-only for reporting and integration purposes. It exposes the descriptive columns of the base subscription entity joined to the translated comments, filtered to the current runtime language. In Oracle EBS 12.1.1 and 12.2.2 the view is documented as VALID, and it is the recommended object for third-party queries, custom reports, and interface programs that need subscription data with descriptions rendered in the user's language.

Underlying Base Objects

The view is defined over two synonyms referenced in the APPS schema:

• AHL_SUBSCRIPTIONS_B — the base table holding the language-independent subscription attributes, including identifiers, parties, dates, quantity, and the coded columns.
• AHL_SUBSCRIPTIONS_TL — the translation table holding the language-dependent descriptive columns, principally COMMENTS.

The two are joined on SUBSCRIPTION_ID, and the translation row is constrained by AST.LANGUAGE = USERENV('LANG'). This predicate restricts the result to a single row per subscription — that of the language currently in effect for the session — preventing the Cartesian duplication that would otherwise occur across installed languages. The ROW_ID column is derived from the base table's ROWID, while all other columns originate from one of the two base tables. Because the join is an inner join, a subscription must have a corresponding translation row in the active language; if a translation is missing, that subscription will not be returned by the view.

Key Columns

• ROW_ID — the base table's ROWID, useful for row identification in update-capable tooling.
• SUBSCRIPTION_ID — the primary key of the subscription and the join key between _B and _TL.
• DOCUMENT_ID — identifies the document (for example a publication or service bulletin) to which the subscription applies.
• REQUESTED_BY_PARTY_ID and SUBSCRIBED_FRM_PARTY_ID — the requesting and subscribing-from trading parties.
• PURCHASE_ORDER_NO, QUANTITY — commercial details of the subscription.
• STATUS_CODE, FREQUENCY_CODE, SUBSCRIPTION_TYPE_CODE, MEDIA_TYPE_CODE — coded attributes that classify the subscription, its delivery cadence, type, and medium. These are typically resolved against lookup types or value sets by the calling application.
• START_DATE, END_DATE — the effective period of the subscription.
• COMMENTS — the translated descriptive text drawn from AHL_SUBSCRIPTIONS_TL.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and the ATTRIBUTE_CATEGORY plus ATTRIBUTE1–ATTRIBUTE15 flexfields.

Common Use Cases and Queries

The view is the natural entry point for reports and interfaces that need subscription data combined with its translated comments. A query filtering on the searched attribute, SUBSCRIPTION_TYPE_CODE, illustrates the pattern:

• SELECT subscription_id, document_id, subscribed_frm_party_id, subscription_type_code, status_code, start_date, end_date, comments FROM ahl_subscriptions_vl WHERE subscription_type_code = :p_type AND status_code = 'ACTIVE' ORDER BY start_date DESC;

Because the USERENV('LANG') predicate is embedded in the view, no explicit language filter is required in the calling query. Typical scenarios include generating active-subscription listings per party, joining to document or party views to build distribution reports, reconciling purchase-order references, and exporting subscription extracts for downstream maintenance systems. Developers should treat the view as read-only, restrict access through APPS, and use the documented coded columns alongside the appropriate lookup definitions when presenting data to end users.