Results for “resource_units”

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

Overview

The GMP_RSRC_UNAVAIL_DTL_V view is an Oracle E-Business Suite database object owned by the APPS schema and defined against Process Manufacturing Process Planning (GMP). It presents "Resource Unavailable Detail" information, exposing the reasons, date ranges, and resource assignments associated with periods during which a production resource is not available for scheduling. GMP uses the concept of resource exceptions and manual unavailability windows to constrain capacity planning; this view consolidates both sources into a single result set so that reports, concurrent programs, and integration extracts can consume a uniform representation of resource downtime. Its status is documented as VALID and it is classified as a VIEW, meaning it stores no data of its own and is resolved at runtime from its underlying base objects.

Underlying Base Objects

The view is defined over five documented base objects, all exposed through APPS synonyms: GMP_RSRC_EXCP_ASNMT, GMP_RSRC_EXCP_DTL, GMP_RSRC_EXCP_HDR, GMP_RSRC_UNAVAIL_MAN, and MTL_TRANSACTION_REASONS. The definition is a UNION of two branches. The first branch joins the exception header, exception detail, and exception assignment tables on EXCEPTION_ID, and filters on H.INACTIVE_IND = 0 so that only active exception definitions are returned. The second branch reads the manually entered unavailability records from GMP_RSRC_UNAVAIL_MAN. Both branches join to MTL_TRANSACTION_REASONS on MTR.REASON_NAME = REASON_CODE, which is why this view frequently surfaces in searches for mtl_transaction_reasons: it is the mechanism by which a short reason code is translated into a human-readable reason description. In the first branch the WIP entity, operation sequence, and maintenance organization columns are deliberately projected as NULLs via TO_NUMBER(NULL), because exception-based unavailability is not tied to a specific work order operation.

Key Columns

• EXCEPTION_ID / EXCEPTION_CODE — Identifier and code of the source exception record; the manual branch supplies 0 and NULL respectively.
• RESOURCE_ID / INSTANCE_ID — The resource and its instance to which the unavailability applies.
• RESOURCE_UNITS — Quantity of resource capacity unavailable.
• FROM_DATE / TO_DATE — The effective window of unavailability used by the scheduler.
• WIP_ENTITY_ID / OP_SEQ / MAINT_ORG_ID — Work order, operation sequence, and maintenance organization context; populated only for manual unavailability rows.
• REASON_CODE — The reason name joined against MTL_TRANSACTION_REASONS.REASON_NAME.
• DESCRIPTION — The descriptive text of the reason, retrieved from MTL_TRANSACTION_REASONS.DESCRIPTION.

Common Use Cases and Queries

Planners and developers use this view to audit why a resource was blocked from scheduling, to report downtime against reason codes, and to reconcile exception-driven and manually entered unavailability. A representative query listing all unavailable windows with their translated reasons is:

SELECT resource_id, instance_id, from_date, to_date, reason_code, description
FROM apps.gmp_rsrc_unavail_dtl_v
WHERE from_date >= :p_from AND to_date <= :p_to
ORDER BY resource_id, from_date;

To aggregate downtime by reason, the view can be grouped on REASON_CODE and DESCRIPTION. Because the manual branch returns 0 for EXCEPTION_ID, consumers can distinguish exception-sourced rows from manual entries and apply appropriate filters. All access should be performed through the APPS synonym to respect the standard EBS security and naming conventions.