Results for “csp_planning_parameters”

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

Overview

CSP_PLANNING_PARAMETERS is the core configuration table for Oracle Spares Management (CSP), a module within the Oracle E-Business Suite (EBS) supply chain suite available in releases 12.1.1 and 12.2.2. It stores the planning parameters that govern how spare parts demand is forecast, how service levels are applied, and how inventory recommendations are generated across an organization's stocking sites. Each row defines a parameter set used by the CSP planning engine to drive forecast rules, excess rules, loop calculation rules, and recommendation logic for spares replenishment.

From a modeling perspective, the table structure is satellite-leaning. The surrogate primary key CSP_PLANNING_PARAMETERS_PK (PLANNING_PARAMETERS_ID) identifies each parameter definition, while the surrounding foreign keys anchor the record to organizational and category context. A Data Vault classification of satellite is a reasonable heuristic suggestion, since the table primarily holds descriptive and reference attributes that elaborate on the planning context rather than serving as a pure hub or associative link.

Key Information Stored

The table contains 108 columns. The most significant attributes include the following:

• PLANNING_PARAMETERS_ID — the surrogate primary key and the identifier referenced by dependent CSP tables.
• FORECAST_RULE_ID and DEFAULT_FORECAST_RULE_ID — link to CSP_FORECAST_RULES_B, controlling the forecasting method.
• EXCESS_RULE_ID and DEFAULT_EXCESS_RULE_ID — link to CSP_EXCESS_RULES_B, governing excess stock evaluation.
• CALCULATION_RULE_ID — links to CSP_LOOP_CALC_RULES_B for loop calculation behavior.
• ORGANIZATION_ID, SECONDARY_INVENTORY, and ORGANIZATION_TYPE — define the inventory context for the parameter set.
• CATEGORY_SET_ID and CATEGORY_ID — anchor the parameter set to a category hierarchy.
• SERVICE_LEVEL, EDQ_FACTOR, SAFETY_STOCK_FLAG, and ASL_FLAG — core planning levers.
• PLANNER_CODE and CONDITION_TYPE — assignment and condition attributes.
• LEVEL_ID, NODE_TYPE, NODE_NAME, and PARENT_NODE_ID — hierarchical placement of the parameter set.

The unique indexes CSP_PLANNING_PARAMETERS_U1 (PLANNING_PARAMETERS_ID, ZD_EDITION_NAME) and CSP_PLANNING_PARAMETERS_U2 (LEVEL_ID, ZD_EDITION_NAME) serve as business-key candidates, supporting multi-edition handling.

Common Use Cases and Queries

Typical usage involves joining planning parameters to forecast or organization data to report on spares configuration. For example:

• Reporting all parameter sets for a given organization and secondary inventory.
• Identifying which category hierarchies have safety stock enabled.
• Auditing planner code assignments across stocking sites.

A representative query pattern is:

SELECT p.planning_parameters_id, p.organization_id, p.category_id,
       p.service_level, p.planner_code
FROM   csp_planning_parameters p
WHERE  p.organization_id = :org_id;

Related Objects

The following objects are most significant in relation to CSP_PLANNING_PARAMETERS:

• CSP_FORECAST_RULES_B — joined on FORECAST_RULE_ID.
• CSP_EXCESS_RULES_B — joined on EXCESS_RULE_ID.
• CSP_LOOP_CALC_RULES_B — joined on CALCULATION_RULE_ID.
• MTL_SECONDARY_INVENTORIES — joined on SECONDARY_INVENTORY and ORGANIZATION_ID.
• MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B — joined on CATEGORY_ID and CATEGORY_SET_ID.
• CSP_PRODUCT_POPULATIONS — references this table via PLANNING_PARAMETERS_ID.
• CSP_USAGE_HEADERS — references this table via PLANNING_PARAMETERS_ID.
• CSP_CURR_SUP_DEM_SUMS and CSP_FAILURE_RATES — dependent tables referencing PLANNING_PARAMETERS_ID.