Results for “insured_amount”

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

Overview

PN_INSURANCE_REQUIREMNTS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, belonging to the PN – Property Manager product. It exposes insurance requirement records maintained against leases so that downstream reporting, integration, and inquiry screens can retrieve decoded insurance data without interacting directly with the base transaction table. The view is validated and available in both EBS 12.1.1 and 12.2.2, retaining the same definition across releases. Its primary purpose is to present insurance requirement rows keyed by INSURANCE_REQUIREMENT_ID, enriched with a human-readable insurance type description resolved from FND_LOOKUPS. Because the Property Manager module governs lease-level insurance obligations — policy periods, insurer details, insured and required amounts, and status — this view serves as the reporting façade for that data, shielding consumers from the lookup join logic and providing a stable, denormalized projection.

Underlying Base Objects

The view is defined over three documented referenced objects:

• PN_INSURANCE_REQUIREMENTS (SYNONYM) — the base transaction table holding the actual insurance requirement rows. It supplies every stored column in the view, including the primary key INSURANCE_REQUIREMENT_ID, lease linkage, dates, amounts, descriptive attributes, descriptive flexfield columns, and ORG_ID.
• FND_LOOKUPS (VIEW) — the Oracle Application Object Library lookup view. It is joined on LOOKUP_TYPE = 'PN_INSURANCE_TYPE' and LOOKUP_CODE = INSURANCE_TYPE_LOOKUP_CODE to translate the stored lookup code into the display value exposed as INSURANCE_TYPE (the MEANING column).
• FND_GLOBAL (PACKAGE) — referenced for session context resolution, typically supplying ORG_ID through FND_GLOBAL.ORG_ID for multi-org security and defaulting within the Property Manager data model.

Because the view joins PN_INSURANCE_REQUIREMENTS to FND_LOOKUPS using an inner join, only insurance requirement rows whose insurance type lookup code has an active matching entry of type PN_INSURANCE_TYPE are returned. Rows with an orphaned or inactive lookup code are filtered out.

Key Columns

• INSURANCE_REQUIREMENT_ID — primary identifier for each insurance requirement record; the column referenced by the user's search term.
• LEASE_ID and LEASE_CHANGE_ID — foreign keys tying the requirement to a lease and, where applicable, a lease change or amendment.
• INSURANCE_TYPE_LOOKUP_CODE and INSURANCE_TYPE — the stored code and its decoded meaning from FND_LOOKUPS.
• POLICY_START_DATE and POLICY_EXPIRATION_DATE — the coverage period for the insurance policy.
• INSURER_NAME, POLICY_NUMBER, INSURED_AMOUNT, REQUIRED_AMOUNT — policy identity and financial limits; REQUIRED_AMOUNT typically represents the contractual minimum while INSURED_AMOUNT is the actual coverage carried.
• STATUS and INSURANCE_COMMENTS — workflow/compliance state and free-text notes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments for client-specific extensions.
• ROW_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit and row identifier columns.
• ORG_ID — operating unit identifier supporting multi-org filtering.

Common Use Cases and Queries

The view is typically queried for lease insurance compliance reporting, expiry monitoring, and integration extracts. A representative query retrieving all requirements for a given lease might read:

• SELECT insurance_requirement_id, insurance_type, policy_start_date, policy_expiration_date, insurer_name, insured_amount, required_amount, status FROM pn_insurance_requiremnts_v WHERE lease_id = :lease_id;
• Expiry monitoring: SELECT insurance_requirement_id, lease_id, policy_expiration_date, status FROM pn_insurance_requiremnts_v WHERE policy_expiration_date BETWEEN SYSDATE AND SYSDATE + 30 ORDER BY policy_expiration_date;
• Shortfall analysis comparing coverage to requirement: SELECT insurance_requirement_id, required_amount, insured_amount FROM pn_insurance_requiremnts_v WHERE NVL(insured_amount,0) < NVL(required_amount,0);
• Multi-org filtered extract joining to lease tables on LEASE_ID while restricting by ORG_ID.

Note the exact view name spelling (PN_INSURANCE_REQUIREMNTS_V, without the second "E") when referencing it in SQL or in Oracle Reports/BI Publisher data models.