Results for “ams_dm_finnum_stg”

28 results




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

Overview

AMS_DM_FINNUM_STG is a staging table owned by the AMS (Marketing) schema in Oracle E-Business Suite. It functions as a container for the financial details of a party — that is, a customer, prospect, or organization — and supplies the financial attribute rows referenced by AMS_DM_DRV_STG. Its role is transitional: data is loaded, validated, and then consumed by the Oracle Marketing mining collection pack, which profiles trading partners and derives business intelligence used by campaign targeting and customer segmentation.

Because the table is a staging artifact, it is not intended as a system of record. Rows are populated during a collection run, reconciled against the driving staging table, and subsequently merged or purged. From a Data Vault modeling perspective, the metadata's heuristic classification places this object as standalone: it carries no foreign key relationships to other mined objects, and its structure — a single business key plus a wide set of descriptive financial measures — is best characterized as a satellite-style descriptor set rather than a hub or a link. This classification is a modeling suggestion only; the physical table remains a flat staging structure keyed on PARTY_ID.

Key Information Stored

The table contains 22 documented columns organized around a single party identifier and a broad set of financial metrics. The surrogate primary key is defined by AMS_DM_FINNUM_STG_PK on PARTY_ID, and a unique index AMS_DM_FINNUM_STG_U1 on the same column establishes PARTY_ID as the business-key candidate for the staging set. The most significant columns include:

Common Use Cases and Queries

The primary use case is populating financial profile attributes during a Marketing mining collection run. Analysts and developers also query the staging table directly for validation and reconciliation — confirming that every party loaded into AMS_DM_DRV_STG has corresponding financial rows before the collection is committed. Typical patterns include:

  • Reconciliation of staged rows against the driving table: SELECT d.party_id FROM ams_dm_drv_stg d, ams_dm_finnum_stg f WHERE d.party_id = f.party_id.
  • Identifying high-risk parties for exclusion from a campaign using HIGH_RISK_FRAUD_FLAG or BANKRUPTCY_FLAG.
  • Segmenting the staged population by DEBT_TO_INCOME_RATIO or NET_WORTH thresholds to build target lists for financial-product campaigns.
  • Data-quality checks on completeness of GROSS_ANNUAL_INCOME and CAPITAL_AMOUNT before the mining pack consumes the data.

Related Objects

The most significant dependencies of AMS_DM_FINNUM_STG are:

  • AMS_DM_DRV_STG — the driving staging table; its rows are enriched by the financial detail held here, joined on PARTY_ID.
  • AMS_DM_FINNUM_STG_PK and AMS_DM_FINNUM_STG_U1 — the primary key constraint and unique index enforcing uniqueness of PARTY_ID.
  • HZ_PARTIES — the Trading Community Architecture entity holding the master party record referenced by PARTY_ID.
  • AMS mining collection programs — the concurrent programs and PL/SQL routines in the Marketing collection pack that read, transform, and consume rows from this table.