Reiner Jabbar IBU Transportation & Logistics January … · SAP Transportation Management 8.1...

SAP Transportation Management 8.1LCL Ocean Freight Scenario

Reiner JabbarIBU Transportation & LogisticsJanuary 2012

© 2012 SAP AG. All rights reserved. 2Confidential

Agenda

1. Scenario Overview

2. Elements of the Scenario1. Organizational Data Setup2. Master Data Setup3. Ocean Freight Prebooking4. Forwarding Order Management5. Freight Order Planning, Execution, and Monitoring6. Load Building – Container Consolidation7. Forwarding Order Settlement – ERP Billing8. Freight Order Settlement – ERP Invoicing

3. Summary

4. Available configuration guides and documentation


LCL Ocean Freight - Scenario Overview

Multimodal LCL * Transport - from forwarding order processing, ocean carrier booking, freight planning, execution & tracking to order settlement

Pre-carriage via scheduled FTL trucking company from station to CFS. Loading of container (20 foot standard dry ) at CFS. Drayage of container via fixed trucking shuttle to port-of-loading

Pickup from shippers of individual LTLshipments.

Main carriage ocean transportation via ocean liner using pre-booked freight capacity

Shippers (Tokyo Region,Japan)

Pickup

Main Carriage

Freight ForwarderStation(Tokyo, Japan )

Port-of-Loading(Yokohama Japan)

Freight ForwarderCFS(Yokohama, Japan )

Pre-carriage


Agenda



3. Summary



Overall Scenario Process Flow


ForwardingHouse

Organizational Units Structure

Company code

OrganizationLevel

Office Level

SalesPurchasing

InterforwardersStation Nagoya

Japan

InterforwardersStation Tokyo

Japan

Operations

InterforwardersStation

Hiroshima,Japan

InterforwardersTokyo, Japan

CC 5000

InterforwardersPurchasing

Japan

InterforwardersSales Japan

InterforwardersOperations

Japan

EnterpriseEnterpriseInterforwardersTokyo, Japan

InterforwardersCFS Yokohama,

Japan

Organization units are used to represent the organizational structure of a company

A company may be structured from different points of view like sales, planning & execution or purchasing

In this scenario the new organizational unit Forwarding House was used, andcombines these 3 views into one.

The Forwarding House depicts a station or business unit. .


Agenda

1. Overall Scenario Process Flow


3. Summary



Master Data

Business PartnersShipper and consignees, ordering party, payer, invoicing party and othersCarriers and other vendors

Vessels and Transportation EquipmentVesselsContainers

