What we are building right now

Approval status in the SAP GUI, now open source

Our extension for the Flexible Workflow is openly available on GitHub as of today. It shows in VA03 where an approval stands and who is involved.

What it shows

A header tab lists every workflow run with processor, status, decision and time stamps. Optionally, a status button in the toolbar shows the result at a glance.

How it gets into the system

Installed with abapGit, MIT licence. The core uses a released BAdI and leaves the SAP standard untouched. Delivered for credit memo requests, further document types can be added.

To the extension →

Create documents directly at the material

New in LeanUp for SAP Fiori: documents can be created right where you already are, at the material. A wizard guides you through it in four steps.

Four steps, one pass

Create new or link an existing document, choose the document type, enter a description, check in originals via drag and drop.

Any number of files in the same pass, the document number assigned yourself if you wish, and the document released right away. That used to be four applications in the DMS; now it is one pass at the material in under a minute.

New: where-used list

Also new: the where-used list. One query shows all parent assemblies at once, with the item in the respective bill of material. Every hit is clickable and leads straight into the assembly.

More about LeanUp for SAP Fiori →

LeanUp for SAP Fiori now reads from four areas

The 360° view of the product now runs directly in the SAP Fiori launchpad as well. The Fiori version of LeanUp reads material master, bill of material, routing and stock from the system through released CDS views.

Four areas, one search

The search works by material description or material number, with a hit list first if there are several matches.

The material master is resolved per plant, the bill of material across multiple levels as an expandable tree, and the routing shows the operations with setup, machine and labour time. Stock is shown across all plants and storage locations, with EWM down to the storage bin.

What already works

Every material you search for opens its own tab, and a right-click on a component opens it as a new tab or in a new window. Columns and fields can be shown or hidden per area and saved as a named variant. The custom objects live in the partner namespace /M2D/.

Next up

Documents from the DMS and the where-used list, then the transactional data and costing, so that the costs are in the same place too.

LeanUp Desktop stays and continues to evolve

We are building the Fiori version of LeanUp, and the question came up: what happens to the Windows application? The answer is clear: it stays and keeps getting new features.

What LeanUp Desktop does today

LeanUp Desktop connects via RFC to SAP ECC and to S/4HANA. The scope: material master, bill of material with item analysis, routing, stock per plant and storage location, where-used list, classification, material movements and documents from the DMS, plus the jump into the SAP transaction with a right-click.

The purchase order history shows price trend, quantities and suppliers over the years with pivot and chart. The export goes to Excel and PDF including sorting, filters and formatting.

Fiori and Desktop side by side

Strategic development continues in Fiori, for companies with S/4HANA and the launchpad. If you work with ECC or prefer the desktop client, you carry on with LeanUp Desktop as before.

Roadmap from practice

What gets built next is something we discuss with the customer who raised the idea. Once a year, at the Innovation Day, we set the next milestones together with all our customers.

Part of the SAP PartnerEdge Open Ecosystem

M2 Digital GmbH is officially part of the SAP PartnerEdge Open Ecosystem. What that means for our development, and what customers get out of it.

What PartnerEdge means for us

Access to SAP resources and tools that let us develop close to the standard. We work in our own partner namespace /M2D/, follow the SAP clean-core principles and work through released APIs.

What customers get out of it

Our development stands on an official foundation. Extensions are clearly separated from the standard and remain traceable. Clean-core principles help reduce customer-specific dependencies and unnecessary rework in future SAP upgrades.

More about SAP Development →

M2 Digital grows out of practice

The beginning. M2 Digital grows out of SAP projects and the day-to-day work of users, where it becomes clear what a good solution has to deliver.

Problems become solutions

From day one the focus has been on SAP and process optimisation, across the modules and grounded in day-to-day work. Whatever gets in the way day to day becomes a requirement, and the requirement becomes a solution. LeanUp later grew out of exactly this work, the 360° view of the product in one application.

Consulting, development and our own software

Three fields from the start. Consulting clarifies the process, development closes the gap to the standard, and our own software bundles what repeats across many customers.

All three interlock in the same project: a process question becomes an extension, and what proves itself several times becomes a product.