• No results found

Quick Guide to Implementing the SAP Extended Financial Planning rapiddeployment

N/A
N/A
Protected

Academic year: 2021

Share "Quick Guide to Implementing the SAP Extended Financial Planning rapiddeployment"

Copied!
17
0
0

Loading.... (view fulltext now)

Full text

(1)

SAP Business

Planning and

Consolidation

SAP EPM add-in for

Microsoft Excel

Web Services

Enhancements 3.0

for

Microsoft .NET

April 2014

English Only

Quick Guide to

Implementing the SAP

Extended Financial

Planning

rapid-deployment solution

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

(2)

Copyright

© 2014 SAP AG 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 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 asF2) 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)

Contents

Quick Guide to Implementing the SAP Extended Financial Planning rapid-deployment solution ... 5

1 Purpose ... 5

2 Solution Overview ... 6

2.1 Input Forms for Scope Items ... 6

2.2 Localization and Language Support ... 6

3 System Setup & Preparation ... 7

3.2 Software Requirements ... 7

3.3 Release and Support Package Level ... 7

3.4 SAP Frontend Components ... 8

3.5 Release and Support Package Level ... 8

3.6 SAP Notes and Messages ... 9

3.7 Manual Implementation ... 9

4 Security Aspects ... 11

4.1 Security Aspects – System Administrators ... 11

4.2 SAP Business Planning and Consolidation application security considerations . 11 4.3 Security considerations for the SAP NetWeaver platform ... 11

4.4 SAP Extended Financial Planning rapid-deployment solution security considerations ... 12

5 Installation ... 13

5.1 Initial Check of System Readiness ... 13

5.2 Installation Checklist ... 14

6 Appendix ... 17

(5)

Quick Guide to Implementing the SAP Extended

Financial Planning rapid-deployment solution

1 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 setup 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 document

SAP Best Practices Tools in the step-by-step guide, Deploy: Activate Solution,

(6)

2 Solution Overview

The SAP Extended Financial Planning rapid-deployment solution leverages the SAP Business Planning and Consolidation platform, solution allows your organization to cover its key planning processes by integrating the three solutions into one environment.

This solution is based on SAP SAP Business Planning and Consolidation 10, version for SAP NetWeaver®

Provides an accelerated deployment of the required configuration settings Includes the following scope items:

General Ledger (G/L) Financial Planning: model your financial planning by

leveraging the SAP General Ledger structure and provide template for Profit Center, Cost Center and Balance Sheet planning

For more information about this scope item, see the General Ledger (G/L)

Financial Planning with SAP Business Planning and Consolidation, version for SAP NetWeaver (A93) business process documentation.

Strategic Financial Planning: long range planning and multiple scenarios

capabilities (M&A, new product launch, competitor analysis). SFP provides a set of interconnected Financial Statements that are dynamically updated as you do your simulations.

For more information about this scope item, see the Strategic Financial Planning

with SAP Business Planning and Consolidation, version for SAP NetWeaver (EA1) business process documentation.

Capital Expenditure Planning: provide a set of templates and integration

methods to plan capital expenditures by Cost Center for a specific project or a discretionary expense. The main Key Performance Indicators such as Net Present Value and Internal Rate of Return are calculated instantly. For more information about this scope item, see the Capital Expenditure

Planning with SAP Business Planning and Consolidation, version for SAP NetWeaver (EG1) business process documentation.

For an overview of the SAP Extended Financial Planning rapid-deployment solution, refer to the

Solution Details Presentation in the step-by-step guide (phase Start: Prepare Project).

2.1 Input Forms for Scope Items

The solution provides baseline planning input forms for each of the scope items. SAP

recommends working on input forms or using reports individually. Only when necessary should multiple inputs forms and reports be opened simultaneously.

For all input forms, SAP strongly advises using the Refresh Workbook, Save

Workbook Data, and Save and Refresh Workbook Data options. Do not use the

