Results for “invoice_currency_code”

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

Overview

JL_BR_AP_SICI_INVOICES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the JL (Latin America Localizations) product family with specific applicability to the Brazilian localization. The view consolidates invoice information originating from two distinct sources into a single, uniform result set. The name references SICI, the Brazilian system for consolidated supplier invoice information (Sistema de Informações de Créditos de Fornecedores / consolidated invoice reporting), which is used to satisfy local fiscal and regulatory reporting obligations.

The view presents a unified list of payables invoice records, distinguishing between consolidated invoices and standard invoices through a discriminator column. Because it is a view rather than a table, it exposes no independent storage; all data is derived at query time from its underlying base objects. Its status is documented as VALID in the ETRM repository for release 12.2.2, and it is equally available in 12.1.1 installations where the Brazilian localization is licensed and enabled.

Underlying Base Objects

The view is defined over two synonym-referenced base objects: AP_INVOICES and JL_BR_AP_CONSOLID_INVOICES. It is implemented as a UNION of two SELECT statements. The first branch selects from JL_BR_AP_CONSOLID_INVOICES, tagging each row with the literal value 'CI' (Consolidated Invoice) in the SICI column. The second branch selects from AP_INVOICES, tagging rows with the literal value 'SI' (Standard Invoice), and imposes two filter predicates: GLOBAL_ATTRIBUTE10 must be NULL, and INVOICE_TYPE_LOOKUP_CODE must equal 'STANDARD'.

The GLOBAL_ATTRIBUTE10 IS NULL condition is significant: consolidated invoices originating in JL_BR_AP_CONSOLID_INVOICES are typically flagged in AP_INVOICES through that descriptive flexfield attribute, so excluding rows where GLOBAL_ATTRIBUTE10 is populated prevents double counting between the two branches of the union. Only standard invoice types are surfaced from the payables table, meaning prepayments, credit memos, debit memos, and other non-standard invoice types are excluded.

Key Columns

• SICI — Discriminator flag; 'CI' identifies consolidated invoices and 'SI' identifies standard invoices.
• INVOICE_ID — Unique invoice identifier, sourced from CONSOLIDATED_INVOICE_ID for consolidated rows and from INVOICE_ID for standard rows.
• INVOICE_NUM — The invoice number, the primary attribute matched by users searching for a specific document.
• VENDOR_ID / VENDOR_SITE_ID — Supplier and supplier site identifiers associated with the invoice.
• INVOICE_DATE — Date of the invoice, used for period and fiscal cutoff reporting.
• INVOICE_CURRENCY_CODE / INVOICE_AMOUNT — Invoice currency and gross invoice amount.
• INVOICE_TYPE_LOOKUP_CODE — Populated as NULL for consolidated rows; carries the lookup value for standard rows.
• ORG_ID — Operating unit identifier, supporting multi-organization security filtering.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is primarily used for Brazilian fiscal reporting, supplier credit reconciliation, and cross-referencing consolidated invoices against their constituent standard invoices. A frequent requirement is locating an invoice by its number, as reflected in the search term "invoice_num":

• SELECT sici, invoice_id, invoice_num, invoice_date, vendor_id, invoice_amount FROM apps.jl_br_ap_sici_invoices_v WHERE invoice_num = :invoice_num;
• SELECT sici, COUNT(*) FROM apps.jl_br_ap_sici_invoices_v WHERE org_id = :org_id GROUP BY sici;
• SELECT invoice_num, invoice_amount, invoice_currency_code FROM apps.jl_br_ap_sici_invoices_v WHERE vendor_id = :vendor_id AND invoice_date BETWEEN :start_date AND :end_date;

Because the view performs a UNION, queries against INVOICE_NUM benefit from indexed access on the underlying AP_INVOICES table; unrestricted full scans should be avoided in high-volume environments. Downstream reporting typically joins the view to AP_SUPPLIERS and HR operating unit tables using VENDOR_ID and ORG_ID respectively.