Week 3: Realization (Architect/Developer) Unit 1: Building ...

Week 3: Realization (Architect/Developer)

Unit 1: Building Work Packages

2PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Business

Process Owner

Solution

Architect

Build Team

(Developer,

Consultant)

Test

Manager

Create work package

Develop, configure, unit

test

Document work item &

progress

Defect correction

Release work item

Plan & execute SFT, FIT, UAT, RT

Assign work items & build

teams

Fit / Gap WS for

requirements

Release

Manager

Hand over release to customer

Build, test and deploy release

PMO

Manage defects

Manage hypercare

Create project plan

▪ Manage waves and sprints▪ Track project readiness, issues, and risks▪ Manage scope change

Manage Q-Gate deliverables,

sign-off

Manage show & tell

▪ Project plan

▪ Release, waves, and sprints

▪ Process model

▪ Application landscape

▪ Requirements and gaps

▪ Functional specification

▪ Config. guide, test cases

▪ System landscape

▪ Tech. design paper

▪ Dev. objects in transports

▪ Test request

▪ Test plan

▪ Release

Building Work Packages

Process flow Focused Build – Requirements-to-deploy

Sprint Wave

Demos Focused Build/02 Search and assign Req/project/PR_DC65E3D1EF3D748A/start_guided.html

Demos Focused Build/05 Process Work Item/project/PR_BDAFF11A92818999/start_guided.html



Demos Focused Build/07 Track Test Progress/project/PR_278CC3B691537F87/start_guided.html

Demos Focused Build/04 Create Work Item/project/PR_41FC3EB898FFF4BB/start_guided.html

Demos Focused Build/01 Create Requirement/project/PR_39CC7DD8FE78A994/start_guided.html

Demos Focused Build/06 Track Project Progress/project/PR_7209C80D204A83B6/start_guided.html




Release planning: roles and responsibilities

Detailed

Release Plan

Based on Wave

2. Prioritize product

backlog

5. What would you like

in the release?

6. Scope release:

Build logical and technical

packages

Busin

ess

Resp

onsib

ility

IT

Resp

onsib

ility

Bu

sin

ess A

na

lyst

Arc

hitect

High-Level

Release Plan

Based on Project

1. Define product

backlog

3. Analysis of

dependencies

4. Estimate product

backlog

Create requirement

based on business

process

Use value points

and priority to rankApprove/

postpone

requirements

Create work

packages

Use effort to

estimate



Define work package responsible: work package owner/architect

Product

Backlog

Configuration (Fit)WRICEF /Gap

Developments

Document the

backlog items from

business

perspective

Requirement

Work Package

▪ Backlog with requirements represents list of

requirements that need to be delivered to the business

▪ Work package owner/architect

– takes the approved requirements and creates work

packages

– assigns the work package to a Build project

▪ Work package owner/architect in collaboration with the

Build project lead assigns the work package to a wave

▪ Architect starts detailed work package scoping

including work package classification



Product backlog in Focused Build

Product Backlog

Requirement

Requirement

Requirement

Work

Package

W I

W I

W I

W I

Fit/Gap RequirementWork

PackageWork Item

Business Analyst Architect

Communication

▪ To efficiently document requirements, an IT expert, the architect, should take part in the FIT/GAP workshops. The

architect knows the right granularity of a work package and can classify a requirement correctly as Gap, WRICEF, Fit, or

Non-Functional, for example.

▪ Tailoring work packages is key to the Focused Build methodology. To address the business needs correctly, the architect

should contact the responsible business analyst and check if his understanding of the requirement is correct.



Launchpad and tasks with Focused Build for the solution architect

▪ Outputs:

– Work packages

– Functional

specification

– Work item

– Work item/task

distribution to

development

– Realize

▫ Create and upload functional specification

▫ Scope and distribute work details

▫ Test case preparation for FIT and AT

▫ Process test defects

– Deploy

▫ Tidy up Solution Documentation

▫ Finalize work items

▪ Project roles:

Work stream lead, integration architect, functional

expert

▪ Responsibilities:

– Detailed design of processes that maps to the

current or future process, application, and system

landscape, proposals for software decisions

– Review business processes and mapping into IT

architecture, analyze requirements for specific

development needs or integration requirements

▪ Tasks:

– Prepare

▫ Prepare process structure for Fit/Gap workshops

– Explore

▫ Track requirement detailed info

▫ Define build activities based on requirements

▫ Check Q-Gate for Explore phase completed

Solution

Architect



Work packages and their relation to other elements

Work Package Work ItemsProject

define scope

for project

break down into

1..n for execution

General Planning Execution

Process Model

defines

requirements

is linked to

process model

Epic

Corresponding to Agile



Attributes of the work package

Related People

Effort Estimations

Related Business

Process(es)

Related

Documents

Project Information Planned Dates

Implementation

Scope

Wave Assignment

Completion Status Status Tracking

Work Package



Focused Build methodology – Status flow

Unit Test

New

Single Functional Test & AT

Approved

Created ScopingIn Develop-

ment

To Be

Tested

Successfully

Tested

Handed Over

to ReleaseProductive

In

RealizationRealized

To Be

Tested

Successfully

Tested

Req

uir

em

en

tsW

ork

Pa

cka

ge

Wo

rk Ite

m

Created

Scope

Finalized

Handed Over


In Develop-

ment

Productive

To Be

Developed

Discovery Team

WP Owner

Test Coordinator

WI Owner

= Automated action

= Manual action

IT,RT



Demo



Create work packages (1:1 or 1:n relation of requirements to work packages)

John DoeApproved

Option 1: Create one work package

Option 2: If a requirement cannot be

developed in one wave, create

additional work packages

Thank you.

Contact information:

[email protected]

© 2021 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/trademark for additional trademark information and notices.

www.sap.com/contactsap

Follow all of SAP

http://www.sap.com/trademark

https://www.sap.com/registration/contact.html

https://plus.google.com/+SAP

https://www.linkedin.com/company/sap

https://www.youtube.com/user/SAP

https://twitter.com/sap

https://www.facebook.com/SAP


Unit 2: Project Documentation


Project Documentation

Result: Work packages are created and documentation is assigned

Requirements

Wave

Work Package

1:m

Functional

Specification

Test Case

Interface

Library

Configuration

Library

Process Step Library

Development Library

Executable Library

Processes

Pro

cess Created

Scoping

Rejected

Draft

Approved

Postponed

▪ In Focused Build, we limit documentation to what is

really required

▪ So there needs to be a document describing what

needs to be customized and tested

▪ The availability of the functional specs can be

tracked via the Solution Readiness Dashboard

Dashboard


dropDoc integration to work package and work item applications

Technical Design

Process Steps

Developments

Executables

Business Processes

The decision where the dropped document will be stored is made in the background by

dropDoc and based on the standard document type configuration e.g.:

▪ Functional Specification will be stored at <Step origin>

▪ Single Functional Test at <Step origin>

▪ Technical Design at development or executable elements

▪ Use Case at <Step reference>

DEFINE DOCUMENT


Functionality of dropDoc



Solution Documentation KPI

Work Package

Created

Scoping

Scope FinalizedHanded Over to

Release

Productive

Postponed

Rejected

To Be Developed

Scope Change

To Be Tested

SuccessfullyTested

Completed

Document KPI

Functional specification availability In Progress

Review

Released

Functional

Specification

Interface

Specification




Work Package

Created

Scoping


Release

Productive

Postponed

Rejected

To Be Developed

Scope Change

To Be Tested

SuccessfullyTested

Completed

Document KPI


Review

Released

Functional

Specification

Interface

Specification



myDocuments: owned by me

23

▪ Selection of documents which are:

– Owned by me

– Processed by me

▪ “Owned by me” presents selection of documents

for which your user is assigned as owner

– Created by you

– Assigned to you as owner



Document area with drag-and-drop area

Refreshes the display of documents in the document area

Creates a document based on a template. The origin storage

is decided based on the document type configuration

Status change of selected document

Delete the selected documentBrowse and select the document from your

