Search Results vendor_total

Overview

AP_XML_PAYMENTLINE2_LEVEL_V is a Payables (AP) reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that consolidates payment instruction and remittance data produced by the Oracle Payments / Payables payment process. It sits in the layered family of XML-oriented views used to build the payment instruction file and remittance advice XML transmitted to banks and suppliers. The "LEVEL_V" naming and the reference to AP_XML_BATCHLEVEL2_V indicate that the view supplies the payment-line level detail that is nested beneath a batch (payment run) level record.

The view joins selection, bank, supplier-site, and check-format information into a single row per selected payment. Because it exposes fields such as PAYMENT_NUMBER, PAYMENT_DATE, PAYMENT_CURRENCY, bank account identifiers, EDI remittance method, and bank charge bearer, it is directly relevant to payment-format and payment-file processing. In practice, such views underpin the outbound payment file or XML remittance generation, and are useful for reconciliation and diagnostics when a payment run must be traced from selected invoice through to the transmitted instruction.

In the documented environment, the view is listed as "Not implemented in this database," meaning no compiled definition is present locally. The records below therefore reflect the documented view text rather than a live object. Column documentation in the source metadata is truncated, providing the first ten column names with the remainder (for example payment currency truncation field names) incomplete.

Underlying Base Objects

The documented view text is defined over the following base objects:

• AP_SELECTED_INVOICE_CHECKS (ASIC) — payment selection and check/instruction records.
• AP_INVOICE_SELECTION_CRITERIA (AISC) — payment run selection criteria and check stock references.
• AP_BANK_ACCOUNTS (ABA) — internal/external bank account details.
• AP_BANK_BRANCHES (ABB) — bank branch and contact data.
• AP_CHECK_STOCKS (ACS) — check stock inventory linking to a format.
• AP_CHECK_FORMATS (ACF) — check/payment format definitions, including separate remittance advice flag.
• PO_VENDOR_SITES (PVS) — supplier site and EDI remittance attributes.
• PO_VENDORS (PV) — supplier header, including vendor type.
• AP_XML_BATCHLEVEL2_V (APBV) — the batch (checkrun) level companion view.

The join keys tie the checkrun name across AP_SELECTED_INVOICE_CHECKS, AP_INVOICE_SELECTION_CRITERIA, and AP_XML_BATCHLEVEL2_V; the bank account to its branch; the check stock to its format; and the supplier site to the supplier. Restricting ASIC.OK_TO_PAY_FLAG to 'Y' or 'F' limits output to payable selections. The documented metadata lists no separate referenced objects, so relationships are inferred from the embedded SQL.

Key Columns

• CHECKRUN_NAME / BATCH_NAME, CHECKRUN_ID, BATCH_ID — identify the payment run/batch.
• SELECTED_CHECK_ID — links to the individual selected payment record.
• VENDOR_AMOUNT, CHECK_AMOUNT, PAYMENT_AMOUNT, VENDOR_TOTAL — monetary values at payment level.
• CHECK_NUMBER / PAYMENT_NUMBER — the instrument or payment reference.
• DUE_DATE, PAYMENT_DATE — liability due date and the scheduled/settlement date.
• CURRENCY_CODE / PAYMENT_CURRENCY, and TRUNC(EXCHANGE_RATE, 9) — currency and rate.
• SEPARATE_REMITTANCE_ADVICE — formatting/remittance instruction flag.
• EDI_REMITTANCE_METHOD, EDI_REMITTANCE_INSTRUCTION — supplier remittance routing.
• BANK_CHARGE_BEARER and a derived transfer-priority/ACH indicator — bank charge and ACH/priority handling.
• BANK_ACCOUNT_NUM, BANK_ACCOUNT_TYPE, CHECK_DIGITS, BANK_ACCOUNT_NAME, BANK_NUMBER, BANK_NAME, BANK_BRANCH_NAME, EFT_SWIFT_CODE — bank and account identifiers for the payment file.

Common Use Cases and Queries

Typical uses include validating payment-format output, reconciling a payment run to selected invoices, and auditing EDI remittance routing. A representative query:

• SELECT CHECKRUN_NAME, CHECK_NUMBER, PAYMENT_DATE, CURRENCY_CODE, PAYMENT_AMOUNT, BANK_ACCOUNT_NUM, EDI_REMITTANCE_METHOD FROM AP_XML_PAYMENTLINE2_LEVEL_V WHERE CHECKRUN_NAME = :checkrun;
• Aggregate per run: SELECT CHECKRUN_NAME, COUNT(*), SUM(PAYMENT_AMOUNT) FROM AP_XML_PAYMENTLINE2_LEVEL_V GROUP BY CHECKRUN_NAME;
• Format diagnostics: filter on SEPARATE_REMITTANCE_ADVICE = 'Y' or bank charge bearer to trace format-driven behavior.

Because the object is not implemented in the documented database, usage should be scoped to environments where the view is deployed, and column names should be verified against that instance's definition.