Results for “je_no_gei_messages”

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

Overview

The JE_NO_GEI_MESSAGES table is a European Localizations object within the Oracle E-Business Suite JE (Journal Entry) product family, residing in the JE schema. Its documented role is to store messages received from FIN — the inbound messaging layer used by the Nordic and European localization features for reporting and reconciliation against tax and government authorities. In practical terms, the table acts as a staging and audit repository for return messages associated with a given GEI order, capturing the outcome of interactions such as acceptance confirmations, rejections, or error notifications.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is link. This is consistent with the physical design: the table records message events tied to an ORDER_NUMBER that resolves to control records, meaning it functions as an associative/transactional structure connecting orders to their returned message events rather than as an independent business hub or a purely descriptive satellite.

Key Information Stored

The documented physical schema exposes thirteen columns. The table carries a surrogate-style key, RECORD_ID, which serves as the primary identifier for each stored message row. The most significant business-relevant columns are:

• ORDER_NUMBER — The linking business key. It is the single documented foreign key column, referencing both JE_NO_GEI_CONTROLAS and JE_NO_GEI_CONTROLS, and identifies the GEI order to which the received message belongs.
• PERIOD — The reporting period associated with the message.
• PERIOD_START and PERIOD_END — The date boundaries delimiting the period covered by the message, enabling date-ranged reporting and reconciliation windows.
• RECEIPT_TYPE — Classifies the nature of the received message, distinguishing among the various response categories returned from FIN.
• ERROR_CODE — The coded identifier of an error condition reported in the message.
• ERROR_MESSAGE — The descriptive text accompanying the error code, providing human-readable diagnostic detail for troubleshooting and audit trails.
• AUDIT_COLUMNS — The standard EBS WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, which record row creation and last modification context.

ORDER_NUMBER is a documented foreign-key candidate and should be treated as the principal business key for joining to the control tables; RECORD_ID remains the technical surrogate primary key.

Common Use Cases and Queries

The table is most commonly interrogated to diagnose errors and to reconcile received messages against their originating orders. A representative query joining the message to its controlling order is:

• SELECT m.RECORD_ID, m.ORDER_NUMBER, m.PERIOD, m.RECEIPT_TYPE, m.ERROR_CODE, m.ERROR_MESSAGE FROM JE.JE_NO_GEI_MESSAGES m WHERE m.ERROR_CODE IS NOT NULL ORDER BY m.CREATION_DATE DESC; — surfaces all error-bearing messages for triage.
• SELECT m.ORDER_NUMBER, COUNT(*) FROM JE.JE_NO_GEI_MESSAGES m GROUP BY m.ORDER_NUMBER HAVING COUNT(*) > 1; — identifies orders with multiple returned messages.
• SELECT * FROM JE.JE_NO_GEI_MESSAGES WHERE PERIOD = :period AND PERIOD_START >= :start AND PERIOD_END <= :end; — period-based reporting for statutory submissions.

Typical consumers are period-close reconciliation reports, error-resolution dashboards, and audit extracts verifying that FIN acknowledgements were received for each submitted GEI order.

Related Objects

The FK metadata documents two parent relationships, both keyed on ORDER_NUMBER:

• JE_NO_GEI_CONTROLS — joined via JE_NO_GEI_MESSAGES.ORDER_NUMBER = JE_NO_GEI_CONTROLS.ORDER_NUMBER; the principal controlling order record.
• JE_NO_GEI_CONTROLAS — joined via JE_NO_GEI_MESSAGES.ORDER_NUMBER = JE_NO_GEI_CONTROLAS.ORDER_NUMBER; the companion control/association record.

Additional dependent objects belong to the broader JE_NO_GEI_* localization family and should be reviewed alongside this table when tracing the full message lifecycle. Because the documented schema is compact and localized, supplemental verification of any API or view dependencies against the live 12.1.1 or 12.2.2 instance is advisable before building integrations.