Skip to main content

SAP Integration Overview

This article goes over Ironclad's SAP integration and the two packages it's offered in: SAP Data Foundation and SAP Procurement Automation. We’ll go over each package, the capabilities included, and where to go for setup instructions. Use this article as a starting point to understand which package fits your needs.

Use Case

Use this article when you're deciding how to connect SAP and Ironclad to understand the difference between the two packages, see which capabilities each one includes, and find the setup article for the capability you want to configure. Choose SAP Data Foundation when the goal is to keep records consistent and eliminate manual data entry, and SAP Procurement Automation when the goal is to have purchasing and contracting trigger each other automatically.

Prerequisites

Features

Integrations, APIs, Entities

Connected Systems

  • SAP Ariba

  • SAP S/4HANA

  • SAP products required for integration:

    • SAP Ariba Procurement

    • SAP Ariba Sourcing

    • SAP Ariba Contracts

    • SAP Ariba Supplier Lifecycle and Performance (Supplier Management)

    • SAP Ariba Developer Portal

Packages

SAP Data Foundation or SAP Procurement Automation

Permissions

Admins or users with Integrations Management permissions.

Comparing SAP Data Foundation and SAP Procurement Automation

Use the table below to compare the two packages at a glance and decide which one fits your situation. The sections that follow list the specific capabilities included in each.

SAP Data Foundation

SAP Procurement Automation

What it answers

“Are my systems talking to each other?”

“Are my systems working together?”

What it solves

Manual data entry, data errors, and information lag between SAP and Ironclad.

Compliance gaps, pricing inconsistencies, and delays between contract signature and operational use.

Best for

Teams that want to eliminate copy-pasting while keeping their records consistent.

Teams that want purchasing and contracting to drive each other automatically.

Included features

  • Connect supplier or requisition data in SAP Ariba to Ironclad

  • Pull supplier or requisition data from SAP Ariba into Ironclad launch forms

  • Sync contracts between Ironclad and SAP Ariba

  • Sync entities in S/4HANA with Ironclad

Everything in SAP Data Foundation, plus:

  • Create an Ironclad contract from an SAP Ariba purchase requisition

  • Sync contract terms to SAP Ariba

  • Sync contract line items to SAP Ariba

  • Create an SAP Ariba purchase requisition from an Ironclad contract

  • Create an SAP S/4HANA purchase contract from an Ironclad contract

i

Note:

SAP Procurement Automation includes all SAP Data Foundation capabilities. You don't need to purchase each package separately.


SAP Data Foundation

The SAP Data Foundation package keeps supplier records, contract data, and signed agreements consistent between SAP and Ironclad.

Feature

Description

Configure which SAP Ariba supplier and requisition data maps into your Ironclad launch forms.

Pull supplier or requisition data into a launch form, and refresh it on demand during negotiation, with a live link back to the source Ariba record.

When a contract is signed in Ironclad, automatically send the signed PDF and its metadata to the related Ariba Contract Workspace, so procurement sees it immediately.

Sync SAP S/4HANA Business Partners into Ironclad as entities, kept up to date as they change in S/4HANA, so S/4HANA stays the source of truth for vendor data.


SAP Procurement Automation

The SAP Procurement Automation package builds on the capabilities of the SAP Data Foundation package so that contracts and purchasing actions trigger each other automatically.

Feature

Description

An approved purchase requisition in SAP Ariba automatically launches an Ironclad workflow with data pre-filled, so purchases are tied to a contract from the start.

For contract-first purchasing, executing a contract in Ironclad automatically creates the purchase requisition in SAP.

When an Ironclad contract is executed, it pushes its negotiated terms and line-item data to the linked SAP Ariba Contract Workspace. Terms map to the workspace’s pricing conditions and spend controls while line items carry item-level pricing, units of measure (UoM), and delivery schedules. Once synced, downstream purchase orders (POs) and invoices are validated against the contracted rates and limits instead of being re-entered manually.

When a contract is signed in Ironclad, a purchase contract is automatically created in SAP S/4HANA with vendor, pricing, terms, and line-item data pre-populated. Procurement works from the contracted data immediately, with no re-entry between contract execution and purchasing.

When a Milestone, Minimum Purchase Commitment, or Payment obligation is added, edited, or removed in Ironclad, the linked Ariba contract updates automatically.

Milestones appear on the compliance contract, commitments update at the contract or line-item level in Pricing Terms, and payments update the contract amount.


Resources

Explore articles, courses, and support options to get the most out of Ironclad.

Help Center

Support

Did this answer your question?