Results for “jlbr_ar_document_type”

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

Overview

APPS.JL_BR_AR_COLLECTION_DOCS_IOB_V is a Brazilian localization (JL_BR) reporting view within Oracle E-Business Suite, designed to expose Accounts Receivable collection documents in a denormalized, reporting-friendly format. The view consolidates data from the core collection document table, bordero (remittance batch) records, bank instruction definitions, and Oracle Receivables/Human Resources (HZ) party and bank account structures. Its principal role is to support Brazilian bank collection (cobrança) reporting and integration with financial institutions, presenting remittance, bordero, and bank instruction details alongside human-readable lookup meanings.

For a user searching on jlbr_ar_document_type, this view is the relevant access point: the DOC_TYPE_MEANING column is derived from the FND_LOOKUPS lookup type joined via the DT alias, providing the document type meaning that the "document type" search term references. The _IOB suffix in the view name indicates an interface/output-bank oriented view commonly used in Brazilian bank file generation and reporting for collection documents.

Underlying Base Objects

Per the documented metadata (ETRM 12.2.2), the view is defined over the following base objects, primarily accessed through APPS synonyms:

• JL_BR_AR_COLLECTION_DOCS (synonym) — the driving table containing the collection document records.
• JL_BR_AR_BORDEROS_ALL (synonym) — bordero (remittance batch) header information.
• JL_BR_AR_BANK_INSTRUCTIONS (synonym) — instruction codes and their descriptions, used twice (aliases BI and ABI) for instruction codes 1 and 2.
• CE_BANK_ACCOUNTS and CE_BANK_ACCT_USES_ALL (synonyms) — bank account number and account usage details.
• HZ_PARTIES, HZ_ORGANIZATION_PROFILES, HZ_CODE_ASSIGNMENTS, HZ_RELATIONSHIPS (synonyms) — remittance bank, branch, and party name/number resolution.
• FND_LOOKUPS (view) — lookup meanings for document status and document type.
• FND_GLOBAL (package) — supplies organization/context values such as ORG_ID for multi-org security.

The joins connect each collection document to its bordero, remittance bank and branch, bank account, and the associated lookup meanings.

Key Columns

• DOCUMENT_ID, BORDERO_ID, PAYMENT_SCHEDULE_ID — primary identifiers linking the document to its batch and receivable schedule.
• DOCUMENT_STATUS / DOCUMENT_STATUS_MEANING — lookup code and its translated meaning.
• DOC_TYPE_MEANING — the document type description from FND_LOOKUPS (the jlbr_ar_document_type lookup), central to document-type classification.
• OUR_NUMBER, PORTFOLIO_CODE — bank-assigned reference number and portfolio grouping.
• BANK_INSTRUCTION_CODE1/2 with BANK_INSTRUCTION1/2 — instruction codes and their descriptions.
• REMITTANCE_BANK_NAME, REMITTANCE_BANK_NUMBER, REMITTANCE_BRANCH_NAME, REMITTANCE_BRANCH_NUMBER — remittance bank and branch details.
• BANK_ACCOUNT_NUM, BORDERO_NUMBER, REMITTANCE_DATE, BANK_CHARGE_AMOUNT — account, batch, date, and charge amounts.
• Audit and multi-org columns: CREATION_DATE, LAST_UPDATE_DATE, ORG_ID.

Common Use Cases and Queries

Typical scenarios include reconciling collection documents to borderos, generating Brazilian bank remittance reports, and validating document types against the jlbr_ar_document_type lookup.

SELECT document_id,
       our_number,
       doc_type_meaning,
       document_status_meaning,
       bordero_number,
       remittance_bank_name,
       remittance_date,
       bank_charge_amount
FROM   apps.jl_br_ar_collection_docs_iob_v
WHERE  org_id = :p_org_id
AND    remittance_date BETWEEN :p_from AND :p_to;

To filter by a specific Brazilian AR document type, constrain doc_type_meaning or join FND_LOOKUPS directly on the jlbr_ar_document_type lookup type. Multi-org security is enforced through ORG_ID; always include it in operational queries.