SAP Ariba Sourcing: Advanced Features Part 1 – AR120 — Lesson 2: Scoring, Team Grading, and Evaluation Governance

Learning Objectives

• Explain how Scoring, Team Grading, and Evaluation Governance supports advanced sourcing control.
• Complete the workflow and produce a reviewable scoring and grading evidence pack.
• Evaluate the condition where a team grade is included twice in the event total and select a supported response.

Detailed Topics

• Weighted scoring rules: settings, dependencies, and derivation rules that control the selected process behavior.
• Team grading assignments: integration touchpoints and downstream effects that must remain aligned with business intent.
• Consensus and normalization: authorization, governance, and change controls required to protect the configuration outcome.
• Evaluator access controls: test conditions and regression evidence needed before transport or operational release.

Instructor Demonstration

The instructor models an end-to-end decision path covering Weighted scoring rules, Team grading assignments, Consensus and normalization, Evaluator access controls. Navigation, documents, configuration influences, authorization boundaries, and retained evidence are connected to scoring and grading evidence pack, including a controlled test where a team grade is included twice in the event total.

Hands-On Exercise

Complete a controlled activity covering Weighted scoring rules, Team grading assignments, Consensus and normalization, Evaluator access controls and preserve the final result in scoring and grading evidence pack.

1. Define the expected business result and the SAP objects that should produce it.
2. Perform the lesson scenario, capturing before-and-after evidence for every material decision.
3. Test the exception without changing unrelated settings or data, then explain the first divergence.
4. Apply proportionate remediation and complete a focused regression test before handover.

Scenario Analysis

• Which SAP object, rule, master record, or process step most strongly influences the observed result?
• What evidence distinguishes a configuration problem from data, authorization, integration, or timing causes?
• How should the scoring and grading evidence pack be approved, retained, monitored, and updated after handover?

Troubleshooting Guidance

Start at the earliest point where expected SAP behavior differs from the observed result. Review process sequence, master data, organizational assignments, configuration, authorization, integration, and timing separately. Treat “a team grade is included twice in the event total” as a testable hypothesis until settings, documents, logs, reports, and retest outcomes confirm the cause.

Validation Checklist

• Required structures, master data, roles, settings, and dependencies for Scoring, Team Grading, and Evaluation Governance are present.
• The scoring and grading evidence pack connects each conclusion to objective, reviewable SAP evidence.
• Normal processing, the stated exception, integration behavior, and access boundaries were tested.
• Corrections, retest criteria, ownership, documentation, monitoring, and operational handover are complete.

Lesson Outcome

Learners can apply Scoring, Team Grading, and Evaluation Governance, explain the resulting SAP behavior, and defend the outcome through scoring and grading evidence pack.