Search Results insert_bank_account

Overview

ARP_EXT_BANK_PKG is a PL/SQL package owned by the APPS schema that supports external bank account and bank branch maintenance within the Oracle Receivables and Oracle Payments (IBY) integration boundary. Its principal business purpose is to allow Receivables customers, or the applications that act on their behalf, to create and validate external bank branch and bank account records held in the IB Y external bank account model, and to associate those accounts with customer receipt method assignments. The package therefore sits at the intersection of customer master data (HZ_CUST_ACCOUNTS), receipt method configuration (AR_RECEIPT_METHODS, RA_CUST_RECEIPT_METHODS), and external banking entities (CE_BANK_BRANCHES_V, IBY_EXT_BANK_ACCOUNTS_V).

The package header carries a version marker of 120.5.12010000.2 dated 2008/08/27, consistent with the 12.1.1 and 12.2.2 code lines. It exposes eight documented procedures and one collection type declaration, and is referenced by three other packages in the ETRM object graph.

Key Procedures and Functions

The package declares the associative array type numeric_tab_typ, defined as TABLE of number INDEX BY BINARY_INTEGER. This is the construct most frequently located through search for numeric_tab_typ; it provides an in-memory, integer-indexed collection of numeric values used internally by the package for set-oriented and positional processing before persistence.

• STRIP_WHITE_SPACES — Accepts a credit card or bank account number and returns a normalized value with embedded white space removed, ensuring stored account numbers are consistent for later matching and validation.
• INSERT_EXT_BANK_BRANCH — Creates an external bank branch record, accepting bank and branch name and number, optional end date and description, and returning the generated bank party and branch party identifiers plus a return status.
• INSERT_BANK_ACCOUNT — Creates an external bank account for a given bank party, branch party, and primary account owner (customer), returning the new bank account identifier and a return status.
• CHECK_BANK_ACCOUNT — Validates an existing external bank account using routing number, account number, bank party, and branch party, returning the resolved bank account identifier and start date information.
• CREATE_BANK_BRANCH_ACC — Composite operation that orchestrates branch and account creation in a single call path.
• INSERT_ACCT_INSTR_ASSIGNMENT — Establishes the association between a created bank account and the customer's payment instrument or receipt method configuration.
• GET_CUST_PAY_METHOD — Retrieves the customer's applicable payment method, reading from the Receivables receipt method tables.
• PROCESS_CUST_PAY_METHOD — Applies or processes the customer payment method, typically pairing with GET_CUST_PAY_METHOD to synchronize receipt method assignment with the newly created bank account.

Tables Accessed

The package operates against APPS synonyms. AP_BANK_ACCOUNT_USES and the receipt method tables AR_RECEIPT_METHODS, RA_CUST_RECEIPT_METHODS, and RA_CUST_RECEIPT_METHODS_S are read and written to establish and validate payment instrument assignments for the customer. HZ_CUST_ACCOUNTS supplies the customer party context for the primary account owner. AR_SYSTEM_PARAMETERS is referenced for Receivables operating configuration, and DUAL is used for single-row evaluations. Underlying bank and account views in the CE and IBY schemas (CE_BANK_BRANCHES_V, IBY_EXT_BANK_ACCOUNTS_V) provide the attributed data types used throughout the package interfaces.

Usage Notes

ARP_EXT_BANK_PKG is an internal application programming interface rather than a standalone user-facing component. It is typically invoked from Receivables forms or concurrent processing that manages customer bank account registration, from Oracle Payments integration flows that require validated external bank account identifiers, and from custom extensions performing bulk customer bank account and receipt method provisioning. Because three other packages reference it, callers should treat the procedures as a layered API: branch and account creation first, followed by assignment and payment method processing. Transaction control is not handled inside the package, so callers are responsible for commit and rollback boundaries.