SAP Ariba Strategic Sourcing: System Administration – AR710 — Lesson 2: Templates, Project Types, Content, and Team Rules

Learning Objectives

• Explain how Templates, Project Types, Content, and Team Rules supports governed sourcing administration.
• Complete the workflow and produce a reviewable sourcing template administration workbook.
• Evaluate the condition where a template update changes active project behavior unexpectedly and select a supported response.

Detailed Topics

• Project template structure: settings, dependencies, and derivation rules that control the selected process behavior.
• Event and document content: integration touchpoints and downstream effects that must remain aligned with business intent.
• Team member rules: authorization, governance, and change controls required to protect the configuration outcome.
• Task and phase configuration: test conditions and regression evidence needed before transport or operational release.

Instructor Demonstration

The instructor models an end-to-end decision path covering Project template structure, Event and document content, Team member rules, Task and phase configuration. Navigation, documents, configuration influences, authorization boundaries, and retained evidence are connected to sourcing template administration workbook, including a controlled test where a template update changes active project behavior unexpectedly.

Hands-On Exercise

Complete a controlled activity covering Project template structure, Event and document content, Team member rules, Task and phase configuration and preserve the final result in sourcing template administration workbook.

1. Confirm the business objective, organizational scope, required roles, source data, and expected SAP result.
2. Execute the workflow in sequence while recording settings, transactions, documents, messages, and observations.
3. Introduce the stated exception and isolate the earliest point where observed behavior differs from expectation.
4. Correct or contain the issue, retest the outcome, and document ownership, evidence, and follow-up.

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 sourcing template administration workbook 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 template update changes active project behavior unexpectedly” 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 Templates, Project Types, Content, and Team Rules are present.
• The sourcing template administration workbook 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 Templates, Project Types, Content, and Team Rules, explain the resulting SAP behavior, and defend the outcome through sourcing template administration workbook.