Engineering change management in SAP S/4HANA

SAP Change Record
with extensions from daily practice

Changes run right across design, quality and production – and often through several plants at once. We tailor the change record in SAP S/4HANA to your processes, separate the implementation cleanly by plant and add views from project practice: process progress with gates, change record information and Lino, the AI assistant inside the change record.

Book a demo View the screenshots

From the request to the shop floor

Engineering change management connects design and production. The change record keeps this path together in one place – it brackets the process, while the change master carries out the object change.

01.

Request and assessment

A change is requested and assessed: what changes, and which materials, documents and bills of material depend on it? The change record collects items, attachments and comments in one place; the impact analysis shows what else is affected.

02.

Approval and change number

The request moves through the stages of the status network. The gates are checked before the next stage becomes reachable. At the status set up for it, the change master is created – the change number that carries the effectivity date.

03.

Implementation per plant

Implementation happens where it belongs: one derived change record per plant, with its own status, its own process route and its own due date. Plant-specific bill of material, routing and production version are updated in the respective plant.

Where changes get stuck in daily work

Five points we keep meeting in change processes. No scare tactics – just what costs the people working with them time every day.

The status does not explain itself

A status code says where the change record stands – but not which path led there and which stages are still ahead.

1

Checks take effect late

If a missing prerequisite only shows up at the status change, the coordination has already happened – and starts over.

2

Impacts remain unclear

Which bills of material, documents and materials depend on a change has to be collected by hand as long as it is not shown together.

3

Knowledge sits in heads and documents

What a check message means and how the process is meant to work is in the project documentation – or in a colleague’s head.

4

One process, many plants

If the implementation is tracked in several plants, everything quickly hangs on a single transaction: one plant is late, and the whole change stands still.

5

What the change record already does as standard

Before talking about extensions, an honest look at the delivered scope is worth it. The change record in SAP S/4HANA brings more with it than it is usually credited for. Which of it is visible is decided by the setup.

Process, status and process route

  • The change record as the bracket around the process: request, items, participants, attachments and comments in one place.
  • A status model on three levels: record status in the header, execution status on the change master and processing status per item.
  • A graphical progress chart of the status transitions and a process flow view of the route.
  • Process routes – the chains of process tasks behind a status – sequential, parallel or in the background, with globally maintained and transportable templates.
  • Teams and responsibilities for agent determination, decisions in My Inbox and digital signature.

Objects, effectivity and impact

  • Items from bill of material, routing, material, document, inspection plan, planning scope and numerous further object types; own object types are provided for.
  • The change master carries the effectivity – date or parameter – and performs the object change; it can be created automatically at the status set up for it, at header as well as at item level.
  • Impact analysis with scenarios, rules and filters, as a table and as a graph.
  • Revision level on the material and the release key in change management, which ties the release to areas such as costing, planning or production.

Structure and evidence

  • Related change records with the function “Derive New Change Record” – the basis for separating by plant.
  • Merging and splitting form a hierarchy of superior and subordinate records, as long as no change number has been created for the record yet.
  • Change documents at field level with old and new value, user and timestamp, plus a log of merging and splitting.
  • Classification through class type 106 brings additional characteristics to the record header.
  • Released interfaces and events for created and changed records, for evaluations alongside.

Tailored to your company

The standard change record is not a rigid form. The change record type is the central lever – it decides what a record is called, what may go into it, which stages it knows and when a change number is created. We say openly where setup ends and extension begins.

One record type per change type

  • Own number range and own status profile per change type – one record type for the design change, one for the implementation in the plant, one for the small correction.
  • Reference objects and item relevance: which object types may enter the record and why they are in it.
  • Dynamic field control: which header field is mandatory, read-only, optional or hidden per stage.
  • Change number handling at header and at item level, including the mapping of the attributes.
  • Digital signature at the status change, at the item and at the process route task.
  • Tab visibility per stage and default classes of class type 106.

Setup instead of programming

  • The status network is built from user statuses, status actions and a status profile – including the link where a stage creates the change master.
  • Rule-based progression: record type, stage and decision determine the next stage.
  • Process route templates, determined by status or by object type, sequential and parallel, with background steps.
  • Teams, functions and responsibilities decide who receives the task.
  • Authorizations through roles and additionally through an authorization group in the record header.
  • Scenarios, rules and filters of the impact analysis per object type.