PC storage

Search of documents and possibility to assign to currently

selected structureSorting and filtering in document area

Connection of already available document to the

work package or work item

Navigate to memory location of selected document

in column browser of Solution Documentation


Configuration GuideConfiguration

Guide Template

Drag &

Drop

Process

Down-

load


Maintain and upload the configuration guide



Change control in document management: Focused Build

Work Item

▪ Inherits the structure assignments and documents from work

package

▪ Offers the only possibility to change process structures and their

documentation in Development branch

▪ Allows to create technical documentation and functional test case

descriptions

Work Package

▪ Inherits the structures from requirement

▪ Allows to create or edit structures (business processes, process step

reference, interface reference, or library elements) in Design branch

▪ Allows to create or edit documentation attached to scoped structures

in Design branch

Requirement

▪ Can refer to a structure like business process, process step

reference, interface reference, or library elements

▪ Cannot change content in the branch; description is attached to the

requirement on Attachment tab. The attachment can be based on a

document type prepared for requirement attachments



Demo



Process management – Test management integration

Application

dropDocs integration to work package and

work item

Feature details

▪ Availability of test steps in drop area

▪ Test management attributes “additive” and

“exclusive” and their impact on test case

visibility in dropDocs is integrated into drop area

Use Case

Test steps can be assigned to the work package

and work item as relevant test cases.

Can select just those test cases that will finally be

visible in test plan generation.

Focused Build



Documentation KPI

Overall KPI rating shows a summary of all

defined KPIs for all relevant structure

ratings. You can define whether the KPI will

be summarized by following worst or best

case principle.

KPI rating per structure element shows which

document types are required for which

structure level. The rating is dependent on

the document status in relation to

WorkPackage/Item status. You can specify

the concurrent document types per KPI.

WorkPackage/WorkItem document rating

shows the status of all overall KPIs as a

summary. It follows the worst case

principle.

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 3: Scoping Work Items


Scoping Work Items

Terminology mapping SAP Activate – Focused Build

Release

Fit/Gap

analysis

WS

Gap

Fit

Prioritized/

ranked, rough

effort estimation

Require-

ments

Gap,

WRICEF, Fit

(only

configuration)

Non-

functional

requirements

Functional

analysis &

release planning

(aggregation or

splitting)

duplicates

eliminated

Work

Packages

Gap,

WRICEF, Fit

(config) Non-

functional

requirements

Work

Item

Work

Item

Work

Item

Product Backlog

Sprint planning

(which dev team,

which order)

Time

Content

WavesSprints

Sprints

Release EpicsUser Stories

User Stories


Scoping Work Items

Two types of work items

NC (Normal Change)

GC (General Change)

Work item (NC) → includes the transportation management

▪ To be used for development of WRICEFs or gap development

▪ To be used for configurations

▪ Allows the creation of transport requests (customizing,

workbench)

▪ Non-ABAP deployments are supported through CTS+

Work item (GC) → is not related to software deployment

▪ To be used for non-functional work activities

▪ To be used to simply get documents released to the next branch,

e.g. test cases

All work items of a work package, independent of type,

have to be processed and successfully tested to get the

work package released for testing!


Scoping Work Items

Background: Focused Build methodology – Status flow and branches: standard workflow

releaseNew

Unit Test

Single Functional Test & FIT & UAT

Test

Confirmed

In Develop-

ment

To Be

Tested

Successfully

Tested

Hand Over


Realized

To Be

Tested

Successfully

TestedCreated

Hand Over


In Develop-

ment

IT,RT

Productive

To Be

Developed

Development Branch Production

Branch

Upload Tech Design to WI Type NC

(Spec. Status = Released)

= Automated action

= Manual action

Upload Test Cases

(Test Case Status = Released)

Req

uir

em

en

tsW

ork

Pa

cka

ge

Wo

rk Ite

m

Design Branch

Approved

Created Scoping

In

Realization

Scope

Finalized


Scoping Work Items

Maintain the basic data of the work item: change type

Choose a sprint of the wave

(assigned with the WP)

Choose Type (GC) = General Change if

you do activities without transports

Choose Type (NC) = Normal Change if you

like to transport customizing or ABAP code

Assign a developer

or dev team

Select the documents

that will be transferred

from the WP


Scoping Work Items

Work items and their relation to other elements

Work Package Work ItemsProject

define scope

for project

breakdown into

1..n for execution

General Planning Execution

Process Model

is linked to

process modelUser Story

Corresponding to Agile

Content and Scope


Scoping Work Items

How to find all of the work items you are assigned as owner

Choose role

Developer

Choose tile

My Work Items


Scoping Work Items

Demo


Scope Work Items

Creation of work items

Applications

My Work Packages

Feature details

▪ Create work items in work package in

status “To Be Tested”

Use Case

Early single functional test: It is possible

to create work items to upload test cases

into WPs still in the status “To Be Tested”.

So there’s no need to return to status

Scope Extension to create the work item

there.


Scope Work Items

Improved scoping usability

Applications

My Work Packages

Feature details

▪ Improved scoping usability

Use Case

To scope work items for work

packages with many process

structure elements and

documents assigned, it is

helpful to have a Select All and

drill down functionality per

business process

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 4: Development and Configurations


Development and Configurations

Focused Build process flow – Requirements-to-deploy

Business

Process Owner

Solution

Architect

Build Team

(Developer,

Consultant)

Test

Manager

Create work package

Develop, configure, unit

test

Document work item &

progress

Defect correction

Release work item

Plan & execute SFT, FIT, UAT, RT

Assign work items & build

teams

Fit / Gap WS for

requirements

Release

Manager

Hand over release to customer

Build, test and deploy release

PMO

Manage defects

Manage hypercare

Create project plan

▪ Manage waves and sprints▪ Track project readiness, issues, and risks▪ Manage scope change

Manage Q-Gate deliverables,

sign-off

Manage show & tell

▪ Project plan

▪ Release, waves, and sprints

▪ Process model

▪ Application landscape

▪ Requirements and gaps

▪ Functional specification

▪ Config. guide, test cases

▪ System landscape

▪ Tech. design paper

▪ Dev. objects in transports

▪ Test request

▪ Test plan

▪ Release

Sprint

Demos Focused Build/02 Search and assign Req/project/PR_DC65E3D1EF3D748A/start_guided.html




Demos Focused Build/07 Track Test Progress/project/PR_278CC3B691537F87/start_guided.html

Demos Focused Build/04 Create Work Item/project/PR_41FC3EB898FFF4BB/start_guided.html

Demos Focused Build/01 Create Requirement/project/PR_39CC7DD8FE78A994/start_guided.html

Demos Focused Build/06 Track Project Progress/project/PR_7209C80D204A83B6/start_guided.html




Launchpad and tasks with Focused Build for developer and consultants

▪ Project roles: developer, consultant

▪ Responsibilities:

– Execute assigned development or configuration tasks

– Perform technical design

– Perform unit test

– Process assigned defects

– Create defect correction if required and proceed

▪ Tasks:

– Realize

▫ Plan and document build activities

▫ Start build activities and document changes

▫ Perform unit test

▫ Process defect correction

▪ Outputs:

– Technical design/specification

– Configuration document

– Development/Customizing objects in transports

– Defect corrections


New

Unit Test

Single Functional Test & UAT

Test

Approved

Created Scoping

In

DevelopmentTo be tested

Successfully

testedProductive

In RealizationRealization

Completed

To be tested Successfully

tested

Wo

rk P

acka

ge

Wo

rk Ite

m

Created

Scope

finalized

Handover to

releaseProductive

In

Development

IT,RT

Productive

To be

Developed

Transport

DEV PrePRD PRDQAS

TOC*

create Release Import

(manual)

Transport

Req

uir

em

en

t

Handed over

to release

* Transport of Copies

Transportbatch import Release Import

(manual)

Defect (batch)


Focus Build – Transport handling with ToC and unit test in QAS



Work items – Confirm successful unit test – TR is released and imported



How to record your effort

On the Effort tab you can record

your effort.

Depending on your role, you can

record your effort per time unit,

time stamp, and with a short

description.

The User column is filled out

automatically.



Tasks in work item

▪ Decompose work items into small

tasks

▪ Tasks help to structure scrum

development

▪ Set status of the task in daily

scrum meetings

▪ Use scrumboard integration to

visualize work items and task

status


To be done means that:

- the work item is not in status: In Development or

- the tech. design or configuration guides haven't been

assigned to work items or

- the document is not released

- and the due date for these documents has not yet been reached

A technical design document describes the

result of a technical activity in an application,

e.g. how a BAdI, report, interface has been

configured, developed, or customized


Documentation-relevant tiles – Technical Design



Demo



Work items – Set status In Development

Set your work item to

status In Development



Maintain the work item: Create Transports

Choose Tab Transport

Press to Create

Transport RequestPress to

login target

system




Select the transport type

Short description is

automatically maintained =

ID of WI + Description

→ Don’t change that!

Maintain the transport owner

Maintain tasks for other

team members

John Doe




Result: As there was a workbench and a

customizing request selected beforehand,

you got 1 transport for each type created



Do your customizing or development in managed system



Release tasks in managed system

Note: Only release tasks –

never release transports!

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 5: Unit Testing


Test Types Test Level Test Requirement Definition Test System

Unit Test Sprint Work Item

(Tech. Design)

Technical feature test to ensure that the feature was

implemented correctly.

QAS

Single Functional Test Wave Work Package

(Func. Spec)

Business function test to ensure that the feature was

implemented correctly. Depending on the project

approach, the singe functional test might be informal

(without test plan creation).

QAS

Acceptance Test Wave Single Work Packages

(Requirement)

Validation of requested functionality by requestor. After

validation, corresponding work packages and defect

corrections would be ready for handover to release. This

is the most important test, as after setting the work

package status Hand Over to Release, all assigned

transports will end in PRD system.

QAS

Functional Integration

Test

Project

(Optional)

Related Work Packages

Process with

Requirements

Early validation of modular processes. QAS

Functional Integration

Test

Release

(Final)

E2E Processes E2E tests of the new or extended functionality validating

the end-to-end business process. Final hands-on

validation by business users.

PRE

Regression Test Release Productive Processes Test of productive processes or functions. PRE

Unit Testing

Test types


Unit Testing

Standard workflow

FIT, RT

Unit Test

ProductiveNew

Single Functional Test & AT

Approved

Created ScopingIn Develop-

ment

To Be

Tested

Successfully

Tested

Handed Over

to Release

Productive/

Completed

In

RealizationRealized

To Be

Tested

Successfully

Tested

Req

uir

em

en

tsW

ork

Pa

cka

ge

Wo

rk Ite

m

Created

Scope

Finalized

Handed Over

to Release

Productive/

Completed

In Develop-

ment

Completed

To Be

Developed

Development BranchDesign Branch Production

Branch= Automated action

= Manual action

= WI with General Change

= WI with Normal Change

In Repair


Unit Testing

Start unit test by importing transport of copies into QAS

Steps

1. Developer selects work item.

2. Developer performs action 'Pass to Test':

− Transport of Copies (ToC) will be imported

to QAS system automatically

− Unit test can be performed in QAS

Effects

▪ In Solution Readiness Dashboard,

development will be shown as completed for

this work item.

Recommendations

▪ Please make sure the unit tester is not the

same user as developer.


Unit Testing

Perform and confirm successful unit test

Steps

1. Tester executes unit test in QAS.

2. Tester selects work item.

3. (Optional:) Tester documents test results.

4. Tester performs action ‘Confirm Successful Test’.

Effects

▪ In Solution Readiness Dashboard the unit test will be

calculated as completed for this work item.

▪ The work package will be changed to ‘To Be Tested’

automatically when all its work items are successfully

tested.

▪ Transport(s) (TR(s)) will be released automatically and

could be imported to QAS via schedule job defined by release manager.

Recommendations

▪ Test results can be maintained as ordinary text on the Text tab using text type ‘Test Report’.


Unit Testing

Check Q-Gate for Realize phase completed

Check unit-test milestone in Solution Readiness Dashboard

Steps

1. All requirements should be completed.

2. All functional specs should be completed.

3. All technical design should be completed.

4. All development should be completed.

5. All unit tests should be completed.


Unit Testing

Demo


Unit Testing

Mass changes for work packages/items

Start in

launchpad

Select filter

criteria

Set the value for

all selected

documents

Mass changes are possible for

▪ Work packages

▪ Work items

– Normal

– general

▪ Defect corrections

▪ Requirements

▪ Use the filter criteria to select the required documents

▪ Select one or multiple documents to set the same value

▪ Change the field


Unit Testing

Mass changes for work packages/items

Set the value

for all selected

documents

Save the changes

which are marked


Select Functional Specification

Unit Testing

How to select a configuration guide template

Create new document

Choose Documentation

In case of several

process structures,

choose the relevant one


TD_PTP_OROQ1Technical Design

Template

Drag &

Drop

Process

Down-

load

Unit Testing

How to create and maintain the document


Decide whether to create a

“New Version” or “New File”

of the document

Unit Testing

Upload the locally maintained document


Unit Testing

How to add test instruction etc.

On the Texts tab you are able

to maintain different text

templates e.g. Test Instruction.

Additionally, the text

assignment block updates by

system messages, e.g. status

changes…


Unit Testing

How to add test instruction etc.

Select text template from

dropdown list and enter text.

Click “Save” at lower right.


Unit Testing

Handover to testing and transport in Q-system

By choosing action Pass to Test, a transport

of copies is automatically created and

imported via a batch job in the Q-system


Unit Testing

Work items – Confirm successful unit test – TR is released and imported by batch job

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 6: Solution Readiness Dashboard – Part II


Unit Test

Handover

to releaseProductiveNew

Single Functional Test & UAT

In

Developmen

t

To be tested

(Unit)Test

Confirmed

Solution Readiness Dashboard – Part II

Focused Build methodology – Status flow and milestones

Approved

CreatedRequired

Analysis

In Develop-

ment

To Be

Tested

Successfully

Tested

Hand Over


In

RealizationRealized

To Be

Tested

Successfully

Tested

Req

uir

em

en

tsW

ork

Pa

cka

ge

Wo

rk Ite

m

Created

Scope

Finalized

Hand Over


In

Developmen

t

IT,

RT

Productive

To Be

Developed10 25

40 50

706020

35

