Search Results ame_calling_apps_pk

Overview

HR.AME_CALLING_APPS is the Oracle E-Business Suite repository that registers every "calling application" — that is, every transaction type that participates in the Approval Management Engine (AME). AME does not approve transactions generically; it must be told which Oracle EBS application and which transaction type within that application are initiating an approval request. HR.AME_CALLING_APPS stores exactly that mapping between an FND application, an AME internal application identifier, and a transaction type key and name. In effect it is the AME transaction-type directory consulted at runtime whenever an approval process is launched.

The table is owned by the HR schema, carries the FND design data reference PER.AME_CALLING_APPS, and is stored in the APPS_TS_TX_DATA tablespace with indexes in APPS_TS_TX_IDX. It is a VALID object in both 12.1.1 and 12.2.2. Heuristic Data Vault classification mined from the foreign-key structure is standalone; the table has only a weak association to FND_SECURITY_GROUPS and therefore is best modeled as a small reference or lookup table rather than a hub, link, or satellite in a dimensional or Data Vault warehouse.

Key Information Stored

The most significant columns fall into three groups: identification, descriptive attributes, and standard audit/date-effectivity columns.

• APPLICATION_ID — the AME internal application identifier that uniquely identifies a transaction type. This column participates in the primary key AME_CALLING_APPS_PK.
• FND_APPLICATION_ID — the FND application identifier of the owning Oracle EBS application (for example, Purchasing or Payables).
• APPLICATION_NAME — the display name of the transaction type (VARCHAR2(240)).
• TRANSACTION_TYPE_ID — the transaction type key (VARCHAR2(50)); it is the leading column of the unique index AME_CALLING_APPS_N1.
• START_DATE / END_DATE — date-effectivity range governing when a registration row is active. Both are components of AME_CALLING_APPS_PK and AME_CALLING_APPS_N1.
• LINE_ITEM_ID_QUERY — documented as "Not used" in current releases; retained for backward compatibility.
• OBJECT_VERSION_NUMBER — optimistic-locking counter incremented on each row update.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• SECURITY_GROUP_ID — documented as "Not used" for this table, though it participates in a foreign-key relationship to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — editioning column present in the 12.2.2 physical schema, supporting Edition-Based Redefinition for online patching.

In 12.2.2 the documented physical schema lists 15 columns, matching the published ETRM metadata with the addition of ZD_EDITION_NAME.

Common Use Cases and Queries

Typical use cases include identifying which applications are AME-enabled, auditing transaction-type registrations after an upgrade or patch, and joining AME configuration tables back to the owning FND application. Because AME resolves transaction types at runtime, this table is also a first-stop diagnostic target when approvals fail to fire for a given document type.

To list all active transaction types for a date window:

SELECT fnd_application_id, application_name, transaction_type_id, application_id FROM hr.ame_calling_apps WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

To find the AME application identifier for a specific transaction type key:

SELECT application_id, fnd_application_id, application_name FROM hr.ame_calling_apps WHERE transaction_type_id = :p_transaction_type_id;

Reporting joins to FND_APPLICATION_VL on FND_APPLICATION_ID resolve the numeric identifier to the application short name and display name, which is the customary pattern for AME setup reports.

Related Objects

• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; the only documented foreign-key relationship.
• AME_CALLING_APPS (APPS synonym) — the APPS-owned synonym over HR.AME_CALLING_APPS, used by application code and customer SQL.
• FND_APPLICATION / FND_APPLICATION_VL — joined on FND_APPLICATION_ID to resolve the owning application name.
• AME_APPLICATIONS — the AME application registry; APPLICATION_ID in AME_CALLING_APPS resolves to the AME application record.
• AME_TRANSACTIONS — runtime transaction rows created against the transaction types registered here.
• AME_RULES / AME_RULE_ASSIGNMENTS — approval rules defined per AME application and therefore scoped to the transaction types listed in this table.
• AME_APPROVAL_GROUPS and AME_ACTION_TYPES — AME configuration objects that reference the same AME application framework.
• HR.AME_CALLING_APPS_N1 and HR.AME_CALLING_APPS_PK — the unique indexes (business-key candidates) that enforce registration uniqueness on TRANSACTION_TYPE_ID and APPLICATION_ID respectively.