Manual FSC800

SAP PORTUGAL | USO EXCLUSIVO | 2013 FSC800 SAP Liquidity Planner

FSC800

SAP Liquidity Planner

THE BEST-RUN BUSINESSES RUN SAP  SAP AG 2008

© SAP AG 2008

SAP ERP Version: 62 Materialnummer 50086719

SAP PORTUGAL | USO EXCLUSIVO | 2013

SAP PORTUGAL | USO EXCLUSIVO | 2013 Copyright

Copyright 2008 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.

 SAP AG 2008

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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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. MaxDB is a trademark of MySQL AB, Sweden.

SAP PORTUGAL | USO EXCLUSIVO | 2013 SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 in several other countries all over the world. 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. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

SAP PORTUGAL | USO EXCLUSIVO | 2013 Course Overview

Contents: Course Goals Course Objectives Course Content Course Overview Diagram Main Business Scenario

 SAP AG 2008

SAP PORTUGAL | USO EXCLUSIVO | 2013 Course Goals

This course will prepare you to: Understand how and where you can use SAP Liquidity Planner functions Obtain detailed knowledge of the entire SAP Liquidity Planner process Use SAP Liquidity Planner independently to develop cash accounting and planning

 SAP AG 2008

SAP PORTUGAL | USO EXCLUSIVO | 2013 Course Objectives

After completing this course, you will be able to: Describe and use the business requirements of cash accounting and planning with SAP Liquidity Planner Set up the technical structure required for cash accounting and planning Define and implement the system settings in ERP and BI Describe the organizational adjustments required

 SAP AG 2008

SAP PORTUGAL | USO EXCLUSIVO | 2013 Course Content

Unit 1

LP (SAP Liquidity Planner) in FSCM

Unit 2

Basic Knowledge Business Administration

Unit 3

Customizing in ERP

Unit 4

Application in ERP

Unit 5

Migration TR-CBM for SAP Liquidity Planner

Unit 6

BI Overview (Business Intelligence)

Unit 7

Business Content, Modeling, and Extraction

Unit 8

Reporting

Unit 9

Planning

Unit 10

Summary and Outlook Appendix

 SAP AG 2008

SAP PORTUGAL | USO EXCLUSIVO | 2013 Main Business Scenario

Plan Data

Group

Planning Unit 1

Planning Unit 2

Actual Data Planning? Unit 1

Central Data Storage

Planning Unit 3

Planning Unit 2

Planning Unit 3

Reporting  SAP AG 2008

An enterprise wants to increase the transparency of its financial operations. It wants to display, analyze, and plan cash flows. The enterprise uses liquidity items to display and plan cash flows. The liquidity items can be revenue or expenditure items. To achieve more transparency the enterprise wants to implement SAP Liquidity Planner. This application comprises three areas: • Actual data (in ERP) • Plan data in (BI) • Reporting (in BI)

SAP PORTUGAL | USO EXCLUSIVO | 2013

SAP PORTUGAL | USO EXCLUSIVO | 2013 LP in FSCM

Contents: Overview of Financial Supply Chain Management (FSCM) Overview of SAP Liquidity Planner Tasks System architecture Differences to Cash Management

 SAP AG 2008

© SAP AG

FSC800

1-1

SAP PORTUGAL | USO EXCLUSIVO | 2013 LP in FSCM: Objectives

At the conclusion of this unit, you will be able to: Integrate SAP Liquidity Planner in Financial Supply Chain Management Distinguish SAP Liquidity Planner from Cash Management Name the main tasks of SAP Liquidity Planner Outline the system architecture

 SAP AG 2008

© SAP AG

FSC800

1-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 Overview of SAP Liquidity Planner: Business Scenario

Before you start working in the project team, you want to obtain an overview of SAP Liquidity Planner. Which goals are to be attained with SAP Liquidity Planner and how is the system architecture structured?

 SAP AG 2008

You are a member of a project team that has to provide the decision makers at your company with an overview (in good time) of how cash accounting and liquidity planning could be implemented.

© SAP AG

FSC800

1-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 SAP Solution MAP – SAP ERP

 SAP AG 2008

In addition to Financial Accounting, Management Accounting, and Corporate Governance, the Financials area also includes Financial Supply Chain Management.

© SAP AG

FSC800

1-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 Solution MAP – FSCM

 SAP AG 2008

The task of Cash and Liquidity Management (note: SAP Liquidity Planner is the equivalent to Liquidity Management) is to provide functions for efficient short, medium, and long-term liquidity analysis and planning. SAP Liquidity Planner is therefore part of FSCM (Financial Supply Chain Management).

© SAP AG

FSC800

1-5

SAP PORTUGAL | USO EXCLUSIVO | 2013 Interaction Between "Treasury" Components Corporate Headquarter – Treasury Risk Management Credit Risk Analyzer

Money market trading

Market Risk Analyzer

Foreign Derivative exchange

Portfolio Analyzer

Loans

Security

Transaction Manager

In-House Cash

Liquidity Planner Cash Management

IHC

CM

Cash and Liquidity Management

LP

Unit 1

IHC

Data of operational systems

CM

LP

Unit 2

IHC

Bank data

CM

LP

Unit 3

 SAP AG 2008

The most important reporting tasks of Cash Management are to provide: • A value date-dependent cash position • A liquidity forecast The reporting tasks of SAP Liquidity Planner are to provide: • Retrograde liquidity analysis • Liquidity planning

© SAP AG

FSC800

1-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 How Cash Management and Liquidity Planner Differ Cash Management

Liquidity Planner

Opening balance

Opening balance

Revenue

Revenue Customer group X

Revenue from sales

Customer group Y

Interest earnings

...

Other revenue

Expenditure

Expenditure

Vendor group X

Personnel

Vendor group Y

Materials

...

Assets ... Closing balance

Closing balance

 SAP AG 2008

The key difference is that Cash Management shows the cash flows on the customer and vendor side in the liquidity forecast ("to whom" or "from whom"). Liquidity Planner shows cash flows according to funds utilization or origin ("for what purpose").

© SAP AG

FSC800

1-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 SAP Liquidity Planner – An Overview •

SAP Liquidity Planner provides: Retrograde determination of cash flows Medium to long-term planning of these flows

•

SAP Liquidity Planner (SAP Liquidity Management) consists of two components: Actual Calculation in ERP Planning in BI

•

Reporting for actual and plan data is carried out in SAP Business Warehouse (BI).

 SAP AG 2008

It must be noted that SAP Liquidity Planner consists of two components.

© SAP AG

FSC800

1-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 System Architecture – Overview

BI Reporting

Planning

Database

Extraction

ERP Operational ERP

Operational ERP

 SAP AG 2008

Actual data is determined in the operational ERP systems through the "actual" calculation. The results are extracted to BI and made available for reporting. Planning is carried out in BI and the data can also be used here for reporting. You can compile various reports in BI: plan-plan comparisons, plan-actual comparisons, variance analyses, and many more.

© SAP AG

FSC800

1-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 LP in FSCM: Summary

You are now able to: Provide an overview of Financial Supply Chain Management Outline the key aspects of SAP Liquidity Planner: Tasks System architecture How it differs from Cash Management

 SAP AG 2008

© SAP AG

FSC800

1-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Administration – Basic Knowledge

Contents: Concept of cash accounting Tasks of cash accounting and liquidity planning Recipients and the need for information Cash accounting and general accounting

 SAP AG 2008

© SAP AG

FSC800

2-1

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Administration – Basic Knowledge: Unit Objectives

At the conclusion of this unit, you will be able to: Understand the relationships between general accounting and cash accounting that are required to implement SAP Liquidity Planner Explain the business concept behind cash accounting and liquidity planning

 SAP AG 2008

© SAP AG

FSC800

2-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 Basic Knowledge Business Administration: Business Scenario

Before you start working in the project team, you want to obtain a business overview of cash accounting and liquidity planning. Which business-related tasks and goals are set for cash accounting and liquidity planning?

 SAP AG 2008

© SAP AG

FSC800

2-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 Concept of Cash Accounting

Data source

Incoming/outgoing payments

(SAP) Cash accounting

Expenditure/revenue

Expense/profit

Costs/benefits

Accounting

Controlling

Cash accounting Cash basis accounting

Profit/loss statement

Managerial accounting

 SAP AG 2008

In business literature, the concept of cash accounting and its definition are the subject of much discussion. These discussions also refer to the terms: cash budget management, flow-of-funds analysis, cash flow statement, and cash flow accounting. Cash accounting records changes to cash flows, whereby cash flows are incoming and outgoing payments of liquid funds, such as cash in hand and bank savings. In accordance with national and international accounting standards such as DRS (Accounting Standards of Germany), FASB, and IAS, the term cash flow is used here to refer to changes in the means of payment. Liquidity is therefore referred to as a financial accounting-related concept. Consequently, cash accounting distinguishes itself from accrual accounting.

© SAP AG

FSC800

2-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 Time-Based Delimitation

Cash flow accounting

Past

Liquidity planning

Current period

Retrograde determination

Future

t

Reciprocal determination

 SAP AG 2008

Within a certain period, cash accounting records transactions that directly influence the stock of liquid funds, regardless of the period in which payments were made. Cash accounting functions across all periods. SAP Liquidity Planner adopts this concept.

© SAP AG

FSC800

2-5

SAP PORTUGAL | USO EXCLUSIVO | 2013 Tasks of Cash Accounting and Liquidity Planning

Solvency information Information about internal financing potential Increase transparency in financial operations by providing information about funds utilization and origin. Why was/is liquidity lost? Why was/is liquidity retained?

 SAP AG 2008

The main task of cash accounting is to provide information about the solvency and internal financing potential of the company. It also forms the basis for creating flow-of-funds analyses and planning. In comparison to balance sheets and profit and loss statements (P&L), it provides a better evaluation of the financial situation of a company. Internal financing potential means that a company can generate more revenue than expenditures from its business activities. This is also referred to as internal financing strength. If a company can continuously build up liquidity in addition to conducting its regular business activities, this surplus is called strategic liquidity.

© SAP AG

FSC800

2-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 Profit and Cash Flow

Profit Cash flow

W.T. Grant 1967 - 1975  SAP AG 2008

Comparing the profit and cash flow of the W.T. Grant company demonstrates the importance of analyzing and determining cash flow. Even though the company was profitable up until one year before its insolvency, it could no longer meet its payment obligations. However, cash flow had already been negative in earlier fiscal years. The reason for such a discrepancy can be found in the different ways accounting information can be interpreted. For example, discrepancies can occur due to an increased stocking up of a warehouse, an expansion strategy requiring high investment, or by a difficult economic period during which extended terms of payment are often granted.

© SAP AG

FSC800

2-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 Display Methods

There are two methods for displaying cash flows: •

Indirect method This method and form of display is predominantly used for cash flows and flow-of-funds analyses.

•

Direct method Many companies strive to use this method for cash flows since it is used for planning.

 SAP AG 2008

The indirect method is currently used the most by companies. However, the direct method is used increasingly more often to improve transparency.

© SAP AG

FSC800

2-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 Structure of the Cash Flow (Direct Method)

According to national and international regulations, the flow-offunds analysis based on the direct method is divided into three areas: Cash flow from operating activities Cash flow from investing activities Cash flow from financing activities

 SAP AG 2008

The international accounting principles specify the following structure: Ÿ Cash flow from operating activities Ÿ Cash flow from investing activities Ÿ Cash flow from financing activities

© SAP AG

FSC800

2-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 Recipients and the Need for Information Investors Lenders

Suppliers

Investment Dividends and withdrawals

Loan

Repayment and interest payments

Payment of activity

Company

Payment of activity

Payment of activity

Employees

Customers Activity

Cash flow

 SAP AG 2008

With regard to liquidity flows, companies are involved with different interested parties and recipients. Employees, customers, suppliers, investors, and lenders have different information requirements.

© SAP AG

FSC800

2-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 Financial Accounting and Cash Accounting (I)

Chart of accounts Cash accounts

Balance sheet accounts

P&L accounts

Cash accounting

Balance sheet

P&L statement

Revenue

Expenditure

Assets (without LF*)

Liabilities and equity

Cash balance

Expense

Profit

P&L account

 SAP AG 2008

The data source for cash accounting is the posting material in financial accounting. In financial accounting, cash accounts, balance sheet accounts, and P&L accounts are integrated to form a threefold accounting system. This account-based integration enables you to determine the cash flow in cash accounting. Accounting and consequently ERP systems are constructed according to the principle of doubleentry accounting. A triple-entry accounting system has not been implemented yet. Note *) LF = Liquid funds

© SAP AG

FSC800

2-11

SAP PORTUGAL | USO EXCLUSIVO | 2013 Financial Accounting and Cash Accounting (II)

Affecting liquidity Affecting Not net incomeaffecting liquidity Affecting liquidity

Not affecting net incomeNot affecting liquidity

Chart of accounts Cash accounts Balance sheet accounts P&L accounts Cash Cash outflow Asset account Capital/debt Expense Revenue inflow account account account Debit Credit Debit Credit Debit Credit Debit Credit Debit Credit Debit Credit 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10 11 11 12 12 13 13 14 14

 SAP AG 2008

There are 14 different account assignment types that can be explained using the following examples: 1.

Cash payment for office materials

2.

Revenue from cash sales

3.

Depreciation of fixed assets

4.

Posting of supplier invoices

5.

Invoicing of an activity

6.

Dissolving of provisions

7.

Revenue from invoices

8.

Borrowing (loans)

9.

Payment of supplier invoices

10. Cash payment for material purchases 11. Accounting exchange on the assets side 12. Contributions in kind from companies 13. Clearing of payables and receivables 14. Accounting exchange on the liabilities side

© SAP AG

FSC800

2-12

SAP PORTUGAL | USO EXCLUSIVO | 2013 Basic Knowledge Business Administration: Summary

You are now able to: Describe the concept of cash accounting Classify tasks of cash accounting and liquidity planning Name the recipients of cash accounting and liquidity planning Outline the relationship between financial accounting and cash accounting

 SAP AG 2008

© SAP AG

FSC800

2-13

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

2-14

SAP PORTUGAL | USO EXCLUSIVO | 2013 Exercises Unit:

SAP Liquidity Planner and Basic Business Knowledge

Topic:

Basic Background Knowledge

At the conclusion of these exercises, you will be able to: • Provide an overview of SAP Liquidity Planner • Name the relationships required from a business perspective You want to outline SAP Liquidity Planner and be able to name the most important business relationships.

1-1 How does SAP Liquidity Planner differ from SAP Cash Management?

1-2 Which components make up SAP Liquidity Planner? Where does reporting take place?

1-3 Outline the system architecture.

1-4 How does cash accounting function (with regard to time)?

© SAP AG

FSC800

2-15

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-5 Name the main task of cash accounting and liquidity planning.

1-6 Which methods exist for a flow-of-funds analysis?

1-7 Name the key sections of a flow-of-funds analysis.

1-8 From where is the data for cash accounting sourced?

© SAP AG

FSC800

2-16

SAP PORTUGAL | USO EXCLUSIVO | 2013 Solutions Unit:

SAP Liquidity Planner and Basic Business Knowledge

Topic:

Basic Background Knowledge

1-1 SAP Liquidity Planner displays liquidity flows according to funds utilization and origin.

1-2 SAP Liquidity Planner consists of the Actual Calculation component (ERP) and a planning component in BI. Reporting is also carried out in BI. 1-3 Use the system architecture shown on slide 9 of unit 1. 1-4 Cash accounting functions across all periods. 1-5 The main task of cash accounting and liquidity planning is to provide information about internal financing potential and to increase transparency in financial operations. 1-6 There are both direct and indirect methods. 1-7 A flow-of-funds analysis is divided into: - Cash flow from current activities - Cash flow from investment activities - Cash flow from financing activities 1-8 The data for cash accounting is sourced from accounting.

© SAP AG

FSC800

2-17

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

2-18

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing in ERP

Contents: Customizing settings Activation of cash accounting (Actual Calculation)

 SAP AG 2008

© SAP AG

FSC800

3-1

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing in ERP: Objectives

At the conclusion of this unit, you will be able to: Configure Customizing for the ERP part of SAP Liquidity Planner Carry out the steps required for activation

 SAP AG 2008

© SAP AG

FSC800

3-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing in ERP: Business Scenario

The Customizing phase of the implementation project has begun. You carry out the required Customizing steps and activation activities.

 SAP AG 2008

© SAP AG

FSC800

3-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 Master Data

SAP Liquidity Planner contains the following master data: Liquidity item Company code Business area

 SAP AG 2008

The master data of SAP Liquidity Planner includes: Ÿ Liquidity item Ÿ Company code Ÿ Business area

© SAP AG

FSC800

3-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 Accessing Customizing

Two main areas have to be configured in Customizing: Basic Settings Assignment From Bank Statement From FI Information From Invoices

 SAP AG 2008

You can access the Customizing settings using transaction /nflqcust or via the Customizing path: Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner.

© SAP AG

FSC800

3-5

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing: Basic Settings (I)

The basic settings are customized in four activities: Edit Liquidity Items (1) Define Global Data (2) Other Actual Accounts (3) Activate Company Code (4)

 SAP AG 2008

You can access the basic settings for Customizing using transaction /nflqcust or via the Customizing path: Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner.

© SAP AG

FSC800

3-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing: Basic Settings (II)

Edit Liquidity Items (1) Here, you define the liquidity items that carry the values. No totals items or summarization line items are maintained. This is carried out in BI.

Define Global Data (2) Default item for incoming and outgoing payments Item for transfer payments Posting date or value date Business area

 SAP AG 2008

You can access the Customizing settings using transaction /nflqcust or via the Customizing path: Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner. Global data Ÿ Default liquidity items are assigned online, whereby debit items are assigned to the incoming payment item and credit items to the outgoing payment item. Ÿ Liquidity-neutral postings are shown in the transfer items. Ÿ A decision must be made as to whether the posting date or the value date is to be included. Ÿ If the business area is to be included, this must be defined in Customizing.

© SAP AG

FSC800

3-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing: Basic Settings (III)

Other Actual Accounts (3) Definition of accounts that are not automatically defined as actual accounts

Activate Company Code (4) Activation of the relevant company codes

 SAP AG 2008

You can access the Customizing settings using transaction /nflqcust or via the Customizing path: Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner. An additional number range must be created when the company code is activated. You can create the number range using transaction OT20.

© SAP AG

FSC800

3-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing: Assignment Mechanisms (I)

From Bank Statement

From FI Information

Document chains

ERP

From Invoice

 SAP AG 2008

There are two sources for determining cash flows. The first is data from electronic bank statements and the second is accounting data. The "From Bank Statement" mechanism analyzes the data in the electronic bank statement, whereas the "From FI Information" and "From Invoice" mechanisms use the accounting data. The assignment mechanisms can be used separately or together.

© SAP AG

FSC800

3-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing: Assignment Mechanisms (II)

Definition of the "From Bank Statement" assignment mechanism: Define Query Sequences Assignment to Bank Accounts

 SAP AG 2008

You can access the Customizing settings using transaction /nflqcust or via the Customizing path: Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner. Under "Define Query Sequences", you define separate queries for each bank since banks often deliver data in different ways. Under "Assignment to Bank Accounts", you specify which query sequence the mechanism uses for which bank account. Every bank account is described in terms of company code, house bank ID, and account ID.

© SAP AG

FSC800

3-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing: Assignment Mechanisms (III)

Definition of "From FI Information" assignment mechanism: Settings for FI Mechanisms Define Query-Relevant G/L Accounts Define Query Sequences

 SAP AG 2008

You can access the Customizing settings using transaction /nflqcust or via the Customizing path: Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner. The settings for FI mechanisms are explained separately. Under "Define Query-Relevant G/L Accounts", you map G/L accounts to liquidity items. Under "Define Query Sequences", you define one or more queries for the "From FI Information" mechanism.

© SAP AG

FSC800

3-11

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing: Assignment Mechanisms (IV)

The following most important settings are configured in "Settings for FI Mechanisms": Partial reassignment N:M treatment Info accounts in the application Order information

 SAP AG 2008

You can access the Customizing settings using transaction /nflqcust or via the Customizing path: Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner. If you select "Part. Reassign.", assignment to a liquidity item is carried out also in cases where the payment has only been partly cleared. The actual document is split temporarily, whereby the partial amounts cleared are assigned to the liquidity item determined and the remaining amount stays assigned to the original liquidity item. In standard company accounting, multiple bank statement postings (N) are cleared to the bank subaccounts together with a number of postings (M). This is known as N:M treatment. In this case, the assignment mechanism cannot trace the document chains. This means that no liquidity items can be determined. If you select this entry, a workaround is activated for the case described above. This enables the document chains to be traced. If you select Info Accts in Appl., it specifies that you want to assign G/L accounts to liquidity items in the application rather than in Customizing.

© SAP AG

FSC800

3-12

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing: Assignment Mechanisms (VI)

Definition of "From Invoices" assignment mechanism: Settings for FI Mechanisms Define Query-Relevant G/L Accounts Define Query Sequences

 SAP AG 2008

You can access the Customizing settings using transaction /nflqcust or via the Customizing path: Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner. The options under "Settings for FI Mechanisms" and "Define Query-Relevant G/L Accounts" correspond to those in the Customizing option for the FI mechanism. Under "Define Query Sequences", you define one or more queries for the "From Invoices" mechanism.

© SAP AG

FSC800

3-13

SAP PORTUGAL | USO EXCLUSIVO | 2013 Tools in Customizing

Three reports are shipped in Customizing: Delete Flow Data Regenerate Flow Data FI Assignment Analysis

 SAP AG 2008

You can access the Customizing settings using transaction /nflqcust or via the Customizing path: Financial Supply Chain Management -> Cash and Liquidity Management Liquidity Planner. You can use report "Delete Flow Data" to delete the data within the cash accounting (actual calculation). You can use report "Regenerate Flow Data" to regenerate the data within the cash accounting (actual calculation). The report "FI Assignment Analysis" provides support when you set up the "From FI Information" assignment mechanism.

© SAP AG

FSC800

3-14

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing in ERP: Summary

You are now able to: Configure Customizing for the ERP part of SAP Liquidity Planner Carry out the steps required for activation

 SAP AG 2008

© SAP AG

FSC800

3-15

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

3-16

SAP PORTUGAL | USO EXCLUSIVO | 2013 Exercises Unit:

Customizing

Topic:

Setting Up Customizing

At the conclusion of these exercises, you will be able to: • Configure baseline Customizing • Name the relationships required from a business perspective You want to configure baseline Customizing for SAP Liquidity Planner.

1-1 Which the transaction code calls the Customizing path for baseline Customizing? 1-2

In company code AC##, create a cash account in chart of accounts INT (for example, 101000) as an “Other Actual Account” for your company code AC##.

1-3 Activate your company code AC## with number range 01. The number range should already exist (if not, you can use transaction ot20). 1-4 For company code AC##, create a query sequence for Deutsche Bank. Since you want this to be valid for your company code only, name the query sequence AC##_DEUBA. 1-5 In your company code AC##, assign the query sequence defined in steps 1-4 for Deutsche Bank (house bank 1000 and account ID 1000). 1-6 Explain the function of the “Part. Reassign.” indicator in transaction FLQC13 (Liquidity Calculation – Settings for FI Mechanisms).

1-7 Explain the function of the “N:M Treatment” indicator.

1-8 Explain the function of the “Info Accts in Appl.” indicator.

© SAP AG

FSC800

3-17

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-9 Map G/L accounts to liquidity items for your company code AC## using transaction “Query-Relevant G/L Accounts”. When doing so, use chart of accounts INT. The mapping between G/L accounts and liquidity items should be as follows:

© SAP AG

G/L Account

Default Value (Liquidity Item)

1000

230000

2000

230000

34000

230000

43000

210000

45000

210000

60500

311000

70000

370000

70001

370000

220000

340000

273100

330000

273300

330000

300000

122000

300010

122000

310000

122000

416300

127000

416302

127000

420000

121100

440000

121200

473000

125000

473110

125000

476000

127000

477100

126000

800000

111000

800001

112000

800002

113000

807000

330000

930000

380000

FSC800

3-18

SAP PORTUGAL | USO EXCLUSIVO | 2013 Map your reconciliation accounts to the corresponding “Buffer Items”. Make a note of this mapping, for example: G/L Account

Default Value (Liquidity Item)

140000

DEBTOR

141000

DEBTOR

160000

VENDOR

160100

VENDOR

1-10 Define a query sequence for the “From FI Information” mechanism. Use the following name: AC##_FIINFO.

1-11 Define a query sequence for the “From Invoices” mechanism. Use the following name: AC##_INVOICE.

1-12 As a rule, what is the purpose of report “Regenerate Flow Data” in a project?

© SAP AG

FSC800

3-19

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

3-20

