0% found this document useful (0 votes)
71 views

Organizational Structures in Logistics 2

The document discusses organizational structures in logistics and SAP. It describes the key structures that are needed to map business processes in shipping and transportation in SAP, including the logistic organizational structures, structures in sales and warehouses. The logistic organizational structures in SAP include the client, company code, plant, warehouse, transportation planning point, shipping point, and loading point. These structures allow enterprises to optimize their business processes in SAP.

Uploaded by

Rupali Barick
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
71 views

Organizational Structures in Logistics 2

The document discusses organizational structures in logistics and SAP. It describes the key structures that are needed to map business processes in shipping and transportation in SAP, including the logistic organizational structures, structures in sales and warehouses. The logistic organizational structures in SAP include the client, company code, plant, warehouse, transportation planning point, shipping point, and loading point. These structures allow enterprises to optimize their business processes in SAP.

Uploaded by

Rupali Barick
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 38

Organizational structures in the SAP system allow you to map the organi-

zation of your enterprise. In this chapter, you’ll learn which structures are
needed for mapping the business processes in shipping and transportation.
You will also find out about other structures of upstream and downstream
process steps.

2 Organizational Structures in Logistics

Business application programs, regardless of whether they have been developed


with SAP software or by another software company, have to map the processes in
your enterprise. However, your enterprise consists of different structures, which
also have to be reflected in the software used. Very often, the same processes (such
as shipping) are handled differently depending on their structure. For instance,
shipping to wholesalers (complete loads, cross-docking, etc.) is different from
shipp­ing to small retailers (many small delivery quantities in a single shipment).

You can find these structures in all areas of your enterprise. However, there are
certain differences: the structure of the Shipping department, for example, is
completely different from the structure of the Financial Accounting department.
Despite this, shipping must also be reflected in financial accounting because ship-
ping not only generates a quantity flow, but also a value flow. Ultimately, all struc-
tures in your enterprise must be coordinated so that processes can run uninter-
rupted from start to finish.

This chapter introduces the structures that have a direct or indirect influence on
the shipping and transportation process. These include the logistic organizational
structures on the one hand, and the structure in your sales organization (upstream
processes) and in your warehouse (interim processes) on the other.

2.1 Logistic Organizational Structures

Each enterprise has its own specific organizational structures. In the SAP system,
these have to be mapped in a client to optimize business processes.

23

5065_BOOK.indb 23 3/7/08 7:52:11 AM


2 Organizational Structures in Logistics

The top organizational unit is the enterprise itself. As a rule of thumb, each inde-
pendent accounting unit should be mapped as a company code. The next level
below the company code is the plant. At plant level, for example, you keep your
stocks and plan your goods. Plants can be located in different locations. However,
it can also make sense to define several plants for the same location, if you produce
and sell different goods in these plants. Within a plant, you often have multiple
storage locations (such as a raw materials warehouse and a shipping warehouse).

The following organizational units characterize the physical structures in an enter-


prise. The transportation planning point is the department in your enterprise that
plans and settles shipments. A transportation planning point can edit multiple
shipping points. As the name implies, shipping points are individual places from
which shipments take place. Each individual shipping point can be subdivided
into loading points. For example, you can set up an export shipment transporta-
tion planning point (where all export shipments are planned) with two shipping
points (container loading and truck loading). The truck loading shipping point can
be physically distributed across two buildings, loading point bldg. 1 and loading
point bldg. 2. The complete logistic structure is shown in Figure 2.1.

The following sections explain the organizational structures in detail.

Company Code

Plant Munich Plant Cologne

Warehouse Central Warehouse


Munich Warehouse Cologne

Shipping Point M Loading Point


Trucks

Shipping Point Z Loading Point


Self -Collectors

Loading Point
Events
Transportation
Planning Point M

Transportation
Planning Point Z

Figure 2.1  Overview of Logistic Organizational Structures

24

5065_BOOK.indb 24 3/7/08 7:52:11 AM


Logistic Organizational Structures 2.1

2.1.1 Client
A client is the highest hierarchy level in the SAP system. It contains the business
processes of the entire enterprise. Settings made at this level affect the company
codes and organizational structures. The client is not supposed to be viewed as an
organizational unit of an enterprise, but rather technically as a separate area in an
SAP system.

If you want to use an SAP system, you have to log in to a particular client. When
logging in, you have to enter your User Name, your Password, and the Language
you would like to work with. The language you use for logging in can also be saved
as the default value in your user defaults.

Although SAP system data, such as the material master, is stored as client-indepen-
dent data in a database, you can only access the data of the client you are logged
in to.

2.1.2 Company Code


Within the SAP system, an enterprise that carries out its own independent account-
ing is configured as a company code. You can perform month-end and year-end clos-
ings at this level.

However, you never have to define a company code when processing a sales order,
a delivery, or a shipment, for example. This is because you directly or indirectly
assign all other organizational units to a company code. Based on the business pro-
cess, the system can then determine the correct company code automatically.

Generally, the following values are assigned to the company code (see Figure
2.2):

EE Address data
Because the company code denotes an independent enterprise, you enter the
enterprise address here.
EE Currency key
Accounting has to be carried out in the country currency. In the SAP system,
this currency is also referred to as the local currency. If documents (for example,
outgoing invoices) are issued in a foreign currency, this currency is converted
into the local currency when the documents are entered into the accounting
system.

25

5065_BOOK.indb 25 3/7/08 7:52:11 AM


2 Organizational Structures in Logistics

EE Country key
The country key specifies the country that is supposed to be considered the
domestic country for business processes. All business transactions with a dif-
ferent country key are considered foreign business.
EE Language key
In all documents and processes, texts are used, which can be created in multiple
languages. The language key serves to find the text in the correct language (the
national language).

Figure 2.2 Defining a Company Code

Technical Information About the Company Code


EE Field Length: 4 places
EE Path in Customizing: Enterprise Structure • Definition • Financial Accounting •
Edit, Copy, Delete, Check Company Code
EE Specific Transaction: EC01 (copy, delete, and check only)
EE Table: T001

2.1.3 Plant
A plant is an operating site or a subsidiary within an enterprise. You must assign
the plant to a company code, and cannot assign it to multiple company codes.
At least one plant has to have the same country key as the company code. SAP

26

5065_BOOK.indb 26 3/7/08 7:52:12 AM


Logistic Organizational Structures 2.1

recommends generally creating a separate company code for each plant with a
different country key.

In the SAP system, a plant has the following characteristics:

EE Quantity-based inventory management, including distribution to storage loca-


tions
EE Inventory management on a value-only basis, if the plant has been selected as
the material valuation level
EE Planning of stocks
EE Assignment to a company code (see Figure 2.4)
EE Assignment of logistic organizational units
EE Assignment of a customer and supplier number, which are used for cross-plant
stock transfers (see Section 4.2.1)

Similar to company codes, you have to maintain the following values for plants
(see Figure 2.3):

EE Address data
The address of the plant.
EE Language key
The language key you assign to the plant.
EE Country key
The country key of the country in which the plant is located.

Figure 2.3 Plant Definition

27

5065_BOOK.indb 27 3/7/08 7:52:12 AM


2 Organizational Structures in Logistics

Figure 2.4 Assigning Plants to a Company Code

Technical Information About the Plant


EE Field Length: 4 places
EE Path in Customizing: Enterprise Structure • Definition • Logistics - General •
Define, copy, delete, check plant
EE Specific Transaction: EC02 (copy, delete, and check only)
EE Table: T001W

Technical Information About Assigning a Plant to a Company Code


EE Path in Customizing: Enterprise Structure • Assignment • Logistics - General •
Assign plant to company code
EE Specific Transaction: OX18
EE Table: T001K

2.1.4 Storage Location


A storage location is the place where stocks are managed physically. In the system,
you assign a plant to the storage location. A plant can have multiple storage loca-
tions, which are physically or functionally separate. Within a plant, for example,
you can define a raw materials warehouse, a production warehouse, a finished
goods warehouse, and a delivery warehouse (see Figure 2.5).

