Search Results jl_co_gl_nits




Overview
Explore in AI Chat

Overview

JL_CO_GL_NITS is a third-party master table within the JL (Latin America Localizations) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its name is derived from the Spanish-language tax concept "NIT" (Número de Identificación Tributaria), the tax identification number used for natural and legal persons in jurisdictions such as Colombia. The table therefore serves as the master repository of third-party (supplier, customer, and counterparty) identification records that feed the Latin American general ledger localization layer, which transforms and bridges subledger and GL activity into statutory reporting formats.

From a Data Vault modeling perspective, the heuristic classification of this object is hub-leaning. That is, it behaves as a business hub: it holds the unique identity of third parties (via NIT_ID and NIT) around which transactional satellites gravitate through foreign keys. This makes JL_CO_GL_NITS the natural anchor point for joins that enrich transaction-level data with third-party identity attributes such as name, type, and tax verification.

Key Information Stored

The table is physically owned by the JL schema and carries 26 documented columns. The most significant are:

  • NIT_ID — surrogate primary key (JL_CO_GL_NITS_PK) and the identifier propagated to dependent tables.
  • NIT — the actual tax identification number; the business-key candidate enforced by unique index JL_CO_GL_NITS_U1. Index JL_CO_GL_NITS_U2 also covers NIT_ID.
  • TYPE — classification of the third party (e.g., legal vs. natural person).
  • NAME — legal or registered name of the third party.
  • VERIFYING_DIGIT — check digit associated with the NIT, used for tax validation.
  • CREATION_DATE / CREATED_BY — audit trail of record creation.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — audit trail of the most recent modification.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, which in the JL localization typically store country-specific or client-specific extension attributes.

Note that only these columns are documented in the given metadata; the remaining columns follow standard EBS conventions and may include WHO/audit and descriptive fields.

Common Use Cases and Queries

The primary use case is resolving transaction records to a third party. For example, to list all GL transaction lines attributed to a given NIT:

  • SELECT n.NIT, n.NAME, t.* FROM JL_CO_GL_NITS n JOIN JL_CO_GL_TRX t ON t.NIT_ID = n.NIT_ID WHERE n.NIT = :nit;
  • To reconcile balances by third party: join JL_CO_GL_BALANCES on NIT_ID and aggregate by NIT or TYPE.
  • To audit the master data: query NAME, TYPE, and VERIFYING_DIGIT filtered by ATTRIBUTE_CATEGORY to validate DFF-populated localization attributes.
  • Reporting: use JL_CO_GL_NITS as the driving table for statutory reports and third-party listings, relying on the unique NIT index for exact-match lookups.

Related Objects

The following tables reference JL_CO_GL_NITS through the NIT_ID foreign key and are the most significant dependents:

  • JL_CO_GL_BALANCES — via JL_CO_GL_BALANCES.NIT_ID → JL_CO_GL_NITS.
  • JL_CO_GL_MG_LINES — via JL_CO_GL_MG_LINES.NIT_ID → JL_CO_GL_NITS.
  • JL_CO_GL_TRX — via JL_CO_GL_TRX.NIT_ID → JL_CO_GL_NITS.

These relationships confirm JL_CO_GL_NITS as the hub from which Latin American localization balances, line-level movements, and transaction records derive third-party identity.