Search Results gl_srce_mst




Overview
Explore in AI Chat

Overview

The GL_SRCE_MST table is a core master data table within the Process Manufacturing Financials (GMF) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a subsystem master, providing a centralized reference for defining and managing the various sources of financial transactions that originate from the manufacturing and process execution systems. Its primary role is to establish and enforce valid transaction source types and codes, ensuring data integrity and proper classification for subsequent financial posting to the General Ledger (GL). This table is fundamental to the integration between manufacturing operations and financial accounting within the GMF framework.

Key Information Stored

Based on the provided ETRM metadata, the table's structure is defined by its primary keys and its relationships with other entities. The two primary keys indicate the critical columns that uniquely identify a record. The TRANS_SOURCE_TYPE column, serving as the primary key for constraint GL_SRCE_MST_PK, holds the high-level classification or category for a transaction source. The TRANS_SOURCE_CODE column, serving as the primary key for constraint GL_SRCE_MST_U1, holds the specific, unique identifier code for a transaction source within a given type. Together, these columns form the authoritative list of valid source combinations that other transactional tables can reference.

Common Use Cases and Queries

This table is primarily used for setup, validation, and reporting. During system configuration, administrators populate this table with all permissible transaction sources (e.g., specific production batches, cost types, or material transactions). Application logic then references GL_SRCE_MST to validate transaction sources before creating financial events. A common reporting use case is to generate a list of all configured transaction sources for audit or setup review. A typical query would join this master table to its related transactional tables to analyze event data by source.

  • Retrieving all configured transaction sources: SELECT trans_source_type, trans_source_code FROM gmf.gl_srce_mst ORDER BY 1, 2;
  • Validating a source before processing: Application code will check for the existence of a provided type and code combination in this table.
  • Troubleshooting integration issues: Queries can identify if a missing or invalid entry in GL_SRCE_MST is causing failures in financial event creation.

Related Objects

The ETRM documentation explicitly lists four key tables that maintain foreign key relationships to GL_SRCE_MST via the TRANS_SOURCE_TYPE column, highlighting its central role in the GMF data model:

  • GL_EVNT_MST (Event Master): The primary transactional table for financial events, linking each event to a valid source type.
  • GL_EVNT_PLC (Event Policy): Stores accounting rules and policies that are triggered based on the transaction source type.
  • GL_SUBR_LED (Subledger): Tracks subledger accounting entries, associating them with their originating source type.
  • GL_SUBR_TST (Subledger Test): Likely used for validation or testing of subledger entries against defined source types.

These relationships demonstrate that GL_SRCE_MST is a foundational lookup table, dictating valid origins for the entire financial event and subledger posting chain within GMF.