Results for “program_application_id”

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

Overview

The HZ_CREDIT_USAGE_RULE_SETS_V view is a reporting and integration interface owned by the APPS schema within the Oracle E-Business Suite Receivables (AR) module. It exposes metadata describing credit usage rule sets, the configuration constructs that determine how a customer's credit exposure is calculated and consumed across order, receivables, and collections activities. As a documented, VALID database object in ETRM 12.1.1 and 12.2.2, the view serves as the read-oriented entry point for the credit usage rule set identifier referenced throughout the Trading Community Architecture (HZ) and Receivables credit management schema.

Because it hides the underlying translation architecture and exposes a stable, denormalized column list, the view is the preferred access point for reports, extensions, and third-party integrations that need to resolve a CREDIT_USAGE_RULE_SET_ID to its descriptive name and audit attributes without joining the multi-language base tables directly.

Underlying Base Objects

The view is defined over a single documented base object: HZ_CREDIT_USAGE_RULE_SETS_VL, itself a view. The defining text performs a straightforward projection:

• SELECT "ROW_ID", "CREDIT_USAGE_RULE_SET_ID", ... , "NAME" FROM HZ_CREDIT_USAGE_RULE_SETS_VL

The _VL suffix identifies the underlying object as a translation ("language") view, which typically unions a base table (HZ_CREDIT_USAGE_RULE_SETS_B) holding language-independent columns with a translation table (HZ_CREDIT_USAGE_RULE_SETS_TL) holding the NAME and other translatable attributes. HZ_CREDIT_USAGE_RULE_SETS_V therefore collapses that structure into a single, locale-aware result set without exposing the union logic to the caller. The view carries no additional filter predicates in the documented text, so it effectively mirrors HZ_CREDIT_USAGE_RULE_SETS_VL column-for-column.

Key Columns

The view exposes thirty columns, most of which are standard EBS WHO columns plus a set of descriptive flexfield segments and a single business attribute:

• CREDIT_USAGE_RULE_SET_ID — the primary business key. This surrogate identifier is the column users most commonly search on and is the value joined from credit profile, credit rule, and usage rule configurations.
• ROW_ID — the unique row identifier used by the Oracle Forms/HTML framework for row-level operations.
• NAME — the user-visible, translated name of the rule set, sourced from the _VL translation layer. This is the only business-facing descriptive attribute exposed.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording who created and last modified the definition and when.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program context identifying the process that last touched the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments available for customer-specific extensions.

Common Use Cases and Queries

Typical usage includes validating a rule set identifier during integration load, listing configured rule sets for a setup report, and joining the identifier to credit exposure data. A simple lookup by identifier:

• SELECT credit_usage_rule_set_id, name, last_update_date FROM hz_credit_usage_rule_sets_v WHERE credit_usage_rule_set_id = :p_id;
• SELECT credit_usage_rule_set_id, name FROM hz_credit_usage_rule_sets_v ORDER BY name;

For reporting on configuration drift, querying the audit columns filtered by last_update_date identifies rule sets changed since a given date. Because the view is a thin projection, it is safe for read-only integration use and can be joined to other HZ or AR objects on CREDIT_USAGE_RULE_SET_ID to enrich credit-management extracts.