Results for “trigger_attribute_id”

16 results




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

Overview

ASO_DEPENDENCY_MAPPINGS is an Order Capture (ASO) reference table that stores dependency mappings used by the Defaulting Triggers framework. Defaulting Triggers are the configuration mechanism through which Oracle EBS populates or derives attribute values on order capture entities — order headers, order lines, pricing attributes, and related extension attributes. The table records which trigger attribute, when evaluated, drives the defaulting or enablement of a dependent attribute, and it identifies the database object on which that mapping operates.

The object resides in the ASO schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. In 12.2.2 the documented physical schema exposes 17 columns. Its primary key is ASO_DEPENDENCY_MAPPINGS_PK, defined on DEPENDENCY_ID. A second unique index, ASO_DEPENDENCY_MAPPINGS__U1, is defined on (DEPENDENCY_ID, ZD_EDITION_NAME), reflecting the presence of an editioning column used by the 12.2 online patching (adop) architecture. Under the supplied heuristic Data Vault classification, the table is characterized as standalone — that is, it carries no resolved foreign-key dependency on a parent hub, so a modeling exercise would treat it as an independent reference or configuration satellite rather than as a link between entities.

Key Information Stored

The primary surrogate key is DEPENDENCY_ID, which uniquely identifies each dependency mapping row and forms the basis of the primary key constraint. The unique index on (DEPENDENCY_ID, ZD_EDITION_NAME) performs the same identification role in the editioned 12.2 environment.

  • TRIGGER_ATTRIBUTE_ID — the attribute that acts as the trigger or source of the dependency evaluation.
  • DEPENDENT_ATTRIBUTE_ID — the attribute whose value or enablement status is affected when the trigger fires.
  • ENABLED_FLAG — indicates whether the dependency mapping is currently active.
  • DATABASE_OBJECT_NAME — the database object (entity or view) to which the mapping applies.
  • APPLICATION_ID — the owning application identifier for the mapping.
  • SEED_TAG — flags seeded Oracle-provided mappings versus customer-defined ones.
  • ZD_EDITION_NAME — the editioning column supporting online patching in 12.2.

The table also carries the standard EBS audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID. These identify when the row was created and last changed, and which concurrent program or request performed the change.

Common Use Cases and Queries

This table is primarily interrogated during troubleshooting of defaulting behavior in Order Management — for example, when an attribute on an order line fails to default, or when an unwanted value is populated. A typical diagnostic query resolves the trigger and dependent attributes for a given object:

  • SELECT dependency_id, trigger_attribute_id, dependent_attribute_id, database_object_name, enabled_flag, application_id, seed_tag FROM aso.aso_dependency_mappings WHERE database_object_name = :object_name AND enabled_flag = 'Y';
  • Audit-oriented queries filter on the audit columns to determine when a custom mapping was introduced: ... WHERE last_updated_by = :user_id ORDER BY last_update_date DESC;
  • Reporting on configuration inventory distinguishes seeded from custom setup via SEED_TAG.

Because the heuristic classification is standalone, joins to other ASO objects are normally made through the attribute identifiers (TRIGGER_ATTRIBUTE_ID and DEPENDENT_ATTRIBUTE_ID) rather than through declared foreign keys.

Related Objects

  • ASO_DEPENDENCY_MAPPINGS_PK — the primary key constraint on DEPENDENCY_ID.
  • ASO_DEPENDENCY_MAPPINGS__U1 — the unique index on (DEPENDENCY_ID, ZD_EDITION_NAME).
  • Attribute definition tables in the ASO schema referenced by TRIGGER_ATTRIBUTE_ID and DEPENDENT_ATTRIBUTE_ID for resolving attribute names.
  • Defaulting Trigger configuration tables that share the DEPENDENCY_ID identifier space and define the associated trigger objects.
  • FND_APPLICATION and FND_CONCURRENT_REQUESTS, referenced by APPLICATION_ID and REQUEST_ID respectively, for ownership and change-provenance reporting.

No foreign-key relationships are documented for this object in the ETRM metadata; the relationship data records it as standalone, so the referenced tables above are used in practice for attribute and application lookup rather than through enforced constraints.