Search Results update_score_comp_type

Overview

APPS.IEX_SCORE_PVT is a private (PVT) PL/SQL package belonging to the Oracle Advanced Collections / E-Business Tax scoring infrastructure delivered with Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business function is to perform server-side validation and persistence of scoring engine definitions used by Collections and credit management. A "score" in this context represents an attribute or model specification—built from score components and component types—that drives how customer or transaction risk is evaluated and triggerred within the Collections scoring engine. The package declares internal constants such as G_MIN_SCORE (10) and G_MAX_SCORE (100), reflecting the bounded numeric range within which score values are assessed. The AUTHID CURRENT_USER pragma indicates the package executes under the privileges of the invoking user rather than the package owner, which is significant for the APPS schema conventions in EBS.

Because it is a PVT package, it is not intended as a standalone public API. It underpins the public package IEX_SCORE_PUB and is referenced by two other packages, implying its procedures are consumed internally within the scoring framework rather than called directly by customers. The metadata lists 22 documented procedures and functions.

Key Procedures and Functions

• VALIDATE_SCORE — The primary validation entry point, invoked with a SCORE_REC_TYPE record from IEX_SCORE_PUB. Returns duplicate status, return status, message count, and message data. This is the relevant procedure for the "validate_score" search.
• VALIDATE_SCORE_NAME — Validates a score name, optionally with a score ID, to detect duplicate or invalid names.
• VALIDATE_SCORE_ID_NAME — Validates a score ID and name combination.
• VALIDATE_SCORE_COMP_TYPE_NAME — Validates a score component type name.
• VAL_SCORE_COMP_TYPE_ID_NAME — Validates a component type ID and name pair.
• CREATE_SCORE, UPDATE_SCORE, DELETE_SCORE — Manage score header records and their base tables.
• CREATE_SCORE_COMP, UPDATE_SCORE_COMP, DELETE_SCORE_COMP — Manage score component rows attached to a score.
• CREATE_SCORE_COMP_TYPE, UPDATE_SCORE_COMP_TYPE, DELETE_SCORE_COMP_TYPE — Manage component type definitions across the base and translation tables.
• CREATE_SCORE_COMP_DET, UPDATE_SCORE_COMP_DET, DELETE_SCORE_COMP_DET — Manage component detail records.
• COPY_SCORINGENGINE — Copies a complete scoring engine configuration, including scores and components.
• GET_SCORE — Retrieves a score definition for downstream processing.
• WRITELOG — Writes diagnostic information for troubleshooting.

Tables Accessed

The package reads and writes IEX_SCORES and IEX_SCORES_S (score header and its translation/audit shadow), IEX_SCORE_COMPONENTS and IEX_SCORE_COMPONENTS_S (component assignments), and IEX_SCORE_COMP_DET plus its _S counterpart for component detail. Component type definitions reside in IEX_SCORE_COMP_TYPES_B, IEX_SCORE_COMP_TYPES_B_S, and IEX_SCORE_COMP_TYPES_TL (the translated table). Validation queries reference IEX_DELINQUENCIES and IEX_DEL_STATUSES to confirm the delinquency context, and IEX_OBJECT_FILTERS for filter scope. IEX_SCORE_HISTORIES and its _S table retain score lifecycle history. DBMS_SQL is referenced for dynamic SQL processing.

Usage Notes

IEX_SCORE_PVT is typically invoked indirectly. The Oracle Collections setup forms that maintain scoring engines call the public IEX_SCORE_PUB wrapper, which delegates validation and CRUD operations to this package's procedures. Concurrent programs that seed or copy scoring configurations use COPY_SCORINGENGINE. Custom extensions should call the public API rather than this PVT layer, since signatures and behavior are subject to change and are not guaranteed for external use. When troubleshooting the "validate_score" path, trace the call from the form or program through IEX_SCORE_PUB.VALIDATE_SCORE into IEX_SCORE_PVT.VALIDATE_SCORE, and enable WRITELOG diagnostics to capture the message data returned via X_MSG_DATA.