Search Results table




Overview
Explore in AI Chat

Overview

The JE.JE_NO_GEI_MESSAGES table is a specialized transactional table within the Oracle E-Business Suite (EBS) Japanese Localization schema (JE). It stores information about the ordering and receiving of files related to the A-Report (a statutory Japanese financial reporting requirement). Specifically, it functions as a staging and error-tracking repository for inbound and outbound file exchanges processed by the GEI (Government Electronic Interface) subsystem. The table captures the linkage between a government order number, the corresponding reporting period, and the receipt status or error outcome of each processing attempt. Its role is diagnostic and operational: it allows support personnel and batch administrators to identify which A-Report file transactions succeeded, which failed, and the precise error messages returned by the interface. From a data modeling perspective, the table's heuristic Data Vault classification is link, since it primarily records relationships between the order numbers recorded in the control tables and the file receipt events they generate, while carrying a limited set of descriptive attributes.

Key Information Stored

The table contains 13 documented columns. The surrogate identifier is RECORD_ID, a VARCHAR2 value that uniquely identifies each file transaction message. The principal business-key candidate is ORDER_NUMBER, a numeric value that ties the message back to the government order and is subject to foreign-key relationships that reference the control tables. PERIOD, PERIOD_START, and PERIOD_END together describe the reporting window covered by the A-Report file, with PERIOD stored as a DATE and the start and end boundaries stored as VARCHAR2 strings. RECEIPT_TYPE indicates the nature of the file exchange (for example, inbound receipt versus outbound transmission). ERROR_CODE and ERROR_MESSAGE provide the diagnostic outcome; ERROR_MESSAGE is constrained to 100 characters. The remaining five columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — are the standard Oracle EBS "WHO" columns that record audit and concurrency information for each row. The table is stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10.

Common Use Cases and Queries

Typical usage centers on monitoring A-Report file processing and troubleshooting failures. A support analyst might retrieve all messages for a given order and period to determine whether the government interface completed successfully:

SELECT ORDER_NUMBER, PERIOD, RECEIPT_TYPE, ERROR_CODE, ERROR_MESSAGE
FROM JE.JE_NO_GEI_MESSAGES
WHERE ORDER_NUMBER = :order
AND PERIOD = :period
ORDER BY CREATION_DATE;

Error-focused reporting is equally common, selecting only rows where ERROR_CODE IS NOT NULL to build an exception report. Batch monitoring may aggregate counts by RECEIPT_TYPE and PERIOD to confirm that all expected files were received. Because RECORD_ID is the primary key, point lookups by identifier are efficient, and the standard WHO columns support auditing who created or last modified a given message.

Related Objects

The table is referenced by the APPS synonym JE_NO_GEI_MESSAGES, the normal access path for concurrent programs and reports. Its foreign-key dependencies point to the control tables:

  • JE.JE_NO_GEI_CONTROLS — joined on ORDER_NUMBER; the parent record defining the A-Report order.
  • JE.JE_NO_GEI_CONTROLAS — also joined on ORDER_NUMBER; an associated control definition used for ordering and receiving validation.

No other database objects are documented as referencing this table directly. Its limited dependency footprint reflects its narrow purpose as a message and error log supporting the A-Report government interface.