Transportation (LE-TRA)

HELP.LETRA

Release 4.6C

Transportation (LE-TRA) SAP AG

2 April 2001

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

, NT

, EXCEL

, Word

, PowerPoint

and SQL Server

are registered

trademarks of

Microsoft Corporation.

IBM

, DB2

, OS/2

, DB2/6000

, Parallel Sysplex

, MVS/ESA

, RS/6000

, AIX

, S/390

AS/400

, OS/390

, and OS/400

are registered trademarks of IBM Corporation.

ORACLE

is a registered trademark of ORACLE Corporation.

INFORMIX

-OnLine for SAP and Informix

Dynamic Server

are registered trademarks of

Informix Software Incorporated.

UNIX

, X/Open

, OSF/1

, and Motif

are registered trademarks of the Open Group.

HTML, DHTML, XML, XHTML 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, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,

SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com

are trademarks or registered trademarks of SAP AG in Germany and in several other countries

all over the world. All other products mentioned are trademarks or registered trademarks of their

respective companies.

SAP AG Transportation (LE-TRA)

April 2001 3

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Tip

Transportation (LE-TRA) SAP AG

4 April 2001

Contents

Transportation (LE-TRA)............................................................................................. 10

About Transportation.................................................................................................................................12

Transportation Planning Point..................................................................................................................13

Procedures Valid for Entire Company Codes .........................................................................................14

Shipment Types..........................................................................................................................................15

Shipment document...................................................................................................................................20

Information in the Shipment Document...................................................................................................21

Copying Information Relevant for Transportation ...................................................................................24

Shipment Outputs ......................................................................................................................................25

Output Control.........................................................................................................................................27

Determining Output in the Shipment Document .....................................................................................28

Output Type .......................................................................................................................................30

Output Processing...................................................................................................................................31

Selecting a Worklist for Output ..........................................................................................................34

Changing Data Relevant to Output....................................................................................................36

Changing Outputs in Document Processing......................................................................................37

Sending Internal Mail .........................................................................................................................39

Processing Internal Mail ...............................................................................................................40

Output Determination Analysis ..........................................................................................................41

Printing Output ...................................................................................................................................42

Printing Outputs from Document Processing ...............................................................................43

Outbound EDI messages ........................................................................................................................44

Inbound EDI messages...........................................................................................................................47

Report: Output for Shipments .................................................................................................................50

Creating Output Lists .........................................................................................................................51

Freight Codes and Freight Code Sets; Freight Classes.........................................................................52

Determining the Freight Code .................................................................................................................53

Freight classes ........................................................................................................................................55

Transportation Processing Reports.........................................................................................................56

Editing Shipment Lists.............................................................................................................................57

Searching for Deliveries in a Transportation List ....................................................................................58

Transportation Planning............................................................................................................................59

Creating Shipments ...................................................................................................................................63

Creating Shipments.................................................................................................................................65

Screen Info for Delivery Selection...........................................................................................................67

Defining Selection Variants for Shipments..............................................................................................71

Creating Additional Shipment Documents ..............................................................................................72

Moving Deliveries....................................................................................................................................73

Removing Deliveries from a Shipment....................................................................................................75

Creating Shipment Documents for Individual Deliveries.........................................................................76

Planning Proposal ...................................................................................................................................77

Subsequent Delivery Split in Shipments .................................................................................................78

Using Collective Processing to Create Shipments .................................................................................81

Creating Shipments with Collective Processing ................................................................................83

Creating Transportation Chains with Collective Processing..............................................................85

SAP AG Transportation (LE-TRA)

April 2001 5

Reports for Transportation Planning .......................................................................................................86

Shipment Execution Monitor ...................................................................................................................87

Select Shipments: Planning ....................................................................................................................88

Creating Transportation Planning Lists..............................................................................................90

Select Shipments: Utilization of Capacity ...............................................................................................91

Creating Utilization Lists ....................................................................................................................92

Select Shipments: Free Capacity............................................................................................................93

Creating Free Capacity Lists..............................................................................................................94

Automatic Leg Determination ...................................................................................................................95

Automatic Assignment of Deliveries .......................................................................................................99

Identification of Places ..........................................................................................................................101

Leg Determination Categories ..............................................................................................................103

Executing Automatic Leg Determination...............................................................................................105

Examples of Automatic Leg Determination...........................................................................................106

Category 1: According to the Itinerary .............................................................................................107

Category 2: Preliminary/Subsequent Leg for Point of Departure/Destination .................................109

Category 3: Preliminary and Subsequent Leg for Each Delivery ....................................................111

Category 4: With Shipping Type for Preliminary Leg and Subsequent Leg ....................................114

Shipment Stages ......................................................................................................................................115

Creating Shipment Stages Manually.....................................................................................................118

Assigning Deliveries to Stages..............................................................................................................121

Maintaining Partners for Stages............................................................................................................122

Displaying Details About Stages...........................................................................................................123

Deleting Stages in the Shipment Document .........................................................................................124

Moving Stages in the Shipment Document...........................................................................................125

Routes and Shipment Stages ...............................................................................................................126

Planning Activities in the Shipment Document ....................................................................................128

Processing Shipment Documents.........................................................................................................129

Mass Shipment Changes ......................................................................................................................130

Making Mass Changes to Shipments ..............................................................................................131

Packing in the Shipment Document......................................................................................................132

Delivery Item Generation in the Shipment ............................................................................................134

Assigning Service Agents in the Shipment Document..........................................................................136

Maintaining Texts in the Shipment Document ......................................................................................137

Maintaining Planned and Actual Deadlines in the Shipment Document...............................................138

Status in the Shipment Document ........................................................................................................139

Maintaining Status in Shipment Documents....................................................................................140

Transfer of Delivery Dates to Shipments .........................................................................................141

Function Authorization for Status.....................................................................................................142

Dangerous Goods Check......................................................................................................................143

Completing Transportation Planning.....................................................................................................144

Shipment Execution.................................................................................................................................145

Activity Profiles ........................................................................................................................................146

Reports for Shipment Completion..........................................................................................................147

Select Shipments: Check-in ..................................................................................................................148

Creating Check-in Lists....................................................................................................................150

Select Shipments: Shipment Completion..............................................................................................151

Creating Shipment Completion Lists ...............................................................................................153

Posting Goods Issue for Shipments ......................................................................................................154

Transportation (LE-TRA) SAP AG

6 April 2001

Monitoring Shipments .............................................................................................................................155

Information System in Transportation ...................................................................................................156

Information System in List Form ...........................................................................................................157

Graphical Information System...............................................................................................................158

Changing Network Views ......................................................................................................................161

Displaying Itineraries Within a Transportation Network ........................................................................162

Displaying Details on Shipment Stages ................................................................................................164

Displaying Details on Transportation Connection Points......................................................................166

Displaying Deadlines for Deliveries ......................................................................................................167

Displaying a Gantt Chart for Deliveries.................................................................................................168

Calculating Allowed Lateness of Deliveries ..........................................................................................169

Displaying Details on a Delivery............................................................................................................170

Displaying Details on a Shipment .........................................................................................................171

Compressing Stages.............................................................................................................................172

Changing the Graphical Representation...............................................................................................173

Displaying Transportation Change Documents....................................................................................174

Displaying Change Documents.............................................................................................................175

Shipment Cost Processing......................................................................................................................176

Shipment cost document ........................................................................................................................178

Shipment Costing.....................................................................................................................................180

Pricing Procedure Determination ..........................................................................................................182

Freight Cost Estimate............................................................................................................................184

Determining the Calculation Basis ........................................................................................................185

Examples for Calculation Bases ......................................................................................................189

Consistency Check for Freight Costs ..............................................................................................190

Shipment Comparisons.........................................................................................................................191

Determination of Geographical Influencing Factors..............................................................................192

Determining Pricing Date and Settlement Date ....................................................................................194

Tax Determination.................................................................................................................................196

Scales....................................................................................................................................................198

Creating Scales................................................................................................................................200

Assigning Scales for Condition Types .............................................................................................202

Creating Condition Records.............................................................................................................203

Multi-Dimensional Condition Scales ................................................................................................204

Allocating/Loading Condition Records........................................................................................205

Break-Weight Calculation......................................................................................................................206

Creating Shipment Cost Documents Online .........................................................................................208

Creating Shipment Cost Documents with Work Lists ...........................................................................210

Processing the Shipment Cost Document ............................................................................................213

Shipment Costs List: Calculation ..........................................................................................................214

Creating Shipment Document Lists for Calculation .........................................................................215

Scales List .............................................................................................................................................216

Creating Scales Lists .......................................................................................................................217

Shipment Cost Settlement with Service Agent .....................................................................................218

G/L Account Determination ...................................................................................................................221

Assignments for Cost Accounting .........................................................................................................222

Purchase Order Determination .............................................................................................................224

Creation of Accruals..............................................................................................................................226

Shipment Costs as Delivery Costs........................................................................................................227

Self-billing Procedure ............................................................................................................................230

SAP AG Transportation (LE-TRA)

April 2001 7

Carrying out the Self-Billing Procedure............................................................................................232

Carrying out Account Assignment.........................................................................................................233

Transferring Shipment Costs to Accounting .........................................................................................235

Manual Invoice Verification ...................................................................................................................236

Shipment Costs List: Settlement...........................................................................................................238

Creating List of Shipment Documents for Settlement......................................................................239

Billing the Shipment Costs to the Customer.........................................................................................240

Shipment Cost Information in the Order................................................................................................242

Calling up Shipment Cost Information in the Order ..............................................................................244

Interfaces...................................................................................................................................................245

EDI Output.................................................................................................................................................246

External Transportation Planning Systems...........................................................................................247

Logical Communications Processes .....................................................................................................250

Application Transactions of the Interface..............................................................................................255

Configuration Options ...........................................................................................................................259

Technical Communication.....................................................................................................................266

IDoc Description....................................................................................................................................274

EDI_DC - IDoc Control Record........................................................................................................278

Special Fields in the Control Segment of EDI_DC ..........................................................................280

EDI_DD - IDoc Data Record............................................................................................................282

TPSDLS01 - Plan/Change Deliveries / Remove Deliveries.............................................................284

TPSLOC01 - Add/Change Location Master Data ............................................................................285

TPSSHT01 - Create/Change/Delete Shipment ...............................................................................286

SYSTAT01 - Status Information for Transfer...................................................................................287

IDoc Segments, Fields and Domain Values ....................................................................................288

E2EDT1x - Processes ................................................................................................................289

E2KNVAM - Business Hours Profiles .........................................................................................292

E2STATS - EDI Status Record...................................................................................................294

E2TPACC - Action Code ............................................................................................................296

E2TPALC - Authorized Service Provider....................................................................................297

E2TPCOC - Goods Code ...........................................................................................................298

E2TPDIH - Delivery Dimensions at Header Level......................................................................299

E2TPDII - Delivery Dimensions at Item Level ............................................................................301

E2TPDIS – Dimensions of Handling Unit ...................................................................................302

E2TPDLC - Shipment Costs at Delivery Level ...........................................................................304

E2TPDLH - Delivery Header.......................................................................................................305

E2TPDLI - Delivery Item .............................................................................................................308

E2TPEQT - Means of Transport.................................................................................................310

E2TPFRC - Shipment Costs at Header Level ............................................................................311

E2TPLCT - Location Code..........................................................................................................312

E2TPLOC - Location Master Record Address............................................................................313

E2TPNOT - Delivery Texts .........................................................................................................316

E2TPSHA - Transportation Activity.............................................................................................317

E2TPSHH - Shipment Header ....................................................................................................319

E2TPSHI - Delivery in Shipment ................................................................................................321

E2TPSHR - Rail Data .................................................................................................................322

Transportation (LE-TRA) SAP AG

8 April 2001

E2TPSHT - Leg Data in Shipment..............................................................................................323

E2TPSHU - Handling Unit ..........................................................................................................325

E2TPSLS - Transportation Connection Points ...........................................................................326

E2TPSUC - Handling Unit Contents...........................................................................................327

E2TPTIW - Time Frame..............................................................................................................328

E2TPTRM- Location Identification..............................................................................................330

E2TPTRP - Existing Shipment ...................................................................................................334

SAP System Settings and Modifications...............................................................................................336

Error Analysis........................................................................................................................................338

Modifications (Customer Functions) .....................................................................................................342

Transportation Planning in Cooperation with Forwarding Agents .....................................................346

Logical Communications Processes .....................................................................................................347

Application Transactions of the Interface..............................................................................................351

Configuration Options ...........................................................................................................................354

Technical Communication.....................................................................................................................361

IDoc Description....................................................................................................................................368

EDI_DC - IDoc Control Record........................................................................................................371

Special Fields in the Control Segment of EDI_DC ..........................................................................373

EDI_DD - IDoc Data Record............................................................................................................375

TPSDLS01 - Plan/Change Deliveries / Remove Deliveries.............................................................377

TPSSHT01 - Create/Change/Delete Shipment ...............................................................................378

SYSTAT01 - Status Information for Transfer...................................................................................380

IDoc Segments, Fields, and Domains .............................................................................................381

E2EDT1x - Processes ................................................................................................................382

E2KNVAM - Business Hours Profiles .........................................................................................385

E2STATS - EDI Status Record...................................................................................................387

E2TPACC - Action Code ............................................................................................................389

-...................................................................................................................................................390

E2TPCOC - Goods Code ...........................................................................................................391

E2TPDIH - Delivery Dimensions at Header Level......................................................................392

E2TPDII - Delivery Dimensions at Item Level ............................................................................394

E2TPDIS – Dimensions of Handling Unit ...................................................................................395

E2TPDLC - Shipment Costs at Delivery Level ...........................................................................397

E2TPDLH - Delivery Header.......................................................................................................398

E2TPDLI - Delivery Item .............................................................................................................401

E2TPEQT - Means of Transport.................................................................................................403

E2TPFRC - Shipment Costs at Header Level ............................................................................404

E2TPLCT - Location Code..........................................................................................................405

E2TPNOT - Delivery Texts .........................................................................................................406

E2TPSHA - Transportation Activity.............................................................................................407

E2TPSHH - Shipment Header ....................................................................................................409

E2TPSHI - Delivery in Shipment ................................................................................................412

E2TPSHR - Rail Data .................................................................................................................413

E2TPSHT - Leg Data in Shipment..............................................................................................414

E2TPSHU - Handling Unit ..........................................................................................................416

E2TPSLS - Transportation Connection Points ...........................................................................417

SAP AG Transportation (LE-TRA)

April 2001 9

E2TPSUC - Handling Unit Contents...........................................................................................418

E2TPTIW - Time Frame..............................................................................................................419

E2TPTRM- Location Identification..............................................................................................421

E2TPTRP - Existing Shipment ...................................................................................................425

SAP System Settings and Modifications...............................................................................................427

Documentation not Available in Release 4.6C......................................................................................429

Modification Concept (Customer Functions).........................................................................................430

Parcel Tracking for Express Delivery Companies ................................................................................434

Creating a Manifest for Express Delivery Companies ..........................................................................436

Communication via Internet ....................................................................................................................437

Shipment Tendering for Service Agents Through the Internet .............................................................439

Tendering Shipments for Service Agents ........................................................................................441

Transportation Tendering Through a Freight Exchange.......................................................................443

Tracking Information .............................................................................................................................444

Transportation Planning with Forwarding Agents Through the Internet ...............................................446

Transportation (LE-TRA) SAP AG

Transportation (LE-TRA)

10 April 2001

Transportation (LE-TRA)

Purpose

Transportation is an essential element in the logistics chain. It affects both incoming and outgoing

goods. Effective transportation planning and processing ensure that shipments are dispatched

without delay and arrive on schedule. Transportation costs play an essential role in the

calculation of the price of a product. It is important to keep these transportation costs to a

minimum so that the price of a product remains competitive. Efficient transportation planning and

processing helps to keep these costs down.

Integration

As illustrated in the following graphic, you can use the SAP transportation functions to plan and

process:

· Incoming shipments in Materials Management based on purchase orders and shipping

notifications

· Outbound shipments in Sales and Distribution based on sales orders and deliveries

The graphic below illustrates this process:

Goods receipt

Inb.delivery

Transport.

(Goods receipt)

Purch.ord.

Incoming invoice

Goods issue

Outb.deliv.

Transport.

(Goods issue)

Sales order

Billing

Transportation planning and processing is based on the shipment document. This document

facilitates the flow of information from the shipper to the customer and to any service agents who

are involved in the business transaction.

Features

The transportation component includes basic transportation processing functions:

· Transportation planning and shipment completion

· Shipment costs calculation

SAP AG Transportation (LE-TRA)

Transportation (LE-TRA)

April 2001 11

· Shipment costs settlement

· Shipment costs calculation for individual customers

· Billing of customer freight

· Service agent selection

· Management of means of transport and utilities

· Follow-up and supervision of shipments

· Management of shipment costs

These transportation functions can handle planning and processing for both inbound and

outbound shipments. You can control and monitor the entire transportation process from the

planning stage to goods issue at your shipping point (for outbound shipments) or vendor location

(for inbound shipments), through to goods receipt at the customer location or your plant.

Other available functions include: shipment costs calculation and settlement with the service

agent, transfer to accounting, credit memo creation and invoice verification.

This documentation describes procedures in outbound shipment processing. Unless

specifically stated otherwise, the information here also applies to inbound shipment

processing. Differences between the two will be pointed out where necessary.

For information on creating and processing inbound deliveries, see the Confirmations

section of the R/3 Library documentation for Purchasing (MM-PUR).

Transportation (LE-TRA) SAP AG

About Transportation

12 April 2001

About Transportation

The following text describes basic elements of shipment processing, which also include:

· the function of the organizational unit of transportation planning point [Page 13]

· the function of the shipment document [Page 20]

· output determination [Page 28]

· a compilation of the reports [Page 56] available in shipment processing

SAP AG Transportation (LE-TRA)

Transportation Planning Point

April 2001 13

Transportation Planning Point

Definition

You can now carry out transportation planning and shipment completion using a new

organizational unit, the transportation planning point. Basically, the transportation planning point

consists of a group of employees responsible for organizing transportation activities. Each

shipment is assigned to a specific transportation planning point for transportation planning and

shipment completion. You must define the various transportation planning points used in your

organization in Customizing for Corporate Structure before they can be used to perform

transportation functions. You can define this organizational unit according to your company’s

needs, for example, according to geographical location or mode of transport.

The transportation planning point is assigned to a company code, but is otherwise

independent of other organizational units.

Transportation (LE-TRA) SAP AG

Procedures Valid for Entire Company Codes

14 April 2001

Procedures Valid for Entire Company Codes

Use

It is not necessary to assign the transportation planning point to a company code for

transportation planning purposes. However, company code assignment is necessary for

shipment costing and settlement. Internal offsetting of costs between company codes (one

company code takes care of transportation processing for all the firm’s company codes, for

example) is presently not available. These must be manually entered in the financial accounting

ledgers.

Prerequisites

In order for this cross-company-code manual processing to be possible in financial accounting,

cost distribution for shipment costs must occur on the shipment cost item level rather than

delivery level or delivery item level, since in the latter two cases, the delivery’s company code

would be adapted to the transportation planning point’s company code.

A company’s plant in Japan delivers goods to a plant in Houston. The plant in Japan

takes care of the shipment costs until the goods reach the airport in Japan, and the

Houston plant pays the rest of the shipment costs (Japan airport ® Houston airport

® Houston plant).

The transportation chain with cross-company-code billing looks like this:

There are a total of three shipments:

· The first shipment is created by the transportation planning point in Japan and ends at the

airport in Japan. Cost distribution occurs on the shipment cost item level.

· The second and third shipment are created by the transportation planning point in Houston.

In both cases, cost distribution occurs on the shipment cost item level.

SAP AG Transportation (LE-TRA)

Shipment Types

April 2001 15

Shipment Types

Definition

The shipment type contains all the important control features for a shipment, such as the number

range, whether the shipment is inbound or outbound, how leg determination is performed, and

which leg indicator has been set for a shipment of this type. You can also enter a selection

variant for the shipment type. The values defined in the variant appear on the selection screen

when you create a shipment document of this type.

The system supports the following shipment types:

· Individual shipment

· Collective shipment

· Transportation chain

Individual shipment

An individual shipment includes

· One or more deliveries

· One point of departure

· One destination

· One mode of transport

Delivery 1

Delivery 2

Shipping point

Dallas

Customer

Kansas City

1 Shipment document

Collective shipment

A collective (or milk-run) shipment includes

· One or more deliveries

· Several points of departure

Transportation (LE-TRA) SAP AG

Shipment Types

16 April 2001

· Several destinations

· One mode of transport

Delivery 1

Delivery 2

Shipping point

Dallas

Customer 1

Kansas City

Customer 2

Chicago

1 Shipment document

Transportation chain

A transportation chain is useful if you are dealing with deliveries that will be transported using

multiple modes of transportation (and are thus processed by different departments at the

transportation planning point).

Transportation Chain

Delivery 1

Shipping point

Dallas

Port of departure

New York

Port of destination

Hamburg

Customer

Cologne

Shipment doc. 1 Shipment doc. 2

Shipment doc. 3

The department responsible for transportation by land organizes truck shipments and

another department organizes ships and their cargo for goods shipment by sea.

Each mode of transport (truck and ship) requires individual shipping papers. Each

mode of transportation requires separate transportation papers, meaning that you

need to create a shipment document for the overland leg and another for the

overseas leg of the journey.

SAP AG Transportation (LE-TRA)

Shipment Types

April 2001 17

If shipments use more than one mode of transportation, it is a good idea to create a

transportation chain. Because you will have a separate shipment document for each

mode of transportation, you can maintain separate output, texts, statuses, and so on.

Example for using a transportation chain