Upload func. spec (spec. status = Released

Development

Set test cases to status Released

Unit TestTech. Design

Func. Spec.

Upload tech design (status: Released)

and/or test cases in any status



Standard milestones and Q-Gates – Milestones reflected in dashboard tiles

10

25

30

35

40

50

60

Milestone ID Milestone Dashboard Measure

BP_REVIEW Requirement reviewed Requirements Backlog BR with WP of wave assigned

FUNC_SPEC Functional specification completed Functional SpecificationWP has released “Functional Specification”

assigned

DEMAND_PLAN Wave scoping completed Requirements Backlog WP in status “Scope completed”

BUILD_START Sprint in progress Development WI in status “In development”

TECH_DESIGN Technical design completed Technical Design WI has released “Technical Design” assigned

BUILD_FINISH Build completed Development WI in status “To be tested”

UNIT_TEST Unit test completed Unit Test WI in status “Successfully tested”

ITRBUILD_FINISH Wave build completed Current Wave Progress WP in status “To be tested”

SFT_FINISH Single functional test completed n.a. n.a.

20

70

= Milestone check = Milestone check with KPI



Solution Readiness Dashboard in Realization phase

3035 50

60 20

25

10



Navigation example – Work packages

By clicking the Work Packages tile you get a

list of all work packages of your workstream

In the detailed list view you can control the

status of each work package and item

To check the detailed

work package content,

click the work package

number or description

To check the assigned work

items, click the number of

assigned work items



Documentation-relevant tiles – Functional Specification

Note: Dates for milestones and Q-Gates are set by the central PMO in alignment with the customer.

They are maintained in the IT Project Management functionality of SAP Solution Manager.

They are synchronized with the work packages/items and the Solution Readiness Dashboard.

A functional specification document contains a configuration or development

request. Each work package needs to have a functional specification.

Non-technical work packages contain an empty placeholder document, a

functional specification substitute.

Here 3 of 30 functional specifications are overdue, because:

- the work package is not assigned to a wave and has no date

- or the milestone/date is already passed

Percentage of all your functional specifications according to

status and due date, e.g. here 3 of 30 func. specs are overdue



Documentation-relevant tiles – Technical Design

To be done means that:

- the work item does not have the status ‘In Development’ or

- the tech. design or configuration guide haven't been

assigned to work item or

- the document has not been released

- and the due date for this document has not yet been reached

A technical design document describes the

result of a technical activity in an application,

e.g. how a BAdI, report, or interface has

been configured, developed, or customized



Meaning of the Scope Change and Development tiles

Percentage of all work packages

which have not been part of the

planned content of release 1 –

not relevant for now

Completed development means that

this work item is ready for a functional

test and the Build Finished milestone

has not yet been reached



Meaning of the test-relevant tiles

Test Status shows the

percentage of all successful tests

(summary of all test types)

Defect Details shows how many

priority 1 or 2 defects are open

in the current wave

Note: There is a separate dashboard for all detailed test information

These work items don't have the

status Unit Test Successful,

but the milestone Unit Test

Finished has not yet been reached

Percentage of work items

according to status and due date



Demo



Solution Readiness Dashboard – Tiles relevant for the central PMO

Project Q-Gates and

milestones –


Project progress

diagram –

not relevant for nowDevelopments to be delivered

by standard SAP development –

not relevant for this projectProject Q-Gates and

Milestones -


Optionally, you can

maintain your personal

project risks and issues

The project status is set manually

by the PMO in collaboration with

the workstream lead



Preconfigured Solution Readiness Dashboard based on live data

Check the information icons to get a detailed

explanation of the tile calculation

No need to consolidate XLS sheets to get project reporting

▪ Next Q-Gate– How many workdays remain until the next Q-Gate?

▪ Work package, work item, and gaps– How many objects are assigned to the project?

▪ Requirements backlog– How many work packages are still open, which ones are

in progress, and how many have been rejected?▪ Schedule

– How many of the tasks in the current project are complete in relation to their due date (to-date target)?

▪ Risks– Number of risks rated acc. to status, impact, and probability

▪ Issues– Number of issues rated acc. to priority

▪ Scope change– Percentage of work packages that have been changed or

extended after the initial scope had been set▪ Effort increase

– Percentage of actual effort increase versus the originally planned effort at the start of the project

▪ Process area status– Status per process area of the project indicating which documents or activities are behind schedule (overdue)

▪ Overall status– Project status set manually by the project manager in cProjects of SAP Solution Manager

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 7: Conversion


Pivot at market speed: With unpredictable changes in

product demand and manufacturing supply chains, organizations need to dynamically reallocate resources to new mission-critical priorities or to quickly adapt to disruptions, enabled by digital business operations driven in real time.

You cannot afford to wait. These are the top 5 realities:

Champion cost savings: Cost pressures have intensified with the COVID-19 pandemic, making it critical to drive cost savings. A modern ERP delivers intelligent automation across your entire business, driving step-change improvements in productivity by unlocking new levels of efficiency and intelligent personalized insight to all employees.

Innovate before competitors: As past recoveries show, the winners re-innovate their business processes andmodels faster, deriving differentiated business outcomes in the context of theirindustry. Intelligent enterprises apply advanced technologies and best practices within agile business processes to make organizations more resilient, profitable, and sustainable.

Run in uncertainty: Running your business in today’s economic uncertainty requires a new ERP that provides instant insight across your end-to-end business operations so you can always analyze, collaborate, prepare, and plan for what’s next – and act immediately, from anywhere.

Grow with modern cloud ERP: The crisis has accelerated the shift to the cloud. With our new consumption models, you can now move more easily to our modern cloud and safeguard your current ERP investment, enabling continuous innovation and operational scalability with a low TCO. This enables a shift from capital expenditures to operating expenses and makes it easier to drive your business remotely.

1

3

2

4

5

Conversion

5 top reasons to move to SAP S/4HANA now


Conversion

The way to SAP S/4HANA – Which option to choose?

New Implementation

With a new implementation, you

build a new SAP S/4HANA

system.

Either you cut over to the new

system (the so-called “big bang”

scenario)

or

you migrate the individual

business units sequentially from

your legacy SAP ERP application

to the new system (“a phased

rollout”).

System Conversion

With a system conversion, you

turn your existing SAP ERP

system into an SAP S/4HANA

system.

Technically, the system conversion

is a one-step procedure with a

single downtime.

Selective Data Transition

With selective data transition, the

migration of relevant business

data from SAP ERP to

SAP S/4HANA is covered.

It balances the benefits of a

system conversion and new

implementation by combining a

redesign of business processes

and retaining historical data in the

new business reality.


Conversion

Focused Build supports all three options

System Conversion

Requirements-to-Deploy process (available since

SP0 of Focused Build)

Upload of simplification items and conversion

activities as starting point for the Requirements-to-

Deploy process (available as of SP6 of Focused

Build)

Selective Data Transition

Tailored approach either with elements of system

conversion or new implementation scenario.

Data migration from ERP to SAP S/4HANA requires

an additional DMLT service

New Implementation


Conversion

Analyze your existing SAP ERP landscape

Analyze

usage and configuration

data of your current

landscape

Determine

conversion compatibility

and required preparation

steps

Access

results in interactive

dashboard for easy

analysis


Conversion

Covered aspects

Active Business Functions

Find out how many

business functions are

active in your system and

whether they are

compatible with

SAP S/4HANA.

Add-On Compatibility

See how many add-ons

are installed in your

system and whether

they are still compatible

with SAP S/4HANA.

Recommended SAP

Fiori Apps

Identify the SAP Fiori

apps that best fit your

needs based on your

historical transaction

volume and usage.

Business Warehouse

Extractors

View how many

extractors for SAP

Business Warehouse

exist in your ERP

system and if they work

with SAP S/4HANA.

Simplification Items for

SAP S/4HANA

View new and updated

data structures /

architectures in SAP

S/4HANA to determine

if they are relevant to

your processes.

Business Process Analytics

Analyze the state of your

processes to determine

any clean-up requirements

before migrating to

SAP S/4HANA.

Custom Code Analysis

Analyze the impact of

custom code by knowing

which SAP objects have

been changed or removed

in SAP S/4HANA.

SAP Custom

Development Projects

View solutions built for

your business by SAP

Innovative Business

Solutions to evaluate if

needed with

SAP S/4HANA.

Data Volume

Management

Plan for migration with

insight into the size of

your existing database

and archiving potential

for 12 or 24 months.

Sizing for SAP S/4HANA

Estimate your sizing for

the initial installation

based on the existing

system and after a data

clean-up.


Conversion

Integration of SAP Readiness Check in Focused Build

SAP

Readiness Check

for SAP S/4HANA

Focused Build

Excel

Export/Import

Simplification Item

Management UI5 App

Evaluation and

Categorization of

Activities

Focused Build

Project

Focused Build

Requirement

Focused Build

Work Package


Conversion

Focused Build – Architecture overview system conversion SP7 and SP8

SAP Readiness

CheckSimplification Item

Management

SimplificationItem

ConversionActivity

SAP Activate

Template Project

Plan

Requirements / Work Packages / Work Items

Requirement

Work Package

Work ItemProcess Management

Design Document

Test Case

Test Suite

Test Plan Test Package

Simplification Item

Management Dashboard

Burndown Chart

Status Pie Charts

Project Management

ActivatePhases

Wave

Sprint

Mile-stone

Activate Tasks

Source for

Process

Management

1) Library

