Results for “pn_options”

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

Overview

APPS.PN_OPTIONS_V is a reporting and integration view in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that presents lease option records maintained by the Property Manager (PN) module. In ETRM terminology, a lease option represents a contractual right — such as renewal, expansion, termination, or purchase — that a tenant may exercise during or at the end of a lease term. The base table PN_OPTIONS stores these options in coded form, referencing lookup codes, a unit-of-measure code, and a lease identifier.

The view adds descriptive meaning to those codes by joining to FND_LOOKUPS for the option type and option status, and to MTL_UNITS_OF_MEASURE for the unit-of-measure description. It also derives the column OPTION_TERM as the difference, in days, between the option expiration date and start date. This makes the view suitable for ad hoc reporting, concurrent programs, and integration extracts where human-readable option attributes are required rather than raw lookup codes.

Underlying Base Objects

The view is defined over four documented base objects:

• PN_OPTIONS (SYNONYM) — the primary source of option data, supplying all identifying, date, status, cost, and descriptive attribute columns.
• FND_LOOKUPS (VIEW) — joined twice, once for lookup type PN_LEASE_OPTION_TYPE to decode OPTION_TYPE_CODE into its meaning, and once for lookup type PN_OPTION_STATUS_TYPE to decode OPTION_STATUS_LOOKUP_CODE.
• MTL_UNITS_OF_MEASURE (SYNONYM) — joined to the option UOM_CODE to return the unit-of-measure description; the outer join symbol (+) indicates that an option may exist without a valid UOM.
• FND_GLOBAL (PACKAGE) — referenced as a documented base object, typically for session context such as ORG_ID, though the supplied view text does not expose a direct call.

Because the two FND_LOOKUPS joins are inner joins, only options whose type and status codes have matching enabled lookup rows in the appropriate lookup types are returned. The UOM join is outer, so options without a UOM still appear.

Key Columns

• OPTION_ID, LEASE_ID, LEASE_CHANGE_ID — primary identifier of the option and the lease or lease change to which it belongs.
• OPTION_NUM — the user-visible option number within the lease.
• OPTION_TYPE_CODE / OPTION_TYPE — the stored lookup code and its decoded meaning for the option category.
• OPTION_STATUS_LOOKUP_CODE / OPTION_STATUS_TYPE — the stored status code and its decoded meaning (for example, exercised or expired).
• START_DATE, EXPIRATION_DATE, OPTION_TERM — the option period; OPTION_TERM is the inclusive number of days between the two dates.
• OPTION_EXER_START_DATE, OPTION_EXER_END_DATE, OPTION_ACTION_DATE — the exercise window and the date the option was actioned.
• OPTION_SIZE, UOM_CODE, UNIT_OF_MEASURE — the option quantity and its decoded unit of measure.
• OPTION_COST, OPTION_AREA_CHANGE, OPTION_REFERENCE — financial and descriptive option details.
• OPTION_NOTICE_REQD, OPTION_COMMENTS — notice requirement flag and free-text comments.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard flexfield descriptive columns.
• ORG_ID — the operating unit identifier supporting multi-org security.
• ROW_ID — the rowid of the base PN_OPTIONS row.

Common Use Cases and Queries

The view is typically used to list all options on a lease with readable descriptions, to monitor upcoming option exercise windows, or to extract lease option data for downstream reporting. A representative query follows:

• List active options for a lease: SELECT option_num, option_type, option_status_type, start_date, expiration_date, option_term FROM apps.pn_options_v WHERE lease_id = :p_lease_id AND option_status_lookup_code = 'ACTIVE' ORDER BY start_date.
• Expiring options within a date range: SELECT lease_id, option_num, option_type, expiration_date FROM apps.pn_options_v WHERE expiration_date BETWEEN :p_from AND :p_to ORDER BY expiration_date.
• Options awaiting exercise: SELECT lease_id, option_num, option_exer_start_date, option_exer_end_date, option_notice_reqd FROM apps.pn_options_v WHERE option_action_date IS NULL AND option_exer_end_date >= SYSDATE.

Because the view resolves lookup meanings and unit-of-measure text, it removes the need for reporting logic to join FND_LOOKUPS and MTL_UNITS_OF_MEASURE separately, and it should be preferred over direct queries against PN_OPTIONS when descriptive output is required.