At shipping points 0001 and 0002 in Germany, a large number of deliveries are to be sent to

customers in the United States by the beginning of December. You and your customers agreed

that part of the shipment be sent carriage paid and the other part carriage, insurance, freight paid

to (CIF) New York only (meaning that the end customer must pay carriage, insurance and freight

from New York to the final destination).

The goods are to be transported by land within Germany, by sea from Hamburg to New York,

and by land again in the United States. It is, of course, possible to document the entire process in

a shipment document. However, problems can arise if certain parts of the shipment functions

are used:

· For instance, data on the shipment status always refers to the entire shipment document (for

example, the status “Loading finished”). However, in this example loading takes place

several times.

· For the same reason, an assignment of dates and texts to a handling unit is difficult because

these can change within the shipment document. The very definition of a handling unit is in

itself problematic.

· Output to be created in combination with the shipment document contains all data for the

entire shipment document. When the truck driver leaves the shipping point, his printout also

contains data that refers to the ship. This is unnecessary and a nuisance. Processing several

required preliminary legs at different times also requires that output be printed at different

times.

In cases like this, it makes more sense to use a transportation chain in which deliveries are

passed on in a series of different shipments. In the above example, you would create several

shipment documents in the system: ten preliminary leg shipments by truck, one main leg by ship,

and if necessary, eight subsequent legs by truck again. That way, you avoid the problem of

assigning deadlines, output, or texts to the packaging material.

With that in mind, you might put together your transportation chain like this:

1. Create a main leg

At transportation planning point 0001, you create a main leg shipment for all deliveries to

be sent by ship from Hamburg to New York City at the beginning of December. There

should be a special shipment type set for this set in Customizing. This could include the

following settings:

– Set the leg indicator field for the shipment header to Main leg. The system will

recognize that this shipment must be linked to other shipments.

– The leg determination type for this shipment type should be ‘ ‘.This means that no

automatic leg determination will be carried out. This is reasonable since the

Hamburg-to-New York leg does not include any points of departure or destinations

from the delivery (however, this data will be taken into account during leg

determination).

Transportation (LE-TRA) SAP AG

Shipment Types

18 April 2001

– Route determination resulting in the Hamburg-to-New York route may have already

been carried out in the delivery. If you want to copy this route automatically into the

main leg shipment, you can specify in Customizing that routes must be copied into

the shipment document. Copying starts as soon as you set the Planned status in the

shipment document.(Note that the route in the deliveries must be unique.) At the

same time, the service agent can also be copied automatically from the delivery

provided you have made the appropriate settings in Customizing and that the same

service agent has been assigned to the deliveries.

When the deliveries were created, they were given transportation planning status A,

meaning they were ready for transportation planning. Now, after creating the main leg

shipment, these deliveries have transportation planning status B, meaning that they have

been partially planned (since a main leg shipment needs preliminary and possibly

subsequent legs).

2. Create preliminary legs

The preliminary leg shipments that are used to send the goods from shipping points 0001

and 0002 to the ship in Hamburg can be organized much faster than the ship itself, which

is why they are planned at this time. You must now combine all deliveries in the main leg

shipment into one or more preliminary leg shipments. You can do this in the Create

Shipment transaction.

To do this, you must select all deliveries in the main leg shipment. The transportation

planning status of the delivery may be helpful in determining which deliveries are in the

main leg shipment since their status is now set to B instead of A. Of course, this is not

sufficient as a single selection criterion. He can enter further selection criteria that are

used during delivery selection for the main leg. This may be impractical since you may

not now what the selection criteria were or too many deliveries may be selected.

Therefore, it is better to specify the shipment number of the corresponding main leg

shipment in the Reference to line when selecting deliveries. If you do not know the

number, press F4 and a selection screen will appear. In this case, a further selection

screen for shipment number selection appears. On this screen, you can specify the

person who created the shipment document, the point of departure, and the date in order

to determine the number of the main leg shipment.

You create shipments using the worklist you defined. If each delivery corresponds to

exactly one truckload, the planner can call up the function Edit ® Automatic planning ®

One dlv. one shipment, which creates a separate shipment for each delivery.

You should use the following settings:

– Set the leg indicator to preliminary leg.

– Set the leg determination type to 1 (leg determination according to pick-up sequence

and itinerary).

– Do not copy the route from the delivery. It may be a good idea to copy the service

agent.

When the Planned status is set, leg determination begins, but the route is not copied

from the deliveries. It will determine the pick-up sequence. In addition, the system

suggests Hamburg as destination since the deliveries are part of a main leg shipment

that runs from Hamburg to New York.

SAP AG Transportation (LE-TRA)

Shipment Types

April 2001 19

When the shipment is saved, the system updates the delivery status. The status for the

carriage paid deliveries remains B (partially planned), since the second part of the

Incoterm was left blank and the system assumes that a subsequent leg is required. The

status of the deliveries with CIF New York is set to C (completely planned) since the

second part of the Incoterm has been specified and the system assumes that a

subsequent leg is not necessary.

3. Create subsequent legs

You create subsequent legs the same way you create preliminary legs. Use these

settings:

– Set the leg indicator to subsequent leg.

– Use category 1 for leg determination.

– Do not copy the route from the deliveries.

In order to create these shipments, search for deliveries with a transportation planning

status of B. The system then finds only those deliveries for which a subsequent leg is to

be created. If the Planned status is set, it also carries out leg determination. The system

automatically suggests ‘New York’ as a point of departure, since the main leg shipment

ends in New York. The sequence in which the goods are delivered (itinerary) is

determined by the sequence in which the deliveries are displayed on the screen. If the

subsequent leg shipments are saved, the transportation planning status of the

corresponding deliveries is set to C (completely planned) since these deliveries now

have preliminary, main, and subsequent legs.

Following these steps ensures that every delivery is included in the transportation chain.

In the example, there are ten preliminary leg shipments to Hamburg followed by a main

leg shipment and eight possible subsequent leg shipments in the United States. In this

way, a group of deliveries forms a network of shipments.

4. Monitor the transportation chain

In order to monitor the shipments, choose Environment ® Transportation info

® Shipment list or Environment ® Transportation info ® Transportat.network

depending on whether you are processing orders, deliveries, or shipments. Worklists for

transportation planning and processing may also provide an overview. To generate a

worklist, enter one of the shipment numbers that make up the transportation network in

the Reference to line. The system will then select all shipment documents in the network.

Transportation (LE-TRA) SAP AG

Shipment document

20 April 2001

Shipment document

Definition

The shipping document is the central element of transportation planning and shipment

completion. It contains all the information necessary for carrying out transportation.

Use

You create shipment documents using a worklist. Different types of shipment documents have

been defined to enable you to reflect in the system the various forms of transportation used in

your organization.

For example, you use the individual shipment document to plan and process the transportation of

goods from one location to another. You use the collective shipment to move goods from one or

more points of departure to one or more destinations. Separate document types deal with

inbound and outbound shipments.

You can use shipment documents to:

· Combine deliveries into one inbound or outbound shipment

· Specify shipment stages

- Legs

- border crossing points

- load transfer points

· Assign goods to handling units

· Assign service agents

· Specify planned transportation deadlines

· Record actual transportation deadlines

· Specify output required for transportation (such as shipping papers or EDI messages)

· Define transport-relevant texts

SAP AG Transportation (LE-TRA)

Information in the Shipment Document

April 2001 21

Information in the Shipment Document

Use

You can record the following information in the shipment document:

· Means of transport

· Service agents

· Deadlines

· Status

· Tendering status

· Route

· Texts

· Output

· Dangerous goods

Features

Means of transport

The means of transport necessary for a shipment is reflected in the system as a handling unit.

These handling units contain information about tare weight and -volume of the means of

transport as well as the weight of the packed handling unit. Information about the country

providing the means of transport, details about the driver and travel time are also included in

these handling units. Handling units that have already been created for delivery items are copied

into the shipment document where they can be packed further, if necessary. Delivery items that

have only been partially packed or not packed at all can be packed in the shipment documents.

See also:

Packing in the Shipment Document [Page 132]

Service agents

You can store information about the service agents (such as forwarding agents or customs

agents) who are involved in the transportation process. You can record this information at the

header or stage level of the shipment document.

See also:

Assigning Service Agents in the Shipment Document [Page 136]

Deadlines

The time required for organizing and performing the various transportation activities is stored as

planned and actual deadlines in the shipment document. This information can be used for

monitoring and analysis purposes.

See also:

Maintaining Planned and Actual Deadlines in the Shipment Document [Page 138]

Transportation (LE-TRA) SAP AG

Information in the Shipment Document

22 April 2001

Transfer of Delivery Dates to Shipment [Page 141]

Status

Once you have completed the planning activities for a shipment document, you can set the

Planned status. As soon as you set this status, you can no longer carry out planning activities for

this shipment document (remove deliveries from the document or move deliveries within the

document, for example). Leg determination is carried out automatically. You can define which

activities take place when you set the status in the Activity Profiles [Page 146] section.

A traffic light icon indicates the overall status of the shipment document. The icon can be

interpreted as follows:

· No traffic light:

No planning activities have been performed

· Red light:

Transportation planning is complete

· Yellow light:

Loading at the plant has either started or is complete

· Green light:

Shipment has been processed and is en route or has arrived

See also:

Maintaining Status in the Shipment Document [Page 140]

Tendering status

The tendering status describes the current status of a shipment with respect to negotiations with

a forwarding agent through the Internet.

See also:

Requesting Tenders for Service Agents Through the Internet [Page 439]

Route

If the route and the forwarding agent are the same in all deliveries, they are copied from the

deliveries into the shipment document when you set the status to Planned.

Country-specific restrictions with respect to total weight of the shipment on a particular route

require recording the restriction already at the route level. This upper level can be specified at

route level and is then taken into consideration during shipment processing. If the allowed total

weight is exceeded during delivery assignment to the shipment, the system issues a warning

message. The shipment can then be changed accordingly. The fields are displayed on the

planning screen.

During order processing and delivery processing, this check is not taken into consideration.

Further transportation-relevant information is copied into the shipment document if you define the

Copying Routines [Ext.] in the Implementation Guide.

SAP AG Transportation (LE-TRA)

Information in the Shipment Document

April 2001 23

Texts

Additional information that could help the transportation process to run smoothly can be entered

as text at header level in the shipment document. This information can be accessed by all

business partners involved in the process. Shipment text types are defined in Customizing and

assigned to text determination procedures. Text determination procedures are defined in the

shipment document type.

See also:

Maintaining Texts in the Shipment Document [Page 137]

Output

Output processing is performed just as it is in other areas of the Sales and Distribution module:

using the condition technique. The types of output that have been set in Customizing for

transportation and for which you have created condition records appear in the shipment

document and apply to the entire document. The output type ALTR has been defined for

transportation in the standard SAP System. You can change this output type to suit your needs.

See also:

Output Determination in the Shipment Document [Page 28]

Dangerous goods

To conform to the legal requirements with respect to the transportation of dangerous goods, it is

important that you check in the shipment document whether transportation of such goods is

actually allowed.

Here different dangerous goods checks can run either automatically or through manual request.

For example, you can check whether the transportation of certain materials is allowed in certain

modes of transport. In this way, you can prevent deliveries or shipments from leaving the

company when they are not suited for transport, according to dangerous goods regulations.

Also, you can create dangerous goods documents using the respective dangerous goods data.

See also:

Dangerous Goods Check in the Shipment [Page 143]

Transportation (LE-TRA) SAP AG

Copying Information Relevant for Transportation

24 April 2001

Copying Information Relevant for Transportation

Use

When you create shipments, you can use information relevant for transportation as selection

criteria. For example, you can group together outbound deliveries with means-of-transport type

“Truck” and means of transport “Small truck” into one shipment. In sales orders and/or

deliveries, you can specify that the following information is relevant for transportation:

· Means of transport

· Shipping type

· Type of means of transport

· Special processing

Integration

In order to copy proposals for dates and times from the delivery, you must create a connection

between the shipment dates and delivery dates. Copy routines serve this purpose.

Prerequisites

The system uses the copy routine to copy data from sales orders into deliveries and then into

shipments. In order for the system to do this, you must first carry out the following activities in the

Implementation Guide (IMG):

· Specify copy control for deliveries [Ext.]

· Define shipment types [Ext.]

Features

Information relevant for transportation is copied from the order into the header of the outbound

delivery, and thus supplies split criteria for outbound deliveries. For example, two order items

with different shipping types, means of transport or means-of-transport types cannot be

combined into the same outbound delivery.

However, information can be copied from the outbound deliveries into the shipment, provided it is

unique data. You create a handling unit in the shipment for the means of transport (likewise only

if this is unique). The copying takes place when you set the status “Planned”. Here you must

store an appropriate copy routine in Customizing for the shipment type.

The system also checks the capacity of the mode of transport in the delivery. If this capacity is

exceeded, you will receive a warning message.

Since the means of transport can also be specified on the Pack screen, the means of transport

entries in the sales order, delivery header and the corresponding packing information could vary.

Changes made on the Pack screen have no effect on the transportation-relevant information in

sales orders and deliveries.

SAP AG Transportation (LE-TRA)

Shipment Outputs

April 2001 25

Shipment Outputs

Purpose

In addition to printing and faxing, electronic data exchange is becoming increasingly important as

a method of communicating transportation data. Senders (shippers) transmit their shipping

orders and transportation information to their service agents (forwarding agents, ship owners,

customs agents). The service agents organize the transportation process and ensure that it is

carried out smoothly. A logistics transportation chain involving multiple modes of transport and

service agents often occurs during the shipment. To ensure efficiency in such a situation, it is

especially important to get all necessary information to all parties involved at the earliest possible

point in the process.

Process Flow

Sample process flow for electronic data exchange:

Shipping Inbound Processing

1. The shipper sends the forwarding agent

a partially- or completely planned

shipment (shipping order).

The forwarding agent receives the

transportation requests and assumes

responsibility for planning the shipment details.

2. The forwarding agent sends information

about the completely planned shipments

back to the shipper.

The vendor receives the completely planned

shipments from the forwarding agent.

3. The shipper or forwarding agent informs

the customer about the upcoming shipment

(shipment notification).

The customer receives information about the

upcoming shipment.

SAP System

(Forwarding agent)

SAP System

(Forwarding agent)

SAP System

(Customer)

SAP System

(Customer)

Rough planning

SAP System

(Sender)

SAP System

(Sender)

Delivery

Shipment

Detailed planning

Delivery

Shipment notification

Transportation (LE-TRA) SAP AG

Shipment Outputs

26 April 2001

For more information on output control, see the Output section in the online Implementation

Guide.

You can find more information about output administration in Working with Output in Sales and

Distribution [Ext.].

SAP AG Transportation (LE-TRA)

Output Control

April 2001 27

Output Control

Use

You can use output control to automate either messages or subsequent processing of partner-

specific messages. The application uses interfaces that were predefined in Customizing for

conditions to call up output control.

You can use these interfaces to describe different constellations of data and the processing

methods of your choice. If one of these data constellations occurs in the application, it triggers

the corresponding processing method (either synchronously or asynchronously). You can define

processing methods in many different ways (as print output or as a shipping IDoc for EDI, for

example).

Prerequisites

The Logistics Execution application always uses output control for issuing output. You can

maintain settings for output control in Customizing in Message control [Ext.] activity.

Features

The condition technique is used in the SAP System for formulating data constellation conditions.

If the current application data matches one of the conditions defined in Customizing, output

determination [Page 28] was successful and an output proposal is generated. You can then

change this proposal (edit [Page 31]) and the output will be processed [Ext.] either immediately

or at a specified time. The output's processing status is saved in a status record and a

processing log is created.

See also:

Message Control Structure [Ext.]

Output control only supports certain transmission media. For more information, see Transmission

media [Ext.].

Activities

In Message Control Customizing [Ext.], you can define rules according to which the system

accesses individual condition records.

You can define concrete messages as condition records in the application: Message definition in

the application [Ext.].

Transportation (LE-TRA) SAP AG

Determining Output in the Shipment Document

28 April 2001

Determining Output in the Shipment Document

Use

The output determination function enables you to perform tasks for shipping and transportation

output for delivery and transportation processing with your customers and within your company.

You can create shipment output and output for handling units. Staff members in your company

can send messages. For example, the system automatically finds the message that a bill of

lading is to be printed.

Integration

The output control checks whether the application data matches the condition records (that were

defined in Customizing). If this is the case, one or several messages are “found”, and they can

then be processed (for example, sent electronically). The condition records are searched for

during output determination on the basis of a predefined hierarchy.

The Output determination function is used in output control. You can use the output control

function to exchange information with internal and external partners. Output control consists of

the following functions that are described in the cross-application documentation CA – Output

Control:

· Output Determination [Ext.]

· Output Processing [Ext.]

· Status Management [Ext.]

Prerequisites

For output determination, the condition elements and condition records need to be defined since

the output determination runs using the condition technique.

In Customizing, you can define the conditions in which the output types you define will be

selected. For more information on output control, see the Output section of the Implementation

Guide.

Features

The system can propose output automatically for a document. You can change this output in the

document.

Output determination occurs when:

· Accessing the output screen during shipment processing

· Saving a shipment document that is new or has been changed

See also:

For more information on output, refer to the following documentation:

Application Documentation

Basis BC – SAP Communication: Configuration

SAP AG Transportation (LE-TRA)

Determining Output in the Shipment Document

April 2001 29

Cross-application functions Output Control [Ext.]

SAP Business Workflow [Ext.]

You will find Customizing settings and examples in the above documentation.

Example

Bill of lading

1. Output determination starts in V7STRA with output type CMR1 and the assigned access

sequence.

2. The access sequence defines the fields with which the key for the condition table is read.

(for example, condition table B017: shipment type of the shipment is read)

3. If the condition record is found, the system proposes an output with the output attributes

found in the table.

4. The output proposal (possibly not yet processed) is stored after the document is posted

as an output status record in the NAST table.

Transportation (LE-TRA) SAP AG

Output Type

30 April 2001

Output Type

Definition

There are predefined output types for shipments. You can display a list of predefined output

types by using the input help. The output type contains parameters, such as partner functions,

that are valid for all outputs that are assigned to that type.

· Shipment outputs include: ALTR general shipment, bill of lading, shipping order, EDI in

general (SEDI), shipment notification, goods receipt/issue slip.

· Delivery outputs include: delivery note, mail (internal output), shipping notification,

warehouse order, and package labels.

The output type signals the use of a printed form such as a delivery note that will be sent to a

customer. An output type can also be an internal, electronic-mail message that you send to a

mail recipient (partner).

Use

The output type is assigned, per transmission medium [Ext.], to a form routine in a program that

is called up to process the output (output status record).

For more information, see Defining Output Types [Ext.].

Integration

The output type comes after the procedure in the condition element hierarchy. The output type is

assigned exactly one access sequence (next hierarchical level), which in turn is assigned one or

more condition tables (next and lowest hierarchy level).

Condition Components: Sample Hierarchy [Ext.]

SAP AG Transportation (LE-TRA)

Output Processing

April 2001 31

Output Processing

Use

Output proposals are presented to you in an application transaction. You can then either change

(process) the proposed output before you save the object (bill of lading, for example).

Features

The output proposal that was created includes, among other things, the output's recipient, the

transmission medium and the processing time for subsequent (automatic) processing. You

can change all these parameters in the application transaction.

When you create an output manually, you can specify the output type [Page 30], transmission

medium, print parameters, partners, and language.

You can display a determination analysis, which displays the outputs that were found in the

procedure. You can display details for an output that show which application data the condition

table was read with.

After you post the document, the processed output proposal is recorded in the NAST table as a

message status record [Ext.].

You create a shipment with forwarding agent 1, and the system proposes a shipping

order that is to be sent via EDI.

The determination analysis shows that the Shipment type and Transportation planning

point application fields were read and a condition record was found.

Output partners

The output recipient of the output that is sent is defined as the output partner. Use the input help

to choose an output partner (sold-to party, Electronic Data Interchange -EDI mail recipient,

forwarding agent, or employee responsible, for example).

During output determination, the output recipients are determined from the partners listed in the

document. In other words, the partner function is used to determine the recipient (forwarding

agent, for example).

You can enter a specific output recipient in this field. Your entry overrides the standard partner

that appears. Output recipients that are entered specifically must also be listed in the document

as partners.

Output's transmission medium

The type of processing is determined by the transmission medium [Ext.]. You can specify, for

example, that an output be printed out or sent by mail, fax or EDI.

Processing status

Possible status values:

Status 0 (not yet processed)

1 (processed - no errors)

2 (processed - with errors)

Transportation (LE-TRA) SAP AG

Output Processing

32 April 2001

Dispatch time

The dispatch time is stored in the condition record. You can have the system process and update

the output either immediately or at a later time. You can use the RSNAST00 report or a special

application function that triggers processing in order to process the outputs at a later time. The

following are linked to the dispatch time as follows:

· Time 1: Send via periodically-planned jobs (next processing run) or start sending from

RSNAST00 online by using the ABAP/4 Development Workbench

· Time 2: send via jobs (as in time 1) with additional time specification of the processing

time: start from RSNAST00 in the background at a defined time (Tools ® Administration,

Jobs ® Job definition).

RSNAST00 processes all output status records that meet the selection criteria and

whose processing times or intervals either include the current date or lie in the past.

Processing times or intervals are fields in the message status record [Ext.] in the NAST

table. These fields are not filled with information in the standard system. Please note:

The first Time field is different from the second Time field. In order to have the system

complete these fields, you can define a corresponding routine in a report as an attribute

of an output type. This routine will then be run for each output determination of this

output type.

· Time 3: Send using an application transaction (specific entry): Call up an application

function.

Print transaction VT70

Only outputs with the status 0 and the dispatch time 3 are included in initial

processing.

