Search Results iby_user_pay_funs_sec_v




Overview
Explore in AI Chat

Overview

IBY_USER_PAY_FUNS_SEC_V is a seeded Oracle E-Business Suite view owned by the APPS schema within the IBY (Payments) product family. It exposes a distinct list of payment function lookup codes derived from the FND_LOOKUPS foundation table, filtered to the lookup type IBY_PAYMENT_FUNCTIONS. The view functions as a security and enumeration layer over the payment function reference data, allowing Oracle Payments and dependent modules to identify which payment functions exist in the current application instance without querying FND_LOOKUPS directly.

In Oracle EBS 12.1.1 and 12.2.2, this view is typically referenced by internal Payments code paths, concurrent programs, and reporting extracts that must reconcile or display the set of valid payment functions. Because it is a simple view over a lookup table rather than a transactional object, it is read-only and carries no data of its own; its contents change only when the underlying lookup rows are added, modified, or end-dated in the FND_LOOKUPS table.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over two referenced base objects:

  • FND_LOOKUPS (VIEW) — the foundation lookup view that stores lookup codes, meanings, descriptions, enabled flags, and date ranges. IBY_USER_PAY_FUNS_SEC_V selects the LOOKUP_CODE from this object where LOOKUP_TYPE = 'IBY_PAYMENT_FUNCTIONS'.
  • FND_GLOBAL (PACKAGE) — the standard EBS global context package, referenced to resolve the current session's application and security context when the lookup view is accessed.

The view text documented in ETRM is essentially: SELECT L.LOOKUP_CODE FROM FND_LOOKUPS L WHERE L.LOOKUP_TYPE = 'IBY_PAYMENT_FUNCTIONS'. This confirms the view is a thin projection: it does not join to IBY payment tables, does not aggregate, and does not apply user-specific filtering beyond what FND_LOOKUPS itself enforces. Actual payment function assignments to users or responsibilities are held elsewhere in the IBY schema; this view only enumerates the available function codes.

Key Columns

  • PAYMENT_FUNCTION — the single documented column exposed by the view. It returns the lookup code values defined under the IBY_PAYMENT_FUNCTIONS lookup type, such as payment function identifiers used to control Payments functionality.

Because the view projects only the lookup code, attributes such as lookup meaning, description, enabled status, and start/end dates are not surfaced. Consumers needing those descriptive attributes must query FND_LOOKUPS directly.

Common Use Cases and Queries

Typical uses include validating that expected payment functions are seeded, driving dynamic lists in extensions, and feeding extract or reconciliation reports.

  • Listing all seeded payment functions:
    SELECT payment_function FROM apps.iby_user_pay_funs_sec_v;
  • Confirming a specific function exists:
    SELECT payment_function FROM apps.iby_user_pay_funs_sec_v WHERE payment_function = :p_function;
  • Joining to lookup attributes for descriptions:
    SELECT v.payment_function, l.meaning, l.enabled_flag FROM apps.iby_user_pay_funs_sec_v v, apps.fnd_lookups l WHERE l.lookup_type = 'IBY_PAYMENT_FUNCTIONS' AND l.lookup_code = v.payment_function;

As with all FND_LOOKUPS-derived objects, results reflect only active lookup configuration at query time; historical or end-dated function codes are excluded by the base view's filtering.