default options on the EPM menu that are Refresh or Save Data. Errors results when using the default options.

For more information about input forms, see the business process documentation for each of the scope items.

2.2 Localization and Language Support

The initial release of this solution is available only in the English language. All documentation, messages, and text are available only in English. The solution does not natively support other languages.

(7)

3 System Setup & Preparation

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

3.1 Prerequisites

SAP Extended Financial Planning rapid-deployment solution requires the installation and configuration of SAP software components before you implement this rapid-deployment solution. For more information about software requirements and the system landscape, see the Software

Requirements documentation for this solution.

3.2 Software Requirements

This rapid deployment solution is based mainly on a set of software components from SAP.

Required Software:

SAP Business Planning and Consolidation, version for SAP NetWeaver SAP NetWeaver® - Business Warehouse

SAP EPM add-in V10 for Microsoft® Office

Web Services Enhancements (WSE) 3.0 for Microsoft® .NET (required for EPM add-in for Excel)

Optional Software:

SAP HANA® Database Edition for SAP BW - Database option to leverage SAP HANA for optimal performance. SAP HANA is not the required database.

3.3 Release and Support Package Level

The deliverables of SAP rapid-deployment solutions are 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 installation and deployment.

Make sure that your system meets the minimum SPS level requirements. In case your system has an exceptional SPS level compared to the requirements, only LIMITED SUPPORT can be provided.

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 tohttps://service.sap.com/swdc Installations and Upgrades SAP Components

For support packages, go tohttps://service.sap.com/swdc Support Packages and Patches A-Z Index

(8)

Components that need to be installed for the above:

SAP Business Warehouse (SAP_BW) 731.0010 (or latest)

Business Intelligence Content (BI_CONT) 747.0007 (or latest)

SAP NetWeaver BP-BW Add-on for BW (BP_BW)

731V4 (or latest)

CPM for BPC (CPMBPC) ** 801.004 (SP11)

Add-on installation (POASBC) 100_731.0004 (or latest)

BPC Accelerator for HANA (HANABPC) ** 801.002 (or latest)

** represent the SAP Business Planning and Consolidation application components

3.4 SAP Frontend Components

The following SAP frontend components must be installed: SAP EPM add-in for

Microsoft® Excel Version 10.0 Service Pack 16 or above Client component

Platform for SAP Business Planning and Consolidation application (design and runtime) Ensure that you have installed the latest and appropriate SAP frontend components.

To download SAP frontend components, go to the SAP Software Download Center (SWDC) on SAP Service Marketplace:

https://service.sap.com/swdc

Software Downloads Analytic Solutions Browse the Analytics Solutions Portfolio Support Packages and Patches SAP Financial Consolidation

SBOP FINANCIAL CONS. 10.0 Comprised Software Component Versions SBOP EPM EXCEL Client 10.0 Win 32

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

(9)

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 Catalog). 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

925690Standard Ordering Procedures for SAP Software

3.6 SAP Notes and Messages

If issues become apparent after shipment of this SAP Best Practices package (and hence of this document), an 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 package to obtain updates and corrections for problems that have not become apparent until after shipment.

SAP Note # Description Component Remark

1975827 Link to Note SAP Extended Financial Planning rapid-deployment solution SV-RDS-BPC

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

3.7 Manual Implementation

The pre-configuration of the solution is implemented manually by following the configuration guides according to the sequence of the Prerequisites Matrix. The Prerequisites Matrix gives an overview of the configuration building blocks and related configuration guides, required for each business process and the correct sequence for implementing the building blocks.

The Prerequisites Matrix can be found via the Content Library Prerequisites Matrix.

We recommend using SAP Solution Manager to control the manual implementation as well as to document your implementation of the solution package.

Prerequisites

Before you can start activating the business processes manually, the following activities must be completed:

The system landscape has been set up according to section Required Product Versions

(10)

The general system settings have been made. For more information, see section General

Client Settings in this guide.

