Search Results delete_periodicity

Overview

BSC_PERIODICITIES_PVT is a private PL/SQL package in the APPS schema that provides the internal implementation layer for managing periodicities within the Oracle E-Business Suite Balanced Scorecard (BSC) module. Periodicity definitions control the time cadence — daily, weekly, monthly, quarterly, and similar intervals — against which KPI targets and scorecard objectives are evaluated and refreshed. The package is classified as a private (PVT) API, meaning it is not intended for direct external invocation. It sits beneath the public specification BSC_PERIODICITIES_PUB, which exposes the supported interface to callers, and it encapsulates the procedural logic that the public layer delegates to. The header comment (BSCVPERS.pls, originally created 14-JUL-2005) confirms the module's purpose: "PRIVATE specification to manage periodicities."

Key Procedures and Functions

• CREATE_PERIODICITY — Inserts a new periodicity definition. It accepts an API version, a commit flag, and a periodicities record, returning standard API status, message count, and message data outputs.
• RETRIEVE_PERIODICITY — Fetches an existing periodicity definition matching the supplied record and returns the fully populated periodicity record along with status and message outputs.
• UPDATE_PERIODICITY — Modifies an existing periodicity. In addition to the standard outputs, it returns a structural flag indicating whether the change affected the structural definition of the periodicity. It defaults its commit parameter to FND_API.G_FALSE.
• INCR_REFRESH_OBJECTIVES — Performs an incremental refresh of objectives associated with a periodicity. This procedure propagates periodicity changes into the objective and KPI calculation cycle, returning standard status and message outputs.
• DELETE_PERIODICITY — Removes a periodicity definition. This is the procedure most directly associated with the user search term "delete_periodicity," and it is the logical counterpart to CREATE_PERIODICITY.

All procedures follow the Oracle Application Object Library (AOL) API conventions, using x_Return_Status, x_Msg_Count, and x_Msg_Data for error and message handling, and passing records typed against BSC_PERIODICITIES_PUB.Periodicities_Rec_Type.

Tables Accessed

• BSC_SYS_PERIODICITIES and BSC_SYS_PERIODICITIES_TL — Store the base and translated periodicity definitions; the TL table supplies language-specific names and descriptions.
• BSC_SYS_PERIODS and BSC_SYS_PERIODS_TL — Hold the individual time periods generated for each periodicity, with translations in the TL counterpart.
• BSC_KPI_PERIODICITIES — Associates KPIs with the periodicities they use, supporting the incremental refresh of objectives.
• FND_LANGUAGES — Provides the installed language list used to resolve translated content.

All tables are accessed through APPS synonyms.

Usage Notes

Because BSC_PERIODICITIES_PVT is a private package, it should not be called directly by custom code. Applications, forms, and concurrent programs in the Balanced Scorecard module invoke the public wrapper BSC_PERIODICITIES_PUB, which in turn calls these private procedures after performing validation. The metadata notes the package is referenced by one other package, reinforcing its role as an internal dependency rather than an entry point. When troubleshooting periodicity deletion or creation issues, the call chain typically begins at the public API or an OAF-based administration page and terminates in DELETE_PERIODICITY or CREATE_PERIODICITY within this package. The INCR_REFRESH_OBJECTIVES procedure is generally triggered when periodicity changes must be reflected in objective scoring, so administrators should expect recalculation activity following structural updates.