Results for “okl_open_int_prty”

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

Overview

OKL_OPEN_INT_PRTY is a staging interface table within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 leasing and finance management module (OKL). Its documented purpose is to hold open interface guarantor details that are subsequently reported to a credit bureau or transferred to an external agency. The table therefore functions as a transient holding area where guarantor party information is assembled, validated, and dispatched through downstream integration processes rather than as a permanent transactional record.

In terms of Data Vault modeling heuristics, the metadata classifies OKL_OPEN_INT_PRTY as a standalone structure, mined from its foreign key topology. Modeling teams may regard it as effectively functioning as a satellite-like staging object, since it carries descriptive guarantor attributes keyed against a parent contract, rather than acting as an independent hub or a true associative link. It is not a candidate hub in its own right; it exists to denormalize guarantor detail for a specific outbound integration event.

Key Information Stored

The table is defined in the OKL schema and contains 57 documented columns. The most significant of these are:

• ID — the surrogate primary key, enforced by the OKL_OIP_PK constraint, uniquely identifying each interface row.
• KHR_ID — the foreign key linking the record back to OKL_PRTFL_CNTRCTS_B, identifying the contract to which the guarantor relates.
• PARTY_ID — the guarantor party reference. Together with KHR_ID, this forms the business-key candidate captured by the unique index OKL_OIP_U01 (KHR_ID, PARTY_ID), ensuring one guarantor entry per contract within the interface.
• PARTY_NAME — the guarantor name as presented to the credit bureau or external agency.
• Address components — ADDRESS1 through ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, POSTAL_PLUS4_CODE, COUNTRY, and granular elements such as STREET, HOUSE_NUMBER, BUILDING, FLOOR, SUITE, and ROOM.
• Contact fields — PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, and PHONE_EXTENSION.
• Multi-org and audit columns — ORG_ID, OBJECT_VERSION_NUMBER, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and fifteen descriptor columns (ATTRIBUTE1 through ATTRIBUTE15) reserved for client extensions.

Common Use Cases and Queries

Typical use cases revolve around credit bureau reporting and guarantor data transfers. A common pattern is to extract pending interface rows joined to the contract table to reconcile guarantors against active contracts:

• SELECT o.ID, o.KHR_ID, o.PARTY_ID, o.PARTY_NAME, o.CITY, o.COUNTRY FROM OKL.OKL_OPEN_INT_PRTY o WHERE o.KHR_ID = :contract_id;
• Reporting by request to trace which concurrent program populated the interface: SELECT REQUEST_ID, PROGRAM_ID, COUNT(*) FROM OKL.OKL_OPEN_INT_PRTY GROUP BY REQUEST_ID, PROGRAM_ID;
• Audit of records updated after a given date using LAST_UPDATE_DATE, and multi-org filtering using ORG_ID.

Related Objects

The most significant related objects, based on the documented relationships, include:

• OKL_PRTFL_CNTRCTS_B — referenced through the foreign key OKL_OPEN_INT_PRTY.KHR_ID, the principal parent for contract-to-guarantor association.
• OKL_OIP_PK and OKL_OIP_U01 — the primary key and unique business-key indexes governing this table.
• Additional OKL interface and reporting tables sharing the ORG_ID, REQUEST_ID, and PROGRAM_ID audit conventions, which support concurrent-program based data flows to external agencies.