An activation user has been created and set up for activation. For more information, see section Creating a User for Activation of SAP Best Practices Content in this guide.

(11)

4 Security Aspects

4.1 Security Aspects – System Administrators

This rapid-deployment solution relies on the existing methodology for security and authentication of the underlying SAP Business Planning and Consolidation application. Integration of the security options in the required components to conform this solution to the end-to-end strategy is part of an overall security methodology for the organization. This section proves generic security aspects for the underlying software products. For more information, refer to the security guides for each software product on the SAP Help Portal.

4.2 SAP Business Planning and Consolidation

application security considerations

There are various methods and techniques available to secure information available with the SAP Business Planning and Consolidation application. The techniques range from the database storage itself, authorization, and data transmission to external consumers of the application information. Each individual installation should have a security strategy in place to adhere to requirements and guarantee privacy and stable information provided to the business user.

For outlines of these techniques, see the SAP Business Planning and Consolidation version for SAP NetWeaver Security Guide. The product Security Guide provides an overview of the security-relevant information that applies to the SAP Business Planning and Consolidation version for the applicable software platforms including the solution content.

4.3 Security considerations for the SAP NetWeaver

platform

The SAP Business Planning and Consolidation version for SAP NetWeaver security guide includes sections that address:

User Administration and Authentication

Provides an overview of user administration and authentication aspects, including both user management and integration into a single sign-on environment. Implementation considerations for user management include user role assignment, privileges, and restrictions. The application uses the same user management and authentication mechanisms provided with the SAP NetWeaver platform, in particular the SAP NetWeaver Application Server ABAP. Therefore, the security recommendations and guidelines for user administration and authentication as described in the SAP NetWeaver Application Server ABAP Security Guide also apply.

Password policies are included in the security methodology. The SAP NetWeaver platform supports many options for defining and controlling password policies and they are reviewed for adherence to the required password policies for your organization.

Authorizations

The application uses the classic authorization concept provided by SAP NetWeaver. Therefore, the recommendations and guidelines for authorizations as described in the SAP NetWeaver Application Server ABAP Security Guide also apply to the application. The SAP NetWeaver authorization concept is based on assigning authorizations to users based on roles.

(12)

Network and Communication Security

SAP NetWeaver supports communication channel security. The communication channel used by the application adapter for Front-end client using a Web browser to the

application server uses the protocol HTTP, HTTPS, SSL (REST communication is used). HTTP connections are protected using the Secure Sockets Layer (SSL) protocol. For more information about transport layer security, see the SAP NetWeaver Security Guide.

Data Storage Security

Review the SAP HANA Security Guide for data encryption capability as well as

considering underlying operating system data encryption to see how it may be integrated into the security requirements specification.

4.4 SAP Extended Financial Planning rapid-deployment

solution security considerations

Roles Definition

The SAP Extended Financial Planning rapid-deployment solution is delivered with three generic roles that define access to SAP Business Planning and Consolidation. These roles are:

SAP Business Planning and Consolidation Administrator SAP Business Planning and Consolidation Planner SAP Business Planning and Consolidation Analyst

More detail is provided on assignment of specific tasks for each of these roles in the SAP Extended Financial Planning rapid-deployment solution business process documentation, building block references A93, EA1 and EG1.

Secure Dimensions

In the CAPEX Model the following dimensions are secure as delivered in the solution: o COMPANY_CODE

o COST_CENTER o C_AUDIT_TRAIL o VERSION

In the PLANNING model the following dimensions are secure, as delivered in the solution: o AUDIT_TRAIL o COMPANY_CODE o COST_CENTER o PROFIT_CENTER o VERSION

In the SFP model the following dimensions are secure, as delivered in the solution: o AUDIT_TRAIL

o BUS_UNIT o VERSION o SCENARIO

In the S_OWNERSHIP model the following dimension are secure, as delivered in the solution:

(13)

o SCOPE

In the RATES model the following dimension is secure, as delivered in the solution: o TIME

o VERSION

