Results for “document_amount”

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

Overview

JL_BR_AR_OCCURRENCE_DOCS_V is an Oracle E-Business Suite dictionary view owned by the APPS schema and defined over the Brazilian Accounts Receivable localization tables within the JL (Latin America Localizations) product family. It consolidates the relationship between bank occurrences and the receivable documents affected by those occurrences, exposing each occurrence-document pairing together with the full set of financial, banking, and accounting attributes required for remittance processing, bank return handling, bordero (remittance batch) management, and portfolio reporting.

The view is used primarily for reporting and integration of Brazilian AR banking events. In the context of the 12.1.1 and 12.2.2 releases, it supports the automated matching of bank occurrence files against open receivables, the calculation of interest, discounts, abatements, endorsements, and bank charges, and the posting of resulting accounting entries. Because the view encapsulates joins across occurrence headers, bordero headers, and customer/bank party data, it allows reporting tools, concurrent programs, and custom extensions to retrieve a denormalized, business-ready representation of each occurrence-document line without reconstructing the underlying relationships.

Underlying Base Objects

The documented base objects are JL_BR_AR_OCCURRENCE_DOCS_ALL (the primary occurrence-document association table), JL_BR_AR_BANK_OCCURRENCES (the occurrence header), JL_BR_AR_BORDEROS_ALL (the bordero or remittance batch header), HZ_PARTIES, and HZ_ORGANIZATION_PROFILES. Each is referenced through APPS-owned synonyms.

The view's driving table is the occurrence-documents table, aliased JLOCC in the view text; its ROWID is published as ROW_ID to allow updatable-view behavior. Occurrence and bordero header information is joined to supply the bordero identifier, portfolio code, and trade note number. Party and organization profile data supply bank identification, notably the BANK_OR_BRANCH_NUMBER derived through BANKPROFILE, which resolves the bank party to its registered branch number. Taken together, these joins translate normalized banking and customer identifiers into the descriptive fields required for localized reporting.

Key Columns

• OCCURRENCE_ID / DOCUMENT_ID — Identify the bank occurrence header and the affected receivable document.
• BANK_OCCURRENCE_CODE / BANK_OCCURRENCE_TYPE — The bank-assigned occurrence identifier and standardized occurrence type, used to classify the return event. The std_occurrence_code search term maps conceptually to this code family, which drives occurrence processing logic.
• BANK_NUMBER / BANK_PARTY_ID — Bank identification, with BANK_NUMBER resolved through the organization profile join.
• OCCURRENCE_DATE / SELECTION_DATE / DUE_DATE — Occurrence date, the date the document was selected into processing, and the document due date.
• DOCUMENT_AMOUNT / ABATEMENT_AMOUNT / DISCOUNT_AMOUNT / BANK_CHARGE_AMOUNT — Core financial amounts applied to the document.
• INTEREST_PERCENT / INTEREST_PERIOD / INTEREST_AMOUNT / GRACE_DAYS — Interest and grace-period calculation attributes.
• BORDERO_ID / PORTFOLIO_CODE / TRADE_NOTE_NUMBER — Remittance batch and portfolio grouping attributes.
• ENDORSEMENT_*_CCID / BANK_CHARGES_*_CCID and amounts — Debit and credit accounting flexfield identifiers and amounts for endorsements and bank charges.
• FLAG_POST_GL / GL_DATE / GL_POSTED_DATE — Accounting status, intended GL date, and actual posting date.
• REMITTANCE_MEDIA / ORIGINAL_REMITTANCE_MEDIA / REQUEST_ID — Media selection, original media, and the request that generated the record.
• CUSTOMER_ID / SITE_USE_ID — Customer and site context for the document.

Common Use Cases and Queries

Typical scenarios include reconciling bank return files to open receivables, reviewing non-posted occurrences awaiting GL transfer, auditing bordero contents by portfolio, and analyzing bank charges and interest by occurrence type.

• List occurrences pending accounting:

  SELECT occurrence_id, document_id, document_amount, gl_date
  FROM   jl_br_ar_occurrence_docs_v
  WHERE  flag_post_gl = 'N';

• Summarize bank charges and interest by occurrence type:

  SELECT bank_occurrence_type,
         SUM(bank_charge_amount) bank_charges,
         SUM(interest_amount) interest
  FROM   jl_br_ar_occurrence_docs_v
  GROUP  BY bank_occurrence_type;

• Retrieve documents by bordero and portfolio:

  SELECT bordero_id, portfolio_code, trade_note_number, document_id, due_date
  FROM   jl_br_ar_occurrence_docs_v
  WHERE  bordero_id = :p_bordero_id;

Because ROW_ID is exposed, the view can support restricted updates when the underlying join preserves key information; however, most usage is read-only reporting and integration.