Results for “ame_attribute_pkg”

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

Overview

AME_ATTRIBUTE_PKG is a core PL/SQL package in the Oracle E-Business Suite Approvals Management Engine (AME) schema, owned by APPS and classified as a non-public API (API classification: OTHER). Its principal business function is the maintenance and retrieval of AME attribute metadata. Within AME, attributes represent the transaction values — such as requisition amounts, employee grades, or item categories — on which approval rules, conditions, and actions are evaluated. AME_ATTRIBUTE_PKG provides the programmatic interface through which other AME components inspect attribute definitions, resolve attribute identifiers, determine where attributes are used, and validate attribute existence before rules execute. The package sits at the metadata layer of the AME engine, supporting the rule authoring, condition building, and runtime evaluation performed by higher-level packages such as AME_ENGINE, AME_RULE_PKG, and AME_CONDITION_PKG. It is marked VALID and present in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents 75 procedures and functions, reflecting the breadth of attribute metadata management. Among the documented entry points:

• ATTRIBUTEEXISTS / ATTRIBUTEEXISTSFORDIFFIC — Validate whether an attribute definition exists, including checks in the context of a specific item class (DIFIC-based validation).
• GETIDBYNAME / GETNAME — Resolve between an attribute's internal numeric identifier and its user-facing name.
• GETATTRIBUTENAMES — Returns the set of attribute names, typically for display or selection in AME setup interfaces.
• GETTYPE / GETDESCRIPTION / GETSTARTDATE / GETCHILDVERSIONSTARTDATE — Return core attribute definition attributes, including type and version-effective dating information.
• GETUSEREDITABLE — Indicates whether an attribute value may be edited by the user at runtime.
• GETAPPROVALTYPENAMES / GETAPPROVERTYPEID — Relate attributes to approver type metadata used by approval rules.
• GETITEMCLASSID / GETLINEITEM — Expose item-class and line-item context associated with an attribute.
• GETQUERYSTRING — Retrieves the query string used to source an attribute's value.
• GETUSECOUNT / GETSTATICUSAGE — Report where an attribute is referenced, supporting impact analysis before modification or deletion.
• GETATTRIBUTECONDITIONCNT / GETATTRIBUTECONDITIONINUSECNT — Count attribute conditions, including those actively in use.
• CALCULATEUSECOUNT — Computes usage totals across AME metadata.

Tables Accessed

The package reads and writes AME configuration and definition tables through APPS synonyms, including AME_ATTRIBUTES and its translated/child table AME_ATTRIBUTES_S, AME_ATTRIBUTE_USAGES, AME_MANDATORY_ATTRIBUTES, AME_CONDITIONS, AME_CONDITION_USAGES, AME_ACTIONS, AME_ACTION_TYPES, AME_ACTION_USAGES, AME_RULES, AME_RULE_USAGES, AME_ITEM_CLASSES, AME_CALLING_APPS, AME_STRING_VALUES, and DUAL. AME_ATTRIBUTES stores the attribute definitions; the usage tables (AME_ATTRIBUTE_USAGES, AME_CONDITION_USAGES, AME_RULE_USAGES, AME_ACTION_USAGES) are the basis for the usage-count routines; AME_ITEM_CLASSES supports item-class-related validation; and AME_STRING_VALUES supports value lookups and query-string resolution. DUAL supports simple scalar queries.

Usage Notes

AME_ATTRIBUTE_PKG is an internal AME framework package rather than a published, supported external API. It is referenced by ten other AME packages, including AME_ACTION_PKG, AME_ADMIN_PKG, AME_API7, AME_CONDITION_PKG, AME_ENGINE, AME_RULE_PKG, AME_TEST_PKG, AME_TEST_UTILITY_PKG, AME_TRANS_DATA_PURGE, and AME_UTIL. It depends on AME_UTIL and SYS.STANDARD. Typical invocation occurs indirectly through AME setup forms, the AME Business Analyst/administrator responsibilities, rule and condition maintenance flows, and runtime rule evaluation performed by AME_ENGINE. Custom code should avoid calling this package directly; supported integration points are the documented AME public APIs (for example, AME_API7 and related API packages). Customers performing impact analysis or data cleanup should use the usage-count functions with caution and validate changes through the AME administrative interface. Because the package manipulates core AME metadata, modifications through unsupported direct calls risk corrupting rule definitions and should be restricted to Oracle Support guidance or sanctioned extension points.