Key Features
The following table explains the key features available:
Key Feature Use
Detailed information about the change Change record acts as a single source of truth for product changes. It con-
tains the details such as the reason for change, expected completion date,
participants involved in the change, objects involved in the change, required
attachments, and status information.
Business objects for change record
You can integrate business objects from the process and discrete industries,
such as materials, bill of materials, BOM items, documents, engineering bill of
materials, manufacturing bill of materials, planning scopes, production orders,
purchase orders, engineering snapshots, master recipes, inspection plans, rec-
ipes, specications, label sets, order specic routings, planning routings, pro-
duction routings, product structure variants, routings, and shop oor routing
templates.
Enhanced workows with process route
parallel-, ad-hoc-, and background tasks
Workow tasks can be parallel or sequential, and can be added ad-hoc or via
a template; executed by the user or in the background. You can set processing
times or deadlines, priorities, and recipients. You can switch from the tabular
to the graphical view of the workow process to get a visual representation of
process routes.
Improved user experience in change re-
cord
You can display an overview chart to view the change items added in the
change record, thumbnails for the representation of change items, graphical
representation of process routes, and integrated visual logs for status transi-
tions and digital signatures.
Impact analysis scenarios for change re-
cord
You can dene impact scenarios and set up rules or constraints. When impact
analysis is performed, the impact scenario identies the objects that are im-
pacted by the proposed change.
BOM redlining for change proposals You can create redlines to indicate the change proposals in BOM components.
When a redline status is approved, it can be applied to the BOM to create a new
BOM version or overwrite an existing BOM with change number.
Split and Merge features Product changes in change records can be eciently structured using split and
merge features. Split allows to divide a change record into two and moves the
objects from one change record to another. Merge integrates the fragmented
change requests by merging multiple change records into one and creates a
successor that contains all items and attachments copied from the source
change records.
Digital signature for change records
You can provide compliance support by conguring the system to request
digital signatures for dedicated status changes of the change record. Digital
signatures can be requested at multiple steps and based on dierent signature
strategies.
Visual status change
Progress indicator allows to view the progress and get an instant overview of
the change process using the record statuses.
Dynamic eld control The visibility of elds can be controlled per change record status and the
behavior can be changed based on the type of elds and where they appear in
the UI.
SAP S/4HANA 2022
SAP S/4HANA Enhanced LoB Functions
PUBLIC 459