sap tm request management overview

1

SAP TM Request Management Overview

2

© SAP 2009 /

SAP TM Document Structure

RequestMgmt

Trans-portationPlanning

Execution

Billing

Shipment Request

Freight Unit Builder

Shipment Order

Supplier FreightInvoice Request

Freight Unit

Freight Agreement

Tour

Tendering

Customer Freight Invoice Request

Accounting Document

Freight Unit Freight Unit

Tariff

TCCS

Rate

Scale

Optimizer/PlanningCapacity

Request to transport goods from a location to another

locationUnits of freight to be moved

throught networkBasic element for planning

Result of planning, consolidation of freight units on a vehicle,

booked capacity or scheduled means of transport

Subcontracting document for carriers to execute

shipment legs

Tendering of subcontracted load: peer-2-peer, broadcast,

open tenders

Manual or optimizer supported load building and

planning (intermodal)

Customer invoice for sold transportation

services

FI/CO, Internal settlement

Invoice forsubcontratced or

internal transportationservices

ActivityBooking Order Shipment Bill of lading

Transportation Charge Management

Dispatching & Execution

Request Management

Sub-contracting

This slides gives an overview of the SAP TM document model and should be used through-out the training as reference

Revisit this slides during the training from time to time to see the overall document flow

Tendering works with additional business objects: Request for Supplier Quote, Response for Supplier Quote

3

© SAP 2009 /

Business Purpose and RequirementsSolution OverviewStructure and ContentsLayout ModificationsShipment Request Key FieldsInbound Controller

SAP TM Request Management – Agenda

Contents:

Vehicle Scheduling & Resource = VSR. See appendix for more information

4

© SAP 2009 /

SAP TM Request Management – Business Purpose

Business Purpose: Provides the ability to handle all incoming transportation requestsThis includes:

Creation of a transportation proposalCalculation of transportation chargesPrinting documents i.e. confirmation of freight forwarding orderConfirmation of the transportation requestCreation of a Customer Invoice Request for billing

Example for In/ Compatibililties: Modeling of material specific transport requirements (cooled products)

FTL – Full Truck Load

LTL – Less than truck load

Manual and automatic planning

Customer Specific Heuristics and functions can be included

Appointments / Delivery Time Windows

One step Optimization allows for:Assigns RoutePerforms carrier selection

5

© SAP 2009 /

SAP TM Request ManagementLogical Model

The confirmation will not be send in standard to ERP (simular to TPS). Could be done via customer project

6

© SAP 2009 /

SAP TM Request ManagementSAP TM Business Objects – Order Processing

Shipment RequestCustomer Order to ship goods from a source to a destination locationRequest to create one or more shipments in Transportation Management (load split supported) Shipment requests are used for consignmentsBased on EDIFACT IFTMIN contentsShipment Requests can be created based on QuotationsUnique ship-from and ship-to business partner

Freight Request Customer Order to ship goods from multiple sources to multiple destination locationsRequest to create one or more shipments in Transportation Management (load split supported) Based on EDIFACT IFCSUM contentsFreight requests allow i.e. buyer’s pre-consolidation.

Not yet supported in automated planning

Transportation request is in the following used to describe a shipment request or a freight request

The logistics process in SAP TM starts with an incoming transportation request.

A transportation request represents a customer order to move goods from one location to another.

SAP TM supports two different types of transportation requests, the shipment request (close to the IFTMIN standard) and the freight request (close to the IFCSUM standard).

The shipment request represents a customer order to ship goods from a source to a destination location while the freight request represents a customer order to ship goods from multiple sources to multiple destination locations.

The freight request contains several shipment requests

7

© SAP 2009 /

SAP TM Request ManagementRequest Receipt

Depending of the Business need, there are several ways how transportation requests can be received via:

SAP ERP delivery XML documentEnter manual

SAP TM

Shipment Request

Freight Request

Manual

Legacy

ERP

8

© SAP 2009 /

SAP TM Request ManagementEDIFACT Standard

The SAP TM Business Objects are based on the EDIFACT standard

SAP TM does not deliver the standard mapping for the EDIFACT based objects but thefield and structure is similar.

Relevant for receiving transportation requests:Shipment Request : IFTMINFreight Request: IFCSUM

