Results for “exception_id”

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

Overview

GMP_RSRC_EXCP_HDR is the exception header table within the Oracle EBS Process Manufacturing Process Planning module (GMP). It defines the master record for resource exceptions used during process planning and scheduling. Each row represents a named exception definition that governs how the planning engine reacts when specific resource conditions occur, such as capacity overloads, constraint violations, or resource availability deviations. The header carries the defining attributes of the exception, while detail and assignment tables extend the definition to specific resources and planning contexts.

Under a heuristic Data Vault classification mined from its foreign-key structure, this table is hub-leaning. The classification is a modeling suggestion rather than a documented fact: GMP_RSRC_EXCP_HDR holds a stable, uniquely identified business entity (the exception definition) referenced by multiple dependent tables through EXCEPTION_ID, which is characteristic of a hub. However, it also carries descriptive and audit attributes typical of a satellite, so a strict Data Vault decomposition might separate those concerns.

Key Information Stored

The physical schema documents nine columns. The most significant are:

• EXCEPTION_ID — the surrogate primary key, enforced by the unique index GMP_RSRC_EXCP_HDR_PK. It is the value propagated to all dependent tables.
• EXCEPTION_CODE — the business-key candidate, a user-recognizable code identifying the exception for lookup and integration purposes.
• DESCRIPTION — the descriptive text explaining the purpose or condition of the exception.
• INACTIVE_IND — the enable/disable flag controlling whether the exception definition is active in planning runs.
• CREATION_DATE, CREATED_BY — standard audit columns recording initial insert.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification and the login context of the change.

No other unique index is documented beyond the primary key, so EXCEPTION_CODE should be treated as a business-key candidate rather than a guaranteed unique constraint unless the implementation adds one.

Common Use Cases and Queries

Typical uses include validating that exception definitions referenced by planning output are active, and reporting on configured exceptions across a planning organization. A standard header lookup returns active definitions:

• SELECT exception_id, exception_code, description FROM gmp_rsrc_excp_hdr WHERE inactive_ind = 'N';

A join to detail rows resolves exceptions to specific planning conditions, while a join to assignment rows resolves exceptions to particular resources:

• SELECT h.exception_code, d.* FROM gmp_rsrc_excp_hdr h, gmp_rsrc_excp_dtl d WHERE h.exception_id = d.exception_id;
• SELECT h.exception_code, a.* FROM gmp_rsrc_excp_hdr h, gmp_rsrc_excp_asnmt a WHERE h.exception_id = a.exception_id;

Reporting scenarios include exception configuration inventories, impact analysis before deactivating an exception (checking dependent detail and assignment rows), and audit reports on who last changed a definition.

Related Objects

The following tables reference this header through EXCEPTION_ID and are the most significant dependents:

• GMP_RSRC_EXCP_DTL — join on GMP_RSRC_EXCP_DTL.EXCEPTION_ID = GMP_RSRC_EXCP_HDR.EXCEPTION_ID; holds detail lines qualifying the exception.
• GMP_RSRC_EXCP_ASNMT — join on GMP_RSRC_EXCP_ASNMT.EXCEPTION_ID = GMP_RSRC_EXCP_HDR.EXCEPTION_ID; assigns exceptions to specific resources.
• GMP_RSRC_EXCP_HDR_PK — the primary-key index enforcing uniqueness of EXCEPTION_ID.

Because both dependent tables carry EXCEPTION_ID as a foreign key, the header must be inserted before its detail or assignment rows and cannot be deleted while dependents exist. Planning and scheduling processes typically resolve exceptions by first reading the header definition, then applying the matching detail and assignment records.