Results for “csd_repair_status”

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

Overview

APPS.CSD_REPAIR_FLOW_STATUSES_V is a reporting and integration view in Oracle E-Business Suite (available in 12.1.1 and 12.2.2) that exposes the status model used by Oracle Depot Repair. It joins the base flow status entity (CSD_FLOW_STATUSES_B and its translation table CSD_FLOW_STATUSES_TL) with two independent FND_LOOKUPS lookups so that a single query returns the internal flow status code, its user-facing description, the associated repair status, and internal display text. For developers and analysts searching on flow_status_desc, the view is the canonical source: the column FS_LKUP.DESCRIPTION is aliased as FLOW_STATUS_DESC and provides the descriptive text attributed to each repair flow status. Because the view resolves the user's session language through USERENV('LANG'), it returns translated values without requiring the calling code to manage language joins.

Underlying Base Objects

The documented base objects referenced by the view are:

• CSD_FLOW_STATUSES_B — the base table holding one row per flow status, keyed by FLOW_STATUS_ID and carrying the flow status code, repair status code, seeded flag, object version number, and the standard attribute flexfield columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15).
• CSD_FLOW_STATUSES_TL — the translation table providing the language-specific EXTERNAL_DISPLAY_STATUS value; joined on FLOW_STATUS_ID with LANGUAGE = USERENV('LANG').
• FND_LOOKUPS — referenced twice. The first alias, FS_LKUP, resolves LOOKUP_TYPE = 'CSD_REPAIR_FLOW_STATUS' against FLOW_STATUS_CODE to supply the flow status meaning and description. The second alias, SS_LKUP, resolves LOOKUP_TYPE = 'CSD_REPAIR_STATUS' against STATUS_CODE to supply the repair status code and meaning.
• FND_GLOBAL — the package that supplies the session language context consumed by USERENV('LANG').

The join filters out rows where FLOW_STATUS_CODE equals 'D', excluding the soft-deleted or obsolete status marker from the result set.

Key Columns

• FLOW_STATUS_ID / FLOW_STATUS_CODE — primary identifier and short code for the repair flow status.
• FLOW_STATUS_MEANING — the meaning text obtained from the CSD_REPAIR_FLOW_STATUS lookup.
• FLOW_STATUS_DESC — the description text from FND_LOOKUPS.DESCRIPTION; this is the column most commonly queried when users search for flow_status_desc.
• EXTERNAL_DISPLAY_STATUS — the translated display label from CSD_FLOW_STATUSES_TL, used for external-facing presentation.
• STATUS_CODE / STATUS_MEANING — the underlying repair status code and its human-readable meaning from the CSD_REPAIR_STATUS lookup.
• SEEDED_FLAG — indicates whether the row is seeded by Oracle or user-defined.
• OBJECT_VERSION_NUMBER — optimistic locking column carried through for update-aware logic.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment values associated with the flow status.

Common Use Cases and Queries

The view supports reporting on repair workflow configuration, validation of lookup alignment, and integration payloads that must translate internal status codes into descriptive text. A typical query to enumerate flow statuses with their descriptions is:

SELECT flow_status_code,
       flow_status_meaning,
       flow_status_desc,
       status_code,
       status_meaning,
       external_display_status
FROM   apps.csd_repair_flow_statuses_v
ORDER  BY flow_status_code;

To search for a specific description value, a developer might run:

SELECT flow_status_id, flow_status_code, flow_status_desc
FROM   apps.csd_repair_flow_statuses_v
WHERE  UPPER(flow_status_desc) LIKE UPPER('%&search_text%');

Because the view already filters obsolete codes and resolves the session language, it is preferable to joining CSD_FLOW_STATUSES_B, CSD_FLOW_STATUSES_TL, and both FND_LOOKUPS directly. Teams building extracts should note that the view is descriptive in nature: all attribute columns are read-only in this context and the view is intended for SELECT access from forms, concurrent programs, and integration interfaces.