Search Results fnd_oam_dscram_stats_s

Overview

FND_OAM_DSCRAM_STATS_PKG is an internal Oracle E-Business Suite package body owned by the APPS schema that supports the Applications DBA (AD) Diagnostics and "DSCRAM" (Diagnostics SCRipt and Analysis Manager) infrastructure. Its business purpose is to record and manage per-object execution statistics while diagnostic scripts, health checks, and analysis routines are executed against an EBS environment. Each diagnostics action operates on a set of "source objects" (schemas, tables, concurrent programs, files, and similar artifacts), and the package persists lifecycle information describing when processing of an object began, its pre-execution status, and whether the object was successfully handled. In Oracle EBS 12.1.1 and 12.2.2, the package is a component of Oracle Applications Manager (OAM) and is classified in ETRM as an OTHER API, meaning it is intended for internal framework use rather than as a public, supported extension API. The header comment ($Header: AFOAMDSSTATB.pls 120.5 ...) confirms its place in the FND/OAM code line and signals that its interface may change between releases without notice.

Key Procedures and Functions

ETRM documents nine procedures and functions in this package body. They fall into three logical groups:

• Entry creation: CREATE_ENTRY_FOR_RUN, CREATE_ENTRY, and CREATE_ENTRY_AUTONOMOUSLY. These routines insert a new row into the statistics table, assigning a STAT_ID from the sequence and recording the owning run, the affected source object, and the start time. The private helper INTERNAL_CREATE_ENTRY performs the actual insert shown in the source, returning the generated STAT_ID and a standard FND_API return status (G_RET_STS_SUCCESS or G_RET_STS_UNEXP_ERROR). The AUTONOMOUSLY variant opens its own transaction through an autonomous block so statistics can be committed independently of the caller's unit of work, ensuring diagnostic progress is preserved even if the main transaction is rolled back.
• Entry completion: COMPLETE_ENTRY_FOR_RUN and COMPLETE_ENTRY. These update an existing statistics row with the finishing state and message once processing of the source object has concluded, closing the lifecycle opened at creation time.
• Existence check: HAS_ENTRY is the function matching the user's search term. It allows a caller to determine whether a statistics record already exists for a given run and source object before creating one, preventing duplicate stat rows and enabling idempotent diagnostics processing.

Tables Accessed

The package operates on three documented objects, all accessed through APPS synonyms:

• FND_OAM_DSCRAM_STATS — the primary table. CREATE_ENTRY variants insert rows into it, COMPLETE_ENTRY variants update them, and HAS_ENTRY queries it. Key columns include STAT_ID, RUN_STAT_ID, SOURCE_OBJECT_TYPE, SOURCE_OBJECT_ID, OBJECT_START, PRESTART_OBJECT_STATUS, MESSAGE, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), which are populated from FND_GLOBAL.USER_ID.
• FND_OAM_DSCRAM_STATS_S — the sequence supplying STAT_ID values via NEXTVAL.
• FND_OAM_DSCRAM_RUNS_B — the parent run table, providing the RUN_STAT_ID context under which individual object statistics are grouped; FOR_RUN procedures accept a run identifier as their entry point.
• DUAL — used for lightweight PL/SQL evaluation and sequence access contexts.

Usage Notes

FND_OAM_DSCRAM_STATS_PKG is invoked by the OAM/DSCRAM diagnostics framework rather than by end users. Typical callers include the diagnostics run controller, the script executor that iterates over source objects, and the six other packages recorded by ETRM as dependent references. Callers are expected to: determine applicability via HAS_ENTRY; record the start of processing with a CREATE_ENTRY variant; perform the diagnostic work; and finalise with a COMPLETE_ENTRY variant. Because return values follow the FND_API convention, callers should always inspect x_return_status and log x_return_msg, since the insert handler deliberately leaves error logging to the caller. The autonomous option is appropriate for long-running or multi-transaction diagnostics where statistics must survive rollback. The package is not a supported public API; customisations should treat it as private, and any direct dependency carries upgrade risk between 12.1.1 and 12.2.2.