Results for “formula_entry_value”

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

Overview

The AMS_ACT_METRIC_FORM_ENT table is a Marketing (AMS) module data object within the Oracle E-Business Suite, holding the individual entries that compose an execution formula used for metric calculation. Each row represents one executable step or operand within a formula, defining the order in which entries are applied, the type of entry, its value, and the operator that connects it. The table therefore forms the granular backbone of the AMS formula engine, allowing a single formula definition to be broken into a sequenced set of operations. The table resides in the AMS schema and is present in both EBS 12.1.1 and 12.2.2, where the documented physical schema contains fourteen columns.

Under a heuristic Data Vault classification mined from the foreign-key structure, this object leans toward a satellite. In modeling terms, that suggests AMS_ACT_METRIC_FORM_ENT behaves as a descriptive, attribute-bearing component attached to a parent driving key (the formula), rather than as a standalone hub or an associative link between two hubs. Modelers should treat FORMULA_ID as the principal parent reference and the entry records as context rows beneath it.

Key Information Stored

The surrogate primary key is FORMULA_ENTRY_ID, enforced by the constraint AMS_ACT_METRIC_FORM_ENT_PK1. This column uniquely identifies a single formula entry and is the documented primary key; the metadata does not document any separate unique business-key index, so no alternate unique key should be assumed.

The most significant columns and their roles include:

• FORMULA_ENTRY_ID — Surrogate primary key; unique identifier for each executable entry.
• FORMULA_ID — Foreign key to AMS_ACT_METRIC_FORMULAS; ties the entry to its owning formula definition.
• ORDER_NUMBER — Sequencing value that establishes the execution order of entries within the formula.
• FORMULA_ENTRY_TYPE — Classifies the entry (for example, an operand, metric, or operator step).
• FORMULA_ENTRY_VALUE — The literal or referenced value used when the entry executes.
• FORMULA_ENTRY_OPERATOR — The operator applied to combine the entry with preceding results.
• METRIC_COLUMN_VALUE — Associates the entry with a specific metric column value.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS; supports multi-org/security partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/ADF framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing change and creation history.

Common Use Cases and Queries

Typical usage centers on reconstructing and validating formula logic, auditing which entries belong to a formula, and reporting formula composition for metric definitions. A recurring pattern retrieves all entries for a formula in execution order:

• SELECT formula_entry_id, order_number, formula_entry_type, formula_entry_value, formula_entry_operator, metric_column_value FROM ams.ams_act_metric_form_ent WHERE formula_id = :formula_id ORDER BY order_number;
• Join to the parent formula to report formula names alongside their entries: ... FROM ams_act_metric_form_ent e, ams_act_metric_formulas f WHERE e.formula_id = f.formula_id.
• Security-filtered extraction joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS for multi-org reporting.
• Count/aggregation queries to detect formulas with unexpected numbers of entries or missing operators.

Related Objects

The table participates in a small, well-defined relationship set:

• AMS_ACT_METRIC_FORMULAS — Parent table referenced by FORMULA_ID; primary dependency.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security grouping.
• AMS_ACT_METRIC_FORM_ENT_PK1 — Primary key constraint on FORMULA_ENTRY_ID.
• AMS metric and formula definition APIs/views in the Marketing module that resolve formula results by reading these entries in ORDER_NUMBER sequence.

Because the documented metadata lists only these foreign keys, further relationships should be confirmed against the ETRM data model before being assumed.