Results for “csp_moveorder_headers”

50+ results




Overview
Explore in AI Chat

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

Overview

CSP_MOVEORDER_HEADERS is a table owned by the CSP schema within the Oracle E-Business Suite Spares Management module. It stores supplementary header-level information for move orders, which are internal inventory transfer and replenishment documents used to move material between subinventories, locators, or organizations. The table does not replace the standard Oracle Inventory move order infrastructure; rather, it extends the base header record held in MTL_TXN_REQUEST_HEADERS with spares-specific attributes. This design allows CSP to layer distribution, shipment, and receipt configuration onto move orders without altering the core WMS and Inventory tables.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning. This is a reasonable heuristic: the table carries descriptive and contextual attributes (carrier, shipment method, auto-receipt flags, attributes) that qualify the move order header rather than defining the core business entity itself. The primary key, HEADER_ID, is shared with MTL_TXN_REQUEST_HEADERS by way of the foreign key relationship, so the table functions as an extension of that hub-like record rather than an independent one.

Key Information Stored

The table contains 28 documented columns. The most significant are summarized below.

  • HEADER_ID — The primary key, enforced by CSP_MOVEORDER_HEADERS_PK and also by the unique index CSP_MOVEORDER_HEADERS_U1. It is the foreign key to MTL_TXN_REQUEST_HEADERS, meaning the value identifies the underlying Oracle move order header.
  • CARRIER — The carrier responsible for shipping the move order contents.
  • SHIPMENT_METHOD — The shipment method used for the move order transfer.
  • AUTORECEIPT_FLAG — Indicates whether receipt of the moved material is processed automatically.
  • LOCATION_ID — The location associated with the move order, typically the ship-to or delivery location.
  • PARTY_SITE_ID — The party site reference, linking the move order header to a specific customer, supplier, or internal site address.
  • SECURITY_GROUP_ID — The security group that governs access to the record, with a foreign key to FND_SECURITY_GROUPS.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle flexfield descriptor and 15 descriptive flexfield segments used for customer-specific extensions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Oracle who-columns that provide audit and concurrency information.

Because HEADER_ID is both the primary key and a foreign key, it is a surrogate identifier that is not independently generated by this table; the business-key candidate CSP_MOVEORDER_HEADERS_U1 coincides with the primary key.

Common Use Cases and Queries

Typical use cases include reporting on spares distribution activity, validating shipment and auto-receipt configuration on move orders, and extracting flexfield data for downstream integrations.

A common pattern joins the CSP header extension to the base move order header for a complete view:

  • SELECT c.HEADER_ID, m.REQUEST_NUMBER, c.CARRIER, c.SHIPMENT_METHOD, c.AUTORECEIPT_FLAG FROM CSP.CSP_MOVEORDER_HEADERS c, MTL_TXN_REQUEST_HEADERS m WHERE c.HEADER_ID = m.HEADER_ID;

A second pattern retrieves line-level detail across the header and its lines:

Flexfield-driven reporting can filter on ATTRIBUTE_CATEGORY and the ATTRIBUTE columns, while security-aware queries should constrain on SECURITY_GROUP_ID when multi-organization access controls apply.

Related Objects

  • MTL_TXN_REQUEST_HEADERS — The base Oracle move order header table; joined on CSP_MOVEORDER_HEADERS.HEADER_ID to MTL_TXN_REQUEST_HEADERS.HEADER_ID.
  • CSP_MOVEORDER_LINES — The line-level companion table, referencing CSP_MOVEORDER_HEADERS.HEADER_ID through CSP_MOVEORDER_LINES.HEADER_ID.
  • FND_SECURITY_GROUPS — Referenced by CSP_MOVEORDER_HEADERS.SECURITY_GROUP_ID to enforce access control.
  • MTL_SYSTEM_ITEMS_B and MTL_ITEM_LOCATIONS — Commonly joined through the line table for item and locator detail.
  • HR_LOCATIONS_ALL — Frequently joined on LOCATION_ID to resolve location descriptions.
  • Standard Inventory move order APIs, such as the transaction request interfaces, are the supported route for creating and maintaining these records.