Results for “ap_payment_programs”

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

Overview

The JL_BR_AR_REC_MET_ACCTS_EXT_V view, owned by the APPS schema, is a Latin America Localizations (JL) object that exposes the extended receipt method accounting configuration for Brazilian Receivables (JL BR AR). It denormalizes the JL_BR_AR_REC_MET_ACCTS_EXT_ALL base table, which stores the account code combinations (CCIDs) and control attributes used by Oracle Receivables when automatically calculating and posting interest, factoring, abatements, bank charges, and endorsements for a given combination of bank account use and receipt method. Because the underlying data is held in an _ALL table with a ROWID-based alias, the view is functionally an informational and reporting layer: it presents each configuration row identified by its ROW_ID together with resolved lookup meanings (for example GL_DATE_BANK_RETURN_DSP from FND_LOOKUPS) rather than storing data itself. For integrators and report developers working in EBS 12.1.1 or 12.2.2, this view is the canonical read-only entry point for retrieving accounting flexfield references such as INTEREST_REVENUE_CCID, which is precisely the column that surfaces the interest revenue account configured for a receipt method and bank account use combination.

Underlying Base Objects

ETRM metadata for 12.2.2 documents the following referenced objects: JL_BR_AR_REC_MET_ACCTS_EXT_ALL (the primary base table supplying all account and control columns); JL_BR_AR_BANK_INSTRUCTIONS; and the standard Receivables and Cash Management synonyms AR_RECEIPT_METHODS, AR_RECEIPT_CLASSES, AR_BATCH_SOURCES, AR_RECEIVABLES_TRX_ALL, CE_BANK_ACCOUNTS, and CE_BANK_ACCT_USES_ALL. Supporting objects include HZ_PARTIES, HZ_ORGANIZATION_PROFILES, AP_PAYMENT_PROGRAMS, the FND_LOOKUPS view, and the FND_GLOBAL package. The view joins these to resolve bank, party, receipt class, and lookup descriptions while preserving the BANK_ACCT_USE_ID and RECEIPT_METHOD_ID foreign keys that identify each configuration row.

Key Columns

• ROW_ID — the ROWID of the base record, useful for updates or direct navigation.
• BANK_ACCT_USE_ID and RECEIPT_METHOD_ID — the composite key linking a receipt method to a specific bank account use.
• INTEREST_REVENUE_CCID — the code combination for the interest revenue account; the column most commonly sought by users searching this view.
• CALCULATED_INTEREST_CCID, INTEREST_WRITEOFF_CCID, FACTORING_INTEREST_CCID, ABATEMENT_WRITEOFF_CCID, ABATEMENT_REVENUE_CCID, BANK_CHARGES_CCID, COLL_ENDORSEMENT_CCID, BILLS_COLLECTION_CCID, OTHER_CREDITS_CCID, FACTORING_DOCS_CCID, DISC_ENDORSEMENT_CCID, DISCOUNTED_BILLS_CCID, BILLS_DISCOUNT_CCID, and FACTORING_CHARGES_CCID — the full set of accounting destinations.
• Amount and rate controls: MIN_DOCUMENT_AMOUNT, MAX_DOCUMENT_AMOUNT, MIN_REMITTANCE_AMOUNT, MAX_REMITTANCE_AMOUNT, FACTORING_RATE, FACTORING_RATE_PERIOD, WRITEOFF_PERC_TOLERANCE, WRITEOFF_AMOUNT_TOLERANCE, FLOATING.
• GL_DATE_BANK_RETURN and its display column GL_DATE_BANK_RETURN_DSP — the general ledger date rule for bank returns, resolved from lookups.

Common Use Cases and Queries

The primary business use case is verifying which accounting accounts Oracle Receivables will use when it automatically creates interest, write-off, factoring, or abatement entries for a receipt method. A typical query returns the interest revenue configuration:

• SELECT receipt_method_id, bank_acct_use_id, interest_revenue_ccid FROM jl_br_ar_rec_met_accts_ext_v WHERE interest_revenue_ccid IS NOT NULL;
• Join to GL_CODE_COMBINATIONS on the CCID to display the actual account segments for reconciliation or audit.
• Filter by receipt_method_id and bank_acct_use_id to confirm the effective tolerance and rate settings before running automatic receipt processing.
• Use alongside FND_LOOKUPS output columns to validate the GL date rule applied on bank returns.

Because the view is a pure projection over JL_BR_AR_REC_MET_ACCTS_EXT_ALL, querying it is safe for reporting; any maintenance of the underlying configuration must be performed against the base table through the Brazil AR setup forms.