# ariba rfp response submit button broken greyed out: how to fix it

A greyed out submit button in Ariba means a required step is incomplete, usually an unanswered mandatory question or an unsigned document. Walk the response checklist top to bottom and fill every required item. The button lights up the moment the last requirement is satisfied.

```text
ariba rfp response submit button broken greyed out
```

## When to use this skill
- The submit button is visible but greyed out
- You think everything is done but Ariba disagrees

## When not to use this skill
- The button is clickable but errors on submit (a different skill)
- The whole page wont load (a session or portal issue)

## Tool compatibility
SAP Ariba sourcing responses. All current releases.
Related area: business SaaS platforms and vendor portals.
Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with the submit button is visible but greyed out, start at step 1 below.
- If instead the button is clickable but errors on submit (a different skill), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Open the response checklist

```
On the response page, expand the full checklist of required items.
```
Expected: one or more items marked incomplete or not started.

### 2. Answer every mandatory question

```
Go through each required question, including the ones that look optional but are marked required.
```
Expected: each question shows a completed check.

### 3. Sign or accept required documents

```
Complete any terms acceptance or document signature steps.
```
Expected: the documents section shows complete.

### 4. Watch the submit button

```
Return to the top of the page after each fix.
```
Expected: the button becomes clickable once everything is complete.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (open the response checklist): Expected: one or more items marked incomplete or not started.
- Step 2 (answer every mandatory question): Expected: each question shows a completed check.
- Step 3 (sign or accept required documents): Expected: the documents section shows complete.
- Step 4 (watch the submit button): Expected: the button becomes clickable once everything is complete.

## Quick recap
1. Open the response checklist
2. Answer every mandatory question
3. Sign or accept required documents
4. Watch the submit button

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### ariba submit button disabled
Same checklist walk, something required is always the cause. If this matches what you saw, the steps above apply as written.

### cant submit rfp response ariba
Check conditional questions that only appear after earlier answers. If this matches what you saw, the steps above apply as written.

## Why it happens
Ariba gates submission on a completeness check across questions, documents, and line items. The button gives no hint about which item is missing, so it looks broken when it is actually enforcing the checklist.

## Edge cases
- Some questions become required only after a previous answer, revisit the list after changes
- Line items with zero quantity can block submission
- A second tab with an old page state can show a stale grey button, refresh

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_zaLEwDTwoiF7Qb-yfBFdJQ