SAP PORTUGAL | USO EXCLUSIVO | 2013 Solutions Unit:

SAP Liquidity Planner and Basic Business Knowledge

Topic:

Basic Background Knowledge

1-1 Transaction FLQCUST calls the Customizing path for SAP Liquidity Planner. 1-2 Go to Customizing (transaction SPRO):

→ Financial Supply Chain Management → Cash and Liquidity Management → Liquidity Planner → Basic Settings: Liquidity Calculation → Define Other Actual Accounts Choose “New Entries”. Enter the following values: Chrt/Accts

CoCode

G/L Account

Not Actual

INT

AC##

101000

Leave blank

and save. 1-3 Go to Customizing:

→ Financial Supply Chain Management → Cash and Liquidity Management → Liquidity Planner → Basic Settings: Liquidity Calculation → Activate Company Code Choose “New Entries”. Enter the following values: CoCd

Company Name

Act.

No.

AC##

Copied automatically

Set X indicator

01

and save. (If required: Create the number range using transaction ot20. Enter your company code (AC##). Choose “Insert Interval”).

© SAP AG

FSC800

3-21

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-4 Go to Customizing:

→ Financial Supply Chain Management → Cash And Liquidity Management → Liquidity Planner → Assignment → From Bank Statement → Define Query Sequences Choose “New Entries”. Enter the following values: Query Sequence

Query CoCd

Name

Description

AC##_DEUBA

AC##

Query_Deuba

Query_Deuba

and save. 1-5 Go to Customizing:

→ Financial Supply Chain Management → Cash and Liquidity Management → Liquidity Planner → Assignment → From Bank Statement → Assignment to Bank Accounts Choose “New Entries”. Enter the following values: CoCd

House Bk

Acct ID

Seq.

AC##

1000

1000

AC##-DEUBA

and save. 1-6 Explanation of the “Part. Reassign.” indicator: If you select Part. Reassign. (partial reassignment), assignment to a liquidity item is carried out also in cases where the payment has only been partly cleared. The actual document is split temporarily, whereby the partial amounts cleared are assigned to the liquidity item determined and the remaining amount stays assigned to the original liquidity item. If the Part. Reassign. indicator is not set, a complete assignment is only carried out once the payment and corresponding documents have been completely cleared in the document chain. Up to this point, the total amount remains assigned to the initial liquidity item.

© SAP AG

FSC800

3-22

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-7 Explanation of the “N:M Treatment” indicator: In standard company accounting, multiple bank statement postings (N) are cleared to the bank subaccounts together with a number of postings (M). This is known as N:M treatment. In this case, the assignment mechanism cannot trace the document chains. This means that no liquidity items can be determined. If you select N:M Treatment, a workaround is activated for the case described above. This enables the document chains to be traced. 1-8 Explanation of the “Info Accts in Appl.” indicator: You use this indicator to specify that info accounts for cash accounting (that is, accounts for which assignment programs try to derive a liquidity item from the information in the document line item) are entered in the application rather than in Customizing (FLQC7). 1-9 Go to Customizing:

→ Financial Supply Chain Management → Cash and Liquidity Management → Liquidity Planner → Assignment → From FI Information → Define Query-Relevant G/L Accounts Choose “New Entries”. Enter all values specified in the task: Chart of Accounts

Company Code

G/L Account

Further

Default Value

INT

AC##

1000

230000

INT

AC##

……

…..

….

…..

……

…..

INT

AC##

140000

DEBTOR

INT

AC##

….

…..

and save.

© SAP AG

FSC800

3-23

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-10 Go to Customizing:

→ Financial Supply Chain Management → Cash and Liquidity Management → Liquidity Planner → Assignment → From FI Information → Define Query Sequences Choose “New Entries” and enter the following values: Query Sequence

Origin

Query CoCd

Name

Description

AC##_FIINFO

C

AC##

FI INFO

FI INFO

Save your data. 1-11 Go to Customizing:

→ Financial Supply Chain Management → Cash And Liquidity Management → Liquidity Planner → Assignment → From Invoices → Define Query Sequences Choose “New Entries” and enter the following values: Query Sequence

Origin

Query CoCd

Name

Description

AC##_INVOICE

C

AC##

Invoice

Invoice

Save your data. 1-12 As a rule, the report “Regenerate Flow Data” is used to generate data created before the activation date of the actual calculation.

© SAP AG

FSC800

3-24

SAP PORTUGAL | USO EXCLUSIVO | 2013 Application in ERP

Contents: Using Liquidity Planner

 SAP AG 2008

© SAP AG

FSC800

4-1

SAP PORTUGAL | USO EXCLUSIVO | 2013 Application in ERP: Unit Objectives

At the conclusion of this unit, you will be able to: Use and execute the Actual Calculation application of SAP Liquidity Planner This includes: Assignment mechanisms Transfer postings Settings Information system

 SAP AG 2008

© SAP AG

FSC800

4-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 Application in ERP: Business Scenario

You have configured Customizing successfully. You now begin to use the application functions, thereby increasing your knowledge in this area.

 SAP AG 2008

© SAP AG

FSC800

4-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 Application Areas

The menu is divided into the following application areas: Assignment Transfer Settings Information System

 SAP AG 2008

The main menu areas are: • Assignment • Transfer • Settings • Information System

© SAP AG

FSC800

4-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 Cash Accounting – Process

Electronic bank statement Documentbased actual movement

Result logs

Import Import bank bank statements statements or or enter enter document document in in SAP SAP FI FI

Automatic assignment mechanisms

Assignment result satisfactory?

No Postprocess parameters

Yes; manual adjustments if required Analysis reports

Actua l data

Extraction – BI

 SAP AG 2008

In the actual data process, the electronic bank statement is first imported and the accounting documents posted. The relevant assignment reports are then initiated. The result is displayed and written to the database. You can display the data by means of the analysis report or extract the data to BI. The process ends within the ERP system when data is extracted to BI.

© SAP AG

FSC800

4-5

SAP PORTUGAL | USO EXCLUSIVO | 2013 Application: Assignment ERP

From FI Information

From Invoice

Document chains

From Bank Statement

Manual

 SAP AG 2008

There are two sources for determining cash flows. The first is the data from the electronic bank statement; the other is the financial accounting data. The "From Bank Statement" mechanism analyses the data in the electronic bank statement, whereas the "From FI Information" and "From Invoice" mechanisms use the financial accounting data. The assignment mechanisms can be used separately or together.

© SAP AG

FSC800

4-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 From Bank Statement (I) Sample Company New York --------------------------------------------------------------------------------------------------------------------------------------------------------------------------Postal giro office Manhattan Account holder: John Smith Bank code: 66010075 Account number: 179097-756 Statement number: 00051 Currency: DEM Statement date: 09/24/2000 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------CNo

Val. Dte Pstg Dte Note to Payee

Posting Text

BTC

Daybook

Amount

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

00001 09/24 00002 09/24 00003 09/24

09/24 09/24 09/24

00004 09/24 00005 09/24

09/24 09/24

00006 09/24

09/24

CHECK DEPOSIT Document 1500000285 ID 8899100 / X4711 EUROTEL GmbH Check 1500000282 Invoice from 06/03/YY Inv. no. 17100008111 Cash discount 3 % Invoice from 06/12/YY

DEBIT MEMO

070 004 005 001 051

EUROTEL telephone costs

Beginning balance 33,900.00 --------------------------------------------30,000.00 3,300.00 386.16 -

600.00 10,700.00

051 1,000,000,000.00 ------------------------------------------------------------Total Debit 4,286.16 Total Credit 1,000,040,700.00 ------------------------------------------------------------Ending balance 1,000,070,314.00

 SAP AG 2008

This mechanism evaluates the actual documents that refer to a manual or electronic bank statement. Queries (rules) must be created that display the information of the electronic bank statement in the liquidity items.

© SAP AG

FSC800

4-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 From Bank Statement (II)

Three steps must be carried out: 1.

Set up queries

2.

Generate queries for the query sequences

3.

Start assignment report "From Bank Statement"

 SAP AG 2008

The query is used to evaluate selected fields of the electronic bank statement. The query can also be interpreted as a type of "rule". The defined queries can be set up in a query sequence. When the assignment mechanism is executed, the query sequence is used to call the respective queries and the electronic bank statement is then evaluated.

© SAP AG

FSC800

4-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 Function: From FI and Invoices Bank 100 3a

Retrograde determination

Bank subaccount 3a 100

100 2a Vendor

2a 100

Posting transactions

100 1a Rent

LI rent

1a 100

-100

 SAP AG 2008

The "From FI Information" and "From Invoices" mechanisms function according to the principle of tracing document chains. The chain is traced from the bank document, via the clearing document, right through to the end.

© SAP AG

FSC800

4-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 "From FI Information" and "From Invoices" For both assignment mechanisms: From FI Information From Invoices Three steps must be carried out: 1.

Set up queries

2.

Generate queries for the query sequences

3.

Start the assignment report "From FI Information" "From Invoices"

 SAP AG 2008

The query is used to evaluate selected fields of the accounting document. The query can also be interpreted as a type of "rule". The defined queries can be set up in a query sequence. When the assignment mechanism is executed, the query sequence is used to call the respective queries and the accounting document is then evaluated.

© SAP AG

FSC800

4-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 Dynamic Analysis Report for Mechanisms

When assignment mechanisms are executed online, a dynamic report is displayed. This provides: Detailed overview Detailed display of the individual cash flow Detailed analysis right through to the original document

 SAP AG 2008

The "From Invoices" or "From FI Information" assignment reports generate a dynamic online report. This shows all the relevant results of the run.

© SAP AG

FSC800

4-11

SAP PORTUGAL | USO EXCLUSIVO | 2013 Transfer Postings

Three transactions are available in the Transfer area: 1.

Create (with template function)

2.

Change

3.

Display

 SAP AG 2008

As already mentioned in Customizing, the document numbers must be defined beforehand. To do so, use transaction OT20. Under these menu options, postings can be made between the individual liquidity items.

© SAP AG

FSC800

4-12

SAP PORTUGAL | USO EXCLUSIVO | 2013 Settings (I)

The following functions are available in the Settings area: Edit Query Display Query Test Query Set Up Query Sequence

 SAP AG 2008

The query is used to evaluate selected fields of the electronic bank statement or the accounting document. The query can also be interpreted as a type of "rule". The defined queries can be set up in a query sequence. When the assignment mechanism is executed, the query sequence is used to call the respective queries and the electronic bank statement or accounting document is then evaluated.

© SAP AG

FSC800

4-13

SAP PORTUGAL | USO EXCLUSIVO | 2013 Settings (II)

The following functions are available in the Settings area: Map liquidity items to G/L accounts Upload/Download Queries Query Sequence (Assignment) Info Account (Application)

 SAP AG 2008

Instead of mapping liquidity items and G/L accounts in Customizing, you can also do so in the application menu. You also create queries here that are relevant for tracing the document chain.

© SAP AG

FSC800

4-14

SAP PORTUGAL | USO EXCLUSIVO | 2013 Information System

The most important reports are: Payment Report Totals List Line Items Line Item History Queries Query Sequences G/L Account List

 SAP AG 2008

The two most important reports are the payment report and the totals list since you can use them to display the results. The G/L account list report provides a brief overview of your mapping (G/L accounts to liquidity items).

© SAP AG

FSC800

4-15

SAP PORTUGAL | USO EXCLUSIVO | 2013 Application in ERP: Summary

You are now able to: Configure the settings required in Actual Calculation and use the functions correctly

 SAP AG 2008

© SAP AG

FSC800

4-16

SAP PORTUGAL | USO EXCLUSIVO | 2013 Exercises Unit:

Application in ERP

Topic:

Using Actual Calculation

(In total: 14 exercises – exercises 1 to 7 are optional) At the conclusion of these exercises, you will be able to: • Use Actual Calculation

You want to use Actual Calculation.

1-1 Generate data using electronic bank statements - optional exercise You can use an auxiliary program to generate files that are normally delivered by the bank with the bank statement and, at the same time, post the FI documents required for the subsequent import of the bank statement. Generate the test data and the files STATEMENT##.TXT and SALES ##.TXT using report RFEBKATX. You can call this report using transaction SE38 or via System Services Reporting. Variant FSC800 contains all input values in the correct format. You can use this variant to simplify the task. You do not download to your PC, but place the files on the application server. Call the files Statement##.TXT and Sales##.TXT to be generated (## = your group number). As bank clearing accounts, post to the accounts of house bank ID 1000 and account ID 1000 that belong to your company code. Select today’s date as the statement date and invoice date. You can decide whether to display the posting screens. Generate one or more open items for customer T-T05A## and also generate open items in your clearing accounts. Execute the report.

© SAP AG

FSC800

4-17

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-2 Import the data (import the electronic bank statement) - optional exercise Now import the files you have just generated (STATEMENT##.TXT and SALES##.TXT). When importing the files, you can also use report variant FSC800, which contains all the required settings. Select Immediate Posting and restrict the Number Range for Document Numbers to 1800000000 to 1809999999. Print out the bank statement, posting log, and statistics. Execute the report. 1-3 Display the imported bank statement - optional exercise You can do so via the menu or using transaction FF.6 1-4 Which business transaction code was used to import the transactions? - optional exercise The business transaction code is: ________________ . Create a query for the BS mechanism. Name the query as follows: AC##_revenue with corresponding names. Assign the liquidity item 111000 to the query. Use business transaction code 051 as a condition - optional exercise 1-5 Assign the query to your query sequence AC##-DEUBA - optional exercise 1-6 Start report “From Bank Statement” with today’s date and document the result - optional exercise

© SAP AG

FSC800

4-18

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-7 Now generate postings as a basis for the accounting assignment report. You can create the following account assignments using transaction FB01 or the relevant accounting posting transactions. In addition to the posting examples below, you can enter other postings. The more postings exist, the more evaluations are included in Actual Calculation. Use: - For input tax, use indicator V0 (or VN) - For output tax, use indicator A0 Use cost center

T-A20A##.

Use customer

T-T05A## or T-F00A##.

Use vendor

T-F00A00.

Use document type

SA.

If you post via a clearing account or customer/vendor (in other words, the document chain is set up this way), you clear the documents accordingly. You can select the value date of your choice. Today’s date is specified in the following table. BS

© SAP AG

Account

Amount

Value Date

40

113100

10000

Today

50

273100

10000

40

220000

12000

50

113100

12000

40

45000

250000

50

113100

250000

Today

40

113100

750000

Today

50

70000

750000

40

416300

11000

50

100000

11000

40

420000

20000

50

113100

20000

40

476000

9000

50

113100

9000

Today

Today

Today

Today FSC800

4-19

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

40

478000

21000

50

113100

21000

40

930000

125000

50

113100

125000

Today

40

113100

99000

Today

50

800200

99000

40

43000

85000

50

113102

85000

40

113102

85000

50

113100

85000

31

T-F00A00

23000

40

476000

23000

25

1000

23000

50

113100

23000

Today

Today

Today

Today

FSC800

4-20

SAP PORTUGAL | USO EXCLUSIVO | 2013 Make a note of your document numbers:

© SAP AG

FSC800

4-21

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-8 Start report FLQAC for your company code. Make a note of the most important results from the run:

Also navigate to the relevant accounting documents. 1-9 Carry out one or more transfer postings. To do so, navigate to the “Transfer” menu node. Carry out the following transfer postings for your company code: Company code: Date: Currency:

AC## Today Euro

For your company code AC## Liquidity item:

127000

Amount: - 5,000

Liquidity item:

112000

Amount: + 5,000

Liquidity item:

126000

Amount: - 1,000

Liquidity item:

127000

Amount: + 1,000

1-10 Execute the payment report. To do so, go to the “Information System” menu node. 1-11 Call the totals list. To do so, go to the “Information System” menu node. 1-12 Call the G/L account list. Which liquidity item is assigned to G/L account 62110? Make a note of the liquidity item:

If the account is not assigned to a liquidity item, assign liquidity item 311000 to it.

© SAP AG

FSC800

4-22

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-13

Develop a query for loan account 62110 for a loan repayment. Which indicator (Debit/Credit) is used for posting in the case of a loan repayment? Make a note of your answer.

Go to Settings Assignment from FI and develop your query. Name your query AC##_REPAY. Add the description/name. Assign the query to the query sequence of your company code. Post a loan taken of EUR 500,000. Make a note of the document number.

Post a loan repayment of EUR 50,000. Make a note of the document number.

Now start the “From FI Information” assignment mechanism (FLQAC). What is the result? Make a note of this:

© SAP AG

FSC800

4-23

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

4-24

SAP PORTUGAL | USO EXCLUSIVO | 2013 Solutions Unit:

Application in ERP

Topic:

Using Actual Calculation

1-1 Solution for generating test data and the files STATEMENT##.TXT and SALES##.TXT. System Services Reporting Program “RFEBKATX” (to call variant FSC800, choose “Get Variant” in the application function bar)

Field Name or Data Type

Values

Format

M - MultiCash

Statement file

Statement##.txt

Line item file

Sales##.txt

Company code

AC##

House bank (ID)

1000

Account (ID)

1000

Statement date

Today

Invoice date

- 10 days

Posting method

Set indicator

Customers to be posted to

T-T05A##

First amount

For example, 1000

... Generate open items in clearing accounts

Set indicator

... Execute the report. Postings and bank statement files are now generated.

© SAP AG

FSC800

4-25

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-2 Solution for importing bank statement files. Accounting Financial Supply Chain Management Cash and Liquidity Management Incomings Import Electronic Bank Statement (to call variant FSC800, “Get Variant” in the application function bar) Field Name or Data Type

Values

Import data

Set indicator

Format

M - MultiCash

Statement file

Statement##.txt

Line item file

Sales##.txt

Workstation upload

Do not set indicator

Post immediately

Set indicator

BELNR number interval

1800000000 - 1809999999

Print bank statement

Set indicator

Print posting log

Set indicator

Print statistics

Set indicator

choose

Execute the report. The files are imported and posted immediately. 1-3 Solution for displaying bank statement data. Use transaction FF.6 or the menu path Accounting Financial Supply Chain Management Cash and Liquidity Management Cash Management Incomings Electronic Bank Statement Display Enter company code AC##, house bank ID 1000, and bank ID 1000. 1-4 The business transaction code for the imported data is: 051.

© SAP AG

FSC800

4-26

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-5 To create the query, you can use transaction FLQQB1 or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Settings Assignment from Bank Statement Edit Query Enter AC##_REV as the query ID and assign the relevant names. Then choose “Conditions”, enter 051 in the “Business trans code” field, and save your entry. To assign the query to the query sequence, you can use transaction FLQQB5 or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Settings Assignment from Bank Statement Set Up Query Sequence Select query AC##-DEUBA and enter the query in position 5. Then save your entry. 1-6 To start the “From Bank Statement” assignment mechanism, use transaction FLQAB or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Assignment From Bank Statement Information 1-7 You can update the posting records using transaction FB01.

© SAP AG

FSC800

4-27

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-8 To start the “From FI Information” assignment mechanism, use transaction FLQAC or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Assignment From FI Information 1-9 To make transfer postings between liquidity items, use transaction FLQT1 or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Transfer Create Now enter your data and save. 1-10 To call the payment report, use transaction FLQREP or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Information System Payment Report 1-11 To call the totals list, use transaction FLQLS or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Information System Totals List

© SAP AG

FSC800

4-28

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-12

To call the G/L account list, use transaction FLQLACC or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Information System G/L Accounts List Map account 62110 with liquidity item 311000 using transaction FLQC7.

1-13 A repayment is posted to the debit side. This means that the debit indicator must be set in the “Conditions” settings. To assign the query to the query sequence, you can use transaction FLQQC1 or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Settings Assignment from FI Edit Query Now enter query ID “AC##_REPAY” and assign liquidity item 312000. Then select the conditions and enter the debit indicator here. Save the conditions and the query. To assign the query to the query sequence, you can use transaction FLQQC5 or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Settings Assignment from FI Set Up Query Sequence

© SAP AG

FSC800

4-29

SAP PORTUGAL | USO EXCLUSIVO | 2013 Post the loan taken with transaction FB01: Debit 113100 to Credit 62110. Post the repayment with transaction FB01: Debit 62110

to Credit 113100.

To start the “From FI Information” assignment mechanism, use transaction FLQAC or the following menu path: Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Assignment From FI Information

© SAP AG

FSC800

4-30

SAP PORTUGAL | USO EXCLUSIVO | 2013 Migration from TR-CBM to LP

Content: How migration is carried out from TR-CBM to SAP LP

 SAP AG 2008

TR-CBM (SAP Cash Budget Management) SAP LP (Liquidity Planner)

© SAP AG

FSC800

5-1

SAP PORTUGAL | USO EXCLUSIVO | 2013 Application in ERP: Unit Objectives

At the conclusion of this unit, you will be able to: Understand the process of migrating from TR-CBM to SAP LP Name and use the relevant programs

 SAP AG 2008

© SAP AG

FSC800

5-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 Introduction

As of mySAP ERP 2004, the SAP Liquidity Planner (LP) application is used for liquidity management. Customers that use SAP Cash Budget Management (CBM) have to migrate from TR-CBM to SAP LP when upgrading mySAP ERP 2004.

 SAP AG 2008

As of mySAP ERP 2004, the SAP Liquidity Planner (LP) application is used for liquidity management. Customers that use SAP Cash Budget Management (CBM) have to migrate from TR-CBM to SAP LP when upgrading mySAP ERP 2004.

© SAP AG

FSC800

5-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 Migration from TR-CBM to LP (Overview) TR-CBM

LP Liquidity item

Commitment item

Liquidity item

Commitment item FMFPO Text FMFPOT

Fin. trans. “30-70”

Accounts SKB1

RFLQ_XCB_INFACC (RFLQ_UPLOAD_INFACC)

Accounts with financial trans.

LP: Info accounts

FLQACC_INFO_APP

Actual accounts T-cd:FLQC4

"90" Fin. trans. Comm. item fin. trans. “90” FMFPO- FIVOR Accounts SKB1

Text

FLQLPOST Info accounts T-cd:FLQINFACC

Accounts with financial trans. "30 – 70" Comm. item fin. trans. FMFPO- FIVOR

FLQLPOS

RFLQ_XCB_MASTER

RFLQ_XCB_ACTACC

LP: Actual accounts

FLQACC_ACT

 SAP AG 2008

The main tasks of migration are: 1) Migrate master data 2) Migrate info accounts 3) Reconciliate actual accounts 4) Regenerate actual data

© SAP AG

FSC800

5-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 Master Data Comparison I “Commitment item”– TR-CBM master data Attributes: 1. Financial transaction 30: Revenue/expense 60: Receivables/payables 80: Bank subaccounts 90: Cash 2. Commitment item category 1. Balance sheet 2. Revenue 3. Expense

The commitment item is assigned to every G/L account.  SAP AG 2008

The commitment item has two important attributes: • 1. Financial transaction • 2. Commitment item category If Cash Budget Management is activated, all G/L accounts must be assigned to a commitment item.

© SAP AG

FSC800

5-5

SAP PORTUGAL | USO EXCLUSIVO | 2013 Master Data Comparison II "Liquidity item" – LP master data Attribute: "Name" and "Description" only

 SAP AG 2008

Only the "Name" and "Description" columns are required for the liquidity item master data.

© SAP AG

FSC800

5-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 Step 1: Master Data Migration I

TR-CBM Commitment item Commitment item FMFPO

Batch input session generated

①

②

Text FMFPOT

Execute RFLQ_XCB_MASTER LP Liquidity item Liquidity item FLQLPOS

④

③ Execute batch input session (T-cd;SM35)

Text FLQLPOST

 SAP AG 2008

①② RFLQ_XCB_MASTER reads the TR-CBM commitment item and generates a batch input session. ③④ The session is executed using transaction SM35 and the liquidity item is generated. Transaction FLQC1 is used to check the result.

© SAP AG

FSC800

5-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 Step 1: Master Data Migration II 1. Execute RFLQ_XCB_MASTER

(T-cd:FLQC1)

①

②

Batch input session generated

④ ③

Execute batch input session (T-cd;SM35)  SAP AG 2008

The migration process • ① Start RFLQ_XCB_MASTER • ② The master data can be checked here • ③ Execute session with SM35 • ④ Check the master data with FLQC1

© SAP AG

FSC800

5-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 Step 2a: Migration of Info Accounts I – RFLQ_XCB_INFACC

CBM G/L accounts with financial transaction "30 – 70" Fin. trans. Commitment item: Fin. trans. “30”-”70” FMFPO- FIVOR

Generate proposal list

①

②

RFLQ_XCB_INFACC

G/L account SKB1

LP Info accounts T-cd:FLQINFACC

Download list

④

LP: Info accounts FLQACC_INFO_APP

③ Upload local file to table FLQACC_INFO_APP with RFLQ_UPLOAD_INFACC

 SAP AG 2008

