SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
Public

SAP Best Practices SAP Solution Manager Template Description
© 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. The information contained herein may be changed without prior notice.
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 and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
© SAP SE Public Page 2 of 9

SAP Best Practices SAP Solution Manager Template Description
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Type Style Description
Example text
Example text
EXAMPLE TEXT
Example text
EXAMPLE TEXT
Example text
<Example text>
Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation.
Emphasized words or phrases in body text, titles of graphics and tables.
Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
Keys on the keyboard, for example, function keys (such as F2 ) or the ENTER key.
Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© SAP SE Public Page 3 of 9

SAP Best Practices
Technical Name of
Template
Available as of
SAP Solution Manager
Content Add-On Release
Industry
Business Variant
Line of Business
Country or Region
Product Releases
RDS_ARI_NW740V6
ST-RDS 100 (latest support package)
No restriction
No restriction
LOB Procurement
No restriction
SAP ERP 6.0 EhP7
SAP NetWeaver 7.4 EhP0 (V7.40 SPS05 recommended)
Ariba Network Adapter for SAP NetWeaver CI-3 (Cloud
Integration 3.0)
SAP Business Suite Add-On ARBFNDI1 or ARBFNDI2 (as of SAP_ABA Release 7.02), ARBERPI1
You have set up your system landscape according to the Package Configuration Guide , which you can find attached to SAP Note 2029722
( http://service.sap.com/sap/support/notes/2029722 ).
With this SAP Solution Manager template, you can perform the implementation of the Ariba
Network Integration for SAP Business Suite rapid-deployment solution.
This rapid-deployment solution connects your on-premise SAP Business Suite securely and reliably to the Ariba Network. You will benefit from seamless integration for the procure-to-pay process and Ariba Procurement Content.
• Easy and quick implementation of the integration to the Ariba Network based on predefined content for procure-to-pay process
• Lower TCO based on predefined configuration
• Paperless transactions
• Reduction of errors caused by manual steps
• Increase of the number of business documents processed fully electronically
• Reduction of the cost of goods and of missed sales opportunities
The business scope supported by this RDS includes:
• Purchase Order and Invoice Automation
• Discount Management integration
• Ariba Procurement Content Integration
For Purchase Order and Invoice Automation as well as for Discount Management Integration you can choose between the following technical connectivity options between SAP ERP and
Ariba:
© SAP SE
SAP Solution Manager Template Description
Public Page 4 of 9

SAP Best Practices SAP Solution Manager Template Description
• Web Service based direct connectivity, without middleware
• Web Service based connectivity with SAP Process Orchestration
• Web Service based connectivity with Hana Cloud Integration
• IDOC based connectivity with SAP Process Orchestration
You can select your favorite connectivity setup via the respective Solution Packages when creating your implementation project. See the table below for the assignment of Solution
Packages to connectivity alternatives.
In order to achieve an optimal fit to your technical requirements the Solution Manager template supplies nine business processes for your use, based on your selection from the four possible connectivity alternatives:
For Web Service based direct connectivity, without middleware :
ARA - PO & Invoice Automation - Web Service based connectivity without middleware (direct)

Covers purchase order and invoice automation between Ariba Network and SAP
Business Suite using SAP Business Suite Add-On and web services framework for direct SAP Business Suite connectivity.

Handles the integration of all necessary business documents: Purchase Order,
Purchase Order Change, Order Confirmation, ASN, Goods Receipt, Supplier-initiated
Invoice, ERP-initiated Invoice, Payment Run
ARJ - Discount Management - Web Service based connectivity without middleware (direct)

Covers integration for discount management between Ariba Network and SAP
Business Suite, based on same connectivity as ARA

Buyer agrees with the supplier on a specific discount by using "discount professional" functionality on the Ariba Network

Based on the discount agreement the Payment run is adjusted automatically on buyer's ERP systems
For Web Service based connectivity with SAP Process Orchestration :
ARB - PO & Invoice Automation - Web Service based connectivity with SAP Process
Orchestration

Technical alternative to ARA: Covers purchase order and invoice automation between Ariba Network and SAP Business Suite using SAP Business Suite Add-On, web services framework for SAP Business Suite connectivity, and SAP NetWeaver
Process Orchestration.

Handles the integration of all necessary business documents: Purchase Order,
Purchase Order Change, Order Confirmation, ASN, Goods Receipt, Supplier-initiated
Invoice, ERP-initiated Invoice, Payment Run
ARK - Discount Management - Web Service based connectivity with SAP Process
Orchestration

Covers integration for discount management between Ariba Network and SAP
Business Suite, based on same connectivity as ARB

Buyer agrees with the supplier on a specific discount by using "discount professional" functionality on the Ariba Network

Based on the discount agreement the Payment run is adjusted automatically on buyer's ERP systems
For Web Service based connectivity with Hana Cloud Integration :
© SAP SE Public Page 5 of 9

SAP Best Practices SAP Solution Manager Template Description
ARS - PO & Invoice Automation - Web Service based connectivity with Hana Cloud
Integration

Technical alternative to ARA, ARB: Covers purchase order and invoice automation between Ariba Network and SAP Business Suite using SAP Business Suite Add-On and Hana Cloud connectivity service

Handles the integration of all necessary business documents: Purchase Order,
Purchase Order Change, Order Confirmation, ASN, Goods Receipt, Supplier-initiated
Invoice, ERP-initiated Invoice, Payment Run
ART - Discount Management - Web Service based connectivity with Hana Cloud Integration

Covers integration for discount management between Ariba Network and SAP
Business Suite, based on same connectivity as ARS

Buyer agrees with the supplier on a specific discount by using "discount professional" functionality on the Ariba Network

Based on the discount agreement the Payment run is adjusted automatically on buyer's ERP systems
For IDOC based connectivity with SAP Process Orchestration :
AR1 - PO & Invoice Automation - IDOC based connectivity with SAP Process Orchestration

Technical alternative to ARA, ARB, ARS: Covers purchase order and invoice automation between Ariba Network and SAP Business Suite using Ariba Adapter for
SAP NetWeaver Process Orchestration, and IDOCs + BAPIs for SAP Business Suite connectivity.

Handles the integration of all necessary business documents: Purchase Order,
Purchase Order Change, Order Confirmation, ASN, Goods Receipt, Supplier-initiated
Invoice, ERP-initiated Invoice, Payment Run

Also handles Service Orders and Service Entry Sheets
AR6 - Discount Management - IDOC based connectivity with SAP Process Orchestration

Covers integration for discount management between Ariba Network and SAP
Business Suite, based on same connectivity as AR1

Buyer agrees with the supplier on a specific discount by using "discount professional" functionality on the Ariba Network

Based on the discount agreement the Payment run is adjusted automatically on buyer's ERP systems
For all connectivity alternatives you can choose in addition:
AR2 - Ariba Procurement Content Integration

Covers best practice and guide for the Ariba Procurement Content integration via
Open Catalog Interface OCI (punch-out) to SAP ERP.

Enables creation of purchase order requisition based on Ariba procurement content
(Seller Catalog content).
© SAP SE Public Page 6 of 9

SAP Best Practices SAP Solution Manager Template Description
The following table shows which business processes are integrated and can therefore be combined, and which Solution Packages are assigned to the connectivity alternatives.
Combination of Business
Processes
Connectivity
Alternative
Implementation
Conditions -
Required
Solution
Package Name
ARA, ARJ, AR2
ARB, ARK, AR2
ARS, ART, AR2
AR1, AR6, AR2
Web Service based direct connectivity, without middleware
ARA
Web Service based connectivity with SAP
Process
Orchestration
Web Service based connectivity with Hana
Cloud
Integration
IDOC based connectivity with SAP
Process
Orchestration
ARB
ARS
AR1
Ariba Network
Integration for
SAP Business
Suite RDS - direct connectivity_V6
Ariba Network
Integration for
SAP Business
Suite RDS - PI mediated_V6
Ariba Network
Integration for
SAP Business
Suite RDS - HCI mediated_V6
Ariba Network
Integration for
SAP Business
Suite RDS -
IDOC-based_V6
You have to create an implementation project to organize your work in SAP Solution Manager
(SOLAR_PROJECT_ADMIN).
To select the rapid-deployment solution within the implementation project, carry out the following steps in transaction SOLAR_PROJECT_ADMIN in the SAP Solution Manager system.
1. Go to the Scope tab.
2. Select the rapid-deployment solution:

If the system uses SAP Solution Manager 7.0 (ST 400) or SAP Solution Manager 7.1
(ST 710) < SP05: a. Select the Template Selection sub-tab by clicking the hyperlink for further information. b. Search for the template RDS_ARI_NW740V6.

If the system uses SAP Solution Manager 7.1 (ST 710) (at least SP05):
© SAP SE Public Page 7 of 9

SAP Best Practices SAP Solution Manager Template Description a. Select the Solution Package sub-tab by clicking the hyperlink for further information. b. Search for the appropriate solution package.
Ensure that SAP Note 1687765 (Robomate) is implemented in SAP Solution
Manager to be able to see the Solution Package sub-tab. This is a mandatory step to be carried out in the SAP Solution Manager 7.1 (ST 710) SP05 upgrade.
3. Save your project.
4. A dialog box for the mapping of the Logical Components is displayed. Adjust the chosen logical component via F4 help if needed. For more information, see the Quick Guide section Preparation of Logical Components Used in Solution Manager Implementation
Project .
The dialog box is only displayed if technical objects have been assigned to the project, which are managed by Logical Components. If the project only has documentation assignments, the dialog box is not displayed.
In general, there are several deployment options depending on the solution package. If you want to implement several solution packages at a time you may have a mixture of deployment options:

SAP Solution Manager only:
Activation content for SAP Best Practices solution builder is not provided or using
SAP Best Practices solution builder in the development system is not possible.
SAP Solution Manager content is provided for each solution package.

Combined use of SAP Solution Manager and SAP Best Practices solution builder:
Use SAP Best Practices solution builder to accelerate the configuration during the complete implementation which is controlled by SAP Solution Manager.
For more information, see the Package Configuration Guide for the solution package attached to SAP Note Note 2029722
( http://service.sap.com/sap/support/notes/2029722 ).
Meeting the requirements according to the Software and Delivery Requirements document
(accessible via the Step-by-Step Guide), the project team can start with the installation and configuration activities of the solution package in SAP Solution Manager.
1. Conduct blueprinting (transaction SOLAR01)

Scope the business processes of your solution package

Activate Business Functions assigned to the solution package
2. Conduct implementation (transaction SOLAR02)
Configure your solution package. To avoid redundant configuration see the Prerequisite
Matrix.
The Prerequisites Matrix indicates which configuration building blocks, and hence related configuration guides, have to be followed in which sequence to configure the respective business process and to avoid redundant work in
SAP Solution Manager.
© SAP SE Public Page 8 of 9

SAP Best Practices SAP Solution Manager Template Description
The Prerequisites Matrix can be found in the Scope Item Fact Sheets within the Step-by-Step Guide .
To prepare SAP Best Practices solution builder with solution file and installation data you have several options:

Using the scoping information of SAP Solution Manager to prepare SAP Best
Practices solution builder
If the solution package only consists of one solution file, in SAP Solution Manager
(transaction SOLAR01 or SOLAR02), choose menu entry Utilities(M)

Pass
Data to Solution Builder.
For this option, you are required to configure WebServices in advance.

Using the preparation described in the appropriate sections of the Quick Guide.

Using the Download Solution & Data from Web button in SAP Best Practices solution builder Solution Editor view
3. For life-cycle reasons, document all changes made to the delivered solution package content in SAP Solution Manager.
4. Continue with test and training using SAP Solution Manager content and techniques.
5. Go live and transfer implementation results into the SAP Solution Manager solution directory.
For more information about SAP Solution Manager (inclusive system administration and implementation aspects described in chapters below), see the
SAP Library documentation for SAP Solution Manager at http://service.sap.com/solutionmanager .
© SAP SE Public Page 9 of 9