Results for “ipe_code”

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

Overview

OKL_INS_POLICIES_V is an APPS-owned database view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Lease and Finance Management (OKL) module. The view consolidates insurance policy and insurance quote records maintained against lease applications, presenting a denormalized, read-only projection of the underlying insurance policy entities. Because OKL insurance data spans a base table (transactional and attribute columns) and a translation table (descriptive and language-dependent columns), the view exists to shield forms, concurrent programs, reports, and integration interfaces from the join logic required to reconstruct a complete insurance policy record.

The view is documented as VALID in the ETRM metadata. Its central role is to expose both policy (actual, in-force coverage) and quote (prospective coverage) rows through a single interface, distinguished by the QUOTE_YN flag. This makes it a standard access point for insurance processing within lease origination and contract administration.

Underlying Base Objects

Per the documented 12.2.2 metadata, OKL_INS_POLICIES_V is defined over two synonyms:

• OKL_INS_POLICIES_B — the base (transactional) table holding policy identifiers, dates, amounts, agency and agent references, and descriptive flexfield attribute columns.
• OKL_INS_POLICIES_TL — the translation table supplying language-dependent descriptive text such as IPY_TYPE description, endorsement text, and comments.

The view text selects from IPYB (the base alias) and joins IPYT (the translation alias), projecting the ROWID of the base row as ROW_ID for use by Oracle Forms block-level DML, and IPYB.ID as the primary identifier. Because the view is a join of a base table and its translation table, it is generally treated as non-updatable in the traditional sense; forms perform DML against the base and translation tables directly, while the view serves read access and LOV population.

Key Columns

• ID / ROW_ID — Primary key of the insurance policy row; the ROWID enables row-level identification.
• LEASE_APPLICATION_ID — Foreign key linking the policy or quote to the lease application it covers.
• IPY_TYPE / DESCRIPTION / ENDORSEMENT — Policy type code and its translated description, plus endorsement detail.
• POLICY_NUMBER, NAME_OF_INSURED — Identification data for the coverage.
• PREMIUM, CALCULATED_PREMIUM, COVERED_AMOUNT, DEDUCTIBLE, ADJUSTMENT — Financial measures of the policy.
• DATE_FROM, DATE_TO, DATE_QUOTED, DATE_QUOTE_EXPIRY, ACTIVATION_DATE, CANCELLATION_DATE — Lifecycle and validity dates.
• QUOTE_YN, ON_FILE_YN, AGENT_YN, LESSOR_INSURED_YN, LESSOR_PAYEE_YN, PRIVATE_LABEL_YN — Status and classification flags.
• AGENCY_SITE_ID, SALES_REP_ID, AGENT_SITE_ID, ADJUSTED_BY_ID — Party and site references. AGENT_SITE_ID and AGENCY_SITE_ID identify the agent and agency site (party site) records, enabling joins to site-level party data via HZ tables. These columns are the reason a search for "agent_site_id" surfaces this view.
• CRX_CODE, IPF_CODE, ISS_CODE, IPE_CODE, IPT_ID, IPY_ID, INT_ID, ISU_ID, KHR_ID, KLE_ID — Internal FK codes to currency, factor, status, provider/type, and related lease/contract entities.
• INSURANCE_FACTOR, FACTOR_CODE, FACTOR_VALUE, TERRITORY_CODE — Rating and territory data.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield columns.

Common Use Cases and Queries

Typical scenarios include insurance tracking reports, quote-to-policy conversion checks, and integrations that retrieve agent/agency site references for downstream party lookups.

List active policies for a lease application:

• SELECT id, policy_number, name_of_insured, premium, date_from, date_to FROM apps.okl_ins_policies_v WHERE lease_application_id = :p_lease_app_id AND quote_yn = 'N';

Retrieve agent site references for a policy:

• SELECT id, policy_number, person_id, agent_site_id, agency_site_id FROM apps.okl_ins_policies_v WHERE agent_site_id IS NOT NULL;

Identify quotes approaching expiry:

• SELECT id, policy_number, date_quoted, date_quote_expiry FROM apps.okl_ins_policies_v WHERE quote_yn = 'Y' AND date_quote_expiry < SYSDATE + 30 ORDER BY date_quote_expiry;

All queries should be executed with the APPS schema context or appropriate MOAC operating unit filtering where lease applications are partitioned by organization.