Step 2: "Migration of info accounts". The program steps in detail: • ①② RFLQ_XCB_INFACC generates a proposal list with the info accounts. Commitment items with category "30-70" should be included. • ③ A local file is generated • ④ RFLQ_UPLOAD_INFACC(T-cd; FLQUPINFAC) -> The local file is uploaded to table FLQACC_INFO_APP.

© SAP AG

FSC800

5-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 Step 2b: Migration of Info Accounts II – RFLQ_XCB_INFACC RFLQ_XCB_INFACC

①

②

List

Select G/L accounts with commitment item and transaction "30-70"

T-cd: FLQINFACC

Upload local file

④

Download list

RFLQ_UPLOAD_INFACC

③  SAP AG 2008

Process: • ①② Data can be checked in the list before it is downloaded • ③

Save the list locally

• ④

Data can be checked in FLQINFACC

© SAP AG

FSC800

5-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 Step 3: Comparing Actual (Cash) Accounts RFLQ_XCB_ACTACC TR-CBM

LP

G/L accounts with transaction "90" Commitment item FMFPO- FIVOR

Other actual accounts T-cd:FLQC4

Fin. trans. “90”

G/L account SKB1

RFLQ_XCB_ACTACC

LP: Other actual accounts

FLQACC_ACT

RFLQ_XCB_ACTACC

G/L account entry with transaction FLQC4

画

G/L account entry in table T012K

面

 SAP AG 2008

The program RFLQ_XCB_ACTACC generates a comparison list for actual accounts. Missing accounts must be entered manually (FLQC4).

© SAP AG

FSC800

5-11

SAP PORTUGAL | USO EXCLUSIVO | 2013 Step 4: Regenerating Cash Flows in LP I

①

(Check)

Master data and Customizing for Basis Complete LP Customizing Activate company codes FI

LP

FI documents

LP tables

②

FI doc BKPF

LP: Totals table

FLQSUM FI doc BSEG

RFLQ_REBUILD

LP: Line item

FLQITEMFI

③ Generation of cash flows with RFLQ_ASSIGN_REX (FLQAD)  SAP AG 2008

Generation of flow data: • ① Check LP Customizing • ② Update the data in LP • ③ Create flow data (cash flows) As an alternative to step 3, you have to copy the flow data using a report. To do so, use the program RFLQ_ASSIGN_EXIT with function module FLQ_STANDARD_ASSIGN_TRCB.

© SAP AG

FSC800

5-12

SAP PORTUGAL | USO EXCLUSIVO | 2013 Step 4: Regenerating Cash Flows in LP II RFLQ_REBUILD

FI data is updated in LP with RFLQ_REBUILD

①

②

③

Generate cash flows via RFLQ_ASSIGN_REX (FLQAD)

 SAP AG 2008

Process: • ①② A check can be carried out here to determine the number of documents updated in LP. • ③

© SAP AG

Actual data is generated using transaction FLQAD.

FSC800

5-13

SAP PORTUGAL | USO EXCLUSIVO | 2013 Summary Master data and Basis rules (steps 1-3): 1.RFLQ_XCB_MASTER – Generation of liquidity items from commitment items 2.RFLQ_XCB_INFACC –

Maintenance of info accounts from commitment items (30…70)

3.RFLQ_XCB_ACTACC – Comparison of TR- CBM actual accounts (90) with LP actual accounts The reports above generate master data and Basis rules (no queries) for the FLQAD assignment mechanism. Exceptions: taxes and cash discounts.

Cash flows (step 4): RFLQT_REBUILD: FI documents are updated in LP. Cash flows can then be generated for the liquidity items (FLQAD).

 SAP AG 2008

You must carry out two key activities: • Generate master data • 2. Generate flow data and assign the cash flows to the liquidity items.

© SAP AG

FSC800

5-14

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing in ERP: Summary

You are now able to: Understand the process of migrating from TR-CBM to SAP LP Name and use the relevant programs.

 SAP AG 2008

© SAP AG

FSC800

5-15

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

5-16

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Overview: Liquidity Planning and Cash Accounting

Contents: Overview of SAP NetWeaver Basic structures of SAP NetWeaver BI Reporting functions of SAP NetWeaver BI

 SAP AG 2008

© SAP AG

FSC800

6-1

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Overview of Liquidity Planning and Cash Accounting: Unit Objectives

At the conclusion of this unit, you will be able to: Provide an overview of SAP NetWeaver Explain the basic structures of SAP NetWeaver BI Explain the reporting functionsSAP NetWeaver BI

 SAP AG 2008

© SAP AG

FSC800

6-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Overview of Liquidity Planning and Cash Accounting: Business Scenario

Before you prepare and implement liquidity planning and cash accounting in BI, you want to obtain an overview of SAP NetWeaver BI.

 SAP AG 2008

© SAP AG

FSC800

6-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 The SAP NetWeaver Platform

SAP NetWeaver™ PEOPLE INTEGRATION Multi channel access

…

Collaboration

INFORMATION INTEGRATION Bus. Intelligence

Knowledge Mgmt

Master Data Mgmt PROCESS INTEGRATION Integration Broker

Business Process Mgmt

Life Cycle Mgmt

Composite Application Framework

Portal

APPLICATION PLATFORM J2EE

ABAP

DB and OS Abstraction

 SAP AG 2008

SAP NetWeaver provides an integration architecture for all business applications and processes in a modern company. This architecture integrates people, information, and processes within a framework, allowing step-by-step implementation of its functions. Business Intelligence is a basic component of the Information Integration layer of SAP NetWeaver. The SAP NetWeaver Portal is a component of the People Integration layer. These two components work closely together and offer the user comprehensive functions for analyses and Business Information Reporting. SAP NetWeaver 2004s is the mySAP Business Suite edition of SAP NetWeaver 2004. The following key areas are relevant for liquidity planning in most projects: • From Information Integration: Business Intelligence and BI Content • From People Integration: Portal • Application Platform

© SAP AG

FSC800

6-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 SAP NetWeaver IT Practices

Enterprise Service Architecture

DB and OS Abstraction

Consolidation

APPLICATION PLATFORM J2EE ABAP

Unified Life-Cycle Management

PROCESS INTEGRATION Integration Business Broker Process Mgmt

Custom Development

Knowledge Mgmt

Master Data Mgmt

End-to-End Process Integration

Bus. Intelligence

Data Unification

INFORMATION INTEGRATION

User Productivity Enablement

Collaboration

Life Cycle Mgmt

Composite Application Framework

Portal

Business Event Management

Multi channel access

Business Information Management

PEOPLE INTEGRATION

Application governance and Security

SAP NetWeaver™

 SAP AG 2008

Business Information Management refers to the management of all types of information (structured and unstructured), from integration to delivery, with the aim of creating transparency and making information available within and outside the company. Companies can implement IT practices in stages so that the most urgent IT problems can be solved first. For each of these IT practices, SAP ships a selection of IT scenarios, all of which can be easily implemented.

© SAP AG

FSC800

6-5

SAP PORTUGAL | USO EXCLUSIVO | 2013 SAP NetWeaver – IT Practices and Scenarios IT Scenarios

IT Practices User Productivity Enablement Data Unification Business Information Management Business Event Management End-to-End Process Integration

Running an Enterprise Portal

Enabling User Collaboration

Master Data Harmonization

Business Task Management

Master Data Consolidation

Enterprise Reporting, Query, and Analysis

Mobilizing Business Processes

Central Master Data Management

Business Planning and Analytical Services

Business Event Resolution Enabling Applicationto-Application Processes

Enterprise Knowledge Management

Enterprise Data Warehousing

Enterprise Data Warehousing

Business Task Management

Enabling Business-toBusiness Processes

Business Process Management

Enabling Platform Interoperability

Business Task Management

Custom Development

Developing, Configuring, and Adapting Applications

Enabling Platform Interoperability

Unified Life-Cycle Management

Software Life-Cycle Management

SAP NetWeaver Operations

Application Governance & Security

Authentication and Single Sign-On

Integrated User and Access Management

Consolidation

Enabling Platform Interoperability

SAP NetWeaver Operations

Enterprise Service Architecture – Design & Deployment

Master Data Consolidation

Enterprise Knowledge Management

Enabling Enterprise Services

 SAP AG 2008

The IT practice of Business Information Management is divided into three IT scenarios. • Enterprise Reporting, Query, and Analysis • Business Planning and Analytical Services • Enterprise Data Warehousing These IT scenarios describe how companies can use the functions of SAP NetWeaver to complete tasks in the IT practice of Business Information Management. Each IT scenario covers everything that companies require to carry out the Discovery, Evaluation, Implementation, and Operations life cycle phases.

© SAP AG

FSC800

6-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Intelligence Scenarios in NetWeaver 2004s BI scenarios in SAP NetWeaver 2004s Enterprise Reporting, Query, and Analysis Stronger focus on user productivity Formatted reporting Intuitive ad-hoc analysis Enhanced Excel integration Model-based BI applications Business Planning and Analytical Services Business Planning – integrated in BI Platform and Suite Enterprise Data Warehousing Increased performance due to BI Accelerator Flexibility through improved data modeling functions Data transfer process Real-time data acquisition Web-based Administrator Cockpit

 SAP AG 2008

SAP NetWeaver BI creates a basis for reporting and analytics in business applications. It provides information to multiple end users, integrates planning in user interfaces and services, and strengthens its role as a strategic data warehouse platform. The IT scenarios focus directly on these goals: • Enterprise Reporting, Query, and Analysis

Increase availability

• Business Planning and Analytical Services

Integrate planning

• EDW

© SAP AG

Strategic data warehouse platform

FSC800

6-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 Requirements for a Data Warehouse System

Source system 1

Company code Source system 2

Source system 3

Germany Austria USA China

Data warehouse

Free liquidity EUR 23,234.98 EUR 33,234.00 EUR 34,324.56 EUR 22,314.36

Database

 SAP AG 2008

The main task of a data warehouse system is to provide information from different data sources. This data and information and resulting reports enable the successful execution of business processes in a company. This type of system can be used by all employees in the company (managers, heads of department, and all other employees). The information is formatted in different ways and made available in the form of personalized reports, freely-definable queries, and predefined reports. On the basis of these reports and analysis options, the information recipient can analyze the data to check for discrepancies or irregularities. A data warehouse can be used, for example, to carry out the following tasks in liquidity planning and cash accounting: • Integrate data from different sources for uniform liquidity analysis • Monitor cash flows from different subsidiaries • Analyze liquidity bottlenecks or surplus funds • Facilitate decisions on planning An actual query could be phrased as follows: How do you see the group's liquidity situation in three weeks? Will additional liquid funds have to be made available?

© SAP AG

FSC800

6-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 SAP Business Intelligence

Source systems

SAP ERP

Business Content OLAP engine Automated warehouse Standardized structures

Non-SAP SAP BI

Business Explorer

XML

Database Database

 SAP AG 2008

SAP BI enables you to evaluate data from both operative SAP applications and any other business applications. You can also extract and analyze data from external sources such as databases, online services, and the Internet. The system for core areas and processes (data retention, loading processes, reporting) preconfigured using Business Content provides multiple views of related processes across the company.

© SAP AG

FSC800

6-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 SAP BI Architecture Enterprise Portal Visual Composer BI Kit

KM

Business Explorer Suite (BEx) Information Broadcasting BEx Web

BI Pattern Web Application Designer

Web Analyzer

BEx Analyzer Report Designer

MS Excel Add-In

BI Consumer Services

BEx Query Designer

BI Platform

Analytic Engine

Planning Modeler

Meta Data Mgr

UDI SAP JDBC XMLA ODBO query

Data Warehouse

DB Connect

BAPI

Service API

File

XML/A

 SAP AG 2008

SAP BI architecture enables you to procure, transform, save, analyze, distribute, and access data from SAP sources and external sources. The Business Explorer Suite (BEx) includes a number of tools that enable you to access and analyze data.

© SAP AG

FSC800

6-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Overview of Liquidity Planning and Cash Accounting: Summary

You are now able to: Provide an overview of SAP NetWeaver Explain the basic structures of SAP NetWeaver BI Explain the reporting functionsSAP NetWeaver BI

 SAP AG 2008

© SAP AG

FSC800

6-11

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

6-12

SAP PORTUGAL | USO EXCLUSIVO | 2013 Exercises Unit:

BI Overview: Liquidity Planning and Cash Accounting - Optional

At the conclusion of these exercises you will be able to: • Provide an overview of SAP NetWeaver • Explain the basic structures of SAP NetWeaver BI • Explain the reporting functions of SAP NetWeaver BI • Before you prepare and implement liquidity planning and cash accounting in BI, you want to familiarize yourself with the BI architecture.

1-1 Name the key areas of SAP NetWeaver (optional).

1-2 Name a few tasks relating to liquidity planning and cash accounting that can be carried out using a data warehouse (optional).

1-3 Which reporting options are offered by SAP BI Reporting (optional)?

A You can display analyses in Microsoft Excel using BEx Analyzer. B You can display analyses on the Internet using the Enterprise Portal and Web Analyzer. C You can create a Web report from a BEx Analyzer report. D You can convert a Microsoft Excel table query to a BI report.

© SAP AG

FSC800

6-13

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-4 Which source system types can be connected to an SAP BI system (optional)?

A XML-based data sources B SAP systems C Databases D Fax machines

© SAP AG

FSC800

6-14

SAP PORTUGAL | USO EXCLUSIVO | 2013 Solutions Unit:

BI Overview: Liquidity Planning and Cash Accounting – Optional

1-1 Name the key areas of SAP NetWeaver. SAP NetWeaver contains the following key areas: Key areas of People Integration: Multi-Channel Access Portal Collaboration Key areas of Information Integration: Business Intelligencehttp://help.sap.com/saphelp_nw70/helpdata/de/37/5fb13cd0500255e10000 000a114084/frameset.htm

BI Content Knowledge Management Master Data Management Key areas of Process Integration: Integration Broker Business Process Management Key areas of Application Platform: Cross-Platform Services ABAP Engine Virtual Machine Controller Java Engine Business Services

© SAP AG

FSC800

6-15

SAP PORTUGAL | USO EXCLUSIVO | 2013 Key areas of Solution Life Cycle Management: Licensing Solution Monitoring Statistics Application Log System Management Software Change Management SAP Solution Manager SAP NetWeaver Administrator Customizing -

Composite Application Framework-

-

Security

-

SAP Knowledge Warehouse

1-2 Name a few tasks relating to liquidity planning and cash accounting that can be carried out using a data warehouse (optional). -

Integrate data from different sources for uniform liquidity analysis

-

Monitor cash flows from different subsidiaries

-

Analyze liquidity bottlenecks or surplus funds

-

Facilitate decisions on planning

1-3 Which reporting options are offered by SAP BI Reporting? A You can display analyses in Microsoft Excel using BEx Analyzer. B You can display analyses on the Internet using the Enterprise Portal and Web Analyzer. C You can create a Web report from a BEx Analyzer report. D You can convert a Microsoft Excel table query to a BI report. 1-4 Which source system types can be connected to an SAP BI system? A XML-based data sources B SAP systems C Databases D Fax machines

© SAP AG

FSC800

6-16

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Content, Modeling, and Extraction

Contents: Business Content for liquidity planning and cash accounting The data model for liquidity planning and cash accounting Data extraction for liquidity planning and cash accounting

 SAP AG 2008

© SAP AG

FSC800

7-1

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Content, Modeling, and Extraction: Unit Objectives

At the conclusion of this unit, you will be able to: Explain the Business Content for liquidity planning and cash accounting in BI and the R/3 Plug-In Explain the data model for liquidity planning and cash accounting in BI Explain the extraction of data from R/3 to BI

 SAP AG 2008

© SAP AG

FSC800

7-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Content, Modeling, and Extraction: Business Scenario

You want to check whether Business Content for liquidity planning and cash accounting covers the requirements of your project. To do so, you must familiarize yourself with the Business Content in BI. You must also familiarize yourself with the data model for liquidity planning and cash accounting and with data extraction.

 SAP AG 2008

© SAP AG

FSC800

7-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: InfoObjects

Assignment via the DWB

Characteristics

Key figures

Company Code Liquidity Item Company Country Key Credit Control Area Fiscal Year Variant Chart of Accounts

Amount Amount - Actual … … ... … ...

If a characteristic (Chart of Accounts) is assigned to another characteristic (Company Code), the "Chart of Accounts" characteristic is identified as an attribute of the "Company Code".

A data record (posting record) consists of a combination of characteristics and key figures Company Code 1000

Business Area

Liquidity Item

…

310000

...

4100

Amount Actual 1000

 SAP AG 2008

Business analysis objects are known as InfoObjects in BI. They are divided into characteristics (such as customers), key figures (such as sales), units (such as currency or units of measure), time characteristics (such as fiscal year), and technical characteristics (such as change request number). InfoObjects… Can be uniquely identified by their technical names. Contain technical and business-related information. Allow information to be modeled. Are used to define reports and evaluate master data and flow data. Attributes can have different properties/uses: For display only For navigation in Reporting With or without time dependency

© SAP AG

FSC800

7-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 Uses of InfoObjects Structures (Communication/transfer structures)

PSA tables

InfoCubes

InfoObjects

ODS objects

Attributes

Texts

Hierarchies

 SAP AG 2008

InfoObjects can also be used in transformations.

© SAP AG

FSC800

7-5

SAP PORTUGAL | USO EXCLUSIVO | 2013 Overview: InfoObjects (Without Attributes) Characteristics

Company Code Company Code of Partner Line Item Category Creation Date Liquidity Item Business Area Company Country Key

0COMP_CODE 0PCOMP_CODE 0LQTYPE 0SEM_CRDATE 0LQPOSIT 0BUS_AREA 0COMPANY 0COUNTRY

Time Characteristics

Calendar Year Calendar Year/Month Calendar Year/Week Calendar Day

0CALYEAR 0CALMONTH 0CALWEEK 0CALDAY

Unit

Currency Key Local Currency

0CURRENCY 0LOC_CURRCY

Key Figures

Amount Amount – Actual Amount in Local Currency

0AMOUNT 0AMOUNT_A 0VALUE_LC

 SAP AG 2008

Special features of the characteristics PCOMP_CODE = Paying company code, not partner company code 0SEM_CRDATE = Date of extraction 0LQPOSIT = Reference characteristic for 0MEASURE key figure Not every characteristic is used in every InfoProvider involved Special features of modeling 0AMOUNT and 0AMOUNT_A distinguish between plan and actual data With regard to the "Creation Date" characteristic, see the following SAP Note: https://service.sap.com/sap/support/notes/865731 The line item category (0LYTYPE) assigns the individual liquidity item to an origin type. Possible values (keys and language-dependent long texts): B Bank Statement Item in FI F

Other Actual Document in FI

M Manual Correction A Opening Balance

© SAP AG

FSC800

7-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 Overview: Attributes

Company code attributes Chart of Accounts Credit Control Area Fiscal Year Variant Source System Source System ID Open Fiscal Year Open Fiscal Year Period Open Posting Period Posting to Previous0RETROPOST

0CHRT_ACCTS 0C_CTR_AREA 0FISCVARNT 0LOGSYS 0SOURSYSTEM 0OFYEAR 0OFPER 0OFPER3

Liquidity item attributes (basic characteristic 0MEASURE) FS Item Type Reverse +/- Sign

0SEM_POSCAT 0SIGN_REV

 SAP AG 2008

Some InfoObjects have multiple uses within a scenario. This means, for example, that the source system is also used as an attribute for the chart of accounts. These multiple uses are not listed here.

© SAP AG

FSC800

7-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 Maintenance: InfoObjects – "General" Tab Page 0COMP_CODE Company Code Company Code New

Characteristic Long Description Short Description Version Object Status General

Not saved

Inactive, not executable BEx

Master Data/Texts

Length

Compounding

Attribute Only

Data Element Data Type

Attribute

Hierarchy

CHAR - Character String 4

Person Respons. Content Release

Convers. Rout. SID table

Characteristic Is Document Property Last Change

Transfer Routine

By

Transfer Routine Exists

On

 SAP AG 2008

When an InfoObject is generated, decisions about the InfoObject characteristics are made on a series of tab pages. These settings greatly influence what the InfoObject can do and how it can be used in BI. These settings form the metadata for the InfoObjects and are stored in the Metadata Repository.

© SAP AG

FSC800

7-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 Maintenance: InfoObjects – "Master Data/Texts" Tab Page 0COMP_CODE Company Code Company Code New

Characteristic Long Description Short Description Version Object Status General

Not saved

Inactive, not executable BEx

With Master Data

Master Data/Texts

Hierarchy

Attributes

Attributes

Compounding

With Texts

View of MstrDtaTbls

Text Table

Master Data Tab.

Short Text Exists

MasDataTab. timDep.

Medium Length Text Exists

SIDTab timeDepAttr.

Long Text Exists Texts Language Dependent Texts Are Time-Dep.

 SAP AG 2008

When an InfoObject is generated, decisions about the InfoObject characteristics are made on a series of tab pages. These settings greatly influence what the InfoObject can do and how it can be used in BI. These settings form the metadata for the InfoObjects and are stored in the Metadata Repository.

© SAP AG

FSC800

7-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 Maintenance: InfoObjects – "Hierarchy" Tab Page 0COMP_CODE Company Code Company Code New

Characteristic Long Description Short Description Version Object Status General

Not saved

- Display - Change ...

Inactive, not executable BEx

Master Data/Texts

Hierarchy

With Hierarchies

Attribute

Compounding

Maintain Hierarchies

Hierarchies, Version-Dependent

Hierarchy Table

Hierarchy Not Time-Dependent

Hierarchy SID Table

Entire Hierarchy Is Time-Dependent Time-Dependent Hierarchy Structure Intervals Permitted in Hierarchy

SID Hierarchy Struc. HierInterval Table

Reverse +/- Sign for Nodes

 SAP AG 2008

When an InfoObject is generated, decisions about the InfoObject characteristics are made on a series of tab pages. These settings greatly influence what the InfoObject can do and how it can be used in BI. These settings form the metadata for the InfoObjects and are stored in the Metadata Repository.

© SAP AG

FSC800

7-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 Maintenance: InfoObjects – "Attribute" Tab Page Characteristic Long Description Short Description Version Object Status General

0COMP_CODE Company Code Company Code New

Not saved

Inactive, not executable BEx

Master Data/Texts

Display/Navigation attributes

Hierarchy Time dependency

Attribute

Long Description

Ty.

0COMPANY

Company

NAV

0COUNTRY

Business Area

NAV

0CURRENCY

Currency Key

DIS

0CHRT_ACCTS

Profit Center

DIS

0C_CTR_AREA

Credit Control Area

Attribute

Compounding

Navigation attributes on/off

Ti...

Nav...

DIS

 SAP AG 2008

When an InfoObject is generated, decisions about the InfoObject characteristics are made on a series of tab pages. These settings greatly influence what the InfoObject can do and how it can be used in BI. These settings form the metadata for the InfoObjects and are stored in the Metadata Repository.

© SAP AG

FSC800

7-11

SAP PORTUGAL | USO EXCLUSIVO | 2013 Example: "Liquidity Item" InfoObject

Master data tables for the "Liquidity Item" characteristic Master data table

Text table

Liquidity item

Liquidity item

FS item type Reverse +/- sign

Short text Medium length text Long text

SID table

Hierarchy tables

Liquidity item SID Liquidity item

 SAP AG 2008

Identical to the 0MEASURE characteristic since the 0LQPOSIT liquidity item is a reference characteristic.

© SAP AG

FSC800

7-12

SAP PORTUGAL | USO EXCLUSIVO | 2013 Overview: Key Figures Type: Amount / CURR Cumulative values with SUM aggregation No exception aggregation Amount 0AMOUNT

Currency Key 0CURRENCY

$

Amount – Actual 0AMOUNT_A

Currency Key 0CURRENCY

$

Amount in Local Currency 0VALUE_LC

Local Currency 0LOC_CURRCY

$

 SAP AG 2008

Not provided in the standard system: third currency (group currency). However, the data flow can easily be extended to include this key figure.

© SAP AG

FSC800

7-13

SAP PORTUGAL | USO EXCLUSIVO | 2013 Maintenance: InfoObjects – "Type/Unit" Tab Page 0AMOUNT_A Amount - Actual Amount - Actual New

Key Figure Long Description Short Description Version Object Status

Not saved

Inactive, not executable Aggregation

Type/Unit

Additional Properties

Type/Data Type Amount

Number

Date

Quantity

Integer

Time

Data Type

CURR – Currency field, stored as DEC

Currency/Unit of Measure

EUR, GBP, ...

Fixed Currency

KG, %, ...

Fixed Unit of Meas. Unit/Currency

0CURRENCY

Units InfoObject

Currency Key

 SAP AG 2008

