Quick Guide to Implementing the SAP IT Portfolio and Project Management Rapid- Deployment Solution V2.60

(1)

SAP Portfolio and

Project Management

6.0 April 2014

English

Quick Guide to

Implementing the SAP IT

Portfolio and Project

Management

Rapid-Deployment Solution

V2.60

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

(2)

Copyright

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.

National product specifications may vary.

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 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. Please see

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

(3)

Icons

Icon Meaning Caution Example Note Recommendation Syntax

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.

(4)

Quick Guide to Implementing the SAP IT Portfolio

and Project Management Rapid-Deployment

Solution V2.60

Purpose

This quick guide provides step by step information you need to implement the complete solution package.

Before proceeding with this document you must have completed the following activities: Defined the scope relevant for your project

Finalized technical prerequisites

Staffed and made available the required resources

This document does not provide a general overview and explanation of SAP Best Practices. For more information about the Best Practices concepts, see the related documentation on

http://service.sap.com/solutionpackages and follow the links to the Learning Maps.

This document is intended for the following project roles, which already have a sound knowledge of SAP Best Practices, including tools and documentation.

System administrators and basis consultants: System set up and preparation including troubleshooting

Activation/implementation consultants (basis or application consultants): Activation/implementation of business content and processes

Business consultants: Evaluate business content/processes including troubleshooting, FAQ and further information for extended usage of the package

If you are not familiar with the SAP Best Practices tools, first refer to the step-by-step guide, phase Deploy: Activate Solution, accelerator Automated Activation.

(7)

1 Solution Overview

SAP IT Portfolio and Project Management rapid-deployment solution version 2.60 Is based on SAP Portfolio and Project Management 6.0

Provides an accelerated deployment of the required configuration settings Supports the following processes:

o K20 - IT Portfolio Management & Monitoring without Project Management o K21 - IT Project Management (without ERP integration)

o K22 - IT Portfolio Management & Monitoring and IT Project Management (without ERP integration)

o K23 - IT Portfolio Management & Monitoring and IT Project Management (with ERP integration)

o K24 - IT Project Management (with ERP integration) Provides “out of the box” integration to ERP for project accounting.

For processes with ERP Integration (K23 and K24):

In general we assume that the customer has a running ERP installation ECC 6.0 EhP7, which forms the basis for the ERP part of this package. Controlling Area, Company Code, Cost elements, mini-master HR are required in the corresponding ERP backend system to complete the Business Processes.

Since this package only covers the implementation of SAP IT Portfolio and Project Management and the integration with SAP Controlling and /or SAP Project System, core ERP functions need to be implemented upfront.

The SAP Best Practices Baseline Packages can be used to run the core business scenarios that support the most important business needs.

For an overview of the rapid-deployment solution, refer to the Solution Details Presentation in the step-by-step guide (phase Start: Prepare Project).

(8)

2 System Setup & Preparation

Prior to installing and activating an SAP Best Practices package (SAP BP package), the target SAP Application Server (AS) must be installed together with the Support Package Stack (SPS) specified in this section.

Additionally, the SAP Notes named in the SAP Notes and Messages section in this guide must be implemented.

2.1 Release and Support Package Level

The deliverables of SAP Best Practices packages were developed and tested in a system landscape with specific release and support package (SPS) level. If the SPS level in your system is different, there may be 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 SAP Best Practices requirements, only limited support can be provided.

If you need a higher SPS level in your system, for example, because of additional functionality, first import and activate the SAP Best Practices package on the SPS levels as mentioned below, then update your system to the target SPS level.

The support package levels relevant for the solution package are listed together with the required components in the Required Product Versions and Software Components section.

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 the SAP Software Download Center (SWDC) on SAP Service Marketplace (SMP). 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 in your SAP Solution Manager system. You can also select relevant SPSs manually one-by-one via the SWDC on SAP Service Marketplace:

https://service.sap.com/swdc Support Packages and Patches A-Z Index

Only the current Service Release (SR) is delivered to SAP customers/partners via the SWDC on SMP and standard delivery (for example, the Software Catalogue). If you encounter the situation that the required SPS for correct SAP BP packages activation is based on a SPS level LOWER than the current Service Release, the request for the necessary SPS is handled by a customer message. For details, see SAP Note

925690 Standard Ordering Procedures for SAP Software.

2.2 Required Product Versions and Software

Components

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

Product Product Version Component Comments

SAP Solution Manager

SAP Solution Manager 7.0 Enhancement Package 1 SP18 or higher

Not applicable Required

implementation tool

Please be aware that SAP Portfolio

(9)

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

and Project Management is also delivered with the SAP Solution Manager stack. However, this is independent from the usage of SAP Solution Manager as a tool for RDS implementations. See also SAP Note

1968343

SAP Portfolio and Project Management

SAP Portfolio and Project Management 6.0 SP00

CPRXRPM600_740

SAP Business Suite

Foundation

SAP Business Suite Foundation 747 SP03

SAP_BS_FOUNDATI ON 747

SAP WEB UIF 747 MDG_FOUNDATION 747 SAP NetWeaver SAP NetWeaver 7.4 SP05 Application Server ABAP Application Server Java Adobe Document Services SAP Netweaver Business Client for Desktop

Required for SAP Portf. and Proj. Management Application Server Java is needed for ADS. Alternatively, SAP Enterprise Portal can be used. SAP enhancement package for SAP ERP

SAP EhP7 for SAP ERP 6.0 – SP03

SAP ERP 607 - Central Applications

Usually, required software components and SPS levels are downloaded using the Maintenance Optimizer in SAP Solution Manager. Alternatively, you can download the software manually from the SAP Software Download Center (SWDC) on SAP Service Marketplace:

