Results for “csp_requirement_headers”

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

Overview

CSP_REQUIREMENT_HEADERS is a transactional table in the CSP (Spares Management) schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the header-level information for parts requirements raised within the spares management process. Each row represents a discrete requirement — typically a demand for a spare or service part — capturing the originating task context, the destination and shipping details, the need-by date, and the organizational and resource information required to fulfil the demand. The table functions as the parent for requirement lines, which define the actual items being requested.

From a Data Vault modeling perspective, the heuristic classification for this object is satellite-leaning. It carries descriptive, mutable attributes (need-by dates, shipping methods, subinventory destinations, descriptive flexfields) alongside references to its business context, suggesting it is best modeled as a satellite attached to a requirement hub or link rather than as an independent hub. This is offered as a modeling suggestion only; the physical EBS table remains a conventional transactional entity with standard WHO audit columns.

Key Information Stored

The surrogate primary key is REQUIREMENT_HEADER_ID, enforced by CSP_REQUIREMENT_HEADERS_PK. A unique index, CSP_REQUIREMENT_HEADERS_U1, also exists on REQUIREMENT_HEADER_ID, which represents the business-key candidate for the record. Thirty-eight columns are documented in the 12.2.2 physical schema; the most significant include:

• OPEN_REQUIREMENT — flag indicating whether the requirement remains outstanding.
• TASK_ID and TASK_ASSIGNMENT_ID — the Oracle Tasks linkage that establishes the business context for the requirement.
• DESTINATION_ORGANIZATION_ID and DESTINATION_SUBINVENTORY — the receiving organization and subinventory.
• SHIP_TO_LOCATION_ID and SHIP_TO_CONTACT_ID — ship-to address and contact for the requirement.
• ADDRESS_TYPE and TIMEZONE_ID — address classification and time zone context.
• RESOURCE_TYPE and RESOURCE_ID — the resource associated with the demand.
• NEED_BY_DATE — the date the requirement must be satisfied.
• SHIPPING_METHOD_CODE and ORDER_TYPE_ID — shipping method and the order type used if the requirement is converted to an order.
• PARTS_DEFINED — indicator of whether the parts on the requirement have been defined.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard descriptive flexfield columns.
• SECURITY_GROUP_ID — the security group scoping the record.

Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — are also present.

Common Use Cases and Queries

The table is typically queried to report on open spare parts demand, to trace requirements back to their originating task assignment, or to join requirement lines for line-level detail. A common reporting pattern is to select open requirements by destination organization and need-by date:

• Open requirements report: filter on OPEN_REQUIREMENT = 'Y' and order by NEED_BY_DATE, joining to CSP_REQUIREMENT_LINES on REQUIREMENT_HEADER_ID to list the requested items.
• Task traceability: join to JTF_TASK_ASSIGNMENTS on TASK_ASSIGNMENT_ID and JTF_TASKS_B on TASK_ID to relate a requirement back to its source task or work order.
• Shipping and order conversion: group by SHIPPING_METHOD_CODE or ORDER_TYPE_ID to analyse fulfilment routing.
• Organization rollups: join to MTL_PARAMETERS on DESTINATION_ORGANIZATION_ID to present inventory organization names in lieu of numeric IDs.

Related Objects

• CSP_REQUIREMENT_LINES — child table; joined on REQUIREMENT_HEADER_ID, holding the individual parts on each requirement.
• JTF_TASK_ASSIGNMENTS — referenced via TASK_ASSIGNMENT_ID; the task assignment that generated the requirement.
• JTF_TASKS_B — referenced via TASK_ID; the base task record.
• MTL_PARAMETERS — referenced via DESTINATION_ORGANIZATION_ID; supplies inventory organization detail.
• HZ_TIMEZONES — referenced via TIMEZONE_ID.
• SO_ORDER_TYPES_115_ALL — referenced via ORDER_TYPE_ID; defines the applicable order type.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for access scoping.

These relationships position CSP_REQUIREMENT_HEADERS as the central header entity within the spares requirement model, linking task-driven demand to inventory and order fulfilment data.