Search Results ap_pbatch_set_lines




Overview
Explore in AI Chat

Overview

APPS.AP_PBATCH_SET_LINES_V is a reporting view in Oracle E-Business Suite (12.1.1 / 12.2.2) that denormalizes the payment batch set line definition table, AP_PBATCH_SET_LINES, by joining it to the bank account, check stock, exchange rate type, and supplier master records needed to make a batch set line meaningful to a user or a downstream process. A payment batch set allows a Payables user to group multiple payment batches under a single named set, and each row of AP_PBATCH_SET_LINES represents one batch definition line within that set: which bank account and check stock to use, which printer to direct, the payment selection criteria (priorities, amount limits, outlay caps), and flags governing zero-amount invoices, future-dated payments, and whether payment should occur only when due.

The view is used principally for reporting and for integration scenarios where external printing, treasury, or reconciliation systems need a flat, human-readable picture of payment batch set configuration. Because the base table stores only surrogate identifiers for the bank account, check stock, exchange rate type, and supplier, the view supplies the descriptive names (BANK_ACCOUNT_NAME, DOCUMENT_NAME, USER_RATE_TYPE, VENDOR_NAME) required by those consumers.

Underlying Base Objects

The view is defined over five referenced objects, resolved through APPS synonyms as documented for 12.2.2:

  • AP_PBATCH_SET_LINES — the driving table; each row is one batch line within a payment batch set.
  • AP_BANK_ACCOUNTS — joined on bank_account_id to supply bank_account_name.
  • AP_CHECK_STOCKS — joined on check_stock_id to supply document_name and future_dated_payments_flag. This is the object referenced by the search term "ap_check_stocks".
  • GL_DAILY_CONVERSION_TYPES — outer-joined on exchange_rate_type to supply user_conversion_type, aliased as USER_RATE_TYPE.
  • PO_VENDORS — itself a view over supplier master data, outer-joined on vendor_id to supply vendor_name.

The two outer joins (+) are significant: a batch set line may exist without a matching currency conversion type or supplier, so results are preserved even when those lookups are absent. The ROW_ID column exposes the base table rowid, which is useful for identifying the underlying AP_PBATCH_SET_LINES record when updating configuration.

Key Columns

Common Use Cases and Queries

Typical uses include auditing payment batch set configuration, reproducing the bank and check stock assigned to each batch, and feeding external check-printing or treasury systems. Querying by operating unit is standard practice.

  • List all lines for a set: SELECT batch_name, bank_account_name, document_name, printer FROM ap_pbatch_set_lines_v WHERE batch_set_id = :p_set_id ORDER BY batch_set_line_id;
  • Find lines tied to a particular check stock: SELECT batch_set_id, batch_name, document_name FROM ap_pbatch_set_lines_v WHERE check_stock_id = :p_check_stock_id;
  • Report multi-org configuration: SELECT org_id, COUNT(*) FROM ap_pbatch_set_lines_v GROUP BY org_id;
  • Identify lines allowing future-dated payments: SELECT batch_name, future_dated_payments_flag FROM ap_pbatch_set_lines_v WHERE future_pmts_allowed = 'Y';

Because the view is read-only and exposes the base table rowid, it should be used for inquiry and reporting only; all maintenance of batch set definition is performed against the base AP_PBATCH_SET_LINES table through the standard Payables forms.