Search Results delete_config_instance

Overview

The APPS.FND_OAM_DSCFG_INSTANCES_PKG package body is a server-side PL/SQL utility that manages configuration-instance records used by Oracle E-Business Suite's OAM (Oracle Applications Manager) diagnostic and support tooling. Its primary responsibility is to maintain the in-memory and persisted state of a "configuration instance," which represents an imported and compiled snapshot of an EBS configuration as captured by the DSCFG (Diagnostics Configuration) framework. The package encapsulates the metadata surrounding that snapshot — identifiers, type, source database name, clone key, policy set, and statistics such as last-imported, last-compiled timestamps, and corresponding durations.

The package is registered under API classification OTHER in the ETRM metadata and is not part of a public integration interface; it is an internal supporting package. Its header identifies it as a non-shipped (noship) component belonging to the OAM diagnostics subsystem. The body file AFOAMDSCINSTB.pls (version 120.1) defines a single package-level record cache, b_config_instance_info, that holds the currently selected configuration instance in session state, allowing lightweight accessors to retrieve cached values rather than re-querying the underlying tables.

Key Procedures and Functions

The 18 documented procedures and functions fall into four functional groups.

• State inspection accessors: IS_INITIALIZED, GET_CURRENT_ID, GET_CURRENT_TYPE, GET_CURRENT_SOURCE_DBNAME, GET_CURRENT_CLONE_KEY, and GET_CURRENT_POLICYSET_ID return attributes of the cached configuration instance. Each getter raises NO_DATA_FOUND when the cache has not been initialized, as illustrated in the source excerpt.
• Import and compile statistics: SET_LAST_IMPORTED, GET_LAST_IMPORTED, SET_IMPORT_DURATION, GET_IMPORT_DURATION, SET_LAST_COMPILED, GET_LAST_COMPILED, and SET_COMPILE_DURATION, GET_COMPILE_DURATION pair setters with getters to record and retrieve timing metrics for the import and compile phases of a configuration instance lifecycle.
• Existence and creation: CONFIG_INSTANCE_EXISTS tests whether a configuration instance is already registered, and ADD_CONFIG_INSTANCE inserts a new instance record.
• Selection and removal: SET_CURRENT_CONFIG_INSTANCE loads the session cache with a chosen instance, and DELETE_CONFIG_INSTANCE removes an instance and its associated state. The user's search term, delete_config_instance, maps directly to this removal routine.

Tables Accessed

The package operates against the following objects (referenced through APPS synonyms):

• FND_OAM_DSCFG_INSTANCES — the base table storing configuration-instance metadata such as target DB name, type, source DB name, and policy set.
• FND_OAM_DSCFG_INSTANCES_S — the corresponding sequence used to generate primary key values during inserts performed by ADD_CONFIG_INSTANCE.
• FND_OAM_DSCFG_OBJECTS — child records describing the individual configuration objects captured within an instance; consulted for existence checks and cascade logic during deletion.
• FND_OAM_DSCRAM_RUNS_B — run-history records for the configuration RAM/diagnostic process, linked to import and compile statistics.
• DBMS_SQL and PLITBLM — Oracle-supplied packages used for dynamic SQL execution and PL/SQL table utilities respectively.

Usage Notes

Because the package maintains a session-level cache, it is intended to be invoked within a single session or concurrent-program runtime that selects a configuration instance once and then repeatedly queries its attributes. Typical callers are OAM Diagnostics configuration forms, the configuration import/compile concurrent programs, and internal OAM dashboards that drive the DSCFG lifecycle. Since the package is documented as "referenced by 5 other packages," direct custom invocation is uncommon; developers integrating with the configuration-instance database are advised to call the owning OAM packages rather than this internal layer. When DELETE_CONFIG_INSTANCE is called, callers should ensure no active jobs reference the selected instance and that the session cache is reset or re-initialized afterward to avoid stale state.