Results for “jlbr_ar_bank_return_errors”

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

Overview

The view APPS.JL_BR_AR_RET_INTERFACE_EXT_V is a reporting and inquiry layer over the Brazilian localizations (JL_BR) bank return interface in Oracle E-Business Suite. It presents processed and pending bank return records for the Brazilian Accounts Receivable (AR) remittance and collection flow, exposing the raw staging data held in JL_BR_AR_RET_INTERFACE_EXT together with resolved descriptive attributes. Its principal value lies in translating opaque codes into user-readable text: bank occurrence codes are decorated with descriptions from JL_BR_AR_BANK_OCCURRENCES, bank identifiers are resolved through HZ_PARTIES and HZ_ORGANIZATION_PROFILES, and error codes are resolved to meanings using the JLBR_AR_BANK_RETURN_ERRORS lookup type in FND_LOOKUPS. The user search term jlbr_ar_bank_return_errors corresponds directly to the lookup type driving the error description column, making this view the primary target for diagnosing bank return validation failures. The view is documented in ETRM for both 12.1.1 and 12.2.2 with identical structure.

Underlying Base Objects

The view is defined over the following documented base objects:

• JL_BR_AR_RET_INTERFACE_EXT (synonym) — the primary staging table holding bank return interface records; aliased as A.
• FND_LOOKUPS (view) — aliased as B; supplies MEANING for the ERROR_DESC column, restricted to lookup type JLBR_AR_BANK_RETURN_ERRORS and to currently active, enabled lookup codes.
• JL_BR_AR_BANK_OCCURRENCES (synonym) — aliased as C; provides occurrence descriptions and enforces that only return-type occurrences (BANK_OCCURRENCE_TYPE = 'RETURN_OCCURRENCE') are joined.
• HZ_PARTIES (synonym) — aliased as BANK; identifies the bank as an active organization party.
• HZ_ORGANIZATION_PROFILES (synonym) — aliased as ORG; supplies BANK_OR_BRANCH_NUMBER and constrains the row to the profile effective as of the current date.
• FND_GLOBAL (package) — referenced in the metadata as a base object, typically for session/multi-org context resolution.

The joins are all inner joins keyed on bank party, occurrence code, and lookup code, so the view returns only rows for which a valid occurrence, active lookup, and active bank organization profile all exist.

Key Columns

• FILE_CONTROL, ENTRY_SEQUENTIAL_NUMBER — bank file identifier and record sequencing for the return file.
• COMPANY_CODE, COMPANY_NAME — the owning company/legal entity for the transaction.
• BANK_PARTY_ID, BANK_NUMBER — the bank party identifier and its resolved bank/branch number.
• BANK_OCCURRENCE_CODE, DESCRIPTION — the occurrence code and its description from JL_BR_AR_BANK_OCCURRENCES.
• ERROR_CODE, ERROR_DESC — the return error code and the lookup meaning from JLBR_AR_BANK_RETURN_ERRORS; central to error diagnostics.
• INSCRIPTION_NUMBER, PORTFOLIO_CODE, OUR_NUMBER, YOUR_NUMBER — trade note / portfolio identifying references.
• DUE_DATE, OCCURRENCE_DATE, PROCESSING_DATE, LAST_VALIDATION_DATE — dates relevant to the return event lifecycle.
• TRADE_NOTE_AMOUNT, BANK_CHARGE_AMOUNT, ABATEMENT_AMOUNT, DISCOUNT_AMOUNT, CREDIT_AMOUNT, INTEREST_AMOUNT_RECEIVED — monetary components of the returned trade note.
• CUSTOMER_NAME, RETURN_INFO, BANK_USE, COMPANY_USE — descriptive and free-text attributes carried from the bank file.
• CANCELLATION_CODE, ORG_ID — cancellation indicator and operating unit identifier.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, ROW_ID — standard audit columns.

Common Use Cases and Queries

Typical scenarios include diagnosing bank return errors before or after the Brazilian AR return concurrent program runs, reconciling returned trade notes against the bank file, and reporting on returns per bank or portfolio. Because the view joins on the active lookup and current organization profile, it naturally excludes stale error codes and inactive banks.

To list all current return errors with descriptions:

• SELECT ERROR_CODE, ERROR_DESC, COUNT(*) FROM JL_BR_AR_RET_INTERFACE_EXT_V GROUP BY ERROR_CODE, ERROR_DESC ORDER BY 3 DESC;
• SELECT INSCRIPTION_NUMBER, PORTFOLIO_CODE, BANK_NUMBER, ERROR_DESC, OCCURRENCE_DATE FROM JL_BR_AR_RET_INTERFACE_EXT_V WHERE ERROR_CODE IS NOT NULL AND ORG_ID = :p_org_id ORDER BY OCCURRENCE_DATE DESC;
• SELECT BANK_NUMBER, CUSTOMER_NAME, TRADE_NOTE_AMOUNT, BANK_CHARGE_AMOUNT, PROCESSING_DATE FROM JL_BR_AR_RET_INTERFACE_EXT_V WHERE TRUNC(PROCESSING_DATE) BETWEEN :start_date AND :end_date;