Results for “iby_sum”

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

Overview

APPS.IBY_EXT_FC_PAYER_1_0_V is a reporting and extraction view in the Oracle Payments (IBY) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It is a denormalized presentation layer that joins payment transaction summary data to the corresponding payer's party, customer account, customer site, and operating unit information. The view is part of the "Extensible" extraction framework used to feed external payment formats, clearing house files, and payer/payee reporting. Its name follows the IBY naming convention for extract views: IBY_EXT_FC_PAYER_1_0_V indicates an external-facing (EXT) format-content (FC) view, version 1.0, exposing payer-level attributes.

Because it flattens multiple HZ and HR tables into a single row per payment transaction summary record, it is commonly used in cash management, disbursement, and reconciliation reporting where a flat, addressable payer record is required.

Underlying Base Objects

The view is defined over the following documented base objects:

• IBY_TRXN_SUMMARIES_ALL (SYNONYM) — the driving table, aliased IBY_SUM, providing transaction-level payment summary rows.
• HZ_PARTIES (SYNONYM) — aliased HZP, the payer party master (outer-joined on PAYER_PARTY_ID).
• HZ_CUST_ACCOUNTS (SYNONYM) — aliased HCA, customer account (outer-joined on CUST_ACCOUNT_ID).
• HZ_CUST_SITE_USES_ALL (SYNONYM) — aliased HCASU, customer account site use (outer-joined on SITE_USE_ID).
• HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — aliased HOU, organization unit (outer-joined on ORG_ID, with LANGUAGE = USERENV('LANG')).
• IBY_FD_EXTRACT_GEN_PVT (PACKAGE) — supplies the tax registration number via the function GET_PAYEE_TAXREGISTRATION.

All joins are outer joins, so a transaction summary row is preserved even when no matching payer party, customer account, site, or organization translation exists.

Key Columns

• TRXNMID — transaction summary identifier linking back to IBY_TRXN_SUMMARIES_ALL.
• PARTY_ID, PARTY_NUMBER, PARTY_NAME — payer party identifiers and display name from HZ_PARTIES.
• PARTY_TYPE — derived via NVL(HZP.PARTY_TYPE,'PERSON'), defaulting to PERSON.
• ALTERNATE_NAME — decoded phonetic name (organization vs. person).
• CUST_ACCOUNT_ID, ACCOUNT_NUMBER — customer account identifiers from HZ_CUST_ACCOUNTS.
• ORG_ID, OPERATING_UNIT — operating unit context from HR_ALL_ORGANIZATION_UNITS_TL.
• CUST_ACCT_SITE_ID, ACCOUNT_SITE_USE_ID, LOCATION — site use data from HZ_CUST_SITE_USES_ALL.
• BILL_TO_ADDRESS_ID — bill-to address reference from the transaction summary.
• TAX_REGISTRATION_NUMBER — derived from the IBY_FD_EXTRACT_GEN_PVT package.
• LE_REGISTRATION_NUMBER — exposed as NULL in this view version.
• PARTY_ATTR_CAT — party attribute category from HZ_PARTIES.

Common Use Cases and Queries

Typical scenarios include payer-level extract preparation, payment reporting by operating unit, and reconciliation of transaction summaries to payer master data.

List payers for a given operating unit:

• SELECT trxnmid, party_name, party_number, account_number, operating_unit FROM apps.iby_ext_fc_payer_1_0_v WHERE org_id = :org_id;

Retrieve tax registration and site data for a transaction:

• SELECT trxnmid, party_name, tax_registration_number, account_site_use_id, location FROM apps.iby_ext_fc_payer_1_0_v WHERE trxnmid = :trxnm_id;

Because IBY_FD_EXTRACT_GEN_PVT.GET_PAYEE_TAXREGISTRATION is invoked per row, queries over large volumes may benefit from filtering on TRXNMID or ORG_ID to limit function execution.