Search Results org_process

Overview

AMW_PROCESS_NAMES_PKG is a PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema whose package body implements the data manipulation layer for the Oracle Internal Controls Manager / Application Management Workspace (AMW) process definition and naming entities. In Oracle EBS 12.1.1 and 12.2.2 this package belongs to the broader AMW (Application Management Workspace / Enterprise Risk and Compliance Management) module family, which supports the definition, categorization, approval, and certification of business processes and their associated risks, controls, and organizational scope. The package provides the canonical DML API for the AMW_PROCESS table and its translation table, AMW_PROCESS_NAMES_TL, exposing insert, update, delete, lock, and translation-maintenance entry points. The package body header revision (120.1) indicates it is a stable, shipping Oracle-owned object, and the ETRM classification registers it as an OTHER API rather than a public, supported customer-facing interface, meaning it is intended primarily for internal use by AMW forms, concurrent programs, and dependent AMW packages.

Key Procedures and Functions

The documented package exposes six procedures. INSERT_ROW creates a new process revision record in AMW_PROCESS; its extensive parameter set covers process identity (PROCESS_REV_ID, PROCESS_ID, PROCESS_CODE, REVISION_NUMBER), lifecycle dates (START_DATE, APPROVAL_DATE, APPROVAL_END_DATE, END_DATE, DELETION_DATE), classification and categorization attributes, approval and certification statuses, ownership identifiers (PROCESS_OWNER_ID, FINANCE_OWNER_ID, APPLICATION_OWNER_ID), rollup counts (RISK_COUNT, CONTROL_COUNT, ORG_COUNT), the standard DFF attribute columns, WHO audit columns, and OBJECT_VERSION_NUMBER for optimistic locking. LOCK_ROW obtains a row-level lock for a process revision to serialize concurrent modification, typically called before UPDATE_ROW or DELETE_ROW. UPDATE_ROW modifies an existing process revision, applying the same attribute surface as INSERT_ROW along with the object version check. DELETE_ROW removes the target process revision row. ADD_LANGUAGE inserts or maintains the translated display name and description for a process in AMW_PROCESS_NAMES_TL, keyed by language. LOAD_SEED_DATA populates seed or reference content required by the AMW process framework, supporting installation and upgrade scripts.

Tables Accessed

The package operates against three documented tables through APPS synonyms. AMW_PROCESS is the primary base table holding process revision records and is written by INSERT_ROW, UPDATE_ROW, and DELETE_ROW and read by LOCK_ROW. AMW_PROCESS_NAMES_TL is the translation table storing language-specific display names and descriptions, populated by ADD_LANGUAGE and referenced during multilingual rendering of process names. FND_LANGUAGES is the Oracle Application Object Library language definition table, consulted to validate or enumerate installed languages when translation rows are created or seeded. The cursor declared in INSERT_ROW (selecting ROWID from AMW_PROCESS by PROCESS_REV_ID) confirms that the package resolves the surrogate ROWID for a process revision as part of its insert contract, returning it through the X_ROWID output parameter used by downstream forms and APIs.

Usage Notes

AMW_PROCESS_NAMES_PKG is not registered as a public API and is referenced by no other documented packages in the ETRM inventory, indicating that its callers are Oracle-internal AMW user interface components, concurrent programs, and installation or upgrade drivers rather than customer extensions. In practice it is invoked from AMW process-definition forms and related OAF pages when users create, revise, approve, certify, or retire a business process, and from seed-data loaders during patch application. Custom code should avoid direct invocation because it bypasses higher-level validation and workflow logic and because no downward compatibility is guaranteed across releases; supported integration is instead achieved through the corresponding AMW public APIs or the AMW forms themselves.