Search Results az_delete




Overview
Explore in AI Chat

Overview

The APPS.AZ_DELETE package is a utility package within the Oracle E-Business Suite (EBS) environment, owned by the APPS schema. In the context of EBS 12.1.1 and 12.2.2, this package is classified under the Oracle Application Object Library (AZ) module, which is predominantly associated with the Applications DBA (AD) and Application Object Library (AOL) utilities. Its primary business function is to facilitate the deletion of specific data sets or source records within the EBS database. The package is categorized as "OTHER" in the ETRM (E-Business Suite Technical Reference Manual) metadata, indicating it is not a standard public API but rather an internal utility script.

Its status is marked as VALID, confirming its integrity and successful compilation in the database. A critical architectural note is that AZ_DELETE is a standalone package with no external dependencies on other custom or standard EBS packages, nor is it referenced by any other packages. This isolation suggests it is a top-level entry point intended to be invoked directly by system administrators or through specific concurrent programs for maintenance tasks.

Key Procedures and Functions

According to the documented metadata, the AZ_DELETE package contains two primary procedures: DELETE_ALL and DELETE_SOURCE. While the exact parameter lists are not exposed in the provided ETRM excerpt, their naming conventions provide insight into their operational scope.

  • DELETE_ALL: This procedure is designed to perform a bulk removal of records. In the context of the AZ module, this likely involves clearing temporary staging tables or removing all rows associated with a specific session or batch process. It is typically used as a "cleanup" routine to reset the state of the system before or after a major data migration or deletion job.
  • DELETE_SOURCE: This procedure appears to target specific data sources rather than a full wipe. Its purpose is likely to remove data based on a defined source identifier or selection criteria. This suggests a more granular approach to data management, allowing administrators to purge data originating from a specific external system or a particular validation set without affecting the entire table.

Both procedures operate within the PL/SQL environment of the APPS schema, leveraging the privileges associated with that schema to perform data manipulation language (DML) operations.

Tables Accessed

The ETRM documentation identifies a single table referenced by this package: PLITBLM. This table is accessed via an APPS synonym. PLITBLM is a standard Oracle Database internal table, often associated with the DBMS_SPACE_ADMIN or similar low-level utilities used for space management and PL/SQL internal metadata. In the context of AZ_DELETE, accessing PLITBLM implies that the deletion logic interacts with the database's underlying storage structures or that the package is used to clean up auxiliary data structures related to the AZ module's internal processing. Because it is a system-level table, any invocation of AZ_DELETE carries a higher risk profile, as incorrect usage could theoretically impact database integrity or space management metadata.

Usage Notes

AZ_DELETE is not typically invoked through standard EBS forms. Given its classification and function, it is most commonly executed via one of the following methods:

  • Concurrent Programs: It is likely registered as a concurrent program in the System Administrator responsibility. Users with the appropriate privileges can submit a concurrent request to execute DELETE_ALL or DELETE_SOURCE to purge data in the background.
  • SQL*Plus or SQL Developer: Database administrators often call these procedures directly from the command line for ad-hoc maintenance tasks. This is usually done during patching cycles or when troubleshooting specific data corruption issues in the AZ module.
  • Custom Code: While the package is not referenced by standard EBS packages, developers writing custom PL/SQL scripts for EBS maintenance might call AZ_DELETE.DELETE_SOURCE to clean up specific staging records before running a custom data load.

Because the package is a direct utility and not an API with complex validation logic, it should be used with caution. Always ensure that a valid backup exists before executing DELETE_ALL, as it performs an irreversible bulk deletion of data.