0

Unit 8 - Overview Diagramm

Preface

Introduction to End-To-End
Solution Support

Business Process Performance

Optimization

Introduction to E2E Business

Process Integration and
Automation Management

Data Consistency
Management

Job Scheduling Management

Data Volume Management

Business Process and Interface

Monitoring

Recap Customer Case

SAP AG 2006

SAP AG

E2E300

8-1

0.2
Storyline
Business Process

Request to change Job

Schedule for MRP
Changes to Business
Process Monitoring for MRP
run

Detecting Alerts

BPPO for MRP Run

Insufficient Outcome caused

by data inconsistencies

Long Runtime caused by

Data Volume

Schedule Consistency
Checks

Adjust Monitoring concept

Adjust Job Schedule

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-2

0.3

Initial Customer Situation Scenario Business

Process Order to Cash
CRM - C00

SAP ECC - TT5

SAP
ENTERPRISE
PORTAL - EPP

Create Sales
Order

Create Sales
Order

Create Sales
Order

Check
Availability

Run MRP

Procurement
Process

Manufacturing
Process
Create
Outbound
Delivery
Create Billing
Document

Post Goods
Issue

Warehouse - TT5
Create
Outbound
Delivery

Create Picking
Transfer Order

Post Goods
Issue

Confirm Picking
Transfer Order

SAP AG 2006, Customer Case Recap / 1

Company IDES sells Pumps, Motorcycles, PCs and light bulb. The company is located in
Frankfurt /Germany and has subsidiaries within Europe, Asia, and North- and South America

Business Process Order to Cash describes the sales process for pumps:
Orders for pumps can be placed by customers directly via the Company Portal or via the Call
Center that uses a non-SAP CRM system and are replicated to the ERP system via BDocs.
The availability of the ordered material is checked on the ERP system. The MRP determines how
the material requirement can be satisfied. Materials that are not available can either be procured or
manufactured in separate business processes.
Once the material is available the Outbound Delivery is created on the ERP system. During the
creation of a delivery, the system establishes whether it is relevant for distribution or not. If it is, a
BAPI is called when the delivery is saved. This BAPI starts the creation of an IDoc and via this
IDOC sends the delivery to the Warehouse system.
In the Warehouse system the Picking Transfer order is created. Once the material is physically put
into the Goods Issue zone the Warehouse Operator confirms the Picking Transfer Order. By this
the posting of the goods issue is triggered, calling a BAPI. This BAPI confirms the data, that was
created or changed in the WMS (e.g. quantities, packaging, batches, ...) to the ERP system.
When the confirmation is received in the ERP system the goods movement is executed in
Inventory Management. Based on this the Goods Issue the billing document is created.

SAP AG

E2E300

8-3

0.4
Technical Details for the Business Process

CRM - C00

SAP ECC - TT5

SAP
ENTERPRISE
PORTAL - EPP

Create Sales
Order

Create Sales
Order

Create Sales
Order

Check
Availability
Job PP_MRP_0001_D runs
once per day at 22:00
Run MRP

Procurement
Process

Manufacturing
Process
Create
Outbound
Delivery
Create Billing
Document

Post Goods
Issue

Warehouse - TT5
Create
Outbound
Delivery

Create Picking
Transfer Order

Post Goods
Issue

Confirm Picking
Transfer Order

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-4

0.5
Structure of Support Organization

Business
Department
Sales

Business
Department
Production
Business Process
Champion

Business Process
Champion

IT Department

Business Process
Operations Team

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-5

0.6

Scenario Business Process Order to Cash Job

Scheduling Management
CRM - C00

SAP ECC - TT5

SAP
ENTERPRISE
PORTAL - EPP

Create Sales
Order

Create Sales
Order

Create Sales
Order

Check
Availability

Job PP_MRP_0001_D
runs daily

Run MRP

Procurement
Process

Manufacturing
Process
Create
Outbound
Delivery
Create Billing
Document

Business Process
Champion

Post Goods
Issue

Warehouse - TT5
Create
Outbound
Delivery

Create Picking
Transfer Order

Post Goods
Issue

Confirm Picking
Transfer Order

We would like to change

the schedule of the MRP
from once per day to four
times a day.

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-6

0.7
Use Job Request Form for Requesting Change
So next steps to consider: planning, scheduling, monitoring!
Job name

PP_MRP_0001_6H

Report

RMMRP000

Substituting which job

PP_MRP_0001_D

