19.country of Origin and Batch Management
19.country of Origin and Batch Management
Batch Management
Supply Chain Execution
SCM 5.0
©SAP AG 2005
© SAP AG 1
Why do we need Batch Management?
ERP SCM
(/sapapo/batch_req)
Material (mara-xchpf) Product
Class /sapapo/verskey
Characteristics
Class
SAP_SPE_COUNTRY_OF_ORIGIN Characteristics
© SAP AG 2005
An ERP Inbound Delivery (originating from an ASN received in ERP) is forwarded to SCE. In
SCE this message is stored in an Inbound Delivery Request (IDR), which is used as a persistent
storage of the incoming message within SCE. This Request object is not used for processing
within SCE, it does not has a SCE specific readable document number.
Promptly a Processing Delivery (Proc.Del.) is created out of the IDR. IDR and Proc.Del. are for a
single warehouse. The Proc.Del. has a SCE specific document number. The Proc.Del. can be
used for forecasting the WM capacity load.Site processing like ‚status in yard‘ and WM
processing is done by means of the Proc.Del. Changes of the Proc.Del. are sent back to ERP as
a kind of SCE delivery info message. A Proc.Del. with status ‘execution completed’ is the basis
for a POD.
ASN updates or manual updates within ERP inbound delivery are forwarded to SCE and stored
within the IDR. If possible, the changes are forwarded to the Proc.Del. The changes could also
be a IDR split. IDR and Proc.Del. splits can be handled smoothly in SCE as long as is no link to
WM objects like a TO. Thus an ‘early’ split is not a problem. Late splits which need an update of
links to WM objects do not occur in inbound execution.
A manual inbound split shall be done in ERP. In case the ERP system is not available, a
Proc.Del. could be manually created in SCE. ERP inbound delivery and IDR are adapted by
means of a message roundtrip via ERP.
© SAP AG 2
Data distribution using CIF (CFM1, CFM2)
Special org. area has to be
•Batch on material level maintained for class type 230
•Batch on client level
•Batch on plant level ERP WME (SCM)
Material Product
Special org. area master
has to be maintained for Batch master Version
Class type 023
AUSP
© SAP AG 2005
© SAP AG 3
Batch Creation within EWM (external numbering only)
ERP EWM1
lgnum 1
Mat. batch (char10) werks lgort lgnum 10
/sapapo/verskey
WERK/LGORT 0001/0001
0001/0010
WERK/LGORT 0002/0815 Product Version (char10)
NRIV BatchID (Raw16)
BATCH_CLT
lgnum 2 EWM2
MCH1
/sapapo/verskey
OBJEK (matnr,charg)
© SAP AG 2005
Because there are two plants in ERP, the right table for batch is MCH1.
© SAP AG 4
Batch Creation/Change/Display within EWM
FUGR CTMS
ERP EWM
Material
master AUSP
MARA Charact.
MARC
OBJEK (matnr, obtab) Classes
© SAP AG 2005
© SAP AG 5
ERP Configuration
© SAP AG 6
Master data
Class name, use class type 023, put organizational view ‘W’ to the corresponding
field of basic data
© SAP AG 2005
© SAP AG 7
Maintain batches within EWM
© SAP AG 2005
© SAP AG 8
Copyright 2005 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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 Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 in several other countries all over the world. 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.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.
© SAP AG 2005
© SAP AG 9