Search Results qp_arch_rltd_modifiers




Overview
Explore in AI Chat

Overview

QP_ARCH_RLTD_MODIFIERS is a key Advanced Pricing (QP) table in Oracle EBS 12.1.1 and 12.2.2 that stores archived records of related modifier relationships. Advanced Pricing handles pricing structures through modifiers—price lists, discounts, surcharges, promotions, and freight charges—and related modifiers allow several modifiers to be linked together so they cascade or apply in a controlled grouping. The base table QP_RLTD_MODIFIERS maintains the live relationships. QP_ARCH_RLTD_MODIFIERS preserves historical versions of those same relationships after they have been archived or purged through the concurrent program driven by the ARCH_PURG_REQUEST_ID column.

The foreign key relationship is documented as RLTD_MODIFIER_ID → QP_RLTD_MODIFIERS, meaning the archive table is anchored to the live related-modifier record it came from. Because the metadata does not define outgoing foreign keys from the archive table to separate hub or link entities, the heuristic Data Vault classification is standalone. Modeled formally, it would function closest to a satellite or historical snapshot of the related-modifier relationship, not a hub or link.

Key Information Stored

  • RLTD_MODIFIER_ID — references the originating record in QP_RLTD_MODIFIERS; the anchor column for the archive row.
  • RLTD_MODIFIER_GRP_NO — the group number that identifies a related-modifier set.
  • FROM_RLTD_MODIFIER_ID / TO_RLTD_MODIFIER_ID — the source and target modifiers that define the relationship, i.e., which modifier is linked to which.
  • RLTD_MODIFIER_GRP_TYPE — indicates the type of qualifying group used to relate the modifiers.
  • ARCH_PURG_REQUEST_ID — the concurrent program request that performed the archival or purge; is the key audit column for tracing a bulk archive operation.
  • CREATION_DATE, CREATED_BY — who created the archived record.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit trail for the last modification.
  • CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield segments, carrying user-defined grouping information.

Surrogate identity is represented by RLTD_MODIFIER_ID; business-key identity for a related-modifier relationship is best expressed by the combination of RLTD_MODIFIER_GRP_NO, FROM_RLTD_MODIFIER_ID, and TO_RLTD_MODIFIER_ID.

Common Use Cases and Queries

This table is primarily consulted for audit and historical analysis: determining what modifier relationships existed at a point in time before a pricing setup was archived, or investigating the scope of a purge. A representative query lists archived relationships for a particular group:

SELECT a.RLTD_MODIFIER_ID, a.RLTD_MODIFIER_GRP_NO,
a.FROM_RLTD_MODIFIER_ID, a.TO_RLTD_MODIFIER_ID,
a.RLTD_MODIFIER_GRP_TYPE, a.ARCH_PURG_REQUEST_ID
FROM QP.QP_ARCH_RLTD_MODIFIERS a
WHERE a.RLTD_MODIFIER_GRP_NO = :grp_no;

Tracking the purge by request is equally common:

SELECT * FROM QP.QP_ARCH_RLTD_MODIFIERS
WHERE ARCH_PURG_REQUEST_ID = :request_id;

Reporting typically joins the archive table back to QP_RLTD_MODIFIERS to pivot specific modifiers, or compares historical relationships against current definitions. Because this is an archive table, queries are read-only and should be filtered by group number, request ID, or date range to remain performant.

Related Objects

Together these objects allow reconstruction of pricing relationships from archive into current time for compliance and analysis.