Results for “pay_group_lookup_code”

50+ results




Overview
Explore in AI Chat

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

Overview

The view OKL_BPD_PAY_GRP_LOOKUP_CODES_V is a lightweight lookup view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment. It is part of the OKL product family — Oracle Leasing and Finance Management — and exists primarily to expose the set of currently valid "Pay Group" lookup codes to reporting, integration, and application logic layers without requiring those consumers to query the underlying Flexfields lookup infrastructure directly.

In the leasing and finance domain, the pay group classification is used to categorize payment arrangements, schedules, and related financial instruments. Because these values are maintained as Oracle Application Object Library (FND) lookups rather than as rows in a dedicated transactional table, the view provides a stable, semantic interface over what would otherwise be a generic, type-discriminated lookup table. In EBS 12.1.1 and 12.2.2 this pattern is common: a product-specific view narrows the FND lookup universe to a single business concept and presents it with an application-meaningful column name.

Underlying Base Objects

The view is defined over a single referenced base object, FND_LOOKUP_VALUES, accessed through a synonym. The ETRM metadata records the view text as follows:

Three predicates define the view's behaviour. First, the lookup type is constrained to the literal PAY GROUP, isolating this view from all other lookup categories stored in the same table. Second, ENABLED_FLAG = 'Y' restricts output to lookups that have not been administratively disabled. Third, the date predicate NVL(END_DATE_ACTIVE, SYSDATE+1) > SYSDATE eliminates entries whose end-date has passed, while treating a null end date as effectively open-ended. Consequently, the view always reflects the currently active pay group codes at query execution time.

Key Columns

The view exposes exactly one column, PAY_GROUP_LOOKUP_CODE, which is the LOOKUP_CODE column of FND_LOOKUP_VALUES aliased to a domain-specific name.

  • PAY_GROUP_LOOKUP_CODE — The short, stored code value identifying a pay group. This is the value typically persisted on leasing transaction records and joined against for reporting.

Because the view surfaces only the code and not the associated MEANING or DESCRIPTION, consumers requiring display text must join back to FND_LOOKUP_VALUES on LOOKUP_TYPE = 'PAY GROUP' and the matching lookup code. This design keeps the view minimal and oriented toward code-list validation.

Common Use Cases and Queries

Typical uses include populating a list of valid values in a concurrent program parameter, validating a pay group code supplied by an inbound interface, and driving a report filter. A simple enumeration of active codes is:

  • SELECT pay_group_lookup_code FROM apps.okl_bpd_pay_grp_lookup_codes_v ORDER BY pay_group_lookup_code;

A validation query confirming that a given code is currently active:

  • SELECT COUNT(*) FROM apps.okl_bpd_pay_grp_lookup_codes_v WHERE pay_group_lookup_code = :p_pay_group;

To retrieve descriptive text alongside the code, join to the base table:

  • SELECT v.pay_group_lookup_code, f.meaning FROM apps.okl_bpd_pay_grp_lookup_codes_v v, apps.fnd_lookup_values f WHERE f.lookup_type = 'PAY GROUP' AND f.lookup_code = v.pay_group_lookup_code AND f.language = USERENV('LANG');

Because the view is unbounded by any partitioning or profile filter beyond the lookup type and date predicates, it remains inexpensive to query and suitable for embedding in both online validation logic and batch reporting in EBS 12.1.1 and 12.2.2.