Search Results gmd_process_loss_u1

Overview

GMD_PROCESS_LOSS is a reference table within the Oracle EBS Process Manufacturing Product Development (GMD) module. It stores routing process loss definitions, which quantify the expected yield loss that occurs during a manufacturing routing step. Process loss is a critical planning parameter in process manufacturing because it determines how much input material must be charged to a routing operation to obtain a given quantity of output. The table allows planners and cost engineers to model loss as a function of batch or routing quantity ranges rather than a single flat percentage.

Based on the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a standalone table, meaning it participates in no documented parent-child foreign key relationships and instead functions as an independent reference or lookup structure. In Data Vault terms, it behaves closer to a reference satellite or a standalone reference table than to a hub or link, since it carries descriptive business attributes keyed by a composite business key rather than by a surrogate foreign key to another entity.

Key Information Stored

The table contains nine documented columns. The two most consequential are the composite business key columns:

• ROUTING_CLASS — identifies the routing class or routing step category to which the loss definition applies. This is part of the unique business key.
• MAX_QUANTITY — the upper bound of the quantity range for which the associated process loss percentage is valid. This is also part of the unique business key.
• PROCESS_LOSS — the actual loss value (typically a percentage or factor) applied when the routing quantity falls within the range bounded by MAX_QUANTITY.
• TEXT_CODE — a coded or descriptive attribute providing additional context for the loss record.
• LAST_UPDATE_DATE, CREATION_DATE — standard audit timestamps.
• CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit user and login identifiers.

The primary key is enforced by unique index GMD_PROCESS_LOSS_U1 on (ROUTING_CLASS, MAX_QUANTITY). Because the table uses a natural composite key rather than a single surrogate sequence-generated primary key, there is no separate surrogate identifier documented; the business key and the primary key coincide. Any lookup of loss for a given routing class and quantity must therefore resolve the correct row by selecting the record with the smallest MAX_QUANTITY that still exceeds the actual quantity, a range-matching pattern rather than an equality join.

Common Use Cases and Queries

The primary use case is yield and material requirement calculation: given a routing class and a target production quantity, retrieve the applicable process loss so that input quantities can be grossed up. A typical range-resolution query is:

SELECT process_loss
FROM   gmd_process_loss
WHERE  routing_class = :routing_class
AND    max_quantity >= :quantity
ORDER BY max_quantity
FETCH FIRST 1 ROW ONLY;

Analysts also use the table to audit loss tiering — reviewing how loss percentages step up or down across quantity bands for a routing class — and to validate that the highest quantity band exists to avoid null results for very large batches. Reporting use cases include loss profile listings by routing class and impact analysis when a process loss value is revised, since a change cascades into every batch or cost rollup that uses the affected routing class.

Related Objects

The metadata documents no foreign keys referencing GMD_PROCESS_LOSS; the Data Vault classification confirms it is standalone. Consequently, related objects are identified by shared business columns rather than by enforced referential constraints:

• GMD_ROUTINGS and routing header/detail tables — share ROUTING_CLASS as the logical join to the routing definition that owns the process loss.
• GMD_ROUTING_STEPS / operation-level routing tables — associated through routing class when loss is attributed at step level.
• GMD_RECIPE_VALIDITY_RULES and recipe quantity range tables — analogous range-based logic applied to recipes rather than routings.
• GMD_PROCESS_LOSS itself is referenced logically by batch sizing and cost rollup routines that consume PROCESS_LOSS during input quantity netting.

Because no declarative foreign keys exist, joins to routing and recipe tables rely on ROUTING_CLASS and must be validated during integration or migration efforts.