An output can be sent more than once. This is useful, for instance, if technical problems

or other problems occurred in the first print output. The system copies the output that

was selected; you can then process and send this copy.

In repeat processing, only outputs with status 1 or 2 are selected (dispatch time is not

taken into account). Only outputs with status 2 are selected for error processing (once

again, dispatch time is not taken into consideration).

There can be several versions of the same output that only differ in date or time of

creation (because of repeat processing or multiple sending, for example). During

selection, the system always chooses the last (chronologically latest) output from a group

of similar outputs.

· Time 4: Send immediately (during save in the application). The output is processed

when the document is updated.

Activities

See also:

Selecting Output Worklist [Page 34]

Changing Data Relevant to Output [Page 36]

Changing Outputs in Document Processing [Page 37]

Sending Internal Mail [Page 39]

SAP AG Transportation (LE-TRA)

Output Processing

April 2001 33

Transportation (LE-TRA) SAP AG

Selecting a Worklist for Output

34 April 2001

Selecting a Worklist for Output

Use

Before you can process messages, you must first select a worklist.

Procedure

1. Call up the respective task:

Function Menu Path What you should know

Shipping

Initial Screen Shipping

[Ext.]

Processing delivery output

Communication/Printing ®

Outbound Delivery Output

Processing loading output

Communication/Printing ®

Loading Output

Processing handling unit

output

Communication/Printing ®

HU output

Shipment

Initial Screen

Transportation [Ext.]

Processing transportation

output

Communication/Printing ®

Transportation Output

You can process transportation

output as well as output for

documents that have a reference to

a shipment (for example, billing

documents, deliveries). To do this,

select the respective field and enter

the selection criteria in the

appropriate section

With background processing

Tools ® ABAP Workbench

® Development ® ABAP

Editor

Print transactions VT70

2. Enter the output type, the transmission medium, and, if required, further selection

parameters. If you want to call up a worklist of all outputs that have not been processed

successfully, enter 3 in the field Processing mode. The system displays all the incorrect

outputs, and you can process them once again.

3. If you wish to look at the worklist first and/or then make changes, choose Program ®

Execute.

If you wish to process the output as a background job, choose Program ® Execute in the

background. In this case, you cannot execute any changes.

4. If you wish to process output, select the respective output.

SAP AG Transportation (LE-TRA)

Selecting a Worklist for Output

April 2001 35

For more information on processing output, refer to the section Processing Existing

Output [Page 37].

5. Choose Edit ® Process.

The system processes the selected output.

6. If you wish to receive a log after output processing, choose Goto ® Log.

Transportation (LE-TRA) SAP AG

Changing Data Relevant to Output

36 April 2001

Changing Data Relevant to Output

Prerequisites

You must have the worklist created. For more information on creating a worklist, refer to the

section Creating a Worklist for Output [Ext.].

Procedure

Select the respective output and execute the task you require.

Function Menu Path What you should know

Changing print parameters

Edit ® Printer

specification

Use this task if wish to enter the same

print parameters for several outputs.

All the selected outputs receive the print

parameters from the screen Printer

specification if there is 1 (Print) in the

field Transmission medium.

Issuing output (printing,

sending fax, and so on)

Edit ® Process

After processing, output is highlighted as

follows:

· green (processed successfully)

· red (processed incorrectly)

Changing details data

Goto ®

Communication

Use this task if wish to enter the

separate print parameters for each

output.

You may only change the parameters for

the transmission media Printing and

Telefax. The parameters are merely

displayed for all other transmission

media.

Creating screen display

Goto ® View

The system displays the first selected

output.

Display processing log

Goto ® Log

The system creates a separate log for

each output.

SAP AG Transportation (LE-TRA)

Changing Outputs in Document Processing

April 2001 37

Changing Outputs in Document Processing

Prerequisites

Normally, the system automatically proposes data for output control in the sales document. If you

must process outputs, choose the following menu path that corresponds to the sales document

you are processing:

Document Menu Path

Delivery

Extras ® Delivery output ® Header or Item

Shipment

Goto ® Output

If you selected several outputs, use Goto ® Next detail screen to process the next output.

Procedure

Function Menu Path What you should know

Repeating an output Select an output and

choose Repeat output.

An output can be sent more than

once. This is useful, for instance, if

technical problems or other problems

occurred in the first print output.

The system copies the output that

was selected; you can then process

and send this copy.

Sending a change output Select an output and

choose Change output.

If you have made changes in a

document, you can create and send

change outputs for outputs that are

based on this document and have

already been sent.

The system copies the output that

was selected; you can then process

and send this copy.

An indicator identifying this output as

a change output then appears in its

Change column.

Changing print parameters Select an output and

choose Communication

method.

The output must be set for printing: for

example, the Medium field must be

set to 1 (Print output) or 2 (Fax).

Changing send data Select an output and

choose Further data.

Dispatch time, for example.

Processing date and status are also

displayed here.

Transportation (LE-TRA) SAP AG

Changing Outputs in Document Processing

38 April 2001

Carrying out output

determination analysis

Goto ® Determin. analysis

This function is described in detail in

Output Determination Analysis [Page

41].

The system displays all accesses.

You can display the fields that

triggered each individual access by

choosing the folder that you want

more information about.

SAP AG Transportation (LE-TRA)

Sending Internal Mail

April 2001 39

Sending Internal Mail

Use

You can use internal mail to send a message referring to a sales document to the person

responsible for that document. That person can then call up the document directly from your mail

in order to check or process it, for instance.

Features

The procedure for processing internal mail can be found in Processing Internal Mails in SD [Ext.].

You can attach certain criteria to automatic proposals so that you only receive an automatic

message from order processing if the value of an order is greater than $1000, for example. For

more information, see Example Message Determination: Processing Condition Component

Hierarchies [Ext.].

See also:

Formatting SAPoffice Messages [Ext.]

Transportation (LE-TRA) SAP AG

Processing Internal Mail

40 April 2001

Processing Internal Mail

Procedure

To process an internal mail that you have received, proceed as follows:

1. On the initial screen, choose Office ® Inbox.

1. Select the mail you wish to process and choose Document ® Display.

The system displays information on the created document, such as document number,

name of creator, and so on. If the creator has entered a text in the mail, this text will also

be displayed.

1. Choose Edit ® Process.

You automatically branch to the transaction specified in the mail. After document processing

you return to the mail. You can repeat this process as often as required.

You can process the mail directly without displaying the content if, after selecting the

mail, you choose Edit ® Process.

SAP AG Transportation (LE-TRA)

Output Determination Analysis

April 2001 41

Output Determination Analysis

Use

A determination analysis can be run for outputs. For example, you can find out which keys were

used to find outputs and whether output determination was successful.

Features

An output determination analysis provides you with the following information:

· Origin of the output proposal (via condition record or from the customer master, for example)

· Output search results (which outputs were found in the corresponding output procedure and

which outputs could not be found)

· Access information (which accesses occurred for outputs that were found using condition

records and the results of the accesses)

· Key combinations (with which key combinations, or combinations of fields, did the accesses

occur?)

Activities

1. Change the corresponding document. For a shipment document, for example, you would

choose:

a. Shipment screen

b. Shipment ® Change

2. Goto ® Output

3. Goto ® Determin. analysis

Determination analysis only works if you are in the change or create mode of the shipment

document. (In other words, this function does not work in display mode.)

There is no output determination analysis for the picking list.

Transportation (LE-TRA) SAP AG

Printing Output

42 April 2001

Printing Output

Use

You can, for example, print a delivery note for a delivery.

Prerequisites

The following prerequisites apply:

· The document must have an output that is designated for printing. The output can be

· Transmitted directly by the system to the document through Output Determination

[Page 28]

· Entered manually into the document.

If an output is allowed according to the output determination procedure, you can enter this

output into the document manually.

For more information, see Output Determination Procedure Technique [Ext.].

To enter an output manually (or display an existing output), choose in the overview screen of

the document Extras ® Output ® Header or Item ® Edit. You must have 1 (Print output) set

in the field Transmission medium for the output to be printed.

For more information on output, refer to the section Output Processing [Page 31].

· In addition the column Status must have the traffic light set to yellow. If the traffic light is set

to red, you must repeat the print by selecting the output and choosing Repeat output.

Features

You can print in the following ways:

· Through the worklist (online)

· Through the worklist (background job)

See also:

For further information on the worklist, refer to the section Selecting Worklist for Output [Page 34]

SAP AG Transportation (LE-TRA)

Printing Outputs from Document Processing

April 2001 43

Printing Outputs from Document Processing

Prerequisites

The general prerequisites listed in Printing Outputs [Page 42] apply.

Additionally, the following settings must be made on the output screen for the output that you

want to print.

· In the second Time column: 3

Procedure

Document Menu Path

Delivery

(Create/Change) Outbound delivery à Issue delivery output

Shipment

(Shipment screen) Goto à Output

Function Menu Path

Printing an output Specify which printer

Displaying an output on a screen Specify which screen

Transportation (LE-TRA) SAP AG

Outbound EDI messages

44 April 2001

Outbound EDI messages

Use

Shipment documents are normally sent in one of the following two situations:

1. The shipper sends the forwarding agent a partially- or completely-planned shipment (transfer

order).

2. The shipper or forwarding agent informs the customer about the upcoming shipment

(shipment notification).

Prerequisites

You need to create an output type that you can use to send the shipment document per

Electronic Data Interchange (EDI). Output type SEDI is provided for this purpose. You can also

make a copy of this output type and tailor it to your needs, if necessary. The transmission

medium must be set to 6 (EDI).

The following condition components must be maintained:

Condition component Value

Access sequence 0001

Output type SEDI (or copy of SEDI)

Schema V7STRA, for example

Application V7

Processing routine RSNASTED program, FORM-routine EDI-PROCESSING

General data

Select Access to conditions and Multiple sending of output. Leave

all other fields blank.

Time 3 (explicit request), as an example

Transmission medium 6

Partner function CR (Carrier) or SH (Ship-to party)

IDoc interface

You must also enter the following values for outbound partner profiles and any additional

outbound parameters under message control.

Field Value

Output type SHPMNT or SHPADV

Partner type LI (vendor/creditor) or KU (customer)

Partner function CR (Carrier) or SH (Ship-to party)

Port SUBSYSTEM

Output mode

Collect IDocs, for example

Basic type SHPMNT03

Application V7

Output type SEDI, or your modified copy of SEDI

Process code SHPM

SAP AG Transportation (LE-TRA)

Outbound EDI messages

April 2001 45

1. Scenario: The shipper sends the forwarding agent a partially- or completely-planned

shipment (transfer order).

You create a shipment document that is either partially or fully planned (depending on

whether the transportation planning details will be carried out by the forwarding agent or if

you do it yourself).

Depending on what point in the process the message determination is set to take place,

the EDI is triggered immediately after posting (time 4) or when explicitly requested (time

3).

Scenario: The shipper or forwarding agent informs the customer about the upcoming

shipment (shipment notification).

You have a fully-planned shipment document (that you have created and planned

yourself, or that the forwarding agent has planned for you).

Depending on what point in the process the message determination is set to take

place, the EDI is triggered immediately after posting (time 4) or when explicitly

requested (time 3).

R/3

(Forwarding agent)

R/3

(Forwarding agent)

R/3

(Customer)

R/3

(Customer)

R/3

(Sender)

R/3

(Sender)

Delivery

Shipment

Shipment notification

Transfer order

To improve performance, you should make sure that when you use IDocs for special

purposes that you only generate segments that include the data you need. You can

hide certain segments by using a reduction technique.

Transportation (LE-TRA) SAP AG

Outbound EDI messages

46 April 2001

To make the necessary settings in Customizing, choose Cross-Application

Components ® Distribution (ALE) ® Processing IDocs ® Set up segment filtering.

SAP AG Transportation (LE-TRA)

Inbound EDI messages

April 2001 47

Inbound EDI messages

Use

You can create or change shipment using EDI output.

In this way, the following tasks are possible:

Collective Goods Traffic

The forwarding agent picks up deliveries from the vendor during the preliminary leg. Then the

agent puts together the shipment for the main leg and passes on this information to the customer

as a shipment notification. Now the customer can easily post a goods issue for the entire

shipment (more precisely, for the deliveries it contains).

Transportation planning

A vendor supplies the forwarding agent with the outbound deliveries as transfer requirements.

The forwarding agent plans the shipment and informs the vendor of the result, who can then start

the appropriate activities for goods issue of the respective outbound deliveries. To create

shipments at the customer site, you can use message SHPADV (shipment message or shipment

notification). To create or change your own shipments, use message SHPMNT. Both messages

are based on IDoc type SHPMNT03; processing is executed through process code SHPM. You

can maintain these parameters within the EDI partner profile. For this purpose, select Tools -

>Business Communication -> IDoc -> Partner profile.

Output for deadline and status

The forwarding agent confirms the planned or actual deadline via EDI, including the status for the

end of the shipment with the respective time.

The inbound deliveries to which the shipment refers must exist in the system. The

reference is made through the delivery number of the vendor (collective goods traffic)

or directly (transportation planning). Therefore, it is necessary to notify the customer

of the deliveries where collective goods traffic is concerned. You can do this using

the DESADV (shipping notification) message. It is not possible to create deliveries in

the initial processing of shipments, as required for direct shipments. Also, no change

is made to the delivery (with effects on material planning) if there is a change in the

shipment (planned arrival date, for example).

Prerequisites

The deliveries that the shipment refers to must exist in the receiving system.

Features

Control of IDoc Receipt SHPMNT03

You can control the processing of the receipt of IDoc SHPMNT03 using the specifications in the

segment E1EDT18. For this purpose, you can use the following E1EDT18-QUALF qualifiers:

QUALF = ORI Shipment document is created

QUALF = CHA Shipment document is changed

Transportation (LE-TRA) SAP AG

Inbound EDI messages

48 April 2001

QUALF = PID Specification of an identification field for the shipment

document.

Processing and copy control

If you use the qualifier ORI or CHA, you can control the data transfer strategy from the IDoc into

the shipment document using the parameter field. Basically, there are four strategies which are

indicated by the first character in the E1EDT18-PARAM field. The respective marker characters

are in the second character in the E1EDT18-PARAM field:

0 IDoc fields are always copied; empty ID fields cause document fields to be deleted (standard

case; will be processed if no specification is made).

1 IDoc fields are only copied if they are empty

2 Similar to strategy 0, but an IDoc field is not transferred if it is filled completely with the

marker character.

3 Similar to strategy 1, but an IDoc field is not transferred if it is filled completely with the

marker character.

Example of segment E1EDT18:

QUALF PARAM

ORI 2!

Copy all fields, except those containing a !

CHA 3%

Copy fields that are filled in and delete fields with %%%%... in the

document.

Control of identification

You can control the identification link between the IDoc and the shipment document in segment

E1EDT18 with qualifier PID, which can appear up to three times per IDoc.

In most day-to-day cases, the PID qualifier is not present. In this case, the E1EDT20-TKNUM

field is copied into VTTK-EXTI1 during creation. The system assigns the shipment number VTTK-

TKNUM internally. If there is a change, the system searches for a suitable shipment document

using the following criteria:

E1EDT20-TKNUM = VTTK-EXTI1

and

E1ADRE4-EXTEND_D = VTTK-TDLNR (where you must have E1ADRE4-

EXTEND_Q = 300)

If PID qualifiers are specified in E1EDT18, no data is copied from TKNUM to EXTI1.

If the shipment number is to have external number assignment, you can specify the shipment

number as a primary identification with E1EDT18-QUALF = PID and E1EDT18-PARAM =

TKNUM. The shipment is created using VTTK-TKNUM = E1EDT20-TKNUM, and is searched for

with the same condition if you want to change it.

SAP AG Transportation (LE-TRA)

Inbound EDI messages

April 2001 49

You can use the IDoc fields EXTI1, EXTI2, and TKNUM for the identification.

Examples of segment E1EDT18:

QUALF PARAM Function for creating Function for changing

None None Copy E1EDT20-TKNUM to

VTTK-EXTI1

Internal number assignment

Search for shipment with VTTK-EXTI1 =

E1EDT20-TKNUM and VTTK-TDLNR =

E1ADRE4-EXTEND_D

PID TKNUM External number assignment

VTTK-TKNUM = E1EDT20-

TKNUM

Search with VTTK-TKNUM = E1EDT20-

TKNUM

PID EXTI1 Internal number assignment Search with VTTK-EXTI1 = E1EDT20-

EXTI1

PID

TKNUM

EXTI2

External number assignment Search with VTTK-TKNUM = E1EDT20-

TKNUM and VTTK-EXTI2 = E1EDT20-

EXTI2

PID

EXTI1

EXTI2

Internal number assignment Search with VTTK-EXTI1 = E1EDT20-

EXTI1 and VTTK-EXTI2 = E1EDT20-

EXTI2

Activities

You must also enter the following values for outbound partner profiles and any additional

outbound parameters under message control.

Field Value

Output type SHPMNT or SHPADV

Partner type LI (vendor/creditor)

Basic type SHPMNT03

Application V7

Output type SEDI, or your modified copy of SEDI

Process code SHPM

Transportation (LE-TRA) SAP AG

Report: Output for Shipments

50 April 2001

Report: Output for Shipments

Use

You can use this report to create a list of outputs that meet your selection criteria. You can

specify whether your list should include outputs related to shipments, deliveries, handling units,

or invoices. You can then display or process the output of your choice from the list.

Features

You can enter shipment numbers, planned shipment completion dates, transportation planning

points or partners as selection criteria. You can also specify that you want to see only those

outputs relating to shipments or deliveries, for example. Use output type, transmission medium

and processing mode to further limit the search.

From the list of outputs that appears, you can start immediate processing, make changes to the

processing parameters, or display either the output itself or its corresponding log. The log records

how often the output is processed or printed.

This report only lists outputs that have been found via output determination or

defined manually in the selected documents (shipments, deliveries, or invoices, for

example). Output determination is not carried out in this report.

See also:

Creating Output Lists [Page 51]

SAP AG Transportation (LE-TRA)

Creating Output Lists

April 2001 51

Creating Output Lists

Procedure

To create an output list, proceed as follows:

1. Choose Logistics Execution ® Goods Issue for Outbound Delivery ®

Communication/Printing ® Transportation Output.

The Output for Shipments screen appears.

2. To use other selection criteria, choose Edit ® All selections.

To define reoccurring selection criteria, you can create a variant for the selection screen

using Goto ® Variants ® Save as variant. You can then retrieve these variants with

Goto ® Variants ® Get.

3. Enter the criteria you want to use for selecting the output.

4. Choose Program ® Execute.

The system then gives you a list of all the outputs that match the selection criteria.

Transportation (LE-TRA) SAP AG

Freight Codes and Freight Code Sets; Freight Classes

52 April 2001

Freight Codes and Freight Code Sets; Freight Classes

Definition

Forwarding agents or railroads use freight codes (and sets of freight codes) to classify the goods

they transport. Freight codes are specified in the transportation papers, and some are specific to

rail or road transportation.

These are compiled in freight code sets published by forwarding agents and the railroad

authorities and are used specifically when referring to rail or road transport. Specific freight codes

are defined in each freight code set.

Freight code Description

4001 Methyl alcohol

4002 Glycol

4003 Alcohol

4004 Formaldehyde

Freight classes are made up of one or more freight codes and are one of the criteria for shipment

costing.

SAP AG Transportation (LE-TRA)

Determining the Freight Code

April 2001 53

Determining the Freight Code

Process Flow

Determining the freight code is carried out in two steps:

Step 1

Automatic freight code determination uses the following criteria:

· Country of origin

· Shipping type (truck, rail, etc.)

· Forwarding agent (forwarding agent freight group in the vendor master)

If an external transportation planning system is being used, then the freight code set can also be

defined by the route.

Step 2

Automatic freight code determination uses the following criteria:

· Freight code set

· Material (material freight group in the material master)

This allows you to determine the freight codes of all materials in a shipment.

The following illustration shows an example of freight code determination.

Transportation (LE-TRA) SAP AG

Determining the Freight Code

54 April 2001

Carrier

freight

group

Shipping type

Country of origin

Rail freight code set

Freight code:

9000002 Graphics card

9000003 Hard drive

9001000 Monitor

9001001 Keyboard

Step 1:

Step 2:

Material freight group

Freight code:

9000003

Hard drive

SAP AG Transportation (LE-TRA)

Freight classes

April 2001 55

Freight classes

Definition

A freight class is a group of freight codes used to calculate shipment costs.

Use

The freight class can be used as one of the criteria for figuring shipment costs. For example, you

could enter condition records for freight rates that specifically refer to a combination of tariff zone

and freight class. The freight code is used if the material that is being shipped should figure into

the shipment costs.

Integration

One or more freight codes are assigned to a freight class within a freight code set.

The following illustration is an example of how freight code set, freight code and freight class are

interrelated.

Rail freight code set

Freight codes:

9000002 Graphics card

9000003 Hard drive

9001000 Monitor

9001001 Keyboard

9001002 Speaker

Freight class 01

Freight class 02

Transportation (LE-TRA) SAP AG

Transportation Processing Reports

56 April 2001

Transportation Processing Reports

Use

The following reports are available in transportation processing:

Select Shipments: Planning [Page 88]

Select Shipments: Utilization of Capacity [Page 91]

Select Shipments: Free Capacity [Page 93]

Select Shipments: Shipment Completion [Page 151]

Select Shipments: Check-in [Page 148]

Displaying Transportation Change Documents [Page 174]

Report: Output for Shipments [Page 50]

Scales List [Page 216]

Shipment Costs List: Calculation [Page 214]

Shipment Costs List: Settlement [Page 238]

SAP AG Transportation (LE-TRA)

Editing Shipment Lists

April 2001 57

