Results for “reference_no”

50+ results




Overview
Explore in AI Chat

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

Overview

GL_MESG_TBL is a General Ledger messages table owned by the GMF schema (Process Manufacturing Financials) in Oracle EBS 12.1.1 and 12.2.2. It stores diagnostic and informational messages generated during transaction posting by the Subsidiary Ledger Update process. When cost transactions are processed and pushed to the general ledger, the Subsidiary Ledger Update routine records status, error, and notification messages against a specific reference so that accounting users and support staff can diagnose why a posting succeeded, failed, or was deferred.

The object is classified as VALID and is a permanent (non-temporary) base table. In Data Vault modeling terms, the mined FK structure suggests a satellite-leaning classification: the table hangs off a parent accounting entity (GL_SUBR_STA) and carries descriptive, mutable message content keyed by that parent plus a sequence value, rather than acting as an independent hub or as a pure many-to-many link. This classification is a heuristic suggestion and not a physical constraint.

Because it is a message/audit-style table, its rows are typically inserted by concurrent programs and remain until purged or archived. It is not a transactional posting table and does not itself drive accounting entries; it records the outcome of that work.

Key Information Stored

The table contains 13 documented columns. The most operationally significant are:

  • REFERENCE_NO — the reference identifier tying each message to its parent accounting process. Part of the composite primary key and the column that participates in the foreign key to GL_SUBR_STA.
  • LINE_NO — the sequential line number within a reference, ordering multiple messages belonging to the same reference. Completes the composite primary key.
  • MESSAGE_TEXT — the actual message string produced by the Subsidiary Ledger Update posting process; the primary human-readable payload.
  • CREATION_DATE, CREATED_BY — standard WHO columns indicating when and by whom the message row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification and the login session responsible.
  • DELETE_MARK — a soft-delete indicator used in place of physical removal, common in Oracle process manufacturing tables.
  • PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent manager context columns identifying the application, concurrent program, and specific request that generated the message, enabling traceability back to the posting run.

The surrogate primary key is GL_MESG_TBL_PK, defined over (REFERENCE_NO, LINE_NO). Because this PK is also the only documented unique index, those two columns serve as the business-key candidate for uniquely identifying a message row.

Common Use Cases and Queries

The most common use case is diagnosing posting failures and reconciliation discrepancies. A support analyst retrieves all messages for a failing reference:

  • SELECT line_no, message_text, creation_date FROM gl_mesg_tbl WHERE reference_no = :ref ORDER BY line_no;
  • Correlating errors to a specific concurrent request via REQUEST_ID and PROGRAM_ID.
  • Filtering recent messages by CREATION_DATE to review a period's posting activity.
  • Excluding logically deleted rows with WHERE NVL(delete_mark,0) = 0.

Reporting scenarios include error-summary dashboards that count messages per reference, and audit reports that trace each reference back to its parent GL_SUBR_STA record to show status context alongside the message detail.

Related Objects

  • GL_SUBR_STA — the parent table referenced by GL_MESG_TBL.REFERENCE_NO; joined to obtain the subsidiary ledger posting status associated with each message.
  • GL_MESG_TBL_PK — the primary key constraint/index enforcing uniqueness on (REFERENCE_NO, LINE_NO).
  • Concurrent manager tables (FND_CONCURRENT_REQUESTS, FND_CONCURRENT_PROGRAMS) — joined via REQUEST_ID and PROGRAM_ID to identify the posting run.
  • FND_USER — joined via CREATED_BY / LAST_UPDATED_BY to resolve user identities.
  • GL (General Ledger) interface and posting tables — contextually related as the destination of the Subsidiary Ledger Update process whose messages this table stores.