Results for “reason_code”

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

Overview

The GMP_RSRC_UNAVAIL_MAN table resides in the GMP schema and belongs to the Oracle Process Manufacturing Process Planning module. It is documented as the "Manual Entries Table," a designation that reflects its purpose: storing manually entered resource unavailability records that constrain or adjust capacity planning calculations. In the process manufacturing model, resources correspond to equipment, production lines, tanks, or labor pools whose availability drives scheduling and capacity rollups. When a planner knows in advance that a resource will be down — for maintenance, sanitation, changeover, or other reasons — the affected windows are recorded here rather than being derived from automated shop-floor or maintenance transactions.

From a Data Vault modeling perspective, the heuristic classification for this object is a link. This suggestion follows from the table's foreign key structure: it associates a resource with a reason code over a defined time interval, effectively resolving a many-to-many relationship between resources and availability exceptions.

Key Information Stored

The table is documented with 14 columns in the 12.2.2 physical schema. The most significant are:

• RESOURCE_ID — Identifies the resource whose availability is being restricted; foreign key to CR_RSRC_DTL.
• FROM_DATE and TO_DATE — Define the unavailability window. Together with RESOURCE_ID and INSTANCE_ID they form the unique index GMP_RSRC_UNAVAIL_MAN_U1, making them the business-key candidates for a specific unavailability record.
• REASON_CODE — Classifies why the resource is unavailable; foreign key to SY_REAS_CDS_B.
• RESOURCE_UNITS — Expresses the magnitude of resource capacity affected during the window.
• INSTANCE_ID — Distinguishes the planning instance context for the entry.
• MAINT_ORG_ID — Identifies the maintenance organization associated with the record.
• WIP_ENTITY_ID and OP_SEQ — Optionally link the unavailability to a specific work-in-process entity and operation sequence.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

No separate surrogate primary key column is documented beyond the composite unique index; the unique index itself acts as the business-key candidate.

Common Use Cases and Queries

Typical reporting scenarios include reviewing manual downtime entries by resource, validating that planned unavailability does not conflict with scheduled production, and analyzing downtime reasons for trend reporting. A representative query joins the resource detail table to enrich IDs with descriptive names:

• List unavailability by resource: SELECT m.RESOURCE_ID, r.RESOURCE_CODE, m.FROM_DATE, m.TO_DATE, m.REASON_CODE FROM GMP_RSRC_UNAVAIL_MAN m, CR_RSRC_DTL r WHERE m.RESOURCE_ID = r.RESOURCE_ID;
• Filter by window: add WHERE m.FROM_DATE >= :start_date AND m.TO_DATE <= :end_date to scope a reporting period.
• Resolve reason descriptions: join SY_REAS_CDS_B on REASON_CODE to obtain human-readable reason text.
• Track manual edits: query LAST_UPDATE_DATE and LAST_UPDATED_BY to audit recent planner changes.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

• CR_RSRC_DTL — Master resource definition; joined via GMP_RSRC_UNAVAIL_MAN.RESOURCE_ID = CR_RSRC_DTL.RESOURCE_ID.
• SY_REAS_CDS_B — Reason code definitions; joined via GMP_RSRC_UNAVAIL_MAN.REASON_CODE = SY_REAS_CDS_B.REASON_CODE.
• Process planning capacity and scheduling views that consume resource availability windows during plan generation.
• WIP entity and operation tables referenced indirectly through WIP_ENTITY_ID and OP_SEQ.

Together these objects support the capacity planning cycle, ensuring manually declared downtime is respected during scheduling and resource loading.