Results for “descriptor_key”

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

Overview

ICX_POR_THIRD_PARTY_LOG_VALUES is a transactional detail table in the Oracle iProcurement (ICX) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the granular, field-level log of Third Party Authoring changes performed on behalf of suppliers for catalog items and prices. Where the parent log table captures the header event (who performed an action, against which entity, and when), this table holds the individual before-and-after data points that constitute that change. Each row records one descriptor/value pair that was altered, enabling full audit reconstruction of what a supplier-authorized third party modified.

From a Data Vault modeling perspective, the relationship metadata suggests a satellite-leaning classification. The table is keyed by a composite of DESCRIPTOR_KEY and LOG_ID, and LOG_ID is a foreign key to the parent ICX_POR_THIRD_PARTY_LOGS table. This structure is characteristic of a satellite that hangs off a log/link parent, storing descriptive change attributes rather than acting as a hub or link in its own right.

Key Information Stored

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

• LOG_ID — Foreign key to ICX_POR_THIRD_PARTY_LOGS, tying each value row to its parent change event. This is the primary grouping key for reconstructing a single authoring transaction.
• DESCRIPTOR_KEY — Identifies which attribute or field was changed (for example, an item attribute name or a price component). Together with LOG_ID it forms the composite primary key.
• OLD_VALUE — The value of the descriptor prior to the third-party authoring change.
• NEW_VALUE — The value of the descriptor after the change, providing the audit delta.
• CREATED_BY / CREATION_DATE — Standard WHO columns recording the user and timestamp of row creation.
• LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard WHO columns recording the last modification user, timestamp, and login context.

The surrogate/business key is the composite primary key ICX_POR_THIRD_PARTY_LOG_VA_PK1, defined on (DESCRIPTOR_KEY, LOG_ID). This makes the pairing of parent log and descriptor the unique business key for any individual logged value.

Common Use Cases and Queries

Typical uses center on audit, compliance, and troubleshooting of supplier-delegated changes to items and prices within iProcurement catalogs.

• Change audit trail: Reconstruct what changed in a given authoring event by joining to the parent log and listing all OLD_VALUE/NEW_VALUE pairs.
• Field-level reporting: Report which descriptors are most frequently modified on behalf of suppliers.
• Reconciliation: Compare logged NEW_VALUE entries against current item or price master data to detect drift.

A representative query pattern joining to the parent log table:

• SELECT v.LOG_ID, v.DESCRIPTOR_KEY, v.OLD_VALUE, v.NEW_VALUE, v.CREATION_DATE FROM ICX_POR_THIRD_PARTY_LOG_VALUES v JOIN ICX_POR_THIRD_PARTY_LOGS l ON v.LOG_ID = l.LOG_ID WHERE v.LOG_ID = :log_id ORDER BY v.DESCRIPTOR_KEY;

Reporting extracts frequently filter on CREATION_DATE and CREATED_BY to isolate activity by user or period, which supports SOX and supplier-compliance reviews.

Related Objects

The most significant related object is the parent log table referenced by the documented foreign key:

• ICX_POR_THIRD_PARTY_LOGS — Referenced via ICX_POR_THIRD_PARTY_LOG_VALUES.LOG_ID → ICX_POR_THIRD_PARTY_LOGS.LOG_ID. This parent captures the header-level authoring event and is the essential join partner for any meaningful query.

Beyond this documented relationship, related objects in the iProcurement/third-party authoring flow include catalog item and price tables maintained by the authoring process, the iProcurement catalog management views, and standard audit/concurrent program objects that invoke third-party authoring. Because the ETRM metadata for this object is limited to the single FK relationship, practitioners should treat ICX_POR_THIRD_PARTY_LOGS as the primary and authoritative join target and validate any additional associations against the live 12.1.1 or 12.2.2 instance.