For installing software, go to https://service.sap.com/swdc Installations and Upgrades Browse our Download Catalog SAP Application Components

For support packages, go to https://service.sap.com/swdc Support Packages and Patches Browse our Download Catalog SAP Application Components

For detailed information on SPS definition for the SRs of SAP ERP, see SAP Note 774615

Support Package levels of ERP/ECC installations/upgrades.

2.2.1 SAP Portfolio and Project Management 6.0

SAP Portfolio and Project Management 6.0 is the core component of this package and it is supported on top of SAP NetWeaver 7.4.

(10)

© SAP AG Page 10 of 59 The SAP IT Portfolio and Project Management rapid-deployment solution can be implemented standalone as add-on on HANA-enabled server with SAP NetWeaver 7.40, without the need to integrate into ERP and/or Enterprise Portal.

The following scenarios are standalone scenarios without ERP Integration: o K20 - IT Portfolio Management & Monitoring without Project Management o K21 - IT Project Management (without ERP integration)

o K22 - IT Portfolio Management & Monitoring and IT Project Management (without ERP integration)

For more information about required support packages for SAP Portfolio and Project Management 6.0, see SAP Note 1826383.

2.2.2 EhP7 for SAP ERP 6.0

The SAP IT Portfolio and Project Management rapid-deployment solution can also be implemented integrated with ECC 6.0 EhP7.

The following scenarios require the ERP Integration:

o K23 - IT Portfolio Management & Monitoring and IT Project Management (with ERP integration)

o K24 - IT Project Management (with ERP integration)

It is assumed that the customer has been using an existing SAP ECC system on release level SAP ECC 6.0 to manage projects with a WBS structure or an Internal Order.

2.3 SAP Frontend Components

Frontend Requirements for Portfolio and Project Management 6.0 are consolidated in SAP Note

1826387

Supported Frontends for Portfolio and Project Management User Interface

Browser: within the Browser either the Enterprise Portal or NetWeaver Business Client for HTML can be used

Users can access SAP Portfolio and Project Management using SAP NetWeaver Business Client or the SAP NetWeaver Portal. In the latter case it is assumed that the customer has an existing SAP NetWeaver Portal already in place.

When you use SAP Portfolio and Portfolio Management 6.0 in SAP NetWeaver Portal, ensure that the protocol used by SAP Portfolio and Project Management to access the portal and the protocol used by the Portal to access back-end system is the same. For example, if you use HTTPS for the Portal, you must use HTTPS for SAP Portfolio and Project Management.

SAP Netweaver Business Client for Desktop (Version 3.5 and 4.0)

SAP Front-End GUIs: SAP Front-End GUI required for customizing activities and for screens which can be called via integration

Acrobat Reader: Acrobat Reader required for printing, status reports, approval documents; requires installation of Adobe Document Server

(11)

https://service.sap.com/swdc SAP Software Download Center Support Packages and

Patches Browse our Download Catalog SAP Frontend Components

2.3.1 Java runtime environment (JRE)

The Timeline Monitor and the Portfolio Structure Graphic of Portfolio Management is

implemented by a Web Dynpro ABAP control which uses an internal Java applet, for which you have to make the settings described below

Procedure

1. Install a Java runtime environment (JRE or Java plug-in) on the local PC

We recommend that you use the latest version of the Java plug-in. We also recommend that you install the latest version of the applet, which can be found in SAP Note 1035436

2. After updating the applet, make sure that the cache of the JRE is reset (see SAP Note

1014150).

The Java runtime environment has a fixed memory size which cannot be increased during runtime. This can cause OutOfMemory exceptions when working with the graphical view

2.4 SAP Solution Manager and SAP Solution Manager

Content Add-on

For the implementation of the solution package, 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.

Please be aware that SAP Portfolio and Project Management is also delivered with the SAP Solution Manager stack. However, this is independent from the usage of SAP Solution Manager as a tool for RDS implementations. See also SAP Note 1968343

It is assumed that a productive SAP Solution Manager system is available in the customer’s system landscape: if the customer is already using other SAP products (for example, SAP ERP) SAP Solution Manager should already be present in the system landscape.

Import the following content Add-on corresponding to the SAP Solution Manager product version in place:

Software Component

Product Version SP Level Description

ST SAP Solution Manager

7.0 Enhancement Package 1

Or

SAP Solution Manager

SP18 or higher

In case the SP is below 24, see SAP Note 1579267.

Implementation tool for the automated content of an RDS.

(12)

Or

SAP Solution Manager 7.1 on HANA (ST 712)

SP01 or higher

SP00 or higher

ST-RDS 100 Always latest SP level This add-on contains SAP Solution Manager content. See also SAP Notes 1686668,

1726649.

For more information about SAP Solution Manager (including system administration and implementation aspects described in chapters below), see the SAP Library documentation for SAP Solution Manager at http://help.sap.com Application Lifecycle Management SAP Solution Manager, or at

http://service.sap.com/solutionmanager.

The latest available ST-RDS 100 content support package has to be downloaded from the SAP Software Download Center on SAP Service Marketplace (http://service.sap.com/swdc

Installation and Upgrades Browse our Download Catalog SAP Rapid Deployment solutions SAP Solution Manager Implementation Content ST-RDS 100).

2.5 SAP Best Practices Add-on and SAP Best Practices

Solution Builder Add-on

The following SAP Best Practices add-ons must be imported into the system: Software

Component

Release Version Description

BP-ERP 617 V3

Use the latest version as outlined in SAP Note

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.

SAP Best Practices All-in-One based on ERP 6.0 (ECC 600, EHP7)

This add-on contains the SAP Best

Practices technical framework (for example, BC-Sets, eCATTS, print programs)

