Results for “aba_global_attribute_category”

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

Overview

ECE_PYO_PAYMENT_V is a private view owned by the APPS schema in Oracle E-Business Suite, defined within the EC (e-Commerce Gateway) product and associated with the Oracle Payables (AP) application. Its documented purpose is to extract payment information for the outbound Payment Order/Remittance Advice transaction, identified by the EDI standards 820 (Payment Order/Remittance Advice), PAYORD, and REMADV. In the e-Commerce Gateway outbound flow, this view serves as the extraction query source that populates the flat-file or XML payload transmitted to a trading partner's bank or financial institution. The view is registered in ETRM with a lifecycle status of active, scope private, and display name "Payment Order/Remittance Advice Payment View." Although the view text itself contains no explicit column named BANK_BRANCH_TYPE, the searched term aligns with the BANK_BRANCH_TYPE alias present in the underlying extract logic, which derives the branch type from the bank account class code.

Underlying Base Objects

The ETRM 12.2.2 metadata documents a single referenced base object for this view: IBY_PYO_PAYMENT_GT. This is a global temporary table belonging to the Payments (IBY) schema lineage, and it acts as the intermediate staging structure that carries payment instruction records between the Payments engine and downstream extraction consumers. The view is defined over this table and enriches its rows with joins to bank, trading partner, and trading partner detail entities. In the view text these joins resolve through aliases such as IPAY (the payment record), BKTPH and BKTPD (trading partner header and detail), HCP (trading partner location), HCA and HCA1 (bank account classifications), and CBA (bank account definition). The dependency on IBY_PYO_PAYMENT_GT means the view returns only rows present in that temporary table for the current session, and it must be invoked within the context of an active e-Commerce Gateway extraction run.

Key Columns

• COMMUNICATION_METHOD — Hard-coded literal 'EDI'; identifies the outbound transport channel.
• DOCUMENT_ID / DOCUMENT_CODE — 'PYO' and IPAY.PAYMENT_ID respectively; the document identifier used to group payment lines.
• TRANSACTION_DATE — Populated with SYSDATE at extraction time.
• BK_TP_TRANSLATOR_CODE, BK_TP_LOCATION_CODE_EXT, BK_TP_DESCRIPTION, BK_TP_REFERENCE_EXT1/EXT2 — Trading partner identification and mapping attributes.
• TRANSACTION_HANDLING_CODE — From IPAY.BANK_INSTRUCTION1_CODE; conveys payment handling instructions.
• CHECK_AMOUNT, CURRENCY_CODE — From IPAY.PAYMENT_AMOUNT and IPAY.PAYMENT_CURRENCY_CODE.
• EDI_PAYMENT_METHOD, EDI_PAYMENT_FORMAT — From IPAY.PAYMENT_METHOD_CODE and IPAY.BANK_INSTRUCTION2_CODE.
• BANK_BRANCH_TYPE — Derived from HCA1.CLASS_CODE, the class code of the bank account's owning party.
• BANK_ACCOUNT_TYPE, BANK_ACCOUNT_NUM, BANK_EDI_ID_NUMBER — Account classification, internal bank account number, and EDI routing identifier.
• VENDOR_BANK_BRANCH_TYPE — Derived from HCA.CLASS_CODE for the vendor-side bank branch.
• TPH_ATTRIBUTE1–15 and TPD_ATTRIBUTE1–5 — Descriptive flexfield segments inherited from the trading partner header and detail records, supporting partner-specific mapping extensions.

Common Use Cases and Queries

The primary use case is outbound 820/PAYORD/REMADV generation. Developers and support analysts query the view to audit exactly what payment data will be transmitted, to diagnose why a payment was omitted, or to confirm bank branch type mapping values before a production run.

To inspect extracted payments for a specific partner and review bank branch classification:

SELECT document_code,
       check_amount,
       currency_code,
       bank_account_num,
       bank_branch_type,
       vendor_bank_branch_type
FROM   apps.ece_pyo_payment_v
WHERE  bk_tp_translator_code = :p_translator_code;

Because the view depends on IBY_PYO_PAYMENT_GT, standalone queries outside an extraction run typically return no rows. Analysts generally confirm that the e-Commerce Gateway concurrent program has populated the temporary table, or run the query during the outbound process. A second common pattern is validating that ATTRIBUTE flexfield mappings carry the expected partner-specific values, using the TPH_ and TPD_ attribute columns in the SELECT list. Where the searched term bank_branch_type is the object of interest, the view remains the correct source, as the value originates from the bank account class code rather than a dedicated base table column.