slug: ariba
provider: Ariba
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 6
edges:
- tag: Purchase Orders
  spec_file: ariba-purchase-orders-api-openapi.yml
  capability_id: BC-500.30
  capability_id_l1: BC-500
  capability_name: Purchase Order Management
  confidence: 0.94
  evidence: POST /orders  createPurchaseOrder  Create a Purchase Order ... POST /orders/{orderId}/cancel  cancelPurchaseOrder
  reason: Full PO lifecycle create/update/cancel with PurchaseOrderStatus and SupplierReference schemas
    is plainly Purchase Order Management.
- tag: Purchase Order Line Items
  spec_file: ariba-purchase-order-line-items-api-openapi.yml
  capability_id: BC-500.30
  capability_id_l1: BC-500
  capability_name: Purchase Order Management
  confidence: 0.88
  evidence: GET /orders/{orderId}/lineItems  listPurchaseOrderLineItems  List Line Items for a Purchase
    Order
  reason: Operations read purchase order line item detail (schemas PurchaseOrderLineItem, AccountingInfo,
    CommodityCode) within a procure-to-pay suite, which is purchase order management.
- tag: Receipts
  spec_file: ariba-receipts-api-openapi.yml
  capability_id: BC-500.40
  capability_id_l1: BC-500
  capability_name: Procure-to-Pay Operations Management
  confidence: 0.85
  evidence: POST /orders/{orderId}/receipts  createReceipt  Create a Receipt
  reason: Goods receipt capture against purchase orders is day-to-day procure-to-pay operations (the L2
    explicitly names requisitions and receipts).
- tag: Requisitions
  spec_file: ariba-requisitions-api-openapi.yml
  capability_id: BC-500.40
  capability_id_l1: BC-500
  capability_name: Procure-to-Pay Operations Management
  confidence: 0.85
  evidence: POST /requisitions  createRequisition  Create a Requisition
  reason: Requisition creation and listing with RequisitionStatus is procure-to-pay operations, which
    explicitly covers requisitions.
- tag: Invoices
  spec_file: ariba-invoices-api-openapi.yml
  capability_id: BC-200.20
  capability_id_l1: BC-200
  capability_name: Accounts Payable Management
  confidence: 0.8
  evidence: POST /invoices/{invoiceId}/approve  Approve an Invoice; "from requisition creation through
    invoice reconciliation and payment processing"; schemas SupplierReference, PaymentTerms
  reason: Supplier invoice creation, retrieval, approval and rejection within the procure-to-pay flow
    is Accounts Payable invoice processing; the supplier/payment-terms schemas confirm the payables (not
    customer billing) direction.
- tag: Suppliers
  spec_file: ariba-suppliers-api-openapi.yml
  capability_id: BC-510
  capability_id_l1: BC-510
  capability_name: Supplier Management
  confidence: 0.8
  evidence: GET /suppliers/{supplierId}  getSupplier  Get a Supplier Profile ... SupplierQualificationStatus
  reason: Read access to supplier profiles and qualification status is supplier management; the read-only
    surface does not clearly single out one sub-capability (onboarding vs relationship).