Generation

2) Best Practices / Model Company

Usage of

Retrofit for

Transport

Handling

Solution Readiness Dashboard / Test Suite Dashboard

Req / WP / WI Totals

Document KPIs

Project Status

Project Schedule

Development Status

Unit Test Status

Test Execution Status

Defect Status

Documentation Reporting

Dashboard

Business Process Readiness

Iterative wave-

planning based on

conversion phase

(available from SP8)


Conversion

Demo


Conversion

Outlook: SP8 – What’s New

▪ More flexibility options:

– Combine several Conversion Activities in one

Follow-Up Document

– Assign / Reassign Conversion Activities to

Follow-Up Documents

▪ Integration in Mass Change Application – easier

Release Backlog and Wave Backlog Planning

▪ Integration to custom transaction types

▪ Enhanced Logging-Information

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 8: New Features Since SP03

What’s New with Focused Build SP4?

Work Package & Work Item


My Work Items, Solution Readiness Dashboard - New with SP04

WI Scoping – Non-Functional Work Item

Applications

My Work Items, Solution Readiness Dashboard

Features

• New WI Classification ‘Non-Functional’ where the KPI for the

Technical Design is not checked (better reporting)

• For these ‘Non-Functional’ Work Items, the corresponding KPI on

the Dates tab automatically get’s the value ‘N/A’

• The WI Classification is moved from Work Package ‘Details‘ to

‘Scope’ screen in form of a drop-down

• The WI Classification drop-down values are dependent on the WP

Classification (improved usability)

• Enhanced Work Item reporting in Solution Readiness Dashboard tile

Work Items according to the WI Classifications

Use Case

The Non-Functional Work Item allows to upload additional documents

like Test Cases in a late WP status, e.g. To Be Tested.

It prevents the unnecessary measurement of KPIs and so prevents

misleading red ratings in the Solution Readiness Dashboard for the

Technical Design.


My Work Packages, My Defect Corrections - New with SP04

Improved Search for Systems

Applications

My Work Packages, My Defect Corrections

Features

• Improved Search for Systems when creating a

General Change, Normal Change or Defect Correction

• New switch for complete search of systems or systems part of the

Release

• Improved display of the results (SID and Client separated)

• Text fragment search enabled

Use Case

Creating a Work Item end users are often not aware, which systems

are relevant. Therefore we limit the search for system results by

default for:

• General Changes -> to all systems which are part of the Change

Control Landscape and Release

• Normal Changes / Defect Corrections -> to the productive systems

which are part of the Change Control Landscape and Release


My Work Packages - New with SP04

Test Management Tab – Support edit functionality

Applications

My Work Packages

Features

In Test Management tab the edit functionality is now

supported:

• Assign Test Plans or Packages to the list

• Unassign Test Plan or Package from the list

Use Case

To give transparency for the Architect, the Test

Management Tab lists the related Test Plans and

Packages.

In case of a 1:1 relationship of Work Package and

Test Package, the assignment is done automatically

in Assignment Analysis. In case this Work Package

assignment was incorrect or changed, the Architect

can now manually remove and/or add Test Plans or

Test Packages.


Requirements Management – new with Focused Build SP05

Requirement Upload Report

Applications

Requirements Management, Upload report

/SALM/Requirement_Import

Features

• Additional options how to handle the

Requirement Owner field

• Overwrite existing with current logon user

• Keep original Business Partner

• Check and take-over in case Business Partner

exists in source and target system

• Complete Requirements with current logon user in

case the Business Partner is not maintained

• Extended consistency checks

• Completeness of obligatory fields

• Duplicate Requirements

• Success of Process Structure mapping

(creation of standalone Requirement)

Use CaseThe extended checks ensure better data quality

and less clean-up effort after the upload


My Requirements, My Work Packages, My Work Items – new with SP05

Extended Change History

Applications

My Requirements, My Work Packages, My Work Items

and the related CRM Web UI

Features

The change history has been extended by the following

values

• Requirement

• Value Points, Effort Points, Local Flag

• Work Package

• Value Points, Effort Points, PPM Project, Wave, Dates

• Work Item

• Value Points, Story Points, Dates

Use CaseE.g. in My Requirements app several fields are open for

changes after approval. As it is compliance relevant, a

Change History is needed to see, if and who changed

the values at a later point in time.


Requirement Management, My Work Packages – new with SP05

Create Work Package - Solution Filter for Project Display

Applications

Requirement Management, My Work Packages

Features

Creating new Work Packages, you need to choose a project.

Now the Project selection is limited to Projects part of the

selected Solution

Use Cases

• Use Case 1:

In case in Requirements Management there is a filter set for one

Solution and you select one or more Requirements from the result list

-> in Project selection pop-up, only projects assigned to this one

Solution are displayed

• Use Case 2:

In case of standalone WP

-> in Project selection pop-up, all projects of all Solutions are shown

• Use Case 3:

In case there is no Solution filter selected and there are Requirements

of more than 1 Solution selected

-> pop-up informing, that it is not allowed to create Work Packages of

different Solutions

What’s New with Focused Build SP6



Work Package & Work Item – new with Focused Build SP6

Modified Preliminary Import Workflow

Applications

My Work Packages, My Work Items

Features

Work Items can only be preliminary imported to Production in case

there is a 1:1-relationship between Work Package and Work Item. As

soon as the Preliminary Import is requested in the Work Item the Work

Package now reflects this status as well.

Use Case

A Work Package should be treated as a complete unit where all related

Work Items are tested and deployed together. With the possibility of the

preliminary import workflow it was possible to bypass this idea which

led to inconsistent system landscapes, as parts of a Work Package

were already in Production System while other parts were still in

Development. With the limitation of the preliminary import option to 1:1-

relationships between Work Packages and Work Items we ensure

consistent system landscapes as a Work Package is always

transported and tested as a complete package.

WP

WI

WI


Work Item – new with Focused Build SP6

Reassignment of Work Items

Applications

My Work Items

Features

The Reassignment of Work Items is a functionality offered for the

Focused Build Tool Lead in exceptional cases to decouple and assign

a Work Item from one Work Package to another, e.g. in case a Work

Item cannot be finished in time while the other Work Items of the same

Work Package could be deployed to Production System.

Use Case

The reassignment-functionality is a powerful tool that must be used

with great care. To avoid inconsistent Work Packages / Work Items the

reassign-functionality is limited by the following points:

▪ The functionality is only available from the CRM UI

▪ Only Work Items before status ‘Handed over to Release’ can be

reassigned

▪ Reassignment is only possible if the related Work Package has more

than one Work Item assigned

▪ The target Work Package must be in status ‘to be developed’ or ‘in

Development’

▪ The required authorization object REASSIGN_WI is delivered by

default in the role of the Focused Build Tool Lead

WP WI



Display Long Text Information of Error Messages in UI5

Applications

My Requirements, My Work Packages, My Work Items,

My Defects, My Defect Corrections, My Risks, My

Requests for Change, My Change Documents

Features

When an error or warning message is raised in UI5-

application a link is visible in the popup to get the

helpful long text information displayed.

Use CaseSo far the valuable long text information of a warning or

error message were only available in the CRM UI. End

users need to jump from the UI5-application to CRM UI

to get this information displayed. Now there is an

additional link in the short text window of the message

available that opens the long text information directly in

the UI5-application.



Automated setting of completion rate to 100%

Applications


Features

When a Work Item or a Work Package is set to

‘Successfully tested’ the completion rate is set

automatically to 100%.

Use CaseThe completion rate is not always used by customers or

the project team. As a consequence the field remains 0

although the development of the Work Item has been

finished or the test of the Work Package was successful

which lead to incorrect reporting in the Solution

Readiness Dashboard. Also the tile ‘Current Wave

Progress’ shows a more accurate result if the

completion rate is automatically filled.



New validation for completed checklist

Applications


Features

When a Work Item or a Work Package is set to

‘Successfully tested’ it is checked whether all checklist

steps have been completed. If not an error message is

raised and the status is not set.

