Search Results create_pick

Overview

APPS.CSP_PLAN_DETAILS_PKG is a server-side PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Oracle Enterprise Asset Management (eAM) and Service supply chain planning functionality. In Oracle EBS 12.1.1 and 12.2.2, the CSP product family (CSP tables, e.g., CSP_PLAN_DETAILS, CSP_PLAN_REORDERS, CSP_PLANNING_PARAMETERS) underpins the planning and replenishment engine used by field service and depot repair organizations to forecast demand, compute reorder points, and generate replenishment or repair purchase order recommendations. This package is registered in ETRM with an API classification of OTHER and a status of VALID, and it is documented as exposing six procedural entry points. Its role is to manage the lifecycle of planning detail rows — including order automation, regeneration of plans, on-hand snapshots, reorder computation, and historical plan archiving — so that the planning engine produces accurate, current replenishment data for serviceable inventory items.

Key Procedures and Functions

• ORDER_AUTOMATION — Drives the automated creation or release of replenishment/repair orders based on planning outcomes, removing the need for manual order entry for qualifying planned items.
• MAIN — The primary driver procedure that coordinates the overall plan-detail processing logic; callers invoke MAIN to execute the package's core planning workflow in a single entry point.
• REGENERATE — Rebuilds or refreshes plan detail records, recalculating planning data when parameters, on-hand quantities, or demand inputs have changed.
• CURRENT_ONHAND — Captures or evaluates current on-hand balances as an input to the planning and reorder calculations.
• REORDERS — Computes or produces reorder information for planned items, feeding replenishment decisions and reorder point/quantity logic.
• COPY_PLAN_HISTORY — Copies plan data into the planning history tables, preserving prior plan versions for audit and trend analysis.

Tables Accessed

The package reads and writes a broad set of CSP planning tables through APPS synonyms. CSP_PLAN_DETAILS and its sequence/related object CSP_PLAN_DETAILS_S1 hold the core plan detail rows that this package maintains. CSP_PLANNING_PARAMETERS, CSP_ITEM_PL_PARAMS, CSP_PL_PARAM_HISTORIES, CSP_FORECAST_RULES_B, CSP_SAFETY_FACTORS, and CSP_PLAN_LEADTIMES provide the planning inputs — parameters, item-level settings, forecast rules, safety stock, and lead times — that shape the calculations. CSP_PLAN_REORDERS stores reorder recommendations produced by the REORDERS procedure. CSP_PLAN_HISTORIES is the target of COPY_PLAN_HISTORY. CSD_PRODUCT_TRANSACTIONS supplies transactional demand history used for forecasting. CSP_POPULATION_CHANGES, CSP_SUPERSEDE_ITEMS, CSP_FAILURE_RATES, and CSP_REPAIR_PO_HEADERS support population tracking, item supersession, failure-rate modeling, and repair purchase order data used in the planning and order-automation logic.

Usage Notes

CSP_PLAN_DETAILS_PKG is an internal planning engine package rather than a public API. It is referenced by the companion package CSP_ITEM_PL_PARAMS_PVT and is self-referencing, indicating internal recursion or helper calls. It is not referenced by any Oracle Forms, Oracle Reports, or concurrent program definitions per the documented dependency information, and the ETRM catalog lists only a single referencing package. Consequently, invocation typically occurs through the EBS planning concurrent programs and flows that drive the CSP replenishment process, or through custom extensions that call the documented procedures directly. Because the procedures lack published parameter signatures in the ETRM metadata, custom callers should resolve the exact interfaces against the deployed package specification in the target instance (12.1.1 or 12.2.2) before coding. Changes to planning parameters or on-hand data are normally followed by a REGENERATE or MAIN execution to refresh plan details. Support and development teams should treat this package as planning-engine-internal and avoid overloading it in place of supported APIs, using it instead for diagnostics, controlled data regeneration, and integration within the service replenishment cycle.