Business Driven Configuration Questionnaire - As

Purpose
The objective of this document is to obtain customer information to prepare the system before the fit-to-standa
discussion during the workshop. These questions makes the fit-to-standard process prescriptive and guided b
drive business decisions and respective configuration in SAP S/4HANA Cloud.

The customer is required to complete and return the document a week prior to the workshop.

Note: This document does not include Configuraiton Activties that are specfiic to Localization topics.

Procedure:
Please provide a response to each question in column labelled 'Customer's Response' of the Accelerator wor

Questions categorized as Level 2 are geared to collect information prior to running the fit-to-standard worksho
of fit-to-standard workshops due to missing information.

Questions listed as Level 3 are answered during the fit-to-standard workshops. They are typically aimed to ob
make a business decision and define specific configuration values in the backlog. Your answers may also com
document which you provide to support the information requested. If this option is utilized, for clarity and comp
referenced accordingly.

Business Consultants will validate the responses during fit-to-standard process.

Note: Level 1 questions are not in this document and are addressed during the Sales process.

Target Audience
Customers and Implementation Consultants
Driven Configuration Questionnaire - Asset Management
© 2023 SAP SE or an SAP affiliate company. All rights reserved
Last updated: 3/20/2023

omer information to prepare the system before the fit-to-standard workshop and to use for further
ns makes the fit-to-standard process prescriptive and guided by the process with business questions to
uration in SAP S/4HANA Cloud.

n the document a week prior to the workshop.

aiton Activties that are specfiic to Localization topics.

column labelled 'Customer's Response' of the Accelerator worksheet.

o collect information prior to running the fit-to-standard workshops. They aim to prevent stop/go execution
ormation.

g the fit-to-standard workshops. They are typically aimed to obtain more detailed information needed to
onfiguration values in the backlog. Your answers may also comprise a link to an additional sheet or
ormation requested. If this option is utilized, for clarity and completeness, please ensure each question is

es during fit-to-standard process.

nt and are addressed during the Sales process.

 Business Driven Configuration Quest

Project
SSCUI
Process Relevant? Ref SAP ID
Reference
Y/N

Asset Management Y N/A N/A

Asset Management Y N/A N/A

Asset Management Y BH1, BH2, BJ2 101889 Master Data

Asset Management Y BH1, BH2, BJ2 101896 Master Data

Asset Management Y BH1, BH2, BJ2 101897 Master Data

Asset Management Y BH1, BH2, BJ2 102260 Master Data

Asset Management Y BJ2 102582 Master Data

Asset Management Y BH1, BH2, BJ2 102583 Master Data

Asset Management Y BH1, BH2, BJ2 102635 Master Data

Asset Management Y BJ2 102636 Master Data

Asset Management Y BJ2, BH1, BH2 103091 Master Data

Asset Management Y 103477 Master Data

Asset Management Y 103478 Master Data

Asset Management Y 103631 Master Data

Asset Management Y 103650 Order Processing

Asset Management Y 103651 Order Processing

Asset Management Y 103652 Order Processing

Asset Management Y 103809 Costing

Asset Management Y 103806 Costing

Asset Management Y 103772 Organization

Asset Management Y 103771 Organization

Asset Management Y 103825 Order Processing

Asset Management Y 103825 Order Processing

Asset Management Y 103764 Order Processing

Asset Management Y 103676 Order Processing

Asset Management Y 103794 General Setting

Asset Management Y 103793 General Setting

iven Configuration Questionnaire - Asset Management

Area Topic

Business Overview Business Overview

Business Overview Business Overview

Maintenance Create Structure Indicator for Reference

Management Locations/Functional Locations

Maintenance
Define Types of Technical Objects
Management

Maintenance
Define Planner Groups
Management

Maintenance
Define ABC Indicators
Management

Maintenance
Define Sort Fields for Maintenance Plan
Management

Maintenance
Define Priorities for Each Priority Type
Management
Maintenance
Define Plant Sections
Management

Maintenance
Define Measuring Point Categories
Management

Maintenance
Define Number Ranges
Management

Maintenance Create Default Value Profiles for External

Management Procurement

Maintenance Default Values for Task List Data and

Management Profile Assignments

