Ariba Procure-to-Pay Integration rapiddeployment

Transcription

1 September 2015 English Ariba Procure-to-Pay Integration rapiddeployment solution: Software and Delivery Requirements SAP SE Dietmar-Hopp-Allee Walldorf Germany Document Revisions Date 0 May 11, July 29, August 17, 2015

2 Copyright 2015 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 for additional trademark information and notices. SAP SE Public Page 2 of 7

3 Icons Icon Meaning Caution Note Recommendation Syntax External Process Business Process Alternative/Decision Choice Typographic Conventions Type Style Description 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. text EXAMPLE TEXT text 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. EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. text < text> 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 7

4 Table of Contents Contents 1 Purpose of the Document General Project Prerequisites Technical Requirements Software product versions SAP Notes SAP Solution Manager and SAP Solution Manager Content Add-On Connectivity Authorizations... 7 SAP SE Public Page 4 of 7

5 1 Purpose of the Document This document contains all information to: Validate that key prerequisites such as software components and versions match the customer situation. Check that all prerequisites for a customer implementation are in place Check that correct content, tools, and skills are in place before the project starts. The document will list different kinds of requirements on package level if they are valid for all Scope Items included in the package. For requirements valid for certain scope items only, these scope items are mentioned. The document contains prerequisites only, not the procedures to meet them. For how-to information (e.g. how to find the download area) please refer to the Configuration Guide Getting Started attached to the SAP Note. 2 General Project Prerequisites The following prerequisites need to be in place before an implementation project can start. Prerequisite Kick off and workshop dates, location, and attendees agreed team allocated with correct skills and training in place Project sponsors and stakeholder identified Hardware fully commissioned Software licenses in place Infrastructure team can respond to requests quickly enough e.g. CSS notes, BW content, patches, user requests, authorization changes and transports User interfaces agreed e.g. SAPGUI, NetWeaver Business Client, or Portal Remote access is in place for SAP consultants and SAP Active Global Support Decision made whether preassembled delivery will be used Decision made whether SAP Best Practices Solution Builder will be used to activate content. Decision made whether Solution Manager will be used. Manager set up with any relevant templates. Tool for project repository and collaboration agreed Test management tool agreed 3 Technical Requirements Solution Responsibility SAP SE Public Page 5 of 7

6 3.1 Software product versions The following software products and versions are required: Product Product Version Solution Manager Component Comments Relevance SAP ERP SAP NetWeaver PI Ariba Downstream OnDemand Ariba Integration Toolkit SAP Solution Manager ERP 6.0 and higher PI 7.31 and higher Ariba 13s and higher ITK version for Cloud Integration 5.0 provided via connect.ariba.com SAP Solution Manager 7.1 Enhancement Scope item: ARX Scope item: ARM, ARW 3.2 SAP Notes The following SAP Notes need to be considered: SAP Note No Content Comments Relevance General information on Ariba Procure-to-Pay Integration rapiddeployment solution 3.3 SAP Solution Manager and SAP Solution Manager Content Add-On For the implementation of the solution package, SAP Solution Manager is recommended. Product Product Version Comments SAP Solution Manager SAP Solution Manager 7.0 Enhancement Package 1 SP18 or higher Or If using SAP Solution Manager 7.0 with SP below 24, see SAP Note SAP SE Public Page 6 of 7

7 SAP Solution Manager 7.1 SP01 or higher Or SAP Solution Manager 7.1 on SAP HANA (ST 712) SP00 or higher For SAP rapid-deployment solutions, implementation content is available in SAP Solution Manager templates. The SAP Solution Manager template for this solution package is in the ST-RDS 100 content add-on. You can download the latest available ST-RDS 100 content add-on from SAP Software Download Center on SAP Service Marketplace at service.sap.com/swdc. For more information about downloading and installing ST-RDS 100 content add-ons, see SAP Note and SAP Note respectively. In the ST-RDS 100 content add-on, access the template in the following way: If you have SAP Solution Manager 7.1 SP04 or lower, select the template ID and template name in the table below. If you have SAP Solution Manager 7.1 SP05 or higher, select the solution package names in the table below. Template ID and Template Name Solution Package Name RDS_P2P_ARIBA13SV3 - Ariba P2P Integration rapid-deployment solution_v3 Ariba P2P Integration rapid-deployment solution_v3 3.4 Connectivity Please refer to the building block configuration guides of the respective scope items as connectivity requirements vary with the scope item. 3.5 Authorizations The ZMASTER_DATA role contains all the required authorizations Please refer to the configuration guide getting started or the building block configuration guides of the respective scope items as authorization requirements vary with the scope item. SAP SE Public Page 7 of 7