This tab page is available only for key figure InfoObjects. When an InfoObject is generated, decisions about the InfoObject characteristics are made on a series of tab pages. These settings greatly influence what the InfoObject can do and how it can be used in BI. These settings form the metadata for the InfoObjects and are stored in the Metadata Repository.

© SAP AG

FSC800

7-14

SAP PORTUGAL | USO EXCLUSIVO | 2013 Maintenance: InfoObjects – "Aggregation" Tab Page 0AMOUNT_A Amount - Actual Amount - Actual New

Key Figure Long Description Short Description Version Object Status Type/Unit

Not saved

Inactive, not executable Aggregation

Additional Properties

Aggregation

SUM

Exception Aggregat.

SUM Summation

Agg. Referen. Char. Cumulative Val NCum. Value with NCum. Value Change Non-Cum. Value Change NCum. Value with In- and OutFlow Inflow Outflow

Maximum Minimum Last value First value Maximum Minimum ...

Cumulative value

Cumulative values

 SAP AG 2008

This tab page is available only for key figure InfoObjects.

© SAP AG

FSC800

7-15

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: Folders in BI − InfoObjects

InfoObjects Customer Relationship Management Cross- Application Performance Sales SAP ERP Sales Analysis SAP ERP Sales Analysis Sales Analysis: Characteristics Sales Analysis: Key Figures Delivered Actual Quantity InfoAreas are folders in Actual Goods Issue which InfoObject catalogs and InfoProviders are An InfoObject may appear organized.* in more than one catalog.

InfoObject catalogs are folders in which either key figures or characteristics are stored.

* Not shown on this slide  SAP AG 2008

© SAP AG

FSC800

7-16

SAP PORTUGAL | USO EXCLUSIVO | 2013 Overview: InfoObject Catalogs 0TRLP_CHA01

TR-LP: Characteristics

Liquidity Item

0LQPOSIT

Company Code

0COMP_CODE

Partner Company Code

0PCOMP_CODE

Line Item Type

0LQTYPE

Creation Date

0SEM_CRDATE

0TRLP_KYF01

TR-LP: Key Figures

Amount – Actual 0AMOUNT_A

 SAP AG 2008

The other InfoObjects used are assigned to different InfoObject catalogs. If required, also assign these InfoObjects to this InfoObject catalog. The InfoObjects are stored in the following InfoArea Financials Management and Controlling 0FMCO Treasury 0TR Liquidity Planning 0TRLP InfoObjects do not have to be organized using InfoObject catalogs. However, this is recommended for overview and authorization purposes. Unassigned InfoObjects are automatically stored in the following InfoObject catalogs in the InfoArea Unassigned nodes NODESNOTCONNECTED Unassigned units

0UNINNOTASSIGNED

Unassigned key figures 0KYFNOTASSIGNED Unassigned characteristics 0CHANOTASSIGNED Unassigned time characteristics 0TIMNOTASSIGNED

© SAP AG

FSC800

7-17

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: InfoProvider

Master data

ODS object

MultiProvider

InfoProvider interface

Standard InfoCube

No data target

Data target

InfoProvider

Business Explorer

OLAP engine

InfoSet Virtual InfoCubes

 SAP AG 2008

An object that can be evaluated via a query is known as an InfoProvider. Data targets are InfoProviders that store data persistently.

© SAP AG

FSC800

7-18

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: InfoCube InfoCube with the transaction data (key figures)

Master data for "Sold-To Party" characteristic

Attributes

Fact table 11

3

Sales 24 ..................

Becker Inc.

Berlin

Texts DIM 1

11 5 ..............

DIM 2

24

3

Short text

Long text

3 ... ..............

Hierarchies

Key relationships 3

Greatly simplified display of the "star schema" with the links to the master data

Parent node

Child node

 SAP AG 2008

© SAP AG

FSC800

7-19

SAP PORTUGAL | USO EXCLUSIVO | 2013 Data Model for Actual Data InfoCube

Non-time-based dimension 1

Non-time-based dimension 2

Company code Company code of partner Business area

Liquidity item Line item category

Fact table Amount - Actual Amount in local currency

Time-based dimension Creation date

Time Calendar Calendar Calendar Calendar

day year/month year/week year

Unit Currency key House currency

 SAP AG 2008

Technical name of the InfoCube: 0TRLP_C01

© SAP AG

FSC800

7-20

SAP PORTUGAL | USO EXCLUSIVO | 2013 Data Model for Plan Data InfoCube

Non-time-based dimension 1

Non-time-based dimension 2

Company code Company Country key

Liquidity item

Fact table

Calendar Calendar Calendar Calendar

Amount

Time-based dimension Creation date

Time day year/month year/week year

Unit Currency key

 SAP AG 2008

Technical name of the InfoCube: 0SEM_C12

© SAP AG

FSC800

7-21

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: MultiProvider

InfoProvider

MultiProvider

InfoCube

Master data

ODS object

InfoSet

 SAP AG 2008

Advantages of the MultiProvider Simplified design: The MultiProvider concept enables you to perform more detailed analyses without having to add data to new extremely large InfoCubes. You can set up more basic standard InfoCubes with smaller tables and less redundancy. Individual InfoCubes and DataStore objects can be partitioned separately. Performance improvement through parallel execution of subqueries. In SAP NetWeaver 2004s, additional aggregation levels can be added to the MultiProvider.

© SAP AG

FSC800

7-22

SAP PORTUGAL | USO EXCLUSIVO | 2013 MultiProvider Liquidity Planning: Plan/Actual Comparison

Liquidity Planning: Plan/Actual Comparison

Liquidity Planning: Plan Data Liquidity Planning: Actual Data SAP BI

 SAP AG 2008

Technical names: 0SEM_MC1 Liquidity Planning: Plan/Actual Comparison 0SEM_C12 Liquidity Planning: Plan Data 0TRLP_C01 Liquidity Planning: Actual Data

© SAP AG

FSC800

7-23

SAP PORTUGAL | USO EXCLUSIVO | 2013 Data Model for MultiProvider Plan/Actual Comparison

Non-time-based dimension 2 Non-time-based dimension 1

Liquidity item

Company code

Fact table Amount Amount - Actual

Time-based dimension Creation date

Time Calendar Calendar Calendar Calendar

day year/month year/week year

Unit Currency key

 SAP AG 2008

Technical name of the InfoCube: 0SEM_MC1

© SAP AG

FSC800

7-24

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: Folders in BI − InfoProvider Data Warehousing Workbench: Modeling

Modeling

An InfoProvider can exist in an InfoArea only.

InfoProvider

InfoProvider InfoObjects

Customer Relationship Management Billing Engine Billing Documents Billing Documents Billing Engine: Billing Documents

InfoSources DataSources Source Systems

InfoAreas are folders in which InfoProviders and InfoObject catalogs are organized.*

* InfoObject catalogs are not shown here.

 SAP AG 2008

The InfoProviders for liquidity planning and cash accounting are stored in different InfoAreas. The InfoCube Liquidity Planning: Actual Data 0TRLP_C01 is stored in the following InfoArea: Financials Management and Controlling 0FMCO Treasury 0TR Liquidity Planning 0TRLP The MultiProvider 0SEM_MC1 Liquidity Planning: Plan/Actual Comparison and the InfoCube 0SEM_C12 Liquidity Planning: Plan Data are stored in the following InfoArea: Strategic Enterprise Management 0SEM Business Planning and Simulation 0SEM_BPS Profit, Balance Sheet, and Cash Flow Statement Planning 0SEM_FSPL

© SAP AG

FSC800

7-25

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: Data Flow Access to information

(Architected) data marts Operational DataStore Data warehouse

Persistent Staging Area

DataSources

Any source  SAP AG 2008

DataSources are BI objects that are used to extract and format data from source systems. DataSources partition the data provided by a source system in self-contained business areas. A DataSource contains a quantity of logically-related fields that are arranged in a flat structure and contain data to be transferred to BI. There are four types of DataSource: DataSources for transaction data DataSources for master data DataSources for attributes DataSources for texts DataSources for hierarchies DataSources of the source system are edited in Customizing for the extractors. You can access Customizing via the context menu (secondary mousebutton) of the relevant source system in the source system tree of the Data Warehousing Workbench – Modeling. You can also maintain a DataSource directly from the DataSource overview for a source system by choosing "Display DataSource in Source System" from the context menu.

© SAP AG

FSC800

7-26

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: Data Flow in BW 3.x - Details Data targets

BI server

Option: Master data Direct InfoSource = No update rules required InfoSource

Update rules

Communication structure Mapping and transfer rules

DataSource flat file

DataSource (replica)

Transfer structure

Transfer structure

Transfer structure

DataSource file

PSA (optional)

DataSource (replica)

PSA

DataSource

Transfer structure

Transfer structure

Extract structure

Extract structure

File system

SAP system For example, FLQSUM

 SAP AG 2008

An InfoSource is a quantity of logically-related information that has been grouped together into one unit. InfoSources contain transaction data (stored in InfoCubes) and master data (attributes, texts, and hierarchies - stored in separate tables). InfoSources describe the quantity of all available data for a business transaction or type of business transaction (for example, Cost Center Accounting). Transfer structures support the transfer of data in a DataSource between a source system and the corresponding SAP BI system. The transfer structure transports the DataSource data from a source system to an SAP BI system and transfers it to the InfoSource using transfer rules. The communication structure is independent of the source system and is generated from the InfoSource. It is filled in compliance with the transfer rules from the transfer structure. The communication structure contains all fields in an InfoSource. This process for extracting and transferring cleansed data to the communication structure is known as "data staging".

© SAP AG

FSC800

7-27

SAP PORTUGAL | USO EXCLUSIVO | 2013 Example: Master Data & Company Code Texts BI

Company code Update rules InfoSource & communication structure

0COMP_CODE_ATTR_TEXT

Company code: attributes and texts (flexible updating)

Transfer structure & rules DataSource replica

DataSource

From company code for &logical system&

0COMP_CODE_TEXT

0COMP_CODE_TEXT

0COMP_CODE_ATTR

Company code

0COMP_CODE_ATTR

R/3 Company code

 SAP AG 2008

Since 0PCOMP_CODE (Company Code of Partner) is an InfoObject that refers to 0COMP_CODE, the master data and texts for 0PCOMP_CODE are identical to those for 0COMP_CODE. Attributes and texts from table T001 -> via view BIW_T001 Structure of InfoSource 0COMP_CODE_ATTR_TEXT

Source

0COMP_CODE

Company Code

Attributes and text (key)

0CHRT_ACCTS

Chart of Accounts

Attributes

0COMPANY

Company

Attributes

0COUNTRY

Country

Attributes

0CURRENCY

Currency

Attributes

0C_CTR_AREA

Credit Control Area

Attributes

0FISCVARNT

Fiscal Year Variant

Attributes

0LOGSYS

Source System

Attributes

0SOURSYSTEM

Source System ID

Attributes

0GN_PAR_SSY

Source System of Partner

Attributes

0TXTMD

Medium Description

Text

The texts are not language-dependent.

© SAP AG

FSC800

7-28

SAP PORTUGAL | USO EXCLUSIVO | 2013 Example: Master Data & Business Area Texts BI

Business area InfoSource for direct update of master data

Transfer structure & rules DataSource replica

DataSource

From company code for &logical system&

0BUS_AREA_TEXT

0BUS_AREA_TEXT

0BUS_AREA_ATTR

Business area

0BUS_AREA_ATTR

R/3 Business area

 SAP AG 2008

Business area attributes (no business context) 0SOURSYSTEM

Source system ID

0LOGSYS

Source system

Language-dependent medium length text Texts from table TGSBT -> via BIW_TGSBT view Attributes from table TGSB -> via BIW_TGSB view

© SAP AG

FSC800

7-29

SAP PORTUGAL | USO EXCLUSIVO | 2013 Example: Texts for Liquidity Item BI

0MEASURE InfoSource for direct update of master data Transfer structure & rules DataSource replica

From company for &logical system& ZLQPOS_TEXT

Company

R/3 DataSource

ZLQPOS_TEXT

Company

 SAP AG 2008

0MEASURE is the basic characteristic for liquidity items. No extractor exists in Business Content for the texts in BI. However, an extractor easily can be created in the form of a generic extractor to table FLQLPOST. Note: The liquidity item in the R/3 system uses two different long texts. The S_TEXT field does not fit in the "Medium Length Text" BI field, which means that information may be lost when data is transferred. For this reason, enter a maximum of 40 characters in the ERP system for the description of the liquidity item.

© SAP AG

FSC800

7-30

SAP PORTUGAL | USO EXCLUSIVO | 2013 Example: Transaction Data (Actual Data) BI

Liquidity Planning: Actual Data 0TRLP_C01 0TR_LP_1

Update rules InfoSource & communication structure

0TR_LP_1

Transfer structure & rules

Liquidity planning From liquidity planning for &logical system&

DataSource replica

0TR_LP_1

Liquidity planning R/3

DataSource

0TR_LP_1

Liquidity planning

 SAP AG 2008

Technical names: InfoCube 0TRLP_C01

Liquidity Planning: Actual Data

How the extractors function: read data from FLQSUM + derive the creation date from the current system date. Key fields of 0TR_LP_1 InfoSource 0COMP_CODE 0PCOMP_CODE 0LQPOSIT 0LQTYPE 0CALDAY 0CALMONTH 0CALWEEK 0CALYEAR 0CURRENCY 0SEM_CRDATE 0LOC_CURRCY 0BUS_AREA

Selection field in the DataSource

Company Code Company Code of Partner Liquidity Item Line Item Type Calendar Day Calendar Year/Month Calendar Year/Week Calendar Year Currency Creation Date Local Currency Business Area

X X X X X

X X X

Value fields of 0TR_LP_1 InfoSource 0AMOUNT 0AMOUNT_A 0VALUE_LC

© SAP AG

Amount Amount - Actual Amount in Local Currency

FSC800

7-31

SAP PORTUGAL | USO EXCLUSIVO | 2013 Example: Enhancement of DataSource 0TR_LP_1 The DataSource for transaction data can be extended to include additional fields.

3.

Customer exit for data extraction

DataSource

0TR_LP_1

+ new fields

2.

1.

R/3

Business area

FLQSUM

FLQGSBER_SUBST

 SAP AG 2008

When extracting transaction data, refer to the following SAP Notes: https://service.sap.com/sap/support/notes/746810 https://service.sap.com/sap/support/notes/763985 Enhancement procedure: Add fields to the DataSource (structure) as customer appends. When maintaining the DataSource, specify as "Only in Customer Exit". Activate the customer exit (enhancement RSAP0001, function exit EXIT_SAPLRSAP_001). Read the additional characteristics (such as "Project") using the substitution table (FLQSBER_SUBST).

© SAP AG

FSC800

7-32

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: Data Flow in BI 7.0 BW350

SAP NetWeaver Business Intelligence InfoProvider

5. DTP Execute the transformation in BI

3. InfoSource **

*

InfoSource Transformation

Data transfer process (DTP)

2. Transformation Transformation

DataSource/PSA 4. InfoPackage for loading data to BI Non-SAP system 1. DataSource

Info Spoke

InfoPackage

Open hub destination

Any target SAP XI

SAP NetWeaver BI

Any source

SAP ** optional

 SAP AG 2008

© SAP AG

FSC800

7-33

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: Transformation in BI 7.0 2. Transformation

Source fields

Transformation rules

Target fields

 SAP AG 2008

© SAP AG

FSC800

7-34

SAP PORTUGAL | USO EXCLUSIVO | 2013 Terminology: BI Content Objects

Excel workbooks

Data mining model BW380

Key figure DataStore object

Transformations Analysis processes BW380 InfoArea Web (BW306) templates

Queries

InfoObject catalog

Characteristic InfoObject Role

Data transfer process

Aggregation level BW370

Broadcast settings BW305/306 and 360

Cubes

BEx reports (BW306)  SAP AG 2008

Business Content contains a number of objects that simplify the implementation of BI and accelerate the setup of effective reporting. These objects are grouped together for optimal usage: For all areas of your company and many industries, roles exist that provide users with the specific reports and applications they require to complete their tasks. In the future, cross-component applications (analytical applications) will be available that provide specific access to related information about a process. They not only enable these processes to be analyzed, but also allow direct actions and responses in the systems that supply the data. Analytical applications are used, for example, in Supply Chain Management (supplier and catalog analysis, manufacturing analysis, and so on), Customer Relationship Management (e-business analysis, market exploration, and so on), or company analyses such as performance analysis, payment analysis, and human capital analysis.

© SAP AG

FSC800

7-35

SAP PORTUGAL | USO EXCLUSIVO | 2013 Example: Installing BI Content Collected

Delete

Modeling Administration Reporting Agent Transport Connection Documents BI Content

Object Changeability Grouping

Roles

Technical Name

Install

