Search Results trans_amount_from

Overview

The AP_BANK_CHARGE_LINES table is a core data structure within the Oracle E-Business Suite Payables (AP) module, specifically for versions 12.1.1 and 12.2.2. It serves as a configuration table that defines tiered or ranged rules for bank charges and tolerance limits. These rules are applied during payment processing to automatically calculate expected bank fees or to determine acceptable variances for payment amounts. The table's primary role is to support the automated financial logic required for accurate payment execution and reconciliation by associating specific charge amounts or tolerance percentages with defined transaction value ranges.

Key Information Stored

The table stores the parameters that define each range or tier for a bank charge rule. The primary key is a composite of BANK_CHARGE_ID, TRANS_AMOUNT_FROM, TRANS_AMOUNT_TO, and START_DATE, ensuring uniqueness for overlapping date-effective ranges. Critical columns include BANK_CHARGE_ID, which links to the parent charge definition in the AP_BANK_CHARGES table. The TRANS_AMOUNT_FROM and TRANS_AMOUNT_TO columns define the lower and upper bounds, respectively, of the transaction amount range to which the rule applies. Other columns typically include attributes like a fixed charge amount, a percentage-based charge rate, and tolerance percentages for overpayments and underpayments, which are configured per amount range.

Common Use Cases and Queries

A primary use case is determining the applicable bank charge for a specific payment draft during payment format generation. The system queries this table to find the rule where the payment amount falls between the TRANS_AMOUNT_FROM and TRANS_AMOUNT_TO values for the relevant BANK_CHARGE_ID. For reporting, administrators may analyze charge structures. A sample query to find all charge lines for a specific bank account, effective as of a certain date, would be:

• SELECT abcl.trans_amount_from, abcl.trans_amount_to, abcl.charge_amount FROM ap_bank_charge_lines abcl JOIN ap_bank_charges abc ON abcl.bank_charge_id = abc.bank_charge_id WHERE abc.bank_account_id = :p_bank_acct_id AND :p_payment_date BETWEEN abcl.start_date AND NVL(abcl.end_date, SYSDATE) ORDER BY abcl.trans_amount_from;

The user's search for "trans_amount_from" indicates a likely need to understand or query the lower boundary of these configured transaction amount ranges.

Related Objects

The AP_BANK_CHARGE_LINES table has a direct, documented foreign key relationship to the parent table AP_BANK_CHARGES. This relationship is defined on the BANK_CHARGE_ID column. The AP_BANK_CHARGES table holds the master definition for a bank charge, including the bank account it applies to. Therefore, AP_BANK_CHARGE_LINES is a child table, storing the detailed, amount-specific rules for each parent charge definition. This structure allows a single bank charge setup in AP_BANK_CHARGES to have multiple, granular tiers (lines) based on payment value.