SAP AG 1

SAP AG 2005

Agenda

Solution Overview

Introduction

Example

Frontend

Content

zSupply Chain DesignzPlanningzProcurementzManufacturingzOrder FulfillmentzInventory Management

SAP AG 2

SAP AG 2005

Content in Order Fulfillment (based on R/3)

Analyses can be created with respect to Customers Materials Plants Shipment routes Etc.

All datasources are ODS-capable

Quotations / OrdersSales Overview

Delivery PerformanceBacklog History

Shipment CostsShipment Stages

TransportationDistributionSales

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

SAP AG 3

SAP AG 2005

Sales - Overview

Sales Overview

Numbers, values and quantities of Orders Deliveries Invoices Returns

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

Order Delivery Invoice

Return

Sales Distr. Trans.

InfoCube: 0SD_C04 -> manage sales process

4 objects taken into account: order delivery invoice returnsInvoice = billing document

SAP AG 4

SAP AG 2005

Sales - Quotations

Quotations / Orders

Analyze rejected quotations

Quotationsz Numbersz Valuesz Quantities

Ordersz Numbersz Valuesz Quantities

Order values and quantitiesresulting from quotations

Sales Distr. Trans.

InfoCube 0SD_C05: -> comparison of orders and quotations (according to numbers, values, quantities)Compare order value and quotation value -> success rateAvailable characteristics: Customer, material, sales representative, sales organization, plant, etc...

SAP AG 5

SAP AG 2005

Delivery Performance - KPIs (SCOR)

Delivery Performance 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

Sales Distr. Trans.

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

SAP AG 6

SAP AG 2005

Delivery Performance

Cubes for reporting on 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

Sales Distr. Trans.

InfoCubes 0SD_C11, 0SD_C12, 0SD_C13 ->calculation of delivery performanceGeneral reporting (On-time Delivery Performance, Quantity Reliability, Quality, Lead times) isavailable on an aggregated level in the InfoCubes

The ODS provides very detailed reporting on a document level (very genereic design, thereforeno 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 calculatethis key figure on quantity and line item level

SAP AG 7

SAP AG 2005

Delivery Performance - Data Basis

Quantitiesz Confirmed quantityz Requested quantityz Delivered quantity

Datesz Confirmed delivery datez Requested delivery datez Actual delivery date

Qualityz Returns

Aggregation

Service Levelz for quantitiesz for itemsz for orders

e.g. Delivery Performance to Scheduled Commit Date

7 basic figures are needed to calculate the delivery performance:Requested/confirmed/actual delivery date

Returns

Requested/confirmed/actual quantity

SAP AG 8

SAP AG 2005

Delivery Performance - Calculation (1)

Order 4711Item 10 1st June - 40

Schedule 1 1st June 10

Schedule 2 5th June - 20

Delivery 80001Item 10 1st June - 5

Delivery 80002Item 10 3rd June - 10

Delivery 80003Item 10 10th June - 25

40104711

Too lateToo earlyDeliveredquantity

Confirmedquantity

ItemOrder

Schedule 3 10th June - 10

Delivery Performance to Scheduled Commit Date = = 50%40 - 2040

510 5525 15

40 5 20

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 9

SAP AG 2005

Delivery Performance - Calculation (2)

200303020471105510304711

2054040104711

Too lateToo earlyDeliveredquantity

Confirmedquantity

ItemOrder

4711 3 1 11

Delivery Performance to Scheduled Commit Date = = 33%3 - 23

Too late Too earlyToo earlyand toolate

ItemsOrder

Aggregation

Toolittle

1

SAP AG 10

SAP AG 2005

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

0SD_C14:Takes into account the currently open orders and backlogs. However, drill-down on order level notpossible.

Limitation up to BW 3.0B: doesnt differentiate between orders according to the time they havebeen open for.

With BW 3.1C: complete backlog history available

SAP AG 11

SAP AG 2005

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 12

SAP AG 2005

Backorders Data Flow SD

2LIS_11_V_SSL SD Sales: Order delivery

0SD_O04 Open order schedule line

0SD_C14 Backorders

Daily snapshot of backorders:

Requested delivery date is overdue !!!

SAP AG 13

SAP AG 2005

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 bymore than 30 days)

Backorder Quantity: open quantity in Base Unit of Measure Backorder Value: open value in Local currency

SAP AG 14

SAP AG 2005

Data Flow

2LIS_11_VAHDR(Order header)

2LIS_11_VASTH(Status order header)

0SD_O02(Return items)

0SD_C13(Cube order level)

2LIS_11_V_SSL(Supplied schedule lines)

2LIS_11_VAITM(Order items)

0SD_O03(Aggregation order header)

0SD_O01(Aggregation order items)

0SD_C12(Cube item level)

0SD_C11(Cube quantity level)

0SD_C14(Backorders)

0SD_O04(open request schedule

line)

predefined reports for returns only on order level (see arrows).However, returns are available on customer order item level as well (0SD_O02).

SAP AG 15

SAP AG 2005

Shipment

Physical Shipment 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.

Sales Distr. Trans.

0LES_C01 ... C05: only focussed on shipmentMeans of transportation (stages)Shipment cost:1 shipment cost document (de: Frachtkostenbeleg) per ShipmentCost on header and item (delivery=shipment item, delivery item, shipment, handling unit, shipment stage,...) level (based on condition technique)

SAP AG 16

SAP AG 2005

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)

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 17

SAP AG 2005

SAP Business InformationWarehouse

Analytical Supply Chain Event Management

Events (e.g.):

Carrier Arrival

Plant Departure

Arrival at Cust. Site

Quantities

...

...

On time performance deliveryOn time performance delivery

SAP Event

Manager

This slide shows the integration from SAP EM to SAP BW

SAP AG 18

SAP AG 2005

Planned Shipment Route, Carriers and Customers

ArrivalCarrier

PickingPacking

Depart.Plant

Arrival Hub

Depart. Hub

Arrival White

Arrival Miller

POD Miller

PODWhite

Arrival Smith

PODSmith

Leg 1 Leg 4Leg 3Leg 2

Deliveries:800050018000500280005003

Deliveries:800050018000500280005003

Deliveries:8000500280005003

Delivery:80005003

Carrier ABC Carrier XY

Loading

Delay:Weather

a

Shipment Type0002

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 19

SAP AG 2005

Exp. Event (Date/Time) Actual. Event (Date/Time) Exp. Message (Date/Time) Act. Message (Date/Time)

Carrier Arrival

Plant Departure

Arrival at Cust. Site

Execution CompliancezOn time performancezAverage delayzNumber of delays per

category (time interval, reason code)

Reporting CompliancezAverage delayzNumber of delays per timintervalTransportation Time (plan

vs. actual)zAverage delayzNumber of delays per time interval

(Time)

KPIs/CPIs for Fulfillment Visibility

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 20

SAP AG 2005

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.

Copyright 2005 SAP AG. All Rights Reserved