Lessons from Early Adopters of SAP Transportation Management 8.

0 What You Need to Know Before You Implement

Bjorn Bernard GOPA IT Consultants
2012 Wellesley Information Services. All rights reserved.

In This Session

GOPA ITC has gained experience over 18 months of working with SAP TM 8.0/8.1 in a variety of formats Testing during SAP TM boot camps Conduct of a 3 month SAP TM Training Academy Demo build and delivery for about 25 SAP TM prospects Creation of a template-based SAP TM solution Proof-of-Concept (POC) and Gap analysis work in Chemical, Trade, and CP Food industries Go-Live implementation in High-Tech Consumer Electronics industry (live since November 2011) Countless requirements discussions A lot of lessons have been learned on how to approach SAP TM initiatives!
1

What Well Cover

SAP Transportation Management A quick status update SAP TMs usage of new technology Implementation options and methodologies Lessons learned from early adopters Wrap-up

SAP TM Quick Status Update

Product versions SAP TM 8.0 entered the market in Ramp-Up in November 2010 SAP TM 8.0 reached GA (General Availability) status in June 2011 SAP TM 8.1 entered Ramp-Up in August 2011 SAP TM 9.0 is planned for Ramp-Up later in 2012 Customers Live with TM 8.0, 8.1 in various regions and industries About 7-8 customers are live with these versions Functional scope SAP TM provides enormous flexibility to implement all kinds of different scenarios SAP continues to invest heavily to complete its extensive roadmap for SAP TM
3

What Well Cover

SAP Transportation Management A quick status update SAP TMs usage of new technology Implementation options and methodologies Lessons learned from early adopters Wrap-up

SAP TMs Usage of New Technology

SAP TM has been developed using a set of new technologies that require skills that go above and beyond typical SAP deployments PI SAP NetWeaver Process Integration NWBC SAP NetWeaver Business Client FPM Floorplan Manager BRF+ Business Rules Framework Plus BOPF Business Object Processing Framework When setting up SAP TM, projects usage of new technology needs to be considered during resource planning The combination of new technologies makes SAP TM a highly flexible solution that is customizable to customer needs
5

SAP TMs Usage of New Technology (cont.)

PI SAP NetWeaver Process Integration Formerly known as XI (Exchange Infrastructure) SAPs primary integration tool for SAP-to-SAP and SAP-to-nonSAP environments Used for transactional integration between SAP ERP and SAP TM (sales orders, purchase orders, deliveries, etc.) Leveraged in case additional data elements need to be transferred from SAP ECC to SAP TM (e.g., append fields)

SAP TMs Usage of New Technology (cont.)

NWBC SAP NetWeaver Business Client Role-based, single point of entry to SAP business applications, such as SAP GUI applications and new applications based on Web Dynpro Available in Desktop and Zero-Footprint versions, allowing flexible access for all user groups Personalization Allow users to create their own queries, filters, worklists Persist user sort sequence Display classic SAP GUI transactions in place for one-step access SAP TM end users will solely use SAP NetWeaver Business Client
7

SAP TMs Usage of New Technology (cont.)

NWBC SAP NetWeaver Business Client (example)

Queries

Filters

Worklists
8

SAP TMs Usage of New Technology (cont.)

FPM Floorplan Manager Framework to create and configure Web Dynpro ABAP applications Adapt standard SAP TM screens without code modifications Provide end users ability to configure their own screens Move or hide tabs Hide entire fields Collapse or move entire building blocks Ensure consistency across applications by means of predefined elements, such as floorplans, toolbars, and building blocks Available as of SAP NetWeaver 7.01
9

SAP TMs Usage of New Technology (cont.)

BRF+ Business Rules Framework Plus Business rules system available in SAP NetWeaver ABAP Comprehensive framework which helps business and IT users to model rules used for automatic decision support in business cases of all kinds Enables customers to leverage current practices and not rely on standard functionality Can be triggered at various stages of an SAP TM process Customer and carrier routing guides Determination of route codes in rail Rules-based planning versus optimization Rule maintenance is now in the hands of end users
10

SAP TMs Usage of New Technology (cont.)

BRF+ Business Rules Framework Plus (cont.) Example of how route codes and Rule 11 (Execution) carriers are derived from a number of input fields in a rail scenario

Input fields in blue

Result fields in green

11

SAP TMs Usage of New Technology (cont.)

BOPF Business Objects Processing Framework Not to be confused with SAP BusinessObjects, the business analytics solution from SAP An architectural concept that new SAP solutions adopt SAP TM models important transactional documents and master data elements in object-oriented environment These objects are addressable via standard access mechanism (method calls) BOPF allows greater enhancement options in non-modifying approach Examples Add additional fields to a bill-of-lading for printing purposes Display these fields in a specific user interface
12

What Well Cover

SAP Transportation Management A quick status update SAP TMs usage of new technology Implementation options and methodologies Lessons learned from early adopters Wrap-up

13

Implementation Options and Methodologies

Proof-of-Concept Evaluate SAP TM with respect to feasibility of solution RDS (Rapid Deployment Solution) Typically covers only small snapshot of entire SAP TM capabilities (e.g., one single process, such as Planning or Tendering) Template-based implementation and POC Delivers end-to-end scenarios (from Order Management, Planning, Freight Costing, Tendering, to Freight Settlement) Conduct blueprint hands-on in model-based approach Classic implementation methodology Primarily paper-based design versus model-based design Big Bang
14

Implementation Options and Methodologies (cont.)