Maintenance Create Authorization Keys for User Status

Management Authorizations

Maintenance Default Values for Maintenance Activity

Management Type for Each Order Type
Maintenance Assign Valid Maintenance Activity Types
Management to Maintenance Order Types

Maintenance
Define Maintenance Activity Types
Management

Maintenance
Maintain Value Categories
Management

Maintenance
Assign Cost Elements to Value Categories
Management
Maintenance Assign maintenance planning plant to
Management maintenance plant
Maintenance
Maintain maintenance planning plant
Management

Maintenance Define Change Documents, Collective

Management Purchase Requisition, MRP relevance

Maintenance Define Change Documents, Collective

Management Purchase Requisition, MRP relevance

Maintenance
Activate Workflow for Maintenance Orders
Management

Maintenance Define Phase Control Code for

Management Maintenance Orders
Maintenance
Define Prioritization Profiles
Management

Maintenance Define Consequences Categories,

Management Consequences, and Likelihoods
sset Management

Topic Definition

These questions are designed to introduce the implementing team to the

fundamentals of the business, so that subsequent answers can be
properly contextualized.

These questions are designed to introduce the implementing team to the

fundamentals of the business, so that subsequent answers can be
properly contextualized.

Define your structure indicators* for reference functional locations* and

functional locations*. The structure indicator determines the edit mask
and the number of the hierarchy levels when you create functional
location structures.

Define different types of technical objects to categorize functional

locations and pieces of equipment.

Define maintenance planner groups that are responsible for planning and
processing maintenance tasks in a maintenance planning plant.

Define ABC indicators to describe criticality statuses in Plant

Maintenance.

Define sort fields for maintenance plans to determine your individual

grouping of maintenance plans in Plant Maintenance.

Define priority type attributes to determine the start and finish dates of
maintenance orders and notifications in Plant Maintenance.
Define plant sections to divide maintenance plants into production areas
in Plant Maintenance.

Define measuring point categories* in this configuration step. You always

need measuring point categories when you want to enter counter
readings or measurement readings for equipment* or functional
locations*.

Define the number range for an equipment category which is defined in

the step equipment categories*. You must allocate a unique number for
each equipment master record.

Define a profile for external service and material procurement. Use

default values such as purchasing organization, purchasing group, cost
element, and material group.

Assign pre-defined external material and task list profile to order type and
plant combination as default values for order processing.

Provides a default maintenance activity type based on the maintenance

order type.
Allows assignment of a maintenance activity type to a maintenance order
type.

Define maintenance activity types to classify maintenance order.

Standard maintenance activity types are defined in the system and
additional maintenance activity types can be added if required.

Value categories are intervals for cost elements and are required to
update the Plant Maintenance Information System and the Customer
Service Information System.

A value category should represent a cost element group for reporting

purposes.
Assign cost element groups to the defined value categories for cost
reporting purposes.
Assign a planning plant to a maintenance plant. Perform this activity for
each maintenance plant if there are multiple maintenance plants.

Defines a plant as a maintenance planning plant.

Define whether one (collective) purchase requisition be generated for

external material and operations for each order, and also whether
reservations or purchase requisitions relevant to materials planning
should be generated when an order is created or only when the order is
released.

Define whether one (collective) purchase requisition be generated for

external material and operations for each order, and also whether
reservations or purchase requisitions relevant to materials planning
should be generated when an order is created or only when the order is
released.

Define whether approval is required for each plant and maintenance

order type combination. This setting, along with the configuration of the
workflow using the "Manage Workflows for Maintenance Orders" app, will
dictate the workflow process.

Phase control code allows you to control the transition of phases. If you
set a phase control code for a maintenance order for blocking a phase,
the system will not allow you to transition to the phase until you reset the
phase control. Phase control codes can be set for order headers and
operations.
 Define one or more prioritization profiles, which would then be assigned
to a particular notification type and plant. Each prioritization profile would
then reference a consequence category group so that the system can
display a list of prioritized consequences, with a likelihood for each
consequence. This is used in conjunction with the configuration to define
the consequence categories, consequences, and likelihoods.

Event prioritization enables you to assess priorities based on

