Results for “iby_xml_bep_acct_options_v”

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

Overview

IBY_XML_BEP_ACCT_OPTIONS_V is a database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the IBY (Payments) product family and is documented as VALID in the ETRM repository. The view exists to produce an XML representation of bank account option values, aggregated by Bank Enterprise Payment (BEP) account. Rather than exposing the account option records in a flat, one-row-per-option format, the view collapses all option entries for a given account into a single XML fragment in which each option is serialized as an ACCOUNTOPTION element carrying a NAME and a VALUE sub-element.

This design is characteristic of the XML gateway and XML output views used throughout IBY and related modules, where downstream payment processing, extract programs, or external integrations require a structured XML payload rather than relational rows. The view therefore functions as a presentation and integration layer over the account option data, not as a transactional object in its own right.

Underlying Base Objects

The view is defined over the base object IBY_BEP_ACCT_OPT_VALS, which appears in the ETRM metadata as a SYNONYM and holds the actual account option code and value pairs along with the owning BEP account identifier. The documented base and referenced objects are:

• IBY_BEP_ACCT_OPT_VALS (SYNONYM) — source of the account option code/value records and the BEP account identifier.
• XMLAGG (SYNONYM) — the aggregate function that concatenates the individual XMLELEMENT fragments into a single XML document per account group.
• AGGXMLIMP (TYPE) — the Oracle type underpinning the XMLAGG aggregate implementation.
• XMLTYPE (TYPE) — the XML type associated with the XML generation machinery.
• IBY_SECURITY_PKG (PACKAGE) — referenced by the view definition context, supporting the security model applied to payments data.
• IBY_UTILITY_PVT (PACKAGE) — referenced utility package used within the IBY payments infrastructure.

The view text groups IBY_BEP_ACCT_OPT_VALS rows by BEP_ACCOUNT_ID and applies XMLAGG over XMLELEMENT("ACCOUNTOPTION", ...) so that the returned ACCOUNT_OPTIONS column contains the complete set of options for each account in one value.

Key Columns

• ACCOUNT_OPTIONS — The XML aggregate column. Each row contains an XML fragment composed of one or more ACCOUNTOPTION elements. Within each element, NAME carries the ACCOUNT_OPTION_CODE and VALUE carries the ACCOUNT_OPTION_VALUE. This column is the payload consumed by XML-aware consumers.
• BEP_ACCOUNT_ID — The identifier of the BEP account to which the option set belongs. Because the view groups by this column, exactly one row is produced per distinct BEP account that has at least one option value defined.

The view exposes only these two columns, which reinforces its narrow purpose: delivering a keyed XML payload rather than a general-purpose reporting structure.

Common Use Cases and Queries

Typical usage involves retrieving the XML option block for a specific BEP account, or extracting all account option payloads for processing by a payment integration or reconciliation routine. A representative query follows:

• SELECT BEP_ACCOUNT_ID, ACCOUNT_OPTIONS FROM APPS.IBY_XML_BEP_ACCT_OPTIONS_V WHERE BEP_ACCOUNT_ID = :p_account_id;
• SELECT BEP_ACCOUNT_ID, XMLSERIALIZE(CONTENT ACCOUNT_OPTIONS AS CLOB) ACCOUNT_OPTIONS_CLOB FROM APPS.IBY_XML_BEP_ACCT_OPTIONS_V; — used when the XML must be materialized as a CLOB for file generation or message payloads.
• SELECT COUNT(*) FROM APPS.IBY_XML_BEP_ACCT_OPTIONS_V; — used to confirm how many BEP accounts currently carry option values.

Because the view relies on XMLAGG, it should be queried with awareness that it is intended for XML consumption and may be less efficient for high-volume flat reporting; direct queries against IBY_BEP_ACCT_OPT_VALS are preferable when row-level option data is required.