EHP5 for SAP ERP
6.0
September 2011
English
Sales Order Processing
with Collective Billing
(205)
Business Process Documentation
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Copyright
© 2011 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components
of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,
OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,
POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System
Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of
IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
Oracle and Java are registered trademarks of Oracle.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C ®, World Wide Web
Consortium, Massachusetts Institute of Technology.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,
SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions,
Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business
Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of
Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its
affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
© SAP AG
Page 2 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths, and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP AG
Page 3 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Contents
1
Purpose ................................................................................................................................... 5
2
Prerequisites............................................................................................................................ 5
2.1
Master Data and Organizational Data .............................................................................. 5
2.2
Business Conditions ......................................................................................................... 7
2.3
Preliminary Steps ............................................................................................................. 7
2.4
Roles ................................................................................................................................ 9
3
Process Overview Table ....................................................................................................... 10
4
Business Processes .............................................................................................................. 11
4.1
Sales Order Entry ........................................................................................................... 11
4.2
Delivery Processing ....................................................................................................... 14
4.3
Picking (Optional) ........................................................................................................... 17
4.4
Checking Batches .......................................................................................................... 18
4.5
Assigning Serial Numbers .............................................................................................. 18
4.6
Posting Goods Issue ...................................................................................................... 20
4.7
Billing .............................................................................................................................. 22
5
Follow-up Processes ............................................................................................................. 23
6
Appendix................................................................................................................................ 24
6.1
Reversal of Process Steps ............................................................................................. 24
6.2
SAP ERP Reports .......................................................................................................... 26
6.3
Used Forms .................................................................................................................... 27
© SAP AG
Page 4 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Sales Order Processing with Collective Billing
1
Purpose
This scenario describes how to use the standard sales processing (sale from stock) for massprocessing.
The process starts with the creation of some standard sales orders.
In periodical intervals all sales orders due to deliver and with availability of the material are
selected and deliveries are created. For optimization of shipping costs all sales orders, which are
delivered to the same customer, are packed into one delivery document. For lean-WM-storage
locations WM-transport orders and picking documents for picking are automatically created.
The materials are picked and the actual amount of picking is noticed in the delivery. The goods
receipts are booked and delivery notes are created. In the background the goods usage is
booked to accounting. The materials can leave the company.
In periodical intervals all deliveries are selected for billing. For cost-optimization all deliveries due
to invoice to the same customer are packed into one invoice-document. In the background the
revenue is posted to accounting.
2
Prerequisites
2.1 Master Data and Organizational Data
SAP Best Practices Standard Values
Essential master and organizational data was created in your ERP system in the implementation
phase, such as the data that reflects the organizational structure of your company and master
data that suits its operational focus, for example, master data for materials, vendors, and
customers.
This master data usually consists of standardized SAP Best Practices default values, and
enables you to go through the process steps of this scenario.
Additional Master Data (Default Values)
You can test the scenario with other SAP Best Practices default values that have the
same characteristics.
Check your SAP ECC system to find out which other material master data exists.
Using Your Own Master Data
You can also use customized values for any material or organizational data for
which you have created master data. For more information on how to create master
data, see the Master Data Procedures documentation.
Use the following master data in the process steps described in this document:
Master /
org. data
Value
Master / Org. data
details
Comments
Material
H11
Trading Good for Reg.
Trading (MRP planning)
See sections Business Conditions
and Preliminary Steps.
© SAP AG
Page 5 of 27
SAP Best Practices
Master /
org. data
Value
Sales Order Processing with Collective Billing (205): BPD
Master / Org. data
details
Comments
no Serial no.; no batch
Material
H12
Trading Good for Reg.
Trading (reorder point
planning)
See sections Business Conditions
and Preliminary Steps.
no Serial no.; no batch
Material
Material
Material
Material
Material
H20
H21
H22
F29
F126
Trading Good for Reg.
Trading (reorder point
planning)
Only use if you have activated the
building block Serial Number
Management (126).
with serial numbers, no
batch
See the sections Business
Conditions and Preliminary Steps.
Trading Good for Reg.
Trading (reorder point
planning)
Only use if you have activated the
building block Batch Management
(117).
no Serial no.; batch
controlled (Exp. Date)
See sections Business Conditions
and Preliminary Steps.
Trading Good for Reg.
Trading (reorder point
planning)
Only use if you have activated the
building block Batch Management
(117).
no Serial no.; batch
controlled (FIFO
strategy)
See sections Business Conditions
and Preliminary Steps.
Finished Good MTS for
Process Industry (PD
planning)
Only use if you have activated the
building block Batch Management
(117).
no Serial no.; with
batch (Exp. Date)
See sections Business Conditions
and Preliminary Steps.
Finished Good MTS for
Discrete Industry (PD
planning)
Only use if you have activated the
building block Serial Number
Management (126).
with Serial no.; with /
w/o batch (FIFO
strategy)
See sections Business Conditions
and Preliminary Steps.
Order combination is switched off in
customer master.
Sold-to
party
100000
Customer domestic 00
Ship-to
party
100000
Customer domestic 00
Payer
100000
Customer domestic 00
Sold-to
party
100002
Customer domestic 02
Ship-to
party
100002
Customer domestic 02
Payer
100002
Customer domestic 02
Plant
1000 (1100)
Storage
1030/1040
© SAP AG
Order combination is switched on in
customer master.
lean WM / w/o lean WM
Page 6 of 27
SAP Best Practices
Master /
org. data
Value
Location
(1130/ 1140)
Sales Order Processing with Collective Billing (205): BPD
Master / Org. data
details
Comments
SalesOrg_V 1000(1100)
001_Sales
Org
Sales
organizatio
n
1000
Distribution
channel
10
Division
10
2.2 Business Conditions
The business process described in this Business Process Documentation is part of a bigger
chain of integrated business processes or scenarios. As a consequence, you must have
completed the following processes and fulfilled the following business conditions before you can
start going through this scenario:
Business condition
Scenario
You have completed all relevant steps described in
the Business Process Documentation Prereq.
Process Steps (154).
Prereq. Process Steps (154)
In order to run through this scenario, the materials
must be available in stock. If you use trading goods
(HAWA) you can either:
Procurement w/o QM (130)

