Configuring Tolerance Limits and Activating Availability Control (Part 2)

📌 KEY POINTS
✅ Configuring AVAC is a strict sequence: budget profile → tolerance limits → controlling-area activation → verification. Each step shapes what the next one can enforce.
✅ Tolerance limits are graded by budget type and usage, not a single on/off switch.
⚠️ Activating AVAC on projects with existing postings triggers a rebuild of assigned values — this takes real processing time and must be scheduled outside peak transaction windows.
💡 Never promote a tolerance change to production without posting test transactions that actually cross each threshold.

━━━━━━━━━━━━━━━━━━━━
▶ 1. BUDGET PROFILE FIRST

• Assigned to the project type; decides whether AVAC is even relevant.
• Sets currency/value-type rules and whether budgeting happens at project or WBS level.
• Confirm this before touching tolerance limits — it constrains everything downstream.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DEFINE TOLERANCE LIMITS

• Defined per controlling area, for each combination of budget type and usage.
• Three response types: warning to the poster, routed warning to the responsible person, or a hard error that blocks the document.
• Typical graded design: warn at 80%, escalate at 90%, hard-block at 100%.
• Can scope by document category — e.g. PRs warn only, POs hard-stop.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ACTIVATE

• Must be explicit at controlling-area (or project) level — never automatic.
• On projects with existing postings, activation rebuilds assigned-value totals.
• Expect noticeable processing time on data-heavy controlling areas; schedule outside peak windows.

━━━━━━━━━━━━━━━━━━━━
▶ 4. VERIFY BEFORE PRODUCTION

• Post a test transaction sized to cross each threshold on a known WBS element.
• Confirm the expected warning/block actually fires.

✅ CHECKPOINT: you can name the four steps in order and explain what activation does to a project with existing postings.

During a fit-gap workshop for a construction industry client, the finance lead requested that purchase requisitions only issue a soft warning while purchase orders and invoices strictly block once 100 percent of budget is reached, so that procurement teams could still plan ahead without hard blocking early in the sourcing cycle. The consultant configured differentiated tolerance limits by document category, activated AVAC for the relevant controlling area, and then ran a structured test cycle across a sample WBS element covering requisition, purchase order and invoice postings at 85 percent, 95 percent and 105 percent of budget consumption to confirm each threshold produced the agreed behavior before promoting the configuration to the production-support environment.

• Defining tolerance limits against the wrong budget type (for example, only original budget) and forgetting that supplements or transfers also need explicit tolerance entries.
• Activating Availability Control without running or verifying the update/rebuild of assigned values, leading to inaccurate initial consumption percentages.
• Assuming activation at controlling area level automatically applies retroactively to every project without checking project-level or profile-level overrides.
• Skipping structured test postings after configuration changes, only discovering gaps when end users report unexpected blocking or unexpected lack of blocking in production.
• Not documenting which document categories or cost elements are excluded from the AVAC check, causing confusion when two similar WBS elements behave differently.

• Confirm budget profile settings and value categories with the finance team before defining tolerance limits, since the profile shapes what AVAC can and cannot enforce.
• Design tolerance limits with graduated warnings before the hard error threshold so project teams have visibility before being blocked.
• Always run a rebuild/update of assigned values immediately after activating AVAC on projects with existing postings, and confirm totals reconcile with expected budget consumption.
• Execute a structured test plan (below warning, above warning, above error) on a representative WBS element before promoting AVAC configuration changes to production.
• Maintain a configuration decision log documenting which document categories, cost elements or statuses are excluded from AVAC checks, to support future troubleshooting.

Interviewers assessing configuration depth often ask candidates to describe the exact sequence of steps to activate AVAC for a new controlling area and to explain what happens to existing postings when AVAC is activated after data already exists. A well-rounded answer covers budget profile prerequisites, tolerance limit definition by budget type and usage, controlling-area activation, the rebuild of assigned values, and a verification test plan, showing the candidate treats configuration as a testable, reversible exercise rather than a one-time setting.