BP-CANW 740 V3 Installation on the

SAP Portf. and Proj. Mgmt. system

BP-SOLBLD 70 V9 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:

(13)

https://service.sap.com/swdc Installations and Upgrades Search for Installations and

Upgrades Search term: BP-ERP 617 or BP-CANW 740 or BP-SOLBLD

Regular Updates Technical Environment

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 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 ERP and the add-on

BP-SOLBLD, see SAP Note 1301301 (see also section SAP Notes and Messages of this document.)

Since the solution scope 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 versions before you start the technical implementation of the 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.

2.6 General Client Settings

After you have set up the required system(s), make the following settings to enable automatic or manual content activation.

Client Roles:

The system must not comprise any clients with the role productive client. If the system contains a productive client, BC sets cannot be activated as required. As a consequence, the automatic activation of SAP Best Practices content using SAP Best Practices solution builder is not possible, because BC sets cannot be activated in a productive system.

To check and maintain the settings of clients in your system, use transaction SCC4. Changes and Transport for Client-specific Objects:

To activate a SAP Best Practices packages, an automatic recording of changes is required. To ensure that all the changes are automatically recorded in a change request, in the Changes and Transport for Client-specific Objects group box, choose Automatic recording of Changes.

Cross-client Object Changes:

During the activation of an SAP Best Practices package cross-client objects are created. Cross-client functions include all cross-client customizing objects (for example, factory calendar, definition of price list conditions, printer controls) and all objects of the SAP Repository (for example, reports, module pools, screens, dictionary and so on).

To enable changes to cross-client objects, in the Cross-Client Object Changes group box, choose Changes to Repository and Cross-client Customizing allowed.

In case you have not allowed changes to Repository and cross-client Customizing, you will be asked during the activation of the package if these settings should be done automatically by solution builder. If you reject the required changes the activation cannot be executed automatically.

(14)

2.7 SAP Enterprise Extensions Sets and Business

Functions

Use

You have to activate the following Extension Sets/Business Functions before you start activating the SAP Best Practices package content.

Activating Enterprise Extensions, Business Functions, and Business Function Sets means permanent changes to your system which cannot be undone. For more information about the impacts on your system, see the documentation of the related Extension Set or Business Function.

Procedure

1. Run the following activity:

IMG Menu Activate SAP ECC Extension

Transaction Code SFW5

2. On the Switch Framework: change Business Function Status screen, select each of the following entries (by selecting the Planned Status column) and then choose the Activate Changes button:

Business Functions Planned Status

Comment

/BCV/MAIN ON FND, Business Context Viewer Main Application /BCV/MAIN_1 ON FND, Business Context Viewer Main Application 2 3. The system displays an informational dialog box. Choose Continue.

4. Choose Back.

2.8 SAP Notes and Messages

If issues become apparent after shipment of this SAP Best Practices package (and hence of this document), a SAP Note exists to document how to solve the issues.

Before you start the activation of the related SAP Best Practices scope, check the latest version of the SAP Note for the solution packageto obtain updates and corrections for problems that have not become apparent until after shipment.

SAP Note #

Description Component Area Remark

1968343 SAP IT Portfolio and Project Management rapid-deployment solution V2

SV-RDS-PPM General Info

Always check the SAP Note of the SAP Best Practices package for updates on the implementation

Apply all SAP Notes to the system via the SAP Note Assistant (transaction SNOTE). All SAP Notes mentioned below must have the implementation status Completely implemented. Some SAP Notes require manual action before you set the status to Completely implemented. To avoid activation errors as a result of generating loads, perform a mass generation using transaction SGEN as described in SAP Note 481548.

(15)

mentioned above): SAP Note #

Description Component Remark

1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

SV-SMB-AIO-BP SAP Note 1301301 refers to other notes.

Always check the

referenced notes and follow the instructions.

Attached to this add-on specific note you can find the corrections for the add-on. Always apply the correction transport for the corresponding add-on.

1826332 FAQs - SAP Portfolio and Project

Management 6.0

PPM-PRO

1826383 PPM 6.0: support package information, notes, and schedule

PPM-PRO 1872722 Additional information for inst./upgrade of CPRXRPM 600_740 PPM-PFM Portfolio Management

It only applies if PPM runs on an SAP HANA database

1988494 PPM-PRO: Reusable ABAP DDL (CDS) for concrete role, abstract role, CGPL_TASK and CGPL_PROJECT

PPM-PRO Project Management

1988562 Optimized My Projects and My Task

Dashboard

PPM-PRO Project Management

1878361 Import: Task and role assignments not transferred

PPM-PRO-EXT-PMT

1949091 Categories and subcategories are not displayed by value help

PPM-PFM

1976060 Decision point data not shown in review item dashboard.

PPM-PFM-UI

1672968 Deactivating "SAP*" during the business partner search

PPM-PRO-RES To implement the BAdI DPR_RES_SEARCH

(16)

2.9 Creating a User for Activation of SAP Best Practices

Content

Use

In this activity, you create a user to run the activation of the related SAP Best Practices scope.

We recommend using only one User ID to activate the SAP Best Practices content. Thus you avoid changing ownership during the activation of the solution.

SAP does not supply separate Customizing or setup roles (according to the security guideline). Instead, use the functions provided in Role Maintenance (transaction PFCG). In the Role Maintenance, you can define a role corresponding to your individual IMG project with all the authorizations you need to access the IMG activities required for the SAP Best Practices scope. For more information about defining a role for a Customizing project, see the documentation for transaction PFCG.

Alternatively you can use the authorization profile SAP_ALL and remove the profile after activation. If this authorization does not apply to your authorization concept, you should restrict the rights of the user according to your internal authorization

