Results for “iby_pa_rstypes_v”

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

Overview

IBY_PA_RSTYPES_V is a database view owned by the APPS schema within the Oracle Payments (IBY) product family. It exposes the set of enabled risk score types used by Oracle Payments risk scoring and scoring-model functionality, particularly in the context of payee and payment risk assessment performed through the IBY_MAPPINGS configuration framework. The view is a lightweight, read-only presentation layer that translates the generic code/meaning pairs stored in Oracle Application Object Library (FND) lookups into a validated list of score type values that carry business meaning for internal payment risk processing.

The name itself is instructive: "PA" refers to the payee-related risk context, "RSTYPES" refers to risk score types, and the "_V" suffix confirms this is a view rather than a base table. Because it is defined entirely over existing lookups and mappings, it contains no persistent storage of its own and always reflects the current transactional state of its underlying objects.

Underlying Base Objects

The documented view text references two base objects, both surfaced in the APPS schema as synonyms:

• FND_LOOKUP_VALUES — the Oracle EBS lookup repository, filtered on LOOKUP_TYPE = 'IBY_RISK_SCORE_TYPE' and ENABLED_FLAG = 'Y', restricted to the current session language via USERENV('LANG').
• IBY_MAPPINGS — the Payments mappings table, used to constrain valid lookup codes to those actually configured for use in the system through MAPPING_TYPE = LOOKUP_TYPE and MAPPING_CODE = LOOKUP_CODE.

The join is an equijoin on lookup type, mapping type, lookup code, and mapping code, with an additional predicate excluding rows where PAYEEID is populated (PAYEEID IS NULL). This ensures the view returns only global/system-level risk score type definitions rather than payee-specific overrides. The view is therefore dependent on both the lookup configuration and the Payments mapping configuration being kept in sync.

Key Columns

Although the documentation lists three columns, each carries significant meaning:

• SCORE_TYPE — the lookup code from FND_LOOKUP_VALUES, qualified by the IBY_RISK_SCORE_TYPE lookup type. Documented allowed values are limited to 'L', 'LM', 'M', 'MH', and 'H', representing a low-to-high risk score band (Low, Low-Medium, Medium, Medium-High, High).
• MEANING — the translated, user-facing description of the score type, resolved in the session's language.
• SEQ — the sequence number from the lookup definition, allowing presentation in the intended risk ordering rather than alphabetical order. The view's ORDER BY SEQ ensures deterministic ordering of the returned rows.

Because the view uses SELECT DISTINCT, duplicates arising from multiple matching mapping rows are collapsed.

Common Use Cases and Queries

The view is typically used to populate a List of Values, validation list, or risk-band picker within Payments setup and risk-model configuration screens, and to support reporting on which score bands are active. A common query to list the enabled risk score types in order is:

• SELECT score_type, meaning, seq FROM apps.iby_pa_rstypes_v ORDER BY seq;

To verify which score type corresponds to a specific risk band, a filtered query is useful:

• SELECT meaning FROM apps.iby_pa_rstypes_v WHERE score_type = 'MH';

For troubleshooting, developers frequently compare the view output against the underlying lookup and mapping rows to identify configuration gaps, for example where a lookup code exists but no corresponding mapping has been defined, causing a risk band to disappear from the view. This diagnostic pattern is common when a score type expected in application screens is unexpectedly absent. The view should always be queried as the APPS user, or from a responsibility with the appropriate grants, since it is not a public synonym by default.