Search Results iex_score_components_s

Overview

IEX_SCORE_PVT is the private implementation package body behind the Oracle Advanced Collections scoring engine. In Oracle EBS 12.1.1 and 12.2.2, this package encapsulates the server-side logic used to define, maintain, and manipulate scoring models — the rule sets that assign numeric scores to customers, transactions, and delinquencies so that collection agents can prioritize their work. The package follows the standard EBS private API (PVT) pattern: it holds the actual DML and validation routines, while the companion public package IEX_SCORE_PUB exposes the callable interface. The API classification "PVT" confirms that IEX_SCORE_PVT is not intended for direct invocation by external developers. Its metadata status is VALID and, as documented, it is referenced by two other database objects but does not itself reference upward to any dependent object.

Key Procedures and Functions

The package body exposes 22 documented procedures and functions, grouped by the entity they manage.

• Score validation: VALIDATE_SCORE, VALIDATE_SCORE_NAME, VALIDATE_SCORE_ID_NAME — perform existence, uniqueness, and identifier/name consistency checks on score definitions.
• Score component type validation: VALIDATE_SCORE_COMP_TYPE_NAME and VAL_SCORE_COMP_TYPE_ID_NAME — validate component type names and ID/name pairings.
• Score CRUD: CREATE_SCORE, UPDATE_SCORE, DELETE_SCORE — insert, modify, and remove scoring model headers.
• Score component CRUD: CREATE_SCORE_COMP, UPDATE_SCORE_COMP, DELETE_SCORE_COMP — manage the individual components that make up a score.
• Component type CRUD: CREATE_SCORE_COMP_TYPE, UPDATE_SCORE_COMP_TYPE, DELETE_SCORE_COMP_TYPE — maintain the seeded/custom types of components.
• Component detail CRUD: CREATE_SCORE_COMP_DET, UPDATE_SCORE_COMP_DET, DELETE_SCORE_COMP_DET — manage the detailed rules beneath each component.
• COPY_SCORINGENGINE: clones an existing scoring engine configuration, typically to seed a new engine from a template.
• GET_SCORE: retrieves score data for downstream use.
• WRITELOG: diagnostic/debug logging via the FND_LOG and IEX_DEBUG_PUB infrastructure.

Tables Accessed

The package reads and writes a tightly related set of Collections scoring tables through APPS synonyms. Score headers reside in IEX_SCORES, with IEX_SCORES_S as the sequence/primary-key source. Components are held in IEX_SCORE_COMPONENTS (with IEX_SCORE_COMPONENTS_S), component detail rows in IEX_SCORE_COMP_DET (IEX_SCORE_COMP_DET_S), and component types in IEX_SCORE_COMP_TYPES_B, its _TL translation table, and the _VL view. Historical score results are preserved in IEX_SCORE_HISTORIES (IEX_SCORE_HISTORIES_S). Delinquency context comes from IEX_DELINQUENCIES and IEX_DEL_STATUSES, and filtering uses IEX_OBJECT_FILTERS. Dynamic SQL is supported through DBMS_SQL. The reference list also touches AS_UTILITY_PVT, FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, IEX_FILTER_PUB, IEX_UTILITIES, and the various _PKG companion packages.

Usage Notes

Because IEX_SCORE_PVT is the private layer, callers should invoke the corresponding procedures in IEX_SCORE_PUB rather than calling this body directly. In practice it is driven by the Collections scoring setup forms, by concurrent programs that build or copy scoring engines, and by the internal scoring run that writes results into the history tables. The user search term "iex_score_components_s" reflects the sequence object backing IEX_SCORE_COMPONENTS, which this package relies on when creating component rows. Custom extensions should preserve the FND_API error-handling conventions and use WRITELOG for diagnostics.