In the S_RATES model the following dimension is secure, as delivered in the solution: o VERSION

Each secure dimension is required to be referenced in a Data Access Profile in order for a user to have Read or Read/Write access to that dimension.

More detail is provided on secured dimensions in the SAP Extended Financial Planning rapid-deployment solution business process documentation, building block references A93, EA1 and EG1.

Data Access Profile Notes:

To support planning, the user may need to set up Data Access Profiles with the following considerations:

Users have write access to the NONE members of each secure dimension. For example, COST_CENTER is a secure dimension but users have to be able to write to member CC_NONE.

Users have appropriate write access to the correct COST_CENTER, PROFIT_CENTER and COMPANY_CODE combinations since these three dimensions are typically linked in defining valid data entry records. For example, if Cost Center CC_CU00CU01HR01is linked to Profit Center PC_CU00CU00021 and Company Code CO_CU01, a user requires write access to all three members to enter a valid data record.

5 Installation

The following section provides a high-level overview of the activities to be done by the system administrator or consultant installing the solution on a system. For more information, see the individual configuration guides for this solution.

5.1 Initial Check of System Readiness

It is necessary that you check if your system administrator has applied the correct SPS level. In addition, ensure that the system administrator completes all activities as described in the section System Setup & Preparation System Administrator.

(14)

5.2 Installation Checklist

The following checklist itemizes the steps to install the primary SAP Extended Financial Planning rapid-deployment solution.

For detailed instructions on the installation of this solution refer to the Building Block Configuration Guides that are attached to the Content Library in the Step by Step Guide. Not all steps apply if only individual scope items are deployed. For more information, see the Installation Checklist by Scope and the Prerequisite Matrix that is attached to the Content Library.

Installation by Scope

The provided scope items for SAP Extended Financial Planning have differences in what configurations are deployed. As scope items can be deployed separately, the following table provides a breakdown of the installation checklist by scope:

Scope Implementation Steps Comments

Strategic Financial Planning (EA1)

Steps 1 through 6 No SAP NetWeaver BW or

SAP ERP settings required General Ledger (G/L)

Financial Planning (A93)

Steps 1 through 11 Configuration inclusive for this scope item

Capital Expenditure Financial Planning (EG1)

Steps 1 through 8 and steps 12 through 20

When implementing Capital Expenditure Planning only, skip G/L configuration steps

Checklist:

1. Restoring the SAP Extended Financial Planning rapid-deployment solution 2. Enable SAP HANA (SAP NetWeaver BW on SAP HANA only)

3. Copy and connect to the new Environment

4. Delete Master Data from the Copy and perform Data Manager changes 5. Change the defaults for Currency and Time

6. Load Master data and Transactional data

For more information about steps 1 through 6, see the Extended Financial Planning

with SAP Business Planning and Consolidation for SAP NetWeaver (EG4)

configuration guide.

7. Configure the basic SAP NetWeaver BW connectivity settings

For more information about step 7, see the SAP NetWeaver BW Basic Connectivity

Settings (BW1) configuration guide .

8. Configure SAP NetWeaver BW connectivity for SAP ERP

For more information about step 8, see the SAP NetWeaver BW: Connectivity for the

SAP ERP System (BW2) configuration guide .

9. G/L Financial Planning: Configure Master Data InfoObjects

10. G/L Financial Planning: Activate SAP NetWeaver BP-BW Add-on Content

11. G/L Financial Planning: Optimize Cubes for SAP HANA (SAP NetWeaver BW on SAP HANA only)

(15)

12. G/L Financial Planning: Load transactional data

For more information about steps 9 through 12, see the G/L Financial Planning

settings for integration with SAP ERP (A95) configuration guide.

13. Capital Expenditure Planning: Configure Master Data InfoObjects

14. Capital Expenditure Planning: Activate SAP NetWeaver BP-BW Add-on Objects - Info Providers

15. Capital Expenditure Planning: Optimize Cubes for SAP HANA (SAP NetWeaver BW on SAP HANA only)

