Results for “failure_score”

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

Overview

HZ_CREDIT_RATINGS is a Receivables (AR) transaction-grade table in the Oracle E-Business Suite 12.1.1 / 12.2.2 data model that stores credit ratings assigned to parties. It is owned by the AR schema and resides in the Trading Community Architecture (TCA) family of HZ_ tables, which means its rows describe the creditworthiness of a party (customer, prospect, supplier, or organization) rather than financial transactions themselves. Each row captures a rating record for a given party, including the rating value, the rating organization, the date the rating was assigned, and a substantial set of derivative credit analytics such as credit scores, failure scores, Paydex metrics, and adverse-event indicators.

From a dimensional modeling perspective, the metadata's heuristic classification is hub-leaning. This suggests treating HZ_CREDIT_RATINGS as a hub, with CREDIT_RATING_ID as the durable business key, and relying on the surrounding _EXT_B and _EXT_TL tables as satellite tables for descriptive and translated attributes.

Key Information Stored

The remaining columns are the credit-scoring and adverse-event attributes that give the table its analytical value. Key groups include:

• Rating identity and type — RATING, RATING_ORGANIZATION, RATED_AS_OF_DATE, CONTENT_SOURCE_TYPE, and ACTUAL_CONTENT_SOURCE, which establish what rating was assigned, by whom, and as of when.
• Credit scores — CREDIT_SCORE, CREDIT_SCORE_DATE, CREDIT_SCORE_CLASS, CREDIT_SCORE_NATL_PERCENTILE, CREDIT_SCORE_INCD_DEFAULT, and AVG_HIGH_CREDIT/HIGH_CREDIT.
• Failure scores — FAILURE_SCORE, FAILURE_SCORE_DATE, FAILURE_SCORE_CLASS, FAILURE_SCORE_NATL_PERCENTILE, GLOBAL_FAILURE_SCORE, and FAILURE_SCORE_INCD_DEFAULT.
• Paydex metrics — PAYDEX_SCORE, PAYDEX_NORM, PAYDEX_FIRM_DAYS, and PAYDEX_INDUSTRY_DAYS.
• Adverse-event indicators — BANKRUPTCY_IND, LIEN_IND, JUDGEMENT_IND, SUIT_IND, DEBARMENT_IND, CRIMINAL_PROCEEDING_IND, and SECURED_FLNG_IND.
• Standard TCA audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER, and REQUEST_ID.

Common Use Cases and Queries

The table supports customer creditworthiness reporting, risk segmentation, and credit-limit decisioning. A typical query joins to HZ_PARTIES to retrieve the party name alongside the latest score:

• Latest rating per party — Retrieve the current row using a correlated subquery or RANK() on RATED_AS_OF_DATE partitioned by PARTY_ID, filtering where RATED_AS_OF_DATE is maximal.
• Risk segmentation — Group parties by CREDIT_SCORE_CLASS or FAILURE_SCORE_CLASS to produce a distribution of credit quality.
• Adverse-event reporting — Filter on BANKRUPTCY_IND = 'Y' or DEBARMENT_IND = 'Y' to surface high-risk parties for collections review.
• Organization-specific ratings — Restrict by RATING_ORGANIZATION (e.g., D&B) and CONTENT_SOURCE_TYPE to analyze a single provider's assessment.

Related Objects

The following are the most significant related objects based on the documented foreign-key structure:

• HZ_PARTIES — the parent party record; joined via HZ_CREDIT_RATINGS.PARTY_ID = HZ_PARTIES.PARTY_ID and referenced by the foreign key on PARTY_ID.
• HZ_CREDIT_RATINGS_EXT_B — an extension satellite table keyed by CREDIT_RATING_ID, used for additional descriptive attributes.
• HZ_CREDIT_RATINGS_EXT_TL — the translated (language) extension table, also keyed by CREDIT_RATING_ID.
• HZ_IMP_CREDITRTNGS_SG — an interface/staging table that references CREDIT_RATING_ID for bulk import of credit-rating data.
• TCA and AR credit-management APIs (e.g., the HZ_PARTY and customer-account APIs) that read and write credit-rating records as part of party maintenance.