sap-ariba-clm

Classifies SAP Ariba Contracts operations by risk and gates publishing, signing, and amendments.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill sap-ariba-clm-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sap-ariba-clm
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/platforms/contracts/sap-ariba-clm
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill sap-ariba-clm-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating SAP Ariba Contracts (CLM) involves two distinct committing acts—signature and publish—plus irreversible actions like termination and missed auto-renewal notice windows. This Skill gives an AI agent the judgment to classify every contract action as read, reversible write, committing write, or destructive, so consequential operations pause for human approval instead of silently binding the company. ## Core Features & Use Cases - Action classification and gating: Maps every Ariba Contracts operation family (authoring, approval routing, signature tasks, publishing, amendments) to a read/write/destructive risk class with the appropriate gate. - Object and state model guidance: Explains contract workspaces, contract terms, line items, clause libraries, deviations, amendment types, and term types (Fixed, Auto Renew, Evergreen, Perpetual) so the agent reasons about state, not nouns. - Edge states and recovery playbooks: Covers publish-vs-signature mismatches, master/sub-agreement inheritance, in-flight amendments, failed ERP syncs, and what can and cannot be undone. - Use Case: A user asks the agent to renew a supplier contract in Ariba. The Skill directs the agent to re-read the workspace status, version, deviation report, and term type, choose the correct Renewal amendment type, and require human approval before re-publishing. ## Quick Start Ask the agent to review a contract workspace in SAP Ariba and tell me whether it is safe to publish the current version.

Frequently Asked Questions about sap-ariba-clm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely publish a contract workspace in SAP Ariba?

Publishing activates the workspace, stamps a version, arms expiration and renewal clocks, and pushes line items into contract compliance. Re-read the status, version, deviation report, and approval state first, and confirm the published version matches the agreed and signed version before proceeding.

What is the difference between signing and publishing in Ariba Contracts?

Signature legally executes the main agreement, usually through the DocuSign integration, while publish is the Ariba act that activates the workspace and pushes line items to compliance. They are separate committing acts, and the published version must match the signed version.

Can a published SAP Ariba contract be edited?

No, a published workspace cannot be edited in place. Every change opens a new version through an amendment whose type (Administrative, Amendment, Renewal, Termination) determines whether approval and signature re-route.

When should I use Icertis guidance instead of Ariba CLM guidance?

Use Icertis guidance when Icertis is the CLM in play, since it operates a single agreement record and binds on execution alone. Ariba operates a contract workspace with a distinct publish act, so the mechanics are not interchangeable.

What happens if I miss an auto-renewal notice window in Ariba?

Missing the notice window on an Auto Renew or Evergreen contract locks in the new term legally, and there is no system undo. Recovery is a renegotiation or a Termination amendment, so track the notice window counting back from the expiration date.

Why is splitting a contract across workspaces flagged as a violation?

Splitting one contract into multiple workspaces to keep each under an approval or signature-authority threshold is circumvention of the authority check, which applies to the whole commitment. It is auditable and treated the same as PO-splitting in procurement.