Results for “csp_requirement_headers_v”

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

Overview

The CSP_REQUIREMENT_HEADERS_V view is an APPS-owned database object within the Oracle E-Business Suite Spares Management (CSP) product family. It exposes header-level information about parts requirements — the demand records that drive spare parts sourcing, planning, and fulfillment against field service activities. The view is validated and available in both Oracle EBS 12.1.1 and 12.2.2.

Rather than requiring integration or reporting developers to join the underlying CSP, JTF (Task), OE, and HR organization tables manually, the view pre-assembles a consolidated, denormalized projection of each requirement header. It resolves foreign keys into human-readable codes and names — service request numbers, task numbers, order type names, and destination organization codes — and flattens assignment context (resource type and resource ID) so that a requirement can be reported against either its own stored resource or the resource captured on the associated task assignment. For this reason the view is commonly used as a reporting and integration access point: discoverable through oe_transaction_types joins (which it already contains internally), it is frequently referenced by Service/Spares reporting extracts, OBIEE/BI Publisher datasets, and custom concurrent programs that need a flat requirement-header result set without owning the join logic themselves.

Underlying Base Objects

The view is defined over the following documented base objects:

• CSP_REQUIREMENT_HEADERS — the driving synonym and primary source of all requirement header columns.
• OE_TRANSACTION_TYPES — outer-joined to resolve ORDER_TYPE_ID into an order type name, restricted so that only transaction types whose type code evaluates to 'ORDER' (via NVL(...,'ORDER')) participate.
• JTF_TASK_ASSIGNMENTS — outer-joined on TASK_ASSIGNMENT_ID to supply assignment-level resource type and resource ID.
• JTF_TASKS_B — accessed indirectly through the JTF_TASKS_VL view for task number and source object context; the outer join is further constrained to NVL(SOURCE_OBJECT_TYPE_CODE,'SR') = 'SR', i.e., service-request-sourced tasks.
• ORG_ORGANIZATION_DEFINITIONS — outer-joined to translate DESTINATION_ORGANIZATION_ID into ORGANIZATION_CODE.
• HR_GENERAL and HR_SECURITY — packages referenced for security/context resolution within the view's execution environment.

All non-driving joins are outer joins, so a requirement header row is retained even when its task, assignment, order type, or destination organization is absent; in those cases the derived descriptive columns return NULL.

Key Columns

• REQUIREMENT_HEADER_ID — primary identifier for the requirement header; the join key back to CSP base tables.
• OPEN_REQUIREMENT — flag indicating whether the requirement is still open.
• SERVICE_REQUEST / TASK_ID / TASK_NUMBER / TASK_ASSIGNMENT_ID — the service request and task context to which the requirement is attached.
• RESOURCE_TYPE_CODE / RESOURCE_ID — derived via DECODE: when a task assignment exists, values come from JTF_TASK_ASSIGNMENTS; otherwise the header's own resource type and ID are used.
• ORDER_TYPE_ID / ORDER_TYPE_NAME — the associated transaction type and its description from OE_TRANSACTION_TYPES.
• NEED_BY_DATE — required-by date for the parts demand.
• SHIP_TO_LOCATION_ID / ADDRESS_TYPE — shipping and address context for the requirement.
• DESTINATION_ORGANIZATION_ID / DESTINATION_ORGANIZATION / DESTINATION_SUBINVENTORY — destination inventory organization and subinventory.
• PARTS_DEFINED — indicator of whether parts lines have been defined for the header.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard descriptive flexfield columns.

Common Use Cases and Queries

The view supports reporting on open requirements, tracing requirements to service requests and order types, and integration extracts that must resolve organization and resource descriptors. A typical query lists open requirements with their service request, order type, and destination:

• Filter by OPEN_REQUIREMENT = 'Y' or NEED_BY_DATE windows for demand reporting.
• Group by DESTINATION_ORGANIZATION and ORDER_TYPE_NAME to summarize spares demand.
• Join ORDER_TYPE_ID back to OE_TRANSACTION_TYPES only where additional transaction type attributes are required, since the view already resolves the name.

Example:

SELECT requirement_header_id, service_request, task_number, order_type_name, need_by_date, destination_organization, open_requirement FROM csp_requirement_headers_v WHERE open_requirement = 'Y' AND TRUNC(need_by_date) >= TRUNC(SYSDATE) ORDER BY need_by_date;

Because the joins are outer joins and the task join is constrained to service-request sources, results reflect only SR-derived task context for task/assignment columns, while the requirement header itself is always preserved for matching base rows.