guidelines. Without the profile SAP_ALL, issues may occur during the activation which must be solved.

If authorization issues occur during activation you can use transaction SU53 to get information on the missing authorizations and extend the authorization data as necessary.

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 the 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.

6. Make the following entries:

Password <initial password>

User type Dialog

7. Choose the Defaults tab. 8. Make the following entries:

Logon language EN

Decimal notation 1.234.567,89 Date format DD.MM.YYYY

(17)

9. Choose the Roles tab and 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 profile corresponds to your internal security guidelines.

11. Save your entries.

Result

You have created the user to activate SAP Best Practices content.

Repeat the steps above for all systems and clients you use. Make sure that you always create the same user in all systems and clients.

Directly after activation of the SAP Best Practices content, remove the authorizations you have given to the system user that has performed the activation steps. Thus you avoid that the system user misuses the authorizations granted before.

2.10 Preparation of Logical Components Used in

SAP Solution Manager Implementation Project

This solution package is designed for a specific system landscape that is represented by its logical components. By preparing and mapping the logical components to the actual physical systems in the landscape it enables you to configure the systems directly using SAP Solution Manager.

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.

Make the following entries (IT administrators, using transaction SMSY): Delivered Logical

Component

Product Product Version Product Instance Logical Component (Customer Namespace) <Choose a name>, for example, ERP60_EHP7_CE NTRAL_APPLICAT ION SAP ERP ENHANCE PACKAGE

EHP7 FOR SAP ERP 6.0 [Central Applications] <Choose a name> <Choose a name>, for example, PORTF_PROJ_MG MT60_PPMNW740 SAP PORTF AND PROJ MANAGEMENT SAP PORTF AND PROJ MGMT 6.0

[Portf and Proj Mgmt NW7.40]

2.11 Creating Transport Requests for Activation

(18)

You can create transport requests during activation. However, if the activation user is not allowed to create own requests, the system administrator must create these requests in advance and they can be assigned during activation.

For manual activation (see section Manual Implementation), the system administrator must also create the transport requests manually.

Creating a Workbench / Customizing Request

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

SAP Menu Tools Administration Transports Transport Organizer Transaction Code SE01

2. On the Transport Organizer (Extended View) screen, choose the Transport tab and choose the Create button.

3. In the Create Request dialog window, choose one of the following options: For a Customizing Request Customizing request

4. Choose Enter.

5. In the Create Request dialog window, enter a Short Description. 6. Save your entries.

7. Repeat from the step 3 for the Workbench request creation.

Result

You have created a workbench and a customizing request to activate the solution content.

Repeat the steps above for all systems and clients you use. If required assign the requests to the relevant activation users.

2.12 Deselecting Activation Links in BC Sets

We recommend that you turn off the creation of activation links for BC sets. By doing this, you can significantly increase activation speed and avoid errors.

Procedure

1. To run the activity, choose the following navigation option:

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. Confirm the information message and save your settings.

2.13 Setting the Maximum Work Process Run Time

Use

Dynamic switchable profile parameters (indicated by a flag in the check box of the parameter) have to be checked before activation. Therefore, check and adapt the following profile parameters.

(19)

© SAP AG Page 19 of 59 For the activation of the SAP Best Practices content, the parameter value for maximum work process run time must be increased because there are some processes that must be performed in dialog and that last for more than 10 minutes.

Procedure

1. Run the following activity: Transaction Code RZ11

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

Field Name Description User Action and Values Note Param. Name Profile parameter name rdisp/max_wprun_time 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.

Parameter Name Description New

value

Note

rdisp/max_wprun_time Max work process runtime 3600 Check and adapt the value if the value is <3600

6. Confirm the information message and save your settings.

Result

You have changed the parameter. This change only becomes effective when you off and log-on to the system again.

Switch back to the default value after activating the solution package.

The change is lost when you restart the server (as all profile parameters). If you had to restart the server, repeat these settings.

2.14 SAP Scripting

Use

eCATTs are used to automate the activation of the rapid-deployment solution configuration settings. Before activation, 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 to true.

Procedure

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

Field Name Description User Action and Values Note 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:

(20)

New Value New Value for user scripting

TRUE Enable SAP

Scripting 6. Confirm the information message and save your settings.

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.

2.15 Setting Default Timeout for HTTP and HTTPS

Services

Use

We recommend that you set the following system parameters for both services TIMEOUT and PROCTIMEOUT to 300 seconds or 600 seconds. The default is 60 seconds.

Procedure

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

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 5. Choose Back.

6. Choose Save.

2.16 Configuring the Print Environment

Use

Adobe Document Services are the prerequisites to print from the SAP Portfolio and Project Management dashboard or to print graphics from the Business Context Viewer.

It is assumed that for the rapid deployment of SAP IT Portfolio and Project Management you have already configured Adobe Document Services for printing in your landscape.

In this activity, you connect the SAP PPM system to an existing Adobe Document Services (ADS).

Prerequisites

An installation of the Adobe Document Services (ADS) is required for printing. For more information about setting up ADS, see SAP Note 894009.

Procedure

1. To activate the service for printing, access the following transaction:

(21)

Execute.

3. Expand the tree and select default_host/ sap/bc/fp. Choose Service/Host Activate. 4. Exit the transaction.

5. To create an ADS connection for PDF printing, access the following transaction:

Transaction Code SM59

6. On the Configuration of RFC Connections screen, choose Create. 7. On the RFC Destination screen, make the following entries:

Field Name Entry Value

RFC Destination ADS

Connection Type G

Description Adobe Document Services

8. Choose Enter.

9. On the Technical Settings tab, create the following settings: Field

Name

Entry Value Comment

