Search Results csp_plan_details




Overview
Explore in AI Chat

Overview

APPS.CSP_PLAN_DETAILS_PKG is a package body belonging to the Oracle E-Business Suite Service (CSP) application module, which supports field service and depot repair operations. The package encapsulates the core planning logic used to generate, maintain, and regenerate service parts planning details, including demand forecast periods, safety stock, reorder points, and on-hand positions. It is the procedural engine behind the service planning process, sitting on top of the data model defined by tables such as CSP_PLAN_DETAILS, CSP_PLAN_REORDERS, and CSP_PLAN_LEADTIMES.

The package is classified as OTHER in the ETRM metadata, meaning it is not an officially published public API but an internal implementation package. Its header identifies it as a core planning database package (file csptpldb.pls), and it is referenced by only one other package in the application, confirming its role as a supporting internal component rather than a widely reused interface.

Key Procedures and Functions

  • ORDER_AUTOMATION — Drives automated order creation based on business rules. It evaluates excess and repair-related value limits, timestamp ranges, and lead times from the workload rule view, determining when service orders should be generated or replenished automatically.
  • MAIN — The primary entry point coordinating the overall plan detail processing. It orchestrates the individual planning steps and invokes supporting routines to build and refresh plan detail records.
  • REGENERATE — Rebuilds planning data for a given plan and organization. It is used when planning parameters, forecasts, or input data have changed and the plan details must be recalculated.
  • CURRENT_ONHAND — Computes or retrieves the current on-hand quantity for items under planning, considering on-hand type, start and end day, and condition parameters. Its output feeds availability and netting calculations in the plan.
  • REORDERS — Calculates reorder recommendations for planned items based on safety factors, lead times, and planning parameters, populating the reorder data used to trigger replenishment.
  • COPY_PLAN_HISTORY — Copies current plan detail information into the plan history tables so that previous planning snapshots are preserved for comparison and audit.

Tables Accessed

The package reads and writes a broad set of CSP planning tables, all referenced through APPS synonyms. CSP_PLAN_DETAILS and its sequence CSP_PLAN_DETAILS_S1 hold the calculated plan rows, while CSP_PLAN_REORDERS, CSP_PLAN_LEADTIMES, and CSP_PLAN_HISTORIES store reorder recommendations, lead time assumptions, and historical snapshots respectively. Configuration and input data come from CSP_PLANNING_PARAMETERS, CSP_FORECAST_RULES_B, CSP_ITEM_PL_PARAMS, CSP_SAFETY_FACTORS, and CSP_PL_PARAM_HISTORIES. Item relationship logic draws on CSP_SUPERSEDE_ITEMS, CSP_FAILURE_RATES, and CSP_POPULATION_CHANGES. Transaction and procurement context is provided by CSD_PRODUCT_TRANSACTIONS, CSP_REPAIR_PO_HEADERS, and related repair order structures.

Usage Notes

This package is typically invoked from the service planning concurrent programs and from the planning forms within the CSP module. Because it is an internal package body rather than a documented public API, custom code should avoid calling its procedures directly; extensions should instead use the standard planning concurrent programs or supported APIs where available. During regeneration, the package deletes and rebuilds plan detail rows, so concurrent execution against the same plan and organization should be serialized to avoid contention on CSP_PLAN_DETAILS and its associated history and reorder tables.