Results for “next_value”

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

Overview

JMF_GTA_BATCH_NUMBERING is a table in the JMF schema, owned by the Supply Chain Localizations product (JMF) within Oracle E-Business Suite 12.1.1 and 12.2.2. The JMF module supports country-specific legal and fiscal requirements — most notably global trade and tax localization for regulated markets such as Latin America, India, and Spain. This table serves as the batch-number sequence registry, holding the next number each organization will assign when generating and submitting legal batch/lot numbering documents. Because regulated authorities (for example, ANVISA in Brazil or DIAN in Colombia) require continuous, unique, and auditable batch sequences, a dedicated numbering table isolates number allocation from the business transactions themselves, allowing concurrency-safe increments and consistent numbering per operating unit.

The mined Data Vault classification for this object is standalone, meaning it neither references nor is referenced by other tables through foreign keys in the documented structure. For modeling purposes this suggests treating JMF_GTA_BATCH_NUMBERING as a standalone satellite-like reference record, keyed by ORG_ID, rather than as a hub or link in a normalized data warehouse.

Key Information Stored

The documented physical schema lists seven columns. The most significant are:

• ORG_ID — the operating unit / inventory organization that owns the numbering sequence. This column forms the primary key JMF_GTA_BATCH_NUMBERING_PK and also the unique index JMF_GTA_BATCH_NUMBERING_U1, making it both the surrogate-level row identity and the business-key candidate.
• NEXT_VALUE — the controlled sequence counter. It holds the next integer that will be assigned to a generated batch number; it is incremented as numbering documents are produced. This is the operational payload of the table.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS "Who" audit columns, recording who created and last modified the row, when, and through which login session. These support SOX-style auditability and change tracking.

There is no separate surrogate sequence column beyond ORG_ID: ORG_ID is simultaneously the unique index and the primary key, so each operating unit maintains exactly one numbering row. Because the table is a standalone (no FK) object, ORG_ID in this context is not documented as a foreign key to HR_OPERATING_UNITS, though it is semantically the operating unit identifier used throughout EBS.

Common Use Cases and Queries

The primary runtime use is allocation of the next batch number. A typical read pattern queries the current counter for an organization:

• SELECT next_value FROM jmf.jmf_gta_batch_numbering WHERE org_id = :p_org_id;
• Inspection of last-touched sequences: SELECT org_id, next_value, last_update_date, last_updated_by FROM jmf.jmf_gta_batch_numbering ORDER BY last_update_date DESC;
• Gap or continuity analysis comparing the reserved range against issued localization documents to detect missing or duplicated batch numbers.
• Post-clone or post-migration validation to ensure NEXT_VALUE was not inadvertently reset, which would cause duplicate legal numbering.

Because rows are sparse (one per operating unit), the table is small and inexpensive to query. Reporting often joins the counter back to the localization transaction tables by ORG_ID to reconcile the reserved range with documents actually transmitted to the tax authority.

Related Objects

The documented metadata records no foreign-key relationships, so the following are functional rather than enforced dependencies:

• HR_OPERATING_UNITS — joined on ORG_ID to resolve the organization name behind each numbering row.
• JMF_GTA_BATCH_NUMBERING_PK / _U1 — the primary key and unique index, both on ORG_ID, enforcing one sequence per operating unit.
• JMF localization batch/document tables — the fiscal document tables that consume NEXT_VALUE when a legal batch number is generated.
• FND_LOOKUPS — commonly referenced for localization status and document-type codes.
• FND_USER — joined on LAST_UPDATED_BY / CREATED_BY to audit who advanced the counter.

Administrators should treat this table with care during data refreshes and cloning, since an incorrect NEXT_VALUE directly threatens legal numbering compliance.