Results for “index_constraint_id”

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

Overview

PN_INDEX_LEASE_CONSTRAINTS_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and registered in the Property Manager (PN) product module. It serves as the form-backed view for the Index Lease Constraints entity, exposing lease indexing constraint records for query, reporting, and integration purposes. The view presents a single ROWID-based identifier column (ROW_ID) alongside the full set of business and descriptive columns defined on the underlying constraints table, together with the standard EBS audit columns and a multi-organization ORG_ID column. Because the object is a view rather than a table, it is read-mostly in nature; DML operations against it resolve through the base object and are subject to the Form view conventions and any additional constraints or grants attached to the base object.

Underlying Base Objects

The view is defined over the table PN_INDEX_LEASE_CONSTRAINTS, which is accessed in the documented view text via the synonym PN_INDEX_LEASE_CONSTRAINTS. Every column in the view text is selected directly from that base object, with the sole exception of ROW_ID, which is generated as ROWID and aliased. No joins, filters, or aggregations are applied in the view definition, so the view is a one-to-one projection of the base table row set. The view is therefore structurally and functionally dependent on the base constraints table, and any row-level security, organization partitioning (ORG_ID), or descriptive flexfield configuration present on the base table is inherited transparently through the view. Indexing constraints are attached to an index lease record through the INDEX_LEASE_ID column, which is the key the user searching for index_lease_id will most commonly filter on.

Key Columns

• ROW_ID — The base row's physical ROWID, used by the form for row-level identification and navigation.
• INDEX_CONSTRAINT_ID — Primary key of the index constraint record.
• INDEX_LEASE_ID — Foreign key linking each constraint to its parent index lease record; the primary filter column for lease-level lookups.
• SCOPE — Defines the scope to which the constraint applies (for example, a lease, an index, or a defined grouping), controlling how the constraint is evaluated.
• MINIMUM_AMOUNT / MAXIMUM_AMOUNT — The allowable monetary boundary values defining the constraint range.
• MINIMUM_PERCENT / MAXIMUM_PERCENT — The allowable percentage boundary values defining the constraint range.
• ORG_ID — Operating unit / organization identifier supporting multi-org partitioning of the constraint data.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The descriptive flexfield (DFF) context and segment columns, enabling customer-specific constraint attributes.
• Audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — Standard EBS who-did-what-when audit tracking.

Common Use Cases and Queries

This view is most often queried to retrieve the minimum/maximum amount and percentage thresholds that apply to a given index lease. A typical query lists all constraints for a lease:

• SELECT index_lease_id, scope, minimum_amount, maximum_amount, minimum_percent, maximum_percent FROM pn_index_lease_constraints_v WHERE index_lease_id = :lease_id;
• SELECT index_constraint_id, index_lease_id, scope, minimum_percent, maximum_percent FROM apps.pn_index_lease_constraints_v WHERE org_id = :org_id AND scope = :scope;
• SELECT COUNT(*) FROM apps.pn_index_lease_constraints_v WHERE index_lease_id = :lease_id;

Beyond ad hoc queries, the view supports lease index reporting, validation of constraint boundaries against calculated index values, and integration extracts feeding downstream property accounting or contract management processes. When joining the view to lease master data, join on INDEX_LEASE_ID; when restricting output to the caller's operating unit, always include ORG_ID.