Results for “posting_type”

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

Overview

AMS_IBA_PS_POSTINGS_B is the base (language-independent) table in the Oracle E-Business Suite Marketing module (AMS schema) that stores posting information. A posting represents a published item or message surfaced to a user through an Oracle iStore / Marketing "Posting System," where postings drive personalized content placement, subscriptions, or targeted communications tied to a marketing or storefront context. The table holds the master posting definition — its type, content type, status, and configuration limits — while translated, user-facing text resides in the companion _TL table.

Within the physical schema documented for ETRM 12.2.2, the table owns 29 columns and is governed by primary key constraint AMS_IBA_PS_POSTINGS_B_PK on POSTING_ID. From a heuristic Data Vault modeling perspective, this object reads as a hub-leaning entity: POSTING_ID is a stable surrogate key, and the surrounding descriptive and status attributes behave like satellite data attached to that hub. This classification is a modeling suggestion derived from FK structure, not a functional requirement.

Key Information Stored

The central identifier is POSTING_ID, the surrogate primary key. It is also the business-key candidate exposed through unique index AMS_IBA_PS_POSTINGS_B_U1, meaning POSTING_ID functions both as the system surrogate and as the enforcement point for uniqueness.

Descriptive and control columns include:

• POSTING_TYPE — classifies the posting (for example, its delivery or rendering category).
• CONTENT_TYPE — identifies the nature or format of the associated content.
• DEFAULT_CONTENT_ID — references the default content record used when no override exists.
• STATUS_CODE — indicates the lifecycle/activation state of the posting.
• MAX_NO_CONTENTS — caps the number of content items attachable to the posting.
• SECURITY_GROUP_ID — supports multi-tenant / operating-unit data partitioning via FND_SECURITY_GROUPS.

Standard EBS audit columns are present: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. Optimistic locking is supported through OBJECT_VERSION_NUMBER. Fifteen descriptive flexfield columns, ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15, provide extensibility without schema change.

Common Use Cases and Queries

Technical and functional teams query this table to audit posting definitions, validate status, and trace content configuration. A typical lookup by the searched key is:

• SELECT posting_id, posting_type, content_type, status_code, max_no_contents FROM ams.ams_iba_ps_postings_b WHERE posting_id = :posting_id;
• Reporting active postings: SELECT ... FROM ams.ams_iba_ps_postings_b WHERE status_code = 'ACTIVE';
• Translating to display text by joining the _TL table on POSTING_ID.
• Reconciling rules by joining AMS_IBA_PS_RULES on POSTING_ID to confirm which postings have rules defined.

Because the base table contains no translatable text, any user-facing reporting should join AMS_IBA_PS_POSTINGS_TL filtered by LANGUAGE and SOURCE_LANG. ETL and data-vault loads commonly treat POSTING_ID as the hub key and stage the status/type attributes into a satellite.

Related Objects

• AMS_IBA_PS_POSTINGS_TL — translated postings; join on POSTING_ID (FK AMS_IBA_PS_POSTINGS_TL.POSTING_ID → AMS_IBA_PS_POSTINGS_B).
• AMS_IBA_PS_RULES — posting rules; join on POSTING_ID (FK AMS_IBA_PS_RULES.POSTING_ID → AMS_IBA_PS_POSTINGS_B).
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, governing row-level security.
• AMS_IBA_PS_POSTINGS_B_PK / AMS_IBA_PS_POSTINGS_B_U1 — primary and unique constraints enforcing POSTING_ID uniqueness.

Together these objects form the posting definition, rules, and translation triad used across the AMS Marketing posting subsystem.