Results for “previous_doc_status”

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

Overview

The APPS.JL_BR_AR_COLLECTION_DOCS_IOB_V view is a reporting and integration construct within the Oracle E-Business Suite Latin America Localizations (JL) product family, specifically targeting Brazilian accounts receivable collection processing. It presents a consolidated, denormalized projection of collection documents — the individual customer payment obligations grouped into remittance portfolios and borderôs (bank remittance batches) used in the Brazilian banking collection model. The view joins the core collection document table to lookup values, portfolio/borderô generation data, bank instruction descriptions, and trading partner banking data held in the Oracle Receivables and Trading Community (HZ) and Cash Management (CE) schemas.

The view exists primarily to expose collection documents together with decoded, human-readable attributes such as status meanings and document type meanings, while resolving the remittance bank, branch, and account relationships through the HZ party model. This makes it suitable for concurrent program output, Oracle Reports, and outbound integration feeds where a flat, readable row per collection document is required rather than the normalized underlying model.

Underlying Base Objects

The documented 12.2.2 metadata lists the following referenced objects:

• JL_BR_AR_COLLECTION_DOCS (synonym) — the primary driving table, aliased JLCOLL, supplying document identity, status, portfolio code, our number, bank account use, bank charges, and cash accounting flexfield references.
• JL_BR_AR_BORDEROS_ALL (synonym) — aliased BORD, supplying the borderô sequential number and remittance date.
• JL_BR_AR_BANK_INSTRUCTIONS (synonym) — referenced twice (BI and ABI) to resolve bank instruction code descriptions.
• FND_LOOKUPS (view) — referenced twice (LV and DT) to decode document status and document type codes to their meanings.
• CE_BANK_ACCOUNTS and CE_BANK_ACCT_USES_ALL (synonyms) — supplying the bank account number and the account use context.
• HZ_PARTIES, HZ_ORGANIZATION_PROFILES, HZ_RELATIONSHIPS, and HZ_CODE_ASSIGNMENTS (synonyms) — resolving remittance bank and branch party names and institution numbers.
• FND_GLOBAL (package) — referenced for session context such as organization and user identifiers applied through ORG_ID and audit columns.

Key Columns

• ROW_ID, DOCUMENT_ID — the row identifier and the collection document primary key.
• BORDERO_ID, BORDERO_NUMBER, REMITTANCE_DATE — the borderô the document belongs to, its generated sequential number, and the remittance date.
• PAYMENT_SCHEDULE_ID — links the document to the receivable payment schedule.
• DOCUMENT_STATUS, DOCUMENT_STATUS_MEANING — the lookup code and decoded meaning of the collection document status.
• DOC_TYPE_MEANING — the decoded meaning of the document type, resolved from FND_LOOKUPS (DT). This is the column most commonly targeted by searches on doc_type_meaning.
• PREVIOUS_DOC_STATUS, PORTFOLIO_CODE, OUR_NUMBER — prior status, the receivables portfolio identifier, and the seller's own document number.
• BANK_ACCT_USE_ID, BANK_ACCOUNT_NUM — the bank account use and remittance bank account number.
• REMITTANCE_BANK_PARTY_ID, REMITTANCE_BANK_NUMBER, REMITTANCE_BANK_NAME and the corresponding REMITTANCE_BRANCH_* columns — the remittance bank and branch trading partner details.
• BANK_INSTRUCTION_CODE1/2, BANK_INSTRUCTION1/2 — instruction codes and their descriptions.
• BANK_CHARGES_CCID, CASH_CCID, BANK_CHARGE_AMOUNT — accounting flexfield references and the bank charge amount.
• ORG_ID and the audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — multi-org and standard WHO audit attributes.

Common Use Cases and Queries

Typical uses include reporting on collection documents by type and status, reconciling borderô contents prior to bank remittance, and extracting decoded document data for integration. A representative query filtering on the decoded document type is:

• SELECT document_id, our_number, portfolio_code, doc_type_meaning, document_status_meaning, bordero_number, remittance_date, remittance_bank_name FROM jl_br_ar_collection_docs_iob_v WHERE doc_type_meaning = :p_type AND org_id = :p_org;
• SELECT bordero_number, COUNT(*) doc_count, SUM(bank_charge_amount) charges FROM jl_br_ar_collection_docs_iob_v GROUP BY bordero_number;
• SELECT document_id, remittance_bank_number, remittance_branch_number, bank_account_num FROM jl_br_ar_collection_docs_iob_v WHERE document_status = :p_status;

Because the view resolves meanings through FND_LOOKUPS and joins across HZ and CE objects, queries should be constrained by ORG_ID in a multi-org environment and supplied with the appropriate lookup context to avoid ambiguous decodes.