Use CaseA Work Package or Work Item can only be completed if

all related items are closed. Also checklist steps are

checked if they are finalized, if this is not the case the

completed status is not set. This caused problems in

the past as the Completed-status is usually set via the

Release Batch Import automatically after the successful

import in the Production System. An open checklist step

prevented this and led to manual extra work after the

Go-Live. With the new check we inform Developers and

Solution Architects at the right time about open items.



Show ToCs in Transport Tab in UI5 Application

Applications

My Work Items

Feature details

In the My Work Items Application it is possible to check directly the

information of a Transport of Copy created automatically by the system

in case the Work Item (NC) has been set to ‘To be Tested’.

Use Case

In the course of an implementation project developers are regularly

asking the Focused Build or Basis Team about the status of a

Transport Request as they are missing a configuration or development

in the Quality Assurance System. To get the information e.g. about a

non-imported Transport of Copy developers had to go to the Advanced

view in CRM UI to get the ID. With the new implementation the

information can be directly retrieved from the My Work Items

Application.



Activate Jump from UI5 to Transport details

Applications

My Work Items

Feature details

In the My Work Items Application it is possible to access directly the

Transport Request related information like included objects or

Transport Logs without making a detour via the CRM UI.

Use Case

The Transport Request Details are an important information for the

developers, e.g. to check the content of the different Transport Tasks,

perform syntax and completeness checks or to see the Transport Log

Information in case an import was not successfully imported. By having

the possibility to access these information directly from the My Work

Items application instead of going to the Advanced view in CRM UI we

increase the acceptance of the UI5-application.



Maintain effort - only allow hours and consulting days

Applications


Feature details

The maintenance of planned and actual effort is by default limited to

Consulting Days and Hours. Customers can enhance the list of

available time units themselves.

Use Case

The maintenance of Planned and Actual Effort was not unified in My

Work Packages, My Work Items and the CRM UI. In addition, the list of

available time units was confusing for the end users. Now, by default,

only Consulting Days and Hours are available for time maintenance in

all Applications. Customers can change or enhance the list via

customizing and also the sequence of the time units can be specified.



Maintain checklist - introduce save-button

Applications


Feature details

A Save-button has been introduced to ease the maintenance of the

checklist steps by avoiding save-roundtrips after every field-update.

Use Case

Checklist Steps help to perform and document required steps in the

processing of a Work Package or Work Item with a due date. Work

Packages and Work Items are delivered with a preconfigured checklist

profile that can be easily adjusted by customers via customizing. In the

My Work Package / My Work Item application the maintenance of the

checklist steps has been improved by providing Save- and Cancel-

Buttons instead of an automatic save-trigger after every field update.



Provide a Test Team in Work Item

Applications

My Work Items

Feature details

The new partner function Test Team is introduced that allows the

assignment of Work Items to teams instead of only single testers.

Use Case

As for the Development Teams, customers organize also their testers

in teams. As Work Items could be also tested not only by developers it

is required to make the assignment of Test Teams possible so that the

members of this team can organize their work according to availability

and current load.



Improve WP Checks for Project and Wave Selection – My WP App & Mass Change

Applications

My Work Packages

Feature details

When a Work Package gets a Solution Documentation Scope inherited

from the Requirement the Project Selection is improved. By default,

only Projects should be displayed that have this Scope assigned. When

the switch is set to Off additional projects without this scope, but from

the same solution are displayed. This will always ensure that the

project assignment is consistent.

Use Case

Scopes help the project team to split up a huge solution documentation

into smaller packages to support the users focusing on a specific

scenario, e.g. Order to Cash. This scope can be assigned to a project

as well. When now the Work Package gets a process step with a

specific scope, in the search help we offer by default only projects that

have this specific scope assigned. To be not too restrictive the option to

consider the documentation scope can be switched off to see other

projects.


Application

My Work Packages

Feature details

The new partner function Test Team is introduced that allows the assignment of Work Packages to teams.

Benefits / Use Case

As for the Development Teams, customers organize also their testers in teams. As Work Packages could be also tested it is required to make the assignment of Test Teams possible so that the members of this team can organize their work according to availability and current load. Also, the Test Team will be copied to the scoped Work Items


Provide a test-team in Work Package


Application

My Work Packages

Feature details

The new fields are taking over the already

maintained values as default values which can be

adjusted.

Benefits / Use Case

While the scoping process value points are taken

over from the Work Package. Afterwards value

and story points can be adjusted for distribution

over the scoped Work Items.


Provide Story and Value points via scope pop-up


My Checklist Steps


Application

My Checklist Steps is an entry point to access all

checklist steps to that a user is assigned to.

Feature details

▪ Switch between My Steps and Team Steps

▪ Filter possibilities

▪ Processing of steps in the overview

▪ Navigation to checklist step details

▪ Navigation to parent document

Benefits / Use Case

Central point to access all checklist steps you are

assigned to.

My Checklist Steps – new with Focused Build SP8

New application for Checklist Steps


Process Management


Process Management – new with Focused Build SP04

Composite interface and Test scripts

Application

dropDocs integration to Work Package and

Work Item

Feature details

• Possibility to address composite interfaces in

Requirement, Work Package and Item

• Visibility of test scripts (CBTA) and recognition

for KPI rating (CBTA + Test Steps)

Use Case

Completing of coverage solution documentation

objects, which can be handled by Focus Build.



Scope and structure scope popup

Application

Solution Documentation “Scope” integration into

Requirement to deploy and process scope popup

harmonization.

Feature details

• Possibility to select solution documentation

“Scope” on the process scope popup. This is

impacting the displayed content.

• Storage of the “Scope” information to all

selected structures on the scoping popup

and in the process assignment area.

Use Case

Simplification of structure assignments and

project selection for projects with assigned

Solution Documentation “Scope”.



Availability of dropDocs

Application

Availability of documentation tab for additional

CRM transaction types:

- Request for Change

- Standard/urgent change

- Defect correction

Feature details

• Possibility to access and change

documentation.

• No impact on KPI rating

Use Case

Unification of UI design for additional CRM

transaction types.


Process Management



Language recognition and performance improvements

Application

dropDocs integration to Work Package and

Work Item

Feature details

• Improvements on structure assignment popup

• Language recognition on documentation tab

• Performance improvements for document handling and KPI

Use Case

Visibility of already scoped structures on structure assignment

popup and visibility of maintained languages and translations.


Process Management


Application

dropDocs integration to Work Package and Work Item

Feature details

▪ Un-assign of structures in Work Package and Work

Item

▪ Move of structures in Work Items

▪ Status display and direct status change for Test

Steps

Use Case

Quick changes on Test Step status trough Work

Package and Item as well as harmonized un-

assignment of structures and documents.

Simplification of move structures between Work Items.


Status change for Test Step and structure related activities


Process Management



Reporting dashboard and handling improvements

Application

dropDocs integration to Work Package and Work Item.

Feature details

• Availability of Documentation Reporting

Dashboard

• Release check of structures in Work Items to detect

release conflicts

• FB specific related documents display per branch

• Customer status schema recognition for KPI and

Solution Readiness Dashboard as well as unlocking

of documents

Use Case

Simplification of activities around documentation

handling and reporting.



Documentation Reporting Dashboard

Application

Documentation Reporting Dashboard

Feature details

Using the Business Process Readiness report as part of

Documentation Reporting Dashboard you can detect the

current status of implementation from business process

perspective.

Running the report for design branch, it provides all

Requirements and Work Packages which are planed for the

selected scope. Executing the same selection for

development branch gives an overview about current active

implementation. Once the process arrived in production

branch, the report gives an absolute number of

Requirements, Work Packages and Items for certain scope.

Benefits

Simplified method to report on the current state of

implementation for a specific business process scope.



Release check

Application

dropDocs integration to Work Item.

Feature details

• Detection of all objects changed or created by

current Work Item

• Detection of all potential obstacles for Work Item

release before hand over to release.

Use Case

This functionality can be used as final documentation

