Search Results icx_por_third_party_logs




Overview
Explore in AI Chat

Overview

The ICX_POR_THIRD_PARTY_LOGS table is a core data repository within the Oracle iProcurement (ICX) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as a historical audit log for catalog management activities performed by external Third-Party Content Providers. These providers are entities contracted to manage and maintain supplier catalog content, including items and pricing, on behalf of suppliers within the iProcurement punchout and catalog ecosystem. The table's primary role is to provide a traceable, auditable record of all modifications—such as item additions, updates, deletions, and price list changes—executed by these third-party entities, ensuring data integrity and accountability for catalog content.

Key Information Stored

The table's structure is designed to capture the "who, what, and when" of each catalog transaction. While the full column list is not detailed in the provided metadata, the foreign key relationships explicitly identify the critical data points stored. Each record is uniquely identified by a LOG_ID (the primary key). Essential relational columns include SUPPLIER_ID and THIRD_PARTY_ID, both linking to HZ_PARTIES to identify the supplier owning the catalog and the third-party entity performing the action. The THIRD_PARTY_USER_ID links to FND_USER, recording the specific user account used. For item-level changes, ITEM_ID references ICX_POR_ITEMS, and for pricing updates, PRICE_LIST_ID references ICX_POR_PRICE_LISTS. The table likely also contains standard audit columns such as CREATION_DATE, LAST_UPDATE_DATE, and a column indicating the ACTION_TYPE or OPERATION performed.

Common Use Cases and Queries

This table is central to troubleshooting, compliance reporting, and change analysis. Common operational and reporting scenarios include auditing all changes made by a specific third-party provider within a date range, investigating synchronization errors for a particular supplier's catalog, and reconciling item data between source systems and iProcurement. A typical diagnostic query would join to the referenced tables to provide contextual details:

  • Audit Trail for a Supplier: SELECT log.LOG_ID, log.CREATION_DATE, tp.PARTY_NAME as Third_Party, usr.USER_NAME, sup.PARTY_NAME as Supplier, item.ITEM_NUMBER FROM ICX_POR_THIRD_PARTY_LOGS log, HZ_PARTIES tp, HZ_PARTIES sup, FND_USER usr, ICX_POR_ITEMS item WHERE log.THIRD_PARTY_ID = tp.PARTY_ID AND log.SUPPLIER_ID = sup.PARTY_ID AND log.THIRD_PARTY_USER_ID = usr.USER_ID AND log.ITEM_ID = item.ITEM_ID AND sup.PARTY_ID = :p_supplier_id ORDER BY log.CREATION_DATE DESC;
  • Identifying Detailed Change Values: For granular change data, such as the specific attribute modified (e.g., list price, description), queries must join to the child detail table ICX_POR_THIRD_PARTY_LOG_VALUES using LOG_ID.

Related Objects

The table exists within a well-defined schema with specific dependencies, as documented by its foreign key constraints.

  • Referenced Tables (Foreign Keys): ICX_POR_THIRD_PARTY_LOGS references the following tables to enforce data integrity:
    • ICX_POR_PRICE_LISTS via PRICE_LIST_ID
    • ICX_POR_ITEMS via ITEM_ID
    • HZ_PARTIES via SUPPLIER_ID (for the supplier)
    • HZ_PARTIES via THIRD_PARTY_ID (for the content provider)
    • FND_USER via THIRD_PARTY_USER_ID
  • Referencing Table (Child Table): The following table has a foreign key dependency on ICX_POR_THIRD_PARTY_LOGS, storing detailed transactional data:
    • ICX_POR_THIRD_PARTY_LOG_VALUES references ICX_POR_THIRD_PARTY_LOGS via LOG_ID. This is the primary table for querying the actual old and new values of changed attributes.