Search Results no_data_found

Overview

PSB_PURGE_DATA_EXTRACT_PVT is a private PL/SQL package in the Oracle EBS Applications (APPS) schema that supports the Human Resources/Payroll data extract functionality within the PSB (Payroll System Batch / Standard Benefits) module. Its primary business function is to remove or purge configured data extract definitions and their dependent child records from the staging and setup tables. Data extracts define sets of entities, positions, defaults, and pay elements that are assembled for downstream processing, reporting, or third-party integration. When a data extract is obsolete, erroneous, or no longer required, business users need a controlled mechanism to remove it and all associated relational artifacts without violating referential dependencies. This package provides that controlled purge capability. The package is classified as a private API (PVT), meaning it is intended to be invoked only by other packages within the same module or by tightly coupled internal components, not by external or customer-facing code.

Key Procedures and Functions

• PURGE_DATA_EXTRACT — The principal procedure of the package. It orchestrates the deletion of a data extract identified by a data extract identifier. Internally it opens a series of cursors (C_Entity_Set, C_Entity, C_Positions, C_Defaults, C_Elements) to collect the child rows associated with the extract before removing them. Because these lookups are performed with SELECT INTO retrievals against a specific identifier, a search for the "no_data_found" exception is directly relevant: when a cursor or a SELECT INTO finds no matching row, the package must handle NO_DATA_FOUND so that the purge completes gracefully rather than aborting mid-transaction.
• PURGE_DATA_EXTRACT_CP — A concurrent-program wrapper for PURGE_DATA_EXTRACT. The "_CP" suffix convention indicates a companion entry point designed to be called from a concurrent program definition, translating the standard FND concurrent manager calling conventions into parameters expected by the private API.
• GET_DEBUG — A diagnostic function that exposes the package-level debug buffer (g_dbug) so that processing steps and errors encountered during a purge can be inspected by the developer or support analyst.

The body also declares the standard token/message infrastructure (message_token, add_message, msg_tok_names, msg_tok_val, no_msg_tokens) used for building translatable FND messages.

Tables Accessed

The package reads and writes the core PSB setup tables. PSB_DATA_EXTRACTS holds the parent extract definition. PSB_ENTITY_SET and PSB_ENTITY contain the entity groupings tied to an extract, while PSB_POSITIONS and PSB_DEFAULTS (with PSB_DEFAULT_ACCOUNT_DISTRS, PSB_DEFAULT_ASSIGNMENTS, PSB_ALLOCRULE_PERCENTS) hold positional and default-rule configuration. PSB_PAY_ELEMENTS, PSB_ACCOUNT_POSITION_SETS and PSB_ACCOUNT_POSITION_SET_LINES, PSB_ATTRIBUTE_VALUES and PSB_ATTRIBUTE_VALUES_I, PSB_BUDGET_POSITIONS, PSB_BUDGET_WORKFLOW_RULES, PSB_COST_DISTRIBUTIONS_I, PSB_ELEMENT_POS_SET_GROUPS, and PSB_EMPLOYEES / PSB_EMPLOYEES_I complete the dependency graph that must be cleared in the correct order.

Usage Notes

PSB_PURGE_DATA_EXTRACT_PVT is not referenced by any other documented package (referenced by 0 other packages) and is invoked through the concurrent-program wrapper PURGE_DATA_EXTRACT_CP or from within forms and internal PSB code. It should never be called directly from customer extensions. In 12.1.1 and 12.2.2 the package relies on cursor-based collection rather than a single DELETE CASCADE, so NO_DATA_FOUND handling in the retrieval loops is essential to tolerate partially populated extracts.