erp integration supplier replication -...

SAP Sourcing / CLM Webcast Series

ERP Integration – Supplier Replication

SAP Sourcing Center of Excellence May 2013

Prasad Venkateshwara Kothapalli

© 2013 SAP AG. All rights reserved. 2 Public

SAP Sourcing / CLM 2013 Webcast Series

Goal

• Spread the knowledge about SAP Sourcing

• Build and leverage the SAP Sourcing community

Audience

• SAP Consulting and Field Services

• Partner Consulting

• SAP Sourcing Customers

Upcoming Webcasts

• ERP integration – Supplier Registration

• ERP integration - Pricing Conditions

• Complex Pricing Formulas

Feedback

• Please take 2 minutes to answer our survey


Agenda

Overview

• Supplier Management with Integration

Replication

• Supplier Replication with ERP

Vendors

• Deactivation of vendors

Supplier Management Overview


SAP Sourcing Supplier Management

Integration to ERP

Sourcing Db

ERP1

Vendor Db

Master

Agreement

ERP2

Vendor Db

ERP3

Vendor Db

Outline

Agreement

Supplier used in Master agreement

Vendors replicated from multiple ERP systems

Suppliers replicated from sourcing to ERP

Supplier Self registration


Information replicated from ERP & Relationships

Basic data

Keywords

Display name

Address data

Order address

Relationships

Purchasing Org’s

Vendor account group

Business System

Supplier

ERP1

(VAG+Vendor)

ERPn

(VAG + Vendor)

ERP2

(VAG+Vendor)

Porg Porg Porg

. . . . .

Supplier Replication with ERP


What is needed to enable Integration ?

PI Content - E-SOURCING SRM JSERVER OP 9.0 (from the service

marketplace)

ECC system 6.0 and above

Key Transactions

SM59 – Connection to PI (XMLHTTP)

WE21 – Port definition for Vendor transfer

WE20 – Partner profile

BD64 – Distribution model

SAP Sourcing

Main parameters

odp.doc.integration.enable.suppliers_to_from_multi_external_systems

Authorizations (two separate objects for publish and republish)


Master Data extraction

Prerequisites

Baseline configuration of Sourcing system must be

completed

Note: Baseline configurations will add some master data like

Currencies and UOMs to the system

Business System/External System must be created in

Sourcing. It represents an ERP system that is integrated with

SAP Sourcing

The user account used for importing master data should have

appropriate access

Setup import Scheduled Tasks if they are used to import the

master data

Company codes

Purchasing organizations

Regions (ERP Regions)

Vendor Account Groups


Replication process

IDOCs and ABAP extraction report

Two ways of extracting vendors to sourcing

IDOC’s

ABAP extraction report

IDOC’s (are the preferred approach)

o One IDOC will generate one XML in PI, which will represent a vendor

o IDOC’s can be bundled to improve performance (mostly used to publish bundled changes)

o IDOC’s can be automated to extract and export any changes to the vendor master records

o IDOC’s supports filters

ABAP extraction report

o Generates an XML file directly.

o Can bundle XML files which is useful during initial data loads

o Can bypass the PI Communication layer

o Has limitations with change pointer handling & inactive vendors


Replication process

Send IDOC - Settings

Ensure correct settings for transfer using the following

transactions

• SM59 – Connection to PI (XMLHTTP)

• WE21 – Port definition for Vendor transfer

• WE20 – Partner profile

• BD64 – Distribution model


Replication process

Send IDOC

1. In the ERP system , use transaction

BD14 to send the vendor out to PI

2. In ERP use transaction WE02 to

check the status


Replication process

Report

1. In the ERP system, use transaction SE38 to execute the report ‘BBP_ES_MASTERDATA_EXTRACT’


Replication process

Check message in PI

Ensure correct settings for transfer using the following transactions

• The right PI Content is imported for the integration (details on configuration guide)

• The correct configuration is maintained in Integration builder to send data to FTP or File Server

• Connections to FTP server are working

1. In the PI system use transaction SXMB_MONI to check the status of the message(IDOC) that was

sent from ERP.


Replication process

Check in Sourcing

2. Ensure correct settings for import

Deactivation of vendors


De-activating vendors

There are multiple ways by which a supplier

(replicated) can be rendered unusable in the

Business documents.

Block select Purchasing Org.

o When the vendor is blocked for a selected purchasing Org.

in ERP, such vendor will also be blocked on the

sourcing/CLM application and will not be usable for the

purchasing Org.

Block all Purchasing Org’s.

o Its is also possible to block the vendor for all Purchasing

Org’s. in ERP which results in the same behavior on

Sourcing/CLM.

Mark vendor for Deletion

o Marking a vendor for deletion and replicating, will make the

vendor inactive for the Business system in question and

also will be unusable in Master agreements and other

Business Documents

NOTE: The ‘Purchasing Hold’ and the ‘Inactive’ fields on the header tab of Supplier record are for a different purpose

and as such are not used to represent the ‘Purchasing Block’ and ‘mark for Deletion’ on the ERP side.


Handy Information

ERP Transactions

• MK01,MK02,MK03 : Create,change, display supplier –

Purchasing view

• XK01,XK02,XK03 : Create, change, display supplier – Central

view

• XK05 : Mark supplier for deletion

• WE02: IDOC monitoring tool

PI Transactions

• SXMB_MONI : Message monitoring tool

Order of Imports:

• Currency

• Regions

• Company Code

• Purchasing Org.

• Vendor account Groups

• VENDORS


Design Considerations

E-Sourcing does NOT provide master data management

functionalities ( like data normalization and consolidation)

Purchasing Org information will NOT be transferred from E-

sourcing to ERP

Notice of IDoc failure in ERP NOT sent to E-Sourcing.

Replication of vendors (import) limited to vendors that belong to

the Vendor account groups in sourcing

Thank you

© 2013 SAP AG. All rights reserved.

© 2013 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, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

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.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

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.