Search Results gmp_aps_output_dtl




Overview
Explore in AI Chat

Overview

GMP_APS_OUTPUT_DTL is a table within the GMP schema, belonging to the Oracle Process Manufacturing Process Planning module. It functions as the Advanced Planning and Scheduling (APS) Output Detail table, storing the granular results generated by the APS planning engine when it produces scheduling and resource-assignment recommendations for process manufacturing environments. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the persistent store for planning output rows that downstream processes consume to update work-in-process (WIP) entities, resource assignments, and material supply requirements.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. In dimensional or Data Vault terms, this suggests the table behaves as an independent satellite or detail-level fact, since it does not serve as a central hub or link in the FK topology. The only documented foreign key is SETUP_ID, which references BOM_SETUP_TYPES. This indicates that despite its rich column set, the table is largely self-contained and does not participate in extensive referential relationships.

Key Information Stored

The table contains 53 documented columns spanning planning, resource, and supply dimensions. The most significant columns include:

The surrogate grouping key is not explicitly defined as a single-column primary key; GROUP_ID combined with GROUP_SEQUENCE_ID or GROUP_SEQUENCE_NUMBER functions as a business-key candidate for uniquely identifying rows within a planning run. The ETRM metadata does not document a unique index, so these columns should be treated as logical identifiers.

Common Use Cases and Queries

Typical use cases include reconciling APS recommendations against current WIP schedules, auditing resource substitutions, and generating reports on planned versus required quantities. A common query pattern retrieves all output rows for a planning batch:

  • SELECT * FROM GMP.GMP_APS_OUTPUT_DTL WHERE GROUP_ID = :p_group_id ORDER BY PARENT_SEQ_NUM, OPERATION_SEQ_NUM;
  • Comparing old and new resource assignments: SELECT WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_ID_OLD, RESOURCE_ID_NEW FROM GMP_APS_OUTPUT_DTL WHERE RESOURCE_ID_OLD <> RESOURCE_ID_NEW;
  • Reporting material substitutions: SELECT INVENTORY_ITEM_ID_OLD, INVENTORY_ITEM_ID_NEW, COUNT(*) FROM GMP_APS_OUTPUT_DTL GROUP BY INVENTORY_ITEM_ID_OLD, INVENTORY_ITEM_ID_NEW;
  • Joining to BOM_SETUP_TYPES via SETUP_ID to enrich setup context.

Related Objects

The most significant related objects include:

  • BOM_SETUP_TYPES — Referenced through SETUP_ID; provides setup type definitions for the planned operations.
  • WIP_ENTITIES — Joined via WIP_ENTITY_ID to obtain job-level context, though not enforced as a declared FK.
  • MTL_SYSTEM_ITEMS_B — Joined via INVENTORY_ITEM_ID_OLD and INVENTORY_ITEM_ID_NEW for item descriptions.
  • BOM_OPERATIONAL_ROUTINGS — Provides routing operation context via OPERATION_SEQ_NUM.
  • BOM_RESOURCES — Resolves RESOURCE_ID_OLD and RESOURCE_ID_NEW to resource definitions.
  • GMP_APS_OUTPUT (header-level counterpart) — Correlates through PARENT_HEADER_ID and GROUP_ID.

These relationships are largely logical rather than enforced foreign keys, consistent with the standalone Data Vault classification.