Where extension begins

  • Additional checks and actions at a status change that go beyond what the setup provides.
  • Additional fields in the record header: the standard does not carry a plant there – the route via classification is setup, an own field is an extension.
  • Agent determination through an own header attribute, for example the affected plant.
  • Deriving the plant records automatically from the affected plants.
  • Dedicated views alongside the record – process progress, change record information and Lino are exactly that.

One process, several plants

One technical change, several production sites, different levels of maturity: if engineering and all plants work in the same record, the slowest plant holds up the entire change. The standard provides a different route – one own record per plant, derived from the leading one.

Leading change record at the top, below it one derived implementation record per plant with its own status, process route and responsibility
Leading record and derived plant records – implementation runs separately per plant, while completion stays coupled. Scrolls sideways.

How the standard separates

  • From the leading record, “Related Change Records” with “Derive New Change Record” creates one own record per plant.
  • Every derived record has its own record type, its own status network, its own process route and its own responsibilities.
  • The relevance “Depends on” keeps the leading and the dependent record together; at completion the standard checks that the two are not closed independently of each other.
  • In change management, objects can additionally be bundled into change packages under a leading change master – for example along organizational lines.
  • At item level, an own change number can be created per group of objects.

What is updated per plant

  • The bill of material is plant-specific through material, plant, usage and alternative.
  • Routing and production version also sit at plant level.
  • The material status takes effect plant-specific and cross-plant at the same time – both apply together.
  • The change master itself is cross-plant; the plant reference arises through its object management records.
  • The standard carries no plant in the record header. The assignment runs through classification or an additional field; deriving one record per affected plant automatically is what we set up.

For the record: the Hierarchy tab only shows what has been created by splitting or merging. Both are only possible as long as no change number has been created for the record, and items are moved rather than inherited. The derived records, not the Hierarchy tab, therefore carry the running implementation.

Clean core as a principle

Extensions are not an end in themselves. The core stays standard so that the next upgrade stays manageable.

The standard stays the standard

We keep the core clean: the change record stays SAP standard. It is adapted through settings – record type, status profile, rules, route templates, classification – instead of through interventions in the standard. Additions sit alongside so that an upgrade does not turn into a project. Modifications of SAP objects are not part of it.

What that means for grown custom code and how legacy can be assessed and replaced is on our page about clean core and custom code migration.

And where the standard ends: our extensions

The standard already shows the progress graphically and logs field changes. Our extensions start where the question is: why does the record stand here – and what exactly did the last transition check?

What the standard already provides

  • A graphical progress chart of the status transitions and a process flow view of the route
  • Change documents at field level with old and new value, user and timestamp
  • A log of merging and splitting
  • Impact analysis with scenarios, rules and filters

What we add on top

  • The gates themselves: the rules checked during a transition sit at the transition – not only in the error message afterwards.
  • Skipped stages stay visible instead of disappearing from the display.
  • Decision with timestamp and user plus the field change log of the stage – at the same gate, in the same picture.
  • Change record information: change master, object list and status log side by side in one tab.
  • Lino, the AI assistant inside the change record – with sources and a visible label.

The change record in practice

A walk through the change record – from the launchpad entry point through process progress, gate rules and record information to the answer of the AI assistant. Each station states whether it is SAP standard or part of our extensions. All images are anonymised: names, identifiers and labels have been removed or replaced with sample values. The user interface is shown in German.

Entry & overview

From the launchpad into the record: where the change process starts and what the header of a change record shows. All four stations are SAP standard.

Fiori launchpad with the change service group and four tiles
Launchpad group for the change service
01

Entry in the Fiori launchpad

Standard. The change service group bundles the apps around the change process: My Inbox, Manage Change Records, Manage Change Masters and the Engineering Cockpit.

List of change records grouped by status with a filter row
Worklist grouped by status Click to enlarge
02

All change records grouped by status

Standard. The worklist shows the change records grouped by record status – the user status that the status profile of the record type defines. Filter row, priority, expected completion date and service relevance sit in the same list.

