Agenda

Introduction
Solution Overview

Frontend

zSupply Chain Design

zPlanning

Content

zProcurement
zManufacturing
zOrder Fulfillment

Example

zInventory Management

SAP AG 2005

SAP AG

Content in Order Fulfillment (based on R/3)

Sales
Quotations / Orders
Sales Overview

Distribution
Delivery Performance
Backlog History

Transportation
Shipment Costs
Shipment Stages

Analyses can be created with respect to

Customers
Materials
Plants
Shipment routes
Etc.

All datasources are ODS-capable

SAP AG 2005

Content

in order fulfillment covers 3 areas: sales, distribution, transportation

SAP AG

Sales - Overview

Sales Overview
Order

Sales

Delivery

Distr.

Trans.

Invoice
Return

Numbers, values and quantities of

Orders
Deliveries
Invoices
Returns

Analyses
Open order value compared to incoming order value
Credit memos to billing documents
Etc...

SAP AG 2005

InfoCube:
->

0SD_C04
manage sales process

objects taken into account: order delivery invoice returns

Invoice

= billing document

SAP AG

Sales - Quotations

Quotations / Orders

Sales

Distr.

Trans.

Order values and quantities

Quotations
Orders
resulting from quotations
z Numbers
z Numbers
z Values
z Values
z Quantities
z Quantities

Analyze rejected quotations

SAP AG 2005

InfoCube
->

0SD_C05:

comparison of orders and quotations (according to numbers, values, quantities)

Compare

order value and quotation value -> success rate

Available

characteristics: Customer, material, sales representative, sales organization, plant, etc...

SAP AG

Delivery Performance - KPIs (SCOR)

Delivery Performance

Sales

Distr.

Trans.

Delivery Performance to Customer Request Date

Delivery Performance to Scheduled Commit Date
Percentage of Orders / Items / Quantities Scheduled To
Requested Date
Fulfillment Rates

Quantity Reliability
Number of Orders / Items / Quantities not delivered complete

Quality
Perfect Order Fulfillment

Order Fulfillment Cycle Time

SAP AG 2005

SCOR

KPIs in Distribution (see SCOR model for definitions www.supply-chain.org)

SAP AG

Delivery Performance
Cubes for reporting on

Sales

Distr.

Trans.

On-time Delivery Performance

Quantity Reliability
Quality
Lead times

ODS for detailed reporting on

Order values and status
Item quantities, values and status

Generic design
Reporting on three aggregation levels
Orders
Quantities
Items

SAP AG 2005

InfoCubes

0SD_C11, 0SD_C12, 0SD_C13

->calculation of delivery performance

General

reporting (On-time Delivery Performance, Quantity Reliability, Quality, Lead times) is

available on an aggregated level in the InfoCubes
The ODS provides very detailed reporting on a document level (very genereic design, therefore
no predefined queries available on ODS-level)
3

levels of evaluations (order, quantities, line items)

->SCOR suggests calculations on order level but many of our customers calculate
this key figure on quantity and line item level

SAP AG

Delivery Performance - Data Basis

e.g. Delivery Performance to Scheduled Commit Date

Dates

Quality

Quantities

z Confirmed delivery date

z Requested delivery date
z Actual delivery date

z Returns

z Confirmed quantity
z Requested quantity
z Delivered quantity

Aggregation
Service Level
z for quantities
z for items
z for orders

SAP AG 2005

basic figures are needed to calculate the delivery performance:

Requested/confirmed/actual

delivery date

Returns
Requested/confirmed/actual

SAP AG

quantity

Delivery Performance - Calculation (1)

Order 4711
Item 10
1st June - 40
Schedule 1 1st June 10
Schedule 2

5th June - 20

Schedule 3 10th June - 10

Order
4711

Item
10

Confirmed
quantity
40

Delivery 80001
Item 10 1st June - 5
Delivery 80002
Item 10 3rd June - 10
Delivery 80003
Item 10 10th June - 25
Delivered
quantity