Target Host

<Target host ADS server> Host name of the J2EE Engine running the Adobe document services, or the SAP Web Dispatcher, if applicable. Service

Number

<Service number of ADS server> HTTP port number of the target host you have specified

The following naming convention applies:

5<J2EE_instance_number>00 (50000, for example, if your J2EE instance is 00).

Path Prefix

/AdobeDocumentServices/Config?style=rpc

10. On the Logon & Security tab, create the following settings:

Basic Authentication X

User ADSUser

Password <Password of ADSUser>

11. Save your RFC destination.

You can test the RFC connection by choosing Connection Test.

2.17 Activating Services

Use

After the installation of the Application Server ABAP (AS ABAP), all Internet Communication Framework (ICF) services are available, but in an inactive state for security reasons. To call the Portfolio Management application, the required services must be activated. The complete path from the service to the root of the tree (default_host) must be active.

(22)

© SAP AG Page 22 of 59 If you upgrade or implement a support package, the services may be deactivated. Therefore, check whether the services are still active after you have upgraded or implemented a Support Package.

Procedure

1. Access the following transaction: Transaction Code SICF

2. On the Maintain Service screen, in the Hierarchy Type field, enter Service and choose Execute.

3. Expand each hierarchy below and activate the following services. To do so, right-click the service and choose Activate Service for each service:

/default_host/sap/public/icman /default_host//sap/public/myssocntl /default_host/sap/public/bc* /default_host/sap/public/PPM/* /default_host/sap/bc/nwbc* /default_host/sap/bc/webdynpro/bcv* /default_host/sap/bc/webdynpro/rpm* /default_host/sap/bc/webdynpro/sap*

Result

You have activated all services relevant for this solution.

2.18 Check Delivery Customizing

SAP Project Portfolio Monitoring rapid-deployment solution also uses standard Customizing entries delivered by SAP in client 000.

Ensure that this Customizing is available in the implementation client.

You can either copy the client 000 or its customizing content to the implementation content. Alternatively, use the transaction /rpm/cust_copy to copy the PPM specific customizing. You should perform these steps before you activate the package content to avoid overwriting of customizing entries.

Procedure

1. Access the following transaction:

Transaction Code /n/RPM/CUST_COPY

2. On the Delete/Restore customizing table entries screen, enter client 000 in the Delivery client field

3. Select all customizing tables and choose Copy.

2.19 Activating Change Documents

(23)

Portfolio Buckets Items

Item Decision Points Reviews

Procedure

1. Access the activity using the following navigation option: Transaction Code SPRO

SAP IMG Menu SAP Portfolio and Project Management Portfolio Management Global Customizing Process and Service Settings

Activate Change Documents

2. On the Activate Change Documents screen, choose New Entries and create the following settings:

Appl. Object Type Description ChangeDocuments

PPM RBH Bucket X

PPM RIH Item X

PPM RPH Portfolio X

RPM EPO Decision point X

PPM RVO Reviews X

2.19.1 Define Units of Measurement

Use

In this step, you define the measurement unit Person Day.

If the SAP IT Portfolio and Project Management rapid-deployment solution is implemented with ERP integration you have to create the measurement unit Person Day also on the ERP System

This is a mandatory activity and should be completed in order to be sure that the solution works properly.

Procedure

1. Access the activity using the following navigation option: Transaction

Code

SPRO

IMG Path SAP Portfolio and Project Management Portfolio Management Global Customizing Global Settings Define Units of Measurement 2. On the Units of Measurement screen, choose the dimension Time and select Units of

Measurement.

(24)

entries:

Int. meas. Unit YPD

Commercial YPD

Technical YPDAY

Numerator 28.800

Denominator 1

Measurement Unit Text – Long text Person Day Measurement Unit Text – Short text Person Day

2.20 Set Webdynpro Parameters

Use

Depending the setup of the SAP Portfolio and Project Management system in the overall system landscape, it could be that the alignment of text is not properly processed. Therefore you can set a Webdynpro parameter to control the system parameter.

Procedure

6. Access the activity using the following navigation option: Transaction

Code

SE80

SAP Menu SAP Menu Tools ABAP Workbench Overview Object Navigator

7. Select Edit Object.

8. On the Object Selection screen, choose Enhanced Options. 9. Select the tab Web Object.

10. Insert the value RPM_ITEM_DETAILS in the filed Web Dynpro Application and choose Enter 11. Go to tab Parameters and in change mode add the Parameter

WDSTYLE_LABELALIGNMENT. 12. Enter LEFT in the column Value. 13. Save your entries.

2.21 Activate Mail Notifications for Decision Point Status

Changes

Use

A mail is to be sent out to the stakeholders whenever the status of a decision point changes.

Prerequisite

An e-mail address is maintained for the users that are to receive the mail notification. You have configured a user for executing the workflow that has sufficient authorization to send mail notifications.

(25)

Management system. For more information, see SAP Note 455140.

Procedure

2.21.1 Automatic Workflow Customizing

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

Code

SWU3

SAP Menu Tools Business Workflow Development Utilities Automatic Workflow Customizing

2. Read carefully through the documentation displayed and create all prerequisites

The user carrying out the workflow customizing should have sufficient authorizations to create RFC connections and workflow user (WF_Batch)

3. Choose from the Menu Auto customizing –Execute (F9).

2.21.2 Activate Portfolio and Project Management Workflows

1. Access the activity using the following navigation option: Transaction

Code

SPRO

SAP IMG Menu

SAP Portfolio and Project Management Portfolio Management Global Customizing Global Settings Workflow Settings Activate Workflows

2. On the Task Customizing Overview screen, choose SAP PPM PPM-PFM in the tree and choose Activate event linking.

