MM / P2Pintermediate

MM Service Procurement Part 2: Service PO Document Flow and Configuration Essentials

Key takeaway

Configure service procurement: item category D and service specifications, service master and service catalogs, account assignment requirements, document types, SES settings, lean services product type, confirmation control, and the document flow from PR to invoice.

Explanation

📌 KEY POINTS
✅ Classic ESM: item category D, service lines, service masters (AC03), standard service catalogs, conditions per service.
✅ Lean services: service products (product type group) and simplified SES, available in S/4HANA.
✅ Service items require account assignment (or unknown account assignment where allowed).
✅ Document flow: service PR → service PO → SES (acceptance) → invoice.
⚠️ Mixing classic and lean services without clear rules confuses users and reporting.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced services. Now configuration.

━━━━━━━━━━━━━━━━━━━━
▶ 1. CLASSIC ESM

Service masters, service specifications, model service specifications, conditions.

━━━━━━━━━━━━━━━━━━━━
▶ 2. LEAN SERVICES

Product type group for services; item simplicity; Fiori SES apps.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ACCOUNT ASSIGNMENT

Cost center/order/project/asset; multiple account assignment on service lines.

━━━━━━━━━━━━━━━━━━━━
▶ 4. DOCUMENT TYPES AND SES

PR/PO types with service items; SES document numbering, acceptance.

━━━━━━━━━━━━━━━━━━━━
▶ 5. DOCUMENT FLOW

PO history shows SES and invoices.

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

Create service masters.
Create a PO with service lines.
Post SES and check PO history.

✅ CHECKPOINT: PO history shows accepted SES values and invoices.

Code example

ABAP Code

===== STEP 1: classic =====AC03 service master "Cleaning per hour" | PO item D → service lines: 160 H × 25.00 | account assignment K ===== STEP 2: lean =====Service product (product type group 2 per config) → PO item without service lines → Fiori SES ===== STEP 3: flow =====PR → PO → SES (ML81N / Fiori) → acceptance → MIRO

Real project scenario

An IT staffing client procured contractors with material items, so hours were received like goods and costs hit inventory accounts temporarily. Moving to service items with account assignment and SES acceptance corrected postings and approvals.

Common mistakes

Services as materials.
Missing account assignment.
Mixed service models.
No service catalog.
Ignoring PO history.

Best practices

Choose classic vs lean deliberately.
Maintain service masters/catalogs.
Enforce account assignment.
Standardize document types.
Train on document flow.

Interview angle

Questions: "How do you configure service procurement?", "What is a service master?", "Lean services vs classic?"
Strong answer: ESM objects, lean services, account assignment, document types/SES, flow.

Practice this lesson

Quick check

1. An IT staffing client procured contractor hours with material items. What is the better approach?

2. Which object in classic external services management defines a reusable service with description and unit?

3. What characterizes S/4HANA lean services compared with classic ESM?

Interview questions

1. How does account assignment on a service PO item interact with supplier evaluation scoring, particularly for the price and quality sub-criteria in the Supplier Evaluation (LOB) or classic MM-based supplier evaluation framework?

Answer it in your own words first, then compare.

2. Walk through how the account assignment category on an external services PO line item determines whether a cost object is mandatory at creation, and how this choice affects downstream GR/IR and invoice posting behavior.