What is InstantTM? Pre-configured, flexible SAP TM template solution enabling significant project acceleration, while reducing cost and risk What is basis for InstantTM Business Content? Engagements with more than 25 globally operating companies What does InstantTM consist of? Pre-configured scenarios, documentation, accelerators, training content, and a model-based implementation methodology Who created it? Release 1, based on SAP TM 8.0, was created in a joint initiative between SAP Value Prototyping and GOPA ITC

Release 2, extended by GOPA ITC, is based on SAP TM 8.1

15

Implementation Options and Methodologies (cont.)

How model-based design applies a hands-on approach to classic blueprint activities that are typically paper-based
Release Model

Config.
TM Template System (TM, ECC, PI)
Clone System

TM Solution Model

Migration & Transport

TM Development & Production System

Iterations

16

Comparison of Implementation Methodologies

Every methodology has pros and cons

Proof-ofConcept
Risk Scope CustomerSpecific Timeline Design Phase Go-Live Time-to-value
Low Very narrow Tailored to customer need 2-12 weeks Scoping Workshop No n/a

RDS
Moderate Narrow Based on standards ~ 3 months Dictated by RDS content Yes Rapid

Templatebased
Moderate End-to-end Based on standards 3 months and longer Model-based in system Yes Instant

Classic
Medium to high End-to-end Often highly customized Typically 6 months or more Typically Paperbased Yes Slow

Big Bang
Very high End-to-end Highly customized Up to 12 months or more Typically Paperbased Yes Very Slow

17

What Well Cover

SAP Transportation Management A quick status update SAP TMs usage of new technology Implementation options and methodologies Lessons learned from early adopters Wrap-up

18

Lessons Learned from Early Adopters

Clarify technical pre-requisites for SAP TM 8.0 early on SAP ECC release Either SAP ECC 6.0 EHP5 or EH4 (SP9) User interface requirements Understand SAP NetWeaver Business Client deployment model (desktop version versus browser-based version) Any portal policies in place at your company? PI implications How will Business Partners be able to interact with TM?

Avoid unnecessary delays by being prepared on the IT infrastructure side

19

Lessons Learned from Early Adopters (cont.)

Phase your SAP TM implementation Helps to define scope more accurately, allowing implementation team to understand the business requirements Better understand limitations of the solution Extract value faster and gain confidence in the solution Many options to phase a TMS implementation By region, business unit, mode of transport, process (inbound vs. outbound), domestic/international

Spend

time early to plan a smart phase approach and win over your business community It is possible to have quick success with SAP TM!
20

Lessons Learned from Early Adopters (cont.)

Master data synchronization between SAP ECC and SAP TM SAP provides a core interface that synchronizes master data between ECC and TM (materials, locations, business partners) However, it will not validate whether the necessary and correct master data is being synchronized Realization and testing phases often do not work with the full master data set that will be used after go-live

Dont

underestimate the effort to set up clean master data in transportation scenarios Assign skilled resources to this task, ideally more than 1 resource Master data is key success factor
21

Lessons Learned from Early Adopters (cont.)

Documentation Starts with the Basis team When setting up new systems (from sandbox to production system), document every step and follow them later Continues with the configuration team Create configuration check lists Ends with the testing cycle Business users need to get used to TM terminology

Thorough

documentation avoids a lot of delays Account for documentation effort during project planning
22

Lessons Learned from Early Adopters (cont.)

Project management Freeze requirements as soon as possible (template-based approach helps to see the solution early) SCRUM-up your review meetings (mini demos keep the rest of your team involved) Grant Implementation Guide (IMG) access carefully Have ABAP resources available full time Involve whoever supports the solution after go-live early enough to allow for knowledge transfer (new technologies!)

Experienced project managers can avoid a lot of pitfalls via hands-on approach
23

What Well Cover

SAP Transportation Management A quick status update SAP TMs usage of new technology Implementation options and methodologies Lessons learned from early adopters Wrap-up

24

Additional Resources

http://blog.gopa-itc.com/ SAP TM blog and commentary to anything related to SAP Transportation Management http://whitepapers.sapinsideronline.com/view.cfm? white_paper=631 GOPA IT Consultants, Inc., SAPs New Transportation Management Solution and What It Means for SAPs Customers (SAPinsider, June 2011). http://help.sap.com/saphelp_tm80/helpdata/en/ 78/3cc7974cdd4edaabcc68254301c80b/frameset.htm SAP TM 8.0 documentation LinkedIn Search for Group SAP Transportation Management to participate in discussions around SAP TM
25

Additional Resources (cont.)

www.marketwire.com/press-release/GOPA-ITC-Introduces-InstantTM-SAP-Transportation-Management-80-On-DemandTemplate-1412443.htm GOPA ITC Introduces Instant TM SAP Transportation Management 8.0 On-Demand Template (Marketwire, March 2011).

26

7 Key Points to Take Home

SAP TM uses a set of new technologies that need to considered during project planning SAP TM is a highly flexible solution that is customizable to customer needs Phase your SAP TM implementation to achieve quick success Get familiar with new user interface aspects, like SAP NetWeaver Business Client and FPM SAP TM gives more power to the end user (caution!) Project Manager should be hands-on to manage scope Leverage a model-based design to apply a hands-on approach to blueprinting and, hence, accelerate your project

27

Your Turn!

How to contact me: Bjorn Bernard Vice President, SCM/TM Practice bjorn.bernard@gopa-itc.com +1 (415) 990 3840
28

Disclaimer
SAP, R/3, mySAP, mySAP.com, SAP NetWeaver, Duet, PartnerEdge, 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. Wellesley Information Services is neither owned nor controlled by SAP.

29