JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

July 7, 2026 · 11 min read

SAP Ariba Catalog

Catalog is the object that turns a Supplier Master record into something a Requester can actually browse and add to a cart — every item a buying organization can select without raising a free-text request lives inside a Catalog. A Catalog is always linked to exactly one Supplier and is exposed to Buying either by loading its content directly onto the Ariba site (buyer-hosted, via CIF) or by redirecting the Requester to the supplier’s own storefront in real time (supplier-hosted, via Punchout). This article maps Catalog’s core concepts across all Ariba capability areas (Part 1), then details every field an Ariba Administrator configures when defining, loading, and maintaining Catalogs and their items (Part 2).

Part 1: Catalog — Core Concepts (All Modules)#

1.1 What Is the Catalog?#

A Catalog is a structured collection of purchasable items — descriptions, pricing, unit of measure, and supplier reference — made searchable inside the Buying and Guided Buying experience. It is the mechanism that lets a Requester find and select a specific, priced item instead of typing a free-text description that then has to be manually sourced and priced by a Buyer. Every Catalog belongs to exactly one Supplier, and every item inside it inherits that Supplier linkage plus whatever Commodity classification is applied at the item level.

1.2 Catalog Hosting Types#

The Hosting Type decision is made per Supplier relationship and is expensive to reverse mid-implementation, because it determines who owns pricing accuracy, how often content refreshes, and what technical setup (file transfer vs. cXML endpoint) the Supplier must support.

Design principle: Prefer Punchout for suppliers with frequently changing pricing or configurable products, and reserve buyer-hosted CIF for stable, simple-priced items — mixing the wrong hosting type onto a volatile supplier relationship produces stale-price disputes at invoice matching.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Supplier Master "SUP-001" — Dell (ANID 12345)
└── Catalog "CAT-001" — buyer-hosted / CIF ──references──> Commodity Code "43211500" (Zone B)
    └── Catalog Item "ITM-9871" — Latitude 5540, $1,200

Supplier Master "SUP-002" — HP (ANID 67890, preferred supplier)
└── Catalog "CAT-002" — supplier-hosted / Punchout ──references──> Commodity Code "43211600" (Zone B)
    └── Catalog Item "ITM-6644" — EliteBook 850, $1,350

This is a strict, 3-level containment hierarchy: a Supplier Master owns one or more Catalogs, and a Catalog owns one or more Catalog Items — Catalog Item never exists independently of the Catalog that hosts it. Catalog sits at the middle of this chain and is the object this article maps: CAT-001 is a buyer-hosted CIF catalog owned by Dell (SUP-001, ANID 12345), containing item ITM-9871 (Latitude 5540, $1,200); CAT-002 is a supplier-hosted Punchout catalog owned by HP (SUP-002, ANID 67890, flagged as a preferred supplier), containing item ITM-6644 (EliteBook 850, $1,350). Note the Commodity Code chip on each Catalog — 43211500 (CAT-001) and 43211600 (CAT-002) are not part of this containment chain; each is a cross-zone reference back to the Commodity Code master (Zone B, see ARIBA-A03-01) that classifies what the catalog’s items are, independent of which Supplier owns the catalog.

1.4 Integration with Other Master Data Objects#

Catalog does not stand alone — it is the content layer that connects Supplier identity to what a Requester actually sees and buys.

Part 2: ARIBA-Specific Field Details#

2.0 Scope of ARIBA Ownership#

Legend: ◎ = Owner / Critical, ○ = Direct involvement

2.1 Catalog Identity & Hosting Configuration#

These fields identify a single Catalog and determine which of the two hosting behaviors described in Section 1.2 applies to it.

2.2 Catalog Item Attributes#

These fields describe a single purchasable line inside a Catalog — for CIF catalogs they are loaded and stored in Ariba; for Punchout they are rendered live from the supplier’s site but still map to these same logical attributes when a cart line returns.

2.3 Supplier & Category Linkage#

These fields connect a Catalog and its items back to the Supplier Master and Commodity Code masters shown in Section 1.3, driving both search filtering and approval routing.

2.4 Integration & Synchronization#

These fields govern how Catalog content reaches Ariba (CIF load or Punchout endpoint) and how a resulting order line is translated to S/4HANA via CIG.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction