Search Results profile_class_id




Overview
Explore in AI Chat

Overview

The view APPS.HZ_PROFILE_AMTS_V is a consolidated reporting object within the Oracle E-Business Suite Receivables (AR) module. It unifies credit limit and profile amount data that is otherwise distributed across multiple credit profile tables in the Trading Community Architecture (TCA) data model. Its principal purpose is to expose transaction credit limits, represented by the TRX_CREDIT_LIMIT column, and overall credit limits alongside a normalized set of profile identifiers, so that consumers can retrieve credit amount information across all profile definition levels through a single query interface.

Because the object is a view (rather than a base table), it does not store data of its own. It is a read-only construct used for reporting, integration, and lookup purposes. In Oracle EBS 12.1.1 and 12.2.2, it is commonly referenced by credit management reporting, custom extensions, and integration interfaces that need to assess credit limits established at various levels of the customer hierarchy.

Underlying Base Objects

Per the documented view text, HZ_PROFILE_AMTS_V is defined as a UNION of four branches, each selecting from a distinct profile amount table. The referenced base objects are:

The operating unit branch filters on CP.ORGANIZATION_ID IS NOT NULL, while the item category branch filters on CP.ITEM_CATEGORY_ID IS NOT NULL. This UNION design allows a single result set to describe credit amounts regardless of which profile dimension the amount was defined against.

Key Columns

The view projects a fixed set of columns that normalize the four source tables. Because each branch originates from a different table, columns that do not apply to a given source are populated with a placeholder value of -1.

Common Use Cases and Queries

Typical scenarios include retrieving the transaction credit limit for a specific profile, aggregating limits by currency, or reconciling limits defined across the profile hierarchy. A representative query returns transaction credit limits by profile type:

  • SELECT profile_type, currency_code, trx_credit_limit FROM hz_profile_amts_v WHERE trx_credit_limit IS NOT NULL;
  • SELECT currency_code, SUM(trx_credit_limit) FROM hz_profile_amts_v GROUP BY currency_code;
  • SELECT * FROM hz_profile_amts_v WHERE profile_type = 'CUSTOMER' AND cust_account_profile_id = :profile_id;

Given the -1 placeholders, filtering on PROFILE_TYPE is advisable to isolate records from the intended source table. All access should be qualified with the APPS schema context.