Editing Shipment Lists

There are various functions which you can perform in both the transportation planning and

shipment completion worklists to help you locate the documents you want to edit.

Transportation List Views

To switch from the normal to the status view of the transportation list and vice versa, choose Edit

®Change view.

Search Function

To find documents with a particular characteristic (for example, you want to find all documents

with a specific forwarding agent), proceed as follows:

1. Choose Edit ®Find ®Find delivery.

The screen Delivery selection view appears where you can specify characteristics of the

delivery you are looking for.

2. Enter one or more delivery characteristics.

3. Choose Program ® Execute.

The system finds all deliveries that match your selection criteria.

Sort Function

You can navigate within the transportation list much easier by sorting it according to criteria such

as shipment type or planned loading date. To do this, proceed as follows:

1. Place your cursor on the column heading according to which you want to sort your list.

2. Choose Edit ® Sort ® Ascending order to sort the list in ascending order. If you want to

sort the list in descending order, choose Edit ®Sort ®Descending.

The system sorts the list based on the column header on which you placed your cursor

and, depending on the menu option you select, in either descending or ascending order.

List Viewer Functions

Some lists are managed with a special tool, the ABAP List Viewer. The List Viewer features

various functions that you can use to tailor the list to your needs. This tool allows you to make

settings such as which columns appear in what order, for example. For more information, see

ABAP List Viewer [Ext.].

Transportation (LE-TRA) SAP AG

Searching for Deliveries in a Transportation List

58 April 2001

Searching for Deliveries in a Transportation List

To locate specific deliveries within a transportation list, proceed as follows:

1. Choose Edit ® Find ® Find delivery.

2. Enter your selection criteria (for example, the number of the ship-to party).

3. Choose Program ® Execute.

The system issues a list of all the shipment documents in the list which contain deliveries

that match your selection criteria.

SAP AG Transportation (LE-TRA)

Transportation Planning

April 2001 59

Transportation Planning

Use

Transportation planning involves all the activities that must be performed before the shipment

leaves the shipping point. These activities include:

Acquiring the services of a forwarding agent

Organizing the means of transport

Specifying the route for the shipment

Defining the stages for covering this route in the most efficient way.

There are different types of shipment document types to deal with the various forms of

transportation (for example, individual shipments or collective shipments). The shipment

documents are used as a basis for carrying out transportation planning. This includes, among

other things, the execution of the above activities.

Prerequisites

Before you can carry out transportation planning, the following requirements must be met:

For outbound shipments

Specify in Customizing for Transportation that a delivery type for the shipping notification

is relevant for transportation planning and shipment completion.

Specify a route in the deliveries.

Specify in Customizing for Transportation that the routes in the deliveries are relevant for

transportation planning and shipment completion.

Make sure the ShpmtBlReason (shipment blocking reason) field is blank. You can find

this field in the delivery header on the transportation screen.

Once these requirements have been met, the system automatically sets the transportation

planning status to A (Not yet planned) in the Trns.plan.status field in the delivery header.

For inbound shipments

Specify in Customizing for Transportation that a delivery type for the inbound delivery is

relevant for transportation planning and shipment completion.

Assign all items to the same plant in the inbound delivery. The system carries out a

corresponding check.

Features

There are different types of worklists and lists you can use to perform various tasks in

transportation planning:

Shipment list

You use the shipment list to establish which inbound or outbound deliveries are due for

shipment. After you have created the list, you can

– Create the necessary

shipment documents for particular inbound or outbound

deliveries

Transportation (LE-TRA) SAP AG

Transportation Planning

60 April 2001

– Specify the order in which the inbound or outbound deliveries (or shipment items) are to

be delivered

Transportation planning list

When you are creating the shipment due list, you do not usually have all the information

you need to complete transportation planning. For instance, you probably do not know

which forwarding agent will take care of goods shipment at this stage. You could also

decide not to finish the entire planning for a shipment in the shipment list because the

capacity for this shipment is not yet used to the full. Once you have the information you

require or once there are enough deliveries to fill the shipment, you can use the

transportation-planning list to locate these documents and complete transportation

planning.

This list contains shipment documents for which planning activities still have to be

completed and which match selection criteria that you define. You can use the list as a

basis for performing transportation planning activities, such as organizing a means of

transport, scheduling loading activities and acquiring the services of forwarding agents.

Besides this “normal” transportation planning list, there are additional lists that you can

use to find shipments according to certain categories. For instance, in the Utilization list,

you could enter the shipment’s degree of utilization as a percent, according to weight and

volume, as one of the selection criteria.

Activities

You must first determine which inbound or outbound deliveries are due for transport. A worklist

for this purpose is created using selection criteria. Deliveries or outbound deliveries are then

assigned automatically or manually to shipment documents. Relevant data, such as shipping

points and destinations, is then used to determine the route and to break it into stages.

The route in the delivery can be used as one of the criteria for selecting deliveries

due for shipment. It is not, however, copied into the shipment document. More

information is available in the following sections.

You can make the appropriate settings in Customizing so that routes and service

agents are copied from the deliveries into the shipment documents.

Using the Route as Selection Criterion

The route in the delivery can represent:

One or more legs

A link between the point of departure and the destination

The destination region

The route in the shipment document differs from the route in the delivery. The following examples

should illustrate the difference between a route in the delivery and a route in the shipment

document.

Example of a route as a link between departure and destination locations

The following graphic shows the route as a link between the point of departure and the

destination

SAP AG Transportation (LE-TRA)

Transportation Planning

April 2001 61

Sales

Dispatch

Transportat.planning

Selection: Route NA

Order 1

Delivery 1 Delivery 2

Order 2

Route NA =

North Atlantic

Possible routes:

NA1 Antwerpen - New York

NA2 Rotterdam - New York

Route: NARoute: NA

Route: NA

Cologne - Brooklyn

Route: NA1

Route: NA

Munich - Long Island

Delivery Route

1 NA

2 NA

In the delivery document, the route NA indicates that both deliveries are to be transported across

the North Atlantic.

During transportation planning, you select all deliveries with the route

NA and then look for a ship

that can transport the deliveries at the required time. You find a ship that sails from Antwerp to

New York and enter the route

NA1 in the shipment document header.

Example of a route as a target area:

Routes can also be destination regions. The following graphic shows routes R5, R6, R7, and so

on as destination regions.

Transportation (LE-TRA) SAP AG

Transportation Planning

62 April 2001

Departure

point

During transportation planning, you select all deliveries with route R5. You notice that there is still

room in the truck. To make use of this capacity, the deliveries with route

R6 are selected as well.

SAP AG Transportation (LE-TRA)

Creating Shipments

April 2001 63

Creating Shipments

Purpose

When you create shipments, you can choose deliveries according to certain selection criteria and

then assign them to the new shipment.

Delivery #

Shipping point

Transportation planning point

On the overview screen you can, for example, assign deliveries to the shipment manually or

automatically, or also remove deliveries from the shipments. On the selection screen that is

within the overview screen you can also enter selection criteria for the relevant deliveries or

inbound deliveries.

Process Flow

1. Activities on the Selection Screen

On the selection screen, you can enter selection criteria for the documents (inbound or outbound

deliveries) that you want to assign to a shipment. You define the selection criteria that are

displayed on the selection screen beforehand. You can use selection variants to specify these

criteria. On the selection screen, you specify whether you want the documents due for shipment

to be assigned automatically to a shipment document or whether you want to assign them

manually once the shipment has been created. There are separate selection screens for

inbound and outbound shipments. The selection screen for creating an inbound shipment

contains, for example, the selection criteria Vendor and Destination point: Plant; in the case of an

outbound shipment, the criteria are Ordering party and Destination point: Shipping point.

Transportation (LE-TRA) SAP AG

Creating Shipments

64 April 2001

2. Activities on the Selection Screen

The overview screen is divided into two sections: One section contains one or several shipment

documents, and the other section lists the deliveries that have not yet been assigned to shipment

documents. If the documents have not been assigned automatically to a shipment document,

you can do this manually on the overview screen. You can also create new shipment documents

and move shipment items (inbound or outbound deliveries) within a shipment or from one

shipment to another. In addition, you can remove shipment items from the shipment if, for

example, you run out of room on a truck. If you decide that you do have the capacity to select

additional deliveries or inbound deliveries for additional shipments, you can create a new

shipment from the overview screen.

Two views are possible: For example, one view displays the address of the ship-to party, and the

other displays the name of the ship-to party. Different data is made available for shipments and

shipment items (delivery, inbound delivery).

The settings can be changed through trees and table controls.

You cannot place outbound deliveries and inbound deliveries together in the same

shipment document. Nor is it possible to assign Items from a delivery or an inbound

delivery to different shipment documents. You must decide at the delivery stage

whether order items can be shipped together in one delivery and therefore require

only one shipment.

See also:

Creating Shipment Worklist [Page 65]

SAP AG Transportation (LE-TRA)

Creating Shipments

April 2001 65

Creating Shipments

Procedure

To create a shipment, proceed as follows:

1. From shipment [Ext.], choose Create ® Single Documents.

The Create Shipment: Initial Screen appears.

2. Enter a transportation planning point.

3. Choose the required shipment type from the list field.

4. Enter a selection variant, if necessary.

You can assign a selection variant to each shipment type in Customizing. When you

create a shipment list for the document type to which a variant has been assigned,

the system automatically proposes these values on the selection screen.

5. Choose Edit ® Select further deliveries.

Depending on the type of shipment you enter, the selection screen for inbound or

outbound shipments will appear. Enter your selection criteria for creating a shipment. If

you have specified a selection variant or if one has already been assigned to the

shipment type, the system will automatically propose these values in the relevant

selection fields.

For further information on delivery selection, refer to the section Screen Info for Delivery

Selection [Page 67].

6. Enter the selection criteria you require.

The system automatically resets the Trns. plan. status field from value A (not yet

processed) to B (Partially processed) and the Total gds mvt stat. field to value A (not

yet processed). Based on these values, the system selects all deliveries that need

shipment documents. The system defines deliveries that need shipment documents

as all deliveries with either no transportation planning or only partial transportation

planning (because certain shipment stages still need to be defined, for instance).

7. If you want the deliveries selected to be assigned automatically to a shipment document, you

must select the Include deliveries in processed shipment field.

8. Choose Enter.

The system returns a list of deliveries that match your selection criteria. The system

automatically creates a shipment document and assigns the selected deliveries to it if

you have selected the Include deliveries in processed shipment field. If you have not set

the indicator, you must make the necessary assignments manually.

Transportation (LE-TRA) SAP AG

Creating Shipments

66 April 2001

9. By choosing Edit ® Selection log, you can obtain information on the selection run such as

the total number of deliveries and items selected, the selection criteria used, and any

problems that occurred.

10. If you still have room in the shipment, you can repeat the selection procedure and fill the

shipment with more deliveries. To repeat the selection procedure, choose Edit ® Select

further deliveries.

For information on processing the worklist, see:

Defining Selection Variants for Shipments [Page 71]

Creating Additional Shipment Documents [Page 72]

Moving Deliveries [Page 73]

Removing Deliveries from a Shipment [Page 75]

Creating Shipment Documents for Individual Deliveries [Page 76]

See also:

Shipment Types [Page 15]

SAP AG Transportation (LE-TRA)

Screen Info for Delivery Selection

April 2001 67

Screen Info for Delivery Selection

On this screen you define the selection criteria for selecting deliveries that are to be assigned to

a shipment.

You can select deliveries, for example, according to geographical factors, due date, and status of

the delivery.

The general term "Delivery" stands for deliveries, return deliveries, or inbound deliveries.

How the Delivery Selection Works

When you create or change a delivery, the shipment planning status of the delivery is queried.

The shipment planning status indicates the current processing status of the delivery, that is, how

far processing has developed so far.

The shipment planning status can have the following settings:

' ' Not transportation-relevant

A Transportation-relevant, but not yet processed

B Transportation-relevant, partially processed

C Transportation-relevant, completely processed

For the user to be able to select the delivery, the shipment planning status must have the setting

"transportation-relevant".

You can display the shipment planning status as follows:

1. In the Shipping Screen [Ext.], select the activity Change outbound delivery.

2. Select a delivery.

3. Choose Goto ® Header ® Shipment.

On the detailed screen for Change Outbound Delivery, you see the status on the tab page

Shipment in the field TranspPlngStat.

For more information on the field for the shipment planning status, refer to the F1 help.

If the shipment planning status is "transportation-relevant", you can select the delivery through

the Shipping Screen [Ext.] ® Create Shipment..

If you cannot select a particular delivery, go through the items in the checklist.

Checklist

· If the shipment planning status of the delivery is not "transportation-relevant", check the

following items:

- If the delivery type is marked as transportation-relevant, proceed to the Implementation

Guide, and, under Logistics Execution ® Transportation ® Shipments ® Maintain

Transportation Relevance, choose the activity Maintain transportation relevance for

delivery types [Ext.].

- If a route is entered in the delivery, and the route is marked as relevant for transportation,

proceed in the Implementation Guide under Logistics Execution ® Transportation ®

Transportation (LE-TRA) SAP AG

Screen Info for Delivery Selection

68 April 2001

Shipments ® Maintain Transportation Relevance [Ext.] and choose the activity Maintain

transportation relevance for routes.

- No transportation blocking reason may be set in the delivery!

Choose Change Delivery, and proceed to the detailed screen through the path Header ®

Shipment. Under the tab page Shipment, you can see whether the field TrBlckResn is

filled.

- If a transportation blocking reason is set in the delivery, you can change this in the

Implementation Guide by calling up the activity Logistics Execution ® Transportation

® Shipments ® Maintain transportation relevance ® Maintain transportation

relevance for delivery types.

- If you have an inbound delivery (delivery type EL), the delivery type must be marked in

the Implementation Guide as relevant for transportation.

- If you change the Customizing setting after you have created a delivery, you must

change and save the delivery. Then the system calculates the status on the basis of the

new Customizing setting. Now call up the function Change delivery and save the

delivery.

· As soon as you have checked that the transportation planning status is set to "relevant for

transportation", you can choose the function Select delivery when creating or changing the

shipment.

Check the following points:

- You can assign either deliveries / return deliveries or inbound deliveries to a shipment. A

mixture of documents, however, is not possible.

On the basis of the shipment type that is assigned to a shipment, the system recognizes

whether the shipment is incoming or outgoing. To do so, it uses the indicator Completion

type, which you can specify in Customizing for shipment type under the following activity:

Logistics Execution ® Transportation ® Shipments ® Define Shipment Types [Ext.].

On the detailed screen of a shipment type, you can set the following processing types

through the field Completion type:

'1' means Outbound shipment loaded

You can select deliveries / return deliveries for this shipment.

2 means Loaded incoming shipment

You can select inbound deliveries.

- You can define selection criteria for a shipment type. In the Implementation Guide,

choose Logistics Execution -> Transportation -> Shipments -> Define Shipment Types

[Ext.], and then select the field Selection variant in the screen section Proposal on the

details screen for Change shipment.

In a selection variant, you can enter values in certain fields and also make them

invisible on the screen. This can be useful, for example, if you select deliveries from

shipping point 0001. Note that with the selection variant in the example above you

cannot select deliveries from shipping point 0002.

SAP AG Transportation (LE-TRA)

Screen Info for Delivery Selection

April 2001 69

- Note that the screens for deliveries / return deliveries and inbound deliveries differ from

one another.

- Make sure that the transportation planning status is specified correctly. The standard

values are A and B. If you wish to select deliveries that are already fully planned, you

must choose the status Transportation-relevant fully processed. Deliveries with the

transportation planning status Not relevant for transportation are not selected.

- Make sure that you have maintained the goods movement status correctly. If you wish to

select deliveries that are already fully planned, you must choose the status

Transportation-relevant fully processed.

- If you wish to select return deliveries, deliveries, or both, select the respective radio

button in the type of delivery.

- Make sure when you specify several selection criteria that these are linked by an AND

condition, not an OR condition.

Example 1: You have specified ship-to party XY and

also entered shipping condition 01.

In the system, however, there are no deliveries with this ship-to party

and this shipping

condition. With the criteria you have entered, the system has not found any delivery.

Example 2: In the section "Reference" you have entered shipment number A

and order

number B. Through these specifications you want to select all deliveries that are included

both in shipment A and in order B. The system does not select any deliveries that are in

order B, but not in shipment A.

· If the system was not able to select deliveries during creation of a shipment, you can display

the selection log. On the overview screen Shipments and Deliveries, choose the activity Edit

® Selection log.

The following can be possible reasons:

- The delivery is blocked by another user.

- The delivery does not contain any items.

- The delivery does not contain any items relevant for transportation. You can set the

transportation relevance for delivery items in Customizing under the following activity:

Logistics Execution ® Transportation ® Shipments ® Maintain Transportation

Relevance ® Maintain transportation relevance for delivery item types.

- The delivery is a return delivery, but (also) contains outbound delivery items. Since the

point of departure and destination are no longer uniquely defined, these deliveries can no

longer be processed in the transportation system.

In the case of return deliveries with reference to an order, note that in the copy control

function in Customizing a copy routine is stored that also copies this indicator from the

order item into the delivery item.

For this purpose, proceed to the Implementation Guide and choose the activity Specify

Copy Control for Deliveries [Ext.] under Logistics Execution ® Shipping ® Copying

control.

- The delivery contains return items.

- If you have an inbound delivery, the plant in the items must be unique.

Transportation (LE-TRA) SAP AG

Screen Info for Delivery Selection

70 April 2001

Example

Special selection options for outbound deliveries:

· Selection by status of credit limit check in the delivery selection

During delivery selection you can only select deliveries where the credit limit has not been

exceeded. You can also define a selection variant for this selection.

· Selection by picking status

You can define that only deliveries where picking is not yet complete are selected.

SAP AG Transportation (LE-TRA)

Defining Selection Variants for Shipments

April 2001 71

Defining Selection Variants for Shipments

Procedure

In the shipment document:

1. Enter the selection criteria that you want to save as a variant on the selection screen.

2. Choose the button for selection options and select the required variant from the list.

3. Enter a code and name for the selection variant.

4. Save your data.

The system informs you that the selection variant with the code you specified in Step 3

has been saved. You can now use this selection variant when you create shipment

documents.

In the shipment lists for transportation planning and processing (Transp. Planning, Utilization,

Free Capacity, Check-in, Shipment Completion):

1. Enter the selection criteria that you want to save as a variant on the selection screen.

2. Choose Goto ® Variants ® Save as variant.

3. Enter a code and name for the selection variant.

4. Save your data.

Transportation (LE-TRA) SAP AG

Creating Additional Shipment Documents

72 April 2001

Creating Additional Shipment Documents

Procedure

If you wish to assign the selected deliveries to several different shipment documents, for

example, for capacity reasons, you can create additional shipment documents on the overview

screen Shipments and Deliveries. Proceed as follows:

1. Select the deliveries and choose Sie Edit ® Automatic planning ® Shipment per delivery.

A message appears informing you that a new shipment document with a provisional

number has been created.

2. Assign the deliveries to the new shipment document, as required.

3. Save the new shipment document. The system displays the number that it assigned to this

document, according to the number range defined for shipment documents.

SAP AG Transportation (LE-TRA)

Moving Deliveries

April 2001 73

Moving Deliveries

Use

As long as you have not set the Planned status in a shipment document, you can move deliveries

· From one shipment to another

· Within a shipment

· From a shipment to the screen section

Procedure

Moving Deliveries From One Shipment to Another

To move a delivery from one shipment document to another, you can use the drag-and-drop

function or the appropriate pushbutton on the overview screen.

If items or handling units of a delivery are packed into a handling unit of a shipment,

the delivery can no longer be removed from the shipment. In such a case, the items

or handling units in the delivery must first be unpacked from the handling unit of the

shipment.

See also: Packing in the Shipment Document [Page 132]

Moving Deliveries Within a Shipment

The delivery sequence in a shipment determines the shipment's itinerary. You can change the

delivery sequence in a shipment using the drag-and-drop operation or by selecting the

appropriate pushbutton in the overview screen.

Determining the Itinerary

The sequence of deliveries determines a shipment's itinerary. To determine delivery sequences,

mark the delivery you want to reposition and choose Move or Assign. Because it can be time-

consuming to change the sequence of a large number of deliveries, we recommend using the

Itinerary function. Simply call up the function Itinerary.

To change the itinerary, proceed as follows:

1. On the overview screen select the shipment required and go to the screen Overview

Shipment.

2. In the screen Stages, choose the pushbutton Leg Determination.

A dialog box with sort numbers for all deliveries appears on the screen.

3. Either change the delivery numbers manually or choose Delete sort numbers to reenter all

the sort numbers.

4. Choose Refresh to re-sort the list of deliveries according to the new sort numbers. The

itinerary is changed accordingly.

Transportation (LE-TRA) SAP AG

Moving Deliveries

74 April 2001

Moving Deliveries to the Screen Section Non-Assigned Deliveries

In some cases, you may want to reduce the weight of a shipment by removing a

delivery from the shipment and later transferring it into another shipment document.

To do this, you can move deliveries temporarily to the Non-assigned deliveries

section.

To move a delivery from a shipment document into the screen section Non-assigned deliveries,

proceed as follows:

1. Mark the delivery or deliveries you want to move on the Shipments and Deliveries overview

screen.

2. Move the selected deliveries using the drag-and-drop function. The delivery or deliveries are

inserted in the Non-assigned deliveries section.

3. Save your changes.

SAP AG Transportation (LE-TRA)

Removing Deliveries from a Shipment

April 2001 75

Removing Deliveries from a Shipment

Use

You can remove deliveries from a shipment document as long as the Planned status has not

been set for that shipment document. There are no restrictions for removing deliveries from the

Deliveries not assigned section of the overview screen. When a delivery is removed from a

