Download Master Data of ERP Retail - EAN_GTIN PDF

TitleMaster Data of ERP Retail - EAN_GTIN
TagsTechnology Software Computer Data Computing And Information Technology Computing
File Size218.7 KB
Total Pages15
Table of Contents
                            Applies to:
Summary
Disclaimer
Author Bio
Table of Contents
What is an EAN?
	Elements on an EAN code
	Prefix
	Check digit
	Different EAN types
		GLOBAL TRADE ITEM NUMBER (GTIN)
	Where to find EANs in a SAP system?
		Classical maintenance view in the basic data
		Additional EANs
	Customizing
		Number Range Customizing
		Prefix Customizing
		SAP EAN Type Customizing (Attributes)
	Technical references
		How SAP will save the EANs on database
		Number Range Objects
	As mentioned before there are only 3 pre defined number range object supported
	Frequently asked questions
Appendix
	Transactions
	Tables
	Function Modules and Reports
	Reports
	Customer Exits and BADIs
	Notes
	Related Content:
	Copyright
                        
Document Text Contents
Page 1

Master Data of ERP Retail
EAN/GTIN

Applies to:

SAP ERP Retail – all releases. For more information, visit the Business Process Expert homepage.

Summary

This document will give you an overview about the capabilities of SAP to handle ‘EAN/GTIN’. It will not be
another kind of help documentation, but more a deep dive into the architecture, process flow and influence
factors. It will give you tips and tricks about customizing, number ranges, additional external knowledge
sources and a kind of trouble shooting guide.

Disclaimer

The information in this document is a collection based on sources from the former EAN organization now
known as Global Standards One (GS1). Details about the latest valid versions can be found at www.gs1.org

Author: Björn Panter – Development Architect

Company: SAP AG - Trade Engineering

Created on: 23 October 2008

Author Bio

Started 1998 at SAP as developer in support area for IS Retail Masterdata, I collected many
experiences in different customer projects or interal lines of business. Most time focussed on
Master Data topics of ERP Retail or ERP PLM. Currently I’m working in the Trade Engineering
Team.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2008 SAP AG 1

https://www.sdn.sap.com/irj/sdn/bpx
http://www.gs1.org/

Page 2

Master Data of ERP Retail EAN/GTIN



Table of Contents
What is an EAN? ................................................................................................................................................3

Elements on an EAN code...........................................................................................................................................3
Prefix............................................................................................................................................................................3
Check digit ...................................................................................................................................................................3

Different EAN types.........................................................................................................................................3
GLOBAL TRADE ITEM NUMBER (GTIN)....................................................................................................................4

Where to find EANs in a SAP system?...........................................................................................................5
Customizing ....................................................................................................................................................6

Number Range Customizing ........................................................................................................................................6
Prefix Customizing .......................................................................................................................................................7
SAP EAN Type Customizing (Attributes) .....................................................................................................................7

Technical references.......................................................................................................................................9
How SAP will save the EANs on database ..................................................................................................................9
Number Range Objects ...............................................................................................................................................9

As mentioned before there are only 3 pre defined number range object supported ......................................9
Frequently asked questions ............................................................................................................................9

Appendix...........................................................................................................................................................12
Transactions..................................................................................................................................................12
Tables............................................................................................................................................................12
Function Modules and Reports .....................................................................................................................12
Reports..........................................................................................................................................................12
Customer Exits and BADIs ...........................................................................................................................13
Notes.............................................................................................................................................................13
Related Content: ...........................................................................................................................................14
Copyright.......................................................................................................................................................15

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2008 SAP AG 2

Page 7

Master Data of ERP Retail EAN/GTIN

The maintenance for perishable or weight EANs are the same, but with a reduced length of the EAN. The
number range will not represent the full EAN code, it is more the internal or external number for a defined
product code determined at a scale directly in market. (Restricted Circulation Number)

Prefix Customizing

The prefix customizing will help you to determine prefixes for different use cases. In the central check routine
for EAN handling, these prefixes will be checked against the EAN type attributes and EAN code.

The prefix has a length of 2 or 3 digits.



SAP EAN Type Customizing (Attributes)

The most important part of the EAN customizing is the area of attribute definition for the EAN types. The
definition of such an EAN type is SAP specific. It is an additional identifier for end-users to see what kind of
EAN code is behind.

Let us see an example to make it easier.



Starting the attribute customizing you will find the figure above.

If you will see an EAN code e.g. 4011111102008 and a code 2050000002182. Do you know what it is? Of
course the numbers are different, but what is the meaning behind? That’s the reason why SAP introduced
the EAN type. This type will help to understand the logic behind such an EAN code and will also trigger some
follow up processes. But it will have no impact on external interfaces to other systems. In this case only the
pure number will send out.

We will focus on the setting of the HE Manufacturer EAN code.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2008 SAP AG 7

Page 8

Master Data of ERP Retail EAN/GTIN


In the field EAN category, you are able to define a nice name for your EAN type. This name will be shown in
article master data, if you call the search help.

The number range object will allow you to select the wished number range object. The default entries are

• EUROPARTNR for common EAN/GTIN

• EANGEWICH5 for perishable weight EANs 5 digits

• EANGEWICHT for perishable weight EANs 4 digits

The internal and external number ranges control how to handle the EAN.

If there is no internal number range assigned, in article maintenance you will not be able to enter only the
EAN type to draw the next free number from the number interval. Manual entered EAN codes will be
checked against the external number range interval.

The check-digit algorithms will provide a list of hard coded rules how to determine the last digit of the code or
to validate the last digit.

Entering a 12 digit code with EAN type HE will automatically lead to a calculation of the needed check digit.
Wrong check digits will be adopted if they are wrong.

Caution: If you are not using a check digit algorithm, you have to ensure that your assigned number range is
longer.

Fresh produce prefix (I guess this is an error in translation) is the prefix for the EAN code. For general GTINs
it makes no sense to check against a prefix. In general, the system will check if the prefix of the EAN code
will fit in any available prefix value. If you enter here a defined restriction, the code must fit and the
corresponding prefix must be used. This feature will be used for RCNs or Coupons.

EAN length is the most important setting for the EAN types. It controls the output in screens and printers.
The issue with migration the EAN-13 to EAN-14/GTIN format can be handled also by changing some setting
without modifying the master data on database. (Example will follow)

We close the settings with the field ‘Alphanumeric EANs’. This is a setting for the future to prepare the SAP
system to support also characters within an EAN code. Sometimes used for customer specific internal EAN
codes.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2008 SAP AG 8

Page 14

Master Data of ERP Retail EAN/GTIN

Related Content:

Training Content ‚SAP Retail Master Data’ IRT310

PLM110 (Basic Data1)

PLM112 (Customizing Master Data)

For more information, visit the Business Process Expert homepage.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2008 SAP AG 14

https://www.sdn.sap.com/irj/sdn/bpx

Page 15

Master Data of ERP Retail EAN/GTIN

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2008 SAP AG 15

Copyright

© 2008 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere,
Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of
IBM Corporation.

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 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.

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.

These materials are provided “as is” 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 not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may
result from the use of these materials.

SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these
materials. 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.

Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be
used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of
certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors
or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

Similer Documents