PRICAT Inbound
SAP Best Practices for Retail
Purpose, Benefits, and Key Process Steps
Purpose
 In this scope item 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 Steps




Simulation of PRICECATALOGUE IDoc inbound processing
Inbound Processing of a Price catalog
Processing of Catalog Items manually / automatically
Creating / Changing of articles
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
2
Required SAP Applications and Company Roles
Required SAP Applications
 SAP Enhancement Package 7 for SAP ERP 6.0
Company Roles
 Retail Master Data Manager
 Manufacturer
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
3
Process Flow Diagram
Manufacturer
PRICAT Inbound
Create Pricecatalog IDoc
Retail Master Data Manager
Simulated
Checking / Changing
Catalog Items
Inbound Processing
Create / Change
Articles
Selecting a Catalog
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Posting a Pricat Item
Automatic
Processing
4
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.
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.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
5
PRICAT Inbound
Introduction
With SAP software you have the possibility to build up the
manufacturer and also the retailer side.
The ECR conformable procurement processes embrace the price
catalog, the buyer managed inventory, and also the vendor managed
inventory.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
6
Price Catalog: 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
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
7
Price catalog: Supply of a data pool
Vendor
Retailer
Sender
Recipient
Data Pool
f. e. SA2
Generate of
PriceCatalogue Idocs
Empf
änger SAP
XI
ERP
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Master Data
BAPI/ALE
XI
Inbound processing
of PriceCatalogue Idoc
Empf
änger SAP
ERP
8
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 (EAN‘s) /
Creating article
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Process available article data in the
customer system (EAN‘s) /
Update of article
9
Price Catalog Inbound: Catalog Creation
 The catalog is stored on the database as a separate business
object PriceCatalog
 EANCOM fields that do not correspond to SAP ERP 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)
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
10
Price Catalog Inbound: Preparation
lPreparation
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
lWorkflow

preparation
Assignment of buyers (SAP users) to organizational units, to which the
relevant purchasing groups are assigned (transaction PFOM)
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
11
Price Catalog Inbound: Accessing Catalog Maintenance
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
If you want to process the catalog, you have to always enter the purchasing group
Price catalog could be processed manually or automatically
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
12
Price Catalog Inbound: Accessing Catalog Maintenance
List of articles
 In the list of articles, you will find the article (items) of the new
price catalog
 Items are distributed among several views according to their
status
 New items have no entry in the field “article” and you can find this
items in the “to be processed” tab and “all entries”
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
13
Price Catalog Inbound: Assignment of EAN to an Article
The assignment of EAN to an article occurs automatically when a catalog
is created (unique EAN)
lManually 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)
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
14
Price Catalog Inbound: Transferring Catalog Data to
Article Data
Adopt Profile
The transfer of catalog data to article data could be done with an adopt profile
The adopt profile enables the 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
Adopt profiles could be stored and used again
The article fields can be edited
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
15
Price Catalog Inbound: Assignment of EAN to Unit of
Measure
lAutomatically


By mapping the EANCOM packaging type to alternative unit of measure in
the converter
During SAP ERP – SAP ERP data interchange
lManually

lNew

in catalog maintenance
Can be changed at a later date
units of measure must be explicitly transferred
It is possible to transfer all units of measure from the catalog
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
16
© 2014 SAP SE or an SAP affiliate company. 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 SE or an
SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE
(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be
changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties
that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking
statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
17