sap-ariba

Classifies SAP Ariba source-to-pay actions by risk and gates consequential operations for approval.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating SAP Ariba involves actions that commit money and reach external suppliers—publishing RFx events, awarding bids, transmitting POs over SAP Business Network, and approving invoice reconciliations—and a wrong move is often irreversible. This Skill gives an AI agent the operator judgment to classify every Ariba action as read, reversible write, committing write, or destructive, so consequential steps pause for human approval. ## Core Features & Use Cases - Action Classification & Gating: Maps Ariba operation families (sourcing events, requisitions, POs, invoice reconciliations, supplier qualification) to read/write/destructive risk classes with explicit gating rules. - Edge-State & Recovery Playbooks: Covers partial receipts, split awards, out-of-tolerance exceptions, failed ERP exports, and what can and cannot be undone after each committing action. - Circumvention Detection: Blocks audit-flagged workarounds like splitting requisitions under approval thresholds, self-qualifying suppliers, or raising tolerances to auto-pass invoice variances. - Use Case: When asked to approve an invoice with a price variance, the agent recognizes an out-of-tolerance exception as a destructive override, stops, and routes it to the named approver instead of clearing it. ## Quick Start Ask the agent to review a pending SAP Ariba invoice reconciliation and tell you whether approving it is safe and what exceptions need a human approver.

Frequently Asked Questions about sap-ariba

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

FAQPage Schema
How do I safely approve an invoice reconciliation in SAP Ariba?

Approving an invoice reconciliation creates the accounts-payable liability and authorizes payment, so it is a committing action requiring human approval. First re-read the IR's exceptions, tolerances, matched PO and receipt, and ERP export status before approving.

What is the difference between SAP Ariba and Coupa skills?

Use this skill when the connected source-to-pay suite is SAP Ariba, covering Sourcing, Guided Buying, Buying & Invoicing, and SLP. If the spend suite is Coupa with requisitions, CSP, and budgets, use the coupa skill instead.

Can a published SAP Ariba sourcing event be unpublished?

No, publishing an event transmits requirements and quantities to invited suppliers over SAP Business Network, so there is no clean undo. Cancelling or pausing notifies suppliers who have already seen the event, making it a destructive action requiring a named approver.

Why is accepting an out-of-tolerance invoice exception risky?

Accepting an out-of-tolerance exception overrides the control that flagged a price, quantity, or tax mismatch and lets the invoice pay despite it. It is classified as destructive and must be routed to a named approver rather than cleared automatically.

Does approving an invoice in Ariba mean it has been paid?

No, approved does not mean paid. The ERP can reject the export due to a closed period, invalid cost object, or blocked vendor, leaving an approved IR with no payable created, so always check export status.

When should I not use the SAP Ariba skill?

Do not use it for ERP-side AP posting and payment runs (use sap-fi), inventory goods-receipt postings in SAP stock (use sap-mm), deep contract clause authoring (use sap-ariba-clm), or physical warehouse receiving handled by a WMS.