check before handing over the Work Item to Release.



Focused Build specific related documents

Application

Solution Documentation

Feature details

• Visibility of new Focused Build specific related

documents:

• (FB) Request for Change

• (FB) Change Document

• Changes on visibility and counting method for

• Requirements

• Work Package

• Work Item

Benefits Better visibility of associated related documents to

selected structure.



Customer status schema and unlocking of documents

Application

dropDocs integration to Work Package and Work

Item.

Feature details

• Enablement to use customer specific status

schemas for document types

• Reflection of customer status values by KPI

calculation and Solution Readiness Dashboard

• Possibility to unlock locked documents directly from

Work Package or Work Item.

Benefits

Handling simplification to unlock documents and

extended flexibility in use of customer status values

for documents.


Process Management


Application

Business Process Readiness Dashboard is

improved by additional filtering capabilities.

Feature details

- Additional selection of business processes as

filtering criteria

- Display of project ID in the result table

Benefits / Use Case

Better results due to the extended filter possibility

and more information in the result table for

additional result processing.


Improvements in BP-Readiness Dashboard

https://ldcioft.wdf.sap.corp:44378/sap/bc/ui2/flp#Action-solDB&/bpreadiness


Application

dropDocs integration for to Requirements, Work Package and Work Items

Feature details

In case relevant structures for a certain Work Package/Item has been deleted in one of following waves:

- the deleted structure will be still displayed in the according Requirement, Work Package/Item

- Click on relevant document from WP/WI opensthe document in the version which was valid asthe WP/WI has been completed.

Benefits / Use Case

- Visibility of related but deleted structures.- Access to the correct document version once the WP/WI is completed


Display of deleted objects from Work Package/Item

https://ldcioft.wdf.sap.corp:44378/sap/bc/ui2/flp?sap-client=200&GUID=42010AEE-CF75-1EEB-A9CD-2364FFAE9F97&sap-language=EN#Action-genericApp?configId=2&/configId/2/workspace/42010AEE-CF75-1EEB-A9CD-2364FFAE9F97

https://ldcioft.wdf.sap.corp:44378/sap/bc/ui2/flp#Action-requirementApp&/object/42010AEECF751EEB9EE967FBD54CBF97,42010AEECF751EEB9EE96DC1D31D1F97

https://ldcioft.wdf.sap.corp:44378/sap/bc/ui2/flp?sap-client=200&GUID=42010AEE-CF75-1EEB-9EE9-67FBD54CBF97&sap-language=EN#Action-genericApp?configId=1&/configId/1/workspace/42010AEE-CF75-1EEB-9EE9-67FBD54CBF97


Application

Related documents for Focused Build related objects has been changed.

Feature details

Depending on the branch from which the related document type is called, different overview possibilities are displayed: - Design => Requirements Management- Development => Mass change app- Production => Mass change app

Benefits / Use Case

Clear visibility of related Requirements, Work Packages and Items for selected solution documentation structure and synchronicity with Business Process Readiness Dashboard.


Navigation from Related Documents area

https://ldcioft.wdf.sap.corp:44378/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html#Action-SolutionDocumentation

https://ldcioft.wdf.sap.corp:44378/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html#Action-SolutionDocumentation


Mass Change Operations


Mass Change, Requirements Management - New with SP04

Value, Effort, Story Points default value ranges

Applications

Requirements Management, Mass Change Operations

Features

• Customizing table for Value, Effort, Story Points

ranges

• Mass Change: Extended Filter and Display Options for

Value, Effort and Story Points ranges

• Example customizing available via BC-Set

Use Case

The range selection in the Mass Change offers an

efficient filtering based on the predefined values, e.g.:

• to define Initial Backlog in Requirements Management

based on Requirements, Value and Effort Points

• to define Product Backlog in Mass Change Operations

based on Work Packages, Value and Effort Points

• to do Sprint planning in Mass Change Operations

based on Work Items, Story Points


My Work Items - New with SP04

Display Role for Mass Change

Applications

My Requirements, My Work Packages, My Work Items,


Features

• Add Mass Change Operations tile has been added to the

following persona: Project Manager, Developer, Test

Manager, Tool Lead

• Sharpened authorization concept dependent on

Document Type, e.g. Defect or Work Package

Use Case

Allows other project members either to display of Mass

Change Operations data, e.g. the developer to check Work

Items in status Postponed.

Other persona got change authorization, e.g. the Test

Manager to mass change the support team for some

Defects


Mass Change – new with Focused Build SP6

Improved Display of Column ‘Release’

Applications

Mass Change

Features

Improved display of Release information in columns:

• Actual Release

• Requested Release

Harmonization of Release display, e.g. in the value help,

the Release is now displayed as a three-digit number to

the right of the description

Use CaseIn Mass Change - Actual and Requested Release:

In the result lists, the Release is displayed as a three-digit

number.

The full Release description is displayed via tooltip.

This reduces the table widths and allows to display more

results, especially on smaller screens


Applications

Mass Change

Features

New filter possibility ‘Sub-Elements’

introduced for:

• Requirements

New filter possibility ‘Sub-Categories’

introduced for:

• Requirements

• Work Packages

• Work Items

• Defects

• Defect Corrections

• Change Requests

• Changes

• Risk

Use CaseAllows more granular filtering like in Requirements

Management application.


New filter for Sub-Elements and Sub-Categories



Filter & View variants for Mass Change

Applications

Mass Change

Feature details

For all Mass Change Document Types it is now

possible to save private and global:

• Filter settings

• View Settings

Use CaseLike in Requirements Management, the Filter Variant

allows an end user to save typical filter settings, e.g.

for a Project Manager to regularly check, if there are

Requirements in Status ‘To Be Approved’ for the

Business Process in his responsibility.

As well the view of the displayed columns can be

saved. This is important as the space to display the

content is limited.

Both features extremely accelerate the search and

display of the required content.



Allow filtering for multiple IDs and fragments

Applications

Mass Change

Feature details

Using filter ‘ID’ it is now possible to search with:

• Multiple IDs, e.g. 8000004711, 8000004712

• Fragments of an ID, e.g. 4711

• Multiple ID fragments, e.g. 4711, 4712

Use CaseIn Mass Change Operations it is now possible

to filter for ID fragments or multiple IDs like in

Requirements Management.


Solution Readiness Dashboard


Solution Readiness Dashboard - New with SP04

Missing KPI displayed in Tiles

Applications


Features

• New bar ‘Milestone Missing’ for the tiles Functional Specification, Technical

Design, Development, Unit Test and Single Functional Test Case

• The ‘Overdue’ values are recalculated

Use Case

Beforehand badly maintained and overdue Work Packages and Work Items

had been summarized in the ‘Overdue’ bar.

With the additional bar you can clearly distinguish:

• The Project Manager immediately recognizes when he missed to maintain

the KPIs in Project Management.

• The Architect and Developer get a clean list of their overdue documents.


Solution Readiness Dashboard – new with Focused Build SP5

Usability and performance improvements of extraction report

Default variant of extraction report /SALM/DATA_EXTRACTION_PPMITSM to be scheduled via Job Scheduler (SM36):

All Focused Build projects with status ‘Created’ or ‘Released’

are considered by the default variant ‘FOCUSED_BUILD1’

Variant can be changed to allow extraction for dedicated

projects based on project id or status.

E.g. if you like to keep data also for completed projects you can

adapt the variant accordingly.

Depending on the amount of projects, requirements, work

packages etc. you might face longer runtime of the batch job.

With the default variant, the extraction is processed in parallel

and uses 50 % of available work processes.

This option extracts only data that has been changed since last

extraction to save runtime. Only deactivate this option when

necessary due to issues.

Focused Build data to be selected for Solution Readiness and

Release Dashboard



Usability and performance improvements of extraction data housekeeping report

Report /SALM/DATA_EXTRACTION_DELETE can be used on demand to cleanup extraction data for un-used

projects or compress transactional historic data on a weekly base

If selected, project data with below criteria are deleted from extraction data.

