Search Results is_table

Overview

GMA_PURGE_VALIDATE is an Oracle EBS PL/SQL package owned by the APPS schema that provides validation services for the purge infrastructure used by Oracle Process Manufacturing (OPM) and related applications. Its central role is to confirm that purge definitions stored in the purge master and definition tables are structurally and syntactically sound before a purge process is executed. The package is compiled with AUTHID CURRENT_USER, meaning that name resolution and privilege checking occur under the invoking schema rather than under APPS. This design allows the validation routines to inspect the caller's own USER_TABLES and USER_TABLESPACES views, returning results that reflect the objects visible to the session performing the purge. The package is referenced by two other packages, confirming that it functions as a shared utility layer for purge-related processing rather than as an entry point invoked directly by end users.

Key Procedures and Functions

• CHECKSQL — Verifies that the SQL statement stored in the SY_PURG_DEF purge definition record is valid for the specified purge identifier and purge type. This routine guards against executing malformed or stale SQL during a purge run.
• IS_TABLE — Determines whether a named table exists. The function accepts a purge identifier and a table name and returns a BOOLEAN result. This is the routine associated with the user search term "is_table" and is the most commonly referenced member of the package, since purge definitions frequently target specific tables that must be confirmed present before deletion logic proceeds.
• IS_TABLESPACE — Validates a tablespace name supplied with a purge identifier, returning a BOOLEAN indicating whether the tablespace is recognized. This supports purge operations that depend on tablespace-level storage or reorganization.

All three documented members return or raise results based on the purge context passed in, ensuring that validation is tied to a specific purge master record.

Tables Accessed

• SY_PURG_MST — The purge master table, supplying the purge identifier used as the key for all validation calls.
• SY_PURG_DEF — The purge definition table, holding the SQL text and purge type values that CHECKSQL evaluates.
• USER_TABLES / ALL_TABLES — Data dictionary sources used by IS_TABLE to confirm table existence, consistent with the AUTHID CURRENT_USER compilation setting.
• USER_TABLESPACES — Dictionary view consulted by IS_TABLESPACE.
• FND_APPLICATION and FND_ORACLE_USERID — EBS application and Oracle user registration tables, used to resolve application context and database user information relevant to purge validation.
• DBMS_SQL — The dynamic SQL facility employed by CHECKSQL to parse or validate stored SQL statements without executing them destructively.

Usage Notes

GMA_PURGE_VALIDATE is not normally invoked directly by end users. It is called from purge setup and execution flows and from the two packages that reference it, which perform the surrounding orchestration. Because CHECKSQL and the two IS_ functions rely on the caller's privileges, custom code invoking them should do so from a schema with visibility to the target tables and tablespaces. Administrators diagnosing purge failures can call IS_TABLE or IS_TABLESPACE from a session to confirm whether a missing table or invalid tablespace is the cause of an aborted purge. The package is compatible with both EBS 12.1.1 and 12.2.2; its header indicates it has been stable since release 115.3, and no online patching implications apply to its dictionary lookups. When reviewing purge definitions, verifying SQL validity through CHECKSQL before scheduling a purge avoids runtime errors in downstream purge programs.