run through the procurement w/o QM (130)
process or

create stock using transaction MIGO (for
details see chapter Preliminary Steps).
In order to run through this scenario, the materials
must be available in stock. If you use finished goods
(FERT) you can either:

run through the Make-to-Stock Production Discrete Industry (145) process (for material
F126) / the Make-to-Stock Production Process Industry (146) process (for material
F29) or

create stock using transaction MIGO (for
details see chapter Preliminary Steps).
Make-to-Stock Production - Discrete
Industry (145) (material F126)
Make-to-Stock Production - Process
Industry (146) (material F29)
2.3 Preliminary Steps
In order to run through this scenario, the materials must be available in stock.
Procedure
1. Access the transaction choosing one of the following navigation options:
© SAP AG
Page 7 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Materials Management  Inventory
Management  Goods Movement  Goods Movement
(MIGO)
Transaction code
MIGO
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role
Warehouse Clerk
(SAP_BPR_WAREHOUSESPECIALIST-S)
Warehouse Management  Receiving  Other Goods
Movement
Business role menu
2. Make the following entries on the MIGO overview screen:
Field name
Description
User action and values
Comment
Business
Transaction
A01 – Goods Receipt
Select A01 – Goods
Receipt from the 1st
Drop-down Menu
Business
Transaction
R10 – Other
Select R10 – Other
from the 2nd Dropdown Menu
Movement Type
561
561 – Receipt per
initial entry of stock
balances into unr.-use
3. Choose Enter.
4. On the Goods Receipt Other screen: Material tab page, make the following entry and choose
Enter:
Field name
Description
Material
User action and values
Comment
<Material number>
5. On the Goods Receipt Other screen: Quantity tab page, make the following entry and
choose Enter:
Field name
Description
User action and values
Comment
10000
Qty in Unit of Entry
6. On the Goods Receipt Other screen: Where tab page, make the following entries and
choose Enter:
Field name
Description
User action and values
Plant
<plant>
Storage Location
<storage location>
Comment
lean WM / w/o lean WM
7. On the Goods Receipt Other screen: Batch tab page, make the following entry and choose
Enter:
Field name
Date of
manufacture
Description
User action and values
Comment
Enter the current date or
a date in the past
Only relevant for material
H22and F29
8. On the Goods Receipt Other screen: Serial Numbers tab page, make the following entry and
choose Enter:
© SAP AG
Page 8 of 27
SAP Best Practices
Field name
Sales Order Processing with Collective Billing (205): BPD
Description
Create Serial
Nos
Automatically
User action and values
Comment

