Results for “ame_condition_keys_s”

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

Overview

AME_CONDITION_PKG is a core package body in the Oracle Approvals Management Engine (AME) schema, APPS. It encapsulates the business logic used to define, validate, and retrieve approval rule conditions within Oracle E-Business Suite 12.1.1 and 12.2.2. In AME, a condition represents a single testable expression — for example, an attribute such as "invoice amount" compared against a value — that governs whether a given approval rule fires. This package provides the programmatic interface through which the AME rule engine, Oracle Forms-based setup screens, and integration points read and manipulate condition definitions, their attributes, and their keys.

The package functions as a foundational dependency for higher-level AME components. As documented, APPS.AME_CONDITION_PKG references AME_ATTRIBUTE_PKG, AME_RULE_PKG, and AME_UTIL, and is referenced by two other database objects, confirming its position as a shared, low-level service layer within the AME rule-processing stack.

Key Procedures and Functions

The package exposes forty-one documented procedures and functions. These are predominantly getter and validation routines, grouped as follows:

• Attribute accessors — GETATTRIBUTEID, GETATTRIBUTENAME, and GETATTRIBUTETYPE return the identifier, display name, and data type for the attribute associated with a condition. ISSTRINGATTRIBUTETYPE tests whether an attribute is string-typed, which governs how comparisons are rendered and stored.
• Condition structure accessors — GETCONDITIONTYPE returns the condition category; GETTYPE returns the overall type classification; GETDESCRIPTION returns the descriptive text; and GETSTARTDATE, GETVERSIONSTARTDATE, and GETVERSIONSTARTDATE-related routines expose effective-dating information used by the AME versioning model.
• Condition key management — GETCONDITIONKEY, CONDITIONKEYEXISTS, and GETNEXTCONDITIONKEY handle the unique key assigned to each condition. The key is the persistent, human-readable identifier referenced by AME_CONDITION_KEYS_S and is the object implied by the user search term "ame_condition_keys_s."
• Parameter accessors — GETPARAMETERONE, GETPARAMETERTWO, and GETPARAMETERTHREE retrieve the operand values associated with a condition's comparison expression (typically the value being tested against the attribute).
• Bound and usage accessors — GETINCLUDELOWERLIMIT and GETINCLUDEUPPERLIMIT indicate whether range boundaries are inclusive. ISCONDITIONUSAGE, ISINUSEBYOTHERAPPS, and ISINUSE determine whether a condition is referenced by any rule or application, which governs deletion eligibility.

Consistent with ETRM metadata, no parameter lists are documented for these routines.

Tables Accessed

• AME_CONDITIONS and AME_CONDITIONS_S — the primary store and its shadow/translation table for condition definitions; the package reads and maintains condition rows here.
• AME_CONDITION_KEYS_S — holds the condition key definitions surfaced by the key-management routines; central to the user's search.
• AME_ATTRIBUTES and AME_ATTRIBUTE_USAGES — supply attribute metadata and record where attributes are consumed.
• AME_CONDITION_USAGES, AME_ITEM_CLASS_USAGES, AME_RULE_USAGES — usage-tracking tables consulted by ISINUSE, ISCONDITIONUSAGE, and ISINUSEBYOTHERAPPS to establish referential dependencies.
• AME_RULES and AME_CALLING_APPS — link conditions to rules and to registered calling applications.
• AME_STRING_VALUES — stores string-valued attribute operands.
• PER_ALL_PEOPLE_F, WF_ROLES, DUAL, PLITBLM, V$DATABASE, V$INSTANCE — supporting objects for person/role resolution, dual-row selects, bulk PL/SQL collections, and instance identification.

Usage Notes

AME_CONDITION_PKG is not invoked directly by end users. It is called by AME's own rule engine, by the Oracle Forms setup interface used to configure approval rules, and by integration or extension code that programmatically creates and validates conditions. The ISINUSE family is typically invoked before deletion to prevent removal of conditions referenced by active rules. Because the package body references V$DATABASE and V$INSTANCE, some routines may behave differently across environments, and DBAs should note the public and SYS-level dependencies (DBMS_STANDARD, STANDARD) when recompiling. Customizations should treat this package as a read-mostly service layer and rely on the documented accessors rather than direct DML against AME_CONDITIONS.