Built on the Graphmantix e360° Platform

Your contracts don't have to live in SAP. You can still buy against them.

Many of your most valuable agreements never became buyable in SAP. Some carry terms SAP simply can't model — milestone and deliverable triggers, service SLAs, complex conditional and blended logic. Others could be operationalized, but only as a sprawl of outline agreements, info records and condition records that few projects ever finish. Buy by Contract keeps the contract where it is and still creates compliant SAP purchase orders that reference it — finding the right supplier and product/service in SAP for the buyer.

Contracts stay out of SAP

Finds the SAP supplier & product

Creates the referencing PO

Learns from your open POs & agreements

Cryptographically attested data

Contracts stay where they are

No re-modeling complex terms across outline agreements, info records and condition records. The full agreement lives in Buy by Contract, intact.

Finds the supplier in SAP

Resolves the contract's parties to your real vendor master (LFA1) — block/flag status included.

Finds the product / service

Matches contract line items to your material and service master (MARA/MAKT) so the buyer doesn't have to.

Creates the referencing PO

Generates a compliant purchase order in SAP that carries the negotiated terms and points back to the contract.

Learns your supply base

Configurable to scan open SAP agreements and existing POs, learning which suppliers provide which products and services.

Respects your controls

Release strategies, approval workflow, and authorizations stay in SAP. We work with them, not around them.

Example flow

A buyer needs an item covered by a 40-page master agreement that was never modeled in SAP. Buy by Contract identifies the supplier and the product/service in SAP, applies the contract's negotiated price, and creates the PO — referenced back to the paper contract.

No rip-and-replace

Connect read-only first. Start with one purchasing org and one category, prove it on your sandbox, then expand. SAP stays the system of record for execution throughout.

See it on your own system

We can stand this up against a sandbox / QAS client and show a complex contract turned into a real test PO — typically within a day.

The contract lives outside SAP. The PO lives inside it.

Your complex agreement stays in Buy by Contract, where its full terms can actually be represented. To execute a buy, the system bridges that contract into SAP through SAP's own interfaces — finding the supplier and the product/service, then creating the PO. Every step maps to a real SAP object.

Holds the complex, negotiated contract

Lives in Buy by Contract — instead of re-modeled across outline agreements, info records and condition records

Finds the right supplier for the contract

Resolves to vendor master LFA1 + vendor detail BAPI, with block/flag status

Finds the product or service to buy

Resolves to material master MARA / MAKT (and service entries)

Learns which suppliers provide what

Configurable scan of open agreements EKKO/EKPO and existing purchase orders

Creates a real PO referencing the contract

Standard PO creation BAPI (the ME21N path), not a hand-off file

Honors release strategy & approvals

SAP-side release / workflow — left intact, never bypassed

“But SAP already supports tiered pricing and rebates.”

It does — through info records, condition records, and rebate / subsequent-settlement agreements. But that only covers pricing. Milestone and deliverable triggers, service SLAs, and complex conditional terms have no native SAP representation at all — and even the pricing has to be spread across SAP objects rather than held in the contract. That's a project of its own, which is why so many agreements never get loaded. Buy by Contract skips it: the contract stays intact, and the PO still references it.

Already on SAP Ariba?

Load your Ariba contracts into Buy by Contract to operationalize them against your existing supplier relationships and the Ariba Network — without waiting for every agreement to be published back into ECC as an outline agreement.

How it works

Keep your complex contracts where they belong, and let the system do the SAP legwork at buying time.

Bring in your complex contracts Load the paper-negotiated agreements into Buy by Contract — full pricing, tiers, scope. Nothing has to be modeled in SAP.

Learn your SAP supply base Configure an automatic scan of open SAP agreements and existing POs to learn which suppliers provide which products and services.

Match at buying time When a buyer needs to purchase, resolve the contract line to the right SAP supplier and product/service, with the negotiated price.

Create the referencing PO in SAP Generate a compliant purchase order through the standard BAPI that points back to the external contract — release strategy intact.

Where the value leaks today

When the best contracts can't live in SAP, the negotiated value never makes it into the PO.

Contracts stranded outside SAP

Agreements sit in Ariba, a CLM tool, or a folder — never operationalized in SAP, so buyers can't act on them at execution time.

Free-text POs lose the deal

With no contract to reference, buyers cut ad-hoc POs — at list price, with none of the negotiated tiers or rebates applied.

Renegotiation goes in blind

Because spend was never tied back to the paper contract, no one can prove utilization when it's time to renew.

Book a sandbox demo

See Buy by Contract read your real outline agreements and create a test PO. Tell us about your SAP environment.

Trust & security

SAP teams don't adopt anything that touches procurement without knowing exactly where it sits.

🔐 Provenance you can prove — powered by EQTY Lab

Every fact in the underlying knowledge graph is cryptographically attested at ingestion using EQTY Lab's Verifiable Compute. Each node is stamped to prove where it came from — read directly from SAP, or ingested by you — and chained into a tamper-evident lineage record. Alter anything after the fact and it shows. So when a purchase order references a contract, you can prove the contract, the supplier, and the product/service behind it are authentic and unchanged — audit-grade, not just logged.

Read-only first

Start with read-only RFC access on a sandbox or QAS client. Write-back is enabled deliberately, per scope.

Stays in your landscape

Runs against your SAP system over RFC/BAPI. No bulk extract, no copy of your master data leaving SAP.

Your authorizations

Operates under SAP user authorizations and release strategies. We don't grant ourselves what SAP wouldn't.

Audit-ready

Every PO traces back to its source contract; every supplier or material block is shown with the raw SAP message. Nothing silent.

Your contracts don't have to live in SAP. You can still buy against them.

Contracts stay where they are

Finds the supplier in SAP

Finds the product / service

Creates the referencing PO

Learns your supply base

Respects your controls

The contract lives outside SAP. The PO lives inside it.

“But SAP already supports tiered pricing and rebates.”

Already on SAP Ariba?

How it works

Where the value leaks today

Contracts stranded outside SAP

Free-text POs lose the deal

Renegotiation goes in blind

Book a sandbox demo

Trust & security

🔐 Provenance you can prove — powered by EQTY Lab

🔒 Read-only first

🏠 Stays in your landscape

👤 Your authorizations

🧾 Audit-ready

Read-only first

Stays in your landscape

Your authorizations

Audit-ready