Results for “cancellation_code”

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

Overview

The JL_BR_AR_RET_INTERFACE_EXT_V view is a reporting and integration object within the Oracle E-Business Suite Latin America Localizations (JL) module, owned by the APPS schema. It exposes the extended interface records used by the Brazilian Accounts Receivable bank return (retorno) processing. The view consolidates raw return interface data captured from bank remittance return files with descriptive attributes retrieved from lookup, bank occurrence, and party/organization tables, producing a fully denormalized, human-readable result set suitable for inquiry, reconciliation, and error analysis.

Its principal purpose is to translate coded values stored in the underlying interface table into meaningful descriptions. Error codes are resolved to lookup meanings, bank occurrence codes are resolved to their occurrence descriptions, and bank party identifiers are resolved to bank numbers. This makes the view particularly useful for diagnosing rejected or unprocessed return records before or after the Receivables auto-reconciliation and return-processing concurrent programs execute.

Underlying Base Objects

The view is defined over JL_BR_AR_RET_INTERFACE_EXT as its driving table, aliased A, which supplies the transactional return interface rows. It is joined to several supporting objects:

• JL_BR_AR_RET_INTERFACE_EXT – the primary source of return interface records, including amounts, dates, and status codes.
• FND_LOOKUPS – supplies the MEANING for the ERROR_CODE column via lookup type JLBR_AR_BANK_RETURN_ERRORS, restricted to currently effective and enabled lookup values.
• JL_BR_AR_BANK_OCCURRENCES – supplies the occurrence DESCRIPTION, joined on bank occurrence code and bank party, and restricted to occurrence type RETURN_OCCURRENCE.
• HZ_PARTIES (alias BANK) – filters bank parties to active organizations (PARTY_TYPE = 'ORGANIZATION', STATUS = 'A').
• HZ_ORGANIZATION_PROFILES (alias ORG) – derives BANK_NUMBER as BANK_OR_BRANCH_NUMBER, constrained to the currently effective organization profile row.
• FND_GLOBAL – referenced for session context (organization and user identifiers) used in the view definition.

Key Columns

The view exposes the full column set of the return interface, plus derived descriptors. Notable columns include:

• ROW_ID – the ROWID of the underlying interface row, useful for direct updates or drill-back.
• FILE_CONTROL, ENTRY_SEQUENTIAL_NUMBER, REMITTANCE_CODE – identify the return file and the sequential position of the record within it.
• BANK_PARTY_ID, BANK_NUMBER – the bank party identifier and its resolved bank or branch number.
• BANK_OCCURRENCE_CODE, DESCRIPTION, OCCURRENCE_DATE – the occurrence type applied by the bank and its description.
• OUR_NUMBER, YOUR_NUMBER, PORTFOLIO_CODE, INSCRIPTION_NUMBER, COMPANY_USE – identification references carried on the trade note and return.
• TRADE_NOTE_AMOUNT, BANK_CHARGE_AMOUNT, ABATEMENT_AMOUNT, DISCOUNT_AMOUNT, CREDIT_AMOUNT, INTEREST_AMOUNT_RECEIVED – monetary components of the returned transaction.
• ERROR_CODE, ERROR_DESC – the validation error code and its lookup meaning; central to the user's search term context.
• CANCELLATION_CODE – the code indicating cancellation or write-off treatment associated with the return record, used alongside error information to determine the correct accounting action.
• ORG_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – standard multi-org and audit columns.

Common Use Cases and Queries

Typical usage includes investigating rejected return records, reconciling bank charges and discounts, and reviewing cancellation activity. The following example lists return records with their error and cancellation information for a given organization:

SELECT row_id,
       file_control,
       entry_sequential_number,
       bank_number,
       bank_occurrence_code,
       description,
       our_number,
       your_number,
       trade_note_amount,
       error_code,
       error_desc,
       cancellation_code,
       occurrence_date
  FROM apps.jl_br_ar_ret_interface_ext_v
 WHERE org_id = :p_org_id
   AND error_code IS NOT NULL
 ORDER BY entry_sequential_number;

To isolate cancellations specifically, the CANCELLATION_CODE column can be filtered directly, and results joined back to JL_BR_AR_RET_INTERFACE_EXT by ROW_ID when correction of the interface row is required prior to reprocessing.