Search Results inactivate_open_items

Overview

OKL_INSURANCE_POLICIES_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Lease and Finance Management (OKL) module, which is part of the Enterprise Traffic and Revenue Management (ETRM) family of applications. The package encapsulates the core business logic for managing insurance policies associated with leased assets and contracts. It is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the invoking user, a common convention for internal EBS private APIs that are called from public wrapper packages, forms, or concurrent programs.

The package is responsible for the lifecycle of insurance policy records maintained against lease contracts. This includes creating and cancelling policies, processing credit memos and refunds, and managing the inactivation of associated open items. The presence of the INACTIVATE_OPEN_ITEMS procedure directly addresses the search term supplied, and it reflects the package's role in keeping the Accounts Receivable and lease contract sub-ledgers synchronized when a policy is cancelled or otherwise terminated. The package also contains party-merge handlers, enabling the consolidation of insurance party, agent, and site records when Oracle Trading Community Architecture (TCA) merge operations are executed.

Key Procedures and Functions

The documented procedures fall into several functional groupings:

• Policy lifecycle: CANCEL_POLICY, CANCEL_POLICIES, and CANCEL_CREATE_POLICIES manage the cancellation and re-creation of insurance policy records, ensuring the correct status transitions and history are retained.
• Open item management: INACTIVATE_OPEN_ITEMS deactivates receivable open items tied to policy transactions, an essential step when policies are cancelled and the corresponding invoices or credit memos must be neutralized.
• Financial settlement: ON_ACCOUNT_CREDIT_MEMO, GET_REFUND, PAY_CUST_REFUND, and INSERT_AP_REQUEST handle credit memo application, refund determination, customer refund payment, and AP invoice request creation for insurance-related financial activity.
• Validation: CHECK_CLAIMS verifies claims data associated with policies.
• Record maintenance: DELETE_POLICY removes policy records that are no longer required.
• Party merge handlers: OKL_INSURANCE_PARTY_MERGE, OKL_INSURANCE_PARTY_SITE_MERGE, OKL_INSURANCE_AGENT_MERGE, and OKL_INSURANCE_AGENT_SITE_MERGE support TCA merge batches, remapping insurance party and agent references when source parties are merged into surviving parties.

Tables Accessed

The package reads and writes through APPS synonyms across contract, insurance, and reference tables. Contract data resides in OKC_K_HEADERS_B, OKC_K_HEADERS_BH, OKC_K_ITEMS, OKC_K_ITEMS_H, OKC_K_LINES_B, OKC_K_LINES_BH, OKC_K_PARTY_ROLES_B, and OKC_LINE_STYLES_B, which define the lease contract header, line, item, and party role structures that insurance policies attach to. OKC_CONTACTS and OKC_CONTACT_SOURCES are used for contact information associated with insurance parties and agents. OKL_INS_ASSETS links insurance policies to specific leased assets. Reference data is drawn from OKC_STATUSES_B, AK_ATTRIBUTES_TL, and FND_APPLICATION. HZ_MERGE_BATCH records the TCA merge batch context used by the party-merge procedures. The package exposes SUBTYPE declarations for taiv_rec_type and tilv_rec_type from the AR invoice public packages, indicating integration with Oracle Receivables for credit memo and invoice processing.

Usage Notes

As a private API, OKL_INSURANCE_POLICIES_PVT is not intended for direct invocation by external or customer code. It is called by the public OKL insurance policy APIs, by the Lease Management forms when users cancel or adjust policies, and by the TCA party merge concurrent program when insurance parties or agents are consolidated. The INACTIVATE_OPEN_ITEMS procedure is typically reached indirectly through CANCEL_POLICY or CANCEL_POLICIES, which trigger open item inactivation as part of the cancellation flow. The package is referenced by one other package in the ETRM schema, confirming its role as a supporting internal component. Developers extending insurance functionality should call the public wrapper APIs rather than this package directly, and should not rely on its private signatures across upgrades, as indicated by the package's internal version header.