SAP S/4HANA Cloud · Procurement

Model Product Specifications in SAP S/4HANA Cloud

Order materials and services as one kit: a live demo, five lessons and a checklist.

Frontino IT6 min read

A pump overhaul is never one line item. It is a technician's hours, a seal kit and the knowledge that they belong together. Model Product Specifications let SAP keep that knowledge, so nobody has to remember it. We built one end to end in a real SAP S/4HANA Cloud system: here is how it works, and what the documentation does not tell you.

A maintenance planner asks for "the annual pump service". In many SAP systems that request turns into separate lines: hours for the technician, a seal kit, perhaps a contract for the labour and a catalogue item for the parts. Each line lives on its own. The fact that they belong to the same job lives in someone's head, or in an Excel file on a shared drive.

When that person is on holiday, the seal kit is forgotten, the technician arrives without parts, and the job is booked twice.

SAP S/4HANA has an answer for this that many teams have never switched on: the Model Product Specification, or MPS.

What a Model Product Specification is

SAP describes an MPS as "a structured set of related services and materials that can be used as a template for procurement processes or documents". In plain words: a reusable kit. You define once which services and materials are ordered together, and every contract or requisition can start from that kit instead of from a blank list.

  • Item sets group the items inside the kit, for example "Labour" and "Parts".
  • Functional items are the real things you buy: a service (hours, a flat-rate job) or a material (pieces, litres).
  • You can build up to five levels of hierarchy, and the number of levels does not limit the number of items.

The kit is maintained in the Fiori app Manage Model Product Specifications. Large catalogues of kits can be uploaded from a spreadsheet; the upload runs as a job that you follow in Monitor Jobs for Model Product Specifications.

Where the kit travels: from template to requisition

StepWhat happensApp
1. Build the kitCreate the MPS with its item set, services and materials, then activate itManage Model Product Specifications
2. Agree pricesCreate a purchase contract from the MPS: the whole kit or only part of itManage Model Product Specifications → Create Purchase Contract
3. Request itAdd the kit to a purchase requisition in one step, with the contract as source of supplyManage Purchase Requisitions – Professional

The point is not fewer clicks. The point is that the structure survives: the contract and the requisition describe the same kit, and anyone can see which hours belong to which parts.

A real example: the pump overhaul kit

In our own SAP S/4HANA Cloud system we built a small kit to test the full flow:

  • One item set, "Pump overhaul", with
  • a service: technician work, in hours,
  • a material: a seal kit, in pieces.

From that one kit we created a quantity contract with the supplier, and then a purchase requisition that pulled in the complete item set with the contract already assigned as the source. The requester did not have to know which material number the seal kit has. They picked the kit.

You can see every click in our video demo on the Frontino IT YouTube channel.

Five things we learned in the system

1. Nothing works until you activate the MPS. A saved MPS is still a draft for the rest of the system. Until you press Activate, it cannot be used in a contract or a requisition. It is the most common reason why "the kit does not appear".

2. Contracts start from the MPS, not from the contract app. In Manage Purchase Contracts, the Create and Insert options of the hierarchy view offer materials, services and item sets, but not an MPS. The way in is the other way round: open the MPS and choose Create Purchase Contract, select the item set and add it. SAP then opens a contract draft.

3. The draft contract still needs you. The kit brings the structure, not the commercial data. Expect to complete the header (supplier, purchasing organisation, group, validity), the account assignment on each item and the target quantities. Price warnings at this stage are normal while prices are still open.

4. Requisitions need the hierarchy view. In Manage Purchase Requisitions – Professional, switch the items table to the hierarchical list and use Create → Items / Item Sets from MPS. You can take the full kit or only the parts you need, with checkboxes. Each item still needs its own account assignment, and service items need the dates when the work takes place.

5. Item hierarchies are a one-way switch. The whole feature depends on the configuration step Activate Item Hierarchies in Purchasing, and SAP is explicit: "When you activate this function in your system, you cannot switch it off again." If it is not active, documents that use an MPS stop with the message "Usage of item hierarchies is disabled". That is not a bug to work around; it is a decision to take on purpose.

When a kit makes sense, and when it does not

Good candidates are jobs that repeat with the same shape:

  • Preventive maintenance: hours plus the standard spare parts for each machine type.
  • Workplace set-up for new employees: laptop, accessories, installation and configuration service.
  • Facility services that include consumables: cleaning hours plus supplies.
  • Installation jobs: equipment, delivery, assembly and commissioning.

Not worth it for a single item, a one-off project, or a "kit" whose content changes every time. There, a normal requisition or a catalogue is simpler.

Before you switch it on: a checklist

  1. Decide the activation on purpose. Item hierarchies cannot be deactivated. Agree with your key users and your partner which processes will use them.
  2. List your top five repeat jobs. For each one: which services, which materials, which suppliers. That list is your first set of kits.
  3. Agree ownership. Who creates, changes and retires kits? In our system the standard purchaser role already includes the app; decide whether that is who you want.
  4. Define a naming rule for kit IDs and grouping codes before the first upload, so the list stays searchable.
  5. Test the full path in your test system: MPS, contract, requisition and the conversion to a purchase order, with your release and your approval workflows.

FAQ

Is the MPS available by default?
No. The app is not enabled by default in SAP S/4HANA Cloud. It appears after item hierarchies are activated in purchasing configuration.

Can one MPS contain several item sets?
Yes. An item hierarchy can hold one or more item sets, each with its own items, up to five levels deep.

Do I have to use the whole kit every time?
No. Both contracts and requisitions can be created from the whole MPS or from parts of it.

Can we load many kits at once?
Yes, from a spreadsheet. The upload is processed as a background job that you can monitor.

Sources

Book a free 30-min call