Results for “cust_jtot_object1_code”

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

Overview

OKL_K_HDR_CRDTLN_UV is a user interface (UI) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product. Its documented purpose is to supply the credit line list of values (LOV) presented when users attach a credit line to a lease contract. Rather than functioning as a transactional base table, the view is a read-only presentation layer that flattens data spread across contract headers, lease-specific header attributes, party role assignments, and trading community (TCA) party and customer account records.

For reporting and integration purposes, the view is significant because it isolates contracts that qualify as active, non-template credit line contracts of the sell-side (BUY_OR_SELL = 'S'), each associated with a lessee party. The presence of the REVOLVING_CREDIT_YN column makes the view directly relevant to searches concerning whether a given credit line is revolving, since that flag is sourced from the OKL-specific header table and exposed alongside the contract-level descriptive and customer identification data.

Underlying Base Objects

The view is defined over the following documented base objects, all resolved through APPS synonyms:

• OKC_K_HEADERS_B – the core contract header table, supplying contract ID, number, SCS code, currency, status, template flag, buy/sell indicator, and start/end dates.
• OKC_K_HEADERS_TL – the translated header table, supplying short and long descriptions filtered by the session language via USERENV('LANG').
• OKL_K_HEADERS – the leasing-specific header extension, supplying the REVOLVING_CREDIT_YN attribute.
• OKC_K_PARTY_ROLES_B – the contract party role table, restricted to the 'LESSEE' role.
• HZ_PARTIES – the TCA party master, supplying the party ID and party name used as the customer name.
• HZ_CUST_ACCOUNTS – the TCA customer account table, supplying the account number.

The join structure links OKC_K_HEADERS_B to OKL_K_HEADERS and OKC_K_HEADERS_TL on the contract ID (ID), and to OKC_K_PARTY_ROLES_B on the DNZ_CHR_ID and CHR_ID columns. Party information is resolved through the role object identifiers OBJECT1_ID1 and OBJECT1_ID2, with OBJECT1_ID2 fixed to '#' and OBJECT1_ID1 matching HZ_PARTIES.PARTY_ID, which in turn ties to HZ_CUST_ACCOUNTS through PARTY_ID and CUST_ACCOUNT_ID.

Key Columns

• ID – the contract header identifier, the primary join key across the underlying tables.
• CONTRACT_NUMBER, SHORT_DESCRIPTION, DESCRIPTION – the contract number and its translated descriptive text.
• SCS_CODE – the contract subtype code; the view is filtered to 'CREDITLINE_CONTRACT'.
• CURRENCY_CODE, START_DATE, END_DATE – credit line currency and effective period.
• STS_CODE, TEMPLATE_YN, BUY_OR_SELL – status, template indicator, and buy/sell flag; the view restricts results to ACTIVE, non-template, sell-side records.
• REVOLVING_CREDIT_YN – the leasing header flag indicating whether the credit line is revolving, sourced from OKL_K_HEADERS.
• CUST_OBJECT1_ID1, CUST_OBJECT1_ID2, CUST_JTOT_OBJECT1_CODE – the lessee party role object identifiers used to resolve the customer.
• CUST_NAME, CUST_ACC_NUMBER – the party name and customer account number from TCA.

Common Use Cases and Queries

Typical usage centers on identifying active credit line contracts available for attachment to a lease and on reporting the revolving characteristic of those lines by customer. A representative query returning revolving credit lines with their associated lessee follows:

• SELECT id, contract_number, cust_name, currency_code, revolving_credit_yn FROM okl_k_hdr_crdtln_uv WHERE revolving_credit_yn = 'Y';
• SELECT contract_number, cust_acc_number, start_date, end_date FROM okl_k_hdr_crdtln_uv WHERE cust_name = :p_customer_name;
• SELECT currency_code, COUNT(*) FROM okl_k_hdr_crdtln_uv GROUP BY currency_code;

Because the view already enforces the credit line subtype, active status, non-template, sell-side, and lessee role filters, consumers need not repeat these predicates in custom SQL, ensuring consistency with the standard Lease Management credit line LOV behavior.