Results for “query_string”

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

Overview

The AME_APPROVAL_GROUP_MEMBERS table resides in the HR schema and belongs to the PER — Human Resources product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It is a core component of the Oracle Approvals Management (AME) engine, which drives dynamic approver list generation for transactions originating in modules such as Purchasing, Payables, iProcurement, and Human Resources. Where the parent approval group defines which set of approvers should be considered, this table enumerates the individual members of that group and the parameters that govern each member's inclusion in the generated approval chain.

The ETRM metadata classifies this object as standalone using a heuristic Data Vault assessment mined from its foreign key structure. In practical Data Vault modeling terms, this suggests the table behaves more like a standalone dimension or reference structure than a classic hub-and-link pair, since its identity is anchored on a single surrogate key and its foreign keys point outward to independent reference objects rather than forming part of an interconnected business key network. This classification is offered as a modeling suggestion and should be validated against the actual reporting and integration requirements of the implementation.

Key Information Stored

The table contains ten documented columns in the 12.2.2 schema. The most significant are:

• APPROVAL_GROUP_MEMBERS_ID — the surrogate primary key uniquely identifying each member record. It also appears first in the unique index AME_APG_MEMBERS_UK1, paired with ZD_EDITION_NAME, making it the principal business-key candidate for this object.
• APPROVAL_GROUP_ID — foreign-key reference to the parent approval group definition, linking each member back to its owning group.
• PARAMETER_NAME and PARAMETER — together these define the rule parameter (for example, a job, position, supervisor level, or amount threshold) that qualifies the member for inclusion.
• QUERY_STRING — the underlying SQL or dynamic criteria used to resolve the member set at runtime, enabling attribute-based approver selection rather than static assignment.
• ORDER_NUMBER — controls the sequencing of members within the generated approval chain.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org and data-security constraints on the member record.
• ORIG_SYSTEM and ORIG_SYSTEM_ID — the latter is a foreign key to HZ_ORIG_SYSTEMS_B, identifying the source system and the corresponding identifier for externally-sourced members (typically parties or persons).
• ZD_EDITION_NAME — the editioning column introduced with the Online Patching (AD_ZD) architecture in Release 12.2, supporting edition-based redefinition and zero-downtime patching.

Common Use Cases and Queries

Typical usage centers on diagnosing and reporting approval routing. A common pattern joins members to their parent group to inspect how an approval chain is composed:

• Listing all members of a group ordered by sequence: SELECT APPROVAL_GROUP_ID, PARAMETER_NAME, PARAMETER, ORDER_NUMBER FROM AME_APPROVAL_GROUP_MEMBERS WHERE APPROVAL_GROUP_ID = :group_id ORDER BY ORDER_NUMBER;
• Auditing dynamic query definitions: SELECT APPROVAL_GROUP_MEMBERS_ID, QUERY_STRING FROM AME_APPROVAL_GROUP_MEMBERS WHERE QUERY_STRING IS NOT NULL;
• Tracing externally-sourced approvers using ORIG_SYSTEM and ORIG_SYSTEM_ID for reconciliation with TCA records.
• In Release 12.2 environments, querying against the active edition filter using ZD_EDITION_NAME to isolate the current runtime edition.

Reporting use cases include approval matrix documentation, segregation-of-duties reviews, and troubleshooting of unexpectedly routed transactions where the group membership is suspected of being misconfigured.

Related Objects

The most significant related objects include the following:

• FND_SECURITY_GROUPS — joined via AME_APPROVAL_GROUP_MEMBERS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• HZ_ORIG_SYSTEMS_B — joined via AME_APPROVAL_GROUP_MEMBERS.ORIG_SYSTEM_ID = HZ_ORIG_SYSTEMS_B.ORIG_SYSTEM_ID.
• AME_APPROVAL_GROUPS — the parent group definition referenced by APPROVAL_GROUP_ID.
• AME_APPROVAL_GROUP_MEMBERS itself participates in the unique index AME_APG_MEMBERS_UK1 covering APPROVAL_GROUP_MEMBERS_ID and ZD_EDITION_NAME.
• AME rule and transaction-type configuration tables that consume group membership during runtime approver list resolution.

Together these objects form the configuration backbone that the AME engine reads when building approver lists for a business transaction.