jaggaer

Classifies JAGGAER source-to-pay actions as read, write, or destructive for safe operation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating the JAGGAER ONE source-to-pay suite involves actions that commit money and reach external suppliers—publishing RFx events, awarding bids, transmitting POs, releasing invoices—and a mistake in any of them is hard to undo. This Skill gives an AI agent the judgment to classify every JAGGAER action by risk and know when to stop for human approval. ## Core Features & Use Cases - Action classification: Maps JAGGAER operations across Sourcing, Contracts, eProcurement, Invoicing/AP, and Supplier Management into read, reversible write, committing write, and destructive tiers with gating rules. - Edge-state and recovery guidance: Covers sealed-bid envelopes, ASO optimization scenarios, partial receipts, match exceptions, tolerance changes, and ERP export failures, with recovery patterns for each. - Circumvention detection: Flags audit-risky patterns like splitting requisitions under approval thresholds, self-qualifying suppliers, or overriding out-of-tolerance holds. - Use Case: When asked to release an AP hold on an invoice with a price variance, the agent recognizes this as a destructive out-of-tolerance override and routes it to a named approver instead of clearing it. ## Quick Start Ask the agent to classify a JAGGAER action such as publishing an RFQ or approving an invoice before executing it.

Frequently Asked Questions about jaggaer

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

FAQPage Schema
How do I safely approve an invoice in JAGGAER?

Approving or releasing a JAGGAER invoice is the money event because it creates the payable and authorizes payment. Check match exceptions, tolerance status, and receipt state first, and route any out-of-tolerance hold release to a named approver rather than clearing it directly.

What is the difference between a JAGGAER sourcing event, award, contract, and PO?

These are four separate governed steps, each with its own approval workflow. An event is a competitive process, an award commits the supplier selection and notifies winners, a contract carries compliance accumulators, and a PO is the transmitted commitment to buy.

Does running an ASO optimization scenario award the business in JAGGAER?

No, running an Advanced Sourcing Optimizer scenario is read-class analysis that computes an optimal allocation under constraints. Nothing is committed until you explicitly apply the scenario through the award step, which selects and notifies suppliers.

When should I use this Skill instead of the Coupa or SAP Ariba skills?

Use it only when the connected source-to-pay suite is JAGGAER ONE, SciQuest, or JAGGAER Direct. If the connector is Coupa, SAP Ariba, Ivalua, or Oracle Procurement Cloud, use that vendor's skill instead, since workflows and terminology differ.

Why did my approved JAGGAER invoice not get paid?

JAGGAER approval is not the same as ERP posting. The ERP can reject the export due to a closed period, blocked vendor, or invalid cost object, so check the per-invoice export status and route failures to the SAP FI side.

Can a registered JAGGAER supplier receive a purchase order?

Registration alone is not enough. The supplier must also be qualified for the specific category and free of risk or compliance holds before an award, contract, or PO, otherwise money goes to an unvetted party.