Search Results invoice_type_lookup_code




Overview
Explore in AI Chat

Overview

APPS.JL_BR_AP_SICI_INVOICES_V is a Brazilian localizations (JL_BR) reporting view that consolidates Accounts Payable invoice data from two distinct sources into a single, query-friendly structure. Its purpose is to present a unified list of invoices relevant to the SICI (Sistema de Informações de Contribuintes / tax reporting) process — namely consolidated invoices and standard payables invoices — through one consistent column layout. The view is owned by the APPS schema and is typically consumed by Brazilian localization reports, concurrent programs, and integration extracts that need to enumerate both consolidated (CI) and standard (SI) invoices together.

The name encodes the source distinction: CI denotes Consolidated Invoice, and SI denotes Standard Invoice. A discriminator column, SICI, is generated in the SELECT list to identify which source each row originated from. Because the view is defined as a UNION rather than a UNION ALL, duplicate rows across the two branches are eliminated, though in practice the INVOICE_ID namespaces and source semantics differ enough that few collisions occur.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects, both exposed to APPS as synonyms:

  • JL_BR_AP_CONSOLID_INVOICES — the Brazilian localization table storing consolidated AP invoices. It contributes the 'CI' branch of the UNION.
  • AP_INVOICES — the core Oracle Payables invoice table. It contributes the 'SI' branch, filtered to standard invoices only.

The second branch applies two filters: GLOBAL_ATTRIBUTE10 IS NULL, which excludes records already tagged by the Brazilian localization (for example, invoices linked to a consolidated structure), and INVOICE_TYPE_LOOKUP_CODE = 'STANDARD', which restricts the result set to standard invoice types. This design prevents double-counting of invoices that appear in both the consolidated localization tables and the base payables table.

Key Columns

Common Use Cases and Queries

A frequent requirement is to list only standard invoices for a vendor, which the INVOICE_TYPE_LOOKUP_CODE search term implies:

  • Filtering by SICI ('SI') to isolate standard invoices.
  • Filtering by ORG_ID to respect operating unit boundaries.
  • Joining to AP_SUPPLIERS on VENDOR_ID for supplier names.

Example:

SELECT SICI, INVOICE_ID, VENDOR_ID, INVOICE_NUM, INVOICE_DATE, INVOICE_AMOUNT
FROM APPS.JL_BR_AP_SICI_INVOICES_V
WHERE SICI = 'SI'
AND INVOICE_TYPE_LOOKUP_CODE = 'STANDARD'
AND ORG_ID = :p_org_id;

Because the CI leg always returns NULL for INVOICE_TYPE_LOOKUP_CODE, any predicate on that column automatically restricts results to standard invoices. This behavior should be accounted for when building union-aware reports.