Results for “cust_object1_id1”

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

Overview

The view OKL_POOL_CUSTOMERS_UV is a database object owned by the APPS schema within the Oracle Lease and Finance Management (OKL) product family. It is documented as a "Securitization - Pool Customers UI view" and is catalogued with a status of VALID in the ETRM 12.2.2 documentation set, reflecting its continued availability across Oracle EBS 12.1.1 and 12.2.2 environments. The view presents a denormalized, presentation-oriented projection of contract lessee data, joining party-role records to the trading community party model to expose customer attributes required by securitization pool maintenance screens.

The "UV" suffix follows the Oracle Applications convention for a UI (user interface) view, indicating that the object is intended to back a specific form, OAF page, or inquiry screen rather than to serve as a general-purpose integration interface. In the securitization workflow, pools group lease contracts whose receivables are pledged or sold; the customer detail associated with each contract in the pool must be displayed and validated by the UI. This view supplies exactly that projection. A user searching for the token cust_object1_id1 — which corresponds to the aliased column CUST_OBJECT1_ID1 — is typically tracing how the party identifier of a lessee is surfaced and filtered on securitization pool customer screens.

Underlying Base Objects

The view text is defined as a join over two documented base objects, both presented through APPS synonyms:

• OKC_K_PARTY_ROLES_B — the contract party roles base table, which records the association between a contract/party role and the underlying entity identifiers. The view filters this table with RLE_CODE = 'LESSEE', restricting the result set to lessee assignments, and with OBJECT1_ID2 = '#', the standard placeholder that Oracle uses for the object identifier attribute set.
• HZ_PARTIES — the Trading Community Architecture (TCA) master party table, supplying the party name and Standard Industrial Classification code for the identified customer.

The join predicate is CPLB.OBJECT1_ID1 = HZPB.PARTY_ID, establishing the referential link between the role record and the TCA party. Because both underlying objects are referenced through APPS synonyms, the view operates entirely within the APPS namespace and requires no additional grants when queried by other APPS-owned objects.

Key Columns

• DNZ_CHR_ID — the contract (CHR) identifier from the party-role record. In securitization terms this identifies the lease contract to which the pool customer belongs, and it is the natural grouping key when reconciling contracts within a pool.
• CUST_OBJECT1_ID1 — the aliased HZPB.PARTY_ID, the unique TCA party identifier of the lessee. This is the column referenced by the search token cust_object1_id1 and is the primary key used to resolve the customer record on the UI.
• LESSEE — the aliased HZPB.PARTY_NAME, providing the display name of the customer for list-of-values and form field presentation.
• SIC_CODE — the Standard Industrial Classification code drawn from the party record, commonly used for customer classification, concentration analysis, and reporting segmentation within a securitization pool.

Common Use Cases and Queries

The view is most often queried when diagnosing why a customer does or does not appear on the securitization pool customers screen, or when extracting the contract-to-customer mapping for reconciliation. A typical diagnostic retrieves all lessee rows for a specific contract:

• SELECT dnz_chr_id, cust_object1_id1, lessee, sic_code FROM okl_pool_customers_uv WHERE dnz_chr_id = :chr_id;
• SELECT cust_object1_id1, lessee, sic_code FROM okl_pool_customers_uv WHERE lessee LIKE :name_fragment ORDER BY lessee;
• Joining back to HZ_PARTIES or HZ_CUST_ACCOUNTS on CUST_OBJECT1_ID1 = PARTY_ID to extend the view with additional TCA attributes not exposed here.

Because the view hard-codes the RLE_CODE = 'LESSEE' filter and does not include an ORG_ID predicate, it returns cross-operating-unit data; queries intended for single-organization reporting must join to the contract header to apply the appropriate organization restriction. The absence of DISTINCT likewise means a contract with multiple qualifying role rows can produce duplicate party entries, so count-based validations should account for this behavior.