Search Results az_commit_rowcount

Overview

AZ_DELETE is a utility package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides the transactional deletion engine used by Oracle's Telecommunications and utility-industry data management components, commonly associated with the AZ product family (Advanced Number/Service Management and related provisioning tables). Its business function is to purge staged, processed, or obsolete request data from large interface tables by request identifier. The package isolates the physical DELETE workload from the calling application so that high-volume cleanup can be executed in controlled batches rather than as a single long-running transaction.

The package is classified as OTHER in the ETRM repository, meaning it is not published as a supported public API. It is internal infrastructure invoked by other AZ components and concurrent programs. Internally, the package distinguishes between a broad delete for an entire request and a narrower delete scoped to a single source value, allowing the caller to avoid one massive DML statement.

Key Procedures and Functions

• DELETE_ALL — Removes every record associated with a given request regardless of the source column value. It determines the distinct set of source values present for the request, then iterates over that set and delegates the actual row removal to DELETE_SOURCE for each source. This design ensures that each source is processed by the same code path and that a failure against one source can be reported with the offending source value. It marks the end of the operation with a commit and performs table statistics gathering to keep the optimizer informed after the bulk purge.
• DELETE_SOURCE — Deletes all records for a single request/source combination. It opens a reference cursor over the target table restricted by request_id and source, then fetches identifiers in bulk and removes them. This is the workhorse routine that DELETE_ALL calls repeatedly; it can also be invoked directly when the caller already knows the specific source to purge.

No additional public functions are documented. The package relies on private variables and types, including a commit batch size derived from the AZ_COMMIT_ROWCOUNT profile option and nested-table collection types used to hold source and ID lists.

Tables Accessed

The ETRM metadata records a single referenced object via APPS synonym: PLITBLM. This is a supporting database object rather than the primary purge target. The package is written to operate dynamically against an arbitrary table name passed in by the caller, using native dynamic SQL to build the SELECT and DELETE statements. Consequently, the effective set of tables touched is determined at runtime by the calling AZ component rather than being fixed in the package source. Because it uses EXECUTE IMMEDIATE with a caller-supplied table name, the package is tightly coupled to the AZ data model and assumes the target table carries at least a request_id column and, where source scoping applies, a source column.

Usage Notes

AZ_DELETE is normally reached indirectly. The user's search term "delete_source" corresponds to the DELETE_SOURCE procedure, which is the most commonly referenced entry point when investigating cleanup behavior. Typical invocation paths include:

• Concurrent programs or request-processing logic that purge staged interface rows after successful validation and transfer.
• Parent AZ packages performing end-of-request housekeeping, which call DELETE_ALL to clear an entire request in one call.
• Custom or diagnostic code that calls DELETE_SOURCE directly when a single source value must be removed.

Administrators investigating performance should note the profile-dependent commit batch size, the session-level cursor sharing setting applied at runtime, and the post-delete statistics gathering, all of which influence throughput and plan stability. Because the package issues its own commits and raises exceptions on failure, callers should not wrap it inside a larger transaction expecting full rollback on error.