Search Results ams_dm_drv_stg_pk

Overview

AMS_DM_DRV_STG is a staging table owned by the AMS (Marketing) schema in Oracle E-Business Suite, with documented validity in both the 12.1.1 and 12.2.2 code lines. The table functions as a container for the list of PARTY_ID values for which analytical data is being collected. It is a working structure consumed by the Oracle Marketing mining collection pack, which drives the extraction of behavioral and transactional data used to populate the data mining and predictive modelling structures within Oracle Marketing. Rather than holding descriptive or transactional content itself, the table serves strictly as a driver list: the target set of parties whose data will be gathered during the mining collection cycle.

Because the documented schema consists of a single column, the object is deliberately narrow. It is populated by the mining collection process to define scope before subsequent collection steps execute against the broader marketing data model. From a Data Vault modelling perspective, the heuristic classification derived from the foreign key structure is standalone. That is, the table exhibits no incoming or outgoing foreign key relationships within the documented model, and it should be treated as an independent staging or driving-list structure rather than a hub, link, or satellite. This classification is a modelling suggestion only; the physical object remains a conventional EBS staging table.

Key Information Stored

The documented physical schema for AMS_DM_DRV_STG contains one column and one primary key constraint:

• PARTY_ID — The sole documented column. It holds the identifier of a party (a person or organization registered in the Trading Community Architecture / HZ party model) for which data collection is required. Each row represents one party in the collection scope.
• AMS_DM_DRV_STG_PK — The primary key constraint defined on PARTY_ID. Because the table owns only this single column, the primary key and the business key coincide structurally.
• AMS_DM_DRV_STG_U1 — A unique index documented on PARTY_ID, providing the business-key candidate. The presence of both a primary key and a unique index on the same column enforces uniqueness of the party list and supports efficient lookups during the collection process.

No surrogate sequence-generated key is documented. The absence of descriptive attributes such as party name, collection status, or timestamps indicates that the table is intended only to enumerate eligible parties; all enrichment occurs downstream in the mining tables populated from this driver list.

Common Use Cases and Queries

The principal use case is population and consumption of the driver list by the Oracle Marketing mining collection pack. Typical operational and reporting scenarios include:

• Scope verification — Confirming which parties are queued for data collection before a mining run.
• Row count auditing — Validating that the number of staged parties matches the expected population delivered by the collection process.
• Duplicate detection — Verifying uniqueness of the driver list, which the AMS_DM_DRV_STG_U1 index enforces.

Representative SQL patterns include:

• SELECT COUNT(*) FROM ams.ams_dm_drv_stg; — returns the size of the current collection scope.
• SELECT party_id FROM ams.ams_dm_drv_stg WHERE party_id = :p_party_id; — tests whether a specific party is included.
• SELECT d.party_id FROM ams.ams_dm_drv_stg d JOIN hz_parties hp ON hp.party_id = d.party_id; — joins the driver list to the TCA party registry to describe the staged population.

Because the table is a transient staging structure, queries should be executed with awareness of the collection cycle; content is expected to be truncated or refreshed between runs.

Related Objects

The documented relationship data classifies AMS_DM_DRV_STG as standalone, with no foreign keys to or from other tables. The significant related objects are therefore those that supply or consume the PARTY_ID values in the context of the marketing mining process:

• HZ_PARTIES — The TCA master party registry; joined on HZ_PARTIES.PARTY_ID = AMS_DM_DRV_STG.PARTY_ID to resolve party details.
• HZ_CUST_ACCOUNTS — Customer accounts associated with the staged parties, joined via PARTY_ID, providing the account-level context used in mining.
• AMS_DM_IMP_STG and other AMS_DM_*_STG tables — Sibling staging structures within the mining collection pack that receive or transform the driver list.
• AMS_LIST_HEADERS / AMS_LIST_ENTRIES — Marketing list objects whose membership frequently overlaps with the collected party population.
• Mining collection pack concurrent programs — The AMS collection executables that read AMS_DM_DRV_STG to determine which parties require data gathering.

Direct database dependencies beyond the primary key and unique index are not documented; integration occurs through the mining collection pack code rather than through declarative constraints.