Search Results csp_prod_task_hist_rule

Overview

The APPS.CSP_PROD_TASK_HIST_RULE package body is a component of Oracle E-Business Suite's Enterprise Technical Reference Model (ETRM) within the Supply Chain / Field Service execution layer. Its business purpose is to encapsulate the logic that determines whether historical Product-Task-Parts consumption data may be used when estimating or defaulting quantities and percentages on product task records. The decision is driven by the profile option CSP_PROD_TASK_HIST_RULE, which establishes a threshold of "times used." Based on the number of times a given product-task combination has been used relative to that profile threshold, the package either suppresses history-based values entirely or derives a recommended value from rollup and part-actual history.

The package carries the header identifier cspgphrb.pls 115.2, dated 2002/11/26, and was originally authored by Arul Joseph on 03-Aug-2001. It is classified as API type "OTHER" and is owned by the APPS schema. The design intent is to centralize a single, consistent rule for history usage so that multiple callers — forms, concurrent processes, or custom extensions — apply identical logic.

Key Procedures and Functions

• GET_QUANTITY — Returns a numeric quantity value for a product-task-part line. It first checks whether a manually entered quantity exists; if so, that manual value takes precedence. Otherwise, it reads the CSP_PROD_TASK_HIST_RULE profile value and compares it against the number of times the product task has been used. When the profile threshold exceeds the usage count, no history-derived quantity is returned (NULL); when the usage count meets or exceeds the threshold, a historical quantity is computed, preferring the rollup-based average and falling back to the part-actual ratio.
• GET_PERCENTAGE — Returns a numeric percentage value for a product-task-part line using an analogous decision path. A manually entered percentage overrides history. If no manual value exists, the profile threshold is compared against the product-task usage count. Below the threshold, the function returns NULL; at or above the threshold, it computes a percentage from the rollup times-used ratio, falling back to the part-actual times-used ratio, each scaled to 100 percent.

Both functions follow the same defensive ordering: manual entry first, profile-gated history second. This ensures user input is never silently overwritten by derived history.

Tables Accessed

Based on the documented package body, no database tables are directly accessed via SQL statements. The only external data retrieval is through the Oracle Application Object Library profile facility, invoked as Fnd_profile.get('CSP_PROD_TASK_HIST_RULE', ...). All other inputs arrive as parameters supplied by the calling program. Accordingly, no APPS synonyms for base tables are documented as being referenced by this package.

Usage Notes

This package is typically invoked during product-task definition and estimation workflows, where quantity and percentage defaults must be proposed to the user or supplied to downstream rollup calculations. The functions accept the underlying usage counters and candidate values as parameters, making the package stateless and safe for repeated invocation within a single transaction. Because the behavior is entirely governed by the CSP_PROD_TASK_HIST_RULE profile option, administrators can tune history usage globally without code changes. The metadata indicates the package is referenced by zero other PL/SQL packages, so its principal consumers are expected to be forms-based or custom code that explicitly call GET_QUANTITY and GET_PERCENTAGE. Developers extending this behavior should honor the manual-entry precedence and NULL-returning threshold semantics, as callers may rely on a NULL result to mean "no history-based recommendation available."