Ariba_SLP_and_ERP_Bi_directional_Integra.pdf

March 8 2017
Ariba SLP and ERP Bi-directional Integration
Customer

© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2
Customer
Agenda
 Overview
 Functional Flow
 Data model
 MDG-S BusinessPartner interfaces
 Integration Design
 Technical Flow Diagram
 Governance Approvals
 Custom fields support
 Q&A

Customer
Overview
Ariba Supplier Lifecycle Performance (SLP) is a new solution, part of the Ariba Application Suite, to
manage the supplier lifecycle and will be the central supplier management solution for all Ariba
applications. Few key features are:
➢ Alignment of the vendor object model to have all details of the MDG-S business partner model Some of the high level
data are:
o Vendor General data
o Vendor Purchasing data
o Vendor company code data
o Vendor bank details
o Vendor partner functions
➢ Complete support of supplier lifecycle processes (e.g. request, registration, qualification, preferred segmentation,
disqualification, development (roadmap), phase out (roadmap))
➢ Customers can decide what vendor data is maintained in SLP and what data is maintained in ERP.
➢ It is recommended to use SLP for supplier maintained data and use the ERP for all the other data like accounting and control data
➢ SLP is designed to replicate entered/maintained data into MDG-S staging area, for processing (review/approval).
Processed vendor records can be replicated back into SLP. This scenario established a unified vendor record.
➢ SLP is also designed for integrating with the ERP without MDG-S by using the data replication framework

Customer
Ariba
Network
SAP PI
Functional Flow – Create & Sync to ERP
Legend: Roadmap Planned
SAP MDG-S or
ERP
Supplier
Self-
Registers
Create
Vendor
Approve
Qualification
Create
Vendor
Ariba
Supplier
Management
Optional
PI Layer
Exists
Create
Request
Approve
Request
Invite to
Register
in AN
Supplier
creates
AN
account
Supplier
completes
registration
Questionnaire
Approve
Questionnaire
Sync to
ERP
Sync to
ERP
Create
Qualification
Questionnaire
Completes
Qualification
Sync to
ERP
OR OR
Create
Vendor
Optional
PI Layer
Create
Vendor
Optional
PI Layer
Optional
PI Layer
Confirmation
& Vendor Id
Integration
Status =
Integrated
Duplicate
Check

Customer
Ariba
Network
SAP PI
Functional Flow – Create & Sync to SLP
SAP MDG-S or
ERP
Ariba
Supplier
Management
Exists
Create
Vendor
Duplicate
Check
Approve
Create
Vendor
Update
Vendor
Optional
PI Layer
Invite to
Register
in AN
Questionnaire
Supplier
creates
AN
account
Supplier
completes
registration
Approve
Questionnaire
Integration
Status =
Integrated
Auto sync
updates
Optional
PI Layer
Confirmation
of Update
Optional
PI Layer
Update
Vendor
Table
Approvals for vendor can be
configured in SLP, however an
external approval can also be done in
MDG-s or if workflow exist in ERP

Customer
Ariba
Network
SAP PI
Functional Flow – Supplier Updates Profile
SAP MDG-S or
ERP
Ariba
Supplier
Management
Exists
Approve
Approve
Update
Vendor
Update
Profile
Auto sync
updates
Optional
PI Layer
Approvals for profile updates can be
configured in SLP, however an
external approval can also be done in
MDG-s or if workflow exist in ERP
Update
Internal

Customer
MDG-S Data model
Everything is supported in
Phase 1 initial release,
except:
• Person, Relationships,
and Contact Partners
in Phase 2.

Customer
SLP Data model
Supplier
Bank data
Vendor Table Tax id
General Data
Internal
External
Templates
Purchasing Org
Company Code
Contacts
Project Team
Tasks
Partner Functions
Questionnaires
Regions
Categories
Certificates
Status
AN Profile
Address
Qualification Status
Preferred Status
Supported in data model but not operationalized in SLP
Business Unit

Customer
BusinessPartner Interfaces
MDG-S BusinessPartner interfaces: MDG-S has 8 messages for supplier data integration.
Inbound from ERP to Ariba SLP:
1. BusinessPartnerSUITEBulkReplicateRequest_In: (Ariba SLP phase 1)
2. BusinessPartnerSUITEBulkReplicateConfirmation_In: (Ariba SLP phase 1)
3. BusinessPartnerRelationshipSUITEBulkReplicateRequest_In: (Ariba SLP phase 2)
4. BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_In: (Ariba SLP phase 2)
Outbound from Ariba SLP to ERP:
1. BusinessPartnerSUITEBulkReplicateRequest_Out: (Ariba SLP phase 1, via polling)
2. BusinessPartnerSUITEBulkReplicateConfirmation_Out: (Ariba SLP phase 1, via polling)
3. BusinessPartnerRelationshipSUITEBulkReplicateRequest_Out: (Ariba SLP phase 2)
4. BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out: (Ariba SLP phase 2)
Persons (Contacts) integration is phase 2 development