Mapping from the EDIFACT message to an XML Message requires an EDI Converter.

9

© SAP 2009 /



Contents:


10

© SAP 2009 /

SAP TM Request ManagementFeatures

Create and maintain Customer Freight Agreements

Create and maintain Shipment Requests (SRQ)

Create and maintain Freight Requests (FRQ)

Create and maintain Shipment

Create and maintain QuotationsThe user can manually create a quotation.Shipment requests can be created from quotationsQuotations are not used for planning and execution.

Stage determination within a SRQ / FRQ via a Transportation Proposal

Transportation Charge Calculation within SRQ / FRQ

Confirmation for SRQ / FRQ

Route determination during creation of Shipment Request based on TM data.

If using SAP ERP, the Route Determination on the Sales Order and on the Delivery in SAP ERP is not based on TM data. This information would, in effect, be considered “dummy data” as the maintenance of transportation network master data only resides in the TM system.

11

© SAP 2009 /

SAP TM Request ManagementFunctional Overview

Once the transportation request has been captured, the user may create transportation proposals to evaluate possible routing options and to pre-select routes which will be later constraints in planning.

The user can also run a transportation charge calculation (freight cost calculation). This can either be used for evaluating the costs or for confirming the final transportation charges for the customer (freight billing).

Customer Order Limit checks can be performed for a transportation request within SAP TM.

After evaluation of the transportation request the user can send the customer a confirmation of his request. This is also possible during a later stage of the process.

The user can also at any time print the shipment request.

In the transportation management system the transportation network (geography) defines the possible transportation ways. For example if a transport can be performed directly from the sending to the receiving location or if this transport request must be transported via a trans-shipment point (hub) is defined by the transportation network.

During the transportation proposal the user can define additional constraints for the transportation request, for example, based on the result of the routing guide, the user may decide that the order must be delivered via the harbor in New York.

12

© SAP 2009 /



Contents:


13

© SAP 2009 /

SAP TM Request ManagementShipment Request Structure and Contents

ViewsBasic view (basic required data and entry fields on one screen grouped in sections):

PartnersLocationsTransportation DataItems

Detail view (all possible data and entry fields grouped in different tabs):

OverviewItem DataPackingResourcesStagesCharges and Method of PaymentBusiness PartnersEtc.

Dossier contains the reference numbers (i.e. the ERP delivery number). In the query you can search for this field via “Document Reference ID”.

14

© SAP 2009 /


AreasRequest Area (Data provided by ordering party)Planning dataConfirmation Area (Data confirmed to the ordering party)

ContentsPartners (ordering, ship-from, ship-to, carriers, agents,..)Date/times (pick-up, delivery,…)Locations and stages (pick-up, POL, POD, final destination,…)Terms and Conditions (Payment terms , freight terms, …)Freight chargesTexts, NotesAttachmentsGovernmental Procedures (i.e. customs, dangerous goods, seals)Cargo detailsPackaging details

Dossier contains the reference numbers (i.e. the ERP delivery number). In the query you can search for this field via “Document Reference ID”.

15

© SAP 2009 /


Constraints in the shipment request:SR can contain, on the stage level, which MoT must be used, i.e. this SR must use SeaSR can contain certain locations which must be considered in the transport (i.e. harbor Hamburg) must be used.

Link to business objects:Link to the related business objects (i.e. freight units), planned activities, and shipmentsDossier to show related external documents (i.e. delivery number from ERP).

Shipment Request can also contain text items

16

© SAP 2009 /



Contents:


17

© SAP 2009 /

SAP TM Request ManagementShipment Request Layout Modifications

Fields can be hidden...

… not to be seen on the screen anymore.

1 Invisible field

Advantage:

Customize layout to adapt to personal requirementSimplify layout overview as required

18

© SAP 2009 /


Any field value can be set to default for all new shipment requests.

2 Default value

Advantage:

Faster creation of shipment requestSimplify data entry

19

© SAP 2009 /


3 Custom field

Advantage:

????

To be completed

To be completed

20

© SAP 2009 /



Contents:


21

© SAP 2009 /

SAP TM Request ManagementShipment Request Key Fields

Shipment request type(defines certain parameters, such as the number range for the shipment request, whether the request is released automatically or if EM tracking and tracing function is activated).

SRQ-Type

