Results for “content_type”

50+ results




Overview
Explore in AI Chat

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

Overview

AMS_IBA_PS_FILTERS_B is a base table in the AMS (Marketing) schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. It stores the filter definitions that the iStore / iMarketing content-serving infrastructure (the "IBA" and "PS" components) applies before returning content to a caller. In functional terms, a filter acts as a pre-condition or restriction that narrows the set of content items a query is permitted to return, so this table is the definition repository for those restriction rules rather than the content itself.

The table carries a surrogate primary key, AMS_IBA_PS_FILTERS_B_PK, defined on FILTER_ID. Base tables in the AMS schema that support translation follow the "_B" (base) and "_TL" (translation) pattern, in which language-independent attributes are held in the base table and descriptive text is held in the translation table keyed by the same identifier. The ETRM relationship data classifies this object as hub-leaning under a heuristic Data Vault model, which suggests it functions as a central business-entity hub for filters, with dependent objects acting as satellites and links around it.

Key Information Stored

The documented physical schema contains 12 columns. The most significant are:

  • FILTER_ID — the surrogate primary key and the column referenced by every dependent table; it is the sole business identifier used for joins.
  • FILTER_REF_CODE — the developer-facing reference code for the filter, used to identify a filter deterministically in code and configuration rather than by internal ID.
  • CONTENT_TYPE — identifies the category of content the filter applies to, determining when the rule is evaluated.
  • GROUP_NUM — the grouping or sequence number that orders filters relative to one another during evaluation.
  • SECURITY_GROUP_ID — the multi-tenant / security grouping column, foreign-keyed to FND_SECURITY_GROUPS, controlling row-level visibility.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the AMS/ADF framework to detect concurrent updates.
  • ZD_EDITION_NAME — the editioning column supporting Online Patching in 12.2.x; it appears alongside FILTER_ID in the unique index AMS_IBA_PS_FILTERS_B_U1, making (FILTER_ID, ZD_EDITION_NAME) the documented business-key candidate.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns present on all AMS transactional tables.

Descriptive, translatable attributes are deliberately absent from this table and reside in AMS_IBA_PS_FILTERS_TL.

Common Use Cases and Queries

Typical usage is to enumerate the filters configured for a content type, to resolve a filter reference code to its internal ID, or to join filter definitions to their translations for a listing report. Because the table is edition-aware in 12.2.x, queries should generally constrain ZD_EDITION_NAME to the active edition or rely on the editioning views, which filter automatically.

  • Resolve a reference code: SELECT filter_id, content_type, group_num FROM ams.ams_iba_ps_filters_b WHERE filter_ref_code = :ref_code;
  • List filters with translated names: join AMS_IBA_PS_FILTERS_TL on FILTER_ID and restrict TL.LANGUAGE to the session language.
  • Inspect filter-to-content linkage through AMS_IBA_PS_RL_ST_FLTRS, which relates stored filters to the content structures they govern.
  • Audit recently changed definitions using LAST_UPDATED_BY and LAST_UPDATE_DATE.

Reporting on this table is most useful when combined with the relationship and translation tables, since the base table alone carries no user-visible name or description.

Related Objects

  • AMS_IBA_PS_FILTERS_TL — translation table; join on FILTER_ID to obtain language-specific filter names and descriptions. FK: AMS_IBA_PS_FILTERS_TL.FILTER_ID → AMS_IBA_PS_FILTERS_B.FILTER_ID.
  • AMS_IBA_PS_RL_ST_FLTRS — relationship table associating filters with stored content; join on FILTER_ID. FK: AMS_IBA_PS_RL_ST_FLTRS.FILTER_ID → AMS_IBA_PS_FILTERS_B.FILTER_ID.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID to enforce security-group scoping across AMS data.
  • AMS_IBA_PS_FILTERS_B_PK / AMS_IBA_PS_FILTERS_B_U1 — the primary key constraint and the unique index (FILTER_ID, ZD_EDITION_NAME) that make the table edition-aware.

Together these objects form the filter definition subsystem within AMS Marketing content delivery.