3. On the Event Linkage: Triggering events screen, choose WS 00800006 and expand the node.

4. To activate the workflow for the event CL_RPM_DECISION-DECISION_POINT_STATUS_CHG, click the Deactivated pushbutton. The status changes and the workflow is activated.

5. Go back to the IMG structure.

8. Access the activity using the following navigation option: SAP IMG

Menu

SAP Portfolio and Project Management Portfolio Management Global Customizing Global Settings Workflow Settings Maintain

Configuration for Workflow Recipients

9. On the Map object types and activity types relevant for workflow screen, choose New Entries and create the following settings:

Object Type Activity Workflow ID

EPO Decision Point Admin Item Decision Point Status Change Workflow 10. Save your entries and go back.

2.21.3 Make Settings for Sending E-Mail Notifications

(26)

3. In the dialog box SAPconnect: General node data of node SMTP, next to the Internet checkbox, choose Set.

4. In the dialog box SAPconnect: Address type for node, in the Business Object/Link field, choose HTM as output format for SAP documents.

5. Choose Continue twice.

6. The system save the changes made.

Result

You have configured to send e-mails for decision point status changes.

The consultant defines which status changes trigger the e-mail notifications. For more information, see the Configuration Guide.

2.22 Configuring the Business Context Viewer

Use

The Business Context Viewer is used to display graphics in the context of the portfolio. To render graphics, the Business Context Viewer requires the Internet Graphics Server to be configured.

Prerequisites

You have activated the business function /BCV/MAIN.

Procedure

1. Access the following transaction: Transaction Code SQ01

2. On the Query from User Group <User Group Name>: Initial Screen, select the user group /RPM/BCV_USR (usually it is proposed by default, but it is possible to select the user group form the Menù Enviroment --> user groups ).

3. Generate the following queries choosing Query More Functions Generate Program: Query Name Title

QUE_BUCK_FD Bucket Financial Data

QUE_BUC_FD_T Bucket Financial Data by Timeline QUE_BUD_VAR Item Budget Variance

QUE_CAP_PLN InfoSet Query to get Capacity Planning data QUE_FIN_PLN InfoSet Query to get Financial Planning data QUE_ITEMS InfoSet Query to get Item Data for Reporting

QUE_ITEMS_C InfoSet Query to get Item Data – Cmplx. Column Chart QUE_ITEMS_G InfoSet Query to get Item Data – Cmplx. Gantt Chart QUE_ITEM_FD Item Financial Data

QUE_ITEM_FD_T Item Financial Data by timeline

QUE_ITEM_F_KPI Infoset Query to get financial KPIs for Item for Reporting QUE_PHASES InfoSet Query to get Phase/Decision Point Data

QUE_PHASES_G InfoSet Query to get Phase/Dec Pt. Data – Cmplx Gantt Chart QUE_PLAN_ACT Item Financial Analysis: Plan versus Actual Cost

(27)

QUE_PRJ_COST_C InfoSet Query to get Fin. Costs Data – Cmplx. Column Chart Optionally, the following queries can be generated:

Query Name Title

QUE_INIT Infoset Query to get Initiative data for Reporting

QUE_INIT_C Infoset Query to get Initiative Data - Cmplx. Column Chart QUE_INIT_FD Initiative financial data

QUE_INIT_FD_T Initiative Financial Data by Timeline

QUE_INIT_F_KPI Infoset Query to get Initiative data for Reporting

QUE_INIT_G Infoset Query to get Initiative Data - Cmplx. Gantt Chart 4. Go back.

5. On the Query from User Group <User Group Name>: Initial Screen, select the user group DPR_USER_G.

6. Generate the following queries choosing Query More Functions Generate Program: Query Name Title

DPR_QUE_BUAV Business Partner Availability DPR_QUE_BUST Business Partner Staffing

DPR_QUE_COBU Confirmation with Business Partner Data DPR_QUE_COPA Confirmation Plan Actual

DPR_QUE_COPR Project Confirmation DPR_QUE_RODE Role Demand DPR_QUE_ROST Role Staffing

7. Access the activity using the following navigation option: Transaction Code SPRO

SAP IMG Menu Cross-Application Components Processes and Tools for Enterprise Applications Business Context Viewer User Interface Define Dashboards

8. On the Dashboard screen, select the entry with context key RPM_ITEM_FPA and dashboard key 1RPM_D_FIN_ANLYS.

9. Choose Delete. 10. Save your entries.

11. To display the graphics in the Business Context Viewer, you need to create an RFC Destination for the Internet Graphics Server. Access the activity using one of the following navigation options:

Transaction Code SM59

12. To create an RFC connection, choose Create.

(28)

RFC Destination IGS_RFC_DEST Connection Type T

Description Generated RFC destination for IGS

14. Choose Enter.

15. On the Technical Settings tab, create the following settings: Field Name Entry Value

Activation Type Registered Server Program Program ID IGS.<PPM System ID> 16. Save your RFC destination.

You can test the RFC connection by choosing Connection Test.

2.23 Logical Systems

Use

To enable communication between Portfolio Management and Project Management, you must Define the systems as logical systems.

Assign the logical system for the SAP PPM system to a client.

If the logical system has already been created, you can skip the activities described in this section.

Logical systems are defined on a cross-client basis

2.23.1 On the PPM System – Define and assign the Logical

System

Procedure

1. Access the activity using the following navigation option: Transaction Code BD54

IMG Path SAP NetWeaver Application Server IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical Systems Define Logical System

2. Confirm the warning message Caution: The table is cross-client. 3. Choose the New Entries pushbutton.

4. In the Log.System column, enter a name for the PPM logical system you want to create.