System/Client

TT5:800

Scheduling

5:30 and then every 6 hours

Business Contact

Mr. Meyer

Business Relevance

See job documentation for PP_MRP_0001_D

Error Handling

See job documentation for PP_MRP_0001_D

...

...

Remark: documentation of technical parameters & business

information, error-handling procedures, monitoring information

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-7

0.8

Planning - Check if new Job Request fits into existing

schedule
For job distribution over time use BATCH_JOB_ANALYSIS tool

HW & time restrictions!! scheduling at 5:30 might be a problem other less

important jobs might need a rescheduling

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-8

0.9

How does Change in Scheduling influence Monitoring

tasks?
Which business process specific objects have to be monitored to ensure that possibly business
critical situations are recognized and solved before the have an impact?
CRM - C00

SAP ECC - TT5

SAP
ENTERPRISE
PORTAL - EPP

Create Sales
Order

Create Sales
Order

Create Sales
Order

Job
PP_MRP_0001_6H
runs every 6 hours
starting at 5:30

Check
Availability

Run MRP

Procurement
Process

Manufacturing
Process

Create
Outbound
Delivery

Create
Outbound
Delivery

Business Process
Champion

Warehouse - TT5

The business process should never stand still. If

Post
Goods
Post Goods
material is available
at the time of
the
order
Create Billing
Issue 12:00, the Issue
Document
creation and the
order is created before
material itself should leave the yard at 16:00.

Create Picking
Transfer Order
Confirm Picking
Transfer Order

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-9

0.10

Incorporate into existing Business Process and

Interface Monitoring concept

Step 3
Identify business
requirements

Error situations
should be
recognized:
Dumps within
MRP Run,
Cancellations
MRP run has to
start within 30
minutes of
scheduled start
time and has to
be finished
within 15
minutes,
otherwise
resources for
other activities
are allocated

Step 4
Define monitoring
objects, alerts and
thresholds

MRP run
cancellation: Red
alert
Dumps within
MRP: Red alert
MRP Start Delay:
15 minutes for
yellow and 30
minutes for red
Maximum
Duration: 10
minutes for
yellow, 15
minutes for red

Step 5
Define
monitoring
activities

Step 6
Define
communication
and escalation
procedures

Use SAP
Solution
Manager for
automated
monitoring

In case of
problems
contact business
department (Mr.
Meyer)

in case of
problem check
job log for MRP
run for problems

If you cant solve

the problem
open ticket

Step 7
Assign
monitoring
activities to
responsibles

Monitoring is
supposed to be
carried out by
Mrs. Hampert in
Business
Process
Operations Team

Job Status is
directly observed
in external job
scheduling tool

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-10

0.11
SAP Solution Manager used for Monitoring MRP Run
Monitoring set up according to
Documentation (especially
Roadmap and Setup Guides)
available in Quicklink /BPM in
SAP Service Marketplace
Monitoring functionalities as they
are available in ST-A/PI on
Satellite system or within ST-SER
on SAP Solution Manager

Link to Error Handling procedures and Analysis Tools in Satellite System

Remark: Data Collection specific for each monitoring object, normally not more
frequent than every 5 minutes

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-11

0.12
IT Department detects Alert Situation

CRM - C00

SAP ECC - TT5

SAP
ENTERPRISE
PORTAL - EPP

Create Sales
Order

Create Sales
Order

Create Sales
Order

Check
Availability
MRP Run takes 30
minutes each time it
runs Red alert

Run MRP

Procurement
Process

Manufacturing
Process
Create
Outbound
Delivery
Create Billing
Document

Post Goods
Issue

Warehouse - TT5
Create
Outbound
Delivery

Create Picking
Transfer Order

Post Goods
Issue

Confirm Picking
Transfer Order

Business Process
Operations Team

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-12

0.13

Example for Process Flow for Business Process

Monitoring
IT Department
Business Process
Operations
Detect Alert
Situation

Alert for Job Duration

Initial Analysis does not solve the
situation

Execute Initial
Analysis

Create Service Desk

message

Business Process Performance

Optimization is triggered for the
MRP run

Application
Management

Assign Service Desk

message to issue

RCA process

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-13

0.14
Business Process Performance Optimization for MRP Run
MRP run has shown increasing runtime over the last weeks
A performance analysis is considered as an urgent issue as
the business process step is considered to be critical as KPIs
a given with regards to time restrictions an throughput
requirements.
Initial error handling did not solve the problem, detailed root
cause analysis is required Business Process Performance
Optimization

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-14

