Search Results check_portfolio_name




Overview
Explore in AI Chat

Overview

FPA_PORTFOLIO_PVT is a private (PVT) PL/SQL API package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Enterprise Tax, Regulatory, and Reporting (ETRM) product family, specifically the Fiscal Portfolio Administration (FPA) module. The package provides the internal programming interface for creating, maintaining, and validating fiscal portfolios — logical groupings of operating units, organizations, or ledger entities that are used to aggregate and report tax and regulatory data in a consolidated manner.

The "PVT" classification indicates that the package is intended strictly for internal consumption by other EBS components, forms, and concurrent programs. It is not a public API and is not documented as a supported integration point for customer extensions. All business logic for portfolio lifecycle management is encapsulated here, ensuring that validation rules, audit columns, and translation records are applied consistently regardless of the calling context.

The package was last modified in the 12.1.x release cycle (as indicated by the 2005 header revision). It remains present and callable in 12.2.2 with the same signature, so upgrade considerations are minimal for existing callers.

Key Procedures and Functions

  • CREATE_PORTFOLIO — Creates a new portfolio record. Accepts a portfolio record type (portfolio_rec_type) that carries the portfolio name, description, owner, type, and start organization, and returns the newly generated portfolio identifier along with standard API return status and message outputs.
  • DELETE_PORTFOLIO — Removes a portfolio identified by its portfolio ID. This is the procedure targeted by the user's search for "delete_portfolio." It returns the standard return status, message data, and message count outputs, allowing the caller to detect constraint violations or referential integrity failures.
  • UPADATE_PORTFOLIO_DESCR — Updates descriptive attributes of an existing portfolio based on the supplied portfolio record. The misspelling ("Upadate") is preserved in the actual package source and must be used exactly as spelled when invoking the procedure.
  • UPADATE_PORTFOLIO_TYPE — Changes the classification code of a portfolio, given its portfolio ID and a new portfolio class code.
  • UPADATE_PORTFOLIO_ORGANIZATION — Reassigns a portfolio to a different organization, given the portfolio ID and the target organization identifier.
  • CHECK_PORTFOLIO_NAME — A function returning a numeric result that validates whether a proposed portfolio name is unique and acceptable, typically against an existing portfolio ID so that the current record is excluded from the duplicate check.

Tables Accessed

  • FPA_PORTFOLIO_S — The primary base table storing portfolio definitions. All create, delete, and update operations write to this table.
  • FPA_OBJECTS_TL — The translation table holding language-specific portfolio names and descriptions. Maintained in parallel with FPA_PORTFOLIO_S to support multi-language deployments.
  • FND_LANGUAGES — Read to determine installed and enabled languages, supporting translation row handling.
  • DBMS_AW — Referenced for analytic workspace operations associated with portfolio data aggregation.
  • DUAL — Used for single-row queries and default value derivation.

Usage Notes

Because this is a PVT package, it is normally invoked by the FPA portfolio maintenance form, by ETRM concurrent programs that seed or reorganize portfolios, and by one other documented package within the ETRM schema. Custom code should generally use a public API rather than calling FPA_PORTFOLIO_PVT directly; direct calls are unsupported and may break during patching.

Callers must supply a valid API version, handle the OUT parameters (return status, message data, message count) and raise the standard error stack when x_return_status indicates failure. The misspelled procedure names must be matched exactly. Deletion should be attempted only when no dependent tax or reporting records reference the portfolio, since referential integrity is enforced at the database level.