Results for “miles_lkup”

4 results




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

Overview

The view APPS.CSD_FLWSTS_MILESTONES_V is a denormalized reporting object within the Oracle E-Business Suite Depot Repair module. It presents repair workflow status milestones — the discrete checkpoints a repaired item passes through during its lifecycle, such as receipt, diagnosis, repair, and return — in a form that resolves raw lookup codes to their user-facing meanings. The view is owned by the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2. Its principal value lies in decoupling callers from the underlying FND_LOOKUPS join, exposing an already-translated milestone label alongside the workflow transaction identifiers. For reporting, integration, and OAF-based pages, this view removes the need to re-issue the lookup join against the CSD_REPAIR_MILESTONES lookup type.

Underlying Base Objects

The view is defined over two documented base objects:

Documented metadata also references FND_GLOBAL (package), reflecting the multi-org / security context applied at runtime through the underlying lookups view rather than through explicit columns in this view text. The join is an inner join, so milestone rows whose code is not present in the lookup set will not appear.

Key Columns

  • FLWSTS_TRAN_MILE_ID — primary key of the milestone row; uniquely identifies a single milestone occurrence.
  • FLWSTS_TRAN_ID — foreign key to the parent workflow status transaction, linking the milestone back to its repair order transaction.
  • MILESTONE_CODE — the lookup code from CSD_REPAIR_MILESTONES; the machine-readable milestone identifier.
  • MILESTONE — the lookup MEANING; the display-ready description of the milestone for user-facing reports.
  • OBJECT_VERSION_NUMBER — the version token carried forward from CSD_FLWSTS_TRAN_MILES, used for concurrency control in OAF/ADF updates.

Common Use Cases and Queries

Typical uses include building milestone timelines per repair transaction, listing all milestones reached for a given FLWSTS_TRAN_ID, and producing label-based dashboards without re-joining lookups. A common query pattern is:

  • Select FLWSTS_TRAN_ID, MILESTONE_CODE, and MILESTONE filtered by a specific transaction to reconstruct the workflow progression.
  • Group by MILESTONE to count occurrences for cycle-time or throughput reporting.
  • Join back to CSD_FLWSTS_TRAN_MILES on FLWSTS_TRAN_MILE_ID when additional milestone attributes are required.

Because the view already filters the lookup type and resolves the meaning, it is the preferred read source for milestone enumeration in concurrent programs and BI Publisher reports built on Depot Repair data.