Only relevant for material
H20and F126
9. Choose Enter.
10. Choose Save.
Result
The quantity of 10000 has been posted.
Financial postings:
Material
Debited Accounts
Credited
Accounts
Cost Element / CO Object
Trading
Good
(HAWA)
121100Trading goods
12200 Pening
Bal.(stocjk)
none
Finished
Good
(FERT)
121010
12200 Pening
Bal.(stocjk)
none
Finished goods
2.4 Roles
Use
The following roles must have already been installed to test this scenario in the SAP Netweaver
Business Client (NWBC). The roles in this Business Process Documentation must be assigned
to the user or users testing this scenario. You only need these roles if you are using the NWBC
interface. You do not need these roles if you are using the standard SAP GUI.
Prerequisites
The business roles have been assigned to the user who is testing this scenario.
Business
Role
Technical name
Process step
Sales
Administration
SAP_BPR_SALESPERSON-S
Sales Order Entry
Warehouse
Clerk
SAP_BPR_WAREHOUSESPECIALISTS
Delivery Creation
Warehouse
Clerk
SAP_BPR_WAREHOUSESPECIALISTS
Picking (optional)
Warehouse
Clerk
SAP_BPR_WAREHOUSESPECIALISTS
Check Batches
Warehouse
Clerk
SAP_BPR_WAREHOUSESPECIALISTS
Assign Serial Numbers
Warehouse
Clerk
SAP_BPR_WAREHOUSESPECIALISTS
Post Goods Issue
Sales Billing
SAP_BPR_SALESPERSON-S2
Billing
Employee
SAP_BPR_EMPLOYEE-S
Assignment of this role is only
necessary if you want to print the
© SAP AG
Page 9 of 27
SAP Best Practices
Business
Role
Sales Order Processing with Collective Billing (205): BPD
Technical name
Process step
invoice via the system icon Print
Invoice.
Automatic printing is possible
without assignment of this role.
(Professional
User)
3
Process Overview Table
As in this process the mass processing and merge of separate customer orders to one delivery
per customer and the merge of several deliveries to one invoice per customer should be shown,
several customer orders are needed.
Overview of the process:
Customer Order
Delivery
Invoice
Order 1 from Customer
100000 with Material 1
Delivery 1 to customer 100000
Invoice 1 to customer
100000
Order 2 from Customer
100000 with Material 1
Delivery 2 to customer 100000
Order 1 from Customer
100002 with Material 1
Delivery 3 to customer 100002
Invoice 2 to customer
100002
Order 4 from Customer
100002 with Material 1
For customer 100002 the sign Order Combination (sales area data) is switched on. Therefore
several customer orders from this customer are merged into one delivery, when you create them
with Collective Processing of Documents Due for Delivery. Customer 100000 has not switched
on this sign and so he will get separate deliveries.
By creating the invoices via the mass-process Billing Due List, all deliveries for one customer are
listed in one invoice for the customer.
Process step
Business
condition
Business
role
Transaction
code
Expected
results
Sales Order
Entry 1
Customer
request for
material
Sales
Administration
VA01
Order 1 from
customer
100000 with
material 1.
Sales Order
Entry 2
Customer
request for
material
Sales
Administration
VA01
Order 2 from
customer
100000 with
material 1.
Sales Order
Entry 3
Customer
request for
material
Sales
Administration
VA01
Order 3 from
customer
100002 with
material 1.
Sales Order
Entry 4
Customer
request for
material
Sales
Administration
VA01
Order 4 from
customer
100002 with
material 1.
Warehouse
VL10C
Delivery is
created. The
Delivery
Creation via
© SAP AG
External
process
reference
Page 10 of 27
SAP Best Practices
Process step
Sales Order Processing with Collective Billing (205): BPD
External
process
reference
Business
condition
Business
role
Transaction
code
Expected
results
Collective
Processing of
Documents Due
for Delivery
Clerk
Picking
(optional)
Warehouse
Clerk
VL06O
Material is
picked
Check Batches
Warehouse
Clerk
VL02N
Batches are
assigned
Assign Serial
Numbers
Warehouse
Clerk
VL02N
Serial Number
s are assigned
Post Goods
Issue
Warehouse
Clerk
VL06O
The goods
issue is posted.
Sales Billing
VF04
Billing is
created
Accounts
Receivable
See
scenario
no. 157
See scenario no.
157
See
scenario
no. 203
See scenario no.
203
(optional)
Billing
Material
shipped
invoice
required
Incoming
Payment
Accounts
Receivable
(157)
Sales: Period End
Closing
Operations
Sales:
Period End
Closing
Operations
(203)
4
Warehouse
Transfer Order
is created for
lean-WM stor.
locations.
Business Processes
4.1 Sales Order Entry
Use
In this activity, you enter four sales orders according to the table Overview of the process in
chapter 3 .
Prerequisites
None
Procedure
Execute following steps for each of the four customer orders.
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
© SAP AG
Logistics → Sales and Distribution → Sales → Order →
Create
Page 11 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Transaction code
VA01
If you have installed the scenario Rebate Processing: Free Goods in your system and
you use material H11the following warning may appear: Minimum quantity 1.000 PC of
free goods has not been reached Choose Enter to skip this warning.
If you do not want to use Lean Warehouse Management (WM), choose a storage
location Shipping w/o Lean WM (for example, «StorLoc_V004_StorLoc») by using the
following path: Goto  Item  Shipping. Enter the selected storage location (for
example, 1040) in field Stor. Location.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role
Sales Administration
(SAP_BPR_SALESPERSON-S)
Business role menu
Sales  Sales Orders  Create Sales Order
2. Enter the Order type OR and choose Enter. (You can optionally enter organizational data)
3. Make the following entries:
Field name
Description
Sold to party
User action and values
Comment
100000 or 100002
See table Overview of the
process in chapter 3 .
Remark: Only for
customer 100002 the sign
Order Combination is
switched on.
100000 or 100002
Ship to party
PO number
See table Overview of the
process in chapter 3 .
Enter an customer
purchase order number as
reference
Material
Number
<Material number>
Quantity
1 each
4. Choose Save.
Option 3: Lean order SAP NetWeaver Business Client (SAP NWBC) via business role
Business role
Sales Administration
(SAP_BPR_SALESPERSON-S)
Business role menu
Sales  Sales Orders  Create Sales Order (Lean Order)
1. On the Create Sales Order (Lean Order) screen, make the following entries, and choose
Enter:
Field name
© SAP AG
Description
User action and values
Comment
Page 12 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Transaction
Type
Create
SD Document
categ.:
Order
Sales
Document type
OR
Standard order
2. Choose Start Transaction.
3. On the Create Standard Order screen, enter the following data, and choose Enter:
Field name
Sold to party
Description
User action and values
Comment
100000 or 100002
See table Overview of the
process in chapter 3 .
Remark: Only for
customer 100002 the sign
Order Combination is
switched on.
Ship to party
100000 or 100002
PO number
See table Overview of the
process in chapter 3 .
Enter a customer
purchase order number
as reference
Material
Number
<Material number>
Quantity
1 each
Delivery Date
Actual date
See table Overview of the
process in chapter 3 .
If you do not want to use Lean Warehouse Management (WM), choose a storage
location Shipping w/o Lean WM (for example, StorLoc_V004_StorLoc). You have to
enter this storage location in the column Stor. Location for each item.
If you have maintained more than 1 partner for one role (for example, ship-to party).
The default partner will be used.
If you have maintained Material Substitution the Material is substituted without
displaying a dialog box.
4. Choose Save.
Result
The two sales orders for customer 100000 and two for 100002 are saved and the order
confirmations are printed.
The printout of the order confirmation is executed automatically and immediately
(see settings in SAP GUI transaction VV11 for output type BA00 and defaults in
your user settings in transaction SU3).
© SAP AG
Page 13 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
You have also the possibility to start the print out manually:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Sales and Distribution  Sales  Order 
Display
Transaction code
VA03
1. Enter the order number in the screen Display Sales Order: Initial Screen: From the menu
choose Sales Document  Issue Output To
2. Mark the line with the message type BA00
3. Choose Print.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role
Sales Administration
(SAP_BPR_SALESPERSON-S)
Business role menu
Sales Sales Orders
1. Choose All Sales Orders tab page (refresh the current query if necessary).
2. Mark your sales order and choose Display.
3. From the menu choose More…  Extras  Output  Header  Print Preview
4. Choose More…  Text  Print
4.2 Delivery Processing
Use
In this activity you create the deliveries in a collective run for sales orders, which are due to
deliver and for which the material is available.
Prerequisites
None
Procedure
1.
Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
2.
SAP ECC menu
Logistics  Logistic Execution  Outbound Process 
Goods Issue for Outbound Delivery  Outbound Delivery
 Create  Collective Processing of Documents Due for
