Search Results get_quantity

Overview

The APPS.CSP_PROD_TASK_HIST_RULE package is a utility package within the Oracle E-Business Suite (EBS) Discrete Manufacturing and Enterprise Asset Management domain, associated with the CSP (Capital/Service Procurement & Production) module family. Its primary business function is to determine whether historical Product-Task-Parts detail data should be applied when calculating production quantity and percentage values. This decision is governed by the value configured in the CSP_PROD_TASK_HIST_RULE system profile option, which allows the application to switch between historical trends and manually entered values.

The package is declared with AUTHID CURRENT_USER, indicating that its executable privileges are evaluated against the invoking schema rather than the package owner. It is a lightweight rules engine whose header dates to 2001 (last modified 2002, version 115.2), reflecting its role as foundational, stable logic that predates more recent EBS releases while remaining present in 12.1.1 and 12.2.2 installations.

Key Procedures and Functions

• GET_QUANTITY — Returns a numeric quantity value. It consolidates several candidate inputs (product-task times used, manual quantity, rollup quantity used, rollup times used, quantity used, and part actual times used) and, based on the active history rule profile setting, decides which source drives the returned quantity. This is the function referenced by users searching for "get_quantity".
• GET_PERCENTAGE — Returns a numeric percentage value using a parallel decision model, weighing product-task times used, manual percentage, rollup times used, and part actual times used. It determines whether the percentage should be derived from history or taken from the manual entry.

Both functions share the same design intent: they encapsulate the rule-evaluation logic so that calling programs do not need to embed profile checks or branching logic themselves.

Tables Accessed

The package metadata does not document any tables referenced through APPS synonyms. The package operates primarily on the scalar values passed into its functions rather than performing direct DML or queries against base tables. The relevant profile option value (CSP_PROD_TASK_HIST_RULE) is read via the standard EBS profile mechanism, typically FND_PROFILE, which is invoked internally rather than enumerated as a formal table dependency. No persistent reads or writes to application tables are recorded, consistent with its role as a pure calculation helper.

Usage Notes

Given that it is not referenced by any other documented package, CSP_PROD_TASK_HIST_RULE is most commonly invoked directly by Oracle Forms or by concurrent program logic within the CSP production-task processing flow. Typical invocation scenarios include:

• Oracle Forms used to record production task completions, where quantity and percentage defaults must respect the history rule profile.
• Concurrent programs that roll up production task history and must apply consistent rule-based calculations.
• Custom extensions or reports in customer-specific schemas that need to replicate Oracle's history-versus-manual decision logic.

Because the functions accept all candidate values as parameters and return a single number, callers should resolve the input data (times used, manual entry, rollup values) before calling. The profile option must be correctly set, as it is the sole determinant of which path the functions take. As with any APPS-owned package, customer code should not modify it; it is safe to call but should be treated as read-only reference logic.