Results for “transfer_priority”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AP_BANK_CHARGES is a Payables (AP) module table that stores bank charges definition information within Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a configuration master that defines the charges a bank levies when funds are transferred between bank branches. Each row captures the pairing of a transferring (sending) bank branch and a receiving bank branch, the currency in which the charge applies, and a transfer priority that governs charge selection when multiple definitions qualify.
In the ETRM 12.2.2 physical schema the table resides in the AP schema and contains 16 documented columns. Its primary key is AP_BANK_CHARGES_PK, defined on BANK_CHARGE_ID. The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning, which suggests modeling AP_BANK_CHARGES as a satellite keyed to the bank branch and currency dimensions, with descriptive attributes (priority, denormalized bank and branch names) attached. The denormalized name columns indicate the table retains descriptive labels alongside the numeric foreign key identifiers.
Key Information Stored
The surrogate primary key is BANK_CHARGE_ID, which uniquely identifies each bank charge definition. The principal business-rule attributes include:
- TRANSFERRING_BANK_BRANCH_ID — foreign key to AP_BANK_BRANCHES identifying the originating branch.
- RECEIVING_BANK_BRANCH_ID — foreign key to AP_BANK_BRANCHES identifying the destination branch; together with the transferring branch this defines the routing pair the charge applies to.
- CURRENCY_CODE — foreign key to FND_CURRENCIES indicating the currency in which the charge is denominated and selected.
- TRANSFER_PRIORITY — governs which definition is picked when several rows match a given branch-pair and currency combination.
- TRANSFERRING_BANK_NAME, TRANSFERRING_BANK, TRANSFERRING_BRANCH — denormalized descriptive fields for the sending institution.
- RECEIVING_BANK_NAME, RECEIVING_BANK, RECEIVING_BRANCH — denormalized descriptive fields for the receiving institution.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns providing audit lineage.
The composite of transferring branch, receiving branch, and currency acts as the practical business-key candidate; no secondary unique index is documented beyond the surrogate primary key.
Common Use Cases and Queries
AP_BANK_CHARGES is consulted when defining and resolving bank charges for inter-branch fund transfers. A common reporting query joins the table to AP_BANK_BRANCHES to resolve branch names and to FND_CURRENCIES to validate currency:
- Listing all charge definitions for a transferring branch:
SELECT bank_charge_id, receiving_bank_branch_id, currency_code, transfer_priority FROM ap_bank_charges WHERE transferring_bank_branch_id = :branch_id ORDER BY transfer_priority; - Resolving the applicable charge priority for a branch pair and currency by filtering on TRANSFERRING_BANK_BRANCH_ID, RECEIVING_BANK_BRANCH_ID, and CURRENCY_CODE, then ordering by TRANSFER_PRIORITY.
- Auditing configuration currency coverage by grouping records by CURRENCY_CODE.
- Identifying orphaned or stale definitions using the denormalized name columns against current branch records.
Typical consumers include payment setup reports, bank charge configuration extracts, and data-migration validation scripts.
Related Objects
The most significant related objects are:
- AP_BANK_CHARGE_LINES — the child table referencing AP_BANK_CHARGES via BANK_CHARGE_ID; it holds the individual charge amounts or rate lines that make up a charge definition.
- AP_BANK_BRANCHES — referenced twice, through TRANSFERRING_BANK_BRANCH_ID and RECEIVING_BANK_BRANCH_ID, supplying branch master data.
- FND_CURRENCIES — referenced through CURRENCY_CODE, validating the currency of each charge definition.
- AP_BANK_CHARGES_PK — the primary key constraint underpinning BANK_CHARGE_ID.
These relationships establish AP_BANK_CHARGES as the parent of charge-line detail and a dependent of the bank branch and currency reference dimensions.
-
Transfer Priority
-
Transfer Priority
-
Bank charges definition information
-
User Defined Payment Process Request Templates
-
User Defined Payment Process Request Templates
-
Payment batch invoice selection criteria
-
View: AP_CHECKS_V 12.2.2
APPS.AP_CHECKS_V·↳ AP_AUTO_PAYMENT_PKG·↳ AP_CHECKS·↳ AP_CHECKS_PKG·Explore AP module →
-
Temporary storage of invoices selected for payment in a payment batch
-
Temporary storage of invoices selected for payment in a payment batch
-
Bank charges definition information
-
Supplier payment data
-
View: APBV_AP_PAYMENTS 12.2.2
Business view
-
View: APBV_AP_PAYMENTS 12.1.1
Business view
-
No Longer Used
-
Payment batch set lines
-
Payment batch set lines
-
View: AP_PBATCH_SET_LINES_V 12.2.2
APPS.AP_PBATCH_SET_LINES_V·↳ AP_BANK_ACCOUNTS·↳ AP_CHECK_STOCKS·↳ AP_PBATCH_SET_LINES·Explore AP module →
-
View: APFV_AP_PAYMENTS 12.2.2
Business view
-
View: APFV_AP_PAYMENTS 12.1.1
Business view
-
No Longer Used
-
View: AP_PBATCH_SET_LINES_V 12.1.1
APPS.AP_PBATCH_SET_LINES_V·↳ AP_BANK_ACCOUNTS·↳ AP_CHECK_STOCKS·↳ AP_PBATCH_SET_LINES·Explore AP module →
-
Payment batch invoice selection criteria
-
View: AP_CHECKS_V 12.1.1
APPS.AP_CHECKS_V·↳ AP_AUTO_PAYMENT_PKG·↳ AP_CHECKS·↳ AP_CHECKS_PKG·Explore AP module →
-
Supplier payment data
-
VIEW: AP.AP_BANK_CHARGES# 12.2.2
-
VIEW: AP.AP_BANK_CHARGES# 12.2.2
-
TABLE: AP.AP_BANK_CHARGES 12.1.1
-
TABLE: AP.AP_BANK_CHARGES 12.2.2
-
VIEW: APPS.APBV_AP_PAYMENTS 12.2.2
-
View: AP_CHECKS_ALL_MRC_V 12.1.1
MULTI-ORG MRC view
Not implemented in this database·Explore AP module →
-
View: AP_CHECKS_ALL_MRC_V 12.2.2
MULTI-ORG MRC view
Not implemented in this database·Explore AP module →
-
VIEW: APPS.APBV_AP_PAYMENTS 12.1.1
-
View: AP_CHECKS_MRC_V 12.1.1
SINGLE-ORG MRC view
Not implemented in this database·Explore AP module →