If selected, transactional data from time frame above are compressed, so

only one entry of a weeks state of an entity will be kept.

Time frame for aggregation of transactional historic data

Selection criteria for projects to be deleted from extractor data

Project ID - Here you choose the Project IDs for the projects, which will be

deleted. When the field is empty, all project with the chosen project status

are deleted.

Project Status - Here you choose the Project Status Values for the projects,

which will be deleted. Default: Completed, Canceled, To be Archived

Data are only deleted, when both conditions are fulfilled.



Work Package tile – additional information on actual vs. planned effort

Application

Effort reporting in Work Package tile

Feature details

New effort tab highlighting planned and actual

effort per Wave

Addition column for actual effort per Work

Package in Details tab

Use Case

Realistic Wave planning based on Planned Effort

Monitoring of actual effort per Wave

Drill down to detail information on actual effort vs.

planned effort per Work Package



Current Wave Progress tile

Application

New Current Wave Progress with bar charts

Feature details

Visualized progress for current Wave using

snapshot of status of related Work Packages per

day

Similar view on Work Items per Wave and per

Sprint

Use Case

Improved transparency on progress during Wave

and Sprints about various activities reflected by

historic status values

Work Packages status values are aggregated:

Successfully Tested: Successfully Tested, Handed over to Release,

Productive, Completed

In Development: To be Developed, In Development, In Repair,

To be Tested

Scoping: Scoping, Scope Finalized, Scope Extension

Created: Created



Realtime update of Dashboard data

Applications


Realtime update and refresh of Dashboard data for Focused Build

entities

Feature Details

The data displayed in the Solution Readiness is provided by extractor

and caching tables which have been updated by batch jobs in the past.

This has been enhanced by a event triggered update and refresh

feature in order to get real-time data shown in the dashboard for

following Focused Build entities:

• Requirements , Work Packages and Work Items

• Defect Corrections

• Projects and Risks

Data refresh can be controlled for the currently selected project by a

timer via new button in the dashboard and typically has a delay of 10 –

40 seconds depending on size of project.

Benefit

Improved monitoring and transparency about implementation progress

and KPI fulfillment with real-time data



Improved Export to spreadsheet feature

Applications

Solution Readiness Dashboard - Export to Spreadsheet

Feature details

Export CSV has been replaced by Export to spreadsheet

for all list views in the dashboard

Benefit

After export the spreadsheet can be directly opened without

conversion. Filter is active by default using the header row

(1). No problems with special characters.



Work Item tile - Display classification column N/A dynamically

Applications

Solution Readiness Dashboard – Work Item tile

Feature details

The column ‘N/A’ for Work Item Classification is displayed dynamically

depending whether Work Items without Classification exist or not.

Use Case

With Support Package 3 of Focused Build a gap was closed in the

functionality where Work Items could be created without a

classification. Such Work Items were listed in the Solution Readiness

Dashboard in the column ‘N/A’. Customers starting with Support

Package 3 or later have always seen zero Work Items in that column.

With the new enhancement the column ‘N/A’ is dynamically displayed,

if no Work Items exist in a project without classification the column is

not shown.



Current Wave Progress tile

Application

Enhanced Current Wave Progress

Feature details

Customizable status grouping

• 4 predefined status groups

• Selectable semantic colors: Positive, Neutral,

Information, Critical, Negative

• Mapping of detailed status per transaction type to

status group

Benefit

Improved flexibility for sematic rating in

progress chart

Default Work Packages status mapping and colors:

Successfully Tested: Successfully Tested, Handed over to Release,

Productive, Completed

In Development: To be Developed, In Development, In Repair,

To be Tested

Scoping: Scoping, Scope Finalized, Scope Extension

Created: Created



Current Wave Progress tile - Details

New IMG activity to change settings for predefined Status Groups

Ability to change sematic color for Status Group

Map detailed status per transaction type (status profile) to status group



Documentation KPI relevant SRD tiles

Application

KPI relevant SRD tiles

Feature details

For better understanding, the documentation KPI

related tiles has been regrouped and renamed

according to the KPI names.

Benefit

Improved overview of document KPI tiles



Defect Corrections in SFT tile

Applications

Defect Corrections in SFT tile

Feature details

• ‘For the tile ‘Defect Corrections in Single

Functional Test’ the following functionality is

available with Focused Build SP7:

• Navigation to Mass Change Operations App for Defect

Corrections for the following bars of the tile:

• To be done

• Overdue

• Export to MS EXCEL for all bars of the tile.

Benefit

• Seamless Integration between Solution Readiness

Dashboard and Mass Change Operations App for

Defect Corrections in relevant (user) status.

• Export to MS EXCEL is available for all bars of this

tile.


S/4HANA Conversion Project Support


Application

Simplification Item Management

Feature details

The new Refresh button allows to get the latest status of Simplification Items, Conversion Activities and follow-up documents without the need of performing a browser refresh. This refresh is faster and keeps the current applied filters and view settings.

Benefits / Use Case

When processing Conversion Activities and their related follow-up documents it is important to regularly update the table view to get the most recent status of all documents. This refresh must be optimized from a performance perspective which the new refresh-functionality offers.

S/4HANA Conversion Project Support – new with Focused Build SP8

Refresh-Functionality


Application


Feature details

Via the Messages-button it is possible to see

relevant backend-information.

Benefits / Use Case

When creating Follow-Up Documents, assigning

or reassigning Activities or assigning projects data

will be processed in the backend. With the new

feature it is directly possible in the frontend to

identify whether a step was successful or not, e.g.

in case the user has no appropriate

authorizations to perform a specific step.


Enhancement of Log-Information


Application


Feature details

Activities with small efforts that are also related to each other can be merged into one Follow-Up Document.

Benefits / Use Case

So far it was only possible to create one Follow-Up Document per Activity. Usually there are Activities which do have a rather small implementation effort where it makes sense to combine several of them in one Follow-Up Document to not get too granular in the Requirements-to-Deploy-process. This is now possible with the n:1-creation.


Combine several activities in one Follow-Up Document


Application


Feature details

Created Requirements or Work Packages can be handed over from the Simplification Item Management application to the Mass Change Application for further processing.

Benefits / Use Case

This feature allows an easier Release Backlog Planning on Requirements or Wave Backlog Planning on Work Packages. Based on attributes of the related Simplification Items and Conversion Activities (e.g. Condition or Phase) a set of Work Packages can be handed over to the Mass Change Application where they are assigned to a specific Project and Wave.


Integration in Mass Change Application


Application


Feature details

Activities without a Follow-Up Document can be assigned to an already created one. If the assignment to or the creation of a Follow-Up document was done incorrectly a reassignment to a different Follow-Up Document can be done.

Benefits / Use Case

A common Readiness Check Analysis consists of more than 100 Simplification Items and related Activities. It is likely to happen that during the creation of Follow-Up Documents Activities are forgotten or that in the course of the processing of the Follow-Up Documents additional Activities should be part of the selected scope. The assign/reassign functionality allows a higher flexibility and offers an option for the correct scope.


Assignment and Reassignment of Activities


Application


Feature details

It can be decided per Readiness Check Analysis which transaction types are allowed as Follow-Up Type. By default these are Requirements and Work Packages plus the assignment of Projects. Via Customizing own transaction types can be chosen and the assignment of projects can be active or inactive.

Benefits / Use Case

Customers who are going to perform a S/4HANA transformation project can use Focused Build as predefined methodology. But especially customers that already have a mature Change Request Management process in place want to use their settled, accepted and well-known process also in this S/4HANA transformation project. With the possibility to define custom transaction types as Follow-Up Document Types customers are enabled to use the Readiness Check Integration with their individual processes.


Integration of custom transaction types

Thank you.


[email protected]










warranty.












See www.sap.com/copyright for additional trademark information and notices.


Follow all of SAP

https://www.sap.com/copyright







Week 3: Realization (Architect/Developer) Unit 1: Building ...

Documents

Transcript of Week 3: Realization (Architect/Developer) Unit 1: Building ...