Header of a change record with status, priority and ring of the object count
Header of the change record Click to enlarge
03

The header shows the state at a glance

Standard. Record type, status, priority and expected completion date sit at the top. The record type is the setting that supplies the number range, the status profile and the permitted object types. The ring on the right counts the affected objects by material, document and bill of material.

General Information tab with administrative data, description and the beginning of the status network
General information and administrative data Click to enlarge
04

Administrative data and description

Standard. The General Information tab holds the administrative data and the description of the change. Which fields are mandatory, read-only or hidden here is steered by the dynamic field control per stage. The process progress tab starts directly below it.

Process progress Extension

The SAP standard already shows the progress as a chart. This tab maps the status network completely – with the gates between engineering and operations and also with the paths that were not taken.

Status network of a change record with stage gates from engineering to operations
Status network from engineering to operations Click to enlarge
05

The whole status network at a glance

Extension. All stages sit next to each other: engineering (K0–K9), operations (L0–L9) and the completion (M0). Colours separate the current status, completed, reachable and rejected stages. The diamonds in between are the gates – the transitions where the checks run.

Status network with greyed-out skipped stages and legend
Skipped stages in the status network Click to enlarge
06

Skipped stages stay visible

Extension. If a shortcut is maintained for the change record, the diagram greys out the skipped stages instead of leaving them out. The note below the diagram explains what the display is based on.

Gate rules & log Extension

At the gate sit the rules checked during the transition, the decision that was taken and the log of the field changes – in the same picture instead of in three views.

Overlay at the gate with the check rules of a status transition
Check rules at the gate Click to enlarge
07

The rules sit at the gate

Extension. Pointing at a gate reveals the checks of the transition – for example material status, object in another change record or where-used – plus the checks that always run in the example shown.

Dialog with the gate decision: timestamp, user and status transition
Decision at the gate Click to enlarge
08

Who decided and when

Extension. A click on the gate opens the decision; in this example the dialog shows timestamp, user and the transition from one stage to the next.

Log of a stage with field, action as well as old and new value per row
Field changes per stage Click to enlarge
09

Field changes per stage

Extension. The log for a stage lists the field changes of the respective period; in this example with field, action, old and new value and a timestamp.

Change record information Extension

Change master, object list and status log sit side by side in one tab.

Change record information tab with change master, object list and status log
Change record information in three columns Click to enlarge
10

Master data, objects and messages side by side

Extension. On the left the change master, which carries the change number and the effectivity date, with its flags for approval, safety and service relevance; in the middle the object list, on the right the status log with the check messages and timestamps. Refresh fetches the current state.

Items & impact analysis

Both are SAP standard: the items carry the affected objects, the impact analysis uses a scenario to find what else depends on them.

Item list with documents and materials next to the impact analysis table
Items and impact analysis Click to enlarge
11

Items and impact analysis

Standard. The items list documents and materials with their processing status; the item relevance says why an object is in the record. On the right the impact analysis runs on a scenario and shows type, status and rule status per object.

Impact analysis as a graph with connected object nodes and marked rule violations
Impact analysis as a graph Click to enlarge
12

The same analysis as a network

Standard. In the graph the identified objects appear as nodes. Violated rules are marked in red; each card names object type, object status and the assignment to the change record.

Log & process routes

Standard as well: status transitions as a timeline, the process route as a chain of process tasks.

Timeline of the status transitions and below it the table of the process tasks
Log and process routes Click to enlarge
13

Timeline and process routes

Standard. The log shows the status transitions as a timeline. Below it sit the process tasks of the route – the chain of tasks started for a stage – with activity, processing time, priority and status.

Lino, the AI assistant Extension

Lino sits inside the change record: it answers questions about the process and about messages – with sources and a clear label.

Chat area of the AI assistant with a question about a message from the status log
Question about a message Click to enlarge
14

Ask about the message right away

Extension. A message from the status log can be handed over to Lino directly. Above the input field a note states that answers are AI-generated and not binding and that no confidential data should be entered.

Answer window of the AI assistant with explanation and list of the sources used
Answer with sources Click to enlarge
15