Manually

Automatically via Condition

Default type in Customizing

Automatically from SAP ERP system

22

© SAP 2009 /


Sales Data (such as the sales organization and group, is needed to create the freight agreement as well as for authorization purposes.

Sales Data

Manually

Automatically via Condition

23

© SAP 2009 /


Business partners involved(transportation refers from one shipper to one consignee. The ordering party may be identical with the shipper or consignee.

You can use the More Partnerspushbutton to add further business partners, for example, the bill-to party.

Use Details pushbutton to enter address, e.g. for business partner without master data (one-time business partner).

Locations and dates/times (specifies the locations and the dates/times that apply to the entire transportation of this shipment request. Specify either pick-up or delivery date/time.

After activation of shipment request, the data is transferred to the data for the individual items (Locations/Dates tab]. However, different locations and dates for individual items can be defined.

Use Details pushbutton to enter address of location without existing master data (one-time location).

Dangerous Goods (identifies if dangerous goods are transported. Certain limitations may apply, such as transportation or location incompatibilities.

24

© SAP 2009 /


Incoterms and location (e.g. CIF, DAF, EXW etc. and location at which the transaction costs and responsibilities between buyer and seller getting divided).

Determination of Incoterm and location are reflected in the of calculated transportation costs.

Nature of Cargo and Value of Goods (describe the cargo and value that is transported. This may be important for insurance issues).

Links to define additional data for whole transport, such as:

Transportation stages (transport via a certain harbor to be considered during planning), Vehicle Resources (vehicle taken into account during planning)Packing and Transportation Units (the system takes into account this packaging/TU when creating freight unit items ) to individual items.

25

© SAP 2009 /


Entering the item-specific data (enter the most important data for the individual transportation items, such as the product ID and weight or transportation unit, in the item list).

Specify additional data per item on the tab pages, such as:Stage Assignment (transport via a certain harbor to be considered during planning)Vehicle Resources (vehicle taken into account during planning)Content Identification (Batch number, Serial number, Customer reference number etc. for reference).

Total Quantity (sums-up all items’ weight or other Unit of Measurement

27

© SAP 2009 /

The request data received from your ordering party and the planning data for transportation requests can change during the order management process.

The inbound controller in SAP Transportation Management (TM) checks whether the transportation requests have changed and assesses the impact of these changes on further transportation planning.

You can define whether the inbound controller automatically copies changes made to the request data to the planning data.

The system can perform the following actions:Remove the corresponding freight units from the transportation planInvalidate successor business objectsRegenerate successor business objects Issue alerts

Actions are only triggered in case the planning area is affected.

SAP TM Request Management –Inbound Controller

The inbound controller is only called if the SR was already activated and if the changesoccur in the planning area of the SR

Invalidate / Regenerate successor business objects such as:Planned transportation activities (PTAs)ShipmentsShipment requests (confirmation data)Shipment ordersFreight ordersTours

Inbound updates on the shipment request are stored in the request area. Duringactivation of the shipment request the data is copied to the planning data. If updatesoccur, i.e. delivery in SAP ERP is changed then only the requested area is updatedautomatically. The inbound controller defines how and if this data is copied to theplanning data. This copy can then be performed automatically.

28

© SAP 2009 /

The Inbound Controller works on pre-defined conditionsDefinition how and when data is copied from the request data to the planning data:

/SCMTMS/IC_TKOVR_SRQ /SCMTMS/IC_TKOVR_FRQ

Definition what should be triggered in case of planning relevant changes (quantity, date, location)

/SCMTMS/IC_STRAT

Definition what should be triggered in case of field change/SCMTMS/IC_SRQ_FIELD/SCMTMS/IC_FRQ_FIELD

Possible actions to be triggered:Alerts

Users can register him/herself to specific alert categories

Definition per organizational units (sales org)

Alerts can be viewed via Application Administration -> Alert Inbox

Invalidate planning and following documents / objectsRe-build following documents / objectsRemove freight units from planning

SAP TM Request Management –Inbound Controller

29

© SAP 2009 /

Copyright 2009 SAP AGAll 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, 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 are trademarks or registered trademarks of IBM Corporation.

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

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries.

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 registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

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 construedas constituting an additional warrant.

sap tm request management overview

Documents