We recommend that you use the following naming convention: <system ID>CLNT<client number> (for example: NXDCLNT085)

<system ID> is the ID of your SAP PPM system.

(29)

Logical System <PPM system ID>CLNT<client> (for example, NXDCLNT085)

Name Logical System for PPM

6. Access the activity using the following navigation option:

SAP Easy Access Menu Tools Administration Administration Client Administration Client Maintenance

Transaction Code SCC4 7. Choose Display Change.

8. Confirm the warning message Caution: The table is cross-client.

9. Select the entry for the client of your SAP Portfolio and Project Management system and choose Details.

10. In the Logical System field, enter the newly created logical system, e.g. NXDCLNT085 11. Save and confirm the warning message Be careful when changing the logical system. 12. Choose the Back pushbutton twice.

13. If the SAP IT Portfolio and Project Management rapid-deployment solution is implemented with ERP integration, repeat steps 3-5 to define the ERP Logical system

Field Name Value

Logical System <ERP system ID>CLNT<client> (for example, RD7CLNT020)

Name Logical System for ERP

2.23.2 On the ERP System - Define and assign the Logical

System

If the SAP IT Portfolio and Project Management rapid-deployment solution is implemented with ECC 6.0 integration, you have to create and assign the ERP logical System

Procedure

1. Access the activity using the following navigation option: Transaction Code BD54

IMG Path SAP NetWeaver Application Server IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical Systems Define Logical System

2. Confirm the warning message Caution: The table is cross-client. 3. Choose the New Entries pushbutton.

4. In the Log.System column, enter a name for the logical system you want to create.

We recommend that you use the following naming convention: <system ID>CLNT<client number> (for example: RD7CLNT020)

(30)

Logical System <ERP system ID>CLNT<client> (for example, RD7CLNT020)

Name Logical System for ERP

6. Access the activity using the following navigation option:

SAP Easy Access Menu Tools Administration Administration Client Administration Client Maintenance

Transaction Code SCC4 7. Choose Display Change.

8. Confirm the warning message Caution: The table is cross-client.

9. Select the entry for the client of your SAP Portfolio and Project Management system and choose Details.

10. In the Logical System field, enter the newly created logical system, e.g. RD7CLNT020 11. Save and confirm the warning message Be careful when changing the logical system. 12. Choose the Back pushbutton twice.

2.24 Roles

2.24.1 Uploading Roles

Use

In this activity, you define the roles for navigation in the NWBC for PPM system.

The following NWBC roles are delivered with this solution package and are attached to the SAP Note 1968343

Business Role Technical Name

Portfolio Admin YNSAP_BPR_PPM_ADMIN

Portfolio Manager YNSAP_BPR_PPM_PORTFMGR

Project Manager YNSAP_BPR_PPM_PROJMGR

Portfolio Review Board YNSAP_BPR_PPM_PORTFREV

Employee YNSAP_BPR_PPM_EMPL

Resource Manager YNSAP_BPR_PPM_RESMGR

In addition, the following roles are available as standard and should be assigned to the users: For Portfolio Management:

SAP_XRPM_USER

SAP_XRPM_ADMINISTRATOR For Project Management:

SAP_CPR_PROJECT_LEAD For the Business Context Viewer (BCV):

(31)

SAP_XRPM_USER should be assigned to all users.

SAP_XRPM_ADMINISTRATOR should be assigned to portfolio administrators who should have for example the authority to create portfolios and to maintain all portfolio The composite role SAP_CPR_PROJECT_LEAD contains the single role

SAP_CPR_USER, which must be included in every composite role, and the single role SAP_CPR_PROJECT_ADMINISTRATOR, which allows projects to be created.

Procedure

Transaction Code PFCG

2. On the Role Maintenance screen, choose Role Upload.

3. Select the YN*.SAP file delivered with this solution (that is, YNSAP_BPR_PPM_ADMIN.SAP) and upload the role.

4. Repeat the upload for all YN* roles.

2.24.2 Updating Roles

Use

You must update the standard and the newly created roles before they become active in the user profiles.

Procedure

1. Access the following transaction: Transaction Code SUPC

2. On the Roles: Mass generation of profiles screen, select the All roles checkbox radio button. 3. In the Role field, enter YNSAP_BPR_PPM*

4. Select the Generate Automatically checkbox. 5. Choose Execute.

6. In the Generate Authorization profiles dialog box, select Online 7. Choose Save.

(32)

3 Activation of Business Content

The following section describes the activities that are carried out by the consultant activating SAP Best Practices in the system (“activation user”).

For detailed information on the usage of SAP Best Practices solution builder refer to this guide: http://service.sap.com/~sapidp/011000358700000283592014E/

3.1 Prerequisites

3.1.1 Initial Check of System Readiness

Ensure that the system administrator has finished all activities as described in section 2 System Setup & Preparation.

You are required to check if your system administrator has applied the correct SPS level as outlined above in section Release and Support Package Level.

Only continue with the following steps if these prerequisites are met.

3.1.2 Check Content Prerequisites in the Client

3.1.2.1 Prerequisites and Assumptions for ECC configuration settings

Prerequisite

For consistent integration between ERP and PPM, some fundamental ECC configurations must be set up as prerequisites.

These settings are required only for Scenarios with ERP Integration.:

K23 - IT Portfolio Management & Monitoring and IT Project Management (with ERP integration)

K24 - IT Project Management (with ERP integration)

If you are implementing a process without ERP integration, you can skip the activities described in this section.

Use

This step ensures that the PPM required Controlling Areas and Company Codes are defined and configured in the corresponding ERP backend system.

Procedure

1. To define the Controlling Area: SAP Easy Access

Menu