28

5065_BOOK.indb 28 3/7/08 7:52:13 AM


Logistic Organizational Structures 2.1

Figure 2.5 Defining a Storage Location

In the SAP system, a storage location has the following characteristics:


EE Stocks are managed by quantity in the storage location.
EE There is no material valuation. This takes place at plant level.
EE If the Warehouse Management (WM) system is activated in the SAP system,
you can define the storage location as a WM-managed storage location and
assign a warehouse number to it.
EE Physical inventories are taken in the storage location and not at plant level.
EE You can assign an address.
You can assign the storage location to a plant when you define it. A popup opens,
in which you are prompted for a plant.

Technical Information About the Storage Location


EE Field Length: 4 places
EE Path in Customizing: Enterprise Structure • Definition • Materials Management •
Maintain storage location
EE Specific Transaction: OX09
EE Table: T001L

2.1.5 Shipping Point


The shipping point is a logistic organizational unit that handles the entire shipping
process. They are assigned to a specific shipping point when they are created, and
so you can plan all deliveries that have been created for a shipping point together.
In most companies, shipping points are physically separate. Different product lines
(for example, car and furniture varnishes) or different customer types (for exam-

29

5065_BOOK.indb 29 3/7/08 7:52:13 AM


2 Organizational Structures in Logistics

ple, deliveries to hardware stores or specialized retailers) can also be processed


through different shipping points.

The shipping point is usually determined automatically when the sales order is cre-
ated, but it can be entered manually as well. You can create individual loading and
pick/pack times for each shipping point, which are then considered for shipment
scheduling. The shipping point can be taken into account for printer determina-
tion to allow shipping documents to get printed. Reports, statistics, or worklists
are selected using the shipping point. You can, for example, select deliveries wait-
ing to be shipped from your shipping point.

As you can see in Figure 2.6, there are additional shipping point settings in the
SAP system. A detailed description of these settings can be found in the sections
in which the associated processes are explained in detail.

Technical Information About the Shipping Point


EE Field Length: 4 places
EE Path in Customizing: Enterprise Structure • Definition • Logistics Execution •
Define, copy, delete, check shipping point
EE Specific Transaction: EC07 (copy, delete, and check only)
EE Tables: TVST and TVSTT (short names)

Figure 2.6 Defining the Shipping Point with All Control Parameters

30

5065_BOOK.indb 30 3/7/08 7:52:14 AM


Logistic Organizational Structures 2.1

If you drill down further, you can subdivide the shipping point into individual
loading points. Higher up the hierarchy you have to assign the shipping point to
at least one plant. An example of this is illustrated in Figure 2.7.

Figure 2.7 Assigning Shipping Points to Plants

Technical Information About Assigning Shipping Points to Plants


EE Path in Customizing: Enterprise Structure • Assignment • Logistics Execution •
Assign shipping point to plant
EE Specific Transaction: OVXC
EE Table: TVSWZ

2.1.6 Loading Point


In larger companies, where the shipping points are distributed across several
buildings, it can be useful to subdivide the shipping points even further into load-
ing points. One loading point, for example, could be used only for self-collectors,
whereas another one could be used for regular truck loading (see Figure 2.8). The
loading point, as such, is informal in the SAP system. It tells the shipping company
where to collect the goods.

Figure 2.8 Defining Loading Points

31

5065_BOOK.indb 31 3/7/08 7:52:14 AM


2 Organizational Structures in Logistics

If you need to define loading points, the system prompts you to enter the ship-
ping point before you can enter the loading point. The loading point is therefore
assigned to a shipping point. If you do not need to define loading points, you can
leave it blank, and the loading point appears blank in delivery documents.

Technical Information About the Loading Point


EE Field Length: 2 places
EE Path in Customizing: Enterprise Structure • Definition • Logistics Execution •
Maintain loading point
EE Specific Transaction: –
EE Tables: TVLA and TVLAT (short names)

2.1.7 Transportation Planning Point


The transportation planning point maps the Shipping Planning and Shipping Sched-
uling department in an enterprise. Here, deliveries are grouped together with
shipments, they are planned and, if necessary, settled. Shipments are generally
assigned to a transportation planning point.

The transportation planning point must be assigned to a company code (see Figure
2.9). This assignment is required when the shipment costs are calculated by the
SAP system and transferred to the accounting department after the shipment has
been completed.

Figure 2.9 Defining the Transportation Planning Points

Technical Information About the Transportation Planning Point


EE Field Length: 4 places
EE Path in Customizing: Enterprise Structure • Definition • Logistics Execution •
Maintain transportation planning point
EE Specific Transaction: –
EE Tables: TTDS and TTDST (short names)

32

5065_BOOK.indb 32 3/7/08 7:52:15 AM


Warehouse-Related Organizational Structures 2.2

2.2 Warehouse-Related Organizational Structures

In addition to the structures that are relevant for logistics, there are other organi-
zational structures in an enterprise that are only indirectly related to the tasks of
the Shipping departments. There is rarely someone in a Shipping department who
does not have to answer the following questions: “Have the goods for delivery XY
already been picked?” and “Are the goods still in the warehouse?“ To be able to
answer these questions quickly and reliably, it is helpful if the employee knows
the organizational structure of the warehouse.

If you don‘t use the SAP WM component, the structures described here are not
needed.

WM is a retailing system used for managing stocks in individual storage bins. If


WM is used in a storage location, this storage location is assigned a warehouse
number, which corresponds to one or more storage locations. Within a warehouse
number, storage types are maintained. A storage type describes a physical location
within a warehouse. You have to define different storage types, if they are orga-
nized differently in terms of the warehouse processes. A fully automated high-
rack storage area, for example, is structured differently than a simple picking area,
where forklifts are used to approach the bins. Figure 2.10 provides another over-
view of the complete warehouse structure.

Warehouse Number

Storage Type 1 Storage Type 2

Storage Area 1 Storage Area 2 Storage Area 1

Storage Bin 1 Storage Bin 1 Storage Bin 1

Storage Bin 2 Storage Bin 2 Storage Bin 2

Interim Interim
Storage Area Storage Area
Goods Goods Issue
Receipt

Figure 2.10  Overview of the Organizational Structure of a Warehouse

33

5065_BOOK.indb 33 3/7/08 7:52:15 AM


2 Organizational Structures in Logistics

Within a storage type, storage areas can be defined. Structural differences of the
storage bins (high storage bins in a rack, low storage bins), for example, can result
in certain materials only being stored in certain bins (storage areas depending
on pallet height). If stocks are divided even further and are managed per pallet,
the term storage units is used in WM. This allows you to immediately see which
materials are stored in the individual storage units and in which storage bin they
are stored.

2.2.1 Warehouse Number


In WM, you define a warehouse number for a warehouse complex (building, site).
You can group together multiple storage locations and plants to a warehouse num-
ber. The stocks at warehouse number level are only recorded by quantity.

Technical Information About the Warehouse Number


EE Field Length: 3 places
EE Path in Customizing: Enterprise Structure • Definition • Logistics Execution •
Define, copy, delete, check warehouse number
EE Specific Transaction: EC09 (copy, delete, and check only)
EE Tables: T300, T300T (short names), and T320 (assigned to a storage location and
plant)

2.2.2 Storage Type


Within a warehouse complex (= warehouse number), you will find different stor-
age areas (high-rack storage areas, block storage areas, shipping deployment areas,
picking areas, etc.), which are called storage types in WM. However, even identical
storage areas that differ only in their organization have to be defined as separate
storage types (there may be shelves in a picking area that require a capacity check
at the storage bin level, whereas other shelves do not require a check).

In addition, there are interim storage areas, which can be difficult to understand,
particularly if WM has only been implemented recently. Interim storage areas (see
Figure 2.11) are not physical, but virtual storage bins. Even negative stocks are
allowed in these areas.