Collected objects Sales Success (Products and S. Web Template Workbook Product Profitability Analysis Distribution Channel Analysis Top Customers Sales Volume/Costs Analysis Returns: quantities + values Plan/Actual/Deviation Curren Product Analysis Incoming Orders Analysis Order Inbound/Sales:

InfoProviders by InfoAreas InfoObjects by InfoAreas InfoSources by Application Comp Roles Object Types Objects in BW Patch Transport Request Packages

Sales Success

Translation Metadata Repository  SAP AG 2008

Version meaning D(elivery)

BI Content version

A(ctive)

Active version

M(odified)

Modified version

Procedure 1. Select the object view in the left-hand navigation window. 2. Select objects to be activated in the middle window Liquidity Planning

for example, SAP_BW_SEM_LP

role3. Define the grouping -> Specify the number of dependent objects. 4. Simulate installation if required. 5. Install Business Content. Business Content for liquidity planning and cash accounting can be activated via the SAP_BW_SEM_LP Liquidity Planning role. Grouping In Data Flow Before.

© SAP AG

FSC800

7-36

SAP PORTUGAL | USO EXCLUSIVO | 2013 Options for Using BI Content •

Use BI Content without modifications Rarely; applies in approx. 10 % of cases only

•

Change shipped BI Content Compared to other SAP products, this versioning allows both a customer version and an SAP version of the same object; these versions can differ.

•

Copy BI Content In this option, BI Content is used as a starting point (template). New objects are created in the customer namespace and are no longer linked with BI Content.

 SAP AG 2008

Changes to active BI Content are not "modifications".

© SAP AG

FSC800

7-37

SAP PORTUGAL | USO EXCLUSIVO | 2013 Advantages of BI Content Efficient data model

Usage in the prototyping phase accelerates the process for defining requirements

SAP BI project: Success! Problem-free enhancement and copying

Integrated technical and business objects offer an end-to-end solution from SAP source systems

Reliable tools for determination and activation

 SAP AG 2008

The shipping of BI Content is very useful for projects. The Content shipped provides a good basis for determining customer-specific requirements.

© SAP AG

FSC800

7-38

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Content, Modeling, and Extraction: Summary

You are now able to: Explain the Business Content for liquidity planning and cash accounting in BI and the R/3 Plug-In Explain the data model for liquidity planning and cash accounting in BI Explain the extraction of data from R/3 to BI

 SAP AG 2008

© SAP AG

FSC800

7-39

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

7-40

SAP PORTUGAL | USO EXCLUSIVO | 2013 Exercises Unit:

Business Content, Modeling, and Extraction

At the conclusion of these exercises, you will be able to: • Explain the Business Content for liquidity planning and cash accounting in BI and the R/3 Plug-In • Explain the data model of liquidity planning and cash accounting in BI • Explain the extraction of data from R/3 to BI • You want to check whether the Business Content for liquidity planning and cash accounting covers the requirements of your project. To do so, you must familiarize yourself with Business Content in BI. • You must also familiarize yourself with the data model for liquidity planning and cash accounting and with data extraction.

1-1 Which of the following statements about InfoObjects are correct?

A Characteristics and key figures are identified as InfoObjects. B An InfoObject can also be an InfoProvider. C All attributes are characteristic or key figure InfoObjects. D All characteristic InfoObjects are assigned attribute, text, and hierarchy data.

1-2 What are the most important aspects of an InfoCube structure?

A An InfoCube contains a maximum of 16 fact tables. B An InfoCube has a primary fact table and a maximum of 16 dimension tables. C A dimension table is made up of characteristics and key figures. D A dimension table is made up of characteristics and attributes. E A dimension table contains key links to attributes.

© SAP AG

FSC800

7-41

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-3 Name the InfoProvider involved in Business Content for cash accounting and liquidity planning.

1-4 Which characteristics and key figures are included in Business Content for liquidity planning?

1-5 Create an InfoArea for your cash accounting and liquidity planning. Create this InfoArea in the InfoArea tree under the existing InfoArea: “T_FSC800” The InfoArea must have the technical name: T_FSC800_GR## (replace ## with your group number) Enter the following description of the InfoArea: “FSC800 InfoArea Group ##”

1-6 Create the InfoProvider required for cash accounting and liquidity planning in your InfoArea. Create a plan data InfoCube with the technical name: TFSCGR##P (replace ## with your group number) Enter the following description of the InfoCube: “FSC800 Plan Data InfoCube Group ##” Select the following InfoCube as a template: “0SEM_C12Liquidity Planning: Plan Data”

© SAP AG

FSC800

7-42

SAP PORTUGAL | USO EXCLUSIVO | 2013 Do not forget to select “Real Time” in the “InfoProvider Type” section. Adjust the InfoProvider so that it displays the following structure: Non-Time-Based Dimension 1 o Country Key 0COUNTRY o Company Code 0COMP_CODE o Company 0COMPANY Non-Time-Based Dimension 2 o Liquidity Item 0LQPOSIT Time-Based Dimension o Creation Date 0SEM_CRDATE Project o Project Definition 0PROJECT Time o Calendar Year 0CALYEAR o Calendar Year/Week 0CALWEEK o Calendar Year/Month 0CALMONTH o Calendar Day 0CALDAY Unit o Currency Key 0CURRENCY Key Figures o Amount 0AMOUNT Now create an InfoCube for the actual data. The InfoCube must have the technical name: TFSCGR##I (replace ## with your group number) Enter the following description of the InfoCube: “FSC800 Actual Data InfoCube Group ##” Select the following InfoCube as a template: “0TRLP_C01 Liquidity Planning: Actual Data” Note that the “Real Time” checkbox must not be selected. Adjust the InfoProvider so that it displays the following structure:

© SAP AG

FSC800

7-43

SAP PORTUGAL | USO EXCLUSIVO | 2013 Non-Time-Based Dimension 1 o Company Code 0COMP_CODE o Company Code of Partner 0PCOMP_CODE Non-Time-Based Dimension 2 o Line Item Category 0LQTYPE o Liquidity Item 0LQPOSIT Time-Based Dimension o Creation Date 0SEM_CRDATE Project o Project Definition 0PROJECT Time o Calendar Year 0CALYEAR o Calendar Year/Week 0CALWEEK o Calendar Year/Month 0CALMONTH o Calendar Day 0CALDAY Unit o Local Currency 0LOC_CURRCY o Currency Key 0CURRENCY Key Figures o Amount in Local Currency 0VALUE_LC o Amount – Actual 0AMOUNT_A 1-7 Now create a new MultiProvider for your cash accounting and liquidity planning. The MultiProvider must have the technical name: TFSCGR##M (replace ## with your group number) Enter the following description of the MultiProvider: “FSC800 MultiProvider Group ##” Select the following MultiProvider as a template: “0SEM_MC1 Liquidity Planning: Plan/Actual Comparison” Remove the two Business Content InfoCubes from the MultiProvider and insert the new InfoProviders. Adjust the MultiProvider so that it displays the following structure: © SAP AG

FSC800

7-44

SAP PORTUGAL | USO EXCLUSIVO | 2013 Non-Time-Based Dimension 1 o Company Code 0COMP_CODE Non-Time-Based Dimension 2 o Liquidity Item 0LQPOSIT Time-Based Dimension o Creation Date 0SEM_CRDATE Project o Project Definition 0PROJECT Time o Calendar Year 0CALYEAR o Calendar Year/Week 0CALWEEK o Calendar Year/Month 0CALMONTH o Calendar Day 0CALDAY Unit o Currency Key 0CURRENCY Key Figures o Amount 0AMOUNT o Amount – Actual 0AMOUNT_A

1-8 Create a new application component and InfoSource in BI for your group (optional). The application component must have the technical name: T_FSC800_GR## (replace ## with your group number). Enter the following description of the application component: “FSC800 Application Component BW Group ##” Create it under the application component: “ZT_FSC800” Then create the new InfoSource with the technical name:

© SAP AG

FSC800

7-45

SAP PORTUGAL | USO EXCLUSIVO | 2013 T_FSC800_GR## (replace ## with your group number) Enter the following description of the InfoSource: “FSC800 InfoSource BW Group ##” Use the InfoSource “0TR_LP_1” as a template. Remove “Business Area” from the InfoSource and insert “Project Definition”.

1-9 Create a transformation for updating the data from your new InfoSource in your actual data InfoCube. When doing so, use the individual rules proposed by the system (optional).

1-10 Create a transformation for updating the data from your DataSource in your InfoSource (optional). The DataSource has the technical name: Z_FSC800_GR## (replace ## with your group number) Select T90CLNT090 as the source system for the DataSource. Link the following DataSource fields with the corresponding target fields. DataSource Field

InfoSource InfoObject

BUKRS

0COMP_COD E

Comment

GSBER LQPOS

0LQPOSI T

ZBUKR

0PCOMP_COD E

LQDAY

0CALDA Y

DISP_PERI 2 DISP_PERIO DISP_YEAR

0CALWEE K

Ignore the warning message

0CALMONT H

Ignore the warning message

0CALYEA R

Ignore the warning message

DATA_OF

0SEM_CRDAT E

TWAER

0CURRENC Y

WRBTR

0AMOUNT_A

WAERS

0LOC_CURRC Y

DMBTR

0VALUE_L C

KWAER KWBTR

© SAP AG

FSC800

7-46

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-11 Create an InfoPackage to load the data from the R/3 DataSource to the PSA of BI. Then load the data for your company code to BI and view the data in the PSA (optional). Assign your InfoPackage the description: FSC800GR## Transaction Data (replace ## with your group number) Load data for your company code only: AC## (replace ## with your group number) To transfer the data to BI, start the loading process. Monitor the loading process and view the data in the PSA.

1-12 Create a data transfer process to load the data from the DataSource to your InfoCube. Then load the data for your company code to the InfoCube for your group (optional). Create the DTP via the context menu for your actual data InfoCube: “Liquidity Planning: Actual Data TFSCGR00I” As the source for the DTP, choose your DataSource: Z_FSC800_GR## FSC800GR## Transaction Data (replace ## with your group number) On the “Extraction” tab page, select “Only Get Delta Once” and then execute the DTP. Monitor the process in the “Request Monitor”.

© SAP AG

FSC800

7-47

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-13 Analyze the loaded data in your InfoCube (optional). To do so, select the InfoCube for the actual data: TFSCGR##I “Liquidity Planning: Actual Data” with the secondary mousebutton and choose “Display Data”.

© SAP AG

FSC800

7-48

SAP PORTUGAL | USO EXCLUSIVO | 2013 Solutions Unit:

Business Content, Modeling, and Extraction

1-1 Which of the following statements about InfoObjects are correct?

A

Characteristics and key figures are identified as InfoObjects.

B

An InfoObject can also be an InfoProvider.

C

All attributes are characteristic or key figure InfoObjects.

D

All characteristic InfoObjects are assigned attribute, text, and hierarchy data.

1-2 What are the most important aspects of an InfoCube structure?

A

An InfoCube contains a maximum of 16 fact tables.

B

An InfoCube has a primary fact table and a maximum of 16 dimension tables.

C

A dimension table is made up of characteristics and key figures.

D

A dimension table is made up of characteristics and attributes.

E

A dimension table contains key links to attributes.

1-3 Name the InfoProviders involved in Business Content for cash accounting and liquidity planning. 0SEM_MC1 Comparison

Liquidity Planning: Plan/Actual

0SEM_C12

Liquidity Planning: Plan Data

0TRLP_C01

Liquidity Planning: Actual Data

© SAP AG

FSC800

7-49

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-4 Which characteristics and key figures are included in Business Content for liquidity planning? Characteristics Company Code Company Code of Partner Line Item Category Creation Date Liquidity Item Business Area Company Country Key

0COMP_CODE 0PCOMP_CODE 0LQTYPE 0SEM_CRDATE 0LQPOSIT 0BUS_AREA 0COMPANY 0COUNTRY

Time Characteristics Calendar Year Calendar Year/Month Calendar Year/Week Calendar Day

0CALYEAR 0CALMONTH 0CALWEEK 0CALDAY

Unit Currency Key Local Currency

0CURRENCY 0LOC_CURRCY

Key Figures Amount Amount – Actual Amount in Local Currency

0AMOUNT 0AMOUNT_A 0VALUE_LC

Attributes for the Company Code Chart of Accounts Credit Control Area Fiscal Year Variant Source System Source System ID Open Fiscal Year Open Fiscal Year Per Open Posting Period Posting to Previous

0CHRT_ACCTS 0C_CTR_AREA 0FISCVARNT 0LOGSYS 0SOURSYSTEM 0OFYEAR 0OFPER 0OFPER3 0RETROPOST

Attributes for Liquidity Item (Basic Characteristic 0MEASURE) FS Item Type Reverse +/- Sign

© SAP AG

0SEM_POSCAT 0SIGN_REV

FSC800

7-50

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-5 Create an InfoArea for your cash accounting and liquidity planning. Call the Data Warehousing Workbench. For the Data Warehousing Workbench, use the SAP Easy Access Menu path: “Information Systems” “Business Information Warehouse” “Modeling” “Data Warehousing Workbench: Modeling” You can call the Data Warehousing Workbench with transaction RSA1. A “Documentation on Modeling Area” message is displayed. Select “Do Not Show This Question Again” and confirm your entry with “No”. Note: You can display the message again later in the Data Warehousing Workbench via the drop-down menu (Data Warehousing Workbench -> Documentation on Modeling). In the Data Warehousing Workbench, navigate to the InfoArea for this course in the InfoProvider tree. To do so, follow the path: “Modeling” “Data Warehouse Workbench: Modeling” “InfoProvider” “BW Training T_BW” “BW Customer Training T_BW_CUST” “T_FSC800T_FSC800” Select “T_FSC800” with the secondary mousebutton and choose “Create InfoArea” from the menu. On the following screen, enter the technical name of your InfoArea in the “InfoArea” field. The InfoArea must have the technical name: T_FSC800_GR## (replace ## with your group number) Enter the following description of the InfoArea: “FSC800 InfoArea Group ##” Confirm your entries.

© SAP AG

FSC800

7-51

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-6 Create the InfoProvider required for your cash accounting and liquidity planning. First, we want to create the standard InfoProvider required for our actual and plan data. We want to use Business Content as the basis for this and adapt it to our requirements. To do so, select your T_FSC800_GR## InfoArea with the secondary mousebutton and choose “Create InfoCube”. Enter the technical name of your InfoCube in the “InfoCube” field. The InfoCube must have the technical name: TFSCGR##P (replace ## with your group number) Enter the following description of the InfoCube: “FSC800 Plan Data InfoCube Group ##” Select the following InfoCube as a template: “0SEM_C12

Liquidity Planning: Plan Data”

Do not forget to indicate that this is a real-time standard InfoCube in the “InfoProvider Type” section, that is, the “Real Time” checkbox must be selected. Choose “Create” (F5). Since we do not require the “Business Area” and are interested in the “Project” additional account assignment instead, we want to remove the “Business Area” from our InfoProviders and insert “Project”. To edit the InfoCube, hide the Navigator (Shift + F11). First, add a new dimension to the InfoProvider. To do so, select the “Dimensions” folder with the secondary mousebutton and choose “Create New Dimensions”. Enter “Project” as the description. Confirm your entries by choosing “Continue” (green checkmark). To include the “Project” characteristic in the InfoCube, select the newly created dimension with the secondary mousebutton and choose “InfoObject Direct Input”. On the following screen, insert the “0PROJECT” (Project Definition) InfoObject in the first cell. Confirm your entries by choosing “Continue” (green checkmark).

© SAP AG

FSC800

7-52

SAP PORTUGAL | USO EXCLUSIVO | 2013 To remove the “Business Area” from the InfoCube, expand “Non-Time-Based Dimension 1” (TFSCGR00P1). Select the “Business Area” (0BUS_AREA) characteristic with the secondary mousebutton and choose “Cut”. Leave all other settings unchanged and save (Ctrl + S). Activate your entries (Ctrl + F3). The InfoCube is now created in the database. We now want to create the InfoCube for the actual data. To do so, end the current process by choosing “Cancel” (F12). If a warning message is displayed, confirm with “No”. Then select your T_FSC800_GR## InfoArea with the secondary mousebutton and choose “Create InfoCube”. Enter the technical name of your InfoCube in the “InfoCube” field. The InfoCube must have the technical name: TFSCGR##I (replace ## with your group number) Enter the following description of the InfoCube: “FSC800 Actual Data InfoCube Group ##”

Select the following InfoCube as a template: “0TRLP_C01 Liquidity Planning: Actual Data”

The “Real Time” checkbox must NOT be selected. Choose “Create” (F5). Insert a new dimension, include the InfoObject for the project in the InfoCube, and remove the “Business Area” from the InfoCube. Proceed as described for the plan data InfoCube. Save and activate your entries. End the process by choosing “Cancel” (F12). If a warning message is displayed, confirm with “No”.

© SAP AG

FSC800

7-53

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-7 Now create a new MultiProvider for your cash accounting and liquidity planning. Select your T_FSC800_GR## InfoArea with the secondary mousebutton and choose “Create MultiProvider”. Enter the technical name of your MultiProvider in the “MultiProv.” field. The MultiProvider must have the technical name: TFSCGR##M (replace ## with your group number) Enter the following description of the MultiProvider: “FSC800 MultiProvider Group ##”

Select the following MultiProvider as a template: “0SEM_MC1 Liquidity Planning: Plan/Actual Comparison” Choose “Create” (F5). The following screen displays the InfoCubes selected as templates for our MultiProvider based on the Business Content MultiProvider selected. We now want to replace these two InfoCubes with our new InfoCubes. First, deselect the two InfoCubes from Business Content: “0SEM_C12

Liquidity Planning: Plan Data”

“0TRLP_C01 Liquidity Planning: Actual Data” In their place, select the two new InfoCubes you created: TFSCGR##P Liquidity Planning: Plan Data TFSCGR##I Liquidity Planning: Actual Data (replace ## with your group number) Confirm your entries by choosing “Continue” (green checkmark). The maintenance interface for MultiProviders appears.

© SAP AG

FSC800

7-54

SAP PORTUGAL | USO EXCLUSIVO | 2013 To edit the MultiProvider, hide the Navigator (Shift + F11). First, add a new dimension to the MultiProvider. To do so, select the “Dimensions” folder with the secondary mousebutton and choose “Create New Dimensions”. Enter “Project” as the description. Confirm your entries by choosing “Continue” (green checkmark). To include the “Project” characteristic in the MultiProvider, you can transfer it from one of the “Involved InfoProviders” in the left-hand screen area to the required dimension using drag and drop. To do so, expand the tree structure of one of your basic InfoProviders. Liquidity Planning: Plan Data Dimensions Project (TFSCGR##I4) Project Definition (0PROJECT) Select “Project Definition” (0PROJECT) with the primary mousebutton, keep it selected, and drag the cursor to the “Project” dimension on the right side of the screen. After we have included the characteristic in the MultiProvider, we still have to define the basic InfoProviders to which the characteristics of the MultiProvider are assigned. To do so, we select a characteristic on the right-hand side of the screen with the secondary mousebutton and choose “Identify (Assign)”. On the next screen, choose “All”. The system then proposes an assignment for all characteristics involved. Confirm the message. The “Project” characteristic and all other characteristics involved are now assigned to the two basic InfoProviders. Confirm your entries (green checkmark). Since we have changed the basic InfoProviders, we have to assign the key figures to the basic InfoProviders in an additional step. To do so, display the key figures by selecting the “Key Figures” folder on the right-hand side of the screen. Then select one of the two key figures with the secondary mousebutton and choose “Select (Assign)”. On the next screen, choose “All”. The system then proposes an assignment for all key figures involved. Confirm the message and your entries by choosing “Continue” (green checkmark). Save and activate your entries. End the process by choosing “Cancel” (F12). If a warning message is displayed, confirm with “No”.

© SAP AG

FSC800

7-55

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-8 Create a new application component and InfoSource in BI for your group (optional). In the Data Warehousing Workbench, navigate to the InfoSource for this course in the InfoSource tree. To do so, follow the path: “Modeling”

“Data Warehouse Workbench: Modeling”

“InfoSources” “BW Training ZBW_TRAINING” “ZT_FSC800 ZT_FSC800” Select ZT_FSC800_GR## with the secondary mousebutton and choose “Create Application Component”. Enter the technical name of your application component in the “Application Comp.” field. The application component must have the technical name: T_FSC800_GR## (replace ## with your group number) Enter the following description of the application component: “FSC800 Application Component BW Group ##”

Then select the new application component with the secondary mousebutton and choose “Create InfoSource”. In the maintenance dialog that appears, assign the technical name of your InfoSource and enter a description. Technical name: T_FSC800_GR## (replace ## with your group number) Description: “FSC800 InfoSource BW Group ##” Once you have filled these two fields, select the template with object type “InfoSource” and the name “0TR_LP_1”. Confirm your entries by choosing “Continue” (green checkmark).

© SAP AG

FSC800

7-56

SAP PORTUGAL | USO EXCLUSIVO | 2013 Select the “Business Area” row (0BUS_AREA) and delete it. Set the cursor on the first empty cell in the “InfoObject” column. In this cell, enter the technical name of the InfoObject for “Project Definition” (0PROJECT) and confirm your entries with “Enter”. Save and activate your entries. End the process by choosing “Cancel” (F12). If a warning message is displayed, confirm with “No”.

1-9 Create a transformation for updating the data from your InfoSource to your actual data InfoCube (optional). This should transform the data from your new InfoSource (T_FSC800_GR##) to your “TFSCGR##I Liquidity Planning: Actual Data” InfoCube. In the Data Warehousing Workbench, navigate to the InfoArea for your group in the InfoProvider tree. To do so, follow the path: “Modeling”

“Data Warehouse Workbench: Modeling”

“InfoProvider” “BW Training T_BW” “BW Customer Training T_BW_CUST” “T_FSC800 T_FSC800” “T_FSC800_GR## T_FSC800_GR##” Select your “Liquidity Planning: Actual Data” InfoCube with the secondary mousebutton and choose “Create Transformation”. Select the “InfoSource” object type as the source for the transformation. As the name, select the ZT_FSC800_GR## InfoSource for your group T_FSC800_GR##. Confirm the message that a proposal with 12 rules has been created. Check the proposal and activate the transformation.

© SAP AG

FSC800

7-57

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-10 Create a transformation for updating the data from your DataSource to your InfoSource (optional). In the Data Warehousing Workbench, navigate to the InfoSource for your group in the InfoSource tree. To do so, follow the path: “Modeling”

“Data Warehouse Workbench: Modeling”

“InfoSources” “BW Training ZBW_TRAINING” “ZT_FSC800 ZT_FSC800” “ZT_FSC800_GR## ZT_FSC800_GR00” “ZT_FSC800_GR## ZT_FSC800_GR00”

Select your InfoSource with the secondary mousebutton and choose “Create Transformation”. Select the “DataSource” object type as the source for the transformation. Select the DataSource: Z_FSC800_GR## (replace ## with your group number) Select T90CLNT090 as the source system. Confirm your entries by choosing “Continue” (green checkmark). Confirm the message that a proposal with one rule has been created. You now have to assign the remaining DataSource fields to the InfoSource manually. To create more space on the screen, hide the Navigator (Shift + F11). To link the DataSource fields and InfoSource fields, select the field description in the DataSource table on the left side of the transformation screen with the primary mousebutton, keep it selected, and drag the cursor to the target field.

© SAP AG

FSC800

7-58

SAP PORTUGAL | USO EXCLUSIVO | 2013 Link the following DataSource fields with the corresponding target fields. DataSource Field

InfoSource InfoObject

BUKRS

0COMP_COD E

Comment

GSBER LQPOS

0LQPOSI T

ZBUKR

0PCOMP_COD E

LQDAY

0CALDA Y

DISP_PERI 2

0CALWEE K

Ignore the warning message

DISP_PERIO

0CALMONT H

Ignore the warning message

DISP_YEAR

0CALYEA R

Ignore the warning message

DATA_OF

0SEM_CRDAT E

TWAER

0CURRENC Y

WRBTR

0AMOUNT_A

WAERS

0LOC_CURRC Y

DMBTR

0VALUE_L C

KWAER KWBTR

Activate the transformation.

1-11 Create an InfoPackage to load the data from the R/3 DataSource to the PSA of BI (optional). In the application component tree, expand your InfoSource until you see the DataSource that was connected to the InfoSource through the transformation. “Modeling”

“Data Warehouse Workbench: Modeling”

“InfoSources” “BW Training ZBW_TRAINING” “ZT_FSC800 ZT_FSC800” “ZT_FSC800_GR## ZT_FSC800_GR00” “ZT_FSC800_GR## ZT_FSC800_GR00” Transformation, Active “Z_FSC800_GR00 Z_FSC800_GR00”

© SAP AG

FSC800

7-59

SAP PORTUGAL | USO EXCLUSIVO | 2013 Select your DataSource with the secondary mousebutton and choose “Create InfoPackage”. Select the row with your DataSource and assign the following name as the description for your InfoPackage: FSC800GR## Transaction Data (replace ## with your group number) Confirm your entries by choosing “Save”. To create more space on the screen, hide the Navigator (Shift + F11). In the “From Value” column on the “Data Selection” tab page, restrict the company code to the code that was assigned to your group: AC## (replace ## with your group number) Save your entries and switch to the “Schedule” tab page. Make sure that “Start Data Load Immediately” is activated and initiate the loading process by choosing “Start”.

Once the data has been requested successfully, choose “Monitor” (F6). Select your loading process (by selecting the row with the time of your request).

Then choose “Details” to refresh the information about your data request (F8). Refresh this information until the data request has “green” status and the data has then been loaded to the PSA successfully (see “Status” tab page).

Monitor the data in the PSA by choosing “PSA Maintenance”. When doing so, confirm the default settings on the next screen by choosing “Continue” (green checkmark). Once you have checked the data, exit the Data Warehousing Workbench (by choosing “Back” or “Cancel”, more than once if required).

© SAP AG

FSC800

7-60

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-12 Create a data transfer process to load the data from the DataSource to your InfoCube. Then load the data for your company code to the InfoCube for your group (optional). Call the Data Warehousing Workbench. For the Data Warehousing Workbench, use the SAP Easy Access Menu path: “Information Systems” “Business Information Warehouse” “Modeling” -> “Data Warehousing Workbench: Modeling” You can call the Data Warehousing Workbench with transaction RSA1. In the Data Warehousing Workbench, navigate to the actual data InfoCube for your group in the InfoProvider tree. To do so, follow the path: “Modeling”

“Data Warehouse Workbench: Modeling”

“InfoProvider” “BW Training T_BW” “BW Customer Training T_BW_CUST” “T_FSC800

T_FSC800”

“T_FSC800_GR## T_FSC800_GR##” “Liquidity Planning: Actual Data TFSCGR00I”

Select your InfoCube with the secondary mousebutton and choose “Create Data Transfer Process”. Select the “DataSource” object type as the source and then select the following as the name of your DataSource: Z_FSC800_GR## FSC800GR## Transaction Data (replace ## with your group number) If your DataSource is already the default target, confirm your entries by choosing “Continue” (green checkmark) and hide the Navigator (Shift + F11) so that you have more space on the screen.

© SAP AG

FSC800

7-61

SAP PORTUGAL | USO EXCLUSIVO | 2013 On the “Extraction” tab page, select “Only Get Delta Once”. Then activate your data transfer process. Switch to the “Execute” tab page and choose the “Execute” button next to the “Processing Mode” field. Display the data request in the “Request Monitor” by confirming the message that appears with “Yes”.

If the data request is not yet complete, choose “Refresh Request” (F8) until the data request has “green” overall status (“Header” tab page).

1-13 Analyze the loaded data in your InfoCube (optional). Return to the Data Warehousing Workbench and view the data in your InfoProvider for the actual data. To do so, select the InfoCube for the actual data: TFSCGR##I “Liquidity Planning: Actual Data” with the secondary mousebutton and choose “Display Data”. On the next screen, choose “Fld Selectn for Output”. On the following screen, select “Highlght all key figs” and “Select All Characteristics”. Choose “Execute” (F8) and then “Execute” again (F8). Check the data loaded.

© SAP AG

FSC800

7-62

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Reporting: Liquidity Planning & Cash Accounting

Contents: Simple report generation using BEx Query Designer and BEx Analyzer Business Content for reporting in liquidity planning and cash accounting

 SAP AG 2008

© SAP AG

FSC800

8-1

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Reporting: Liquidity Planning and Cash Accounting - Unit Objectives

At the conclusion of this unit, you will be able to: Create and execute your own simple report for reporting in liquidity planning and cash accounting. Explain Business Content for reporting in liquidity planning and cash accounting in BI.

 SAP AG 2008

© SAP AG

FSC800

8-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Reporting: Liquidity Planning and Cash Accounting: Business Scenario

You want to check whether the reporting Business Content for liquidity planning and cash accounting covers the requirements of your project. You also want to learn how to create simple reports that meet your requirements.

 SAP AG 2008

© SAP AG

FSC800

8-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 SAP BI Architecture Enterprise Portal Visual Composer BI Kit

KM

Business Explorer Suite (BEx) Information Broadcasting BEx Web Web Analyzer

BI Pattern Web Application Designer

BEx Analyzer Report Designer

MS Excel Add-In

BI Consumer Services

BEx Query Designer

BI Platform Analytic Engine

Planning Modeler

Meta Data Mgr

UDI SAP JDBC XMLA ODBO query

Data warehouse

DB Connect

BAPI

Service API

File

XML/A

 SAP AG 2008

SAP BI architecture enables you to procure, transform, save, analyze, distribute, and access data from SAP sources and external sources. The Business Explorer Suite (BEx) includes a number of tools that enable you to access and analyze data.

© SAP AG

FSC800

8-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 User Types High

Analytical performance

Query developer

Experienced users

Inexperienced users

Low  SAP AG 2008

© SAP AG

FSC800

8-5

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Content for Liquidity Planning and Cash Accounting

 SAP AG 2008

The objects are BW 3.5 objects that can be called using the relevant front-end components. You can migrate the objects to BI 7.0 front-end components.

© SAP AG

FSC800

8-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 Open Options in BEx Analyzer

Use this option to create a new query.

Open a workbook that has already been saved.

Open a new workbook with an existing query.

 SAP AG 2008

© SAP AG

FSC800

8-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 The “Open” Dialog Box Find query by entering search parameters

The queries most recently used Queries that you want to find quickly

Queries relevant for your position

Queries organized by InfoArea

 SAP AG 2008

© SAP AG

FSC800

8-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 Finding Queries

 SAP AG 2008

© SAP AG

FSC800

8-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 Changing Variable Values

Save these selections to use later.

Option for returning to the variables dialog box.

Call values from your personal list.

Save values in your personal list.

Save these values with the workbook.  SAP AG 2008

© SAP AG

FSC800

8-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 Navigation Options

Basic Navigation

Other Options

• • • Select Filter Value • • Keep Filter Value • Remove Filter Value Filter and Drilldown According To • • • Drilldown According To • Drill ... Across ... • Remove Drilldown • Change Drilldown

• Back • Back to Start • • • • • • • •

... Exchange with… Swap Axes Sort Goto Convert to Formula Add Local Formula Explain Properties Query Properties Save View Broadcast and Export Documents

Note: You can execute the underlined options using drag&drop.  SAP AG 2008

© SAP AG

FSC800

8-11

SAP PORTUGAL | USO EXCLUSIVO | 2013 BEx Analyzer – Navigation Pushbuttons

 SAP AG 2008

© SAP AG

FSC800

8-12

SAP PORTUGAL | USO EXCLUSIVO | 2013 ... Replace With ... Drag Sales Group to Distribution Channel

Result

 SAP AG 2008

© SAP AG

FSC800

8-13

SAP PORTUGAL | USO EXCLUSIVO | 2013 Drilldown Drag Division to any of the Distribution Channel values.

Result

 SAP AG 2008

© SAP AG

FSC800

8-14

SAP PORTUGAL | USO EXCLUSIVO | 2013 Retaining the Filter Value

Drag Australia to the navigation area.

Result: The query is filtered by values for Australia.  SAP AG 2008

© SAP AG

FSC800

8-15

SAP PORTUGAL | USO EXCLUSIVO | 2013 Removing a Filter Value

Remove Canada from the results area.

Result: Canada is not taken into account during filtering.

 SAP AG 2008

© SAP AG

FSC800

8-16

SAP PORTUGAL | USO EXCLUSIVO | 2013 “Save Workbook” Dialog Box

Save the workbook here if you do not want to release it. Save the workbook here if you want to release it for colleagues.

 SAP AG 2008

© SAP AG

FSC800

8-17

SAP PORTUGAL | USO EXCLUSIVO | 2013 “Open Workbook” Dialog Box Find the workbook by entering search parameters

The workbooks most recently used

Workbooks that you want to find quickly

Workbooks relevant for your position

 SAP AG 2008

© SAP AG

FSC800

8-18

SAP PORTUGAL | USO EXCLUSIVO | 2013 Options for Refreshing Workbooks In manual refresh mode…

In automatic refresh mode…

Option for switching to manual refresh mode

Refresh data (if required)

Keep old data or call new data when you open a workbook?

 SAP AG 2008

© SAP AG

FSC800

8-19

SAP PORTUGAL | USO EXCLUSIVO | 2013 Tools

Create a new query for this workbook.

Check/manage the definition of the current workbook query.

Links to other BEx tools

 SAP AG 2008

© SAP AG

FSC800

8-20

SAP PORTUGAL | USO EXCLUSIVO | 2013 New Query Dialog Box BEx Query Designer: No Query Loaded Query

Edit

View

Extras

Help

New Query: Select InfoProvider Search in

Sales reports Last Changed On

Find

Weekly sales figures Monthly sales figures Quarterly sales figures Regional analysis

History

Team analysis Customer analysis

InfoAreas

Name

Open InfoProvider

Type

Cancel

 SAP AG 2008

© SAP AG

FSC800

8-21

SAP PORTUGAL | USO EXCLUSIVO | 2013 BEx Query Designer Toolbar

New Query

Check Query Save Query

Table View Cut

Paste

Query Properties

Open Query

Execute

Filter (Open)

Conditions

InfoProvider (Open) Copy

Documents

Properties

Cells Rows/Columns (Open)

Messages (Open)

Exceptions Tasks

Where-Used List Technical Names

 SAP AG 2008

© SAP AG

FSC800

8-22

SAP PORTUGAL | USO EXCLUSIVO | 2013 BEx Query Designer Menus

Query

Edit

View

Extras

Help

New…

CTRL+N

Open…

CTRL+O

Check… Save

CTRL+S

Save as

CTRL+SHIFT+S

Delete Properties Execute

CTRL+R

Publish End and Discard Changes

CTRL+Q

 SAP AG 2008

© SAP AG

FSC800

8-23

SAP PORTUGAL | USO EXCLUSIVO | 2013 Layout of the BEx Query Designer (View)

3 .

2 .

4 .

1 .

5 .  SAP AG 2008

© SAP AG

FSC800

8-24

SAP PORTUGAL | USO EXCLUSIVO | 2013 Layout of the BEx Query Designer (Rows/Columns View)

6.

7.

10. 8.

9.

11.

 SAP AG 2008

© SAP AG

FSC800

8-25

SAP PORTUGAL | USO EXCLUSIVO | 2013 InfoCube Elements in BEx Query Designer InfoCubes Key Figure Restricted key figures Calculated key figures Key figure...

Global objects

Dimensions Dimension ... Characteristic ... Compounding information Attributes Characteristic variables Values Time Unit

Standard dimensions

Data package

 SAP AG 2008

For MultiProviders, the "InfoProvider" characteristic also appears in the "Data Package" dimension. You can use this characteristic to restrict the query to single Basis InfoProviders (that are contained in a MultiProvider).

© SAP AG

FSC800

8-26

SAP PORTUGAL | USO EXCLUSIVO | 2013 Selecting Filter Values Select by single value, areas, favorites, history, or variables

Default settings Save frequent selections

Include, exclude, offset Search options Select the values on the left and move them to the right by drag & drop or by clicking the arrow.

 SAP AG 2008

© SAP AG

FSC800

8-27

SAP PORTUGAL | USO EXCLUSIVO | 2013 Defining Restricted Key Figures Query level

Right-click

Edit ...

Right-click

New restricted key figures ...

In the report, the "Incoming Orders" key figure is displayed for April 2005 only.

 SAP AG 2008

© SAP AG

FSC800

8-28

SAP PORTUGAL | USO EXCLUSIVO | 2013 Calculated Key Figures Query level

InfoProvider level

Right-click

Right-click

New calculated key figures

New formula ...

You can create a new, restricted key figure directly in the formula editor.

 SAP AG 2008

© SAP AG

FSC800

8-29

SAP PORTUGAL | USO EXCLUSIVO | 2013 Boolean Operators

Define your Boolean logic here. This is based on IF-THENOTHERWISE.

Select your Boolean operators from the list.

 SAP AG 2008

© SAP AG

FSC800

8-30

SAP PORTUGAL | USO EXCLUSIVO | 2013 Input Screen for Properties

Locate the required InfoObject easily using the dropdown list.

The properties are arranged in various categories. Use the tab page to locate the required property.

You must select the correct tab page.

 SAP AG 2008

© SAP AG

FSC800

8-31

SAP PORTUGAL | USO EXCLUSIVO | 2013 Creating a Reusable Structure

Save as...

The structure can then be used in every query for this InfoProvider.

 SAP AG 2008

© SAP AG

FSC800

8-32

SAP PORTUGAL | USO EXCLUSIVO | 2013 Characteristic Properties Use the dropdown list to access each characteristic directly.

Properties are organized in groups.

Use the standard settings for the metadata.

Open this tab page to access the properties.

 SAP AG 2008

© SAP AG

FSC800

8-33

SAP PORTUGAL | USO EXCLUSIVO | 2013 Hierarchical Positioning of Characteristics

Select the hierarchical display and default level to display the result.

 SAP AG 2008

© SAP AG

FSC800

8-34

SAP PORTUGAL | USO EXCLUSIVO | 2013 Hierarchies in Analyses 1.

2.

3.

 SAP AG 2008

Characteristics of the presentation hierarchy: • Sorting • Expand to level • Position of lower-level nodes • Values of posted nodes • Nodes with only one lower-level node

© SAP AG

FSC800

8-35

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Reporting: Liquidity Planning and Cash Accounting Summary

You are now able to: Explain Business Content for reporting in liquidity planning and cash accounting in BI. Create and execute your own report for reporting in liquidity planning and cash accounting.

 SAP AG 2008

© SAP AG

FSC800

8-36

SAP PORTUGAL | USO EXCLUSIVO | 2013 Exercises Unit:

BI Reporting

At the conclusion of these exercises, you will be able to: • Explain Business Content for reporting in liquidity planning and cash accounting in BI • Create and execute your own report for reporting in liquidity planning and cash accounting • You want to check whether the reporting Business Content for liquidity planning and cash accounting covers the requirements of your project. • You also want to learn how to create simple reports that meet your requirements.

1-1 Create a simple query based on your MultiProvider “FSC800 MultiProvider Group ##” TFSCGR##M (replace ## with your group number) The query should be structured as follows: •

Characteristic restrictions: Restrict the “Company Code” characteristic to your company code: AC## (replace ## with your group number)

•

Default values: Restrict the “Creation Date” characteristic to the variable: FSC800VARERZEUG

Restrict the “Calendar Year” characteristic using the following variable: © SAP AG

FSC800

8-37

SAP PORTUGAL | USO EXCLUSIVO | 2013 Calendar Year (0P_CALYE) •

Columns: Add the “Amount - Actual” key figure to “Columns”. Then drag the “Currency” characteristic to this area.

•

Rows: Add the “Liquidity Item” characteristic to the rows. Display the long text and key for the “Liquidity Item”. Liquidity items must be displayed based on the Cash Flow FSC800 hierarchy.

Save your query in “Favorites” with the technical name: FSC800GR##QUERY1 and the description: FSC800 Group ## Query 1

1-2 Execute your query and navigate to it. You can, for example: Add a drilldown according to calendar month Restrict the query to specific liquidity items

1-3 Save your navigational state in a new workbook. Name your workbook FSC800 Group ## Workbook 1.

© SAP AG

FSC800

8-38

SAP PORTUGAL | USO EXCLUSIVO | 2013 Solutions Unit:

Business Content, Modeling, and Extraction

1-1 Create a simple query based on your MultiProvider. Call Business Explorer Analyzer via the following path: “START” “Programs” “Business Explorer” “Analyzer”

Create a new query by choosing “BEx Analyzer” -> “Tools” -> “Create New Query”. Select “SAP Training System” from the list and log on to the system. Create a new query by choosing “New Query”. Switch to the “InfoAreas” view by selecting “InfoAreas” in the “Search In” field. Navigate to your MultiProvider: “BW Training” “BW Customer Training” “T_FSC800” “T_FSC800_GR##” “FSC800 MultiProvider Group ##” Select your MultiProvider and choose “Open”. The dimensions, key figures, and characteristics for your MultiProvider are displayed on the left side of the screen. Open the “Non-Time-Based Dimension 1” and drag the “Company Code” characteristic to the “Characteristic Restrictions” area. Select the “Company Code” characteristic with the secondary mousebutton in the “Characteristic Restrictions” area and choose “Restrict”.

© SAP AG

FSC800

8-39

SAP PORTUGAL | USO EXCLUSIVO | 2013 In “Direct Input”, restrict the company code to your company code: AC## (replace ## with your group number) To do so, display the company codes as single values by selecting “Single Values” in the “Show” field. Select your company code and add it to the “Selection” area. Confirm your entries by choosing “OK”. Next, expand the “Time-Based Dimension” and drag the “Creation Date” characteristic to the “Default Values” area. In the “Show” field, select “Variables” and restrict this characteristic to the following variable: FSC800VARERZEUG Confirm your entries by choosing “OK”. Then drag all “Time” characteristics to the “Default Values” area. Restrict the “Calendar Year” characteristic using the following variable: Calendar Year (0P_CALYE) Confirm your entries by choosing “OK”. Switch to the “Rows/Columns” view and drag the “Amount - Actual” key figure to the columns. Expand the “Unit” dimension and drag the “Currency” characteristic to the columns. The “Liquidity Item” characteristic still had to be included in the query. To do this, drag and drop it from “Non-Time-Based Dimension 2” to the rows for the query. Now change the “Display” mode in the query “Properties”. Under “Display as”, choose “Text and Key” and select “Long Text” as the “Text View”. We also want to display the liquidity items as a hierarchy. To do so, choose the “Hierarchy” tab page in the “Properties” area and use

to select the hierarchy name:

Cash Flow FSC800

© SAP AG

FSC800

8-40

SAP PORTUGAL | USO EXCLUSIVO | 2013 Save your query in “Favorites” with the technical name: FSC800GR##QUERY1 and the description: FSC800 Group ## Query 1

1-2 Execute your query and navigate to it. If BEX Query Designer is still active, execute your query by choosing the green checkmark. In this case, ignore the following instructions. ---------------------------------------------------------------------------------------------------------Call Business Explorer Analyzer again via the “Programs” menu. To do so, choose the following path: “START” “Programs” “Business Explorer” “Analyzer” Choose “BEx Analyzer” and select “Open Query”. Select your query from the “History” and choose “Open”. ---------------------------------------------------------------------------------------------------------On the “Change Variable Values” screen, restrict the creation date to today’s date and the calendar year to the current year. Use the input help if required. Confirm your entries by choosing “OK”. Navigate to your query. You can, for example: Add a drilldown according to calendar month Restrict the query to specific liquidity items

© SAP AG

FSC800

8-41

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-3 Save your navigational state in a new workbook. To do so, choose the Workbook As”.

icon in the menu bar for saving workbooks and select “Save

Name your workbook: FSC800 Group ## Workbook 1 Confirm your entries by choosing “Save”.

© SAP AG

FSC800

8-42

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Integrated Planning

Contents: Options and functions in BI Integrated Planning Creating a simple planning application with BI Integrated Planning

 SAP AG 2008

© SAP AG

FSC800

9-1

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Integrated Planning: Unit Objectives

At the conclusion of this unit, you will be able to: Describe the options and functions in BI Integrated Planning Create a simple planning application for liquidity planning and cash accounting

 SAP AG 2008

© SAP AG

FSC800

9-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Integrated Planning: Business Scenario

Your company introduces liquidity planning and cash accounting. Your project team wants to learn about the options and functions of BI Integrated Planning.

 SAP AG 2008

© SAP AG

FSC800

9-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 Management Cycle Analysis

Environment Corporate philosophy

Analysis (for example, profitability)

Reporting (plan/actual)

Operations

Analyze

Model

Valuate

Execute

Planning (strategic, operational)

Planning (execution)

Execution

 SAP AG 2008

Planning is an integral part of the management cycle. Companies find themselves in complex environments (competitors, political situation, geographical location, and so on). Different companies follow different business models (for example, private and public companies). Depending on the general objectives of the company (specific percentage of profitability, maximum use for public good, and so on), the working environment must be taken into account. The management cycle helps companies position themselves in complex environments and achieve their general company objectives. The business philosophy forms the framework that should include all of the company's operations. Planning supports decision-making and the co-ordination of various departments with regard to the common objective, and defines general conditions for operations. Execution involves all of the steps that are required to add value to the company. Reporting traces all transactions that occur during execution. Analysis concentrates on calculating success in terms of meeting objectives and searches for reasons if objectives are not met. The analysis results are measured against the desired business philosophy and lead to the evaluation of the common objectives and actions that are carried out to keep the company on course.

© SAP AG

FSC800

9-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 Strategic, Operational, and Execution Planning

Low

Strategic planning

Operational planning Granulation Valuate

Execution planning -

Detailed planning (MRP) Flow of goods control Product planning Capacity planning Contracting...

-

Model Sales planning Revenue planning Requirements planning (MRP) Proposal planning Sales and profit planning Cost center planning Strategic procurement …

- Company vision and mission - Long-term investments - Strategic orientations - Strategic market development specifications - …

and your liquidity planning?

Execute

High t0

Week 1 Week 2 Week 3

…

Year 1

…

Year x

Time  SAP AG 2008

Business Planning comprises various levels: • Strategic planning specifies the direction for future development of a company; for example, product/service offering, return on investment, company growth, and so on. Strategic planning is a simulative process in which various scenarios are modeled and then evaluated to calculate the expected value added. The strategic evaluation leads to objectives being set for the various operational units, that is, the higher-level strategic objectives are divided into targets at execution level (for example, expected net revenue, sales growth, and so on). • Operational planning is the assignment of resources (labor, capital, assets) that are necessary for meeting the objectives and reconciling resources beyond the operational units (for example, the sales quantity must be reconciled with the production quantity - if your company has the capacity to produce 200 bottles of suntan lotion per month but you could sell 1,000 bottles in August, you have to produce at least 800 bottles of suntan lotion in the months before August ...). The results of the operational planning process can be used for detailed planning and material requirements planning in execution planning.

© SAP AG

FSC800

9-5

SAP PORTUGAL | USO EXCLUSIVO | 2013 Top-Down and Bottom-Up Product category

Product master group

Product group

Product master group

Product group

Product

Top-down

Product group

Product Company

Subgroup I

Company I

Subgroup II

Company II

Company III

Bottom-up

 SAP AG 2008

Top-down and bottom-up are structures used to coordinate the vertical planning process. These structures are generally hierarchy based. • Bottom-up represents the data flow from detailed planning at various sublevels to an overall summary. • Top-down is the opposite direction where strategies and targets that were defined at higher levels are converted to operational targets. A mixed top-down/bottom-up planning system combines these two structures. Various versions separate different plan versions and can be used to compare different perspectives (CFO – sales employees). The final version is normally used as the basis for construction planning (for example, detailed planning).

© SAP AG

FSC800

9-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 Rolling Planning May

June

July

May forecast

June forecast

July forecast

6-period actual Current period (actual) 5-month forecast

 SAP AG 2008

In the past, planning was often a static process carried out once a year that was to form the basis of execution and budgets for the following year. Dynamic environments and fast-changing economic situations force companies to think about strategies for responding to changing conditions. Key words in this context include: beyond budgeting, better budgeting, active planning…. In general, these concepts result from the need to manage changes regarding the planning process and persons involved. Part of these changes is the need for a constant process that enables companies to quickly respond to changes in their environment. Rolling planning is a continuous process that compares planned values with actual values, through which the further development of plan figures is derived. If the difference between the plan and the forecast exceeds a specific limit, the strategy must be re-evaluated so that appropriate measures can be taken or the strategy adjusted.

© SAP AG

FSC800

9-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 How SAP NetWeaver BI Supports Business Planning SAP NetWeaver BI Cross-company planning tasks Prepare data

Automatic planning

for planning process

Load

Load

Master data Actual data

New master data Operational transaction

Budget data

Budget control mySAP ERP

mySAP SCM

mySAP CRM

mySAP …

 SAP AG 2008

BI Integrated Planning is part of SAP NetWeaver BI, the SAP platform for business analyses. BI Integrated Planning is a generic planning tool that supports various types of strategic and operational planning and enables planning at any detail level. User interfaces and company-specific logic for creating models in a company can be defined in accordance with the requirements of any planning type. BI Integrated Planning provides convenient process support. BI Integrated Planning provides tools that close the gaps between operational transactions by loading and distributing data from and to transaction systems.

© SAP AG

FSC800

9-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Planning Integrated in BI Platform & Suite Highest user productivity during planning Combined standardized user interface for planning and analysis Combined standardized processing logic for both planning and analysis (for example, hierarchies, variables, calculated key figures, and so on)

Design of planning applications Standard user-oriented design tools for planning and analysis (for example, Query Design and Web applications follow the same approach)

Integrated analysis and planning applications

Web-based and Web-managed modeling and administration environment for planning applications Joint modeling and integrated metadata

Intuitive design environment  SAP AG 2008

BI Integrated Planning enables: • Integrated design time tools: BEx Query Designer and BEx Web Application Designer are used to build analysis and planning applications. • Integrated planning and analysis engine -> OLAP services such as drilldown, hierarchies, calculated key figures, and so on can also be used during planning. Data entries are also supported in the BEx Analyzer. • Joint runtime and metadata for planning and analysis The Planning Modeler is a Web-based modeling environment for all tasks related to planning.

© SAP AG

FSC800

9-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 Conflict Between the “Flexibility” of the End Users and Integration “Freedom” for end users

Covered by the tool

Integration

Spreadsheets

ERP BW-BPS BI Integrated Planning

BI Integrated Planning encompasses a wide spectrum and provides a highly user-friendly platform with multiple integration options.

 SAP AG 2008

If you look at what companies require with regard to planning functions, you can expect different requirements from end users and administrators at the company. The end user wants a high degree of flexibility and data integration during planning, whereas administrators place importance on fixed and controllable planning structures. If you compare different planning software, you can see also the trade-off between flexibility and integration. For example, ERP systems offer high integration in planning but little flexibility to the end user. In contrast, MS Excel is a very flexible planning tool but can be integrated across landscapes only through complex mechanisms. BI Integrated Planning meets the needs of both end users and administrators at the same time. This enables end users to take an input-ready query that is equally valid for all planners of a planning area and carry out more detailed planning in Excel offline. Only part of this data is fed back into the input-ready query (that is, the part for which a cell link exists).

© SAP AG

FSC800

9-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Integrated Planning Modeling of planning structures Planning Modeler DW Workbench

Manual planning

Automatic planning Planning functions

Multidimensional company structures Definition of work packages Hierarchy maintenance

Simulation/“what if?” Forecasting Copying, deleting Currency translation Top-down distribution ...

Version management

Planning sequences

User authorizations

Event-based execution of planning sequences

Building blocks

Draft a planning model

User interfaces

Managing and distributing data

Excel and Web Document management

Status and monitoring

Input-enabled queries

Variable management

Drilldown Calculated key figures Structures Currency translation Excel formulas (get/set data) ….

Design a query

Create a planning function

Process control

Write back to operating systems (retraction, XI, and open hub) Use of planning sequences in process chains

Execute a planning application

Set up a Web application

Implementation (combine queries and planning functions)

Embed queries in workbooks Draft a workbook

 SAP AG 2008

BI Integrated Planning comprises four parts:

• During modeling, you create the data model for your planning process. This means that you define the

structure of your planning process. When doing so, you take into account your company structure (slice and dice*) and your planning strategy (for example, bottom-up, top-down, or mixed).

• Planning functions are functions that support the automatic processing of plan data (for example, copying, forecasting, and so on). This is done through simulation or embedding in background processing.

• You can use the planning layout to create a context in which you enter the plan data for your various users. Web applications comprise one or more planning queries with planning functions for supporting the planner in his or her planning tasks.

• To coordinate the planning processes and their sequence, you can assign planning tasks to the planners and track the status of the planning results.

*Slice and dice = filter using various criteria The Web-based Planning Modeler is the core application in which all modeling and adjustment takes places for BI Integrated Planning. In the Modeler, the various objects are maintained in connection with planning, such as aggregation levels and planning functions and the relationships between these objects. The Planning Modeler provides a central entry point for planners. It is a Web-based tool that provides an integrated test environment. Modeling is also possible for business experts who cannot access to Data Warehousing Workbench (transaction RSA1). To manage a planning process, settings (variables, “data slices”, formulas) frequently have to be changed, which is possible in the Planning Modeler.

© SAP AG

FSC800

9-11

SAP PORTUGAL | USO EXCLUSIVO | 2013 Architecture of the Planning Modeler

Real-time InfoCube

Aggregation level

Filter Filter BI Integrated Planning  SAP AG 2008

This is the architecture of BI Integrated Planning: • The planning model in BI Integrated Planning is based on a real-time InfoCube. • Real-time InfoCube is the new term for a transactional InfoProvider. • This InfoProvider provides the database for the aggregation level. • An aggregation level is a new type of virtual InfoProvider. The aggregation level is the basis for the input-ready query. • You can create work packages for the planners using filters.

© SAP AG

FSC800

9-12

SAP PORTUGAL | USO EXCLUSIVO | 2013 Planning Modeling

Version

Region Year Country

Price

Year Price Year

Who does the planning?

Customer Production costs Sales quantity

Sales

Year

Product

Country

What has to be planned?

Manager

Sales quantity

Country

Region

Regional manager

Sales quantity Country

Region

Account manager

Customer Sales quantity

 SAP AG 2008

If you want to start planning, you first have to decide what you want to plan and which person groups are involved, that is, define the granularity. The figure above shows that three planner groups are to be mapped in the model: manager, regional manager, and account manager. For each of these groups, the segmentation characteristics for planning have to be determined. For example, the account manager plans the sales quantity key figure at the more detailed levels (year, country, region, and customer). The three granularities can later be found at separate aggregation levels.

© SAP AG

FSC800

9-13

SAP PORTUGAL | USO EXCLUSIVO | 2013 Planning Modeling – Real-Time InfoCube Real-time InfoCube Aggregation level

Real-time InfoCube

Filter Filter

Year Year

Country

Sales quantity

Country

Region

Regional manager

Sales quantity Year

Country

Manager

Region

Account manager

Customer Sales quantity

 SAP AG 2008

The figure above shows which fields have to be included in a real-time InfoCube if all three planner groups are to plan based on one InfoProvider. These fields are then used later as the basis for analyzing the InfoProvider. These fields are then the basis for structuring the aggregation levels in which each planner group is modeled at a separate aggregation level.

© SAP AG

FSC800

9-14

SAP PORTUGAL | USO EXCLUSIVO | 2013 Planning Modeling – Aggregation Level Real-time InfoCube Aggregation level

Filter Filter

Year Year

Country

Manager

Sales qty

Country

Region

Regional manager

Sales quantity Year

Country

Region

Account manager

Customer Sales quantity Aggregation level  SAP AG 2008

One aggregation level is modeled for each planner group. It comprises the fields that are relevant in accordance with the planning granularity. The aggregation level is then used to “reserve” a “slice” of the InfoProvider for planning.

© SAP AG

FSC800

9-15

SAP PORTUGAL | USO EXCLUSIVO | 2013 Planning Modeling – Filter Real-time InfoCube Aggregation level

Country USA

Sales Filter

Year 2010 Country USA Region 001 Price Production costs

Filter

Manager

Year 2010 Country USA Region 001

Customer 1

Sales quantity

Regional manager

Year 2010 Country USA Region 001

Key account manager 1

Customer 2

Key account manager 2

Sales quantity

Filters  SAP AG 2008

You use filters for each aggregation level, for example, per planner group, to define the corresponding characteristic values that are relevant for a planner in the group. When doing this, you generally try to minimize the number of filters using variables to keep the planning structure simple. You could also refer to filters as work packages for the individual planners. Example for a filter: cost planning of all costs accrued at a cost center. Responsibility for a cost center always lies with exactly one person. This means you could group all cost elements of a specific cost center into one filter/work package and assign this to the cost center managers based on authorizations.

© SAP AG

FSC800

9-16

SAP PORTUGAL | USO EXCLUSIVO | 2013 Using the Filter

Filter selection period

Input-ready query

Planning function

Restriction of data selection for which the function is executed

Further restriction of the data selection when function is executed

 SAP AG 2008

A filter functions depending on how it is used in a planning function or query. Filter in planning functions In connection with planning functions, a filter describes the data in the characteristic restrictions that is used to execute a planning function. Filter in a query The values defined in the characteristic restrictions of a query restrict the dataset that is available for additional filtering when a query is run. Once the runtime has started, a characteristic value outside of this value set can no longer be filtered.

© SAP AG

FSC800

9-17

SAP PORTUGAL | USO EXCLUSIVO | 2013 Variable Types Char. value variables

X

=

?

Hierarchy variables Hierarchy node variables

Text variables Formula variables

 SAP AG 2008

Depending on the objects for which you want to define variables, different variable types are available. Characteristic value variables represent characteristic values. Hierarchy variables represent hierarchies. Hierarchy node variables represent a node in a hierarchy. Text variables represent a text and can be used in descriptions of queries, calculated key figures, and structural components. You can use text variables in the object description when creating calculated key figures, restricted key figures, selections, and formulas. Formula variables represent numeric values and can be used in formulas. Formula variables are also used to delimit exceptions and conditions.

© SAP AG

FSC800

9-18

SAP PORTUGAL | USO EXCLUSIVO | 2013 Uses of Variables Object

Use of variables

Queries, especially input-ready queries

- Parameterization of characteristic restrictions in query - In formulas, conditions, exceptions, placeholders for texts

Filters

Parameterization of characteristic restrictions

Planning functions

Depending on planning function type for parameterization of conditions and parameters

Characteristic relationships

- To parameterize the hierarchy - To parameterize the selection from a DataStore object

Data slice

Parameterization of characteristic restrictions that describe data slices

Other objects

Parameterization of a display hierarchy for the query

 SAP AG 2008

Variables are used to parameterize a query, planning function, filter, characteristic relationship, or data slice. When a query, planning function, or Web application is executed, these placeholders are filled with values. Variables are placeholders for characteristic values, hierarchies, hierarchy nodes, texts, and formula elements and can be processed in various ways: • Depending on the objects for which you want to define variables, different variable types are available. • The processing type determines how a variable is filled with a value when a query, planning function, or Web application is run. Variables are not dependent on an InfoProvider, but rather on the respective InfoObject. A variable that has been defined for an InfoObject is available in all InfoProviders that use this InfoObject. Variables can be defined in the Query Designer, Planning Modeler, or Planning Wizard and can then be reused for all queries or planning functions. Note that you can only assign exactly one characteristic to a variable. Also note that no user-specific variables exist in BI Integrated Planning. If you require user-specific variables, you should create a DataStore object that contains the user master data and upload the user-specific characteristic combinations using a flat file. You must then create a query based on the DataStore object in which the user-specific combinations can be accessed.

© SAP AG

FSC800

9-19

SAP PORTUGAL | USO EXCLUSIVO | 2013 Overview of Planning Function Types

Planning function types in BI Integrated Planning • • • • • • • • • • • • •

Unit Conversion Create Combinations Formula Copy Delete Deletion of Invalid Combinations Repost Repost on Basis of Characteristic Relationships Revaluation Distribution by Keys Distribution by Reference Data Currency Translation Customer-Specific Planning Function Types (for each user exit)

 SAP AG 2008

To create planning functions, aggregation levels are required at which planning functions can be created, whereby planning functions can be created and executed at every active aggregation level. Filters can be used to select data. Filter and planning functions are merged through the planning sequence so that direct execution or batch processing is possible in the BI process chain. In the Data Warehousing Workbench, the planning function objects are displayed in the functional areas Business Content and Transport Connection, in the Planning folder.

© SAP AG

FSC800

9-20

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Requirements and Their Implementation in BI Integrated Planning: Standard Planning Functions Distribution with reference data Distribute sales to products

Copy Copy from actual to plan Revaluation Revaluate planned sales by 10%

Standard planning functions Delete Delete data in a plan version

Currency translation Convert currency from EUR to USD

Quantity x Price Contribution margin scheme

Calculate sales per working day in accordance with factory calendar

 SAP AG 2008

If you map a business process, you usually require a high number of predefined planning functions to create or modify plan data. BI Integrated Planning provides a high number of different standard planning functions that can be used for all planning requirements. Standard planning functions provide predefined functions that can be carried out with ease. These enable you to: • Copy data • Translate currency • Delete data • Repost data • Revaluate data • Convert units • Delete invalid combinations • Repost based on characteristic relationships

© SAP AG

FSC800

9-21

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Requirements and Their Implementation in BI Integrated Planning – FOX Formula Editor

Distribute sales to products

Copy from actual to plan

Delete data in a plan version

Revaluate planned sales by 10%

Convert currency from EUR to USD

Quantity x Price Contribution margin scheme

FOX formula Calculate sales based on working days according to factory calendar

 SAP AG 2008

If one of the standard planning functions already mentioned is unable to execute the algorithm required, you should use the FOX formula editor (FOX = formula extension) to model the function algorithm as required. Not only can you use FOX to calculate basic figures such as a contribution margin, but it is a very flexible and powerful tool for defining complex formulas that may need to use loops, read attributes, integrate variables, and so on. Programming knowledge such as ABAP, Java, and so on is not required if FOX formulas are created.

© SAP AG

FSC800

9-22

SAP PORTUGAL | USO EXCLUSIVO | 2013 Business Requirements and Their Implementation in BI Integrated Planning – Customer-Specific Planning Functions

Distribute sales to products

Copy from actual to plan

Delete data in a plan version

Revaluate planned sales by 10%

Convert currency from EUR to USD

Quantity x Price Contribution margin scheme

Customer-specific planning function

Calculate sales based on working days according to factory calendar

 SAP AG 2008

If a planning function cannot be mapped with the standard functions defined, you can set up a customer-specific planning function (ABAP knowledge required). This function type is discussed in unit 9.

© SAP AG

FSC800

9-23

SAP PORTUGAL | USO EXCLUSIVO | 2013 Planning Functions: Complexity versus Functionality

Standard planning functions

FOX formulas

Customerspecific planning functions

Complexity, functionality

 SAP AG 2008

The planning functions that can be most easily defined are standard planning functions. They can be implemented easily and can only be changed in Customizing through specific conditions. FOX formulas are a powerful tool for setting up planning functions. FOX contains terms that are usually only found in programming languages, such as “if” queries and loops. For this reason, they can cover most business requirements that cannot be modeled using standard planning functions. The option of writing your own programs means that FOX is more complex than standard planning functions. Customer-specific planning functions are implemented using the ABAP programming language and provide all the features of a programming language. This is the most complex type of planning function but also the most flexible.

© SAP AG

FSC800

9-24

SAP PORTUGAL | USO EXCLUSIVO | 2013 Copy Function

 SAP AG 2008

In the example above, the copy function is used to copy actual data from an InfoCube to a real-time InfoCube. In this case, you set not only the version, but also the InfoProvider characteristic as the characteristics to be changed. No condition characteristics are configured in the example above. The parameter records contain the actual rules for the copy process. These are entered in the “From” field and “To” field. Note that the copy function is always set to overwrite the target data records if a planning function is executed more than once. It is possible to copy from a source characteristic to a target characteristic, target interval, hierarchy node, or variable. If you have defined multiple values at the same time for a sender characteristic and copied them to a characteristic value of a target characteristic, all sender data records are copied to the target value. You can decide whether to copy all key figures or only individual key figures. You must first save a planning function before you can execute it at a later point. You can always save the function even if it is not configured correctly. To check the consistency of a function, you can always choose “Check”.

© SAP AG

FSC800

9-25

SAP PORTUGAL | USO EXCLUSIVO | 2013 Revaluation Function

 SAP AG 2008

Plan data records are usually generated by copying the actual data or by copying one plan version to another and then changing the values. The revaluated data is then revised manually. Percentages and variables of percentages should be set as the revaluation factor. In the example above, a variable was set for the “Costs in statistics currency” key figure and a fixed percentage was set for the “Quantity in base units” key figure. The figure above shows a revaluation in which different percentages are to be used for the individual material groups. For this purpose, it is sufficient to create one function with various conditions for the individual material groups instead of several planning functions. This means that a material group is a condition characteristic. When the planning function is executed, the system checks the material groups in the filter and determines whether the material groups formulated in the condition of the function are also contained in the filter. It then executes the planning function for the individual conditions. In this case, only key figures of existing data records are modified, so that no characteristic can be selected as a characteristic to be changed. You can select whether you want to enter a general percentage for all key figures or revaluate any number of key figures with individual percentages.

© SAP AG

FSC800

9-26

SAP PORTUGAL | USO EXCLUSIVO | 2013 Repost Function

Old model of a product is discontinued Plan data exists on the old model

Writing negative delta records

Reposting planned values to new product Writing positive delta records

 SAP AG 2008

You can use the Repost function type to post the key figure values of existing characteristic combinations to other combinations (in a similar way to Copy). Unlike copying, this function writes credit lines that are cleared in full with the original debit in the buffer. You generally use this function to correct an account assignment error. You can use the key figure selection table to specify which key figures are to be reposted. You can use the From-Value and To-Values for Repost Procedure table to create one simple reposting transaction or several reposting transactions within one planning function. The following rules apply: • Both the from-value and the to-values of the repost procedures must be single values. • Both the from-values and to-values are changed and must therefore be contained in the filter that is transferred to the planning function. • When values are reposted, the key figure values are always added to the to-values.

© SAP AG

FSC800

9-27

SAP PORTUGAL | USO EXCLUSIVO | 2013 FOX Formula Editor

Access statements for data records

Calculations

Information derivation (variables)

String operations

FOX formulas

Call ABAP function modules

Functions with predefined business logic (for example, linear regression)

Different types of loops Do loops Programming variables

 SAP AG 2008

You can use the function type formula (FOX = Formula Extension) to apply advanced mathematical functions to calculate plan data. No ABAP knowledge is required. The system generates ABAP coding from FOX coding and this is executed at runtime.

© SAP AG

FSC800

9-28

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing the FOX 1/4

 SAP AG 2008

The figure above and the following three figures show how to create a formula using the editor. As you can see, data must be calculated for characteristic Z_PRODUCT for one specific year only, namely 2009.

© SAP AG

FSC800

9-29

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing the FOX 2/4

{SEMPS_003, Mango Juice}

= {SEMPS_003, Apple Juice} + …

“Transfer”

Specify the combination of the next pair {key figure, characteristic attribute}, then choose “Transfer” again.

Control line of the InfoObjects that can be changed and used to build the formula.

 SAP AG 2008

The calculation for the Z_PRODUCT characteristic is carried out in combination with the key figure(s) of the aggregation level that are provided here in the “Key Figure” area. As you can see, the key figure field is always part of the formula to be created. An expression in brackets (that is, the operand, as seen in the formula editor area in the top-left of the screen) describes the formula components that logically belong together: Operand: {characteristic 1, ..., characteristic n, key figure}. The characteristic attribute(s) of the expression in brackets result from the characteristics recorded in the previous figure in the “Changed” area and the characteristic attributes defined in the characteristics text input help in the figure above. You can choose “Transfer” to transfer the combination of characteristic attribute(s)/key figure(s) required by the formula to the editor. You can then transfer the formula components that are required for the formula to the editor in the same way. If a statement is completed, you must enter a period (.). In the bottom area of the editor, the system displays the structure of the objects summarized in logical parentheses under “Operand”.

© SAP AG

FSC800

9-30

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing the FOX 3/4

Reference characteristics in the FOX

Reference characteristics in the editor

 SAP AG 2008

The example above shows how reference data is to be integrated in the formula editor. The figure above shows only the technical settings. Business example: • Sales are determined from the plan quantity and the price, whereby sales and the quantity are in plan version 1 and the price is in the actual version 0. The version does not have to be identified as changeable but can be included in the reference characteristics area. • The selection can then later be set to version 1 in the filter to enable write access to this version. The reference version 0 can be entered directly in the formula as seen here: - Formula: {0REVENUE} = {0QUANTITY} * {0PRICE|0VERSION = 0}.

© SAP AG

FSC800

9-31

SAP PORTUGAL | USO EXCLUSIVO | 2013 Customizing the FOX 4/4 Creating a variable in the editor

FOX program elements

Result in the editor

 SAP AG 2008

The figure above shows how you should proceed if you want to use the programming elements of the FOX. The “Input Help for Further Program Elements” area is provided for this purpose. The figure above shows the terms that are possible in the FOX and explains, for example, how you can define a variable in the formula editor . Some elements are framed under “Program Elements” in the figure above. They show the terms that have been developed as part of BI Integrated Planning and that were not available in the previous BPS Planning. Note that the following financial functions can be built using the FOX: • Perpetual bond (via the program element PERP) • Currency translation (via the program element CURC) • Discounting (via the program element DISC) • Declining-balance method of depreciation (via program element DECD) • Straight-line method of depreciation (via program element DECL) You can also use the FOX to determine the date (via program element C2DATE), create a rounding function (program element ROUND), and read attributes and time-dependent attributes (via program element ATRV and ATRVT). You can also calculate data using time characteristics (program element TMVL). Note that “Exit” as a program element describes the termination criterion of the loop command.

© SAP AG

FSC800

9-32

SAP PORTUGAL | USO EXCLUSIVO | 2013 Planning Sequences

 SAP AG 2008

Planning sequences combine planning functions and filters, whereby a sequence can comprise one or more planning function-filter combinations. A planning sequence is mainly defined for three reasons: • To bundle several planning functions as one complex function and execute it automatically in one step • To test one or more planning functions at runtime • To execute a planning function or a sequence as a batch process as part of a process chain Within a sequence, a planning function/sequence combination is referred to as a “step”. For each step, the underlying aggregation level, filter, and planning function is always specified. You can use a planning sequence to bundle planning functions of different aggregation levels. You cannot attach one planning sequence to another.

© SAP AG

FSC800

9-33

SAP PORTUGAL | USO EXCLUSIVO | 2013 Executing a Planning Sequence at Runtime Execute the entire sequence

Execute one step of the sequence

Variables query

 SAP AG 2008

A planning sequence can be executed in various ways. If you want to execute the entire sequence, you should choose “Execute” on the top screen shown above. Then all of the steps in the sequence are executed one after the other. However, if you want to test only one step, select this step and choose “Execute” in the middle of the screen. If the planning functions contain input-ready variables, you can set these manually before executing the step and save the value combinations of the variables as variants. Variables can also be personalized. The figure above shows a variable for the revaluation factor within the revaluation function. If the sequence is executed, the data is modified and the result is written to the plan buffer. You write the modified transaction data from the buffer to the database by choosing “Save”.

© SAP AG

FSC800

9-34

SAP PORTUGAL | USO EXCLUSIVO | 2013 Saving Planning Sequences and Plan Data

Save the definition of the planning sequence

Save the data created by the sequence

 SAP AG 2008

Saving the definition of the sequence and saving the data in the provider are two completely separate actions. This means that saving data does not save the definition of the sequence and vice versa. When you leave the “Planning Sequences” tab page, you must save the definition or any changes to the definition of the planning sequence. Otherwise the data is lost. However, in accordance with the approach of the plan data buffer, you do not have to save the plan data when you leave the “Planning Sequences” tab page. The data is retained in the buffer for as long as the Planning Modeler is open. If you close the Planning Modeler without choosing “Save Plan Data”, you lose the plan data that was changed by the sequence.

© SAP AG

FSC800

9-35

SAP PORTUGAL | USO EXCLUSIVO | 2013 Trace Mode for Planning Functions

 SAP AG 2008

The trace mode allows you to obtain detailed information about which data objects were changed when a planning function was executed, as well as how the objects were changed. This means that you analyze the behavior of the planning function. This function is particularly useful if you set up new planning functions and parameter groups and want to check whether the function has the required effects on the data set. Planning functions are generally called and executed in blocks. In trace mode, you can see the blocks and their selection criteria. For each selected block, you can display the various views of the plan data using the four tab pages. This allows you to analyze the following: • Data before it is changed by the planning function • Data after it is changed by the planning function • Reference data that has been imported by the planning function • A view that compares the data records before and after execution on one screen. After the trace, you can save the traced data. The tracing of planning functions can be started in the Planning Modeler only.

© SAP AG

FSC800

9-36

SAP PORTUGAL | USO EXCLUSIVO | 2013 Relevant Settings in the BEx Query Designer for Planning 1/2

Reference data

Protection against manual planning Manual and automatic planning allowed

 SAP AG 2008

If you have defined a query in the InfoProviders mentioned above, you will find the Planning tab page under the Properties of structure elements (for example, in key figures or restricted key figures). You can use the options provided there to specify which structure elements are to be ready for input at the runtime of an input-ready query. For structure elements that are not to be input ready, you can also specify whether these elements are to be seen as reference data or should only be protected against manual entries. If the data is reference data, the structure elements are not protected by data locks for the exclusive access of one user because this data is used as a reference by many users. This is the standard default setting.

© SAP AG

FSC800

9-37

SAP PORTUGAL | USO EXCLUSIVO | 2013 Relevant Settings in the BEx Query Designer for Planning 2/2

 SAP AG 2008

You can also specify whether an input-ready query is to be started in change mode or display mode. You can find this property in the Query Properties on the Planning tab page. As soon as an element is set to “Planning” as shown on the previous slide, the “Start query in change mode” indicator is set and can be deselected later.

© SAP AG

FSC800

9-38

SAP PORTUGAL | USO EXCLUSIVO | 2013 Setting the Drilldown Properties of Rows and Columns 1/3

Drilldown is filled in the selection using transaction data Product group

Product

Amount

Alcohol

Wine

10

Alcoholfree

Juice

40

 SAP AG 2008

The figure above and the subsequent two figures show you how to configure the drilldown characteristics of the rows and columns drilldown area. All examples are based on the row drilldown. The column drilldown functions in the same way. In the figure above, Product Group and Product are drilldown characteristics. “Booked Values” means that only combinations of products and product groups for which transaction data already exists are displayed.

© SAP AG

FSC800

9-39

SAP PORTUGAL | USO EXCLUSIVO | 2013 Setting the Drilldown Properties of Rows and Columns 2/3

Drilldown is filled in the selection using master data

Product group

Product

Amount

Alcohol

Wine

10

Alcohol

Beer

20

Alcohol

Juice

30

Alcohol

Water

40

Alcohol-free

Wine

50

Alcohol-free

Beer

60

Alcohol-free

Juice

70

Alcohol-free

Water

80

 SAP AG 2008

If “Master data” is selected for drilldown characteristics, all characteristic attributes of the data range are displayed in the rows and/or columns, regardless of whether transaction data exists for the master data. If you include multiple characteristics in the drilldown, the query creates possible mathematical combinations for this data range.

© SAP AG

FSC800

9-40

SAP PORTUGAL | USO EXCLUSIVO | 2013 Setting the Drilldown Properties of Rows and Columns 3/3

If there are several characteristics, “business-related combinations” appear in the drilldown that result from the characteristic relationships defined in the Planning Modeler.

Product group

Product

Amount

Alcohol

Wine

10

Alcohol

Beer

20

Alcohol-free

Juice

30

Alcohol-free

Water

40

 SAP AG 2008

If "Characteristic Relationships" is selected for the drilldown characteristic, the query (both the input-ready query and the reporting query) displays all business-related combinations that result from the characteristic relationships maintained in the Planning Modeler. Note that possible mathematical combinations may be displayed in the query despite characteristic relationships being maintained in the Planning Modeler. This is the case if the “Master Data” indicator was set instead of “Characteristic Relationships” in the figure above.

© SAP AG

FSC800

9-41

SAP PORTUGAL | USO EXCLUSIVO | 2013 BI Integrated Planning: Summary

You are now able to: Describe the options and functions in BI Integrated Planning Create a simple planning application for liquidity planning and cash accounting

 SAP AG 2008

© SAP AG

FSC800

9-42

SAP PORTUGAL | USO EXCLUSIVO | 2013 Exercises Unit:

BI Integrated Planning

At the conclusion of these exercises, you will be able to: • Describe the options and functions in BI Integrated Planning • Create a simple planning application for liquidity planning and cash accounting • Your company introduces liquidity planning and cash accounting. Your project team wants to learn about the options and functions of BI Integrated Planning.

1-1 What is the transaction for calling the Planning Modeler?

1-2 From which SAP NetWeaver or SAP BW release is BI Integrated Planning available?

1-3 Create an aggregation level in the Planning Modeler based on your MultiProvider (TFSCGR##M FSC800 MultiProvider Group ##). Add the following characteristics to the aggregation level. Characteristic Calendar Year/Month Company Code Liquidity Item Amount Amount - Actual Currency Key Use the following values as the technical name and description for your new aggregation level: © SAP AG

FSC800

9-43

SAP PORTUGAL | USO EXCLUSIVO | 2013 TFSCGR##A FSC800 Aggregation Level Group ## (replace ## with your group number)

1-4 Create a filter for your new aggregation level. When doing so, restrict the company code to your company code AC## and the calendar year/month using a variable, which is interpreted when executed. Also restrict the InfoProvider in the filter to your real-time InfoCube (TFSCGR##P FSC800 InfoCube Plan Data Group ##). Assign the following name and description for your filter: TFSCGR##F FSC800 Filter Group ## (replace ## with your group number) Use the following variable to restrict the “Calendar Year/Month” characteristics: Calendar Year/Month (Single Value/Required Entry) 0PCALMON

1-5 Create a planning function of type “formula” at your aggregation level to transfer the data from the actual key figure to the key figure for planning and copy the data from the previous month. Select the following values as the technical name and description of the planning function: TFSCGR##F FSC800 Formula Function Group ## (replace ## with your group number) After you have made the settings, your formula should look like this: DATA PREVIOUS MONTH TYPE 0CALMONTH. DATA CURRENT MONTH TYPE 0CALMONTH. © SAP AG

FSC800

9-44

SAP PORTUGAL | USO EXCLUSIVO | 2013 PREVIOUS MONTH = VARV(0PCALMON). CURRENT MONTH = VARV(0PCALMON). PREVIOUS MONTH = TMVL(VORMONAT, -1). { 0AMOUNT, CURRENT MONTH, TFSCGR##P } = {0AMOUNT_A, PREVIOUS MONTH, TFSCGR##I }.

1-6 You now want to increase the plan value by a specific factor. To do so, create a planning function of type “Revaluate” at your aggregation level. Select the following values as the technical name and description of the planning function: TFSCGR##U FSC800 Revaluation Function Group ## (replace ## with your group number) Specify the percentage for the revaluation using the following variable: TFSC800FAKT FSC800 Revaluation Factor

1-7 Merge the two planning functions into one planning sequence. In the planning sequence, first execute the formula function and then the revaluation function. Assign the following technical name and description for your planning sequence: TFSCGR##F FSC800 Planning Sequence Group ## (replace ## with your group number)

© SAP AG

FSC800

9-45

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-8 In the new planning sequence, execute the formula function and then the revaluation with a trace and see how the data is changed. Save the new plan data.

1-9 View the new data records in your strategic InfoCube using the Data Warehousing Workbench (optional).

1-10 Create an input-ready query for the data entry. Use the aggregation level you created as the basis for your input-ready query. TFSCGR##A “FSC800 Aggregation Level Group ##” The query should be structured as follows: •

Characteristic restrictions: Use the filter you defined for the characteristic restrictions.

TFSCGR##F FSC800 Filter Group ## (replace ## with your group number) •

Default values:

Restrict the “currency” characteristic to the value “EUR”. •

Columns

Include the “Amount - Actual” key figure in the columns. In the properties of the key figure, change the input readiness on the “Planning” tab page: “Data can be changed by user entries or planning functions only” Also drag the “Currency” characteristic to this area. © SAP AG

FSC800

9-46

SAP PORTUGAL | USO EXCLUSIVO | 2013 •

Rows

Add the liquidity item to the rows. Display the long text and key for the liquidity item. The liquidity items must be displayed based on the Cash Flow FSC800 hierarchy. On the “Advanced” tab page, also ensure that not only the posted values but all master data values are displayed. Select “Master Data” as the access type for the results. For “Filter Value Table for Query Execution”, also choose “Values in Master Data Table”. Also make these changes for the “Unit” characteristic. Save your query in “Favorites” with the technical name FSC800GR##QUERY2 and the description FSC800 Group ## Query 2

1-11 Execute the query, enter the plan values, and save the values.

© SAP AG

FSC800

9-47

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

9-48

SAP PORTUGAL | USO EXCLUSIVO | 2013 Solutions Unit:

BI Integrated Planning

1-1 What is the transaction for calling the Planning Modeler? The transaction code for calling the Planning Modeler is “RSPLAN”.

1-2 From which SAP NetWeaver or SAP BW release is BI Integrated Planning available? BI Integrated Planning is available as of Release SAP NetWeaver 2004s or SAP BW 7.0

1-3 Create an aggregation level in the Planning Modeler based on your MultiProvider (TFSCGR##M FSC800 MultiProvider Group ##). Call the Planning Modeler from the SAP Easy Access Menu as follows: “Information Systems” “Business Information Warehouse” “Business Planning and Simulation” “BI Integrated Planning” The transaction code for the Planning Modeler is “RSPLAN”. In the transaction, choose “Start Modeler”. The Planning Modeler is then started in a new Internet Explorer window. Log on to the Planning Modeler with your user and password. The Planning Modeler first displays the “InfoProvider” tab page, where you should search for your MultiProvider. To do so, enter the technical name or description of your MultiProvider in the “Search String” field: TFSCGR##M or FSC800 MultiProvider Group ## (replace ## with your group number)

© SAP AG

FSC800

9-49

SAP PORTUGAL | USO EXCLUSIVO | 2013 Select your MultiProvider and switch to the “Aggregation Levels” tab page. Then choose “Create” to create a new aggregation level. Assign the following values as the technical name and description: TFSCGR##A FSC800 Aggregation Level Group ## (replace ## with your group number) Confirm your entries by choosing “Transfer”. Note: The technical name of the aggregation level must contain at least three characters and no more than nine characters. In the lower part of the screen, select the characteristics and key figures for which planning should be executed. To do so, set a checkmark in the “Used” column for the following characteristics: Characteristic Calendar Year/Month Company Code Liquidity Item Amount Amount - Actual Currency Key

Check, save, and activate your aggregation levels using the corresponding pushbuttons.

© SAP AG

FSC800

9-50

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-4 Create a filter for your new aggregation level. When doing so, restrict the company code to your company code AC## and the calendar year/month using a variable, which is interpreted when executed. Also restrict the InfoProvider in the filter to your real-time InfoCube (TFSCGR##P FSC800 InfoCube Plan Data Group ##). Select the “Filter” tab page in the Planning Modeler. Create a new filter for your aggregation level by choosing “Create”. If your aggregation level is not selected automatically, select it manually in the “Aggregation Level Selection” area: TFSCGR##A FSC800 Aggregation Level Group ## (replace ## with your group number)

Use the following values as the technical name and description: TFSCGR##F FSC800 Filter Group ## (replace ## with your group number) Confirm your entries by choosing “Transfer”. In the lower area of the screen, select a characteristic and restrict it to the relevant date period. Restrict the “Company Code” characteristic to your company code. To do so, select the “Company Code” characteristic from the dropdown list in the lower area of the screen. Then choose “Add” to add the characteristic to the filter. After you have added the characteristic to the filter, use the input help to restrict the company code to your company code. AC## (replace ## with your group number)

Specify the company code in the value field and choose “Enter”. Alternatively, you can select the company code from the input help and copy it to your selection by choosing “Add”. Confirm your entries by choosing “OK”.

© SAP AG

FSC800

9-51

SAP PORTUGAL | USO EXCLUSIVO | 2013 You also want to restrict the calendar month using a variable. To do so, select the “Calendar Year/Month” characteristic from the dropdown list in the lower area of the screen. Then choose “Add” to add the characteristic to the filter. Then switch the view in the input help to “Variables”. Select the variable Calendar Year/Month (Single Value/Required Entry) 0PCALMON and add the variable to the list of “Chosen Selections” by choosing “Add”. Confirm your entries by choosing “OK”. Since only the InfoCube TFSCGR##P FSC800 InfoCube Plan Data Group ## (replace ## with your group number) is identified as a real-time InfoCube, you should also restrict this in your filter, that is, actual data should be read as reference data. You should therefore select the “InfoProvider” characteristic from the dropdown list in the lower area of the screen. Then choose “Add” to add the characteristic to the filter. After you have added the characteristic to the filter, use the input help to restrict the InfoProvider to the value specified above. Click your InfoProvider for plan data in the input help and add it to the “Chosen Selections” by choosing “Add”. Check and save the changes you have made to the filter.

1-5 Create a planning function of type “formula” at your aggregation level to transfer the data from the actual key figure to the key figure for planning and copy the data from the previous month. Select the “Planning Functions” tab page in the Planning Modeler. Create a new planning function for your aggregation level by choosing “Create”. If your aggregation level is not selected automatically, select it manually in the "Aggregation Level Selection” area: TFSCGR##A FSC800 Aggregation Level Group ##

© SAP AG

FSC800

9-52

SAP PORTUGAL | USO EXCLUSIVO | 2013 (replace ## with your group number)

Select “Formula” from the dropdown list as the type of planning function. Select the following values as the technical name and description of the planning function: TFSCGR##F FSC800 Formula Function Group ## (replace ## with your group number) Confirm your entries by choosing “Transfer”. The formula must now be maintained in the formula editor. Now switch to the characteristic usage (choose “Characteristic Usage”). Now select the “Calendar Year/Month” and “InfoProvider” characteristics as characteristics to be changed (set a checkmark in the “Changed” column). Then switch back to the formula editor (choose “To Parameters”). Since you do not want to transfer the plan values from the current period, you must use the (program) variables in the formula editor and determine the selection for the actual values using an offset function. To do so, expand the “Statements” hierarchy node in the program elements area and choose “DATA”. Enter PREVIOUS MONTH as the name and 0CALMONTH as the data type. Choose “Transfer” in the “Input Help for Further Program Elements” area. You have now created a program variable. Next, create a program variable for the current month. To do so, proceed as described above. Enter the following value as the name of the program variable:

© SAP AG

FSC800

9-53

SAP PORTUGAL | USO EXCLUSIVO | 2013 CURRENT MONTH You now have to assign the value of your filter variables to the program variables for the previous month. To do so, enter your program variable in the next row, followed by an equals (=) sign. PREVIOUS MONTH = Then choose the “VARV” command from the program elements. You can find this command under the “Variable” hierarchy code. Use the input help to select the relevant variable Calendar Year/Month (Single Value/Required Entry) 0PCALMON Choose “Transfer” in the “Input Help for Further Program Elements” area. Add a period (.) after your statement. Carry out the same steps for your program variable CURRENT MONTH. Now fill the program variable for the previous month with an offset of “-1”. To do so, enter your program variable in the next row again, followed by an equals (=) sign. PREVIOUS MONTH = Now expand the “Characteristics and Attributes” hierarchy node in the program elements area and choose “TMVL”. Choose “Transfer” in the “Input Help for Further Program Elements” area. You have now added a statement to the formula editor. Replace the placeholder with the value “PREVIOUS MONTH” and the placeholder with the value “-1”. Add a period (.) after your statement. PREVIOUS MONTH = TMVL (PREVIOUS MONTH, -1). You now want to add the actual value assignment to the formula editor. Use the “Input Help for Operands” to avoid incorrect entries. In this area, select the input help for the key figure and select the “Amount” key figure from the selection list. Then choose “DATA” in the row with the “Calendar Year/Month” characteristic and select your program variable: CURRENT MONTH © SAP AG

FSC800

9-54

SAP PORTUGAL | USO EXCLUSIVO | 2013 Then use the input help to restrict the InfoProvider to the characteristic value TFSCGR##P FSC800 InfoCube Plan Data Group ## (replace ## with your group number) Transfer your selection by choosing “Transfer” in the “Input Help for Operands” area. Insert an equals (=) sign after the operand. In the input help for key figures, select the “Amount – Actual” key figure and then choose “DATA” to restrict the “Calendar Year/Month” to your program variable: PREVIOUS MONTH Change the selection for the InfoProvider to your actual data InfoCube TFSCGR##I FSC800 InfoCube Actual Data Group ## (replace ## with your group number) and transfer your selection by choosing “Transfer” in the “Input Help for Operands” area. Insert a period (.) after the second operand. Your formula should now look like this: DATA PREVIOUS MONTH TYPE 0CALMONTH. DATA CURRENT MONTH TYPE 0CALMONTH. PREVIOUS MONTH = VARV(0PCALMON). CURRENT MONTH = VARV(0PCALMON). PREVIOUS MONTH = TMVL(VORMONAT, -1). { 0AMOUNT, CURRENT MONTH, TFSCGR##P } = {0AMOUNT_A, PREVIOUS MONTH, TFSCGR##I }. Choose “Check Formula” to validate your entries. Save your entries by choosing the relevant pushbutton. © SAP AG

FSC800

9-55

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-6 You now want to increase the plan value by a specific factor. To do so, create a planning function of type “Revaluate” at your aggregation level. Select the “Planning Functions” tab page in the Planning Modeler. Create a new planning function for your aggregation level by choosing “Create”. If your aggregation level is not selected automatically, select it manually in the "Aggregation Level Selection” area: TFSCGR##A FSC800 Aggregation Level Group ## (replace ## with your group number)

Select “Revaluation” from the dropdown list as the type of planning function. Select the following values as the technical name and description of the planning function: TFSCGR##U FSC800 Revaluation Function Group ## (replace ## with your group number) Confirm your entries by choosing “Transfer”. Specify the percentage for the revaluation using the following variable: TFSC800FAKT FSC800 Revaluation Factor To do so, select this variable from the input help. Check and save your planning function using the corresponding pushbuttons.

© SAP AG

FSC800

9-56

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-7 Merge the two planning functions into one planning sequence. In the planning sequence, execute the formula function and then the revaluation function. Select the “Planning Sequences” tab page in the Planning Modeler. Create a new planning sequence by choosing “Create”. On the following maintenance screen, assign the following technical name and description for your planning sequence: TFSCGR##F FSC800 Planning Sequence Group ## (replace ## with your group number) Confirm your entries by choosing “Transfer”. Add the formula function as the first step by choosing “Add step for planning function” to the planning sequence. If your aggregation level is not selected automatically, select it manually using the input help in the lower area of the screen: TFSCGR##A FSC800 Aggregation Level Group ## (replace ## with your group number) In the Filter field, select the filter created for your aggregation level: TFSCGR##F FSC800 Filter Group ## (replace ## with your group number). In the “Planning Function” field, select the formula function that was created for your aggregation level: TFSCGR##F FSC800 Formula Function group ## (replace ## with your group number)

In an additional step, insert the revaluation function you created by choosing “Add step for planning functions” again in the planning sequence. In the “Filter” field, select the filter created for your aggregation level: TFSCGR##F FSC800 Filter Group ## © SAP AG

FSC800

9-57

SAP PORTUGAL | USO EXCLUSIVO | 2013 (replace ## with your group number) In the “Planning Function” field, select the revaluation function that was created for your aggregation level: TFSCGR##U FSC800 Revaluation Function Group ## (replace ## with your group number) Save your planning sequence after you have selected the revaluation function (choose “Save” in the upper area of the maintenance screen).

1-8 In the new planning sequence, execute the formula function and then the revaluation with a trace and see how the data is changed. Save the new plan data. After you have saved your planning sequence, an additional area for entering variables appears in the lower area of the screen. Select a calendar month from the input help, which you know follows a month with actual data in your actual data InfoCube. Do not change the variable for the revaluation from the default value. Select the first step of your planning sequence and choose “Execution with trace”. An additional “Execution” area will appear below the variable area. Select a row with a block number in this screen area. In the detail area, you can trace the changes to the data records for this block number. In the second step, select your planning sequence and choose “Execution with trace”. To display the changes to the data after this step, proceed as described above. Save your plan data by choosing “Save Plan Data” in the “Execution” screen area.

1-9 View the new data records in your strategic InfoCube using the Data Warehousing Workbench (optional). To do so, return to the Data Warehousing Workbench. In the Data Warehousing Workbench, navigate to the InfoArea for your group in the InfoProvider tree. To do so, follow the path: © SAP AG

FSC800

9-58

SAP PORTUGAL | USO EXCLUSIVO | 2013 “Modeling”

“Data Warehouse Workbench: Modeling”

“InfoProvider” “BW Training T_BW” “BW Customer Training T_BW_CUST” “T_FSC800

T_FSC800”

“T_FSC800_GR## T_FSC800_GR##” Select your “FSC800 InfoCube Plan Data Group ##” InfoCube with the secondary mousebutton and select “Display Data”. On the screen that appears, choose “Fld Selectn for Output”. On the following screen, select “Highlight all key figs” and “Select All Characteristics”. Choose “Execute” (F8) and then “Execute” again (F8). Check the new data.

1-10 Create an input-ready query for the data entry. Call Business Explorer Analyzer. To do so, choose the following path: “START” “Programs” “Business Explorer” “Analyzer”

Create a new query by choosing “Bex Analyzer” -> “Tools” -> “Create New Query”. Select the training system from the list and log on to the system. Create a new query by choosing “New Query”. Switch to the InfoAreas view by choosing “InfoAreas” in the “Search In” field. Navigate to your aggregation level: “BW Training” “BW Customer Training” “T_FSC800” “T_FSC800_GR##” “FSC800 Aggregation Level Group ##” TFSCGR##A © SAP AG

FSC800

9-59

SAP PORTUGAL | USO EXCLUSIVO | 2013 Select your aggregation level and choose “Open”. The dimensions, key figures, and characteristics of your aggregation level are displayed on the left side of the screen. Expand the “Filter” node and select the filter that is defined in the Planning Modeler for your aggregation level. Move the filter to the “Characteristic Restrictions” area using drag and drop. Switch to the “Rows/Columns” view and drag the “Amount” key figure to the “Columns” area. Change the readiness for input in the properties of the key figure on the “Planning” tab page: “Data can be changed by user entries or planning functions only” Next, expand the “Unit” dimension and drag the “Currency” characteristic to “Columns”. Restrict the characteristic to the value “EUR” using the default values (to so, you must switch back to the “Filter” view). The “Liquidity Item” characteristic still had to be included in the query. To do so, drag it from “Non-Time-Based Dimension 2” to “Rows/Columns”. In the properties of the liquidity item, then change the display of the liquidity item on the “Properties” tab page. Under “Display as”, choose “Text and Key” and select “Long Text” as the “Text View”. We also want to display the liquidity items as a hierarchy. To do so, choose the “Hierarchy” tab page in the “Properties” area and use hierarchy name:

to select the

Cash Flow FSC800

On the “Advanced” tab page, also ensure that not only the posted values but all master data values are displayed. Select “Master Data” as the access type for the results. For “Filter Value Table for Query Execution”, also choose “Values in Master Data Table”. Also make these changes for the “Unit” characteristic. Save your query in “Favorites” with the technical name FSC800GR##QUERY2 and the description FSC800 Group ## Query 2 © SAP AG

FSC800

9-60

SAP PORTUGAL | USO EXCLUSIVO | 2013 1-11 Execute the query, enter the plan values, and save the values. If BEX Query Designer is still active, execute your query by choosing the green checkmark. In this case, ignore the following instructions. --------------------------------------------------------------------------------------------------------Call Business Explorer Analyzer again via the program menu. To do so, choose the following path: “START” “Programs” “Business Explorer” “Analyzer” Choose “BEx Analyzer” and select “Open Query”. Select your query from the “History” and choose “Open”. --------------------------------------------------------------------------------------------------------Restrict the calendar month on the variables screen. Use the input help if required. Confirm your entries by choosing “OK”. Specify the plan values for a liquidity item and select “Copy Values” from the dropdown menu (for example, on any field that is ready for input) to calculate the total nodes. Choose “Save Values” to update the data in the database.

© SAP AG

FSC800

9-61

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

9-62

SAP PORTUGAL | USO EXCLUSIVO | 2013 Summary and Outlook

Contents: Summary of SAP Liquidity Planner Outlook: further business requirements of SAP Liquidity Planner

 SAP AG 2008

© SAP AG

FSC800

10-1

SAP PORTUGAL | USO EXCLUSIVO | 2013 LP in FSCM: Objectives

At the conclusion of this unit, you will be able to: Provide a summary of SAP Liquidity Planner Formulate future requirements for SAP Liquidity Planner

 SAP AG 2008

© SAP AG

FSC800

10-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 Summary: MAP – FSCM Solution

 SAP AG 2008

The task of Treasury and Risk Management is to manage financial transactions and positions and provide methods and procedures for assessing risk positions. The task of Cash and Liquidity Management (note: SAP Liquidity Planner corresponds to Liquidity Management) is to provide functions for efficient short-, medium-, and long-term liquidity analysis, and planning.

© SAP AG

FSC800

10-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 Summary: Interaction Between "Treasury" Components Corporate Headquarter – Treasury Risk Management Credit Risk Analyzer

Derivative

Market Risk Analyzer

Money market

Foreign exchange

Portfolio Analyzer

Loans

Security

Transaction Manager

In-House Cash

Liquidity Planner Cash Management

IHC

CM

Cash and Liquidity Management

LP

Unit 1

IHC

Data of transaction systems

CM

LP

Unit 2

IHC

Bank data

CM

LP

Unit 3

 SAP AG 2008

The most important reporting tasks of Cash Management are to provide: • A value date-dependent cash position • A liquidity forecast The Reporting tasks of SAP Liquidity Planner are to provide: • Retrograde liquidity analysis • Liquidity planning

© SAP AG

FSC800

10-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 Summary: How Cash Management and Liquidity Planner Differ Cash Management

Liquidity Planner

Opening balance

Opening balance

Revenue

Revenue Customer group X

Revenue from sales

Customer group Y

Interest earnings

...

Other revenue

Expenditure

Expenditure

Vendor group X

Personnel

Vendor group Y

Materials

...

Assets ... Closing balance

Closing balance

 SAP AG 2008

The key difference is that Cash Management shows the cash flows of the customer and vendor side in the liquidity forecast ("to whom" or "from whom"). The Liquidity Planner shows cash flows according to funds utilization or origin ("for what").

© SAP AG

FSC800

10-5

SAP PORTUGAL | USO EXCLUSIVO | 2013 Summary: SAP Liquidity Planner •

SAP Liquidity Planner provides: Retrograde determination of cash flows Determines their medium- to long-term planning

•

SAP Liquidity Planner (SAP Liquidity Management) consists of two components: Actual Calculation in ERP Planning in BI

•

Reporting for actual and plan data is carried out in SAP Business Warehouse (BI).

 SAP AG 2008

It is important to note that SAP Liquidity Planner comprises two components: • Actual Calculation • Planning and Reporting in BI

© SAP AG

FSC800

10-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 Summary: System Architecture

BI Reporting

Planning

Database

Extraction

ERP Operational ERP

Operational ERP

 SAP AG 2008

Actual data is determined in operational ERP systems through "actual" calculation. The results are extracted to BI and made available for reporting. Planning is carried out in BI and the data can also be used here for reporting. You can compile various reports in BI: plan-plan comparisons, plan-actual comparisons, variance analyses, and many more.

© SAP AG

FSC800

10-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 Outlook: SAP Liquidity Planner Business requirements: Integration of commitments in cash accounting and liquidity planning, for example: From MM, SD, FI, and Treasury Management

Display of external and internal cash flows Display of segment cash flows Display of profit center cash flows Integration in other business plans

 SAP AG 2008

In the long term, it is expected that the SAP content of SAP Liquidity Planner will be enhanced.

© SAP AG

FSC800

10-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 Literature

Geupert, F.: Cash Flow Accounting, Bamberg 2003 Kerber, S.; Warntje, D.: Cash Accounting and Cash Flow Planning with SAP Liquidity Planner, Bonn, 2005 (SAP Press) Kerber, S; Warntje, D.: Cash Accounting and Cash Flow Planning with SAP Liquidity Planner, Bonn, 2005 (SAP Press) Bieber, R; Kerber, S.: Cash Management mit dem FSCM, Bonn, 2006 (SAP Press)

 SAP AG 2008

© SAP AG

FSC800

10-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 LP in FSCM: Summary

You are now able to: Provide a summary of SAP Liquidity Planner Specify the future business requirements of SAP Liquidity Planner.

 SAP AG 2008

© SAP AG

FSC800

10-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 Appendix

 SAP AG 2008

© SAP AG

FSC800

Appendix-1

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

Appendix-2

SAP PORTUGAL | USO EXCLUSIVO | 2013 For Unit 6

 SAP AG 2008

© SAP AG

FSC800

Appendix-3

SAP PORTUGAL | USO EXCLUSIVO | 2013 Architecture of the BI Platform Services and Warehouse Components

Aggregation

Security

Analysis Process Design

Planning Services

Planning Functions and Planning Sequences

Data Warehouse Operational Data Store (NonPermanent)

Architected Data Marts Data Warehouse Layer (Historical)

Open Hub Service

Monitoring / Administration

InfoObjecs / Master Data

Metadata Repository / Documents

BI Accelerator

Analytic Engine Calculations Caching

Control of Data Flow / Process Chain

Business Explorer Suite (BEx)

DataSource PSA Data Retrieval

 SAP AG 2008

Physical data storage in • Operational Data Store • Data Warehouse Layer • Architected Data Marts The Persistent Staging Area (PSA) • Data storage and processing to support data transformation • Usually temporary • Not set up for end user or tool access • Designed especially to provide work center (or temporary) memory space for ETL processing

© SAP AG

FSC800

Appendix-4

SAP PORTUGAL | USO EXCLUSIVO | 2013 Data Retrieval

DataSource/Persistent Staging Area DB Connect

UD Connect

BI Service API

File interface

Web service

BAPI not available for SAP NetWeaver 2004s DataSource BAPI

ELT tool Relational source For example, IBM DB2, Teradata

Multidimensional source For example, Hyperion

SAP source For example, SAP CRM

File For example, CSV

XML Usually from Internet-based applications

Legacy applications For example, Oracle Financials

Source system types

 SAP AG 2008

© SAP AG

FSC800

Appendix-5

SAP PORTUGAL | USO EXCLUSIVO | 2013

© SAP AG

FSC800

Appendix-6

SAP PORTUGAL | USO EXCLUSIVO | 2013 For Unit 7

 SAP AG 2008

© SAP AG

FSC800

Appendix-7

SAP PORTUGAL | USO EXCLUSIVO | 2013 Data Flow – Company Text BW

Company InfoSource for direct update of master data Transfer structure and transfer rules DataSource replica

DataSource

From company for &logical system& 0COMPANY_TEXT

Company

0COMPANY_TEXT

R/3 Company

 SAP AG 2008

Medium-length, non-language-dependent text From table T880

© SAP AG

via View

BIW_T880T

FSC800

Appendix-8

SAP PORTUGAL | USO EXCLUSIVO | 2013 Data Flow – Line Item Type Text BW

InfoSource for direct update of master data

Line item type

Transfer structure and transfer rules DataSource replica

DataSource

From line item types for &logical system& 0LQTYPE_TEXT

0LQTYPE_TEXT

Cash accounting: Type of line items

R/3 Cash accounting: Type of line items

 SAP AG 2008

Language-dependent long text From the FLQTYPE domain in SAP R/3

© SAP AG

FSC800

Appendix-9

SAP PORTUGAL | USO EXCLUSIVO | 2013 Data Flow – Country Key Text BW

InfoSource for direct update of master data

Country key

Transfer structure and transfer rules DataSource replica

DataSource

From country for &logical system& 0COUNTRY_TEXT

Country

0COUNTRY_TEXT

R/3 Country

 SAP AG 2008

Language-dependent short text From table T005T

© SAP AG

via the view BWV_T005T

FSC800

Appendix-10

SAP PORTUGAL | USO EXCLUSIVO | 2013 Extractor Types

Extractor Types Application-Specific

Application-Independent

BW Content Extractors

Customer-Specific Extractors

Generic Extractors

FI HR CO SAP CRM LO Cockpit

LIS

DB-View

CO-PA

Function Module

ApplicationSpecific DB Tables

ApplicationSpecific DB Tables

Various SAP DB Tables

FI-SL

InfoSet

 SAP AG 2008

You will find the DataSources in an SAP source system in transaction SBIW. This transaction contains a menu option for transferring the application component hierarchy. The application component hierarchy structures the DataSources in the source system. DataSources must then be activated. The following slides show you where you can find the necessary DataSources for liquidity planning and cash accounting in the application component hierarchy.

© SAP AG

FSC800

Appendix-11

SAP PORTUGAL | USO EXCLUSIVO | 2013 Application Component Hierarchy – Liquidity Planning SAP SAP

Application component SAP R/3 SAP application components

DataSource

… … TR Treasury TR-LP Liquidity planning TR-LP-IO Liquidity planning master data 0LQTYPE_TEXT Cash accounting: type of line item 0TR_LP_1 Liquidity planning … … … …  SAP AG 2008

© SAP AG

FSC800

Appendix-12

SAP PORTUGAL | USO EXCLUSIVO | 2013 Application Component Hierarchy – Financial Accounting SAP SAP

Application component

SAP R/3 SAP application components

DataSource

… … FI Financials … … FI-IO

General Financial Accounting master data

… …

0COMPANY_TEXT Company 0COMP_CODE_TEXT Company code 0COMP_CODE_ATTR Company code

0BUS_AREA_TEXT Business area 0BUS_AREA_ATTR Business area

… …  SAP AG 2008

© SAP AG

FSC800

Appendix-13

SAP PORTUGAL | USO EXCLUSIVO | 2013 Application Component Hierarchy – Country

Application component

SAP SAP

DataSource PI_BASIS PI-Basis … … 0CA_GD General DataSources

0CA_GD-IO General DataSources master data 0COUNTRY_TEXT Country … …

 SAP AG 2008

© SAP AG

FSC800

Appendix-14