Results for “get_condition_description”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AME_UTILITY_PKG is the shared utility package for the Oracle Approvals Management (AME) module in Oracle E-Business Suite 12.1.1 and 12.2.2. AME provides the rules engine that determines approval routing, approver lists, and approval actions for transactions originating in iProcurement, Purchasing, Payables, Human Resources, and other EBS products. Rather than duplicating logic across these integration points, AME_UTILITY_PKG centralizes the low-level helper routines that resolve descriptive text, validate SQL fragments, manage transaction-scoped savepoints, and translate surrogate identifiers into meaningful business values.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer. Classification in ETRM is OTHER, reflecting its role as an internal infrastructure utility rather than a public business API. Its header carries the identifier $Header: ameutility.pkh 120.4 2006/01/04, and the package is referenced by 41 other packages in the EBS codebase, underscoring its central position within the AME framework.

Key Procedures and Functions

The package exposes functions that resolve descriptions and metadata for AME configuration objects. GET_ATTRIBUTE_CATEGORY returns the category name associated with a given attribute identifier, which is the routine most directly relevant to the search term get_attribute_category. GET_ACTION_DESCRIPTION and GET_CONDITION_DESCRIPTION return human-readable descriptions for action and condition records, with GET_ACTION_DESCRIPTION accepting an effective date and GET_CONDITION_DESCRIPTION supporting a truncation flag.

• VALIDATE_QUERY — validates a SQL query string, optionally against an expected column count and object name; the header explicitly warns it must be called from the middle tier via select ame_utility_pkg.validate_query() from dual to prevent execution of embedded DDL.
• IS_APPROVER_VALID_IN_ACTION — determines whether an approver type is permitted for a given action.
• GET_ACTION_TYPES — returns the action types applicable to a specified attribute.
• GET_VALUE_SET_QUERY — derives the underlying value set query for a value set identifier via an OUT parameter.
• GET_RULE_LAST_UPDATE_DATE, GET_RULE_LAST_UPDATED_BY, GET_RULE_LAST_UPDATE_ACTION, GET_RULE_END_DATE, GET_RULE_ID — resolve rule metadata and identity within a usage context.
• IS_RULE_UPDATABLE, IS_VALID_ATTRIBUTE, GET_CONDITION_ID, GET_ITEM_CLASS_ID, CHECK_SEEDDB — validate rule editability, attribute validity, condition and item class identity, and database seeding state.
• SET_AME_SAVEPOINT and ROLLBACK_TO_AME_SAVEPOINT — establish and roll back a transaction savepoint for atomic AME operations.
• PURGE_LOG — removes entries from the AME exceptions log by transaction type and identifier.

Tables Accessed

The package reads and writes through APPS synonyms across the core AME configuration and runtime tables. Description and metadata lookups draw on AME_ATTRIBUTES, AME_ATTRIBUTE_USAGES, AME_ACTIONS, AME_ACTION_TYPES, AME_ACTION_USAGES, AME_CONDITIONS, AME_CONDITIONS_S, AME_CONDITION_USAGES, AME_APPROVER_TYPES, AME_APPROVER_TYPES_S, AME_ITEM_CLASSES, AME_ITEM_CLASS_USAGES, and AME_MANDATORY_ATTRIBUTES. Rule-level operations target AME_RULES and AME_RULES_USAGES. PURGE_LOG interacts with AME_EXCEPTIONS_LOG, the diagnostic repository for AME processing errors.

Usage Notes

AME_UTILITY_PKG is invoked primarily by other AME packages and by the AME setup forms, where description and category resolution populate list of values and display fields. Concurrent programs that process approval workflows call it for savepoint management and log purging. Custom code may call GET_ATTRIBUTE_CATEGORY to map an attribute ID to its category, but VALIDATE_QUERY must only be invoked from the middle tier as documented, since improper use permits DDL execution under the caller's privileges.