Too early

Too late

5
10
25

5
15

40

20

Delivery Performance to Scheduled Commit Date =

40 - 20

= 50%

40
SAP AG 2005

In

order to calculate the delivery performance a mapping of schedule lines of a customer order
and Items of a delivery is implicitely made
The

example describes the mapping

SAP AG

Delivery Performance - Calculation (2)

Order

Item

Confirmed
quantity

Delivered
quantity

Too early

Too late

4711

10

40

40

20

4711

20

30

30

20

4711

30

10

Aggregation
Order
4711

Items
3

Too early
and too
late 1

Too late Too early

1

Delivery Performance to Scheduled Commit Date =

Too
little

1
3-2

1
= 33%

3
SAP AG 2005

SAP AG

Backlog History
Analyse trends in your backlog for
Customers
Materials
Time intervals

Report on your current open orders

Backlog with respect to
customer requested delivery date

Reports based on
Quantities
Values
Backlogs

SAP AG 2005

0SD_C14:
Takes

into account the currently open orders and backlogs. However, drill-down on order level not
possible.
Limitation up to BW 3.0B: doesnt differentiate between orders according to the time they have
been open for.
With

BW 3.1C: complete backlog history available

SAP AG

10

Backorders - Definition

Back orders are orders

that have an open quantity,
where the planned / requested delivery date is in the past
where the delivery completed indicator is not set.

SAP AG 2005

SAP AG

11

Backorders Data Flow SD

0SD_C14 Backorders
Daily snapshot of backorders:

Requested delivery date is overdue !!!

0SD_O04 Open order schedule line

2LIS_11_V_SSL SD Sales: Order delivery

SAP AG 2005

SAP AG

12

Backorders - KPIs
KPIs on material / plant/etc:
Backorders (number of days order is overdue) -> on order level
Backorders One Day (number of orders which are overdue by one day)
Backorders 7 Days (number of orders which are overdue by 1 to 7 days)
Backorders 30 Days (number of orders which are overdue by 7 to 30
days)
Backorders more than 30 Days (number of orders which are overdue by
more than 30 days)
Backorder Quantity: open quantity in Base Unit of Measure
Backorder Value: open value in Local currency

SAP AG 2005

SAP AG

13

Data Flow

2LIS_11_VASTH
(Status order header)

2LIS_11_VAHDR
(Order header)

2LIS_11_VAITM
(Order items)

2LIS_11_V_SSL
(Supplied schedule lines)

0SD_O02
(Return items)

0SD_O01
(Aggregation order items)

0SD_O03
(Aggregation order header)

0SD_C13
(Cube order level)

0SD_C12
(Cube item level)

0SD_O04
(open request schedule
line)

0SD_C11
(Cube quantity level)

0SD_C14
(Backorders)

SAP AG 2005

predefined
However,

SAP AG

reports for returns only on order level (see arrows).

returns are available on customer order item level as well (0SD_O02).

14

Shipment
Physical Shipment

Sales

Distr.

Trans.

Vehicle utilization
Loading, transportation times and delays
Distances

Delivery Dates for Shipment Stages

Combines delivery data and shipment stages
Delivery weights and volumes per stage

Shipment Costs
Overview information on level of shipment headers or items
Detailed information on level of delivery items

Analyses can be created with respect to

Forwarding agents
Routes, Point of departure and destinations
Shipment types
Etc.

SAP AG 2005

0LES_C01
Means

of transportation (stages)

Shipment
1

... C05: only focussed on shipment

cost:

shipment cost document (de: Frachtkostenbeleg) per Shipment

Cost on header and item (delivery=shipment item, delivery item, shipment, handling unit,
shipment stage,...) level (based on condition technique)

SAP AG

15

Content in Order Fulfillment (based on EM)

