Search Results fnd_oam_dscram_stats_pkg




Overview
Explore in AI Chat

Overview

FND_OAM_DSCRAM_STATS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM API taxonomy as OTHER (that is, an internal supporting package rather than a public, documented API). It forms part of the Oracle Application Manager (OAM) "DSCRAM" family of packages, whose collective purpose is to collect, store, and report diagnostic and configuration statistics about an EBS environment. The package name itself indicates its narrow responsibility: managing the lifecycle of individual statistics records generated during a diagnostic data-collection run. Where sibling packages such as FND_OAM_DSCRAM_BUNDLES_PKG or FND_OAM_DSCRAM_TASKS_PKG handle bundles and tasks respectively, FND_OAM_DSCRAM_STATS_PKG handles the measurement rows themselves — creating a run's entry, populating the statistics, recording completion, and answering whether an entry already exists for a given run. In 12.1.1 and 12.2.2 the object reports a status of VALID, and it depends only on SYS.STANDARD together with the APPS synonyms listed below, so it has no EBS application-level prerequisites beyond those tables.

Key Procedures and Functions

The documented package exposes nine procedures and functions, all concerned with the state of statistics rows tied to a collection run:

  • CREATE_ENTRY_FOR_RUN — Creates the statistics entry (header/row set) associated with a specific diagnostic run.
  • CREATE_ENTRY — Performs the core insert of a statistics entry; the run-specific variant above is the contextual wrapper around this logic.
  • CREATE_ENTRY_AUTONOMOUSLY — Creates an entry using an autonomous transaction, allowing the record to be committed independently of the caller's transaction. This is significant for diagnostic collection, where an entry must survive even if the surrounding collection logic subsequently fails or rolls back.
  • COMPLETE_ENTRY_FOR_RUN — Marks the statistics entry belonging to a given run as complete, typically after all measurements for that run have been written.
  • COMPLETE_ENTRY — The underlying operation that finalizes an entry; the run-specific procedure above supplies the run context.
  • HAS_ENTRY — A predicate used to determine whether an entry already exists, supporting idempotent or conditional invocation by the DSCRAM orchestration packages.

No parameter lists are documented in the ETRM metadata and none are asserted here; signature details should be obtained from the package specification in the target environment.

Tables Accessed

Via APPS synonyms, the package accesses FND_OAM_DSCRAM_STATS, FND_OAM_DSCRAM_STATS_S, FND_OAM_DSCRAM_RUNS_B, and DUAL.

  • FND_OAM_DSCRAM_STATS — the primary statistics table where collected measurement data is inserted and updated.
  • FND_OAM_DSCRAM_STATS_S — the sequence used to generate unique statistic identifiers.
  • FND_OAM_DSCRAM_RUNS_B — the base table describing diagnostic runs, used to associate entries with their run and to validate run context.
  • DUAL — used for singleton evaluations, consistent with the HAS_ENTRY predicate and lightweight default lookups.

Usage Notes

This package is not intended for direct customer invocation. It is referenced by six other packages — FND_OAM_DSCRAM_BUNDLES_PKG, FND_OAM_DSCRAM_DIAG_PKG, FND_OAM_DSCRAM_DMLS_PKG, FND_OAM_DSCRAM_PLSQLS_PKG, FND_OAM_DSCRAM_TASKS_PKG, and FND_OAM_DSCRAM_UNITS_PKG — which invoke it as part of the OAM diagnostic statistics collection workflow initiated through the Oracle Application Manager interface or the associated concurrent programs. Custom code should not call these entry points directly, since the entry/complete handshake is coordinated by the DSCRAM orchestration layer. The presence of CREATE_ENTRY_AUTONOMOUSLY confirms that entry creation may be committed independently of the parent collection transaction, so administrators diagnosing partial or orphaned statistics rows should consider that behavior when reviewing FND_OAM_DSCRAM_STATS data.