Search Results pn_opex_grp_exp_u1

Overview

The PN.PN_OPEX_EXP_GRPS_ALL table is a core transactional store within the Oracle Property Manager (PN) module of Oracle E-Business Suite, available across releases 12.1.1 and 12.2.2. It persists the definition of operating expense (opex) groups, which are logical containers used to aggregate and prorate recoverable operating costs across agreements. Each row associates an expense group with a specific agreement and with a pro rata basis detail, enabling Property Manager to compute the tenant’s share of common area maintenance, taxes, insurance, and similar operating expenses.

From a Data Vault modeling perspective, the heuristic classification of this object is standalone, indicating that the table is not strictly dependent on another entity for its identity. Because it carries a surrogate primary key (EXPENSE_GRP_ID), descriptive attributes, and a foreign-key reference to the pro rata basis detail table, it is best modeled as a hub-like entity that also bears satellite-style descriptive payload. This classification is offered as a modeling suggestion rather than a prescriptive rule.

Key Information Stored

PN_OPEX_EXP_GRPS_ALL contains 34 documented columns. The most operationally significant are listed below.

• EXPENSE_GRP_ID – The surrogate primary key (PN_OPEX_EXP_GRPS_PK) and the column indexed by the unique business-key candidate PN_OPEX_GRP_EXP_U1.
• AGREEMENT_ID – Identifies the agreement to which the expense group belongs; indexed non-uniquely by PN_OPEX_GRP_AGR_N1.
• PRORAT_BASIS_DTL_ID – Foreign key to PN_OPEX_PRORAT_BASIS_DTLS_ALL, defining how the expense is allocated; indexed non-uniquely by PN_OPEX_GRP_PRO_DT_N1.
• EXPENSE_GRP_NAME – The unique, user-defined name for the expense group (up to 90 characters).
• STD_GRP_NAME_CODE – A coded reference to a standard expense group name.
• CONTRIBUTION_FLAG – Indicates whether the group represents a contribution or credit rather than an expense.
• CAP_FLAG, FEE_FLAG, TAX_FLAG, GROSS_UP_FLAG – Processing controls governing whether a cap, administration fee, tax, or gross-up applies to the group.
• MULTIPLE – The multiplier factor applied before calculating the pro rata share.
• DESCRIPTION – Free-form description (up to 240 characters).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1…15 – Descriptive flexfield columns for extensibility.
• ORG_ID – The operating unit, enforcing multi-org security. Audit columns include LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Property Manager administrators and reporting developers query this table to reconcile recoverable expense setups and to verify that each agreement’s expense groups are properly linked to a pro rata basis. A typical pattern joins the table to its pro rata basis parent to trace allocation rules:

• Retrieve all expense groups for an agreement: SELECT expense_grp_name, contribution_flag, cap_flag FROM pn_opex_exp_grps_all WHERE agreement_id = :agreement_id;
• Identify gross-up or tax-bearing groups using GROSS_UP_FLAG and TAX_FLAG filters.
• Report descriptive flexfield values (ATTRIBUTE1…15) for user-defined categorization.
• Validate uniqueness of EXPENSE_GRP_NAME within a given AGREEMENT_ID.

Related Objects

• PN.PN_OPEX_PRORAT_BASIS_DTLS_ALL – Referenced via PRORAT_BASIS_DTL_ID; defines the allocation basis for each expense group.
• PN.PN_OPEX_EXP_GRPS_PK – The primary key constraint on EXPENSE_GRP_ID.
• Agreement master tables in the PN schema keyed by AGREEMENT_ID supply the parent agreement context.
• Property Manager concurrent programs and recovery calculation routines consume these group definitions during expense recovery processing.
• Operating unit (ORG_ID) joins to HR_OPERATING_UNITS for multi-org reporting.

Together these relationships position PN_OPEX_EXP_GRPS_ALL as the central configuration store for operating expense recovery in Oracle Property Manager.