Results for “ext_fc”

4 results




Overview
Explore in AI Chat

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

Overview

The view APPS.IBY_XML_FNDCPT_PAYER_1_0_V is a payment-facing XML generation view in Oracle E-Business Suite, owned by the APPS schema. It is part of the Oracle Payments (IBY) extract-generation framework, whose purpose is to transform structured payer master data stored in EBS into a canonical XML document conforming to the Payer 1.0 message schema. The view assembles a single XMLType document per payer by concatenating discrete XMLElement fragments for party identity, tax and legal registration identifiers, descriptive flexfields, addresses, and customer account references.

Its role is integration and reporting: downstream payment processing, bank-format extract generation, and third-party integrations consume the emitted XML rather than querying the base tables directly. In ETRM terms, the view is documented for both release 12.1.1 and 12.2.2 and inherits its behavior from the IBY extract generation package stack.

Underlying Base Objects

The documented base objects underlying this view are:

  • IBY_EXT_FC_PAYER_1_0_V — the primary driver view (aliased ext_fc), supplying payer row attributes such as party_id, party_number, party_name, party_type, tax_registration_number, le_registration_number, alternative_name, account_number, bill_to_address_id, and trxnmid.
  • FND_LOOKUP_VALUES (synonym) — joined on lookup_code = party_type for LOOKUP_TYPE = 'PARTY_TYPE', restricted to VIEW_APPLICATION_ID = 222 and LANGUAGE = userenv('LANG'), to resolve the party type meaning.
  • HZ_LOCATIONS (synonym) — outer-joined on bill_to_address_id = location_id to supply address lines, city, county, state, country, and postal code.
  • FND_TERRITORIES_VL (view) — outer-joined on country = territory_code to provide territory_short_name and iso_territory_code.
  • IBY_EXTRACTGEN_PVT and IBY_FD_EXTRACT_GEN_PVT (packages) — invoked (notably Get_Dffs) to render the HZ_PARTIES descriptive flexfield as XML.
  • XMLTYPE (type) — the returned payload type.

All non-driving joins are outer joins (indicated by the (+) operator), so a payer row is preserved even when lookup, address, or territory data is absent.

Key Columns

Because the projection is a single XMLType concatenation, the practical "columns" are the XML elements emitted:

  • PartyInternalID / PartyNumber / Name / AlternateName — core party identity from the driver view.
  • PartyType (Code, Meaning) — code from the driver, meaning resolved via FND_LOOKUP_VALUES.
  • TaxRegistrationNumber / LegalRegistrationNumber — regulatory identifiers.
  • PartyDescriptiveFlexField — emitted only when party_attr_cat is not null, generated by IBY_EXTRACTGEN_PVT.Get_Dffs('HZ_PARTIES', …).
  • Address — emitted only when bill_to_address_id is not null; contains AddressInternalID, AddressLine1–3, City, County, State, Country, CountryName, ISO3DigitCountry, PostalCode, AlternateAddressName.
  • CustomerAccountNumber / FirstPartyReference — account context; FirstPartyReference repeats party_number when present.

The view's tail also returns ext_fc.party_id and ext_fc.trxnmid, supporting correlation of the generated XML back to the source transaction.

Common Use Cases and Queries

Typical scenarios include generating payer payloads for payment extracts, validating address completeness before disbursement, and auditing flexfield rendering.

Sample query returning payer XML for a specific party:

  • SELECT party_id, trxnmid, xmltype.getclobval(x) AS payer_xml FROM apps.iby_xml_fndcpt_payer_1_0_v WHERE party_id = :p_party_id;

Inspecting a single element:

  • SELECT EXTRACT(x, '/PartyType/Meaning/text()').getStringVal() AS party_type_meaning FROM apps.iby_xml_fndcpt_payer_1_0_v WHERE party_id = :p_party_id;

Filtering to payers with addresses:

  • SELECT party_id, trxnmid FROM apps.iby_xml_fndcpt_payer_1_0_v WHERE EXTRACT(x, '/Address/City/text()').getStringVal() IS NOT NULL;

Note that the supplied search string is an injection-style probe and has no bearing on the view's definition; such input should never be concatenated into SQL against this or any other IBY view.