With SAP EM (Event Manager) SAP delivers so-called visibility scenarios
that are ready-to-go so you can put the solution to work right away.
BW Business Content will now be available with SAP BW 3.1Content for
the fulfillment visibility scenario of the SAP Event Manager.
It will allow to evaluate the
Transportation Time (plan vs. actual)

Execution Compliance (Carrier on time performance, average

delay)
Reporting Compliance (Have the events been reported on time)

SAP AG 2005

With

the release of the SAP Event Manager as a component of the mySAP SCM solution, SAP
delivers the backbone for supply chain event management (SCEM). The SAP Event Manager
offers a broad range of functions for tracking, proactive notification and alert creation. It is able to
track and control business processes along the entire supply chain by integrating with supply chain
planning, supply chain execution, customer relationship management and product lifecycle
management in both SAP and non-SAP applications.
SAP delivers visibility scenarios that are ready-to-go so you can put the solution to work right
away. BW Business Content will now be available with SAP BW 3.1Content for the fulfillment
visibility scenario of the SAP Event Manager. It will allow to evaluate the
zTransportation Time (plan vs. actual)
zExecution Compliance (Carrier on time performance, average delay)
zReporting Compliance (Have the events been reported on time)
Benefits

of integrating SAP Event Manager into SAP BW:

Evaluate

the performance of processes that span the entire SC (no limitation to R/3 objects)

Very

precise data, because the source data is not limited to one particular system. Events can be
reported through almost any device (web, telephone, SAP system, 3rd party systems)

SAP AG

16

Analytical Supply Chain Event Management

On
On time
time performance
performance delivery
delivery

SAP
Event
Manager

Events (e.g.):

Carrier Arrival

Plant Departure

Arrival at Cust. Site

Quantities
...

SAP Business Information

Warehouse

...

SAP AG 2005

This

slide shows the integration from SAP EM to SAP BW

SAP AG

17

Planned Shipment Route, Carriers and Customers

Shipment Type
0002

Carrier ABC
Deliveries:
80005001
80005002
80005003
Leg 1

Picking
Packing

Arrival
Carrier

Loading

Carrier XY
Deliveries:
80005001
80005002
80005003

Deliveries:
80005002
80005003

Leg 2

Leg 3

Delivery:
80005003
Leg 4

Depart.
Plant
Arrival
Hub

Delay:
Weather

Depart.
Hub
Arrival
White

Arrival
Miller
POD
White

Arrival
Smith
POD
Miller

POD
Smith

SAP AG 2005

In

this chart you can see the detailed steps that are defined as events in the fulfillment visibility
scenario from the arrival of the carrier to pick up the materials through the final delivery to the
customer. Each step along the way is visible to anyone who requires and has access to that
information.

SAP AG

18

KPIs/CPIs for Fulfillment Visibility

Exp. Event (Date/Time) Actual. Event (Date/Time) Exp. Message (Date/Time) Act. Message (Date/Time)
Carrier
Arrival
Plant
Departure
Arrival at
Cust. Site

(Time)

Execution Compliance

Reporting Compliance

zOn time performance

zAverage delay
zNumber of delays per
category (time interval,
reason code)

zAverage delay
zNumber of delays per tim
interval

Transportation Time (plan

vs. actual)
zAverage delay
zNumber of delays per time
interval

SAP AG 2005

This shows the mySAP BI Business Content based on the fulfillment visibility process as of SAP
BW 3.1

To be regarded as an example, can easily be extended

Not only for outbound fulfillment scenario

Benefits of integrating SAP Event Management with SAP BW:

Evaluate the performance of processes that span the entire SC (no limitation to R/3 objects)

Very precise data, because the source data is not limited to one particular system. Events can
be reported through almost any device (web, telephone, SAP system, 3rd party system)

SAP AG

19

Copyright 2005 SAP AG. 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 AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other

software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or
registered trademarks of IBM Corporation in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,

Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and

implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein

as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group
shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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.
SAP AG 2005

SAP AG

20