Rds Atp Scm70 Quick Guide en Xx

SAP SCM 7.0 ERP 6.0 EhP4 June 2011 English

Quick Guide for Implementing SAP SCM Rapid-Deployment Solution for Global Available-to-Promise Check

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany


© SAP AG of 38

Copyright

© 2010 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG 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 AG of 38

Icons Icon Meaning

Caution

Example

Note

Recommendation

Syntax

For your information

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 Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT 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.

Example text 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 Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.


© SAP AG of 38

Contents 1 About this Quick Guide ....................................................................................... 6

1.1 Solution Overview .............................................................................................. 6 2 Implementation Methodology .............................................................................. 7

2.1 SAP SCM Rapid-Deployment Solution for Global Available-To-Promise Check - Scope Options.................................................................................................... 7

2.2 SAP SCM Rapid-Deployment Solution for Global Available-To-Promise Check - Content Implementation Variants ........................................................................ 7

3 SAP System Requirements (Administrator)......................................................... 8

3.1 SAP Software Component Installation Check ..................................................... 8 3.2 Required SAP Software Components ................................................................. 8

3.2.1 SAP SCM Software Components ...................................................................... 10 3.2.2 SAP ERP Software Components ...................................................................... 10 3.2.3 SAP Solution Manager ...................................................................................... 11

3.3 Receiving the Software at the Correct SP Level ................................................ 12 3.4 Required SAP Notes and Messages ................................................................. 12 3.5 Troubleshooting ............................................................................................... 13 3.6 Related Documentation .................................................................................... 13

4 System Preparation for SAP RDS Implementation (Administrator/Consultant) ... 14

4.1 Installation of the SAP Best Practices Add-On .................................................. 14 4.2 Installation of the SAP Best Practices Solution Builder ...................................... 14 4.3 General Client Settings ..................................................................................... 15

4.3.1 Creating User for Activation of Rapid-Deployment Solution Content .................. 15 4.3.2 Deselecting Activation Links in BC Sets ............................................................ 17 4.3.3 SAP Scripting ................................................................................................... 17 4.3.4 Set Default Timeout for HTTP and HTTPS Services .......................................... 18

4.4 Prepare System User for Content Activation ..................................................... 18 4.4.1 SAP Software Change Registration (SSCR): Developer Key ............................. 18 4.4.2 Activation Language ......................................................................................... 19 4.4.3 User Settings for Activation ............................................................................... 19 4.4.4 Deactivate Info Dialog Box on Dynpro Size Check ............................................ 19 4.4.5 Unicode Settings .............................................................................................. 20 4.4.6 Allow GUI Scripting ........................................................................................... 20 4.4.7 Set Decimal Notation and Date Format ............................................................. 20

5 Implementation of Rapid-Deployment Solution Business Content (Consultant) . 22

5.1 Installation of Preconfigured Scenarios of the SAP Best Practices Baseline Package for Manufacturing of SAP ERP ........................................................... 22

5.2 Installation of Language/Country-Specific Content ............................................ 22 5.3 Rapid-Deployment Solution Content Installation Variants .................................. 22

5.3.1 Manual Implementation ..................................................................................... 22


© SAP AG of 38

5.3.2 Solution Manager Template-Based Implementation .......................................... 23 5.3.3 Automated Implementation Using SAP Best Practices Solution Builder ............. 26 5.3.3.1 Getting Files for Content Activation ................................................................... 26 5.3.3.2 Import Solution Scope File................................................................................ 27 5.3.3.3 Maintain User Settings: Path to Installation Data............................................... 28 5.3.3.4 Maintain User Settings: Path to Documentation ................................................ 28 5.3.3.5 Maintain Solution Settings: Select Languages .................................................. 29 5.3.3.6 Scope the Solution ........................................................................................... 29 5.3.3.7 Upload Installation Data ................................................................................... 29 5.3.3.8 Personalize your Solution ................................................................................. 30 5.3.3.9 Download Installation Data ............................................................................... 31 5.3.3.10 Create Characteristic Combinations – Load Data From File .......................... 32 5.3.3.11 Activating Solution........................................................................................ 32 5.3.3.12 Manual interaction during Installation of Building Blocks ............................... 34 5.3.3.13 Processing General Errors during Installation ............................................... 34 5.3.3.14 Processing Error Inbound Queue Blocked “Version 000 not found” ............... 36

5.3.3.15 Processing Error in Task Maintain Calendar of Building Block S66 Transportation and Shipment Scheduling for Global Available to Promise Check............. 36 5.3.3.16 What to do when APO client is not the BW client? ........................................ 38 5.3.3.17 Error: No valid version exists for for planning area ‘9ADP01’......................... 38

5.3.3.18 Error: Display Product Allocation Situation – Not all characteristics are displayed 38


© SAP AG of 38

Quick Guide Implementing the SAP SCM Rapid-Deployment Solution for Global Available-To-Promise Check 1 About this Quick Guide This Quick Guide helps consultants and customer project members to implement the SAP SCM rapid-deployment solution for global available-to-promise (global ATP) check. The guide focuses on the technical implementation aspects and usage of the SAP Solution Manager and the SAP Best Practices Solution Builder add-on. The document mentions all required steps for a successful implementation of the SAP SCM rapid-deployment solution for global available-to-promise check and directs you to more detailed documentation if necessary.

The System Landscape Prerequisites section lists all system pre-requisites that have to be fulfilled by customers before the implementation of the rapid-deployment edition can start. Installation of the required systems is not part of the SAP SCM rapid-deployment solution for global available-to-promise check delivery scope.

The Preparation Activities section explains the tasks that need to be carried out specifically for the implementation of this rapid-deployment solution.

In the Implementation section you will be guided step-by-step through the actual technical implementation process. What you actually implement and configure is subject to a previous scoping effort.

The SAP SCM rapid-deployment solution for global available-to-promise check addresses core functional needs of availability check, backorder processing and transportation and shipment scheduling in SAP Advanced Planning and Optimization (SAP APO). From a technical implementation perspective, the content of this guide is valid for the SAP SCM rapid-deployment solution for global available-to-promise check. The deployment option of the rapid-deployment solution in scope here is with integration to the customer’s existing SAP ERP backend.

1.1 Solution Overview SAP SCM rapid-deployment solution for global available-to-promise check

Is based and tested on SAP SCM 7.0 with an SAP ERP 6.0 with EHP4

Provides an accelerated deployment of the required configuration settings for global ATP

Is targeting on customers that:

o Already run sales order management scenarios in SAP ERP

o Do not use SAP SCM, but want to grow their business with global ATP in SCM

Contains SAP-SCM-specific configuration settings and SAP ERP configuration settings to enable the availability check in SAP SCM

Is delivered with two solution files:

o The leading solution for SAP SCM, that is covering all building blocks to implement in the SCM system

o A SAP ERP solution file that is delivering the integration part from a SAP ERP perspective and the necessary settings in SAP ERP to enable the availability check in SAP SCM

For testing and demo purposes, the SAP SCM rapid-deployment solution for global available-to-promise check is delivering demo data covering:

o 2 plants


© SAP AG of 38

o 14 finished goods materials

o 11 trading goods materials

o 10 customers

o 2 sales organizations

o 31 characteristic combinations for product allocation planning

o Conditions for transportation and shipment scheduling

o Rules for product and location substitution

2 Implementation Methodology Overall project guidance is provided by a specific implementation step-by-step guide for SAP SCM rapid-deployment solution for global available-to-promise check, which is a phased, delivery-oriented methodology that streamlines implementation projects for solution packages, guiding project teams through the following phases:

Discover

Start

Deploy

Run

The methodology supports project teams with templates, tools, questionnaires, and checklists, including guidebooks and accelerators to ensure the quick and pragmatic implementation of rapid-deployment solutions.

