Results for “parameter_value”

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

Overview

CSD_PARAMETER_EFFECTIVITY_PVT is a private (PVT) PL/SQL package body in the APPS schema that supports the effectivity determination of return parameters within the Oracle E-Business Suite Advanced Pricing and Order Management return-authorization flow. Its core responsibility is to evaluate whether a given rule condition matches a set of runtime inputs, and to resolve the effective parameter value that applies to a return scenario. The package encapsulates the business logic that governs which return parameter values are active for a specific combination of return type, item, customer, item category, and contract. Because it is classified as a private package, it is intended for internal consumption by its parent public API and other EBS components rather than for direct invocation by external code. The package body header identifies it as a member of the CSD (Common Supply and Demand, used by returns management) module, with the source file csdvpreb.pls and a creation date of Mar-04-2011.

Key Procedures and Functions

• PARAMETER_VALUE — The principal documented procedure of the package. It resolves and returns the effective value of a return parameter after applying the applicable rule conditions. This is the procedure callers rely on to obtain the parameter value that should be used given the current return inputs.
• GET_SQL_OPERATOR — A helper routine that maps or returns the SQL operator associated with a supplied rule condition. It supports the condition-matching logic by translating an operator token into its usable comparison form.
• is_rule_condition_match (private function) — An internal function that compares a rule's stored operator and criterion against a runtime input record. It selects the runtime criterion based on the parameter type (RETURNTYPE, ITEM, CUSTOMER, ITEM_CATEGORY, or CONTRACT) and returns TRUE or FALSE depending on whether the operator condition is satisfied.

The condition-matching logic is the location most relevant to the search term g_equals. The literal G_EQUALS is a package-level global constant representing the equality operator. In the documented source, the function tests p_operator = G_EQUALS (paired with a companion G_NOT_EQUALS for inequality) to determine whether the input criterion equals the stored rule criterion. This global constant centralizes the operator string so that equality comparisons remain consistent across the package.

Tables Accessed

• CSD_PARAMETER_VALUES — Stores the parameter value definitions evaluated by PARAMETER_VALUE to determine the effective value returned to the caller.
• CSD_RETURN_RULES_B — Holds the return rule header records that drive the effectivity logic.
• CSD_RET_RULE_CONDITIONS_B — Holds the individual rule conditions (operator, parameter type, criterion) evaluated by the condition-matching function.
• PLITBLM — A standard Oracle-supplied PL/SQL index-by table of VARCHAR2 values used internally for passing collections of criteria or identifiers.

Usage Notes

As a private package, CSD_PARAMETER_EFFECTIVITY_PVT is not exposed for direct customer invocation. It is referenced by one other package, which acts as the public entry point that orchestrates parameter effectivity. It is typically executed in the context of return processing within Oracle Order Management and Advanced Pricing, most often triggered through the returns/authorization forms and underlying concurrent or workflow-driven processing. The package relies on the FND logging framework (via G_LEVEL_PROCEDURE and G_RUNTIME_LEVEL) and the FND_API return-status constants (G_RET_STS_SUCCESS, G_RET_STS_ERROR), confirming that it follows standard EBS API conventions. Customizations should avoid modifying this package directly; instead, behavior should be influenced through the configuration of the CSD rule and parameter tables. Because it was certified for the 12.1.1 and 12.2.2 releases, any extension should account for the online-patching model introduced in 12.2.