Results for “entry_id”

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

Overview

AMS_UPGRADE_ENTRIES is a table owned by the AMS schema within the Oracle E-Business Suite Marketing (AMS) product family. It is documented in the ETRM reference for release 12.2.2 and remains a valid object in both the 12.1.1 and 12.2.2 footprints. The name and structure indicate that the table serves as a staging or control repository recording discrete entries processed during marketing module upgrade routines — that is, during the transition from earlier release levels to the target 12.1.1 or 12.2.2 application code. Rather than holding transactional marketing data such as campaign members, offers, or collateral, it captures the set of records that an upgrade driver has identified, transformed, or reconciled.

From a modeling perspective, the ETRM metadata classifies the object heuristically as standalone under Data Vault conventions. This is a suggestion only: with a single documented column and no foreign key dependencies, the table has no natural hub, link, or satellite relationships. It behaves as a self-contained work or log table, not as a conformed dimension or fact.

Key Information Stored

The documented physical schema for 12.2.2 is minimal and precise:

• ENTRY_ID — the only documented column, described as part of the primary key. It is the surrogate identifier that uniquely tags each upgrade entry row.
• AMS_UPGRADE_ENTRIES_PK (ENTRY_ID) — the primary key constraint, enforcing uniqueness on ENTRY_ID.
• AMS_UPGRADE_ENTRIES_N1 (ENTRY_ID) — a unique index on the same column, documented as a business-key candidate. Because it mirrors the primary key, it functions primarily as an access path for lookups by entry rather than as a distinct business identifier.

No additional columns — such as status flags, source identifiers, error text, or timestamps — are documented in the ETRM metadata for this object. Where the table is used in practice, any such attributes would be undocumented extensions rather than guaranteed interface elements. Consultants should treat the absence of documentation as a caution: it is the presence of rows keyed by ENTRY_ID that carries meaning, not the column list, which is limited to the surrogate key.

Common Use Cases and Queries

Typical usage centers on verifying upgrade state, counting processed entries, and confirming that a row exists for a specific identifier supplied by an upgrade log or concurrent program.

• Counting total staged entries: SELECT COUNT(*) FROM ams.ams_upgrade_entries;
• Checking a specific entry: SELECT entry_id FROM ams.ams_upgrade_entries WHERE entry_id = :entry_id;
• Confirming uniqueness of the documented key: SELECT entry_id, COUNT(*) FROM ams.ams_upgrade_entries GROUP BY entry_id HAVING COUNT(*) > 1;
• Validating index health prior to re-running an upgrade step by checking that AMS_UPGRADE_ENTRIES_PK and AMS_UPGRADE_ENTRIES_N1 are VALID in DBA_INDEXES and DBA_CONSTRAINTS.

Because only one column is documented, these queries are inherently limited to existence and count checks. Reporting use cases should avoid projecting undocumented columns into custom extracts.

Related Objects

The ETRM metadata records no foreign key relationships, consistent with its standalone classification. Any relationships are therefore functional rather than declarative. The objects most likely to reference or depend on AMS_UPGRADE_ENTRIES in an AMS upgrade context are:

• AMS_UPGRADE_ENTRIES_PK and AMS_UPGRADE_ENTRIES_N1 — the constraints and indexes defined directly on ENTRY_ID.
• AMS schema upgrade driver and concurrent programs that populate the table during release transitions.
• DBA_CONSTRAINTS, DBA_INDEXES, DBA_TAB_COLUMNS, and DBA_TABLES — data dictionary views used to confirm the documented single-column structure.
• AMS module transactional tables (for example campaign and offer tables) that upgrade scripts reconcile against, using ENTRY_ID as the tracking handle rather than a joined key.

Consultants should not assume join paths that the metadata does not document; any linkage to AMS transactional objects should be validated against the specific upgrade script in use.