Results for “parameter_ref_code”

40 results




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

Overview

AMS_IBA_PL_PARAMETERS_B is a base table within the AMS (Marketing) product schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definitions of parameters that are configured on a per-site basis for Oracle Marketing's iBA (Internet Business Application) and personalization infrastructure. Each row represents a single parameter definition, identifying which site the parameter belongs to, its reference code, and the sequence in which it should be executed. The table is a foundational configuration object that governs how parameterized processing behaves at different marketing sites.

The table's status is VALID and it is owned by the AMS schema. Its role is primarily as a definitional master: it holds parameter metadata that is consumed by other configuration and translation tables rather than transactional data. Under the heuristic Data Vault classification mined from its foreign key structure, AMS_IBA_PL_PARAMETERS_B is characterized as hub-leaning. This suggests that in a Data Vault model, the table would most naturally be represented as a hub, since its primary key (PARAMETER_ID) is a stable, unique business identifier referenced by dependent satellites and related tables.

Key Information Stored

The primary key of the table is AMS_IBA_PL_PARAMETERS_B_PK, defined on the PARAMETER_ID column. This surrogate identifier uniquely distinguishes each parameter definition and forms the anchor referenced by downstream tables. The documented unique index AMS_IBA_PL_PARAMETERS_B_U1 covers (PARAMETER_ID, ZD_EDITION_NAME), indicating the presence of editioning support in the 12.2.x architecture and serving as the business-key candidate for the object.

Common Use Cases and Queries

Typical usage centers on retrieving parameter definitions for a given site, resolving execution order, and joining to translation data for multilingual display. A common reporting query joins the base table to its translation table on PARAMETER_ID, and to the sites table on SITE_ID, filtering by SECURITY_GROUP_ID to enforce access control:

SELECT b.parameter_id, b.parameter_ref_code, b.execution_order, t.parameter_name
FROM ams.ams_iba_pl_parameters_b b, ams.ams_iba_pl_parameters_tl t
WHERE b.parameter_id = t.parameter_id AND t.language = USERENV('LANG')
AND b.site_id = :p_site_id;

Administrators also query EXECUTION_ORDER to validate processing sequences and use the ZD_EDITION_NAME column for edition-aware lookups during patching. Troubleshooting scenarios frequently involve tracing which parameters are attached to a site and how they map to page-level parameters via AMS_IBA_PL_PG_PARAMS.

Related Objects

  • AMS_IBA_PL_SITES_B — Referenced via AMS_IBA_PL_PARAMETERS_B.SITE_ID; the parent site definition.
  • AMS_IBA_PL_PARAMETERS_TL — References this table on PARAMETER_ID; supplies translated parameter names and descriptions.
  • AMS_IBA_PL_PG_PARAMS — References this table on PARAMETER_ID; links parameters to page-level parameter mappings.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs security-group-based data access.

These relationships establish AMS_IBA_PL_PARAMETERS_B as a central configuration hub for site-level marketing parameter definitions across both 12.1.1 and 12.2.2 releases.