Results for “xml_hr_addr”

4 results




Overview
Explore in AI Chat

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

Overview

IBY_XML_FNDCPT_PAYEE_1_0_V is a database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is an internal, XML-generating view that belongs to the Oracle Payments (IBY) module and specifically to the Funds Capture (FNDCPT) infrastructure. The view presents payee information in an XMLType column named XML_PAYEE, conforming to the Oracle Payments Funds Capture XML message standard version 1.0. Its role is to assemble payer and payee party data, legal entity identifiers, and address information into a structured XML document used by the funds capture extraction and settlement processes.

The object carries the designation "Oracle Internal Use Only." Oracle does not support direct access to application data through this view except from standard Oracle Applications programs. The object status is VALID, and it is registered in FND Design Data under the IBY application. Developers and technical consultants should treat it as a building block of the Payments XML generation layer rather than as a public reporting interface.

Underlying Base Objects

The view is defined over a combination of packages, views, and a system type. The documented referenced base objects are:

  • IBY_EXTRACTGEN_PVT (PACKAGE) — The extraction generation package that supplies processed payer, payee, and settlement data in XML form.
  • IBY_EXT_FD_PAYER_1_0_V (VIEW) — The XML payer view providing the payer-side data elements referenced by the payee XML structure.
  • IBY_FD_EXTRACT_GEN_PVT (PACKAGE) — The funds capture extract generation package, which orchestrates the assembly of funds capture XML documents.
  • IBY_XML_HR_ADDR_1_0_V (VIEW) — The HR address XML view supplying formatted party address information.
  • XMLTYPE (TYPE) — The Oracle SQL/XML datatype used for the XML_PAYEE column.

The view is, in turn, referenced by IBY_XML_BATCH_FCI_1_0_V, IBY_XML_FNDCPT_ORDER_1_0_V, and IBY_XML_FNDCPT_ORDER_PN_1_0_V. This dependency chain confirms its position as a reusable component within the higher-level funds capture order and batch XML views.

Key Columns

The view exposes three columns, each with a specific purpose:

  • XML_PAYEE (XMLTYPE, length 64) — The generated XML fragment containing the full payee definition, including name, address, and related party attributes conforming to the 1.0 message format.
  • PARTY_ID (NUMBER, length 15) — The identifier of the payee party in the Trading Community Architecture (TCA) model, linking the XML content to the HZ_PARTIES registry.
  • LEGAL_ENTITY_ID (NUMBER, length 15) — The identifier of the legal entity associated with the payee, supporting legal entity–level segregation of payment and funds capture data.

Because XML_PAYEE is an XMLTYPE, it can be queried with SQL/XML functions such as XMLQuery and EXTRACT, or serialized directly using GETCLOBVAL for integration purposes.

Common Use Cases and Queries

The primary use case is the generation and retrieval of payee XML for funds capture order and batch processing, including credit card and bank account settlement flows, remittance handling, and integration with external payment systems that consume Oracle Payments XML messages. Typical troubleshooting scenarios include validating payee addresses, confirming legal entity mapping, and diagnosing missing or malformed payee XML in credit card refund or batch capture transactions.

A basic query selecting the exposed columns is:

SELECT XML_PAYEE, PARTY_ID, LEGAL_ENTITY_ID FROM APPS.IBY_XML_FNDCPT_PAYEE_1_0_V;

To render the XML as text for inspection or external transmission:

SELECT PARTY_ID, LEGAL_ENTITY_ID, XML_PAYEE.GETCLOBVAL() AS PAYEE_XML FROM APPS.IBY_XML_FNDCPT_PAYEE_1_0_V;

To filter to a specific payee party:

SELECT XML_PAYEE.GETCLOBVAL() FROM APPS.IBY_XML_FNDCPT_PAYEE_1_0_V WHERE PARTY_ID = :p_party_id;

Because Oracle restricts support for direct queries against this view, such SQL is appropriate for diagnostic and implementation verification purposes, while production integration should route through the standard Oracle Payments funds capture APIs and extraction programs.