Results for “je_gr_je_header_sequence_u1”

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

Overview

JE_GR_JE_HEADER_SEQUENCE is a GL-schema table delivered with the JE – European Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the Greek Accounting sequence number and value for each journal entry whose journal requires statutory numbering under Greek localization rules. The table acts as a localization companion to the core General Ledger journal header tables, allowing a journal header to be associated with a document sequence assignment that satisfies Greek regulatory book-numbering requirements.

Under the heuristic Data Vault classification mined from the documented foreign-key structure, this object is modeled as a standalone entity rather than a hub, link, or satellite. In practical terms, this means the table is treated as an independent reference of sequence assignments keyed by journal header, rather than a dependent descriptive structure attached to a parent hub. This classification should be regarded as a modeling suggestion rather than a prescribed design.

Key Information Stored

The documented physical schema in ETRM 12.2.2 comprises five columns. The most significant are:

• JE_HEADER_ID — The journal header identifier from the General Ledger journal entry header. This column is both the primary key column of JE_GR_JE_HEADER_SEQUENCE_PK and the unique index JE_GR_JE_HEADER_SEQUENCE_U1, confirming a strict one-row-per-journal-header relationship.
• DOC_SEQUENCE_ID — The document sequence identifier, resolved against FND_DOCUMENT_SEQUENCES. This identifies which Greek accounting sequence was applied to the journal entry.
• DOC_SEQUENCE_VALUE — The assigned sequence value (the actual statutory number) captured for the journal entry at the time the sequence was applied. This is the value reported on Greek accounting registers and audit outputs.
• CREATION_DATE and CREATED_BY — Standard Oracle EBS audit columns recording when and by which user the sequence assignment row was created.

Because JE_HEADER_ID serves simultaneously as primary key and unique business-key candidate, no separate surrogate identifier is documented for this table; the journal header identifier functions as the natural key.

Common Use Cases and Queries

Reporting and audit scenarios in Greek localizations typically require resolving the statutory sequence number for a set of journal entries, or reconciling sequence usage against the document sequence definition. A representative join pattern is:

• Join JE_GR_JE_HEADER_SEQUENCE to GL_JE_HEADERS on JE_HEADER_ID to obtain journal name, period, and currency alongside DOC_SEQUENCE_VALUE.
• Join DOC_SEQUENCE_ID to FND_DOCUMENT_SEQUENCES to validate the sequence name, application, and numbering method used for the assignment.
• Filter by CREATION_DATE to identify sequence assignments generated within a given accounting period for statutory reporting.
• Detect journals lacking a Greek sequence row by outer-joining GL_JE_HEADERS to this table, a common reconciliation control for localization compliance.
• Audit sequence continuity by ordering extracted DOC_SEQUENCE_VALUE values per sequence and checking for gaps or duplicates.

Related Objects

The following objects are most significant in relation to this table:

• FND_DOCUMENT_SEQUENCES — referenced via the documented foreign key JE_GR_JE_HEADER_SEQUENCE.DOC_SEQUENCE_ID; provides the sequence definition and numbering attributes.
• GL_JE_HEADERS — parent journal header table, joined on JE_HEADER_ID, supplying journal context for the stored sequence value.
• GL_JE_LINES and GL_JE_BATCHES — commonly joined through GL_JE_HEADERS for localization reporting at line and batch level.
• JE_GR_JE_HEADER_SEQUENCE_PK / _U1 — the documented primary key and unique index enforcing one sequence assignment per journal header.