consequence categories, consequences, and likelihoods. When you
select consequences and likelihoods while creating a maintenance
request, the system calculates and suggests the applicable priority for
the maintenance request. This will provide contextual information to the
screener.

For example, if oil is dripping from a pump in a plant, you can create a
maintenance request for the technical object. Using prioritization, you
can specify that it is a high priority equipment which is responsible for
core drilling tasks and, if it is not repaired within two weeks, it could lead
to total asset damage. Based on these details, the system suggests
‘Very High’ as the priority. This activity is maintained as a configuration
step.
 Question Level

Are there defined processes (manual paper based,

manual system entry, automated) that are followed in the
L2
event of a machine breakdown to perform corrective
maintenance?

How is the planning, scheduling, and execution of

L2
preventative maintenance tracked?

Do you want to make use of the system's automatic

functions for generating the structure when you create L2
functional locations?

Do you want to assign pieces of equipment and

functional locations to the technical object types that you L3
have created?

Do you want to fine maintenance planner groups

L3
separately for each maintenance planning plant?

What object categories do you want to maintain by

L3
means of the ABC indicator?

What sort fields do you want to maintain on maintenance

L3
plan?

What priority types do you want to maintain? L3

 Define plants sections that need to be maintained? L2

What categories do you want to maintain? L3

What number ranges do you want to maintain? L3

How many different profiles are required, and what

default values need to be defined, for use during the
procurement of external services or materials? For L3
example, different purchasing groups might be desired
when procuring materials compared to services.

What default values, if any, do you want to include when

generating an order? This would include previous
definitions around profiles for external procurement of L3
materials or services, order profile, and a default quantity
unit for external processing.

For each maintenance order type (for example,

Corrective Maintenance, Preventative Maintenance,
Unplanned Maintenance, etc.), what is the default L3
maintenance activity type that should be proposed when
the order is created?
 Typically, only a subset of the defined maintenance
activity types should be identified as valid maintenance
activity types for each particular maintenance order type. L3
What are the possible maintenance activity types that
need to be assigned to each maintenance order type?

What activity types are required (for example, Fault

Clearance, Preventative Maintenance, Major Overhaul,
etc.) to identify the type of maintenance work for each
L3
maintenance order? Are additional maintenance activity
types required that are not covered by the predefined
types in the system?

What value categories need to be added to the list of

default value categories to represent the various cost L3
elements required by Finance and Controlling?

Which cost element group (from Controlling) do you want

L3
to assign to each of the value categories?
Which planning plant is used to execute the
L2
maintenance planning for each maintenance plant?
Is maintenance planning performed centrally by one
plant or does each plant execute their maintenance L2
planning independently?

Do you want to generate an internal purchase requisition

for each external operation and external material, or one
L3
collective purchase requisition for all external operations
and materials?

When should purchase requisitions be generated? On

L3
order creation or on order release?

Do you require approvals to be implemented for any

L3
plant / maintenance order type combination?

Is there a need to block the movement of maintenance

orders (based on maintenance order type) as it L3
progresses from one subphase to another subphase?
There are multiple steps to perform in this configuration.
The goal is to define a list of prioritization profiles. When
we define a prioritization profile, it contains a reference
to the consequence category group, notification type,
and plant, such that when a priority assessment is
triggered for a notification at a plant, the system
searches for a matching profile.

For each prioritization profile, we also associate a

consequence category group, which contains a set of
L3
consequence categories (defined in SSCUI 103793)
within it.

For each of the consequence categories in the group,

we can assign a UI position such that the consequence
categories will appear on the UI in the sequence that is
defined here.

Finally we assign a priority to each of the consequences

and likelihoods that are possible.

There are multiple steps to perform in this configuration.

The first step is to define the consequence categories.
There are four categories pre-configured (People, Asset,
Environment, Reputation) in the system. If additional
categories are required, a new entry can be created.

The second step is to define the consequences that will

L3
be assigned to each of the consequence categories.
Again, there are pre-configured consequences assigned
to each of the pre-configured consequence categories,
but additional entries can be created.

The third step is to define the different ranges of

likelihoods that these occurrences could happen.
 Solution Customer's Response

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition

SAP S/4HANA Cloud, public edition