Search Results maximum_credit_currency_code

Overview

HZ_WSRVC_ORG_ACCOUNT_V is an internal Oracle E-Business Suite view owned by the APPS schema and classified under the Receivables (AR) product family. Its documented description is "Internal view for Organization Account," which indicates that it is not intended as a general-purpose end-user reporting object but rather as a supporting data access layer consumed by Oracle's service, self-service, and Web Services (WSRVC) components. In EBS 12.1.1 and 12.2.2, the HZ_ prefix denotes membership in the Trading Community Architecture (TCA) model, and the WSRVC naming convention signals that the view was constructed to serve web service and UI integration calls involving organization (business-to-business) customer accounts.

The view consolidates account-level attributes from the customer account record with profile-level and party-level attributes, exposing them under a single, denormalized structure. This design lets calling programs retrieve organization account details without writing complex multi-table joins against the base TCA entities.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, HZ_WSRVC_ORG_ACCOUNT_V is defined over four referenced base objects, all accessed through APPS synonyms:

• HZ_CUST_ACCOUNTS — the primary source of customer account records, supplying identifiers, account numbers, and the Attribute and Global Attribute descriptive flexfield columns.
• HZ_CUSTOMER_PROFILES — provides account-level profile attributes, including credit and collections settings.
• HZ_ORGANIZATION_PROFILES — supplies organization-specific profile data such as organization name and business classification.
• HZ_PARTIES — the master party entity, supplying party identifiers, party numbers, and party-level naming information.

The view text excerpt confirms that HZ_CUST_ACCOUNTS columns are aliased with a CUST_ prefix (for example, CUST.CUST_ACCOUNT_ID is exposed as CUST_CUST_ACCOUNT_ID), indicating the account columns are projected directly rather than renamed to business-friendly labels. This is consistent with an internal view whose column naming follows a programmatic convention.

Key Columns

The documented projection centers on HZ_CUST_ACCOUNTS and includes the following categories:

• Identification — CUST_CUST_ACCOUNT_ID and CUST_ACCOUNT_NUMBER identify the customer account.
• Audit — CUST_LAST_UPDATE_DATE, CUST_LAST_UPDATED_BY, CUST_CREATION_DATE, CUST_CREATED_BY, and CUST_LAST_UPDATE_LOGIN carry standard EBS audit tracking.
• Descriptive flexfields — CUST_ATTRIBUTE_CATEGORY and CUST_ATTRIBUTE1 through CUST_ATTRIBUTE20 expose the account-level DFF segments.
• Global flexfields — CUST_GLOBAL_ATTRIBUTE_CATEGORY and CUST_GLOBAL_ATTRIBUTE1 through CUST_GLOBAL_ATTRIBUTE15 expose the global descriptive flexfield segments.
• Credit attributes — because the view draws on HZ_CUSTOMER_PROFILES, it surfaces credit-related profile columns. Users searching for maximum_credit_currency_code will find this attribute among the profile-derived columns, since that column is defined on HZ_CUSTOMER_PROFILES and represents the currency in which a customer's maximum credit limit is expressed.

Common Use Cases and Queries

Because the view is internal, it is most commonly referenced by Oracle's own service and integration code rather than by custom reports. Typical scenarios include retrieving consolidated organization account data for web service responses, validating account credit configuration during order or invoice processing, and driving self-service account maintenance pages.

A representative query retrieving the maximum credit currency for organization accounts is:

SELECT cust_account_number, maximum_credit_currency_code, credit_limit
FROM apps.hz_wsrvc_org_account_v
WHERE cust_account_number = :p_account_number;

When the exact column label is uncertain, DBAs can confirm exposure using:

SELECT column_name
FROM all_tab_columns
WHERE table_name = 'HZ_WSRVC_ORG_ACCOUNT_V'
AND column_name LIKE '%CREDIT%';

For long-term custom development, Oracle recommends querying the underlying base tables directly, since internal views such as HZ_WSRVC_ORG_ACCOUNT_V may change without notice across patches and point releases in both 12.1.1 and 12.2.2.