Search Results declaration_id




Overview
Explore in AI Chat

Overview

JE_BE_LOGS is a General Ledger (GL) schema table within the Oracle E-Business Suite JE product family, which covers European Localizations. The table stores data associated with VAT declarations, serving as the persistent record of declaration runs generated for Belgian (BE) localizations. In Oracle EBS 12.1.1 and 12.2.2, the object carries VALID status in the GL schema and is defined with a documented physical schema of thirteen columns and a primary key constraint named JE_BE_LOGS_PK spanning DECLARATION_ID, DECLARATION_TYPE_CODE, and SET_OF_BOOKS_ID.

From a dimensional modeling perspective, the heuristic Data Vault classification for this object is standalone, meaning it does not participate in a hub, link, or satellite pattern that could be mined from its foreign key structure. This suggests that, in a Data Vault model, JE_BE_LOGS is best treated as an independent entity. Modelers should note that this classification is heuristic and derived from the absence of detectable foreign key relationships rather than from an explicit design declaration.

Key Information Stored

The most significant columns in JE_BE_LOGS are:

  • DECLARATION_ID — The declaration identifier and the first component of the JE_BE_LOGS_PK composite primary key.
  • DECLARATION_TYPE_CODE — Classifies the type of VAT declaration; the second component of the primary key and part of the unique index JE_BE_LOGS_U1.
  • SET_OF_BOOKS_ID — Identifies the ledger (set of books) for which the declaration applies; the third component of the primary key.
  • START_DATE and END_DATE — The date range covered by the declaration.
  • PERIOD_NAME — The accounting period associated with the declaration run.
  • DECLARATION_STATUS_CODE — The processing status of the declaration.
  • REGIME_CODE — The VAT regime under which the declaration was filed.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns capturing the audit trail of record creation and modification.

The composite primary key combines a surrogate-style identifier (DECLARATION_ID) with two business discriminators, DECLARATION_TYPE_CODE and SET_OF_BOOKS_ID. The unique index JE_BE_LOGS_U1 mirrors this combination, confirming the combination as the business-key candidate for uniqueness enforcement. DECLARATION_ID is not suffixed by any single sequence-generated column in the documented metadata; rather, uniqueness is enforced at the composite level.

Common Use Cases and Queries

Typical reporting scenarios include auditing VAT declaration history by ledger, extracting declarations for a given period or regime, and reconciling declaration statuses. Because the primary key leads with DECLARATION_ID, lookups by declaration identifier are efficient:

  • Retrieve a specific declaration: SELECT * FROM GL.JE_BE_LOGS WHERE DECLARATION_ID = :id AND DECLARATION_TYPE_CODE = :type AND SET_OF_BOOKS_ID = :sob;
  • List declarations for a ledger and status: SELECT DECLARATION_ID, PERIOD_NAME, DECLARATION_STATUS_CODE, START_DATE, END_DATE FROM GL.JE_BE_LOGS WHERE SET_OF_BOOKS_ID = :sob AND DECLARATION_STATUS_CODE = :status;
  • Audit trail review: SELECT DECLARATION_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM GL.JE_BE_LOGS ORDER BY CREATION_DATE DESC;
  • Period-based reporting: filter on PERIOD_NAME and START_DATE/END_DATE to produce declarations filed within a reporting window.

These patterns are commonly embedded in BI Publisher reports and custom concurrent programs that support statutory VAT filing in Belgium localizations.

Related Objects

The documented metadata classifies JE_BE_LOGS as standalone and lists no foreign-key relationships. As a result, related objects must be inferred from shared GL context rather than from explicit constraints. Likely reference objects include:

  • JE_BE_HEADERS or similar declaration-header tables in the JE European Localizations family, joined on DECLARATION_ID and DECLARATION_TYPE_CODE.
  • GL_SETS_OF_BOOKS (or GL_LEDGERS in 12.2.2), joined on SET_OF_BOOKS_ID.
  • GL_PERIODS / GL_PERIOD_STATUSES, joined on PERIOD_NAME.
  • FND_USER, joined on CREATED_BY and LAST_UPDATED_BY for audit traceability.
  • JE_BE_LINES or declaration-line counterparts where they exist, joined on the declaration key.

Because JE_BE_LOGS is standalone in the documented schema, identifying explicit parent-child relationships requires validation against the actual data model in the target release rather than reliance on declared constraints.