Results for “risk_code”

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

Overview

The AMS_DM_PARTY_PROFILE_STG table is a staging object within the AMS (Marketing) product schema of Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It serves as a container for profile-specific details associated with a party, holding rows that correspond to entries in the AMS_DM_DRV_STG staging table. The object is populated and consumed by the Mining Collection Pack, a component of Oracle Marketing's data mining and customer intelligence infrastructure, and is explicitly documented as a staging table rather than a master or transactional entity.

Because AMS_DM_PARTY_PROFILE_STG is a landing area for profile attributes extracted or derived during a mining run, its contents are typically transient. Rows are inserted by collection or extraction processes, read by downstream transformation logic, and then purged or truncated between runs. The table is owner-qualified as AMS.AMS_DM_PARTY_PROFILE_STG and is governed by the primary key constraint AMS_DM_PARTY_PROFILE_STG_PK on PARTY_ID.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as standalone. In Data Vault terms this suggests it is best treated as a satellite-style staging structure keyed on the party business key, rather than as a hub or link, because it carries descriptive profile attributes tied to a single party identifier without documented foreign-key relationships to other hubs or links.

Key Information Stored

The table contains 12 documented columns. The central identifier is PARTY_ID, which serves both as the primary key (AMS_DM_PARTY_PROFILE_STG_PK) and as the unique business-key candidate exposed through the unique index AMS_DM_PARTY_PROFILE_STG_U1. In EBS terms, PARTY_ID corresponds to the HZ_PARTIES.PARTY_ID surrogate key for a person or organization.

The remaining columns capture credit, collections, and receivables-related profile flags and values that drive customer treatment decisions:

• CREDIT_CHECK_FLAG – indicates whether credit checking is enforced for the party.
• CREDIT_HOLD_FLAG – signals that the party is currently under a credit hold.
• CREDIT_RATING – the assigned credit rating value for the party.
• RISK_CODE – a risk classification code associated with the customer.
• TOLERANCE – the payment or credit tolerance threshold permitted.
• DISCOUNT_TERMS_FLAG – whether discount terms apply.
• DUNNING_LETTERS_FLAG – whether dunning (collection) letters are sent.
• INTEREST_CHARGES_FLAG – whether late interest charges are applied.
• SEND_STATEMENTS_FLAG – whether statements are dispatched to the party.
• INTEREST_PERIOD_DAYS – the interest calculation period in days.
• PAYMENT_GRACE_DAYS – the grace period permitted before collection action.

Common Use Cases and Queries

The principal use case is supporting the Mining Collection Pack's extraction and scoring workflows. Analysts and developers use the table to inspect which profile attributes were staged for a given set of parties before those attributes are loaded into the mining data model. A typical inspection query joins the staging table to its driving staging parent:

• Reconciling staged rows against AMS_DM_DRV_STG by PARTY_ID to validate collection completeness.
• Filtering parties under credit hold or with a specific credit rating for targeted marketing suppression.
• Reporting on dunning, interest, and grace-period settings for risk segmentation.
• Troubleshooting mining load failures by confirming that expected profile columns were populated.

A representative pattern is: SELECT p.PARTY_ID, p.CREDIT_RATING, p.RISK_CODE, p.CREDIT_HOLD_FLAG FROM AMS.AMS_DM_PARTY_PROFILE_STG p WHERE p.CREDIT_HOLD_FLAG = 'Y';. Because the object is a staging table, queries should be scoped to the current mining run and should not be relied upon for persistent reporting.

Related Objects

• AMS_DM_DRV_STG – the parent staging table whose rows this table details; join on PARTY_ID.
• AMS_DM_PARTY_PROFILE_STG_PK / _U1 – the primary key and unique index enforcing PARTY_ID uniqueness.
• HZ_PARTIES – the EBS party master referenced by PARTY_ID.
• HZ_CUSTOMER_PROFILES – the persistent customer profile store from which staged values may be derived.
• AR / Collections profile tables – downstream consumers of credit, dunning, and statement flags.