Working with a Status Network

Objective

After completing this lesson, you will be able to define and use a status network

Use a Status Network

Introduction

A status network defines how a Change Record progresses through its lifecycle and determines which actions are allowed at each stage of the process. Rather than being a simple collection of statuses, the status network acts as a control framework that connects business process stages, user actions, responsibilities, and automation mechanisms into a consistent process model.

The definition of a status network typically starts by identifying the major lifecycle phases of the Change Record. The example shown in the presentation follows a process that moves from Design to Review, then to Approval, and finally to Completion. These phases represent the key milestones that a Change Record must pass before the change is fully implemented and released.

In summary, defining a status network means designing the lifecycle of a Change Record, making relevant statuses visible, controlling allowed transitions and user actions through status profiles, and linking status changes to workflows and approvals. The resulting network ensures that every Change Record follows a controlled, transparent, and auditable path from design through review and approval to final completion.

Status Network

In SAP Change Record, a Status Network acts as the orchestration layer between the overall Change Record lifecycle and the detailed processing status of individual objects. It links user actions, approvals, execution activities, and exception handling into a coherent status model, ensuring that every change progresses through a controlled and traceable process.

The figure explains the connection between the User, header and processing status.

The Header Status describes the overall progress of the Change Record from a business process perspective.

The Status Network links user actions to status transitions.

Because both status dimensions are connected, the system can automatically determine which process step is allowed and what actions should follow.

The Object Processing Status represents the actual state of the affected business object during execution.

Defining a Status Network

The lifecycle of a Change Record is controlled through a status-driven process that reflects the progression of engineering changes from initiation to completion.

To support this process, SAP provides Status Profiles that define the permissible states of a Change Record and the transitions between them. In this scenario, you will learn how the foundation of a status-controlled lifecycle is established by defining user statuses, the actions that trigger status changes, and the conditions that govern these transitions.

User statuses are used to represent the various phases and situations that can occur during the change process, while user status actions define how a Change Record progresses from one stage to the next.

These elements are combined within a Status Profile, creating a structured status network that controls the behavior of the Change Record throughout its lifecycle. By configuring fields, actions, and conditions, organizations can align the Change Record process with their specific business requirements and ensure that engineering changes follow a consistent and controlled workflow.

The following video gives you a brief overview how to configure a change record status Profile in three steps.

At the end the status profile is connected to the Change Record Type.

Defining and Using a Processing Status

The figure explains the processing status and the possible transitions.

The Change Record Processing Status represents the operational lifecycle of a changeable object within a Change Record.

It begins with an assessment of whether the change is possible, unnecessary, or impossible, continues through execution stages such as Change Started, Change Completed, and Change Released, and provides dedicated exception handling through Error in Change and Error Corrected statuses. Together, these statuses ensure transparent, controlled, and auditable execution of change processes.

The Processing Status is maintained with [SM30] in the table/PLMI/CR_PRO_VAL and defines the lifecycle of an individual object that is being changed as part of a Change Record. It allows the system to track whether a change can be performed, is currently being executed, has been completed successfully, or requires corrective action.

Engineering Cockpit

The Engineering Cockpit provides an immediate overview of all change processes that are currently active in your company.

For example, you can apply filters based on the change responsible, upcoming effective changes, or the specific change record type in use. This allows you to quickly identify relevant changes and monitor their status at a glance.

This figure gives detail information about the Engineering Cockpit. Follow the notes for more information.

The individual sections of the Engineering Cockpit can be freely rearranged, and their size can be adjusted as needed.

In addition, you can use the quick links to navigate directly to the corresponding change numbers or change records.

Work with a Status Network

Introduction

Engineering changes often affect multiple business objects and require coordination across different functional areas before implementation can begin. To ensure that all relevant information, responsibilities, and impacted objects are identified and managed in a structured manner, SAP provides the Change Record as a central control object for the change process.

In this scenario, an Engineering Change Record is created and maintained using the Manage Change Records app. After entering the required header information, such as the change description, priority, reason for change, planned completion date, and responsible person, the Change Record is prepared for further processing. The affected business objects are then assigned to the record, including documents, materials, bills of material, BOM components, and routings that require modification as part of the change.

Throughout the process, processing and approval statuses are updated to reflect the progress of the involved departments and to ensure that all prerequisites for implementation have been fulfilled.

Once the required approvals have been completed, change numbers are generated for the affected objects, preparing them for the subsequent implementation phase and enabling controlled execution of the engineering change.

Create and work with a Change Record

Watch the next video to see how a Change Record is created.

Perform Object Changes

Once all required planning activities, approvals, and object assignments have been completed, the engineering change enters the implementation phase. At this stage, the approved design and master data modifications are carried out in a controlled and traceable manner using the assigned change numbers. In this training scenario, the implementation process begins with the update of the affected document, ensuring that a new version is created to capture the design changes while maintaining full version history and object traceability.

After the document has been updated and released, the corresponding changes are applied to the associated master data objects, including materials, bills of material, BOM items, and routings. Throughout the implementation process, the assigned change numbers provide control over the validity of the changes and support consistent documentation of all modifications.

To ensure transparency and accurate progress tracking, the processing status of each affected object is updated as the change advances through the various implementation stages.

Once all required updates have been completed, verified, and released, the Change Record is finalized, providing a complete record of the engineering change and ensuring that all affected business objects are available for productive use.

The second video demonstrates how master data changes are carried out using a Change Number.