Search Results process_certification

Overview

AMW_PROCESS_CERT_SCOPE_PVT is a private (PVT) PL/SQL package body in the APPS schema that supports Oracle E-Business Suite's Enterprise Transaction and Risk Management (ETRM) module. Its principal business function is the construction and population of certification process scope hierarchies used by the Application Monitoring and Warning (AMW) framework. ETRM relies on certification scopes to define which business processes, subsidiaries, lines of business (LOBs), and organizations fall within the boundary of a given audit or certification exercise. This package translates parent-child process relationships held in the application hierarchy into concrete rows in the execution scope table, thereby determining exactly what a certification run will cover.

The package is classified as PVT, meaning it is an internal implementation package not intended for direct customer invocation. Its logic is consumed by other certification processing components rather than exposed as a public API.

Key Procedures and Functions

The ETRM metadata documents two procedures for this package:

• INSERT_AUDIT_UNITS — Populates audit unit scope records, driving the set of audit units that participate in a certification run. Based on the package's source structure, this procedure is understood to build scope rows by iterating over the process hierarchy and inserting corresponding entries into the execution scope table.
• INSERT_SPECIFIC_AUDIT_UNITS — A variant that inserts a targeted subset of audit units rather than the full hierarchy, allowing callers to restrict a certification scope to explicitly identified units.

The source excerpt additionally reveals a private helper, Insert_Process, which is a recursive procedure. It accepts parameters including level identifier, parent/top process identifiers, subsidiary and LOB value-set and code pairs, organization identifier, and certification identifier. It walks the AMW_CURR_APP_HIERARCHY_ORG_V view, recursing through child processes and inserting rows into AMW_EXECUTION_SCOPE with an entity type of 'PROCESS_CERTIFICATION' and a scope status of 'C' (changed). This recursion is the mechanism through which the full parent-child process tree is flattened into scope records.

Tables Accessed

• AMW_EXECUTION_SCOPE — The primary target table. The package inserts certification scope rows here, capturing the execution scope identifier, entity type, entity (certification) identifier, level, subsidiary and LOB value-set/code columns, organization, and the process hierarchy identifiers (PROCESS_ID, TOP_PROCESS_ID, PARENT_PROCESS_ID), together with standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).
• AMW_EXECUTION_SCOPE_S — The sequence used to generate EXECUTION_SCOPE_ID values for each inserted row.
• DUAL — Referenced in the package metadata, typically for sequence evaluation or FND_GLOBAL-based value retrieval.

Note that the source also queries AMW_CURR_APP_HIERARCHY_ORG_V, a hierarchy view over applications, processes, and organizations, which supplies the process tree that is traversed.

Usage Notes

Because this package is classified PVT and is referenced by no other documented packages, it is invoked internally by the ETRM certification engine and AMW processing flows rather than by customer-facing forms or concurrent programs directly. The metadata indicates zero external references, reinforcing that callers reach this logic through higher-level ETRM certification APIs and the standard certification submission workflow.

When troubleshooting the user search term "lob_vs," note that LOB_VS and LOB_CODE are explicit columns propagated through the package's insert logic. They originate from the caller's LOB parameter values and are carried unchanged into each AMW_EXECUTION_SCOPE row, so the LOB value set/value recorded on a certification scope row directly reflects the LOB context passed at scope construction time. Any customization that extends certification scope should preserve this pass-through behavior to keep downstream scope queries consistent.