Bpc Nw Quick Guide en De

SAP BusinessObjects Planning and Consolidation 7.5, version for the Netweaver platform

August 2011

English

Quick Guide to Implementing the SAP Best Practices BPC(NW) Package V1.75

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

1.1.1

SAP Best PracticesQuick Guide to Implementing the SAP Best Practices for BPC (NW) Package V1.75 (GLOBAL)

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

© SAP AG Page 2 of 29


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.



IconsIcon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.Cross-references to other documentation.

Example text 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.



Contents

1 Purpose...........................................................................................................62 System Setup & Preparation – System Administrator.....................................6

2.1 Install SAP ERP System.................................................................................62.2 Install Business Information Warehouse (BW) System...................................72.3 Install SAP Business Objects Planning and Consolidation.............................7

2.3.1 Release and Support Package Level..............................................................72.3.2 Important Steps in Installation.........................................................................7

2.4 SAP Notes and Messages............................................................................142.5 Preparation Activities....................................................................................14

2.5.1 User Creation in Windows Server.................................................................142.5.2 IE Configuration – Logging on Interface for Web..........................................152.5.3 Prepare Transaction Data in ERP system.....................................................16

3 Activation of Business Content / Scenarios – Activation consultant..............233.1 Activation Sequence of Scenarios................................................................233.2 Error Handling: Installation Errors during Activation......................................24

3.2.1 Dynamic Hierarchy Editor not shown............................................................243.2.2 Dimension XXX does not have a XXXX property..........................................243.2.3 How to delete a BPF template.......................................................................253.2.4 Application XXXX was not found...................................................................25

4 Historical Data Preparation...........................................................................254.1 Historical Data for Planning related Business Scenarios..............................254.2 Historical Data for Consolidation Business Scenario (B64)..........................26

5 Error Handling: Usage Errors........................................................................275.1 Encounter error message “Failed to get next member of range member

(UJJ_JRNID).................................................................................................275.2 Encounter error messages in Work Status...................................................285.3 Encounter error message “Root element is missing”....................................285.4 Encounter error message “EVDRE disabled. Initial cache first”....................285.5 EVDRE encountered an error retrieving data from Web Server...................285.6 Reset Business Process Flow......................................................................28

6 Security Aspects – System Administrators....................................................286.1 User Administration and Authentication........................................................286.2 Roles Management.......................................................................................296.3 RFC Destinations..........................................................................................29



Quick Guide to Implementing the SAP Best Practices for BPC Package V1.75 (Global)

2 PurposeThis quick guide provides the information you need to activate the complete SAP Best Practices for BPC (Net Weaver) Global Package step by step. It also explains how to proceed if you want to implement individual scenarios instead.Before proceeding with this document,

The scope relevant for you need to be defined The technical prerequisites have to be finalized The required resources (see involved roles) need to be available

This document does not provide a general overview and explanations of SAP Best Practices. For general information regarding content and positioning, refer to the SAP Best Practice documentation CD/DVD. This document is intended for

System administrators / basis consultants Business consultants

who already have a sound knowledge of SAP Best Practices, including the tools and documentation. The following chapters are assigned to the roles required for it.

3 System Setup & Preparation – System Administrator

The deliverables of SAP Best Practices were developed and tested in a system landscape with specific support package levels. The mentioned Support Package Stack (SPS) is the minimum level that must be applied to the system before you can use the relevant SAP Best Practice package, and this is also the recommended level.

3.1 Install SAP ERP System SAP Best Practices Baseline packages V1.604SAP Best Practices for Business Warehousing was developed based on the latest Baseline versions for the following countries, which considered as the Source System for BW:

Germany (SAP Note 1408706)For detailed information, refer to the respective SAP Best Practices Baseline Package in the SAP Help Portal:http://help.sap.com SAP Best Practices Baseline Packages Based on SAP ECC 6.0 Country of your choiceThe Quick Guide for each Baseline Package is attached to the SAP Note specified above.



3.2 Install Business Information Warehouse (BW) System

