Lean services and classic service procurement

Contoso is converting from SAP ECC 6.0, where service procurement used the classic MM-SRV model. After conversion, those documents and transactions are still there, and new lean services sit alongside them. Testers and key users need to recognize both, because a defect report that says "the service entry sheet failed" means different things in each.

The classic model

Classic service procurement uses PO items with item category D (service) and a service specification: an outline of service lines, each with a quantity, unit and price, often taken from service master records. Unplanned services are covered by value limits on the item. Work is recorded with the classic service entry sheet in ML81N, and acceptance of the entry sheet posts the receipt. Classic entry sheets support hierarchical outlines and model service specifications, which some construction and facility contracts relied on.

Why the two do not mix

The two models use different objects. A service product with product type group service on an item category D PO gives an error; an item category D PO cannot be recorded in the lean entry sheet app; and a lean entry sheet is not the same object as one created in ML81N. Interfaces and reports built on classic service entry sheet tables will not see lean entry sheets. Make an explicit list of which suppliers, contracts and document types use which model.

Procurement from other modules has its own switch. Maintenance orders and project networks can procure external services, and their settings decide the model: in plant maintenance, a compatibility procurement mode keeps classic external services (control keys such as PM02 and PM03), while an enhanced procurement mode supports lean services. Projects keep the mode they were created with. If Contoso's maintenance team creates purchase requisitions from maintenance orders, check which mode the order types use before testing.

For Public Edition customers this lesson is simpler: lean services is the service procurement model, and classic transactions are not available. For Private Edition and on-premise customers, the main risk is a mixed landscape in which nobody is sure which model a given PO uses. A simple report of open service POs by item category and product type group, run weekly during the first months, removes that uncertainty.

Converted data needs attention too. Service master records, model service specifications and long-running classic contracts are not converted into lean service products automatically. If Contoso wants recurring classic services such as forklift maintenance to continue as lean services, purchasing must create service products, set up new POs or contracts, and close the classic ones. Treat that as a small migration project with its own data checks, not as something that happens by itself at cutover.