Results for “party_attr_cat”

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

Overview

The IBY_EXT_FD_PAYER_1_0_V view is an Oracle Payments (IBY) extraction view owned by the APPS schema. It is part of the payments extract framework used to supply payer information to external payment formatting, disbursement, and treasury integration processes, most notably the Funds Disbursement (FD) extract generation flow. The view presents a flattened, denormalized projection of first-party (legal entity) payer data — party identity, party type, and legal entity registration attributes — that downstream extract programs and payment instruction builders consume as a single logically consistent record set.

In Oracle EBS releases 12.1.1 and 12.2.2, the view is catalogued as VALID and is intended for read-only consumption by extract generation and reporting logic rather than for direct transactional updates. Because it carries the _1_0_ version suffix, it aligns with the funds disbursement extract interface versioning convention, where the version marker indicates the shape of the payload expected by the consuming formatting template or external system.

Underlying Base Objects

The view is defined over four referenced objects, all resolved within the APPS schema:

• XLE_FIRSTPARTY_INFORMATION_V (VIEW) — Supplies the legal entity first-party context: legal entity ID, name, registration number, location, and attribute category.
• HZ_PARTIES (SYNONYM) — Supplies the trading party identity: party ID, party number, party name, party type, and attribute category. In EBS the synonym resolves to the TCA party entity.
• AR_LOOKUPS (VIEW) — Provides the decoded party type meaning via the PARTY_TYPE lookup type.
• IBY_FD_EXTRACT_GEN_PVT (PACKAGE) — Referenced only through a stored function call, GET_FP_TAXREGISTRATION, which returns the first-party tax registration value derived from the legal entity ID.

The join is driven by XLE_FIRSTPARTY.PARTY_ID = PARTY.PARTY_ID, with PARTY.PARTY_TYPE joined to AR_LOOKUPS.LOOKUP_CODE restricted to LOOKUP_TYPE = 'PARTY_TYPE'. The package function is invoked per row against the legal entity identifier, so the view is not purely relational; it embeds a PL/SQL call that must be available and unpurged during query execution.

Key Columns

• PARTY_ID / PARTY_NUMBER / PARTY_NAME / PARTY_TYPE — Core TCA party identifiers and classification.
• PARTY_TYPE_MEANING — Decoded party type from AR_LOOKUPS.
• TAX_REGISTRATION_NUMBER — First-party tax registration, returned by GET_FP_TAXREGISTRATION.
• LE_REGISTRATION_NUMBER — Legal entity registration number from XLE_FIRSTPARTY.
• LEGAL_ENTITY_ID / LEGAL_ENTITY_NAME — Identifying attributes of the owning legal entity.
• LE_LOCATION_ID — Location identifier for the legal entity.
• PARTY_ATTR_CAT / LE_ATTR_CAT — Attribute categories for descriptive flexfield context on party and legal entity records.

Common Use Cases and Queries

The primary use case is verifying the payer payload produced for a funds disbursement extract run, and diagnosing missing or incorrect tax registration and legal entity registration values. A typical query retrieves all payer rows for a given legal entity:

• SELECT party_name, party_type_meaning, tax_registration_number, legal_entity_name FROM iby_ext_fd_payer_1_0_v WHERE legal_entity_id = :p_le_id;
• SELECT party_id, party_number, le_registration_number, le_location_id FROM iby_ext_fd_payer_1_0_v WHERE party_type = 'ORG';
• SELECT COUNT(*) FROM iby_ext_fd_payer_1_0_v; for extract-volume sanity checks.

Because the view invokes a PL/SQL function, performance tuning should focus on indexed access to XLE_FIRSTPARTY_INFORMATION_V and HZ_PARTIES rather than on the lookup join.