Search Results purge_data_extract




Overview
Explore in AI Chat

Overview

PSB_PURGE_DATA_EXTRACT_PVT is a private (PVT-classified) PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Human Resources family of modules within the Oracle Public Sector / HR budgeting and position control product area (the PSB prefix designates position and budget-related objects). Its functional purpose is to provide the internal API layer used to purge data extract records and their associated dependent data from the underlying tables. A data extract in this context represents a stored snapshot of position, budget, costing, and distribution information that has been generated by processes such as position budgeting or costing runs. Over time these extracts accumulate and consume storage, so the package supplies a controlled programmatic mechanism to remove a single extract (identified by a data extract identifier) together with the configuration and detail rows that reference it.

The package follows the standard Oracle EBS private-API conventions, exposing a message-list-aware entry point and a concurrent-program wrapper, and marking itself as internal by using the _PVT suffix that signals the API is not intended for direct third-party invocation.

Key Procedures and Functions

The documented package exposes two procedures and one function:

  • PURGE_DATA_EXTRACT — The primary API entry point. It is a standard EBS "PL/SQL API" that follows the FND_API parameter pattern, accepting a version indicator, an initialize-message-list flag, a commit flag, and a validation level, and returning an API return status along with message count and message data. Its business input is the data extract identifier to be removed, and it returns a purge-out indicator. This is the callable interface used by other PL/SQL code that needs to remove a specific extract within a managed transaction and message context.
  • PURGE_DATA_EXTRACT_CP — The concurrent-program wrapper for the same operation. It uses the standard concurrent manager signature of errbuf and retcode output parameters together with the data extract identifier input. This variant is registered against a concurrent program definition so the purge can be submitted from the standard request submission interface and run in the background.
  • GET_DEBUG — A diagnostic helper returning the package's current debug setting. It supports troubleshooting by allowing callers or administrators to determine whether verbose debug output is enabled.

Tables Accessed

The package operates across the PSB schema tables that collectively define a data extract and its dependencies. PSB_DATA_EXTRACTS is the driving table, holding the extract header identified by the data extract identifier. Supporting configuration and reference data come from PSB_DEFAULTS, PSB_DEFAULT_ASSIGNMENTS, PSB_DEFAULT_ACCOUNT_DISTRS, PSB_ALLOCRULE_PERCENTS, and PSB_BUDGET_WORKFLOW_RULES. Position and budgeting detail resides in PSB_BUDGET_POSITIONS, PSB_ACCOUNT_POSITION_SETS and its child PSB_ACCOUNT_POSITION_SET_LINES, PSB_ELEMENT_POS_SET_GROUPS, and PSB_ATTRIBUTE_VALUES with its _I interface counterparts. Costing and employee-related rows are drawn from PSB_COST_DISTRIBUTIONS_I, PSB_EMPLOYEES, and PSB_EMPLOYEES_I. Because purging an extract must remove or reconcile all rows that reference it, the package necessarily touches this broad set of tables to preserve referential and business consistency during deletion.

Usage Notes

PSB_PURGE_DATA_EXTRACT_PVT is a private package and is not intended to be called directly by customer code. Typical invocation paths are twofold. First, the PACKAGE's PURGE_DATA_EXTRACT procedure is called by other PSB application APIs or forms that need to delete an extract inside an existing transaction and message list. Second, PURGE_DATA_EXTRACT_CP is registered as an Oracle EBS concurrent program, allowing administrators or users with appropriate responsibility and security to submit a purge request from the standard Submit Requests form and have it processed by the concurrent manager.

Because the API honors the p_commit and validation-level parameters, callers should supply a message-list initialization flag when invoking it programmatically and should check the returned status and message count before committing. In Oracle EBS 12.1.1 and 12.2.2 the package is shipped under the APPS schema with public synonyms, so any direct call must be made as APPS. Purges are inherently destructive and should be scheduled during maintenance windows; users are advised to confirm that the target data extract is no longer required by downstream costing, budgeting, or reporting processes before submission.