©
© SAP SAP AG AG IRT340 IRT340 0-10-1
SAP AG 2003SAP AG 2003
IRT340 Supply Chain
IRT340 Supply Chain
Executio
Executio
n
n
FS310 Inkasso/Exkasso
FS310 Inkasso/Exkasso
THE BEST RUN BUSINESSES RUN SAP
THE BEST RUN BUSINESSES RUN SAP
©
© S AS AP AP AG 2G 20 00 033
Supply Chain Execution
Supply Chain Execution
R/3 SystemR/3 System
Release 4.7 / SAP RetailRelease 4.7 / SAP Retail
Col.33Col.33
5006234350062343
C
C
ContContact for Bact for Buyinuying Any Sg Any SAP ModAP Module Mule Materiaaterials: sapls: sapallmaallmaterialterials@gmas@gmail.coil.com m VisitVisit: www.: www.sapfasapfans.cons.co.nr.nrIRT 340
©
© SAP SAP AG AG IRT340 IRT340 0-20-2
SAP AG 2003SAP AG 2003
Copyright 2003
Copyright 2003 SAP AG.
SAP AG. All rights
All rights reserved.
reserved.
No part of this publication may be reproduced or transmitted in
No part of this publication may be reproduced or transmitted in
any form or for any
any form or for any purpose without
purpose without the expres
the express permission of
s permission of
SAP AG. The information contained herein may be changed
SAP AG. The information contained herein may be changed
without prior notice.
without prior notice.
All rights reserved.
All rights reserved.
Copyright
Copyright
Trademarks: Trademarks:
Some software products marketed by SAP Some software products marketed by SAP AG and its distributors contain proprietary softwareAG and its distributors contain proprietary software
components of other software
components of other software vendors.vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registeredregistered
trademarks of Microsoft Corporation. trademarks of Microsoft Corporation.
IBM®, DB2®, DB2 Universal Database, OS/2®, IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®,Parallel Sysplex®, MVS/ESA, AIX®, S/390®,
AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS,
AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,AFP, Intelligent Miner,
WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
Corporation in USA and/or other countries.
ORACLE® is a registered trademark of ORACLE® is a registered trademark of ORACLE Corporation.ORACLE Corporation.
UNIX®, X/Open®, OSF/1®, and Motif® are UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.registered trademarks of the Open Group.
Citrix®, the Citrix logo, ICA®, Program Citrix®, the Citrix logo, ICA®, Program Neighborhood®Neighborhood®, MetaFrame®, WinFrame®, , MetaFrame®, WinFrame®, VideoFrame®,VideoFrame®,
MultiWin® and other Citrix product names referenced herein are
MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide WebHTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of
Consortium, Massachusetts Institute of Technology.Technology.
JAVA® is a registered trademark of JAVA® is a registered trademark of Sun Microsystems, Inc.Sun Microsystems, Inc.
JAVASCRIPT® is a registered trademark of JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for Sun Microsystems, Inc., used under license for technologytechnology
invented and implemented by Netscape. invented and implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned hereinproducts and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the
several other countries all over the world. All other product and service names mentioned are world. All other product and service names mentioned are thethe trademarks of their respective companies.
trademarks of their respective companies.
C
SAP AG 1999SAP AG 1999
Required:
Required:
IRT100 Retail Process Overview
IRT100 Retail Process Overview
IRT310 Retail Master Data
IRT310 Retail Master Data
Course Prerequisites
©
© SAP SAP AG AG IRT340 IRT340 0-40-4
SAP AG 1999SAP AG 1999
Target Group
Target Group
Participants
Participants
::
Members of project teams and consultants responsible
Members of project teams and consultants responsible
for configuring supply chain management processes for a
for configuring supply chain management processes for a
distribution center
distribution center
Duration: 3 days
Duration: 3 days
User notes User notes
These training materials areThese training materials are not a teach-yourself programnot a teach-yourself program. They. They compliment the explanationscompliment the explanations
provided by your course instructor
provided by your course instructor. Space is provided on each page for you to note down additional. Space is provided on each page for you to note down additional information.
information.
There may not be There may not be sufficient time during the course to complete all the sufficient time during the course to complete all the exercises. The exercises provideexercises. The exercises provide
additional examples that are covered during the course. You
additional examples that are covered during the course. You can also work through the examples in can also work through the examples in youryour own time to increase your understanding of the
own time to increase your understanding of the topic.topic.
C
SAP AG 2003SAP AG 2003
Course Goals
Course Goals
Course Objectives
Course Objectives
Course Content
Course Content
Course Overview Diagram
Course Overview Diagram
Main Business Scenario
Main Business Scenario
Contents:
Contents:
Course Overview
© SAP AG IRT340 1-2 SAP AG 2003
This course will prepare you to:
Set up the processes for supply chain execution
in a distribution center that does not have a
separate warehouse management system
Course Goals
SAP AG 2003
At the conclusion of this course, you will be able to:
Carry out the goods receipt and goods issue
processes, explain inventory management, and
name the special features of merchandise
distribution
Set up the necessary master data and make the
necessary settings in Customizing
Create a number of variants of these processes to
meet your individual requirements
© SAP AG IRT340 1-4 SAP AG 2003
Unit 5
Goods Issue Process
Unit 6
Merchandise
Distribution
Unit 7
Conclusion
Unit 1
Course Overview
Unit 2
Basic Concepts
Unit 3
Goods Receipt Process
Unit 4
Inventory Management
Preface
Course Content
SAP AG 2003
Basic Concepts
Goods Receipt Process
Inventory Management
Goods Issue Process
Conclusion
7
6
5
4
3
2
Course Overview
1
Course Overview
Merchandise Distribution
© SAP AG IRT340 1-6 SAP AG 2003
Your company has decided to implement SAP
Retail and you are responsible for optimizing
warehouse processes
Main Business Scenario
SAP AG 2003
Master data and organizational units
Contents:
Basic Concepts
© SAP AG IRT340 2-2 SAP AG 2003
Describe the structure of a distribution center in
the SAP Retail system
List the various differences in warehouse
structures
At the conclusion of this unit, you will be able to:
Basic Concepts: Unit Objectives
SAP AG 2003
Course Overview
Goods Receipt Process
Inventory Management
Goods Issue Process
Merchandise Distribution
Summary
7
6
5
4
3
1
Basic Concepts
2
Course Overview
© SAP AG IRT340 2-4 SAP AG 2003 Site Address Organizational data Merchandise categories Departments Staging area Receiving points ...
Storage location (Customizing)
Customer Customer Vendor Vendor Distribution Center Distribution Center
The Structure of a Distribution Center
SAP AG 2003
Site
Site
Site
Storage
location
Storage
Storage
location
location
Warehouse number
Warehouse number
Warehouse number
MM
Warehouse New York
Store. loc.0001 Store. loc.0002
088
Stock
WM
042
Store. loc.0003
© SAP AG IRT340 2-6 SAP AG 2003
Site
Site
Site
Storage loc.
Storage
Storage loc
loc ..
Warehouse no.
Warehouse no.
Warehouse no.
MM
Storage type
Door
Staging area
Storage type
Storage type
Door
Door
Staging area
Staging area
Areas
(optional)Areas
Areas
(optional) (optional) Warehouse: New York 088 Door 1 Door 2 Zone A 360 Hall 4 Stock Aisle 2WM
Aisle 1 042 902 Storage loc. 0001 Storage loc. 0002 Storage loc. 0003Structures in the Warehouse
If stocks are to be managed at storage bin level within a storage location in a distribution center (or site),
you can use the SAP Warehouse Management (WM) function. To do so, you must assign a warehouse number to the relevant storage location. This represents the entire warehouse structure.
Storage locations that have different technical or organizational requirements have different storage
types in the warehouse numbers. For example: GR zone = storage type 902, high rack storage section, bulk storage, GI zone = storage type 910. To make goods receipt processing and picking easier, you can
define multiple doors and staging areas below a warehouse number.
You can also choose to group neighboring areas within the same storage type. If you choose to make this
grouping on a goods receipts basis , we refer to storage sections. If grouping is created on a picking basis, we refer to picking areas.
SAP AG 2003
Site
Site
Site
Storage loc.
Storage
Storage loc
loc ..
Warehouse no.
Warehouse no.
Warehouse no.
MM
Storage type
Door
Staging area
Storage type
Storage type
Door
Door
Staging area
Staging area
Storage bin
Storage bin
Storage bin
Areas
(optional)Areas
Areas
(optional) (optional) Warehouse: New York 088 ... Door 1 Door 2 Zone A 360 Hall 4 Stock 12-6-54 4-23-89 Aisle 2WM
Aisle 1 042 902 Storage loc. 0001 Storage loc. 0002 Storage loc. 0003 StockStructures in the Warehouse
If stocks are to be managed at storage bin level within a storage location in a distribution center (or site),
you can use the SAP Warehouse Management (WM) function. To do so, you must assign a warehouse number to the relevant storage location. This represents the entire warehouse structure.
Storage locations that have different technical or organizational requirements have different storage
types in the warehouse numbers. For example: GR zone = storage type 902, high rack storage area, bulk storage, GI zone = storage type 910. To make goods receipt processing and picking easier, you can define multiple doors and staging areas below a warehouse number.
You can also choose to group neighboring areas within the same storage type. If you choose to make this
grouping on a goods receipts basis , we refer to storage scetions. If grouping is created on a picking basis, we refer to picking areas.
Storage bins are located within areas or within storage types for which no specific areas have been
© SAP AG IRT340 2-8 SAP AG 2003 Staging area 4 Staging area 2 Staging area 3 Staging area 5 Storage type 002 Picking warehouse Door 5 Door 4 Storage type 001 High rack stor. area
Warehouse area 1 Warehouse area 2 Staging area 1 Door 1 Door 2 Picking area 1 Picking area 2 Picking area 3 Storage location 0004 (Distribution zone) Storage location 0004 (Distribution zone)
Warehouse 030
Storage location 0003 (Cross-docking) Storage location 0003 (Cross-docking) Storage bins Storage location 0001 DC R300 DC R300Structures in the Distribution Center
SAP AG 2003
Describe the structure of a distribution center in
the SAP system
List the various differences in the organizational
structure of a warehouse
You are now able to:
© SAP AG IRT340 2-10
Exercises
Unit: Basic Concepts
Topic: Basic Concepts
At the conclusion of these exercises, you will be able to:
•Create a site structure
•
Add a new storage location to your site and assign it to your
WM warehouse.
Your distribution center is assigned a new storage location which
you need to maintain in your site master data.
1-1
Throughout this course, you will always use distribution center T7##. Familiarize
yourself with some of the details concerning this distribution center.
1-1-1 To which distribution chain does this DC belong?
______________________________________________________
1-1-2 Which purchasing organization can procure articles for this DC and to which
company code does it belong?
PO:_________________________________________________
CC:_________________________________________________
1-1-3 What are the table keys for the site’s customer and vendor master records?
Customer________________________________________________
Vendor_______________________________________________
1-1-4 Where do you find out whether this site is a distribution center?
______________________________________________________
______________________________________________________
1-2
Create some more settings for your DC and look at the Customizing settings for this
site, too. The inventory management entries are of particular relevance to you.
1-2-1 Which storage locations already exist for your distribution center?
______________________________________________________
1-2-2 Your distribution center is going to have a new storage location. Create this
storage location using the number
0005and the description ‘Storage loc. Gr##’.
Save your entries and exit the distribution center.
1-3
Make some more settings for the Warehouse Management.
1-3-1 Which is the highest organizational unit in the WM system?
______________________________________________________
1-3-2 Create a new warehouse number
L##in Customizing by copying the warehouse
number
T##.
To copy the warehouse number, you must use
[Copy, delete, check warehouse number]1-4* Go to the IMG:
Logistics Execution Warehouse Management Master Dataand
look at the details of your new warehouse
L##.
1-4-1 Which storage types are already available?
______________________________________________________
______________________________________________________
______________________________________________________
1-4-2 Which staging areas exist and which doors are they assigned to?
Staging area:
Door:
______________________________________________________
______________________________________________________
______________________________________________________
1-4-3 Are there any storage sections in warehouse
L##?
© SAP AG IRT340 2-12
Solutions
Unit: Basic Concepts
Topic: Basic Concepts
In the solutions the following points are valid:
•
You can access the SAP Retail menu using transaction W10T. You
should enter this transaction as a start menu in your user parameters:
System User Profile Own Data,
enter
‘W10T’as a
start menuin the
‘User Default’view.
•
If you see the word
MENUbefore a menu path
,then you should go to
the Retail menu, the SAP Retail application menu.
You can easily access the Retail menu by going from the SAP Easy
Access SAP Retail using this menu path:
Logistics Retail
•
If you see the term
IMGin front of a menu path then you should go to
the Implementation Guide of the system where yo u can customize
your settings.
To access IMG, you go from the SAP Easy Access SAP Retail and
follow this menu path
Tools Accelerated SAP Customizing Project Processing SAP Reference- Display IMG (F5)
or use the following transaction
/NSPRO F5 key
Solutions
Unit: Basic Concepts
Topic: Basic Concepts
1-1
Master data Site data Site DisplayField name or data type Values
Site
T7##
1-1-1 Tab Organization/calendar data:
The distribution chain consists of the sales organization and the distribution
channel and is called R300/ R5
Sales organization: R300
Distribution channel: R5
1-1-2 Purchasing organization: R300
Company code:
R300
1-1-3 Button [Customer], Customer T7##
Back/F3
Button [Vendor], Vendor T7##
Back/F3
1-1-4
Extras Admin. dataSite cat. B = Distribution center
1-2
Customizing For site1-2-1 Double click on row:
Storage locations
Double click on view name: V_T001L
© SAP AG IRT340 2-14
1-2-2
Table view Display Change[New entries]
Field name or data type Values
SLoc:
0005
Description
Storage location Gr.##
Table view Save
Return to the SAP Easy Access Menu for SAP Retail using the yellow arrow.
1-3
IMG
1-3-1 The highest organizational unit in the WM system is the
warehouse number.
1-3-2
IMG: Enterprise Structure Definition Logistics Execution Define,copy, delete, check warehouse number
[Copy/delete/check warehouse number]
Organizational object Copy org. object
Field name or data type Values
From warehouse number
T##
To warehouse number
L##
[Enter]
Confirm information by selecting [Enter]
1-4* IMG
Logistics Execution Warehouse Management Master Data
1-4-1
Define storage typeThe following storage types are already available for warehouse L##:
005
Fixed bin storage
916
Shipping area deliveries
999
Differences
FRM Floor Ready Merchandise
1-4-2
Define Article Staging AreasStaging area:
Door:
Area 001
Door A1
Area 002
Door A1
Area 010
Door A2
1-4-3
Define Storage Sections© SAP AG IRT340 3-1 SAP AG 2003
Confirmation documents
Goods receipt posting
Putaway process in lean WM
Contents:
Goods Receipt Process
SAP AG 2003
Carry out the goods receipt process, from the
delivery of the goods to transferring them to the
stock in a storage location.
Set up the delivery process in a lean WM
managed storage location.
At the conclusion of this unit, you will be able to:
© SAP AG IRT340 3-3 SAP AG 2003
Course Overview
Inventory Management
Goods Issue Process
Merchandise Distribution
Summary
7
6
5
4
1
Basic Concepts
2
Goods Receipt Process
3
Course Overview
SAP AG 2003
The vendor delivers the ordered goods to you. You
would like to enter both the delivery quantities and
the delivery note data, which can be used at a later
stage to check the deliveries.
When the delivery quantity varies, you want the
goods receipt to be posted in the future only in the
context of specified tolerance limits.
To keep your losses low in your warehouse, the
articles' expiration date should always be entered
and checked when your goods receipts are posted
in future.
© SAP AG IRT340 3-5 SAP AG 2003
2
2
2
4
4
4
Purchase order Purchase order Goods receipt in distribution center Goods receipt in distribution center1
1
1
Requirements planning Requirements planning3
3
3
Shipping notification Shipping notification5
5
5
Invoice verification and check Invoice verification and check Vendor Vendor Distribution center Distribution center Merchandise flow Information flowBusiness Process (Example)
SAP AG 2003
Describe the confirmation documents, shipping
notification and rough goods receipt.
Set up the confirmation controls as a requirement
for confirmation documents.
At the conclusion of this topic, you will be able to:
© SAP AG IRT340 3-7 SAP AG 2003
Shipping notification ... Vendor ...
IDES Smart Retailer Inc. IDES Smart Retailer Inc. IDES Smart Retailer Inc.
Purchase order ... VendorPurchaseorder ......
VendorPurchaseorder ... ... Vendor ... Post Fax EDI Inbound delivery ... Vendor ... Vendor Vendor
Confirmation Document: Shipping Notification
Shipping notifications are used by vendors to announce the delivery of articles. The vendor sends
information about the delivery date, delivery time, delivery quantities and the articles that are to be delivered.
The shipping notification is based on one or more purchase orders that have been placed with the same
vendor. In SAP Retail, an inbound delivery is created for the shipping notification or in EDI. Inbound deliveries can be used as reference documents for the (rough) goods receipt that follows.
SAP AG 2003 Purchase order Delivery (see note) Enter differences in quantity
Sort purchase order items Generate count lists
Generate tickets Create delivery note
Logistics functions
Reference
document
Purchase order ... Vendor ... Delivery ... Vendor ...Rough GR
Createdelivery note quantity
Confirmation Document for Rough GR
Rough GRis used to identify deliveries, meaning that the items in the delivery documents are assigned
to the items contained in the vendor shipping notification items in the system. Rough GR can only be used for certain order items that have a specific confirmation code (detailed information for the item for the relevant order items).
Rough GR can be used for one or more purchase orders or shipping notifications (inbound deliveries). If
a rough GR is created for one or more purchase orders, and if a delivery has already been posted based on a shipping notification, the user receives notifications.
When a rough GR is posted, a document is also posted. The document has a very similar function to a
delivery notification.
The following options can be used for a rough GR:
- You can enter differences in quantity in delivery notes and purchase orders or delivery notifications.
- You can sort the items from all the assigned purchase orders for additional online processing using the same structure as the delivery document from the vendor.
- You can print out a count list for the GR that is to follow. - You can generate (article) sales tickets.
© SAP AG IRT340 3-9 SAP AG 2003
Purchase order ...
Vendor ... Suitable confirmation control keyin purchase order item
Confirmation control key Customizing Customizing Customizing Definition Conf.control Purchase data Conf.control
Shipping notification entry allowed? Rough GR entry allowed?
...
Vendor
Vendor ArticleArticle
View: Purchasing
Confirmation Document : Prerequisites
To create a confirmation document (for example, a rough GR) for a purchase order item, you need a
suitable confirmation control key for the purchase order item (item details in the purchase order).
Confirmation control keys are defined in Customizing (see next slide) and entered in the purchase order
item. If there is already a confirmation control key in the article master purchasing view, it will automatically become the default value in the purchase order item.
A confirmation control key also may be entered as a default value for article maintenance in the vendor
master data.
SAP AG 2003
Confirmation sequence Confirmation sequence Confirmation sequence
Confirmation control key
Sequence Int. conf. cat.
1 LA
2 GW
3 ...
Confirmation control key
Sequence Int. conf. cat.
1 LA 2 GW 3 ... Monitoring period Monitoring period Reference date Reference date Controls for EDI access Controls for EDI access MRP relevance MRP relevance GR relevance GR relevance GR assignment GR assignment
Purchase order date + Delivery date -Purchase order date + Delivery date -Remove confirmation category as a result of GR? Remove confirmation category as a result of GR? Take account of confirmation in MRP?
Take account of confirmation in MRP? Assign GR to current confirmation? Assign GR to current confirmation?
Ext. confirmation cat. Ext. confirmation cat. Ext. confirmation cat.
Int. confirmation cat. Int. confirmation cat. Int. confirmation cat.
Description
Heading in purchasing list Description
Description
Heading in purchasing list Heading in purchasing list Delivery type
Confirmation Control Key: Definition
The confirmation sequence
Contains a confirmation control key that determines which confirmation categories are expected
Determines the sequence in which the confirmation categories for the purchase order items are expected
Determines the date and time by which the confirmation must have arrived
Determines the relevance for requirements planning and goods receipt.
When you set the inbound delivery indicator with the confirmation control key, you determine that those
purchase orders that contain this confirmation control key should have inbound deliveries created for them automatically. The inbound delivery document is required for creating putaway transfer orders in decentralized warehousing systems.
LA and GW are standard internal confirmation categories to which a delivery type must be assigned.
© SAP AG IRT340 3-11 SAP AG 2003
Describe the procedure for and various methods
for processing goods receipts.
Post a goods receipt for a purchase order and
explain how to control goods receipt using a
movement type.
List the results of posting a goods receipt.
Make settings for checks and tolerances for
goods receipt posting.
At the conclusion of this topic, you will be able to:
Goods Receipt: Objectives
SAP AG 2003
Storage
location
(Stock type) Goods receipt Goods receipt Goods receipt 0003 0001 0002 Vendor Vendor Distribution center Distribution center© SAP AG IRT340 3-13 SAP AG 2003
Storage
location
(Stock type) Rough goods receipt
Rough goods receipt Rough goods receipt
Goods receipt Goods receipt Goods receipt 0003 0001 0002 Distribution center Distribution center Vendor Vendor
Goods Receipt: Steps Involved
SAP AG 2003
Storage
location
(Stock type)
WM
Rough goods receipt Rough goods receipt Rough goods receipt
Goods receipt Goods receipt Goods receipt 0003 0001
Storage bin
0002 Putaway Putaway Putaway Distribution center Distribution center Vendor VendorGoods Receipt: Steps Involved
Goods receipt in a site (distribution center or store) can be done in one or two steps.
Single-step procedure:
A (complete) goods receipt (GR) is executed directly.
Two-step procedure:
A rough goods receipt (rough GR) is run first, enabling delivery quantities to be entered, and is followed by a GR.
In both procedures, the merchandise is assigned to a stock type for a storage location at the site that is to
receive the delivery.
If the destination storage location is connected to the SAP Warehouse Management (WM) system,
articles can be assigned to specific storage bins (putaway). You can restrict the putaway procedure to individual storage sections (= a group of several storage bins within the same storage type for putaway).
© SAP AG IRT340 3-15 SAP AG 2003 Purchase order Inbound delivery (possible note) Rough GR (possible notes) Outbound delivery No reference
Logistics
functionalities
Reference
document
Purchase order ... Vendor ... Inbound delivery ... Vendor ...Goods receipt
Searching the corresponding purchase orders using: - article number - EAN - vendor - ... Checking and monitoring: - quantities (tolerances) - expiration dates - EAN Entering returnable transport packaging Batch handling Entering free deliveries
Return deliveries to
vendors
...
Goods Receipt: Reference and Functionality
You can create a GR (goods receipt) for a purchase order, shipping notification, or rough GR. The user
will be alerted if a GR is created for a purchase order and a delivery notification or rough GR already exists.
The advantages of goods receipt processing with reference documents are:
The goods receiving department can check if the delivery actually contains the merchandise that was delivered;
When the goods receipt is being created, data for the reference document is proposed by the system.
This makes it easier to create the goods receipt and also monitor the development of the goods receipt;
The GR data is updated in purchase order development and vendor evaluation. The means that associates can monitor purchase order development, trigger the dunning procedure, and ensure that quantities and deadlines are adhered to;
The relevant purchaser is automatically informed about GR using SAPmail.
The incoming invoice is used to check the quantity ordered against the actual delivered quantity.
It is also possible to post goods receipt without a reference document for a document that has been
created previously in the system. This allows you to subsequently generate a purchase order thereby allowing you to use invoice verification at a later date.
At GR, you can also run checks and monitoring (for example, for delivered quantities, expiration dates,
shipping instructions, EAN).
Additional features of GR in SAP Retail include the creation of returnable transport packaging as special
stock and handling batch articles, setting up free deliveries and returns to the vendor. Returnable transport packaging is transport equipment, for example, a carton, or an empty, such as bottles.
SAP AG 2003
Non-stock articles
Cost center Project Others
Blocked stock BWA 101 (S)
Stock in quality inspection BWA 101 (X) Unrestricted-use stock BWA 101
GR blocked stock BWA 103
non-valuated non non--valuatedvaluated valuated valuated valuated Consumption Provisionally accepted Stock Goods receipt Goods receipt
Goods Receipt for Purchase Orders
Goods receipt is a form of goods movement.
An article can either be used or placed in stock, following goods receipt, or a GR can be blocked. When
entering a goods movement in the system, you must enter a movement type to differentiate between the different types of goods movements. The goods movement type is a three-character key that is used to identify a goods movement.
For each goods receipt, you decide which stock to post the quantity. The stock is important for
determining availability of stock in requirements planning and also for picking in inventory management. A goods receipt in the warehouse can be posted to three valuated stock types:
- Unrestricted-use stock
- Stock in quality inspection (may be used for requirements planning, but not for picking) - Blocked stock (cannot be used for requirements planning and not available for picking)
Movement type 101 is always used for goods receipt quantities from purchase orders that are to be put
into valuated stock. The individual stock types are distinguished by their stock indicator, which you can enter in the item screen of goods receipt processing.
Merchandise accepted provisionally (for example, damaged articles or unexpected deliveries) is posted
© SAP AG IRT340 3-17 SAP AG 2003 Article doc. Accounting document
Issues
Receipts
Goods movementArticle and accounting documents are generated at the same time as the goods movement takes place.
Article and accounting documents are generated at the same time as the goods movement takes place.
Warehouse Warehouse
Goods Movements Documents
Even when inventory management is computerized, documentation is necessary. A document serves as
proof of a change in stock levels. Documents are saved in the system.
An article document is produced in the SAP system as proof of a change in stock levels.
At least one account document is created in addition to the article document if an article movement
process affects stock valuation.
As soon as a goods movement is posted to the system, quantity, article, movement type and
organizational level cannot be changed. However, some changes can still be made to text fields. If you need to make corrections, a new document must be created. The document containing the errors must first be canceled.
An article document is created so that the process can be recorded Accounting documents are only
created when there is a change in stock valuation (for example, with stock transfers from one plant to another).
The article and accounting documents are separate from one another. The article document can be
distinguished by its article document number and year. The accounting document can be distinguished by the company code, the accounting document number and the fiscal year.. The company code to which
the accounting document has been posted is derived from the plant in which the goods movement took place.
SAP AG 2003 Message to sold-to party (optional) Updating stock and consumption accounts Transfer requirement for WM (if this is active) Transaction document Printing (optional) Opening an inspection lot to trigger quality inspection Update Update purchase purchase order order Goods receipt Value and quantity update Article Article master master Article document GR slip
WM
WM
QM
QM
Statistical updateThe Results of a Goods Receipt
FI docu
This slide gives you an overview of the results of goods receipts creation with reference to a purchase
© SAP AG IRT340 3-19 SAP AG 2003 Purchase order Goods receipt Goods receipt Rough GR Inbound delivery Delivery notification Delivery note ... FI doc. Article doc.
Documents from the Purchase Order to the GR
A goods receipt should always be posted based on a purchase order (in exceptional cases, you can also
post a goods receipt without a reference, however, a purchase order will be needed if you need an invoice verification at a later stage). The goods receipt always creates an article document and an FI document.
In addition, you can create more vendor confirmation documents (delivery notification, delivery note) in
the system. For each purchase order item, you can decide on the confirmation control key and which documents you are expecting from the vendor for this purchase order item.
When using confirmation documents, you should always consider which documents are really necessary
so that you do not overload the system.
SAP AG 2003 Purchase order ... Vendor ... Art. 3214 20 PC Art. 5110 15 PC FI doc. Article doc. Goods receipt Returns
Item 1: Movement type 101
New PO
Item 2: Movement type 101 ...
Item 6: Movement type 161 Customizing Customizing Customizing
Movement type 161: Create purchase order Movement type 161: Create purchase order
For item 6
(with return indicator)
R
Returns with Automatic Purchase Order
Generation
In the case of unplanned returns to vendors, the goods issues (negative goods receipts) are posted
without a reference document. Depending on your settings in Customizing that define whether an item allows a PO to be created, a purchase order is created for an item in the background which can then be used for invoice verification. The article returns can be posted during the goods receipt process. In this case, the purchase orders for which the goods receipt was posted and the purchase order containing the return items are combined into one article document (possibly under an external delivery note number). During invoice verification, the system takes account of a credit memo against the vendor. You can post the return without first creating a reference document (for example, a purchase order).
A return order is created for the planned vendor return. The vendor is therefore information about the
return and can schedule capacity, as required, for the returned merchandise. (NB: this situation is not shown in the slide).
© SAP AG IRT340 3-21 SAP AG 2003 Post GR PO GR quantity 1000 PC 900 PC System message • Error • Warning • None System message System message •• Error Error •• WarningWarning •• NoneNone Underdelivery tolerance Overdelivery tolerance 15 % 10 % Purchase order 345688.. Vendor 309089 .... .... Art. 55421 1000 PC Art. 56334 10 CAR Art. 73452 50 PAL • • • • Tolerances not adhered to ? Article Article Vendor Vendor Site Site
Default "delivery completed" indicator?
Default "delivery completed" Default "delivery completed" indicator?
indicator?
Tolerance Limits and "Delivery Completed"
Indicator
For each item, the system checks whether there are discrepancies between the PO and the article master
data during the GR processing.
In Customizing, you can decide whether each site should have a defaulted "delivery completed"
indicator for goods receipt as long as the quantity delivered is within the under/overdelivery tolerances. The "delivery completed" indicator produces the following effects:
The PO item is considered closed, even if the full quantity ordered has not been delivered.
Although a delivery is not expected, it is still possible.
In the next goods receipt, the item will not be defaulted as being a marked item on the selection list.
The PO item can be deleted, even if the full quantity ordered has not been delivered.
If an underdelivery lies outside the tolerances, you can set the indicator manually either in the goods
receipt or in the PO item so that the PO item is viewed as being a completed delivery.
SAP AG 2003
Shelf life expiration date check activated ? Shelf life expiration date Shelf life expiration date
check activated ? check activated ? Enter/check expiration date/ date of production ? Enter/check Enter/check expiration date/ expiration date/ date of production ? date of production ? Movement type Movement type Movement type System message • Error • Warning • None System message System message •• Error Error •• WarningWarning •• NoneNone ED Date of manufacture Actual ED = date of production
+ total shelf life Record goods receipt
Actual ED < planned ED? Actual ED
is determined
Planned ED = posting date + remaining shelf life
Total shelf life
Remaining shelf life 50 days 30 days Site Site Article Article
Shelf Life Expiration Date Check
An article's expiration date can only be checked if:
- The minimum remaining shelf life is maintained in the article master record - The shelf life expiration date check has been activated in the site
- The shelf life expiration date check has been activated for the type of movement (goods receipt)
If the shelf life expiration date check has been activated, then at the goods receipt stage you must:
- Enter the expiration date or
- Enter the production date if a total shelf life has already been entered for the article.
At the goods receipt stage, the system checks whether the remaining shelf life is sufficient. If it is not
sufficient, then depending on the settings of the system, a warning or error message will appear.
When the goods receipt is posted, the expiration date is recorded in the article document. When the expiration date is calculated, you can set a rounding rule in the article master which
determines whether:
- You round to the beginning of the period - You round to the end of the period
© SAP AG IRT340 3-23 SAP AG 2003 PO history updated GR blocked stock updated
OR
Released to warehouse Return to vendor Goods receipt Goods receiptGoods accepted provisionally Goods accepted provisionally
(GR blocked stock) (GR blocked stock)
Posting Goods Receipt to GR Blocked Stock
Merchandise accepted provisionally (for example, damaged articles or unexpected deliveries) is posted
to GR blocked stock. This means: - Quantities are posted to the stock - No article evaluation is carried out
- The transaction is recorded in the PO history. If the acceptance conditions are fulfilled, then the article can be released and evaluated.
If the merchandise has to be returned to the vendor, then it can be taken out of the GR blocked stock and
sent back to the vendor. An article document is created in this process and the PO history updated.
Articles released from the GR blocked stock can be transferred to the following stocks:
- Restricted-use stock - Unrestricted-use stock - Stock in quality inspection - Blocked stock (valuated)
These are the results of releasing articles from the GR blocked stock:
- Article and FI documents are created - The entire valuated stock is updated - PO and the PO history are updated - The G/L accounts are updated
SAP AG 2003
Set up a lean WM system in your warehouse.
Use lean WM for putaway and create a transfer
order for putaway.
At the conclusion of this topic, you will be able to:
© SAP AG IRT340 3-25 SAP AG 2003
Site
Site
Site
Storage loc.
Storage loc.
Storage loc.
Warehouse no.
Warehouse no.
Warehouse no.
MM
Storage type
Door
Staging area
Storage type
Storage type
Door
Door
Staging area
Staging area
Fixed storage bin
Fixed storage bin
Fixed storage bin
Areas
(optional)Areas
Areas
(optional) (optional) Warehouse: New YorkStorage loc. 0001 Storage loc. 0002
088 042 ... Door 1 Door 2 Zone A 360 Hall 4 Stock 12-6-54 4-23-89 Aisle 2
WM
Aisle 1 902Structures in Lean WM
You can carry out picking with transfer orders using lean warehouse management (WM) even if no
storage bins are managed in the system. No goods receipts or issues are processed in WM as a
subsequent process when using Lean WM. This means that bin dates and stocks are not updated on a storage bin level with quantities. Instead, this updating is done on a storage location level.
No storage bins are managed in lean WM, but you can allocate a fixed storage bin to the article in the
article master and it will then be printed onto the transport order for the information of the picker.
Essentially the lean WM processes are the same as the standard WM. You work with deliveries and
create transport orders for these deliveries. The other WM structures (storage types, doors, staging areas, storage areas) can be mapped out in lean WM in just the same way as in WM (see Unit 2 Basic
Concepts).
SAP AG 2003
Site
Site
Site
Storage loc.
Storage loc.
Storage loc.
Warehouse no.
Warehouse no.
Warehouse no.
MM
Storage type
Door
Staging area
Storage type
Storage type
Door
Door
Staging area
Staging area
Fixed storage bin
Fixed storage bin
Fixed storage bin
Areas
(optional)Areas
Areas
(optional) (optional)1
1
1
2
2
2
3
3
3
Control warehouse number in lean WM Control warehouse number in lean WM
Details of performance data Details of performance data Lean WM activated Lean WM activated
Fixed storage bin
Fixed storage bin Shipping areaShipping area
Difference interface Difference interface Picking area Picking area
Fixed storage bin Fixed storage bin
4
4
4
X5
5
5
Inventory ManagementWM
Article Article Site SiteGoods receipt area Goods receipt area
Setting Up Structures in Lean WM
To produce an efficient procedure for goods receipt and goods issue processing in your warehouse, you
can define and link up the following organizational units:
The entire warehouse structure is managed under one warehouse number. This number reflects the warehouse complex.
The various warehouses may have different organizational and technical features that are defined as storage types.
In a lean WM-managed warehouse, there always has to be at least the following storage types: - Goods receipt area (only in lean WM for putaway)
- Fixed-bin storage - Shipping area and - Difference interface
In lean WM, you can manage picking areas separately from deliveries. To do this, you need to assign the
picking area and the storage bin to the article.
Unlike full WM, in lean WM, no dynamic storage bin determination and no stock administration is
carried out in the storage bins. A fixed storage bin can, however, be recorded in the picking document if it is maintained in the article master (DC Logistics view).
Lean WM can be used for putaway and picking. You need to set the activation level of the warehouse
© SAP AG IRT340 3-27 SAP AG 2003
Difference ? Inventory
Management Warehouse Management System
Corrections? Purchase order Inbound delivery Transfer order Confirmation of transfer order Confirmation of transfer order Post difference Post difference Goods receipt Goods receipt
Putaway Process in Lean WM
Lean WM can be used for the stock removal and for the putaway processes. An inbound delivery is
created in a purchase order for putaway. This inbound delivery serves as a worklist in WM for the putaway.
A transfer request, which controls the physical putaway, is created for the inbound delivery. Like the
picking process in lean WM, no stocks or storage bins are updated in WM. The allocation of storage bins takes place at the same time as the picking process using the movement type and the article master (fixed storage bin). The quantity is not available to MRP/RP.
After confirmation of the putaway, the goods receipt is posted. Differences can be picked out straight
away. Now the putaway quantity is available to MRP/RP.
Customizing:
The delivery item category must be relevant for picking
The warehouse management activation level for a specific storage location has to allow for lean WM in putaway (1 or 4)
As an alternative to the process described above, it is also possible to post the goods receipt first and
then generate transfer requests for warehouse management. If differences should occur; the goods receipt posting is corrected after the transfer request has been confirmed in inventory management.
SAP AG 2003
Transfer order 188 Movement type 101
.... ....
Art. R100002 Site R300 200 PC
Art. R100001 Site R300 10 Car
• • • • • • • • • • • • • • • • Warehouse number
• Transfer order no. • Creation date/ time • Movement type • Reference data • Confirmation indicator/date • ...
• Article with short text • Quantity to be transferred • Site (DC) • Source storage type/bin • Destination storage type/bin
• Storage unit type • Confirmation indicator • ... Head er Items 1 n
Source storage type/bin: 902 01-17-22 Dest. storage type/bin: 001 51-12-44
Source storage type/bin: 902 09-17-33
Dest. storage type/bin:004 33-64-28
Warehouse Warehouse
Transfer Order (Structure)
A transfer order (TO) is an SAP WM document that documents an instruction to transfer articles within
the warehouse complex.
A TO is assigned to just one warehouse number in the organizational structure of the warehouse. This
number identifies an entire warehouse complex and is used to connect a storage location of a site to SAP WM.
A TO consists of a header and one or more items. The following data is included in the TO header:
warehouse number
TO number
TO creation date and time
movement type (which relates to all the TO items)
TO reference data (for example, the number of a transfer requirement or a SD document)
confirmation indicator and confirmation date.
The following data can be entered for each TO item:
the article to be transferred with short text
the quantity of the article (from the item) to be transferred
the site (DC here) where the transfer is taking place
© SAP AG IRT340 3-29 SAP AG 2003
You are now able to:
Carry out the goods receipt process from the
delivery of the goods to transferring them to the
stock in a storage location.
Set up the delivery process in a Lean WM
managed storage location.
Goods Receipt: Unit Summary
Exercises
Unit: Goods Receipt Process
Topic: Confirmation Documents
At the conclusion of these exercises, you will be able to:
•
Create confirmation documents, shipping notifications and
rough goods receipts in the system
•
Explain the settings in Customizing for confirmation
documents
•
Find the confirmation control key in the master data.
After you have sent your purchase order to the vendor, you
receive a confirmation from them in the form of a shipping
notification. You record this in the system with reference to your
PO. The delivery note data should also be created to make the
invoice verification easier.
1-1
Create a purchase order for your vendor.
1-1-1 Choose
Purchasing Purchase order Purchase Order Create Vendor knownto create a PO using the following data:
Standard purchase order
Vendor:
TS1##
Purchasing organization: R300
Purchasing group:
R30
Item overview (expand)
Article: TA03## 10 Car
Delivery date: One week from today
Site: T7##
Article: TA04## 10 Car
Delivery date: One week from today
Site: T7##
1-1-2 Which confirmation control key is used as the default for the individual article
items?
© SAP AG IRT340 3-31
1-1-3 Where does this default value come from?
______________________________________________________
1-1-4 Generate the purchase order and make a note of the number:
______________________________________________________
1-2
In response to your PO, the vendor sends you a shipping notification with the number
2304##
, in which the goods for the inbound delivered are listed.
1-2-1 Enter this information by creating a delivery for your purchase order. The
articles will be available to you in one week from today at 15:00. Ensure that
you also enter the number of the shipping notification (
2304##) as an “ External
ID”.
1-3
The merchandise that you ordered is delivered with the delivery note
4711##.
Vendor: TS1##
Delivery note
No: 4711##
for shipping notification no: 2304##
Article
Quantity
TA03##
8 Car
TA04##
10 Car
1-3-1 Use the delivery note to create the rough goods receipt for your purchase order.
When doing so, refer to the shipping notification that you have received that has
already been entered in your system as an inbound delivery. It can be identified
by using the vendor’s shipping notification number (enter
2304##in the field
External ID).
1-3-2 Enter the vendor’s delivery note number (
4711##) to be able to find the
delivery note more easily in future.
1-3-3 Which delivery type is in the document you have just created?
______________________________________________________
1-3-4 Check the individual defaulted items. Does the delivery note data match the
data defaulted by the system from the shipping notification?
______________________________________________________
1-3-5 Change the first delivery note item quantity as needed and save your rough GR.
Rough GR number:__________________________________
1-4* Look at the purchase order created in 1-1-4.
1-4-1 In the PO how do you find out which confirmation documents already exist for
the PO items?
______________________________________________________
1-4-2 Does the system take into account the information from the confirmations in
requirements planning?
______________________________________________________
1-5* Now take a closer look at the technical background.
1-5-1 Which confirmation categories are for rough GR and for shipping notification?
______________________________________________________
1-5-2 Which delivery type is allocated to the rough GR confirmation category using
the internal confirmation type? Compare this to the rough GR delivery type in
1-1-3.
______________________________________________________
1-5-3 Look at the confirmation sequence for the confirmation control key 0003.
Which indicator ensures that shipping notifications as well as rough GR are
taken into account in requirements planning?
©
© SAP SAP AG AG IRT340 IRT340 3-333-33
Exercises
Exercises
Unit: Goods Receipt Process
Unit: Goods Receipt Process
Topic: Goods Receipt
Topic: Goods Receipt
At the conclusion of these exercises, you
At the conclusion of these exercises, you will be able to:
will be able to:
•
•
Use checks and controls for GR
Use checks and controls for GR
••
Post a goods receipt with items to be
Post a goods receipt with items to be returned on a PO
returned on a PO
••
Explain the consequences of posting a GR
Explain the consequences of posting a GR
The merchandise is delivered to your DC. You run various checks
The merchandise is delivered to your DC. You run various checks
and controls.
and controls.
2-1
2-1
You
You check
check and
and count
count the
the merchandise
merchandise that
that has
has been
been delivered
delivered and
and post
post the
the GR
GR for
for your
your
PO. In doing so, you use the delivery note quantities to check your delivery.
PO. In doing so, you use the delivery note quantities to check your delivery.
2-1-1
2-1-1 Create
Create the
the goods
goods receipt
receipt from
from vendor
vendor
TS1##TS1##with an unknown PO number (
with an unknown PO number ( for
for
a different reference
a different reference) for distribution center
) for distribution center
T7##T7##. Use
. Use movement type
movement type “Goods
“Goods
receipt for PO to warehouse”. You post the goods receipt with reference to the
receipt for PO to warehouse”. You post the goods receipt with reference to the
previous rough goods receipt as a preceding document. The preceding
previous rough goods receipt as a preceding document. The preceding
document is identified by the vendor's delivery note number (
document is identified by the vendor's delivery note number (
4711##)4711##)..
2-1-2
2-1-2 Which quantity
Which quantity does the
does the system
system default for
default for the individual
the individual articles?
articles?
__________________________
______________________________________________________
____________________________
2-1-3
2-1-3 The
The article
article quantities
quantities in
in
TA04##TA04##should be posted to the quality inspection
should be posted to the quality inspection
stock (stock type X).
stock (stock type X).
2-1-4
2-1-4 Select both i
Select both items. You
tems. You assume that
assume that there will
there will be no subs
be no subsequent delivery of
equent delivery of the
the
two missing cartons of article TA03##. How do yo
two missing cartons of article TA03##. How do yo u ensure that the relevant
u ensure that the relevant
items in the purchasing documents are flagged as being completed?
items in the purchasing documents are flagged as being completed?
__________________________
______________________________________________________
____________________________
2-1-5
2-1-5 Save the
Save the GR posting
GR posting and note
and note the number
the number of the
of the article document:
article document:
__________________________
______________________________________________________
____________________________
C
2-1-6*
2-1-6* Display the article document in your system. What other (accounting)
Display the article document in your system. What other (accounting)
documents were created/updated as a result of posting?
documents were created/updated as a result of posting?
__________________________
______________________________________________________
____________________________
2-1-7*
2-1-7* Go to the PO list display and display all the PO (
Go to the PO list display and display all the PO ( scope of list
scope of list ::
BESTBEST) for site
) for site
T7##
T7##
for which there are open GRs (selection parameter
for which there are open GRs (selection parameter
WE101WE101).
).
Is your PO displayed?
Is your PO displayed?
__________________________
______________________________________________________
____________________________
2-2
2-2
You
You decide
decide that
that in
in the
the future
future the
the delivery-completed
delivery-completed indicator
indicator will
will be
be automatically
automatically
defaulted by the system if delivery quantity discrepanc
defaulted by the system if delivery quantity discrepanc ies lie within certain tolerance
ies lie within certain tolerance
limits. If the discrepancies go over these tolerance
limits. If the discrepancies go over these tolerance limits, then a warning message will
limits, then a warning message will
appear on your screen.
appear on your screen.
2-2-1
2-2-1 Where can
Where can you create
you create the tolerances
the tolerances for
for over and
over and underdeliveries of
underdeliveries of articles?
articles?
__________________________
______________________________________________________
____________________________
Allow for a 10% under-delivery of
Allow for a 10% under-delivery of article
article
TA03##TA03##from vendor
from vendor
TS1##TS1##..
2-2-2
2-2-2 Make the
Make the settings i
settings in Customizi
n Customizing to
ng to set the
set the delivery-completed indicator
delivery-completed indicator
automatically for your site
automatically for your site
T7##T7##. Which conditions need to be fulfilled for the
. Which conditions need to be fulfilled for the
delivered quantity so that the system automatically sets the d
delivered quantity so that the system automatically sets the d elivery completed
elivery completed
indicator (F1 Help)?
indicator (F1 Help)?
__________________________
______________________________________________________
____________________________
__________________________
______________________________________________________
____________________________
2-2-3 Choose
2-2-3 Choose
Purchasing Purchasing Purchase oPurchase order rder Purchase OrPurchase Order der CreateCreate Vendor knownVendor known