Results for “instance_id”

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

Overview

GMP_RSRC_EXCP_ASNMT is a table in the GMP schema, owned by the Oracle Process Manufacturing Process Planning module and valid in both Oracle EBS 12.1.1 and 12.2.2. Its documented description is "Resource Assignment Table," and it functions to associate specific production resources with resource exceptions defined at a header level. This design separates the definition of an exception condition (held in GMP_RSRC_EXCP_HDR) from the individual resource instances to which that exception applies, enabling one exception to govern multiple resources.

From a modeling perspective, the mined foreign-key structure suggests a link classification under Data Vault heuristics. The heuristic derives this because the table's documented foreign keys—EXCEPTION_ID referencing GMP_RSRC_EXCP_HDR and RESOURCE_ID referencing CR_RSRC_DTL—position the table as a connector between two independent business entities. It resolves a many-to-many style relationship and carries a small amount of descriptive context (RESOURCE_UNITS) rather than serving as a standalone hub or a pure descriptive satellite.

Key Information Stored

The documented physical schema for 12.2.2 contains nine columns. The most significant are:

• EXCEPTION_ID — Foreign key to GMP_RSRC_EXCP_HDR; identifies the parent exception definition.
• RESOURCE_ID — Foreign key to CR_RSRC_DTL; identifies the specific resource assigned to the exception.
• INSTANCE_ID — Distinguishes multiple instances of the same exception-resource pairing, forming part of the business key.
• RESOURCE_UNITS — The quantity or unit measure of the resource subject to the exception.
• CREATION_DATE, CREATED_BY — Standard audit columns recording initial insertion.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the login under which it occurred.

The unique index GMP_RSRC_EXCP_ASNMT_U1 spans EXCEPTION_ID, RESOURCE_ID, and INSTANCE_ID, making this composite the business-key candidate. This confirms that a given exception may apply repeatedly to the same resource across distinct instances, but not duplicate within the same instance. No separate single-column surrogate primary key is documented in the provided metadata; the composite unique index serves as the effective key.

Common Use Cases and Queries

Planners and reporting developers query this table to determine which resources are impacted by a given exception, or conversely which exceptions affect a specific resource. A typical join retrieves exception details alongside resource assignments:

• List resources for an exception: SELECT a.EXCEPTION_ID, a.RESOURCE_ID, a.RESOURCE_UNITS FROM GMP_RSRC_EXCP_ASNMT a WHERE a.EXCEPTION_ID = :p_exception_id.
• Find exceptions touching a resource: SELECT a.EXCEPTION_ID, a.INSTANCE_ID FROM GMP_RSRC_EXCP_ASNMT a WHERE a.RESOURCE_ID = :p_resource_id, joined to GMP_RSRC_EXCP_HDR for header attributes.
• Exception impact reporting: Join to CR_RSRC_DTL to obtain resource descriptions and to GMP_RSRC_EXCP_HDR to surface exception type, effective dates, and scope, producing an impact matrix for capacity or scheduling analysis.
• Audit and change tracking: Filter on LAST_UPDATE_DATE to identify recently reassigned resources.

Because the table sits at the intersection of exceptions and resources, it is commonly used in process planning reports that quantify capacity loss or resource availability adjustments resulting from exception conditions.

Related Objects

• GMP_RSRC_EXCP_HDR — Parent header table; joined on EXCEPTION_ID. Supplies exception definition and scope.
• CR_RSRC_DTL — Resource detail table; joined on RESOURCE_ID. Supplies resource name, cost, and capacity attributes.
• GMP_RSRC_EXCP_ASNMT_U1 — Unique index enforcing the composite business key (EXCEPTION_ID, RESOURCE_ID, INSTANCE_ID).
• CR_RSRC_DTL-related resource master views and resource availability queries that depend on assigned exceptions.
• Process Planning workbench and scheduling reports that consume exception-to-resource assignments for capacity calculations.
• Standard concurrent programs in the GMP module that generate or maintain resource exception assignments.

When extending or integrating with this object, developers should honor the composite unique key and the two foreign-key relationships, as both constrain valid assignments and drive the referential integrity of the planning data model.