589 Planning And Reporting With Web Dynpro 589_erp607_bb_configguide_en_us.doc

EHP7 for SAP ERP 6.0 February 2014 English

Planning and Reporting with Web Dynpro (589) Building Block Configuration Guide

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Planning and Reporting with Web Dynpro (589): Configuration Guide

Copyright © 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SE

Page 6 of 8

SAP Best Practices

Planning and Reporting with Web Dynpro (589): Configuration Guide

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, buttons 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 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 SE

F2)

or the

Page 6 of 8

SAP Best Practices

Planning and Reporting with Web Dynpro (589): Configuration Guide

Content 1

Purpose............................................................................................................................. 5

2

Preparation........................................................................................................................ 5 2.1

3

ODP Reporting.................................................................................................................. 5 3.1.1

4

Prerequisites............................................................................................................ 5 Maintaining BW Client Settings...........................................................................5

3.2

Basic Configuration for Operational Analytics..........................................................6

3.3

Set TREX Destination.............................................................................................. 6

3.4

Specify Client for Modeling......................................................................................7

3.5

Content Bundle activation for ODP Reporting.........................................................7

CO Planning...................................................................................................................... 9 4.1

Basic Configuration for Operational Analytics..........................................................9

4.1.1

Use RSTCO_ADMIN to check status..................................................................9

4.1.2

Start activation a second time using RSTCO_ADMIN in case of problems.......10

4.2

Activate Data Sources........................................................................................... 10

4.3

Content Bundle activation for CO Planning...........................................................10

4.4

Run Report RSICF_SERVICE_ACTIVATION........................................................11

4.5

Activation of Services for CO Planning..................................................................12

© SAP SE

Page 6 of 8

SAP Best Practices

Planning and Reporting with Web Dynpro (589): Configuration Guide

Planning and Reporting with Web Dynpro 1 Purpose This configuration guide provides the information you need to set up the configuration of this building block manually. If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the Quick Guide.

2 Preparation 2.1 Prerequisites Read the Quick Guide document delivered with the specific SAP Best Practices for SAP Business All-in-One installation. Ensure that you meet the recommended prerequisites. Before you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix, located on the documentation package on the Technical  Content Library page.

3 ODP Reporting 3.1.1

Maintaining BW Client Settings

Use You must maintain the client settings for BW to ensure that the implementation activities for CO planning and reporting work properly. This setting is done in BW client. Log in to your BW client to perform these steps

Procedure Carry out the following steps: 1. Access the activity using one of the following navigation options: IMG Menu

N/A

Transaction Code

SCC4

2. On the Display View: “Clients”: Overview screen, switch to the change mode. 3. Select your BWclient, and choose Details. 4. Maintain the following settings: Field name

Description

User action and values

Comment

LOGSYS

Logical System

Select the logical system of the current client

Defined before

CCCATEGORY

Client Role

Customizing

© SAP SE

Page 6 of 8

SAP Best Practices

Planning and Reporting with Web Dynpro (589): Configuration Guide

Field name

Description

User action and values

CCCOR_ACTV

Automatic Recording of Changes

Select

CCNOCLIIND

Cross-Client Object Changes

Changes to Cross-Client Customizing and Repository Objects allowed

Comment

5. Save your settings.

3.2 Basic Configuration for Operational Analytics Use Before you can use Operational Analytics, you must first complete the basic configuration for SAP NetWeaver BW on your system. This allows you to use operational data provisioning and Classic InfoSets in BI tools. This setting is done in the BW client. Log on to your BW client to perform these steps.

Procedure Carry out the following steps: 1. Access the activity using one of the following navigation options: IMG menu

SAP NetWeaver  Serch and Operational Analytics  Operational Data Provisioning for Operational Analytics  Basic Configuration for Operational Analytics

Transaction Code

RSRTS_ACTIVATE_R3IS

2. On the Basic Configuration for Operational Analytics screen, in the BW Client field, enter your BW client and choose Execute. 3. In the dialog box, deselect the checkbox. 4. Choose Execute. 5. Wait for the job to complete, and check the Job log.

3.3 Set TREX Destination Use If a separate SAP HANA/BWA is not connected to the system, you can only activate Operation Data Providers if an explicit RFC connection NO TREX is defined here. This setting is done in the BW client. Log on to your BW client to perform these steps.

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

© SAP SE

SAP NetWeaver  Search and Operational Analytics Common Settings for Operational Analytics and Embedded Search  Configure Indexing Set TREX/BWA Destination or SAP HANA DB Connection Page 6 of 8

