1 / 30

Product Catalog

Product Catalog. Best Practices for mySAP Retail. Introduction Process flow Price catalog outbound Price catalog inbound Internet presentation. Price Catalog Interface. Introduction: EANCOM Message 'PRICAT'. EDIFACT

diamond
Download Presentation

Product Catalog

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Product Catalog Best Practices for mySAP Retail

  2. Introduction Process flow Price catalog outbound Price catalog inbound Internet presentation Price Catalog Interface

  3. Introduction: EANCOM Message 'PRICAT' • EDIFACT • Electronic Data Interchange For Administration Commerce and Transport • Cross-industry standard for exchanging formatted, structured data • Very complex; wide-ranging functionality • EDIFACT messages can be combined with application guidelines to meet specific requirements = subset

  4. Introduction: EANCOM Message 'PRICAT' • EANCOM • Is an EDIFACT subset • Detailed implementation guidelines for simple EDIFACT messages • Covers the main business transactions in the whole consumer products industry • Master data (partners, price list/catalog etc.) • Movement data (inquiry/RFQ, quotation, purchase order, invoice etc.) • Reporting and planning data (physical inventory, sales forecasts etc.) • Transportation data (notification of arrival, transfer/shipping order etc.) • Financial data

  5. Introduction: EANCOM Message '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

  6. Message type PriceCatalogue Pricat Message type PriceCatalogue Pricat Converter Converter BAPI/ALE Introduction: Overview Vendor Retailer INBOUND OUTBOUND External system External system SINFOS Pool EDI file

  7. Price Catalog Interface • Introduction • Process flow • Price catalog outbound • Price catalog inbound • Internet presentation

  8. RFC Process Flow: Simulation on a System Vendor Retailer OUTBOUND INBOUND Create price catalog A (VPRICAT): Article X, EAN: 123Send complete version Revision of IDoc using CATTIDoc: Article X, EAN: 124Processing of IDoc Price catalog E is created Process price catalog E (PRICAT):Create new article Y with EAN 124 IDoc PriceCatalogue Change article X, EAN 123Engineering change management in price catalog ASend change version Revision of IDoc using CATTIDoc: Article X, EAN:124 Price catalog E is changed Process price catalog E (PRICAT):Change article Y with EAN 124

  9. Price Catalog Interface • Introduction • Process flow • Price catalog outbound • Price catalog inbound • Internet presentation

  10. Price Catalog Outbound: Creation Creation of catalog using assortment and/or customer DB DB R/3 master data Price catalog • Catalog created on the basis of R/3 data and stored (not sent directly) • EANCOM fields that do not correspond with R/3 fields can be enhanced • Catalog can be revised manually • Differences between new data and master data can be recognised • Transfer of catalog fields can be configured (for example, certain fields are not transferred)

  11. Price Catalog Outbound: Creation • Price determination for individual customer or template customer • Entry of a validity date • Control of price determination using profiles • Release of catalog for presentation on the internet

  12. Price Catalog Outbound: Engineering Change Management Engineering change management for each item Manual engineering change management Change management via batch run DB DB R/3 master data Price catalog • Comparison of catalog data with R/3 master data • Creation of history (with change date) • Manual changes can be write-protected • Batch run with specific check interval • Automatic start of transfer if processing is error-free

  13. Price Catalog Outbound: Catalog Maintenance DB Price catalog • Integrated maintenance interface • Maintenance of header, customer, and item data on a single screen • Integrated creation of new catalog and start of integrated change • Easy navigation using a tree structure • Filter function for restricting data selection • Direct link to catalogs and items • Distribution of catalog fields over the various views can be configured • Areas of the screen that are not needed can be hidden

  14. Price Catalog Outbound: Catalog Maintenance: Header Data DB Price catalog • Maintenance of catalog header (currency, syntax etc.) • Configuration and manual starting of engineering change management • Release for internet • Maintenance of assigned customers • Transfer parameters • Customers can be manually excluded from transfer • Release for internet • Items can be manually excluded from transfer to customers

  15. Price Catalog Outbound: Catalog Maintenance: Items DB Price catalog • "Engineering change management per item" • Check on catalog item • Catalog fields can be protected from changes made by engineering change management • Units of measure, characteristics, BOM components, and conditions can be excluded from transfer • Manual change to validity date

  16. Price Catalog Interface • Introduction • Process flow • Price catalog outbound • Price catalog inbound • Internet presentation

  17. Price Catalog Inbound: Preparation • Preparation before catalog transfer • Assignment of ILN to SAP vendor, purchasing group • Assignment of merchandise categories to SAP merchandise categories (for each ILN) • Assignment of SAP merchandise categories to purchasing groups • Workflow preparation • Assignment of buyers (SAP users) to organizational units, to which the relevant purchasing groups are assigned (transaction PFOM)

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

  19. Price Catalog Inbound: Accessing Catalog Maintenance • Find catalogs using ILN vendor number and status • Preselection for product groups and purchasing groups • Changes can only be made if a purchasing group is entered • Link to maintenance of assignments for catalog creation Header data • Set catalog status • After processing, the catalog status is automatically set to 'processed' • Catalog status can be manually set to 'closed' • Set test indicator

  20. Price Catalog Inbound: Maintenance of Catalog Items • Items are distributed among several views according to their status • Set item status • Excluding and parking EANs • Mass maintenance • Assignment of items to other purchasing groups • Workflow started if the group is not yet assigned • Display of assigned articles

  21. Price Catalog Inbound: Assignment of EAN to an Article • Automatically when a catalog is created (unique EAN) • Manually in catalog maintenance • Assigned article is stored in price catalog • Can be entered at a later date • If the EAN is not unique, all possible EANs are displayed • For assignment, articles are also displayed with the vendor article number from the catalog • New articles need template articles (proposed from the merchandise category)

  22. Price Catalog Inbound: Transferring Catalog Data to Article Data • Simultaneous display of catalog data and article data (or in the case of new data, the template article) • Required data must be explicitly transferred from the catalog to the article side, either manually or by using a transfer profile • Transfer profiles allow you to transfer several fields in a view • Transfer profiles can be stored • The article fields can be edited

  23. Price Catalog Inbound: Assignment of EAN to Unit of Measure • Automatically • By mapping the EANCOM packaging type to alternative unit of measure in the converter • During R/3-R/3 data interchange • Manually in catalog maintenance • Can be changed at a later date • New units of measure must be explicitly transferred • It is possible to transfer all units of measure from the catalog

  24. Price Catalog Inbound: Updating to Article • What can be updated: • Basic data • Texts • BOMs (new) • What cannot be updated: • Characteristics • Generic article/prepack • BOM changes • Conditions • Material

  25. Price Catalog Interface • Introduction • Process flow • Price catalog outbound • Price catalog inbound • Internet presentation

  26. Display and selection of required products Request price catalog Internet Presentation Vendor Internet Retailer ITS ITS XML application Trigger standard interchange EDI file PriceCatalogue.SaveReplica Converter SBC SBC

  27. Scenario Flow

  28. Scenario Flow

  29. Scenario Flow

  30. Scenario Flow

More Related