Organizational Structures in Logistics 2
Organizational Structures in Logistics 2
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.
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.
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
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).
Company Code
Loading Point
Events
Transportation
Planning Point M
Transportation
Planning Point Z
24
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.
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
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).
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
recommends generally creating a separate company code for each plant with a
different country key.
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.
27
28
29
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.
Figure 2.6 Defining the Shipping Point with All Control Parameters
30
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.
31
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.
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.
32
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.
Warehouse Number
Interim Interim
Storage Area Storage Area
Goods Goods Issue
Receipt
33
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.
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
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.
Figure 2.11 Some Preconfigured Storage Types in the Standard SAP System
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
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.
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
Figure 2.12 Storage Unit Types Predefined in the Standard SAP System
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
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.
Division AC Division AC
Division AB Division AB
38
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.).
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
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:
40
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.
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.
41
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.
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
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
558
559
560
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
562
563
564
565
566
567
568
569
570
571
572
573
574