34

5065_BOOK.indb 34 3/7/08 7:52:15 AM


Warehouse-Related Organizational Structures 2.2

Employees in Shipping departments mostly come across interim storage area 916.
This is the storage type from which goods issues are posted in the standard SAP
system.

Technical Information About the Storage Type


EE Field Length: 3 places
EE Path in Customizing: Logistics Execution • Warehouse Management • Master
Data • Define Storage Type
EE Specific Transaction: –
EE Table: T331

Figure 2.11 Some Preconfigured Storage Types in the Standard SAP System

2.2.3 Storage Section


Within a storage type, there are usually storage bins with different properties. Stor-
age bins with the same properties are combined into storage sections.

For example, you can combine storage bins of a certain capacity (volume or storage
weight). You can also define storage sections based on the ABC classification of the
materials. This means quicker access to fast-moving items (A materials), whereas
slow-moving items are stored at the back of the storage section. You can also group
the storage sections by hazardous materials classes or temperature sensitivity.

35

5065_BOOK.indb 35 3/7/08 7:52:15 AM


2 Organizational Structures in Logistics

Technical Information About the Storage Section


EE Field Length: 3 places
EE Path in Customizing: Logistics Execution • Warehouse Management • Master
Data • Define Storage Section
EE Specific Transaction: -
EE Tables: T302 and T302T (short names)

2.2.4 Storage Bin


In SAP WM, a storage bin is the physical location of the bin in the warehouse. In
interim storage areas, however, you can also find dynamic storage bins.

Physical storage bins are not created using Customizing. WM transactions are used
instead to create them manually. The name of a storage bin can be 10 characters
long. Dynamic storage bins are created automatically by the system when goods
receipts and goods issues are posted.

You want to pick and clear a delivery with delivery number 7480003600. After pick-
ing has been completed, the materials are located in storage type 916, storage bin
7480003600 in the system. The goods issue posting withdraws the material from this
storage bin so that this bin becomes empty and is deleted by the system.

2.2.5 Storage Unit


If you also manage your stocks in the WM system with pallets or other loading
equipment (wire baskets, metal containers, etc.), you have to configure storage
units for the relevant storage types. The quantity-based stock is then managed at
the storage bin, and additionally at pallet level.

These pallets are assigned a number in WM, the storage unit number. The number
consists of ten places. To be able to identify the unit in the system, the storage unit
number is assigned a storage unit type. The storage unit type is a three-digit key.
Figure 2.12 shows the storage unit types predefined in the standard SAP system.

36

5065_BOOK.indb 36 3/7/08 7:52:16 AM


Organizational Structures in Sales 2.3

Figure 2.12 Storage Unit Types Predefined in the Standard SAP System

Technical Information About the Storage Unit Type


EE Field Length: 3 places
EE Path in Customizing: Logistics Execution • Warehouse Management • Strategies •
Activate Storage Bin Type Determination • Definitions Storage unit type
EE Specific Transaction: OMM1 (Storage unit type button)
EE Tables: T307 and T307T (short names)

2.3 Organizational Structures in Sales

Deliveries in SAP Logistics Execution System (LES) are mostly based on sales orders
or stock transport orders from the Purchasing department.

The structure of the Sales Order and Purchasing departments differs from the
structure of the Shipping department in the SAP system. This structure is reflected
in the shipping view for stock transport orders and in the header data for sales
orders.

The top structure is the actual sales organization. An enterprise often sells different
products that are processed by different organizations. Within the organization,
multiple distribution channels can exist, which are mainly based on the customer
structure (for example, processing orders with beverage wholesalers or directly
with restaurants and hotels). Based on the material structure, the sales organiza-
tion can be subdivided into several divisions (for example, alcoholic beverages and
accessories). These structures are shown in Figure 2.13.

37

5065_BOOK.indb 37 3/7/08 7:52:16 AM


2 Organizational Structures in Logistics

You can also structure the Sales department or the order processing physically
in the SAP system. Using the sales offices, you can reflect the physically separate
responsibilities for sales orders. Within a sales office, you can establish different
sales groups.

Sales Organization G Sales Organization M

Distribution Distribution Distribution Distribution


Channel Direct Channel Channel Direct Channel
Customer Wholesalers Customer Wholesalers

Division AC Division AC

Division AB Division AB

Division BE Division BE Sales Office South

Sales Office North

Sales Group 1 Sales Group 2

Figure 2.13 Overview of the Sales Organization

2.3.1 Sales Organization


The sales organization is the organizational unit in an enterprise responsible for the
sale of certain goods. The most important features of a sales organization are:

EE It contains separate material master data and customer master data.


EE It belongs to a company code.
EE It is assigned to at least one plant.
EE It is assigned all items of a sales document (and also of a delivery note).

38

5065_BOOK.indb 38 3/7/08 7:52:17 AM


Organizational Structures in Sales 2.3

Even though the sales organization does not play a major role in logistic sales and
distribution documents, it is helpful for the user to know about this organizational
unit.

In the beverages industry, two sales organizations could be considered: One deals with
the actual sales of beverages, the other is responsible for the sales and maintenance of
promotional material and restaurant supplies (for example, glasses, coasters, draft beer
dispensing equipment, billboards, etc.).

Technical Information About the Sales Organization


EE Field Length: 4 places
EE Path in Customizing: Enterprise Structure • Definition • Sales and Distribution •
Define, copy, delete, check sales organization
EE Specific Transaction: EC04 (copy, delete, and check only)
EE Tables: TVKO and TVKOT (short names), and TVKWZ (assigning to a plant)

2.3.2 Distribution Channel


Within a sales organization, you must define the distribution channels, which is
based on the customer structure (for example, retail or wholesale). The most
important features of a distribution channel are:

EE It is assigned to one or more sales organizations.


EE It is assigned to one or more plants.
EE It contains separate material master data and customer master data. If the mas-
ter data for each distribution channel is the same, you can also enter the data
for a general distribution channel.
EE At the distribution channel level, price determination can be undertaken sepa-
rately.

In the beverages industry, you could define one distribution channel for the delivery to
wholesalers, and another one for direct delivery to restaurants and hotels.

39

5065_BOOK.indb 39 3/7/08 7:52:17 AM


2 Organizational Structures in Logistics

Technical Information About the Distribution Channel


EE Field Length: 2 places
EE Path in Customizing: Enterprise Structure • Definition • Sales and Distribution •
Define, copy, delete, check distribution channel
EE Specific Transaction: EC05 (copy, delete, and check only)
EE Tables: TVTW and TVTWT (short names), and TVKOV (assigning to the sales orga-
nization)

2.3.3 Division
A division is an organizational unit that is based on the material structure in your
enterprise. Using divisions, you can define materials with the same sales orienta-
tion. In addition, a division in the material master is used to carry out the business
area account assignment for logistic processes in financial accounting together
with the plant. The most important features of a division are:

EE It is assigned to one or more sales organizations and to one or more distribution


channels (see Figure 2.14).
EE The material is always assigned to a division.
EE It contains separate customer master data.
EE At division level, price determination can be performed separately.

Figure 2.14 Assigning Distribution Channels and Divisions to a Sales Organization

40

5065_BOOK.indb 40 3/7/08 7:52:18 AM


Organizational Structures in Sales 2.3

In the beverages sales organization, you will find the three divisions: mineral water, fruit
juices, and alcoholic drinks. This allows for several combinations. The mineral water
division, for example, can be processed via the wholesale distribution channel or can be
sold directly to restaurants and hotels.

Technical Information About the Division


EE Field Length: 2 places
EE Path in Customizing: Enterprise Structure • Definition • Logistics - General •
Define, copy, delete, check division
EE Specific Transaction: EC06 (copy, delete, and check only)
EE Tables: TSPA and TSPAT (short names), and TVKOS (assigning to the sales organiza-
tion)

2.3.4 Sales Office


