Search Results bsc_periodicities_wrapper

Overview

The APPS.BSC_PERIODICITIES_WRAPPER package is a PL/SQL wrapper component within the Oracle E-Business Suite Balance Scorecard (BSC) schema. Its role is to provide a controlled, encapsulated interface for managing the definition and maintenance of "periodicities" — the time-interval constructs that govern how frequently balance scorecard metrics, indicators, and scorecard computations are evaluated and refreshed. In the broader ETRM/BSC architecture, periodicities underpin the scheduling semantics of performance management, allowing scorecard designers to associate metric evaluations with recurring time windows such as daily, weekly, monthly, or quarterly periods.

The package is classified as an OTHER API in the ETRM documentation, meaning it is not a public, supported integration API but rather an internal wrapper used by the BSC application layer. It resides in the APPS schema and carries a status of VALID in both 12.1.1 and 12.2.2 environments, indicating the compiled specification and body are present and free of compilation errors.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions, of which four named routines are recorded:

• CREATE_PERIODICITY — Inserts a new periodicity definition, establishing the interval pattern that scorecard components will reference. It encapsulates the validation and persistence logic required to introduce a new time-qualifier record.
• UPDATE_PERIODICITY — Modifies the attributes of an existing periodicity definition, allowing administrators to adjust interval characteristics without directly manipulating base tables.
• DELETE_PERIODICITY — Removes a periodicity definition, subject to whatever referential or business-rule checks the wrapper enforces before physical or logical deletion.
• VALIDATE_PERIODICITY — Performs data-integrity and business-rule checks against a candidate periodicity definition, typically invoked prior to or as part of the create/update operations.

The remaining two routines are not individually named in the ETRM excerpt, but they follow the same DML-wrapper pattern. No parameter lists are documented, and none should be assumed; the routines are best treated as internal interface points rather than a published callable contract.

Tables Accessed

The ETRM metadata for BSC_PERIODICITIES_WRAPPER records no explicit table references via APPS synonyms. In practice, a wrapper of this name and purpose would operate against the BSC periodicity base tables (the underlying BSC_PERIODICITIES entity and its related lookup structures), reading existing definitions for validation and writing new or amended rows during DML operations. Because the documented dependency list shows only SYS.STANDARD, the metadata confirms the package is a lightweight wrapper with no declared direct table dependencies captured in the ETRM extract. Consultants should verify the actual table access by inspecting the package body source in the target environment.

Usage Notes

As an internal wrapper classified as OTHER, this package is not intended for direct invocation by external integrations or custom concurrent programs. It is typically called from the BSC administrative/configuration layer — for example, from Oracle Forms or internal BSC application code that manages scorecard setup. The dependency metadata indicates the package references only SYS.STANDARD and is referenced by no other packages, reinforcing its position as a leaf-level configuration utility rather than a shared service.

When extending or troubleshooting BSC periodicity behavior, developers should treat BSC_PERIODICITIES_WRAPPER as a presentation-to-data bridge: business rules and validation belong in VALIDATE_PERIODICITY, while persistence belongs in the create, update, and delete routines. Direct DML against the underlying periodicity tables should be avoided in favor of these wrapper routines to preserve consistency with BSC application expectations.