Results for “csd_flwsts_tran_resps_v”

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

Overview

The CSD_FLWSTS_TRAN_RESPS_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite CSD – Depot Repair product module. It exposes the association between workflow status transactions and the Oracle EBS responsibilities authorized to act upon them. In the Depot Repair and Service lifecycle, a flow status transaction (FLWSTS_TRAN) represents a discrete move of a repair order or service line from one operational status to another. Each such transition may be governed by one or more responsibilities, and this view resolves the internal responsibility identifier into a user-friendly, language-specific responsibility name so that the data can be presented directly in forms, reports, and outbound interfaces without an additional lookup join.

The view is documented as VALID across both Oracle EBS 12.1.1 and 12.2.2 and remains a dependable read-only source for responsibility-transaction mapping queries. Because it is a view rather than a table, it carries no independent storage and no direct DML path; all data originates from the underlying transaction-responsibility intersection table and the responsibility translation table.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects, both accessed through APPS synonyms:

• CSD_FLWSTS_TRAN_RESPS — the transaction-responsibility intersection stored in the CSD schema. This table holds the primary key FLWSTS_TRAN_RESP_ID, the foreign key FLWSTS_TRAN_ID pointing to the parent status transaction, the foreign key RESPONSIBILITY_ID, and the concurrency control column OBJECT_VERSION_NUMBER.
• FND_RESPONSIBILITY_TL — the Oracle Application Object Library responsibility translation table, which supplies the translated, language-dependent RESPONSIBILITY_NAME.

The join condition is an equality between RESPS.RESPONSIBILITY_ID and A_RESPS.RESPONSIBILITY_ID, further restricted by RESPS.LANGUAGE = USERENV('LANG'). This session-environment predicate ensures that only the responsibility name matching the caller's current runtime language preference is returned, preventing duplicate rows that would otherwise arise from the multi-language structure of FND_RESPONSIBILITY_TL.

Key Columns

• FLWSTS_TRAN_RESP_ID — Primary key of the transaction-responsibility assignment; the unique surrogate identifier for each responsibility linked to a status transition.
• FLWSTS_TRAN_ID — The identifier of the parent flow status transaction. This is the column most frequently supplied as a search predicate, and it corresponds directly to the user search term "flwsts_tran_id".
• RESPONSIBILITY_ID — The numeric responsibility identifier in FND, used as the join key to the translation table.
• RESPONSIBILITY_NAME — The translated responsibility name in the user's session language, suitable for direct display on reports and inquiry screens.
• OBJECT_VERSION_NUMBER — The optimistic locking version column inherited from the base intersection table, indicating the revision level of the assignment record.

Common Use Cases and Queries

Typical usage includes determining which responsibilities are permitted to execute a given status transition, validating user access before invoking a depot repair status change, and producing administrative reports of transition-to-responsibility mappings. Integration consumers frequently extract the FLWSTS_TRAN_ID and RESPONSIBILITY_NAME pairs to populate external workflow or mobile repair applications.

A representative query retrieving all responsibilities for a specific transaction is:

• SELECT flwsts_tran_id, responsibility_id, responsibility_name FROM csd_flwsts_tran_resps_v WHERE flwsts_tran_id = :p_tran_id ORDER BY responsibility_name;
• SELECT flwsts_tran_resp_id, flwsts_tran_id, responsibility_name, object_version_number FROM apps.csd_flwsts_tran_resps_v WHERE responsibility_id = :p_resp_id;

Because the view enforces the USERENV('LANG') predicate, queries automatically return names in the invoking user's language, and no explicit language join is required by the caller. Always qualify the view with the APPS schema in custom code and avoid treating it as a DML target.