Results for “ap_enc_gl_pay_v”

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

Overview

AP_ENC_GL_PAY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Payables (AP) product module. It consolidates payment-related accounting entries originating from Payables and presents them in a structure compatible with the Oracle Subledger Accounting (SLA) and General Ledger (GL) interface model. The view is exposed as an integration and reporting artifact that maps Payables payment transactions—checks and electronic payments recorded in AP_CHECKS_ALL—to their corresponding journal entry lines held in GL_JE_HEADERS and GL_JE_LINES.

The view carries the constant APPLICATION_ID of 200, identifying Payables as the originating application, and sets TRX_CLASS to 'PAY' to distinguish payment transactions from invoice or adjustment entries. In Oracle EBS 12.1.1 and 12.2.2, views of this naming pattern (AP_ENC_GL_*) are used for reconciliation, subledger-to-GL drill-down, and financial reporting where a unified projection of payment accounting data is required. Because it references CE_STATEMENT_HEADERS, CE_STATEMENT_LINES, and CE_STATEMENT_RECONCILIATIONS, it also supports matching payment activity against bank statement reconciliation records in Cash Management.

Underlying Base Objects

The documented base objects referenced by AP_ENC_GL_PAY_V span several EBS modules. Core Payables objects include AP_CHECKS_ALL, AP_ENCUMBRANCE_LINES_ALL, AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, and AP_TAX_CODES_ALL. General Ledger objects include GL_JE_HEADERS, GL_JE_LINES, GL_IMPORT_REFERENCES, and the GL_LOOKUPS view. Cash Management is represented through CE_STATEMENT_HEADERS, CE_STATEMENT_LINES, and the CE_STATEMENT_RECONCILIATIONS view. Payment method data is drawn from IBY_PAYMENT_METHODS_VL, supplier data from PO_VENDORS, and purchasing context from PO_HEADERS_ALL and PO_DISTRIBUTIONS_ALL.

Security and context are enforced through FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS, ensuring that row-level and organizational (ORG_ID) filtering is applied consistent with the EBS multi-org architecture. The view joins these objects so that each payment journal line is presented with its associated supplier, tax code, payment method, currency conversion details, and document sequence information.

Key Columns

The view exposes JE_HEADER_ID and JE_LINE_NUM, linking each row to a specific GL journal header and line. SET_OF_BOOKS_ID and ORG_ID identify the ledger and operating unit context. TRX_NUMBER_N and TRX_NUMBER_DISPLAYED present the payment number, typically the check number derived from AP_CHECKS_ALL.CHECK_NUMBER. TRX_TYPE_C carries the payment method lookup code and TRX_TYPE_NAME the corresponding payment method name from IBY_PAYMENT_METHODS_VL.

Amount columns ACCOUNTED_CR, ACCOUNTED_DR, ENTERED_CR, and ENTERED_DR are sourced from GL_JE_LINES and represent the accounted and entered debit/credit values. CURRENCY_CODE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE, and CURRENCY_CONVERSION_TYPE describe the currency conversion applied to the journal. CODE_COMBINATION_ID identifies the accounting flexfield combination. Third-party attributes include THIRD_PARTY_TYPE (set to 'SUPPLIER'), THIRD_PARTY_NUMBER from PO_VENDORS.SEGMENT1, and THIRD_PARTY_NAME from VENDOR_NAME. Audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY are carried from AP_CHECKS_ALL, along with REQUEST_ID and PROGRAM_ID from the concurrent request context.

Common Use Cases and Queries

The user search term "ce_statement_reconciliations" indicates interest in matching payment accounting entries to bank statement reconciliations. A typical query joins the view to CE_STATEMENT_RECONCILIATIONS to trace reconciled payments.

• Payment-to-GL reconciliation: verify that each check has corresponding journal lines and amounts balance.
• Bank reconciliation analysis: link payment rows to CE_STATEMENT_LINES via check number and date to identify unreconciled items.
• Supplier payment reporting: aggregate by TRX_DATE and VENDOR_NAME for period-end cash disbursement reports.
• Currency exposure review: analyze CURRENCY_CODE and CURRENCY_CONVERSION_RATE for foreign currency payments.

Sample query:

SELECT v.trx_number_displayed, v.trx_date, v.third_party_name, v.accounted_dr, v.accounted_cr, v.currency_code FROM apps.ap_enc_gl_pay_v v WHERE v.org_id = :org_id AND v.trx_date BETWEEN :start_date AND :end_date ORDER BY v.trx_date;