16. Capital Expenditure Planning: Create Transformation for InfoCubes 17. Capital Expenditure Planning: Create Data Transfer Processes 18. Capital Expenditure Planning: Load transactional data

For more information about steps 13 through 18, see the configuration guide Capital

Expenditure Planning settings for integration with SAP ERP Project System (PS) (EG2) configuration guide.

Step Descriptions:

Step 1: Restoring the SAP Extended Financial Planning

rapid-deployment solution

The application set provided with this solution is restored on the SAP NetWeaver platform using a standard software backup/restore feature.

Step 2: Enable SAP HANA

The SAP Extended Financial Planning rapid-deployment solution can be enabled for use with SAP HANA.

Step 3: Copy and Connect to the new Environment

Copy the PLANNING_SHELL environment and verify the connection to the new environment

Step 4: Delete Master Data from the Copy and perform Data

Manager Changes

The environment that was copied contains no transaction data. It does contain master data from PLANNING_SHELL. Some of that master data is deleted and some is retained, as described in this section. After deletion of the master data, the application is ready to have client-specific master data loaded. The conversion files, transformation files and package links require changes.

Step 5: Change the defaults for Currency and Time

If required, change the reporting currency default from USD (U.S. Dollars) and change the Planning Horizons time dimension.

Step 6: Load Master Data and Transactional data

Master Data, including Attributes, Texts, and Hierarchies, is loaded from standard SAP ERP G/L business content. Transaction data is imported from the SAP NetWeaver BW SAP Business Planning and Consolidation staging cube. Imported data is filtered through Transformation and Conversion files.

Step 7: Configure the basic SAP NetWeaver BW connectivity settings

You assign the SAP NetWeaver BW menu to your user to allow you to follow the menu paths as described in the documentation. Define Client Administration to customize settings. Define a Logical System and assign the system to a Client. Create users for Remote Function Call (RFC), defining your RFC user as the default. Configure users in SAP NetWeaver BW to assign roles and menus. Activate Business Content. Ensure the correct SAP NetWeaver BW client is set in

(16)

the system. Configure Business Content for SAP NetWeaver BW on SAP HANA to provide optimized data model.

Step 8: Configure SAP NetWeaver BW connectivity for SAP ERP

After setting the basic connectivity for SAP NetWeaver BW, you configure connectivity for SAP ERP following some of the same steps. Define Client Administration for SAP ERP. Define a Logical System and assign the system to a Client. Create an RFC user and designate as default user. Connect the SAP NetWeaver BW Logical System with the Source System and transfer the component hierarchy from SAP ERP

Step 9: Update Master Data InfoObjects - G/L Financial Planning

Master data (attributes, texts, and hierarchies) are loaded for all InfoObjects provided by the business content.

Step 10: Activate BI Content - G/L Financial Planning

This step includes checking the namespaces before activating business content, assigning source system for activation, activating BP-BW add-on objects - Info Provider, optimizing DSO / Cube for In-Memory Database (SAP NetWeaver BW on SAP HANA only), creating transformation and creating a data transfer process .

Step 11: Optimize Cubes for SAP HANA (SAP NetWeaver BW on

SAP HANA only) – G/L Financial Planning

In order that the InfoCubes included in this solution can take advantage of the performance improvements of running SAP Business Warehouse on an SAP HANA database, the Info Cubes must be optimized to run on an in-memory database.

Step 12: Load transactional data - G/L Financial Planning

The purpose of this task is to modify filters for the data transfer processes and load transactional data into the InfoCube

Step 13: Configure Master Data InfoObjects – Capital Expenditure

Planning

Master data (attributes, texts, and hierarchies) is loaded for all InfoObjects provided by the business content.

Step 14: Activate BP-BW Add-on Objects and Info Providers –

Capital Expenditure Planning

