SAP Quality Issue Management Rapid Deployment Solution October 2014 English SAP Quality Issue Management Rapid Deployment Solution: Software and Delivery Requirements SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany
Copyright 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 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://www.sap.com/corporate-en/legal/copyright/index.epx#trademark 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 forwardlooking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. SAP SE Public Page 2 of 9
Icons Icon Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice Typographic Conventions Type Style Description 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. Example text EXAMPLE TEXT Example 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. Example text <Example 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 9
Table of Contents Contents 1 Purpose of the Document... 5 2 General Project Prerequisites... 5 3 Technical Requirements... 5 3.1 Software product versions... 6 3.2 SAP Notes... 6 3.3 Required Content... 7 3.4 Active Business Functions Required... 8 3.5 System Landscape... 9 3.6 Connectivity... 9 3.7 Authorizations... 9 SAP SE Public Page 4 of 9
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 pre-requisites only, not the procedures to meet them. For how-to information (e.g. how to find the download area) please refer to the Quick Guide. 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 pre-assembled 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. Solution Manager set up with any relevant templates. Tool for project repository and collaboration agreed Test management tool agreed Responsibility 3 Technical Requirements This section contains technical requirements in different areas. For each requirement, the relevance for scope items of the package is provided. SAP SE Public Page 5 of 9
3.1 Software product versions The following software products and versions are required: Product Product Version Components as tested Solution Manager Component Comments SAP Solution Manager SAP Solution Manager 7.0 Enhancement Package 1 SP18 or higher Not applicable Not required Required implementatio n tool In case the SP is below 24, see SAP Note 1579267. Or SAP Solution Manager 7.1 SP01 or higher Or SAP Solution Manager 7.1 on HANA (ST 712) SP00 or higher SAP Quality Issue Management 1.0 SPS04 Not applicable SAP ERP SAP ERP 6.0 SAP ECC Server SAP ERP ECC SERVER SAP ERP Enhancement Package EHP7 FOR SAP ERP 6.0 SAP ERP ABAP Server ERP60_EHP7_CENT RAL_APPLICATION SAP NETWEAVER SAP NW 7.41 Support Package Stack Support Package Stack 6 FOR SAP NW 7.41 Not applicable 3.2 SAP Notes The following SAP Notes need to be considered: SAP Note No Content Comments Relevance 1673333 Release information for SAP Quality Issue Management This Release Information Note (RIN) contains information and references to notes for applying Support Package (SP) Stacks of SAP Quality Issue All Scope Items SAP SE Public Page 6 of 9
1771893 You want to create a quality issue on the basis of an audit action in Quality Issue Management (QIM). 1747104 Setting up system connections in SAP QIM 1865206 Enhancement of the worklist for quality issues/activities Management 1.0. Note will be implemented during deployment of RDS. You need more information about how to set up the system connections from SAP QIM to other systems like SAP ERP. Comprehensive note describing the enhancement possibilities of the worklist for issues and activities. All Scope Items Included for information purposes only. Included for information purposes only. 3.3 Required Content The following SAP Best Practices add-ons must be imported into the system: Software Component Release Version Description BP-ERP (1) 607 Use the latest version as outlined in SAP Note 1301301 1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons For more information, see the document Importing SAP Best Practices Add- Ons (ADDONINS.PDF) on the configuration DVD. This add-on contains the SAP Best Practices technical framework (for example, BC-Sets, ecatts, print programs) BP-SOLBLD (1) 70 SAP Best Practices solution builder This add-on contains the SAP Best Practices solution builder program You can find additional and detailed information in the document Importing SAP Best Practices Add- Ons (ADDONINS.PDF) on the Configuration DVD (latest available DVD via SAP Note 1240936). To download the SAP Best Practices add-ons, go to the SAP Software Download Center (SWDC) on SAP Service Marketplace: https://service.sap.com/swdc Download Installations and Upgrades A - Z Index SAP Best Practices Download the technical add-on from any Best Practices Solution Regular Updates Technical Environment SAP SE Public Page 7 of 9
The technical add-ons provided by SAP Best Practices form the technical environment required for the automated implementation of your SAP Best Practices version with the solution builder. This technical framework is continuously updated providing enhanced, fixed, or additional technical objects required for the technical implementation process. SAP Best Practices therefore offers updated versions of the add-ons on a regular basis. Each updated add-on replaces the previous version in your system. For more information about the currently available versions of the add-on BP-ERP and the add-on BP-SOLBLD, see SAP Note 1301301 (see also section SAP Notes and Messages of this document.) Since the solution file and the most current installation data files always correspond to the current technical add-ons, you always have to ensure the system is at the current version before you start the technical implementation of your SAP Best Practices version. The update of the technical framework has no impact on scope or business content of your SAP Best Practices version as it is described in the respective documentation. 3.4 Active Business Functions Required Functionality in this solution package requires certain business functions to be active in the SAP landscape. These business functions need to be activated: /BCV/MAIN /BCV/MAIN_1 SAP SE Public Page 8 of 9
3.5 System Landscape 3.6 Connectivity The following connectivity is required: RFC Connection from QIM to ERP system (type 3/ABAP) RFC Connection from QIM to ERP system (type H/ABAP-HTTP) RFC Connection from ERP to QIM system (type 3/ABAP) See also SAP Note 1747104 (Setting up system connections in SAP QIM) and administrators guide of SAP Quality Issue Management (available at help.sap.com/qim100 Installation and Upgrade Information Administrators Guide). 3.7 Authorizations The following authorizations are required: SAP_QIM_COORDINATOR (full authorizations within QIM application) Authorizations for QIM customizing (No QIM-specific roles are supplied) Optional: SAP_BCV_ADMIN and SAP_BCQ_ADMIN2 (Administration of Business Context Viewer) SAP SE Public Page 9 of 9