Search Results ar_cc_credit_usage_type

Overview

APPS.HZ_CREDIT_USAGE_RULES_V is a reportable and queryable view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It exposes the configuration of credit usage rules that govern how credit is consumed across the order-to-cash cycle within the Oracle Receivables and Oracle Credit Management (Advanced Collections) functional areas. Specifically, the view presents rows from the credit usage rules base entity and enriches each row with the decoded, user-facing meaning of the usage type. The user search term "ar_cc_credit_usage_type" corresponds to the Oracle lookups lookup_type that drives this decoding, which is joined within the view definition. The view therefore serves as the canonical read-only interface for reporting on, integrating with, or validating credit usage rule definitions without requiring application-layer lookup resolution.

Underlying Base Objects

The view is defined in the APPS schema and is built over two documented referenced objects:

• HZ_CREDIT_USAGE_RULES — referenced in the view text by the alias CUR; documented as a SYNONYM in the ETRM metadata. This is the driving object and supplies the credit usage rule identifier, usage type code, user code, exclusion and inclusion flags, rule set identifier, and the standard WHO/audit and descriptive flexfield columns.
• AR_LOOKUPS — referenced by the alias AL; documented as a VIEW. This supplies the lookup meaning for the usage type.

The join condition is CUR.USAGE_TYPE = AL.LOOKUP_CODE restricted by AL.LOOKUP_TYPE = 'AR_CC_CREDIT_USAGE_TYPE'. This restriction is what ties the view directly to the searched term: only lookup codes belonging to the AR_CC_CREDIT_USAGE_TYPE lookup type are joined. The view is an inner join, so a credit usage rule whose usage type has no matching lookup value in that lookup type will not be returned. All base columns of HZ_CREDIT_USAGE_RULES are projected, with ROWID carried through as the first selected expression.

Key Columns

• CREDIT_USAGE_RULE_ID — primary identifier of the credit usage rule record.
• USAGE_TYPE — the credit usage type code; joined to AR_LOOKUPS.LOOKUP_CODE for the AR_CC_CREDIT_USAGE_TYPE lookup type.
• MEANING — the decoded, translatable display value of the usage type, sourced from AR_LOOKUPS. This is the principal benefit of querying the view rather than the base object.
• USER_CODE — the user-defined code associated with the rule.
• EXCLUDE_FLAG — indicates whether the usage type is excluded from the rule.
• INCLUDE_ALL_FLAG — indicates whether all usage types are included.
• CREDIT_USAGE_RULE_SET_ID — identifies the rule set to which the rule belongs, enabling grouping of related rules.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program and request context columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield (DFF) context and segment columns.

Common Use Cases and Queries

Typical scenarios include reporting on configured credit usage rules, validating that all usage types map to active lookup values, and extracting rule definitions for integration or migration. A standard query to list rules with their decoded usage type meaning is:

• SELECT credit_usage_rule_id, usage_type, meaning, exclude_flag, include_all_flag, credit_usage_rule_set_id FROM apps.hz_credit_usage_rules_v ORDER BY credit_usage_rule_set_id, meaning;

To isolate rules for a specific rule set:

• SELECT usage_type, meaning, user_code, exclude_flag FROM apps.hz_credit_usage_rules_v WHERE credit_usage_rule_set_id = :p_rule_set_id;

To identify rules whose usage type lacks a valid AR_CC_CREDIT_USAGE_TYPE lookup (rows absent from the view due to the inner join), query HZ_CREDIT_USAGE_RULES directly with a NOT EXISTS against AR_LOOKUPS. Because the view joins to AR_LOOKUPS, reports relying on it return only lookup-validated rows, making it well suited for user-facing listings while the base object supports diagnostic queries.