Answer with sources

Extension. Lino explains the message and names the sources it relies on: chapters of the project documentation, live data of the open change record and an extract of the status network.

Answer of the AI assistant labelled as general information
General information, visibly labelled Click to enlarge
16

General stays labelled as general

Extension. If the documentation does not cover a question, Lino still answers – and visibly labels the answer as general information that does not come from the project documentation.

SAP, SAP S/4HANA and SAP Fiori are trademarks or registered trademarks of SAP SE in Germany and other countries.

Four pillars that carry the daily work

What the extensions change in the daily work with change records.

01.

Transparency in the process

The status network shows where the change record stands, which path led there and which stages are reachable – including the skipped ones.

02.

Check rules at the gate

The rules of the transition can be shown at the gate, together with the decision and the log of the field changes.

03.

Know the impact beforehand

Impact analysis and change record information show the affected objects and the messages about them before the next stage is due.

04.

Knowledge on demand

Lino answers questions inside the change record, names its sources and makes visible what is only general information.

Every role sees what it needs

The same change record, four perspectives.

Design & development

The change request is assessed, the affected materials, documents and bills of material hang on the record instead of in a side list, and the path through the approval stages is visible.

1

Change management & coordination

Moves the change through the stages, distributes the implementation to the plants and sees from the related records where it is stuck – without asking every plant separately.

2

Work scheduling & production planning

Gets an own record with an own due date for the own plant: plant-specific bill of material, routing and production version are updated there, independently of the progress of other plants.

3

Quality & regulatory

Relevance flags, check messages and gate decisions sit on the change record – depending on the setup traceable with timestamp, user and field change.

4

Frequent questions about the change record

Five questions we are regularly asked about the change record.

No. The change record in SAP S/4HANA remains the basis. We first set it up through settings; our extensions then come as additional tabs inside the same change record: process progress, change record information and Lino. Items, process routes, impact analysis and log stay exactly as you know them. Modifications of SAP objects are not part of it.
For the most part through settings. The change record type is the central lever: it defines number range and status profile, which object types are allowed as items, which header fields are mandatory, read-only or hidden per stage, when a change master is created and where a digital signature is required. Status network, process routes, teams and responsibilities as well as the scenarios of the impact analysis are settings too, not programming. Extension begins where the standard does not provide something – for example an additional field in the record header or an own check at a status change.
Yes. From a leading change record, one own record can be derived per plant – with its own record type, its own status network, its own process route and its own responsibilities. They stay connected through the relevance “Depends on”; at completion the standard checks that leading and dependent records are not closed independently of each other. Plant-specific bill of material, routing and production version are then updated in the respective plant, without a delayed plant holding up the others. The standard carries no plant field in the record header; the assignment and the automatic derivation per affected plant are what we set up.
The SAP standard already shows the progress as a chart. Our tab maps the status network completely: all stages from engineering to operations, the current status, the path already taken, reachable and rejected stages as well as skipped stages. At the gates in between, the rules checked during the transition, the decision with timestamp and user and the log of the field changes can be shown – in the same picture. Which stages and rules these are depends on the setup in each system.
Lino is the AI assistant inside the change record. It answers questions about the process and about messages from the status log, names the sources of its answer, labels it as AI-generated and not binding and visibly distinguishes between information from the project documentation and general information.

Related topics: SAP S/4HANA migration partner in Germany · Clean core & custom code migration · AI consulting for mid-sized companies

We make SAP processes smarter, not louder.

Steer changes – not the other way round

See the change record with our extensions in a demo – along your questions, on your process.

Book a demo

Get in touch

Get in touch with us

Our experienced team is ready to answer your questions and accompany you on your journey into digital transformation. Don't hesitate to contact us.

Moritz Scharfe, SAP & AI Consultant at Scharfe GmbH

Moritz
Scharfe

Get in touch

SAP & AI Consultant

SAP S/4HANA & AI solutions for mid-sized companies

Scharfe GmbH

Let's shape your digital future together.

Learn more: *
Topic:

For privacy reasons, the Google Maps map is only loaded after your consent. Data is transferred to Google when it loads. You can find more information in our privacy policy.