Before sharing an

Architecture Review deck

with customers:
1. 1. Remove the slide
notes that are internal
facing instructions on
how to complete the
slides and what to talk
about when showing
the slide.
2. Replace all the
text in red with
customer-specific
information
<Customer> Architecture Review 3. Remove these
post-it notes!
1. The “Slide Notes” have helpful
<Facilitator’s Name>, SAP Ariba
Architecture Review started on <Date> information on what discussion each slide
should drive and how each template slide
INTERNAL
should be updated to tailor it for your
customer’s Architecture Review.
<Customer> logo
Agenda

SAP Ariba Implementation Project Overview

 Recap of Project Parameters

<Customer>’s Existing Technology Landscape

 <Customer>’s Technology Rules, Policies, and Other Initiatives

Technology Landscape Diagrams Illustrating SAP Ariba Solutions

 Realm Strategy

Business Processes with Integration Scope

Key Deployment Items

Open and Closed Architecture Review Items

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 2

SAP Implementation Project Overview
SAP Ariba Implementation Project Overview

<Share a few words about the customer. What do they do? What’s their business?>
– <Customer> has existing implementations of the following SAP Ariba solutions
▫ <List of SAP Ariba solutions>
– <Customer> is newly implementing these SAP Ariba solutions
▫ <List of SAP Ariba solutions>

The parties involved in this implementation project are

 <Customer>
 SAP Ariba
 <Implementation partner(s)>
 <Teams representing third-party software>

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 4

Recap of Project Parameters

<Implementation methodology / Agile?>

Initial Phase: <Date> Next Phase: <Date> Next Phase: <Date>

<Phase driver: system <Phase driver: system <Phase driver: system

functionality or functionality or functionality or
product, geographies, product, geographies, product, geographies,
spend categories, spend categories, spend categories,
targeted supplier targeted supplier targeted supplier
categories, indirect categories, indirect categories, indirect
versus direct, etc?> versus direct, etc?> versus direct, etc?>

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 6

<Customer>’s Existing Technology
Landscape
<Customer>’s Existing Technology Landscape

<Customer>’s ERP system<s> is <ERP system type>

 <Instances in landscape: Test, Prod, etc>
 <Version> <For SAP: SAP_APPL and SAP_BASIS>
 <Any additional information the customer deems is relevant and important. For instance, highly customized>

<Customer>’s middleware system<s> is <middleware system type>

 <Instances in landscape: Test, Prod, etc>
 <Version> <For SAP: SAP_APPL and SAP_BASIS>
 <Any additional information the customer deems is relevant and important. For instance, highly customized>

In addition, <Customer> has the following solutions that may have an integration impact on the SAP Ariba deployment
 <Current procurement system and how/if it will be used along side SAP Ariba solutions. For instance, SRM.>
 <Current invoice management system and how/if it will be used along side SAP Ariba solutions. For instance, OpenText.>
 <Tax solution. For instance, Vertex>
 <Receiving and/or asset management solution>
 <HR / User Data solution>
 <Remote authentication / single sign-on (SSO) solution>
 <Master data management solution. For instance, SAP MDG>
 <Reporting / data warehouse solution>

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 8

<Customer>’s Technology Rules, Policies, and Other Initiatives

<Are there> competing IT initiatives (ERP upgrades, etc) or subsequent systems to integrate with
the SAP Ariba that may compete with, delay, or impact the SAP Ariba implementation project?
 Including customer resource availability.

<Are there> maintenance or down-time windows?

 Including on-premises, hosted, and cloud solutions.

<Are there> migration windows, especially for moving to the Production system?

What are <Customer>’s rules or policies for integration between on-premises and cloud solutions?
 Specifically for HTTPS communication between on-premises systems and the SAP Ariba cloud.
 Firewall rules
 Reverse proxy

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 9

Technology Landscape Diagrams
Illustrating SAP Ariba Solutions
Technology Landscape Diagram
<Customer> ERP Landscape

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 11