In this activity, you activate the Info Providers delivered as BP-BW Add-on Objects. If the InfoCube 0PS_C041 is not active in your SAP BW system you should activate it, as well as the Info Providers delivered as BP-BW Add-ons. This facilitates the creation of the BW

Transformations for the Info Providers provided with the Add-on.

Step 15: Optimize Cubes for SAP HANA (SAP NetWeaver BW on

SAP HANA only) – Capital Expenditure Planning

In order that the InfoCubes included in this solution can take advantage of the performance improvements of running SAP Business Warehouse on an SAP HANA database, the Info Cubes must be optimized to run on an in-memory database.

Step 16: Create Transformation for InfoCubes

You create transformations for 2 InfoCubes

InfoCube /PKG/CP_C01 is based on InfoCube 0PS_C041 that is provided with the Business Content. It is used to create two InfoCubes, one for actuals and one for budget and

commitments. This InfoCube is for actuals.

InfoCube /PKG/CP_03 is based on InfoCube 0PS_C041 that is provided with the Business Content. It is used to store budget and commitments.

(17)

The purpose of this task is to create data transfer processes from the standard InfoSources to InfoCube /PKG/CP_C01 and InfoCube /PKG/CP_C03. These Data Transfer Processes are used for data loading. The DataSources provided use the full update method.

Step 18: Load transactional data

The purpose of this task is to modify filters for the data transfer processes from InfoCube /PKG/CP_C01 to InfoCube /PKG/CP_C02 and from InfoCube /PKG/CP_C03 to InfoCube /PKG/CP_C04 and to load the transactional data into the staging cubes, InfoCubes /PKG/CP_C02 and /PKG/CP_C04, for use with Business Planning and Consolidation Data Manager.

6 Appendix

The following table lists the configuration guides for this solution.

Building Block Number

Configuration Guide Name

A95 G/L Financial Planning SAP NW BW settings for integration with SAP ERP

BW1 BW Basic Connectivity

BW2 BW Connectivity for SAP ERP

EG2 CAPEX settings for integration with SAP ERP - Project System

EG4 Content Deployment for Planning with SAP Business Planning and Consolidation, version for SAP NetWeaver

7 Further Information – Step-by-Step Guide

A Step-by-Step Guide is available for this package. Step-by-Step Guides are built specially for every rapid-deployment solution. This interactive guide follows the overall process, in

chronological order, of all the steps to be executed during the project to plan, install, configure, and run.

The guide is based on rapid-deployment methodology: Start, Deploy, Run, which is to be used as an implementation roadmap. Documentation assets, project accelerators, and reference

materials, are linked to the Step-by-Step Guide.

The Step-by-Step Guide is available on the SAP Software Download Center at

service.sap.com/swdc under Installation and Upgrades Browse our download catalog SAP Rapid Deployment solutions. The Step-by-Step Guide is available on the solution page at:

References

Related documents

A statistically significant negative correlation was dem- onstrated in the study cohort between the maternal serum PIGF levels, foetal heart rate (FHR), birth weight and length,

The decisions in our system is binary (0 for not change device status, 1 for change it). Therefore, it is accessible that CBR assumption works in our system. As most of CBR systems

Four basic themes emerged from the analysis; social and cyber arrangements within the Dublin Chemsex scene; poly drug use and experiences of drug dependence; drug and sexual

to effect a transfer of any immovable property, or of any movable property other than debentures issued by, or shares in, a company, shall, if the

A recently published article “New and rapid analytical procedure for water determination: microwave accelerated Dean Stark”* describes for the first time how heating by microwave

It mentions the following results “(1) Surya kshetra: commander of an army, (2) Chandra kshetra: blessed with wife, wealth and children, (3) Kuja kshetra: having

UC-Paid Life Insurance: Appointed 50% or more for a year or more and participating in a university retirement plan. UC-Paid Disability Insurance: Appointed 50% or more for a year

Corresponding sales invoices with credit note invoice template offers that has more sales order to credit notes with the item.. Revenue your customer level which can use this