Results for “csd_flwsts_milestones_v”

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

Overview

The CSD_FLWSTS_MILESTONES_V view is an APPS-owned database view within the Oracle E-Business Suite Depot Repair (CSD) module. Its primary function is to expose repair workflow status transaction milestones in a denormalized, human-readable form by joining the underlying milestone transaction table with the Oracle Application Object Library lookup definitions. As documented in the ETRM metadata, the view is VALID and is defined in the APPS schema, which indicates it is a standard seeded or supported database object intended for querying rather than direct DML against the base table.

The view serves as an integration and reporting surface for depot repair workflows. Where the base table CSD_FLWSTS_TRAN_MILES stores only coded identifiers, this view resolves the MILESTONE_CODE into a descriptive MILESTONE meaning drawn from the CSD_REPAIR_MILESTONES lookup type. This enables reports, OAF-based pages, and external integrations to present milestone information without embedding lookup resolution logic. The presence of OBJECT_VERSION_NUMBER also signals that the view participates in the EBS optimistic locking framework used by the business components that manage repair workflow transactions.

Underlying Base Objects

According to the documented view text and the 12.2.2 metadata, the view is constructed over three referenced objects:

• CSD_FLWSTS_TRAN_MILES — the primary transaction table holding workflow status transit milestone rows. Aliased as MILES in the defining query, it contributes FLWSTS_TRAN_MILE_ID, FLWSTS_TRAN_ID, MILESTONE_CODE, and OBJECT_VERSION_NUMBER. It is referenced as a synonym in the APPS schema.
• FND_LOOKUPS — the standard Oracle Applications lookup view against FND_LOOKUP_VALUES, aliased as MILES_LKUP. It supplies the lookup code and meaning for the milestone.
• FND_GLOBAL — the standard EBS package used for session and context resolution. Its presence in the dependency list reflects standard APPS view behavior, including multi-org and security context handling.

The join condition is a lookup resolution: MILES_LKUP.LOOKUP_TYPE = 'CSD_REPAIR_MILESTONES' and MILES_LKUP.LOOKUP_CODE = MILES.MILESTONE_CODE. Because this is an inner join against FND_LOOKUPS, only milestone codes that have a corresponding active lookup value of type CSD_REPAIR_MILESTONES are returned by the view.

Key Columns

The view exposes five columns, each carrying a specific reporting or transactional meaning:

• FLWSTS_TRAN_MILE_ID — the unique identifier (primary key) of the milestone transaction row.
• FLWSTS_TRAN_ID — the foreign key linking the milestone to its parent flow status transaction record.
• MILESTONE_CODE — the coded value of the repair milestone, sourced from MILES.MILESTONE_CODE and matched to MILES_LKUP.LOOKUP_CODE. This is the column most commonly referenced in user searches and API queries, for example the term milestone_code.
• MILESTONE — the translatable MEANING value from FND_LOOKUPS, providing the user-facing description of the milestone.
• OBJECT_VERSION_NUMBER — the concurrency control version stamp inherited from the base table, used to detect stale updates in the EBS BC4J layer.

Common Use Cases and Queries

Typical usage includes depot repair status reporting, milestone audit extraction, and integration feeds that require both the coded and descriptive milestone values. A common pattern filters by parent transaction or by milestone code:

• Retrieve all milestones for a given flow status transaction: SELECT FLWSTS_TRAN_MILE_ID, MILESTONE_CODE, MILESTONE FROM CSD_FLWSTS_MILESTONES_V WHERE FLWSTS_TRAN_ID = :p_tran_id;
• Resolve a specific coded milestone to its meaning: SELECT MILESTONE FROM CSD_FLWSTS_MILESTONES_V WHERE MILESTONE_CODE = :p_milestone_code AND ROWNUM = 1;
• Join the view back to the base transaction table for combined workflow and milestone reporting to expose parent transaction detail alongside milestone descriptions.

Because the view joins through FND_LOOKUPS, queries dependent on a particular milestone meaning will only return rows where the lookup remains defined and enabled for the CSD_REPAIR_MILESTONES lookup type. For reporting completeness, join the view to CSD_FLWSTS_TRAN_MILES on FLWSTS_TRAN_MILE_ID.