The SAP Best Practices scenarios have been tested in an environment with a system landscape components on certain release levels and support package levels specified in the following sections.If the release and support package levels do not match the indicated levels, errors might occur. The documentation is based on the menu paths and transaction views as they appear in the given system environment.Therefore, we recommend that you use the release and support package levels prerequisites given below for each involved system. After the installation, you can upgrade to the latest release and support packages.

Application Component

Software Component

Release Level Highest Support Package

SAP BW SAP_BASIS 701 0007 SAPKB70107

SAP_ABA 701 0007 SAPKA70107

SAP_BW 701 0007 SAPKW70107

PI_BASIS 701 0007 SAPK-70107INPIBASIS

BI_CONT 704 0007 SAPK-70407INBICONT

3.3 Install SAP Business Objects Planning and Consolidation

Prior to installing an SAP Best Practices package, the target SAP application (for the SAP Best Practices for BPC Package, this would be SAP BusinessObjects Planning and Consolidation, version for Netweaver platform) must be installed up to the specific SAP Support Package with the correct SAP Notes applied as specified in detail in section SAP Notes and Messages in this guide.

3.3.1 Release and Support Package Level Application Release SP Level

SAP BPC, version for the Netweaver platform 7.5 SP06

3.3.2 Important Steps in Installation Refer to the Installation Guide SBOP_PC_75_NW_SP06_Install.pdf. For the confusing steps, we have listed as following:

3.3.2.1 Step 3.3 Configuring the ABAP Server Component1. For Step 3 in this part: ensure user ALEREMOTE is created with appropriate

authorization with profile S_BI-WX_RFC (Please use T-Code SU01 and enter the information with reference to the following data, then choose Save).



2. For step 4 in this part, using transaction RSTPRFC set up transports by creating the RFC destination for the After Import method. Save the password, and then assign the BW client. (Please use T-code RSTPRF and enter the information with reference to the following data, then choose Save.)

3. For step 5 in this part, using transaction SM59, run a connection test on the RFC destination MDX PARSER.(Please use T-code: SM59, choose connection MDX PARSER, then choose Connection Test. Ensure the connection is OK. )





4. For Step 6 in this part, assign the authorization SAP_BW_CONTENT_ADMIN to the user installing ApShell as the Planning and Consolidation system administration user to activate business content (such as default BW objects). (In our solution, the relevant user is BPC_SYSADMIN. Please use t-code: SU01, enter the information with reference to the following data, then choose Save)

5. For step 7 in this part, assign profile S_RS_ALL to the Planning and Consolidation system administration user. We recommend that you also assign the SAP_ALL profile during the installation process of ApShell. You can remove the SAP_ALL profile after the installation.( In our solution, the relevant user is BPC_SYSADMIN .Please use T-Code SU01 and enter the information with reference to the following data, then choose Save )



6. For step 8 in this part: If they do not already exist, create entries in the BPC Transports table by doing the following:

- Go to transaction SM30.- Enter the table name UJT_TRANS_CHG, then click Maintain.- Choose New Entries.- From the T Logo Object column, select one of the available entries from the listbox, then select Development in the adjacent column.- Repeat step 8d for each available item in the listbox in the TLogo Object column.- After all entries have been added, click Save.(Please use T-code: SM30, choose Maintain. Maintain the table as follows, choose Save.)



7. For step 9 in this part, Install ApShell by doing the following:- Run the program UJS_ACTIVATE_CONTENT. (T-code: SE38)- In the Content Activation window, set the AppSet ID toApShell and the Content Version to 1.- Choose the following options: Update Default Users Update Default Formula Table Update Client Options Update Language Activate SAP NetWeaver BW content objects for Planning and Consolidation Update Default DM (Data Manager) Instructions Activate ApShell



8. For step 10 in this part, Define the .NET service user that is needed to log on to ApShell and run Server Manager by doing the following:

- Stop the IIS and SAP Planning and Consolidation instances using the stoposoft.bat file.

- Go to transaction SE38 and run program UJA3_WRITE_SYS_USERS.



(While running UJA3_WRITE_SYS_USERS, please make the input as follows, then choose execute.)

