Search Results iby_payments_sec_v




Overview
Explore in AI Chat

Overview

IBY_PAYMENTS_SEC_V is a security-enabled view in the Oracle Payments (IBY) module of Oracle E-Business Suite, owned by the APPS schema and validated across release levels 12.1.1 and 12.2.2. It exposes payment records drawn from the IBY_PAYMENTS_ALL synonym while enforcing row-level access control, so that a user querying the view sees only those payments they are authorized to view under their assigned security profile and payment function privileges.

The view is the preferred read interface for reporting, integrations, and custom extensions that require payment data without bypassing Payments security. Rather than granting direct access to IBY_PAYMENTS_ALL, implementers query IBY_PAYMENTS_SEC_V to inherit operating unit, user, and function-based restrictions automatically. This makes it central to disbursement analysis, treasury reporting, bank instruction validation, and stop/void audit extracts. The metadata also indicates that the view surfaces a broad set of payment columns, including several relevant to discount and remittance processing; note that the column DISCOUNT_AMOUNT_TAKEN is not among the columns enumerated in the documented view text, and is instead sourced from the underlying payments table when full payment detail is required.

Underlying Base Objects

The documented referenced base objects establish both the data source and the security mechanism:

  • IBY_PAYMENTS_ALL (SYNONYM) — the underlying payments entity from which all payment attributes are selected.
  • IBY_USER_PAY_FUNS_SEC_V (VIEW) — resolves the set of payment functions accessible to the current user, forming a core filter predicate.
  • CE_SECURITY_PROFILES_V (VIEW) — supplies cash management security profile context used to restrict bank account and payment visibility.
  • FND_GLOBAL and FND_PROFILE (PACKAGES) — provide session values such as user ID, responsibility, and profile option settings used within the view's WHERE clause.
  • FND_ACCESS_CONTROL_UTIL (PACKAGE) — supplies access control helper logic applied to restrict the returned rows.
  • MO_GLOBAL (PACKAGE) — enforces multi-org / operating unit access, ensuring only payments belonging to accessible organizations are returned.
  • XTR_USER_ACCESS (PACKAGE) — provides treasury user access checks that further narrow the result set.

Key Columns

The view exposes the principal payment attributes, including:

Because discount-related fields such as DISCOUNT_AMOUNT_TAKEN are not explicitly listed in the documented column set, they should be obtained by joining to IBY_PAYMENTS_ALL when both security filtering and discount analysis are required.

Common Use Cases and Queries

Typical applications include payment status dashboards, stop-payment audit reports, remittance advice validation, and integration extracts feeding treasury or bank reconciliation systems.

Listing payment documents and stop status for the current user:

  • SELECT paper_document_number, payment_due_date, stop_request_placed_flag, stop_request_reason FROM iby_payments_sec_v WHERE stop_request_placed_flag = 'Y';

Joining to the base table to include discount amounts alongside secured payment data:

  • SELECT s.paper_document_number, s.payment_due_date, p.discount_amount_taken FROM iby_payments_sec_v s, iby_payments_all p WHERE s.payment_id = p.payment_id AND p.discount_amount_taken > 0;

Extracting voided payments for audit purposes:

  • SELECT paper_document_number, void_reason, voided_by, void_date FROM iby_payments_sec_v WHERE void_date IS NOT NULL;