shipment due list, the system determines the transportation planning status anew. Depending on

this status, you can select the delivery when you create a new shipment.

Your customer postpones the delivery date for a certain delivery. The delivery has

already been assigned to a shipment. The planned status has not yet been set for

the shipment, so you can remove it from the shipment. The transportation planning

status is reset to A (not yet planned). The delivery is included in a later shipment.

Procedure

To remove a delivery from a shipment, use the Drag & Drop operation or press the key Remove

delivery from shipment.

Result

The deliveries are removed from the shipment. The transportation planning status for this

delivery is determined anew by the system.

Transportation (LE-TRA) SAP AG

Creating Shipment Documents for Individual Deliveries

76 April 2001

Creating Shipment Documents for Individual Deliveries

Use

To plan and process individual deliveries in a shipment using separate shipment documents (FTL

(full truck load) or FCL (full container load) transactions, for example):

Procedure

1. Select the deliveries for which you wish to create a separate shipment document.

2. Choose Edit ® Automatic planning ® One dlv.one shipment.

A message appears informing you how many new shipments have been created and

what provisional numbers have been assigned to them.

3. Save your data.

The new shipment documents are saved and assigned numbers.

SAP AG Transportation (LE-TRA)

Planning Proposal

April 2001 77

Planning Proposal

Use

The planning proposal enables you as the material requirements planning (MRP) controller to

simplify your manual planning. As you create or change shipments manually, the planning

proposal gives you default profiles, which include “rules” that automatically create shipments and

fill them with data. You can still make manual changes to the planning proposal during

processing, unlike collective processing for shipment creation, where you cannot influence

processing manually.

Features

You can save the selection criteria that you use for collective processing for shipment creation as

a selection variant. You can also save combination criteria that you have maintained as a

combination profile and save the data that is used to fill the shipment as a data profile. You can

then access these profiles as you carry out collective processing for the automatic creation of

shipments, for example. You can also save settings, selection criteria, combination criteria and

data together in one planning profile. Technically , the planning profile is a variant of collective

processing for shipment creation. A planning profile can be assigned to a shipment type.

If you select a planning proposal while you are creating shipments manually, a dialog box

containing that planning proposal with its corresponding data appears, provided a planning

proposal was assigned to the shipment type. All default values in the dialog box can be changed

except for the basic data (transportation planning location and shipment type), since you just

entered that data in the initial screen for creating a shipment. When you choose Execute, the

selected deliveries are automatically put together in a shipment and filled in with data, according

to the specifications you just made. If errors or warnings occur, they are recorded in a log.

Transportation (LE-TRA) SAP AG

Subsequent Delivery Split in Shipments

78 April 2001

Subsequent Delivery Split in Shipments

Use

During shipment processing it is often necessary to split a delivery up into two or more shipments

because they do not all fit on to one truck, for example. However, since it is not possible to

assign deliveries to shipments item by item, there is a special function called

Subsequent

Delivery Split

. You can carry out a subsequent split either in outbound deliveries [Ext.] or in

shipments. The following are a few examples in which a delivery split would be necessary:

· A customer's purchase order cannot be transported in a single shipment (for example, 100

tons of coal per truck; delivery would have fitted into a 30 foot container, but there is only a

20 foot container available).

· No suitable means of transport is available when transportation planning takes place.

· Estimates based on SAP System calculations are not appropriate for the actual situation.

In the first example, the delivery split could take place as the delivery is being created; in the

second and third examples, the delivery split would happen after the delivery was created (during

loading or transportation planning).

Prerequisites

So that you can use the functionality of the subsequent delivery split, you need to configure the

respective settings for the activity subsequent delivery split [Ext.] in the Implementation Guide

under the path Logistics Execution ® Shipping ® Deliveries. Pay attention to the conditions that

are listed under the heading “Prerequisites”.

A delivery split is only allowed, for example, if the delivery has a particular status. This means

that, for example, no goods movement, no invoice, and not pick quantity pending confirmation (at

least for the split quantity of an item) may exist. The shipment must also be fully processed

already.

The type of split is controlled through a

Split Profile that you define in Customizing and assign to

the shipment type. You store a profile for the delivery split

before planning and after planning.

Whether or not the split deliveries remain in the shipment depends on your Customizing settings:

· before planning: Already when you are making up the shipment, you know that the delivery

needs splitting. The split results and the split remainder remain in the shipment.

· after planning: Already when you are loading up the means of transport you determine that

the delivery needs splitting. In the case of a loading ramp split, the split results are removed

from the shipment.

Features

You can use the Subsequent delivery split function to divide up a delivery that does not fit into

one shipment and redistribute parts of that delivery to two or more shipments. You can split

deliveries on the Shipments and Deliveries overview screen of the Create Shipment or Change

Shipment transaction.

You can also split handling units, delivery items, and partial quantities of delivery items. You

always have the option of running a simulation of the split beforehand.

SAP AG Transportation (LE-TRA)

Subsequent Delivery Split in Shipments

April 2001 79

During the subsequent delivery split, the system checks the status (no goods movements or

billing documents, for example), confirms characteristics (delivery groups and correlation), copies

data (texts), calculates attributes (volume and weight) and executes output determination.

The split result controls which delivery items are grouped together in the same delivery. All

remaining items make up the split remainder.

Delivery 1

18 Pallets

Delivery 3

6 Pallets

Delivery 1

5 Pallets

Delivery 2

7 Pallets

Results 1

Results 2

Remainder

Original

Delivery

Activities

You are now on the overview screen for Shipments and Deliveries. Select a delivery, choose the

pushbutton Split deliveries, and break up the respective quantity. While saving the shipment, the

system automatically generates further outbound deliveries for the split quantities (split results).

Whether or not the split deliveries remain in the shipment depends on your Customizing settings.

The system checks whether the delivery contains items that have not been packed. If all items

have already been packed, they must be unpacked (from the packing screen). If the delivery

contains items that have not been packed, you can define how the delivery is to be split. You can

enter as split quantity the quantity displayed under Non-packed quantity, as maximum.

One delivery can be split into several deliveries. You can use the result number to control the

combination of deliveries that are involved in the split. If you assign the same result number to

delivery items in one delivery, these items will remain together in the delivery after the split. If

delivery items have different result numbers, the split distributes them among several deliveries

(split results). Result numbers are only ever valid for one delivery at a time. In other words, the

same result numbers can be assigned in splits of different deliveries. Entire deliveries cannot be

combined by assigning the same result number. Combination by assigning the same result

number is only valid for items, as described above.

The split produces one split remainder and one or more split results with temporary delivery

numbers.

Transportation (LE-TRA) SAP AG

Subsequent Delivery Split in Shipments

80 April 2001

If a delivery was assigned to a shipment before it was split, you must indicate whether the split

result(s) should remain in the shipment or whether the split remainder should be assigned to the

shipment instead and the split result(s) should be assigned to Deliveries not assigned. If the

delivery was not assigned to a shipment before the split, both the split remainder and the split

result(s) are not assigned. If the shipment is saved, the split results and split remainder are also

saved. For more information, refer to the section Executing Subsequent Delivery Split [Ext.].

Please note the following points regarding delivery splits:

· Delivery items that are packed into a single shipment item can not longer be split.

· The delivery-item quantity that is to be split cannot be larger than the quantity of that item

that is not packed.

· Automatic delivery splits cannot be used for mass changes.

· A shipment transaction that is running can either be split

or packed, but not both.

· In a transportation chain, there is no difference made between the preliminary leg, main leg,

and subsequent leg during the delivery split. Depending on your Customizing settings for the

current shipment type, the split results and the split remainder are also assigned in the

background for all the other shipments to which the delivery is assigned, or this assignment

is deleted.

· The delivery split is no longer possible after shipment completion.

SAP AG Transportation (LE-TRA)

Using Collective Processing to Create Shipments

April 2001 81

Using Collective Processing to Create Shipments

Use

This function lets you create shipments automatically in the system (either in the foreground or

background). You can define simple rules as to how deliveries are to be grouped into shipments.

You can use collective processing to:

· Create individual shipments

· Create collective shipments

· Create Full Truck Loads (one shipment per delivery)

· Create parts of a transportation chain

· Create entire transportation chains

· Define field groupings that can then be used as individual criteria

(You could, for example, define shipping points 1 and 2 as a group if they are near each

other in the same geographical area. You can still use a shipping point as a criterion. It

is, however, possible to transport deliveries from shipping points 1 and 2 together,

because of the grouping you have just defined.)

You can also use groupings to define the order of deliveries within a shipment (according

to zip code, transportation zone, etc.).

Integration

You can use collective processing for both inbound and outbound shipments. This way, you can

combine inbound deliveries generated in purchasing or deliveries generated in sales and

distribution into shipments.

Features

Collective processing normally entails three steps:

· Definition of selection variants

Define which deliveries are to be considered in the creation process. The same selection

criteria as those in the individual creation process can be used here.

· Definition of grouping criteria

You can define which fields in the deliveries must be identical so that those deliveries

can be grouped together into one shipment. You can also define in which order the

deliveries appear in the shipment and enter capacity limits for those shipments that are

to be considered. To define grouping and sort criteria, you can choose from over 80

delivery header fields in the field catalog.

Transportation (LE-TRA) SAP AG

Using Collective Processing to Create Shipments

82 April 2001

· Set default shipment data

You can define shipment data, such as forwarding agents or deadlines, that should

appear in each shipment you create.

When you create transportation chains, the system copies dates and times from the

preliminary leg into the main leg. For example, the loading end time in the preliminary leg

is automatically copied into the main leg as the loading start time.

SAP AG Transportation (LE-TRA)

Creating Shipments with Collective Processing

April 2001 83

Creating Shipments with Collective Processing

Procedure

1. From shipment [Ext.], choose Create ® Collective Processing.

A screen appears on which you can define how the collective processing for the creation of

shipments should be carried out.

2. Enter which kind of shipments (inbound or outbound) you want to create in the Default

settings section.

Among other things, this entry controls which selection variants you can use to choose

deliveries. One of the variants that is used to select inbound deliveries may not be used for

outgoing shipments, for example.

3. Enter which outbound (or inbound) deliveries are to be processed in this collective shipment

in the Select deliveries section of the screen.

You can also enter the name of a selection variant that you may have already created, for

example, for the creation of individual shipments (transaction VT01). You can either enter the

name of this selection variant here or choose it from the list of possible entries in input help.

You can display and change the content of this variant by choosing Maintn (to the right of the

field).

You may also create a new variant. Simply enter the name of the new variant and choose

Maintn. The selection screen for selecting deliveries then appears. Specify the criteria

according to which you want to select deliveries. For example, you would enter here that all

deliveries that have route 000001 (north route) or 000002 (west route) should be

selected.

The Selection variant field is a mandatory entry field and therefore must contain a name.

4. Enter the rules according to which the selected deliveries should be divided into shipments in

the Grouping criteria field in the Rules section of the screen.

As with the Selection variants field (see point 3), you can enter the name of a variant that

defines the rules for grouping deliveries into shipments in this field. For example, you could

specify that all deliveries with the same shipping point and route should be grouped together

into one shipment. You can further specify that these deliveries are to be sorted according to

the ship-to party’s zip code and that the shipment may weigh no more than 30 tons.

The Grouping criteria field is optional. If it is left blank, all deliveries that are selected are

assigned to one shipment.

5. In the Data and options field in the Rules section of the screen, you can specify which data

should be found in the shipment documents you create (transportation planning point,

shipment type, service agent, route, etc.) and which functions should be carried out (leg

determination, set status to planned, etc). As with the other fields, you must either enter the

name of a variant or create a new variant here.

This field is a mandatory entry field and therefore must be filled in.

Transportation (LE-TRA) SAP AG

Creating Shipments with Collective Processing

84 April 2001

6. Enter whether or not the system should save the shipment if errors or warnings occur in the

Save created shipments part of the screen.

Some errors prevent a document from being created. For example, you cannot

create a document with a shipment type that does not exist. Other errors or warnings

do not necessarily indicate an inconsistent document, but the system indicates that

you may want to reconsider creating the document in its current state. For example,

you may not want to create the document if leg determination could not be carried

out, if the service agent could not be transferred from the delivery or if the maximum

weight has been exceeded.

Indicate here whether the system should save shipments if one of the above-

mentioned minor errors occur. If you choose Do not save if warning/error, shipments

will only be created when all necessary data was entered (when no corrections are

necessary).

If you choose Do not save if error, a shipment is created in spite of any warnings that

occur. As a result, a few corrections may be necessary after the document is

created.

If you choose Simulation (do not save), you are only running a test process to see if

errors would occur.

If you choose Always save data, the document is always saved, even if errors or

warnings have occurred. In this case, we recommend that you check the document

manually.

7. Indicate whether you want a log to be created and how detailed it should be on the Log

portion of the screen.

For example, if you indicate that the log should not be saved, it is displayed at the end of

collective processing, but disappears after the transaction is finished. Only errors, warnings

(invalid service agent, etc.) and important messages (“Shipment 1013 was created”) are

included in the normal log. The detailed log also contains information about partial functions

that were carried out successfully (“Leg determination was carried out,” for example). The

very detailed version of the log also includes technical information (“Stage with key

1013/0004 was created,” for example).

8. Choose Execute.

Result

The log that lists the collective processing results is then displayed after collective processing

has been carried out.

SAP AG Transportation (LE-TRA)

Creating Transportation Chains with Collective Processing

April 2001 85

Creating Transportation Chains with Collective

Processing

Prerequisites

Within collective processing, you can also define that a transportation chain consisting of multiple

shipment documents should be created. For example, all deliveries you select (outbound

shipments, for example) are grouped together into main leg, preliminary leg and subsequent leg

shipments. The selected deliveries are then processed as the system makes multiple runs

through the transportation chain.

Procedure

1. From Transportation [Ext.], choose Create ® Collective Processing.

2. Choose Create transportat. chain.

You can define for each run which grouping criteria should be valid and what data the

runs (individual shipments within the transportation chain) should contain. This data fill-in

process is similar to the one that occurs when you create collective shipments. See also

Creating Shipments with Collective Processing [Page 83].

All deliveries should first be packed onto a main leg shipment, which goes by rail

from Frankfurt to Hannover. So, you enter a variant that contains the transportation

planning point, shipment type, service agent and route for this rail shipment in the

Data and options field found in the 1st run (create main leg shipments) part of the

screen. Leave the Grouping criteria field blank, since all deliveries in one shipment

should be grouped together. In the second run, all deliveries are distributed among

the corresponding preliminary leg shipments that lead from the shipping point to the

train station in Frankfurt. Create a variant that contains the shipping point as one of

the grouping criteria in the Grouping criteria field. Also specify that one shipment can

hold a maximum of 30 tons. Enter a variant that contains the transportation planning

point, shipment type, etc. for the preliminary leg by land in the Data and options field.

Then specify that leg determination should also be carried out. In the third run,

subsequent legs are created in the same way as preliminary shipments.

The dates from the preliminary leg are transferred automatically to the main leg: The

load finish date from the preliminary leg will be the load start date in the main leg, for

example.

Transportation (LE-TRA) SAP AG

Reports for Transportation Planning

86 April 2001

Reports for Transportation Planning

Use

For transportation planning, there are three reports available that you can call up to select

shipments:

· Select Shipments: Planning [Page 88]

· Select Shipments: Utilization of Capacity [Page 91]

· Select Shipments: Free Capacity [Page 93]

SAP AG Transportation (LE-TRA)

Shipment Execution Monitor

April 2001 87

Shipment Execution Monitor

Use

The monitor gives an overview, grouped by status, time, and date, as to how much workload

exists. In this way, the transportation planner can react quickly to situations and also have a

complete overview of the overall status of all shipments.

For example, a transportation planner can view the workload during a particular shift and react to

the situation as it arises. In this way, the work can be distributed more evenly.

In addition, the transportation manager has a type of control function for the current processing

status.

Features

You can display the different statuses for shipment processing for an entire period by calling up

the path Logistics Execution ® Transportation ® Transportation Planning ® Lists and Logs ®

Shipment Processing Monitor. This period can be either the current day or a complete week. The

number of shipments is listed by status.

Also, you can specify threshold values for the number of found documents for each status in the

selection criteria for the report. If these values are exceeded, this is displayed in color on the

monitor list. Shipments that have not been processed by the time specified by the transportation

planner are marked. You can process shipments immediately by branching into the change

function.

Transportation (LE-TRA) SAP AG

Select Shipments: Planning

88 April 2001

Select Shipments: Planning

Use

You can use this report to list certain shipments that match your selection criteria. You can use

the list of shipments that the system has generated for information purposes, or you can use it to

execute planning activities for the shipments concerned.

Features

Selection Screen

You can compile the transportation planning list by entering selection criteria. You can control

which fields appear as selection criteria on the selection screen. The initial criteria displayed in

the selection screen are taken from the list settings in Customizing for Transportation. For

information on changing these settings, see the section entitled Maintain standard selection

variants for shipment list in the Implementation Guide.

List Screen

You can select from two different views on the list screen. One contains general shipping

information about the selected shipments. The second view contains information on planned and

actual deadlines for individual shipments and the status of planning activities. You can access

each shipment document directly from the list to complete planning activities. In the Planner list,

you can select several shipments and process these at the same time (the only limitation being

that the shipments must have the same shipment type and the same transportation planning

point, and must not have the same deliveries).

The List Viewer features various functions that you can use to tailor the list to your needs. This

tool allows you to total or sort columns, for example. You can also decide the sequence in which

the columns are displayed. For more information, see ABAP List Viewer [Ext.].

Processing

From this list you can branch directly to the selected shipment documents in order to execute

changes in the shipments and perform shipment planning activities. If required, you can assign

deliveries here or change a service agent. You can also call up the function for collective change

if you wish to change several documents. For more information, refer to the Mass Shipment

Changes [Page 130] section.

Example

A planner may use this report to display a list of all shipments to be planned or scheduled. He or

she can also use this report as a worklist. For example, he or she enters, as selection criteria, the

total shipment status 0 (= in planning), the transportation planning point, the planned check-in

date, and the shipment type Truck, since this planner is responsible for planning of shipments by

truck.

See also:

Creating Transportation Planning Lists [Page 90]

SAP AG Transportation (LE-TRA)

Select Shipments: Planning

April 2001 89

Editing Shipment Lists [Page 57]

Transportation (LE-TRA) SAP AG

Creating Transportation Planning Lists

90 April 2001

Creating Transportation Planning Lists

Procedure

To create a transportation planning list, proceed as follows:

1. From transportation [Ext.], choose Lists and Logs ® Transp. Planning List.

You then come to the Shipment List: Planning screen.

2. To use other selection criteria, choose Edit ® All selections.

To define recurring selection criteria, you can create selection screen variants by

choosing Goto ®Variants ®Save as a variant. Then, to retrieve these variants, choose

Goto ®Variants ®Get.

3. Enter the criteria you want to use for selecting the shipment document.

4. Choose Program ® Execute.

You obtain a list of all the shipment documents that match your selection criteria.

For more information about processing this list, see Editing Shipment Lists [Page 57].

SAP AG Transportation (LE-TRA)

Select Shipments: Utilization of Capacity

April 2001 91

Select Shipments: Utilization of Capacity

Use

This report enables you to combine shipments as efficiently as possible by allowing you to enter,

in the selection screen of the list, the percentage of weight and volume for shipment utilization for

the shipments you wish to display. For this purpose, you specify the packaging material type and

the percentage rate of shipment utilization with respect to weight or volume allowed for the

handling units in the shipment and for the specified packaging material type. Using this report

you can determine which shipments are not utilized to the full extent and are therefore to be

considered “inefficient”; on the basis of this information you can then take appropriate measures,

for example, by assigning additional deliveries.

Features

The system selects all those shipments whose weight or volume percent of utilization is equal to

or less than the level you specify in the selection screen. You can select two different views on

the list screen. The first view contains exact details on the percentage of the shipment capacity

utilized in terms of weight and volume as well as general data, such as the transportation

planning point, shipment type, and forwarding agent. The second view contains the deadline

specifications. The functions are the same as those provided for transportation planning.

Processing

From this list you can branch directly to the selected shipment documents in order to execute

changes in the shipments and assign additional deliveries to the shipments.

Example

A planner wants to find out how the planned shipments are utilized so far, that is, shipments that

are planned, but not yet finally scheduled. In addition to the standard selection criteria (shipment

type, total status of shipment, planning final date), the planner can specify the packaging material

type Truck, and a maximum weight utilization of 70%.

See also:

Editing Shipment Lists [Page 57]

Creating Utilization Lists [Page 92]

Transportation (LE-TRA) SAP AG

Creating Utilization Lists

92 April 2001

Creating Utilization Lists

Use

To create a worklist for transportation planning that displays shipments that are not utilized to full

capacity, proceed as follows:

Procedure

1. In the Shipment [Ext.], choose List ® Utilization.

You then see the screen Shipment List: Utilization.

2. To use other selection criteria, choose Edit ® All selections.

To define recurring selection criteria, you can create selection screen variants by

choosing Goto ®Variants ®Save as a variant. Then, to retrieve these variants, choose

Goto ®Variants ®Get.

3. Enter the criteria you want to use for selecting the shipment document. Here you specify the

utilization rate in percentage (between 0 and 100) with regard to the weight and/or volume

allowed for the shipment units in the shipments and for the packaging material type involved.

The system calculates the utilization degree (that is, remaining capacity that can be

used) on the basis of the packaging material type you have specified. Only handling

units that were created in the shipment (not in the delivery) and for which the

corresponding values (such as allowed weight) have been maintained are taken into

account. If you do not specify a packaging material type, the packaging material at

the highest level of the packing hierarchy is used automatically. For further

information, see the help text for the field PackMatltype.

4. Choose Program ® Execute.