You configure the organizational units in your enterprise, which are considered
physically or functionally separate, as sales offices in the SAP system. Configuring
sales offices is not mandatory. However, if you configure sales offices, you must
assign each sales office to one or more sales organizations, distribution channels,
and divisions (see Figure 2.15).

The sales office has no additional function in the SAP system, which would have
an impact on business processes. However, you can maintain a sales office in the
sales documents. This allows you to select sales documents by sales offices.

For beverage sales, you configure a sales office for northern and central Germany, and
another sales office for southern Germany.

Figure 2.15 Assigning Sales Offices to Sales Organizations/Distribution Channels/Divisions

41

5065_BOOK.indb 41 3/7/08 7:52:18 AM


2 Organizational Structures in Logistics

Technical Information About the Sales Office


EE Field Length: 4 places
EE Path in Customizing: Enterprise Structure • Definition • Sales and Distribution •
Maintain sales office
EE Specific Transaction: –
EE Tables: TVBUR and TVKBZ (assigning to sales organization, distribution channel, and
division)

2.3.5 Sales Group


Organizationally, the sales office can be subdivided even further into sales groups.
The sales groups have the same features in the SAP system as the sales offices.
They are not necessarily required for the business process flow. Sales groups are
assigned to the sales offices.

The sales office handling southern Germany is divided into three sales groups. One sales
group is only in charge of the cities of Munich and Stuttgart, the other sales group looks
after customers in the rest of southern Germany. The third group is responsible for de-
liveries for special occasions and celebrations.

Technical Information About the Sales Group


EE Field Length: 3 places
EE Path in Customizing: Enterprise Structure • Definition • Sales and Distribution •
Maintain sales group
EE Specific Transaction: –
EE Tables: TVKGR and TVBVK (assigning to sales offices)

2.4 Summary

This chapter has provided an overview of the logistic organizational units. You now
know the relevance and tasks of the individual units and how they relate to each other.
You have also learned about the organizational structures that do not directly
belong to the shipping and transportation system, but are a part of the upstream
processes (organizational structure of sales and distribution) and warehouse pro-
cesses (organizational structure of a warehouse in WM).
The next chapter covers the master data that is required for processes in the ship-
ping and transportation system.

42

5065_BOOK.indb 42 3/7/08 7:52:18 AM


Index
0-items Per schedule line category, 73
Retroactive delivery split, 544 Scheduling in delivery document, 179
Available To Promise (ATP), 163

A
B
Access sequence, 352
Batch determination, 211 Backward scheduling, 162, 184
For shipment document, 505, 506 Base mode-of-transport category, 319
Output determination, 352, 506 Base unit of measure, 45, 46
Packing instructions, 307 Basic data
Shipment cost settlement, 463 Material master file, 44
Text determination, 199 Basic IDoc type, 520
Account assignment category Batch
Per schedule line category, 73 Capture in transfer order, 271
Account determination Batch classification, 216
GI posting, 548 Batch determination, 209
Account determination simulation, 552 Access sequence, 211
Accounting document, 552 Background processing, 212
Activity profile, 494 Condition table, 210
Assign, 495 In delivery document, 111, 218
Maintain, 496 Log in delivery document, 220
Additional data Per order item category, 70
Customer master file, 51, 55 Strategy type, 212
Material master file, 46 Batch item
Address Packing relevance, 283
Company code, 25 Batch job
Customer master file, 53 Create for GI posting, 536
Plant, 27 Batch management, 57, 207
Purchase order, 94 Batch master data maintenance
Sales order, 67 Transaction, 60
Storage location, 29 Batch master file, 57
ADR Batch master maintenance
Dangerous goods regulations, 320 Transaction, 59
Air traffic Batch search procedure, 213
Transit country, 332 Batch search strategy, 209
Alternative unit of measure, 45 Batch split, 217
Analysis function Confirmation of transfer order, 272
Batch determination, 223 Batch split item, 115, 223
ATP availability check After picking, 243
Sample cases, 167 Batch status, 58
ATP check, 163 Batch variant
Availability check, 162 Shipment creation, 402
In the delivery document, 111 Billing

557

5065_BOOK.indb 557 3/7/08 7:55:50 AM


Index

In activity profile, 498 Combination of characteristic values


Outputs in activity profile, 498 Packing instructions, 305
Billing status, 377 Commercial/import code number, 203, 205
internal billing, 378 Communication channel
Bill-to party, 52 Output determination, 366
Bin location Output type in shipment document, 508
In material master, 265 Company code
Blocked stock, 163 Customer master file, 51
Break-weight settlement, 484 Definition, 25
Business transaction type, 204 In-stock transport order, 99
Complete delivery
Retroactive delivery split, 544
C Sales order entry, 78
Completeness check
Calculation base
Dangerous goods check, 323
Shipment cost settlement, 466
Components
Calculation type
Packing instructions, 311
Scale, 475
Condition, 482
Shipment cost settlement, 466
Copying texts, 199
Cancellation
Execution of picking, 241
Goods issue posting, 536
In access sequence, 352
Capacity limit
Output determination shipment, 507
Shipment creation, 399
Condition category
CARNOT, 516
Shipment cost settlement, 466
Carrier, 414
Condition class
Certificate or origin, 205
Shipment cost settlement, 465
CFR-49
Condition exclusion group, 485
Dangerous goods regulations, 323
Condition exclusion procedure, 487
Chart of accounts
Condition record
For account determination, 548
Batch determination, 216
Check-in
Output determination, 358
In shipment document, 412, 492
Condition system
Checking rule, 163
Shipment cost settlement, 461
Check method type
Condition table
Dangerous goods check, 324
Batch determination, 209
Check profile
For shipment document, 505
Packing instruction, 311
Message determination, 350, 505
Classification
Shipment cost settlement, 461
Of the batch, 215
Condition type
Dangerous goods master file, 60
Price analysis, 481
Client, 25
Shipment cost settlement, 460, 464
Collective processing
Confirmation
Goods issue posting, 532
Complete transfer order, 270
Transportation chain, 427
Delivery monitor, 379
Collective run number, 136
Of transfer orders, 270
Shipment creation, 403
Picking quantity, 244
Collective shipment, 389

558

5065_BOOK.indb 558 3/7/08 7:55:50 AM


Index

Transfer order items, 270 D


Transport order, 240
Confirmation requirement Dangerous goods, 59
Picking, 240 Dangerous goods check, 321
User exit, 240 Activate, 322
Confirmation status, 375 Activating in shipment document, 338
Consignment In delivery document, 327
Fill-up, 85 In shipment document, 337
Pickup, 87 Dangerous goods check log
Processing, 85 In delivery document, 334
Return, 88 Dangerous goods check method
Store, 85 Definition, 324
Withdrawal, 86 Dangerous goods check schema
Conversion Factor Definition, 325
unit of measure, 45, 46 For delivery document, 327
Copy control, 138 Dangerous goods flag
For a delivery item, 140 Sales order entry, 78
Copy requirement, 139 Dangerous goods indicator profile, 329
Sales order delivery type, 138 In delivery document, 336
Copy routine Dangerous goods management profile
Deadlines in shipment document, 413 Sales order entry, 78
Partner function in shipment document, Dangerous goods master data, 317
417 Dangerous goods master file, 59
Country key Dangerous goods master record
Company code, 26 Release, 334
Plant, 27 Dangerous goods regulation, 59
Country of origin, 204 Definition, 321
Credit check Dangerous goods rule
Overall status, 377 Dangerous goods master file, 61
Currency key Dangerous goods storage class
Company code, 25 Dangerous goods master file, 60
Customer Data transfer
As transportation connection point in a For creating delivery documents, 140
route, 150 Item fields in the delivery document, 141
Customer master Date
Delivering plant, 147 In shipment stage, 494
Customer master file, 50 Status in shipment document, 493
Additional data, 51, 55 Date/time
Company code data, 51 In output determination, 358
Defining views, 50 Delete
General data, 50, 53 Conditions, 467
Organizational level, 50 Deletion flag
Sales area data, 51 Customer master file, 55
Customer master record maintenance DELFOR, 514
Transaction, 51 Delivering plant, 80
Customer-material info record, 146 Customer master file, 55
Delivering plant, 146 Definition, 146

