Results for “ams_iba_pl_parameters_vl”

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

Overview

The AMS_IBA_PL_PARAMETERS_VL view is a multi-language (VL) reporting view owned by the APPS schema within the Oracle E-Business Suite AMS – Marketing product family. Its documented role, per Oracle's ETRM reference for 12.1.1 and 12.2.2, is to "list all parameters." It exposes the parameter definitions used by the AMS Internet Business Application (IBA) component for Predictive Learning, making the parameter catalogue available for translation-aware queries, concurrent programs, and BI Publisher reporting without requiring callers to join the base and translation tables manually.

The view is a standard EBS "_VL" construct: it joins the base (or "_B") table, which holds the language-independent attributes, to the translation (or "_TL") table, which holds the language-dependent NAME and DESCRIPTION. Because it resolves the NAME column through the translation table, the view's behaviour depends on the session environment, and locale-specific naming is returned automatically to the reporting layer.

Underlying Base Objects

The documented DDL defines the view over two synonyms that resolve to the underlying AMS tables:

• AMS_IBA_PL_PARAMETERS_B (SYNONYM) – the base table containing language-independent parameter rows, referenced through the alias B.
• AMS_IBA_PL_PARAMETERS_TL (SYNONYM) – the translation table containing NAME and DESCRIPTION, referenced through the alias T.

The join condition is B.PARAMETER_ID = T.PARAMETER_ID, constrained by T.LANGUAGE = USERENV('LANG'). This means the view returns exactly one translated row per parameter for the session's current language, and the effective data set is bounded by the language setting of the querying session. Tables exposed as synonyms in the ETRM listing are typically owned by the APPS schema but may be deployed from the AMS schema, so downstream queries should be written against the view rather than directly against the base tables.

Key Columns

• ROW_ID – the base table ROWID, included to support update/correction logic; it is not a stable primary key for reporting joins.
• PARAMETER_ID – the unique identifier of the parameter and the join key between the base and translation tables.
• PARAMETER_REF_CODE – the reference code that uniquely identifies a parameter within the parameter framework; often the practical business key for lookups.
• EXECUTION_ORDER – the sequence in which parameters are executed or applied. This is the column most relevant to the search term "execution_order," and it is the documented field used to order parameter processing.
• SITE_ID and SITE_REF_CODE – identify the site to which the parameter belongs, allowing multi-site parameter configurations to coexist.
• OBJECT_VERSION_NUMBER – used for optimistic locking in EBS APIs; relevant when writing back through supported interfaces.
• SECURITY_GROUP_ID and LAST_UPDATE_LOGIN – standard EBS multi-org and audit context columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – standard WHO-column audit trail inherited from the base table.
• NAME and DESCRIPTION – the translated labels, sourced from AMS_IBA_PL_PARAMETERS_TL for the session language.

Common Use Cases and Queries

Because it provides translated names alongside the execution sequence, this view is commonly used to display and validate parameter ordering for AMS IBA Predictive Learning, and to compare execution order across parameter reference codes.

To list parameters in processing order:

• SELECT parameter_ref_code, name, execution_order FROM apps.ams_iba_pl_parameters_vl ORDER BY execution_order, parameter_ref_code;

To inspect parameters for a specific site:

• SELECT site_id, site_ref_code, parameter_ref_code, name, description, execution_order FROM apps.ams_iba_pl_parameters_vl WHERE site_id = :site_id ORDER BY execution_order;

To locate duplicate execution orders that may affect processing:

• SELECT execution_order, COUNT(*) FROM apps.ams_iba_pl_parameters_vl GROUP BY execution_order HAVING COUNT(*) > 1;

Because the view's translated columns are language-filtered, always set the session language (or rely on the application session context) before running reports against it.