Search Results evnt_plc_id

Overview

The GL_EVNT_PLC table is a core data object within the Process Manufacturing Financials (GMF) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as a critical junction table that defines and stores event-specific fiscal policy information for a company. Its primary role is to link a company's general ledger accounting policies to specific transaction events and source types, enabling precise control over the financial accounting rules applied during transaction processing. This table ensures that financial events, such as material transactions or production completions, are accounted for according to the correct fiscal policies based on the company, the event type, and the originating transaction source.

Key Information Stored

The table's structure centers on a composite key that uniquely identifies a policy assignment. The primary columns include EVNT_PLC_ID, a unique system-generated identifier. The key business columns are CO_CODE, which stores the company code; TRANS_SOURCE_TYPE, which identifies the origin system or module of the transaction (e.g., Inventory, Purchasing); and EVENT_TYPE, which specifies the financial event being triggered. Together, these columns point to a specific fiscal policy record. The table's integrity is maintained through foreign key relationships to master tables for events (GL_EVNT_MST), company policies (GL_PLCY_MST), and transaction sources (GL_SRCE_MST). This design enforces valid combinations of companies, sources, and events within the financial policy framework.

Common Use Cases and Queries

A primary use case is the validation and determination of the applicable accounting policy during the creation of financial journal entries for manufacturing and inventory transactions. For instance, when a material issue is posted, the system queries this table using the company, the 'Inventory' source type, and the specific event type (e.g., 'Material Issue') to find the correct policy ID for cost posting. Common reporting and diagnostic queries involve listing all policy assignments for a company or identifying missing policy setups for critical event and source combinations. A sample query to audit setups would be:

SELECT co_code, trans_source_type, event_type, evnt_plc_id
FROM gmf.gl_evnt_plc
WHERE co_code = '&company_code'
ORDER BY trans_source_type, event_type;

Troubleshooting journal generation failures often involves verifying that a valid record exists in GL_EVNT_PLC for the transaction's context.

Related Objects

• GL_EVNT_MST: Master table for financial event types. GL_EVNT_PLC.EVENT_TYPE is a foreign key to this table.
• GL_PLCY_MST: Master table defining company fiscal policies. GL_EVNT_PLC is linked to it via the CO_CODE, establishing the company-policy relationship.
• GL_SRCE_MST: Master table for transaction source types. GL_EVNT_PLC.TRANS_SOURCE_TYPE is a foreign key to this table.
• Transaction Interfaces & Journal Creation Programs: Downstream programs in GMF and related modules reference GL_EVNT_PLC to fetch the policy ID for accounting.