559

5065_BOOK.indb 559 3/7/08 7:55:50 AM


Index

In-stock transport order, 94 Delivery relevance


Material master file, 48 Per order item category, 70
Stock transport order entry, 99 Per schedule line category, 71
Delivery Delivery scheduling, 179
Free-of-charge, 91 Delivery split, 173
Delivery block For different partner functions, 174
Automatic per order type, 69 Delivery tolerance
Per schedule line category, 72 Sales order entry, 81
Sales order entry, 78 Delivery type
Delivery combination, 172 Creating a delivery document, 117
Delivery creation date Definition, 109
Rule for calculating a default value, 122 Determination, 109
Delivery date Incompletion procedure, 188
In schedule line, 81 In output determination, 358
In shipment document, 413 Partner determination procedure, 193
Suggestion per order type, 69 Per order type, 68
Delivery document, 103 Text determination procedure, 195
Adding items, 119 Delvery split
Background creation, 125 For different warehouse numbers, 175
Batch determination, 218 Department
Creating, 115 Sales order entry, 78
Creating individual documents manually, Departure country
116 Dangerous goods check in delivery docu-
Creation in a collective run, 122 ment, 330
Creation in batch mode, 134 Dangerous goods check in shipment docu-
Remove from shipment document, 409 ment, 340
Serial number, 228 Departure point
Transfer to shipment document, 410 Dangerous goods check in shipment docu-
Delivery document creation ment, 340
Availability check, 165 For stages, 443
Delivery header, 105 DESADV, 514
Outputs in activity profile, 498 Destination
Delivery item, 105 For stages, 443
Delivery item category, 110 Destination country
Definition, 111 Dangerous goods check in delivery docu-
Determination, 112 ment, 330
Delivery item type Dangerous goods check in the shipment
Text determination procedure, 195 document, 340
Delivery monitor, 178, 276, 378 Destination point
Selection options, 380 Dangerous goods check in shipment docu-
Delivery note ment, 340
With dangerous goods data, 343 In preliminary leg, 426
Delivery priority Determination of loading time, 182, 183
Customer master file, 55 Determination of time required for picking
Sales order entry, 80 and packing, 180
Delivery quantity Determination rule
Picking status, 373 Packing instruction, 312

560

5065_BOOK.indb 560 3/7/08 7:55:50 AM


Index

Determination type E
Packing instruction, 308
Determining the shipping type EAN, 47
Dangerous goods check in delivery docu- EDI output
ment, 332 Delivery document settings, 514
DG63_CHK_INIT_HEADER, 323, 326 For delivery document, 514
DG63_CHK_MLOAD, 323 For shipment document, 516
DG check schema determination routine EDI_PROCESSING, 515
For delivery documents, 328 Entrances, 229
For shipment documents, 338 Equipment category
Difference indicator Serial number, 225
In lean WM, 260 Error log
Difference quantity Collective processing GI posting, 534
Transfer order item, 272 Creating a delivery document, 118
Direct leg, 440 During save of shipment, 497
Definition in shipment type, 389 Extending the delivery document, 120
Dispatch time Foreign trade, 206
Output type in shipment document, 508 For goods issue posting, 529
Display European Article Number (EAN), 47
Of custom layouts, 130 Exclusion procedure
Distance Shipment cost settlement, 484
In route, 424 EXIT_SAPLSTAG_001, 443
Distribution EXIT_SAPLV02V_001, 97
Warehouse management system, 380 EXIT_SAPLV02V_003, 248
Distribution channel EXIT_SAPLV02V_004, 250
Assigning to sales organization, 39 EXIT_SAPLV50P_001, 273
Sales order entry, 74 EXIT_SAPLV50Q_001, 381
Division EXIT_SAPLV50Q_002, 381
assigning to sales organization, 40 EXIT_SAPLV56B_001, 388
Definition, 40 EXIT_SAPLV56F_010, 414
Sales order entry, 74 EXIT_SAPLV56F_011, 500
Document flow, 65, 530 EXIT_SAPLV56F_012, 500
Stock transport order, 93 EXIT_SAPLV56S_001, 441
Document header EXIT_SAPLV56U_004, 395
Material document, 531 EXIT_SAPLV56U_005, 395
Document item, 67 EXIT_SAPMV53W_001, 280
Document number EXIT_SAPMV53W_002, 280
Sales document, 64 EXIT_SAPMV53W_003, 280
Document status, 65 Expiration date, 215
Document type Export customs office, 203
Definition, 65 Export declaration, 205
Domestic mode of transportation, 203 Export procedure, 204
Door, 244 External transportation planning system, 428
Definition, 246 Extrastat, 205
Determination by route, 248
Determination by ship-to party, 247
Determination rule, 246

561

5065_BOOK.indb 561 3/7/08 7:55:50 AM


Index

F Goods movement data


In delivery document, 529
Fast entry Goods receipt posting
During setting of status, 496 For returns orders, 90
F code profile Goods receipt processing time, 165
Creating a delivery document in the back- Goods receiving hour
ground, 135 Of a goods receiving point, 159
Field catalog Goods receiving hours
Batch determination, 210 Customer master file, 54
Fields Maintaining a time scheme, 160
Determine in shipment document, 496 Taking into consideration in sales order,
Field selection 161
For fast entry, 496 Goods receiving point
Filter Customer master file, 54
In custom layouts, 130 For a ship-to party, 159
Final destination Gross weight
In a route, 150 Material master file, 45
Fixed bin locations Group
In lean WM, 257 Of delivery documents, 275
Forwarding agent Of the collective run, 137
In shipment document, 414 Group condition
Forward scheduling, 162, 184 Shipment cost settlement, 466
FTCn, 206 Group condition routine
FV45Cnnn Shipment cost settlement, 466
For creating delivery documents, 140 Group creation, 275
FV50UZXX, 190 Group formation
Retroactive delivery split, 543
Group indicator
G Shipment cost settlement, 466
Grouping criteria
Generate HUs
Shipment creation, 396
In activity profile, 498
Group number, 276
Goods issue
Creating a delivery document in the back-
In pick list, 379
ground, 136
Goods issue date, 534
Group type, 275, 356
In shipment document, 413
Retroactive delivery split, 543
Goods issue document, 530
Goods issue interim storage
In lean WM, 272 H
Goods issue posting, 104, 528
Availability check, 165 Handling Unit (HU)
Background, 534 Adjust quantities, 301
Batch job, 536 Create full HUs, 295
Collective processing, 532 Delete, 300
In activity profile, 497 Empty, 300
Single document, 529 Individual packing, 292
Goods issue status, 376 Outputs in activity profile, 498

562

5065_BOOK.indb 562 3/7/08 7:55:50 AM


Index

Pack from the tree structure, 297 Individual shipment, 388


