MM / P2Parchitect

MM Service Procurement Part 4: Architecting Service Procurement Across Landscapes

Key takeaway

Design service procurement for large organizations: classic vs lean services strategy, service catalogs and contracts, integration with Ariba or supplier networks for SES and invoices, central procurement, migration of open service POs and SES, and governance of approvals and accruals.

Explanation

📌 KEY POINTS
✅ Choose a service model: classic ESM for complex specifications, lean services for simpler services and cloud alignment.
✅ Use contracts and catalogs for recurring services.
✅ Supplier collaboration (SES and invoices via network) reduces manual work.
✅ Migration must handle open service POs, SES and limits carefully.
⚠️ Without accrual logic for performed-not-accepted services, month-end costs are understated.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 3 covered acceptance. Now architecture.

━━━━━━━━━━━━━━━━━━━━
▶ 1. MODEL STRATEGY

Classic vs lean by category and deployment (on-premise vs cloud).

━━━━━━━━━━━━━━━━━━━━
▶ 2. CONTRACTS AND CATALOGS

Service contracts, rate cards, catalogs.

━━━━━━━━━━━━━━━━━━━━
▶ 3. INTEGRATION

Ariba/supplier network for PO, SES, invoice; central procurement.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MIGRATION

Open POs with partial SES, limits consumed, open invoices.

━━━━━━━━━━━━━━━━━━━━
▶ 5. GOVERNANCE

Approvals, accruals, KPIs (acceptance time, overbilling).

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Classify service categories.
Choose model and integration per category.
Plan migration of open items.

✅ CHECKPOINT: each service category has a defined buying channel, acceptance and invoice flow.

Code example

ABAP Code

===== STEP 1: category strategy =====Facility services: lean services + contracts + supplier SES via networkEngineering projects: classic ESM with detailed service specificationsTemporary labor: contingent workforce solution / timesheets (per landscape) ===== STEP 2: migration =====Open service POs: open value, accepted SES, remaining limit → migrate with consistent history ===== STEP 3: KPIs =====SES approval time | invoices without SES | overbilling rate | accrual accuracy

Real project scenario

A multinational facilities and construction group ran services on three models across regions. Harmonizing on lean services for routine facilities work, classic ESM for construction projects and supplier-created SES via network cut processing effort and improved accrual accuracy.

Common mistakes

One model for all services.
Manual SES entry for high volume.
Migrating open POs without SES history.
No accruals.
No KPIs.

Best practices

Choose model per category.
Use contracts/catalogs.
Enable supplier collaboration.
Plan migration carefully.
Measure performance.

Interview angle

Questions: "Classic vs lean services strategy?", "How do you integrate Ariba for services?", "How do you migrate open service POs?"
Strong answer: category-based model, contracts, supplier collaboration, migration, governance and accruals.

Practice this lesson

Quick check

1. Which capability reduces manual SES entry for high-volume services?

2. A multinational runs three different service models across regions. What should the architect do?

3. When is classic external services management preferable to lean services?

Interview questions

1. A vendor reports they never received scheduled delivery output for a scheduling agreement covering external services, causing invoice discrepancies in FI-AP. How would you investigate the output management integration?

Answer it in your own words first, then compare.

2. How would you configure output management for centrally created service purchase orders in a Central Procurement (Hub) scenario where POs are replicated back to backend ECC/S4 systems?