Search Results truncate_table

Overview

FND_CONC_CLONE is a package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It supports the concurrent manager cloning and cleanup infrastructure by providing low-level utilities for locating the database schema owners of FND and JTF objects and for selectively truncating tables that hold stale or duplicated concurrent processing configuration. The package is classified as "OTHER" in the ETRM documentation, meaning it is not a public API in the conventional sense, but is used internally by the concurrent processing subsystem during cloning, refresh, and reconfiguration operations.

The package header comment identifies a design goal of removing hard-coded schema names such as APPLSYS and JTF (see Bug 3335806). This reflects the multi-schema architecture of EBS releases, where the FND and JTF data may reside in schemas other than the historical defaults.

Key Procedures and Functions

The ETRM metadata documents two procedures for this package: TARGET_CLEAN and SETUP_CLEAN.

• TARGET_CLEAN — Supported functionality for cleaning concurrent processing setup data on a target/refresh environment. It typically removes or rebuilds rows relating to concurrent programs, queues, and manager definitions so that the cloned environment reflects the target configuration rather than the source.
• SETUP_CLEAN — Companion cleanup routine that removes residual setup records (for example queue definitions and related translation rows) so the environment can be re-seeded cleanly.

The excerpt also exposes internal helper routines that are not part of the documented public interface: get_database_user, which populates the package variables OracleUserFND and OracleUserJTF by querying FND_ORACLE_USERID, FND_PRODUCT_INSTALLATIONS, and FND_APPLICATION; and truncate_table, which accepts a schema and table name and issues a dynamic TRUNCATE TABLE. truncate_table declares a TableNotFound exception with PRAGMA EXCEPTION_INIT(TableNotFound, -942) and silently ignores the ORA-00942 error, allowing cleanup to proceed even when a target table is absent.

Tables Accessed

The package reads and writes the following APPS synonyms, based on ETRM documentation.

• FND_APPLICATION, FND_PRODUCT_INSTALLATIONS, FND_ORACLE_USERID — used by get_database_user to resolve the actual database usernames that own FND and JTF objects.
• FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_QUEUES, FND_CONCURRENT_QUEUES_TL, FND_CONCURRENT_QUEUE_SIZE, FND_CONCURRENT_REQUESTS, FND_CONCURRENT_PROCESSES, FND_CP_SERVICES — concurrent processing definition and runtime tables touched during cleanup.
• FND_NODES, FND_CONFLICTS_DOMAIN, FND_PRINTER, FND_PRINTER_TL, FND_PROFILE_OPTIONS — supporting configuration tables affected by target/setup cleanup.

Usage Notes

FND_CONC_CLONE is not referenced by any other package per the ETRM metadata and is invoked directly, typically in the context of cloning or refreshing an EBS environment. Administrators run cleanup by calling TARGET_CLEAN and SETUP_CLEAN, often from SQL*Plus or via a concurrent program wrapper rather than from an EBS form. Because internal routines such as truncate_table perform DDL via EXECUTE IMMEDIATE, callers should treat the package as privileged and restricted to controlled maintenance windows. Custom code should not depend on the private helpers; any direct invocation of the documented procedures should be followed by re-seeding concurrent manager definitions from the appropriate source environment or template.