3.4 SAP Notes and MessagesIf issues become apparent after shipment of this BPC Package (and hence of this document), an SAP Note exists to cover such eventualities.

Before you start the activation of the related SAP Best Practices scope, 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 Component

1620123 SAP Best Practices for BPC (NetWeaver) V1.75 Global Version

SV-SMB-AIO-BP-BPC

3.5 Preparation ActivitiesUseAfter installing SAP BusinessObjects Planning and Consolidation, applying the required SAP SP and SAP Notes, you can prepare your system for activation.

3.5.1 User Creation in Windows Server

UseIn both planning scenarios and consolidation scenario, different users access BPF to accomplish different tasks, for example sales representative user BPF to do the planning and submit data, sales manager approves data. These user accounts have to be created in Windows Server in advance.

Procedure1. In Windows Server, create users by choosing Start Settings Control Panel

Administration Tools Computer Management Local Users and Groups, then in the right window, right click and select New User.

2. Below table list all the necessary users required in BP for BPC China V1.75 package.

User ID Full Name Where used

User_S000 S000 Operation User Consolidation Scenario






Manager_S000 S000 Manager Consolidation Scenario




Conso Consolidation User in Holding Company

Consolidation Scenario

Mgr_HR HR Manager Planning Scenario

Mgr_FI FI Manager Planning Scenario

Mgr_IT IT Manager Planning Scenario

Mgr_S2 Sales Team 2 Manager Planning Scenario

Mgr_ S1 Sales Team 1 Manager Planning Scenario

Planner_S1 SalesHQ Planning User Planning Scenario

Planner_S2 SalesTeam1 User Planning Scenario

Planner_HR SalesTeam2 User Planning Scenario

Planner_FI FI Planner Planning Scenario

Planner_IT IT Planner Planning Scenario

BPC_SYSADMIN System User

BPC_ADMIN System User

BPC_USER System User

3.5.2 IE Configuration – Logging on Interface for Web

UseBefore Log on interface for web, please make following setting and make sure there is a pop-up window to ask you enter user name and password.

Procedure



1. Open Windowns internet Explorer Brower.2. Choose Tool Internet Options.

3. Choose Security tab.

4. Make setting as screenshot in both Local intranet and Trusted sites zone:

5. Choose OK and exit.

3.5.3 Prepare Transaction Data in ERP system

UseBased on the German Baseline Solution, please refer to the following steps for the customizing adjustment. All the configuration guide in this solution is based on the adjusted customizing.

The detailed steps of extracting data from ERP to BW is described in configuration guide B66_BPC075_BB_ConfigGuide_EN_DE.doc.

3.5.3.1 Create Profit Center

Procedure1. Access the activity using on of the following menu:

SAP ECC menu Accounting Controlling Profit Center Accounting Master Data Profit Center Individual Processing Create

Transaction code KE51

2. In the Set Controlling Area dialog box enter controlling area 1000 and choose Continue.

3. On the Create Profit Center screen, enter following informaiton:



Field name Description User action and values Comment

Profit Center YB100

Copy From/Profit Center

YB110

CO Area 1000

4. Choose enter.

5. Choose Save.

6. Choose Activate.7. Repeat the above-mentioned steps 1-6 to create profit center YB200, copy from profit

center YB120..

3.5.3.2 Change Profit Center


SAP ECC menu Accounting Controlling Profit Center Accounting Master Data Profit Center Individual Processing Change

Transaction code KE52


3. On the Change Profit Center screen, enter following informaiton:


Profit Center YB700

4. Choose enter.

5. On the Change Profit Center screen, change name and long text as “HR Department“

6. Choose Save.

7. Choose Activate.8. Repeat the above-mentioned steps 1-7 to change profit center YB100, YB200, YB600

and YB900 as following:

Profit Center Short text Name Comment

YB100 Sales Team 1 Sales team 1

YB200 Sales Team 2 Sales Team 2

YB600 FI Department FI Department

YB900 IT Department IT Department

3.5.3.3 Create Cost Center




SAP ECC menu Accounting Controlling Cost Center Accounting Master Data Cost Center Individual Processing Create