Delivery  Sales Order Items
Transaction code
VL10C
Make the following entries:
Field name
Description
User action and values
Shipping point
1000
Delivery creation
dates (From)
<actual date>
© SAP AG
Comment
Use this and the next
field together, or use
the Calc rule. Do not do
Page 14 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
both.
Delivery creation
dates (To)
< actual date + 2 days>
Use this and the last
field together, or use
the Calc rule. Do not do
both.
Calc Rule
<2>
Use this field, or use
the last two fields
together. Do not do
both.
3.
Choose Execute.
4.
Select the line item(s) and choose Background.
5.
Select the entry with the green light and choose Details.
6.
7.
Select the line with the green light and choose Details. In the dialog box you see the delivery
numbers, which have been created.
Note down the delivery numbers: ______________________________.
At delivery creation, the scenario-settings for check availability is using available
inventory and replenishment lead time. Without sufficient stock, the created delivery
has no confirmed quantities therefore it dose not start the warehouse
management picking process. As soon as there is sufficient stock at delivery
creation, the system creates a delivery with further picking process in warehouse
management.
If you want to avoid open deliveries, ensure that there is sufficient inventory quantity at delivery
creation. Additionally you have the following options to restrict the creation of deliveries with no
confirmed quantities.
- You may increase replenishment lead time, which is used during the availability check (has to
be larger than the selection period used for delivery creation).
- You may change the customizing settings for the incompleteness procedure for delivery
creation, so that only complete deliveries may be saved
- You may change the customizing settings for the used delivery-item-category. The field Check
quantity 0 has to be adapted to B = Situation rejected with an error message.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role
Warehouse Clerk
(SAP_BPR_WAREHOUSESPECIALIST-S)
Warehouse Management  Shipping
Business role menu
1.
On the All Sales Order Sales Due for Delivery tab page, make the following entries:
Field name
Description
Shipping point
2.
User action and values
Comment
1000
Choose change query. New you can define the delivery creation date for the delivery
selection.
Field name
Deliv. Creation Date
© SAP AG
Description
User action and values
Comment
<actual day>
Use this and the
next field together,
Page 15 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
(From)
or use the Calc rule.
Do not do both.
Deliv. Creation Date (To)
<actual day + 2 days>
Use this and the
next field together,
or use the Calc rule.
Do not do both.
Deliv. Creation Date
(Calculation Rule)
<Calculation Rule>
Use this and the
next field together,
or use the Calc rule.
Do not do both.
3.
Choose Apply.
4.
Select your order you created in the previous process steps.
5.
Choose Create Delivery.
6.
You can see message: Delivery <delivery number> created.
Result
Three deliveries are created. As for customer 100002 the sign Order Combination is switched
on, several sales orders for this customer are merged together into one delivery. As this sign is
not set for customer 100000, you receive separate deliveries.
The cost of shipping is decreased, because you will need less separate transports.
Batches are automatically determined if batch management is activated.
In case of lean warehouse management, the transfer order is created, printed and automatically
confirmed.
The print-out of the transfer order is executed automatically and immediately. This
printout is used for picking.
You have also the possibility to start the print-out manually:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics Logistics Execution  Outbound Process 
Goods Issue for Outbound Delivery  Communication /
Printing  Single Print Pick Document
Transaction code
LT31
1.
Enter the Warehouse Number and transfer order number (you can find this number using
transaction VL02N and checking the document flow) and choose Enter.
2.
To start the print process, choose Transfer order  Print.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role
Warehouse Clerk
(SAP_BPR_WAREHOUSESPECIALIST-S)
Business role menu
© SAP AG
Warehouse Management  Shipping  Print TO manually
Page 16 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
1.
Enter the Warehouse Number and transfer order number (you can find TO number using
Business role menu Warehouse Management  Shipping  Display Outbound Delivery
and checking the document flow of your outbound delivery) and choose Enter.
2.
To start the print process, choose from the menu More Transfer order 
Print
4.3 Picking (Optional)
Use
The picking process involves taking goods from a storage location and staging the right quantity
in a picking area where the goods will be prepared for shipping.
Prerequisites
This step is to be used if lean WM has not been activated.
Procedure
1.
Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Sales and Distribution  Shipping and
Transportation  Outbound Delivery  Lists and Logs 
Outbound Delivery Monitor
Transaction code
VL06O
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role
Warehouse Clerk
(SAP_BPR_WAREHOUSESPECIALIST-S)
Business role menu
Warehouse management  Shipping  Outbound
Delivery Monitor
1.
On the Outbound Delivery Monitor screen choose For Picking.
2.
On the Outbound Deliveries for Picking screen, make the following entry:
Field name
Shipping
point
Description
User action and values
Comment
<shipping point>
3.
Choose Only Picking without WM checkbox.
4.
Choose Execute.
5.
Select your delivery note and choose (NWBC: More… ) Subsequent Functions  Picking
Output.
6.
On the Output from Picking screen, select your delivery note and choose Execute.
Result
The picking list EK00 has been printed and the picking quantity at delivery item level has been
updated with the requested delivery quantity.
© SAP AG
Page 17 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
4.4 Checking Batches
Use
In this activity you check the batch numbers assignment to the materials.
Prerequisites
This step is to be used if batch management is activated.
Procedure
Option 1: SAP Graphical User Interface (SAP GUI)
1. Access the transaction choosing one of the following navigation options:
SAP ECC menu
Logistics  Sales and Distribution  Shipping and
Transportation  Outbound Delivery  Change  Single
Document
Transaction code
VL02N
2. On the Change Outbound Delivery screen enter the outbound delivery number and choose
Enter.
3. In the Batch Split Indicator column, choose Batch Split Exits.
4. In the Batch field, check the batch number assignment.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
1. Access the transaction as follows:
Business role
Warehouse Clerk
(SAP_BPR_WAREHOUSESPECIALIST-S)
Business role menu
Warehouse management  Shipping
2. Select the tab page All Deliveries Due to Post Goods Issue.
3. Enter the Shipping Point / Receiving Pt: and choose Apply.
4. Select your Delivery.
5. Choose Change.
6. In the Batch Split Indicator column, choose Batch Split Exits.
7. In the Batch field, check the batch number assignment.
Result
Batch numbers are assigned to the items of the delivery.
4.5 Assigning Serial Numbers
Use
In this activity you assign serial numbers to the materials.
© SAP AG
Page 18 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Prerequisites
This step is to be used if serial number management is activated.
Procedure
Option 1: SAP Graphical User Interface (SAP GUI)
1. Access the transaction choosing one of the following navigation options:
SAP ECC menu
Logistics  Sales and Distribution  Shipping and
Transportation  Outbound Delivery  Change  Single
Document
Transaction code
VL02N
2. On the Change Outbound Delivery screen enter the outbound delivery number, and choose
Enter.
3. Select the material to which you need to assign a serial number, and choose Batch Split (for
example, Material F126). If the material is not batch controlled (H20) choose Item Details
instead of Batch Split.
4. On the Delivery XXX Change: Item Details screen, select the batch you need to assign a
serial number and choose Extras  Serial Numbers. If the material is not batch controlled
(H20) choose Extras  Serial Numbers.
5. In the Maintain Serial Numbers dialog box select the serial number from the input help. For
testing purposes, choose a serial number from the selection list that has a plant and a
storage location assigned to it. Make sure that the serial number comes from the batch
determined in step 4.5 in case the material is batch controlled (for example, F126).
6. Choose Save.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
1. Access the transaction choosing one of the following navigation options:
Business role
Warehouse Clerk
(SAP_BPR_WAREHOUSESPECIALIST-S)
Business role menu
Warehouse management  Shipping
2. Choose the tab page All Deliveries Due to Post Goods Issue.
3. Enter the Shipping Point / Receiving Pt: and choose Apply.
4. Select your Delivery.
5. Choose Change.
6. Select the material to which you need to assign a serial number, and choose Batch Split (for
example,Material F126). If the material is not batch controlled (H20) choose Item Details
instead of Batch Split.
7. On the Delivery XXX Change: Item Details screen, select the batch you need to assign a
serial number and choose More…  Extras  Serial Numbers. If the material is not batch
controlled (H20) choose More…  Extras  Serial Numbers.
8. In the Maintain Serial Numbers dialog box select the serial number from the input help. For
testing purposes, choose a serial number from the selection list that has a plant and a
© SAP AG
Page 19 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
storage location assigned to it. Make sure that the serial number comes from the batch
determined in step 4.5 in case the material is batch controlled (for example,F126).
9. Choose Save.
Result
Serial numbers are assigned to the items of the delivery.
4.6 Posting Goods Issue
Use
In this activity, you post the goods issue.
Prerequisites
None
Procedure
Option 1: SAP Graphical User Interface (SAP GUI)
1. Access the transaction choosing one of the following navigation options:
SAP ECC menu
Logistics  Logistics Execution  Outbound Process 
Goods Issue for Outbound Delivery  Outbound Delivery
 Lists and Logs  Outbound Delivery Monitor
