Search Results delete_period_mask

Overview

PA_PERIOD_MASKS_PUB is a public PL/SQL API in the Oracle EBS Projects (PA) application that provides a supported programmatic interface for creating, maintaining, and deleting period masks. Period masks are configuration constructs used by the Project resource management and forecasting functionality to define a repeating, relative set of GL periods — for example "the three accounting periods beginning from a given anchor period" — that drive how forecast amounts, budgets, and other period-based project data are spread across time. The package centralizes the business logic and validation associated with period masks so that concurrent programs, forms, and custom integrations do not manipulate the underlying base tables directly. Its procedures enforce record version checking (optimistic locking), effective dating, and multi-language handling on behalf of the caller.

The package follows the standard EBS PL/SQL API conventions: every procedure carries an x_return_status out parameter (returning FND_API.G_RET_STS_SUCCESS or an error status), an x_msg_count and x_msg_data pair for message retrieval via FND_MSG_PUB, and the common p_init_msg_flag and p_commit_flag control parameters that let the caller decide whether to reset the message stack and whether the API should commit its own transaction.

Key Procedures and Functions

• MAINTAIN_PERIOD_MASKS — The primary maintenance entry point. It inserts a new period mask or updates an existing one, accepting the mask identifier, name, description, time phase code, effective start and end dates, and record version number. It also accepts the detail-level attributes (number of periods, anchor period flag, from-anchor position) and returns per-row error flags through a table-type out parameter. Record version checking is performed against the persisted row to prevent lost updates.
• MAINTAIN_PERIOD_MASK_DTLS — Maintains the detail rows of an existing period mask. This procedure operates on a period mask identified by p_period_mask_id and manages the set of detail records (number of periods, anchor flag, from-anchor position), performing the necessary insert/update/delete synchronization against the detail table.
• DELETE_PERIOD_MASK — Deletes a period mask identified by p_period_mask_id. It validates the supplied p_record_version_number before deletion to ensure the row has not been modified since it was queried. Like the other procedures, it observes the p_init_msg_flag and p_commit_flag conventions and returns status and message information to the caller.

Tables Accessed

The package reads and writes the period mask entity through the following APPS synonyms:

• PA_PERIOD_MASKS_B — base table storing the period mask header rows, including effective dates and the record version number used for concurrency control.
• PA_PERIOD_MASKS_TL — translation table holding the language-specific name and description; accessed together with FND_LANGUAGES to resolve the current session language.
• PA_PERIOD_MASKS_S — the sequence used to generate new period mask identifiers.
• PA_PERIOD_MASK_DETAILS — detail rows defining the number of periods, anchor flag, and from-anchor position for each mask.
• PA_FP_PERIOD_MASK_TMP — temporary/working table used during period mask processing.
• DUAL and PLITBLM — utility references used for single-row selection and message/bulk processing support.

Usage Notes

PA_PERIOD_MASKS_PUB is normally invoked from the Projects forecasting and period mask maintenance forms, and from concurrent programs that build or refresh period mask definitions. Custom code should call DELETE_PERIOD_MASK rather than issuing a direct DELETE against PA_PERIOD_MASKS_B, because the API performs record version validation and translation-table cleanup and populates the standard EBS message stack. Callers should retrieve diagnostics with FND_MSG_PUB.GET when x_return_status is not success, and must pass a record version number obtained from a prior query to avoid stale-row errors. The package is not referenced by any other documented PL/SQL package, so it functions as a leaf-level public API intended for external consumers.