Search Results invoice_description

Overview

ECE_PYO_INVOICE_V is a private Oracle E-Business Suite view owned by the APPS schema in the e-Commerce Gateway (EC) product. It extracts invoices selected for payment in order to support the outbound Payment Order/Remittance Advice transaction, commonly identified by the ANSI X12 820/PAYORD/REMADV document family. The view is registered as active with a lifecycle status of active and a display name of "Payment Order/Remittance Advice." Because it is scoped private, it is an internal implementation object supporting the extraction of payment instruction data rather than a general-purpose reporting interface exposed to end users.

The view serves as the integration bridge between Oracle Payables payment selection processing and the outbound 820 extract logic. When payment batches are selected and confirmed for payment, the corresponding invoices, payment amounts, and vendor identifiers are made available through this view so that the e-Commerce Gateway can assemble a structured remittance message for transmission to a bank or trading partner.

Underlying Base Objects

The documented view metadata for release 12.2.2 identifies a single referenced base object: IBY_PYO_INVOICE_GT (TABLE). IBY_PYO_INVOICE_GT is a global temporary table in the Oracle Payments (IBY) schema. During payment processing, the Payments engine populates this table with the invoice-level detail associated with payments that have been created and selected for the payment instruction. ECE_PYO_INVOICE_V is defined over this global temporary table, meaning its contents are session-scoped and reflect only the payment documents generated within the current processing context.

The view remains VALID across both EBS 12.1.1 and 12.2.2 releases. The 12.1.1 and 12.2.2 implementations share the same extraction contract, with the underlying IBY global temporary table providing the source rows.

Key Columns

The view text exposes a broad set of identifiers and amounts aligned to the 820 outbound format. Notable columns include:

• PAYMENT_ID — Identifier of the payment document; sourced from IDPA.PAYMENT_ID.
• PAYMENT_INSTRUCTION_ID — Identifier of the payment instruction; sourced from IPA.PAYMENT_INSTRUCTION_ID.
• PAY_SELECTED_CHECK_ID — Returned as NULL in the view text, but present because downstream extraction code expects the column in the result set.
• PRINT_SELECTED_CHECK_ID — Also returned as NULL, mirroring the PAY_SELECTED_CHECK_ID placeholder behavior.
• VENDOR_NUM — Supplier number (APS.SEGMENT1).CUSTOMER_NUM — NULL, reflecting that the 820 focuses on payments rather than receipts.
• INVOICE_NUM, INVOICE_DATE, INVOICE_DESCRIPTION — Invoice identifiers and descriptors.
• PROPOSED_PAYMENT_AMOUNT and INVOICE_AMOUNT — Payment amount versus document amount.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield attributes from the payment document.
• INV_GLOBAL_ATTRIBUTE_CATEGORY and INV_GLOBAL_ATTRIBUTE1–INV_GLOBAL_ATTRIBUTE15 — Global descriptive flexfield attributes from the invoice.
• DISCOUNT_AMOUNT — NULL in the view text, reserved for the 820 discount element.

Common Use Cases and Queries

The primary use case is the outbound 820 Payment Order/Remittance Advice extract, invoked during e-Commerce Gateway payment processing. Developers and support analysts typically query this view to validate the rows that will be transmitted for a given payment instruction. Because PAY_SELECTED_CHECK_ID and PRINT_SELECTED_CHECK_ID are NULL, they serve as placeholders and should not be relied upon for filtering.

Sample query for invoices associated with a specific payment:

SELECT payment_id,
       payment_instruction_id,
       vendor_num,
       invoice_num,
       invoice_date,
       proposed_payment_amount,
       invoice_amount
FROM   apps.ece_pyo_invoice_v
WHERE  payment_id = :p_payment_id;

To list all invoices for a payment instruction:

SELECT invoice_num,
       vendor_num,
       proposed_payment_amount
FROM   apps.ece_pyo_invoice_v
WHERE  payment_instruction_id = :p_payment_instruction_id
ORDER  BY invoice_num;

Because the view is defined over a global temporary table, the result set depends on the payment processing session having populated IBY_PYO_INVOICE_GT. Queries run outside an active payment selection context typically return no rows. This behavior distinguishes ECE_PYO_INVOICE_V from permanent reporting views and reinforces its role as a runtime extraction component of the 820 outbound interface.