SAP Best Practices

Transaction Code

Planning and Reporting with Web Dynpro (589): Configuration Guide

ESH_ADM_TREX_DEST

2. On the Set the RFC destination of TREX or DB connection for HANA DB screen, make the following entries: Field

User Action or Values

Use TREX

Selected

RFC destination of TREX

NO_TREX

Comments

3. Choose Execute.

3.4 Specify Client for Modeling Use The analytic query is defined on a cross-client basis. Therefore, the ODP modeling for the underlying Transient Provider must only be read from one single client. You specify this client as a modeling client (for search and analysis) in this step. Use this step to specify the RFC destination that is used to read the ODP modeling. This allows you to run the query on other clients as well. This setting is done in BW client. Log in to your BW client to perform these steps

Procedure Carry out the following steps: 1. Access the activity using one of the following navigation options: IMG menu

SAP NetWeaver  Search and Operational Analytics  Operational Data Provisioning for Operational Analytics  Specify Client for Modeling

Transaction Code

RODPS_ODP_IMG

2. On the Define Modeling screen, make the following entries: Field

User Action or Values

Modeling client



Destination

<destination client>

Comments

3. Choose Execute. 4. Wait for the job to finish, and check the job log.

3.5 Content Bundle activation for ODP Reporting Use To use new ODP Simplified Report you should activate the BW content . This setting is done in

BW client. Log in to your BW client to perform these steps

Procedure © SAP SE

Page 6 of 8

SAP Best Practices

Planning and Reporting with Web Dynpro (589): Configuration Guide

Carry out the following steps: IMG activity to activate the Content Bundle: 1. Access the activity using one of the following navigation options: IMG menu

Controlling  General Controlling  Roles for NetWeaver Business Client Project Planner and Cost Estimator  Activate BI content Bundle for Planning

Transaction code

BSANLY_BI_ACTIVATION

2. On the BI Content Activation Workbench: Content Bundle Overview screen, for Business Category, select 03-Business Functions. By Default the values is 01 and grayed out (press F4 and select 03) 3. Select the row with the Technical Name FIN_REP_SIMPL_4 and choose Activate. Note: If the content bundle has a status of Activation Finished with green light, do not activate again. 4. On BI Content Activation Workbench: Activate Content Bundle screen, select RFC mapping. 5. On Maintain RFC Mapping Dialog box, select the Local checkbox and in Dialog RFC Connection field, enter NONE. Choose Enter. You do not need the RFC mapping functionality for the local planning content. 6. For the RFC Destination for Content Objects, select NONE. 7. Select No Data Source Replication. 8. For the Treatment of Already Active Content Objects, choose Copy and Install all Collected Objects. 9. Choose Activate. If the content bundle is already activated, the system displays the message Do you want to reactivate already activated content bundles? Choose Cancel. 10. In the Select Source Systems dialog box, under Self-def'd, select Logical System for BW client and choose Enter. 11. Check the activation log. If the log shows many red traffic lights, reactivate. In many cases, the second run of the installation solves most of the issues.

© SAP SE

Page 6 of 8

SAP Best Practices

Planning and Reporting with Web Dynpro (589): Configuration Guide

4 CO Planning 4.1 Basic Configuration for Operational Analytics Use To use the new CO planning template, activate the BW content. This setting is done in BW client. Log in to your BW client to perform these steps

Procedure Carry out the following steps: 1.

Access the activity using the following navigation options: IMG Menu

SAP NetWeaver  Search and Operational Analytics  Operational Data Provisioning for Operational Analytics  Basic Configuration for Operational Analytics

Transaction Code

SPRO

2. In the BW Client field, enter your client and choose Execute. 3. In the dialog box, deselect the checkbox. 4. Choose Execute. 5. Wait for the job to finish and check the job log.

4.1.1

Use RSTCO_ADMIN to check status

Transaction Code

RSTCO_ADMIN

Call Transaction and check if the Installation status is green: Click Display Log and check if the log looks similar to this without any red error messages:

Keep in mind that the activation is executed for the user DDIC. If there are red error messages and authorization problems mentioned in the job log, assign the user DDIC at least to the role SAP_BW_BI_ADMINISTRATOR or provide him or her with the SAP_ALL authorization.

4.1.2

Start activation a second time using RSTCO_ADMIN in case of problems

Transaction Code © SAP SE

RSTCO_ADMIN Page 6 of 8

SAP Best Practices

Planning and Reporting with Web Dynpro (589): Configuration Guide

