Sap retail global registry

©SAP AG 2005

GDS for Retail

Solutions Management, IBU Retail

© SAP AG 2006

Agenda

Glossary / ExplanationArchitecture

Catalogue Item Subscription

Catalogue Item Notification

Maintenance of Data

Confirmation Message

Functionality of the Rule Engine

© SAP AG 2006

Glossary 1

GS1GS1 is a leading global organisation dedicated to the design and implementation of global standards and solutions to improve the efficiency and visibility of supply and demand chains globally and across sectors. The GS1 system of standards is the most widely used supply chain standards system in the world. GS1 defines all presented standards.

Advantages GDSNThe advantage of GDSN for a Retailer is that the effort to receive master data in standardized way can be reduced tremendously. For example a Retail who receives information from 30.000 vendors would need to synchronize their data in hundreds of different formats. If all these vendors would ship their data over the data pool the format and the connections needs to be set up only one time.

Global Registry (Function)The global registry works like a search engine to find the data pools where the needed information of the vendor is stored, so that each data pool knows where to get the data from.

Communication between data poolsThe communication between the data pools is standardized so that from all data pools in the network the same information can be received.

© SAP AG 2006

Glossary 2

CatalogueItem MessagesThe CatalogueItem messages are used to exchange the data between the data pools in the

network and are offered from some data pools as well to their clients (Retailers) to receive the information in a standardized format.

Parts of GDSN (GDD, XML Business Messages (BMS), GPC)

The messages are using different standardized techniques for the messages.

1. GDD (Global Data Dictionary)The GDD is a repository for core components which are reused in several GS1 Standards like the GS1 XML Standard Schemas or the GS1 Business Message Standards.

2. XML Business Message Standards (BMS)The BMS defines messages which are used for B2B message data exchange. The messages are devided into sections which are reused in the different messages.

3. GPC (Global Product Classification)The GPC is a classification schema for Products which is in the GDSN.

Used Object in GDSNTrade Item (including price information), Party

© SAP AG 2006

Global Data Synchronisation - Inbound Processes

GDS inbound offers mass adoption of product master data from either external data pools, or from supplier (peer-to-peer scenario). Efficient maintenance is of major importance for retailers because of high data volumes.

Features of GDS maintenance:

- Support of three GDSN message types: Subscription, Notification, Confirmation, based on standard GS1 XML- Maintenance UI for administration of Subscription messages- Rule Engine offering enough flexibility to enable customers to define rules according to their needs (to check message inbound and enhance messages)- Functionality for Confirmation messages - Message mapping for XI- User friendly maintenance UI for convenient display and/or enhancement of relevant data- Mass maintenance functionality- Functionality to enhance relevant data not originating from the data pool- Scheduled data inbound- Fully automated data inbound- Support for EANCOM Pricat messages

Creation of single, generic, and structured articles is supported (article categories in SAP ECC). It’s possible to create all the relevant views of the article master data, i.e. basic data, purchasing information record, purchase conditions, sales conditions etc. Both, creation of new articles as well as maintenance of already existing articles are possible.

© SAP AG 2006

Process of Global Data Synchronisation - Inbound Process

The following business process is executed in XI/SAP ECC (here, the straight forward process is presented) (An external service is needed to support the relevant AS2 protocol.)

1. Maintenance/sending of the message ‘Catalogue Item Subscription’ with relevant GTINs/GLNs(products/suppliers). Maintaining these subscriptions allows to activate/deactivate of the subscription service for receiving master data

2. Receiving message ‘Acceptance/Acknowledgement’ for ‘Catalogue Item Subscription’ (data pool acknowledges the receiving and correctness of the subscription)

3. Receiving message ‘Catalogue Item Notification’ (data pool sends newly requested and changed master data, respectively)

4. Sending message ‘Acceptance/Acknowledge’Message is sent after maintenance and adoption into own master data (acknowledges receipt of message ‘Catalogue Item Notification’)

5. Data formatting (mapping of the XML into the SAP ECC format)

6. Maintenance of cross references ‚VendorID – Purchasing Group’Maintenance of these cross references is a prerequisite for successfully posting GDS-XML messages. These settings need to be maintained at least once, and typically will be changed rarely.

7. Maintenance of cross references ‘SAP Merchandise Category – external merchandise category’These settings are optional, and require infrequent updating. In case no mapping is found, the external value will be adopted.

8. Importing GDS messages into GDS Staging Area

9. Dialog processing- enter layout profile Subsequent selection and display is controlled via layout profile, e.g. how many rows will be displayed per item- selection of catalogue/catalogue entries.

© SAP AG 2006

The Retail GDSN Business Steps

The business steps are done from a vendor and a retailer to exchange master data information. The Retailer himself only exchange messages with his “home data pool” which forwards messages from the vendor data pool and sends messages to the vendor over his data pool.

The Retailer creates a permanent subscription on the required master data

The Retailer Data Pool forwards the item information in the “Catalogue Item Notification message”

The Retailer sends a confirmation for accepted items

© SAP AG 2006

Agenda

Glossary / Explanation

ArchitectureCatalogue Item Subscription


Maintenance of Data



© SAP AG 2006

Overview GDSN Inbound Functionality

© SAP AG 2006

Converter

Data Pool

Architecture

XI

