Search Results gmp_rsrc_excp_hdr




Overview
Explore in AI Chat

Overview

The GMP_RSRC_EXCP_HDR table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing Process Planning (GMP) module. It functions as the master header table for recording and managing resource-related exceptions. In the context of process manufacturing, where precise resource allocation and scheduling are critical, this table provides the foundational structure for tracking deviations, constraints, or issues identified during the planning or execution phases. Its primary role is to serve as a parent record, uniquely identifying each exception event, to which detailed assignment and transactional data are linked. This structure is essential for maintaining data integrity and enabling comprehensive exception analysis and resolution workflows within the GMP application.

Key Information Stored

While the provided ETRM metadata does not list individual column names, the table's structure is defined by its primary key and its relationships. The central and most critical column is EXCEPTION_ID, which serves as the unique identifier (primary key) for every exception record created in the system. This ID is a sequential number or a system-generated unique key that distinguishes one exception header from another. As a header table, GMP_RSRC_EXCP_HDR likely contains additional descriptive and control columns common to such structures, which may include fields for the exception type, status (e.g., OPEN, CLOSED), creation date, last update date, the user who raised the exception, and a reference to the specific plan, batch, or operation from which the exception originated. The EXCEPTION_ID is the anchor point for all related data.

Common Use Cases and Queries

This table is central to exception management processes. A primary use case is generating exception reports for planners to identify scheduling conflicts, resource overloads, or material shortages that impact production plans. Support personnel use data linked to this header to investigate the root cause of an exception and track its resolution status. Common SQL queries involve joining this header table to its detail and assignment child tables to get a complete view of an exception. For example, to list all open exceptions with their basic details, a query might pattern: SELECT hdr.* FROM gmp_rsrc_excp_hdr hdr WHERE hdr.status = 'OPEN';. For a more detailed report, a join would be essential: SELECT hdr.exception_id, hdr.creation_date, dtl.resource_id, asnmt.assigned_to FROM gmp_rsrc_excp_hdr hdr JOIN gmp_rsrc_excp_dtl dtl ON hdr.exception_id = dtl.exception_id JOIN gmp_rsrc_excp_asnmt asnmt ON hdr.exception_id = asnmt.exception_id WHERE hdr.status = 'OPEN';.

Related Objects

The GMP_RSRC_EXCP_HDR table has defined foreign key relationships with two key child tables, forming a central hub in the exception data model. These relationships are documented as follows:

  • GMP_RSRC_EXCP_DTL: This table holds the detailed transactional records for each exception. It references the header via the foreign key column GMP_RSRC_EXCP_DTL.EXCEPTION_ID, which joins to GMP_RSRC_EXCP_HDR.EXCEPTION_ID.
  • GMP_RSRC_EXCP_ASNMT: This table manages the assignment of exceptions to users or roles for action and resolution. It also references the header via the foreign key column GMP_RSRC_EXCP_ASNMT.EXCEPTION_ID, which joins to GMP_RSRC_EXCP_HDR.EXCEPTION_ID.

These relationships enforce referential integrity, ensuring that all detail and assignment records are tied to a valid exception header.