Results for “profile_class_amount_id”

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

Overview

HZ_CREDIT_USAGES is a Receivables (AR) table that defines the association between a customer's credit limit and the credit usage rule set applied to it. In Oracle EBS 12.1.1 and 12.2.2, credit checking operates at the level of a credit profile amount; the rule set determines which transactions and balances are counted toward usage of that limit. HZ_CREDIT_USAGES is the connective table that binds a specific credit amount definition to a specific usage rule set, so the Credit Management engine knows how to compute exposure for a given customer account, profile class, or credit profile.

The table supports multi-entity credit risk management, where a single customer may have different limits at account, profile, and profile-class levels, each with its own rules for inclusion of open receivables, unapplied cash, pending orders, and disputed items. Physically it resides in the AR schema with 30 columns, a primary key HZ_CREDIT_USAGES_PK on CREDIT_USAGE_ID, and a documented unique index HZ_CREDIT_USAGES_U1 on the same column.

From a Data Vault modeling perspective, the metadata's heuristic classification is link. This is appropriate: the table resolves a many-to-many association among three amount sources and one rule set, making it a natural link table rather than a hub or satellite.

Key Information Stored

Only a subset of the 30 documented columns carries business meaning; the remainder are standard EBS audit and descriptive flexfield columns.

• CREDIT_USAGE_ID — surrogate primary key; also the sole documented unique index (HZ_CREDIT_USAGES_U1), so it is the only business-key candidate identified.
• CREDIT_PROFILE_AMT_ID — foreign key to HZ_CREDIT_PROFILE_AMTS; identifies the credit limit defined at the credit profile level.
• CUST_ACCT_PROFILE_AMT_ID — foreign key to HZ_CUST_PROFILE_AMTS; identifies the credit limit defined for a specific customer account profile.
• PROFILE_CLASS_AMOUNT_ID — foreign key to HZ_CUST_PROF_CLASS_AMTS; identifies the credit limit defined at the profile class level.
• CREDIT_USAGE_RULE_SET_ID — foreign key to HZ_CREDIT_USAGE_RULE_SETS_B; identifies which usage rule set governs credit computation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program context, useful for tracing which process created or changed a row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments for customer-specific extensions.

Common Use Cases and Queries

Typical scenarios include reconciling which rule set applies to a given credit limit, auditing credit check configuration after upgrades, and building reports of rule-set assignments across the customer hierarchy.

• Resolve the rule set name for a credit profile amount by joining to HZ_CREDIT_USAGE_RULE_SETS_B on CREDIT_USAGE_RULE_SET_ID.
• List all usage associations for a customer account limit:

  SELECT cu.credit_usage_id, cu.credit_usage_rule_set_id
FROM hz_credit_usages cu
WHERE cu.cust_acct_profile_amt_id = :amt_id;

• Audit configuration by joining each FK to its parent table and reporting effective limits alongside rule sets.
• Trace concurrent program activity using REQUEST_ID and PROGRAM_ID when investigating unexpected credit behavior.

Related Objects

• HZ_CREDIT_PROFILE_AMTS — joined on CREDIT_PROFILE_AMT_ID.
• HZ_CUST_PROFILE_AMTS — joined on CUST_ACCT_PROFILE_AMT_ID.
• HZ_CUST_PROF_CLASS_AMTS — joined on PROFILE_CLASS_AMOUNT_ID.
• HZ_CREDIT_USAGE_RULE_SETS_B — joined on CREDIT_USAGE_RULE_SET_ID; provides rule definitions.
• HZ_CREDIT_USAGE_RULE_SETS_TL — translations for rule-set names and descriptions.
• Credit Management engine APIs and concurrent programs (Credit Check, Credit Revaluation) that consume these associations at runtime.