Results for “ahl_pc_headers_vl”

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

Overview

The AHL_PC_HEADERS_VL view is an Oracle E-Business Suite dictionary object owned by the APPS schema within the AHL product family, which supports Complex Maintenance Repair and Overhaul (CMRO). It is a "VL" (view with translated columns plus base table columns) that presents maintenance program or "PC" (Program/Configuration) header records together with their language-specific translated attributes. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the standard read interface for program header information, exposing both the non-translated base columns and the language-dependent description. Its status is documented as VALID, making it suitable for use in custom reports, concurrent program queries, forms-based LOVs, and integration extracts where a single flattened row per program header is required.

Underlying Base Objects

The view is defined over two documented base objects:

• AHL_PC_HEADERS_B (SYNONYM) — the base table holding language-independent program header data.
• AHL_PC_HEADERS_TL (SYNONYM) — the translation table holding language-specific columns such as DESCRIPTION.

The view text joins the two tables on PC_HEADER_ID and restricts the translation row using AHPCTL.LANGUAGE = USERENV('LANG'), thereby returning the translation matching the session language. The base table alias is AHPC and the translation table alias is AHPCTL. This dependency structure means the view inherits all DML restrictions inherent to a multi-table join; it is effectively read-only for practical purposes, and any update to the underlying program header data must target the base and translation tables directly.

Key Columns

The view exposes the following notable columns:

• ROW_ID — the ROWID of the base table row, useful for building updatable forms or identifying physical rows.
• PC_HEADER_ID — the primary key linking header and translation records.
• OBJECT_VERSION_NUMBER — supports optimistic locking and change tracking.
• NAME — the program header name.
• STATUS — the lifecycle state of the header.
• PRODUCT_TYPE_CODE — the product type classification.
• PRIMARY_FLAG and ASSOCIATION_TYPE_FLAG — flags indicating primary and association behavior.
• DRAFT_FLAG — the column most relevant to the user's search. It indicates whether the header is in a draft state (typically Y/N), which is essential when filtering out unpublished or in-progress programs from operational or reporting queries.
• LINK_TO_PC_ID — a self-referencing link to a related program header.
• DESCRIPTION — the translated description sourced from AHL_PC_HEADERS_TL.
• SECURITY_GROUP_ID — the security group owning the row.
• ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• Standard WHO columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Because DRAFT_FLAG was the search term of interest, a frequent query filters on that column to isolate finalized program headers:

• Filter out drafts: SELECT pc_header_id, name, status, product_type_code FROM apps.ahl_pc_headers_vl WHERE draft_flag = 'N';

• Join to translated descriptions for reports joined by language: SELECT h.pc_header_id, h.name, h.description FROM apps.ahl_pc_headers_vl h WHERE h.draft_flag = 'Y';

• Find linked programs: SELECT name, link_to_pc_id, association_type_flag FROM apps.ahl_pc_headers_vl WHERE link_to_pc_id IS NOT NULL;

Typical scenarios include CMRO program validation extracts, reconciliation reports distinguishing draft from released headers, and integration interfaces that push program definitions into external maintenance systems. Since the view strips the language dimension to the session setting, it is preferable over direct table access when only the current language description is required.