Transaction code KS01


3. On the Create Cost: Initial screen, enter following information:


Cost Center Z003

Valid from 2000.01.01

to 9999.12.31

4. choose Enter.5. On the Create Cost center: Basic screen, choose the Basic data tab and enter following

information


Name HR Department

Description HR Department

Person Responsible

SAP

Cost Center Category

H

Hierarchy area

0001

Company Code

1000

Functional Area

YB40

Currency EUR

Profit Center YB700

6. Choose Control tab, select “Actual revenues“ ， ”Plan revenues“ and “Commitment update“..

7. Choose Save. 8. Repeat above-mentioned steps 1-7 and create following cost centers:

Cost Center: Z004




Basic Data

Name FI Department

Description FI Department

Person Responsible

test


H

Hierarchy area

0001

Company Code

1000

Functional Area

YB40

Currency EUR

Profit Center YB600

Control

Actual revenues

Checked

Plan revenues

Checked

Commitment update

Checked

Cost Center: Z005




Basic Data

Name IT Department

Description IT Department

Person Responsible

SAP


H

Hierarchy area

0001

Company Code

1000

Functional Area

YB40

Currency EUR

Profit Center YB900

Control

Actual revenues

Checked

Plan revenues

Checked

Commitment update

Checked

Cost Center: Z006




Basic Data

Name Sales Team 1

Description Sales Team 1

Person Responsible

SAP


V

Hierarchy area

0001

Company Code

1000

Functional Area

YB30

Currency EUR

Profit Center YB100

Control

Actual revenues

Checked

Plan revenues

Checked

Commitment update

Checked



Cost Center: Z007


Basic Data

Name Sales Team 2

Description Sales Team 2

Person Responsible

SAP


v

Hierarchy area

0001

Company Code

1000

Functional Area

YB30

Currency EUR

Profit Center YB200

Control

Actual revenues

Checked

Plan revenues

Checked

Commitment update

Checked

3.5.3.4 Change customer


SAP ECC menu Logistics Sales and Distribution Master Data Business Partner Customer Change Complete

Transaction code XD02

2. On the Customer Change:Initial Screen, make the following entries:




Customer 100005

Company code

1000

Sales Organization

1100

Distribution Channel

10

Division 10

3. Choose Enter.4. Choose Sales Area Data.5. On the Change Customer: Sales Area Data screen, change the value of field Currency to

USD.6. Choose Save.

4 Activation of Business Content / Scenarios – Activation consultant

The following chapters describe the activities that have to be done by the consultant who is going to activate SAP Best Practices in the system.

4.1 Activation Sequence of ScenariosWhen install the complete BPC Package (all scenarios) or just selected scenarios, the necessary technical building blocks need to be installed in the correct sequence. Use following sequence to install the BPC package.

ScenarioScenario Description Application Set 1 2 3 4 5 6 7

B59

Business Result Analysis and Simulation SAP_BP_Planning B66 B57 B59

B61Sales Planning SAP_BP_Planning B66 B57 B59 B61

B62HCM Planning SAP_BP_Planning B66 B57 B59 B62

B63 PL Planning SAP_BP_Planning B66 B57 B59 B63

B60

Performance Review and Forecast SAP_BP_Planning B66 B57 B59 B61 B62 B63 B60

B64

Legal Consolidation SAP_BP_Cons_GL B66 B57 B64

Details for individual scenarios are available on the documentation DVD in the area Business Information Preconfigured Scenarios. Depending on the scenarios you are interested in, choose the corresponding scenario. On that page, you can access the business process



documentation, process overview document and the configuration guide of the respective scenario.

The business process documentation (BPD) provides a detailed process step description of the business scenario.

The scenario overview document comprises of a graphical overview of the scenario process flow.

The configuration guide describes crucial parts of the system configuration of the respective scenario. Together with the configuration guides of the underlying building blocks, you can track which system settings have been configured.

You can use the documents as described above to review the business scenarios you are interested in. Use the business process documentation (BPD) to pass through the scenario in the system.

4.2 Error Handling: Installation Errors during Activation

