Search Results source_ref_code




Overview
Explore in AI Chat

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, AHL_DOC_TITLE_ASSOS_VL is a seeded, VALID view owned by the APPS schema within the AHL product family (Complex Maintenance Repair and Overhaul). It is a "VL" (view-language) construct, a standard EBS designation indicating that the view exposes translated descriptive columns alongside its base, language-independent columns. The view associates document revisions with the business objects they support, effectively serving as a documentation-to-asset link. Because it resolves directly to underlying AHL tables rather than a single denormalized structure, it normalizes the association between an operational object—such as an asset, work order, or serialized component—and the controlling documentation (chapters, sections, pages, figures) that governs it.

Functionally, the view is the primary read interface for document title associations. It is consumed by Oracle Forms (the AHL maintenance user interface), concurrent programs, OBIEE/BI Publisher reports, and custom OAF or web-service integrations that need a translatable, language-aware projection of the association data.

Underlying Base Objects

The view is defined over two documented base objects, exposed to APPS as synonyms:

The join is performed on the shared primary key DOC_TITLE_ASSO_ID, with the translation side filtered by ADTAT.LANGUAGE = USERENV('LANG'). This design ensures that whichever session language is active, the view returns the association record with its properly translated chapter, section, subject, page, figure, and note values, falling back to the installation's base language where no translation exists. One row is returned per association record.

Key Columns

  • ROW_ID — the ROWID of the base table record, useful for direct post-DML targeted access.
  • DOC_TITLE_ASSO_ID — the primary key linking the B and TL records.
  • DOC_REVISION_ID, DOCUMENT_ID — identify the specific document and revision being associated.
  • ASO_OBJECT_TYPE_CODE, ASO_OBJECT_ID — the associated object's type and identifier, enabling polymorphic linking to assets, work orders, and similar entities.
  • USE_LATEST_REV_FLAG — indicates whether the association should track the latest document revision.
  • SERIAL_NO — the serialized item reference, where applicable.
  • SOURCE_REF_CODE — a source reference code qualifying the origin or authority of the association. This is the column that appeared in the user's search term and is a frequently queried discriminator for filtering associations by their documented source.
  • CHAPTER, SECTION, SUBJECT, PAGE, FIGURE, NOTE — translated locators pinpointing the relevant documentation content.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive-flexfield columns available for client-specific extensions.

Common Use Cases and Queries

Typical scenarios include retrieving all documentation governing a given object, identifying which serialized items reference a document revision, and filtering associations by SOURCE_REF_CODE for compliance or audit reporting. A representative query that retrieves all associations for a specific object type, restricted through the searched column, is:

  • SELECT DOC_TITLE_ASSO_ID, DOCUMENT_ID, DOC_REVISION_ID, ASO_OBJECT_TYPE_CODE, ASO_OBJECT_ID, SERIAL_NO, CHAPTER, SECTION, SOURCE_REF_CODE FROM AHL_DOC_TITLE_ASSOS_VL WHERE SOURCE_REF_CODE = :source_ref_code;
  • SELECT DOC_TITLE_ASSO_ID, DOCUMENT_ID, CHAPTER, PAGE, NOTE FROM AHL_DOC_TITLE_ASSOS_VL WHERE ASO_OBJECT_TYPE_CODE = :type AND ASO_OBJECT_ID = :id;
  • SELECT COUNT(*) FROM AHL_DOC_TITLE_ASSOS_VL WHERE USE_LATEST_REV_FLAG = 'Y';

Because the view performs the translation join internally, developers should query it rather than joining the B and TL tables directly, guaranteeing language-correct results and insulating custom code from underlying table changes.