Search Results func_call




Overview
Explore in AI Chat

Overview

The APPS.CSP_PLANNING_DRILLDOWN_V view is a reporting and integration object within the Oracle E-Business Suite Spares Management (CSP) module. It exposes consolidated planning detail at the item and organization level, joining planning header data to organization definitions so that downstream inquiries, BI Publisher reports, and custom extensions can present spares planning results with human-readable context. The view is documented as VALID in the APPS schema and is available in both EBS 12.1.1 and 12.2.2. Functionally, it serves as the drilldown layer beneath the CSP planning header view: consumers select from CSP_PLANNING_DRILLDOWN_V to retrieve item-level costs, recommended values, and organizational attributes without needing to resolve the underlying header structure themselves. The presence of columns such as ACTUAL_COST, RECOMMENDED_COST, and DELTA_COST confirms its role as a cost-comparison reporting surface for planning recommendations.

Underlying Base Objects

The view definition is a direct join between CSP_PLANNING_HEADERS_V (aliased CPHV) and ORG_ORGANIZATION_DEFINITIONS (aliased OOD), matched on ORGANIZATION_ID. The documented referenced base objects for this object are CSP_PICK_UTILS (PACKAGE), CSP_PLANNING_HEADERS_V (VIEW), FND_GLOBAL (PACKAGE), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), and ORG_ORGANIZATION_DEFINITIONS (VIEW). Of these, CSP_PLANNING_HEADERS_V and ORG_ORGANIZATION_DEFINITIONS are the only objects appearing directly in the SELECT text. The remaining objects—CSP_PICK_UTILS, FND_GLOBAL, HR_GENERAL, and HR_SECURITY—are referenced indirectly through the underlying header view or through the organization security model applied to ORG_ORGANIZATION_DEFINITIONS. FND_GLOBAL provides session context (user, responsibility, and org), while HR_SECURITY and HR_GENERAL support the operating unit and organization security predicates that constrain which organization rows a given user may see. CSP_PICK_UTILS supplies the pick/planning utility logic invoked by the headers view.

Key Columns

The view exposes twelve columns. FUNC_CALL carries the functional call identifier originating from CSP_PICK_UTILS. INVENTORY_ITEM_ID and ORGANIZATION_ID are the core inventory keys, with ITEM_NUMBER and ITEM_DESCRIPTION providing the descriptive item context from the header view. SECONDARY_INVENTORY identifies the subinventory to which the planning line applies. HEADER_DATA_TYPE is the discriminator column the user searched for; it classifies the header record and drives drilldown filtering. ORGANIZATION_NAME is sourced from ORG_ORGANIZATION_DEFINITIONS and renders the organization key in readable form. The cost trio—ACTUAL_COST, RECOMMENDED_COST, and DELTA_COST—expresses the observed cost, the planning engine's recommendation, and the variance between them, supporting exception-based review of planning output.

Common Use Cases and Queries

Typical usage includes exception reporting on high-variance planning items, subinventory-level cost review, and integration feeds that require organization names resolved inline. A representative query filters by HEADER_DATA_TYPE and organization:

  • SELECT HEADER_DATA_TYPE, ITEM_NUMBER, ITEM_DESCRIPTION, ORGANIZATION_NAME, SECONDARY_INVENTORY, ACTUAL_COST, RECOMMENDED_COST, DELTA_COST FROM APPS.CSP_PLANNING_DRILLDOWN_V WHERE HEADER_DATA_TYPE = :p_data_type AND ORGANIZATION_ID = :p_org_id ORDER BY DELTA_COST DESC;

  • Cost variance analysis: SELECT ITEM_NUMBER, SUM(DELTA_COST) FROM APPS.CSP_PLANNING_DRILLDOWN_V GROUP BY ITEM_NUMBER;

  • Drilldown from a header inquiry: SELECT * FROM APPS.CSP_PLANNING_DRILLDOWN_V WHERE INVENTORY_ITEM_ID = :p_item AND SECONDARY_INVENTORY = :p_subinventory.

Because organization security is inherited through the underlying join, results are automatically constrained by the caller's responsibility and HR security profile. Extract and load programs should therefore be scheduled under a responsibility with the intended organization access, and any direct SQL should be validated against the HR_SECURITY model to avoid unintended data exposure or omitted rows.