Results for “iby_xml_batch_fci_1_0_v”
40 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view APPS.IBY_XML_BATCH_FCI_1_0_V is a Payments (IBY) module database object that constructs an XML representation of a Funds Capture Instruction for a payment batch. In Oracle EBS 12.1.1 and 12.2.2, this view is the primary vehicle through which closed payment batches are serialized into an XMLTYPE document conforming to the Funds Capture Instruction (FCI) message schema. The resulting XML is consumed by Oracle Payments funds capture processing, typically for transmission to a payment system or processor that accepts standardized funds capture instruction payloads.
The view is defined in the APPS schema and is reported as VALID. Rather than storing data, it dynamically assembles XML at query time by joining batch header information in IBY_BATCHES_ALL with account, payee, and bank account content derived from companion XML views. This design keeps the canonical batch data in its normalized form while producing a message-oriented projection on demand.
Underlying Base Objects
The view is defined over the following primary base objects:
IBY_BATCHES_ALL(SYNONYM) — supplies the batch header: identifier, name, close date, status, totals, currency, settlement date, legal entity, and organization.IBY_XML_FNDCPT_ACCT_1_0_V(VIEW) — produces the per-payee account XML fragment.IBY_XML_FNDCPT_PAYEE_1_0_V(VIEW) — produces the payee XML fragment.IBY_XML_FNDCPT_BANKACCOUNT_V(VIEW) — produces the payee bank account fragment.
The view also references several packages and types, including IBY_UTILITY_PVT, IBY_FNDCPT_EXTRACT_GEN_PVT, IBY_EXTRACTGEN_PVT, IBY_FD_EXTRACT_GEN_PVT, IBY_AR_UTILS, IBY_CREDITCARD_PKG, IBY_SECURITY_PKG, IBY_TRANSACTIONCC_PKG, IBY_EXT_BANKACCT_PUB, HZ_FORMAT_PUB, and FND_GLOBAL. Aggregation is performed using XMLAGG over the AGGXMLIMP type, and the result is an XMLTYPE value.
Key Columns
The view exposes a single implicit column: the assembled XMLTYPE document rooted at the FUNDSCAPTUREINSTRUCTION element. Within that document, the principal sub-elements are:
- INSTRUCTIONINFO — carries
INSTRUCTIONINTERNALID(fromMBATCHID),INSTRUCTIONNAME(fromBATCHID), creation date, sent date, and status. - INSTRUCTIONSEQUENCE — identifies
SENT_COUNTER_DAILYand its last value fromSENTCOUNTERDAILY. - INSTRUCTIONTOTALS — reports the payee account count and the settlement total with currency code.
- INSTRUCTIONGROUPING — contains settlement date, settlement currency, aggregated payee, organization internal identifier, and aggregated payee bank account.
The EXTRACT_MODE parameter is central to the view's behavior. The trailing DECODE evaluates IBY_UTILITY_PVT.GET_VIEW_PARAM('EXTRACT_MODE'); when it returns G_EXTRACT_MODE_SRA, the payee account aggregate is generated by IBY_FNDCPT_EXTRACT_GEN_PVT.GET_INS_PAYEEACCTAGG; otherwise the aggregate from XMLAGG(XML_ACCT.PAYEE_ACCOUNT) is used. This makes EXTRACT_MODE the switch that governs which account aggregation strategy is applied at extraction time.
Common Use Cases and Queries
The view is primarily used by the funds capture extraction programs to generate instruction payloads. A typical diagnostic query retrieves the assembled XML for a specific batch:
SELECT x.*
FROM apps.iby_xml_batch_fci_1_0_v x
WHERE EXTRACTVALUE(VALUE(x), '//INSTRUCTIONINTERNALID') = :mbatch_id;
Because the view's output is an XMLTYPE, common operations include validating the root element or extracting individual fields with XML functions:
SELECT EXTRACT(x.COLUMN_VALUE, '/FUNDSCAPTUREINSTRUCTION/INSTRUCTIONTOTALS/SETTLMENTTOTAL/VALUE').getStringVal() AS total
FROM TABLE(apps.iby_xml_batch_fci_1_0_v) x;
Administrators and developers also use the view to confirm how the EXTRACT_MODE view parameter changes output. Setting the parameter prior to querying and comparing the PAYEEBANKACCOUNT fragment reveals whether the SRA aggregation path is in effect. This is especially relevant during upgrades between 12.1.1 and 12.2.2, where extraction behavior and referenced packages may differ.
-
APPS.IBY_XML_BATCH_FCI_1_0_V·↳ FND_GLOBAL·↳ HZ_FORMAT_PUB·↳ IBY_AR_UTILS·Explore IBY module →
-
APPS.IBY_XML_BATCH_FCI_1_0_V·↳ FND_GLOBAL·↳ HZ_FORMAT_PUB·↳ IBY_AR_UTILS·Explore IBY module →
-
TYPE: SYS.AGGXMLIMP 12.1.1
-
SYNONYM: PUBLIC.XMLAGG 12.1.1
-
TYPE: SYS.AGGXMLIMP 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
SYNONYM: PUBLIC.XMLAGG 12.2.2
-
TYPE: SYS.XMLTYPE 12.1.1
-
TYPE: SYS.XMLTYPE 12.2.2
-
eTRM - IBY Tables and Views 12.1.1
Stores the user privilege settings for viewing sensitive data in iPayment operations UI
-
eTRM - IBY Tables and Views 12.2.2
Stores the user privilege settings for viewing sensitive data in iPayment operations UI
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - IBY Tables and Views 12.1.1
Stores the user privilege settings for viewing sensitive data in iPayment operations UI
-
eTRM - IBY Tables and Views 12.2.2
Stores the user privilege settings for viewing sensitive data in iPayment operations UI