Results for “pn_loc_acc_map_v”

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

Overview

PN_LOC_ACC_MAP_V is an Oracle E-Business Suite view owned by the APPS schema within the PN (Property Manager) product module. Its documented purpose is to store the information for mapping of expense accounts to the location. In practice, the view presents a denormalized, report-friendly projection of the location-to-account mapping rules maintained in the Property Manager module, joining the mapping header and detail tables to property, location, and lookup information. It is classified as a VIEW and is documented with a VALID status in ETRM 12.2.2, with the same definition applicable in 12.1.1.

The view exists primarily to support reporting and integration requirements. Rather than requiring consumers to resolve the underlying header-to-detail relationships, account segment ranges, and lookup meanings manually, PN_LOC_ACC_MAP_V delivers a single flat row per mapping detail, enriched with property name, property code, location code, location type, and the descriptive meaning of the expense type. This makes it suitable for expense account rule extraction, reconciliation extracts, and downstream interfaces that need to interpret mapping configuration without embedding the PN data model directly.

Underlying Base Objects

The documented view definition draws on the following base objects:

• PN_LOC_ACC_MAP (synonym) — the mapping detail table, aliased as PLAM in the view text. It supplies the mapping identifier, account ranges, effective dates, recoverable flag, and the twelve segment low/high pairs.
• PN_LOC_ACC_MAP_HDR (synonym) — the mapping header table, aliased as PLMH, providing MAPPING_NAME.
• PN_PROPERTIES (synonym) — aliased as PR, supplying PROPERTY_NAME and PROPERTY_CODE.
• PN_LOCATIONS (synonym) — correlated subqueries against PN_LOCATIONS (aliases L1 and LOC) return LOCATION_TYPE_LOOKUP_CODE and LOCATION_CODE for the referenced location.
• FND_LOOKUPS (view) — aliased as ETYPE, providing the MEANING for the EXPENSE_TYPE_CODE lookup value.
• FND_GLOBAL (package) — referenced by the view for session and responsibility context.

The header-to-detail relationship is a standard parent/child join keyed on LOC_ACC_MAP_HDR_ID, while PROPERTY_ID and LOCATION_ID link each mapping line to its property and location. The location subqueries use outer-join syntax with ROWNUM = 1, so a mapping row is returned even when no matching PN_LOCATIONS record exists.

Key Columns

• LOC_ACC_MAP_ID / LOC_ACC_MAP_HDR_ID — primary identifiers of the mapping detail and its header.
• MAPPING_NAME — descriptive name of the mapping header, useful for grouping rule sets.
• PROPERTY_ID, PROPERTY_NAME, PROPERTY_CODE — property context of the mapping.
• LOCATION_ID, LOCATION_CODE, LOCATION_TYPE — location context, including the location type lookup code.
• EXPENSE_TYPE_CODE — the expense type lookup code being mapped, the value most frequently used to filter the view; EXPENSE_TYPE is the corresponding decoded MEANING from FND_LOOKUPS.
• ACCOUNT_LOW / ACCOUNT_HIGH — the account range bounds for the mapping.
• SEGMENT1_LOW / SEGMENT1_HIGH through SEGMENT12_LOW / SEGMENT12_HIGH — per-segment range columns supporting granular account rule definition.
• EFFECTIVE_FROM_DATE / EFFECTIVE_TO_DATE — validity window for the mapping rule.
• RECOVERABLE_FLAG — indicates whether the mapped expense is recoverable.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing expense account mapping configuration, extracting rules for a specific property or location, and validating that mappings are active for a given date. The following query returns active mappings for a given expense type:

• SELECT LOC_ACC_MAP_ID, MAPPING_NAME, PROPERTY_CODE, LOCATION_CODE, EXPENSE_TYPE, ACCOUNT_LOW, ACCOUNT_HIGH, EFFECTIVE_FROM_DATE, EFFECTIVE_TO_DATE FROM APPS.PN_LOC_ACC_MAP_V WHERE EXPENSE_TYPE_CODE = :p_expense_type_code AND SYSDATE BETWEEN EFFECTIVE_FROM_DATE AND NVL(EFFECTIVE_TO_DATE, SYSDATE + 1);

A complementary query lists all mappings for a property, decoding the expense type through the view itself:

• SELECT PROPERTY_NAME, LOCATION_CODE, EXPENSE_TYPE, RECOVERABLE_FLAG FROM APPS.PN_LOC_ACC_MAP_V WHERE PROPERTY_CODE = :p_property_code ORDER BY LOCATION_CODE, EXPENSE_TYPE;

Because EXPENSE_TYPE_CODE and its decoded EXPENSE_TYPE are both exposed, the view is especially convenient for ad-hoc lookups and for BI Publisher or OBIEE extracts where the lookup meaning must be shown without an additional join.