Results for “pn_loc_acc_map_hdr_v”

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

Overview

The PN_LOC_ACC_MAP_HDR_V view is a reporting and integration object within the Oracle E-Business Suite (EBS) Property Manager (PN) module, available in both 12.1.1 and 12.2.2. It is owned by the APPS schema and holds a VALID status. Its documented purpose is to store the mapping of accounts to location header information, exposing header-level accounting mapping definitions that govern how property locations are linked to general ledger accounts.

Functionally, the view is a thin projection over its base table and presents a single row per location-account mapping header. Because it carries the standard EBS "WHO" audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN), the view is well suited for downstream reporting, data extraction, and integration. The MAPPING_NAME column — the term the user searched for — provides the human-readable identifier for each mapping header record, making it the primary descriptive key that consumers rely on when querying or selecting a mapping configuration.

Underlying Base Objects

According to the documented metadata, the view is defined over a single referenced base object: the synonym PN_LOC_ACC_MAP_HDR, which resolves to the corresponding table in the PN schema. The view text confirms this relationship, selecting all listed columns directly from PN_LOC_ACC_MAP_HDR using the alias PLMH:

SELECT PLMH.LOC_ACC_MAP_HDR_ID ... FROM PN_LOC_ACC_MAP_HDR PLMH

Because there is a one-to-one column projection from a single base table with no joins, filters, or aggregations, the view does not introduce data transformation. It functions as a controlled presentation layer over PN_LOC_ACC_MAP_HDR, giving the APPS schema a consistent, named access point for the mapping header data while insulating report logic from direct table references.

Key Columns

• LOC_ACC_MAP_HDR_ID — The unique primary key identifier for each location-account mapping header record.
• MAPPING_NAME — The descriptive name assigned to the mapping header. This is the searched term and the primary business-facing identifier for a mapping definition.
• ORG_ID — The operating unit identifier, enabling multi-org (MOAC) filtering so each mapping is scoped to the appropriate organization.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard EBS descriptive flexfield (DFF) columns, allowing client-specific attribute capture on the mapping header.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard audit ("WHO") columns tracking record creation and modification history.

Common Use Cases and Queries

This view is typically used to review, audit, and extract location-account mapping configurations. A frequent scenario is looking up a mapping by its name, which reflects the user's search for mapping_name:

SELECT LOC_ACC_MAP_HDR_ID, MAPPING_NAME, ORG_ID, LAST_UPDATE_DATE
FROM APPS.PN_LOC_ACC_MAP_HDR_V
WHERE MAPPING_NAME = :mapping_name
AND ORG_ID = :org_id;

Because the view exposes ORG_ID, it is compatible with Multi-Org Access Control views (_ALL style) or can be filtered explicitly by operating unit:

SELECT MAPPING_NAME, ATTRIBUTE1, CREATION_DATE
FROM APPS.PN_LOC_ACC_MAP_HDR_V
WHERE ORG_ID = :org_id
ORDER BY MAPPING_NAME;

Integration and reporting consumers use the view to drive account assignment logic, to reconcile mappings during period-end processing, or to migrate mapping definitions between environments. Administrators may also query the audit columns to determine when a mapping was last changed and by whom, supporting SOX-style change tracking over accounting configuration.