Search Results csd_product_action_code




Overview
Explore in AI Chat

Overview

APPS.CSD_LOGISTICS_LINE_STATUS_V is a reporting and integration view in Oracle E-Business Suite, part of the Enterprise Territory and Repair Management (depot repair) schema owned by the CSD (Customer Service Depot) product family. It exposes logistics line status information for repair and product transactions, providing a denormalized, business-friendly projection of the underlying CSD_PRODUCT_TXNS_V view. The view's primary value is that it resolves raw lookup codes into their human-readable meanings directly within the SQL definition, eliminating the need for report developers and integration consumers to join to FND_LOOKUP_VALUES_VL independently.

In EBS 12.1.1 and 12.2.2 the object remains structurally consistent. It presents one row per product transaction line, carrying identifiers, order context, product, quantity, action attributes, and the current transaction status. Because the view is defined with an inline scalar subquery per row rather than a join, consumers see a single flat result set, which is convenient for concurrent programs, Oracle Reports, BI Publisher data templates, and OAF-based depot screens that must display actionable status information alongside descriptive lookup text.

Underlying Base Objects

The documented reference objects for this view are:

  • CSD_PRODUCT_TXNS_V (VIEW) — the sole FROM-clause source. All columns projected by CSD_LOGISTICS_LINE_STATUS_V originate from this view, which itself derives from the depot repair product transaction tables and the CS_STD package logic.
  • CS_STD (PACKAGE) — the Customer Service standard utility package that supplies core depot repair business logic, including status derivation and transaction handling used indirectly by the underlying view chain.
  • FND_LOOKUP_VALUES_VL (VIEW) — the Applications lookup view, referenced twice as inline scalar subqueries to translate ACTION_TYPE and ACTION_CODE into descriptive meanings via lookup types CSD_PROD_ACTION_TYPE and CSD_PRODUCT_ACTION_CODE respectively.

No direct base tables are declared for this view; it is a layer of presentation over an existing transactional view, and therefore inherits all row-level security, org context, and transaction filtering applied within CSD_PRODUCT_TXNS_V.

Key Columns

  • PRODUCT_TRANSACTION_ID — unique identifier of the product transaction line; the natural primary key for the row.
  • ORDER_HEADER_ID / ORDER_LINE_ID / ORDER_NUMBER — depot repair order context, enabling linkage back to the repair order header and line.
  • PRODUCT — the item or product being repaired or processed.
  • REPAIR_QUANTITY — the quantity associated with the repair or product action on the line.
  • ACTION_TYPE — the coded value describing the category of action performed; sourced from lookup type CSD_PROD_ACTION_TYPE. Because the user searched for csd_prod_action_type, this is the column most closely tied to their interest.
  • ACTION_TYPE_MEANING — the descriptive meaning of ACTION_TYPE, resolved by inline subquery against FND_LOOKUP_VALUES_VL.
  • ACTION_CODE — a more granular action coding from lookup type CSD_PRODUCT_ACTION_CODE.
  • ACTION_CODE_MEANING — the descriptive meaning of ACTION_CODE.
  • PROD_TXN_STATUS — the current status of the product transaction, reflecting where the line sits in the depot logistics flow.

Common Use Cases and Queries

Typical uses include depot repair status dashboards, logistics reporting on repair order lines, and integration extracts where downstream systems require both codes and descriptions. Because the lookup meanings are embedded, a query can be written without any explicit joins:

SELECT product_transaction_id,
       order_number,
       product,
       repair_quantity,
       action_type,
       action_type_meaning,
       action_code_meaning,
       prod_txn_status
FROM   apps.csd_logistics_line_status_v
WHERE  action_type = 'RECEIVE'
AND    prod_txn_status = 'PENDING';

To report counts by action type across all open repair lines:

SELECT action_type_meaning, COUNT(*) line_count
FROM   apps.csd_logistics_line_status_v
GROUP  BY action_type_meaning
ORDER  BY action_type_meaning;

To trace a line back to its repair order context:

SELECT order_number, order_line_id, product,
       repair_quantity, prod_txn_status
FROM   apps.csd_logistics_line_status_v
WHERE  order_header_id = :p_order_header_id;

For performance, note that each of the two inline lookup subqueries executes per returned row; restricting the result set with selective predicates, and ensuring the lookup types CSD_PROD_ACTION_TYPE and CSD_PRODUCT_ACTION_CODE are properly maintained, keeps query cost predictable. All access should be granted through the APPS schema or via a synonym with appropriate responsibility-level security.