Results for “iby_notify_ins_fail_xml_v”

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

Overview

The view IBY_NOTIFY_INS_FAIL_XML_V is a reporting and integration object in the Oracle Payments (IBY) module of Oracle E-Business Suite, owned by the APPS schema. Its purpose is to expose payment instruction records that have failed during the instruction creation or insertion process in an XML-formatted structure suitable for notification, diagnostics, or downstream consumption. The view filters the underlying payment instructions table to return only those rows whose PAYMENT_INSTRUCTION_STATUS is not equal to CREATED, effectively isolating instructions that did not complete the initial creation lifecycle step.

Rather than returning a plain relational row, the view projects an XML fragment through the SQL/XML XMLELEMENT construct, producing a nested <PAYMENTINSTRUCTION> document with a child <PAYMENTINSTRUCTIONID> element. This design supports notification workflows (for example, advising that an instruction insertion attempt failed) where a self-describing XML payload is preferred over raw columnar output. The object holds a VALID status in the ETRM documentation and is present in both the 12.1.1 and 12.2.2 releases. Because it is a view and not a table, it stores no data of its own and is always resolved against live base data at query time.

Underlying Base Objects

The documented base objects referenced by this view are:

• IBY_PAY_INSTRUCTIONS_ALL (exposed to the view as a SYNONYM) — the transactional table holding payment instructions across all operating units.
• XMLTYPE (TYPE) — the Oracle built-in datatype used to represent the generated XML content.

The view is therefore a thin, purpose-built projection over IBY_PAY_INSTRUCTIONS_ALL. The alias INS is applied to the base table, and the WHERE clause restricts the result set to instructions whose status is other than CREATED. The XML output is generated on the fly using XMLELEMENT, so the columns returned are derived rather than physically stored. Any change to the base table's structure or to the instruction status values will directly affect the behavior and output of this view.

Key Columns

• INSTRUCTION_CONTENT — The XML document emitted by the XMLELEMENT expression. It wraps the payment instruction identifier inside a <PAYMENTINSTRUCTION> root element containing a <PAYMENTINSTRUCTIONID> child, and is of type XMLTYPE.
• INSTRUCTION_ID — Sourced from INS.PAYMENT_INSTRUCTION_ID; the unique identifier of the underlying payment instruction row.
• INSTRUCTION_STATUS — Sourced from INS.PAYMENT_INSTRUCTION_STATUS; the current lifecycle status of the instruction, restricted by the view's predicate to values other than CREATED.

The combination of the raw identifier and status alongside the XML payload allows both relational joins and XML-based processing from a single query.

Common Use Cases and Queries

Typical scenarios include failure notification, reconciliation of incomplete instructions, and integration feeds that require an XML message body. A representative query retrieving all current failure records is:

• SELECT instruction_id, instruction_status, instruction_content FROM apps.iby_notify_ins_fail_xml_v;
• SELECT instruction_id, instruction_status FROM apps.iby_notify_ins_fail_xml_v WHERE instruction_status = 'REJECTED';
• SELECT v.instruction_id, x.paymentinstructionid FROM apps.iby_notify_ins_fail_xml_v v, XMLTABLE('/PAYMENTINSTRUCTION/PAYMENTINSTRUCTIONID' PASSING v.instruction_content COLUMNS paymentinstructionid NUMBER PATH '.') x;

These patterns support operational monitoring and downstream notification where only non-created payment instructions are relevant.