Results for “status_lookup_code”

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

Overview

JL_BR_AP_COLLECTION_DOCS_ALL is a Brazilian localization table owned by the JL schema within Oracle E-Business Suite, and it is validated in both release 12.1.1 and 12.2.2. The table stores detailed bank collection document records (cobrança bancária) generated for Payables transactions, capturing the instructions, charges, and status information that a Brazilian company exchanges with its banking partners when it places unpaid supplier invoices into a bank collection portfolio for settlement. The "_ALL" suffix indicates a multi-organization structure, and the table carries an ORG_ID column consistent with that convention, though it is registered as a localization detail table rather than a partitioned transactional entity.

From a Data Vault modeling perspective, the documented foreign key structure suggests classification as a link: the table connects payment schedule records, vendor and vendor site master data, currency definitions, bank branches, and accounting sets of books into a single collection document event. The documented unique index JL_BR_AP_COLLECTION_DOCS_U1 on BANK_COLLECTION_ID supports its role as a connectable business object rather than a pure descriptive satellite.

Key Information Stored

The table is documented with 78 columns. The surrogate primary key exposed through the JL_BR_AP_COLLEC_DOC_PK constraint is BANK_COLLECTION_ID, and the same column appears in the unique index JL_BR_AP_COLLECTION_DOCS_U1, making it both the physical identifier and the primary business-key candidate.

• INVOICE_ID and PAYMENT_NUM — the payment schedule reference identifying the payable being collected.
• VENDOR_ID, VENDOR_SITE_ID, and BRANCH_PARTY_ID / BANK_PARTY_ID — supplier and banking party context.
• CURRENCY_CODE, AMOUNT, DISCOUNT_DATE, DISCOUNT_AMOUNT, PENALTY_FEE_AMOUNT, PENALTY_FEE_DATE, ARREARS_INTEREST, ABATE_AMOUNT, PAID_AMOUNT — the financial settlement amounts and charges associated with the collection.
• ISSUE_DATE, DUE_DATE, PROCESSING_DATE, and ENTRY_SEQUENTIAL_NUMBER — lifecycle dates and ordering.
• DOCUMENT_NUMBER, DOCUMENT_TYPE, ACCEPTANCE, OUR_NUMBER, PORTFOLIO, FILE_CONTROL, and BARCODE — the printed and electronically exchanged collection document attributes.
• STATUS_LOOKUP_CODE, HOLD_FLAG, and ELECTRONIC_FORMAT_FLAG — processing state and format control.
• SET_OF_BOOKS_ID and ORG_ID — accounting and multi-organization context.

Common Use Cases and Queries

Typical reporting includes monitoring open collection documents by vendor, aging unpaid portfolios, reconciling bank returns against recorded payments, and generating remittance files. A representative query pattern joins the table to the payment schedules and vendor master:

• SELECT c.bank_collection_id, c.document_number, c.amount, c.due_date, c.status_lookup_code FROM jl_br_ap_collection_docs_all c WHERE c.org_id = :p_org AND c.status_lookup_code = 'OPEN';
• Invoice-level drill-down: join INVOICE_ID and PAYMENT_NUM to AP_PAYMENT_SCHEDULES_ALL to tie collection documents back to the originating invoice installments.
• Currency exposure: join CURRENCY_CODE to FND_CURRENCIES for reporting totals by currency.
• Bank and branch analysis: join BANK_BRANCH_ID to AP_BANK_BRANCHES and VENDOR_ID to PO_VENDORS for portfolio summaries.

Related Objects

The documented referential relationships identify the following significant dependent and referenced objects:

• AP_PAYMENT_SCHEDULES_ALL — via INVOICE_ID and PAYMENT_NUM.
• FND_CURRENCIES — via CURRENCY_CODE.
• PO_VENDOR_SITES_ALL — via VENDOR_SITE_ID.
• GL_SETS_OF_BOOKS_11I — via SET_OF_BOOKS_ID.
• PO_VENDORS — via VENDOR_ID.
• AP_BANK_BRANCHES — via BANK_BRANCH_ID.