Results for “okl_la_payment_headers_uv”

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

Overview

OKL_LA_PAYMENT_HEADERS_UV is a user interface view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL - Leasing and Finance Management product family. Its documented role is to expose payment header information for the leasing and finance application's user interface layer. The view provides a flattened, query-friendly representation of lease payment headers by joining rule group data to rule data filtered on a specific rule information category, namely 'LASLH'.

Functionally, the view sits above Oracle Contracts (OKC) rule structures and translates them into a leasing-oriented projection. Rather than querying the underlying rule tables directly and reproducing the join logic and category filter, consumers can read payment header attributes from a single object. This makes it suitable for UI data blocks, concurrent program extracts, and integration interfaces that require the payment identifier and its associated rule grouping context without traversing the full OKC rule model.

Because the object is a view rather than a table, it holds no data of its own. All values are derived at query time from the base objects, so results always reflect the current committed state of the underlying rules and rule groups. In EBS 12.1.1 and 12.2.2 the object is documented as VALID in the APPS schema.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through synonyms in the APPS schema:

• OKC_RULE_GROUPS_B — aliased as RG, the source of the rule group identifier and the associated contract and transaction context columns.
• OKC_RULES_B — aliased as SLH, the source of the payment header rule record, the rule group reference, and the payment identifier.

The join is performed on the rule group identifier and a shared DNZ_CHR_ID value: RG.ID equals SLH.RGP_ID, and SLH.DNZ_CHR_ID equals RG.DNZ_CHR_ID. The view additionally constrains SLH.RULE_INFORMATION_CATEGORY to 'LASLH', which is the information category that identifies lease payment header rules. This filter is what narrows the general OKC rule population down to payment header records relevant to leasing. Both base objects are the "_B" variant tables, indicating the base (non-translated) rule and rule group definitions.

Key Columns

The view exposes six columns. Each carries a specific meaning in the leasing data model:

• RULE_GROUP_ID — RG.ID, the primary identifier of the rule group to which the payment header belongs.
• DNZ_CHR_ID — the contract or transaction header identifier that ties the rule group and rule together in the same context.
• CHR_ID — the contract header identifier carried on the rule group record, indicating the owning contract.
• CLE_ID — a leasing-related identifier on the rule group, typically associated with the lease or contract line entity context.
• SLH_ID — SLH.ID, the identifier of the lease payment header rule record itself; this is the column most commonly used as the primary correlation key by consumers.
• PAYMENT_ID — SLH.OBJECT1_ID1, the payment identifier referenced by the rule. This is the business-facing payment reference associated with the header.

Common Use Cases and Queries

Typical usage centres on retrieving payment headers for a given contract or lease context, and on resolving a payment identifier from its rule group. The following examples illustrate practical access patterns.

Listing all payment headers for a contract context:

• SELECT slh_id, payment_id, rule_group_id, chr_id FROM okl_la_payment_headers_uv WHERE dnz_chr_id = :p_chr_id;

Retrieving the payment header for a specific rule group:

• SELECT slh_id, payment_id FROM okl_la_payment_headers_uv WHERE rule_group_id = :p_rule_group_id;

Joining invoice or payment data to source documents by payment identifier:

• SELECT h.payment_id, h.slh_id, h.chr_id FROM okl_la_payment_headers_uv h WHERE h.payment_id = :p_payment_id;

Integrations should treat this view as read-only and rely on the documented category filter, since the 'LASLH' restriction is what separates payment header rules from other rule types in OKC. Queries that omit a predicate on DNZ_CHR_ID, CHR_ID, or RULE_GROUP_ID may scan a large rule population and should be tuned accordingly.