Transaction code
VL06O
2. Choose For Goods Issue.
3. Make the following entries:
Field name
Description
Shipping point
User action and values
Comment
<shipping point>
4. Choose F8.
5. Mark the relevant delivery.
6. Choose the Post Goods Issue.
7. Choose today’s date and select continue in the dialog box.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
1. Access the transaction choosing one of the following navigation options:
Business role
Warehouse Clerk
(SAP_BPR_WAREHOUSESPECIALIST-S)
Business role menu
Warehouse management  Shipping
2. Choose the tab page All Deliveries Due to Post Goods Issue.
3. Enter the Shipping Point / Receiving Pt: and choose Apply.
4. Select your Delivery.
© SAP AG
Page 20 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
5. Choose Post Goods Issue.
6. The number of the created material document is displayed.
Result
The goods issue is posted.
FI account example:
Material
Debited Accounts
Credited
Accounts
Cost Element / CO Object
Trading Good
(HAWA)
500701 COS
121100 Trading
goods
none
Finished Good
(FERT)
524000 Inv.chg.sale
own prd
121010
none
Finished goods
Delivery Note
The printout of the delivery note is executed automatically and immediately (see settings
in SAP GUI transaction VV23 for output type LD00 and defaults in your user settings in
transaction SU3).
You can also start the printout manually:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Logistics Execution  Outbound Process 
Goods Issue for Outbound Delivery  Outbound Delivery
 Display
