Search Results icx_procurement_server_setup




Overview
Explore in AI Chat

Overview

The ICX.ICX_PROCUREMENT_SERVER_SETUP table is an Oracle iProcurement (ICX product family) configuration table that stores connection information for an external Catalog source. In Oracle E-Business Suite releases 12.1.1 and 12.2.2, iProcurement allows purchasing and requisitioning users to punch out to external supplier catalogs or to retrieve catalog content hosted on a remote procurement server. Each row in this table captures the endpoint and authentication metadata required to establish that connection, effectively acting as a registry of configured external catalog servers and their associated item source definitions.

From a data modeling perspective, the heuristic Data Vault classification provided in the metadata is standalone. As a modeling suggestion, this indicates that the table does not participate in an explicit hub-and-satellite or link structure within the mined foreign-key graph. The single documented foreign key to ICX_POR_ITEM_SOURCES suggests a loose association rather than a complete hub/link relationship. Analysts should treat the object primarily as a configuration or reference satellite whose rows are keyed by the item source identifier.

Key Information Stored

The table contains nine documented columns in the 12.2.2 physical schema. The most significant of these are described below.

  • ITEM_SOURCE_ID — The surrogate identifier for the catalog source configuration. It is the foreign key target column referencing ICX_POR_ITEM_SOURCES, and it functions as the primary business-key candidate for each configuration record.
  • COMPANY — The company or supplier entity associated with the external catalog connection, used to distinguish multiple catalog providers.
  • AUTHENTICATION_URL — The URL endpoint used to authenticate the iProcurement session against the external procurement server.
  • CALLBACK_URL — The return URL that the external server uses to pass control and response data back to iProcurement after the punch-out or catalog request completes.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each configuration row, when, and under which login session.

The surrogate primary key is ITEM_SOURCE_ID, while the audit columns follow the conventional Oracle Applications "WHO" column pattern. No additional unique indexes beyond the key are enumerated in the documented metadata.

Common Use Cases and Queries

Functional and technical users typically query this table to audit external catalog connectivity, diagnose punch-out failures, and migrate configuration between environments. A common diagnostic query joins the setup row back to its item source definition:

  • Listing all configured catalog servers with their authentication endpoints: SELECT item_source_id, company, authentication_url, callback_url FROM icx.icx_procurement_server_setup;
  • Identifying recent changes using the audit columns: SELECT item_source_id, last_updated_by, last_update_date FROM icx.icx_procurement_server_setup WHERE last_update_date > SYSDATE - 30;
  • Correlating connection setup with item sources to validate referential integrity across the two tables by joining on ITEM_SOURCE_ID.

Reporting use cases include configuration baselines, environment comparison (production versus test), and pre-upgrade validation of external catalog registrations.

Related Objects

The following objects are most significant relative to this table:

  • ICX_POR_ITEM_SOURCES — Referenced by the foreign key ITEM_SOURCE_ID; stores the parent item source definition to which each server setup row is bound.
  • ICX_POR_ITEM_SOURCE_MAP — Maps item sources to catalog content and is commonly joined for end-to-end catalog configuration reporting.
  • ICX_POR_CATALOG_MANAGERS — Defines catalog management responsibilities that may be associated with a given external source.
  • PO_CATALOG_SOURCES / PO_CATALOGS — Purchasing catalog definitions that consume the same external source identifiers.
  • iProcurement punch-out APIs — Runtime components that read the authentication and callback URLs stored here when initiating a catalog session.
  • FND_USER — Related via the CREATED_BY and LAST_UPDATED_BY audit columns for user attribution in audit reports.