Results for “validate_name”

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

Overview

PA_FP_SPREAD_CURVES_UTILS is a PL/SQL utility package in the Oracle EBS Projects (PA) module that supports the definition, validation, and maintenance of spread curves used in forecasting and financial planning. Spread curves in Oracle Projects distribute amounts across accounting periods or budget buckets according to a predefined pattern, allowing planners to model revenue, cost, or effort recognition over time. The package encapsulates the business rules that govern which values are legal for a spread curve, whether a curve may still be modified, and whether it is already referenced elsewhere in the system. In Oracle EBS 12.1.1 and 12.2.2, this package is part of the internal Projects foundation layer; it is not a public API in the sense of an integration interface but rather a validation and lookup utility invoked by the forms and concurrent processes that maintain spread curve definitions. The header comment identifies the source as PAFPSCUS.pls (version 120.1), indicating an Origination/Projects shared library consistent with the 11i/12.x lineage. The package is owned by APPS and classified as OTHER in the ETRM metadata, reflecting its supporting rather than externally callable role.

Key Procedures and Functions

The package exposes four documented procedures and functions. Each performs a discrete validation or status check, and all rely on standard Oracle EBS error-handling conventions, returning status through OUT parameters (x_return_status, x_msg_count, x_msg_data) rather than raising unhandled exceptions to the caller.

• IS_SPREAD_CURVE_IN_USE — A function that determines whether a given spread curve is currently referenced by other records in the system. It accepts a spread curve identifier and returns a VARCHAR2 indicator. This is the primary gating check used before allowing deletion or modification of a curve.
• VALIDATE — The main validation routine for a spread curve definition. It accepts the spread curve identifier, name, effective date range, and the ten point values (point1 through point10) that define the curve's shape, together with the standard error-handling OUT parameters. It enforces business rules such as date range consistency and point value constraints.
• VALIDATE_NAME — Validates the name of a spread curve, ensuring uniqueness and conformance to naming rules within the translation table. It accepts the name, the spread curve identifier, and error-handling OUT parameters, allowing the same routine to be used for both insert and update scenarios.
• VALIDATE_AMOUNT_IN_BUCKETS — Validates the distribution of amounts across the curve's buckets by accepting the ten point parameters. It confirms that the entered point values represent a legitimate distribution pattern.

Tables Accessed

The package references four tables through APPS synonyms. PA_SPREAD_CURVES_B is the base table holding the spread curve definition, including the identifier, effective dates, and the ten point columns; it is the primary target of the validation procedures. PA_SPREAD_CURVES_TL is the translation table storing the language-specific curve name; VALIDATE_NAME queries it to enforce uniqueness. PA_RESOURCE_ASSIGNMENTS is consulted by IS_SPREAD_CURVE_IN_USE to determine whether the curve has been assigned to resources, which would prevent modification or removal. PLITBLM is the standard Oracle EBS PL/SQL table (index-by table) type used for collecting and iterating over error messages; its presence confirms that the package accumulates multiple validation messages before returning them to the caller via x_msg_data. No direct DML against these tables is implied by the metadata; the package functions primarily as a read-and-validate utility.

Usage Notes

This package is typically invoked from the Oracle Projects setup forms that maintain spread curves, and from any concurrent program or internal process that creates or updates curve definitions. Because it is classified as OTHER and is not listed as referenced by any other package, it should be treated as an internal implementation detail rather than a supported integration point. Custom code should not call it directly for new development, since Oracle does not guarantee its signature across releases and patches. When troubleshooting spread curve setup errors in 12.1.1 or 12.2.2, the messages surfaced through x_msg_data from VALIDATE, VALIDATE_NAME, and VALIDATE_AMOUNT_IN_BUCKETS are the most useful diagnostic output, and IS_SPREAD_CURVE_IN_USE explains why a curve may be protected from change. The reference to PA_RESOURCE_ASSIGNMENTS indicates that resource assignments are the principal downstream consumer of spread curves, so removal of a curve already used in assignments will be blocked by the in-use check.