The system lists all shipments that match your selection criteria and have a weight or

volume utilization less than or equal to the percentage specified.

You can find more information on processing these lists in Editing Shipment Lists [Page 57].

SAP AG Transportation (LE-TRA)

Select Shipments: Free Capacity

April 2001 93

Select Shipments: Free Capacity

Use

You use this report to find another shipment with sufficient capacity for an existing package.

Along with other selection criteria, you specify the weight and volume of the package to be

packed and you also specify whether it can be split up among several handling units.

Features

The system selects all those shipments with a remaining usable load that is equal to or greater

than the value you specified in the selection criteria. You can select two different views on the list

screen. The first view contains exact details on the percentage of the shipment capacity utilized

in terms of weight and volume as well as general data, such as the transportation planning point,

shipment type, and forwarding agent. The second view contains the deadline specifications. The

functions are the same as those provided for transportation planning.

Processing

From this list you can branch directly to the selected shipment documents in order to execute

changes in the shipments. For example, you can assign the delivery of the package still to be

shipped to a particular shipment.

Example

A planner still has one pallet with a volume of 2 cubic meters; he/she would like to assign this

pallet to a shipment that has already been created, but is not yet fully scheduled. The planner

therefore enters, in addition to the standard selection criteria (transportation planning point,

shipment type, planned final date), the packaging material type Pallet and the volume to be

packed. Also, he or she specifies the shipment route. Then the system generates an overview of

all shipments that are planned for the route specified and still have capacity to include the pallet.

The planner can choose a suitable shipment and assign the respective delivery to it.

See also:

Editing Shipment Lists [Page 57]

Creating Free Capacity Lists [Page 94]

Transportation (LE-TRA) SAP AG

Creating Free Capacity Lists

94 April 2001

Creating Free Capacity Lists

Use

To create a list for transportation planning with the shipments that still have the available capacity

you need, proceed as follows:

Procedure

1. Choose Environment ® Planning ® Free capacity on the Transportation screen [Ext.].

You then come to the Shipment List: Free Capacity.

2. To use other selection criteria, choose Edit ® Selection Options.

To define recurring selection criteria, you can create selection screen variants by

choosing Goto ®Variants ®Save as a variant. Then, to retrieve these variants, choose

Goto ®Variants ®Get.

3. Enter the criteria you want to use for selecting the shipment document. Specify the weight or

volume of the freight goods to be packed.

The system calculates the capacity (for example, remaining load) on the basis of the

packaging material type that you specified. Only handling units that were created in

the shipment (not in the delivery) and for which the corresponding values (such as

allowed weight) have been maintained are taken into account. If you do not specify a

packaging material type, the packaging material at the highest level of the packing

hierarchy is used automatically. For further information, see the help text for the field

PackMatltype.

4. Choose Program ® Execute.

The system lists all shipments that match your selection criteria and have free capacity

greater than or equal to the capacity specified in the selection screen.

For more information about processing this list, see Editing Shipment Lists [Page 57]

SAP AG Transportation (LE-TRA)

Automatic Leg Determination

April 2001 95

Automatic Leg Determination

Purpose

Automatic leg determination is an easy-to-use function that simplifies manual leg creation, or

even eliminates the need for it. It does not involve optimization algorithms and also has no

“geographical intelligence”.

Automatic leg determination creates legs using simple rules that determine point of departure

and destination as well as some leg data (service agent, shipping type, leg indicator, and

shipment cost relevance for the leg).

The result of automatic leg determination is determined by different parameters you have set; this

allows you to simulate various business scenarios.

The most important parameter is the type of leg determination, which can have five

characteristics. For more information, see Leg Determination Categories [Page 103].

The following data is taken from the shipment document:

· Deliveries in the shipment (departure point, destination, sequence)

· Existing shipment legs (for example, created through the route that was entered in the

shipment header)

· Shipment header: Service agents

· Shipment header: Shipping type

· Shipment header: shipping type preliminary leg (this field is not always available for

entry)

· Shipment header: Shipping type subsequent leg (this field is not always available for

entry)

· Shipment header: Leg indicator

Process Flow

Leg determination is generally executed as follows:

1. The system checks whether leg determination can be carried out. Leg determination

cannot be carried out, for example, if the leg determination type is set to ‘_’ (blank), if

there are no deliveries in the shipment, or if the shipping types mentioned above have

not been filled in (see step 6 for more details).

In this case, the system responds with a message.

2. The system analyzes the deliveries in the shipment. What is the point of departure and

the destination for the deliveries?

A delivery can go from shipping point ‘0001’/ loading point ‘01’ to customer ‘123’

unloading point ‘ramp 15’. A return goes the opposite way, however. An inbound

shipment goes from vendor ‘456’ to plant ‘0005’ to storage location ‘0004’.

Warehouse number and door are also taken into account where necessary.

Transportation (LE-TRA) SAP AG

Automatic Leg Determination

96 April 2001

Places (departure points and destinations of deliveries or of a leg, etc.) are given a

unique identification number during leg determination; this number is then used in further

processing. See also Identification of Places [Page 101].

3. The system analyzes the stages that exist in the document as they relate to the following

questions: Which stages are legs, border crossing points, or load transfer points? How

were they created (did they come from a route, were they entered manually, or are they

from a previous leg determination run that was changed later, and so on)? This

information is important, since leg determination can calculate legs connecting to a route

(or manual legs).

You can display the history of a leg on the stage detail screen. For this purpose,

select Management in this screen. You can tell which route a leg originated from and

whether it was created manually or automatically.

4. The system checks to see if this shipment is part of a transportation chain. This

information can be determined from the leg indicator in the shipment header (not to be

confused with the leg indicator in the leg of the shipment).

Leg indicator Effect

‘4’ (direct leg) or ‘5’ (return leg) The entire shipment process appears in one

shipment document. The shipment document is not

related to any other shipments.

‘1’ (preliminary leg) ‘2’ (main leg)

or ‘3’ (subsequent leg)

This shipment is part of a transportation chain that

is reflected in multiple shipment documents.

This information is important because, as in the case of a preliminary leg shipment, for

example, the deliveries are not to be delivered directly to the customer, but to another

destination where they are then transferred to the main shipment.

A delivery is brought by truck from shipping point ‘0001’ to Hamburg harbor as a

preliminary leg shipment. The delivery is loaded onto a ship in Hamburg harbor. The

ship then transports the delivery from Hamburg harbor to New York harbor (main

leg). The delivery is then transferred once again and is shipped by train to customers

in Chicago (subsequent leg).

For the preliminary shipment, the destination is not the customer in Chicago, but

Hamburg harbor. A dialog box appears during leg determination that asks you to enter

the destination. If the main leg shipment was created beforehand in the system,

Hamburg is automatically taken as a default.

If a destination was entered, the original destination is replaced by the new one in all

deliveries. If this does not occur, leg determination is terminated.

The same is valid for a subsequent leg shipment (leg indicator value ‘3’ in the shipment

header), except that the point of departure for the deliveries is replaced by the

destination harbor from the main leg, as an example.

5. The system now carries out the actual leg determination. For more information, see Leg

Determination Categories [Page 103]. A certain number of legs that must still be filled in

with data appear.

6. The system fills the legs it created with data. If there are legs that were entered or

modified manually beforehand, their data is directly transferred.

SAP AG Transportation (LE-TRA)

Automatic Leg Determination

April 2001 97

If new legs are involved, the following data is re-determined:

– Service agents in the leg

(copied from the shipment header)

– Shipment cost relevance for the leg

(default triggered by the shipment type)

– Leg indicator

If a preliminary shipment is concerned, the leg also gets this indicator (the same

applies to subsequent shipment). If only one leg exists or if the leg links the delivery

departure point directly to the destination, the leg is a direct leg. For all other

shipments, the following applies:

If leg departure point = delivery departure point, then preliminary leg

If leg destination = delivery destination, then subsequent leg

If both apply = main leg

– Shipping type for the leg

(copied from the shipment header)

Exception: In leg determination types ‘2’ to ‘4’, the shipping type preliminary leg is

copied to preliminary legs and shipping type subsequent leg is copied to subsequent

legs. In this case, these two shipping types can be maintained in the shipment

header (on the Control tab page) and are suggested from the shipment type.

If no shipment type can be determined for a leg, the shipment type is not created.

This characteristic can be used to better illustrate certain scenarios (for example, it

could make sense to give the subsequent legs lower priority in the shipment since

they are not important).

7. The border crossing points and load transfer points taken out in step three are replaced.

The system attempts to place them correctly.

There are two existing legs from A to G and from G to B. The border crossing point G

is placed between the two legs.

8. Finally, the assignments of deliveries to stages are determined. For more information,

see Automatic Assignment of Deliveries [Page 99].

Step 8 is the only step carried out during leg determination of type ‘0’. This means that no legs at

all are determined. This may be useful if you want to enter all legs manually (if a scenario is very

complicated, for example), but an automatic assignment of deliveries to stages should occur at

the very least.

If the standard leg determination does not meet your needs, you can activate a

customer enhancement (enhancement ‘V56SLDET’), in which you can create your

own leg determination.

Transportation (LE-TRA) SAP AG

Automatic Leg Determination

98 April 2001

See also:

Automatic Assignment of Deliveries [Page 99]

Identification of Places [Page 101]

Leg Determination Categories [Page 103]

Executing Automatic Leg Determination [Page 105]

SAP AG Transportation (LE-TRA)

Automatic Assignment of Deliveries

April 2001 99

Automatic Assignment of Deliveries

Use

It often happens that the deliveries in a shipment are only to be assigned to a few rather than all

stages of the shipment. This function is useful if a shipment stops at various locations, unloading

or loading goods along the way, for example. In such a situation, not all deliveries would be

included in each stage of transportation.

The system provides an algorithm that attempts to determine these assignments automatically to

save you from having to do so manually.

Prerequisites

This algorithm is triggered automatically in the following circumstances:

· When a route is entered in the shipment header

· After you carry out leg determination with category ‘0’ to ‘4’ (leg determination category

‘0’ initiates the assignment determination process only).

Features

Assignment determination is carried out as follows:

1. The system analyzes the point of departure and destination for each delivery, one after

