Search Results ja_cn_journal_numbering




Overview
Explore in AI Chat

Overview

The JA_CN_JOURNAL_NUMBERING table is a localization data object owned by the JA schema (Asia/Pacific Localizations product family) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to store the next available journal number, segmented by legal entity and General Ledger period, so that the Account and Journal Itemization Program can generate gapless GL journal numbers. Gapless numbering is a statutory requirement in several Asia/Pacific jurisdictions, including China, and this table functions as the persistence layer for the counter that enforces that requirement.

Under the heuristic Data Vault classification provided in the ETRM metadata, this object is scored as standalone. In Data Vault modeling terms, this suggests treating it as a hub-like reference rather than a transactional link or descriptive satellite: it is a narrow, low-cardinality control table keyed on business attributes (legal entity plus period) rather than on a generated surrogate. Modeling it as a reference hub alongside the legal entity dimension is the recommended approach if the EBS schema is being reverse-engineered into a Data Vault warehouse.

Key Information Stored

The table is physically narrow, with 9 documented columns in the 12.2.2 ETRM schema. The most significant are:

  • LEGAL_ENTITY_ID — Foreign key to FV_LEGAL_ENTITIES; identifies the legal entity whose journals are being numbered. This is the principal partitioning attribute of the counter.
  • PERIOD_NAME — The GL accounting period for which the next number applies. Numbering sequences are maintained independently per period.
  • NEXT_NUMBER — The next gapless journal number to be assigned by the Account and Journal Itemization Program. This is the operational payload of the table.
  • LEDGER_ID — Identifies the ledger context associated with the numbering record, allowing the same legal entity to be resolved across multiple ledgers where applicable.
  • CREATED_BY, CREATION_DATE — Standard WHO audit columns recording who inserted the numbering row and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the last modification to the counter, which is critical for audit trails on statutory numbering.

The documented unique index JA_CN_JOURNAL_NUMBERING_U1 spans (LEGAL_ENTITY_ID, PERIOD_NAME). This composite is the business-key candidate: it guarantees exactly one numbering counter exists per legal entity per period. No separate generated surrogate primary key column is documented in the ETRM metadata; the unique index effectively serves that role.

Common Use Cases and Queries

The primary use case is operational: the Account and Journal Itemization Program reads the current NEXT_NUMBER, assigns it to the next journal, and increments the value, typically within a locked transaction to prevent gaps from concurrent submissions. Because gaps are prohibited, administrators and auditors frequently query this table to verify sequence integrity.

A representative query retrieves the current counter position for a given legal entity and period:

  • SELECT legal_entity_id, period_name, next_number, last_update_date FROM ja.ja_cn_journal_numbering WHERE legal_entity_id = :p_legal_entity AND period_name = :p_period;

Reporting use cases include reconciling the highest assigned journal number against the actual maximum journal number in GL for the same period, identifying legal entities whose counters were reset unexpectedly, and auditing last-update activity during statutory close windows.

Related Objects

The documented foreign key relationship ties this table most directly to FV_LEGAL_ENTITIES via LEGAL_ENTITY_ID. That is the only FK recorded in the ETRM metadata. Surrounding objects that interact with it at runtime include the GL journal tables (which supply the journals being numbered), the General Ledger period definitions that back PERIOD_NAME, and the Account and Journal Itemization Program itself, which is the sole documented consumer of NEXT_NUMBER. Any downstream report on gapless numbering should join this table to FV_LEGAL_ENTITIES for entity names and to the GL period/ledger setup for calendar context.