Technology Landscape Diagram – SAP Ariba Commerce Automation

Ariba Network / cXML integration will use <Integration Technology> integration package

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 13

Technology Landscape Diagram – SAP Ariba Applications

Legend:
Common Master data : Common Suppliers, Common commodity
code, Units of measure, Common/shared users, User-group
mappings, Currency conversion rates.
AN Transactions: Purchase order, Goods receipts, Invoices,
Payment remittances
Strategic Sourcing Suite: Sourcing, SIPM, Supplier Risk
Procurement Suite : Buying & Invoicing and Invoice Management

Key points:
- Master data is never stored on the Ariba network (they have
users, but are treated separately)

**
- Transactional Data need not be strictly web-services based, there
are file channel options too (but are limited such as RTBC,
comments and attachment exports etc.)
- SAP PI/PO is not strictly required for all application transaction
integration, direct connectivity can be used wherever feasible

SAP Ariba Applications master and transactional data integration will use <Integration
Technology> integration package

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 14

SAP Ariba Cloud Applications Realm Setup

Key points:
-- Test and Production sites are all on the same code stack, any new release is available on both of them simultaneously
- Any non-production Ariba site is denoted with a suffix of “-T”
- An SAP ARIBA account consists of a pair of realms (Strategic sourcing; Buying and invoicing) and a Buyer Network account.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 15
SAP Ariba Cloud Applications Realm Setup – With Supplemental Realm

Key points
- Test, Prod and Supplemental sites are all on the same code stack, any new release is available on all of them simultaneously
- Any non-production Ariba site is denoted with a suffix of “-T”
- Supplemental sites are denoted with a suffix of “-S-T” ; But corresponding ANID would have “-T”
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 16
Business Process with Integration Scope
Business Processes with Integration Scope - Sourcing

• Sourcing Request
• Awards
• Product Sourcing with BOM (Bill of Materials)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 18

Business Processes with Integration Scope - Contracts

• Contract Line Item Document (CLID – Outline Agreement from ERP)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 19

Business Processes with Integration Scope – Supplier Management

• SLP - Supplier Record and Profile Questions

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 20

Business Processes with Integration Scope – Purchasing

• Purchase Orders
• New, Change, and Cancel
• Service POs
• “Framework” or Blanket POs, including Releases
• Order Confirmation
• Advance Ship Notice
• Goods Receipt
• Service Entry Sheets
• Service Entry Sheet Responses

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 21

Business Processes with Integration Scope – Purchasing (Direct / Supply
Chain)

• Forecast Collaboration • Supplier Managed Inventory (SMI)

• Forecast • Scheduling Agreement
• Forecast Commitment • Inventory
• Subcontracting Collaboration • Demand
• Subcontract Purchase Orders • Min/Max Level
• Component Shipment • Schedule Lines
• Component Receipt • Returns Processing
• Component Consumption • Return PO
• Production Execution Visibility • Return Shipment
• Scheduling Agreement Collaboration • Delivery Receipt
• Vendor Consignment Collaboration • Manufacturing Visibility
• Consignment Purchase Orders • Quality Collaboration
• Consignment Withdrawals / Stock Transfer
• Consignment Settlement

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 22

Business Processes with Integration Scope – Accounts Payable / Finance

• Invoicing
• PO-based
• Non-PO invoices
• Invoice Against Contract
• Credit Memos – Header, Line, and Negative Invoices
• Debit Memos
• Invoice Status Update
• Scheduled Payment Information
• Payment Remittance
• Ariba Payables
• Discount Proposals and Responses
• Supply Chain Finance
• Ariba Pay

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 23

Business Processes with Integration Scope – Visibility/Analysis

• Transactional Reporting Data

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 24

Key Deployment Items
Key Deployment Items

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 26

Open and Closed Architectural Review
Items
Open and Closed Items

Open Items:

Closed Items:

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 28

Thank you.
Contact information:
<F name L name>
<Title>
<Email Address>
<Phone number>

Partner logo
Appendix