Search Results iby_payment_functions




Overview
Explore in AI Chat

Overview

IBY_USER_PAY_FUNS_SEC_V is an APPS-owned security and lookup view in Oracle EBS Payments (IBY). It exposes the set of valid payment function codes for use in Oracle Payments and related modules. The view is a thin projection over the FND_LOOKUPS lookup type IBY_PAYMENT_FUNCTIONS, returning only the LOOKUP_CODE values that represent payment functions available to the user's session. It is commonly used to populate LOVs, validate payment function parameters, and drive conditional processing logic in payment process profiles, payment formats, and payment instruction APIs.

Because the view selects directly from FND_LOOKUPS, it is always consistent with the seeded lookup definitions. It does not perform user-specific filtering in the documented SQL; the "USER" and "SEC" naming reflects its use in user-facing security context rather than row-level predicates in the view text itself. In EBS 12.1.1 and 12.2.2, the definition is identical, so customizations and personalizations relying on the view behave consistently across both releases.

Underlying Base Objects

The documented ETRM 12.2.2 metadata identifies the following referenced base objects:

  • FND_LOOKUPS (View) — The application lookup view that stores lookup types and their associated lookup codes. The view filters on LOOKUP_TYPE = 'IBY_PAYMENT_FUNCTIONS'.
  • FND_GLOBAL (Package) — The standard Oracle Applications global context package. Although not referenced by name in the view text, it is documented as a referenced object because the view is typically consumed within a session context established by FND_GLOBAL, providing user, responsibility, and application IDs.

The view therefore inherits all standard FND_LOOKUPS behavior: lookup codes may be enabled or disabled, and only enabled rows are generally visible to end users through the standard LOV mechanism. No IBY base tables are directly referenced; IBY_PAYMENT_FUNCTIONS is a lookup type, not a table.

Key Columns

The view exposes a single documented column:

  • LOOKUP_CODE — A short alphanumeric code identifying a payment function. Values correspond to the seeded IBY_PAYMENT_FUNCTIONS lookup codes (for example, codes representing payment instruction creation, formatting, validation, and settlement functions). This is the only column projected by the view, making it a lightweight, single-column lookup source suitable for embedded subqueries and LOV definitions.

Because the view is single-column, it does not expose lookup meaning, description, enabled flag, or display sequence. Callers requiring those attributes must join to FND_LOOKUPS or FND_LOOKUP_VALUES directly.

Common Use Cases and Queries

The view is typically used to validate or display payment function codes in custom reports, concurrent programs, and payment format or process profile setups. A representative query retrieving all available payment functions is:

  • SELECT lookup_code FROM apps.iby_user_pay_funs_sec_v ORDER BY lookup_code;

A common validation pattern checks whether a value supplied by a user or parameter is a valid payment function:

  • SELECT 1 FROM apps.iby_user_pay_funs_sec_v WHERE lookup_code = :p_payment_function;

To obtain the human-readable meaning for each function code, join to the lookup table:

  • SELECT v.lookup_code, lv.meaning FROM apps.iby_user_pay_funs_sec_v v, fnd_lookup_values lv WHERE lv.lookup_type = 'IBY_PAYMENT_FUNCTIONS' AND lv.lookup_code = v.lookup_code AND lv.language = USERENV('LANG') AND lv.view_application_id = 0;

Other scenarios include populating LOVs in custom Forms or OAF pages, driving conditional branching in payment format programs based on the selected payment function, and auditing which payment functions are currently enabled by comparing against FND_LOOKUPS. Administrators should note that adding or disabling entries under the IBY_PAYMENT_FUNCTIONS lookup type immediately affects the rows returned by this view.