Search Results reference_no




Overview
Explore in AI Chat

Overview

The GL_MESG_TBL is a core transactional table within the Process Manufacturing Financials (GMF) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as the repository for detailed messages generated during the critical financial process of transaction posting. Specifically, the table captures informational, warning, and error messages produced by the Subsidiary Ledger Update process, which is responsible for transferring accounting entries from subsidiary ledgers (like those in inventory or purchasing) into the central General Ledger. Its primary role is to provide an auditable log of the posting process, enabling users and system administrators to diagnose issues, verify successful completions, and understand the flow of accounting data.

Key Information Stored

The table's structure is designed to log messages associated with a specific posting transaction. Its primary key is a composite of REFERENCE_NO and LINE_NO, indicating that multiple message lines (LINE_NO) can be linked to a single posting reference identifier (REFERENCE_NO). While the full column list is not detailed in the provided metadata, the logical data stored includes the posting reference number, a sequential line number for each message, and the message text itself. This text typically contains details about the transaction being processed, the account combinations involved, and the nature of any errors or validations encountered, such as invalid accounts, period closure issues, or posting rule failures.

Common Use Cases and Queries

The primary use case is troubleshooting failed or problematic General Ledger posting runs. After a posting job completes with errors, financial analysts or system administrators query this table to retrieve the specific error messages. A common query pattern involves joining to the GL_SUBR_STA table, which holds high-level status information for the subsidiary ledger update request. For example:

  • Retrieve all messages for a specific posting run: SELECT * FROM GMF.GL_MESG_TBL WHERE REFERENCE_NO = '<reference_number>' ORDER BY LINE_NO;
  • Investigate a failed posting request: SELECT m.* FROM GMF.GL_MESG_TBL m, GMF.GL_SUBR_STA s WHERE m.REFERENCE_NO = s.REFERENCE_NO AND s.STATUS = 'ERROR';

This data is crucial for month-end close support, ensuring all subsidiary transactions are correctly reflected in the General Ledger.

Related Objects

Based on the documented foreign key relationship, GL_MESG_TBL has a direct and critical dependency on the GL_SUBR_STA table. The relationship is defined as:

  • Foreign Key: The column GL_MESG_TBL.REFERENCE_NO references the table GMF.GL_SUBR_STA. This links the detailed messages to the parent request record that tracks the overall status, parameters, and submission details of the Subsidiary Ledger Update process.

Therefore, any meaningful reporting or analysis from GL_MESG_TBL typically requires a join to GL_SUBR_STA to contextualize the messages within a specific posting batch or request. This table is a key component in the GMF posting architecture, sitting downstream from transaction sources and upstream from the General Ledger interface tables.