The following information helps you to solve problems that might occur during the installation process.

Before you start with detailed error analyzing and working through the error processing as described below proceed as follows:

4.2.1 Dynamic Hierarchy Editor not shown

UseIn some circumstances, Dynamic Hierarchy Editor (DHE) in B64 scenario does not show properly. You might enable it by providing the OWNERSHIP type cube name in the Org_OwnershipCube application parameter.There are also some default consolidation method in the initial appset. Although they are not used in this solution, please do not delete them. Otherwise the DHE may not work.

Procedure1. Make sure you have created Ownership application, and assigned Ownership to

Consolidation application.

2. Make sure you have maintained corresponding parameters as described in B64 Configuration Guide chapter 5.11.

4.2.2 Dimension XXX does not have a XXXX property

UseWhen processing a dimension, this message may occur. This is because the property definition for this dimension is not consistent with dimension member sheet.

Procedure1. Make sure that every property used in dimension member sheet is defined.

2. Delete undefined property from the member sheet if necessary.

3. If you cannot find a solution for the problem this way, open a customer message specifying the component SV-SMB-AIO-BP-BPC.



4.2.3 How to delete a BPF template

UseIf you want to delete a wrong configured BPF template, please do not simply delete it in admin console. This may leave some useless records in system and caused some ‘lock’ problem while editing other elements such as dimension.

Procedure1. Please refer to Note 1544309 and follow the instruction to delete all related records.

2. If you can’t solve the problem this way, open a customer message specifying the component SV-SMB-AIO-BP-BPC.

4.2.4 Application XXXX was not found

UseWhen validating the script logic, this error may display. Not only for application, may this kind of validation error also occur for other elements such as dimension member and property. This is because script logic is case sensitive for this kind of definitions or statements. Sometimes these errors are not reported, but results are not correct when calling these scripts. The wrong cases lead to empty results after filtering.

Procedure1. Make sure that you have used the exactly correct case in script logic. Compare the script

contents with the dimension definitions in previous steps.

2. Log on to the Service Marketplace and search for appropriate SAP Notes.

3. If you cannot find a solution for the problem this way, open a customer message specifying the component SV-SMB-AIO-BP-BPC.

5 Historical Data Preparation5.1 Historical Data for Planning related Business

ScenariosUseIn our solution, the actual sales data and P/L data used in the planning related business scenarios are retrieved from ERP system. If you would like to upload the historical data to the system directly, you may refer to the this step to load the data to BW.

Procedure



1. Refer to BPD B61_BPC075_BPD_EN_DE, part 2.3, Log on the BPC system using the installation user(eg. BPC_sysadmin)


Application Sales Planning

2. Choose Planning & Consolidation tab, choose eData - > More -> Data Upload. On the Data Manager – upload screen, make the following entries:


Source file Use the file attached to note 1620123.

SD INITIAL.CSV from CSV_files.zip

Destination file Enter the target place you would like to save the file.

3. Choose OK.

4. In the pop-up window, choose OK for the message File transferred successfully.

5. Choose Planning & Consolidation tab, choose eData - > Run Package.

6. Choose Import Transaction Data under Package Group Data Management.

7. On the Data Manager – Run Package screen, make the following entries:


Import file Put the menu path you stored the file in step 2

Transformation file

The transformation file stored in the server.eg: Transformation InitialData.xls

8. Choose Next.

9. Select Run now and choose Finish.

10. Choose OK.

11. Log off the system12. Refer to BPD B63_BPC075_BPD_EN_DE, part 2.3, Log on the BPC system using the

installation user(eg. BPC_sysadmin)


Application PL Planning

13. Repeat step 2-11 to upload the historical PL data using following information:Application Source File Transformation File

PL Planning Use the file attached to note 1620123.PL INITIAL.CSV (from CSV_files.zip)

Transformation InitialData.xls

5.2 Historical Data for Consolidation Business Scenario (B64)

Use



In our solution, we used flat file to upload the financial statement data to the system for consolidation. If you would like to upload the financial statements for different companies in 2010, you may refer to this step.

