Results for “other_accretions”

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

Overview

The JL_BR_AP_INT_COLLECT_EXT_ALL table is a Latin America Localizations (JL) object owned by the JL schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the exception or rejection repository for the Brazilian accounts payable bank collection interface. When records loaded into the working interface table JL_BR_AP_INT_COLLECT fail validation, or when processing errors occur during the collection remittance cycle, the offending rows are diverted into this table for isolation, review, and subsequent correction or resubmission. This separation keeps the primary interface clean for successful processing while preserving a complete audit trail of rejected data.

From a data modeling perspective, the supplied metadata classifies this table heuristically as standalone, with no documented foreign key dependencies. A Data Vault assessment would treat it as a satellite-like structure recording error and rejection context, whose business key component aligns with the source collection interface rather than acting as a true hub or link.

Key Information Stored

The table contains 74 documented columns. The most operationally significant are listed below:

• FILE_CONTROL and ENTRY_SEQUENTIAL_NUMBER — together form the composite primary key JL_BR_AP_COLLECT_EXT_PK and the unique index JL_BR_AP_COLLECT_EXT_U1. FILE_CONTROL identifies the bank file (retorno) batch, and ENTRY_SEQUENTIAL_NUMBER sequences each record within that file.
• REGISTRY_CODE, RETURN_CODE, SERVICE_CODE, CNAB_CODE — Brazilian CNAB banking layout codes conveying the return reason and service type.
• DOCUMENT_NUMBER, DUE_DATE, AMOUNT — core collection document identity and financial values.
• DRAWER_GUARANTOR, DRAWEE_NAME, DRAWEE_BANK_CODE, DRAWEE_ACCOUNT_NUMBER — payer and drawee banking details.
• ERROR_CODE — the specific reason the record was rejected from the main interface.
• SET_OF_BOOKS_ID, ORG_ID, LAST_UPDATE_DATE, CREATED_BY — standard Multi-Org and audit/WHO columns tracking ledger, operating unit, and user activity.
• ATTRIBUTE1 through ATTRIBUTE15 and ELECTRONIC_FORMAT_FLAG — descriptive flexfield and format indicators for extension and identification.

Common Use Cases and Queries

Typical usage centers on diagnosing and correcting collection interface failures. A support analyst might retrieve all rejected documents for a specific bank file:

• SELECT FILE_CONTROL, ENTRY_SEQUENTIAL_NUMBER, DOCUMENT_NUMBER, ERROR_CODE, AMOUNT FROM JL_BR_AP_INT_COLLECT_EXT_ALL WHERE FILE_CONTROL = :file_control;
• Reporting by error cause: SELECT ERROR_CODE, COUNT(*) FROM JL_BR_AP_INT_COLLECT_EXT_ALL GROUP BY ERROR_CODE;
• Joining back to the interface to confirm successful resubmission after corrections.

These queries support reconciliation reporting, error trend analysis, and operational dashboards for treasury and accounts payable teams processing Brazilian bank returns.

Related Objects

The most significant related objects are the interface and setup tables that feed or complement this exception store:

• JL_BR_AP_INT_COLLECT — the primary collection interface; rejected rows originate here and share the FILE_CONTROL, ENTRY_SEQUENTIAL_NUMBER, DOCUMENT_NUMBER, and ERROR_CODE columns.
• JL_BR_AP_INT_COLLECT_EXT_ALL variants and staging objects that populate the interface.
• JL_BR_AR_BANK_OCCURRENCES (or equivalent occurrence code setup) — supplies RETURN_CODE and CNAB_CODE meanings.
• AP_INVOICES_ALL — the eventual target to which accepted collections are applied.
• HR_OPERATING_UNITS and GL_SETS_OF_BOOKS — resolve ORG_ID and SET_OF_BOOKS_ID context.

Collectively these objects demonstrate how JL_BR_AP_INT_COLLECT_EXT_ALL isolates invalid Brazilian collection records for correction while preserving essential banking and error diagnostics.