How to Capture and Manage Serial Numbers during Goods Receipt and Outbound Delivery Applies to: SAP Retail ECC 6.0. For more information, visit the Retail homepage. Summary This document explains about how to capture serial numbers and also how to manage them especially during Goods Receipt and Outbound Delivery processes Author: Aram Kalyanasundaram Company: SAP India Created on: June 13, 2011 Author Bio Aram Kalyanasundaram is a Solution Consultant from SAP India and he has worked on different modules within SAP Arena including SD, IS-Retail, POSDM and EPOS. He is currently focusing on Point of Sales Solution Portfolio POS 2.3 and EPOS 3.1 2011 SAP AG 1
Table of Contents Brief Introduction on Serial Numbers... 3 Customizing Serial Numbers... 3 Create Serial Number... 7 Goods Receipt... 9 Create Sales Order & Delivery Document... 11 Related Content... 17 Copyright... 18 2011 SAP AG 2
Brief Introduction on Serial Numbers Serial Numbers are used to track articles/items especially during Inbound and outbound Logistics processes typical example would be Mobile handsets that normally come along with an IMEI/Serial number or both which can either be tracked based on the IMEI (International Mobile Equipment Identity) number or based on a serial number. Serial numbers can be used in Plant Maintenance (Equipment, Maintenance contract etc), Production Orders, Sales and Distribution (Sales order, Delivery etc), Quality Management (Inspection Lots) Materials Management (Goods Receipt) etc.however this document explains in detail how to create serial numbers and capture them during Goods receipt and O/B delivery processes. Customizing Serial Numbers SPRO ->Sales and Distribution ->Basic Functions ->Serial Numbers -> Determine Serial Number Profile (Tcode OIS2) Note: You can also reach the same screen by navigating using a different path(s) as shown below SPRO->Logistics Execution ->Shipping->Basic Shipping Functions->Shipping ->Determine Serial Number Profiles Serial number profiles are also configurable in SPRO as part of Handling Unit Management, Plant Maintenance and Global Label Management Create a New Serial Number Profile by copying Profile 0001 Let s say we keep Stock check as a warning when there are inconsistencies found as shown above. 2011 SAP AG 3
Choose Serial No Profile ZTST and click on Serializing Procedure 2011 SAP AG 4
Serial Number Usage(s) are given below As per above procedure it s kept as Obligatory (Mandatory) for both GR (Procedure MMSL) and Delivery (SDCC) Create Article Create an article using MM41 as shown below where this Serial Number Profile will be added. Go to Logistics DC View ->Other Logistics data 2011 SAP AG 5
Note: Typically Serial numbers can also be maintained at Sales Set header level and/or component level items depending on how the customer wants them to be tracked, inventory managed etc 2011 SAP AG 6
Create Serial Number Serial Numbers can be created automatically at the time of application transaction for e.g. during Goods Receipt, O/B delivery etc or you can manually assign serial numbers For manually assigning the serial number you can use Tcode IQ01 2011 SAP AG 7
You can go to Tcode IQ03 to check the serial number(s) attached to an article 2011 SAP AG 8
Goods Receipt Let s now do a Goods Receipt (without PO) using MIGO for Article 200 Quantity is entered as 10 Enter Site as AC01 & Storage Location as 1000 Note: Only after entering the site details Serial number Tab will become active and visible in this MIGO screen 2011 SAP AG 9
An option to create Serial Nos Automatically is also available. In our case, since we have already defined the serial number as 12345 for Article 200, we would continue to use it Article Document posted successfully (After Check and Post Functions are performed in MIGO) 2011 SAP AG 10
Go to Tcode MB03 and check the article document which shows 10 Quantity of Article 200 in store AC01 and Storage Location 1000 Create Sales Order & Delivery Document After this I have created sales orders 330 and 331 respectively in which I have used the Serial Number 12345 at the time of Delivery (0080000303) for Sales Order number 330. VA02 - Change Sales Order for 330 2011 SAP AG 11
Delivery Document will show the serial Number 12345 against article 200 2011 SAP AG 12
If you click on details, it will take you to Tcode IQ03 which will display the Article serial number Now I create another sales order for same article 200 in which I give let s say Quantity as 2 2011 SAP AG 13
Go to Va02 and try to deliver Now Go to Extras->Serial Numbers in the Delivery Create Screen 2011 SAP AG 14
Click on F4 which will take you to Tcode IQ09 from where you can find the Serial Number assigned to article 200 and pick the relevant one in this case 12345 and you will get the following error message which will not allow you to save the delivery document. The reason being Serial Number 12345 is already used by Delivery Document (0080000303) which is now active If you click on Cancel the following screen pops up 2011 SAP AG 15
Instead of terminate processing let s say No and choose Create Serial Number Automatically System generates Serial Numbers 12346 and 12347 since there are 2 Quantities of Article 200 ordered and to be delivered Press OK and save the document. Now if you check the Serial Numbers associated for Article 200, the system would have already added the automatically created ones into the account Go to Tcode IQ03 Note : It will not show the site and Storage Location for the automatically generated Serial numbers during the O/B delivery creation 2011 SAP AG 16
Related Content http://help.sap.com/saphelp_ewm2007/helpdata/en/46/4fd2416d9c1c7be10000000a1550b0/content.htm http://help.sap.com/printdocu/core/print46c/en/data/pdf/lomdsn/lomdsn.pdf http://help.sap.com/retail For more information, visit the Retail homepage. 2011 SAP AG 17
Copyright 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 is a registered trademark of Oracle Corporation. 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. Java is a registered trademark of Oracle Corporation. JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 S.A. in the United States and in other countries. Business Objects 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. 2011 SAP AG 18