SAP Branch Agreement Origination V3.703: Software and Delivery Requirements

Transcription

1 RDS BAO V3.703 May.2015 English Branch Agreement Origination V3.703: Software and Delivery Requirements SE Dietmar-Hopp-Allee Walldorf Germany Document Revisions Date

2 Copyright 2015 SE or an 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 SE or an affiliate company. and other products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SE (or an affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SE or an affiliate company for informational purposes only, without representation or warranty of any kind, and SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SE or 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, 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 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 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. SE Public Page 2 of 10

3 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. SE Public Page 3 of 10

4 Table of Contents Contents 1 Purpose of the Document General Project Prerequisites Technical Requirements Software Product Versions Notes Solution Manager Content Add-On Activation Content Active Business Functions Connectivity SE Public Page 4 of 10

5 1 Purpose of the Document This document contains all information to: Validate that key prerequisites such as software products 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 lists 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 configuration guides. 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. GUI, Netweaver Business Client or Portal Remote access is in place for consultants and Active Global Support Decision made whether pre-assembled delivery will be used Decision made whether 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. SE Public Page 5 of 10

6 3.1 Software Product Versions The following software products and versions are required: Product Product Version Components Solution Manager Logical Componen t Comment s Relevanc e CRM EHP3 FOR CRM 7.0 SPS06 FSPOT 400 SP01 NETWEAVE R NETWEAVE R 740 SPS08 AS JAVA USAGE TYPE PI GWJPO 7.40 INTEGRATION VISIBILITY 7.40 NETWEAVER 7.4 Enterprise Services Repository NETWEAVER 7.4 PI Adapter Engine (Java EE) XI ADMIN 7.40 XI TOOLS 7.40 PI SCP BUILD TOOLS 7.40 PI SCP BUILD TOOLS 7.40 ESM BKG INTGRTN 1.0 SP00 ESM INTEGRATION 3.0 SP03 XI_CNT_FSPOT 400 SP00 XI CONTENT BASIS 7.40 XI CONTENT BBPCRM 5.0 SP17 XI CONTENT CRM ABAP 7.13 SE Public Page 6 of 10

7 NETWEAVE R NETWEAVE R 740 SPS08 AS JAVA USAGE TYPE BPM SP06 XI CONTENT _ABA 740 BPEM ACCELERATED 7.40 BPEM BASE 7.40 BPEM BUILD 7.40 BPEM COLLABORATION 7.40 BPEM CONTENT 7.40 BPEM CORE 7.40 BPEM FACADE 7.40 BPEM HUMAN INTERFACE MGMT 7.40 BPEM METAMODEL BASIC LIB 7.40 BPEM NWA PLUG INS 7.40 BPEM PORTAL CONTENT 7.40 BPEM WEBDYNPRO UIS 7.40 BPEM CU UI 7.40 BRMS BASE 7.40 BRMS BUILD TOOL 7.40 BRMS CORE 7.40 BRMS FACADE 7.40 BRMS WEBDYNPRO UIS 7.40 BUSINESS RULES SE Public Page 7 of 10

8 Solution Manager Content Solution Manager Best Practices Add-on and Best Practices Solution Build Add-on ST-RDS 100 plus latest SP level Solution Manager 7.1 MONITORING 7.40 CU BASE WD EXTENSIONS 7.40 FROMS INFRASTRUCUR E 7.40 NETWEAVER 7.4 Composition Platform TM WORK LIST UI 7.40 ST-RDS BP-CANW (1) BP-SOLBLD (1) BP-CRM (1) (1) Use the latest version as outlined in Note Release Strategy for Best Practices Package ABAP Add-ons Further documentation, how to download Best Practices, see: Notes The following Notes need to be considered: Note No Content Comments Relevance This Note contains critical information for implementing the Branch Agreement Origination rapiddeployment solution V Set Type correction for the Category Before you start the activation of the related Best Practices scope, check the latest versions of this Note. All Scope Items SE Public Page 8 of 10

9 BASE_FS_LOAN Differentiation Period getting set from Guided Flowalthough switch 'crm_fs_nb_bcq_1' is not ON Dump during BRF+ mapping table upload XI runtime: XI protocol PARSING GENERAL Configuration of the Web service runtime 3.3 Solution Manager Content Add-On For the implementation of the solution package, a Solution Manager system is recommended. For rapid-deployment solutions, implementation content is delivered via Solution Manager templates. Template ID and Template Name Solution Package Name(s) BAO703V3 - Branch Agreement Origination RDS_V3 Branch Agreement Origination RDS_V3 The latest available ST-RDS 100 content support package can be downloaded from the Software Download Center on Service Marketplace at service.sap.com/swdc. 3.4 Activation Content The following content is required: Product Product Version Components as tested Comments Relevance Best Practices Configuration Content (for CRM and NetWeaver) BP-CRM 713Vx BP-CANW 740Vx BP-SOLBLD 70Vx Always use the latest available versions as outlined in Note Add-ons containing configuration content (only necessary to be implemented in the system which is used for the initial content activation (i.e. Sandbox or Development System). All Scope Items SE Public Page 9 of 10

10 3.5 Active Business Functions Functionality in this solution package requires certain business functions to be active in the landscape. These business functions need to be activated: Product Business Function Configuration or Data required Relevance CRM CRM_MKT_PERMISSION CRM_PERFORMANCE CRM_FS_PERF_1 CRM_FS_NBRNWL_1 CRM_INF_1 CRM_PERFORMANCE_2 CRM_TCI_1 CRM_WFI_FILTER_1 UI_FRW_1 UI_FRW_1_DOCU 3.6 Connectivity The following connectivity is required: Integration Point Product Type Master Data Loan Master Data CRM and Banking Service CRM and Banking Service PI PO SE Public Page 10 of 10