Search Results get_dffs

Overview

IBY_EXTRACTGEN_PVT is a private PL/SQL package in the APPS schema that provides the core extraction and XML generation engine for Oracle Payments (IBY) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its role is to instantiate payment document templates, resolve descriptive flexfield content, and assemble the XML payload that carries payment instructions to banks, clearing houses, and third-party payment partners. Conceptually it sits between the payment instruction model — extracted document headers, payment records, and format definitions — and the public XML views (IBY_XML_*_V) that expose generated output to the concurrent request and transmission layers. Because the package is classified as PVT, it is intended strictly for internal invocation by Oracle Payments and its XML view family; it is not part of the supported public API surface.

Key Procedures and Functions

• CREATE_EXTRACT — The primary generation routine. It orchestrates creation of an extract for a given extract definition and format, combining template metadata with document, payment, payee, and payer data to produce the XML output consumed downstream.
• GET_DFFS — Retrieves descriptive flexfield definitions and values relevant to the extract, enabling flexfield content to be projected into payment XML for formats that require it.
• GET_TEMPLATE_PARAMETERS — Resolves the parameters and bind values associated with an XML template defined against a payment format, supplying the substitution values used during XML assembly.
• GET_XML_CHAR_ENCODING_HEADER — Returns the character encoding header fragment (for example, the XML declaration encoding attribute) appropriate to the target format, ensuring the generated document is correctly declared for the receiving party.
• IS_FLEX_FIELD_ENABLED — Boolean predicate that determines whether a given flexfield is enabled and therefore whether flexfield-related processing should proceed.

Tables Accessed

The package reads the IBY payment foundation tables — IBY_EXTRACTS_B and IBY_FORMATS_B for extract and format definitions — and the IBY payment model: IBY_PAYMENTS_ALL, IBY_DOCS_PAYABLE_ALL, IBY_PAYMENT_METHODS_B, IBY_ACCT_PMT_PROFILES_B, IBY_EXT_BANK_ACCOUNTS, and IBY_BEPKEYS. It joins outward to AP_CHECKS_ALL for payment instrument details and CE_BANK_ACCOUNTS for bank account attributes, to HZ_PARTIES for payee, payer, and party information, and to the flexfield metadata tables FND_DESCR_FLEX_CONTEXTS and FND_DESCR_FLEX_COLUMN_USAGES when resolving descriptive flexfield output. FND_CONCURRENT_REQUESTS is referenced to associate generation with the running request, and XMLTYPE (a public synonym for the SYS XML type) supports XML construction and manipulation. The nested table type JTF_VARCHAR2_TABLE_200 and the STANDARD package provide supporting PL/SQL and collection facilities.

Usage Notes

IBY_EXTRACTGEN_PVT is invoked indirectly rather than by custom code. The XML viewing layer — including IBY_XML_BATCH_FCI_1_0_V, IBY_XML_FC_PRBA_1_0_V, IBY_XML_FD_DOC_1_0_V, IBY_XML_FD_INS_1_0_V, IBY_XML_FD_PMT_1_0_V, IBY_XML_FD_PPR_1_0_V, IBY_XML_FD_PRBA_1_0_V, the IBY_XML_FNDCPT_* views, and IBY_XML_ONLINE_FCI_1_0_V — references the package to render extract output. These views are exposed through Oracle Payments concurrent programs that generate payment formats and XML payment documents. Because the package is PVT, references from custom PL/SQL are unsupported and may break across patches; the documented dependents (26 referencing packages and views) are all Oracle-owned. When troubleshooting payment XML generation, errors surfaced from this package typically originate from format definition, template parameter, or flexfield configuration rather than the package itself.