Handling Unit monitor, 314 In-house production time, 165
HAZMAT_CHK_ACTIVE, 322 Interim storage areas, 34
HAZMAT_CHK_FIND_SCHEMA, 328, 339 Intrastat, 202, 205
HAZMAT_CHK_MOT, 323 Item
HAZMAT_CHK_PIH, 323 Shipment document, 386
HAZMAT_CHK_VARIOUS, 323, 326 Item category, 107
Header check methods Sales order, 69
Dangerous goods check, 323 Third-party order, 83
Header condition Item category determination
Shipment cost settlement, 467 In the delivery document, 112
Header data Item category group, 84, 112
Shipment document, 386 Packaging material, 303
Header status Item category usage, 114
In delivery document, 371 Item condition, 467
Header text, 193 Item data
Hidden columns In the material document, 531
List variant, 127 Item generation
History Packing, 302
Serial number, 228 Item number
HUMO, 315 Sales order entry, 75
HU type Item numbering
Per packaging material type, 287 Retroactive delivery split, 544
Item procedure group, 470, 471
Item text, 193
I Itinerary, 440
IATA-C
Dangerous goods regulations, 320 J
IATA-P
Dangerous goods regulations, 320 Job overview
IDoc creation Goods issue posting, 535
Direct, 518
IDoc number, 524
IDoc output K
Inbound, 518
KOBRA, 205
Outbound, 517
IDoc processing, 517
Indirect, 518 L
IDoc type, 519
IFTMIN, 516 Labeling
Immediate delivery flag, 69 Dangerous goods master file, 61
Incompletion check, 185 Language
In delivery document, 189 In output determination, 358
Incompletion group, 187 Language ID
Incompletion procedure, 187 Copying texts, 199
Incompletion status group, 185 Language key

563

5065_BOOK.indb 563 3/7/08 7:55:50 AM


Index

Company code, 26 Creating a delivery document in the back-


Plant, 27 ground, 136
Layout During save of shipment, 497
Selecting, 129 Shipment creation via batch, 403
User-specific, 128 Logging in to system, 25
Lean WM, 254 LV45Cnnn
Bin location in the material master, 265 Copy requirement, 139
Picking area, 265 LV50PFZA, 378
Legal controls, 202
Leg determination
According to departure point and itiner- M
ary, 447
Main leg, 391, 440, 448
Leg indicator, 391, 440, 448
Dangerous goods check in delivery docu-
For the transit country, 332
ment, 333
Per shipment type, 389
Maintaining dangerous goods master data
LE_SHP_DELIVERY_PROC, 121, 142
Transaction, 320
LE_SHP_TAB_CUST_HEAD, 106
Maintain text
LE_SHP_TAB_CUST_ITEM, 106
In delivery document, 201
LE_SHP_TAB_CUST_OVER, 105
Manual entries
List variant
Shipment cost settlement, 467
Creation, 127
Material availability date, 162
Loading date, 181, 183
Material group
In shipment document, 413
Packaging materials, 287
Loading end
Material item usage, 302
In shipment document, 412, 493
Material master file, 43
Status in shipment document, 493
Additional data, 46
Loading group
Basic data, 44
Definition, 145
Defining organizational level, 44
Determination, 145
Defining views, 44
Determination of loading time, 182
Plant, 49
Shipping point determination, 145
Sales data, 48
Loading point, 245
Storage location data, 49
Assigning to shipping point, 32
Material master maintenance
Definition, 31
Transactions, 44
In delivery document, 251
Material master record
Loading start
Delivering plant, 147
In shipment document, 412
Material staging date, 180
In the shipment document, 492
Matrix maintenance
Status in the shipment document, 492
Shipment cost settlement, 466
Loading time, 180, 182
Maximum
Load transfer point, 451
Shipment values, 475
As transportation connection point in a
Maximum number of partial delieries
route, 150
Sales order entry, 80
Log
MD04 Stock/Requirements Overview, 166
Creating a delivery document, 118
Means of transport, 437
Creating a delivery document in a collective
Category, 437
run, 126

564

5065_BOOK.indb 564 3/7/08 7:55:50 AM


Index

Type, 404 In customer master, 173


Medium Sales order entry, 78
Output type in shipment document, 508 Order header, 67
Minimum quantity Order item Category
In the delivery document, 111 per schedule line category, 73
Minimum values Order type, 93
Shipment cost settlement, 475 Consignment fill-up, 85
Mixed loading Consignment pickup, 87
Dangerous goods master file, 61 Consignment return, 88
Mode of transport, 406 Consignment withdrawal, 86
Definition, 319 Definition, 68
Dangerous goods regulations, 319 Free-of-charge delivery, 91
Movement type Free-of-charge subsequent delivery, 91
In lean WM, 258 Per schedule line category, 73
Per schedule line category, 71 Returns, 90
In material document, 531 Standard order, 74
Multilevel packing, 298 Third-party order, 82
MV50AFZ1, 121, 142 Organizational key
MV50AFZ2, 224 Tariff zones assignment, 476
MV50AFZ3 Organizational level
Confirmation requirement, 240 Customer master file, 50
MV50AFZZ, 224 Material master file, 44
Storage location determination, 236 Organizational structure
Logistic, 23
Sales and accounting, 37
N Warehouse-related, 33
Organizational unit
Net weight
Company code, 25
Material master file, 45
Distribution channel, 39
Number assignment
Division, 40
For handling units, 287
Loading point, 31
Number of messages
Plant, 26
In output determination, 358
Sales group, 42
Number of packages in the delivery
Sales office, 41
­document, 297
Sales organization, 38
Number range
Shipping point, 29
Delivery document, 107
Storage area, 35
SSCC numbers, 290
Storage bin, 36
Transfer order, 256
Storage location, 28
Storage type, 34
O Transportation planning point, 32
Warehouse number, 34
One-step Procedure Output
stock transport order, 98 Determination using conditions, 357
Order combination, 171 For each delivery group, 363
Customer master file, 55 For each handling unit, 509

565

5065_BOOK.indb 565 3/7/08 7:55:50 AM


Index

In shipment document, 503 P


Output via activity profile, 509
Per handling unit, 363 Packaging
Output control Dangerous goods master file, 61
In shipment document, 503 Packaging material, 301
Output determination As means of transport, 438
Condition table, 350, 505 Generate delivery items, 301
Key combination, 358 In activity profile, 496
Output determination procedure, 354, 506 Proposal for packing, 294
Output type, 353, 506 Packaging material type, 285
Output determination procedure Assigning packaging material group, 288
Assignment to delivery item, 507 In activity profile, 496
Assignment to delivery type, 507 In the material master, 290
Assignment to shipment type, 507 Packing, 104
Assign to delivery item, 355 In shipment document, 432
Assign to delivery type, 355 Multilevel, 298
Assign to handling unit, 355 Packing instruction determination procedure,
In shipment document, 504, 506 308
Output determination, 354, 506 Packing instructions
Per packaging material type, 287 Access sequence, 307
Output device Combination of characteristic values, 305
In output determination, 358 Maintenance, 310
Output type Packing transaction profile, 309
As a user exit, 500 Packing list
Assignment to shipment type, 507 With dangerous goods data, 343
Default values, 354 Packing proposal
General data, 353 In the delivery document, 313
In activity profile, 498 In the sales order, 314
In SAP standard, 348 Packing-relevance, 111
In shipment document, 504, 506 Packing relevance per delivery item category,
Output determination, 353, 506 282
Per packaging material type, 287 Packing requirements, 283
Process in shipment document, 507 Packing status, 376
Repeat in shipment document, 509 Packing transaction profile
Standard output type, 504 Packing instructions, 309
Time, 354 Packing weight
Overall status Maximum allowed per handling unit, 290
Status in shipment document, 492 Partial delivery
Overdelivery Maximum for each delivery item, 253
Definition, 251 Partial delivery flag
In customer master, 252 Sales order entry, 80
In delivery document, 252 Partial delivery indicator
Over delivery tolerance Retroactive delivery split, 544
In the delivery document, 111 Partial quantities
Overhead rates or deductions Distribute to handling units, 295
Pricing procedure, 469 Partner determination
In delivery document, 190

566

5065_BOOK.indb 566 3/7/08 7:55:51 AM


Index

Partner determination procedure, 192 Planned delivery time, 165


