Results for “csp_moveorder_lines_v”

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

Overview

The CSP_MOVEORDER_LINES_V view is a reporting and integration object within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, owned by the APPS schema and validated as VALID. It belongs to the CSP product module, Spares Management, and is described in the ETRM documentation as "Mover order lines including extra information for Spares Management." The view presents the line-level detail of move orders—documents used to transfer material between subinventories or organizations—enriched with attributes required by the field service and spares replenishment flows. Because it follows Oracle's standard _V naming convention, it is intended to be consumed by reports, concurrent programs, OAF pages, and external integrations rather than serving as a transaction-entry entity. A significant characteristic of this view, confirmed by the implementation text, is that it is a passthrough (simple) view: it performs no joins, aggregations, or decoding, and its column list mirrors the base table exactly. Consequently, it behaves as a stable, read-oriented access layer over the underlying move order lines data, protecting dependent code from direct table references.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: CSP_MOVEORDER_LINES, exposed to the view through a SYNONYM. The view definition is a direct SELECT of every column in that base object, with no WHERE clause, join, or analytical transformation, meaning row cardinality and data content are identical to the base table. In the EBS schema model, the APPS-owned synonym points to the CSP product schema's table, so the view is compiled and owned in APPS while the data resides in the CSP application schema. From a lineage perspective, the base table stores move order line records generated by Spares Management and Oracle Inventory move order processing. Because there is no filtering or de-duplication, any constraint, trigger, or data quality behavior enforced at the table level flows through unchanged to the view.

Key Columns

The view exposes the standard Oracle who-columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_LOGIN. This last column, LAST_UPDATED_LOGIN, is the attribute most directly relevant to the user's search term; it stores the application login identifier of the user who most recently modified the row, complementing LAST_UPDATED_BY, which holds the corresponding FND_USER identifier. The primary key is LINE_ID, with HEADER_ID providing the foreign key to the parent move order header. CUSTOMER_PO carries the customer purchase order reference used in spares and service flows, while INCIDENT_ID, TASK_ID, and TASK_ASSIGNMENT_ID link the line to the service incident and field service task context. COMMENTS holds free-text remarks. The list of columns references TASK_ASSIBNMENT_ID in the documented column listing, an apparent typographical variant of TASK_ASSIGNMENT_ID present in the source metadata. ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 supply the standard Oracle flexible attribute (Descriptive Flexfield) segment set for extension without schema change.

Common Use Cases and Queries

Typical scenarios include auditing who last changed a move order line, reconciling spares movements against incidents and tasks, and extracting line data for warehouse or service reporting. A basic query listing lines with their last-updating user is:

• SELECT line_id, header_id, last_updated_by, last_updated_login, last_update_date FROM csp_moveorder_lines_v WHERE header_id = :p_header_id;
• SELECT line_id, incident_id, task_id, customer_po FROM csp_moveorder_lines_v WHERE incident_id = :p_incident_id ORDER BY line_id;
• SELECT COUNT(*), last_updated_login FROM csp_moveorder_lines_v GROUP BY last_updated_login;

Because the view is a direct passthrough, developers may query the base table for the same results; however, referencing the view is preferred for consistency with Oracle's documented interface and to insulate custom code from future table changes.