Search Results pn_loc_acc_map_u1

Overview

PN.PN_LOC_ACC_MAP_ALL is a transactional mapping table in the Oracle E-Business Suite Property Manager (PN) module. It stores the configuration that associates general ledger expense accounts—expressed as low/high account ranges—with specific properties, locations, and accounting periods. The table's operational purpose is narrowly defined: it is the source of the account-to-location mappings consulted when expense amounts are extracted from Oracle General Ledger into the PN_REC_EXP_ITF interface table. In effect, it governs which GL balances are attributed to which recoverable property locations for a given effective period, making it a central artifact for expense recovery processing.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and it carries the ORG_ID column, marking it as a multi-org (operating unit) enabled object. Its unique index, PN_LOC_ACC_MAP_U1, is built on LOC_ACC_MAP_ID in the APPS_TS_TX_IDX tablespace. From a Data Vault modeling perspective, the heuristic classification of this object is a link, because it records the association between two or more business entities (a header mapping, a property, a location, and a GL account range) rather than describing a single entity in isolation. The 92-column footprint, dominated by 30 pairs of key flexfield segment low/high columns, reflects the need to accommodate any GL chart-of-accounts structure.

Key Information Stored

The table's surrogate primary key is LOC_ACC_MAP_ID (NUMBER(15)), defined by the primary key constraint PN_LOC_ACC_MAP_PK and independently enforced by the unique index PN_LOC_ACC_MAP_U1. The parent linkage is carried by LOC_ACC_MAP_HDR_ID, a foreign key to PN_LOC_ACC_MAP_HDR_ALL, which groups detail mapping lines under a mapping header. The ORG_ID column is a foreign key to HR_ALL_ORGANIZATION_UNITS, scoping each row to an operating unit.

The most operationally significant columns include:

• PROPERTY_ID — identifies the property whose expenses are being mapped.
• LOCATION_ID — identifies the specific location within the property.
• ACCOUNT_LOW and ACCOUNT_HIGH — the GL account range boundaries (VARCHAR2(240)) used for account matching.
• EXPENSE_TYPE_CODE — the expense type associated with the location and account-range combination.
• EFFECTIVE_FROM_DATE and EFFECTIVE_TO_DATE — the accounting period window during which the mapping is valid.
• RECOVERABLE_FLAG — indicates whether the mapped expenses are recoverable.
• SEGMENT1_LOW through SEGMENT30_HIGH — the flexible-format key flexfield segment ranges supporting granular account definition.
• LAST_UPDATE_DATE, CREATED_BY, and the remaining Who columns — standard audit tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield support.

Common Use Cases and Queries

Recovery accountants and developers use this table to audit and troubleshoot expense extraction. A typical diagnostic query resolves an active mapping for a property and period:

• Verify active mappings for a property/location: SELECT loc_acc_map_id, property_id, location_id, account_low, account_high, expense_type_code FROM pn_loc_acc_map_all WHERE property_id = :p AND org_id = :o AND SYSDATE BETWEEN effective_from_date AND NVL(effective_to_date, SYSDATE);
• Trace which GL account ranges feed the recovery interface, joining detail lines back to their header via LOC_ACC_MAP_HDR_ID.
• Identify non-recoverable mappings with WHERE recoverable_flag = 'N'.
• Reporting on coverage gaps where a location lacks an effective mapping for a given period.

Because the low/high segment columns mirror the GL chart of accounts, queries frequently intersect these ranges against GL_CODE_COMBINATIONS to confirm that balances fall inside a defined range.

Related Objects

The table participates in a well-defined dependency graph. Key related objects include:

• PN.PN_LOC_ACC_MAP_HDR_ALL — parent header, joined on LOC_ACC_MAP_HDR_ID.
• HR_ALL_ORGANIZATION_UNITS — operating unit reference, joined on ORG_ID.
• PN_REC_EXP_ITF — the recovery expense interface table populated using these mappings.
• GL_CODE_COMBINATIONS — GL account validation against the ACCOUNT_LOW/ACCOUNT_HIGH and SEGMENTn ranges.
• Property and location base entities referenced through PROPERTY_ID and LOCATION_ID.
• The PN_LOC_ACC_MAP_PK constraint and PN_LOC_ACC_MAP_U1 index, which enforce and accelerate access by LOC_ACC_MAP_ID.

Together these objects form the configuration backbone for property expense recovery in Oracle Property Manager 12.1.1 and 12.2.2.