Shipment document, 415 Planned order, 163
Partner function, 190 Planned packaging level, 544
Customer master file, 51, 55 Planning
Definition, 51 Status in shipment document, 492
EDI output type, 515 Plant
In the delivery document, 107 Assigning to company code, 26
Partner functions As transportation connection point in a
In shipment document, 415 route, 150
Partner identification, 190 Definition, 26
In shipment document, 415 Material master file, 49
Partner profile, 523 Sales order entry, 80
Partner type, 191 Plant determination
Special stock partner, 86 Per packaging material type, 287
Pass, 229 Plant —> delivering plant, 80
Payer, 52 Plus/minus
Phrase, 344 Shipment cost settlement, 465
In the phrase set, 344 PM material group
Phrase management, 342 For means of transport, 438
Phrase set, 344 POD, 79
Phrase set attribute assignment, 344 PO date
Phrasing assignment Sales order entry, 75
Activation, 342 POD status, 378
Picked quantity, 242 PO number of the customer
Batch split item, 243 Sales order entry, 75
Picking, 104, 235 Port
Delivery documents relevant for picking, As transportation connection point in a
379 route, 150
Picking area Posting transaction
In lean WM, 257 Key for account determination, 549
In the material master, 265 Preference calculation
Picking lists Export data, 202
In lean WM, 257, 261 Preference situation, 204
Print code, 262 Preliminary leg, 391, 440
Printer pool, 261 Dangerous goods check in delivery docu-
Sort profile, 262 ment, 333
Spool code, 261 Price analysis 1, 481
Picking quantity Price dependency, 462
Entry in delivery document, 242 Price unit
Picking status, 373 Pricing procedure, 475
Transfer as delivery quantity, 243 Pricing procedure, 468
Picking relevance, 111, 239 Printer
Picking status, 242, 373 Assignment to transportation planning
In lean WM, 266 point, 509
Picking storage location Printer assignment
Determination, 236 In lean WM, 263

567

5065_BOOK.indb 567 3/7/08 7:55:51 AM


Index

In shipment document, 510 RECADV, 514


Printer determination, 364, 509 Receiving plant
In lean WM, 263 As ship-to party, 95
In shipment document, 511 In-stock transport order, 94, 100
Printer name Receiving point
For output in shipment document, 511 Sales order entry, 77
Print parameter Recovery indicator
In shipment document, 509 Shipment costs, 457
Print parameters, 364 Reference condition type, 484
Process code, 518, 523 Region of origin, 204
Process control Registration, 229
Per shipment type, 389 At entrance, 231
Processing mode During checkout, 232
Outputs in activity profile, 499 Regulation
Processing routine Dangerous goods master data, 320
For EDI outputs, 515 Regulations for transporting dangerous
Processing status goods, 317
Dangerous goods master record, 335 Release status
Processing time, 49 Condition table, 463
Of the purchasing department, 165 Replenishment delivery, 92
Production order, 163 Replenishment lead time, 164
Proof of delivery Required delivery date, 162
Sales order entry, 79 In schedule line, 82
Proof of delivery —> LEB, 79 Sales order entry, 75
Provision of materials for subcontract order, Requirement
66 Shipment cost settlement, 464
Purchase order, 163 Requirements overview, 166
Creating a delivery document in a collective Reservation, 163
run, 130 Return leg, 440
Definition, 92 Returns flag
Purchase order header, 94 Per order item category, 70
Purchase requisition, 163 Returns order, 90
Purchasing group RF
In-stock transport order, 99 In lean WM, 261
Purchasing organization RLAUTA10, 273
In-stock transport order, 99 RLAUTA11, 273
RLVSDR40
In lean WM, 264
Q Role
Creating a delivery document in the back-
Quality inspection stock, 163
ground, 135
Rounding difference
R Shipment cost settlement, 466
Rounding quantity
Railway station Packing instructions, 311
As transportation connection point in a Rounding rule, 474
route, 150

568

5065_BOOK.indb 568 3/7/08 7:55:51 AM


Index

Shipment cost calculation, 475 Sales order entry, 74


Shipment cost settlement, 466 Sales order, 64
Route Document header, 67
Dangerous goods check in delivery docu- Overview screen, 77
ment, 330 Partners tab, 79
Dangerous goods check in the shipment Schedule Lines tab, 81
document, 340 Shipping tab, 77
Definition, 149, 154 Texts tab, 79
Definition of forwarding agent, 424 Sales order entry
Definition of shipping type, 424 Availability check, 165
Determination of loading time, 182 Sales order number
Determination of transit time, 183 Creating a delivery document, 117
In shipment document, 423 Sales order stock, 165
In the delivery document, 149 Sales organization
Maximum allowed total weight, 424 Assigning to plant, 38
Preliminary, main, and subsequent leg, 424 Definition, 39
Sales order entry, 80 In output type, 358
Time required for picking and packing, 180 Sales order entry, 74
Route determination, 150 SAP workflow, 518
Definition, 156 Scale basis
Example in sales order, 158 Scale, 474
New determination in delivery document, Scale type, 474
151 Scale unit of measure, 475
Transportation zone, 151 Schedule line, 68, 71
Transport group, 152 Schedule line category, 71
Route section, 150 Structure, 71
Route stage, 452 Scheduling
RSNASTED, 515 In delivery document, 178
RV45PFZA, 378 Sea traffic
RV56BPGI, 498 Transit country, 332
RVV50TOP, 130 Section
In a route, 150
Segment
S IDocs, 520
Segment attribute, 521
Safety stock, 163
Segment type, 520
Sales area
Selecting orders due for shipping
Customer master file, 51
Using a variant, 125
Sales document
Selection
Definition, 64
Sales orders due for shipping, 122
Sales group
Selection criteria
Definition, 42
Batch determination, 223
Sales order entry, 75
Creating a delivery document in a collective
Sales office
run, 123
Assigning to sales area, 41
Selection date
Assigning to sales group, 42
Creating a delivery document, 116
Definition, 41
Selection variant

569

5065_BOOK.indb 569 3/7/08 7:55:51 AM


Index

Creating a delivery document in a collective Shipment start


run, 124 In shipment document, 413
Creation, 124 Status in shipment document, 493
Serial number, 225 Shipment type, 388
Entry in the delivery document, 228 In lean WM, 258
Serial number management, 225 Shipping company, 52
Serial number master record, 226 Vendor master file, 56
Serial number profile, 225 Shipping condition
Service agent procedure group, 470, 471 Definition, 144
Setup time, 49 Determination, 144
Shelf life expiration date Per order type, 69
Batch master file, 58 Sales order entry, 78
Shipment Shipping point determination, 144
Output in activity profile, 498 Shipping deadlines
Shipment completion In shipment document, 412
In shipment document, 413, 493 Shipping instructions
Status in shipment document, 493 Sales order entry, 79
Shipment completion type, 391 Text type, 79
Per shipment type, 388 Shipping point, 104
Shipment cost document, 455 Assigning to plant, 31
Create in batch run, 490 As transportation connection point in a
Create manually, 480 route, 150
Via collective processing, 488 Creating a delivery document, 116
Shipment cost document number, 483 Dangerous goods check in delivery docu-
Shipment cost item category, 457 ment, 330
Shipment cost relevance, 460 Determination of time required for picking
Shipment cost settlement, 454 and packing, 180
Status in shipment document, 494 In the delivery document, 142
Shipment cost subitem, 459 Sales order entry, 80
Shipment cost type, 456 Shipping point determination
Shipment creation Delivering plant, 146
In batch job, 401 Example, 148
Logs, 403 Loading group, 145
Shipment document, 383 Shipping condition, 144
Creation via collective processing, 396 Storage location, 148
Exchange within shipments, 411 Shipping scheduling
Header data, 386 In shipment document, 413
Item data, 386 Shipping type, 405
Manual creation, 393 In route, 407
Retroactive delivery split, 543 Sales order entry, 79
Stage, 386 Shipping type procedure group, 470, 471
Shipment end Ship-to party, 52
In shipment document, 413, 493 Dangerous goods check in delivery docu-
Status in shipment document, 493 ment, 330
Shipment processing, 409 Sales order entry, 75
Shipment relevance, 107 SHPADV, 516

570

5065_BOOK.indb 570 3/7/08 7:55:51 AM


Index

SHPCON, 516 Status group


