Results for “gl_srce_mst”

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

Overview

GL_SRCE_MST (Subsystem Master Table) is a reference and control table owned by the GMF schema within the Oracle E-Business Suite Process Manufacturing Financials (OPM Financials) product. Its purpose is to define and validate the transaction source types and transaction source codes that feed the Process Manufacturing subledger and its interface into Oracle General Ledger. In practical terms, it functions as the master registry of subsystem sources — the enumerated values that identify where a given financial transaction originated before it is posted into the OPM subledger and subsequently transferred to GL.

Because GL_SRCE_MST holds a relatively stable, low-volume set of enumerated reference values that are referenced by multiple transactional and setup tables through the TRANS_SOURCE_TYPE column, the metadata's heuristic Data Vault classification places it as hub-leaning. Under this modeling suggestion, TRANS_SOURCE_TYPE behaves as a business key that anchors a hub, with dependent descriptive attributes (such as the description and rate type) forming satellite-style data, and the referencing tables acting as links or satellites attached to that hub. This classification is a heuristic derived from the foreign-key structure rather than a physical design statement.

Key Information Stored

The table consists of 12 documented columns. The most significant are:

• TRANS_SOURCE_TYPE — The primary key of the table (via GL_SRCE_MST_PK). This column uniquely identifies each subsystem transaction source type and is the value propagated as a foreign key into downstream tables.
• TRANS_SOURCE_CODE — A business-key candidate, enforced by the unique index GL_SRCE_MST_U1. It provides the human-readable or coded identifier for the source.
• TRANS_SOURCE_DESC — The descriptive text associated with a transaction source type, used for reporting and user display.
• RATE_TYPE_CODE — Identifies the rate type applicable to the source, relevant to currency conversion and valuation logic.
• TEXT_CODE — A code value used to associate descriptive or reference text with the source definition.
• TRANS_CNT — A counter column, typically used to track transaction or processing counts associated with the source.
• DELETE_MARK — The standard soft-delete (logical deletion) flag. Rows are marked rather than physically removed.

The audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — follow the standard Oracle EBS WHO-column convention, recording who created and last modified each row and when. Note the distinction between the surrogate/primary identifier (TRANS_SOURCE_TYPE) and the alternate unique business key (TRANS_SOURCE_CODE): both are unique, but TRANS_SOURCE_TYPE is the one used for referential integrity across the subledger tables.

Common Use Cases and Queries

Typical uses include validating the set of active transaction sources, decoding source codes in subledger reporting, and confirming which sources are enabled before creating or transferring transactions. A common query retrieves all non-deleted sources with their descriptions:

• SELECT trans_source_type, trans_source_code, trans_source_desc, rate_type_code FROM gl_srce_mst WHERE NVL(delete_mark,0) = 0 ORDER BY trans_source_type;
• Decoding a specific code: SELECT trans_source_desc FROM gl_srce_mst WHERE trans_source_code = :p_code;

Reporting scenarios frequently join GL_SRCE_MST to transaction and event tables to resolve TRANS_SOURCE_TYPE into a meaningful description. For example, joining GL_EVNT_MST or GL_SUBR_LED to GL_SRCE_MST on TRANS_SOURCE_TYPE allows a report to display the originating subsystem source rather than a numeric code. Because DELETE_MARK governs visibility, queries intended for production user reporting should filter on it to exclude deprecated definitions.

Related Objects

GL_SRCE_MST is referenced by several downstream tables through the TRANS_SOURCE_TYPE foreign key. The documented relationships are:

• GL_EVNT_MST — references GL_SRCE_MST via GL_EVNT_MST.TRANS_SOURCE_TYPE.
• GL_EVNT_PLC — references GL_SRCE_MST via GL_EVNT_PLC.TRANS_SOURCE_TYPE.
• GL_SUBR_LED — the subledger ledger table, referencing GL_SRCE_MST via GL_SUBR_LED.TRANS_SOURCE_TYPE.
• GL_SUBR_TST — the subledger test table, referencing GL_SRCE_MST via GL_SUBR_TST.TRANS_SOURCE_TYPE.

These foreign keys confirm the hub-leaning role of GL_SRCE_MST: it is a parent reference table whose primary key value is distributed into event, control, and subledger detail tables. When reconciling OPM subledger activity to GL, joining these dependent tables to GL_SRCE_MST on TRANS_SOURCE_TYPE is the standard method for identifying and grouping postings by their originating subsystem source.