Search Results steprelease_type




Overview
Explore in AI Chat

Overview

The view APPS.PMITS_ROUTING_DETAIL_V is a reporting and integration construct within Oracle E-Business Suite that exposes routing step detail records from the manufacturing routing infrastructure, joined to a lookup table to decode the step release type into a human-readable meaning. It is owned by the APPS schema and is documented in ETRM for both the 12.1.1 and 12.2.2 releases, where the view definition is identical.

The view is a denormalized projection: it selects routing step attributes from the base routing detail table and replaces the coded StepRelease_Type column with the corresponding lookup meaning value sourced from GEM_LOOKUPS. This conversion from internal lookup code to descriptive text makes the view suitable for direct consumption by reports, concurrent programs, and interface extracts that must present manufacturing routing information in business terms rather than encoded values. The view includes an explicit alias mapping, lkp.meaning AS StepRelease_Type, which means consumers see a meaningful string in the STEPRELEASE_TYPE column rather than the underlying lookup code.

Because the view performs an inner join between the routing detail table and the lookup view, only routing detail rows whose STEPRELEASE_TYPE code resolves to a valid entry of lookup type STEPRELEASE_TYPE are returned. This behavior is important when troubleshooting missing rows in downstream reports.

Underlying Base Objects

The view is defined over two documented objects:

  • FM_ROUT_DTL (SYNONYM) — the routing detail (routing step) entity. The synonym resolves to the underlying routing detail table in the manufacturing module. This is the primary source of routing step data such as routing identifier, step number, operation, step quantity, and step release type.
  • GEM_LOOKUPS (VIEW) — the standard EBS lookup view over FND_LOOKUP_VALUES, filtered in this join to LOOKUP_TYPE = 'STEPRELEASE_TYPE'. It supplies the decoded MEANING for each step release type code.

The join condition is LKP.LOOKUP_CODE = RD.STEPRELEASE_TYPE, combined with the lookup type predicate. The view therefore acts as a controlled decode layer between the manufacturing routing data model and reporting consumers, without duplicating data storage.

Key Columns

  • ROUTING_ID — identifier of the routing header to which the step belongs; the primary join key back to the routing master.
  • ROUTINGSTEP_ID — unique identifier of the individual routing step (also surfaced in some metadata as RoutingStep_Id).
  • ROUTINGSTEP_NO — sequence number of the step within the routing; governs execution order. Note the underlying column is spelled ROUTINGSTEP_NO in the formatted view text, while the raw text uses RoutingStep_No.
  • OPRN_ID — identifier of the operation associated with the routing step, linking to the operations master.
  • STEP_QTY — the quantity basis for the step, used in routing calculations.
  • STEPRELEASE_TYPE — aliased from LKP.MEANING; the descriptive meaning of the step release type lookup code (lookup type STEPRELEASE_TYPE). This is the column most frequently referenced by users searching on steprelease_type.
  • TEXT_CODE — the text code associated with the routing detail step.

Common Use Cases and Queries

Typical usage includes routing step listings for a given routing, verification that all step release types resolve to valid lookups, and feeds into MES or shop-floor integrations that require decoded release semantics.

List all steps for a routing:

SELECT routing_id, routingstep_no, oprn_id, step_qty, steprelease_type, text_code
FROM   apps.pmits_routing_detail_v
WHERE  routing_id = :p_routing_id
ORDER BY routingstep_no;

Group by decoded release type to audit usage:

SELECT steprelease_type, COUNT(*)
FROM   apps.pmits_routing_detail_v
GROUP BY steprelease_type;

To identify routing steps whose step release type is not resolvable (i.e., rows excluded by the inner join), query FM_ROUT_DTL directly and outer-join to GEM_LOOKUPS for lookup type STEPRELEASE_TYPE. This diagnostic is essential when the view appears to be missing step records.