Search Results ame_condition_pkg




Overview
Explore in AI Chat

Overview

AME_CONDITION_PKG is a core Oracle Approvals Management Engine (AME) package owned by the APPS schema. It provides a programmatic interface for the creation, maintenance, and interrogation of conditions within AME transaction-type rule configurations. Conditions define the qualifying criteria that determine whether a particular approval rule fires; each condition associates an AME attribute (for example, a purchasing category or dollar amount) with an operator, a value, and optional lower and upper limits.

The package encapsulates the underlying AME condition data model, presenting typed getters and validators that other AME components — notably AME_API3 and AME_RULE_PKG — invoke during rule evaluation and administrative setup. Its API classification is recorded as OTHER, reflecting its role as an internal supporting utility rather than a public external-facing integration interface.

Key Procedures and Functions

The package exposes 41 documented procedures and functions. They may be grouped functionally as follows:

  • Attribute accessors: GETATTRIBUTEID, GETATTRIBUTENAME, and GETATTRIBUTETYPE return the identifier, display name, and data type of the AME attribute associated with a condition. ISSTRINGATTRIBUTETYPE tests whether a given attribute is string-based.
  • Condition classification: GETCONDITIONTYPE, GETTYPE, and GETVERSIONSTARTDATE describe the condition's classification and date-effective status.
  • Condition key management: GETCONDITIONKEY, CONDITIONKEYEXISTS, and GETNEXTCONDITIONKEY support lookup and generation of the human-readable condition key used to identify conditions uniquely within a transaction type.
  • Limit handling: GETINCLUDELOWERLIMIT and GETINCLUDEUPPERLIMIT indicate whether boundary values are included in range comparisons, while GETPARAMETERONE, GETPARAMETERTWO, and GETPARAMETERTHREE return the positional parameter values of the condition.
  • Descriptive and date attributes: GETDESCRIPTION and GETSTARTDATE return the condition's description and effective start date.
  • Usage and integrity checks: ISCONDITIONUSAGE, ISINUSE, and ISINUSEBYOTHERAPPS determine whether a condition is referenced by rules or other applications, guarding deletion and modification operations.

Tables Accessed

Through APPS synonyms the package reads and writes the AME condition tables: AME_CONDITIONS and its date-effective counterpart AME_CONDITIONS_S, AME_CONDITION_KEYS_S, and AME_CONDITION_USAGES. Attribute metadata is drawn from AME_ATTRIBUTES and AME_ATTRIBUTE_USAGES, while rule linkage is verified through AME_RULES and AME_RULE_USAGES. Calling-application context is resolved via AME_CALLING_APPS, item classes via AME_ITEM_CLASS_USAGES, and string parameter values via AME_STRING_VALUES. PER_ALL_PEOPLE_F supports people-related attribute resolution, DUAL and PLITBLM serve utility purposes, and V$DATABASE supplies database-level context. These accesses underpin the usage, key-existence, and type-determination logic exposed by the public API.

Usage Notes

AME_CONDITION_PKG is referenced by two other packages — AME_API3 and AME_RULE_PKG — which invoke it during rule definition and runtime evaluation. It also references AME_UTIL and STANDARD (SYS). Administrators typically reach this functionality indirectly through the AME Business Rules setup pages in the Oracle E-Business Suite, particularly the condition definition screens within transaction-type configuration. Custom code requiring direct condition interrogation should prefer the supported AME_API3 entry points, which internally delegate to AME_CONDITION_PKG, ensuring date-effective and usage-validation logic is applied consistently. Direct invocation of the condition package is appropriate only where finer-grained access to condition parameters, limits, or keys is required, and it should always respect the returned usage indicators before attempting deletion or modification. The package is VALID in both 12.1.1 and 12.2.2, and its dependent objects should be recompiled after any patch affecting the AME schema.