Search Results po_recv_hst

Overview

The GL_SEVT_MST table is a core reference data object within the Oracle E-Business Suite (EBS), specifically for the Process Manufacturing Financials (GMF) module. It serves as the master repository for defining and storing sub-event types, which are granular transaction classifications used within the financial integration framework. Its primary role is to support the detailed mapping of manufacturing and inventory transactions from Oracle Process Manufacturing (OPM) to the General Ledger (GL). As indicated by the documentation, this table contains seeded configuration data that is critical for the integrity of financial posting; consequently, OPM users are explicitly restricted from modifying its contents.

Key Information Stored

The table's structure is centered on defining the relationship between high-level events and their detailed sub-events. The primary key column, SUB_EVENT_TYPE, uniquely identifies each sub-event code. A critical foreign key column is EVENT_TYPE, which links each sub-event back to its parent event type as defined in the related GL_EVNT_MST table. This establishes a hierarchical classification essential for accurate accounting. While the provided metadata does not list all columns, typical data stored would include descriptive names, enabled flags, and potentially control attributes that dictate how transactions of this sub-event type are processed and summarized for journal entry creation.

Common Use Cases and Queries

This table is primarily referenced in background processes for financial integration and in diagnostic or reporting queries. A common use case is troubleshooting issues with journal generation for OPM transactions, where verifying the validity and setup of a sub-event is necessary. System administrators or functional consultants may run queries to audit the setup or understand the mapping hierarchy. Sample SQL patterns include joining to the event master table to see the full event-sub-event relationship:

• SELECT sevt.sub_event_type, sevt.description, evnt.event_type FROM gl_sevt_mst sevt, gl_evnt_mst evnt WHERE sevt.event_type = evnt.event_type ORDER BY evnt.event_type, sevt.sub_event_type;
• SELECT * FROM gl_sevt_mst WHERE sub_event_type = '&sub_event_code'; -- To validate a specific sub-event.

Direct transactional reporting from this table is uncommon, as it is a reference point for classifying transactions stored in history tables like PO_RECV_HST.

Related Objects

As per the foreign key relationships documented, GL_SEVT_MST is central to several key integration tables. The table GL_EVNT_MST is its direct parent. Key child tables that reference SUB_EVENT_TYPE include:

• GL_SEVT_TTL: Likely stores sub-event level transaction totals or summaries for journal generation.
• GL_SUBR_LED: Presumably holds sub-ledger accounting entries linked to specific sub-events.
• PO_RECV_HST: Stores purchase order receipt history, with a sub-event classification for financial posting.

These relationships underscore the table's function in propagating the sub-event classification through the transaction lifecycle, from operational event (e.g., a receipt) to final general ledger journal line.