Customer
Ariba Supplier Management integration design
Integration between SAP ERP and Ariba SLP uses
➢ MDG-S BusinessPartner interfaces on ERP
➢ Ariba provides polling client in CI-8 and CI-9 (and above) to pull pending messages from Ariba SLP.
➢ PI mediation with simple pass through (no mapping in PI – direct mapping to SLP data model) has been
tested and is supported; PI mediation is not required.
➢ For multi-ERP integration MDG is the recommendation for governance on ECC, for single ERP integration
MDG is not required.
➢ Without MDG, Data Replication Framework (DRF) must be configured to accept replication from Ariba
SLP and to replicate ERP changes back to Ariba SLP.
➢ EHP 6 (circa 2011) is minimum requirement – MDG_FND component must be release 731 or higher.

Customer
Technical Flow Diagram – Ariba SLP to Customer ECC, via optional PI
Supplier data
Customer ECC
system
Customer PI /
Middleware system
Ariba SLP System
SOAP
Adapter
Periodic
Request for
pending
replicate
messages
etc.
Message
pass
through
Supplier
data
MDG-S
Interfaces
SOAP
Adapter
Periodic
Request for
pending
replicate
messages
etc.
Quick empty
OK Response
Ariba ABAP
code for polling
pending
messages
MDG-S
Interfaces
Event Driven
Confirmation
or Replicate
message
pushed from
ECC
Replicate
message(s)
Response
MDG
Governance,
or DRF
update
Response
Response
(4) Ariba SLP updates SLP
Vendor Data in response to
Replicate or Confirmation
message from ERP system
(1) Approved updates queue
replicate messages for ECC
(2) Replicate messages
from Ariba SLP are
received and
processed as
configured
(3) When
processing is
finished, MDG or
DRF will enqueue
to Ariba SLP

Customer
Technical Flow Diagram – Customer ECC to Ariba SLP, via optional
PI
Supplier data
Customer
ECC System
Customer PI / Middleware
system
Ariba SLP system
SOAP
Adapter
Event Driven
Replicate
message
pushed from
ECC
Message
pass
through
Supplier
data
MDG-S
Interfaces
SOAP
Adapter
Event Driven
Replicate
message
pushed from
ECC
Confirmation
message
Response
Ariba ABAP
code for polling
Confirmation
MDG-S
Interfaces
Periodic
Request for
pending
confirmations,
update etc.
Quick empty
OK Response
Response
Response
(1) Update to ECC
Supplier data causes
replicate to be sent to
Ariba SLP
(2) Replicate from ECC
is applied to Ariba SLP
supplier data
(3) Confirmation is
enqueued for Customer
ECC system
(4) Confirmation is
received and processed
by customer ECC

Customer
Governance Approvals done in SLP
Supplier
Managed
Vendor Table
Supplier/Internal provides updates via
the questionnaires and forms
Approvers Review / Approve
Vendor Table gets updated
on Approval using field
mapping on questions
Messaging queue gets an update
ERP
Pull the message,
create or update vendor
Enrich vendor record by adding
ERP maintained data ex. CCODE
or PORG data
SLP gets the replication from
ERP and updates the vendor
table
1
2
3
4
5
6
7

Customer
Governance Approvals done in ERP
Vendor Table
Supplier/Internal provides updates via
the questionnaires and forms
ERP Approvers Review /
Approve
Vendor Table gets
updated on Approval from
ERP
Messaging queue gets an update
ERP Pull the message,
Trigger workflow
Enrich vendor record by adding
ERP maintained data ex. CCODE
or PORG data
SLP gets the replication from
ERP
1
2
3
4
5
6
7

Customer
Custom Fields
➢ Standard BusinessPartner fields are conveyed to & from Ariba SLP, with no mapping in CI.
➢ Replication of custom fields should be done in the usual SAP way by extending the standard
enterprise service, as detailed in the SAP “Enterprise Services Enhancement Guide” 2.0:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0bb5687-00b2-2a10-ed8f-c9af69942e5d?overridelayout=true
➢ To send/receive custom data to Ariba SLP, Ariba SLP’s extended WSDL should be used.
➢ GenericCustomField XML elements in Ariba SLP’s extended WSDL can be used in Supplier
segment, BusinessPartner segment, and also Bank and Accounting segments.
➢ Each GenericCustomField instance has its name and value as attributes.
➢ Within Ariba SLP, dotted paths can be used to map questions and default value configuration to
both standard fields and GenericCustomFields by name
➢ Ariba SLP stores GenericCustomFields persistently when mapped or received, and requires no
pre-declaration of these custom fields

Thank you
Contact information:
Maria Gammon
Product Manager
Ariba SAP, Bldg. 03,
3420 Hillview Ave
Palo Alto, CA 94304 USA
maria.elena.gammon@sap.com
Office: +1-610-661-9930
Robert Wells
Principal Staff Engineer
Ariba SAP, Bldg. 03,
3420 Hillview Ave
Palo Alto, CA 94304 USA
robert.wells@sap.com
Office: +1-650-390-1945

Customer
© 2016 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.

Ariba_SLP_and_ERP_Bi_directional_Integra.pdf

Recommandé

Recommandé

Contenu connexe

Similaire à Ariba_SLP_and_ERP_Bi_directional_Integra.pdf

Similaire à Ariba_SLP_and_ERP_Bi_directional_Integra.pdf (20)

Ariba_SLP_and_ERP_Bi_directional_Integra.pdf