Contracts / AgreementsCustomer contractSupplier contract ((haulage, carriers, and other service providers)


Transport Network Elements

LocationsLocation where shipments may change themode of transportExample: port, rail ramp

Carrier ScheduleConnection of loading/unloading locations withvoyage and lay times between portsExample: Vessel loop / schedule

VoyageDetailed trip plan for a specific vessel on a loopon a specific dateDetailed cut-off, departure and arrival times

Sailing ScheduleConnection of loading/unloading locations withvoyage and waiting timesOrigin and destination are container stations, routing is done via POL, PODReference to carrier scheduleExample: CFS-CFS schedule of forwarders

Default routeDefinition of a route consisting of multiple schedules which is used as standard route between two portsExample: Route from Station Tokyo to Station Phoenix with transshipment in Long Beach


Sailing Schedule CFS Yokohama – CFS Los Angeles

Voyage detailsSchedule data for duration, cut-

offs, CFS and port pairs


Default Route Definition: Station Tokyo – Station Phoenix

Combines existing multi modal schedules. Used for

transportation proposals

DeterminantDeterminant if gateway needs to giveexplicit approaval


Container Type Definition

Inside / outside measures / capacity

Temperatureconditions


LCL Ocean Freight Charge Concept using Thru-Rates

PickupStage Type 1

Pre-CarriageStage Type 2

Main-CarriageStage Type 3

On-CarriageStage Type 4

DeliveryStage Type 5

Land Pre-Carriage FreightDimensions;•Source-Destination Location•Weight

•Toll Fee Fix: 25 USD•Fuel Surcharge 3% of Pre-Carriage Freight

Ocean FreightDimensions;•Source-Destination Location•Weight

•THC/Container: 25 USD•B/L Fee Fix: 100 USD

Land On-Carriage FreightDimensions;•Source-Destination Location•Weight


Customer Contract / Agreement (1)

Validity Data


Customer Contract / Agreement: Main Carriage

Calculation Sheet


Agenda



3. Summary



LCL Ocean Scenario - Document Structure Export


Ocean Freight Prebooking – General Data

Assign Booking to an existingsailing schedule


Ocean Freight Prebooking – Assign Schedule

Select Voyage accordingto required date


Ocean Freight Prebooking – General Data

Voyage data copied intobooking

Requirements and Org. Data


Ocean Freight Prebooking – Ports and Detailed Capacity

POL with ETS and cut-off dates

POD withrecovery date

Detailed capacity requirements withconfirmed capacity and container types


Ocean Freight Prebooking – Carrier Confirmation

Confirmation DataCarrier BookingNumber

Carrier BookingNumber


Agenda



3. Summary



Export Forwarding Order – General Data

Service Data

Organisational Data

Requirements Data


Export Forwarding Order – Location & Dates

well Pickup location and date as well as destination location and

requested delivery date


Export Forwarding Order – Stage Data

Select schedule for maincarriage ( default route )


Forwarding Order – Select Transportation Proposal

Select appropriate proposaldefault route

Select appropriate proposalfrom default route


Export Forwarding Order – Stage Data II

Vessel, Voyage and scheduleVessel, Voyage and scheduledata copied from default

route

Incoterm FOB is consideredIncoterm FOB is consideredwhen calculating stage-

related charges

Pre/Main/On-carriage stagesPre/Main/On-carriage stagesautomatically copied intoorder from default route


2nd. Forwarding Order – Business Partners


2nd. Forwarding Order Incoterm DDP – Charge Details

All Stages billed toshipper

All Stages billed toshipper


2nd. Forwarding Order – Item Package Details

Dimensional andquantity data

Dimensional andquantity data


2nd. Forwarding Order – Item Customs Data

Customs data


Agenda



3. Summary



Forwarding Order - Select Booking for Main Carriage

Assigned booking. Optional gateway confirmation

Select booking


Generate Pick Up Order From FWO

Direct creation of pickup order from Forwarding Order

Direct creation of pickup order from Forwarding Order


Pick Up Order Overview in FWOPick up order assigned to pickup stage


Pick Up Order – General DataDistance and durationautomatically calculated


Pickup Order Execution : Arrival at Destination

Reporting Event: Arrivalat Tokyo StationReporting Event: Arrivalat Tokyo Station


Planning of Pre-Carriage ( FTL) I Selects Orders to beSelects Orders to beLoaded onto truck bydrag and drop toschedule


Planning of Pre-Carriage ( FTL) II Freight Order for pre-Freight Order for pre-carriage FTL generatedand forwarding ordersassigned


Pre-Carriage Freight Order : General DataOrganizational data andscheduling dataautomatically determined


Pre-Carriage Freight Order : Sample Output Management


Agenda



3. Summary



Ocean Booking – Cargo Management Data after Loading

Assigned forwardingorders. Utilization rate as a %


Ocean Booking – Send Shipping Instructions to Carrier

Send SI to carrier


Ocean Booking – Stage Overview

Booking consistsof 3 stagesBooking consistsof 3 stages


Ocean Booking – Create Pick-Up Order to Container Terminal


Ocean Booking – Pick-Up Order to Container Terminal


Ocean Freight Booking: Shipped-on-Board

Set status after receivingconfirmation from carrier


Ocean Freight Booking: Event generated from SOB

Event automaticallygenerated after status set


Monitor Pre-Alerts at Port of Destination

Worklist of OceanBookings in Transit


Report Arrival at Port of Discharge Event


Report Arrival at Port of Discharge Event

Arrival at PODReported


Ocean Freight Booking - Cost Overview

Based on freightagreement withcarrier


Agenda



3. Summary



Forwarding Order Settlement Document Structure


Forwarding Order - Charge Overview

Charged as per incoterm FOB


Forwarding Order - Create Forwarding Settlement Document

Trigger creation ofForwarding Settlement Document


Forwarding Settlement Document Create & Transfer

Transfer to ERP Billing


Forwarding Order Document Flow


Corresponding ERP Billing Document


ERP Billing Document for 2nd. Forwarding Order


Agenda



3. Summary



Pick Up Order - Create Freight Settlement Document

Trigger creation ofFreight Settlement Document


Freight Settlement Document Created

Document Hierarchy


Freight Settlement Document Transfer

Transfer to ERP Invoicing


Agenda



3. Summary



LCL Ocean Scenario utilized features & functions new in SAP TM 8.1

Network Master Data & Organization: Forwarding House / Agent (One Organization which covers Sales and Purchasing Extended Location Master (UN/Locode) Enhanced schedule master data: carrier schedules, voyages, default routes, sailing schedule CFS-CFS etc.

Booking / Forwarding Order Management: Movement Attributes (Direction, Shipping Type, Movement Type) Configurable Item types (e.g. type of container)Routing (Configurable definition of stage types, Statistical stages, Differentiation between ordered and actual routing, Default routing), Stage View, Short-Cut functions to directly create job orders (execution orders)Collaboration between Bunisness units and Gateway, B/L creation, Improved visibility of execution status


LCL Ocean Scenario - IIutilized features & functions new in SAP TM 8.1

Cargo Management: Visibility and Document Flow Subcontracting of Pick-Up/Delivery/Dray of Containers to/from Ports, Cargo Status Management, Loading, Unloading Configurable Equipment Type Data (e.g. Container)Consolidation, Deconsolidation

Prebooking / Cartage Management: Cargo Management View allowing flexible container assignmentBook from Schedule Capacity Management Enhanced status management (shipped on board, loaded, unloaded), Container Tracking (via Event Management),


LCL Ocean Scenario - IIIutilized features & functions new in SAP TM 8.1

Forwarding and Freight Contract/Agreement Management:First steps towards Service Product Definition by introducing relevant Data and Attributes (Direction, Mode of Transport, Shipping Type, Stage Type, Service Level) External contract number Simplicity and Usability (Top-Down Maintenance including Calculation Sheet and Rate Tables, Usage of Templates to reduce data entry and increase productivity, …) Master Data Cockpit (Overview Work List showing the relevant data of the agreements including calculation sheets and rate tables)

Rate Tables: Simplicity and Usability (straight forward data entry in the rate table, e.g. all key values and scale intervals, different views, …) Performance improvements Ability to maintain rates w/ partial keys Maintenance of complex rate tables w/ different price units, currencies and calculation types


LCL Ocean Scenario - IVutilized features & functions new in SAP TM 8.1

Calculation Sheets: Simplicity and Usability (On line item level: Validity period, shipping type, stage type, service level; relative rates; reference rate tables)

Charge Calculation: Configurable procedures (e.g. stage level calculation and “through rate and cross-stage” algorithm) Simplicity and Usability (e.g. Aggregated View per Container Type, simplified data entry in overview screen, …) Agreement determination considering organizational and business partner structures,

Customer Billing: Flexible Incoterm Split logic ( FOB, DDP examples )Credit Memo creation

Customs: Handling of Export Declarations (done by the shipper, done by the LSP)


Agenda



3. Summary



Find out More…..Visit the Supply Chain Execution Community

Collaboration / InteractionDiscussion, Questions, BlogsDocument Sharing

Solution InformationOverview AssetsSystem DocumentationImplementation / Configuration GuidesConsulting NotesClassroom Training CurriculumVirtual Knowledge Transfer Sessions

Customer ProjectsSuccess Stories, Videos, etc.Event Presentation Recordings

Join Today…..register via:https://cw.sdn.sap.com/cw/community/sce

and access TM SAP 8.1 details Learn about SAP TM 8.1

© 2011 SAP AG. All rights reserved. 62

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 pr ior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software c omponents of ot her software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix ar e trademarks or r egistered trademarks of IBM Corporation.

Linux is the registered trademark of Linus T orvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are ei ther trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of O racle 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 r egistered trademarks of C itrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W 3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are t rademarks or registered trademarks of SAP AG in Germany and other countries.

© 2012 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or r egistered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the t rademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may var y.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the ac curacy or c ompleteness of the information, text, graphics, links, or ot her items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of t hese materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of h ot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Thank You!

Reiner Jabbar IBU Transportation & Logistics January … · SAP Transportation Management 8.1...

Documents

Transcript of Reiner Jabbar IBU Transportation & Logistics January … · SAP Transportation Management 8.1...