Results for “check_range_overlap”

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

Overview

APPS.AP_BANK_CHARGE_PKG is a Payables-side PL/SQL package that centralizes the business logic governing bank charges in Oracle E-Business Suite. Bank charges represent the fees levied by transferring and receiving banks on international payments and fund transfers, and they may be borne by the payer, the payee, or shared. This package resolves the correct charge for a given transaction context, validates the configuration of bank charge setups, and exposes a hook point used by Oracle Payments during payment processing. It is the programmatic engine behind the Bank Charges setup and the automatic calculation of bank charge amounts on payments.

The package header carries the RCS identifier apsudbcs.pls 120.4 2006/09/27, confirming its lineage in the Payables product family. In ETRM 12.2.2 it is classified as API classification OTHER, indicating it is not a formally published public API and should be treated as internal infrastructure. The presence of the ap_JapanBankChargeHook procedure reflects the Japan-specific payment processing requirements, where bank charges are calculated and applied differently from other localizations.

Key Procedures and Functions

The package exposes nine documented procedures. They fall into three functional groups.

• Bank and branch resolution — GET_BANK_NUMBER retrieves the bank number for a supplied bank name. GET_BANK_BRANCH_NAME resolves the bank number, branch number, and branch name for a given bank branch identifier.
• Bank combination and charge-range validation — CHECK_BANK_COMBINATION validates a transferring/receiving bank and branch pairing together with transfer priority and currency. CHECK_RANGE_OVERLAP, CHECK_RANGE_GAP, and CHECK_LAST_RANGE enforce the integrity of the amount ranges defined for bank charges, detecting overlapping ranges, gaps in coverage, and an improper final range.
• Charge calculation and inquiry — GET_BANK_CHARGE is the core computation routine. Given the charge bearer, transferring and receiving bank branches, transfer priority, currency, transaction amount and date, it returns the standard and negotiated charge amounts, the calculated standard and negotiated amounts, and the tolerance limit. CHECK_BANK_CHARGE performs a companion validation and returns a check flag plus a do-not-pay reason when the charge is not permitted.
• Japan localization hook — AP_JAPANBANKCHARGEHOOK is invoked by Oracle Payments when the Japan bank charge rules apply, allowing the standard charge to be replaced or adjusted.

Tables Accessed

The package operates across Payables, Cash Management, and Payments schemas via APPS synonyms.

• AP_BANK_CHARGES and AP_BANK_CHARGE_LINES — the setup and range definitions that determine which charge applies to a transaction; these drive the range validation and calculation logic.
• IBY_HOOK_PAYMENTS_T and IBY_HOOK_DOCS_IN_PMT_T — the Payments hook tables that supply payment and document context to the Japan bank charge hook.
• CE_BANK_ACCOUNTS and IBY_EXT_BANK_ACCOUNTS — internal and external bank account definitions used to resolve bank and branch identifiers.
• AP_SYSTEM_PARAMETERS_ALL — system-level Payables options that affect charge processing.
• AP_SUPPLIER_SITES_ALL and AP_INV_SELECTION_CRITERIA_ALL — supplier site and selection criteria context.
• FND_CURRENCIES — currency validation and precision for charge amounts.

Usage Notes

Because this package is classified as OTHER rather than as a public API, direct invocation from custom code is discouraged; Oracle does not guarantee the signature across patches. The package is most commonly reached indirectly: through the Bank Charges setup forms (APXBCSBR or equivalent), through the Payables payment workbench during payment creation and validation, and through Oracle Payments when the Japan bank charge hook is triggered. The AP_JAPANBANKCHARGEHOOK entry point is registered so that the Payments engine can call back into Payables for Japan-localized charge determination. Customizations that require charge information should preferentially query AP_BANK_CHARGES and AP_BANK_CHARGE_LINES, or call GET_BANK_CHARGE only after confirming the procedure remains unchanged in the target patch level. ETRM records that the package is referenced by one other database package, indicating limited internal coupling and a restricted call surface.