Results for “pn_rights”

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

Overview

APPS.PN_RIGHTS_V is a reporting and integration view in Oracle E-Business Suite that exposes the property rights records stored in the Property Manager (PN) module. The view joins the base rights table, PN_RIGHTS, to the FND_LOOKUPS view to resolve the coded values for right type and right status into their user-facing meanings. It is defined in the APPS schema and is available in both EBS 12.1.1 and 12.2.2. Because it presents translated meanings rather than raw lookup codes, the view is commonly used in custom reports, concurrent programs, and interface extracts where a readable description of each lease right is required without additional lookup logic in the calling code.

Underlying Base Objects

The view is defined over three documented objects. The primary source is the synonym PN_RIGHTS, which resolves to the underlying APPS.PN_RIGHTS table holding lease right records. Two joins are made against the FND_LOOKUPS view to translate lookup codes. The first join matches TLK.LOOKUP_CODE to PNR.RIGHT_TYPE_CODE where LOOKUP_TYPE equals 'PN_RIGHTS_TYPE', and the second matches RLK.LOOKUP_CODE to PNR.RIGHT_STATUS_CODE where LOOKUP_TYPE equals 'PN_RIGHT_STATUS_TYPE'. The view metadata also references the FND_GLOBAL package, which supplies session-level context such as the operating unit, reflected in the ORG_ID column and the standard WHO audit columns. Each row carries the ROWID of the base PN_RIGHTS record, exposed as ROW_ID, allowing the view to be used for both read and updatable operations.

Key Columns

• RIGHT_ID — Primary key of the underlying rights record; the unique identifier for a lease right.
• LEASE_ID / LEASE_CHANGE_ID — The lease header and the specific change (amendment) against which the right was created.
• RIGHT_NUM / RIGHT_REFERENCE — The internal sequence number and any external reference for the right.
• RIGHT_TYPE_CODE / RIGHT_TYPE — The coded value and its translated meaning from the PN_RIGHTS_TYPE lookup, identifying the nature of the right.
• RIGHT_STATUS_CODE / RIGHT_STATUS — The coded value and its translated meaning from the PN_RIGHT_STATUS_TYPE lookup, indicating whether the right is active, terminated, or in another state.
• START_DATE / EXPIRATION_DATE — The effective and expiry dates of the right.
• RIGHT_COMMENTS — Free-form descriptive notes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard EBS descriptive flexfield columns for capturing client-specific data.
• ORG_ID — The operating unit that owns the record, used for multi-org security.
• ROW_ID — The ROWID of the base table row.

Common Use Cases and Queries

The view is typically queried to report on all rights attached to a lease, to monitor rights approaching expiry, or to extract data into a downstream system. A representative query filters rights by operating unit and status:

• SELECT right_id, lease_id, right_num, right_type, right_status, start_date, expiration_date FROM apps.pn_rights_v WHERE org_id = :p_org_id AND right_status = 'Active' ORDER BY lease_id, right_num;
• Rights expiring within a window: SELECT lease_id, right_num, right_type, expiration_date FROM apps.pn_rights_v WHERE expiration_date BETWEEN SYSDATE AND SYSDATE + 90;
• Aggregation by type: SELECT right_type, COUNT(*) FROM apps.pn_rights_v WHERE org_id = :p_org_id GROUP BY right_type;

Because the view resolves lookup meanings in the database layer, queries remain concise and consistent with the form-level presentation of right data.