Production Engineering and Operations - PP-PEO

Enhancements in Manufacturing Change

Management – PP-PEO
CUSTOMER

1
Objectives

After completing this learning module, you will be able to:

• Explain task coordination and review using Workflow for Change Record.
• Explain the enhancements for Change Impact Analysis.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 2

2
Workflow for Change Record

3
 Typical Manufacturing Change Management Flow

Create CR Discarded Completed

Review Execute Perform

Request Plan Execute Final
Planned Routing Order
Change Change MBOM Approval
Changes Changes Adjustments

Identify Make
Impact Perform
EBOMs for Adjustments
Analysis and EBOM-MBOM
Change for Comp.
Plan Changes Handover
Handover Review Alloc
Planned
Changes

Check and
Rework Adjust WI
Planned
Changes

Check and Perform Order

Adjust Tools Updates Check
Implementation

Rework
Changes
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 4

4
 Pre-delivered Workflow Configuration

A: Workflow Scenario

C: Team Category
B: Activity Type

D: Outcomes for User

Decision Tasks

E: Context Data for

Workflow

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER F: WF Scenario Assignment to CR Type 5

A predefined workflow scenario is delivered by SAP to be used as default workflow scenario

with manufacturing Change Record. The default workflow delivered is “WS02000394” (PEO
Manufacturing Scenario). You can access this configuration using transaction
SWDD_SCENARIO
The Workflow Scenario contains most of the metadata for design time and runtime handling
of the workflow. Following are some of the important aspects controlled by Workflow
Scenario.
1. Type of Tasks/Activities that can be created: There are mainly two types of task (see Fig
A)
1. Activity: This is a task that can be just performed by the recipient. The agent cannot
reject or cancel the task.
2. User Decision: These are task for which can have multiple possible outcomes both
positive and negative.
2. Every task is to be performed by an agent. The Agent determination is provided by
Responsibility Management (This is same as used for Routing Buyoff). The Team
Category to be used by the WF scenario is defined here. Based on this the possible
Agent functions can be chosen when workflow is created. (see Fig B)
3. Possible outcomes of the task such as rework, reject etc. can be defined here. (see Fig
C)
4. Can define the properties that can be utilized for workflow design time and runtime
processing. The properties like Change Record Name and Type are available for
processing.
5. Workflow Scenario is assigned to a Change Record Type using the Change Record
Configuration.
1. CR Type ‘MFG’ is a pre-delivered CR Type which is pre-configured for Manufacturing
Change Cycle.
2. CR Type ‘MFG’ is linked to the WF scenario ‘WS02000394’ (see Fig. F)

5
 Responsibility Management: Configuration
Responsibility Management is used in
• Functions are used to identify a functional role of a
Workflow to determine the appropriate Define Functions person in a team. Sample bullets
agent(person) for a task. • Ex. Operator, Supervisor, Welder, Laser specialist etc.

The configuration allows to define the

functions and team types using which Define Function • A mechanism to group functions so that it may be
Profiles used as a profile of a team.
team with appropriate persons and
responsibility can be created.
• Team Category ‘EPO’ is pre-delivered by SAP for use
in the PEO. The team category is assigned to the
Define Team Workflow Scenario. And the workflow scenario is
Categories assigned to Change Record Type.
• One or more function profiles can be assigned to a
team category.

• Team type is defined for a Team Category. When a

team is created with a team type then all attributes of
Define Team Types the team category is applicable for the team.
• Some functions assigned to the Team Category can
be excluded from Team Type if required.

SAP Pre-delivered
Change Record
Team Category Workflow Scenario
Type
“EPO” “WS02000394”
“MFG”

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 6

The workflow tasks need to be assigned to appropriate persons. Although sometimes it can
be assigned to a named person, in case of big organizations teams are defined with
functions to identify the individual expert.
The module of Responsibility Management within S4HANA is utilized by Workflow to find the
appropriate person for executing a task.
This slide explains the basic configuration required to create such teams.

The Team Category is the highest level of segregation between team. The team category
‘EPO’ is pre-delivered with Production Engineering and Operations and this team category is
assigned to the default workflow scenario used for CR Type ‘MFG’.

6
 Define Team with Functions
Teams can be created using the Tile ‘Manage Teams and
Responsibilities’.

Teams consist of business partner(person) who are assigned

functions available for the team type.

These functions are utilized to determine the right business

partner to handle a workflow steps(see next slide).

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 7

After the configurations in the previous slides are done, the Teams can be created using the
App ‘Manage Teams and Responsibilities’.

The team is created for a team type.

Multiple Business partners can be added to the team and could be assigned one or more
‘Functions’.

7
 Creating Workflow for Change Record

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 8

After the workflow scenario is mapped to a Change Record Type, workflows can be created
for the Change Record.
To create a change record go to the App ‘Manage Engineering Changes’. Create a CR with
CR Type Manufacturing Engineering or any other CR type that you may nave configured.

Enter mandatory information for the Change Record describing the scope of the change
record.

Go to the ‘Process Route’ section of the Change Record and Click on ‘Add’.

The options available in the definition of step are as per the configuration of the Workflow
Scenario. For example the Step Type and possible outcomes for the step types; Agent
Functions are as defined in the Workflow Scenario.

You can also select the Change Record Status that should be triggered when the step is
invoked. This enables automatic transition of CR status via workflow step completion.

8
 Workflow for Change Record – Create User-Decision Steps

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 9

In same way as described in previous slide, steps with user-decision can also be created.
The user-decision steps can have multiple positive and negative outcomes(as described in
the WF Scenario). The action to be performed on each of these outcomes are also
configured with the step definition.