1. If the log shows many red traffic lights, use Start Installation in transaction RSTCO_ADMIN. 2. to run the installation a second time. Wait until the batch job BI_TCO_ACTIVATION is finished and check the log again using transaction RSTCO_ACDMIN. 3. In many cases, the second run of the installation solve most of the issues.

4.2 Activate Data Sources Use In this step, you transfer and activate the DataSources delivered by SAP as well as partner DataSources delivered in your own namespace where applicable. This setting is done in BW client. Log in to your BW client to perform these steps.

Procedure 1. Access the activity using the following navigation options: IMG Menu

N/A

Transaction Code

RSA5

2. Expand the complete SAP structure. 3. Use the Find functionality to jump to the following DataSources: 

0FI_GL_21



0FI_GL_41



0GL_ACCOUNT_COCD_ATTR

4. Position the cursor on the DataSource, choose Select Sub-Tree and Activate DataSource.

4.3 Content Bundle activation for CO Planning Use To use new CO planning template, you should activate the BW content. This setting is done in BW client. Log in to your BW client to perform these steps.

Procedure Carry out the following steps: IMG activity to activate the Content Bundle: 1. Access the activity using one of the following navigation options: IMG menu © SAP SE

Controlling  General Controlling  Roles for NetWeaver Business Page 6 of 8

SAP Best Practices

Planning and Reporting with Web Dynpro (589): Configuration Guide

Client Project Planner and Cost Estimator  Activate BI content Bundle for Planning Transaction code

BSANLY_BI_ACTIVATION

2. On the BI Content Activation Workbench: Content Bundle Overview screen, for Business Category, select 03-Business Functions. By Default the values is 01 and grayed out (press F4 and select 03). 3. Select the row for Technical Name /ERP/FCOM_PLANNING and choose Activate.

Note: If the content bundle has a status of Activation Finished with green light, do not activate again. 4. On the BI Content Activation Workbench: Activate Content Bundle screen, select RFC mapping. 5. On the Maintain RFC Mapping dialog box, select the Local checkbox and in the Dialog RFC Connection field, enter NONE and choose Enter. You do not need the RFC mapping functionality for the local planning content. 6. For the RFC Destination for Content Objects, select NONE. 7. Select No Data Source Replication. 8. For the Treatment of Already Active Content Objects, choose Copy and Install all Collected Objects. 9. Choose Activate.

Note: If the content bundle is already activated, the system displays the message Do you want to reactivate already activated content bundles? Choose Cancel. 10. On the Select Source Systems dialog box, under Self-def'd, select Logical System for BW client and choose Enter. 11. Check the activation log. If the log shows many red traffic lights, reactivate. In many cases, the second run of the installation solve most of the issues. 12. If you still receive errors in content bundle activation, see the Quick guide (Processing of Scenario Specific Errors section).

4.4 Run Report RSICF_SERVICE_ACTIVATION Use Process this activity to make sure that the service is activated in your ECC client. This setting is done in ECC client.

Procedure Carry out the following steps: 1. Access the activity using one of the following navigation options: SAP ECC menu © SAP SE

Tools  ABAP Workbench  Development  ABAP Editor Page 6 of 8

SAP Best Practices

Planning and Reporting with Web Dynpro (589): Configuration Guide

Transaction Code

SE38

2. On the ABAP Editor: Initial Screen, enter the source program RSICF_SERVICE_ACTIVATION and Execute. 3. Technical name: WEB DYNPRO ABAP and Execute.

4.5 Activation of Services for CO Planning Use Process this activity to make sure that the service is activated in your ECC client. This setting is done in ECC client.

Procedure Activate the services needed for the New CO Planning and reporting function: 1. Call transaction SICF. 2. On the Maintain Services screen, choose Execute (F8). 3. On the Maintain service screen, expand the Virtuelle Hosts / Services node as follows and activate all the following services: default_host

Sap

bc

webdynpro

Sap

FCOM_IP_CC_ACTOUTPUT01

default_host

Sap

bc

webdynpro

Sap

fcom_ip_cc_costelem01

default_host

Sap

bc

webdynpro

Sap

FCOM_IP_ORD_COSTELEM01

default_host

Sap

bc

webdynpro

Sap

fcom_ip_proj_actinput01

default_host

Sap

bc

webdynpro

Sap

fcom_ip_proj_costelem01

default_host

Sap

bc

webdynpro

Sap

FCOM_IP_PROJ_OVERALL01

4. Choose Back.

© SAP SE

Page 6 of 8