Search Results ame_calling_apps




Overview
Explore in AI Chat

Overview

The AME_CALLING_APPS table is an Oracle E-Business Suite repository object owned by the HR schema and associated with the PER – Human Resources product family. Its name places it within the Oracle Approvals Management Engine (AME) framework, whose core responsibility is to evaluate approval rules, generate approver lists, and route approval transactions across EBS application modules. AME_CALLING_APPS serves as a registration point for the calling applications and transaction types that participate in the approvals infrastructure, allowing AME to identify which applications invoke the approval engine, which transaction types they submit, and how the relevant line items should be retrieved and secured.

The table is documented with 15 columns in the ETRM 12.2.2 physical schema; the documentation is valid but the descriptive text remains marked "To be Updated." Heuristic Data Vault classification, mined from the foreign-key structure, identifies this object as standalone — that is, it is not modeled as a hub, link, or satellite candidate. This classification should be treated as a modeling suggestion rather than an architectural directive. The single documented foreign key points to FND_SECURITY_GROUPS, indicating that AME registration records are scoped by security group.

Key Information Stored

The table's primary key is the composite AME_CALLING_APPS_PK, defined over APPLICATION_ID, START_DATE, END_DATE, and ZD_EDITION_NAME. This date-effective, edition-aware key structure is characteristic of Oracle's date-tracked reference data. A second unique index, AME_CALLING_APPS_N1, spans TRANSACTION_TYPE_ID, START_DATE, END_DATE, and ZD_EDITION_NAME, making it the principal business-key candidate for lookup by transaction type.

  • APPLICATION_ID – identifies the calling EBS application; part of the primary key.
  • FND_APPLICATION_ID – the Oracle Applications (FND) application identifier, aligning the record with the Applications Object Library registry.
  • APPLICATION_NAME – the descriptive, user-facing name of the calling application.
  • TRANSACTION_TYPE_ID – the transaction type submitted to AME; the driver of the AME_CALLING_APPS_N1 unique index.
  • LINE_ITEM_ID_QUERY – an SQL fragment used to resolve line item identifiers for the transaction, enabling AME to locate approvable line items dynamically.
  • SECURITY_GROUP_ID – the security group governing visibility of the record; foreign key to FND_SECURITY_GROUPS.
  • START_DATE / END_DATE – the date-effectivity window for the configuration row.
  • OBJECT_VERSION_NUMBER – optimistic concurrency control, incremented on each update.
  • ZD_EDITION_NAME – editioning identifier supporting Online Patching in EBS 12.2.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS audit columns.

Common Use Cases and Queries

Typical use cases center on troubleshooting approvals and confirming AME registration coverage. Security administrators query registered applications and transaction types when an approval workflow fails to fire, verifying that the calling application was correctly enrolled. The date-effectivity columns support as-of reporting on configuration history; the edition name supports Online Patching diagnostics.

A representative query resolving the application name and effective transaction types for a transaction type identifier follows:

  • SELECT application_id, application_name, transaction_type_id, line_item_id_query FROM hr.ame_calling_apps WHERE transaction_type_id = :p_transaction_type AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);
  • SELECT ca.application_id, ca.application_name, ca.transaction_type_id FROM hr.ame_calling_apps ca, fnd_security_groups fsg WHERE ca.security_group_id = fsg.security_group_id;

Related Objects

  • FND_SECURITY_GROUPS – joined via AME_CALLING_APPS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; the only documented foreign key.
  • FND_APPLICATION – resolves the numeric application identifier to registered EBS application names.
  • AME_TRANSACTIONS – AME transaction instances that reference the calling application and transaction type defined here.
  • AME_RULES / AME_RULE_USAGES – approval rules associated with the registered transaction types.
  • AME_ATTRIBUTES / AME_CONDITIONS – attribute and condition definitions scoped by transaction type.
  • AME_APPLICATION_INSTALLATIONS – installation and configuration metadata for AME-enabled applications.
  • HR_OPERATING_UNITS / FND_RESPONSIBILITY – common join targets for security and responsibility-based reporting.