Results for “routing_id”

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

Overview

The view APPS.PMITS_ROUTING_DETAIL_V is a reporting artifact belonging to the Process Manufacturing Intelligence (PMI) product family. PMI is documented in Oracle E-Business Suite as an obsolete module, and the view is retained largely for backward compatibility with historical reports, discoverer workbooks, and legacy integration points that reference routing-step data. The view's purpose is to present the production routing detail records held in the Process Manufacturing (GMD) routing schema, while resolving the raw lookup code stored on the base record into its human-readable meaning. In the ETRM documentation for release 12.2.2 the object is recorded as VALID in the APPS schema, with a description of "GMD Routing Detail View."

Because it is a view rather than a table, it stores no data of its own; it is a read-only projection that joins routing detail rows to the lookup repository. This makes it suitable for ad-hoc querying and for report definitions where a decoded release type is preferred over the internal code.

Underlying Base Objects

The documented base objects are two: FM_ROUT_DTL, which is referenced through a synonym, and GEM_LOOKUPS, which is itself a view. FM_ROUT_DTL supplies the routing detail records — the routing header identifier, the individual routing step, the operation, the step quantity, the release type code, and the text code. GEM_LOOKUPS supplies the descriptive meaning for the step release type by matching on LOOKUP_TYPE = 'STEPRELEASE_TYPE'.

The relationship is a simple equijoin on lookup code: the view returns a row for each routing detail record whose STEPRELEASE_TYPE code has a corresponding entry in GEM_LOOKUPS for the STEPRELEASE_TYPE lookup type. Records without a valid lookup match are filtered out by the inner join.

Key Columns

• ROUTING_ID — Identifier of the parent routing header in FM_ROUT_DTL.
• ROUTINGSTEP_ID — Surrogate identifier of the individual routing step record.
• ROUTINGSTEP_NO — The sequence or step number that orders the operation within the routing.
• OPRN_ID — Identifier of the operation performed at the step.
• STEP_QTY — The quantity associated with the routing step, the column most directly relevant to the user's search term. It expresses the amount produced or consumed at the step and is a key measure in yield and step-ratio analysis.
• STEPRELEASE_TYPE — The decoded meaning of the release type, derived from GEM_LOOKUPS.MEANING, describing how the step is released (for example, manual or automatic).
• TEXT_CODE — A short text identifier passed through from the routing detail record.

Common Use Cases and Queries

The view is typically used to report routing step structure, to compare step quantities across routings, and to inspect release-type behaviour without decoding the lookup separately. A representative query enumerating steps for a given routing:

• SELECT routing_id, routingstep_no, oprn_id, step_qty, steprelease_type FROM apps.pmits_routing_detail_v WHERE routing_id = :p_routing_id ORDER BY routingstep_no;
• SELECT routingstep_id, step_qty FROM apps.pmits_routing_detail_v WHERE step_qty > :threshold; — for flagging steps whose quantity exceeds a limit.
• SELECT steprelease_type, COUNT(*), SUM(step_qty) FROM apps.pmits_routing_detail_v GROUP BY steprelease_type; — for summarising step quantities by release type.

Given the obsolete status of PMI, new development should target the underlying GMD routing tables directly; the view remains appropriate for supporting existing reports and reconciliations.