Results for “budgeted_amount”
40 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PN_REC_EXP_LINE_DTL_ALL is a Property Manager (PN) transaction table in Oracle E-Business Suite that stores recovery expense lines and recovery expense line allocation detail. In property management accounting, tenants are frequently billed for a proportionate share of operating expenses — common area maintenance, taxes, insurance, and utilities — and this table is where those recovery expense calculations are persisted line by line. Each row represents a single recovery expense detail record, capturing the amounts and percentages that determine how a pool of recoverable expenses is distributed across a property or location.
The table is owned by the PN schema and carries a _ALL suffix, indicating that it is partitioned or organized by operating unit through the ORG_ID column, which in turn is validated against HR_ALL_ORGANIZATION_UNITS. The documented physical schema for 12.2.2 lists 39 columns, and the object is marked VALID in the ETRM dictionary for both 12.1.1 and 12.2.2 releases.
From a dimensional modeling perspective, the metadata supports classifying this table as a satellite-leaning structure. It carries descriptive and measure attributes (amounts, percentages, flags, descriptive attributes) around the core recovery expense business key represented by EXPENSE_LINE_ID, and it also references itself through PARENT_EXPENSE_LINE_ID, which suggests a self-referencing hierarchy rather than a pure transactional hub. Modelers should treat the expense line identifier as the business anchor and this table as the detail/measure-bearing satellite attached to it.
Key Information Stored
The surrogate primary key is EXPENSE_LINE_DTL_ID, enforced through the constraint PN_REC_EXP_LINE_DTL_PK and backed by the unique index PN_REC_EXP_LINE_DTL_U1. This is the only documented business-key candidate for uniqueness; EXPENSE_LINE_ID is a foreign key to the parent recovery expense line, not a unique key on its own.
The most operationally significant columns are:
EXPENSE_LINE_ID— foreign key toPN_REC_EXP_LINE_ALL, tying the detail to its parent expense line.PARENT_EXPENSE_LINE_ID— self-referencing key used to express hierarchical or nested expense line structures.PROPERTY_ID— foreign key toPN_PROPERTIES_ALL, identifying the property to which the recovery expense belongs.LOCATION_ID— identifies the specific location or unit within the property.EXPENSE_TYPE_CODE— classifies the nature of the recoverable expense.EXPENSE_ACCOUNT_IDandACCOUNT_DESCRIPTION— the accounting account and its description used for posting and reporting.ACTUAL_AMOUNT,ACTUAL_PCT, andACTUAL_AMOUNT_OVR— the actual expense amount, the allocation percentage, and any override amount.BUDGETED_AMOUNT,BUDGETED_PCT, andBUDGETED_AMOUNT_OVR— the corresponding budgeted figures and overrides, enabling budget-versus-actual comparison.CURRENCY_CODE— the currency in which amounts are denominated.EXPENSE_LINE_INDICATORandRECOVERABLE_FLAG— control flags denoting line type and whether the expense is recoverable from tenants.ORG_ID— operating unit identifier, validated againstHR_ALL_ORGANIZATION_UNITS.- The standard audit columns
CREATION_DATE,CREATED_BY,LAST_UPDATE_DATE,LAST_UPDATED_BY, andLAST_UPDATE_LOGIN. - Fifteen
ATTRIBUTE1throughATTRIBUTE15descriptive flexfield columns plusATTRIBUTE_CATEGORY.
Common Use Cases and Queries
Recovery expense detail is most often queried to verify how a recoverable expense pool was allocated, to reconcile budget against actual recovery, and to feed tenant billing or reconciliation reports. A typical query joins the detail to its parent line and property:
- Allocation review: select expense amount, percentage, and override by property and location to confirm each participant's share of the pool.
- Recoverability reporting: filter on
RECOVERABLE_FLAGto isolate expenses eligible for tenant recovery. - Budget versus actual analysis: compare
ACTUAL_AMOUNTagainstBUDGETED_AMOUNTbyEXPENSE_TYPE_CODE. - Hierarchy traversal: use
PARENT_EXPENSE_LINE_IDwith aCONNECT BYclause to walk nested expense structures. - Account reconciliation: group by
EXPENSE_ACCOUNT_IDto tie recovery amounts back to the general ledger.
A representative pattern selecting detail for a given expense line is SELECT EXPENSE_LINE_DTL_ID, PROPERTY_ID, LOCATION_ID, EXPENSE_TYPE_CODE, ACTUAL_AMOUNT, ACTUAL_PCT, RECOVERABLE_FLAG FROM PN_REC_EXP_LINE_DTL_ALL WHERE EXPENSE_LINE_ID = :line_id, filtered by ORG_ID for multi-org security.
Related Objects
The most significant related objects, established through documented foreign key relationships, are:
PN_REC_EXP_LINE_ALL— parent table joined onEXPENSE_LINE_ID.PN_PROPERTIES_ALL— property master joined onPROPERTY_ID.HR_ALL_ORGANIZATION_UNITS— operating unit reference onORG_ID.PN_REC_EXPCL_DTLACC_ALL— dependent allocations table joining onEXPENSE_LINE_DTL_ID.PN_REC_EXP_ITF— interface table referencing the detail throughEXPENSE_LINE_DTL_ID, used when recovery expense data is staged for import or processing.PN_REC_EXP_LINE_DTL_ALL— self-reference viaEXPENSE_LINE_DTL_IDandPARENT_EXPENSE_LINE_IDfor hierarchical structure.
Together these relationships position the table as the allocation and measure-bearing detail layer within the Property Manager recovery expense model.
-
Stores recovery expense lines and recovery expense line allocations information.
-
Recovery Expense Interface Table.
-
Recovery Expense Interface Table.
-
Stores recovery expense lines and recovery expense line allocations information.
-
VIEW: PN.PN_REC_EXP_ITF# 12.2.2
-
VIEW: PN.PN_REC_EXP_ITF# 12.2.2
-
TABLE: PN.PN_REC_EXP_ITF 12.2.2
-
TABLE: PN.PN_REC_EXP_ITF 12.1.1
-
eTRM - PN Tables and Views 12.1.1
Interface table to contain batch lines information.
-
eTRM - PN Tables and Views 12.2.2
Interface table to contain batch lines information.