To get access to the methodology approach your SAP Consulting contact.

2.1 SAP SCM Rapid-Deployment Solution for Global Available-To-Promise Check - Scope Options

The SAP SCM rapid-deployment solution for global available-to-promise check can be operated with a basic solution scope as well with an enhanced solution scope.

The SAP SCM rapid-deployment solution for global available-to-promise check contains three scenarios:

Scenario Scenario Description

S60 Global Available-to-Promise with Product Availability Check

S61 Global Available-to-Promise with Check against Product Allocation

S62 Global Available-to-Promise with Rules-Based Availability Check

Scenario S60 Global Available-to-Promise with Product Availability Check is mandatory. Scenarios S61 Global Available-to-Promise with Check against Product Allocation and S62 Global Available-to-Promise with Rules-Based Availability Check are optional.

Automated business content activation requires a Solution Scope file for SAP ERP and SAP SCM each. The Solution Scope files are attachted to rapid-deployment solution SAP note 1577698.

2.2 SAP SCM Rapid-Deployment Solution for Global


© SAP AG of 38

Available-To-Promise Check - Content Implementation Variants

For the imlementation of the SAP SCM rapid-deployment solution for global available-to-promise check the following implementation variants are offered:

Manual implementation following configuration guides

SAP Solution Manager template-based implementation

Automated implementation using SAP Best Practices Solution Builder

3 SAP System Requirements (Administrator) This chapter summarizes the prerequisites that are assumed to be delivered by the customer, i.e. in a phase preceding the actual implementation project.

Note that the setup of the system landscape is not part of the rapid-deployment solution delivery scope.

The customer will need to provide the system landscape, i.e. install the required software components, to enable the project team to implement and configure the scope of the SAP SCM rapid-deployment solution for global available-to-promise check. During this phase SAP provides advice on aspects of the system landscape and the components required.

In addition to the following information, the SAP rapid-deployment solution’s specific implementation methodology provides an installation-related checklist covering additional aspects.

3.1 SAP Software Component Installation Check Before the rapid-deployment solution content implementation activities can be executed, the SAP project team performs a check of the software installation based on the requirements provided in the following chapters of this guide. Based on the result the project team advises the customer on any missing steps to be performed.

3.2 Required SAP Software Components The deliverables of SAP SCM rapid-deployment solution for global available-to- were developed and tested in a system landscape with specific SPS levels SPS08. If the SPS level in your system is different, there may occur errors during the activation. You may be able to perform the activation activities manually using the configuration guides, but errors may still occur.

Make sure that your system meets the minimum SPS level requirements. In case your system has an exceptional SPS level compared to the rapid-deployment solution requirements, issues might occur.

If you need a higher SPS level in your system, for example because of additional functionality than the required SPS level for the rapid-deployment solution, FIRST import and activate the rapid-deployment solution SPS levels as mentioned below, THEN upgrade your system to the higher SPS level.

The support package levels relevant for the SAP SCM rapid-deployment solution for global available-to-promise check V1.700 are listed together with the required components in the next sections.

The table lists all software required to implement and run the solution:


© SAP AG of 38

Product Product Version Component Logical Component in SAP Solution Manager*

Comments

SAP Solution Manager

SAP Solution Manager 7.0

Not applicable

Not required Required implementation tool

SAP Supply Chain Management

SAP Supply Chain Management 7.0

Global Available-to-Promise (GATP)

SAP_SCM_700

SAP ERP SAP ERP 6.0 SAP ERP 6.0 Application Server ABAP

SAP_ERP_EHP_CENTRAL_APPL

SAP ERP Enhancement Package

SAP Enhancement Package 4 for SAP ERP 6.0

Not applicable

Not required

* The logical component in SAP Solution Manager is an identifier provided by SAP for the combination of product and product version. When selecting the SAP Solution Manager template later on, the logical component provided by SAP will automatically be mapped with the logical component in the customer system landscape with the same combination of product and product version to set up access from SAP Solution Manager to the correct customer system.

For the availability check with SAP SCM 7.0, you need the following software components: SAP SCM 7.0 - SCM Server SAP SCM 7.0 - SAP LiveCache

As a prerequisite you already run the standard sales order processing in SAP ERP scenario which requires the following software component: EHP4 FOR SAP ERP 6.0 - Central Applications

© 2010 SAP AG. All rights reserved. / Page 1

For a global ATP check to be executed in the SAP SCM system, there must be an active integration model for the material/plant combination

Of course all the other data (plants, materials, stocks, …) that are needed for the check are integrated as well

Figure 1: Logical View on Data Flow


© SAP AG of 38

3.2.1 SAP SCM Software Components

SAP Supply Chain Management Server (SAP SCM Server) SAP Supply Chain Management Server (SAP SCM Server) is part of the SAP Supply Chain Management application suite. It is an advanced planning and scheduling tool that enables real-time decision support and collaborative network optimization across the extended supply chain. SAP SCM Server helps companies synchronize supply chain activities with their partners and excel to improve customer service and order fulfillment.

Embedded SAP BI SAP SCM Server is shipped with an embedded SAP Enhancement Package 1 for SAP NetWeaver 7.0 usage type BI (SAP BI) that, together with SAP liveCache, enhances the performance of forecasting and replenishment tasks.

SAP SCM Server uses the embedded SAP BI architecture to plan for technical reasons (such as using info cubes), that is, the SAP BI embedded in SAP SCM Server is not meant to be used for reporting purposes of your company.

SAP liveCache for SAP SCM SAP liveCache is based on SAP MaxDB technology and ensures the highest SAP SCM performance. SAP liveCache is SAP’s state-of-the-art memory-based computing technology for real-time, high-speed processing of large data volumes.

Related Information The SAP SCM Master Guide provides a central starting point for the technical implementation of SAP SCM. It contains all the information for the implementation of SAP SCM business processes.

You can find the most current information about the technical implementation of SAP SCM and the latest installation and configuration guides on SAP Service Marketplace at http://service.sap.com/instguides.

We strongly recommend that you use the documents available there. The guides are regularly updated.

Before SAP SCM rapid-deployment solution for global available-to-promise check can be implemented, three SAP SCM 7.0 systems (development, quality system and production system) must be installed and updated to service pack level SPS08.

To configure the SAP SCM backend system you need the SAP GUI for Microsoft Windows.

Usually required software components and SP levels are downloaded using the Maintenance Optimizer of SAP Solution Manager. If you need to download manually from SAP's Software Distribution Center in Service Marketplace please follow below given path:

Installation: http://service.sap.com/swdc Installations and Upgrades Browse our Download Catalog SAP Application Components SAP SCM SAP SCM 7.0

Support Packages: http://service.sap.com/swdc Support Packages and Patches Browse our Download Catalog

SAP Application Components SAP SCM SAP SCM 7.0 Entry by Component

3.2.2 SAP ERP Software Components Installation:

http://service.sap.com/instguides

http://service.sap.com/swdc



© SAP AG of 38

It is assumed that the customer already has the SAP ERP system installed and configured on SAP ERP EhP4. As part of implementing the rapid-deployment solution, the SAP SCM system will be integrated with the SAP ERP system.

Support Packages: http://service.sap.com/swdc Support Packages and Patches Browse our Download Catalog

SAP Application Components SAP ERP SAP ERP Enhance Package EhP4 for SAP ERP 6.0 / NW7.01 Entry by Component