SHPMNT, 516 Incompletion check, 185
SHPORD, 516 Step
Size/dimensions, 46 Pricing procedure, 469
Sold-to party, 52 Stock in transfer, 163
Sales order entry, 75 Stocks
Sort criteria Packaging material, 301
Creation of shipment documents, 398 Stock situation
Sorting In an ATP check, 163
In custom layouts, 130 Stock transport order, 66
Special processing indicator, 407 Creating a delivery document in a collective
Special stock account, 85 run, 130
Special stock partner, 86 Cross-company code, 100
Split profile, 540, 542 Definition, 92, 94
Splitting rule, 542 Delivering plant, 99
SSCC code Shipping tab, 100
Definition, 287 Storage area
SSCC number Definition, 35
Search for, 315 Storage bin
SSCC numbers Definition, 36
Number range, 290 Dynamic, 36
Stackability factor, 290 Storage class
Stage Dangerous goods master file, 60
Create manually, 442 Storage condition
Date and time start/end, 494 Definition, 237
Definition, 440 Material master file, 50
Determine automatically, 447 Storage location
Determine via routes, 451 Assigning to plant, 29
Shipment document, 386 Assignment to lean WM, 255
Staging area, 244, 249 Definition, 28
Definition, 248 Material master file, 49
Determination by route/storage condition, Sales order entry, 80
250 Shipping point determination, 148
Determination by ship-to party/storage Storage location determination, 111
condition, 249 Rule, 236
Standard order Setting, 238
Definition, 74 Storage condition, 237
Start destination Strategies, 236
In a route, 150 User exit, 236
Status Storage type
In delivery header, 372 Definition, 34
In delivery item, 372 In lean WM, 256
Of an IDoc, 524 Storage unit, 36
Reset in shipment document, 493 Storage unit number, 36
Sales document, 65 Storage unit type, 36
Set in shipment document, 493 Strategy scheme
Status FTCn, 206 Batch determination, 209

571

5065_BOOK.indb 571 3/7/08 7:55:51 AM


Index

Strategy type Tolerance limit


Batch determination, 212 Overdelivery and underdelivery, 253
Subitem Unlimited, 253
In the delivery document, 114 Total replenishment lead time, 165
Sales order, 71 Total weight in the delivery document, 297
Subsequent delivery TPS, 428
Free-of-charge, 91 Transaction key
Subsequent leg, 391, 440 BSX, 550
Dangerous goods check in delivery docu- For account determination, 549, 550
ment, 333 Transaction type
Substance properties, 317 In material document, 532
Substance rating Transfer order
Dangerous goods master file, 60 Create, 267
Substances poisonous by inhalation Create by delivery time, 280
Dangerous goods check, 323 create with a shipment, 279
Subtotal Creation for a group, 279
In custom layouts, 130 Creation in the background, 273
Pricing procedure, 470 In lean WM, 267
Superordinate item, 114 Permit manual creation, 259
Supplementary unit, 204 Transfer order confirmation
Availability check, 165
Transit country
T Dangerous goods check in delivery docu-
ment, 330
Tax
Dangerous goods check in shipment docu-
Shipment cost settlement, 465
ment, 340
Text
Transit country table, 330
Customer master file, 56
Definition, 330
In shipment document, 418
Transit time, 180, 183
Text determination procedure, 195
Transmission medium
In shipment document, 419
Output in activity profile, 499
Text determination procedure assignment,
Transport, 104
200
Transportation chain, 390
Text ID
Create via collective processing, 426
In shipment document, 419
Manual creation, 424
Text identification, 194
Retroactive delivery split, 543
Text type, 194
Transportation connection point, 150
Customer master file, 56
Transportation lead time, 180, 183
In the delivery document, 107
Transportation planning, 411
Shipment document, 419
Transportation planning date, 183
Shipping instructions, 79
Transportation planning point, 386
Third-party order
Definition, 32
Definition, 82
Pricing procedure, 470
Time
With TPS, 429
In shipment stage, 494
Transportation planning status, 376, 380
Status in shipment document, 493
In delivery document, 392
Time required for picking and packing, 180
Transportation planning system, 428

572

5065_BOOK.indb 572 3/7/08 7:55:51 AM


Index

Transportation scheduling, 179 USEREXIT_SAVE_DOCUMENT_PREPARE,


Transportation zone, 451 142
Assignment to shipping point, 152 USEREXIT_SET_STATUS_VBUK, 378
Customer master file, 53 USEREXIT_SET_STATUS_VBUP, 378
Definition, 151
For route determination, 151
Per plant, 95 V
Transport connection point, 451
V02V0001, 97
Transport group
V02V0003, 248, 250
Definition, 152
V02V0004, 250
For route determination, 152
V50PPCAT, 273
Material master file, 49
V50PSTAT, 374
Transport relevance, 392
V50Q0001, 381
Transport request
V50R_USEREXITS, 130
Vs. shipment document, 384
V50UC_CHECK_EXAMPLE, 190
WM status, 374
V50UC_CHECK_SLLST, 190
Transport requests, 384
V53W0001, 280
Tree structure
V56BMOD, 388
Pack, 297
V56DISTZ, 443
Tremcards, 343
V56FCOPY, 414
Two-step procedure
V56FSTAT, 500
Stock transport order, 98
V56SLDET, 441
V56USVDO, 395
U V56USVDP, 395
Validity area
Underdelivery Dangerous goods regulations, 318
Definition, 252 Validity area category, 318
In delivery document, 252 Validity period
Unit of measure Condition table, 463
Sales order entry, 75 For a dangerous goods master record, 329,
Unloading point 339
Customer master file, 53 Shipment rates, 467
Sales order entry, 77 Valuation class
Usage profile For account determination, 550
Dangerous goods check, 324 Valuation grouping code
User exit, 105, 106, 121, 130, 142, 190, 248, Account determination, 549
250 Variant
USEREXIT_BATCH_DETERMINATION, 224 Batch job GI posting, 536
USEREXIT_BATCH_QUAN_ALLOCATION, Creation, 124
224 Selecting orders due for shipping, 124
USEREXIT_LGORT_DETERMINATION, 236 Variant name, 124
USEREXIT_LIPS-KOQUI_DETERMINE, 240 Vendor master file, 56
USEREXIT_MOVE_FIELD_TO_LIKP, 142 Vendor master maintenance
USEREXIT_MOVE_FIELD_TO_LIPS, 142 Transaction, 57
USEREXIT_SAVE_DOCUMENT, 142 Versandstellenfindung, 143
Views

573

5065_BOOK.indb 573 3/7/08 7:55:51 AM


Index

Customer master file, 50 Weight unit, 45


Material master file, 44 WM group
VL10BATCH, 134, 137 Retroactive delivery split, 543
Volume WM status, 266, 373
Material master file, 45 Work steps
Volume calculation In shipment document, 491
Per order item category, 70
Volume unit, 45
Z
W Zero quantity Permitted
in the delivery document, 111
Warehouse number ZXKWLU01, 280
Assignment to storage location, 264 ZXKWLU02, 280
Creating for lean WM, 256 ZXKWLU03, 280
Definition, 34 ZXTBFU01, 248
In lean WM, 255 ZXTBFU02, 250
Warning message ZXV50QU01, 381
During save of shipment, 497 ZXV50QU02, 381
Water pollution class ZXV50U07, 273
Dangerous goods master file, 60 ZXV56U10, 395
Wave pick, 274 ZXV56U11, 395
Monitor, 278 ZXV56U13, 441
Number, 274 ZXV56U15, 414
Output determination, 356 ZXV56U16, 500
Weight calculation ZXV56U23, 443
Per order item category, 70 ZXV56U34, 388
Weight group ZXV56U35, 500
Definition, 153 ZXVBFU01, 97
For route determination, 151
Weight scales
For route determination in the delivery doc-
ument, 153

574

5065_BOOK.indb 574 3/7/08 7:55:52 AM

You might also like