the other (see also step 2 in Automatic Leg Determination [Page 95].

2. If the point of departure of this delivery is found among the departure points of the

existing legs and the destination is found among existing destinations, the system then

looks for the legs that connect these two locations.

If the legs are incomplete (that is, if there are gaps between them), the delivery is

assigned to all legs that start at the beginning point and also to all those that end at

the destination.

3. If only the departure point exists in the system, the system assigns all adjoining legs to

the delivery.

4. If only the destination exists in the system, all adjoining legs are assigned to the delivery

(in other words, similar to step 3, only backwards).

5. If neither the departure point nor the destination exists in the system and if the delivery is

a preliminary leg shipment or subsequent leg shipment, it is assigned to all legs. All other

shipments with no departure point or destination in the system are only assigned to main

legs. If this does not work either (because the leg indicator is not maintained, for

instance), the deliveries are assigned to all legs that were created manually.

6. Now the system assigns the deliveries to border crossing points and load transfer points.

The system then also checks which legs start or end at border point G, for example. All

deliveries that are found in these legs are assigned to this border crossing point, since all

deliveries that are shipped to this border crossing point must most likely go through

customs.

Transportation (LE-TRA) SAP AG

Automatic Assignment of Deliveries

100 April 2001

Only deliveries that are to be loaded or unloaded at this point or those whose shipping

type or service agent changes (meaning that they must be transferred) are assigned to a

load transfer point.

If there are no legs that begin or end at this point, the system assigns all deliveries to this

point.

SAP AG Transportation (LE-TRA)

Identification of Places

April 2001 101

Identification of Places

Use

During leg determination (and also as assignments of deliveries to stages are being determined),

various locations must be compared to one another at many points in the component. In other

words, the system checks to make sure the location defined is the same physical location that

exists in the system.

This can sometimes be rather difficult, since one location can appear in the system in various

ways.

A customer with the number ‘ABCD’ is created in the system. This customer’s

address is Mr. Smith, 1200 Main Street, Anytown, USA 90018. A transportation

connection point that refers to this customer has been entered in Customizing. A

one-time customer with the same address was also entered (the same customer

called up to order an express shipment and could not remember the customer

number from previous orders, for example). All three of these entries describe the

same physical location and should be identified as such.

Delivery 1 has a destination of customer ‘ABCD’, unloading point ‘dock door 29’; but

delivery 2 has customer ‘ABCD’ and unloading point ‘dock door 1’ as its destination.

These are most likely two distinct physical locations. In this case, the truck needs to

go to both dock door 1 and dock door 29 at this customer’s warehouse.

Features

Location entries are analyzed by the system as follows:

The system takes the address and other important data from the location description:

· Location description:

- Loading point at the shipping point

- Customer’s unloading point

- Storage location at the plant

- Warehouse number

- Door for the warehouse number

- Additional information

· Address:

- Name 1

- Location

- Zip code for location

- Zip code for the post office box

Transportation (LE-TRA) SAP AG

Identification of Places

102 April 2001

- Company zip code (for major customers)

- Street

- Street number

- Post office box

- Location of the post office box

- Transportation zone

- Country key

If this data is identical for two location entries, the system assumes that they are the exact same

location. (Technically speaking, the system assigns a temporary number within the program for

this identification. This number is then also assigned to every location that is identified with the

same entries.

If this method of location comparison is not sufficient for your business scenario (if

you would also like to include a phonetic comparison to allow for typing errors, for

example), you can modify the analysis to fit your needs using customer

enhancement ‘V56LOCID’.

SAP AG Transportation (LE-TRA)

Leg Determination Categories

April 2001 103

Leg Determination Categories

Use

The basic procedures are described in Automatic Leg Determination [Page 95].

Prerequisites

In the Customizing [Ext.] application, you can define for the shipment type (Parameters for

‘Determine legs’) how leg determination should be carried out.

You can also display this information on the overview screen of the shipment document (Control

tab).

Features

The R/3 System supports the following categories of leg determination:

· Leg determination ‘_’ (blank):

The system does not perform leg determination.

· Leg determination ‘0’:

The system does not perform leg determination, but the assignment of deliveries to

stages is determined. (See also Automatic Assignment of Deliveries [Page 99].)

· Leg determination ‘1’

Legs are determined according to the itinerary (order of deliveries) in the shipment

document.

This type of leg determination is used for collective shipments in which the goods are

picked up at individual shipping points in a certain order and then delivered to individual

ship-to parties in a certain order.

· Leg determination ‘2’

A type of leg determination in which a preliminary leg is created for each starting point

and a subsequent leg is created for each destination point.

This type of leg determination is used for transporting deliveries that are to be sent by

sea in a group, but originate from different shipping points or are to be transported to

different ship-to parties.

· Leg determination ‘3’

A type of leg determination in which a preliminary leg and a subsequent leg are created

for each delivery.

This leg determination type is used for transporting extensive amounts of goods that

must be distributed among multiple deliveries because one delivery would not offer

enough capacity.

· Leg determination ‘4’

This type of leg determination is similar to type ‘1’ except that shipment types for

preliminary and subsequent legs (which you can enter in the shipment header) are taken

into consideration. This way you can suppress certain preliminary or subsequent legs.

Transportation (LE-TRA) SAP AG

Leg Determination Categories

104 April 2001

Each type of leg determination is described in detail in the following sections:

Category 1: According to the Itinerary [Page 107]

Category 2: Preliminary/Subsequent Leg for Point of Departure/Destination [Page

109]

Category 3: Preliminary and Subsequent Leg for Each Delivery [Page 111]

Category 4: With Shipping Type for Preliminary Leg and Subsequent Leg [Page 114]

SAP AG Transportation (LE-TRA)

Executing Automatic Leg Determination

April 2001 105

Executing Automatic Leg Determination

Procedure

The following options are available for initiating automatic leg determination:

· Set the Planned status on the screen Overview Shipment in the shipment document.

After setting the status, choose the tabstrip Control to check the results of leg

determination.

· Choose the pushbutton Leg determination on the tabstrip Stages.

Result

The system calculates the shipment legs based on the leg determination indicator for the

shipment document type. It takes into account the shipping points and ship-to parties in the

deliveries, as well as the shipping type, the leg indicator, and the route (if you have defined one).

If your shipment is part of a transportation chain, the system also takes this into consideration.

If you have leg determination category 1 or 4, the system displays a dialog box in

which you can modify the sequence of the relevant locations. This dialog box always

appears if you execute leg determination on the overview screen for the stages.

However, if you set the status planned for the general header data (this means that

leg determination will be initiated), this dialog box only appears if absolutely

necessary (for more information, refer to the descriptions for the individual leg

determination types).

Transportation (LE-TRA) SAP AG

Examples of Automatic Leg Determination

106 April 2001

Examples of Automatic Leg Determination

The following sections briefly describe business scenarios for the various types of automatic leg

determination:

Category 1: According to the Itinerary [Page 107]

Category 2: Preliminary/Subsequent Leg for Point of Departure/Destination [Page 109]

Category 3: Preliminary and Subsequent Leg for Each Delivery [Page 111]

Category 4: With Shipping Type for Preliminary Leg and Subsequent Leg [Page 114]

SAP AG Transportation (LE-TRA)

Category 1: According to the Itinerary

April 2001 107

Category 1: According to the Itinerary

Leg determination category 1 generates a sequence of locations that links together the departure

points and destinations for the deliveries without gaps.

The system proceeds as follows:

1. The system connects the departure points of the deliveries onto one another (Example:

the truck drives from shipping point 0001 to shipping point 0002, then to shipping point

0003). The sequence is set in such a way that the deliveries that need to be unloaded

first at the customer are loaded onto the truck last.

Exception 1:

The shipment document already contains manually entered legs (all manually created

legs and legs that originate from a route). If the departure point of a delivery is already

mentioned in these legs, it must be included here once again.

Exception 2:

If you have already specified a particular sequence through a previous leg determination,

the system will take this.

2. The system now connects up all the manual legs.

3. Finally, all the destinations of the deliveries are connected up. The sequence matches

the sequence of the deliveries in the shipment (the so-called itinerary).

Exception:

If a target location is already mentioned in the manually created legs, it is not added on

to the leg, but omitted.

You can modify the sequence of locations determined in this way in a dialog box. This can be

important, for example, if the truck should not to drive to all the shipping points first, the reason

being that there are customers on the routes between the shipping points, and these need to be

driven to. This dialog box always appears if you execute leg determination on the overview

screen for the stages.

However, if you set the status Planned for the general header data (this means that leg

determination will be initiated), this dialog box only appears if absolutely necessary. This is

usually the case if the general data is not unique or has inconsistencies. In this way, expedient

processing is not hindered by a superfluous dialog box.

The 5 deliveries in your shipment depart from shipping point 0001, 0002, and 0003.

The system cannot know the sequence in which these should be driven to (since the

sequence of the deliveries only defines in general the sequence in which the

destinations, that is, the customers, should be driven to). In this case, a dialog box

appears.

The deliveries in your shipment specify a particular itinerary (for example, first to

customer K1, then K2, K3, and so on).

Transportation (LE-TRA) SAP AG

Category 1: According to the Itinerary

108 April 2001

If you have also specified a route in the shipment, and the transportation connection

points of this route also point to the customers, then it could be that a different

sequence was specified in the route. In this case, the system needs confirmation

regarding which itinerary is to be taken (the system proposes the itinerary given in

the route).

Now the system generates legs from the sequence of locations defined (for example,

A, B, C, D).

The legs that were created are filled in with data in accordance with step 6 in Automatic Leg

Determination [Page 95], and border points and load transfer points, as in step 7.

Finally, the system determines which deliveries are assigned to which legs. See also Automatic

Assignment of Deliveries [Page 99].

You have created a shipment document that contains three deliveries. The

deliveries are to be picked up from two different shipping points and delivered to

three different ship-to parties. The deliveries are listed in the following sequence in

the shipment document:

Delivery Shipping point Destination

1 San Francisco Denver

2 San Francisco Dallas

3 Phoenix Oklahoma City

On the basis of the sequence of the deliveries in the shipment document, the system

creates a main leg from Phoenix to Denver, one preliminary leg from San Francisco

to Phoenix, one subsequent leg from Denver to Dallas, and a second from Dallas to

Oklahoma City. The illustration shows how the deliveries are assigned:

San Fr. Phoenix Dallas

Den.

Okl.City

PrelLeg

Deliveries 1,2

Main Leg

Deliveries 1,2,3

SubsLeg

Deliveries 2,3

SubsLeg

Delivery 3

If the manually specified leg management has gaps, these are now closed.

SAP AG Transportation (LE-TRA)

Category 2: Preliminary/Subsequent Leg for Point of Departure/Destination

April 2001 109

Category 2: Preliminary/Subsequent Leg for Point of

Departure/Destination

This type of leg determination forms a preliminary leg for each point of departure and a

subsequent leg for each destination point. It can be used if a transportation chain is to be set up

within a shipment document.

For example, multiple trucks leave from different shipping points to take deliveries to a harbor,

where they are to be loaded onto the ship. The ship then carries the deliveries to the destination

harbor, where they are once again loaded onto multiple trucks to be delivered to different

customers. During this process, the system assumes that only one truck is needed between each

departure point and destination point (Less Than Truckload - LTL).

Only preliminary, main and subsequent legs appear here, as opposed to transportation chains,

which use multiple documents (preliminary shipment document(s), main shipment document,

subsequent shipment document(s)) to illustrate the process.

If you want depict a transportation chain within a shipment document, you must also

accept the limited functions available to you.

The reason: Almost all shipment document functions refer to the document as a

whole:

· Outputs can only be printed for the entire document, not for individual legs

· Handling units can only be created for the entire document, not for individual legs

· The same is valid for texts, deadlines in general, etc.

In our example, when the trucks go from their respective shipping points to the harbor, the freight

documents should not also contain main leg and subsequent leg information. When you create

texts, you would not know if they are supposed to be valid for the preliminary, main or

subsequent legs.

In order to avoid such limitations, we would recommend that you denote a transportation chain

using multiple shipment documents. You can create these shipment documents almost

automatically by using collective processing.

However, if you only want preliminary, main and subsequent legs to show up for documentation

purposes, then this is the correct leg determination type.

Procedure for this type of leg determination:

1. The system assumes that the main leg will be entered manually (here, manually means

either entered directly or by way of a route entry)

Hamburg-New York

2. Now, legs are automatically formed for all existing delivery departure points to the main leg’s

starting point (which was entered manually).

Example:

Shipping point ‘0001’ - Hamburg

Transportation (LE-TRA) SAP AG

Category 2: Preliminary/Subsequent Leg for Point of Departure/Destination

110 April 2001

Shipping point ‘0002’ - Hamburg

3. Now the system creates legs from the end point of the main leg (which was entered

manually) to all destination points of the delivery.

New York - Customer 1,

New York - Customer 2,

New York - Customer 3,

Exception:

If there is no main leg, the system creates direct links between the departure points and the

destination points of the delivery.

Shipping point ‘0001’ - Customer 1,

Shipping point ‘0001’ - Customer 2,

Shipping point ‘0002’ - Customer 3.

The legs that were created are filled in with data in accordance with step 6 in Automatic Leg

Determination [Page 95], and border points and load transfer points, as in step 7.

Finally, the system determines which deliveries are assigned to which legs. See also Automatic

Assignment of Deliveries [Page 99].

You have created a shipment document that contains two deliveries to be dispatched

to a ship-to party in Heidelberg. The first delivery is to be loaded in Boston, the

second in Chicago. You specify the New York-Rotterdam route in the shipment

header. Automatic leg determination creates a main leg from New York to

Rotterdam, one preliminary leg from Chicago to New York, a second preliminary leg

from Boston to New York, and one subsequent leg from Rotterdam to Heidelberg.

Chicago

Boston

New York

Rotterdam Heidelberg

Prelim.leg

Delivery 1

Prelim.leg

Delivery 2

Subseq.leg

Deliveries 1,2

Main leg

(Route from

shipment

header)

Deliveries 1,2

SAP AG Transportation (LE-TRA)

Category 3: Preliminary and Subsequent Leg for Each Delivery

April 2001 111

Category 3: Preliminary and Subsequent Leg for Each

Delivery

This type of leg determination type can generally be used if a transportation chain is to be

illustrated in a shipment document.

For example, multiple trucks leave from different shipping points to take deliveries to a harbor,

where they are to be loaded onto the ship. The ship then carries the deliveries to the destination

harbor, where they are once again loaded onto multiple trucks to be delivered to different

customers. During this process, the system assumes that each delivery is so large that an entire

truck is necessary for each one (Full Truckload - FTL).

Only preliminary, main and subsequent legs appear here, as opposed to transportation chains,

which use multiple documents (preliminary shipment document(s), main shipment document,

subsequent shipment document(s)) to illustrate the process.

If you want depict a transportation chain within a shipment document, you must also

accept the limited functions available to you.

The reason: Almost all shipment document functions refer to the document as a

whole:

· Outputs can only be printed for the entire document, not for individual legs

· Handling units can only be created for the entire document, not for individual legs

· The same is valid for texts, deadlines in general, etc.

In our example, when the trucks go from their respective shipping points to the harbor, the freight

documents should not also contain main leg and subsequent leg information. When you create

texts, you would not know if they are supposed to be valid for the preliminary, main or

subsequent legs.

In order to avoid such limitations, we would recommend that you denote a transportation chain

using multiple shipment documents. You can create these shipment documents almost

automatically by using collective processing.

However, if you only want preliminary, main and subsequent legs to show up for documentation

purposes, then this is the correct leg determination type.

Procedure for this type of leg determination:

1. The system assumes that the main leg will be entered manually (here, manually means

either entered directly or by way of a route entry)

Hamburg-New York

2. Now, legs are automatically formed for all existing deliveries from the delivery’s departure

point to the main leg’s starting point (which was entered manually).

Shipping point ‘0001’ - Hamburg (for delivery 1),

Transportation (LE-TRA) SAP AG

Category 3: Preliminary and Subsequent Leg for Each Delivery

112 April 2001

Shipping point ‘0001’ - Hamburg (for delivery 2),

Shipping point ‘0002’ - Hamburg (for delivery 3),.

Shipping point ‘0002’ - Hamburg (for delivery 4),.

3. Now the system creates legs from the end point of the main leg (which was entered

manually) to the destination point of each delivery.

New York - customer 1 (for delivery 1),

New York - customer 2 (for delivery 2),

New York - customer 2 (for delivery 3),

New York - customer 3 (for delivery 4),

Exception:

If there is no main leg, the system creates direct links between the departure points and the

destination points of the delivery.

Shipping point ‘0001’ - customer 1 (for delivery 1),

Shipping point ‘0001’ - customer 2 (for delivery 2),

Shipping point ‘0002’ - customer 2 (for delivery 3),

Shipping point ‘0002’ - customer 3 (for delivery 4),

The legs that were created are filled in with data in accordance with step 6 in Automatic Leg

Determination [Page 95], and border points and load transfer points, as in step 7.

Finally, the system determines which deliveries are assigned to which legs. See also Automatic

Assignment of Deliveries [Page 99].

You have created a shipment document that contains three separate deliveries for a

total of 60 tons of a product. Each delivery departs from Chicago and is transported

to New York by truck. In New York, all the deliveries are loaded onto a ship and

transported to Hamburg. In Hamburg, each delivery is loaded onto a separate truck

and transported to the ship-to party in Heidelberg. You specify the New York-

Hamburg route in the shipment document header. The system creates a main leg

from New York to Hamburg, three preliminary legs from Chicago to New York, and

three subsequent legs from Hamburg to Heidelberg.

SAP AG Transportation (LE-TRA)

Category 3: Preliminary and Subsequent Leg for Each Delivery

April 2001 113

Leg 1

Leg 5

Leg 4

Leg 2

Leg 6

Leg 3

Leg 7

Delivery 1

Deliveries

1,2,3

Delivery 2

Delivery 3

Chicago

Shipping

point

Port of departure Port of arrival Customer

New York

Hamburg Heidelberg

Point

Time

Preliminary

legs

Subsequent

legs

Main leg

Transportation (LE-TRA) SAP AG

Category 4: With Shipping Type for Preliminary Leg and Subsequent Leg

114 April 2001

Category 4: With Shipping Type for Preliminary Leg and

Subsequent Leg

This leg determination type works in exactly the same way as in Category 1: According to the

Itinerary [Page 107].

Here, however, the preliminary leg shipping type and the subsequent leg shipping type (that you

can maintain in the shipment header) are taken into account. These shipping types are used for

the preliminary and subsequent legs that are created.

You can use this to hide subsequent legs by not maintaining the shipping type for the subsequent

leg. This is helpful if you are only responsible for transportation up to a certain point and not all

the way to the ship-to party location.

SAP AG Transportation (LE-TRA)

Shipment Stages

April 2001 115

Shipment Stages

Definition

Stages contain information about the geographical factors for a shipment. In addition to their

other functions, stages can also be the basis for calculation of shipment costs. Shipment stages

can include:

· Legs

A beginning point and end point is defined. For example, you can define main,

preliminary, and subsequent legs.

· Load transfer points

The point where a shipment is unloaded from one means of transport and loaded onto

another.

· Border crossing points

The point where a shipment crosses the border.

The various types of shipment stages are illustrated in the following figure:

Stop

Border crossing point

A B

Partner:Forwarding agent

Border crossing point

Partner: Customs broker

Load transfer point

Partner: Forwarding agent

Stage of

shipment

Use

The following can be beginning points or end points:

Transportation (LE-TRA) SAP AG

Shipment Stages

116 April 2001

· Transportation connection point (train station or port, for example)

· Shipping point (or loading point)

· Plant (or storage location)

· Customer location (may include customer’s unloading point)

· Vendor

· Freely-definable address

It is also possible to record other information about beginning or end points:

· Warehouse number/dock door

· Additional info, can be any text you choose (quay 17, for example)

If reference to a customer, shipping point, etc. is made in Customizing in the definition of a

transportation connection point, that reference is automatically copied. This reference cannot be

changed in the document since it was copied from the transportation connection point.

You can display the address of each point by choosing Address. If you are in change mode, you

can make any necessary changes to the address. If you make changes to the address, the

system simply creates a different address in the current shipment document.

Load transfer points can be defined the same way as beginning or end points of a leg. This

means that it is possible to create a load transfer point at a customer or vendor address. If a

transportation connection point is to serve as a location entry, however, it must have the

corresponding characteristic Load transfer point in Customizing.

You can only use transportation connection points for border crossing points. These must already

be set up in Customizing with the Border crossing point attribute.

Certain rules must be followed when defining a point in a shipment stage (a customer and a

shipping point may not be entered at the same time, for example). You can find these rules in the

Creating Shipment Stages Manually [Page 118] section.

You can create stages manually in the shipment document.

You can, however, use various functions to simplify or automate the entries:

· Entering a route in the shipment header. The stages defined in Customizing for the route are

then transferred to the shipment document. You can control which stages are transferred, if

any.

· Using the Leg determination function. Leg determination is a mechanism that generates

stages. The determination is based on simple rules. It uses delivery information that is

relevant for shipment in order to generate stages. (No optimization is involved here.)

See also:

Automatic Leg Determination [Page 95]

By combining various control parameters for the transfer of the routes with leg determination, you

can automatically generate leg scenarios (either fully or partially).

SAP AG Transportation (LE-TRA)

Shipment Stages

April 2001 117

Transportation (LE-TRA) SAP AG

Creating Shipment Stages Manually

118 April 2001

Creating Shipment Stages Manually

Procedure

You can use the following functions when you create a shipment stage:

· Create a shipment leg

· Create a load transfer point

· Create a border crossing point

Create a shipment leg

To create a leg in the shipment document:

1. On the initial shipment screen or any of the shipment overview screens, choose

Overview ® Stage overview.

Choose Stage ® New stage ® Leg. You can now see how a location can be defined

(entry of a transportation connection point, shipping point, customer, etc.) by looking at

the Departure and Destination point data fields.

2. Now enter the departure point and destination point (shipping point 0001 and customer

K1, for example).

This departure point must be defined as a transportation connection point in Customizing

for Shipping.

· The location definition must be unique, meaning that only one of the following fields

should contain a value:

– Transportation connection point

– Shipping point

–Customer

–Plant

– Vendor

· An exception is made for transportation connection points that refer to shipping

points, customers, plants, vendors, etc. In such a case, only the transportation

connection point and the shipping point (for instance) may contain values. Except for

the transportation connection point itself, all other fields are not available for entry

and are only displayed.

· Some fields are optional, meaning that they do not have to be maintained. They may

only be maintained in the following situations, however:

– Loading point: The shipping point must have been maintained

– Storage location: The plant must have been maintained

– Unloading point: The customer must have been maintained

– Warehouse: The shipping point or the plant must have been maintained

SAP AG Transportation (LE-TRA)

Creating Shipment Stages Manually

April 2001 119

– Dock door: The warehouse must have been maintained

– Additional info: can always be maintained

· You can always maintain the address:

– As a newly-defined, independent address without any other field having been

filled in. Example: Delivery to a construction site

– As an alternative address for an object (alternative customer address, for

instance).

After entering the locations and pressing a key, the entry fields for departure and

destination point are automatically reduced in size, since now the Transportation

planning point field may not contain a value for the departure point, for example,

according to the above rules. You can make these fields available for input once again

by either deleting the shipping point or choosing Change for the destination point.

This screen compression serves to display only the important location information so that

the lower data area remains accessible, even on small screens. Choose Address to

change an existing location address or add a new one.

3. Maintain other data about the stage on the various tab pages.

4. The system automatically inserts the agent’s name in the header of the shipment

document. Enter the name or number of a service agent in the Service agent field if you

are working with an agent other than the one defined in the shipment header.

Default values for the shipping type and leg indicator are suggested by the system

depending on the shipment type, but you can change them if necessary.

5. Maintain the planned and actual transportation deadlines if needed.

6. Save your data.

To create another leg immediately following this transaction, you can choose Stage ® New stage

® Leg again from the details screen. This takes you directly to the entry screen for the next new

leg.

The shipping document currently contains no scheduling. Planned deadlines on the

leg level can therefore only be maintained manually.

The shipping document also has no distance determination. You therefore have to

maintain the Distance field manually. If you still want to have an automatic distance

determination function, you can activate customer enhancement V56DISTZ.

Creating a load transfer point

To create a load-transfer point in the shipment document:

1. On the initial shipment screen or any of the shipment overview screens, choose

Overview ® Stage overview.

2. Choose Stage ® New stage ® Load transfer point.

3. Enter the transportation connection point for the load transfer point.

Transportation (LE-TRA) SAP AG

Creating Shipment Stages Manually

120 April 2001

The same rules as for definition of a departure or destination point are valid for definition

of a load transfer point.

The specified transportation connection point must be classified in Customizing as a

load transfer point.

4. Enter the name or number of a service agent in the Service agent field if you are working

with an agent other than the one defined in the shipment header.

5. Maintain the planned and actual transportation deadlines if needed.

6. In many cases, the costs calculated for a load transfer depend on where the shipment is

being transported (load transfer at the harbor, for instance). If this is the case, you can

define a destination point for a load transfer point by choosing Stage ® Load transfer

point ® Define destination. A dialog box appears in which you can enter a destination

point (following the same rules as for the load transfer point).

7. Save your data.

Creating a border crossing point

To create a border-crossing point in the shipment document:

1. On the initial shipment screen or any of the shipment overview screens, choose

Overview ® Stage overview.

Choose Stage ® New stage ® Boarder crossing point.

3. Enter the transportation connection point for the border crossing point.

The specified transportation connection point must be classified in Customizing as a

border crossing point.

4. Enter the name or number of a service agent in the Service agent field if you are working

with an agent other than the one defined in the shipment header.

5. Maintain the planned and actual transportation deadlines if needed.

6. Save your data.

SAP AG Transportation (LE-TRA)

Assigning Deliveries to Stages

April 2001 121

Assigning Deliveries to Stages

Prerequisites

You can either assign all deliveries in the shipment to a stage or only a few deliveries to each

stage. This function is useful if a shipment stops at various locations, unloading or loading goods

along the way, for example. In such a situation, not all deliveries would be included in each stage

of transportation.

Deliveries can be assigned to stages automatically (see Leg Determination Categories [Page

103]).

This process can also be carried out manually.

Procedure

1. Choose Overview ® Stage overview on the initial screen or one of the overview screens.

2. Select the stage that the delivery is to be assigned to on this overview screen. Choose

Stage ® Deliveries in stage.

A screen that is divided into two parts appears.

– Deliveries in stage

– Deliveries not in stage

Here you will find data for each delivery in table format.

3. Select the deliveries and then use the movement buttons that are found between the two

halves of the screen to assign deliveries to the stage. You can also delete deliveries.

Transportation (LE-TRA) SAP AG

Maintaining Partners for Stages

122 April 2001

Maintaining Partners for Stages

Prerequisites

You can enter a service agent on the detail screen of each stage. In a leg, the partner is the

forwarding agent; at a load transfer point, it is the load transfer service provider, and at a border

crossing point, it is the customs agent.

You can enter a different address for this service agent by going to the partner maintenance

section of the stage. You can also enter an additional partner (carrier) for a leg. Entry of

additional partner roles for load transfer points or border crossing points is not currently possible.

The partner determination procedures for stages are fixed and therefore cannot be

set in Customizing.

Procedure

1. Choose Goto ® Shipment Overview ® Stages on the initial screen or one of the overview

screens.

2. Select the stage to which deliveries are to be assigned and choose the tab page Partner.

A partner overview screen for the stage appears. If necessary, you can enter another

partner here and change address data in the detail screen.

SAP AG Transportation (LE-TRA)

Displaying Details About Stages

April 2001 123

Displaying Details About Stages

To display details about the stages in the shipment document:

1. On any of the shipment overview screens, choose Overview ® Stages.

2. Select the stage(s) for which you want to display details.

3. Choose Stage ® Stage detail.

You can also display the deliveries or partners for the stage by choosing Deliveries in

stage or Partner stage.

You will reach the detail screen for the first stage that you selected. If you are in change

mode, you can make any necessary changes. To reach the detail screen for any other

stages you marked, choose Stage ® Next stage.

4. Save your changes.

Transportation (LE-TRA) SAP AG

Deleting Stages in the Shipment Document

124 April 2001

Deleting Stages in the Shipment Document

Procedure

To delete stages from the shipment document:

1. From the shipment overview screen, choose the Stages tab.

2. Select the stages you want to delete.

3. Choose Delete section.

The stages will be deleted.

4. Save your changes.

SAP AG Transportation (LE-TRA)

Moving Stages in the Shipment Document

April 2001 125

Moving Stages in the Shipment Document

Procedure

1. Choose the Stage tab on the overview screen.

2. Select the stages you want to move.

3. Place the cursor on the stage you want the selected stages to appear

after.

4. Choose Move stage.

If you want to move the stages to the top of the list, put the cursor in a field above the

overview screen (in the Shipment number field, for example).

Transportation (LE-TRA) SAP AG

Routes and Shipment Stages

126 April 2001

Routes and Shipment Stages

Use

If you find that you use certain routes and stages often, you can define them in Customizing. This

way, you spare yourself the unnecessary effort of creating and re-creating the same stages. You

can find more information in the Define routes and stages section of the Implementation Guide

(IMG).

Features

You can enter the route manually in the shipment’s general header data. All stages of the route,

including their detail screens, are then copied into the shipment automatically. The system also

copies data (such as service agent, shipping type, distance and planned duration) from the route

header into the shipment document header. This only occurs when the relevant fields in the

document header are blank or originate from the old route. Manual entries have priority.

You can control which stages are to be transferred by maintaining the Adopt route control

parameters in Customizing for the shipment type. The control parameters can have the following

values:

· blank All stages are copied over from the route (standard)

· ‘1’: Only stages that have the exact same leg indicator that appears in the transport

header of the current transport document are copied from the route. This is useful when

you want to copy only the preliminary legs of a route into a preliminary shipment which

itself is part of a transportation chain, for example.

· ‘2’: No stages are taken from the route. In this case, the route is only a classification

characteristic in the shipment header.

In the shipment header, you can also display which route stages are to be copied over by

choosing Control on the general header screen.

If you change the route in the shipment document, the system automatically deletes the stages of

the old route and adds the stages of the new one.

After a route is entered, the system tries to assign the deliveries in the shipment automatically to

stages. For more details about this process, see Leg Determination Categories [Page 103].

Automatic Route Transfer

You can automate route entry by choosing the Route from del. option in Customizing for the

shipment type. When you set the status to Planned in the shipment document, the route is

automatically adopted from the deliveries into the shipment document (provided it is unique). The

data transfer described above (route stages and route header data) then occurs automatically.

The service agent field can also be automatically filled in for the stages. For this, you only need

to enter the service agent in the shipment header. It is also automatically copied into all existing

legs that have no service agent.

If you change the service agent in the shipment header, the system also substitutes the new

service agent for the old one in the stages. You can also make the service agent entry happen

automatically if you choose the Frwd. agent delivery indicator in Customizing for shipment types.

As in route processing, when you set the status to Planned, the forwarding agent is automatically

SAP AG Transportation (LE-TRA)

Routes and Shipment Stages

April 2001 127

adopted from the deliveries into the shipment document (and, in turn, into the stages). This can

only occur if the forwarding agent is unique.

A Service agent selection function is not currently available.

Transportation (LE-TRA) SAP AG

Planning Activities in the Shipment Document

128 April 2001

Planning Activities in the Shipment Document

Use

You can execute various activities in the shipment document, including assigning service agents,

packing deliveries or maintaining shipment texts, for example.

SAP AG Transportation (LE-TRA)

Processing Shipment Documents

April 2001 129

Processing Shipment Documents

Procedure

1. In the Shipment Screen [Ext.], choose Change ® Single document.

The Change Shipment: screen appears.

2. Enter the number of the shipment document that you want to change.

3. If you do not know the document number, select the possible entries button to call up the

Find Shipments selection screen. Enter your selection criteria (for example, the name of the

service agent or the transportation planning point) and choose Program ® Execute. The

system will return a list of all the shipments that match the selection criteria. Select the

document that you want to process. The system then enters that number in the Shipment

number field on the initial Change Shipment screen.

4. Press ENTER.

You see the overview screen in the shipment document. From this screen, you can

maintain data such as deadlines, handling units, output data, and stages.

Follow the same procedure to display a shipment document, but select Display

instead of Change in Step 2.

Transportation (LE-TRA) SAP AG

Mass Shipment Changes

130 April 2001

Mass Shipment Changes

Use

Sometimes it is necessary to make changes to more than one shipment. For example, a

forwarding agent that has agreed to ship multiple shipments for you is suddenly no longer

available. Instead of changing each document individually, you can make a mass change in

multiple shipment documents in one step.

Features

You can select shipments according to certain criteria and carry out changes at header level.

This comprehensive change function also allows you to enter changes in a sample line and then

carry those changes over into all selected shipments. That way, you can change the forwarding

agent in multiple shipments by making a single entry.

SAP AG Transportation (LE-TRA)

Making Mass Changes to Shipments

April 2001 131

Making Mass Changes to Shipments

To make changes in multiple shipments simultaneously:

1. Choose Logistics ® Logistics Execution ® Transportation.

2. Choose Shipment ®Mass change.

A selection criteria entry screen appears.

3. Choose which shipments you want to change by entering the corresponding selection

criteria.

4. Choose Execute.

A list of all shipments that meet your selection criteria appears. This list includes all the

shipment header data. The tab pages correspond to those found on the general header

screen of the shipment.

5. Make your changes.

If you want to carry out the same changes in multiple shipments, select those shipments,

enter the value you want to add to those shipments in the default line and choose

Ref.doc. The value in the default line is substituted for older values in the selected

shipments.

6. Save your changes.

Transportation (LE-TRA) SAP AG

Packing in the Shipment Document

132 April 2001

Packing in the Shipment Document

The packing hierarchy, which is set up in the delivery, is continued in the shipment document.

Delivery items that were packed into crates and loaded on pallets can be packed into containers

and loaded on trucks in the shipment document.

1. To pack items in the shipment document, choose Goto ® Shipment and Packaging Matls on

the initial screen or any of the shipment document overview screens. You see the screen for

Editing Handling Units. All the delivery items not packed are displayed in the screen section

Items to be packed.

If goods have already been packed into the deliveries, the system displays the individual

handling units and you can, if necessary, pack these further.

2. To pack a delivery item that has not yet been packed, mark the item and choose Extras

® Allowed pack.matl to find the appropriate packaging materials.

3. Select a packaging material from the Allowed packaging materials dialog box.

4. In the quantity overview of the delivery, choose Edit ® Pack ® Pack.

5. In the screen section All existing HUs (into which you can pack materials), create the

required handling units. You can also call up handling units that have already been created

(Non-Assigned Handling Units [Ext.]) . For further information on creating handling units,

refer to the section Working with Handling Units [Ext.].

6. In the screen section Material to be packed or material packed, select the items that you wish

to pack. Then in the section All existing HUs, select the handling units into which you wish to

pack the goods and choose Pack material. See also: Pack if full [Ext.], New HU per Number

of HUs [Ext.], and Packing per Partial Quantity [Ext.]).

7. To pack an existing HU into a larger HU, for example into a truck, select the HU and choose

Extras ® Allowed pack.matl to select the appropriate packaging material for the HUs

concerned.

8. Select a packaging material from the Allowed packaging materials dialog box.

9. The system marks both the handling unit to be packed and the packaging material. Then

choose Edit ® Pack ® Pack item.

You either receive a message from the system that the handling units are packed or you

are notified that not all the items could be packed because the system reached the

weight or volume limits.

If you have marked several handling units for packing, the handling units at the top of

the list are packed fully first. If not all the items to be packed fit onto this handling

unit, the packing process is automatically continued with the next selected handling

unit.

If only a partial quantity of a delivery item is to be packed, you must enter this in the

section Material to be packed or packed material for the respective item in the field

Partial quantity.

The total weight of the delivery is not increased by the packing weights.

SAP AG Transportation (LE-TRA)

Packing in the Shipment Document

April 2001 133

For handling units that represent means of transport, you may want to maintain the

additional data such as the truck driver’s name or nationality..

1. Select the respective HU and choose Edit ® Detailed data HU.

2. Maintain the necessary data and return to the Pack Items screen.

3. Save your data.

Handling units that were created in the delivery cannot be unpacked in the shipment

document.

Transportation (LE-TRA) SAP AG

Delivery Item Generation in the Shipment

134 April 2001

Delivery Item Generation in the Shipment

Use

Packaging materials for handling units are mostly cost items and are managed as stock in

inventory management. For goods receipt from suppliers and goods issue to customers, it is

therefore important to generate delivery items for the respective packaging materials so that

these can be seen in the delivery note, posted in stock, and then invoiced as required.

Using the function for delivery item generation, you can generate delivery items for packaging

materials that are only yet in planning for the shipment.

Prerequisites

Choose the following activities in the Implementation Guide for delivery item generation from the

shipment.

Logistics Execution ® Transportation ® Shipments ® Define Transportation Relevance [Ext.]

Logistics Execution ® Transportation ® Shipments ® Define and Assign Activity Profiles [Ext.]

Logistics - General ® Handling Unit Management ® Basics ® Define Packaging Material Types

[Ext.]

Logistics Execution ® Shipping ® Deliveries ® Define Delivery Types [Ext.]

Features

In delivery processing, the plant and the item category in the handling unit are decisive factors in

the generation of delivery items. In the shipment, you can set the control for delivery item

generation using an indicator for generation relevance in the Customizing application under

Shipment Type [Ext.]. In the activity profile [Ext.]

you can determine at which times (for example,

during planning, processing) the delivery items for the HUs are to be generated. For example,

changes can occur during planning and processing.

Also, in the Customizing section for Handling Unit Management, there is an indicator in the

packaging material type [Ext.] for generation relevance.

· Delivery items generated from packaging materials are not updated if there is a change to

the handling unit (plant, weight, and so on).

· Generated delivery items are deleted only if the handling unit is deleted.

· The generation of packaging materials in deliveries already posted for goods issue is not

possible.

· Any change in the HU content does not affect the generated item, even if the new contents

do not have any reference to this delivery.

· For technical reasons, the delivery update can only be called up during the update of the

shipment. Issuing a log is no longer possible at this point.

For further information on delivery item generation, refer to the section under Delivery Item

Generation for Packaging Materials [Ext.].

SAP AG Transportation (LE-TRA)

Delivery Item Generation in the Shipment

April 2001 135

Transportation (LE-TRA) SAP AG

Assigning Service Agents in the Shipment Document

136 April 2001

Assigning Service Agents in the Shipment Document

Prerequisites

Before you assign a service agent to a shipment document, make sure that a vendor master

record has been maintained for that service agent.

At Header Level

1. On the initial shipment screen or any of the shipment overview screens, choose Header

® General data.

2. Enter the name of the service agent or the service agent number.

3. Save your data.

At Stage Level

1. On the overview screen of the shipment document, choose Overview ® Stage overview.

2. Mark the stage to which you want to assign a service agent and choose Stage ® Stage

detail.

3. Enter the name or service agent number of the service agent who is responsible for this

stage of the shipment.

The service agent in the shipment header is entered for the shipment leg and the

load transfer point and can be overwritten. No default appears for the border

crossing point.

4. Save your data.

SAP AG Transportation (LE-TRA)

Maintaining Texts in the Shipment Document

April 2001 137

Maintaining Texts in the Shipment Document

In the shipment document, texts are maintained manually at header level. No automatic text

determination occurs for shipments.

To enter important information for shipment planning and completion as a text in the shipment

document, proceed as follows:

1. On the overview screen of the shipment document, choose the tab page Texts.

The text screen appears, where you can maintain various types of texts (for example,

freight list texts, header notes, or forwarder’s order texts).

The text types that appear for maintenance depend on the text procedure, which is

specified for the shipment document type in Customizing.

2. Enter your text.

3. If you need additional space, mark the text and choose Edit Details.

The SAPscript editor will appear and you can complete your text.

4. Save your text on the SAPscript editor screen and choose Back to return to the text screen.

5. Save your text once again on the text screen.

Transportation (LE-TRA) SAP AG

Maintaining Planned and Actual Deadlines in the Shipment Document

138 April 2001

Maintaining Planned and Actual Deadlines in the

Shipment Document

To maintain planned deadlines in the shipment document:

1. On the overview screen in the shipment document, choose the screen sections Status and

Deadlines.

2. The most important shipment deadlines are listed in the screen section Status and

Deadlines. Enter the planned or actual deadlines for the different activities in the Planning

and Execute fields.

You can enter actual deadlines for the required activities automatically or manually.

· Automatically

To enter deadlines automatically, set the status and the system fills in the current

date. You can find further information in Maintaining Status in the Shipment

Document [Page 140].

· Manual

You enter the date; the system automatically sets the status.

3. If you want to maintain deadlines that do not appear in the Dates or Status sections on the

overview screen, choose More Deadlines.

You will reach a screen where you can maintain any other planned or actual deadlines.

If planned and actual deadlines are different, you can record why and where the

deviation occurred by choosing Goto ® Details and maintaining the fields Point and

DeviationReason.

The transportation of a shipment is delayed because of a defective freight car at the

train station in Chicago. Enter the name of the station in Chicago in the Point field

and record that a defective freight car delayed proceedings in the DeviationReason

field.

4. Save your data.

SAP AG Transportation (LE-TRA)

Status in the Shipment Document

April 2001 139

Status in the Shipment Document

Definition

The overall shipment status shows the shipment’s processing stage. There are various

transportation statuses:

· Planned: The shipment´s planning is complete.

· Check-in: The vehicle arrives at the plant.

· Start load: The vehicle is loaded or unloaded.

· End load: Loading and unloading finished.

· Shipment completion: The documents are created.

· Shipment start: The shipment starts.

· Shipment end: The shipment is finished.

Integration

In Customizing [Ext.], you can define Activity profiles [Page 146] for the shipment types, i.e. for

the statuses for which activities are to be carried out.

Example

Possible activities of shipment completion:

· Posting the goods issue for the deliveries in shipment

· Billing the deliveries in shipment

· Printing outputs

Transportation (LE-TRA) SAP AG

Maintaining Status in Shipment Documents

140 April 2001

Maintaining Status in Shipment Documents

Procedure

To maintain status in the shipment document, proceed as follows:

1. On the overview screen for the shipment, set the Planned status in the Deadlines section.

2. Choose the appropriate button for the relevant activity (such as Check-in) on the Deadl. tab

page.

The system records the current date and time as the actual deadline when you choose

the button for the relevant activity.

When you set a status, the status traffic light icon appears on the Status tab page.

For more detailed information on the status that the traffic light represents, click once

on the traffic light and choose F1.

For more information on setting this status, see Transfer of Delivery Dates to Shipment [Page

141].

SAP AG Transportation (LE-TRA)

Transfer of Delivery Dates to Shipments

April 2001 141

Transfer of Delivery Dates to Shipments

Use

You can have planned dates proposed in the shipment for the individual transportation activities.

You can copy these from the outbound deliveries that belong to the shipment. You can use a

copy routine to copy dates and times into the shipment document. There are two copy routine

options: you can either accept the default copy routine or create your own copy routine.

Integration

In order to copy proposals for dates and times from the delivery, you must create a connection

between the shipment dates and delivery dates. Copy routines serve this purpose.

Copy routines link shipment dates and times to previous documents, such as deliveries. In other

words, date and time entries in the shipment can use date and time entries in previous

documents as references.

Prerequisites

A copy routine must be set in the Implementation Guide (IMG) for copying the dates and times.

You can choose a suitable copy routine as a standard default or create your own copy routine to

use as a default in the Define shipment types [Ext.] activity under the path Logistics Execution ®

Transportation ® Shipments.

Features

You can use this function to have the system propose shipment dates and times from the

delivery. There are two methods to choose from:

· Standard default

When this indicator is set, dates and times are copied from deliveries into the shipment. There

are a few rules that apply to standard defaults. First, the loading date and time in the delivery

becomes check-in time and loading start in the shipment. The delivery's planned goods-issue

time becomes the loading end, shipment completion and transportation start time for the

shipment. If the goods-issue date and time (loading time) is unclear in the delivery, the latest

goods issue date that appears in the delivery is copied into the shipment. The delivery date and

time is copied into the shipment's transportation end.

When shipment planning is complete, set the Planned status. At this point, the dates and times

are copied from the delivery into the shipment.

· You can create your own copy routine to use for date and time defaults by using the flexible

default option.

Activities

In shipment processing, choose Planning. Shipment dates and times appear as defaults. A dialog

box appears, in which you can choose whether you want the system to copy the default dates

and times into the shipment or whether leg determination should be re-run.

Transportation (LE-TRA) SAP AG

Function Authorization for Status

142 April 2001

Function Authorization for Status

Use

The scope of transportation status activities should be reserved for administrative personnel for

various reasons. For example, it could be the case that some employees only process one

shipment type, that some are only responsible for transportation by land while others are

responsible for transportation by sea. Still others could be responsible for organizing

transportation planning and some could monitor all activities up through shipment completion. It

may not make sense for someone who only works with one status activity to be authorized to

execute other status activities. The system should carry out an authorization check to see if the

user has the authorization to set or reset a particular transportation status. Status authorization

can be an important security instrument to avoid the shipment being changed after the fact by

someone with no authorization because of an accident during shipping, for example.

Integration

The SAP standard function for checking authorization is used. The new authorization object

V_VTTK_TSA is used with authorization fields SHTYP for the shipment type and TRSTACT for

the shipment status activities to check authorization.

Features

When the shipment status is changed, the system checks whether the user is authorized to

process the shipment type and status. If the user has this authorization in his or her user master

record, processing of the status activity is allowed. Otherwise, an message appears in which the

causes and further procedures appear.

SAP AG Transportation (LE-TRA)

Dangerous Goods Check

April 2001 143

Dangerous Goods Check

Use

In order to fulfill the statutory requirements regarding shipment of dangerous goods, it is

necessary to check whether shipments containing these goods are permitted according to

agreements made with the countries in which the shipments take place.

Integration

The dangerous goods check applied here is part of the standard dangerous goods management

package in the SAP R/3 System.

Prerequisites

The necessary settings must be made in the dangerous goods management section of

Customizing. The necessary data must also be available (transit countries must be defined, for

example).

You can find further information about these prerequisites in Dangerous Goods Check in

Shipment Documents [Ext.].

Features

You can carry out a dangerous goods check in the shipment document. Depending on your

settings, this either happens automatically or can be initiated manually on the Dang. gds tab

page in the general header data for the shipment.

If only one of the items in the deliveries grouped to make this shipment is categorized as

dangerous, the indicator Contains DG is automatically set. This indicator is only for informational

purposes.

Depending on your settings in the dangerous goods management section of Customizing, the

overall reaction of the dangerous goods check may cause the Lock indicator DG to be set. In this

case, it is not possible to assign another document status.

You can find further information about dangerous goods check features in Dangerous Goods

Check in Shipment Documents [Ext.].

Transportation (LE-TRA) SAP AG

Completing Transportation Planning

144 April 2001

Completing Transportation Planning

Procedure

To complete transportation planning for a shipment document, first access the document either

using the change function or using a worklist for transportation planning (see Processing

Shipment Documents [Page 129]).

After you have completed all the necessary activities, such as packing, maintaining texts, or

assigning service providers, you can set the Planned status in the shipment header screen. For

more information on setting this status, see Maintaining Status in the Shipment Document [Page

140]. Once the Planned status has been set, leg determination is performed automatically. The

shipment document is then ready for shipment completion.

Result

Setting the Planned indicator in the header screen of a shipment document will result in the

following:

· You can no longer add deliveries to the shipment document.

· You cannot move deliveries within the shipment document.

· You cannot remove deliveries in the shipment document.

· You cannot reassign deliveries to other shipment documents in the

transportation planning work list.

· You can copy the route from the deliveries into the shipment header if the

appropriate indicator is set in the shipment type and if all deliveries in the

shipment document have the same route.

· You can copy the forwarding agent from the deliveries as the transportation

service agent in the shipment header. However, the indicator for copying the

forwarding agent must first be set in the shipment type and all deliveries must

have the same forwarding agent.

· You can transfer delivery dates to the shipment document, if you set a copy

routine for Transfer of Delivery Dates [Page 141] in the Implementation Guide

(IMG) [Ext.].

SAP AG Transportation (LE-TRA)

Shipment Execution

April 2001 145

Shipment Execution

Use

The aim of shipment completion is to complete the formalities involved in getting a shipment

ready for dispatching to the customer. Tasks in shipment completion include weighing the

shipments, loading, and posting goods issue. At check-in (when a truck arrives on the company’s

premises) information about the means of transport such as driver details, the weight of the truck,

and its arrival time can be recorded. You can store all this information in the shipment document

and it is printed out on the transportation documents, for example, when the completion status is

set. There are various reports available to assist you in choosing the shipments relevant for

check-in and those relevant for shipment completion.

Features

You can carry out certain functions configured in Customizing using Shpmt completion in the

shipment completion list (see About Transportation Processing [Ext.] and Creating Shipment

Completion Lists [Page 153]). These functions include goods issue posting or billing as well as

printing transportation documents, deliveries or billing documents.

Using this function button, you can quickly and efficiently carry out all functions that you want to

use during shipment completion.

You can use the Shipment completion log to display which functions were carried out or which

ones led to problems.

Following shipment completion, you can compare any differences that were found between

the shipment completion and the delivery (during weighing, for example) directly to the

delivery.

For example, in bulk product transportation (gases or liquids), the actual quantity often is

different from the quantity that was ordered.

Transportation (LE-TRA) SAP AG

Activity Profiles

146 April 2001

Activity Profiles

Use

Activity profiles define activities that are to be carried out in the shipment document when a

certain status is set for that shipment. You can define a different profile for each status (planning,

check-in, completion, etc.) Possible activities that can be carried out as the status is set include:

· Add to the data in the dialog box

· Post goods issue for the deliveries in the shipment

· Calculate the shipping costs

· Create invoices for the deliveries in the shipment

· Print certain outputs

Prerequisites

A variant in Customizing must be maintained per shipment type for the status that is to be carried

out. Define in this variant which activities should be carried out and whether a dialog box should

appear when the status is set.

To configure the activity profiles, choose Define and assign activity profiles [Ext.] in the

Implementation Guide (IMG).

Features

The system automatically executes the activities that you specified for the respective shipment

type and status, once the relevant status is set.

You want to make sure that goods issue is always posted for all deliveries in

shipments with shipment type Individual shipment immediately after the shipment is

marked as complete. You also want a dialog box containing the driver’s name to

appear when the status is set to Check-in.

You then define activity profiles for Check-in and Completion for shipment type

Individual shipment. For check-in, you set the default for a dialog box that appears

containing the contents of the field Driver. For completion, you set goods issue

posting to be carried out automatically as this status is set.

Activities

Define activity profiles for your shipment types for any status at which activities should be carried

out.

SAP AG Transportation (LE-TRA)

Reports for Shipment Completion

April 2001 147

Reports for Shipment Completion

Use

For shipment completion, there are two reports available that you can call up to select shipments:

· Select Shipments: Shipment Completion [Page 151]

· Select Shipments: Check-in [Page 148]

Transportation (LE-TRA) SAP AG

Select Shipments: Check-in

148 April 2001

Select Shipments: Check-in

Use

You can use this report to select shipments that you want to check in. An employee at the dock

door of the plant could select all shipments that are expected to arrive on that day, for instance,

so that check-in can occur as the trucks arrive.

Features

Selection Screen

The check-in list is compiled using selection criteria. You can control which fields appear as

selection criteria on the selection screen. The set of criteria that are displayed are determined on

the basis of settings made in Customizing for Transportation. For more information about

changing these settings, see the Maintain selection views for lists of shipments section in the

online Implementation Guide. Criteria that is especially important for check-in include planned

deadlines and service agents, for example.

List Screen

You can select from two different views on the list screen. The first view list contains general

shipping information for the selected shipment documents. You can switch to a second view of

the list which provides you with information on the planned and actual deadlines for the

documents and the status of the various transportation activities. You can access each shipment

document from the list directly and perform the necessary shipment completion activities. There

are various functions which enable you to pare down the list to exactly those documents you

want to process. In addition, search and sort functions have been designed to help you access

the information you need from the list. After you have made changes to a shipment document in

the list and then returned to the list, you can use the Refresh function to update the list.

The List Viewer features various functions that you can use to tailor the list to your needs. This

tool allows you to total or sort columns, for example. You can also decide the sequence in which

the columns are displayed. For more information, see ABAP List Viewer [Ext.].

Processing

From this list, you can set the check-in status for all selected documents. Provided the

relevant setting was made in the activity profile, a dialog box will appear in which the truck’s

license plate number and driver’s name can be entered. See also Shipment Completion [Page

145] and Activity Profiles [Page 146].

Example

Every morning, an employee stationed at the dock door of the plant creates a list of all shipments

expected that day. He or she uses the planned check-in date and status 1 (planned) as selection

criteria for this list. When a truck arrives at the dock door, he or she consults the list, finds the

relevant document and checks the truck in. During this process the truck’s license plate number

and driver’s name are recorded. The system is configured so that a dialog box appears

requesting entry of the license plate number and driver’s name as soon as the Check-in status is

set.

See also:

SAP AG Transportation (LE-TRA)

Select Shipments: Check-in

April 2001 149

Creating Check-in Lists [Page 150]

Editing Shipment Lists [Page 57]

Transportation (LE-TRA) SAP AG

Creating Check-in Lists

150 April 2001

Creating Check-in Lists

To create a transportation completion list, proceed as follows:

1. Choose Shipment [Ext.]® Environment ® Check-in.

You branch to the screen List Shipments: Check-in.

2. To use other selection criteria, choose Edit ® All selections.

To define recurring selection criteria, you can create selection screen variants by

choosing Goto ®Variants ®Save as a variant. Then, to retrieve these variants, choose

Goto ®Variants ®Get.

3. Enter the criteria you want to use for selecting the shipment document.

4. Choose Program ® Execute.

You obtain a list of all the shipment documents that match your selection criteria.

You can find more information on processing these lists in Editing Shipment Lists [Page 57].

SAP AG Transportation (LE-TRA)

Select Shipments: Shipment Completion

April 2001 151

Select Shipments: Shipment Completion

Use

You can use this report to select shipment documents for which planning activities have been

completed and tasks such as weighing, loading, and goods issue still have to be performed.

Features

Selection Screen

The shipment completion list is compiled using selection criteria. You can control which fields

appear as selection criteria on the selection screen. The set of criteria that are displayed are

determined on the basis of settings made in Customizing for Transportation. For more

information about changing these settings, see the Maintain selection views for lists of shipments

section in the online Implementation Guide. Important criteria for shipment completion include the

loading and transportation deadlines.