Proxy(Notification)

StoragePPO

Desktop

Rule Engine

Pricat Tables

W_PRICAT_MAINTAIN

Rule Engine

Subscription UI

Confirmation Report

Proxy

Proxy

PricecatalogueIDOC

ALE Customizing

PPO API

Context UI

Rule Work Object

= XI Part

= Rule Engine

= GDS Process (incl. UI and functions)

= existing solution

ExistingFunctionality

NEW

D

EVELOPM

ENT

© SAP AG 2006

Converter

Data Pool

Architecture

XI

Proxy(Notification)

StoragePPO

Desktop

Rule Engine

Pricat Tables

W_PRICAT_MAINTAIN

Rule Engine

Subscription UI

Confirmation Report

Proxy

Proxy

PricecatalogueIDOC

ALE Customizing

PPO API

Context UI

Rule Work Object

= XI Part

= Rule Engine

= GDS Process (incl. UI and functions)

= existing solution

ExistingFunctionality

NEW

D

EVELOPM

ENT

1 Subscription

2Notification

2aRule Engine

3Maintain

4Confirmation

© SAP AG 2006

Agenda


Architecture

Catalogue Item SubscriptionCatalogue Item Notification

Maintenance of Data



© SAP AG 2006

GLN

GTIN

GPC

ERP Data Pool

GLN

GTIN

GPC

4025783000005

10000111

Subscribed


Subscription valuesOn following values a subscription can be made GPC, Target market, GLN, GTIN

Subscription or RequestA subscription is a request to receive information ongoing on a trade item or trade items. The request is proceed on creation of new trade items or on changes of trade items.A Request is message to receive just one time the information on a trade item or on several trade items.

© SAP AG 2006

SAPERPRecipient

Data Pool

DataRecipient

CatalogueItemSubscription

EAN UCC Response

GDSN Exception

RequestForCatalogueItemNotification

SAPXI

(AS2-Adapter)

1

2

3

1) Transaction TWGDS_SUBSCRIPTION2) Report WGDS_XI_PROXY


© SAP AG 2006

Subscription User Interface

© SAP AG 2006

Agenda


Architecture


Catalogue Item NotificationMaintenance of Data



© SAP AG 2006

ERP Data Pool

Notification received

Monitor

GLN

GTIN’s

4025783000005

New Data


Data structure NotificationThe notification message contains the information about the trade item or items which have been previously subscribed or requested.

Follow up processesAfter the trade item information have been received, the original message is stored and forwarded to a rule engine event. In the rule engine event several rules are executed to check and enrich the received trade item information to transform it to an internal article. This internal representation is stored in PRICAT tables and can be processed with the transaction W_PRICAT_MAINTAIN.

© SAP AG 2006

RecipientData Pool

DataRecipient

CatalogueItemNotification

EAN UCC Response

GDSN Exception

1) Transaction WGDS_STORAGE_MONI2) Transaction WER_RULE_CONFIG3) Transaction W_Pricat_Maintain

Pricat tables

Rule Engine

PPO (Storage)

W_PRICAT_MAINTAIN


© SAP AG 2006

PPO Monitoring of Notification Messages

© SAP AG 2006

Details on Single Message

© SAP AG 2006

Agenda


Architecture



Maintenance of dataConfirmation message


© SAP AG 2006

Maintenance of the Data

Through W_PRICAT_MAINTAIN the usual maintenance capabilities can be accessed.

Via the default settings you define per field:

Storage options (data that is displayed in the dialog comes from the catalog, from the reference article or is a default value)

Display options (is the field in the dialog displayed, not displayed or ready for input)

The configuration at client-level is done in customizing; differences at vendor or vendor/merchandise category level are maintained inthe application.

© SAP AG 2006

User Interface for the Maintenance of the Data

The user interface offers :New user interface to mass maintain the dataTime-depended transfer of data to ERP article masterTransfer of prices and generic articles

© SAP AG 2006

ERPData Pool

Data confirmed

Data Maintenance

State GTIN Description


Data structure Confirmation:The Confirmation message contains the information about the trade item or items which have been previously accepted by the retailer.

This message is been sent after the data has been stored in the retailers system.

© SAP AG 2006

RecipientData Pool

DataRecipient

CatalogueItemConfirmation

Send Catalogue Item Confirmation

1) Transaction RWGDS_CONFIRMATION

© SAP AG 2006


The rule engine is a generic tool that allows to check and enrichdata. The rule engine can be called by an event which one or severalrules. Rules can be changed and created on the rule engineconfiguration UI. Each rule has an entry condition and action. Rulescan be grouped in rules sets.

Examples:

Check rule: Entry condition is GLN/ ILN field is empty action is raise error log.

Enrichment rule:Entry condition none, action get Material number for GTIN number.

Enrichment rule: Entry condition specific GLN/ILN, action create purchasing info record forthis vendor

© SAP AG 2006

Further Examples for the use of the Rule Engine

Incoming data is validated catalogue item validation

Find corresponding product data and user correlation (catalogue item-GTIN/ product data-GTIN)

Transformation of catalogue- and product data to work item

Work item enrichment

Product data validation

© SAP AG 2006

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

Copyright 2007 SAP AG. All Rights Reserved

Sap retail global registry

Documents

Transcript of Sap retail global registry