cs ewm packspec distribution pdf
TRANSCRIPT
Consulting Solution
Packing specification
Distribution of packing instructions to SCM
Contact:
Matthias Nater ([email protected])
for questions & contract details
© SAP 2009 / Page 2
1. General Information
2. Functional Description
3. Realization in the System
4. Technical CV
Agenda
© SAP 2009 / Page 3
Consulting Solution
Requirements known, concept and solution existing
Solution used by multiple customers
Usage of the knowledge of SAP Consulting and SAP Development
Functionality based on SAP standard functionality
Solution available for all EWM releases
Fast and easy to be implemented
Efficient and short project duration
Time saving leads to cost saving, also at the customer side
Exact pricing possible due to fix price implementation
No running costs like user licenses, maintenance
In advance investment by SAP Consulting reduces cost risk
Cost sharing model strongly reduces cost of the customer implementation
Solution
Time
Cost
Well-tried solution, with efficient and cost-saving
implementation for a high security of the investment
This Consulting Solution means for you…
© SAP 2009 / Page 4
Scope of Solution
Fixed price contains the following services
Technical implementation
Configuration Guide
Technical documentation
Explanation of the function and hand over
6 Month free of charge post implementation care (Error
corrections after technical implementation end), after
this consulting support based on normal fees
© SAP 2009 / Page 5
1. General Information
2. Functional Description
3. Realization in the System
4. Technical CV
Agenda
© SAP 2009 / Page 6
Packing instruction / Packaging specification
Packing instruction is master data in ECC:
“A packing instruction serves as a template for the creation of a handling unit. In a packing
instruction, you define the materials and packaging materials to be packed in a handling unit.”
Packaging specification is the corresponding master data in SCM.
Furthermore the packaging specification in SCM is used for other processes like e.g. ATP
sourcing. Therefore the structures between ECC and SCM are not fully compatible.
Goals & concept
Situation:You want to use EWM for Goods Receipt from production and you want to create HU
automatically in EWM . You already have packing instructions in ECC and they are used
by several applications (not only warehouse). Hence you need a “copy” of the packing
instruction in EWM.
No standard interface like CIF is available in standard – only a solution for an
initial transfer from ECC to SCM 4.1: see note 832221.
This consulting solution is a new interface to transfer periodically the ECC
packing instructions to SCM packaging specifications.
Also the corresponding condition records (or only parts of it) can be transferred
to SCM. A project specific mapping must be added in SCM to fill the right
condition technique fields. Restrictions to certain fields exists. In a workshop the details of these mapping must be
clarified, before it can be added to the add-on.
© SAP 2009 / Page 8
1. General Information
2. Functional Description
3. Realization in the System
4. Technical CV
Agenda
Technical aspects
The same interface technology as standard interfaces for ECC – EWM is used:
A new qRFC interface will be built to transfer and convert the packing instruction
information into SCM packaging specification.
The report can be used to schedule periodically a distribution of changed
packaging instructions to SCM.
Example selection screen:
Technical aspects
Example
ECC packing instruction:
SCM packaging specification:
new qRFC interface
Technical aspects
Good to know:
A distributed packaging specification is protected against changes in SCM
(no change / deletion allowed – adding condition records is allowed)
A nested packing instruction in ECC will result in a nested packaging
specification in SCM.
The linked documents (in ECC) are not distributed to SCM.
The ID of the ECC packing instruction and SCM packaging specification will be
the same.Due to technical restrictions for packaging specification IDs in SCM not all packing
instructions can be distributed: Valid characters include numbers from 0 to 9, letters from A
to Z, and the underscore '_„.
The SCM packaging specification contains more information than the ECC
packing instruction. Due to this reason, there are several fields in SCM
packaging specification not filled (e.g. quantity classification).
The report can be used for an initial transfer / one-time migration too.
© SAP 2009 / Page 12
1. General Information
2. Functional Description
3. Realization in the System
4. Technical CV
Agenda
© SAP 2009 / Page 13
Technical CV
Function
Interface for packing instruction
distribution to SCM
g
AddOn/Modification
AddOn
Function available
R/3 4.7 or higher
SCM-Basis 5.0 or higher
(included in EWM, APO, SNC, …)
© SAP 2008 / Page 14
Thank you!
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 and/or its affiliates.
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.
Copyright 2011 SAP AG
All rights reserved
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects
Explorer, StreamWork, 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.
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.