Detailed information regarding the installation of Enhancement Package 4 for SAP ERP 6.0 can be found in SAP Note 1143022 Installation of Enhancement Package 4 on SAP ERP 6.0 (http://service.sap.com/sap/support/notes/1143022).

As outlined in SAP note 1064635, SPS levels for SAP ERP are synchronized throughout all Enhancement Package versions. Software components and add-ons not used within an enhancement pack should have the SP level assigned to the concurrent SPS of SAP ECC 6.0. Attached to SAP note 1386389 - SAP BAiO/BP: Stack Information/Explanation for Used Products (http://service.sap.com/sap/support/notes/1386389) an overview of all software components and their support package levels combined in the various support package stacks is given.

3.2.3 SAP Solution Manager For the implementation of this rapid-deployment solution, a SAP Solution Manager system is recommended. SAP Solution Manager in general is needed for installation and managing of maintenance certificates, Enhancement Packages and upgrades. In the context of SAP rapid-deployment solutions, implementation content is delivered via SAP Solution Manager templates.

The template content for SAP Solution Manager is tailored for the deployment of the SAP SCM rapid-deployment solution for global available-to-promise check with SAP ERP integration.

It is assumed that a productive SAP Solution Manager system (7.0 or higher) is available in the customer’s system landscape: if the customer is already using other SAP products (for example SAP ERP) then the customer should already have SAP Solution Manager in the system landscape.

For more information about SAP Solution Manager, see the SAP Library documentation for SAP Solution Manager at http://help.sap.com -> SAP Solution Manager, or at http://service.sap.com/solutionmanager.

Component Mandatory Remark

SAP Solution Manager 7.0 (or higher) ABAP

Recommended If you do not wish to use SAP Solution Manager to leverage the SAP SCM rapid-deployment solution for global available-to-promise check implementation content see chapter 5.3 Rapid-Deployment Solution Content Installation Variants


http://service.sap.com/sap/support/notes/1143022


http://help.sap.com/

http://service.sap.com/solutionmanager


© SAP AG of 38

3.3 Receiving the Software at the Correct SP Level For delivery of the software, an installation number and a corresponding license agreement are required. An S-USER is required to order software in the Software Catalog or download from SAP's Software Download Center in the SAP Service Marketplace. You can only order unrestricted SAP software. Contact the SAP contract department to ask for a physical shipment or create a customer message on component XX-SER-GEN-CONTR.

For downloading SPSs, use the Maintenance Optimizer within your SAP Solution Manager system. You can also select relevant SPs manually one-by-one via the Software Download Center:

https://service.sap.com/swdc Support Packages and Patches Browse our Download Catalog SAP Application Components:

SAP ERP SAP ERP Enhance Package EHP4 for SAP ERP 6.0

SAP SCM SAP SCM 7.0

Only the current Service Release (SR) is delivered to SAP customers / partners via the Software Download Center in the SAP Service Marketplace or via standard delivery (for example, Software Catalog). If you encounter the situation that the required SPS for correct SAP BP packages activation is based on an SPS level LOWER than the current SR, the request for the necessary SPS is handled via a customer message. For details, see SAP Note 925690 - Standard Ordering Procedures for SAP Software (http://service.sap.com/sap/support/notes/925690).

3.4 Required SAP Notes and Messages It may be that issues become apparent after the shipment of SAP SCM rapid-deployment solution for global available-to-promise check (and hence also of this document). An SAP Note exists to cover such eventualities.

Before you start the building block installation process, check the latest version of the SAP Note below to obtain updates and corrections for problems that do not become apparent until after shipment.

SAP Note Description

1577698 Rapid deployment of Global ATP check with SAP SCM (http://service.sap.com/sap/support/notes/1577698)

All SAP Notes have to be applied to the system using the SAP Note Assistant (transaction SNOTE).

All SAP Notes mentioned below need to have the implementation status Completely implemented. Note that some SAP Notes require manual action before you set them to the status Completely implemented.

Implement the following SAP Notes before proceeding with the next steps in this guide:

SAP Note Description

1060253 Problem in activating BC Sets -> check if relevant

Those SAP Notes in the overview list, which are classified as Application Software Correction (that are SAP SCM application software corrections) can already be implemented in advance, before starting with the rapid-deployment solution implementation.

https://service.sap.com/swdc




© SAP AG of 38

3.5 Troubleshooting If errors occur during the installation process, proceed as follows:

1. Check for troubleshooting notes in the step description of the Configuration Guide.

2. Check for SAP Notes on the relevant topic in the section SAP Notes in the Building Block Configuration Guide.

3. Log on to the Service Marketplace and search for problem-related SAP Notes. If the problem persists, proceed as follows:

Only if the problem relates to the rapid-deployment solution pre-configuration, open a customer message with the component SV-RDS-SCM.

If the problem is a general one, indicate the relevant application component.

3.6 Related Documentation The Master Guide SAP SCM 7.0 provides crucial information on the installation of SAP SCM 7.0. Read this guide thoroughly.

The Security Guide SAP SCM 7.0 provides an overview of the security-relevant information that applies to SAP SCM.

The Application Operations Guide SAP SCM 7.0 provides a starting point for managing your SAP solutions and keeping them up and running optimally.

To access the latest version of these guides, log on to the SAP Service Marketplace at http://service.sap.com/scm-inst SAP SCM 7.0.

http://service.sap.com/scm-inst


© SAP AG of 38

4 System Preparation for SAP RDS Implementation (Administrator/Consultant)

Before the consultant can start with the automated rapid-deployment solution content implementation the steps in the following chapter need to be performed.

4.1 Installation of the SAP Best Practices Add-On The following SAP Best Practices content add-on hasto be installed in order to use the automated installation of the SAP SCM rapid-deployment solution for global available-to-promise check:

Software Component

Release Version

BP-SCM70 700VX Always use the latest available version as outlined in SAP Note 1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons (https://service.sap.com/sap/support/notes/1301301)

Use If possible, Business Configuration Sets (BC Sets) for maintaining customizing settings and Extended Computer Aided Test Tool procedures (eCATT) for master data creation are used for SAP Best Practices. This use automates the configuration of the SAP Best Practices scenarios.

BC Sets and eCATTs were delivered as so-called add-on transport files with the SAP Best Practices ADD-ON BP-SCM BP-SOLBLD 70V4. Import this file into your SAP SCM system, if you want to make use of the automated configuration.

Procedure 1. Download the add-On BP-SCM70 BP-SOLBLD 70V4 from the Software Download Center at

http://service.sap.com/swdc Installations and Upgrades Browse our Download Catalog SAP Rapid Deployment solutions SAP SCM rapid-deployment solution for global

available-to-promise check

2. Import the SAR file using transaction SAINT into your SAP SCM system.

Result BC Sets and eCATTs are now available in your SAP SCM system and can be used in combination with the SAP Best Practices Solution Builder for automated configuration of SAP Best Practices SCM scenarios.

4.2 Installation of the SAP Best Practices Solution Builder

The following SAP Best Practices add-ons have to be installed in order to use the automated installation of this rapid-deployment solution:

Software Component

Release Version

BP-SOLBLD BP-SOLBLD 70V4

Always use the latest available version as outlined in SAP Note 1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons (https://service.sap.com/sap/support/notes/1301301)

https://service.sap.com/sap/support/notes/1301301




© SAP AG of 38

Use Use the SAP Best Practices Solution Builder to easily install the complete SAP Best Practices package or selected scenarios at minimum time.

The SAP Best Practices Solution Builder is a tool that guides you step-by-step through the installation process directly in the system.

Procedure 1. Download the Add-On BP-SOLBLD BP-SOLBLD 70V4 from the Software Distribution center:

http://service.sap.com/swdc Installations and Upgrades Entry by Application Group SAP Rapid Deployment Solutions SAP Service Parts Planning rapid-deployment solution

2. Import the SAR file using transaction SAINT into your SAP SCM system.

Result The SAP Best Practices Solution Builder has been installed in your SAP SCM system. The use of the Solution Builder is described in the section Installation of Business Content of this guide.

4.3 General Client Settings 4.3.1 Creating User for Activation of Rapid-Deployment

Solution Content

Use If you want to create a certain user to run the activation of the related rapid-deployment solution scope, please consider the following:

SAP SCM rapid-deployment solution for global available-to-promise check does not supply separate roles for customizing or setup tasks.

If necessary, you can define a separate role corresponding to your individual IMG project according to the functions provided in Role Maintenance (transaction PFCG), containing all the authorizations you need to access the corresponding IMG activities required for the rapid-deployment solution scope.

Alternatively you can use the authorization profile SAP_ALL. If this authorization does not apply to your authorization concept, you should restrict the user rights according to your internal authorization guidelines. Without the profile SAP_ALL, issues during the activation may occur and need to be solved. You can use the transaction SU53 to get information on the missing authorizations and extend the authorization data as necessary.

Directly after activation of the rapid-deployment solution content, remove the authorizations you have given to the system user that has performed the activation steps. This is for security reasons to avoid that the system user misuses the authorizations granted before.

The procedure below describes how to setup a system user necessary to activate the rapid-deployment solution-specific content.



© SAP AG of 38

Procedure 1. To carry out the activity, choose one of the following navigation options:

SAP Menu Tools Administration User Maintenance Users

Transaction Code SU01

2. On the User Maintenance: Initial screen, in the User field, enter <User-ID> and choose Create.

3. Choose the Address tab.

4. Make the following entries:

Field name User action and values Note

Last name <Last name of the user>

First name <First name of the user>

5. Choose the Logon Data tab.



Password <initial password>

User type Dialog

7. Choose the Defaults tab.



Logon language EN

Decimal notation 1.234.567,89

Date format DD.MM.YYYY

9. Choose the Roles tab.

10. Enter the user role you created that contains the necessary authorization profile.

Alternatively you can assign the profile SAP_ALL on the Profiles tab. Make sure that this corresponds to your internal security guidelines.

11. Save your entries.

Result A user to activate the rapid-deployment solution content has been created.


© SAP AG of 38

4.3.2 Deselecting Activation Links in BC Sets We recommend that you turn off the creation of activation links. By doing this, you can significantly increase activation speed and avoid errors.

Procedure 1. Choose one of the following navigation options:

SAP Menu Tools Customizing Business Configuration Sets Activation of BC Sets

Transaction Code SCPR20

2. On the Business Configuration Sets: Activation screen, choose Utilities System Settings.

3. Choose Change (Shift + F1).

4. In the Activation section, select the radio button for Do Not Create parameter.

5. Choose Enter on the information message.

6. Save your settings.

4.3.3 SAP Scripting

Use eCATTs are used to automate the activation of the SAP SCM rapid-deployment solution for global available-to-promise check configuration settings. Prior to activation, you must allow eCATT processing in the system by setting the profile parameter sapgui/user_scripting. The value for Enable or disable user scripting on the front-end must be set true.

Procedure 1. Start transaction RZ11.

2. On the Maintain Profile Parameters screen, make the following entries

Field name Description User action and values

Param. Name Profile parameter name sapgui/user_scripting

3. Choose Display.

4. On the Display Profile Parameters Attributes screen, select Change values.

5. On the Change Parameter Value screen, make the following entries.

Field name Description User action and values Note

New Value New Value for user scripting

TRUE Enable SAP Scripting

6. Choose Save.


© SAP AG of 38

When you save the change, the window closes and the current value of the parameter changes to TRUE. This change only becomes effective when you log on to the system again.

If the parameter is set in RZ11, you lose the change when you restart the server.

4.3.4 Set Default Timeout for HTTP and HTTPS Services

Use We recommended that you set the following for both services TIMEOUT and PROCTIMEOUT to 300 or 600 (seconds). The default is 60.

The values are also set using system parameters (see below section Procedure):

icm/server_port_<*> - Standard value for *: 0: http, 1 or 2: https

For example:

icm/server_port_0 = PROT=HTTP, PORT=8000, PROCTIMEOUT=300,

TIMEOUT=600

icm/server_port_2 = PROT=HTTPS, PORT=44300, PROCTIMEOUT=300,

TIMEOUT=600

Procedure 1. Start transaction RZ10.

2. On the Edit Profiles screen, enter your instance profile.

3. In the Edit Profile box, select the radio button for Extended maintenance and choose Change.

4. On the Maintain Profile screen, make the following entries

Parameter Name Description New value

Note

icm/server_port_<*> Standard value for *:

0: http, 1 or 2: https

300 or 600

Set to 300 or 600 (seconds) for TIMEOUT and PROCTIMEOUT, the default is 60

5. Choose Back

6. Choose Save.

This adaptation of these profile parameters is only necessary if you are using SAP NetWeaver Business Client.

4.4 Prepare System User for Content Activation 4.4.1 SAP Software Change Registration (SSCR):


© SAP AG of 38

Developer Key The user ID used for activation has to be registered as developer on SAP Service Marketplace (SAP Software Change Registration (SSCR)). For more information, see SAP Note 86161. The SSCR developer key is needed, because the user ID used for SAP Service Parts Planning rapid-deployment solution activation creates and changes objects from the customer name range during the SAP Rapid-Deployment Solution activation process. If the SAP Rapid-Deployment solution activation user is not registered as a developer, the automated SAP Rapid-Deployment solution activation incurs errors.

Procedure 1. Access the SAP Service Marketplace at http://service.sap.com/sscr.

2. On the SAP Software Change Registration (SSCR) start page, you get the detailed user documentation on how to proceed to get the SSCR developer key.

An SSCR developer key is a 20-character combination of digits that is queried when an SAP ERP user tries to create or change an object from the customer name range FOR THE FIRST TIME. The prompting message for the developer key appears once for each SAP ERP user; if registration is successful, this SAP ERP user is no longer prompted to enter a developer key. The SSCR developer key is generated from the installation number of the affected installation and the SAP ERP user name.

4.4.2 Activation Language Make sure that your logon language is always English (and NOT your local language) for all activation activities.

4.4.3 User Settings for Activation

For activation, we recommend that only one User ID is used to activate the rapid-deployment solution. It can be a tedious procedure to change ownership of the activation of the solution.

Make sure that you only have one single SAP GUI session running when you activate SAP Best Practices. If you run several SAP GUI sessions, some automated installation activities might run into errors.

4.4.4 Deactivate Info Dialog Box on Dynpro Size Check The dialog box Sizing conflicts may appear which may pop up during activation has to be deactivated.

Procedure 1. Log on with the user in the system.

2. Choose the first button from the right side of the Standard Tool Bar Customizing of Local Layout or type ALT + F12.

3. Select the menu item Options.

http://service.sap.com/sscr


© SAP AG of 38

4. Choose the Options tab.

5. De-select the Enable dialog box for dynpro size check checkbox.

6. Choose the OK button at the bottom.

4.4.5 Unicode Settings

Use Before each user logs on to the system for the first time, the user’s local GUI must be set to use the Unicode code page.

Procedure 1. From the SAP Logon pad, select your system ID.

2. Choose the Change Item button.

3. On the System Entry Properties dialog box, choose the Code Page tab.

4. On the Encoding dropdown, select Unicode (UTF-8).

5. Choose OK.

4.4.6 Allow GUI Scripting

Use Perform this activity so that eCATTs GUI scripts can by executed with your GUI.

Procedure 1. Choose the first button from the right side of the Standard Tool Bar Customizing of Local

Layout or type ALT + F12.

2. Select the menu item Options.

3. Choose the Scripting tab.

4. Select the Enable scripting checkbox.

5. Deselect the checkboxes Notify When a Script Attaches to a Running GUI and Notify When a Script opens a Connection.

6. Choose the OK button at the bottom.

4.4.7 Set Decimal Notation and Date Format

Use Perform this activity to set up the activation user ID.

Procedure 1. Choose one of the following navigation options:

SAP Menu System User Profile Own Data

Transaction Code SU3


© SAP AG of 38

2. Choose the Defaults tab.

3. Set Decimal Notation according to your country’s default, like 1.234.567,89.

4. Set Date Format according to your country’s default, like DD/MM/YYYY.

5. Assign your printer in the field output device (see also the section Printer Environment in this document).

6. Save your settings.

7. Log off from the system.

8. Log on to the system.

Logoff and logon are necessary since the change in the user settings only becomes effective when you log on to the system again.

9. When the complete activation procedure is finished, you may change these values as desired.

Result The decimal notation and date format have been set up according to your country format. The standard printer has been defined.


© SAP AG of 38

5 Implementation of Rapid-Deployment Solution Business Content (Consultant)

When the customer has finished with the set-up of the system landscape, the project team can start with the implementation of the rapid-deployment edition. The following chapter describes additional preparation activities that need to be carried out by the project team.

5.1 Installation of Preconfigured Scenarios of the SAP Best Practices Baseline Package for Manufacturing of SAP ERP

We assume that you already have running a SAP ERP system with sales order management in place. If you want to create a demo system environment with a new SAP ERP system you may first install the following preconfigured scenarios of the SAP Best Practices Baseline package for Manufacturing which cover the key functional area Sales of SAP ERP:

Sales Order Processing: Sale from Stock

Sales Quotation

The configuration guides can be found in the SAP Best Practices Baseline Package content library at http://help.sap.com/bp_bl604/BL_US/html/index.htm.

5.2 Installation of Language/Country-Specific Content The current available version of SAP SCM rapid-deployment solution for global available-to-promise check always comprises all languages; there are no separate rapid-deployment solution versions for different countries/languages.

Language-specific configuration and master data will automatically be installed in the SAP ERP and SAP SCM system when using SAP Best Practices Solution Builder.

For manual configuration activities, the translation is provided in the configuration guides; language-specific texts have to be maintained manually.

As far as SAP ERP integration is concerned, SAP ERP configuration and master data will be replicated from the SAP ERP system to the SAP SCM system in all maintained languages.

Typically configuration content will be installed in the master language English and a second local language. However, you have the option of installing content in additional languages.

5.3 Rapid-Deployment Solution Content Installation Variants

5.3.1 Manual Implementation Depending on which scenario you want to install, you will have to follow the correct installation sequence. For detailed information on the installation sequence of our building blocks, refer to the Prerequisites Matrix.

http://help.sap.com/bp_bl604/BL_US/html/index.htm


© SAP AG of 38

5.3.2 Solution Manager Template-Based Implementation

Checking the System Landscape in SAP Solution Manager SAP SCM rapid-deployment solution for global available-to-promise check is designed for a specific system landscape that is represented by the logical components in the SAP Solution Manager template.

By mapping the logical components to the actual physical systems in the landscape, it enables you to configure the systems directly via SAP Solution Manager.

You can also check and maintain the system landscape during the template selection. However, we recommend to maintain the system landscape up-front to the template selection in order to complete this administrative IT task before starting the business-driven content implementation.

In order to maintain the system landscape in SAP Solution Manager, in the SAP Solution Manager Easy Access menu, choose System Landscape (SMSY).

Procedure 1. Click on System Groups and Logical Components.

2. Choose Logical Components SAP SCM SCM Server.

3. Right-click on SCM Server and choose Create New Logical Components.

4. Enter the following values:

Logical Component Product in Template

Product Version

Product Instance

Name

1 ZSCM70_SCM_ SERVER_<SystemID>_ <client>

SAP SCM SAP SCM 7.0

SCM Server <Choose a name>

For SAP SCM rapid-deployment solution for global available-to-promise check with SAP ERP integration peform steps 5 - 7:

5. Open Logical Components SAP ERP ENHANCE PACKAGE Central Applications.

6. Right-click on Central Applications and choose Create New Logical Components.

7. Enter the following values:

Logical Component Product in Template

Product Version

Product Instance

Name

1 ZERP60_EHP4_ CENTRAL_APPL_ <System ID>_<client>

SAP ERP Enhancement Package

EHP4 FOR SAP ERP 6.0

Central Applications

<Choose a name>

8. In the table on the right-hand side assign your development system and client in the column Development System.

9. Repeat step 8 for your quality assurance system and optional for your training and evaluations system.

The definition should look similar to the following example (replace the example data with your own data):

Logical Product Product Product Develop- Quality Remark


© SAP AG of 38

Component Version Instance ment System

AssuranceSystem

ZSCM70_SCM_SERVER

SAP SCM SAP SCM 7.0

SCM Server RDO:901 RQO:901 SAP SCM System

ZERP60_EHP4_CENTRAL_ APPL_ <SystemID>_ <client>

SAP ERP Enhance-ment Package

EHP4 FOR SAP ERP 6.0

Central Applications

RDE:901 RQE:901 SAP ERP System

Technically, there are no restrictions regarding the use of SAP SCM rapid-deployment solution for global available-to-promise check with deviating SAP ERP release levels, as the SAP ERP part of the rapid-deployment solution installation is performed manually without eCATTs or BC sets. However, the rapid-deployment solution documentation is only provided for the recommended SAP ERP release levels.

For more information on the system landscape in SAP Solution Manager, see the SAP Solution Manager documentation in the SAP Help Portal at http://help.sap.com -> SAP Solution Manager -> SAP Solution Manager 7.0 EhP1 SP23 -> Basic Settings -> Solution Manager System Landscape.

Creating the SAP Solution Manager Project Create a project to organize you work in SAP Solution Manager.

Procedure To create a project, perform the following steps: 1. In the SAP Solution Manager Easy Access menu, choose Project Administration (transaction

SOLAR_PROJECT_ADMIN). 2. Create a new project and enter the following values:

Project Type Solution

<Enter a name> Implementation Project <leave empty>

3. Click Ok. 4. On the next screen, enter a title.

5. Choose a project language.

6. Save and confirm the message.

Templates in SAP Solution Manager assist you in performing predefined implementation projects. The template specific to the SAP SCM rapid-deployment solution for global available-to-promise check contains the content for the default implementation of the rapid-deployment solution.

http://help.sap.com/saphelp_smehp1/helpdata/en/45/59dccac2091deae10000000a155369/frameset.htm



© SAP AG of 38

Selecting the SAP Solution Manager Template

Procedure To select the template, carry out the following steps in transaction SOLAR_PROJECT_ADMIN:

1. Navigate to the Scope tab page.

2. Select the Template Selection sub-tab.

3. Search for the template SAP SCM rapid-deployment solution for global available-to-promise check (Technical name RDS_SCMATP).

4. To select the template, expand the appropriate template node and select the checkbox adjecent to the relevant child-node.

5. Save your project.

6. In the Assignment of Logical-Components pop-up, check whether the proposed logical components match those required by the the template. If the values in the Mapped Logical Component column are assigned incorrectly, correct it by choosing the F4 help for guidance in selecting the correct logical component that you have created.

For more information about the system landscape in SAP Solution Manager, see the SAP Solution Manager documentation on SAP Help Portal at http://help.sap.com SAP Solution Manager SAP Solution Manager 7.0 EhP1 SP23 Implementing and Upgrading SAP Solutions Project Administration Create/Change Project Specify Scope.

7. Once corrected, confirm and proceed. In the System Landscape tab page, ensure the correct logical components are assigned.

8. Save your project.

If you use a SAP ERP release lower than SAP ECC 6.0 EHP 4, you would need to follow a slightly different approach.

Since the F4 help would filter-out logical components that do not match the Product/Product Version of the template, in order to proceed further, you would need to first assign the newly created logical components. Checking the System Landscape in SAP Solution Manager as a placeholder, this would later be replaced.

Adjust Process Scope in SAP Solution Manager In the subsequent steps, you will adjust the scope of the solution where possible to reflect business goals, and adjust the configuration settings in the systems accordingly.

In SAP Solution Manager, adjust the scope of the business processes you would like to implement.

Procedure 1. In the SAP Easy Access menu, choose Business Blueprint (transaction SOLAR01).

2. Switch to the correct project context, choose Other Project (second button in the top-left corner, or type SHIFT+F5).

3. Select the appropriate project from the pop-up.

For more information about the scope of the SAP SCM rapid-deployment solution for global available-to-promise check, refer to the template description.

http://help.sap.com/saphelp_smehp1/helpdata/en/45/59dccac2091deae10000000a155369/frameset.htm



© SAP AG of 38

In the template, all business processes (scenarios) are self-contained i.e. have all related content assigned. Therefore, you do not need to select Master Data or Organizational Unit nodes or Interface Scenarios in the blueprint structure. We recommend deselecting these nodes to have a better overview during the configuration lateron (transaction Configuration SOLAR02).

In transaction SOLAR01, you can also access the template description to check which processes are mandatory/optional for the rapid-deployment solution.

For more information about business blueprints in SAP Solution Manager, see the SAP Solution Manager documentation on SAP Help Portal at http://help.sap.com SAP Solution Manager SAP Solution Manager 7.0 EhP1 SP23 Implementing and Upgrading SAP Solutions Business Blueprint.

Once the blue-print is adjusted appropriately, you configure the systems using transaction Configuration (SOLAR02).

The SAP SCM rapid-deployment solution for global available-to-promise check contains integration with SAP ERP and the template contains both SAP SCM-related and SAP ERP-related configuration information. On the SAP ERP side, the template’s content has only been validated with SAP ECC 6.0 EHP4. If you are using an SAP ERP release lower than SAP ECC 6.0 EHP4 and want to leverage the template’s SAP ERP content, you can follow the steps below as a workaround solution:

1. Choose the project that you created.

2. In transaction SOLAR02, open Business Scenarios Order Fulfillment Business Processes.

3. For the business process, select the entry in the configuration structure.

4. Check that the transaction is in display mode. Otherwise change to display mode.

5. In the menu, choose Edit Replace Log. Comp.

6. On the screen that appears, enter the logical component for SAP ECC 6.0 EHP 4 in the Logical Component to Be Replaced field. Enter your actual SAP R/3 / SAP ERP logical component in the Replace with Logical Component field.

7. Choose Save.

8. Confirm the warning.

5.3.3 Automated Implementation Using SAP Best Practices Solution Builder

5.3.3.1 Getting Files for Content Activation

Use The scoping, personalization, and installation phase of SAP Best Practices Solution Builder require solution scope and installation data files in a specific folder.

http://help.sap.com/saphelp_smehp1/helpdata/en/45/f6da633a292312e10000000a11466f/frameset.htm



© SAP AG of 38

Procedure 1. Create an installation data folder on a server that can be accessed from within the SAP

system where you want to install the SAP Best Practices package. Ensure that the persons who will install the rapid-deployment solution will have the necessary user rights to access this folder. There are specific files for SAP ERP and SAP SCM each.

2. The solution scope files can be found as attachment 51041569_SCOPE_RDS_ATP_604V7.zip and 51041569_SCOPE_RDS_ATP_SCM_700V2.zip of the SAP SCM rapid-deployment solution for global available-to-promise check support note 1577698 (https://service.sap.com/sap/support/notes/1577698).

3. Unpack the file and copy the solution scope file (*.xml file) that is needed for the rapid-deployment solution installation into the installation data folder created in step 1.

4. The installation data files can be found as attachment 51041569_BP_FILES_EN_SCM_604V7.ZIP and 51041569_BP_FILES_EN_SCM_700V2.ZIP of the support note 1577698 (https://service.sap.com/sap/support/notes/1577698).

5. Unpack the files into the installation data folder created in step 1. After doing so, you will find the installation data files (*.txt files) in this folder.

5.3.3.2 Import Solution Scope File

Procedure To install the SAP SCM rapid-deployment solution for global available-to-promise check, upload the relevant solution scope file as follows:

Procedure 1. To start the Solution Builder, use one of the following navigation options:

Transaction name Solution and Implementation

Transaction code /SMB/BBI

2. The Solution Editor screen displays, listing all solutions available in the system.

The solution list is empty the first time you enter the Solution Editor (if no other users have uploaded or created solutions in the system).

The button bar indicates the sequence of operation for end-users.

We strongly recommend adding the transaction for the Solution Builder (/SMB/BBI) to the favorites of your SAP user menu.

1. In the Solution Builder – Solution Editor screen, choose Solution -> Import -> Solution (XML) from the menu.

2. In the Select the Solution Scope File (XML) dialog box, indicate the path to the installation directory, select the relevant solution scope file and choose Open.

3. Choose the following Solution Scope file:

a. 51041569_SCOPE_RDS_ATP_604V7.xml for the ERP solution when in the SAP ERP system




© SAP AG of 38

b. 51041569_SCOPE_RDS_ATP_SCM_700V2.xml for the SCM solution when in the SAP SCM system

4. After the solution is uploaded (depending on the size of the solution a few seconds up to one minute), an information box about the uploaded scenarios and building blocks is displayed. Choose OK to confirm.

Execute steps 1 to 5 in the ERP and the SCM system.

Result The uploaded solution is visible in the solution list and is marked as your favorite solution.

If the path to the installation data directory is too long, the system will display an error message. If you receive this error message, either rename directories in the path to shorten the file path, or copy the installation files to a directory being closer to the root folder of the hard drive.

5.3.3.3 Maintain User Settings: Path to Installation Data

Use The solution definition (as uploaded as XML file) and the installation data define the solution content, that will be implemented.

To simplify the procedure and to avoid confusion with different sets of installation data, we strongly recommend to assign the installation data directory’s path to the solution. This is done in the user settings (because path information very often is user-dependent).

This is an important step for consultants that have imported multiple solutions in the solution builder.

Procedure 1. On the Solution Builder – Solution Editor screen, choose Goto User Settings from the

menu.

2. On tab Solution Specific, select the directory where you stored your installation data files.

The solution ID of the Favorite solution is fixed. To maintain it for another solution, select another solution as a Favorite before maintaining the solution-specific part of the user settings.

3. Choose OK to confirm the settings.

4. Execute steps 1 to 3 in the ERP and the SCM system.

Result The path to the installation data directory being assigned to the solution is always set as default entry for the particular solution.

5.3.3.4 Maintain User Settings: Path to Documentation

Use This activity sets the document path for information that may be useful during activation so that users can find details from the SAP Help Portal about the scenario being activated.


© SAP AG of 38

Procedure 1. Run the following activity:

Transaction Code /n/SMB/BBI

2. From the menu, choose Goto User Settings.

3. Choose tab External Documents.

4. Choose button Display <-> Change.

5. Choose the Insert Row button.

6. Enter the following value:

Parameter Value

DOCUMENTATION http://help.sap.com/

7. Choose OK (Enter).

5.3.3.5 Maintain Solution Settings: Select Languages The configuration content (customizing) of SAP SCM rapid-deployment solution for global available-to-promise (global ATP) check is provided in english language only.

5.3.3.6 Scope the Solution

You have 2 options:

Option 1: If you want to activate the complete SAP SCM rapid-deployment solution for global ATP check scope, you can skip now to step 4 Personalize the Solution below.

Option 2: If you want to activate a subset of the complete SAP SCM rapid-deployment solution for global ATP check scope, follow the steps in this section. Choosing this option, you can decide if you put the Global ATP with Check against Product Allocation or Global ATP with Rules-Based Availability Check scenarios in scope or out-of-scope.

1. Choose the Scoping button (Ctrl+F9).

2. On the Scoping for Solution RDS_SCM_ATP screen, you can deselect the scenario you do not want to install.

3. Choose the Save Data button.

4. On the informational box, enter a Solution ID and a Description, then choose OK. On the next dialog box, choose OK.

5. Choose Back twice.

6. Select your solution from the list, then choose the Favorite button.

5.3.3.7 Upload Installation Data

Prerequisites The installation files have been downloaded to the local directory you created in step Create Installation Folder for the SAP SCM rapid-deployment solution for global available-to-promise (global ATP) check Installation Files and Scope File.

The Solution Scope file has been uploaded into the SCM and ERP system.


© SAP AG of 38

To assure the installation data upload is working correctly, make sure before installation data upload the following user settings are set as described (access via Solution Builder Solution Editor Goto User Settings, General tab):

o Deselect the setting Check consistency with eCATT definitions during Installation data upload

o Select the setting Maintain references in eCATT Definitions during Installation Data upload

Use This step is the prerequisite for the personalization of the default delivered settings for the implementation of a solution.

Personalization is mandatory for SAP SCM rapid-deployment solution for global available-to-promise (global ATP) check.

In addition, the upload allows you to review the installation data for the tasks in the Building Block Builder for better transparency, troubleshooting, or to maintain installation data

The step activating a solution is independent of the uploading the installation data step. The activation step uses the files in the installation data folder on the presentation server, to ensure that you have uploaded the correct installation data files and been pointed to the correct folder location.

Procedure To upload the installation files, proceed as follows in the Solution Builder:

1. Go to view Solution Builder – Solution Editor.

2. From the menu choose Solution Set as Favorite to set the uploaded solution as a favorite.

3. Choose button Upload Installation Data (Ctrl+F5).

4. In dialog box Upload Installation Data, maintain the following values:

Field Name Value

Path <your directory of installation files>

All Files X

5. Choose Continue (F8).

5.3.3.8 Personalize your Solution

Prerequisites Ensure that the graphic files have been imported into the system. These graphics are attached to the SAP Note Additional information for BP- SOLBLD 70V* (see SAP Note 1301301; in this SAP note the release strategy for SAP Best Practices ABAP Add-ons is listed including information on the latest solution builder version. Once you have identified your solution builder version, you can check the relevant SAP Note Additional information for BP- SOLBLD 70V* which refers to the version of the solution builder you have in usage).

The generic personalization functionality provides additional personalization tasks if supported by your solution. For selected personalization tasks, it displays values that correspond to the respective uploaded installation data.


© SAP AG of 38

Within the definition of personalization tasks, only selected parameters are displayed or changeable to simplify personalization for end-users.

Besides field length, no consistency check of the changed data will be executed by the Personalization Assistant, which means that errors will occur in the installation phase if inconsistent data is entered. Therefore it is highly recommended to run the personalization with the assistance of an experienced SCM and ERP consultant.

In most cases you have to enter the values directly, i.e. there will be no input help for the parameters.

Procedure 1. Choose the Personalization button.

2. On the left-hand side of the screen, the system displays a list of available personalization tasks. On the right-hand side, the system displays the respective change options for the selected personalization task.

3. Change the values according to your requirements by considering the guidelines in the instructions in the system and reading the configuration guides for more information.

4. After completion of a personalization task choose Set Status Completed.

5. Changed values are marked in blue color.

To reset the values of a personalization task back to the default values choose Reset to default.

6. Save your changes.

Result The Installation data uploaded to the Solution Builder has been changed.

5.3.3.9 Download Installation Data

Prerequisites The personalization of the solution is finished.

It is strongly recommended to download the installation data to a folder that already contains the complete set of installation data as delivered by your solution provider (confirm overwrite in case of a warning message). Otherwise required files that are not covered by the up- and download process (such as graphic files) will be missing.

Procedure 1. In the menu choose Goto -> Installation Data -> Download (Ctrl+F6).

2. In dialog box Download Installation Data, maintain the following values:

Field Name Value

Path <your directory of installation files>

All files X


© SAP AG of 38

If you maintained the user settings according to section Maintain User Settings: Path to Installation Data, the directory of the installation data is already set as default in the dialog box.

3. Choose OK to overwrite the installation data.

Result The personalized installation data is downloaded to the folder that contains all installation files required during the implementation of a solution.

5.3.3.10 Create Characteristic Combinations – Load Data From File

The procedure is described in detail in Global ATP with Product Allocation (S63): Configuration Guide for the SAP SCM system.

You need to create a file with the following properties:

The file needs the format text (tab-delimited), meaning that the individual values have to be delimited through a tab space. For example, in a spreadsheet application, you can create the file by saving it in this format. You need the following column sequence:

Column: 01 Charac.: 01 9AKONOB Prod. Alloc. Object

Column: 02 Charac.: 02 9ALOCTO APO Destinatn Loc.

Column: 03 Charac.: 03 9AMATNR APO Product

Column: 04 Charac.: 04 9AVKORG Sales Organization

1. Create the text file in format tab delimited without header lines.

a. When you load your data from a file you can use MS Excel to edit the characteristic combinations.

b. This step is best done after you created your master data in ERP and SCM because then you know the product and location names and the values of the other characteristics.

2. Note the file name and where the file is kept. Use the path in the activity described in Global ATP with Product Allocation (S63): Configuration Guide.

You can find an example file Char_Combs_PAL.txt attached to support note 1577698 (https://service.sap.com/sap/support/notes/1577698). If you use other characteristics you have to create other columns.

5.3.3.11 Activating Solution

Use The implementation of a solution is performed in the Implementation Assistant.

The Implementation Assistant provides two activation options:

Activation in the Solution View (standard view)

o All selected scenarios will be installed according to the sequence listed in the Solution/Scenario structure.



© SAP AG of 38

o No parallel activation or individual selection of scenarios possible.

o Recommended Activation Option because activation conflicts will be avoided.

Activation in the Scenario View

o Scenarios can be individually selected for activation and the installation sequence can be freely defined.

Activation in the Scenario View will not prevent parallel activation of solution content, because only the currently activated scenario is protected. If you run automated steps in different scenarios accessing the same data, table errors and inconsistencies can occur.

Therefore using this activation option is not recommended and is at your own risk – for example, you should make sure that only a single user is running the activation.

The Implementation Assistant screen provides the scenario list of a solution on the left-hand side. Expanding the Scenario shows the Building Blocks of the Scenario in the correct sequence.

Expanding a Building Block shows the implementation activities of each Building Block in the correct sequence.

On the right-hand side in the upper part of the screen, you see the Building Block repository for your solution.

The lower part shows all messages and message details that are generated during checks and implementation.

Procedure To activate a solution, the following activation information must be provided:

Target language (the language of text fields for system parameters that are not language dependent in a technical sense. After starting the installation, the target language cannot be changed.)

Folder containing installation data (it is recommended to use already-determined folder retrieved from the user settings.

A workbench and customizing request (these can be created using the respective create buttons at the bottom of the activation dialog box)

Other options

o Skip this screen – During activation, if the system stops due to a manual task or error, you must restart activation. This option prevents the activation dialog box from displaying again. The system uses the same settings from the first activation. To redisplay this activation option screen, you can right-click the solution node, and choose Display Activation Option.

o If the Activation Options are skipped, you can make the Implementation Assistant stop the activation after the installation of each scenario and to display the activation options screen (Choose option Stop activation by the end of each Scenario)

1. Go to Implementation Assistant.

2. In the Implementation Assistant - Solution view choose the button.

3. Alternatively, you can select a specific scenario in the Implementation Assistant - Scenario view for activation.

4. Specify the activation options as described above.

5. Confirm the Activation dialog box.


© SAP AG of 38

Result The activation starts. Depending on the number of manual activities and possible errors during implementation, the activation may stop occasionally, waiting for manual input or troubleshooting.

Refer to the information provided with your solution for any specific information that must be considered for prerequisites or during implementation. This will also provide you with information of the expected implementation time and specific troubleshooting procedures.

If several people are involved in the implementation, make sure to take activation

ownership (choose the button). Otherwise, the solution is locked.

5.3.3.12 Manual interaction during Installation of Building Blocks

Use The installation procedures of the following scenarios / building blocks contain manual installation steps and / or require manual confirmation.

Procedure If the Solution Builder stops because of a manual activity please proceed as follows:

1. Confirm the Information screen There is no instructional document attached to this manual task.

2. On the navigation option screen, memorize the header of this screen. This header information is identical with the configuration activity that has to be executed manually.

3. Open the Configuration Guide for this building block which is provided on the documentation html structure in section Technical Information Content Library. Navigate to the Building Block and open the Configuration Guide.

4. Choose the proposed navigation option, e.g. Navigate to IMG.

5. Execute the configuration activity manually by following the instruction of the related section in the Configuration Guide.

6. Choose Back (from the IMG activity or the transaction).

7. Choose Proceed.

8. In the Implementation Assistant – Scenario Edit View choose Confirm Manual Step.

9. Enter a reason (optional) and choose Enter.

10. Proceed with the activation.

5.3.3.13 Processing General Errors during Installation

Use When an activation of an automated task runs into errors, the activation stops at the point of the error. No further implementation can be done until the error is resolved.

Procedure 1. On the Implementation Assistant – Solution View screen, select a task that has a red light in

the Current status column.


© SAP AG of 38

2. Expand the task and choose the log that is assigned to this task. Detailed information about the error is displayed in the Error List pane.

3. In the Error List pane choose Display Detailed Log. The detailed log information about an eCATT or BC Set activation is displayed.

4. In this log information, check entries with a red light to identify the reason for the error.

If the error can be solved based on the log information, you can run the eCATT or BC Set again.

If the activation fails because of locked objects, please make sure, that no objects are locked by any users. Then try to activate the activity again.

See the document SAP Best Practices Tools for details about the manual activation of eCATTs and BC Sets. The document can be found in the documentation in the area Technical Information Tools & Concepts.

5. If the log information is not sufficient to solve the problem you can proceed as follows:

a. Execute the task manually: use the description of the related section in the Configuration Guide for executing the task,

or

b. Open a customer message for this problem specifying the component SV-RDS-SCM.

Do NOT delete Solution Builder scenarios ONCE they have been activated. If you delete scenarios, the activation history and the respective logs are lost and it is not possible to find possible error reasons with tenable efforts.

In such cases, NO SAP SUPPORT CAN BE PROVIDED.

6. When you have solved the problem (either executed the task manually or a solution has been provided via customer message), choose the Change button that is displayed in the Old Status column to the right of the task.

Do NOT proceed with installation if the problem has not been solved. If you continue without solving the problem, severe errors might result in the subsequent installation steps that cause incalculable efforts to fix.

In such cases, NO SAP SUPPORT CAN BE PROVIDED.

7. On the Confirmation dialog box, choose OK to manually change the status to successful.

8. On the Information dialog box, you can enter a reason for changing the status.

9. Choose Continue.

The information is saved in a log. To view details for a changed task, choose the red light in the Original Status column for that task. A dialog box displays the user who performed the change, the date of the change, and the reason for the change. Choose Continue to close the dialog box.

10. Choose Activate to continue with the installation.


© SAP AG of 38

5.3.3.14 Processing Error Inbound Queue Blocked “Version 000 not found”

Use If you get the error message Inbound Queue Blocked “Version 000 not found” during activation of an integration model, make the following settings in the SCM system:

Procedure

Create Planning Version 000

SCM Menu Advanced Planning and Optimization Master Data Planning Version Management Model and Version Management

Transaction Code

/SAPAPO/MVM

On the Model and Version Management screen, check the following settings:

Field Name Entry Value

Check if the active model 000 and the active version 000 are available

If you have to create the

model, choose the pushbutton with quick info Create Model/Planning Version.

For model, name it 000 with description 000 – Active Model.

If you have to create the planning area, choose the

pushbutton with quick info Create Model/Planning Version.

For planning version, name it 000 with description 000 – Active Planning Version and select the following indicators

Backorder Processing Active (in the ATP area)

CBF Time Series Updated (in the ATP area)

Update from ATP Time Series (in the ATP area)

Create and Save the Model and Planning Version.

5.3.3.15 Processing Error in Task Maintain Calendar of Building Block S66 Transportation and Shipment Scheduling for Global Available to Promise Check

If you get the error “Not activated – error” when activating task Maintain Calendar of Building Block S66 Transportation and Shipment Scheduling for Global Available to Promise Check make the following entries:


© SAP AG of 38

Checking Holiday and Factory Calendar

Use The validity of the holiday and factory calendars need to be checked and extended if necessary. The some of the standard settings are valid until year 2010 only and need to extended. Several business functions are using the calendar information.

The validity of the Holiday Calendar and the holidays have to be checked according to the legal requirements of the related country.

Procedure Carry out the following steps:

1. Access the activity using one of the following navigation options:

IMG-Menu SAP Netweaver General Settings Currencies Maintain Calendar

Transaction Code SCAL

2. Select the Holiday calendar and click on Change .

3. On the Change Public Holiday Calendar: Overview screen, select the Holiday Calendar entry specific for your country and region.

4. Click on Change .

5. On the Change Public Holiday Calendar: Details screen, check and change the Valid to field to a future year (like +3 years).

6. Check the validity range of every public holiday assigned to the holiday calendar. Extend the validity if necessary.

7. Click on Save to save the entries. Confirm the message regarding transporting of holiday and fabric calendar settings.

8. Click on Back to the SAP Calendar: Main Menu screen.

9. Select the Factory calendar and click on Change .

10. On the Change Factory Calendar: Overview screen, select the Factory Calendar entry specific for your country and region.

11. Click on Change .

12. On the Change Factory Calendar: Details screen, check and change the Valid to field to a future year (like +3 years).

13. Click on Save to save the entries and leave the IMG activity.

Result The validity of both Holiday and Factory Calendar, and the public holidays have been checked and extended to a future year.


© SAP AG of 38

5.3.3.16 What to do when APO client is not the BW client?

If you your APO client is not the BW client follow the instructions in SAP note 522569. BW objects are needed for the ATP check against product allocations.

5.3.3.17 Error: No valid version exists for for planning area ‘9ADP01’

If you get the pop-up message during task Creating a Selection Profile for the Planning Book.

Make the following settings:

Procedure 1. Choose No.

2. If you get message Error generating a program for the selection tool double click on the message line and follow the instructions in the message.

3. Proceed with steps of task Creating a Selection Profile for the Planning Book.

5.3.3.18 Error: Display Product Allocation Situation – Not all characteristics are displayed

If you have the problem with transaction /SAPAPO/AC42 - Display Product Allocation Situation that not all characteristics are displayed on the screen to select the product allocations for a particular combination execute transaction /SAPAPO/ATPCQ_GENER - Generate Objects with settings Generate all. This will regeneration the display screen.

Rds Atp Scm70 Quick Guide en Xx

Documents

Transcript of Rds Atp Scm70 Quick Guide en Xx