Transaction code
VL03N
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role
Warehouse Clerk
(SAP_BPR_WAREHOUSESPECIALIST-S)
Business role menu
Warehouse Management  Shipping  Display Outbound
Delivery
1. Enter your outbound delivery on the Display Outbound Delivery screen and choose from
the menu (NWBC: More…) Outbound Delivery  Issue delivery Output
2. Mark the line with the message type LD00 – Delivery Note
3. Choose Print.
Bill of Lading
The printout of the bill of loading is executed automatically and immediately (see settings
in SAP GUI transaction VV23 for output type YBL1 and defaults in your user settings in
transaction SU3).
You have also the possibility to start the print-out manually:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
© SAP AG
Logistics  Logistics Execution  Outbound Process 
Page 21 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Goods Issue for Outbound Delivery  Outbound Delivery
 Display
Transaction code
VL03N
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role
Warehouse Clerk
(SAP_BPR_WAREHOUSESPECIALIST-S)
Business role menu
Warehouse Management  Shipping  Display
Outbound Delivery
1. Enter your outbound delivery on the Display Outbound Delivery screen and choose from
the menu (NWBC: More… ) Outbound Delivery  Issue delivery Output
2. Mark the line with the message type YBL1 – Bill of Lading
3. Choose Print.
4.7 Billing
Use
In this activity you handle the billing.
Prerequisites
None
Procedure
Option 1: SAP Graphical User Interface (SAP GUI)
1. Access the transaction choosing one of the following navigation options:
SAP ECC menu
Logistics  Sales and Distribution  Billing  Billing
Document  Process Billing Due List
Transaction code
VF04
2. Enter relevant search criteria, select the delivery-related flag and deselect the Order-related
flag and choose DisplayBillList (F8).
3. Select the relevant rows and choose Collective Billing Document.
4. Choose Save.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
1. Access the transaction choosing one of the following navigation options:
Business role
Sales Billing
(SAP_BPR_SALESPERSON-S2)
Business role menu
Sales  Billing
2. On the Billing screen, choose the tab All Sales Documents Due for Billing.
3. Mark the lines with the sales documents, which you want to bill and choose Collective Billing.
4. The system will provide you with a list of the created billing documents.
© SAP AG
Page 22 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Result
The system generates an invoice for billing for each customer. Several deliveries for one
customer are listed in one invoice for this customer. The costs for invoicing are decreased
because you need less separate invoices.
Material
Debited Accounts
Credited
Accounts
Cost Element / CO Object
Trading Good
(HAWA)
100000 Customer
domestic 00
400000 Sales
revenue dom.
235000 Output tax
none
Finished Good
(FERT)
100000 Customer
domestic 00
400000 Sales
revenue dom.
235000 Output tax
none
The printout of the invoice is executed automatically and immediately (see
settings in SAP GUI transaction VV33 for output type RD00 and defaults in your
user settings in transaction SU3).
You have also the possibility to start the printout manually:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Sales and distribution  Billing  Billing
document  Display
Transaction code
VF03
1. Go to transaction VF03, on the Display Billing Document: screen. From the menu choose
Billing document  Issue Output to
2. Mark the line with the message type RD00.
3. Choose Print.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role
Sales Billing
(SAP_BPR_SALESPERSON-S2)
Business role menu
Sales  Billing
1. Choose Change Billing Document.
2. Enter the billing document number.
3. Choose More …  Billing Document  Issue Output to.
4. Select the relevant Output and choose Print.
5 Follow-up Processes
You have finished all activities that are part of the business process described in this document.
To accomplish subsequent activities of this business process, carry out the process steps
described in one or more of the following scenarios, using the master data from this document.
Accounts Receivable (157)
© SAP AG
Page 23 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Use
In this activity you post the incoming payment.
Procedure
Complete all activities described in the Business Process Documentation of the scenario:
Accounts Receivable (157) (Chapters Post Payments using Automatic Payments Program, Post
Incoming Payment from Customer Manually, Automatic Clearing of open items in customer
accounts, Manual Clearing of Open items in customer accounts) using the master data from this
document.
Sales: Period End Closing Operations (203) (optional)
Use
This scenario describes the collection of periodic activities such as day ending activities or legal
requirements like Intrastat and Extrastat reporting.
Procedure
Complete all activities described in the Business Process Documentation of the scenario: Sales:
Period End Closing Operations (203) (Chapters Review Sales Documents blocked for billing,
Review Billing Due List, Review Log of collective invoice creation and Review List Blocked (for
accounting) Billing Documents) using the master data from this document.
6
Appendix
6.1 Reversal of Process Steps
In the following section, you can find the most common reversal steps, which you can take to
reverse some of the activities described in this document.
Sales Order Entry
Transaction code ( SAP GUI)
VA01
Reversal:
Delete Sales Document
Transaction code ( SAP GUI)
VA02
Business role
Sales Administration
Business role menu
Sales Sales Orders
Choose All Sales Orders tab page.
Mark your sales order and choose Change.
Comment
© SAP AG
Select menu Sales Document  Delete
Page 24 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Delivery Process
Transaction code ( SAP GUI)
VL10C
Reversal:
Delete Delivery
Transaction code ( SAP GUI)
VL02N
Business role
Warehouse Clerk
Business role menu
Warehouse management  Shipping
Choose All Deliveries tab page.
Mark your delivery and choose Change.
Comment
Select menu Outbound Delivery  Delete
Check Batches
Transaction code ( SAP GUI)
VL02N
Reversal:
Edit Batch Number
Transaction code ( SAP GUI)
VL02N
Business role
Warehouse Clerk
Business role menu
Warehouse management  Shipping  Display
Outbound Delivery
Comment
Assign Serial Number
Transaction code ( SAP GUI)
VL02N
Reversal:
Edit Serial Number
Transaction code ( SAP GUI)
VL02N
Business role
Warehouse Clerk
Business role menu
Warehouse management  Shipping
Choose All Deliveries tab page.
Mark your delivery and choose Change.
Comment
© SAP AG
Page 25 of 27
SAP Best Practices
Sales Order Processing with Collective Billing (205): BPD
Picking
Transaction code ( SAP GUI)
VL06O
Reversal:
Remove Picking Quantity from Delivery Item
Transaction code ( SAP GUI)
VL02N
Business role
Warehouse Clerk
Business role menu
Warehouse management  Shipping
Choose All Deliveries tab page.
Mark your delivery and choose Change.
Comment
Post Goods Issue
Transaction code ( SAP GUI)
VL02N
Reversal:
Reverse Goods Issue.
Transaction code ( SAP GUI)
VL09
Business role
Warehouse Clerk
Business role menu
Warehouse management  Shipping  Cancel
Goods Issue for Delivery Note
Comment
Billing
Transaction code ( SAP GUI)
VF04
Reversal:
Cancel Billing document
Transaction code ( SAP GUI)
VF11
Business role
Sales Billing
Business role menu
Sales  Billing  Change Billing Document
Comment
Go to transaction VF11, enter the relevant billing
document number, choose Enter and save your result. An
invoice cancellation document has been created
balancing the original invoice.
6.2 SAP ERP Reports
Use
The table below lists the reports that you can use to obtain additional information on this
business process.
You can find detailed descriptions of the individual reports in the following BPD
documents, which provide a comprehensive compilation of all important reports:

