Results for “sub_event_type”

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

Overview

GL_SEVT_MST is a reference (setup) table owned by the GMF schema, the database account associated with Oracle Process Manufacturing Financials. It stores the master list of General Ledger mapping subevents — the discrete accounting events that OPM transaction processing recognizes when generating GL distributions. Each row defines a permissible subevent that may be combined with a parent event type, and the resulting combinations drive the rules by which OPM activity (receipts, inventory issues, manufacturing completions, costing adjustments) is translated into journal entries.

The table is documented as an Oracle-controlled object. The metadata explicitly states that the OPM user is not permitted to modify its contents; rows are seeded and maintained by Oracle, and the application treats the table as read-only reference data. This distinguishes GL_SEVT_MST from user-maintainable setup tables such as GL_SUBR_LED, which consume its subevents to build posting rules.

Under the heuristic Data Vault classification supplied in the metadata, the table is described as hub-leaning. As a modeling suggestion, this reflects its role as a stable, business-key-driven catalog of subevent identities, from which downstream link and satellite structures could be derived. The classification is a heuristic rather than a statement of Oracle's design intent.

Key Information Stored

• SUB_EVENT_TYPE — the primary key column and the business key of the table, unique per the GL_SEVT_MST_PK index. It is the value carried into every child table that references a subevent.
• SUB_EVENT_CODE — a short, user-recognizable code used to identify the subevent in setup forms and reports.
• SUB_EVENT_DESC — the descriptive text of the subevent, used for display and reporting.
• EVENT_TYPE — the foreign key to GL_EVNT_MST, linking each subevent to its parent GL event type. This is the sole documented outbound foreign key.
• TRANS_CNT — a transaction or usage counter associated with the subevent record.
• TEXT_CODE — a code field used for supplementary classification or reference text.
• DELETE_MARK — the soft-delete indicator. Rows are not physically removed; the mark determines whether the subevent is treated as active.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns recording who created and last modified each row and through which session.

The documented physical schema contains twelve columns in total. GL_SEVT_MST_PK on SUB_EVENT_TYPE is the only unique index reported, confirming SUB_EVENT_TYPE as both surrogate and business key candidate. No separate artificial sequence column is documented.

Common Use Cases and Queries

Typical usage is diagnostic and analytical. Because the table is Oracle-seeded, the most frequent query pattern is a lookup that resolves a stored subevent identifier into its code and description when auditing GL distributions or investigating unexpected accounting entries.

• Listing all subevents belonging to a given event type, joined to GL_EVNT_MST for the parent description.
• Verifying whether a particular SUB_EVENT_TYPE is active by inspecting DELETE_MARK and the audit columns.
• Reconciling OPM receipt or inventory activity to GL by expanding records in PO_RECV_HST and GL_SUBR_LED through their SUB_EVENT_TYPE values.
• Supporting migration and testing validation, where the expected seeded set of subevents is compared against a target instance.

A representative pattern is a three-way join across the event hierarchy: SELECT s.SUB_EVENT_CODE, s.SUB_EVENT_DESC, e.EVENT_TYPE, e.EVENT_DESC FROM GMF.GL_SEVT_MST s, GMF.GL_EVNT_MST e WHERE s.EVENT_TYPE = e.EVENT_TYPE AND s.DELETE_MARK = 0; Filtering on DELETE_MARK is advisable in any operational query, since the soft-delete flag governs the effective row set.

Related Objects

• GL_EVNT_MST — the parent event master. Joined on GL_SEVT_MST.EVENT_TYPE = GL_EVNT_MST.EVENT_TYPE.
• GL_SEVT_TTL — subevent translation/title table, referencing GL_SEVT_MST.SUB_EVENT_TYPE.
• GL_SUBR_LED — subledger mapping rules, referencing GL_SEVT_MST.SUB_EVENT_TYPE. This is the principal consumer of subevent definitions when deriving posting accounts.
• PO_RECV_HST — purchase order receipt history, referencing GL_SEVT_MST.SUB_EVENT_TYPE. Links receipt transactions to the subevent that generated their accounting.
• GL_EVNT_TTL and other GL event-side translation tables that operate alongside GL_EVNT_MST in the event hierarchy.

Because three separate tables carry a foreign key to SUB_EVENT_TYPE, the table functions as a hub within the GL mapping model: its key is propagated outward, while descriptive attributes remain localized. Changes to seeded rows should be handled only through Oracle-supplied patches or datafix scripts, never through direct DML.