0.15

Procedure for finding cause of longer runtimes for

MRP run
Analysis via transaction ST03N shows that the increasing
runtime is mainly caused by an increasing DB time share.
Further analysis via ST03N shows that the amount of
sequential reads is constantly growing perhaps a Data
Volume problem
An SQL trace analysis (transaction ST05) shows that no
significant tuning potential is given, e.g. no identical selects,
no unsuitable indexes used

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-15

0.16
Data Volume Management triggered by MRP
So in order to improve the runtime of the MRP run the DB
table RESB should be analyzed via transaction DB02 (size
20GB).
Can the size be reduced and/or the growth slowed down? So
can you avoid, delete, summarize or archive data?
For RESB data avoidance and archiving is possible.

SAP AG 2006, Customer Case Recap / 1

Archiving production orders using archiving object PP_ORDER is especially helpful if table RESB
contains many order reservations (field BDART = AR). Archiving these noticeably reduces the data
volume in RESB. This also improves the performance of reading order reservations.

A good indicator for deciding whether archiving table RESB would make sense or not is the number
of old (for example older than three months) reservation entries, for which the final issue indicator
(field KZEAR final issue) has been set. If your system has a large number of these kind of
reservations, you should check, whether it would be possible to flag them for deletion and then
remove them from table RESB when the production orders are archived.

SAP AG

E2E300

8-16

0.17
Database Size and Growth
Database Size < 500GB
Database Growth <
20GB/month

No indication for establishing Data

Volume Management, but nonetheless
DVM can solve the long runtime

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-17

0.18
Archiving Objects for table RESB
Archiving Object

Archived Application Data

MM_EBAN

Purchase Requisitions

MM_EKKO

Purchasing Documents

PM_ORDER

Service & Maintenance Orders

PP_ORDER

Production Orders

PR_ORDER

Process Orders

PS_PROJECT

Operative Structures

Can be checked in /nDB15.

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-18

0.19
Storyline
Business Process

Request to change Job

Schedule for MRP
Changes to Business
Process Monitoring for MRP
run

Detecting Alerts

BPPO for MRP Run

Insufficient Outcome caused

by data inconsistencies

Long Runtime caused by

Data Volume

Schedule Consistency
Checks

Adjust Monitoring concept

Adjust Job Schedule

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-19

0.20

Stock Difference between IM and WM Effects for

MRP run
Business complains that throughput for business
process is not good enough Materials are not
sent out immediately even though they are
physically available on the shelf
Business Process
Champion

Root Cause Analysis: MRP only considers stock in Inventory

Management (on ERP system) and not on the warehouse
system
Check for inconsistencies between IM and WM via
transaction LX23

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-20

0.21
Recognizing Inconsistencies Possible Causes

Possible Reasons:

Missing Error Handling

Business Process not followed by end users

Implicit COMMITS within customer coding (ignoring SAP LUW

principle)

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-21

0.22
Solve Inconsistency

1.

Execute Error Handling

2.

Confirm open transfer orders to should already have been

confirmed

3.

Use LX23 to correct stock information

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-22

0.23

Adjust Monitoring Activities to recognize potentially

critical situations proactively
Include monitoring of open transfer orders and of IDocs between ERP
and WHS into the BP+IMon concept

Step 3
Identify business
requirements

Step 4
Define monitoring
objects, alerts and
thresholds

Error situations
in interface
should be
recognized

Error status for

IDocs of type
DESADV, one for
yellow, 5 for red

Open TOs older

than 5 days
should be
recognized

Open TOs older

than 5 days: 100
for yellow, 50 for
red

Step 5
Define
monitoring
activities

Use SAP
Solution
Manager for
automated
monitoring

Step 6
Define
communication
and escalation
procedures

In case of
problems
contact business
department (Mr.
Meyer)
If you cant solve
the problem
open ticket

Step 7
Assign
monitoring
activities to
responsibles

Monitoring is
supposed to be
carried out by
Mrs. Hampert in
Business
Process
Operations Team

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-23

0.24

Schedule data consistency run to detect

inconsistencies in the future
For job distribution over time use BATCH_JOB_ANALYSIS tool

HW & time restrictions!! scheduling would fit best at 04:00, at that time no
application data is posted

SAP AG 2006, Customer Case Recap / 1

SAP AG

E2E300

8-24