Best Practices for mySAP Retail Partneroriented Masterdata

Best Practices for mySAP Retail

Partneroriented Masterdata

SAP AG 2003, Title of Presentation, Speaker Name / 2

Article Creation


Article Creation: types of vendors

External vendors

vendors

CpD-vendor

Internal vendors

Distribution center

Central warehouse

Regional warehouse


Vendor: Data

General Data

AddressControl dataBank account

Accounting data

Account managementPayment transactionsCorrespondence

Purchasing organisation

Purchasing dataPartner function

VendorVendorContact person


Vendor: partner function

VendorVendorVendorVendor Invoicer

PayeeGoods supplier

Order address

obligatoryobligatory

DEUTSCHEMARK

DEUTSCHEMARK

DEUTSCHEMARK


Customer Creation


Customer master development

Accounting area dataAccounting area data

Relevant for accounting

Available for company code

Relevant for accounting

Available for company code

General dataGeneral data

Relevant for distribution

and accountingAvailable for all

organizational units


and accountingAvailable for all

organizational units

Sales area dataSales area data


Available for: division, distr. chnl., sales

organization


Available for: division, distr. chnl., sales

organization

Customer masterCustomer master


Data of the tab strip “General Data“

Customer master data “General Data”

Address

Steuerungsdaten

Payment transac

Marketing

Unloading points

Export data

Contact person

Name, Anschrift, Sprache, ...

Bank details, ...

Sales tax informations, ...

Indusrty, customer class, ...

Goods accepted times, ...

Data for export control, ...

Address business partner, ...


Data of the tab strip “Company code data“

Customer master data “Company code data”

Aufträge

Correspondence

Insurance

Payment transac

Accounting manag Name, Anschrift, Sprache, ...

Bankverbindung, ...

Dunning procedure, person responsible, ...

Reconciliation account, ...

Payment method, payment lock, ...

Contract amount, ...


Data of the tab strip “Sales area data“

Customer master data “Sales area data”

Aufträge

Faktura

Partner functions

Shipping

Orders Name, Anschrift, Sprache, ...

Bankverbindung, ...

Output tax classification, term of payment, ...

Sales office, currency, sales district, price group, ...

Shipping condition, delivering plant, transportation zone, ...

Ship-to party, invoice-to party, payer, ...


Partner functions for the customer master

PersonalPersonalPersonal

........

Contact personContact person

CarrierCarrier

Partnerrollen

Sold-to party*Sold-to party*

Partner functionsPartner

functions

Ship-to party*Ship-to party*

Payer*Payer*

Invoice-to party*Invoice-to party*

*obligatory roles*obligatory roles


Customer Creation: customer types

Customer Anonymous Established Customers

• Customer in the wholesale trade

• Customer with creditcard

• Internal customer

• Customer in the mail order

• CpD-Customer

• Cash sale customer

• Customer with payment card

• Customer with creditcard


Consideration as regards of the customer differentiation

THE customer = industrial enterprise

A lot of data of the standard-customer master are without any

meaning for the natural person as customer (e.g. unloading

point, foreign trade data, license)

A minimal master data maintanace and address entry in the

operational business is importent

A great group of consumers have the same sales area- and

company code data = data redundancy


Site


Site Categories

DC

StoreStore

Vendor

Customer


Stock-keeping

level

Stock-keeping

level

Components of a Site

DistributionCenter

Store

VendorVendor RetailSpecific

RetailSpecific CustomerCustomer


Sales area data

salesbillingmessagespartner functions

General datacontrol datamarketingpaymt. transactionsunloading pointsforeign tradecontact person

Company code dataaccount mgmt.

correspondenceinsurance

payment transactions

Customer

Site: Customer Data


General data

control datamarketingforeign trade

Company code data

account managementpayment transactions

Purchasing organization data

purchasing datapartner functions

correspondence

Site: Vendor Data

Vendor


Purchasing Organizations

Standard purchasingorganization (T001W)

Further purchasingorganization (T024W)


Distribution Chain: Site


Distribution Chain: Site Customer

Distribution chain thatthe site is supplied by (KNVV)


= is supplied by = belongs to

DCdistribution chain

Store distribution chain

DC

Store Store

Supplying Relationships

= delivers via / sells through


DC: Sales Price Valuation

Distribution chain forsales price valuation


Assignment

Working with Site Profiles

Site Profile

Reference siteReference site

Cust. tableCust. table

Cust. tableCust. tableCust. table

Copy rule 1Copy rule 1

Site category

Customer

Vendor Account group

Account group

Reference dataControl parameters

StoreStore DCDC


Creating and/orchanging

new articles

ArticlesArticlesArticlesArticles

Logistic data store

Article 4711DCH *Store *

RP type ND

Reference site Dependent sites

Logistic Data store

Article 4711Store R153

RP type ND

Logistic Data store


RP type ND

Logistic data store


RP type ND

Independent site

Logistic data store


RP type RP

automatic creation

MABW-Record

Article Master: Reference Site (1)


provides default data for

Distribution chain North


Distribution chain South

OptionalOptionalOptionalOptional

StoreKiel

StoreUlm

StoreCologne

DC

Reference site - general

Reference siteDistribution chain

South

Reference siteDistribution chain

North

Article Master: Reference Site (2)


Global

TWPA TVKOV



Copyright 2003 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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® 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®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA 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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML 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.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com 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 trademarks of their respective companies.

Documents

Best Practices for mySAP Retail Partneroriented Masterdata