Results for “iby_notify_xmission_fail_xml_v”

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

Overview

The IBY_NOTIFY_XMISSION_FAIL_XML_V view is a dictionary object owned by the APPS schema within the Oracle Payments (IBY) module. It is classified as a VIEW and reported as VALID in both Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal function is to generate an XML representation of payment instructions that have failed transmission or notification processing, packaging the relevant payment instruction identifier inside a structured XMLTYPE payload. Rather than acting as a transactional or interface table, the view serves as an integration and reporting aid, allowing callers to retrieve failure-related payment instruction data in XML form for consumption by notification engines, retry logic, and diagnostic reporting.

The user search term instruction_status maps directly to a column exposed by this view, confirming that the object is commonly inspected to determine the current processing state of a payment instruction. The view deliberately restricts its result set to instructions whose status is not equal to 'CREATED', meaning only instructions that have advanced beyond creation and subsequently entered a failure or exception state are returned.

Underlying Base Objects

The view is defined over a single base object documented in the ETRM metadata: IBY_PAY_INSTRUCTIONS_ALL, referenced through a SYNONYM. This table stores all payment instructions processed by Oracle Payments, and the view aliases it as INS in its defining query. The second documented referenced object is the XMLTYPE type, which is used as the return type for the XML construction column. The definition combines an XMLELEMENT construction with a projection of the underlying instruction identifier and status, applying a WHERE clause filter on PAYMENT_INSTRUCTION_STATUS that excludes records in the 'CREATED' state. Because it is a simple single-table view with no joins, aggregation, or inline functions beyond XML generation, its rows correspond one-to-one with non-CREATED rows in IBY_PAY_INSTRUCTIONS_ALL.

Key Columns

• INSTRUCTION_CONTENT — An XMLTYPE value produced by XMLELEMENT("PAYMENTINSTRUCTION", ...). It nests a PAYMENTINSTRUCTIONID element carrying the payment instruction identifier, yielding a minimal though well-formed XML document suitable for transmission or logging.
• INSTRUCTION_ID — The raw PAYMENT_INSTRUCTION_ID of the underlying IBY_PAY_INSTRUCTIONS_ALL row. It provides a relational key that can be joined back to the base table or to related XML gateway and notification tables.
• INSTRUCTION_STATUS — The PAYMENT_INSTRUCTION_STATUS value from the base table. Because of the view's filter, this column never returns 'CREATED'; typical values reflect states such as failure, cancellation, or transmission error conditions.

Common Use Cases and Queries

This view is typically queried by support and integration staff investigating payment instruction transmission failures, or by code that requires an XML envelope for a failed instruction. A representative query retrieves all failed instructions and their XML content:

• SELECT instruction_id, instruction_status, instruction_content FROM apps.iby_notify_xmission_fail_xml_v;
• Filtering by status to isolate a specific failure class: SELECT instruction_id FROM apps.iby_notify_xmission_fail_xml_v WHERE instruction_status = 'TRANSMITTED';
• Joining back to the base table for additional context: SELECT v.instruction_id, i.payment_instruction_status FROM apps.iby_notify_xmission_fail_xml_v v, apps.iby_pay_instructions_all i WHERE v.instruction_id = i.payment_instruction_id;
• Extracting the identifier from the XMLTYPE payload: SELECT v.instruction_id, EXTRACTVALUE(v.instruction_content, '/PAYMENTINSTRUCTION/PAYMENTINSTRUCTIONID') FROM apps.iby_notify_xmission_fail_xml_v v;

Because the view exposes only two scalar columns plus the XML fragment, consumers needing richer detail must join to IBY_PAY_INSTRUCTIONS_ALL or associated payment, transmission, and notification tables. The instruction_status column remains the primary discriminator for identifying which failed instructions are relevant to a given retry or notification exercise.