Search Results insert_specific_audit_units




Overview
Explore in AI Chat

Overview

AMW_PROCESS_CERT_SCOPE_PVT is a private PL/SQL package in the APPS schema that supports the Oracle Enterprise Asset Management (eAM) module within Oracle E-Business Suite 12.1.1 and 12.2.2. The package is classified as a PVT (private) API, meaning it is not intended as a public integration interface; it is invoked internally by other eAM components to manage the scope of process certification, specifically the audit units that participate in a certification or audit execution cycle.

In the eAM certification model, an execution scope defines the set of assets, audit units, or organizational entities included in a given certification or quality audit run. AMW_PROCESS_CERT_SCOPE_PVT encapsulates the logic that resolves and persists these audit units, isolating the caller from the underlying data model of the AMW_EXECUTION_SCOPE tables. Its dependency on FND_API confirms that it observes Oracle Application Object Library conventions — most notably standard error handling, message stacking, and the return-status pattern (success, warning, error) used across EBS public and private APIs.

Key Procedures and Functions

The ETRM metadata documents two procedures in this package:

  • INSERT_AUDIT_UNITS — Inserts the audit units associated with the certification scope into the execution scope tables. This procedure is used when a scope is populated generically, deriving the set of qualifying audit units according to the certification definition and writing the resulting rows for the execution.
  • INSERT_SPECIFIC_AUDIT_UNITS — Inserts a specific or explicitly identified set of audit units rather than deriving them from the broad certification criteria. This supports scenarios where the user or calling process selects particular audit units to include in the scope.

Consistent with the FND_API dependency, both procedures are expected to follow the standard EBS API pattern of accepting an initialization flag and returning an outcome status, though the exact parameter lists are not documented in the available metadata and should not be assumed.

Tables Accessed

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

  • AMW_EXECUTION_SCOPE — The primary table holding execution scope records for certification and audit processing. INSERT_AUDIT_UNITS and INSERT_SPECIFIC_AUDIT_UNITS write audit unit scope rows into this table.
  • AMW_EXECUTION_SCOPE_S — The companion sequence or secondary table associated with AMW_EXECUTION_SCOPE, used to generate or supply primary key values when new scope rows are created.
  • DUAL — The standard Oracle single-row dummy table, typically used for lightweight operations such as sequence value retrieval, date or value checks, or conditional expression evaluation.

All access is mediated through the APPS schema, which owns the synonyms and the package itself.

Usage Notes

Because this is a private package (PVT classification), it is not exposed for direct customer or partner invocation. In practice it is called by higher-level eAM certification processing logic — for example, the certification workflow that establishes an execution scope before assets are evaluated. Oracle Forms and concurrent programs within the eAM responsibility do not call this package directly; they invoke public APIs or internal program units that in turn delegate scope construction to AMW_PROCESS_CERT_SCOPE_PVT.

The metadata records zero dependent packages that reference it, indicating it sits at a leaf in the call hierarchy relative to other stored program units, though it may still be invoked from forms or concurrent program libraries not captured as package dependencies. Customizations should not bind to this package directly; any requirement to manipulate certification scope should be implemented through supported eAM public APIs, with AMW_EXECUTION_SCOPE treated as a protected data model. As with all APPS-owned private APIs, the implementation may change between 12.1.1 and 12.2.2 patch levels without notice as Oracle refines the eAM code line.