IMG Enterprise Structure Definition Controlling Maintain Controlling Area

Transaction Code OX06

This step validates that the PPM required Controlling Area (for example: controlling area 1000) is defined in the ECC backend system.

1. To define the Company Code: SAP Easy Access

Menu

IMG Enterprise Structure Definition Financial Accounting Edit, Copy, Delete, Check Company Code

(33)

1. To maintain the Controlling Area and Company Code assignment. SAP Easy Access

Menu

IMG Enterprise Structure Assignment Controlling Assign company code to controlling area

Transaction Code OX19

This step validates that the PPM required Company Codes are assigned to the corresponding Controlling Area in the ECC backend system.

3.1.2.2 Project Profile

Use

This step is to ensure that the PPM required Project Profile for automation has been configured in ECC backend system with correct organization level settings.

Procedure

1. To maintain Project Profile CPR0001 as required by the PPM solution automation, access the transaction using one of the following methods:

SAP Easy Access Menu

IMG Project System Structures Operative Structures Work Breakdown Structure (WBS) Create Project Profile

Transaction Code OPSA 2. Select entry CPR0001. 3. Choose the Organization tab.

4. Validate the assigned Controlling Area and Company Code as required by the PPM solution. Otherwise, you may encounter errors when triggering project creation automatically from PPM to ECC.

3.1.2.3 Model Order

Use

This step ensures that the PPM required Project Profile for automation is configured in the ECC backend system with correct organization level settings.

Procedure

1. To define order types for internal orders: SAP Easy Access

Menu

IMG Controlling Internal Orders Order Master Data Define Order Types

Transaction Code KOT2_OPA 2. Select entry CPR1.

3. Validate that the Model Order field contains “$CPR1”

4. Validate that the Model Order $CPR1 is created in the ECC back-end system (transaction KOM2).

3.1.2.4 Master Data

A range of indispensable master and organizational data (for example, master data for Financial Accounting and Controlling) forms the basis of this package and are required in the ERP system to complete the Business Processes.

(34)

© SAP AG Page 34 of 59 For example, the master data used for this package consist of standardized SAP Best Practices default values and the SAP Best Practices Baseline Packages is used as basis for this package.

The “Financial_Capacity_Planning.zip” file attached to SAP note 1968343 provides the detail of Cost elements, Cost centres and Activity Types used in customizing by the solution.

If you have the requirement to personalize the Organizational Unit values, please refer to the chapter “Personalize your solution”.

3.1.3 Activation Language

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

3.1.4 User Settings for Activation

For activation, we recommend using only one user ID to activate SAP Best Practices content. It can be a tedious procedure to change ownership of the activation of the solution.

3.1.4.1 Deactivate Info Dialog Box on Dynpro Size Check

Use

This section is only relevant for SAP internal users.

To prevent the dialog box Sizing conflicts may appear from appearing during activation, you can deactivate the screen size check.

Procedure for GUI Version Below 720

1. Log on with the user in the system.

2. Choose the first button on the right of the standard toolbar (Customize Local Layout) or choose ALT + F12.

3. Choose the Options menu item. 4. Choose the Options tab.

5. Deselect the Enable Dialog Box for Dynpro Size Check checkbox. 6. Choose OK.

Procedure for GUI Version 720 and above

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

2. Choose the first button on the side of the standard toolbar (Customize Local Layout) or choose ALT + F12.

3. Choose the Options menu item. 4. Choose the SAP Internal node. 5. Choose SAP Internal.

6. Deselect the Enable Dialog Box for Screen Size Check checkbox. 7. Choose OK.

Repeat all the steps for the ECC system if you are activating an integrated scenario with two different systems.

Quick Guide to Implementing the SAP IT Portfolio and Project Management Rapid- Deployment Solution V2.60

SAP Portfolio and

Project Management

6.0

April 2014

English

Quick Guide to

Implementing the SAP IT

Portfolio and Project

Management

Rapid-Deployment Solution

V2.60

Copyright

Icons

Typographic Conventions

Contents

Quick Guide to Implementing the SAP IT Portfolio

and Project Management Rapid-Deployment

Solution V2.60

Purpose

1 Solution Overview

2 System Setup & Preparation

2.1 Release and Support Package Level

Receiving the Software at the Correct SP Level

2.2 Required Product Versions and Software

Components

2.2.1 SAP Portfolio and Project Management 6.0

2.2.2 EhP7 for SAP ERP 6.0

2.3 SAP Frontend Components

2.3.1 Java runtime environment (JRE)

Procedure

2.4 SAP Solution Manager and SAP Solution Manager

Content Add-on

2.5 SAP Best Practices Add-on and SAP Best Practices

Solution Builder Add-on

2.6 General Client Settings

2.7 SAP Enterprise Extensions Sets and Business

Functions

Use

Procedure

2.8 SAP Notes and Messages

2.9 Creating a User for Activation of SAP Best Practices

Content

Use

Procedure

Result

2.10 Preparation of Logical Components Used in

SAP Solution Manager Implementation Project

2.11 Creating Transport Requests for Activation

Creating a Workbench / Customizing Request

Result

2.12 Deselecting Activation Links in BC Sets

Procedure

2.13 Setting the Maximum Work Process Run Time

Use

Procedure

Result

2.14 SAP Scripting

Use

Procedure

2.15 Setting Default Timeout for HTTP and HTTPS

Services

Use

Procedure

2.16 Configuring the Print Environment

Use

Prerequisites

Procedure

2.17 Activating Services

Use

Procedure

Result

2.18 Check Delivery Customizing

Procedure

2.19 Activating Change Documents

Procedure

2.19.1 Define Units of Measurement

Use

Procedure

2.20 Set Webdynpro Parameters