Search Results action_code_meaning

Overview

The CSD_LOGISTICS_LINE_STATUS_V view is a reporting and inquiry object within the Oracle E-Business Suite Depot Repair (CSD) module. It is owned by the APPS schema and is documented as a "View for logistics line on status details tab." Its principal role is to present the per-line logistics and product-transaction status information that the Depot Repair user interface surfaces on the Status Details tab, allowing repair orders, their associated product transactions, and their action/status classifications to be interrogated in a single, denormalized result set.

Because the object is a view rather than a base table, it carries no persistent data of its own. Instead, it consolidates columns from an underlying product-transaction view and enriches them at query time with lookup meanings, making it suitable for both interactive inquiry and downstream reporting or integration use. Operations and reporting teams searching by product_transaction_id — the primary key-like identifier of a product transaction line — use this view to retrieve the transaction in its logistics context together with human-readable action and status descriptions.

Underlying Base Objects

The ETRM metadata for release 12.2.2 documents the following referenced base objects:

• CSD_PRODUCT_TXNS_V (VIEW) — the primary source of the projection. The outer view selects all of its logistics columns directly from this product-transactions view.
• FND_LOOKUP_VALUES_VL (VIEW) — referenced twice through scalar subqueries in the SELECT list to translate the ACTION_TYPE and ACTION_CODE codes into their displayed meanings.
• CS_STD (PACKAGE) — a Depot Repair standard package associated with this functionality, referenced as part of the documented dependency set.

Structurally, the view is a straight projection with two correlated lookup subqueries. It does not introduce joins beyond those embedded in CSD_PRODUCT_TXNS_V; the FND_LOOKUP_VALUES_VL subqueries filter on LOOKUP_TYPE values of 'CSD_PROD_ACTION_TYPE' and 'CSD_PRODUCT_ACTION_CODE' respectively, matching LOOKUP_CODE to the selected ACTION_TYPE and ACTION_CODE. This design keeps the view thin and defers lookup resolution to execution time.

Key Columns

• PRODUCT_TRANSACTION_ID — the unique identifier of the product transaction line; the primary correlation key for searches and joins.
• ORDER_HEADER_ID — foreign key to the depot repair order header.
• ORDER_LINE_ID — foreign key to the repair order line.
• ORDER_NUMBER — the user-facing repair order number.
• PRODUCT — the product or item associated with the transaction line, as presented by CSD_PRODUCT_TXNS_V.
• REPAIR_QUANTITY — quantity of product handled on the line.
• ACTION_TYPE — coded action type, decoded via the CSD_PROD_ACTION_TYPE lookup.
• ACTION_TYPE_MEANING — the translated display meaning for ACTION_TYPE.
• ACTION_CODE — coded action, decoded via the CSD_PRODUCT_ACTION_CODE lookup.
• ACTION_CODE_MEANING — the translated display meaning for ACTION_CODE.
• PROD_TXN_STATUS — the status of the product transaction, sourced from CSD_PRODUCT_TXNS_V.

Common Use Cases and Queries

Typical uses include investigating the logistics status of a repair order, reporting on product transactions by action or status, and integrations that must resolve lookup meanings without re-implementing the CSD_* lookup logic. The following query retrieves a single transaction and its decoded attributes:

• SELECT product_transaction_id, order_number, order_line_id, product, repair_quantity, action_type_meaning, action_code_meaning, prod_txn_status FROM apps.csd_logistics_line_status_v WHERE product_transaction_id = :p_product_transaction_id;

To list all logistics lines for a repair order ordered by transaction, use:

• SELECT order_number, product_transaction_id, product, repair_quantity, action_type_meaning, action_code_meaning, prod_txn_status FROM apps.csd_logistics_line_status_v WHERE order_header_id = :p_order_header_id ORDER BY product_transaction_id;

Because the view is owned by APPS, callers should qualify it as APPS.CSD_LOGISTICS_LINE_STATUS_V or rely on a synonym and the appropriate MO or responsibility-level grants. Since the SELECT list embeds scalar subqueries against FND_LOOKUP_VALUES_VL, high-volume extracts should filter aggressively on product_transaction_id, order_header_id, or order_line_id to limit lookup resolution overhead.