Search Results create_payer_notif_extract_1_0

Overview

IBY_FNDCPT_EXTRACT_GEN_PVT is a private PL/SQL package in the Oracle Payments (IBY) module of Oracle E-Business Suite, owned by APPS and classified as PVT within the ETRM repository. Its business purpose is to generate extract documents — XML payloads delivered to payment counterparties such as banks, payment processors, and payers — that carry funds capture and funds disbursement transaction data. The package acts as the engine behind the extract-generating XML views used by Oracle Payments for outbound payment instructions, payer notifications, and accompanying letters.

The package exposes a family of package-level constants that parameterize these views. Among them is G_VP_SYS_KEY, defined as the constant VARCHAR2(30) value 'SYS_KEY'. The comment in the package specification states that this is the "system security key - for registered instrument decryption." It is complemented by G_VP_PAYEE_KEY ('PAYEE_KEY') for payee transaction data decryption, G_VP_SEC_VAL ('SEC_VAL') for CVV2 values, G_VP_XML_BASE ('XML_BASE') for the XML base setting, and G_VP_EXTRACT_MODE ('EXTRACT_MODE'). Applications searching on "g_vp_sys_key" are typically tracing how encrypted credit card, debit card, and bank account data is decrypted during extract generation.

Key Procedures and Functions

ETRM documents fourteen procedures and functions, including:

• CREATE_EXTRACT_1_0 — the primary extract generator. It accepts an instrument type, request type, a transaction identifier (which may reference IBY_BATCHES_ALL for batch extracts), and a system security key of type iby_security_pkg.DES3_KEY_TYPE used for instrument decryption, returning the resultant extract document as a CLOB.
• CREATE_PAYER_NOTIF_EXTRACT_1_0 — introduced under Bug 5115161, it builds a payer notification extract using batch identifier, date and PSON ranges, delivery method, format code, transaction ID, and system key, returning the extract as a CLOB.
• SUBMIT_PAYER_NOTIFICATION and SUBMIT_ACCOMPANY_LETTER — handle submission of notification and accompanying letter documents to payers.
• GET_INS_PAYEEACCTAGG — retrieves payee account aggregation data for the extract.
• GET_SRA_ATTRIBUTE and GET_PAYER_DEFAULT_ATTRIBUTE — resolve Smart Receipt Attributes (SRA) and payer default attribute values used to shape extract content.
• GET_BATCH_FORMAT — determines the format applied to batch extracts.
• UPDATE_PMT_SRA_ATTR_PRT and UPDATE_PMT_SRA_ATTR_ELE — update payment SRA attributes at the party and element levels.
• IS_AMENDED — evaluates amendment status of an underlying document or mandate.
• GET_ASSIGNMENT_IBAN and GET_MANDATE_DETAILS — retrieve IBAN assignment information and direct debit mandate details.

Tables Accessed

The package operates against core Oracle Payments and Trading Community tables through APPS synonyms. Instrument and security data are read from IBY_FNDCPT_SYS_CC_PF_B, IBY_FNDCPT_SYS_DC_PF_B, IBY_FNDCPT_SYS_EFT_PF_B, and IBY_FNDCPT_USER_CC_PF_B, which store system and user payment profiles for credit card, debit card, and EFT instruments, and which rely on the system security key for decryption. IBY_EXT_BANK_ACCOUNTS and IBY_EXTERNAL_PAYERS_ALL supply external payer and bank account details, while IBY_DEBIT_AUTHORIZATIONS supports direct debit mandate processing. IBY_BATCHES_ALL is referenced for batch-level extract transactions, IBY_BEPKEYS for extract key handling, and IBY_AR_DOC_HEADER_GT as a global temporary staging table for receivable documents. Party, site, and location data are drawn from HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, and HZ_PARTY_SITES. XMLTYPE is used to construct and manipulate the resulting XML extract documents.

Usage Notes

Because the package is classified PVT, it is not a public API and should not be called directly from custom code; Oracle supports invocation only through the Oracle Payments concurrent programs, XML Publisher templates, and forms that drive extract generation and payer notification. In practice it is invoked when a funds capture or disbursement process produces outbound payment files, when payer notifications or accompanying letters are delivered by email, fax, or print, and when registered instruments must be decrypted for inclusion in the extract. The G_VP_SYS_KEY constant governs the system security key binding used in those decryption routines, and its value is resolved at runtime from the Oracle Payments security infrastructure rather than hard-coded by callers. Customizations requiring similar extract output should be based on the supported XML views and concurrent program interfaces rather than on direct calls to this private package.