© SAP AG
Financial Accounting: SAP ERP Reports for Accounting (221)
Page 26 of 27
SAP Best Practices

Sales Order Processing with Collective Billing (205): BPD
Logistics Processes: SAP ERP Reports for Logistics (222)
Note that the descriptions of some reports that are an indispensable part of the process flow may
be located directly in the section where they belong.
Reports
Report title
Transaction
code ( SAP GUI)
Comment
List of Sales Orders
VA05
A list of all selected sales orders is
displayed.
List Billing Documents
VF05
A list of all selected billing documents is
displayed.
Orders within Time Period
SD01
A list of sales orders within a specific time
period
Incomplete SD
Documents
V.02
A list of all incomplete documents on the
basis of the specified selection criteria is
displayed.
Outbound delivery monitor
VL06O
Monitor for collective processing of deliveries
and for obtaining information on general
shipping processing.
6.3 Used Forms
Common form
name
Form type
Used in
process step
Output Type
Technical name
Order
Confirmation
SmartForm
Sales Order
Entry
BA00
YBAA_SDORC
Delivery Note
SmartForm
Post Goods
Issue
LD00
YBAA_SDDLN
Transfer Order
SAP Script
Delivery Due
List
Pick List SD
SAP Script
Picking
(optional)
EK00
YB_SD_PICK_SINGL
Bill of Lading
SmartForm
Post Goods
Issue
YBL1
YBAA_SDBLD
Sales Invoice
SmartForm
Billing
RD00
YBAA_SDINV
© SAP AG
YB_LVSTAEINZEL
Page 27 of 27