Perform any of the following system action with an option to precede it with one of the
available pre-defined steps:
1. Cancel Workflow: This would cancel the workflow and put the CR in a cancelled statues.
This should be used carefully.
2. Restart Workflow: This could retrigger the workflow again from the first step. It is
appropriate when all steps before the review has to be repeated.
3. Repeat Step: This means the user-decision step shall be repeated. This option is
normally combined with a preceding rework step.
4. Continue: Move to next step in the workflow.

9
 Workflow for Change Record - Runtime

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 10

Once the Workflow is Started, the workflow runtime engine determines the task that should
be instantiated and determines the agents based on the functions specified in the workflow
step.

The relevant users shall receive their instance of task on the Universal Inbox App called ‘My
Inbox’.

Depending upon the configuration of the task, the agent may be able to navigate to the
Change Record App to make the relevant changes. He/She can also take the allowed
actions for the task such as ‘Complete’, ‘Approve’, ‘Reject’ etc.

10
Enhancements for Change Impact
Analysis

11
 Consolidated List View
• Filter bar for effective determination of
Impacted/related objects
• Trigger Object
− Will only consider objects which are part
of the change cycle.
• Object Type
− Filter only the objects that the user is
interested in.
▪ The List view will show the following
details:
• Analysis Status
− Impacted By Change indicator:
o This icon indicates if the object is impacted by the
change or just a related object
− Net Change Considered indicator:
o This icon indicates if the Net Change of the object
is considered for determining the impacted/related
objects
− Added to CR indicator
o Indicates if the objects is already part of the
Change Cycle(Change Record)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 12

As a Production Engineer, the user needs to:

• Understand the impact on manufacturing when a change is made to an Engineering or
Manufacturing object.
• Be able to add impacted or related objects to a Manufacturing Change Record.

Based on the configuration, the system performs complete impact analysis and displays a
complete list of potentially impacted objects in a flat list format. This list does not show the
relationship between the objects but gives a overall picture of the impact.
The impact analysis determines whether an object is just a related object or really an object
impacted by change in the EBOM or MBOM Versions. This is highlighted using the Analysis
Status.

After initial analysis result is displayed, the page also provides some additional filter options
like for example you can choose to display only impacted Production Orders and not other
objects etc.

12
 Network Graph Layout

• Network graph layout for better

visualization
• Impacted Objects are color coded
to red
• The determination path is depicted
using the arrows
• Zoom in & Zoom out feature
• Toggle between List view and
Network view
• Perform actions on nodes

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 13

As a Production Engineer, the user needs to:

• Understand the relationships between the affected object and other related objects that
could potentially be affected by the change.
• To be able to get a holistic view of the impacted and related objects.

The Network graph view of the Analyze Change Impact app will provide the user a better
visualization of the impacted and related objects and their relationship details.

For Example, if the user wants to know how a particular Production Orders is determined and
which EBOM and MBOM change caused the impact, then the Network Graph layout will
provide the required information.

13
 Net Change

• The Net Change tab in EBOM & MBOM

details page will give the user a
snapshot of the change in EBOM &
MBOM.
• The change in Effectivity is also
displayed in the Net Change tab as
Impacted Units

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 14

As a Production Engineer, the user needs to :

• Know the changes done on EBOM & MBOM including effectivity change

The Net change tab in EBOM & MBOM details page will provide the user with a snapshot of
the change. The change can be a Quantity change, component change or effectivity change.

14
 Highlighting Impacted Items

• Identifies and highlights all objects that

are directly impacted by the change
guiding the user to the critical points
• Identifies and highlights all affected
operation activities for each impacted
routing.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 15

As a Production Engineer, the user needs to:

• Know the impacted items in MBOM for an EBOM change.
• Know the impacted Operation and Activity in Routing for an EBOM & MBOM change

The highlighting of impacted items feature will help the user to quickly identify the impacted
items in MBOM and identify the impacted Operation and Activities in the Routing.

15
 Extensibility for Analyze Change Impact

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 16

SAP delivers a pre-defined impact analysis based on the objects like EBOM, MBOM, Shop
floor Routing, Production Order etc. But some times customers may want to slightly tweak
the logic for analysis and impact determination. To support such minor extensibility
requirements, the Impact Analysis also provides following extensibility options:
• Make slight adjustment to relationship determination logic between two analysis objects by
replacing SAP delivered logic with custom logic.
• Defining additional actions to be performed on the Analysis objects: As you can see some
actions like ‘Hold’, ‘Release Hold’ is available on Production Order. Similar background
actions can be defined for existing or new analysis objects.
• Defining the fields to be considered for Net Change calculation: The Impact Analysis
determines impact on the related objects based on the changes in the EBOM and MBOM
changes. Since there are several fields in these objects, we provide extensibility for
customers to define which fields are to be considered for change determination.
• Effectivity changes are considered for Net change calculation by default. There is no
need to maintain any special customizing for considering the effectivity.
• Adding their own Analysis Objects. Like EBOM, MBOM, Routing sometimes you may want
to add a custom object as Analysis Object. If you add such new objects, then you will also
need to make other extension for relationship determination etc.
• Defining the relationships between objects: You can also define new pairs for relationship
determination.

• Please note that these extensions involve custom coding and depending upon the data
volume and algorithm, this might adversely impact the performance of the application. So
please use these extension options with care and proper testing.

16
© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components
of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are
set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products,
and/or platforms, directions, and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks
and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and
they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company)
in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

17