Procedure1. Refer to BPD B64_BPC075_BPD_EN_DE, part 2.3, Log on the BPC system using the

installation user(eg. BPC_sysadmin)


Application Consolidation

2. Choose Planning & Consolidation tab, choose eData - > More -> Data Upload. On the Data Manager – upload screen, make the following entries:


Source file Refer to the files attached to note 1620123

NW_INITIAL_FINANCIAL_2010.csv (from CSV_files.zip)

Destination file Enter the target place you would like to save the file.

3. Choose OK.

4. In the pop-up window, choose OK for the message File transferred successfully.

5. Choose Planning & Consolidation tab, choose eData - > Run Package.

6. Choose Import Transaction Data under Package Group Data Management.

7. On the Data Manager – Run Package screen, make the following entries:


Import file Put the menu path you stored the file in step 2

Transformation file

The transformation file stored in the server.eg: Transformation file.xls

8. Choose Next.

9. Select Run now and choose Finish.

10. Choose OK.

6 Error Handling: Usage ErrorsThe following chapters describe the activities that have to be done by the business consultant who is taking care that the business processes work as desired.

6.1 Encounter error message “Failed to get next member of range member (UJJ_JRNID)

The new application set is copied from an original application set. The journal table will not work properly in the new application set. Please refer to Note 1544127 for workaround or Note 1549824 for correction.



6.2 Encounter error messages in Work StatusWhen changing work status, error messages below maybe displayed. Please check the table below for detailed information.

Error Message ReasonControlled by rule has been violated

If the scenario is one of the below: If the user is acting as an Owner, and they select a work status

controlled by “Manager” If the user is acting as an Manager, and they select a work status

controlled by “Owner” Cannot include children when the owner dimension is a base member

If the controlling dimension you have selected is a base member.

Bottom up rule has been violated

If the work status that is being set for parent is higher than the work status that is set for the child.

user is not a owner/manager, work status cannot be updated

If BPC logged in user is not setup as a owner in the Owner property of the controlling dimension

6.3 Encounter error message “Root element is missing”

This error occurs when sending data in an input schedule. Please refer to note 1523410.

6.4 Encounter error message “EVDRE disabled. Initial cache first”

Normally, this error message is encoutnered when there is some inconsistentnt dimension information for the application. Please try to re process all the dimensions with full process for all cubes. Please also delete the local application information.

6.5 EVDRE encountered an error retrieving data from Web Server.

This error occurs when opening or refreshing an input schedule or report in Excel. Please refer to Note 1475233.

6.6 Reset Business Process FlowAfter the business process flow has been reset, please remember to reorder the workstatus to reset the workstatus of the data.

7 Security Aspects – System AdministratorsThis section provides an overview of the security-relevant information that applies to the deliverables of this SAP Best Practices package.

7.1 User Administration and AuthenticationIn this chapter you will find an overview of the required users for this package.



Purpose User-ID User Type

Created in

Initial Password

Authoriza-tion Profile

Comment

System User

BPC_SYSADMIN

System(Type B)

Creation described in Installation Guide

Password is defined by your System Admin.

SAP_ALLS_RS_ALL

System User

BPC_ADMIN

System (Type B)



T_K1300004 Role: SAP_BPC_ADMIN

System User

BPC_USER

System (Type B)



SAP_ALL Role: SAP_BPC_USER

You can check the user using transaction SU01.

7.2 Roles ManagementNot relevant

7.3 RFC DestinationsIn this chapter you will find an overview of the required RFC destinations created and used for this package.

RFC Destination

Description Connection Type

Created in

Logon Data Comment

EH4CLNT102 Connect from BW to ERP

ABAP Connection

Configuriaotn Guide

User ID: RFCUSERPassword: Welcome1

EH4CLNT100 Connect from ERP to BW

ABAP Connection

Configuriaotn Guide

User ID: RFCUSERPassword: Welcome1

You can check the roles using transaction SM59.


Date post:	12-Apr-2016
Category:	Documents
Upload:	lesley-trujillo
View:	23 times
Download:	2 times

Bpc Nw Quick Guide en De

Documents