Search Results fpa_portfolio_s




Overview

FPA_PORTFOLIO_PVT is a private API package in the APPS schema that encapsulates the server-side business logic for creating, maintaining, and validating portfolio records in Oracle Enterprise Asset Management (EAM) and the Enterprise Portfolio Analysis (FPA) module. Portfolios in this context are named groupings of asset objects, projects, or other tracked entities used for analytical reporting, capital planning, and asset performance evaluation. The PVT classification indicates that the package is not part of the public integration surface; it is intended to be called by the public wrapper FPA_PORTFOLIO_PUB and by other internal EBS code rather than directly by external consumers. The package body is documented as VALID in ETRM for release 12.2.2 and relies exclusively on the FND_API and FND_MSG_PUB error-handling framework, consistent with the Oracle Application Object Library standard for private APIs.

Key Procedures and Functions

The ETRM metadata documents six entry points within the package body:

  • CREATE_PORTFOLIO — Inserts a new portfolio definition, including its descriptive attributes and type classification, into the underlying portfolio entity and translation tables.
  • DELETE_PORTFOLIO — Removes an existing portfolio and its associated descriptive rows, applying standard validation before deletion.
  • UPADATE_PORTFOLIO_DESCR — Updates the descriptive text for a portfolio, writing to the translated description columns. The spelling as documented reflects the actual object name in the ETRM repository.
  • UPADATE_PORTFOLIO_TYPE — Changes the portfolio type attribute, used to reclassify a portfolio within its analytical category.
  • UPADATE_PORTFOLIO_ORGANIZATION — Reassigns the owning organization for a portfolio, supporting multi-organization asset structures.
  • CHECK_PORTFOLIO_NAME — Performs uniqueness and validity validation on the portfolio name before insert or update, returning success or error through the FND_API messaging framework.

Parameter lists are not reproduced here. All procedures follow the FND_API convention of accepting a p_init_msg_list flag and returning x_return_status and x_msg_count/x_msg_data, allowing callers to handle errors consistently.

Tables Accessed

The package body references the following documented objects through APPS synonyms:

  • FPA_PORTFOLIO_S — The primary sequence source used to generate unique portfolio identifiers during creation. The user search term "fpa_portfolio_s" corresponds to this sequence.
  • FPA_OBJECTS_TL — The translated objects table, consulted for multilingual description and naming support when creating or updating portfolios.
  • FND_LANGUAGES — Used to resolve the active language environment for translated description handling.
  • DUAL — Employed for sequence next-value selection and simple validation queries.
  • DBMS_AW — An Oracle database package dependency, likely used for analytic workspace or OLAP-related processing associated with portfolio analysis.
  • FPA_PORTFS_VL — A portfolio view referenced for read operations during validation and update processing.

Writes propagate to the portfolio base and translation entities; reads are directed at the validation and language tables.

Usage Notes

FPA_PORTFOLIO_PVT is invoked indirectly through the public API layer. In a standard EBS configuration, the EAM portfolio setup form and any concurrent program that imports or maintains portfolio definitions call FPA_PORTFOLIO_PUB, which in turn delegates to the procedures in this private package. Because the package is documented as not referenced by any database object and is referenced by only one other package, its dependency surface is narrow: FND_API, FND_MSG_PUB, FND_LOG, FPA_OBJECTS_TL, FPA_PORTFOLIO_S, and FPA_PORTFS_VL. Customizations should target the public layer rather than FPA_PORTFOLIO_PVT, since private package signatures may change between patch levels of 12.1.1 and 12.2.2. When debugging portfolio creation or update failures, FND_LOG entries generated by this package and messages raised through FND_MSG_PUB provide the primary diagnostic trail.