Results for “to_subinventory_code”

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

Overview

CSP_MO_LINES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined under the CSP – Spares Management product. Its documented purpose is to present move order lines together with the additional descriptive and attribute information introduced by Spares Management, allowing consumers to query move order activity without joining the underlying replenishment and incident structures themselves. The view is documented as VALID in ETRM 12.2.2 and is available in both 12.1.1 and 12.2.2 environments, although column availability may vary slightly by patch level.

The view sits at the intersection of inventory replenishment and field service operations. Move orders are the primary mechanism by which spares are requested, staged, and transferred between subinventories, and this view enriches those transactions with detail required for service reporting. Because the view exposes the ROWID of the underlying CS-owned move order line table along with the full set of MTL_TXN_REQUEST_LINES_V columns, it functions simultaneously as a reporting surface and as a key-preserved, updatable-in-principle access path for the Spares Management line records.

Underlying Base Objects

The ETRM metadata documents four referenced base objects: CSP_MOVEORDER_LINES (synonym), CS_INCIDENTS_ALL (synonym), JTF_TASKS_B (synonym), and MTL_TXN_REQUEST_LINES_V (view). The core projection in the view text is drawn from MTRLV, an alias over MTL_TXN_REQUEST_LINES_V, the inventory move order line view that resolves transaction source types, transaction types, organizations, items, subinventories, and locators.

CSP_MOVEORDER_LINES supplies the CS-owned extension columns — notably TXN_SOURCE_ID, TXN_SOURCE_LINE_ID, and TXN_SOURCE_LINE_DETAIL_ID — which identify the service document that generated the move order line. CS_INCIDENTS_ALL and JTF_TASKS_B provide the service request and task context associated with incidents that drive spares demand. The view therefore joins inventory execution data to CRM service data, with CMOL.ROWID preserving the identity of the Spares Management line record.

Key Columns

• TXN_SOURCE_ID, TXN_SOURCE_LINE_ID, TXN_SOURCE_LINE_DETAIL_ID – The columns most relevant to the search term txn_source_line_id. They tie the move order line back to its originating service document, line, and detail line.
• LINE_ID, HEADER_ID, REQUEST_NUMBER, LINE_NUMBER – Primary identifiers and human-readable references for the move order and its lines.
• MOVE_ORDER_TYPE, MOVE_ORDER_TYPE_NAME, TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_TYPE_ID, TRANSACTION_TYPE_NAME, TRANSACTION_ACTION_ID – Classification of the move order and the transaction semantics applied to it.
• ORGANIZATION_ID, INVENTORY_ITEM_ID, REVISION, LOT_NUMBER, SERIAL_NUMBER_START, SERIAL_NUMBER_END, UNIT_NUMBER – Inventory and material identification, including lot and serial control.
• FROM_SUBINVENTORY_ID, FROM_LOCATOR_ID, TO_SUBINVENTORY_ID, TO_LOCATOR_ID, TO_ACCOUNT_ID, SHIP_TO_LOCATION_ID – Source and destination stocking and accounting context.
• QUANTITY, PRIMARY_QUANTITY, QUANTITY_DELIVERED, QUANTITY_DETAILED, UOM_CODE, DATE_REQUIRED – Demand, fulfillment, and scheduling quantities and dates.
• LINE_STATUS, STATUS_DATE, REFERENCE, REFERENCE_TYPE_CODE, REFERENCE_ID, PROJECT_ID, TASK_ID – Lifecycle status and external references, including project and task accounting.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield content carried through from the underlying line.
• Standard WHO/audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The view is typically queried to reconcile spares demand against move order execution, to trace a move order line back to the incident or task that requested it, and to report open versus delivered quantities by organization and item.

SELECT line_id, request_number, line_number, organization_id,
       inventory_item_id, quantity, quantity_delivered,
       txn_source_id, txn_source_line_id, line_status
FROM   apps.csp_mo_lines_v
WHERE  txn_source_line_id = :source_line_id;

Traceability from a service request into inventory movement is a frequent pattern:

SELECT h.request_number, l.line_number, l.inventory_item_id,
       l.from_subinventory_code, l.to_subinventory_code,
       l.quantity, l.quantity_delivered, l.date_required
FROM   apps.csp_mo_lines_v l
WHERE  l.txn_source_id = :incident_id
ORDER  BY l.request_number, l.line_number;

Operational dashboards commonly aggregate outstanding quantity by organization and item, filtering on LINE_STATUS to isolate lines that have not yet been fully delivered. Because the view is defined over MTL_TXN_REQUEST_LINES_V, transaction types, subinventory codes, and locator identifiers are already resolved, which reduces the join overhead otherwise imposed on custom reports.