Results for “pn_rec_exp_itf”

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

Overview

PN_REC_EXP_ITF is the Recovery Expense Interface table owned by the PN (Property Manager) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as a staging and integration surface through which recovery expense transactions are loaded into or passed between Property Manager and external sources such as subledger accounting, feeder systems, or third-party property management applications. Because recovery expenses represent costs recoverable from tenants under lease agreements, this interface table captures the expense amount, the property or location to which it applies, the accounting context, and the effective date range before the data is validated and posted to the permanent recovery expense line tables.

Applying a Data Vault modeling heuristic to the documented foreign key structure, PN_REC_EXP_ITF can be classified as a link entity. It resolves relationships between properties and recovery expense line details, and its two documented foreign keys behave as references to hub-like parent entities rather than defining independent business concepts. This classification is a modeling suggestion derived from the foreign key graph and should be treated as guidance rather than as a formal Data Vault implementation, since the table is physically a standard EBS interface object.

Key Information Stored

The table is documented with 35 columns in the ETRM 12.2.2 physical schema. The most operationally significant columns are listed below. A surrogate primary key is not explicitly documented for this interface table; the closest structural identifier is EXPENSE_LINE_DTL_ID, which is also a foreign key, while PROPERTY_ID and LOCATION_ID serve as business-key candidates for identifying where the recovery expense applies. ORG_ID provides the multi-org operating unit context.

• EXPENSE_LINE_DTL_ID — Foreign key to PN_REC_EXP_LINE_DTL_ALL; links the interface row to the originating recovery expense line detail.
• PROPERTY_ID — Foreign key to PN_PROPERTIES_ALL; identifies the property to which the recovery expense belongs.
• LOCATION_ID — Identifies the specific location or building associated with the expense.
• EXPENSE_TYPE_CODE — Classifies the recovery expense (for example, operating or tax recovery categories).
• EXPENSE_ACCOUNT_ID and ACCOUNT_DESCRIPTION — The GL account and its description used to record the expense.
• ACTUAL_AMOUNT and BUDGETED_AMOUNT — The incurred and budgeted recovery amounts.
• CURRENCY_CODE — Currency in which the amounts are expressed.
• FROM_DATE and TO_DATE — The effective date range of the recovery expense.
• TRANSFER_FLAG and MODE_FLAG — Processing status indicators that govern whether and how the row is transferred.
• ORG_ID — Operating unit identifier for multi-org security and reporting.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns for client-specific extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns.

Common Use Cases and Queries

The primary use case is validating and transferring staged recovery expense records. Typical reporting queries join PN_REC_EXP_ITF to PN_PROPERTIES_ALL and PN_REC_EXP_LINE_DTL_ALL to verify that amounts, dates, and accounts are consistent before posting.

• Staged vs. transferred expense monitoring — Filter on TRANSFER_FLAG to identify rows awaiting transfer or those that failed validation.
• Property-level recovery reporting — Aggregate ACTUAL_AMOUNT by PROPERTY_ID and EXPENSE_TYPE_CODE for recovery analysis.
• Multi-org reconciliation — Restrict by ORG_ID and CURRENCY_CODE to reconcile recovery expenses by operating unit.
• Sample join pattern — SELECT i.PROPERTY_ID, i.EXPENSE_TYPE_CODE, i.ACTUAL_AMOUNT FROM PN_REC_EXP_ITF i, PN_PROPERTIES_ALL p WHERE i.PROPERTY_ID = p.PROPERTY_ID AND i.TRANSFER_FLAG = 'N';

Related Objects

PN_REC_EXP_ITF depends on the following documented parent objects and interacts with Property Manager processing routines and descriptive flexfield definitions.

• PN_PROPERTIES_ALL — Joined via PROPERTY_ID; provides property master data.
• PN_REC_EXP_LINE_DTL_ALL — Joined via EXPENSE_LINE_DTL_ID; holds the permanent recovery expense line details.
• PN_REC_EXP_ITF_PKG / concurrent recovery expense import programs — Validate and transfer interface rows into the base recovery expense tables.
• FND_ORG_ASSIGNMENTS / ORG_ID context — Supplies the operating unit referenced by ORG_ID.
• GL_CODE_COMBINATIONS — Resolves EXPENSE_ACCOUNT_ID to a valid GL account combination.