Die Präsentation wird geladen. Bitte warten

Die Präsentation wird geladen. Bitte warten

PRICAT Inbound SAP Best Practices for Retail (US) SAP Best Practices.

Ähnliche Präsentationen


Präsentation zum Thema: "PRICAT Inbound SAP Best Practices for Retail (US) SAP Best Practices."—  Präsentation transkript:

1 PRICAT Inbound SAP Best Practices for Retail (US) SAP Best Practices

2 Scenario Overview - 1 Purpose In this scenario you transfer pricing and catalog-related data for goods and services from a vendor to a buyer. Benefits Efficient merchandise control which fulfills the requirements of ECR-compliant procurement processes Simulation of data coming from the manufacturer and process this data further in the retailer system Key process flows covered Simulation of PRICECATALOGUE IDoc inbound processing Inbound Processing of a Price catalog Processing of Catalog Items manually / automatically Creating / Changing of articles Purpose and Benefits:

3 Scenario Overview - 2 Required SAP EHP3 for SAP ERP 6.0 Company roles involved in process flows Retail Master Data Manager Manufacturer SAP Applications Required:

4 Process Flow Diagram Create Pricecatalog - IDoc Create / Change Articles Automatic Processing Inbound Processing Selecting a Catalog Checking / Changing Catalog Items Posting a Pricat Item Retail Master Data Manager Manufacturer Simulated

5 PRICAT Inbound Introduction Between Retailers and Manufacturer of the German textile and apparel industry, cooperatively concepts within the framework of procurement, marketing and using of information and communication technology are developed. Between Retailers and Manufacturer of the German textile and apparel industry, cooperatively concepts within the framework of procurement, marketing and using of information and communication technology are developed. Collaboration concepts, like Efficient Consumer Response (ECR), earn on importance. The new technologies open small and middle comanies the possibility to accomplish the structure change and also to reinforce their competitive strength. SAP offers a software solution within the framework of the SAP Best Practices Version, which reflects the new requirements of ECR conformable procurement processes.

6 PRICAT Inbound Introduction With SAP software you have the possibility to build up the manufacturer and also the retailer side. We will show you here the procurement processes on the retailer side. With SAP software you have the possibility to build up the manufacturer and also the retailer side. We will show you here the procurement processes on the retailer side. The ECR conformable procurement processes embrace the price catalog, the buyer managed inventory and also the vendor managed inventory.

7 Price catalog: PRICAT PRICAT Is an EANCOM standard message type Area of master data Enables pricing and catalog-related data for goods and services to be transferred from a vendor to a buyer Complete listing of all products Notification of changes Information relevant for all customers Customer-specific information Data supplied to a central article database

8 Price catalog: Supply of a data pool VendorRetailer Master Data Data Pool f. e. Sinfos XI Inbound processing of PriceCatalogue Idoc Inbound processing of PriceCatalogue Idoc BAPI/ALE Generate of PriceCatalogue Idocs Generate of PriceCatalogue Idocs SenderRecipient XI

9 Price catalog inbound: process flow Simulation of IDoc Inbound processing Display Header Data (catalog) List of article Adopt Profile Process Price catalog manual / automatical Process not existing article data in the Customer system (EANs) / Creating article Process available article data in the customer system (EANs) / Update of article

10 Price catalog inbound: catalog creation The catalog is stored on the database as a separate business object PriceCatalogue EANCOM fields that do not correspond to R/3 fields are transferred to the system It is possible to select articles to be updated Transfer can be controlled at field level If an EAN exists uniquely in the system, article assignment is carried out If errors occur, an application log containing all messages is created (transaction PRICATLOG)

11 Price catalog inbound: preparation l Preparation before catalog transfer n Assignment of ILN to SAP vendor, purchasing group n Assignment of merchandise categories to SAP merchandise categories (for each ILN) n Assignment of SAP merchandise categories to purchasing groups l Workflow preparation n Assignment of buyers (SAP users) to organizational units, to which the relevant purchasing groups are assigned (transaction PFOM)

12 Price catalog inbound: accessing catalog maintenance Header data l Set catalog status n After processing, the catalog status is automatically set to 'processed' n Catalog status can be manually set to 'closed' l Set test indicator l If you want to process the catalog you have to enter always the purchasing group l Price catalog could be processed manually or automatically

13 Price catalog inbound: accessing catalog maintenance List of article l In the list of article you will find now the article (items) of the new price catalog l Items are distributed among several views according to their status l New items have no entra in the field article and you can find this items in tabstrip to be processed, to be processed (article can not be assigned) and all entries

14 Price catalog inbound: assignment of EAN to an article l The assignment of EAN to an article occurs automatically when a catalog is created (unique EAN) l Manually in catalog maintenance n Assigned article is stored in price catalog n Can be entered at a later date n If the EAN is not unique, all possible EANs are displayed n For assignment, articles are also displayed with the vendor article number from the catalog n New articles need template articles (proposed from the merchandise category)

15 Price catalog inbound: transferring catalog data to article data Adopt profile l The transfer of catalog data to article data could be done with an adopt profile l The adopt profile enables the simultaneous display of catalog data and article data (or in the case of new data, the template article) l Required data must be explicitly transferred from the catalog to the article side, either manually or by using a transfer profile l Adopt profiles could be stored and used again l The article fields can be edited

16 Price catalog inbound: assignment of EAN to unit of measure l Automatically n By mapping the EANCOM packaging type to alternative unit of measure in the converter n During R/3-R/3 data interchange l Manually in catalog maintenance n Can be changed at a later date l New units of measure must be explicitly transferred n It is possible to transfer all units of measure from the catalog

17 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. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 and associated logos displayed 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. 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. 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 Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Alle Rechte vorbehalten.


Herunterladen ppt "PRICAT Inbound SAP Best Practices for Retail (US) SAP Best Practices."

Ähnliche Präsentationen


Google-Anzeigen