Search Results edr_amerule_input_var




Overview
Explore in AI Chat

Overview

The EDR_AMERULE_INPUT_VAR table is a component of the EDR (E-Records) product module in Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores the input variable definitions consumed by Oracle Approvals Management (AME) rules processed within the E-Records framework. AME rules evaluate transaction attributes through named input variables; this table persists the binding between a given AME transaction type, a named input variable, and the rule that consumes it, along with the value assigned or resolved for that variable. The object is owned by the EDR schema and is documented as VALID in the ETRM data dictionary.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. In modeling terms, this suggests the table operates as an independent reference or configuration structure rather than participating in a classic hub-link-satellite chain — it holds AME rule input variable configuration with no documented parent dependency relationships. Designers implementing a Data Vault-style model over EDR data may therefore treat it as a standalone reference entity keyed by its own business composite.

Key Information Stored

The table contains twelve documented columns. The three-column primary key, defined by the unique index EDR_AMERULE_INPUT_VAR_P, is the business-key candidate for this object: the combination of AME_TRANS_NAME, INPUT_NAME, and RULE_ID uniquely identifies each row. There is no separate single-column surrogate key documented, so this composite functions as the effective row identifier.

  • AME_TRANS_NAME — the AME transaction type name defining the approval context in which the rule executes; first component of the primary key.
  • INPUT_NAME — the name of the input variable being supplied to the rule; second component of the primary key.
  • RULE_ID — the identifier of the AME rule that consumes the input variable; third component of the primary key.
  • RULE_NAME — the descriptive name of the associated rule, stored redundantly for reporting convenience.
  • RULE_CONFIG_ID — a reference to the rule configuration under which the input variable is defined.
  • AME_TRANS_ID — the numeric identifier corresponding to the AME transaction type, complementing AME_TRANS_NAME.
  • INPUT_VALUE — the value bound to the named input variable for the rule evaluation context.
  • CREATED_BY, CREATION_DATE — standard audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent modification, its timestamp, and the login session responsible.

Common Use Cases and Queries

Typical usage centers on approval workflow diagnostics: determining which input variables a specific AME rule expects, and what values were resolved at runtime. A common diagnostic query retrieves all variables for a given rule:

  • SELECT input_name, input_value, ame_trans_name FROM edr.edr_amerule_input_var WHERE rule_id = :rule_id;

Configuration auditing often filters by transaction type to compare rules across approval contexts:

  • SELECT rule_id, rule_name, input_name FROM edr.edr_amerule_input_var WHERE ame_trans_name = :trans_name ORDER BY rule_id, input_name;

Because the audit columns are maintained by EBS conventions, change-tracking reports can isolate recently modified variable bindings using LAST_UPDATE_DATE, and RULE_CONFIG_ID can be joined to rule configuration metadata to reconstruct the configuration lineage of a given approval rule. Reporting on INPUT_NAME distributions supports impact analysis when a shared input variable is renamed or retired.

Related Objects

The ETRM metadata classifies this object as standalone, so no foreign-key parents or children are documented. The most significant related objects are therefore conceptual peers within the AME rule configuration and runtime evaluation footprint in the EDR schema. These include the AME rule definition and rule configuration entities referenced by RULE_ID and RULE_CONFIG_ID, the AME transaction type definition referenced by AME_TRANS_ID and AME_TRANS_NAME, and the broader EDR E-Records rule evaluation structures that consume resolved input variables during transaction processing. Joins are performed on the documented key columns: RULE_ID joins rule metadata, RULE_CONFIG_ID joins rule configuration, and AME_TRANS_ID or AME_TRANS_NAME joins transaction type definitions. Any query joining external AME dictionary tables should be validated against the target release, as AME internal table names are not guaranteed across 12.1.1 and 12.2.2.