Bw370.Ingr Plng1

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

%:��%,�LQWHJUDWHG SODQQLQJ

��

© SAP AG 2006

%:��%,�,QWHJUDWHG 3ODQQLQJ

�

� 2006/Q2

� Material number 50080002

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

&RS\ULJKW

&RS\ULJKW�� 6$3�$*��$OO�ULJKWV�UHVHUYHG�1R�SDUW�RI�WKLV�SXEOLFDWLRQ�PD\�EH�UHSURGXFHG�RU�WUDQVPLWWHG�LQ�DQ\�IRUP�RU�IRU�DQ\�SXUSRVH�ZLWKRXW�WKH�H[SUHVV�SHUPLVVLRQ�RI�6$3�$*��7KH�LQIRUPDWLRQ�FRQWDLQHG�KHUHLQ�PD\�EH�FKDQJHG�ZLWKRXW�SULRU�QRWLFH�

�

� Some software products marketed by SAP AG and its distributors contain proprietary software

components of other software vendors. �

Microsoft, Windows, 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

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

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

5HTXLUHG .QRZOHGJH�� %:��%,�± (QWHUSULVH�5HSRUWLQJ��4XHU\��$QDO\VLV�� %:��%,�± (QWHUSULVH�'DWD�:DUHKRXVLQJ�� %DVLF�.QRZOHGJH�RI�WKH�3ODQQLQJ�3URFHVV

&RXUVH 3UHUHTXLVLWHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

7KLV�FRXUVH�LV�LQWHQGHG�IRU�WKH�IROORZLQJ�DXGLHQFH�� (PSOR\HHV�LQ�&RUSRUDWH�&RQWUROOLQJ�ZKR�DUH�LQYROYHG�LQ�

SODQQLQJ� 0HPEHUV�RI�WKH�SURMHFW�WHDP�DQG�FRQVXOWDQWV

'XUDWLRQ��GD\V

7DUJHW $XGLHQFH

�

� 8VHU�QRWHV�

• These training materials are not a WHDFK�\RXUVHOI�SURJUDP. They FRPSOHPHQW�WKH�H[SODQDWLRQ�SURYLGHG�E\�\RXU�FRXUVH�LQVWUXFWRU. Space is provided on each page for you to note down additional information.

• There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

%XVLQHVV�3ODQQLQJ�ZLWK�6$3�1HW:HDYHU�%,

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

&RXUVH�2YHUYLHZ

&RQWHQW�� &RXUVH�*RDOV� &RXUVH�2EMHFWLYHV� &RXUVH�&RQWHQW� 2YHUYLHZ�'LDJUDP� 0DLQ�%XVLQHVV�6FHQDULR

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

&RXUVH�*RDOV

7KLV�FRXUVH�ZLOO�SUHSDUH�\RX�WR�� +DYH�DQ�LQ�GHSWK�LQVLJKW�LQWR�%:�LQWHJUDWHG�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

&RXUVH�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�FRXUVH��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�WR�VHW�XS�D�SODQQLQJ�PRGHO� 8QGHUVWDQG�KRZ�D�SODQ�TXHU\�RU�D�ZHE�TXHU\�

LV�FUHDWHG� 8QGHUVWDQG�KRZ�WR�VHW�XS�SODQQLQJ�IXQFWLRQV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

Unit 7 &UHDWLQJ�DQG�8VLQJ�DQ�([FHO�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�WKH�%([$QDO\]HU

Unit 8 0RGHOLQJUnit 9 3ODQQLQJ�)XQFWLRQV�±

(QKDQFHPHQWUnit 10 3ODQQLQJ�6HTXHQFHV�Unit 11 &KDUDFWHULVWLF�5HODWLRQVKLSV�

DQG�'DWD�6OLFHVUnit 12 &UHDWLQJ�DQG�8VLQJ�D�

:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'

Unit 13 6WDWXV�DQG�7UDFNLQJ�6\VWHP

Unit 1 *HQHUDO�&RQFHSWV�DQG�&KDOOHQJHV�LQ�%XVLQHVV�3ODQQLQJ

Unit 2 &UHDWLQJ�D�6LPSOH�'DWD�0RGHO�ZLWK�'DWD�,QSXW

Unit 3 )LOWHUV�DQG�9DULDEOHV�LQ�%,�,QWHJUDWHG�3ODQQLQJ

Unit 4 3ODQQLQJ�)XQFWLRQV�±%DVLFV

Unit 5 &UHDWLQJ�D�3ODQ�4XHU\Unit 6 /RFNLQJ�&RQFHSW�IRU�

7UDQVDFWLRQ�'DWD

3UHIDFH

$SSHQGLFHV�

&RXUVH &RQWHQWV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

&RXUVH 2YHUYLHZ 'LDJUDP

8QLW��8QLW��

8QLW��8QLW��8QLW��8QLW��8QLW��8QLW��

8QLW��

*HQHUDO�&RQFHSWV�DQG�&KDOOHQJHV�LQ�%XVLQHVV�3ODQQLQJ&UHDWLQJ�D�6LPSOH�'DWD�0RGHO�ZLWK�'DWD�,QSXW)LOWHUV�DQG�9DULDEOHV�LQ�%,�,QWHJUDWHG�3ODQQLQJ3ODQQLQJ )XQFWLRQV %DVLFV&UHDWLQJ D�3ODQ�4XHU\/RFNLQJ�&RQFHSW�IRU�7UDQVDFWLRQ�'DWD&UHDWLQJ�DQG�8VLQJ�DQ�([FHO�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�WKH�%([$QDO\]HU0RGHOLQJ3ODQQLQJ )XQFWLRQV ± (QKDQFHPHQW3ODQQLQJ 6HTXHQFHV&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV&UHDWLQJ�DQG�8VLQJ�D�:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'6WDWXV�DQG�7UDFNLQJ 6\VWHP

8QLW��8QLW��8QLW��8QLW��

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

SAP AG 2006

0DLQ�%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�%,�LQWHJUDWHG�SODQQLQJ��ZKLFK�\RX�ILUVW�ZDQW�WR�VHW�XS�DV�SDUW�RI�D�1HWZHDYHUSURMHFW�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-1

SAP AG 2006

&RQWHQW�� 3ODQQLQJ�FRQFHSWV� %,�LQ�1HW:HDYHU��V� $GYDQWDJHV�RI�%,�LQWHJUDWHG�SODQQLQJ� %,�LQWHJUDWHG�SODQQLQJ�± SURFHVV�IORZ�YLHZ�RI�WKH�

SODQQLQJ�VWHSV� :ULWH�DFFHVV�IRU�SODQ�GDWD�LQ�WKH�%:

*HQHUDO�&RQFHSWV�DQG�&KDOOHQJHV�LQ�%XVLQHVV�3ODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-2

SAP AG 2006

*HQHUDO�&RQFHSWV�DQG�&KDOOHQJHV�LQ�%XVLQHVV�3ODQQLQJ��/HDUQLQJ�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG WKH EDVLF SODQQLQJ FRQFHSWV� 3RVLWLRQ�%,�LQ�1HW:HDYHU��V� 8QGHUVWDQG WKH�DGYDQWDJHV�RI�%,�LQWHJUDWHG�SODQQLQJ� 8QGHUVWDQG�WKH�SURFHVV�IORZ�YLHZ�RI�WKH�SODQQLQJ�

VWHSV�LQ�%,�LQWHJUDWHG�SODQQLQJ� 8QGHUVWDQG�WKH�ZULWH�DFFHVV�IRU�SODQ�GDWD�LQ�WKH�%:

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-3

SAP AG 2006

*HQHUDO�&RQFHSWV�DQG�&KDOOHQJHV�LQ�%XVLQHVV�3ODQQLQJ��&RXUVH�2YHUYLHZ�'LDJUDP



8QLW��8QLW��8QLW��8QLW��8QLW�� *HQHUDO�&RQFHSWV�DQG�&KDOOHQJHV�LQ�%XVLQHVV�3ODQQLQJ

&UHDWLQJ�D�6LPSOH�'DWD�0RGHO�ZLWK�'DWD�,QSXW)LOWHUV�DQG�9DULDEOHV�LQ�%,�,QWHJUDWHG�3ODQQLQJ3ODQQLQJ )XQFWLRQV %DVLFV&UHDWLQJ D�3ODQ�4XHU\/RFNLQJ�&RQFHSW�IRU�7UDQVDFWLRQ�'DWD&UHDWLQJ�DQG�8VLQJ�DQ�([FHO�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�WKH�%([ $QDO\]HU0RGHOLQJ3ODQQLQJ )XQFWLRQV ± (QKDQFHPHQW3ODQQLQJ 6HTXHQFHV&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV&UHDWLQJ�DQG�8VLQJ�D�:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'6WDWXV�DQG�7UDFNLQJ 6\VWHP

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-4

SAP AG 2006

*HQHUDO�&RQFHSWV�DQG�&KDOOHQJHV�LQ�%XVLQHVV�3ODQQLQJ��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�JHQHUDO�FRQFHSWV�DQG�FKDOOHQJHV�RI�SODQQLQJ�DQG��E\�GRLQJ�VR��SRVLWLRQ�%,�LQWHJUDWHG�SODQQLQJ�LQ�WKH�FRQWH[W�RI�1HW:HDYHU�

� ,W�LV�LPSRUWDQW�IRU�\RX�WR�ZRUN�RXW�ZKDW�DGYDQWDJHV�%,�LQWHJUDWHG�SODQQLQJ�FDQ�RIIHU�

� <RX�ZLOO�ILQG�RXW�DERXW�WKH�DUFKLWHFWXUH�RI�SODQQLQJ�DQG�WKH�VHTXHQFH�RI�SURFHVV�VWHSV�

� <RX�DUH�DOVR�LQWHUHVWHG�LQ�ZULWH�DFFHVV�DQG�VWRULQJ�WUDQVDFWLRQ�GDWD�LQ�WKH�%:�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-5

SAP AG 2006

� /HVVRQ��$GYDQWDJHV�RI�%,�,QWHJUDWHG�3ODQQLQJ�� /HVVRQ��%,�,QWHJUDWHG�3ODQQLQJ�± 3URFHVV�)ORZ�9LHZ�RI�WKH�3ODQQLQJ�6WHSV� /HVVRQ��:ULWH�$FFHVV�IRU�3ODQ�'DWD�LQ�WKH�%:

8QLW�2YHUYLHZ� /HVVRQ��3ODQQLQJ�&RQFHSWV� /HVVRQ��%,�LQ�1HWZHDYHU��V

3ODQQLQJ�&RQFHSWV��8QLW�2YHUYLHZ�'LDJUDP

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-6

SAP AG 2006

3ODQQLQJ�&RQFHSWV��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�EDVLF�SODQQLQJ�FRQFHSWV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-7

SAP AG 2006

3ODQQLQJ�&RQFHSWV��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�JHQHUDO�FRQFHSWV�DQG�FKDOOHQJHV�LQ�SODQQLQJ��

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-8

SAP AG 2006

0DQDJHPHQW�&\FOH

$QDO\VLV��H�J��SURILWDELOLW\��

3ODQQLQJ�VWUDWHJLF��RSHUDWLRQDO�

3ODQQLQJ�H[HFXWLRQ�

([HFXWLRQ

$QDO\VLV

2SHUDWLRQV

5HSRUWLQJ��SODQ�DFWXDO�

$QDO\]H 0RGHO

([HFXWH !

(QYLURQPHQW&RPSDQ\�PLVVLRQ

(YDOXDWH

�

� Planning is an integral part of the management cycle.

� Companies are situated in complex environments (competitive landscape, political situation,

geographical location…). Different companies follow different business models (such as public sector vs. private owned companies). Depending on their overall company goal (certain percentage of profitability, maximizing the public welfare…) they must consider the environmental situation in which they operate.

� The management cycle helps companies to position themselves in complex environments and to keep on

track in reaching their overall company goal. �

The company mission is the framework to which all the operations in the company are supposed to contribute.

� Planning supports decision making, the coordination of different divisions toward a common goal and

defines general conditions for operations. �

Execution involves all steps necessary for the actual value creation of the company. �

Reporting tracks all transactions incurred by the execution processes. �

Analysis focuses on calculating the success of objectives achieved and seeks out the reasons for any deviations.

� The result of the analysis is measured against the company mission and leads to an evaluation of overall

goals and actions to be taken in order to steer the course.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-9

SAP AG 2006

6WUDWHJLF��2SHUDWLRQDO�DQG�([HFXWLRQ�3ODQQLQJ

6WUDWHJLF�3ODQQLQJ- �� - �� !�� - "#�!� �� $%�� &$ �!� ��- "#�!� �� $��%��!'&�� ( �#��( �)��*� �� - +

([HFXWLRQ�3ODQQLQJ- ,#�� ( ��-��( �� . /)021�3- "�4��)5 ( ��67$ �� (- 1#� ��8�$��( �� - �2��$�� ( �� - �2�#��!� �$&��4��( � ��9+

t0 6:��'�; 6%��' < + ��!; ��=+6%��' >

?A@CB)D)E�F B)@ G HCI

( ��6

4�� 4

J)K B)F!E�BLHCM

2SHUDWLRQDO��3ODQQLQJ- "#�( � �*��( �� - 0#�&��8��)��( �� - ,#��-�( �� - "28��( *��( �� - 1�� 5 � ��( �� - �2��$&�� ( �� - "��!� � �� $*�� $�8� ��- +

N G OPM

QSR%T M%F!G!D%U

J*V M�W%E�HXMZY

�

� Business Planning covers different levels:

� Strategic planning is concerned with determining the direction of an enterprise’s future development; for

example the range of products and services, return on investment, company growth and so on. Strategic planning is a simulative process, where different scenarios are modeled and then evaluated to calculate the expected value creation. Strategy evaluation leads to setting targets for the operational units, which means breaking down the high-level strategic goals to targets on the execution level (for example, expected net revenue, sales growth rate and so on).

� Operational planning means allocating the resources (labor, capital, assets) necessary to fulfill the

targets, and reconciling the resources across operational units (the sales volume has to be reconciled with production volume, for example – if you have production capacity to produce 200 bottles of sunscreen per month but you can sell 1000 bottles in August, you must produce at least 800 bottles of sunscreen in the months prior to August....).

� The results of the operational planning process may be used for detailed planning and scheduling in

execution planning.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-10

SAP AG 2006

7RS�'RZQ�DQG�%RWWRP�8S

J DLHCM)@�[)@�G \�M

]-B)F ML\^7@_U%B)D�G `2BaH�G R D

"b�( ��)cd5 5 � $��

]-B)F Ma\^S@&U%B)D*G `2BLH�G R D

"b�( � �)cd5 5!� $�� "b�( ��)cd5 5 � $��

e @ R*T E%W�H�fgB�HXM�U R @hI

e @ R)T E%WaH Q B)G!D?S@ R E%[

e @ R)T E%WaH�?S@ R E*[ e @ R%T E%W�H�?7@ R E)[

e @ R%T E%WaH Q B)G!D?S@ R E%[

e @ R%T E:WaH�?S@ R E*[

e @ R)T E%W�H e @ R%T E%W�H

7RS�'RZQ

%RWWRP�8S

�

� Top-down and bottom-up are directions used to coordinate the vertical planning process. Usually these

directions follow hierarchical structures. �

Bottom up refers to the data flow from detail planning on different sublevels to an aggregated perspective.

� Top down is the opposite direction, where strategies and targets that were defined on higher levels are

translated to operational targets. �

The mixed top-down/bottom-up planning system is a combination of both. �

Different versions separate different plan assumptions and may be used to compare different perspectives (CFO – Sales representatives). The final version is usually the basis for execution planning (such as detailed scheduling).

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-11

SAP AG 2006

5ROOLQJ�3ODQQLQJ

��0RQWKV�)RUHFDVW

&XUUHQW�3HULRG�$FWXDO

��3HULRG�$FWXDO

)RUHFDVW�-XQH

0D\ -XQH-XO\

)RUHFDVW�0D\

)RUHFDVW�-XO\

�

� In the past, planning was very often a static process carried out once a year and intended as the basis for

action and the budget in the following years. �

Dynamic environments and fast changing business situations force companies to think of strategies to react to changing conditions. Buzzwords heard in this context are: beyond budgeting, better budgeting, active planning… .

� Usually these concepts evolve around the necessity for change management in regard to the planning

process and the people involved in it. Part of this change is the need for a constant process that allows companies to react to changes in their environments in a time.

� Rolling planning is an ongoing process that compares the plan values with the actual values and derives

an expected further evolution of the plan figures. If the deviation between the plan and the forecast exceeds a certain range, the strategy has to be reevaluated in order to take appropriate measures or adjust the strategy.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-12

SAP AG 2006

,PSDFW�RI�3ODQQLQJ�RQ�'DWD�9ROXPHi�jlkLmdnbo�p qgn#r2s�pht p!ui�jlkLmdn#o�p

v j!k:n2wx n�y#pzkL{}|ajx n�y�pzkd{~|aj v j!k:n�wi�|�jCt kLm��|�raj

qgn�ras�p_t p!ui�j!kLm�n#o�p v jlk�n2wx n�y#pzkd{~|aj v jlk:n�w�*|#raj

$FWXDOGDWD

3ODQ

i�jlkLmdnbo�p qgn#r2s�pht p!ui�j�kam:n�o�pv jlk�n2w

x n�y#pzkL{}|ajx n�y�pzkd{~|aj v j!k:n�wi�|�jCt kLm�*|#raj$FWXDOGDWD

qgn�ras�p_t p!u�)|aj yLt kdsx n�y#pzkL{}|aj v j�k�n2w�*|#raj3ODQ

��o�p_n�ra��m�r�p�r�t y~r��#rat � rb�a� |�r�pLrg�b|2j u}m�|�p�rat � |#m� |��b|�� hj�kL{�phjlras�ybr#o�pht k�s�mar�p�r��l��wa� ras�mar�plr��r�ypzkS�#|�o�jl|�r�pl|bm}y�pz|aw}��u�y�pX|2w��)��|�wa� ras�t y v |as�|aj!ra� � u�� |�y�y�ma|p�rat � |�m�ph�#r�sgph��|rbo�phn�ra�mar�p�r2�

��m�m:t pht k�s�ra��m�|�p�rat ��{}ru��#|�s�|bo�|�y#y�raj ug�zk:jwa� ras�s�t s v �!yLn�o��r�yg�b|aj yLt k:s�y2��%�at y�{}|�ras�y�pC��r�pph��|~m�r�p�r��2k�� nb{}|}{~r�u�t s�o�jl|�r�yb|2�

�

� Data volume increases in planning due to:

• Additional transactional cubes

• Additional data records (delta records)

• Additional detail level (such as version handling) �

However:

• Planning is usually done on a more aggregated level than actual reporting (a ship builder may plan by single customer, whereas a telecommunications company may plan by customer group only).

• Plan data is archived more often.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-13

SAP AG 2006

� ph�#|2ji�� ras�y� ph��|�ji�� ras�y

,QWHJUDWHG�3ODQQLQJ�ZLWK�6$3�1HW:HDYHU�%,

x-�)�

� p_��|�ji�� ras�y

x k2y#ply

i�j�k2�ht p��bk�y#yi�j!k��ht p�ra�at � t plu

6$3�1

HW:HDYHU�%

,2/

73

�:ra� ras�o�|� ��|�|�p

x r�yL��a� k2�

� p_��|�ji�� ras�y

,QWHJUDWLQJ 3ODQV 'HULYLQJ 3ODQV

x kby#plyi:jlkam:n�o�pht k:s

�)n�jzsbk#�b|�j

�:|b{}ras#m

,QWHJUDWHG�EXVLQHVV�SODQV�ZLWK�GHULYHG�SURILW�DQG�ORVV�VWDWHPHQWV��EDODQFH�VKHHWV�DQG�FDVK�IORZV�VXSSRUW�WKH�HQWHUSULVH�PDQDJHPHQW�

�

� BI integrated planning can be used (as shown in the diagram) to create process-oriented planning. The

SAP NetWeaver BI platform functions as the central layer for integrating all kinds of plans. �

The original plan data can come from either OLTP systems (operative plans) or from BI systems.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-14

SAP AG 2006

3ODQQLQJ�&RQFHSWV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�EDVLF�SODQQLQJ�FRQFHSWV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-15

SAP AG 2006


%,�LQ�1HWZHDYHU��V��8QLW�2YHUYLHZ�'LDJUDP


�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-16

SAP AG 2006

%,�LQ�1HWZHDYHU��V��/HVVRQ�2EMHFWLYHV

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 3RVLWLRQ�%,�LQWHJUDWHG�SODQQLQJ�LQ�WKH�FRQWH[W�

RI�1HW:HDYHU

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-17

SAP AG 2006

%,�LQ�1HWZHDYHU��V��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�ORRN�LQWR�WKH�SRVLWLRQLQJ�RI�%,�LQWHJUDWHG�SODQQLQJ�LQ�WKH�FRQWH[W�RI�1HW:HDYHU�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-18

SAP AG 2006

+RZ�6$3�1HW:HDYHU�%,�6XSSRUWV�%XVLQHVV�3ODQQLQJ

/RDG /RDG

6$3�1HW:HDYHU�%,

P\6$3�(53 P\6$3�6&0 P\6$3�&50 P\6$3�«

0DVWHU�GDWD!$FWXDO�GDWD

3UHSDULQJ�GDWD�IRUSODQQLQJ�SURFHVV

&ROODERUDWLYH�SODQQLQJWDVNV

1HZ�PDVWHU�GDWD%XGJHW�GDWD2SHUDWLRQDO�SURFHVV

%XGJHW�FRQWURO

$XWRPDWLFSODQQLQJ

�

� BI integrated planning is a part of SAP NetWeaver BI, which is SAP’s platform for business analysis.

� BI integrated planning is a generic planning tool that supports various types of strategic and operational

planning and allows planning at any level of detail. �

User interfaces and business rules may be defined to meet the needs of any type of plan when structuring a model in a company.

� BI integrated planning provides convenient and easy-to-use process support.

� BI integrated planning provides tools that close the gaps between operational processes by loading and

distributing from and to transactional systems.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-19

SAP AG 2006

� G \*ELB)Ff R O�[ R \�M%@¡ ~¢

£ G H

8',¤ � �#�� iqgn�|aj u ¥ �� x � �*� �

%XVLQHVV�([SORUHU�6XLWH��%([�

%([�4XHU\�'HVLJQHU

,QIRUPDWLRQ�%URDGFDVWLQJ

¦ M)§¨ DLB)F ILàM)@

¦ M)§¨ [)[)F!G WLBLH&G R D© M�\*G U�D�M)@

Q ] J%V WLM%F¨�T*T)ª ¢lD

« M%[ R @_H© ML\*G U-DdM)@

%([�:HE

,�¬��$&� BAPI ServiceAPI File XML/A

%([�$QDO\]HU �¢ e BLHCHCM)@�D

~¢�f R DL\*E�OM)@*]®M)@ K G WLML\

%,�3ODWIRUP

'DWD�:DUHKRXVH

(QWHUSULVH�3RUWDO

¨ DLB)F IaH�G W J D:U�G�DdM Q M�HhB © B�HhB Q U�@

£�Q

6$3�1HW:HDYHU�%,

e F B)D)D%GzDdUQSR*T M)F M%@

�

� In SAP NetWeaver, BI is the central integrated data storage area for information from distributed and

heterogeneous sources. Data can be collected from source systems and structured. Plans and analyses can be created on the basis of this data.

� Integrated planning is located in different areas:

• Data Warehouse: the plan data is stored in real-time InfoCubes in the Data Warehouse. Plan data can also be extracted and stored in the Data Warehouse or transferred on to other systems via retraction. Open Hub or XI in SAP NetWeaver provide further options for forwarding on data.

• BI Platform: the data model and planning functions are modeled for BI integrated planning in the Planning Modeler.

• Business Explorer Suite: the Business Explorer Suite contains the majority of the surfaces available for BI integrated planning. In addition to this, the Visual Composer is also available in SAP NetWeaver for building BI cockpits. Furthermore, plans can be distributed throughout the company using Information Broadcasting.

� Since BI is closely interlinked conceptually to SAP NetWeaver, all of SAP NetWeaver’s functions are

also available for planning.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-20

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-21

SAP AG 2006

%XVLQHVV�3ODQQLQJ�,QWHJUDWHG�LQWR�WKH�%,�3ODWIRUP�DQG�6XLWH

0D[LPXP�XVHU�SURGXFWLYLW\�GXULQJ�SODQQLQJ¯ ]�°dB%@_M T B)D T E*D*G ± R @&O²EL\:M)@®G!D�HXM)@C±hB:WLMS± R @-[)F B)D�D%G!D%U

B%D T B)DdB)F Id\*G \¯ ]�°dB%@_M T B)D T E*D*G ± R @&O²[)@ R WLML\:\%G!D%U³F R U�G WS± R @¡§ R H�°

[)F B)D)D*G!D:U´B)D T B*D�B%F Ia\*G \Pµz± R @�M V B:O�[*F M*¶*°*G M%@hB%@&W)°)G ML\)·K B)@�G B)§�F Ma\%·dWLB%F W)E*F BLHhM T�¸ MLI¹±�G U�E*@hML\*º!ºlº »

7KH�GHVLJQ�RI�SODQQLQJ�DSSOLFDWLRQV¯ ¼ \�M%@ ªzR @�G M)DdHhM T B%D T E*D*G ± R @ O T Ma\�G U�DAH R*R F \A± R @

[)F B)D)D*G!D:U´B)D T B*D�B%F Ia\*G \Pµz± R @�M V B:O�[*F M*¶:½�ELM)@hIT ML\*G U�D¹B*D TP¦ M)§PB%[�[)F!G WLBdH G R D T Ma\*G U-DÉ�\LMAH °:M\dB:O´MAB*[*[%@ R B�W)°�»

¯ ¦ M)§ ª §dBL\�M T B*D T M V M�W)ELHhM T O R%T M%FlG!D:U´B*D TB T OG!D�G \LH�@_BLH�G R DAM)D K G!@ R D�O´M)DdH*± R @¡[*F B)D�D*G D:UB%[*[%F!G WLBLH G R Dd\

¯ ]�°dB%@_M T O R)T M%F!G!D%U9B*D T G�DaHhM:U�@CBLH_M T O¾MaH_B T BLH_B

,QWXLWLYH�GHVLJQ HQYLURQPHQW

,QWHJUDWHG�DQDO\VLV�DQG�SODQQLQJ�DSSOLFDWLRQV

�

� BI Integrated Planning allows:

• Integrated design time tools: BEx Query Designer and BEx WAD are used to create analysis and planning applications.

• Integrated planning and analysis engine -> OLAP services such as drill-down, hierarchies, calculated key figures and so on can also be used in planning. In addition, data entries are supported in the BEx Analyzer.

• Shared runtime and shared metadata for planning and analysis. �

The Planning Modeler is a Web-based modeling environment for all tasks related to planning.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-22

SAP AG 2006

%,�3ODQQLQJ�$UFKLWHFWXUH

�EL\*G!DdML\d\ « M%[ R @hH�GlD�U)·�¿SE�M:@hIPB%D T9¨ DLB)F IL\�G \

�EL\*G!DdML\d\ e F B)D*D*G D%U À ¨ D�B)F ILH�G WLB)F2]¡M)@ K G WLM�\

J DdHCM)@�[%@�G \dM © BLHXB ¦ B)@_M%° R E�\*G!D:U

id� ras2sat s v �Lnas�o�pht kds�y}�id� ras2sat s v � |#Á:n�|ds�o�|�y• ,2� ��!�!� Â�8�� • Ã��#� ��8( • �2�#�� • 0#� ��( 8&�l� ��• 0#��• 1#� �� $��• �a8�� 7��5 � ��• +

e F B)D)D%GzDdU QSR�T M)F M:@

�¡j!oL�2t p�|#o�p�|#mS��r�plr � raj ply� w#|ajlr�pht k�s�r��:r�pzr � pzk�j | �:r�pzrgÄAraj!|a��k:n�yb|��r�u#|aj � r�y#p�|aj��r�plr�Å

��ÆbÇ�qgn�|aj u��:|�yLt v s#|�j

J)V¹¦ M�§

ÄA|a��¡s�ra� u#È|aj Ä¹|a�g�®wLw�� t o�r�pht kds��:|�yLt v s�|aj

J)V�¨ D�B)F Id`2M%@

¨ D�B)F IaH�G WaB)F J D%U�G DdM

x rbo��|�yb|2j �Lt o�|�y i�� r�s~m2r�pzr~o�r#o2��|

� ��®i � |aj!��t o�|�y• ,2�!� ( ( ��6)�• �a8��!� ��$�� &É 8�� • �2�( $�8�( � � ��É 5 �� 8�( �• Ê=�$�� _É $�� • Ë2��!� �Â�( ��• Ì2� �� $�4�� • Í��#� � �� • "b�� • +

i�� ras2sLt s vaÎ � w�|bo�t �ht o� |�j �Lt o�|�y• ��$�'�� • Ë2�( � �� • ,#�� )��( � $��• �a4�� $ � ��!� � �!� $*� ��( &�!� ��

i�r�p�p�|�jCs

¢!Da± R @ O´BLH G R D´ �@ R B T WdBa\dH G�DdU

� ��iSÏ:|�p!Ä�|�r��#|�jiak�j!p�ra�

� |2w2k�j!p:�:|�yLt v s�|aj�¡� ÆbÇ�o�|��mam Î�Ð s

�

� The master data and the transaction data for BI integrated planning is stored in the Enterprise Data

Warehouse. �

The Analytical Engine (OLAP and planning-specific services) is responsible for formatting the plan data and for executing the planning functions. The planning functions are created in the Planning Modeler.

� The BEx tools (BEx Query Designer, BEx Web and BEx Analyzer) are available for manual data entry

and for creating the planning applications. �

You can use Information Broadcasting to distribute the planning applications. In addition to this, there is also a Status and Tracking System available for process management and status monitoring.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-23

SAP AG 2006

%,�LQ�1HWZHDYHU��V��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 3RVLWLRQ�%,�LQWHJUDWHG�SODQQLQJ�LQ�WKH�FRQWH[W�

RI�1HW:HDYHU

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-24

SAP AG 2006


$GYDQWDJHV�RI�%,�,QWHJUDWHG�3ODQQLQJ��8QLW�2YHUYLHZ�'LDJUDP


�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-25

SAP AG 2006

$GYDQWDJHV�RI�%,�,QWHJUDWHG�3ODQQLQJ��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� $VVHVV�WKH�DGYDQWDJHV�RI�%,�LQWHJUDWHG�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-26

SAP AG 2006

$GYDQWDJHV�RI�%,�,QWHJUDWHG�3ODQQLQJ��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�ILQG�RXW�DERXW�WKH�DGYDQWDJHV�RI�%,�LQWHJUDWHG�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-27

SAP AG 2006

%XVLQHVV�3ODQQLQJ�DQG�$QDO\WLFDO�6HUYLFHV�² &UHDWLQJ�3ODQQLQJ�,QWHUIDFHV

Ñ © @ G!F!F ªzT�RdÒ DÑÔÓ G M:@_B%@&W%°*G WLB)F T BLHhB

G D¾@ R:Ò \�YbB)D T W R FlE%O³Dd\Ñ f�B:F W%E)F BLHhM T³¸ MdIA±�G U�E*@hMd\Ñ ]-H�@ E:W�H�E%@_ML\Ñ ¼ D%G H�W R D K M)@X\*G R D

Ñ ¨ F M)@XH�G!D:UÑ f R D T G H G R Da\Ñ ?A@CB)[*°*G Wa\Ñ ¨�T ° R WAW)E*@�@hM%D%WaIÑ f�E*@ @_M%D:WLI

W R D K M%@h\*G R D

%([ 4XHU\�'HVLJQHU��%([ 4XHU\�'HVLJQHU�4XHULHV�WKDW�DUH�EDVHG�RQ�WKH�DJJUHJDWLRQ�OHYHO�FDQ�ZULWH�GDWD�EDFN�WR�WKH�,QIR3URYLGHU.

%([ :HE�$SSOLFDWLRQ'HVLJQHUÑ f�@hMdBLH&GlD:U9B*D´GlDdHXM)@h±hB�WLM

Ñ f R DL± G U�E)@�G�DdU¾B%D¾GlDLHCM%@h±_BdWLMÑ ]-M)F MdWaH�G!D�U´H&°�M T BdHCB�W R D�DdM�WaH�G R DÑ f R DL± G U�E)@�G�DdU´H °�M´G!DLH_M%@_BdWaH�G R D

�

Õ You can use the BEx Query Designer to create Queries that are ready for input.

Õ In the BEx Web Application Designer you can place queries in a context, such as planning functions.

This results in planning interfaces that can be made available to end users.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-28

SAP AG 2006

J*V WLM)F ª §dBL\:M T[)F B%D�D)G!D%UPB�[)[)F!G WLBaH�G R D

3ODQQLQJ�LQ�WKH�:HE�DSSOLFDWLRQ

,QWHJUDWHG�3ODQQLQJ

�

Õ Depending on your end users’ requirements, you can provide them with planning interfaces either on the

Web or in Excel.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-29

SAP AG 2006

³)UHHGRP´ IRU�HQG�XVHUV,QWHJUDWLRQ

6SUHDGVKHHWV

%,�SODQQLQJ�FRYHUV�D�EURDG�UDQJH�DQG�HQDEOHV�ERWK�D�PRUH�XVHU�IULHQGO\�H[SHULHQFH�DV�ZHOO�DV�PDQ\�RSSRUWXQLWLHV�IRU�LQWHJUDWLRQ�

(53%:�%36

%,�,QWHJUDWHG�3ODQQLQJÖ × ØÙÚÙÛÜÝ

Þß ÙÞ ××à á

&RQIOLFW�%HWZHHQ�WKH�(QG�8VHUV�´)OH[LELOLW\µ DQG�,QWHJUDWLRQ

�

Õ If you look at the requirements companies have regarding planning functions, it is obvious that there is

a discrepancy in most enterprises between the needs of the end user and those of the administrators. Õ

The end user would like a large degree of freedom and extensive data integration in planning, whereas firm planning structures that can be easily controlled are important to administrators.

Õ Comparing different planning software, you can see that the tension between “freedom” and integration

is also present there. For example, ERP systems offer highly integrative planning, but give the end user little room for maneuver. Using Excel as a planning tool, on the other hand, gives you a great deal of flexibility but can only be integrated into overarching landscapes with the help of complicated mechanisms.

Õ BI integrated planning fulfils both the end user's and the administrator's wishes at the same time. The

end user can work from a plan query that is equally valid for all planners in a planning area, can open Excel offline planning and then carry out significantly more detailed planning there. Only part of this data is then written back to the enterable query; that is, the part that refers to the cell in question.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-30

SAP AG 2006

([DPSOH�RI�2IIOLQH�3ODQQLQJ�ZLWK�([FHO

([FHO�

�

Õ Using BEx Analyzer as the front-end system enables you to combine the advantages of Excel with those

of the centrally managed planning model. Õ

Advantages:

• Users can add “private” calculations to their workbooks.

• Workbooks can be saved locally, without losing the link to the central planning model.

• You can use highly-adjusted, individual workbooks (comparable to BI Web applications).

• BEx Analyzer functions are available in the planning applications, such as drill-down, filtering, sorting, drag and drop, and so on.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-31

SAP AG 2006

3ODQQLQJ�0RGHOHU':�:RUNEHQFKâ � n�� pht m:t {~|Ls�y�t k�s�ra��Ln�yLt s�|�y#y�y�p&jzn#o�phn2jl|�y

â �:|��ht s2t s v �gkdjCãwbr#o�ã�r v |�yâ}ä t |aj!raj�o��u{}r�t s�p�|as�ras#o�|

â �%|aj yLt k�s}{~ras�r v |2{}|�s�pâ}å yb|�j�ran�p_��k:jCt Èr�pht k:s�yâ �%rajXt ra�a� |�{}ras�r v |2{~|as�p

8VHU�,QWHUIDFHV

â ÆbÇ�o�|a�r�sbm}ÄA|a�â �%kao�n#{}|�s�p:{}r�s�r v |b{}|as�pâ7Ð s2wLn�p Î |as�ra�a� |bm�Á:n�|ajXt |�yâ ��jXt � � Î mLkb��sâ x r�� obna� r�pz|�m7ã|�ug�&t v n�j!|�yâ � p_jznbo�phn�j!|�yâ x n�jzjl|Ls#o�u�phj!ras�yL� r�p_t k�sâ ÆbÇ�o�|a��zk�jz{�n�� r�y

� v |�p!æ yb|�pLm2r�plrb�â¹ç �

&RQWUROOLQJ�DQG�'LVWULEXWLQJ�'DWD

â � p�r�p_n�y}r2sbm�{�k�s�t pzk:jzt s vâ Ä¾jzt pht s v �br#o�ã-pzkk:w�|ajlr�p_t s v y�u�y#pl|b{~y� � |�phjlr�o�pht k:s#��¤ Ð ras#m� w�|as ä na�#�

â}å yLt s v wL� ras�s2t s vyb|bÁ�n�|�sbo�|�y�t s�wLjlkao�|�y#yo��rat s�y

%,�,QWHJUDWHG�3ODQQLQJ�0RGHOLQJ

3ODQQLQJ�6WUXFWXUHV0DQXDO�3ODQQLQJ

3URFHVV�&RQWURO

è¡éaê*ë ì�í*ë!í:ìî´ï%ð î í)í*ëlí�ì

ñ9ò*ó é ðè®éLê)ë ì-í)ë!í%ìî¹ô�õ é)öh÷

è�é�ê*ë ì�í*ë!í:ì îSøSò ö ù�ú ò*ò ù

û®ü ö õ�ý ü õ ö_é ò)þ*îSÿ é)ú î)ï*ï*ð ë ýLî ü ë ò í

��:é ý:õ ü ë í%ì î¾ï*ð î í�í%ë!í%ìî)ï%ï*ð ë ýaî ü ë ò í� õ ë ð ó ëlí:ì

ú ð ò%ý ùbê

,PSOHPHQWLQJ�� ! "��$#% �&�$�('

â*) �� #% �&�,+ -/.��#10� â32 �&�4�5��,��#â76 � �$8(9 �(� � ��#��â76 �� 8 #"� ��$� � ��#% ��â*: � � 0��(�(-;�� #"�� <#" �=�â?> > >â3@=� �� /�5��&��$�â3A5B ��<#10��5��5�/�,C(��5��#% ��( �� 5�;�5�5�=��5�<��

3ODQQLQJ�)XQFWLRQV

$XWRPDWLF3ODQQLQJ

D öhé î ü ë�í�ì î¾ï)ð î í)í)ë�ídìþ�õ í ý ü ë ò í

� ñ úLé ó*ó ë!í:ì ô�õ é%ö�ë édê´ë!í ü òPøAò ö�ùLú ò%ò ùbê

�

Õ BI integrated planning consists of four components:

Õ During modeling, you create the data model for your planning process. In other words, you specify what

you want your planning process to look like. In the process, you take account of your company’s structure (slice and dice*) and your planning strategy (that is, bottom-up, top-down, mixed top-down/bottom-up).

Õ Planning functions are functions that support automatic processing of the plan data (such as copying,

forecasting, ...). This processing takes place via simulation or embedding into background processing. Õ

You can use the planning layout to create a context, into which you can enter the plan data for your different users. Web applications consist of one or more planning queries with planning functions for supporting planners in carrying out their planning tasks.

Õ You can coordinate the planning processes and their sequence by assigning planning tasks to the

planners and then tracking the status of the planning results. Õ

* slice and dice = filtering according to different criteria

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-32

SAP AG 2006

$GYDQWDJHV�RI�%,�,QWHJUDWHG�3ODQQLQJ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� $VVHVV�WKH�DGYDQWDJHV�RI�%,�LQWHJUDWHG�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-33

SAP AG 2006


%,�,QWHJUDWHG�3ODQQLQJ�² 3URFHVV�)ORZ�9LHZ�RI�WKH�3ODQQLQJ�6WHSV��8QLW�2YHUYLHZ�'LDJUDP


�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-34

SAP AG 2006

%,�LQWHJUDWHG�SODQQLQJ�² 3URFHVV�)ORZ�9LHZ�RI�WKH�3ODQQLQJ�6WHSV��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 6RUW�RXW�WKH�EDVLF�VWHSV�LQ�WKH�SODQQLQJ�SURFHVV�IRU�

%,�LQWHJUDWHG�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-35

SAP AG 2006

%,�LQWHJUDWHG�SODQQLQJ�² 3URFHVV�)ORZ�9LHZ�RI�WKH�3ODQQLQJ�6WHSV��%XVLQHVV�6FHQDULR

� $V�D�PHPEHU�RI�WKH�SURMHFW�WHDP��\RX�ZDQW�WR�JDLQ�DQ�RYHUYLHZ�RI�WKH�LQGLYLGXDO�SURFHVV�VWHSV�LQ�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-36

SAP AG 2006

6FHQDULR�9DULDQW��%XVLQHVV�3ODQQLQJ�² ([FHO�%DVHG

E @ ��$��4�F�� B ��4�5�G� 8;H �� 8�9�I � � ��4#% ��(��/JK�$� � 8 �� !�ML : ��$��(�N ��'

6 � ��#" �5�!�� %�(��$#% ��

O&�� =�( ��/��&�$�� 8

A C(�5�(��#% ��/�� ( ��

� �� <��#% �=�$E

A ��5�� &�$�� $�� <#��-F��NP��5��=PQ�

) #%�1�5�<#%��1 ��RS��

� �� <��#% �=�O&�� =�( ��/�-T�&��P��P

O&�<�� =�( ��/�� (�� !��

U VXW<Y�Z []\_^ [�` a b ^ [cZ

U dXW,YZ [_\X^ [\Xe<e$Z []ec\_^4a f$gb [ihQ[cb

U j]Wck<[Xl]^m b \Xg$gca g]eKnof$p,[]b

U qiW<r�[Qb [Xs_^t gQ` f<u�Z fQhca p,[cZ

U vXW$Y�Z [X\_^ [m b \]g,gca gQe` w<gQsX^ a f�g

U x]Wcr5[]b [Xs_^t g]` f<u�Z fchca p,[cZU \Xe,e�Z [_e<\X^ a f<gb [ihQ[cb W

U yXW$Y�Z [X\_^ [m b \]g,gca gQel][Xz�wQ[]gcsX[

U {XW,r5[Xb [XsX^t gQ` f<u�Z fchQa p,[cZU \Xe<e$Z [Xe<\_^ a f<gb [ihc[]b WU |XW�}�[Xlca e<gz�wQ[cZ ~

U qi�]Wcr5\ihc[&z<wc[QZ ~

%,�-$9$

U q]q"W$� m [Qg�z<wc[QZ ~

U q_d_W��$n7�][]pz�wQ[cZ ~U qiV]Wcr5\ihc[� f�Z �X�Qf,f$�

U qixQW,Y�Z [X\X^ [� f$Z4�_�cfcf��b \_~]f<wQ^

U q_j]Wcr5\ihQ[� f$Z4�_�cfcf��

U q_v]W,Y��cfcf<lX[p,[XlQa e�g*a ^ [Qn�l\Qgcp*p,\X^ \sXf�gcgQ[]s_^4a f$gU q_y]W$��lQ[��]�cs][Qb` f�Z n�\_^ l�f$Z` f�Z n�l

U q_{_W��c�c[_sQw]^ [%,�$%$3

�

Õ Scenarios represent the structure of technical processes.

Õ The “Business Planning and Analysis” scenario is divided into two variants:

• Excel-based

• Web-based Õ

The “Excel-based Business Planning” variant describes the steps needed to create a planning application in an Excel workbook.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-37

SAP AG 2006

6FHQDULR�9DULDQW��%XVLQHVV�3ODQQLQJ�² :HE�%DVHG

E @ ��$��4�F�� B ��4�5�G� 8;H �� 8�9�I � � ��4#% ��(��/JK�$� � 8 �� !�ML : ��$��(�N ��'

6 ��#% ��/�� (�� %��<#% ��

O&�� =�� &�� 8

A C(�5��<#% ��!�� (�( ��

� �� $��#% �=�$E

A /�5�� &�$�� $�� $#1�-��=��P��5��Pc�

) #%�1��$#%��1 ��R��(�

� �� <��#% �=�O&�$�� =�( ��/�-T�=�NP��P

O=�� =�� 5�!�� (�� !��

U VXW$Y�Z [X\_^ [�` a b ^ [QZ

U dXW<Y�Z []\_^ [\Xe<e�Z [_e,\_^4a f<gb [ihc[]b

U jXW,k<[XlX^m b \Xg,g,a g]e?n�f<p<[]b

U q_Wcr5[Xb [XsX^<t g]` fu�Z f,hca p<[QZ

U v]W,Y�Z []\_^ [m b \Xg$gca g]e`4w<gcsi^�a f�g

U x]W,r5[Xb [XsX^t gQ` f<u�Z fchQa p,[cZU \Xe<e$Z [Xe<\_^ a f<gb [ihc[]b W

U y]W,Y�Z []\_^ [m b \Xg$gca g]elQ[Xz$w,[XgcsX[

U {]Wcr5[Xb [XsX^t gQ` f<u�Z fchQa p$[]ZU \]e,e$Z []e<\i^ a f$gb [ihc[]b WU |]W$}�[Xlca e<gz�wQ[cZ ~

U q"�]Wcr5\_hQ[&z<w,[QZ ~

U q_y_W��c�c[_sQw]^ [

U4q_q_W,Y�Z []\i^ [�gQ[ ��[]�*^ []n m b \X^ [U q_d_W�t gQl][cZ ^*�T[Q�a ^ [Qn�lU4q"V]WQ��lXlca e$g�p<\_^ \m Z fQh,a p<[cZU4q%xQW,Y�f�gQ` a e<w<Z [a gc^ [cZ \Xs_^ a f�gU qiv]Wcr5\ihc[�T[Q�\ m,m b a sX\X^ a f<g%,�

-$9$

�

Õ Scenarios represent the structure of technical processes.

Õ The “ Business Planning and Analysis” scenario is divided into two variants:

• Excel-based

• Web-based Õ

The “ Web-based Business Planning” variant describes the steps needed to create a planning application in a Web application.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-38

SAP AG 2006

%,�LQWHJUDWHG�SODQQLQJ�² 3URFHVV�)ORZ�9LHZ�RI�WKH�3ODQQLQJ�6WHSV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 6RUW�RXW�WKH�EDVLF�VWHSV�LQ�WKH�SODQQLQJ�SURFHVV�IRU�

%,�LQWHJUDWHG�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-39

SAP AG 2006


:ULWH�$FFHVV�IRU�3ODQ�'DWD�LQ�WKH�%:��8QLW�2YHUYLHZ�'LDJUDP


�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-40

SAP AG 2006

:ULWH�$FFHVV�IRU�3ODQ�'DWD�LQ�WKH�%:��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�LQWHJUDWLRQ�EHWZHHQ�SODQQLQJ�DQG�

UHDO�WLPH�,QIR3URYLGHUV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-41

SAP AG 2006

:ULWH�$FFHVV�IRU�3ODQ�'DWD�LQ�WKH�%:��%XVLQHVV�6FHQDULR

� $V�D�PHPEHU�RI�WKH�SURMHFW�WHDP��\RX�ZDQW�WR�ORRN�LQWR�WKH�EDVLF�FKRLFH�RI�,QIR3URYLGHU DQG�LQWR�ZULWLQJ�SODQ�GDWD�EDFN�WR�WKH�%:��EHIRUH�PRGHOLQJ�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-42

SAP AG 2006

7\SHV�RI�,QIR3URYLGHU�LQ�3ODQQLQJ��

%:�'DWD�:DUHKRXVH

%,�3ODWIRUP

3ODQ�GDWD�HQWU\��PDQXDO�(YDOXDWLRQ

6$3�1HW:HDYHU�%,�

([WUDFWLRQ 5HWUDFWLRQ

03 �0XOWL3URYLGHU573� �5HDO�7LPH�,QIR3URYLGHU

573 03

�

Õ BW differentiates between master data and transaction data. Transaction data can be stored in BW using

two types of InfoProvider: InfoCubes or Operational Data Stores (ODS). Õ

BI integrated planning can use only UHDO�WLPH�,QIR3URYLGHUV for SODQQLQJ�SXUSRVHV (that is, changing or writing data); these InfoProviders can be assigned to a MultiProvider.

Õ The real-time InfoProvider can be filled here either manually or by planning functions.

Õ It is also possible to use transactional InfoCubes both for loading actual data via extraction and for

planning. To do this, you have to set a switch in the InfoProvider to enable either the “ loading” or the “ planning” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-43

SAP AG 2006

3URFHVVLQJ�5HTXHVW�,'V�LQ�5HDO�7LPH�,QIR3URYLGHUV

3ODQQLQJ�WUDQVDFWLRQV

2SHQ�FXUUHQW�ZULWH�UHTXHVW

6WRUH�SRVWLQJV��WR��ZLWK�UHTXHVW�,'

� ò ê ü ëlí�ì%ê�� ü ò�� ò ê ü ëlí�ì��o�=� ��=�

&ORVH�UHTXHVW

� �

� ��

�-ë ñ é

6WRUH�SRVWLQJ��ZLWK�UHTXHVW�,'

�

Õ Data requests in real-time InfoProviders stay open until the number of records in the data request

exceeds 50,000. When an application writes data to the request and the limit of 50,000 records is exceeded, the data is stored and the request is closed. Thus, a request can actually contain more than 50,000 records.

Õ Physically, the design of these real-time InfoProviders may differ with respect to indexing and

partitioning (depending on the database). For an Oracle DBMS this means, for example: no bitmap indexes on the F fact table and no partitioning of the F fact table by packet dimension (initiated by the BW).

Õ It is still possible to rollup and define aggregates, compress and so on.

Õ For reporting purposes, a real-time InfoProvider needs the variables Most Current Data or Most Recent

Data in the filter or in the custom characteristics. This allows it to also report on data records from open requests.

Õ Please note that if you execute a reporting query in a plan query’s environment (that is, if both access the

same data from the same real-time InfoProvider), that the Most Current Data setting automatically applies in the plan query, and you do not need to set Most Current Data in the reporting query. Instead, it takes the setting from the plan query.

Õ It is not possible to transfer data to a second InfoProvider until the first real-time InfoProvider’s request

has ended.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-44

SAP AG 2006

8VLQJ�D�3URFHVV�&KDLQ�WR�&RQWURO�WKH�6ZLWFK�IRU�WKH�5HDO�7LPH�,QIR3URYLGHU

�

Õ A real-time InfoProvider can be either loaded or planned, meaning that it has two “ states” .

• Real-time InfoCube can be loaded with information; no plans allowed

• Real-time InfoCube can be planned; no data loading allowed. Õ

In the first case, the information can be loaded whilst the plan data can only be read and not changed. Õ

In the second case (planning), the InfoProvider cannot be loaded at the same time, nor can it be filled via a data transfer process.

Õ There are process types for both “ states” and for switching between them.

Õ This means that you can use the process chain to specify that a real-time InfoProvider set up for

planning is switched to loading; that the load or data transfer process is then carried out; and that the InfoProvider is then reset to planning.

Õ Note that switching from planning to loading automatically closes the open planning request.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-45

SAP AG 2006

:ULWH�$FFHVV�IRU�3ODQ�'DWD�LQ�WKH�%:��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�LQWHJUDWLRQ�EHWZHHQ�SODQQLQJ�DQG�

UHDO�WLPH�,QIR3URYLGHUV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 1-46

SAP AG 2006

*HQHUDO�&RQFHSWV�DQG�&KDOOHQJHV�LQ�%XVLQHVV�3ODQQLQJ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�EDVLF�SODQQLQJ�FRQFHSWV� 3RVLWLRQ�%,�LQ�1HW:HDYHU��V� 8QGHUVWDQG�WKH�DGYDQWDJHV�RI�%,�LQWHJUDWHG�

SODQQLQJ� 8QGHUVWDQG�WKH�SURFHVV�IORZ�YLHZ�RI�WKH�SODQQLQJ�

VWHSV�LQ�%,�LQWHJUDWHG�SODQQLQJ� 8QGHUVWDQG�WKH�ZULWH�DFFHVV�IRU�SODQ�GDWD�LQ�WKH�%:

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-1

SAP AG 2006

&RQWHQW�� 3ODQQLQJ�DUFKLWHFWXUH�IURP�D�PRGHOLQJ�SHUVSHFWLYH� 3ODQQLQJ�DUFKLWHFWXUH�IURP�WKH�YLHZSRLQW�RI�WKH�SODQQLQJ�

PRGHOHU

&UHDWLQJ�D�6LPSOH�'DWD�0RGHO�ZLWK�'DWD�,QSXW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-2

SAP AG 2006

&UHDWLQJ�D�6LPSOH�'DWD�0RGHO�ZLWK�'DWD�,QSXW��/HDUQLQJ�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 6RUW�RXW�WKH�SODQQLQJ�REMHFWV�LQ�WKH�SODQQLQJ�

PRGHOHU� 8QGHUVWDQG�WKH�WHFKQLFDO�LPSOHPHQWDWLRQ�RI�

SODQQLQJ�REMHFWV�LQ�WKH�SODQQLQJ�PRGHOHU

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-3

SAP AG 2006

&UHDWLQJ�D�6LPSOH�'DWD�0RGHO�ZLWK�'DWD�,QSXW��&RXUVH�2YHUYLHZ�'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-4

SAP AG 2006

&UHDWLQJ�D�6LPSOH�'DWD�0RGHO�ZLWK�'DWD�,QSXW��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�UHVSRQVLEOH�IRU�VHWWLQJ�XS�%,�LQWHJUDWHG�SODQQLQJ�DQG�\RX�QRZ�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�PRGHOLQJ�LQWHUIDFHV��LQ�RWKHU�ZRUGV��WKH�SODQQLQJ�PRGHOHU��

� )LUVW��\RX�ZDQW�WR�XQGHUVWDQG�WKH�FRQFHSW��7KHQ�\RX�ZDQW�WR�VHH�KRZ�WKH�V\VWHP�LV�LPSOHPHQWHG�DQG�ILQDOO\�\RX�ZDQW�WR�VWDUW�HQWHULQJ�WKH�ILUVW�WHVW�GDWD�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-5

SAP AG 2006

3ODQQLQJ�$UFKLWHFWXUH�IURP�D�0RGHOLQJ�3HUVSHFWLYH��8QLW�2YHUYLHZ�'LDJUDP

� /HVVRQ��3ODQQLQJ�$UFKLWHFWXUH�IURP�D�0RGHOLQJ�3HUVSHFWLYH� /HVVRQ��3ODQQLQJ�$UFKLWHFWXUH�IURP�WKH�9LHZSRLQW�RI�WKH�3ODQQLQJ�0RGHOHU�

8QLW�2YHUYLHZ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-6

SAP AG 2006

3ODQQLQJ�$UFKLWHFWXUH�IURP�D�0RGHOLQJ�3HUVSHFWLYH��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 6RUW�RXW�WKH�SODQQLQJ�REMHFWV�LQ�WKH�SODQQLQJ�

PRGHOHU

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-7

SAP AG 2006

3ODQQLQJ�$UFKLWHFWXUH�IURP�D�0RGHOLQJ�3HUVSHFWLYH��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�UHVSRQVLEOH�IRU�VHWWLQJ�XS�%,�LQWHJUDWHG�SODQQLQJ�DQG�\RX�QRZ�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�SODQQLQJ�LQWHUIDFHV��LQ�RWKHU�ZRUGV��WKH�SODQQLQJ�PRGHOHU��

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-8

SAP AG 2006

$UFKLWHFWXUH�RI�WKH�3ODQQLQJ�0RGHOHU�

)LOWHU)LOWHU

%,�LQWHJUDWHG�SODQQLQJ

5HDO�WLPH�,QIR3URYLGHU

$JJUHJDWLRQ�OHYHO

�

� This is the architecture of BI integrated planning.

• The planning model for BI integrated planning is based on a real-time InfoProvider.

• Real-time InfoProvider is the new name for a transactional InfoProvider.

• This InfoProvider makes the database for the aggregation level available.

• 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 planners by using filters.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-9

SAP AG 2006

3ODQQLQJ 0RGHOLQJ

5HJLRQ 9HUVLRQ3HULRG

&XVWRPHU3URGXFW

:KR LV SODQQLQJ":KDW�KDV�WR�EH�SODQQHG"&RXQWU\

<HDU

*URVV VDOHV &RVW RI�VDOHV

6DOHV�YROXPH3ULFH

0DQDJHUV

$FFRXQWPDQDJHUV

5HJLRQDO PDQDJHUV5HJLRQ�<HDU &RXQWU\3ULFH &RVW RI�VDOHV

&RXQWU\<HDU *URVV VDOHV

&XVWRPHU5HJLRQ<HDU &RXQWU\

��

�

�

� If you want to start a planning run, you first have to know what area you want to plan and which people

are involved; in other words, you have to decide the granularity of the planning. �

In the diagram above, three planner groups are to be modeled: managers, regional managers and account managers.

� The segmentation characteristics need to be determined for each of the three groups. For example, the

account manager plans the sales volume key figure for the finest granularity of year, country, region, customers.

� The three granularities will later each be in a separate aggregation level.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-10

SAP AG 2006

0DQDJHUV

$FFRXQWPDQDJHUV




��

3ODQQLQJ 0RGHOLQJ ² 5HDO�7LPH ,QIR3URYLGHU

5HDO�WLPH ,QIR3URYLGHU

�� ! "��# $&% ')(�* '&+� ,-��*

.�/ 0 1 243

.�/ 0 1 243

576-68* �96)�4�! ')$� �:+��9�

�

� The above diagram shows which fields need to be incorporated into a real-time InfoProvider if all three

planner groups are supposed to plan using one InfoProvider. These fields are then also used as the basis for an analysis on the InfoProvider.

� These fields are then used to build the aggregation levels in which each planner group is modeled on a

separate aggregation level.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-11

SAP AG 2006

3ODQQLQJ 0RGHOLQJ ² $JJUHJDWLRQ /HYHO

$JJUHJDWLRQ OHYHO

�;��&� � � "��# $�% '8(�* '&+& ,)��*

.9/ 0 1 243

.4/ 0 1 243

0DQDJHUV

$FFRXQWPDQDJHUV




��

576-68* ��68�:�� ')$� �4+&�&�

�

� One aggregation level is modeled for each planner group. This aggregation level covers all the fields

that, according to the planning’s granularity, are relevant. �

The aggregation level “reserves” a “slice” of the InfoProvider for planning.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-12

SAP AG 2006

3ODQQLQJ 0RGHOLQJ ² )LOWHU

)LOWHU

&RXQWU\ 86

5HJLRQ��

&XVWRPHU �

<HDU �� &RXQWU\ 86

5HJLRQ��<HDU �� &RXQWU\ 86

*URVV 6DOHV

3ULFH &RVW RI�6DOHV

6DOHV�9ROXPH

&XVWRPHU �5HJLRQ��<HDU �� &RXQWU\ 86

6DOHV�9ROXPH

�;��&� � � "��# $�% '8(�* '&+& ,)��*

.4/ 0 1 243

.9/ 0 1 2�3

5<6868* ��6-�� '8$� �4+9��

5HJLRQDO PDQDJHUV

0DQDJHUV

$FFRXQW 0DQDJHU�$FFRXQW 0DQDJHU�

�

� The relevant characteristic values are stored for each aggregation level using the filters; so for example

the values that are relevant to a planner are stored in his or her planner group. �

In general, you should use variables to try and keep the number of filters as low as possible so that the planning structure remains small.

� You could also see the filters as work packages for the individual planners.

� Example of a filter: cost planning for all the costs incurred at a cost center. There is always exactly one

person responsible for a cost center. You could therefore group together all the cost types for a specific cost center into one filter/work package and use authorizations to assign it to the cost center manager.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-13

SAP AG 2006

0RGHOLQJ 3ODQQLQJ 6WUXFWXUHV

=�> ��? ��@7ACB > �D�CE

F GHI JK

L ��AM� >ON �CP @7�RQ��S� >

T � > A�U

V ��SA

��D�7A9UWSX�Y<X

Z �� >

.H\�ILJXUHV

-XLFH-XLFH-XLFH

5HDO�WLPH ,QIR3URYLGHU%:�,QIR3URYLGHU�DV�D�GDWDEDVH

=[> ��? ��@7A�B > ��E

F GHI JK

N �CP @7�WSXSX�\

T � > A�U

V ��SA

��D�7A9U

Z �]� >

WSX]XS^WSX�XS\

(85��6RXWK(85��(DVW(85��1RUWK

*URVV6DOHV

<HDU5HJLRQ3URGXFW*URXS

&KDUDFWHULVWLFV

$JJUHJDWLRQ OHYHO RUILOWHU�8VHU�VSHFLILF VHOHFWLRQ

�

� In summary:

• The aggregation levels of BI integrated planning correspond to subsets of the real-time InfoProvider.

• They represent a drill down level in a query.

• Key figures are aggregated for all the characteristics that are not in the aggregation level.

• The structure of a data record is determined by the InfoProvider. When saving in any aggregation level, every characteristic in the data record will be filled with a value.

• Delta records will have the value � (not assigned) for all characteristics that are not in the level. �

In the example above, gross sales are planned across all regions for one division (beverages) and one product group (water).

� The selection defines the aggregation level on which the entry of data will be allowed.

� The table above shows a slice; in other words, a partial section of the InfoProvider.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-14

SAP AG 2006

�8QDVVLJQHG�9DOXHV�LQ�WKH�&RQWH[W�RI�7RS�'RZQ�3ODQQLQJ

³,QLWLDO´��V\PERO IRUXQDVVLJQHG YDOXHV

��6PLWK��

��0LOOHU��

��

*URVV6DOHV

&XVWRPHU)LVFDO<HDU

Customers Miller and Smith usually generate 70 – 80% of the gross sales, therefore they are planned individually. About 20% of the gross sales is generated by 100 other customers. It is not always necessary to plan those in detail. The values do not need to be assigned.

�

� Delta records have the value � (not assigned) for all characteristics that are not in this aggregation level.

� # (not assigned) is always treated as a regular characteristic value and can be used accordingly.

� # (not assigned) can be used if you intentionally want to leave a part of the values unassigned.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-15

SAP AG 2006

$JJUHJDWLRQ LQ�WKH ,QIR3URYLGHU

��-XLFH��:DWHU$PRXQW)LVFDO <HDU3URGXFW *URXS

��$PRXQW)LVFDO <HDU

��$PRXQW)LVFDO <HDU

(QWULHV LQ�WKH,QIR3URYLGHU��


&KDQJH�

1HZ�GDWDUHFRUG

$JJUHJDWH�

400

�VW�$JJUHJD�WLRQ OHYHO

�QG�$JJUHJD�WLRQ OHYHO

�

� In BI integrated planning, data can be created at any of an InfoProvider’s aggregation levels.

� The InfoProvider contains the characteristics 3URGXFW�JURXS and )LVFDO�\HDU, for example. You can

always enter the data at the fiscal year aggregation level or at a detailed aggregation level such as product group, fiscal year.

� If you enter data at the detailed aggregation level (the first aggregation level in the example above), the

data is always aggregated/totaled automatically, as can be seen in the second aggregation level in the above example.

� If the data was changed by the higher-level planner, this results in a new data record, which displays #

(not assigned) for the characteristic being used for aggregation (product group in this example). �

Please note that, if the higher-level planner reduces the value 300 to zero, a credit line amounting to -300 is written to the database for the fiscal year, connected to # for the product group.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-16

SAP AG 2006

'LVDJJUHJDWLRQ LQ�WKH ,QIR3URYLGHU

��-XLFH��

��:DWHU$PRXQW)LVFDO <HDU3URGXFW *URXS


(QWU\ LQ�WKH,QIR3URYLGHU

'LVWULEXWLRQ�WR�WKHSURGXFW�JURXSV�

��:DWHU��-XLFH

��

�VW�$JJUHJDWLRQOHYHO ��

��

3ODQQHGERWWRP�XS %\

GLVWULEXWLRQ

�

� If the data was changed by the higher-level planner, this results in a new data record, which displays #

(not assigned) for the characteristic being used for aggregation (product group in this example). �

If the value of the 100 units for the 2010 fiscal year is then distributed to the product groups together with product group #, a credit line and a debit line are then written, as shown in the figure above.

� If the detailed planner then returns to his or her first aggregation level, he or she receives an automatic

summation of all the data records on the aggregation level, as shown in the figure above.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-17

SAP AG 2006

3ODQQLQJ�$UFKLWHFWXUH�IURP�D�0RGHOLQJ�3HUVSHFWLYH��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 6RUW�RXW�WKH�SODQQLQJ�REMHFWV�LQ�WKH�SODQQLQJ�

PRGHOHU

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-18

SAP AG 2006

3ODQQLQJ�$UFKLWHFWXUH�IURP�WKH�9LHZSRLQW�RI�WKH�3ODQQLQJ�0RGHOHU��8QLW�2YHUYLHZ�'LDJUDP

8QLW�2YHUYLHZ� /HVVRQ��3ODQQLQJ�$UFKLWHFWXUH�IURP�D�0RGHOLQJ�3HUVSHFWLYH� /HVVRQ��3ODQQLQJ�$UFKLWHFWXUH�IURP�WKH�9LHZSRLQW�RI�WKH�3ODQQLQJ�0RGHOHU�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-19

SAP AG 2006

3ODQQLQJ�$UFKLWHFWXUH�IURP�WKH�9LHZSRLQW�RI�WKH�3ODQQLQJ�0RGHOHU��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�WHFKQLFDO�LPSOHPHQWDWLRQ�RI�


�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-20

SAP AG 2006

3ODQQLQJ�$UFKLWHFWXUH�IURP�WKH�9LHZSRLQW�RI�WKH�3ODQQLQJ�0RGHOHU��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�WHDP�UHVSRQVLEOH�IRU�VHWWLQJ�XS�%,�LQWHJUDWHG�SODQQLQJ�DQG��DIWHU�\RX�KDYH�XQGHUVWRRG�WKH�FRQFHSW��\RX�ZDQW�WR�VHH�KRZ�LW�LV�LPSOHPHQWHG�LQ�WKH�V\VWHP�DQG�WKHQ�\RX�ZDQW�WR�HQWHU�\RXU�ILUVW�WHVW�GDWD�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-21

SAP AG 2006

3ODQQLQJ�0RGHOLQJ

7KH�3ODQQLQJ�0RGHOHU�7KH�ZHE�EDVHG SODQQLQJ�PRGHOHU LV�WKH�FRUH DSSOLFDWLRQ�LQ�ZKLFK�DOO�WKH�PRGHOLQJ�DQG�DGMXVWPHQWV�IRU�%,�LQWHJUDWHG�SODQQLQJ�WDNH�SODFH��7KH�GLIIHUHQW�REMHFWV�DUH�PDLQWDLQHG�LQ�WKHPRGHOHU�LQ�FRQQHFWLRQ�ZLWK�SODQQLQJ��VXFK�DV�DJJUHJDWLRQ�OHYHOV��DV�DUH�WKH�UHODWLRQVKLSV�EHWZHHQ�WKHVH�REMHFWV�

�

� The planning modeler provides a central entry point for planners. This is a Web-based tool that offers an

integrated test environment. �

Business experts who do not have any access to the Data Warehousing Workbench (transaction RSA1) can also model with this tool. Managing a planning process requires frequent changes to the settings (variables, "data slices", formulas): these can all be made in the planning modeler.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-22

SAP AG 2006

0RGHOLQJ�WKH�3ODQQLQJ

3ODQQLQJ 0RGHOHU:L]DUG

3ODQQLQJ0RGHOHU

�

� BI integrated planning provides you with the 3ODQQLQJ�0RGHOHU and the�3ODQQLQJ�:L]DUG for modeling

your planning scenarios. This involves the new, Web-based planning tool: the Planning Modeler. It is possible to set up the planning model here even if you do not have any authorization in the Data Warehousing Workbench (transaction RSA1).

� The 3ODQQLQJ�:L]DUG leads you through all the steps (URDGPDS�RQ�WKH�XSSHU�VFUHHQ�HGJH) that you need

to take to create the planning model. �

Both tools are Web Dynpro-based applications that have to be installed on the SAP J2EE server. You can set up links or iViews to access these applications from the portal. This means that you do not need to install them locally on the SAP front end. �

� 3ODQQLQJ�0RGHOHU��

You can use the planning modeler to model, administer and test all the metadata belonging to a planning scenario.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-23

SAP AG 2006

&RQILJXUDEOH�,QWHUIDFHV�

)LOWHU�6HOHFW�WKH�LQIR�REMHFWVLQ�WKH�FROXPQ

6HWWLQJV�•6HOHFW�DQG�VRUW�GLVSOD\HG�FROXPQV

•'LVSOD\HG�URZV•7DEOH�OD\RXW

([SDQG�RU�FROODSVH�WDEOH

�

� The ,QIR3URYLGHU, $JJUHJDWLRQ�/HYHOV, )LOWHU, 3ODQQLQJ�)XQFWLRQV and 3ODQQLQJ�6HTXHQFHV tab pages

are each constructed with a function in the upper screen area that allows you to search for specific objects available for selection in the system. They also contain a table for displaying the results of the search. If you select or create an entry, the system displays the properties of the object in question in the lower part of the screen or gives you the option of changing the object

� You can adapt the interface to suit your requirements by showing or hiding certain areas.

� To adjust the table layout, you can:

• Enter descriptions into the input-ready rows via )LOWHU�RQ. These descriptions are then used to filter the table columns.

• Go to 6HWWLQJV, select table columns and specify their sequence, as well as changing general table layout settings.

� If you upgrade the system, however, your user-specific settings for the table views in the Planning

Modeler may be lost or, if you have saved them locally, they may not be reusable. �

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-24

SAP AG 2006

,QIR3URYLGHU

)LUVW�VWHS�ZKHQ�FUHDWLQJ�D�VLPSOH�SODQQLQJ�PRGHO

6HOHFW�WKH�,QIR3URYLGHU

�

� The data basis for BI integrated planning is the ,QIR3URYLGHUV�WKDW�LQFRUSRUDWH�UHDO�WLPH�,QIR&XEHV.

� 5HDO�WLPH�,QIR&XEHV are different to standard InfoCubes in that they can support parallel write

accesses. 6WDQGDUG�,QIR&XEHV are technically optimized for read access, to the detriment of write access. 5HDO�WLPH�,QIR&XEHV have a reduced read performance, which allows them the option of parallel (transactional) writing and an improved write performance generally.

� A 0XOWL3URYLGHU is a special InfoProvider that combines data from several InfoProviders and makes it

available for reporting. The MultiProvider does not contain any data itself. Its data comes exclusively from the InfoProviders on which it is based, which are grouped together in a union operation. For a more detailed examination of the MultiProvider, see the Modeling unit.

� When using the planning modeler, you can create YLUWXDO�,QIR3URYLGHUV�RI�WKH�DJJUHJDWLRQ�OHYHO�W\SH

on the basis of an InfoCube or a MultiProvider containing this kind of InfoCube. These virtual InfoProviders are specially designed for planning data manually or changing data using planning functions.

� Please note that you can specify a NH\�GDWH�DV�WKH�VWDQGDUG�NH\�GDWH�LQ�SODQQLQJ in FKDQJH�PRGH on

the 6HWWLQJV tab page. If time-dependent objects, such as attributes or hierarchies, are used in planning model objects, you can always refer to the default key date for planning. This ensures that one key date is used throughout the planning model.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-25

SAP AG 2006

$JJUHJDWLRQ�/HYHO

0DNH�RU�GHOHWH�\RXU�VHOHFWLRQ

6HOHFW�WKH�GLVSOD\HG�LQIR�REMHFWV�)XQFWLRQV��• $OO• 8VHG• 1RW�XVHG

'LVSOD\�WKH�QH[W�LQIR�REMHFW��RU�WKH�QH[W�ILYH��RU�JR�WR�WKH�HQG�RI�WKH�OLVW

�

� An DJJUHJDWLRQ�OHYHO is a YLUWXDO�,QIR3URYLGHU. With an aggregation level, you model the level whose

data can be changed manually using input-ready queries, or automatically using planning functions. An aggregation level represents a selection of characteristics and key figures for the underlying InfoProvider and determines the granularity of the planning. The key figures included in the aggregation level are aggregated using characteristics that are not included in the aggregation level.

� You can create several aggregation levels for an InfoProvider and therefore model various levels of

planning and, for example, hierarchical structures. Note, however, that aggregation levels FDQQRW�EH�QHVWHG. You can change an aggregation level by selecting info objects that you want to be used or not used. You can select these objects in the lower area of the screen.

� The input-ready queries are created on the basis of the aggregation level. This is described in a later

unit. The following InfoProviders can be used as the basis of DQ�LQSXW�UHDG\�TXHU\:

• The InfoProvider is a (simple) aggregation level that is defined on a real-time InfoCube.

• The InfoProvider is a (complex) aggregation level that is defined on a MultiProvider, where the MultiProvider contains at least one real-time InfoCube and no simple aggregation level.

• The InfoProvider is a MultiProvider containing at least one simple aggregation level. This context is examined in more detail in a later unit.

� Please note that, in the 'DWD�:DUHKRXVLQJ�:RUNEHQFK’s 0RGHOLQJ function area, the system displays

both the aggregation levels and the InfoProviders that these are based on. This is displayed in the InfoProvider overview. By double-clicking on the aggregation level, you can go to the planning modeler and edit the aggregation level.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-26

SAP AG 2006

)LOWHU

'HILQH�D�VHOHFWLRQ�RI�FKDUDFWHULVWLFV�LQ�\RXU�DJJUHJDWLRQ�OHYHO� '\QDPLF�XVH�RI�YDULDEOHV��KLHUDUFKLHV�DQG�DWWULEXWHV� )OH[LEOH�GHVLJQ�RI�D�YHUVLRQ�FRQFHSW� 'HILQH�WKH�ZRUN�SDFNDJHV�IRU�WKH�SODQQHU� 7KH�ILOWHU�LV�XVHG�WRJHWKHU�ZLWK�WKH�4XHU\�'HVLJQHU

6HOHFW�DQ�DJJUHJDWLRQOHYHO�DQG�FUHDWH�D�ILOWHU�

,QSXW�KHOS�IRU�•6LQJOH�YDOXHV•9DOXH�UDQJHV•+LVWRU\•)DYRULWHV

2U�VWDUW�WKH�ZL]DUG�IRU�WKH�YDULDEOHV

2SHQ�WKH�GURSGRZQ�ER[��

VHOHFW�WKH�FKDUDFWHULVWLFV�

DQG�FOLFN�RQ�³$GG´

�

_ A ILOWHU is an object that describes a multidimensional segment of data from a dataset.

_ Filters are used in UHSRUWLQJ��DQDO\VLV�DQG�SODQQLQJ to restrict data to a certain business area, certain

product group, or certain time periods, for example. _

Segmenting the dataset in this way can ensure that users or user groups only have access to the data that is relevant to them, or that only certain data areas are visible within an application scenario. Within BI Integrated Planning, filters set the selection for the data upon which a planning function operates.

_ Filters are mandatory if you want to use a planning function in a planning sequence. They are optional if

you only want to create input-ready queries using the aggregation level. _

You can create multiple filters for an InfoProvider. To do this, you can use the 3ODQQLQJ�0RGHOHU or the 3ODQQLQJ�:L]DUG as well as the 4XHU\�'HVLJQHU.

_ You can use the “ 6KRZ�$GYDQFHG�6HWWLQJV” button to limit selected characteristics of the InfoProvider

to single values, value ranges, hierarchy nodes, history or favorites and you can specify whether or not these can be changed when the query is executed.

_ You can enter a ILOWHU�NH\�GDWH for specifying time-dependent selections, such as determining a time-

dependent hierarchy of time-dependent hierarchy node selections. You can use the standard provided variable 0PLANDAT on characteristic 0CALDAY to synchronize key dates in queries, filters, characteristic relationships, data slices and planning functions. That way, you can ensure that the same key date is used in all the objects.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-27

SAP AG 2006

)XQFWLRQDOLW\ RI�D�)LOWHU

�

_ A filter’s functionality depends on its particular use in either a planning function or a query. �

_ )LOWHUV�LQ�3ODQQLQJ�)XQFWLRQV�

In connection with planning functions, a filter in the characteristic restrictions describes the data that is used for executing a planning function. Selections in the default values are QRW�XVHG�IRU�H[HFXWLQJ�WKH�SODQQLQJ�IXQFWLRQ��You can also use a key date for the filter to determine time-dependent selections.

_ )LOWHUV�LQ�D�4XHU\�

The values defined in a query’s characteristic restrictions limit the volume of data that is available for further filtering during a query’s runtime. It is then no longer possible to filter using a characteristic value outside this value set. The default values determine the query’s initial filter state. The settings &KDQJHDEOH�RQ�([HFXWLRQ and 6LQJOH�9DOXH�2QO\ essentially refer to the use of filters with a query:

• &KDQJHDEOH�RQ�([HFXWLRQ determines whether the selection of values affected by the characteristic restrictions can be changed when the query is executed. This setting is a prerequisite for the definition of default values for a characteristic.

• If you select the &KDQJHDEOH�RQ�([HFXWLRQ option, you can use the 6LQJOH�9DOXHV�2QO\ option to specify that only a single value can be used for filtering the query.

_ The two functionalities described above are described in more detail in the following units.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-28

SAP AG 2006

3ODQQLQJ�6HTXHQFH�IRU�7HVW�3XUSRVHV�XVLQJ�WKH�,QSXW�7HPSODWH

�

�

�

�

Add a step for the input templateSelect the aggregation levelSelect your filterSave your selectionExecute

`

a

b

�c

d

�

_ You can use a planning sequence to generate a test layout that makes it possible to enter plan data into a

selected DJJUHJDWLRQ�OHYHO�ILOWHU. _

This test layout is called an LQSXW�WHPSODWH in BI integrated planning and is equivalent to opening the plan data buffer.

_ Another important application of the buffer can be seen in connection with planning functions and their

execution in planning sequences. This area of use will be presented in unit 10.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-29

SAP AG 2006

6XSSOHPHQWDU\�'RFXPHQWV�LQ�WKH�,QIR3URYLGHU)DFW�7DEOH

Fact Table Before Compression

Fact Table After Compression

3 & 7 4�6DOHV 7XUQRYHU��'LVFRXQW 6DOHV�2YHUKHDG� � � ��

3 & 7 4�6DOHV 7XUQRYHU��'LVFRXQW 6DOHV�2YHUKHDG� � � ��

Data Input4�6DOHV��

7XUQRYHU��

'LVFRXQW��

6DOHV�2YHUKHDG��

�

_ In accordance with the concept of data retention in BW, the plan data is also stored in the database of

the associated real-time InfoProvider in the form of VXSSOHPHQWDU\�HQWULHV. If the data is read, then all the entries in the fact tables that contain the same key are read and reported as a totals record.

_ The supplementary documents are not balanced until a FRPSUHVVLRQ�UXQ�LQ�WKH�,QIR3URYLGHUV�DGPLQLVWUDWLRQ. The size of the database and read access are thus optimized. For this reason, you should run the compression run in SAP BW daily.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-30

SAP AG 2006

1H[W�6WHSV�LQ�0RGHOLQJ�WKH�3ODQQLQJ�3URFHVV

egf�h�ikj�l�m nSo;p�qDl�r�f�h�s7p�m;t�qMu[j�v�pCj]w

igr]rCx yDjCx!j]yzv�{]p|[}�p�qMn�vMu~l��u�q&�S��u�u �

egf�h��p��i��m!x sSl�v4x u[j��p�rCx yDj]p�q

��p��lC��m x!s<l�v4x u j

%([ 4XHU\�'HVLJQHU�IRU�FUHDWLQJ�DQ�LQSXW�UHDG\�TXHU\

�

_ The aggregation level is the basis for creating an input-ready query.

_ You can then use the %([�$QDO\]HU to integrate one or more input-ready queries into a workbook, or

you can create a web application with the %([�:HE�4XHU\�'HVLJQHU.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-31

SAP AG 2006

3ODQQLQJ�$UFKLWHFWXUH�IURP�WKH�9LHZSRLQW�RI�WKH�3ODQQLQJ�0RGHOHU��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�WHFKQLFDO�LPSOHPHQWDWLRQ�RI�


�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-32

SAP AG 2006

&UHDWLQJ�D�6LPSOH�'DWD�0RGHO�ZLWK�'DWD�,QSXW��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 6RUW�RXW�WKH�SODQQLQJ�REMHFWV�LQ�WKH�SODQQLQJ�

PRGHOHU� 8QGHUVWDQG�WKH�WHFKQLFDO�LPSOHPHQWDWLRQ�RI�


�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-33

�([HUFLVHV�

�

�8QLW�� &UHDWLQJ�D�6LPSOH�'DWD�0RGHO�ZLWK�'DWD�,QSXW�/HVVRQ�� 3ODQQLQJ�$UFKLWHFWXUH�IURP�WKH�3HUVSHFWLYH�RI�

WKH�3ODQQLQJ�0RGHOHU�

At the conclusion of this exercise, you will be able to:

• Understand the interface of BI integrated planning

• Create a simple planning model

A multi-level plan is to be modeled; in which CFO is to plan the sales quantities manually first, at the granularity of the controlling area and the company code.

1-1 Log on to the training system according to the information given by your instructor and navigate to the planning interface via 6$3�0HQX��!�%XVLQHVV�3ODQQLQJ�DQG�6LPXODWLRQ��!�3ODQQLQJ�0RGHOHU. Log on to the planning interface via “6WDUW�0RGHOHU´. In doing so, use the user and password given to you by the instructor. You will then have to make your ODQJXDJH�VHWWLQJ. To do so, position the cursor in the URL of the Planning Modeler, which may appear as follows: 6DPSOH�85/� http://iwdf8390.wdf.sap.corp:50100/webdynpro/dispatcher/sap.com/bi~plan~workbench1/Modeler 5HPRYH�DOO�HQWULHV�DIWHU�«��, so that your URL only appears as follows – as you can see for the sample URL here - : http://iwdf8390.wdf.sap.corp:50100 Now add ,5- to call up the start page of the portal. <RXU�H[DPSOH�85/�QRZ�DSSHDUV�DV�IROORZV� http://iwdf8390.wdf.sap.corp:50100/IRJ On the start page of the portal you will find “3HUVRQDOL]H´ at the top right. Confirm this jump. This takes you to the user profile. The initial load can take a while.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-34

Press the “0RGLI\” button and select the course language for the “/DQJXDJH” field on the *HQHUDO�,QIRUPDWLRQ tab page. Then press Save and close both sessions. Log on to Planning Modeler again. Your course language should appear automatically.

1-1-1 You are now on the ,QIR3URYLGHU tab page. First of all, you are going to configure the “ Displayed Columns” , which are to be displayed on this tab page, under “ Settings” For the configuration, the following fields are supposed to be displayed in the following order: 1. Technical name of InfoProvider 2. InfoProvider description 3. InfoProvider type 4. Last changed by 5. Date 6. Time. Select �� as the “'LVSOD\HG�&ROXPQV” and save your settings under the description: ,QIR3URYLGHUB��B�� and select “ ,QLWLDO�9LHZ” .

1-1-2 In the ,QIR3URYLGHU area, select the real-time InfoProvider 7%:��6�� (where ## = monitor number). This InfoProvider is intended for quantity planning.

1-2 Create an aggregation level for planning the CFO. Enter the following: Technical name:6��B$/B�� Description: 7%:��B6��B$/��.

1-2-1 Here, configure the “6HWWLQJV” in the upper part of the screen first. Except for the ,QIR3URYLGHU�GHVFULSWLRQ field, include all fields in the “ Displayed columns and specify the following order of fields: 1. Technical name of InfoProvider 2. Technical name of aggregation level 3. Description of aggregation level 4. Last changed by 5. Date 6. Time. Select ��as the “'LVSOD\HG�5RZV” and save your settings under the description: “$JJUHJDWLRQ/HYHOB��B��” � Also select “ ,QLWLDO�9LHZ” .

1-2-2 In the lower part of the screen go to “6HWWLQJV” and select ��as the “'LVSOD\HG�5RZV” . Save your settings under the description $JJUHJDWLRQ/HYHOB��B��D�and select “ ,QLWLDO�9LHZ” .

1-2-3 Include all key figures and their units in the aggregation level and model it so that the CFOs can plan on the granularity controlling area, company code. They are all supposed to plan in a certain version, at fiscal year level.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-35

Following that, FKHFN the consistency of the created aggregation level and DFWLYDWH it.

1-3 You should now create a filter for planning for aggregation level 6��B$/B��. Enter the following descriptions: Technical name: 6��B)B�� Description: 7%:��B6��B$/��B)�� Now include all the characteristics that you’ve included in the aggregation level in the filter as well. Select “6WDQGDUG�.H\�'DWH” as the key date. Select [.H\@�as the�“'LVSOD\” .

1-3-1 Model the filter so that the CFOs all plan in version�$, for company code �� and �� and in controlling area ��. Choose 67 as the unit of measure and currency 86'. 6DYH your settings.

1-3-2 Planning is to refer to fiscal year variant .�. You need to store a YDULDEOH fort he selection of individual values for the ILVFDO�\HDUV to be planned. Enter the following descriptions: Technical name: *URXS��B9$5B)<B��B30 Description: *URXS��B9$5B)<B��B30��Select ³0DQXDO�HQWU\�GHIDXOW�YDOXH´ for the ³3URFHVVLQJ�E\´ field. �Model the variable so that only LQGLYLGXDO�YDOXHV can be taken into account, making it a PDQGDWRU\ variable entry. “5HDG\�IRU�LQSXW´ should be selected. Select ��as the�GHIDXOW�YDOXH. The 9DULDEOH is to be included�in the filter as the selection for the characteristic fiscal year. &KHFN your settings for the filter and VDYH�it.

1-4 Create a planning sequence to enable you to look at the input template as a test layout or buffer display and to enable you to enter test data manually.

1-4-1 Enter the following descriptions for the sequence: Technical name: 6��B6B�� Description: 7%:��B6��B$/��B6�� A “ sWHS�IRU�WKH�LQSXW�VFUHHQ” is to be added to generate the input template. In doing so, select the filter of your first aggregation level. 6DYH�your settings and execute the input template for fiscal year ��, which has been configured as the variable default. You will now see that the InfoProvider already contains data for the CFOs. Please overwrite the data with the following values:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-36

1. Company code 2. Fiscal year 3. Sales volume

4. 1000 5. 2010 6. 150

7. 2000 8. 2010 9. 250

Now set the variable to ��. Execute the “ ,QSXW�7HPSODWH” again by pressing the “([HFXWH” button. You should overwrite the data that is now displayed as follows:

10. Company Code 11. Fiscal year 12. Sales volume

13. 1000 14. 2011 15. 150

16. 2000 17. 2011 18. 250

Finally, VDYH your SODQ�GDWD for the first time��then�reset the variable to �� and press the “([HFXWH” button once again. Stay in Planning Modeler.

1-4-2 Now open a second session and navigate to the Administrator Workbench. Under 0RGHOLQJ��!�,QIR3URYLGHU search for your InfoProvider 7%:��6��and use the OLVW�YLHZHU for data targets to look at the development of the data records. You should get the following results:

How is the data stored in the real time InfoCube? _____________________________________________________________

1-4-3 Verify that both the real-time InfoProvider and the aggregation level that you’ve created can be found in the Administrator Workbench in the 0RGHOLQJ��!�,QIR3URYLGHU area and display the respective 2EMHFW�2YHUYLHZ.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-37

1-4-4 Navigate to the 0HWDGDWD�5HSRVLWRU\ and search for your ,QIR3URYLGHU (which you can find using the search term “ ,QIR&XEH” in the Meta Repository) using its description “4XDQWLW\�3ODQQLQJ” and the technical name 7%:��6�� Navigate to the DJJUHJDWLRQ�OHYHO you have created via the “$GGLWLRQDO�2EMHFWV” area and go to the corresponding ILOWHU�there. Close the second session.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-38

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-39

�6ROXWLRQV�

8QLW�� &UHDWLQJ�D�6LPSOH�'DWD�0RGHO�ZLWK�'DWD�,QSXW�/HVVRQ�� 3ODQQLQJ�$UFKLWHFWXUH�IURP�WKH�3HUVSHFWLYH�RI�

WKH�3ODQQLQJ�0RGHOHU�

1-1 Log on to the training system according to the information given by your instructor and navigate to the planning interface via 6$3�0HQX��!�%XVLQHVV�3ODQQLQJ�DQG�6LPXODWLRQ��!�3ODQQLQJ�0RGHOHU or by calling up transaction 563/$1. Log on to the planning interface using “6WDUW�0RGHOHU” . In doing so, use the user and password given to you by the instructor. You will then have to make your ODQJXDJH�VHWWLQJ. To do so, position the cursor in the URL of the Planning Modeler, which may appear as follows: ([DPSOH�85/� http://iwdf8390.wdf.sap.corp:50100/webdynpro/dispatcher/sap.com/bi~plan~workbench1/Modeler 5HPRYH�DOO�HQWULHV�DIWHU�«��, so that your URL only appears as follows – as you can see for the example URL here - : http://iwdf8390.wdf.sap.corp:50100 Now add LUM�to call up the start page of the portal. <RXU�H[DPSOH�85/�QRZ�DSSHDUV�DV�IROORZV� http://iwdf8390.wdf.sap.corp:50100/irj

On the start page of the portal, you will find the “3HUVRQDOL]H” link at the top right. Click it. This takes you to the user profile. (The initial load can take a while.) Press the “0RGLI\” button and select the course language for the “/DQJXDJH” drop-down box on the *HQHUDO�,QIRUPDWLRQ tab page. Then press the “ Save” button and close both browser windows. Log on to Planning Modeler again using “ Start Modeler” . Your course language should now appear automatically.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-40

1-1-1 You are now on the ,QIR3URYLGHU tab page. First of all, you are going to configure the “ Displayed Columns” , which are to be displayed under “ Settings” on this tab page. For the configuration, the following fields are supposed to be displayed in the following order: 1. Technical name of InfoProvider 2. InfoProvider description 3. InfoProvider type 4. Last changed by 5. Date 6. Time. Press the “$GG” button, to include all selected properties (e.g. “ ,QIR3URYLGHU�GHVFULSWLRQ” ) in the area on the right (“'LVSOD\HG &ROXPQV” ). You can change the order using the arrow buttons underneath this area. Enter �� as the “'LVSOD\HG�&ROXPQV” and save your settings under the description: ,QIR3URYLGHUB��B�� and select “ ,QLWLDO�9LHZ” . To do so, choose the “'LVSOD\” �tab and enter ��in the�“'LVSOD\HG�5RZV” �field� Then click the “ Save As…” button, enter the description “ ,QIR3URYLGHUB��B��” and activate the “ ,QLWLDO�9LHZ” �FKHFNER[� Confirm the settings by choosing OK.

1-1-2 In the ,QIR3URYLGHU area, select the real-time InfoProvider 7%:��6�� (where ## = monitor number). This InfoProvider is intended for quantity planning. To do so, select the ,QIR3URYLGHU�option on the right side of “ Search” and enter the search term “ WEZ��V ” � Scroll down using the arrow buttons until you can see the InfoProvider with your number. Select it by clicking the field on the left of the first column.

1-2 Create an aggregation level for planning the CFO. Enter the following: Technical name:6��B$/B�� Description: 7%:��B6��B$/��. First of all, click the “$JJUHJDWLRQ�/HYHOV” tab. Choose the “7HFKQLFDO�QDPH�RI�,QIR3URYLGHU” �option in the search area and, if necessary, enter “7%:��6” �as well.

1-2-1 Here, configure the “6HWWLQJV” in the upper part of the screen first. Except for the ,QIR3URYLGHU�GHVFULSWLRQ�field, include all fields in the “ Displayed Columns” and specify the following order of fields: 1. Technical name of InfoProvider 2. Technical name of aggregation level 3. Description of aggregation level 4. Last changed by 5. Date

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-41

6. Time. Press the “$GG” button, to include all selected properties in the area on the right (“'LVSOD\HG &ROXPQV” ). You can change the order by using the arrow buttons underneath this area. You hide the “ ,QIR3URYLGHU�GHVFULSWLRQ” �column by selecting and pressing the “5HPRYH” �button. Enter ��as the “'LVSOD\HG�5RZV” in the “'LVSOD\” �tab and save your settings using the description: “$JJUHJDWLRQ/HYHOB��B��” � Also select the “ ,QLWLDO�9LHZ” field.

1-2-2 You open the dialog for creating an aggregation level by pressing the “&UHDWH” button. Enter technical name “6��B$/B��” and description “7%:��B6��B$/��” and confirm using “7UDQVIHU“ . In the lower part of the screen go to “6HWWLQJV” and select ��as the “'LVSOD\HG�5RZV” on the “'LVSOD\” �tab. Display the “ Technical name” column as well. Here, you save your settings using the description $JJUHJDWLRQ/HYHOB��B��D, select “ ,QLWLDO�9LHZ” and confirm these settings.

1-2-3 Include all key figures and their units in the aggregation level and model it so that the CFOs can plan on the granularity controlling area, company code. They are all supposed to plan in a certain version, at fiscal year level. The selection should appear as follows:

Following that, FKHFN the consistency of the created aggregation level and DFWLYDWH it. To do so, press the “&KHFN” �button in the top window first. The check result is displayed at the top left in the browser. After the successful check, click the “ Save” and “ Activate” buttons. Here, messages are also displayed at the top left, informing you of success or problems.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-42

1-3 You should now create a filter for planning for aggregation level 6��B$/B��. Enter the following descriptions: Technical name: 6��B)B�� Description: %:��B6��B$/��B)�� To do so, click the “)LOWHU” tab first. Choose the “7HFKQLFDO�QDPH�RI�DJJUHJDWLRQ�OHYHO” �option in the search area and, if necessary, enter “6��B$/B��” �as well. Then press the “&UHDWH” button to open the dialog for creating filters. Enter technical name “6��B)B��” and description “7%:��B6��B$/��B)��” and confirm using “7UDQVIHU” . Now include all the characteristics that you've included in the aggregation level in the filter as well. Select “6WDQGDUG�.H\�'DWH” as the key date. Select [�H\@�as the�“'LVSOD\” . To do so, press the “$GG�$OO” button. In the “ Settings” tab, choose the “ Standard Key Date” radio button.

1-3-1 Model the filter so that the CFOs all plan in version�$, for company code �� and �� and in controlling area ��. Choose 67 as the unit of measure and currency 86'. 6DYH your settings. Use the input help to fill �),6&9$517 with “.�” , �9(56,21 with “$” , �&203B&2'( with �� and ��, �&2B$5($ with ��, �&23$6/478 with “67” and �&855(1&< with “86'” . To do so, you might have to move the horizontal scroll bar of the value help dialog.

1-3-2 Planning should refer to fiscal year variant .�. You need to store a YDULDEOH for the selection of individual values for the ILVFDO�\HDUV�to be planned. Enter the following descriptions: Technical name: *URXS��B9$5B)<B��B30 Description: *URXS��B9$5B)<B��B30��Select “0DQXDO�HQWU\�GHIDXOW�YDOXH” for the “3URFHVVLQJ�E\” field. �Model the variable so that only LQGLYLGXDO�YDOXHV can be taken into account, making it a ELQGLQJ variable entry. “5HDG\�IRU�LQSXW” should be selected. Select ��as the�GHIDXOW�YDOXH. The 9DULDEOH is to be included�in the filter as the selection for the characteristic fiscal year. &KHFN your settings for the filter and VDYH�it. To do so, the “9LHZ” dropdown box in the value help dialog of characteristic 0FISCYEAR must be set to “9DULDEOHV” �first� You can now click on the “&UHDWH” button to call up the Variable Wizard. Enter the following in the first step “ General Information” :

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-43

• Variable name: “*URXS��B9$5B)<B��B30”

• Description:�“*URXS��B9$5B)<B��B30”

• Processing by: “0DQXDO�HQWU\�GHIDXOW�YDOXH” .

Pressing “&RQWLQXH” takes you to the “'HWDLOV” step where you enter “6LQJOH�YDOXH” for “9DULDEOH�5HSUHVHQWV” and “0DQGDWRU\” for “9DULDEOH�,QSXW�,V” . Furthermore, you need to select the “ Ready for input” checkbox.

In the “'HIDXOW�YDOXHV” �step, use the value help to select .�� and copy these settings by pressing the “6DYH” button as the last step.

Following that, include the newly created variable in the “&KRVHQ�6HOHFWLRQV” by pressing “$GG” and confirm it as the value for characteristic �),6&<($5 by pressing OK.

Finally, check and save the filter by pressing the corresponding buttons in the “)LOWHU�6HOHFWLRQ” area.

1-4 Create a planning sequence to enable you to look at the input template as a test layout or buffer display and to enable you to enter test data manually. To do so, choose the “3ODQQLQJ�6HTXHQFHV” �tab.

1-4-1 Enter the following descriptions for the sequence: Technical name: 6��B6B�� Description: 7%:��B6��B$/��B6�� Pressing the “&UHDWH” button opens the “&UHDWH 3ODQQLQJ�6HTXHQFH” dialog in which you enter technical name and the description and save them using “7UDQVIHU” . A “ sWHS�IRU�WKH�LQSXW�WHPSODWH” is to be added to generate the input template. In doing so, select the filter of your first aggregation level “7%:��B6��B$/��B)��” . 6DYH�your settings and press the “([HFXWH” �button to execute the input template for fiscal year ��, which has been configured as the variable default. You will now see that the InfoProvider already contains data for the CFOs. Please overwrite the data for the sales quantity with the following values, without saving the changes:

&RPSDQ\�FRGH )LVFDO�\HDU 6DOHV�YROXPH

1000 2010 150

2000 2010 250

Set the variable to��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-44

On the “ Filter” tab choose the filter you’ve just created and switch to edit mode by choosing “&KDQJH” and fill variable “*URXS��B9$5B)<B��B30” with default value �� Confirm the value change of �),6&<($5 and save the filter. Execute the “ ,QSXW�7HPSODWH” again by pressing the “([HFXWH” button. You should overwrite the data that is now displayed as follows:

&RPSDQ\�&RGH )LVFDO�\HDU 6DOHV�YROXPH

1000 2011 150

2000 2011 250

Finally, VDYH your SODQ�GDWD for the first time��then�rHset the variable to �� and press the “([HFXWH” button once again. Stay in Planning Modeler.

1-4-2 Now open a second session and navigate to the Data Warehousing Workbench by calling up transaction 56$�. There, under 0RGHOLQJ��!�,QIR3URYLGHU search for your InfoProvider 7%:��6��and use “'LVSOD\�'DWD” to look at the development of the data records. You should get the following results:

How is the data stored in the real time InfoCube? $V�GHOWD�GRFXPHQWV�_____________________________________________________________

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-45

1-4-3 Verify that both the real-time InfoProvider and the aggregation level that you’ve created can be found in the Administrator Workbench in the 0RGHOLQJ��!�,QIR3URYLGHU area and display the respective 2EMHFW�2YHUYLHZ�from the context menu.

1-4-4 Navigate to the 0HWDGDWD�5HSRVLWRU\ and search for your ,QIR3URYLGHU (which you can find using the search term “ ,QIR&XEH” in the Meta Repository) using its description “4XDQWLW\�3ODQQLQJ” and its technical name 7%:��6�� Navigate to the DJJUHJDWLRQ�OHYHO you have created via the “$GGLWLRQDO�2EMHFWV” area and go to the corresponding ILOWHU�there. Close the second session.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 2-46

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-1

SAP AG 2006

&RQWHQW�� 8VLQJ�)LOWHUV�LQ�3ODQQLQJ� 9DULDEOH�&RQFHSW�LQ�%,�,QWHJUDWHG�3ODQQLQJ� ([DPSOH�RI�&UHDWLQJ�D�9DULDEOH

)LOWHUV�DQG�9DULDEOHV�LQ�%,�,QWHJUDWHG�3ODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-2

SAP AG 2006

)LOWHUV�DQG�9DULDEOHV�LQ�%,�,QWHJUDWHG�3ODQQLQJ��/HDUQLQJ�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�XVH�RI�YDULDEOHV�LQ�SODQQLQJ� $VVHVV�WKH�YDULDEOH�FRQFHSW�LQ�%,�LQWHJUDWHG�

SODQQLQJ� 8QGHUVWDQG�WKH�FUHDWLRQ�RI�D�YDULDEOH��XVLQJ�DQ�

H[DPSOH

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-3

SAP AG 2006

)LOWHUV�DQG�9DULDEOHV�LQ�%,�,QWHJUDWHG�3ODQQLQJ��&RXUVH�2YHUYLHZ�'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-4

SAP AG 2006

)LOWHUV�DQG�9DULDEOHV�LQ�%,�,QWHJUDWHG�3ODQQLQJ��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�GDWD�VHOHFWLRQV�LQ�%,�LQWHJUDWHG�SODQQLQJ��

� <RX�DUH�LQWHUHVWHG�LQ�WKH�FRQFHSWV�RI�ILOWHULQJ�DQG�YDULDEOHV�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-5

SAP AG 2006

)LOWHUV�DQG�9DULDEOHV�LQ�%,�,QWHJUDWHG�3ODQQLQJ��8QLW�2YHUYLHZ�'LDJUDP

� /HVVRQ��9DULDEOH�&RQFHSW�LQ�%,�,QWHJUDWHG�3ODQQLQJ

8QLW�2YHUYLHZ� /HVVRQ��8VLQJ�)LOWHUV�LQ�3ODQQLQJ

� /HVVRQ��([DPSOH�RI�&UHDWLQJ�D�9DULDEOH

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-6

SAP AG 2006

8VLQJ�)LOWHUV�LQ�3ODQQLQJ��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�FRQFHSW�DQG�LPSOHPHQWDWLRQ�RI�

ILOWHUV�LQ�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-7

SAP AG 2006

8VLQJ�)LOWHUV�LQ�3ODQQLQJ��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�ILOWHULQJ�SRVVLELOLWLHV�LQ�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-8

SAP AG 2006

7KH�)LOWHU�DV�D�6HOHFWLRQ�5DQJH

7KH�ILOWHU�VSHFLILHV�ZKLFK�GDWD�D�XVHU�LV�DOORZHG�WR�SODQ�ZLWK

:DWHU

:LQH -XLFH

%HHU

9HUVLRQ

)LVFDO \HDU

3URGXFW JURXS

3URGXFW

$FWXDO 3ODQ�

��

$OFRKROLF 1RQ�DOFRKROLF

6HOHFWLRQ UDQJH

�

� A ILOWHU is an object that describes a multidimensional segment of data from a dataset. It is not possible

to plan outside this dataset. �

Filters are used in UHSRUWLQJ��DQDO\VLV�DQG�SODQQLQJ to restrict data to a certain business area, certain product group, or certain time periods, for example.

� Segmenting the dataset in this way can ensure that users or user groups only have access to the data that

is relevant to them, or that only certain data areas are visible within an application scenario. �

Within BI Integrated Planning, filters set the selection for the data upon which a planning function operates.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-9

SAP AG 2006

8VLQJ WKH )LOWHU

)LOWHU�6HOHFWLRQ�5DQJH

3ODQQLQJ)XQFWLRQ

3ODQ4XHU\

5HVWULFWLQJ�WKH�GDWD�VHOHFWLRQ�H[HFXWHG�IRU�WKH�IXQFWLRQ

5HVWULFWLQJ�WKH�GDWD�VHOHFWLRQ��FDQ�EH�UHVWULFWHG�IXUWKHU�LQWHUDFWLYHO\�GXULQJ�H[HFXWLRQ

�

� A filter’s functionality depends on its particular use in either a planning function or a query. �

� )LOWHUV�LQ�3ODQQLQJ�)XQFWLRQV�

In the context of planning functions, a filter in the characteristic restrictions describes the data that is used for executing a planning function.

� )LOWHUV�LQ�D�4XHU\�

The values defined in a query’s characteristic restrictions limit the volume of data that is available for further filtering during a query’s runtime. It is then no longer possible to filter using a characteristic value outside this value set.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-10

SAP AG 2006

&UHDWLQJ D�)LOWHU

3ODQQLQJ�0RGHOHU 3ODQ�4XHU\�

��

�

� You can either create a filter in the planning modeler or configure a filter in the plan query.

� A filter created in a plan query can be saved as a separate object with the “Save filter” option; this filter

is then also available in the planning modeler and in other plan queries. �

If you save only the query, the filter is available in that query only. �

If a filter was created in the planning modeler, you can then decide if you want to use the filter again in a plan query when you define the query.

� The advantage of storing a filter in the planning modeler and then transferring the filter to a query

without changing it is that this ensures the planning structure is consistent. Both the functions and the plan query access the same data records.

� Filters are only mandatory if they are used for a planning function that is executed via a planning

sequence. �

You can also integrate planning functions into both Web interfaces and workbooks without the need for filters.

� You can store a filter in more than one plan query for the same aggregation level.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-11

SAP AG 2006

)LOWHUV�LQ�4XHULHV�² )LOWHUV�IRU�3ODQQLQJ�)XQFWLRQV

3ODQQLQJ�0RGHOHU� 3ODQ�4XHU\

100200

1020

AlcoholicNon-alcoholic

8;3URGXFW*URXS

)LOWHU��3URGXFW�JURXS�ZLWKDOFRKROLF��QRQ�DOF�

3URGXFW JURXS�$OFRKROLF

3URGXFW�:LQH

3URGXFW�%HHU

3URGXFW JURXS�1RQ�DOFRKROLF

3URGXFW�-XLFH

3URGXFW�:DWHU

)LOWHU��3URGXFW�JURXS�ZLWK�DOFRKROLF��QRQ�DOF�3URGXFW�ZLWK�ZLQH��EHHU��MXLFH��ZDWHU

'LVWULEXWLRQIXQFWLRQ

'LVWULEXWLRQIXQFWLRQ

�

� The image above shows an example of the different granularities that are needed for business reasons at

different points in modeling. The slide also shows where you would create the filters so that they fulfill their purpose.

� You would proceed in exactly the same way if you wanted to carry out a comparison between plan and

actual values in the plan query but you wanted only plan data to be included in the execution of the planning functions.

� It is especially useful to XVH�D�ILOWHU because you know which data records are selected and which

locked. If you worked without a filter, you would not know this. �

You can control locking by defining a filter; as a rule, you should make the filter as detailed as possible, to keep the ORFN�DV�VPDOO�DV�SRVVLEOH. The more detailed the filter is, the less data is selected; this has a SRVLWLYH�HIIHFW�RQ�SHUIRUPDQFH.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-12

SAP AG 2006

)XQFWLRQDOLW\�RI�D�)LOWHU�LQ�WKH�3ODQQLQJ�0RGHOHU��

6HOHFWLRQ�RI�FKDUDFWHULVWLF�DWWULEXWHV��VSHFLILHV�WKH�PD[LPXP�TXDQWLW\�RI�GDWD�WKDW�FDQ�EH�XVHG��

�

� If you create a filter in the planning modeler, you first need to select the aggregation level for which you

want to create the filter. The filter then represents the work package that will be carried out for a function, for example.

� It is possible not to incorporate all of an aggregation level’s characteristics into the filter; however, the

filters contain all the key figures for the aggregation level. �

It is possible to set your chosen characteristic attributes firmly into the filter, or you can leave the selections free and set them via the plan query, or carry out a detail selection via the navigation block at runtime.

� Note that you can enter a ILOWHU�NH\�GDWH for specifying time-dependent selections, such as determining a

time-dependent hierarchy of time-dependent hierarchy node selections. You can use the standard provided variable 0PLANDAT on characteristic 0CALDAY to synchronize key dates in queries, filters, characteristic relationships, data slices and planning functions. That way, you can ensure that the same key date is used in all the objects.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-13

SAP AG 2006

)XQFWLRQDOLW\�RI�D�)LOWHU�LQ�WKH�3ODQQLQJ�0RGHOHU��

�

� The image above shows the additional functions available via “Show Advanced View”; these options

are principally of interest in connection with the plan query. �

These functionalities are described in more detail in the subsequent three slides and their effect on the plan query is examined.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-14

SAP AG 2006

´&DQ�EH�&KDQJHG�DW�4XHU\�([HFXWLRQµ )XQFWLRQDOLW\

��

��

!�� "$#� ��

%&� ��' � ��()� � � *

%&� ��' � ��

+,�$� � �" %&" ��

-�.�/�. -�.�/�/

+0" ��&1��2" � � 3&�2��4 �" ��)1��)" � �

5 �( 67 �� (�

8:9);&<�=?>A@CB)D,E�D�@)<GF,EIH ;)<JH @ ;K Product group

8L=NM 9&>PO);Q Sales quantity key figure. Turnover key figureR =�S;K Fiscal year

20102011

8;)LVFDO \HDU%&� � ' � ��(2� � ��* +?" ��21��&" � ��T�3&�)��4 �" �� 1�� " � �U H M <IF�EVH O2WYX�=�;&;?H ZCM F[Z)\0]

^,_ O)F`=CaC<JB&Fb<�S=XCEG=?c09&@)<?WdE�=d9�X&;

^Ne \PZ�=�<JB[X,E�=,cd92@)<W0EG=d9�X2;�;?H >f9�M <GDCO2F&=d9 ;?M \

g =haJH M <GFCEVH O�W Z2\iDX,E�=?c09&@)<NW0EG=N9�X`=C<JB2F,E<JB2DCOb<JB2F2;�Fb<�Sb=?j�Z&F�@ D,9 ;�FZ�=�<JBSF,E�FbaJH EG>PM \�;2<�=dE F�cH O<JB&FbaJH M <IF�E

3URGXFW JURXS

k�l m�n�o�pVq�r�l m�o�s

k�l m�n�o�pVq�r�l m�o�s

tuH >f9�M <IDCO)F�=v9 ;h=dX)<JH =NOi=�aH O�@2=dE�X�=NE�D2<wH O2W[<JB)F�awH M <GF,E�;�F,M F&@)<JH =NOa�=dE<JB2F[X?E�=?cN9&@ <NWNE�=N9�XfH O<JB&FicNEVH M M c,=�SÒi=�aEG=&Sx=0E,@&=NM 9&>fO

�

� If the maximum number of selection-enabled characteristic values has already been stored for a

characteristic (for example the product group) in the planning modeler's filter (“alcoholic and non-alcoholic” in the figure), it is not possible (despite the “Can be Changed at Execution” setting) to leave this data range; the setting only allows you to select the attribute from this range.

� The detail filter is then set from the named quantity at runtime via the navigation block, which you can

then use to filter at runtime. �

In addition to filtering, it is possible to incorporate the filtered characteristic in the drilldown of the row or column by dragging and dropping the characteristic from the customer characteristics area.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-15

SAP AG 2006

´'HIDXOW�9DOXH �NH\�µ )XQFWLRQDOLW\

8:9);&<�=?>A@CB)D,E�D�@)<GF,EIH ;)<JH @ ;Q Product group

8L=NM 9&>PO);K Sales quantity key figure. Turnover key figureR =�S;Q Fiscal year

20102011

8;)LVFDO \HDU%&� ��' � ��()� � ��* +0" ��&1��2" � ��T�3&�2��4 �" �� 1�� " � �

%2� ��' � ��(&� � � *4�+?" ��)1�� " � �

y M @&=0B�=NM H @

- z B&Fic�D2<GDicNH ;?X?M D)\&F�cYH ;fH O,H <JH D,M M \D {�D,H M D,Z?M FbaG=NE�<JB&F�DCM @&=0B&=dM H @X,EG=Ccd9&@)<?WdE�=N9CX Q

- | =&SbF {�F,E�j \�=d9�@2D,O}a$H M <GF,ENH Ob<$B2F@�92;2<�=0>A@CB)D,E�D�@)<�F,EVH ;&<JH @�;`D2<EI9?O <JH >`Fb<�=[;2SiH <�@�Bb<�=YO&=NO ^DCM @&=0B&=dM H @`=NENO2=dO ^ D,M @&=NB2=dM H @DCO�chD,M @2=dB2=NM H @ Q

)LOWHU�VWDUW�YDOXH��DOFRKROLF

��

��

!�� "$#� ��

%&� ��' � ��()� � � *

%&� ��' � ��

+,�$� � �" %&" ��

-�.�/�. -�.�/�/

+0" ��&1��2" � � 3&�2��4 �" ��)1��)" � �

5 �( 67 �� (�

�

� If you selected “ Default Value (Key)” for a characteristic in the planning modeler and you stored a

default value (such as "alcoholic"), then the query opens for this filtered start value. You can, however, switch to another selection within the maximum data range at any time. The end user can switch to another selection via the navigation block.

� To use a default value, you must have selected “ Can be Changed at Execution” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-16

SAP AG 2006

)LOWHUV�LQ�3ODQQLQJ�)XQFWLRQV�DQG�,PSRUWLQJ�5HIHUHQFH�'DWD

3ODQQLQJIXQFWLRQ :ULWH�DFFHVV�WR�

GDWD�3ODQQLQJIXQFWLRQ � 5HDG�DFFHVV�WR�

UHIHUHQFH�GDWD

~�,�J��w�d�0�7�w��0�?�N�v�� I��u�d�� 0�?�� 0�

~��,�J��V�d�0�7�$�v��d�C�N�v��L��u�?�$�G�� v��0�� u�u��d��u�N�,��

R F)D,M ^ <wH >bF� O aV=0�dE�=�{,H cCF,E

!�� " � ��

!�� " � ��

y W?WNE�F�W�D2<JH =dO`M F {�F,M

��o��pVq � m��5 ��

�

� The filter specifies the write access’s selection range for planning functions. Selections of data records

that are contained in the InfoProvider but not stored in the filter can always be imported as reference data, however it is not possible to write access them.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-17

SAP AG 2006

8VLQJ�)LOWHUV�LQ�3ODQQLQJ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�FRQFHSW�DQG�LPSOHPHQWDWLRQ�RI�

ILOWHUV�LQ�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-18

SAP AG 2006

9DULDEOH�&RQFHSW�LQ�%,�,QWHJUDWHG�3ODQQLQJ��8QLW�2YHUYLHZ�'LDJUDP




�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-19

SAP AG 2006

9DULDEOH�&RQFHSW�LQ�%,�,QWHJUDWHG�3ODQQLQJ��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�FRQFHSW�DQG�RSWLRQV�DVVRFLDWHG�

ZLWK�XVLQJ�YDULDEOHV�LQ�%,�LQWHJUDWHG�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-20

SAP AG 2006

9DULDEOH�&RQFHSW�LQ�%,�,QWHJUDWHG�3ODQQLQJ��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�GLIIHUHQW�RSWLRQV�IRU�PRGHOLQJ�YDULDEOHV�LQ�%,�LQWHJUDWHG�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-21

SAP AG 2006

3RVVLEOH 8VHV RI�9DULDEOHV

3DUDPHWHUL]DWLRQ�RI�FKDUDFWHULVWLF�UHVWULFWLRQV�WKDW�GHVFULEH�WKH�GDWD�VOLFH

'DWD VOLFH

� )RU�SDUDPHWHUL]DWLRQ�RI�WKH�KLHUDUFK\� )RU�SDUDPHWHUL]DWLRQ�RI�WKH�VHOHFWLRQ�IURP�D�'DWD6WRUH REMHFW

&KDUDFWHULVWLF UHODWLRQVKLSV

'HSHQGLQJ�RQ�WKH�SODQQLQJ�IXQFWLRQ�W\SH�IRU�SDUDPHWHUL]LQJ FRQGLWLRQV�DQG�SDUDPHWHUV

3ODQQLQJ IXQFWLRQV

3DUDPHWHUL]DWLRQ�RI�D�GLVSOD\�KLHUDUFK\�IRU�WKH�TXHU\

$GGLWLRQDO�REMHFWV

3DUDPHWHUL]DWLRQ RI�FKDUDFWHULVWLFUHVWULFWLRQV

)LOWHU

� 3DUDPHWHUL]DWLRQ�RIFKDUDFWHULVWLF�UHVWULFWLRQV�LQ�WKH�4XHU\� ,Q�IRUPXODV��FRQGLWLRQV��H[FHSWLRQV�SODFHKROGHU�IRU�WH[WV

4XHULHV��SDUWLFXODUO\ LQSXW�UHDG\ TXHULHV

9DULDEOHV�XVHG IRU�2EMHFW

�

� Variables are used to parameterize a query, a planning function, a filter, a characteristic relationship or a

data slice. When you execute a query, planning function or Web application, these placeholders are filled with values.

� Variables act as placeholders for characteristic values, hierarchies, hierarchy nodes, texts, and formula

elements, and can be processed in many different ways.

• There are different YDULDEOH�W\SHV, depending on which objects you want to define variables for.

• The SURFHVVLQJ�W\SH specifies how a variable is filled during a query’s, a planning function’s or a Web application’s runtime.

� Variables do QRW depend on an InfoProvider: they only depend on the InfoObject in question. A variable

that was defined for an InfoObject is available in all the InfoProviders that use this InfoObject. �

You can define variables in the Query Designer or the planning modeler or Planning Wizard. The variables are then available for re-use in all queries or planning functions.

� Please note that you can only ever assign one characteristic to a variable.

� Also note that there are no user-dependent variables in BW integrated planning. If you require user-

dependent variables, you should create a DataStore object containing the user master data and then have the DataStore object upload the user-specific characteristic combinations with a flat file. Then you have to create a query on the DataStore object that can be used to access the user-dependent combinations.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-22

SAP AG 2006

7\SHV RI�9DULDEOHV

7H[W�YDULDEOHV)RUPXOD YDULDEOHV

+LHUDUFK\YDULDEOHV

&KDU��YDOXHYDULDEOHV

;

"

+LHUDUFK\ QRGHYDULDEOHV

�

� There are different YDULDEOH�W\SHV, depending on which objects you want to define variables for.

� &KDUDFWHULVWLF�YDOXH�YDULDEOHV represent characteristic values.

� +LHUDUFK\�YDULDEOHV represent hierarchies.

� +LHUDUFK\�QRGH�YDULDEOHV represent a node in a hierarchy.

� 7H[W�YDULDEOHV represent a text. You can use text variables in query descriptions, calculated key figures

and structural components. �

You can use text variables when creating calculated key figures, restricted key figures, selections and formulas, in the description of these objects.

� )RUPXOD�YDULDEOHV represent numerical values. You can use formula variables in formulas. In addition

to this, formula variables are used to define exceptions and conditions.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-23

SAP AG 2006

3URFHVVLQJ�7\SH�IRU�9DULDEOHV��

6$3�([LW

$XWKRUL]DWLRQ

&XVWRPHU ([LW

5HSODFHPHQW 3DWK

0DQXDO�(QWU\ ��'HIDXOW�9DOXH

+RZ�LV�D�YDULDEOH�ILOOHG�ZLWK�D�YDOXH�GXULQJ�D�TXHU\V��D�SODQQLQJ�IXQFWLRQV�RU�D�ZHE DSSOLFDWLRQV�UXQWLPH"

&DQ�EH�XVHG�IRU�DOO�YDULDEOH�W\SHV

�

� 0DQXDO�HQWU\�GHIDXOW�YDOXH allows you to enter the necessary value manually or to use the default

value specified when the variable was defined. This default value is defined for when the query or Web application is executed. When the query is executed, you can enter the value for the variable manually in a dialog box (the variable dialog), provided that the variable is ready for input. Otherwise, the variable’s default value (default value for the query) is used.

� When you create a variable, you have the option of specifying a GHIDXOW�YDOXH or not. If you define a

default value, it is then displayed for input-enabled variables in the input field of the variable dialog. For fields that are not input-enabled, the default value is used as the variable value.�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-24

SAP AG 2006


6$3�([LW

$XWKRUL]DWLRQ

&XVWRPHU ([LW

5HSODFHPHQW 3DWK



&DQ�EH�XVHG�IRU�FKDUDFWHULVWLF�YDOXH�YDULDEOHV��WH[W�YDULDEOHV�DQG�IRUPXOD�YDULDEOHV

�

� You can use the UHSODFHPHQW�SDWK to specify the value that automatically replaces the variable when

you execute the query or Web application.�� You can choose from the following replacement paths:

• 5HSODFH�E\�&KDUDFWHULVWLF�9DOXH - Text variables and formula variables can be replaced by a suitable characteristic value; you need to

set the offset start and the offset length for this processing type. <RX�FDQ�VDYH�DQ\�QXPEHU�RI�FKDUDFWHULVWLF�FRPELQDWLRQV�IRU�HDFK�VHOHFWLRQ.

• 5HSODFH�E\�4XHU\ - Characteristic value combinations that need to be set in the variable editor are replaced here by the

result of a query. You can now use the data result of the selected query as a variable in a different query.

• 5HSODFH�E\�9DULDEOH - Characteristic value variables, hierarchy variables, text variables and formula variables can take

their value from another variable. The YDULDEOH cannot be ready for input and it has to represent a single value. The VRXUFH�YDULDEOH must not be a hierarchy node variable, it has to be ready for input and it must be present in the query. The source variable must represent a single value or an interval. �

If you UHSODFH�ZLWK�D�YDULDEOH, the value is either determined from the key, the key's external attribute, the description or the attribute value. You need to specify the RIIVHW�VWDUW and RIIVHW�OHQJWK for output. The variable is replaced every time data is released on the variable screen. Define a text variable with automatic replacement if you want the text for the characteristic variables to be filled dynamically.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-25

SAP AG 2006


6$3�([LW

$XWKRUL]DWLRQ

&XVWRPHU ([LW

5HSODFHPHQW 3DWK


1577B

672C

2635A

z 9�EIO&=�{�F�E,�,� Q �& Q ¡ �C�� ^��¢ Q �) Q ¡ �C��z 9�EVO2=�{&F,E��¢ Q Q ¡ �,��

y E <JH @CM F

8�D,M F,O&c,D�E?cCD)\[H O<JB2F � O aI=N�NEG=�{,H c�F,E£ D,O?9)D,M�F,O)<JE \

¤ =09icCF2<GF,EG>fH O&Fb<JB2Fi@C9�>¥9�M D2<GF�c`{&D,M 9&F=�a?<JB2F[X�FCEIH =?c�aI=NE,F&D)@CB�@C9 ;&<I=?>iF,EF)¦,H <�j�Z&F2WdH O�O,H O2WhSiH <wBb<JB2F[��;&<vX�F�EVH =,c

§ DCEVH D,Z,M F`¨�@C9 ;&<G=?>`FCECF)¦0H <�©a�=NEN��;&<,cCD)\PH Ob<JB)FPX&FCEVH =?c

&DQ�EH�XVHG�IRU�DOO�YDULDEOH�W\SHV

+RZ�LV�D�YDULDEOH�ILOOHG�ZLWK�D�YDOXH�GXULQJ�D�TXHU\V��D�SODQQLQJ�IXQFWLRQV�RU�D�:HE�DSSOLFDWLRQV�UXQWLPH"

�

� The customer exit is a predefined enhancement that you can develop using customer-specific logic.

� The prerequisite here is that you created a project in transaction CMOD and that you have selected SAP

enhancement 565�� for global variables in reporting and you have assigned it to the enhancement project. You then activated the project.

� The &XVWRPHU�([LW processing type for variables enables you to determine default values for variables

by means of a function module exit. The function module used is (;,7B6$3/556�B��.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-26

SAP AG 2006


6$3�([LW

$XWKRUL]DWLRQ

&XVWRPHU ([LW

5HSODFHPHQW 3DWK



�

ª The 6$3�([LW processing type is contained in variables that are delivered as part of the Business

Content.�ª

You can find the delivered variables in the Metadata Repository if you use the search function to find variables.

ª The delivered SAP objects’s technical names always begin with a digit.

ª Example:

• If you want to define a query that only ever provides data from the current month, drag the "current month" standard variable (technical name: 0CMONTH) for the calendar year/month characteristic (technical name: 0CALMONTH) into the query’s filter.

ª Variables with the processing type 6$3�([LW can be created LQ�6$3�V\VWHPV�RQO\. Customers cannot

create any variables with processing type 6$3�([LW.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-27

SAP AG 2006


6$3�([LW

$XWKRUL]DWLRQ

&XVWRPHU ([LW

5HSODFHPHQW 3DWK



&DQ�EH�XVHG�IRU�FKDUDFWHULVWLF�YDOXH�YDULDEOHV�DQG�KLHUDUFK\�QRGHV

�

ª The $XWKRUL]DWLRQ processing type enables you to fill the variables automatically with the values from

the user’s authorization.�ª

The $XWKRUL]DWLRQ processing type is available for FKDUDFWHULVWLF�YDOXH�YDULDEOHV and KLHUDUFK\�QRGH�YDULDEOHV.

ª As a prerequisite, you must have maintained the authorizations in transaction RSECADMIN.�

ª If you choose 3URFHVVLQJ�E\�DXWKRUL]DWLRQ when you create a variable, the variable is filled

automatically with the values in the user’s authorization. When the user opens a query, the data selection is automatically carried out according to his or her authorizations.

ª Note that if you want the variables to be filled automatically, these variables cannot be input-enabled

and therefore the variable dialog does not need to appear when the query or Web application is executed. The user opens the query with the variable from the authorization and only the data that corresponds to his or her authorization appears automatically.�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-28

SAP AG 2006

9DULDEOH�&RQFHSW�LQ�%,�,QWHJUDWHG�3ODQQLQJ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�FRQFHSW�DQG�RSWLRQV�DVVRFLDWHG�

ZLWK�XVLQJ�YDULDEOHV�LQ�%,�LQWHJUDWHG�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-29

SAP AG 2006

([DPSOH�RI�&UHDWLQJ�D�9DULDEOH��8QLW�2YHUYLHZ�'LDJUDP




�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-30

SAP AG 2006

([DPSOH�RI�&UHDWLQJ�D�9DULDEOH��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�EDVLFV�RI�FUHDWLQJ�D�YDULDEOH�XVLQJ�

WKH�9DULDEOH�:L]DUG

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-31

SAP AG 2006

([DPSOH�RI�&UHDWLQJ�D�9DULDEOH��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�VHH�DQ�H[DPSOH�RI�XVLQJ�WKH�9DULDEOH�:L]DUG�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-32

SAP AG 2006

9DULDEOH�:L]DUG

�

ª The Variable Wizard helps you create variables; you use it in a step-by-step sequence when creating a

variable. ª

The individual steps are context-sensitive, depending on the combination of variable types and processing types; in this way, the system only offers you the selection options that are allowed for the particular combination of variable type and processing type.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-33

SAP AG 2006

([DPSOH�RI�&UHDWLQJ�D�6LPSOH�9DULDEOH��

�� ,Q�WKH�6HOHFWLRQ DUHD��VHOHFW�³6LQJOH�YDOXH´�DQG�³9DULDEOHV´�LQ�WKH�9LHZ DUHD�

�� &KRRVH�&UHDWH WR�FUHDWH�D�QHZ�YDULDEOH�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-34

SAP AG 2006


�� (QWHU�WKH�YDULDEOH�QDPHV�DQG�GHVFULSWLRQV�DQG�VSHFLI\�WKH�SURFHVVLQJ�W\SH�IRU�WKH�YDULDEOHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-35

SAP AG 2006


�� 6HW�WKH�RSWLRQV�³6LQJOH�YDOXH´ DQG�³2SWLRQDO´��IRU�H[DPSOH

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-36

SAP AG 2006


�� 6HOHFW�WKH�³GHIDXOW�YDOXHÍRU�WKH�YDULDEOH

�� &KHFN�WKDW�WKH�VHWWLQJV�\RX�PDGH�ZHUH�FRUUHFW�DQG�FOLFN�RQ�³6DYH´�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-37

SAP AG 2006

9DULDEOH�&RQFHSW�LQ�%,�,QWHJUDWHG�3ODQQLQJ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�EDVLFV�RI�FUHDWLQJ�D�YDULDEOH�XVLQJ�

WKH�9DULDEOH�:L]DUG

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 3-38

SAP AG 2006

)LOWHUV�DQG�9DULDEOHV�LQ�%,�,QWHJUDWHG�3ODQQLQJ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�XVH�RI�YDULDEOHV�LQ�SODQQLQJ� $VVHVV�WKH�YDULDEOH�FRQFHSW�LQ�%,�LQWHJUDWHG�

SODQQLQJ� 8QGHUVWDQG�WKH�FUHDWLRQ�RI�D�YDULDEOH��XVLQJ�DQ�

H[DPSOH

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-1

SAP AG 2006

&RQWHQW�� 3ODQQLQJ�)XQFWLRQ�7\SHV� &RQILJXULQJ�D�3ODQQLQJ�)XQFWLRQ� 6HOHFWHG�6WDQGDUG�3ODQQLQJ�)XQFWLRQV

3ODQQLQJ )XQFWLRQV ² %DVLFV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-2

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�%DVLFV��/HDUQLQJ�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 'LIIHUHQWLDWH�EHWZHHQ�WKH�SODQQLQJ�IXQFWLRQ�W\SHV� 8QGHUVWDQG�KRZ�D�SODQQLQJ�IXQFWLRQ�LV�HVVHQWLDOO\�

FRQILJXUHG�DQG�ZKDW�\RX�QHHG�WR�SD\�DWWHQWLRQ�WR� 0DS�LQGLYLGXDO�SODQQLQJ�IXQFWLRQV�WR�WKH�V\VWHP

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-3

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�%DVLFV��&RXUVH�2YHUYLHZ�'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-4

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�%DVLFV��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�UHVSRQVLEOH�IRU�LPSOHPHQWLQJ�%,�LQWHJUDWHG�SODQQLQJ�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�FRQILJXUDWLRQ�RI�D�SODQQLQJ�IXQFWLRQ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-5

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�7\SHV��8QLW�2YHUYLHZ�'LDJUDP

� /HVVRQ��6HOHFWHG�6WDQGDUG�3ODQQLQJ�)XQFWLRQV

8QLW�2YHUYLHZ� /HVVRQ��3ODQQLQJ�)XQFWLRQ�7\SHV� /HVVRQ��&RQILJXULQJ�D�3ODQQLQJ�)XQFWLRQ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-6

SAP AG 2006

3ODQQLQJ�)XQFWLRQ�7\SHV��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�ZKLFK�W\SHV�RI�SODQQLQJ�IXQFWLRQV�H[LVW� 5HFRJQL]H�WKDW�ZKHQ�VHOHFWLQJ�D�SODQQLQJ�IXQFWLRQ��

\RX�KDYH�WR�GHFLGH�EHWZHHQ�FRPSOH[LW\�DQG�IXQFWLRQDOLW\

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-7

SAP AG 2006

3ODQQLQJ�)XQFWLRQ�7\SHV��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�DQ�RYHUYLHZ�RI�WKH�GLIIHUHQW�SODQQLQJ�IXQFWLRQ�W\SHV�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-8

SAP AG 2006

%XVLQHVV�5HTXLUHPHQWV�DQG�,PSOHPHQWLQJ�WKHP�LQ�%,�,QWHJUDWHG�3ODQQLQJ�² 6WDQGDUG�3ODQQLQJ�)XQFWLRQV

&RS\�IURP�DFWXDO�WR�SODQ

5HYDOXDWH�SODQQHG�VDOHV�E\��

'LVWULEXWH�VXSSOLHV�WR�SURGXFWV

4XDQWLW\�[�SULFH

'HOHWH�WKH�GDWD�LQ�D�SODQ�YHUVLRQ

7UDQVODWH�FXUUHQF\�IURP�(85�WR�86'

&RQWULEXWLRQ�PDUJLQ�VFKHPH

&DOFXODWH�WXUQRYHU�GHSHQGLQJ�RQ�ZRUNGD\V�DFFRUGLQJ�WR�IDFWRU\�FDOHQGDU�

6WDQGDUG�SODQQLQJIXQFWLRQV&RS\

'LVWULEXWLRQ�ZLWK�UHIHUHQFH�GDWD

'HOHWH!

&XUUHQF\�WUDQVODWLRQ�5HYDOXDWLRQ

�

� When you map a business process, you normally need a large number of SUHGHILQHG�SODQQLQJ�IXQFWLRQV to generate or change plan data.

� BI integrated planning provides a large number of different VWDQGDUG�SODQQLQJ�IXQFWLRQV that can be

used for all planning requirements. �

Standard planning functions are functions with a predefined behavior that are easy to use. These include:

• Copying

• Currency translation

• Deleting

• Reposting

• Revaluating

• Unit conversion

• Deleting invalid combinations

• Reposting on the basis of characteristic relationships �

The functions mentioned above are composed exclusively of characteristic relationships and are examined in more detail in unit 6.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-9

SAP AG 2006

%XVLQHVV�5HTXLUHPHQWV�DQG�,PSOHPHQWLQJ�WKHP�LQ�%,�,QWHJUDWHG�3ODQQLQJ�² )2;�)RUPXOD�(GLWRU �

)R[�IRUPXOD


'LVWULEXWH�VXSSOLHV�WR�SURGXFWV 'HOHWH�WKH�GDWD�

LQ�D�SODQ�YHUVLRQ5HYDOXDWH�SODQQHG�

VDOHV�E\�� 7UDQVODWH�FXUUHQF\�IURP�(85�WR�86'

4XDQWLW\�[�SULFH&RQWULEXWLRQ�PDUJLQ�VFKHPH


�

� If one of the standard planning functions mentioned before is not able to execute the algorithm that you

require, you should model the function algorithm individually using the )2;�IRUPXOD�HGLWRU��)2;� �IRUPXOD�H[WHQVLRQ�.

� FOX is not simply a means of carrying out simple arithmetic operations, such as contribution margin

accounting: you can also use it as a very flexible and powerful tool for defining complex formulas that may require you to work with loops, read attributes, include variables and so on.

� It is not necessary to have programming knowledge of ABAP, Java or similar if FOX formulas are

compiled.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-10

SAP AG 2006

%XVLQHVV�5HTXLUHPHQWV�DQG�,PSOHPHQWLQJ�WKHP�LQ�%,�,QWHJUDWHG�3ODQQLQJ�² &XVWRPHU�6SHFLILF�3ODQQLQJ�)XQFWLRQV

&XVWRPHU�VSHFLILF�SODQQLQJ�IXQFWLRQ


'LVWULEXWH�VXSSOLHV�WR�SURGXFWV 'HOHWH�WKH�GDWD�

LQ�D�SODQ�YHUVLRQ5HYDOXDWH�SODQQHG�

VDOHV�E\�� 7UDQVODWH�FXUUHQF\�IURP�(85�WR�86'

4XDQWLW\�[�SULFH&RQWULEXWLRQ�PDUJLQ�VFKHPH


�

� If it is not possible to map a planning function using the functions provided as standard, you can create a FXVWRPHU�VSHFLILF�SODQQLQJ�IXQFWLRQ. You do not need any knowledge of ABAP to do this.

� This function type is examined in unit 9.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-11

SAP AG 2006

3ODQQLQJ�)XQFWLRQV��&RPSOH[LW\�YHUVXV�)XQFWLRQDOLW\

6WDQGDUG�SODQQLQJ�IXQFWLRQV

)R[�IRUPXODV

&XVWRPHU�VSHFLILF�SODQQLQJIXQFWLRQV

&RPSOH[LW\��IXQFWLRQDOLW\

�

� The standard planning functions are the easiest to define. You can set them up simply and you can

influence their behavior in their Customizing, but only with regard to certain conditions. �

FOX formulas are a powerful tool for creating planning functions. FOX contains language elements that are normally only contained in programming languages, such as If queries and loops. This means that FOX formulas are able to cover most business requirements that cannot be modeled using standard planning functions.

� However, because of this ability to write their own programs, FOX formulas are more complex than

standard planning functions. �

Customer-specific planning functions are set up using ABAP programming language and supply all the functions available to a programming language.

� This is the most complex type of planning function, but also the most flexible.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-12

SAP AG 2006

2YHUYLHZ�RI�3ODQQLQJ�)XQFWLRQ�7\SHV

• Unit conversion • Generating combinations• Formula • Copying• Deleting• Deleting invalid combinations• Reposting• Reposting on the basis of

characteristic relationships• Revaluation • Distribution by key• Distribution by reference data • Currency translation• Customer-defined planning function

types (by user exit)

3ODQQLQJ�)XQFWLRQ�7\SHV�RI�WKH�%,�,QWHJUDWHG�3ODQQLQJ

�

� $JJUHJDWLRQ�OHYHOV�DUH�D�SUHUHTXLVLWH�IRU�FUHDWLQJ�SODQQLQJ�IXQFWLRQV. Planning functions are created

on aggregation levels; the planning functions can be created and executed on any active aggregation level. �

� You can use filters to select the data.

� The filter and the planning function are combined by the SODQQLQJ�VHTXHQFH, which makes it possible to

execute them directly or process them in a batch as part of a BW process chain. �

The planning function objects are displayed in the 'DWD�:DUHKRXVLQJ�:RUNEHQFK in the %XVLQHVV�&RQWHQW and 7UDQVSRUW�&RQQHFWLRQ function areas in the 3ODQQLQJ�IROGHU.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-13

SAP AG 2006

3ODQQLQJ )XQFWLRQ 7\SHV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�ZKLFK�W\SHV�RI�SODQQLQJ�IXQFWLRQV�H[LVW� 5HFRJQL]H�WKDW�ZKHQ�VHOHFWLQJ�D�SODQQLQJ�IXQFWLRQ��

\RX�KDYH�WR�GHFLGH�EHWZHHQ�FRPSOH[LW\�DQG�IXQFWLRQDOLW\

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-14

SAP AG 2006

&RQILJXULQJ�D�3ODQQLQJ�)XQFWLRQ��8QLW�2YHUYLHZ�'LDJUDP



�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-15

SAP AG 2006

&RQILJXULQJ�D�3ODQQLQJ�)XQFWLRQ��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�WR�FRQILJXUH�D�SODQQLQJ�IXQFWLRQ�

DQG�ZKDW�WR�SD\�DWWHQWLRQ�WR�ZKHQ�UHFRQFLOLQJ�WKH�ILOWHU�DQG�WKH�SODQQLQJ�IXQFWLRQ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-16

SAP AG 2006

&RQILJXULQJ�D�3ODQQLQJ�)XQFWLRQ��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�LPSOHPHQWDWLRQ�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�FRQILJXUDWLRQ�RI�WKH�VWDQGDUG�SODQQLQJ�IXQFWLRQV�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-17

SAP AG 2006

0RGHOLQJ�D�3ODQQLQJ�)XQFWLRQ��&RS\�)XQFWLRQ�([DPSOH

,QLWLDO�GDWD�UHFRUG�

1HZ�GDWD�UHFRUG ��

��

$PRXQW

��&�',9��

��&�',9��

4XDQWLW\9HUVLRQ)LVFDO\HDU

'LYLVLRQ

³&KDUDFWHULVWLF�WR�EH�FKDQJHG´

&RS\LQJ�IURP�YHUVLRQ��WR�YHUVLRQ��

�

� Every SODQQLQJ�IXQFWLRQ is JHQHULF; in other words, the EXVLQHVV�ORJLF has to be realized by

configuring a planning function. �

Then you decide what W\SH�RI�SODQQLQJ�IXQFWLRQ matches your requirements. �

You can use what are known as VHJPHQW�OHYHO�FKDUDFWHULVWLFV to separate the characteristics from the aggregation level into the FKDUDFWHULVWLFV�WR�EH�FKDQJHG and the FRQGLWLRQ�FKDUDFWHULVWLFV.

� You can use the “&KDUDFWHULVWLFV�WR�EH�FKDQJHG” to specify which characteristic values the planning

function changes when it processes a data record in the target data record, compared to the initial data record.

• The figure above shows that the “Version” characteristic is selected for the "Characteristics to be changed".

� Then the SDUDPHWHUL]DWLRQ�RI�WKH�SODQQLQJ�IXQFWLRQ can be provided; so in the example above,

version 1 and version 2 represent the parameterization. �

During parameterization, you can also control whether the function is carried out for all key figures or for one specific key figure only.

� Please note that the planning function can only be executed in the 3ODQQLQJ�0RGHOHU via a SODQQLQJ�VHTXHQFH that links a filter to the function.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-18

SAP AG 2006

0RGHOLQJ�D�3ODQQLQJ�)XQFWLRQ��([DPSOH�RI�WKH�5HYDOXDWLRQ�)XQFWLRQ

5HYDOXDWLRQ�IRU�PDWHULDO�JURXS�-XLFH��5HYDOXDWLRQ�IRU�PDWHULDO�JURXS�:DWHU��

��4XDQWLW\

��-XLFH��:DWHU7XUQRYHU0DWHULDO�*URXS

³&RQGLWLRQ�FKDUDFWHULVWLF´

Condition 1: Revaluate Water by 10% for all key figures

Revaluate Juice by 20% for all key figures

Condition 2:

�

� ³&RQGLWLRQ�FKDUDFWHULVWLFV´ are the characteristics that are not included in the “ characteristics to be

changed” . For these, you can define a FRQGLWLRQ, although you do not have to. �

In the above example with the revaluation function, different conditions are to be defined for the individual material groups. To make this possible, the Material Group field has to be included in the “ condition characteristics” .

� Only characteristic conditions can be specified for defining the revaluation function.

� However, there are functions whose definition offers characteristics that are to be changed as well as

condition characteristics. �

You should avoid the possibility of using conditions to restrict a filter further because if condition fields are required then this shows that too many data records were selected in the filter, meaning that too much data is locked.

� You should therefore keep the filter selections as narrow as possible and use condition fields with care.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-19

SAP AG 2006

'DWD�6HOHFWLRQ�LQ�3ODQQLQJ�)XQFWLRQV

��

3ODQQLQJ�IXQFWLRQ

5HDO�WLPH�,QIR&XEH

&KDQJH�WUDQVDFWLRQ�GDWD

,PSRUW�UHIHUHQFH�GDWD

,QIR&XEH'DWD6WRUHREMHFW

�

� A planning function can use two types of plan data:

• Data that is supposed to be changed by the function. This is transaction data.

• Data that is imported so that the function can be executed. This is reference data. �

Only data records in the real-time InfoProvider that is used as the basis can be changed. The transaction data is locked when the function is executed.

� Note that the selection of the planning function and the query have to match. Data not contained in the

selection for the filter that is used for the planning function cannot be changed because there is no write access to these attributes. This is explained using examples on the next two slides.

� The system automatically determines the reference data that is needed to execute the planning function.

Reference data is not locked when the function is executed. Reference data can come from any InfoProviders.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-20

SAP AG 2006

)LOWHU�6HOHFWLRQ�IRU�3ODQQLQJ�)XQFWLRQV

$OO�WKH�FKDQJHG�UHFRUGV�PXVW�EH�LQ�WKH�ILOWHU�IRU�WKH�SODQQLQJ�IXQFWLRQ�WR�EH�H[HFXWHG�

��&RS\ IXQFWLRQ�

��5HSRVWLQJ IXQFWLRQ

)LVFDO \HDU �� )LVFDO \HDU ��&RS\

)LOWHU�GRHV�QRW�QHHG�WR�FRQWDLQ�ILVFDO�\HDU��

)LVFDO \HDU �� )LVFDO \HDU ��5HSRVW

)LOWHU�PXVW�FRQWDLQ�ILVFDO�\HDU��DQG��

,QLWLDO�GDWD�UHFRUG�ZLWK�ILVFDO�\HDU��KDV�QRW�FKDQJHG

,QLWLDO�GDWD�UHFRUG�ZLWK�ILVFDO�\HDU��KDV�FKDQJHG

�

� The above diagram shows which selections of characteristic attributes have to be included in the filter if

the filter is used to execute a planning function. �

The choice of selections depends on the behavior of the planning function in question. Copy functions always read initial data records and also write new data records. Reposting and distribution functions change the change data records and also write new data records.

� The illustration above does not explain how the change data records are changed. This is explained on

the next slide.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-21

SAP AG 2006

+RZ�DUH�'DWD�5HFRUGV�&KDQJHG"�

��

$PRXQW)LVFDO\HDU

)LVFDO \HDU �� )LVFDO \HDU ��5HSRVWLQJ

5HSRVW IXQFWLRQ

0DQXDO�GDWD�FKDQJH�LQ�WKH�SODQ�TXHU\

�� !��"�#�$!"��

��

$PRXQW)LVFDO\HDU

��

�%�!��&'(�)� *+��'�� ,-�� !��.��/0(�!�� )� ��,��#�-�� "��1$""�+�2��43!��0"��56'�+�--7+�� )� *+�� -�#�� 1��'�108�� 2�� 3!��0!0"9

'HOHWH )XQFWLRQ! )LVFDO \HDU �� )LVFDO \HDU ��'HOHWH!

�%�!��&'"�.� *+��'�� ,-��! !��.�:� ��.� ��#��) ��'"�,'$�(��43(��08�

�

� The top diagram shows how data records are changed if you change the plan query plan data manually

or plan data is changed by planning functions. �

In general, functions such as reposting and distribution change the initial data records and also write new data records.

� When the initial data records are changed, new data records are always created; you can think of these

as negative delta records. The additional, new data records represent positive delta records. �

Please note that if you use the delete function, negative delta records are added to the initial data records and these delta records have the same amount as the initial data records.

� Also note that the initial data records can never be overwritten.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-22

SAP AG 2006

&RQILJXULQJ�D�3ODQQLQJ�)XQFWLRQ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�WR�FRQILJXUH�D�SODQQLQJ�IXQFWLRQ�

DQG�ZKDW�WR�SD\�DWWHQWLRQ�WR�ZKHQ�UHFRQFLOLQJ�WKH�ILOWHU�DQG�WKH�SODQQLQJ�IXQFWLRQ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-23

SAP AG 2006

6HOHFWHG�6WDQGDUG�3ODQQLQJ�)XQFWLRQV��8QLW�2YHUYLHZ�'LDJUDP



�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-24

SAP AG 2006

6HOHFWHG�6WDQGDUG�3ODQQLQJ�)XQFWLRQV��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�H[DPSOHV�RI�WKH�PRVW�IUHTXHQWO\�

XVHG�VWDQGDUG�SODQQLQJ�IXQFWLRQV�DUH�FRQILJXUHG� 8QGHUVWDQG�ZKLFK�SURSHUWLHV�WKH�LQGLYLGXDO�

SODQQLQJ�IXQFWLRQV�KDYH

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-25

SAP AG 2006

6HOHFWHG�6WDQGDUG�3ODQQLQJ�)XQFWLRQV��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�ILQG�RXW�PRUH�DERXW�WKH�SURSHUWLHV�RI�WKH�PRVW�IUHTXHQWO\�XVHG�VWDQGDUG�SODQQLQJ�IXQFWLRQV�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-26

SAP AG 2006

*HQHULF�3ODQQLQJ�)XQFWLRQV�LQ�%,�,QWHJUDWHG�3ODQQLQJ

• &RS\LQJ• 5HYDOXDWLRQ��• 'HOHWLQJ• 5HSRVWLQJ• Currency translation• Unit conversion• Distribution by key • Distribution by reference data • Formula• Customer-defined planning function

types (by user exit)

• Generating combinations• Reposting on the basis of

characteristic relationships• Deleting invalid combinations

3ODQQLQJ�)XQFWLRQ�7\SHV�LQ�%,�,QWHJUDWHG�3ODQQLQJ

�

� The above illustration gives a highlighted overview of the planning functions that will be discussed in

this unit.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-27

SAP AG 2006

&RS\ )XQFWLRQ

�

� In the above example, the copy function is used to copy actual data from an InfoCube to a real-time

InfoProvider. �

In this case, you would set both the version and the InfoProvider characteristic in the “ FKDUDFWHULVWLFV�WR�EH�FKDQJHG” . In the example above, no condition characteristics were set. The parameter records contain the actual rules for copying. These are specified in the “)URP�ILHOG” and the “7R�ILHOG” .

� Note that the copy function is always set to RYHUZULWH 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, to a target interval, to a hierarchy node or to a variable.

� If you saved multiple simultaneous attributes for a sender characteristic and you copy to a characteristic

attribute of a target characteristic, all the sender data records are summarized and copied to the target attribute.

� You can decide whether all the key figures are to be copied or only individual ones.

� You have to save a planning function first so that you can execute it later. You always have to save,

even if the function has not been configured correctly. You can always use the “ Check” button to check a function's consistency.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-28

SAP AG 2006

'HOHWH�)XQFWLRQ"

�

� You can use the GHOHWH function type to delete the key figure values from the selected data record. The

function creates additional data records in the form of offsetting postings (minus symbol). �

No characteristic values are changed. This means that, in the segment level characteristics, you can select characteristics as condition characteristics only, not as “ Characteristics to be changed” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-29

SAP AG 2006

5HYDOXDWLRQ�)XQFWLRQ

�

� Normally, plan data records are created by copying the actual data, or by copying from one plan version

to another and then revaluating. Then, the revaluated data is revised manually. �

Percentages, or variables of percentages, need to be determined as revaluation factors. In the example above, a variable was set for the key figure “ Costs in statistics currency” . For the “ Quantity in base units” key figure, on the other hand, a fixed percentage was set.

� The figure above shows a revaluation in which different percentages are to be used for the individual

material groups. Here, it is enough to create a function with different conditions for the individual material groups, rather than creating multiple planning functions. The material group is therefore a condition characteristic.

� Whilst the planning functions are being executed, the system checks the material groups contained in

the filter and carries out a comparison to establish whether the material groups formulated in the function's condition are contained in the filter. The system then executes the planning function for the individual conditions.

� Here, as elsewhere, only the key figures of existing data records can be changed, meaning that no

characteristic can be selected as a “ Characteristic to be changed” . �

You can choose whether you want to enter a common percentage for all key figures or revaluate any key figures with individual percentages.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-30

SAP AG 2006

5HSRVW�)XQFWLRQ

� 2OG�PRGHO�LV�SKDVHG�RXW� 3ODQ�GDWD�IURP�ROG�PRGHO�DYDLODEOH

5HSRVWLQJ�SODQQHG�YDOXHV�WR�WKH�QHZ�SURGXFW

:ULWLQJ QHJDWLYH�GHOWD UHFRUGV

:ULWLQJ SRVLWLYH�GHOWD UHFRUGV

�

; You can use the 5HSRVW�function type to post the key figure values from existing characteristic

combinations to other combinations (similar to the &RS\ function). Unlike copying, the repost function writes credit lines that are offset against the original debit to zero in the buffer.

; Typically, you would use this function to remove an account assignment error.

; You can use the key figure selection table to determine which key figures are reposted.

; You can use the %HIRUH�DQG�DIWHU�YDOXHV�IRU�WKH�UHSRVWLQJ�SURFHGXUH table to create either a simple

reposting procedure or various reposting procedures in a planning function. ;

The following rules apply:

• Both the before and after values for the reposting procedures have to be singe values.

• Both the before and after values are changed and therefore have to be in the filter that is transferred to the planning function.

• During reposting, the key figure values are always added to the after values.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-31

SAP AG 2006

6HOHFWHG�6WDQGDUG�3ODQQLQJ�)XQFWLRQV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�H[DPSOHV�RI�WKH�PRVW�IUHTXHQWO\�

XVHG�VWDQGDUG�SODQQLQJ�IXQFWLRQV�DUH�FRQILJXUHG� 8QGHUVWDQG�ZKLFK�SURSHUWLHV�WKH�LQGLYLGXDO�

SODQQLQJ�IXQFWLRQV�KDYH

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-32

SAP AG 2006

3ODQQLQJ )XQFWLRQV %DVLFV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 'LIIHUHQWLDWH�EHWZHHQ�WKH�SODQQLQJ�IXQFWLRQ�W\SHV� 8QGHUVWDQG�KRZ�D�SODQQLQJ�IXQFWLRQ�LV�HVVHQWLDOO\�

FRQILJXUHG�DQG�ZKDW�\RX�QHHG�WR�SD\�DWWHQWLRQ�WR� 0DS�LQGLYLGXDO�SODQQLQJ�IXQFWLRQV�WR�WKH�V\VWHP

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-33

([HUFLVHV�

8QLW�� 3ODQQLQJ�)XQFWLRQV�±�%DVLFV�/HVVRQ�� 6HOHFWHG�6WDQGDUG�3ODQQLQJ�)XQFWLRQV�


• Understand the configuration of the standard planning functions within BI integrated planning

• Create individual planning functions and additional variables

Once the CFO has completed quantity planning in version A for fiscal year 2010 and 2011, the data is to be copied into another version and then distributed to the finer granularity of the material groups by means of a distribution function. In the context of multi-level planning this has resulted in default values for the sales managers. The data is then to be reposted within the material groups. Quantity planning is then complete. It is the result of the mere “ break down” of the values of the CFo to the granularity of the sales manager, generally, controlling area, company code, goods group.

Price and production cost planning follows, but this takes place on a separate InfoProvider. This planning should also be done by the sales managers, whereby the granularity of this planning only depends on the material groups, in contrast to quantity planning. Planning should take place in two versions in parallel. One of the two versions is created through a copy and revaluation function, whereby the data can be revised manually. A deletion function is also to be made available so that the data of the second version can be deleted again, if necessary. After the sales manager has been able to plan the prices and production costs in two versions, he has to choose a version. He then copies this chosen version to a “ consolidated” version in which quantity planning is also available.

1-1 For quantity planning within aggregation level 6��B$/B��create a new ILOWHU�by copying filter 6��B)B�� Enter the following descriptions: Technical name:6��B)B�� Description:�� 7%:��B6��B$/��B)��Select “.H\” �in the Display area.

1-1-1 Following that, you need to configure the copy function for copying from version A to B. Which of the two versions PXVW�be included in the filter? _____________________________________________________________

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-34

Select this YHUVLRQ in your filter and�VDYH it.

1-1-2 Now configure the FRS\�IXQFWLRQ to copy the data of version A to version B and only for the VDOHV�TXDQWLW\�key figure. Create the function for the previously created aggregation level 6��B$/B��. Enter the following descriptions: Technical name: 6��B3)B�� Description: 7%:��B6��B$/��B3)��BFRS\ ��Which field is to be selected as “&KDQJHG” ?��BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB��No field is to be selected in the “XVHG�LQ�FRQGLWLRQV” area.��Limit the execution of the function to the VDOHV�TXDQWLW\�key figure and enter the concrete processing rule in the input template.��6DYH�the IXQFWLRQ.

1-1-3 Now create a sequence to test whether the function can be executed for the default fiscal year. Enter the following descriptions for the sequence: Technical name: 6��B6B�� Description: 7%:��B6��B$/��B6�� Ass the “6WHS�IRU�SODQQLQJ�IXQFWLRQV” and link filter 6��B)B��to function 6��B3)B��. Then VDYH�the�VHTXHQFH.

1-1-4 Now execute this sequence in the WUDFH. Do so for the default fiscal year ��of the variables from the filter. Please take a look at the data for EORFN�� for example. It should be displayed as follows:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-35

Then set the variable to ��and execute the function again. Now VDYH your SODQQLQJ�GDWD for the first time in order to generate the initial data in versions B for a later task. The reset the YDULDEOH�to ��and VDYH the VHTXHQFH again. Your InfoProvider should now contain the following data records. Check this for yourself.

1-2 The planning data of quantity planning in version B of the CFOs represents the default values for the VDOHV�PDQDJHUV� Since the planning granularity of the sales managers is the controlling area, company code and material group, you need to create an aggregation level first. You then need to create another filter and a distribution function that breaks down the default values to material groups.

1-2-1 First, create a new aggregation level by copying aggregation level 6��B$/B�� and include the characteristic that describes the detailed planning level of the sales managers in the level. Which characteristic is this? _____________________________________________________________ Enter the following description for the new aggregation level: Technical name: 6��B$/B�� Description: 7%:��B6��B$/�� and DFWLYDWH the aggregation level after including the characteristic.

1-2-2 Now define a filter for this aggregation level, which is to be used for the distribution function. Technical name:�� 6��B)B��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-36

Description: 7%:��B6��B$/��B)�� . Now enter >.H\@�for “'LVSOD\” � Include all characteristics of the aggregation level and, for version %, select unit of measure 3&��and currency 86'� The company codes are ��and��the controlling area is ��.��is to be selected as the fiscal year variant and variable *URXS��B9$5B)<B��B30 is to be selected for the fiscal year. How does modeling of the selection for the material group characteristic have to be made, if this filter is later used for the distribution to material group water and juice? Material group: _______________________________________________ Select these characteristic values into the filter and VDYH�it.

1-2-3 Now create a GLVWULEXWLRQ�IXQFWLRQ�DFFRUGLQJ�WR�WKH�NH\V�created in the DJJUHJDWLRQ�OHYHO�in your task ��in order to perform the distribution from controlling area, company code to the material group. The distribution is to be performed only for the key figure VDOHV�TXDQWLW\� Model the distribution function according to this information and use the following descriptions: Technical name: 6��B3)B�� Description: 7%:��B6��B$/��B3)��B',675,%B.(< Which field is to be selected as “&KDQJHG” ?��BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB��In the configuration of the corresponding parameter record choose the distribution variant “'LVWULEXWH�“QRW�DVVLJQHG��” �RQO\” ��Select the parameter row and press the “&UHDWH�E\�YDOXH” �pushbutton in order to define two rows for the recipients of the distribution rule. Select one material group into each of the two distribution rows. Leave the entries for the weighting factor blank. Then�VDYH�the function.

1-2-4 The keys for the distribution to the two material groups Water (WAT) and Juice (JUC) are not to be defined as predefined values but as variables so that the sales manager can set the weighting factors in a decentralized way. For this purpose create a variable for each distribution factor, for each rule row within the distribution function role, using the following description:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-37

Variable for weighting factor water: Variable name:� 6��B9$5B'LVWULEB.H\:$7�Description: 6��B9$5B'LVWULEB.H\:$7 Variable for weighting factor juice: Variable name:� 6��B9$5B'LVWULEB.H\-8&�Description: 6��B9$5B'LVWULEB.H\-8& You need to make the following system settings for both variables: Processing By: ´ 0DQXDO�HQWU\�GHIDXOW�YDOXHV Variable Input Is: 0DQGDWRU\ Ready for Input: 6HOHFW� Default values: ��IRU�ZDWHU�RU�IRU�MXLFH� After the variables have been created, they are to be included in their respective rule row instead of the weighting factor. 6DYH your planning function again.

1-2-5 To be able to test again whether your planning function works correctly you should create another planning sequence and merge the function and the filter 6��B)B�� of aggregation level 6��B$/B�� Here, enter the following descriptions for the sequence: Technical name: 6��B6B�� Description: 7%:��B6��B$/��B6�� 6DYH�the configuration. 7UDFH the sequence for the variable default setting (��) and then look at the data development by means of %ORFN��. You should get the following display:

'R�QRW�VDYH�the plan data. Stay in Planning Modeler.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-38

1-3 Now that the data is available at the correct granularity of controlling area, company, material group for the sales managers, the data is to be reposted IURP�PDWHULDO�JURXS�:$7��ZDWHU��WR�7:$7��IRU�WDEOH�ZDWHU��because the company had been restructured. Modeling is to take place within aggregation level 6��B$/B��.

1-3-1 For this purpose, create another filter in this aggregation level by copying filter 6��B)B�� and enter the following description: Technical name�� 6��B)B�� Description: 7%:��B6��B$/��B)�� .�

Compared to filter 6��B)B��how does this new filter have to be configured with regard to the material group? Material group: _______________________________________________ Make the adjustment and then save the filter.

1-3-2 Now, create a UHSRVW�IXQFWLRQ that performs the reposting for the key figure sales quantity. Enter the following descriptions for the function: Technical name: 6��B3)B�� Description: 7%:��B6��B$/��B3)��B5(3267 Which field is to be selected as “&KDQJHG” ? _____________________________________________________________ Once again, limit the function to the key figure VDOHV�TXDQWLW\�and configure the concrete reposting rule��6DYH�the IXQFWLRQ.

1-3-3 Now create another planning sequence that includes filter 6��B)B��and the UHSRVWLQJ�IXQFWLRQ in order to test whether the function works correctly. Here, enter the following descriptions for the sequence: Technical name: 6��B6B�� Description: 7%:��B6��B$/��B6�� 6DYH�the sequence. 7UDFH the sequence for the default setting of your variable for fiscal year �� and then look at the data development by means of %ORFN��. You should get the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-39

'R�QRW�VDYH�the plan data. This concludes the quantity planning of the sales managers.

1-4 Price and production cost planning, which are also done by the sales managers, take place in a separate real-time InfoProvider. In contrast to quantity planning, the granularity for prices and production costs is only on the material group!

1-4-1 For this purpose, select the real-time InfoProvider 7%:��3�� (where ## = monitor number) that is intended for price and production cost planning in the ,QIR3URYLGHU�area.

1-4-2 For this InfoProvider, create an aJJUHJDWLRQ�OHYHO with the following description. Technical name: 3��B$/B�� Description: 7%:��B3��B$/�� Include all InfoObjects in the aggregation level, except for the characteristic customer group and posting period, and then DFWLYDWH�it.

1-4-3 Now create a ILOWHU for price and production cost planning and enter the following descriptions: Technical name: 3��B)B�� Description: 7%:��B3��B$/��B)�� Select DOO�ILHOGV�RI�WKH�DJJUHJDWLRQ�OHYHO and choose the following FKDUDFWHULVWLF�YDOXHV for the individual characteristics:

1. Characteristic in the filter 2. Characteristic value to be selected

3. Material or goods group 4. TWAT, JUC

5. Currency 6. USD

7. Fiscal year 8. Variable: Group##_VAR_FY_01_PM

9. Version 10. B1, B2, B

11. Fiscal year variant 12. K4

Please note that the two versions, B1 and B2, correspond to optimistic and pessimistic price and production cost planning. That is, sales planners can plan in two different versions and then have to decide on a planning version later, which they then copy into version B. Version B then not only contains the quantity planning data but also the price and production planning data.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-40

6DYH�the settings in the filter.

1-4-4 In order to be able to look at the input template again as a test layout or buffer display and to enter some test data manually, you should define another sequence and assign filter 3��B)B��of aggregation level 3��B$/B��as “6WHS�IRU�WKH�LQSXW�WHPSODWH” � Enter the following descriptions for the sequence: Technical name: 6��B6B�� Description: 7%:��B3��B$/��B6�� 6DYH�the sequence. Now execute the “ ,QSXW�WHPSODWH” �for fiscal year ��and look at the data for %ORFN�.

From the InfoProvider perspective, the following data in version B1 is already planned for you:

1-5 In the following, the typical planning process of the sales managers is to be started for price and production cost planning. First, the planner is to plan manually in version B1, then copy the data into version B1 via a copy function. Following that, the planner is to use a revaluation function for the data of version B2, whereby the sales manager is to set the revaluation factor as a variable. Following that, the data of version B2 is to be revised manually and finally, the planner is to be able to decide whether version B1 or B2 is to be the binding or consolidated version for him. Finally, the user can decide decentralized which of the two versions is to be copied to version B by means of a copy function with a variable on the sender version.

1-5-1 First, create a FRS\�IXQFWLRQ�for aggregation level 3��B$/B��which copies DOO key figures from version %��to %�� Enter the following descriptions: Technical name: 6��B3)B�� Description: 7%:��B3��B$/��B3)��B&23< Which field is to be selected as “&KDQJHG” ? _____________________________________________________________ Select the concrete processing rule, then VDYH the function.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-41

1-5-2 Now create another planning sequence that includes filter 6��B)B��and the FRS\�IXQFWLRQ in order to test whether the function works correctly. Here, enter the following descriptions for the: Technical name: 3��B6B�� Description: 7%:��B3��B$/��B6�� 6DYH�the sequence. 7UDFH this for default fiscal year �� and then look at the data development for %ORFN��.

You should get the following display:

'R�QRW�VDYH�the plan data.

1-5-3 The sales manager is now supposed to be able to UHYDOXDWH�the data that was just copied; this is to be possible only in version B2.� The function is now to be executed for the fiscal year again according to the set YDULDEOH and is now to be modeled so that the revaluation percentages are set using variables. In doing so, you need to consider that the valuation percentage is identical for both key figures price and production costs and is only applied to specific material groups, that is material groups TWAT and JUC. Revaluation only takes place within version B2. Model this function in the system and assign the following descriptions: Technical name: 3��B3)B�� Description: 7%:��B3��B$/��B3)��B5(9$/8$7(��Which two fields are to be selected as “XVHG�LQ�FRQGLWLRQV” ? _____________________________________________________________ _____________________________________________________________

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-42

How many conditions are to be stored for this planning function and which conditions are these? _____________________________________________________________ _____________________________________________________________ Now enter the two conditions in this function according to the information above. �The revaluation percentages have not been determined yet. You need to do so for each condition RQ�WKH�&RUUHVSRQGLQJ�3DUDPHWHU�5HFRUG�WDE�SDJH in the “0DLQWHQDQFH�RI�5HYDOXDWLRQ�3DUDPHWHUV” .

Which setting is to be chosen for each condition and why? _____________________________________________________________ _____________________________________________________________ For the UHYDOXDWLRQ�IDFWRU� a YDULDEOH for the “ Percentage” field has to be configured for each condition. Enter the following descriptions for the two formula variables to be created: 7HFKQLFDO�QDPH��3��B9$5B5(9B&2*6B7:$7�'HVFULSWLRQ�� 3��B9$5B5(9B&2*6B7:$7 7HFKQLFDO�QDPH��3��B9$5B5(9B&2*6B-8&�'HVFULSWLRQ�� 3��B9$5B5(9B&2*6B-8& Assign a variable to each condition. Both variables should have the following settings:

13. Processing by 14. Manual Entry / Default Value

15. Variable input is 16. Mandatory

17. Ready for input 18. Select

19. Default Values 20. ��(%) (for TWAT) or��(%) (for JUC)

After defining a variable for each condition, these are to be select for the “ Percentage” field for each condition. 6DYH�the function.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-43

1-5-4 Create another sequence for aggregation level 3��B$/B��to test the planning function� Enter the following descriptions: Technical name:��3��B6B�� Description: 7%:��B3��B$/��B6�� and, within this sequence, assign the filter 3��B)B��Dnd the revaluation function to each other. 6DYH the sequence. Run a WUDFH�for default percentage records ��RU��and default fiscal year ��. Then take a look at the data development for EORFN��DQG�EORFN��because block 1 and 3 display the initial data in version B1! If the function does not find any data, you should trigger sequence 3��B6B��again and then 3��B6B��

You should get the following display for EORFN��:

'R�QRW�VDYH�the planning data.

1-5-5 In order to be able to reset the planning process with regard to version B2, you need to create a GHOHWLRQ�IXQFWLRQ for aggregation level 3��B$/B��which “ deletes” the plan data for�DOO�NH\�ILJXUHV�of version�%�� Create such a function and enter the following descriptions: Technical name: 3��B3)B�� Description: 7%:��B3��B$/��B3)��B'HOHWH Which field is to be selected as “XVHG�LQ�FRQGLWLRQV”? _____________________________________________________________ The deletion function is to delete across DOO�NH\�ILJXUHV but only data of version %�. Select these settings and VDYH the created function.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-44

How would the data be updated in the InfoProvider, if you were to execute the deletion function and save? _____________________________________________________________

1-5-6 Create another sequence for aggregation level 3��B$/B��to test the planning function� Enter the following descriptions: Technical name:��3��B6B�� Description: 7%:��B3��B$/��B6�� and, within this sequence, assign the filter 3��B)B��Dnd the deletion function to each other. 6DYH the sequence. Run a WUDFH�for default fiscal year ��and look at the data development for�EORFN��RU�EORFN��, which refer to version B2. You should get the following display for block 2:

'R�QRW�VDYH�the planning data.

1-5-7 At the end of the planning process, the sales manager will have to decide, whether the planning data of version B1 or B2 describes the “ real development” of the situation in the corresponding fiscal year and copy the data of this version (b1 or B2) to version B, which also contains the sales manager’s quantity planning. That is why you have to create another FRS\�IXQFWLRQ that copies a VHQGHU�YHUVLRQ�selected by the planner�WR�UHFHLYHU�YHUVLRQ�%� This applies to DOO�NH\�ILJXUHV� A YDULDEOH�needs to be created for the VHQGHU�YHUVLRQ� Model the function and variable according to the information above. Enter the following description for the planning function aggregation level 3��B$/B��:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-45

Technical name: 3��B3)B�� Description: 7%:��B3��B$/��B3)��B&23< Which field is to be selected as “ Changed“ ?? _____________________________________________________________ You need to enter the following descriptions to define the YDULDEOHV: Technical name: 3��B9$5B6HQGHUYHUVLRQBFRS\ Description: 3��B9$5B6HQGHUYHUVLRQBFRS\ The variable should have the following settings:

21. Processing by 22. Manual Entry / Default Value

23. Variable Represents 24. Single value

25. Variable input is 26. Mandatory

27. Ready for input 28. Select

29. Default Values 30. B1

After defining the variable, it is to be selected as the sender version in the concrete processing rule. The receiver of the rule is version %. 6DYH�the planning function after you have configured it.

1-5-8 Create another sequence for aggregation level 3��B$/B��to test the planning function� Enter the following descriptions: Technical name:��3��B6B�� Description: 7%:��B3��B$/��B6�� and, within this sequence, assign the filter 3��B)B��Dnd the copy function 3��B3)B��to each other. 6DYH the sequence. Run a WUDFH�for default fiscal year ��and�default version %� of the variables and look at the data development for EORFN�� You should get the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-46

'R�QRW�VDYH�WKH�SODQ�GDWD�DQG�FORVH�WKH�3ODQQLQJ�0RGHOHU�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-47

�6ROXWLRQV�

8QLW�� 3ODQQLQJ�)XQFWLRQV�±�%DVLFV�/HVVRQ�� 6HOHFWHG�6WDQGDUG�3ODQQLQJ�)XQFWLRQV�

1-1 For quantity planning within aggregation level 6��B$/B��create a new ILOWHU�by copying filter 6��B)B�� Enter the following descriptions: Technical name:6��B)B�� Description:�� 7%:��B6��B$/��B)��To do so, search for the previously created filter 6��B)B�� on the “)LOWHU” tab, select it and copy it using the “&RS\” button. Enter the technical name and the description and confirm using “7UDQVIHU” . �Select “.H\” �in the Display area.

1-1-1 Following that, you need to configure the copy function for copying from version A to B. Which of the two versions must�be included in the filter? Version % Select this YHUVLRQ in your filter and�VDYH it. Click the “ ,QSXW�KHOS” icon to call up the input help for characteristic 0VERSION, remove the value “$” and enter “%” .

1-1-2 Now configure the FRS\�IXQFWLRQ to copy the data of version $ to version % and only for the VDOHV�TXDQWLW\�key figure. Create the function for the previously created aggregation level 6��B$/B��. Enter the following descriptions: Technical name: 6��B3)B�� Description: 7%:��B6��B$/��B3)��BFRS\��On the “ PODQQLQJ�)XQFWLRQV” tab, select aggregation level 6��B$/B��, click the “ Create” button and choose function type “ Copy” . Enter the technical name and the description and confirm your entries using “7UDQVIHU” . Which field is to be selected as “ ,V�&KDQJHG” ? 9HUVLRQ��9(56,21��No field is to be selected in the “XVHG�LQ�FRQGLWLRQ” area.��Limit the execution of the function to the VDOHV�TXDQWLW\�key figure and enter the

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-48

concrete processing rule in the input template.��Press the “)RU�3DUDPHWHUV” button and only choose the 6DOHV�TXDQWLW\ key figure (0COPASLQTY). To do so, press the “&UHDWH�5RZ” button. “&KDQJH�IURP” takes you to the input help for the value of the source version. Set the display to “.H\” and choose “$” . “&KDQJH�7R” takes you to the input help for the value of the destination version. Set the display to “.H\” as well and choose “%” .��6DYH the function using the “6DYH” �button�

1-1-3 Now create a sequence to test whether the function can be executed for the default fiscal year. Enter the following descriptions for the sequence: Technical name: 6��B6B�� Description: 7%:��B6��B$/��B6�� Use the “&UHDWH” button in the “3ODQQLQJ�6HTXHQFHV” �area to create a new planning sequence. �Press the “$GG�sWHS�IRU�SODQQLQJ�IXQFWLRQV” button and connect filter 6��B)B��with function 6��B3)B�� Then WHVW�the sequence using “6DYH” .

1-1-4 Now execute this sequence in the WUDFH. Do so for the default fiscal year ��of the variables from the filter. To do so, you select the planning function and press the “([HFXWLRQ�ZLWK�WUDFH” button. Please take a look at the data for EORFN�� for example. It should be displayed as follows:

Then set the variable to ��and execute the function again. To change the value of the variable “*URXS��B9$5B)<B��B30” please use the input help in the “9DULDEOH�,QSXW” panel. Enter �� and confirm using “2.” � Then press the “([HFXWLRQ�ZLWK�WUDFH” button again. Now VDYH your SODQQLQJ�GDWD for the first time to generate the initial data in versions B for a later task.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-49

To do so, press the “ Save Plan Data” button in the “ Execution” panel. Then reset the YDULDEOH�to ��and VDYH the VHTXHQFH again.

To reset the variable “*URXS��B9$5B)<B��B30” to the default value, use the value help in the “9DULDEOH�(QWU\” panel.

Enter �� and confirm using “2.” � Your InfoProvider should now contain the following data records. Check this for yourself.

1-2 The planning data of quantity planning in version B of the CFOs represents the default values for the VDOHV�PDQDJHUV� Since the planning granularity of the sales managers is the controlling area, company code and material group, you need to create an aggregation level first. You then need to create another filter and a distribution function that breaks down the default values to material groups.

1-2-1 First, create a new aggregation level by copying aggregation level 6��B$/B�� and include the characteristic that describes the detailed planning level of the sales managers in the level. Which characteristic is this? The additional characteristic to be used is called “0DWHULDO�*URXS” �(0MATL_GROUP).�Select this in the “8VHG” �column� Enter the following description for the new aggregation level: Technical name: 6��B$/B�� Description: 7%:��B6��B$/�� and DFWLYDWH the aggregation level after including the characteristic.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-50

1-2-2 Now define a filter for this aggregation level, which is to be used for the distribution function. Technical name:�� 6��B)B�� Description: 7%:��B6��B$/��B)�� . First of all, click the “)LOWHUV” tab. Choose the “ Technical name of aJJUHJDWLRQ�OHYHO” �option in the search area and, if necessary, enter “6��B$/B��” �as well. Then press the “&UHDWH” button to open the dialog for creating filters. Enter technical name “6��B)B��” and description “7%:��B6��B$/��B)��” and confirm using “7UDQVIHU” . Now enter >.H\@�for “'LVSOD\” � Include all characteristics of the aggregation level and, for version %, select unit of measure 3&��and currency 86'� The company codes are ��and��the controlling area is ��.��is to be selected as the fiscal year variant and variable *URXS��B9$5B)<B��B30 is to be selected for the fiscal year. How does modeling of the selection for the material group characteristic have to take place, if this filter is later used for the distribution to material group water and juice? Material group: ��>�@��:DWHU�>:$7@��-XLFH�>-8&@ Select these characteristic values into the filter and VDYH�it.

1-2-3 Now create a GLVWULEXWLRQ�IXQFWLRQ�DFFRUGLQJ�WR�WKH�NH\V created in the DJJUHJDWLRQ�OHYHO�in your task �� to perform the distribution from controlling area, company code to the material group.�The distribution is to be performed only for the key figure VDOHV�TXDQWLW\� Model the distribution function according to this information and use the following descriptions: Technical name: 6��B3)B�� Description: 7%:��B6��B$/��B3)��B',675,%B.(< In the “3ODQQLQJ�)XQFWLRQV” tab, search for the aggregation level 6��B$/B��, click the “&UHDWH” button and choose the function type ”'LVWULEXWLRQ�E\�NH\V” . Enter the technical name and the description and confirm your entry using “7UDQVIHU” . Which field is to be selected as “&KDQJHG” ?��0DWHULDO�JURXS��0$7/B*5283��Now press the “)RU�3DUDPHWHUV” button and select the “XVHG�LQ�FRQGLWLRQ” �flag for the “6DOHV�TXDQWLW\” key figure. In the configuration of the corresponding parameter record choose the distribution variant “'LVWULEXWH�“QRW�DVVLJQHG��” �RQO\” ��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-51

Select the parameter row and press the “&UHDWH�E\�YDOXH” �pushbutton to define a second row for the recipients of the distribution rule. Select one material group into each of the two distribution rows. Leave the entries for the weighting factor blank. Then�VDYH�the function.

1-2-4 The keys for the distribution to the two material groups Water (WAT) and Juice (JUC) are not to be defined as predefined values but as variables so that the sales manager can set the weighting factors in a decentralized way. For this purpose, create a variable for each distribution factor, for each rule row within the distribution function role, using the following description: Variable for weighting factor water: Variable name:� 6��B9$5B'LVWULEB.H\:$7�Description: 6��B9$5B'LVWULEB.H\:$7 Variable for weighting factor juice: Variable name:� 6��B9$5B'LVWULEB.H\-8&�Description: 6��B9$5B'LVWULEB.H\-8& You need to make the following system settings for both variables: Processing By: 0DQXDO�HQWU\�GHIDXOW�YDOXHV Variable Input Is: 0DQGDWRU\ Ready for Input: 6HOHFW� Default values: ��IRU�ZDWHU�RU�IRU�MXLFH� After the variables have been created, they are to be included in their respective rule row instead of the weighting factor. 6DYH your planning function again.

1-2-5 To be able to test again whether your planning function works correctly, you should create another planning sequence and merge the function and the filter 6��B)B�� of aggregation level 6��B$/B�� Enter the following descriptions for the sequence: Technical name: 6��B6B�� Description: 7%:��B6��B$/��B6�� Use the “&UHDWH” button in the “3ODQQLQJ�6HTXHQFHV” �area to create a new planning sequence. �Add the “6WHS�IRU�3ODQQLQJ�)XQFWLRQV” and connect filter 6��B)B��with function 6��B3)B��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-52

Then WHVW�the sequence using “6DYH” . 7UDFH the sequence for the variable default setting (��) and then look at the data development by means of EORFN��.

You should get the following display:

'R�QRW�VDYH�the plan data. Stay in Planning Modeler.

1-3 Now that the data is available at the correct granularity of controlling area, company, material group for the sales managers, the data is to be reposted IURP�PDWHULDO�JURXS�:$7��ZDWHU��WR�7:$7��IRU�WDEOH�ZDWHU��because the company has been restructured. Modeling is to take place within aggregation level 6��B$/B��.

1-3-1 For this purpose, create another filter in this aggregation level by copying filter 6��B)B�� and enter the following description: Technical name�� 6��B)B�� Description: 7%:��B6��B$/��B)�� . Compared to filter 6��B)B��how does this new filter have to be configured with regard to the material group? Material group: :DWHU��:$7��7DEOH�ZDWHU��7:$7� Make the adjustment and then save the filter.

1-3-2 Now, create a UHSRVW�IXQFWLRQ that performs the reposting for the key figure sales quantity. Enter the following descriptions for the function: Technical name: 6��B3)B�� Description: 7%:��B6��B$/��B3)��BUHSRVW Which field is to be selected as “&KDQJHG” ? 0DWHULDO�JURXS��0$7/B*5283� Once again, limit the function to the key figure VDOHV�TXDQWLW\�and configure the concrete reposting rule��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-53

Press the “ For Parameters” button and only choose the key figure VDOHV�TXDQWLW\ (0COPASLQTY). To do so, press the “&UHDWH�5RZ” button. Use the “)URP�&KDQJH” button to call up the selection dialog for the source value of the material group. Select “:DWHU�>:$7@” from the list. Use the “7R�&KDQJH” button to call up the dialog for the destination value of the material group. Here, choose “7DEOH�ZDWHU�>7:$7@” . 6DYH�the IXQFWLRQ.

1-3-3 Now create another planning sequence that includes filter 6��B)B��and the UHSRVWLQJ�IXQFWLRQ in order to test whether the function works correctly. Enter the following descriptions: Technical name: 6��B6B�� Description: 7%:��B6��B$/��B6�� Use the “&UHDWH” button in the “3ODQQLQJ�6HTXHQFHV” �area to create a new planning sequence. �Add the “6WHS�IRU�3ODQQLQJ�)XQFWLRQV” and connect filter 6��B)B��with function 6��B3)B�� Then VDYH�the sequence using “6DYH” . 7UDFH the sequence for the default setting of your variable for fiscal year �� and then look at the data development by means of %ORFN��. You should get the following display:

'R�QRW�VDYH�the plan data. This concludes the quantity planning of the sales managers.

1-4 Price and production cost planning, which are also done by the sales managers, take place in a separate real-time InfoProvider. In contrast to quantity planning, the granularity for prices and production costs is only on the material group!

1-4-1 For this purpose, select the real-time InfoProvider 7%:��3�� (where ## = monitor number) that is intended for price and production cost planning in the ,QIR3URYLGHU�area.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-54

1-4-2 For this InfoProvider, create an aJJUHJDWLRQ�OHYHO with the following description. Technical name: 3��B$/B�� Description: 7%:��B3��B$/�� Include all InfoObjects in the aggregation level, except for the characteristic customer group and posting period, and then DFWLYDWH�it.

1-4-3 Now create a ILOWHU for price and production cost planning and enter the following descriptions: Technical name: 3��B)B�� Description: 7%:��B3��B$/��B)�� Select DOO�ILHOGV�RI�WKH�DJJUHJDWLRQ�OHYHO and choose the following FKDUDFWHULVWLF�YDOXHV for the individual characteristics:

&KDUDFWHULVWLF�LQ�WKH�ILOWHU &KDUDFWHULVWLF�YDOXH�WR�EH�VHOHFWHG

Material or goods group 7:$7��-8&

Currency

86'

Fiscal year 9DULDEOH��*URXS��B9$5B)<B��B30

Version %��%��%

Fiscal year Variant .�

Please note that the two versions, B1 and B2, correspond to optimistic and pessimistic price and production cost planning. That is, sales planners can plan in two different versions and then have to decide on a planning version later, which they then copy into version B. Version B then not only contains the quantity planning data but also the price and production planning data. 6DYH�the settings in the filter.

1-4-4 In order to be able to look at the input template again as a test layout or buffer display and to enter some test data manually, you should define another sequence and assign filter 3��B)B��of aggregation level 3��B$/B��as “6WHS�IRU�WKH�LQSXW�WHPSODWH” � Enter the following descriptions for the sequence: Technical name: 6��B6B�� Description: 7%:��B3��B$/��B6�� 6DYH�the sequence. Now execute the “ ,QSXW�WHPSODWH” �for fiscal year ��and look at the data for %ORFN��.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-55

From the InfoProvider perspective, the following data in version B1 is already planned for you:

1-5 In the following, the typical planning process of the sales managers is to be started for price and production cost planning. First, the planner is to plan manually in version B1, then copy the data into version B1 via a copy function. Following that, the planner is to use a revaluation function for the data of version B2, whereby the sales manager is to set the revaluation factor as a variable. Following that, the data of version B2 is to be revised manually and finally, the planner is to be able to decide whether version B1 or B2 is to be the binding or consolidated version for him. Finally, the user can decide decentralized which of the two versions is to be copied to version B by means of a copy function with a variable on the sender version.

1-5-1 First, create a FRS\�IXQFWLRQ�for aggregation level 3��B$/B��which copies DOO key figures from version %��to %�� In the “3ODQQLQJ�)XQFWLRQV” tab, search for the aggregation level 3��B$/B��, click the “&UHDWH” button and choose the function type “&RS\” . Enter the technical name and the description and confirm your entry using “7UDQVIHU” . Technical name: 6��B3)B�� Description: 7%:��B3��B$/��B3)��B&23< Which field is to be selected as “ ,V�&KDQJHG” �in the &KDUDFWHULVWLF�8VDJH�area? 9HUVLRQ�>�9(56,21@ In the 3DUDPHWHU area, select the field “6HOHFW�DOO�NH\�ILJXUHV” and then choose the following processing rule: &KDQJH�)URP: Version = %�; &KDQJH�7R�: Version = %�.�Then save the IXQFWLRQ.

1-5-2 Now create another planning sequence that includes filter 6��B)B��of aggregation level�3��B$/B��and the FRS\�IXQFWLRQ to test whether the function works correctly. Enter the following descriptions: Technical name: 6��B6B�� Description: 7%:��B6��B$/��B6�� Use the “&UHDWH” button in the “3ODQQLQJ�6HTXHQFHV” area to create a new planning sequence. �Add the “6WHS�IRU�3ODQQLQJ�)XQFWLRQV” and connect filter 6��B)B��with function 6��B3)B��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-56

Then VDYH�the sequence using “6DYH” . 7UDFH this for default fiscal year �� and then look at the data development for %ORFN��. You should get the following display:

'R�QRW�VDYH�the plan data.

1-5-3 The sales manager is now supposed to be able to UHYDOXDWH�the data that was just copied; this is to be possible only in version B2.� The function is now to be executed for the fiscal year again according to the set YDULDEOH and is now to be modeled so that the revaluation percentages are set using variables. In doing so, you need to consider that the UHYDOXDWLRQ�SHUFHQWDJH�LV�LGHQWLFDO�IRU�ERWK�NH\�ILJXUHV�SULFH�DQG�SURGXFWLRQ�FRVWV and is RQO\�DSSOLHG�WR�VSHFLILF�PDWHULDO�JURXSV, that is material groups 7:$7 and -8&. Revaluation only takes place within version B2. Model this function in the system and assign the following descriptions: Technical name: 3��B3)B�� Description: 7%:��B3��B$/��B3)��B5(9$/8$7( In the “3ODQQLQJ�)XQFWLRQV” tab, search for the aggregation level 3��B$/B��, click the “&UHDWH” button and choose the function type ”5HYDOXDWLRQ” . Enter the technical name and the description and confirm your entries using “7UDQVIHU” .��Which two fields are to be selected as “XVHG�LQ�FRQGLWLRQV” ? 0DWHULDO�JURXS�>�0$7/B*5283@��9HUVLRQ�>�9(56,21@ How many conditions are to be stored for this planning function and which conditions are these? ��FRQGLWLRQV�� VW�FRQGLWLRQ: material group = “7:$7” , version = “%�” � < = �FRQGLWLRQ: Material group = “ JUC” , version = “ B2”

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-57

Now enter the two conditions in this function according to the information above. In the parameter area, use the “&UHDWH�URZ” button to create a second condition first. Then use the value help to configure the conditions as described above. �The revaluation percentages have not been determined yet. You need to do so for each condition RQ�WKH�&RUUHVSRQGLQJ�3DUDPHWHU�5HFRUG�WDE�SDJH in the “0DLQWHQDQFH RI�5HYDOXDWLRQ�3DUDPHWHUV” . Which setting is to be chosen for each condition and why? <RX�KDYH�WR�VHOHFW�“6DPH�3HUFHQWDJH�IRU�$OO�.H\�)LJXUHV” �IRU�ERWK�RI�WKH�FRQGLWLRQV��EHFDXVH�IRU�HDFK�FRQGLWLRQ��WKDW�LV��IRU�HDFK�PDWHULDO�JURXS��WKH�VDPH�UHYDOXDWLRQ�IDFWRUV�DSSO\�WR�DOO�NH\�ILJXUHV� For the UHYDOXDWLRQ�IDFWRU� a YDULDEOH for the “ Percentage” field has to be configured for each condition. Enter the following descriptions for the two formula variables to be created: 7HFKQLFDO�QDPH��3��B9$5B5(9B&2*6B7:$7�'HVFULSWLRQ�� 3��B9$5B5(9B&2*6B7:$7 7HFKQLFDO�QDPH��3��B9$5B5(9B&2*6B-8&�'HVFULSWLRQ�� 3��B9$5B5(9B&2*6B-8& Assign a variable to each condition. Both variables should have the following settings:

Processing by 0DQXDO�(QWU\��'HIDXOW�9DOXH Variable input is 0DQGDWRU\

Ready for input 6HOHFW Default Values ��(%) (for TWAT) or��(%) (for JUC)

After defining a variable for each condition, these are to be selected for the “ Percentage” field for each condition. 6DYH�the function.

1-5-4 Create another sequence for aggregation level 3��B$/B��to test the planning function� Enter the following descriptions: Technical name:��3��B6B�� Description: 7%:��B3��B$/��B6�� Add a “ Step for planning functions” and assign it filter 3��B)B��and revaluation

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-58

function 3��B3)B��. 6DYH the sequence. Execute a WUDFH�for default percentage records ��RU��and default fiscal year ��. Then take a look at the data development for EORFN��DQG�EORFN��because block 1 and 3 display the initial data in version B1! If the function does not find any data, you should trigger sequence 3��B6B��again and then 3��B6B�� You should get the following display for EORFN��:

=> wrong screenshot: the revaluation was called up twice. 'R�QRW�VDYH�the planning data.

1-5-5 To be able to reset the planning process with regard to version B2, you need to create a GHOHWLRQ�IXQFWLRQ for aggregation level 3��B$/B��which “ deletes” the plan data for�DOO�NH\�ILJXUHV�of version�%�� Create such a function and enter the following descriptions: Technical name: 3��B3)B�� Description: 7%:��B3��B$/��B3)��B'HOHWH In the “3ODQQLQJ�)XQFWLRQV” tab, search for the aggregation level 3��B$/B��, click the “&UHDWH” button and choose the function type “'HOHWH” . Enter the technical name and the description and confirm your entries using “7UDQVIHU” . Which field is to be selected as “ uVHG�LQ�FRQGLWLRQV” ? 9HUVLRQ�>�9(56,21@��In the &KDUDFWHULVWLF�8VDJH area in column XVHG�LQ�FRQGLWLRQV� choose the characteristic “9HUVLRQ” . The deletion function is to delete across DOO�NH\�ILJXUHV but only data of version %�. Select these settings and VDYH the created function. In the 3DUDPHWHU�area, under 6HOHFWHG�&RQGLWLRQ the version is to be set to “%�” by means of the value help. In the &RUUHVSRQGLQJ�3DUDPHWHU�5HFRUG “6HOHFW�$OO�.H\�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-59

)LJXUHV” �is selected. How would the data be updated in the InfoProvider, if you were to execute the deletion function and save? 'HOWD�FUHGLW�URZV�DUH�ZULWWHQ�VR�WKDW�WKH�DJJUHJDWHG�GDWD�UHFRUGV�DUH��

1-5-6 Create another sequence for aggregation level 3��B$/B��to test the planning function� Enter the following descriptions: Technical name: 3��B6B�� Description: 7%:��B3��B$/��B6�� Use the “&UHDWH” button in the “3ODQQLQJ�6HTXHQFHV” �area to create a new planning sequence. �Add the “6WHS�IRU�3ODQQLQJ�)XQFWLRQV” and connect filter 6��B)B��with function 6��B3)B�� Then VDYH�the sequence using “6DYH” . Run a WUDFH�for default fiscal year ��and look at the data development for�EORFN��RU�EORFN��, which refer to version %�. You should get the following display for block 2:

=> wrong screenshot: the revaluation was called up twice before the deletion. 'R�QRW�VDYH�the planning data.

1-5-7 At the end of the planning process, the sales manager has to decide whether the planning data of version B1 or B2 describes the “ real development” of the situation in the corresponding fiscal year. The sales manager then has to copy the data of this version (B1 or B2) to version B, which also contains the sales manager’s quantity planning. That is why you have to create another FRS\�IXQFWLRQ that copies a VHQGHU�YHUVLRQ�selected by the planner�WR�UHFHLYHU�YHUVLRQ�%� This applies to DOO�NH\�ILJXUHV�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-60

A YDULDEOH needs to be created for the VHQGHU�YHUVLRQ� Model the function and variable according to the information above. Enter the following description for the planning function for aggregation level 3��B$/B��: Technical name: 3��B3)B�� Description: 7%:��B3��B$/��B3)��B&23< ��On the “ PODQQLQJ�)XQFWLRQV” tab, select aggregation level 6��B$/B��, click the “&UHDWH” button and choose function type “&RS\” . Enter the technical name and the description and confirm your entries using “7UDQVIHU” . Which field is to be selected as “&KDQJHG” ? 9HUVLRQ�>�9(56,21@��In the &KDUDFWHULVWLF�8VDJH area in column ,V�&KDQJHG� choose the characteristic “9HUVLRQ” . Leave the XVHG�LQ�FRQGLWLRQV column unchanged. You need to enter the following descriptions to define the YDULDEOHV: Technical name: 3��B9$5B6HQGHUYHUVLRQBFRS\ Description: 3��B9$5B6HQGHUYHUVLRQBFRS\ The variable should have the following settings:

Processing by 0DQXDO�(QWU\��'HIDXOW�9DOXH Variable Represents 6LQJOH�YDOXH Variable input is 0DQGDWRU\

Ready for input 6HOHFW Default Values %�

After defining the variable, it is to be selected as the sender version in the concrete processing rule. The receiver of the rule is version %. Select the “6HOHFW�$OO�.H\�)LJXUHV” �checkbox in the 3DUDPHWHU area. Under )URP�YDOXHV�DQG�WR�YDOXHV�IRU�FRS\LQJ�� you create a new processing role using the “&UHDWH�5RZ” �button� The value of the target version (“7R�&KDQJH” � is filled with “%” . Create the above variable for the source value of the version. To do so, set the 9LHZ in the input help to “9DULDEOHV” and use the “&UHDWH” button of the input help to create a variable with the above settings and assign it using “$GG” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-61

6DYH�the planning function after you have configured it.

1-5-8 Create another sequence for aggregation level 3��B$/B��to test the planning function� Enter the following descriptions: Technical name:��3��B6B�� Description: 7%:��B3��B$/��B6�� and, within this sequence, assign the filter 3��B)B��Dnd the copy function 3��B3)B��to each other. To do so, use the “&UHDWH” button to create a new planning sequence in the “3ODQQLQJ�6HTXHQFHV” area. Add the “6WHS�IRU�3ODQQLQJ�)XQFWLRQV” and connect filter 6��B)B��with function 6��B3)B��6DYH the sequence. Run a WUDFH�for default fiscal year ��and�default version %� of the variables and look at the data development for EORFN��

You should get the following display�

'R�QRW�VDYH� the plan data and close 3ODQQLQJ�0RGHOHU�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 4-62

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-1

SAP AG 2006

&RQWHQW�� %DVLF�3ODQQLQJ�6HWWLQJV�LQ�4XHU\�'HVLJQHU� 8QLTXHQHVV�LQ�D�5HDG\�IRU�,QSXW�&HOO� )LOWHUV�LQ�WKH�3ODQ�4XHU\�DQG�3ODQQLQJ�0RGHOHU� 7KH 4XHU\V 'ULOOGRZQ 3URSHUWLHV� 5HDG %HKDYLRU RI�4XHULHV

&UHDWLQJ D�3ODQ�4XHU\

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-2

SAP AG 2006

&UHDWLQJ�D�3ODQ�4XHU\��/HDUQLQJ�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�EDVLF�SODQQLQJ�VHWWLQJV�LQ�WKH�TXHU\�

GHVLJQHU� 8QGHUVWDQG�KRZ�WR�VHW�XS�XQLTXHQHVV�LQ�DQ�LQSXW�

UHDG�TXHU\� 5HFRJQL]H�ZKDW�\RX�QHHG�WR�SD\�DWWHQWLRQ�WR�ZKHQ�

GHILQLQJ�D�ILOWHU� 8QGHUVWDQG�KRZ�WKH�TXHU\V�GULOOGRZQ�EHKDYLRU�LV�

GHVLJQHG� 8QGHUVWDQG�WKH�UHDG�EHKDYLRU�LQ�TXHULHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-3

SAP AG 2006

&UHDWLQJ�D�3ODQ�4XHU\��&RXUVH�2YHUYLHZ�'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-4

SAP AG 2006

&UHDWLQJ�D�3ODQ�4XHU\��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�ILQG�RXW�DERXW�FUHDWLQJ�D�SODQ�TXHU\�

� <RX�ZDQW�WR�IRFXV�RQ�H[DPLQLQJ�WKH�4XHU\�'HVLJQHU�DQG�WKH�TXHVWLRQ�RI�KRZ�\RX�FDQ�DFWXDOO\�FUHDWH�DQ�LQSXW�UHDG\�TXHU\�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-5

SAP AG 2006

%DVLF�3ODQQLQJ�6HWWLQJV�LQ�WKH�4XHU\�'HVLJQHU��8QLW�2YHUYLHZ�'LDJUDP

8QLW�2YHUYLHZ

� /HVVRQ��8QLTXHQHVV�LQ�DQ ,QSXW�5HDG\�&HOO

8QLW�2YHUYLHZ� /HVVRQ��%DVLF�3ODQQLQJ�6HWWLQJV�LQ�WKH�4XHU\�'HVLJQHU

� /HVVRQ��)LOWHUV�LQ�WKH�3ODQ�4XHU\�DQG�3ODQQLQJ�0RGHOHU�� /HVVRQ��7KH�4XHU\V�'ULOOGRZQ�3URSHUWLHV� /HVVRQ��5HDG�%HKDYLRU�RI�,QSXW�5HDG\�4XHULHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-6

SAP AG 2006

%DVLF�3ODQQLQJ�6HWWLQJV�LQ�WKH�4XHU\�'HVLJQHU��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�ZKDW�VHWWLQJV�\RX�QHHG�WR�JHQHUDWH�D�

TXHU\�ZLWK�ZULWH�DFFHVV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-7

SAP AG 2006

%DVLF�3ODQQLQJ�6HWWLQJV�LQ�WKH�4XHU\�'HVLJQHU��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�EDVLF�4XHU\�'HVLJQHU�VHWWLQJV�IRU�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-8

SAP AG 2006

4XHU\�'HVLJQHU�)XQFWLRQV�IRU�WKH�3ODQ�4XHU\4XHU\�IXQFWLRQV�IRU�SODQQLQJ��•��

• � � �� !��"$#%�$�• & �� "'� � ()��*�� +-,�� ./"�� -��,0�'��#1"�� 2�

• 3 � �4(��5� ��(��6*7�$+8,�� .9"��)� �• : � � ()��0�;��<$��5� ��='� �2�• > (��5"$�2(5"�� • ?�@ � ��A2(�� 9�4�• & "��0�� +B��%"�� (C�;��,/#D�4� ��"��)��4�/�4<�� /�

• E � ��)(9#��4�4�$�$.�� • & �9��9� (�� /� �• F ��A'�� 2�• & "��0�� +8(��4�� 2(�� 9�;�4(!��"'�4(�� #D�

�

G

The new %([�4XHU\�'HVLJQHU is used to set up the LQSXW�UHDG\�TXHULHV for manual planning. This means that the query’s properties and settings (as shown above) are also available for planning.

G Note that any number of characteristics may be included in the )UHH�FKDUDFWHULVWLFV area and a maximum of only 50 “Number of structures” characteristics can be selected in the 5RZV�DQG�FROXPQV area.

G So if the query contains no structure, there can be a total of 50 characteristics in the rows and columns.

G If you use a structure, there is a total of 49 characteristics allowed in the rows and columns and if you use two structures, a total of 48 is allowed.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-9

SAP AG 2006

,QSXW�5HDG\�4XHULHV

,QSXW�UHDG\�FHOO

�

G You can use LQSXW�UHDG\�TXHULHV to create applications for manual planning. These applications range from simple data entry to complex planning applications.

G You define an input-ready query in the %([�4XHU\�'HVLJQHU.

G Then, in the :HE�$SSOLFDWLRQ�'HVLJQHU or the %([�$QDO\]HU, you can combine the queries with other queries and planning functions to create complex planning applications, as required.�

G You can use the following ,QIR3URYLGHUV to define an input-ready query:

y Aggregation levels

y MultiProviders, containing at least one simple aggregation level G

As a prerequisite for manual planning, the real-time InfoProvider that you are using for planning must be set to “planning enabled”.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-10

SAP AG 2006

6HWWLQJV�5HOHYDQW�IRU�3ODQQLQJ�LQ�WKH�%([ 4XHU\�'HVLJQHU��

5HIHUHQFH�GDWD

0DQXDO�DQG�DXWRPDWLF�SODQQLQJ�DOORZHG

3URWHFWLRQ�DJDLQVW�PDQXDO�SODQQLQJ

�

G If you have defined a query on the InfoProviders mentioned before, you can find the 3ODQQLQJ tab page under the �3URSHUWLHV�of structure elements (so, for example, in key figures or restricted key figures).

G You can use the options offered there to specify which structure elements are ready for input during an input-ready query’s runtime and which are not.

G For structure elements that you do QRW want to be ready for input, you can also specify whether these components are treated as reference data or if they should be protected against manual entries.

G If they are to be UHIHUHQFH�GDWD, the structure elements are not protected by a data lock for exclusive access from one user because this data is used as a reference by many users. This is the standard default setting.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-11

SAP AG 2006

6HWWLQJV�5HOHYDQW�IRU�3ODQQLQJ�LQ�WKH�%([ 4XHU\�'HVLJQHU��

�

G In addition, you can specify whether an input-ready query is started in FKDQJH�PRGH or in GLVSOD\�PRGH. You can find this property in the 4XHU\�SURSHUWLHV�on the 3ODQQLQJ tab page.

G As soon as an element is set to “Planning” (as explained on the previous slide), the “Start query in change mode” flag is set; you can then deselect it again.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-12

SAP AG 2006

%DVLF�3ODQQLQJ�6HWWLQJV�LQ�WKH�4XHU\�'HVLJQHU��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�ZKDW�VHWWLQJV�\RX�QHHG�WR�JHQHUDWH�D�

TXHU\�ZLWK�ZULWH�DFFHVV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-13

SAP AG 2006

8QLTXHQHVV�LQ�DQ ,QSXW�5HDG\�&HOO� 8QLW�2YHUYLHZ�'LDJUDP

8QLW�2YHUYLHZ




�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-14

SAP AG 2006

8QLTXHQHVV�LQ�DQ ,QSXW�5HDG\�&HOO� /HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�WR�VHW�XS�DQ�LQSXW�UHDG\�TXHU\�DQG�

KRZ�WR�FUHDWH�XQLTXHQHVV�LQ�WKH�TXHU\V�LQSXW�UHDG\�FHOOV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-15

SAP AG 2006

8QLTXHQHVV�LQ�DQ ,QSXW�5HDG\ &HOO��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�\RX�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�FUHDWLQJ�DQ�LQSXW�UHDG\�TXHU\�DQG�ZLWK�WKH�XQLTXHQHVV�RI�FHOOV�LQ�WKLV�TXHU\�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-16

SAP AG 2006

,QSXW�5HDG\ 6WDWXV�LQ�D�4XHU\��

��*HQHUDO�UHTXLUHPHQWV�IRU�LQSXW�UHDG\�FHOOV�LQ�D�SODQ�TXHU\

�� 5HDO�WLPH�,QIR3URYLGHU IRUPV�WKH�EDVLV�RI�SODQQLQJ�� 7KH�³FDQ�EH�SODQQHG´�ORDG�EHKDYLRU�LV�VHW�IRU�WKH�UHDO�WLPH�,QIR3URYLGHU�� 7KH�SODQ�TXHU\�LV�EDVHG�GLUHFWO\�RU�LQGLUHFWO\�RQ�DJJUHJDWLRQ�OHYHOV�� 7KH�LQSXW�UHDG\�FHOO�PXVW�EH�ILOOHG�IURP�WKH�DJJUHJDWLRQ�OHYHO�� ³6WDUW�TXHU\�LQ�FKDQJH�PRGH´�PXVW�EH�VHOHFWHG�LQ�WKH�SODQ�TXHU\�� &HOOV�LQ�WKH�SODQ�TXHU\�PXVW�EH�VHW�WR�WKH�³SODQQLQJ´�SURSHUW\�� 7KHUH�PXVW�EH�QR�ORFNV�� 7KHUH�PXVW�EH�QR�GDWD�VOLFHV�VHW�� 7KH�DLP�RI�SODQQLQJ�PXVW�QRW�EH�D�FRPELQDWLRQ�QRW�DOORZHG�E\�WKH

FKDUDFWHULVWLF�UHODWLRQVKLSV��

�

G This and the following slides present you with a checklist that you can use to check for possible reasons if a plan query is not ready for input.

G The criteria in the diagram above are not fixed criteria for the query.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-17

SAP AG 2006

,QSXW�5HDG\�6WDWXV LQ�D�4XHU\��

��5HTXLUHPHQWV�IRU�WKH�LQSXW�UHDG\�VWDWXV RI�D�FHOO�LQ�WKH�SODQ�TXHU\

(DFK�FKDUDFWHULVWLF�LQ�WKH�DJJUHJDWLRQ�OHYHO�PXVW�KDYH�H[DFWO\�RQH�VLQJOH�YDOXH�IRU�WKH�LQSXW�UHDG\�FHOO��

�

G A simple method for obtaining an input-ready query is to first include all the characteristics from the underlying aggregation level in the drilldown (rows or columns). This action immediately supplies you with the input-ready cells. You could position all the characteristics in the rows and all the key figures in the data columns.

G If the query is then ready for input, you can remove single characteristics one by one from the drilldown and include them in the filter, or use structures or restricted key figures in the data columns instead of key figures.

G If the query is not ready for input after this, then you should use the checklist of the general prerequisite criteria for an input-ready query (as mentioned before) to find the error.

G Essentially, your aim is to VHW�WKH�SODQ�TXHU\�WR�WKH�ILQHVW�JUDQXODULW\�RI�DJJUHJDWLRQ�OHYHO�LQ�RUGHU�WR�UHFHLYH�DQ�LQSXW�UHDG\ FHOO�DQG�WKXV�EH�DEOH�WR�SODQ�LQ�D�TXHU\��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-18

SAP AG 2006

:KDW�&DXVHV�WKH�,QSXW�5HDG\ 6WDWXV"�� %DVLF�,GHD

$JJUHJDWLRQ�OHYHO��\HDU��PRQWK��YHUVLRQ��SURGXFW�JURXS��SURGXFW� DPRXQW�NH\�ILJXUH

�$PRXQW��

Beer

Wine

3URGXFW

Alcoholic

Alcoholic

$PRXQW��

3URGXFW*URXS

�9HUVLRQ��<HDU

)LOWHU


H�IKJ�L�M)N OPLQISRUTVIKWYX�N Z$[�M�I]\�M7J^L�M)[ÔKL0[7M_IN `YL�aKIcbed'\�f [7gU`^hji�M�I�i

H�\7klJ

m�n

o�n

�

G The above illustration shows that the finest granularity leads to the input-ready status in the plan query, because DOO the characteristics contained in the aggregation level are included in either the drilldown or the filter, and there is no multiple selection of the characteristics in the data columns or in the filter.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-19

SAP AG 2006

,Q�:KLFK�&DVHV�GRHV�WKH�,QSXW�5HDG\ 6WDWXV�1RW�2FFXU�"��


�$PRXQW��

Alcoholic

$PRXQW��

3URGXFW*URXS


)LOWHU

&HOO�QRW�UHDG\�IRU�LQSXW�EHFDXVH�SURGXFW�LV�UHPRYHG�IURP�GULOOGRZQ�

p5n

3URGXFW�"

�

G This and the following diagrams shows which query modelings can lead to the cells in the plan query not being ready for input.

G In the illustration above, the product characteristic contained in the aggregation level on which the query is based is not included in either the drilldown or the filter. This means that the data records are totaled using the products, the finest granularity is not reached, meaning that no input-ready cell results.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-20

SAP AG 2006

,Q�:KLFK�&DVHV�'RHV WKH�,QSXW�5HDG\�6WDWXV 1RW�2FFXU"��


)LOWHU


�$PRXQW��± ��

Beer

Wine

3URGXFW

Alcoholic

Alcoholic

$PRXQW��± ��

3URGXFW*URXS

&HOO�QRW�LQSXW�UHDG\�GXH�WR�PXOWLSOH�VHOHFWLRQ�LQ�WKH�GDWD�FROXPQ

q5n

�

G In the example above, you can see a cumulated display over three months in the data columns, where there is no single value per column, resulting in a summation. The cell that is used for the cumulation over the months is therefore not ready for input.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-21

SAP AG 2006

,Q�:KLFK�&DVHV�'RHV WKH�,QSXW�5HDG\�6WDWXV 1RW�2FFXU�"��

$JJUHJDWLRQ�OHYHO��\HDU��PRQWK��YHUVLRQ��SURGXFW�JURXS��SURGXFW��FXUUHQF\��DPRXQW�NH\�ILJXUH

)LOWHU

�9HUVLRQ(85��86'&XUUHQF\�

!

��<HDU

�$PRXQW��

Beer

Wine

3URGXFW

Alcoholic

Alcoholic

$PRXQW��

3URGXFW*URXS

&HOO�QRW�LQSXW�UHDG\�GXH�WR�PXOWLSOH�VHOHFWLRQ�LQ�WKH�ILOWHU

r!gc\[7`PLs�t�uv�v2wPx y^v2wevzr9g{\�[�`KL|�s�Hv^v2wKx y�v�wev

}�M�\ R$[ÔKL}$M_\ R4[�OKL~ MQ\4[��


�

G You should note that, if more than one currency is involved, the different currencies are selected as single values in separate data columns, to enable write access. If the selection in the filter is set to multiple selection, there is no input-ready status accordingly.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-22

SAP AG 2006

5HVXOW��$�SODQ�TXHU\�UHPDLQV�UHDG\�IRU�LQSXW�LI��HYHQ�GHVSLWH�DQ\�FKDQJHV�PDGH�DW�UXQWLPH��HDFK�FKDUDFWHULVWLF�LQ�WKH�DJJUHJDWLRQ�OHYHO�LVUHVWULFWHG�WR�D�VLQJOH�YDOXH�

,QSXW�5HDG\�3ODQ�4XHULHV�5HPDLQ�5HDG\�IRU�,QSXW�LI�«

• 7KH�ILOWHU�FKDQJHV�LQ�WKH�H[HFXWHG�TXHU\��• &KDUDFWHULVWLFV�DUH�PRYHG�IURP�WKH�GULOOGRZQ�WR�WKH�ILOWHU�• 7KH�VHTXHQFH�RI�FROXPQV�LV�UH�VRUWHG�• 5RZV�DQG�FROXPQV�DUH�VZDSSHG�

�

G The figure above shows that many of the changes made to settings in the plan query at runtime do not affect the planning’s granularity; in this way, the cells remain ready for input.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-23

SAP AG 2006

8QLTXHQHVV�LQ�DQ ,QSXW�5HDG\ &HOO��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�WR�VHW�XS�DQ�LQSXW�UHDG\�TXHU\�DQG�

KRZ�WR�FUHDWH�XQLTXHQHVV�LQ�WKH�TXHU\V�LQSXW�UHDG\�FHOOV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-24

SAP AG 2006

)LOWHUV�LQ�WKH�3ODQ�4XHU\�DQG�3ODQQLQJ�0RGHOHU��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�WKH�ILOWHU�LQ�WKH�SODQ�TXHU\�LV�

VWUXFWXUHG�DQG�ZK\�WKH�ILOWHUV�LQ�WKH�SODQ�TXHU\�DQG�SODQQLQJ�PRGHOHU�DUH�OLQNHG�WR�RQH�DQRWKHU

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-25

SAP AG 2006

)LOWHUV�LQ�WKH�3ODQ�4XHU\�DQG�3ODQQLQJ�0RGHOHU��8QLW�2YHUYLHZ�'LDJUDP

8QLW�2YHUYLHZ




�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-26

SAP AG 2006

)LOWHUV�LQ�WKH�3ODQ�4XHU\�DQG�3ODQQLQJ�0RGHOHU��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�ILQG�RXW�DERXW�WKH�FRQQHFWLRQV�EHWZHHQ�WKH�ILOWHU�LQ�WKH�SODQ�TXHU\�DQG�WKH�ILOWHU�LQ�WKH�SODQQLQJ�PRGHOHU�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-27

SAP AG 2006

$�4XHU\V�)LOWHU�&RPSRQHQWV

�j� �)��'� ��4�$�B�� 9�� )�� '� �!�_� �9�$��5� �2� ��D� ��D�4�;��4��$�$��B��$�B�4��D��-�2�-�$�-��0�$��0�� 4�5� ��0�4� �� 2�� /� �'��9�4�4�;��4�)��%��4�B�5�4�D�_�� '�S�� C��4�0�2�)��$��$�B�!�$��;��/�'� ��4��4��_��'�

�j� ��'� ��4��4�4�� '�^�$�� $�7�� /�

�9�4�;��$��0�� 4�� D� ��4�4�� 4�C�$�D��5��l�2��Q�4� �'��9� �B��4�$�$��$�D��2�� 6�$�'�� $��5� �� 9�4�;��$��0�� 4�� D�0�2�4�� 2�� /�4� ��0��$�8�5� �;�$�� 2�� !�;�� )�� D��4��

� �$��)�$�4�C�� $�� $�2�� 9�� 2�)�D�0��$��

�j� �$��5�_� �� /�� 9�4�� $�/��4��

¡$iK¢ N Z�i^L�N \4`¤£2f \ O�T\7X L�aKI]IK¥ÎSO�[KLQISR¦ [KI2M W

§2ë©«ªe¬V®P�¯ ©e°e± ²e³«©«± °«�´�©�²^µ °Vª«² ¶ ·�

�

G Please note when defining a filter that if you include all the characteristics in the rows or columns, too many data records would be locked. You should therefore restrict the data range that is selected for manual planning and planning functions.

G You restrict using a filter. You can define the filter either in the planning modeler or in the query itself. If you create the filter in the query, you can then save it and it will be available to the planning modeler as well.

G Your aim should always be to keep the characteristic restrictions as small as possible so that you keep the locks as small as possible.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-28

SAP AG 2006

&KDUDFWHULVWLF�5HVWULFWLRQV�DQG�'HIDXOW�9DOXHV�IRU�WKH�)LOWHU

¸7¹ ®V�¯ ©�°V± ²e³«©5± °«´�e± �º�² �®» �¯ ©«°P± ²P³�©e± °e�´�«± �º�² �®

�

G The “'HIDXOW�YDOXHV” area contains the values that end users are supposed to see when they open the plan query as the initial selection of the data range; in other words, the “ FKDUDFWHULVWLF�UHVWULFWLRQV” . End users can change selections and set filter values from the data range for this characteristic at runtime.

¼ In the example above, multiple selection was specified in the data range (characteristic restrictions area) for the characteristics version, product line, fiscal year and division. However, when the query starts, only data records for version P00, product line C-PL-611, the 2010 fiscal year and the division C-DIV-61 are supposed to be displayed.

¼ It is possible to change the selection at runtime, as the figure for the characteristic fiscal year shows; however, it is only possible to to change in the data range specified, for the fiscal years 2010 and 2011.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-29

SAP AG 2006

,QSXW�+HOS�ZKHQ�6HOHFWLQJ�)LOWHU�9DOXHV�

�

¼ The setting shown above in the query’s enhanced properties refers to the LQSXW�KHOS, which you receive for an executed query if, for example, the filter that relates to the data range is to be restricted at runtime or if the characteristics positioned in the free characteristics are also to be restricted at runtime.

¼ “2QO\�SRVWHG�YDOXHV�IRU�QDYLJDWLRQ” means that when filter values are selected when the query is executed, the values are determined by the data that the query selects. Thus only the values for which data is selected in the current navigation state appear.

¼ In many cases, however, it may be useful to allow other values. For this reason, the settings “ Only values in InfoProvider” and “ Values in master data table” are also possible. However, selecting these may result in the message “ No data found” appearing after you select filter values.

¼ “2QO\�YDOXHV�LQ�,QIR3URYLGHU” means that the input help only displays selections that relate to characteristic attributes contained in the transaction data record.

¼ “9DOXHV�LQ�PDVWHU�GDWD�WDEOH” means that characteristic attributes from the data range are displayed whether or not transaction data records exist for them.

¼ You can also set the system so that the default setting is always used for input help in the characteristic's master record. You can control this using the “8VH�FKDUDFWHULVWLF�VHWWLQJ” setting.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-30

SAP AG 2006

&RQQHFWLRQ�%HWZHHQ�WKH�)LOWHU�DQG�3ODQQLQJ�0RGHOHU��

�

¼ As you saw before, you can save the filter in both the planning modeler and in the plan query and then use the filter in either of the two areas.

¼ The figure above shows that you can save both filter components together from the query, which makes it possible to use the filter more than once in the query. You can also use this filter in the planning modeler, as shown on the next slide.

¼ If you save the filter in the query, another query for the same aggregation level can also access this filter.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-31

SAP AG 2006

&RQQHFWLRQ�%HWZHHQ�WKH�)LOWHU�DQG�3ODQQLQJ�0RGHOHU��

bed!aî2M�i�OKLQI2MCN J�L�N O{M�I^J�L�M)N OPL�N \4`^JShbKu$I^XQi2[�f L�¢Si�f [Î^J�h

�

¼ By saving the filter in the query, you are saving the filter in the planning modeler as well. The above diagram shows the connections.

¼ In the following, we will compare the filter settings in the planning modeler and the effects on the query, or how the filter in the query influences the settings in the planning modeler.

¼ “&DQ�EH�&KDQJHG�DW�4XHU\�([HFXWLRQ” : fields such as the version that are deselected in the planning modeler's filter are only assigned to the area of the “ fixed” filter. There are no default values for these. In the executed query, this kind of field would either be located in the row/column with the possibility to restrict the data range selected in the “ fixed” filter, or (if the characteristic is not in the drilldown as well), the characteristic would be in the navigation block under “ Free characteristics” and you can carry out a selection at runtime.

¼ If you selected a field in the “ Can be Changed at Query Execution” area, then you selected a start value in the “ Default Values” area that the query uses to display the initial data. Regardless of whether the characteristic was stored in the drilldown in parallel or not in parallel, you can still change the selection within the data range via a runtime selection.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-32

SAP AG 2006

)LOWHUV�LQ�WKH�3ODQ�4XHU\�DQG�3ODQQLQJ�0RGHOHU��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�WKH�ILOWHU�LQ�WKH�SODQ�TXHU\�LV�

VWUXFWXUHG�DQG�ZK\�WKH�ILOWHUV�LQ�WKH�SODQ�TXHU\�DQG�SODQQLQJ�PRGHOHU�DUH�OLQNHG�WR�RQH�DQRWKHU��

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-33

SAP AG 2006

7KH�4XHU\V�'ULOOGRZQ�3URSHUWLHV��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�ZKDW�RSWLRQV�WKHUH�DUH�IRU�GHVLJQLQJ�WKH�

GULOOGRZQ�RI�FKDUDFWHULVWLFV�LQ�URZV�DQG�RU�FROXPQV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-34

SAP AG 2006


7KH�4XHU\V�'ULOOGRZQ�3URSHUWLHV��8QLW�2YHUYLHZ�'LDJUDP



�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-35

SAP AG 2006

7KH�4XHU\V�'ULOOGRZQ�3URSHUWLHV��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�ILQG�RXW�DERXW�WKH�GULOOGRZQ�SURSHUWLHV�RI�FKDUDFWHULVWLFV�LQ�WKH�TXHU\�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-36

SAP AG 2006

6HWWLQJ�WKH�'ULOOGRZQ�3URSHUWLHV�RI�5RZV�DQG�&ROXPQV��

'ULOOGRZQ�LV�ILOOHG�ZLWK�WUDQVDFWLRQ�GDWDLQ�WKH�VHOHFWLRQ�

Juice

Wine

3URGXFW

40

10

$PRXQW

Non-alc.

Alcoholic

3URGXFW*URXS

�

¼ The figure above and the next two figures show how you can configure the GULOOGRZQ�FKDUDFWHULVWLFV�IRU�WKH�FKDUDFWHULVWLFV�LQ�WKH�URZV�DQG�FROXPQV�GULOOGRZQ�DUHD. All the examples refer to the line structure. The column structure functions in the same way.

¼ In the image above, the product group and the product are drilldown characteristics.

¼ “%RRNHG�YDOXHV” means that only the product group-product combinations for which transaction data already exist are displayed.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-37

SAP AG 2006


'ULOOGRZQ�LV�ILOOHG�ZLWK�PDVWHU�GDWD LQ�WKH�VHOHFWLRQ�

��:DWHU$OFRKROLF��-XLFH$OFRKROLF

��-XLFH1RQ�DOFRKROLF��:DWHU1RQ�DOFRKROLF

��%HHU$OFRKROLF

��:LQH1RQ�DOFRKROLF��%HHU1RQ�DOFRKROLF

��:LQH$OFRKROLF$PRXQW3URGXFW3URGXFW *URXS

�

¼ ³0DVWHU�GDWD´ for the drilldown characteristics means that all the characteristic attributes in the data range is displayed in the rows (or columns), regardless of whether or not there is any transaction data for the master data.

¼ If you include multiple characteristics in the drilldown, the query generates the PDWKHPDWLFDO�FRPELQDWLRQV that are possible for this data range.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-38

SAP AG 2006


��-XLFH1RQ�DOFRKROLF��:DWHU1RQ�DOFRKROLF

��%HHU$OFRKROLF��:LQH$OFRKROLF$PRXQW3URGXFW3URGXFW *URXS

,I�WKHUH�DUH�PXOWLSOH�FKDUDFWHULVWLFV�LQ WKH�GULOOGRZQ��³EXVLQHVV�UHOHYDQW�FRPELQDWLRQV´ DULVH��UHVXOWLQJ�IURP�WKH�FKDUDFWHULVWLF�UHODWLRQVKLSV�GHILQHG�LQ�WKH�SODQQLQJ�PRGHOHU�

�

¼ If “&KDUDFWHULVWLF�UHODWLRQVKLSV” is selected for the drilldown characteristics, the query (like the plan query and the reporting query) displays all the EXVLQHVV�UHOHYDQW�FRPELQDWLRQV that result from the characteristic relationships maintained in the planning modeler.

¼ Please note that mathematically possible combinations may be displayed in the query despite the characteristic relationships maintained in the planning modeler. This is the case if the “ Characteristic relationships” flag (which was set in the figure above) was not selected and “ Master data” was chosen instead.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-39

SAP AG 2006

7KH�4XHU\V�'ULOOGRZQ�3URSHUWLHV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�ZKDW�RSWLRQV�WKHUH�DUH�IRU�GHVLJQLQJ�WKH�

GULOOGRZQ�RI�FKDUDFWHULVWLFV�LQ�URZV�DQG�RU�FROXPQV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-40

SAP AG 2006

5HDG�%HKDYLRU�RI�,QSXW�5HDG\�4XHULHV��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�HVVHQWLDOO\�ZKLFK�GDWD�UHFRUGV�DUH�

GLVSOD\HG�LQ�D�SODQ�TXHU\�DQG�LQ�D�UHSRUWLQJ�TXHU\

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-41

SAP AG 2006

5HDG�%HKDYLRU�RI�,QSXW�5HDG\�4XHULHV��8QLW�2YHUYLHZ�'LDJUDP

8QLW�2YHUYLHZ

� /HVVRQ��8QLTXHQHVV�LQ�DQ�,QSXW�5HDG\�&HOO



�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-42

SAP AG 2006

5HDG�%HKDYLRU�RI�,QSXW�5HDG\�4XHULHV��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�ILQG�RXW�DERXW�WKH�UHDG�EHKDYLRU�RI�UHSRUWLQJ�DQG�SODQ�TXHULHV�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-43

SAP AG 2006

5HDG�%HKDYLRU�LQ�5HDO�7LPH�,QIR3URYLGHUV

5HDG�PRGH�� UHDG�IURP�FORVHG�UHTXHVWV�RQO\5HTXHVW��5HTXHVW��

2SHQ�UHTXHVW

5HTXHVW��5HTXHVW��

2SHQ�UHTXHVW

5HDG�PRGH��UHDG�IURP�RSHQ�DQG�FORVHG�UHTXHVWV��

4XHU\�SURSHUWLHV�UHJDUGLQJ�UHDG�PRGH�� $OO�SDUW�SURYLGHUV�XS�WR�VDIHO\�UHDFKDEOH�VWDWH�� 7KH�WUDQVDFWLRQ�SDUW�SURYLGHUV�XS�WR�FXUUHQW�VWDWH

�

¼ The figure above shows the basic read behavior of requests in a query.

¼ For VWDQGDUG�,QIR&XEHV, the read mode is always set to 0. This means they only read from closed requests, which is the normal case for a reporting query.

¼ If the query is based on a UHDO�WLPH�,QIR3URYLGHU, this can form the basis of a reporting query or a plan query.

¼ Every query that is created on a real-time InfoProvider or an aggregation level has read mode 1 by default.

¼ (YHQ�LI�\RX�VZLWFK�WKH�UHDG�PRGH�WR��WKH�PRGH�VZLWFKHV�DXWRPDWLFDOO\�WR��LI�D�SODQ�TXHU\�DQG�D�UHSRUWLQJ�TXHU\�UXQ�LQ�WKH�VDPH�HQYLURQPHQW.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-44

SAP AG 2006

3ODQQLQJ�DQG�5HSRUWLQJ�LQ�WKH�6KDUHG�(QYLURQPHQW

5HSRUWLQJ�4XHU\

3ODQ4XHU\

5HTXHVW��5HTXHVW��

2SHQ�5HTXHVW

3ODQ�%XIIHU

�

¼ If a reporting query runs together with a plan query in the same environment, the reporting query also displays data from the plan buffer without the need for saving data. This makes it possible to run simulations.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-45

SAP AG 2006

5HDG�%HKDYLRU�RI�,QSXW�5HDG\�4XHULHV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�HVVHQWLDOO\�ZKLFK�GDWD�UHFRUGV�DUH�

GLVSOD\HG�LQ�D�SODQ�TXHU\�DQG�LQ�D�UHSRUWLQJ�TXHU\

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-46

SAP AG 2006

&UHDWLQJ�D�3ODQ�4XHU\��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�EDVLF�SODQQLQJ�VHWWLQJV�LQ�WKH�TXHU\�

GHVLJQHU� 8QGHUVWDQG�KRZ�WR�VHW�XS�XQLTXHQHVV�LQ�DQ�LQSXW�

UHDG�TXHU\� 5HFRJQL]H�ZKDW�\RX�QHHG�WR�SD\�DWWHQWLRQ�WR�ZKHQ�

GHILQLQJ�D�ILOWHU� 8QGHUVWDQG�KRZ�WKH�TXHU\V�GULOOGRZQ�EHKDYLRU�LV�

GHVLJQHG� 8QGHUVWDQG�WKH�UHDG�EHKDYLRU�LQ�TXHULHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-47

�([HUFLVHV�

8QLW�� &UHDWLQJ�D�3ODQ�4XHU\�/HVVRQ�� *HQHUDWLQJ�D�4XHU\�WKDW�,V�5HDG\�IRU�,QSXW�


• Make the basic settings for setting up write access to the query

• Define a plan query that is ready for input in Query Designer

In the following sections, the required, ready-for-input queries are to be created for the CFO and the sales manager by using Query Designer.

First of all, the CFO needs to be able to plan the sales quantity at his granularity controlling area, company code.

Then, an input option for planning quantities and prices must be created for the detailed planner.

Since the conceptual requirements regarding the queries also contain conditions and exceptions, these are to be taken into account at the corresponding point in Query Designer.

1-1 First of all, log on to 4XHU\�'HVLJQHU. You get to query designer by pressing the “6WDUW” button within Citrix and then choosing 3URJUDPV��!�%XVLQHVV�([SORUHU��!�4XHU\�'HVLJQHU. If you now get a ³6$3�/RJRQ´�SURPSW for your training system, select client 800 as well as your user and password and select the language setting for this course. Then FUHDWH a new plan query.

1-1-1 First of all, a plan query is to be created for the &)2�DQG�WKH�&)2V�TXDQWLW\�SODQQLQJ. This plan query of the CFO is to refer to aggregation level 6��B$/B��. 6HDUFK for it by its WHFKQLFDO�QDPH and then start the Customizing of the query. First of all, enter “ >.H\@ 7H[W“ for the “7HFKQLFDO�1DPH” button and drag all characteristics into the “5RZV” area, so that you get the following RUGHU: ILVFDO�\HDU��FRQWUROOLQJ�DUHD��FRPSDQ\�FRGH��ILVFDO�\HDU�YDULDQW��VDOHV�XQLW��FXUUHQF\��YHUVLRQ� Drag all key figures into the “&ROXPQV” area. This is where the 6DOHV�TXDQWLW\�EHIRUH�UHYHQXH and the 5HYHQXH�EHIRUH�SURILW�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-48

PDUJLQ are positioned.

6DYH�your query using the following description: Description: 7%:��B6��B$/��B34��B&)2 Technical name: 6��B$/B��B3ODQTXHU\B��B&)2

1-1-2 You should now set up ZULWH�DFFHVV�LQ�WKH�TXHU\. Where do you have to make these settings? 1.___________________________________________________________ 2. ___________________________________________________________ Which write access options can you set up with regard to the key figures? 1.___________________________________________________________ 2.___________________________________________________________ 3.___________________________________________________________ For the 6DOHV�TXDQWLW\ key figure, you should allow PDQXDO�HQWU\ and DXWRPDWLF entry of data. For the two NH\�ILJXUHV�&$� (coverage amount 1) and 5HYHQXH you should only allow DXWRPDWLF�HQWU\. 6DYH your settings after you’ve made DOO settings from 1-1-2.

1-1-3 Configure the filter of the query by first limiting the data range to the selections to be planned by the CFOs. Which area of the filter is responsible for the configuration of the data range? _____________________________________________________________ Assign the following fields with the following selections to this area of the filter:

1. Characteristic 2. Limit to

3. Version 4. A

5. Currency � 6. USD

7. Sales unit 8. ST


11. Fiscal year 12. Variable: Group##_VAR_FY_01_PM

13. Controlling area 14. 1000

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-49

15. Company code 16. 1000; 2000

1-1-4 Planning is to commence with the start selection of company code ��. In which part of the query do you have to configure the start selection of the company code? _____________________________________________________________ 0DNH�WKLV�DVVLJQPHQW and then VDYH the query.

1-1-5� ([HFXWH the thus defined 3ODQ�4XHU\�RI�WKH�&)2V�for fiscal year ��by pressing the ³([HFXWH´�button. You should now see the following display:

As you can see, the cell of the sales quantity with 150 is ready for input in this Web test screen!

1-1-6 Now change the start selection at runtime by setting the company code to �� and the variable of the fiscal year to ��. Please note that manually planning and subsequently pressing the 5HIUHVK in this ad-hoc query always overwrites the manually planned data with the initial data that is read from the InfoProvider. That is, the manually planned values would not be retained in this interface! To be able to actually plan, this ad-hoc plan query must be integrated into a workbook or web-based query. This happens in later chapters. &ORVH�WKH�H[HFXWHG�TXHU\, to avoid subsequent locks and open a VHFRQG�VHVVLRQ.

1-1-7 You can also execute the TXHU\�XVLQJ�4XHU\�0RQLWRU, which would also allow you to save the plan data. There, you can also choose between a GUI-based and a web-based display of the query. There are two variants of Query Monitor. The second variant is more user-friendly.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-50

Variant 1: Open a second session and navigate via 6$3�0HQX��!�%XVLQHVV�([SORUHU��!�%([�0RQLWRU��!�4XHU\�0RQLWRU.

Variant 2: To be able to select between GUI and web-based display, you should select transaction 5657 on the second monitor. Choose the VHFRQG�YDULDQW� For the “4XHU\” field select your query “6��B$/B��B3ODQTXHU\B��B&)2” �and for the “4XHU\�'LVSOD\” field select “+70/” . ([HFXWH the query for fiscal year �� . You should see the following display:

Now close the executed query and change the “4XHU\�'LVSOD\” field to “%([�$QDO\]HU” . Execute the query again for ��. You should see the following display:

/HDYH 4XHU\�0RQLWRU and return to the first 4XHU\�'HVLJQHU session.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-51

1-1-8 :LWKLQ�TXHU\�&XVWRPL]LQJ��VDYH the ILOWHU�that you’ve created for task 1-1-3 and 1-1-4: Description: 7%:��B6��B$/��B)��$ Technical name: 6��B)B��$�� Which of the filters that you have created could be selected into the characteristic restrictions and default values area within the plan query and where can you find them in Query Designer? Enter only the respective WHFKQLFDO�QDPHV of these filters. ______________________________________________________________ ______________________________________________________________ ______________________________________________________________ 6DYH the Customizing of the query and leave Query Designer open.

1-1-9 Open a second session and navigate to 3ODQQLQJ�0RGHOHU to take a closer look at filter 6��B)B��$�, which has been created for InfoProvider 7%:��6�� and aggregation level 6��B$/B��. Look especially at the settings via the “6KRZ�DGYDQFHG�YLHZ” pushbutton in Planning Modeler. Which query area is reflected in the “'HIDXOW�YDOXH��NH\�” of the Planning Workbench? Why do all fields of the filter in Planning Modeler show a selection for the “&DQ�%H�&KDQJHG�DW�([HFXWLRQ” selection field? ______________________________________________________________ ______________________________________________________________ ______________________________________________________________ Close the second session.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-52

1-2 You need two more queries for VDOHV�PDQDJHU�SODQQLQJ, one for TXDQWLW\�SODQQLQJ�DQG�RQH�IRU�SULFH�SODQQLQJ.

1-2-1 In the context of InfoProvider 6��B$/B�� you need to create a plan query for quantity planning that is ready for input and appears as follows:

17. Controlling area

18. Company code

19. Material group

20. Sales volume 2010

21. 22. 23. 24.

25. Sales volume 2011

26. Revenue 2010

27. Revenue 2011

28. DB1 2010

29. 30. 31. 32.

Implement the following concept for the plan query: Only include characteristics according to the figure above in the row. Create a ORFDO�VWUXFWXUH�ZLWK��VHOHFWLRQ�FROXPQV. Each of these columns is to contain the characteristic )LVFDO�\HDU and the NH\�ILJXUH mapped for each column, the unit of measure 67 DQG�the currency 86'. Please take into account that all columns, irrespective of whether they are quantity or amount columns always include the unit of measure for the quantity and that for the amount! Both key figures 5HYHQXH and '%� should only be fillable by DXWRPDWLF�SODQQLQJ whereas it should be possible to plan the 6DOHV�TXDQWLW\ manually and automatically. Please note that these write accesses to the key figures must now be defined for each selection columns of the structure! Ensure that the query always has a write access. With regard to the Fiscal year characteristic, you have to use the variable *URXS��B9$5B)<B��B30, which has been created in Planning Modeler and which has the default value 2010. Here, the variable is to be entered in all six columns of the local structure at first. For columns representing the year 2011 the variable offset must subsequently be set to �.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-53

For the three columns representing 2011, double-click the variable within your local structure column for 2011 first. This takes you to the following screen: ³6HOHFW�YDOXHV�IRU�>�ILVF\HDU@�ILVFDO�\HDU´�� On the right side of this screen, in the “6HOHFWLRQ” �DUHD��you can then increase the�variable *URXS��B9$5B)<B��B30�by a factor of “��” . 6DYH these settings in the query. Enter the following description for the query: Description: 7%:��B6��B$/��B34��B6$/0$1 Technical name: 6��B$/B��B3ODQTXHU\B��B6$/0$1��

The header of the respective selection column in the local structure is to be supplied using a WH[W�YDULDEOH that automatically adjusts the fiscal year to that of the variable. To do so, go to the column that you have designed for “6DOHV�TXDQWLW\��” , double-click it and define this text variable by clicking on the “EODFN�WULDQJOH” to the right of the “'HVFULSWLRQ” field next to the variable pushbutton and select “1HZ�9DULDEOH” . Description: *URXS��B9$5B)<B4'B7(;79�� Technical name: *URXS��B9$5B)<B4'B7(;79 This time, choose “3URFHVVLQJ�%\” VXEVWLWXWLRQ�SDWK and refer to the “5HIHUHQFH�FKDUDFWHULVWLF” �),6&<($5. Replace the variable with the ,QIR2EMHFW and select 'HVFULSWLRQ for “9DULDEOH�5HSUHVHQWV” . Please note that you have to select the “ InfoObject” here and not the “ variable” because the “ variable” only refers to already existing text variables. The settings in the fields “ User interval” and “ Offset setting” are not relevant for the text variable *URXS��B9$5B)<B4'B7(;79 so that you can apply the already selected standard settings. 6DYH the variable definition. This thus defined variable has to be included in the “'HVFULSWLRQ” area of every selection column of the local structure. You do so by clicking the variable icon next to the “ Description” area and then selecting the previously created variable for every column. After creating the text variable, every column should have the following entry in the “'HVFULSWLRQ” area, here illustrated using the sales quantity:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-54

Sales quantity *URXS��B9$5B)<B4'B7(;79��

Please note that a distinction between headers by 2010 and 2011 is not required for the text variable, because there is a reference to characteristic 0FISCYEAR and this characteristic is determined by means of the characteristic variable in the selection column. In general, the text variable first searches the selection column for the value to be replaced and then, with priority 2, searches for a selection in the filter. Here, it knows the assignment from the structure and since the characteristic value in the next column was increased by “ +1” , the text variable for the corresponding columns is also increased by “ +1” . 6DYH the query.

1-2-2 Now specify the ILOWHU for the query. The attributes version and fiscal year variant are not included in the drilldown of the structure. Hence, they should not be displayed when the query is called up. Select these fields into the “&KDUDFWHULVWLF�UHVWULFWLRQV” and specify the data range as follows: Version: % Fiscal year variant: .� Furthermore, select the fields Controlling Area, Company code, Material group into the “&KDUDFWHULVWLF�UHVWULFWLRQV” as well and limit the data range to: Controlling area: �� Company code: �� Material group: ��:$7��7:$7��-8& . Do not make a selection in the “'HIDXOW�YDOXHV” area. Since this filter is only required for this query and not in Planning Modeler, the filter is not saved.

1-2-3 ([HFXWH the�TXHU\ and select for fiscal year��. Data in version % with material group� should be available for sales quantity ��, and the cells for the Sales quantity 2010 and 2011 column should be ready for input. The query should appear as follows (here's an excerpt):

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-55

Please note that the “ Fiscal year” field is stored under Free Characteristics in the navigation block. The sales manager can choose a different variable value for the fiscal year by ULJKW�FOLFNLQJ�WKLV�ILHOG��!�)LOWHU��!�9DULDEOH�6FUHHQ or by pressing 5HIUHVK.

1-2-4 Navigate back to 4XHU\�'HVLJQHU and define a &RQGLWLRQ that is going to be used in the workbook and the Web query later. The condition that you are about to model is supposed to achieve the following: The “6DOHV�4XDQWLW\��” column is to be ODUJHU�WKDQ�RU�HTXDO�WR�� and this condition is supposed to apply to the characteristic assignment “$OO�FKDUDFWHULVWLFV�LQ�WKH�EUHDNGRZQ�LQGHSHQGHQWO\” . As the description choose: *URXS��B6DOHVB4XDQWLW\B&RQGLWLRQ� $FWLYDWH the condition you've created in the context menu of the condition as well as in the ³3URSHUWLHV” area (right edge of the query). 6DYH your query and H[HFXWH�the query for the fiscal year ��. According to the query display the results should not differ from those in task 1-2-3 because all sales quantities are larger than 100.

1-2-5 Define an ([FHSWLRQ, which is to be modeled as follows: As the description choose: *URXS��B([FHSWLRQB�� $FWLYDWH the exception you are creating in the context menu of the exception as well as in the “3URSHUWLHV” area (right edge of the query). Select the following intervals and the following settings for “'HILQHV�([FHSWLRQ�9DOXHV” :

33. Alert level 34. Operator 35. From value

36. To value

37. Good 1 38. ≥ 39. 1000 40.

41. Critical 1 42. Between 43. 500 44. 1000

45. Bad 1 46. ≤ 47. 500 48.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-56

For “([FHSWLRQ�,V�'HILQHG�2Q” , select “$OO�VWUXFWXUH�HOHPHQWV” . For “'DWD�FHOOV” select “([FHSWLRQ�$IIHFWV�'DWD�&HOOV” and for “.H\�)LJXUHV” select “$OO�6WUXFWXUH�(OHPHQWV” . For “&HOO�5HVWULFWLRQV” and here under “6WDQGDUG�2SHUDWRU�IRU�$OO��&KDUDFWHULVWLFV�7KDW�$UH�1RW�/LVWHG” select “([FHSWLRQ�$IIHFWV�(YHU\WKLQJ” . Under “&HOO�5HVWULFWLRQV” select characteristic “0DWHULDO�*URXS” and operator “$OO�H[FHSW�HYHQWV” .

6DYH the query and execute it for ��. Here is an excerpt of what you should see:

With regard to the condition you should only see sales quantities greater than or equal to 100 pieces and some data cells - not the totals rows - should have the same color highlight across all structure columns. The sales for the sales quantity are still ready for input!

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-57

1-3 Following that you need to create a third query for the SULFH�SODQQLQJ�RI�WKH�VDOHV�PDQDJHUV. Create the query for aggregation level 3��B$/B�� of InfoProvider 7%:��3��. The query should look like this:

49. Fiscal year

50. Material group

51. Price version B 1 52. Price version B 2

53. 54. 55. 56.

57. Price version B

58. Cost of goods sold Version B 1

59. Cost of goods sold Version B 2

60. Cost of goods sold Version B

61. 62. 63. 64.

1-3-1 Use ORFDO�VWUXFWXUHV and set columns “3ULFH�YHUVLRQ�%” and “&RVW�RI�JRRGV�VROG�YHUVLRQ�%” as FDQ�RQO\�EH�ILOOHG�DXWRPDWLFDOO\. In contrast, the SULFH�DQG�FRVW�RI�JRRGV�VROG�FROXPQV for YHUVLRQ�%��%� should be set to FDQ�EH�SODQQHG�PDQXDOO\�DQG�DXWRPDWLFDOO\. Set the HQWLUH�TXHU\ to UHDG\�IRU�LQSXW. Save your query as follows: Description: 7%:��B3��B$/��B34��B6$/0$1 Technical name: 3��B$/B��B3ODQTXHU\B��B6$/0$1��

1-3-2 Position the ILVFDO�\HDU�and�PDWHULDO�JURXS in the “5RZV” area of the query. For both of them “3URSHUWLHV” , “.H\V” and “3RVWHG�YDOXHV” need to be set. )LVFDO�\HDU��FXUUHQF\��ILVFDO�\HDU�YDULDQW and PDWHULDO�JURXS are to be included in the “&KDUDFWHULVWLF�UHVWULFWLRQV” and the data range needs to be restricted as follows:

65. Characteristic 66. Limit to

67. Currency 68. USD


71. Material group 72. TWAT; JUC

For the fiscal year, you create an LQWHUYDO (that is, select “9DOXH�UDQJHV” for the selection field “6KRZ” ) in the “&KDUDFWHULVWLF�5HVWULFWLRQV” . Its left and right boundary value refer to the variable *URXS��B9$5B)<B��B30.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-58

The left boundary value should then receive the offset “ �” and the right boundary should have the offset “��” . The “'HIDXOW�YDOXHV” area does not get any values! 6DYH the query and execute it for the fiscal year ��. Here is an excerpt of what you should see:

)ROORZLQJ�WKLV close 4XHU\�'HVLJQHU�DQG�WKH�H[HFXWHG�TXHULHV and return to the initial screen after the system logon.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-59

��6ROXWLRQV�

8QLW�� &UHDWLQJ�D�3ODQ�4XHU\�/HVVRQ�� *HQHUDWLQJ�D�4XHU\�WKDW�,V�5HDG\�IRU�,QSXW�

1-1 First of all, log on to 4XHU\�'HVLJQHU. You get to query designer by pressing the “6WDUW” button within Citrix and then choosing 3URJUDPV��!�%XVLQHVV�([SORUHU��!�4XHU\�'HVLJQHU. If you now get a “6$3�/RJRQ³�SURPSW for your training system, select client 800 as well as your user and password and select the language setting for this course. Then FUHDWH a new plan query. Then click the left button of the left toolbar or enter the key combination <Ctrl>+N.

1-1-1 First of all, a plan query is to be created for the &)2�DQG�WKH�&)2¶V�TXDQWLW\�SODQQLQJ. This plan query of the CFO is to refer to aggregation level 6��B$/B��. 6HDUFK for it by its WHFKQLFDO�QDPH and then start the Customizing of the query. First of all, enter “ >.H\@ 7H[W“ for the “7HFKQLFDO�1DPH” button and drag all characteristics into the “5RZV” area, so that you get the following RUGHU: ILVFDO�\HDU��FRQWUROOLQJ�DUHD��FRPSDQ\�FRGH��ILVFDO�\HDU�YDULDQW��VDOHV�XQLW��FXUUHQF\��YHUVLRQ� Drag all key figures into the “&ROXPQV” area. This is where the 6DOHV�TXDQWLW\�EHIRUH�UHYHQXH and the UHYHQXH�EHIRUH�SURILW�PDUJLQ are positioned.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-60

Your query should look like this:

6DYH�your query using the following description: Description: 7%:��B6��B$/��B34��B&)2 Technical name: 6��B$/B��B3ODQTXHU\B��B&)2

1-1-2 You should now set up ZULWH�DFFHVV�LQ�WKH�TXHU\. Where do you have to make these settings? 1. In the properties of the NH\�ILJXUHV (“ Planning” tab) 2. In the properties of the TXHU\ (“ Planning” tab) &DXWLRQ: <RX�FDQ�RQO\�DFWLYDWH�WKH�³6WDUW�TXHU\�LQ�FKDQJH�PRGH´�VHWWLQJ��LI�DW�OHDVW�RQH�NH\�ILJXUH�KDV�EHHQ�UHOHDVHG�IRU�GDWD�HQWU\� Which write access options can you set up with regard to the key figures? 1. Data cannot be changed 2. Data can be changed using planning functions. 3. Data can be changed using user input and planning functions. For the 6DOHV�TXDQWLW\ key figure, you should allow XVHU�HQWULHV and �DXWRPDWLF�HQWULHV of data. For the two NH\�ILJXUHV�&$� (coverage amount 1) and 5HYHQXH you should only allow DXWRPDWLF�HQWU\. 6DYH your settings after you have made DOO�VHWWLQJV�from 1-1-2.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-61

1-1-3 Configure the filter of the query by first limiting the data range to the selections to be planned by the CFOs. Which area of the filter is responsible for the configuration of the data range? “&KDUDFWHULVWLF�5HVWULFWLRQV” area Assign the following fields with the following selections to this area of the filter:

&KDUDFWHULVWLF� /LPLW�WR�Version $�Currency 86'�Sales unit 67�Fiscal year variant .��Fiscal year 9DULDEOH��*URXS��B9$5B)<B��B30�Controlling area ��Company code ��

Your characteristic restrictions should now look like this:

1-1-4 Planning is to commence with the start selection of company code ��. In which part of the query do you have to configure the start selection of the company code? “'HIDXOW�YDOXHV” area 0DNH�WKLV�DVVLJQPHQW and then VDYH�WKH query.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-62

1-1-5 ([HFXWH the thus defined 3ODQ�4XHU\�RI�WKH�&)2V�for fiscal year ��by pressing the “([HFXWH” �button. You should now see the following display:

As you can see, the cell of the sales quantity with 150 is ready for input in this Web test screen!

1-1-6 Now change the start selection at runtime by setting the company code to �� and the variable of the fiscal year to ��. Please note that manually planning and subsequently pressing the 5HIUHVK in this ad-hoc query always overwrites the manually planned data with the initial data that is read from the InfoProvider. That is, the manually planned values would not be retained in this interface! To be able to actually plan, this ad-hoc plan query must be integrated into a workbook or web-based query. This happens in later sections. &ORVH�WKH�H[HFXWHG�TXHU\ to avoid subsequent locks and open a VHFRQG�VHVVLRQ.

1-1-7 You can also execute the TXHU\�XVLQJ�4XHU\�0RQLWRU, which would also allow you to save the plan data. There, you can also choose between a GUI-based and a web-based display of the query. There are two variants of Query Monitor. The second variant is more user-friendly. Variant 1: Open a second session and navigate via 6$3�0HQX��!�%XVLQHVV�([SORUHU��!�%([�0RQLWRU��!�4XHU\�0RQLWRU. Variant 2: To be able to select between GUI and web-based display, you should select transaction 5657 on the second monitor. Choose the VHFRQG�YDULDQW� For the “4XHU\” field, select your query “6��B$/B��B3ODQTXHU\B��B&)2” �and for the “4XHU\�'LVSOD\” field, select “+70/” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-63

([HFXWH the query for fiscal year �� . You should see the following display:

Now close the executed query and change the “4XHU\�'LVSOD\” field to “%([�$QDO\]HU” . Execute the query again for ��. You should see the following display:

/HDYH 4XHU\�0RQLWRU and return to the first 4XHU\�'HVLJQHU session.

1-1-8 :LWKLQ�TXHU\�&XVWRPL]LQJ��VDYH the ILOWHU�that you have created for task 1-1-3 and 1-1-4: Description: 7%:��B6��B$/��B)��$ Technical name: 6��B)B��$�� To do so, right-click in the header of the “&KDUDFWHULVWLF�5HVWULFWLRQV” area and choose the “6DYH” entry in the context menu. Which of the filters that you have created could be selected into the characteristic restrictions and default values area within the plan query and where can you find them in Query Designer? Enter only the respective WHFKQLFDO�QDPHV of these filters.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-64

6��B)B��6��B)B��D��6��B)B�� - You can find them in the left panel of Query Designer, which also contains the dimensions/characteristics.

6DYH the Customizing of the query again and keep Query Designer open.

1-1-9� 2SHQ a second session and navigate to 3ODQQLQJ�0RGHOHU to take a closer look at filter 6��B)B��$�, which has been created for InfoProvider 7%:��6�� and aggregation level 6��B$/B��. Look especially at the settings using the “6KRZ�DGYDQFHG�YLHZ” pushbutton in Planning Modeler. Which query area is reflected in the “'HIDXOW�YDOXH��NH\�” of the Planning Workbench? “'HIDXOW�YDOXHV´ area Why do all fields of the filter in Planning Modeler show a selection for the “&DQ�%H�&KDQJHG�DW�([HFXWLRQ” selection field? %HFDXVH�WKHVH�FKDUDFWHULVWLFV�DUH�HLWKHU�FRQWDLQHG�LQ�WKH�URZV��FROXPQV��RU�WKH�IUHH�FKDUDFWHULVWLFV�DQG�WKHVH�YDOXHV�FDQ�WKXV�EH�FKDQJHG�DW�UXQWLPH� Close the second session.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-65

1-2 You need two more queries for VDOHV�PDQDJHU�SODQQLQJ, one for TXDQWLW\�SODQQLQJ�DQG�RQH�IRU�SULFH�SODQQLQJ.

1-2-1 In the context of InfoProvider/ aggregation level 6��B$/B�� you need to create a plan query for quantity planning that is ready for input and appears as follows:

&RQWUROOLQJ�DUHD�

&RPSDQ\�FRGH�

0DWHULDO�JURXS�

6DOHV��YROXPH��

6DOHV��YROXPH��

5H�YHQXH�

5H�YHQXH ��

&$� ��

&$� ��

Implement the following concept for the plan query: Only include characteristics according to the figure above in the row. Create a ORFDO�VWUXFWXUH�ZLWK��VHOHFWLRQ�FROXPQV. Each of these columns is to contain the characteristic )LVFDO�\HDU and the NH\�ILJXUH mapped for each column, the unit of measure 67 DQG�the currency 86'.

First of all, create a structure by placing the cursor on the “&ROXPQV” , right-click “1HZ�6WUXFWXUH” and then go to the structure node, right-click and choose “1HZ�6HOHFWLRQ” . Following that, configure the “6DOHV�4XDQWLW\��” column as follows:

.H\�ILJXUH�6DOHV�TXDQWLW\��XQLW�RI�PHDVXUH��FXUUHQF\�86'��ILVFDO�\HDU��9DULDEOH�*URXS��B9$5B)<B��B30� 3URFHHG�DFFRUGLQJO\�IRU�DOO�FROXPQV� Please take into account that all columns, irrespective of whether they are quantity or amount columns always include the unit of measure for the quantity and that for the amount! Both key figures 5HYHQXH and &$� should only be fillable by DXWRPDWLF�SODQQLQJ whereas it should be possible to plan the 6DOHV�TXDQWLW\ manually and

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-66

automatically. Please note that these write accesses to the key figures must now be defined for each selection column of the structure! Ensure that the query always has a write access. With regard to the Fiscal Year characteristic, you have to use the variable *URXS��B9$5B)<B��B30, which has been created in Planning Modeler and which has the default value 2010.

Here, the variable is to be entered in all six columns of the local structure first. For columns representing the year 2011 the variable offset must subsequently be set to �.

For the three columns representing 2011, double-click the variable within your local structure column for 2011 first. This takes you to the following screen:�³6HOHFW�YDOXHV�IRU�>�ILVF\HDU@�ILVFDO�\HDU´�� On the right side of this screen, in the “6HOHFWLRQ´�DUHD��\RX�FDQ�WKHQ�LQFUHDVH�WKH�variable *URXS��B9$5B)<B��B30�by a factor of “��” . 6DYH these settings in the query. Enter the following description for the query: Description: 7%:��B6��B$/��B34��B6$/0$1 Technical name: 6��B$/B��B3ODQTXHU\B��B6$/0$1�� The header of the respective selection column in the local structure is to be filled using a WH[W�YDULDEOH that automatically adjusts the fiscal year to that of the variable. To do so, go to the column that you have designed for “6DOHV�TXDQWLW\��” . Double-click it and define this text variable by clicking on the “EODFN�WULDQJOH” to the right of the “'HVFULSWLRQ” field next to the variable pushbutton and select “1HZ�9DULDEOH” . Description: *URXS��B9$5B)<B4'B7(;79�� Technical name: *URXS��B9$5B)<B4'B7(;79 This time, choose “3URFHVVLQJ�%\” VXEVWLWXWLRQ�SDWK and refer to the “5HIHUHQFH�FKDUDFWHULVWLF” �),6&<($5.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-67

Replace the variable with the ,QIR2EMHFW and select 'HVFULSWLRQ for “9DULDEOH�5HSUHVHQWV” .

Please note that you have to select the “ InfoObject” here and not the “ Variable” because the “ variable” only refers to already existing text variables. The settings in the fields “ User interval” and “ Offset setting” are not relevant for the text variable *URXS��B9$5B)<B4'B7(;79 so that you can apply the already selected standard settings. 6DYH the variable definition. This thus defined variable has to be included in the “'HVFULSWLRQ” area of every selection column of the local structure. You do so by clicking the variable icon next to the “ Description” area and then selecting the previously created variable for every column. After creating the text variable, every column should have the following entry in the “'HVFULSWLRQ” area, here, illustrated using the sales quantity: Sales quantity *URXS��B9$5B)<B4'B7(;79�� Please note that a distinction between headers by 2010 and 2011 is not required for the text variable. This is because there is a reference to characteristic 0FISCYEAR and this characteristic is determined by means of the characteristic variable in the selection column. The text variable first searches the selection column for the value to be replaced and then, with priority 2, for a selection in the filter. Here, it knows the assignment from the structure and since the characteristic value in the next column was increased by “ +1” , the text variable for the corresponding columns is also increased by “ +1” . 6DYH the query.

1-2-2 Now specify the ILOWHU for the query. The attributes version and fiscal year variant are not included in the drilldown of the structure. Hence, they should not be displayed when the query is called up. Select these fields into the “&KDUDFWHULVWLF�UHVWULFWLRQV” and specify the data range as follows: Version: % Fiscal year variant: .� Furthermore, select the fields Controlling Area, Company code, Material group into the “&KDUDFWHULVWLF�UHVWULFWLRQV” as well and limit the data range to:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-68

Controlling area: �� Company code: �� Material group: ��:$7��7:$7��-8& . Do not make a selection in the “'HIDXOW�YDOXHV” area.

Since this filter is only required for this query and not in Planning Modeler, the filter is not saved.

1-2-3 ([HFXWH the�TXHU\ and select for fiscal year ��. Data in version % with material group� should be available for sales quantity ��, and the cells for the Sales quantity 2010 and 2011 column should be ready for input. The query should appear as follows (here's an excerpt):

Please note that the “ Fiscal year” field is stored under Free Characteristics in the navigation block. The sales manager can choose a different variable value for the fiscal year by ULJKW�FOLFNLQJ�WKLV�ILHOG��!�)LOWHU��!�9DULDEOH�6FUHHQ or by pressing 5HIUHVK.

1-2-4 Navigate back to 4XHU\�'HVLJQHU�and define a &RQGLWLRQ that is going to be used in the workbook and the Web query later. The condition that you are about to model is supposed to result in the following: The “6DOHV�4XDQWLW\��” column is to be ODUJHU�WKDQ�RU�HTXDO�WR�� and this condition is supposed to apply to the characteristic assignment “$OO�FKDUDFWHULVWLFV�LQ�WKH�EUHDNGRZQ�LQGHSHQGHQWO\” . *URXS��B6DOHVB4XDQWLW\B&RQGLWLRQ� $FWLYDWH the condition you have created in the context menu of the condition as well as in the“3URSHUWLHV” area (right edge of the query). 6DYH your query and H[HFXWH�the query for the fiscal year ��. According to the query display the results should not differ from those in task 1-2-3 because all sales quantities are larger than 100.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-69

1-2-5 Define an ([FHSWLRQ, which is to be modeled as follows: Choose the following description: *URXS��B([FHSWLRQB�� $FWLYDWH the exception you are creating in the context menu of the exception as well as in the “3URSHUWLHV” area (right edge of the query). Select the following intervals and the following settings for “'HILQH�([FHSWLRQ�9DOXHV” :

For “([FHSWLRQ�,V�'HILQHG�2Q” , select “$OO�VWUXFWXUH�HOHPHQWV” . For “'DWD�&HOOV” select “([FHSWLRQ�$IIHFWV�'DWD�&HOOV” and for “.H\�)LJXUHV” select “$OO�6WUXFWXUH�(OHPHQWV” . For “&HOO�5HVWULFWLRQV” and here under “6WDQGDUG�2SHUDWRU�IRU�$OO��&KDUDFWHULVWLFV�7KDW�$UH�1RW�/LVWHG” select “([FHSWLRQ�$IIHFWV�(YHU\WKLQJ” . Under “&HOO�5HVWULFWLRQV” select characteristic “0DWHULDO�*URXS” and operator “$OO�H[FHSW�HYHQWV” . 6DYH the query and execute it for ��. Here is an excerpt of what you should see:

With regard to the condition, you should only see sales quantities greater than or equal to 100 pieces and some data cells - not the totals rows - should have the same color highlight across all structure columns.

$OHUW�/HYHO� 2SHUDWRU� 9DOXH�)URP�

9DOXH��7R�

Good 1 ≥ 1000

Critical 1 Between 500 1000

Bad 1 ≤ 500

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-70

The sales for the sales quantity are still ready for input!

1-3 Following that you need to create a third query for the SULFH�SODQQLQJ�RI�WKH�VDOHV�PDQDJHUV. Create the query for aggregation level 3��B$/B�� of InfoProvider 7%:��3��. The query should look like this:

Fiscal Year

Material group

Price Version B1

Price Version B2

Price version B

Cost of goods sold Version B1

Cost of goods sold Version B2

Cost of goods sold Version B

1-3-1 Use ORFDO�VWUXFWXUHV and set columns “3ULFH�YHUVLRQ�%” and “&RVW�RI�JRRGV�VROG�YHUVLRQ�%" as FDQ�RQO\�EH�ILOOHG�DXWRPDWLFDOO\. In contrast, the SULFH�DQG�FRVW�RI�JRRGV�VROG�FROXPQV for YHUVLRQ�%��%� should be set to FDQ�EH�SODQQHG�PDQXDOO\�DQG�DXWRPDWLFDOO\. Set the HQWLUH�TXHU\ to UHDG\�IRU�LQSXW. Save your query as follows: Description: 7%:��B3��B$/��B34��B6$/0$1 Technical name: 3��B$/B��B3ODQTXHU\B��B6$/0$1��

1-3-2 Position the ILVFDO�\HDU�and�PDWHULDO�JURXS in the “5RZV” area of the query. For both of them “3URSHUWLHV” , “.H\V” and “3RVWHG�YDOXHV” need to be set. )LVFDO�\HDU��FXUUHQF\��ILVFDO�\HDU�YDULDQW and PDWHULDO�JURXS are to be included in the “&KDUDFWHULVWLF�UHVWULFWLRQV” and the data range needs to be restricted as follows:

&KDUDFWHULVWLF� /LPLW�WR�Currency 86'�Fiscal year variant .��Material group 7:$7��-8&�

For the fiscal year, you create an LQWHUYDO (that is, select “9DOXH�UDQJHV” for

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-71

the selection field “6KRZ” ) in the “&KDUDFWHULVWLFV�OLPLWDWLRQV” . Its left and right boundary value refer to the variable *URXS��B9$5B)<B��B30. The left boundary value should then receive the offset “ �” and the right boundary should have the offset “��” . The “'HIDXOW�YDOXHV” area does not get any values! 6DYH the query and execute it for the fiscal year ��. Here is an excerpt of what you should see:

)ROORZLQJ�WKLV�close 4XHU\�'HVLJQHU�DQG�WKH�H[HFXWHG�TXHULHV and return to the initial screen after the system logon.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 5-72

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-1

SAP AG 2006

&RQWHQW�� *HQHUDO�&RQFHSW�RI�WKH�/RFN�/RJLF� ([HUFLVH�RQ�WKH�/RFNLQJ�&RQFHSW� ³/RFNLQJ 6HUYLFH´�/RFN�0DQDJHPHQW

/RFNLQJ�&RQFHSW�IRU�7UDQVDFWLRQ�'DWD

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-2

SAP AG 2006

/RFNLQJ�&RQFHSW�IRU�7UDQVDFWLRQ�'DWD��/HDUQLQJ�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�JHQHUDO�FRQFHSW�RI�WKH�ORFN�ORJLF� &DUU\�RXW�DQ�H[HUFLVH�RQ�WKH�ORFNLQJ�FRQFHSW� 8QGHUVWDQG�KRZ�WR�XVH�WKH�³/RFNLQJ�6HUYLFH´�ORFN�

PDQDJHPHQW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-3

SAP AG 2006

/RFNLQJ�&RQFHSW�IRU�7UDQVDFWLRQ�'DWD��&RXUVH�2YHUYLHZ�'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-4

SAP AG 2006

/RFNLQJ�&RQFHSW�IRU�7UDQVDFWLRQ�'DWD��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�ORFNLQJ�FRQFHSW�

� <RX�DUH�SDUWLFXODUO\�LQWHUHVWHG�LQ�WKH�³/RFNLQJ�6HUYLFH´�ORFN�PDQDJHPHQW�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-5

SAP AG 2006

*HQHUDO�&RQFHSW�RI�WKH�/RFN�/RJLF��8QLW�2YHUYLHZ�'LDJUDP

� /HVVRQ��³/RFNLQJ�6HUYLFH´�/RFN�0DQDJHPHQW

8QLW�2YHUYLHZ� /HVVRQ��*HQHUDO�&RQFHSW�RI�WKH�/RFN�/RJLF�� /HVVRQ��([HUFLVH�RQ�WKH�/RFNLQJ�&RQFHSW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-6

SAP AG 2006

*HQHUDO�&RQFHSW�RI�WKH�/RFNLQJ�&RQFHSW��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�JHQHUDO�FRQFHSW�RI�WKH�ORFN�ORJLF

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-7

SAP AG 2006

*HQHUDO�&RQFHSW�RI�WKH�/RFNLQJ�&RQFHSW��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�UHVSRQVLEOH�IRU�LPSOHPHQWLQJ�%,�LQWHJUDWHG�SODQQLQJ�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�ORFNLQJ�FRQFHSW�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-8

SAP AG 2006

´/RFNLQJ�6HUYLFHµ /RFN�0DQDJHPHQW

:K\�GR�\RX�QHHG�WKH�³/RFNLQJ�6HUYLFH´ ORFN�PDQDJHPHQW"� %HFDXVH�PDQ\�SODQQHUV�ZRUN�LQ�SDUDOOHO�GXULQJ�SODQQLQJ�� %HFDXVH�\RX�DUH�QRW�DOORZHG�WR�FKDQJH�WKH�VDPH�GDWD�DW�WKH�VDPH�

WLPH�Î $�ORFNLQJ�FRQFHSW�LV�QHFHVVDU\�

:KDW�GRHV�WKH�³/RFNLQJ�6HUYLFH´ ORFN�PDQDJHPHQW�DFKLHYH"� ,W�FKHFNV�LI�WKH�GDWD�WKDW�WKH�XVHU�QHHGV�LV�DOUHDG\�EHLQJ�XVHG�� ,W�LVVXHV�DSSURSULDWH�PHVVDJHV�WR�LQIRUP�WKH�XVHUV�� ,W�GLVSOD\V�WKH�ORFNHG�VHOHFWLRQV�DQG�LQIRUPDWLRQ�DERXW�ZKR�LV�

ORFNLQJ�WKHP�

�

� In general, the following applies to the locking of transaction data:

y All the data that a user calls up in the context of a plan query or a planning function is locked exclusively for that user.

y Two planners lock each other if their selections/segments match in at least one data record and use at least one shared key figure.

� The data record is locked because it is a part of the selection, regardless of whether the data record

exists or not. The reasons: the planner might be about to create the data record, or may want to later.

� If you enter plan data at a very fine granularity, the data at the next highest granularity level is also

locked.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-9

SAP AG 2006

'HWHUPLQLQJ�WKH�6HOHFWLRQV�WR�EH�/RFNHG

<RX�FDQ�WDNH�WKH�IROORZLQJ�ORJLFDO�VWHSV WR�GHWHUPLQH�WKH�ORFNHG�VHOHFWLRQV�

� ,GHQWLI\�DOO�WKH�FKDUDFWHULVWLFV IRU�WKH�TXHU\�ZLWK�WKHLU�UHVWULFWLRQ WKURXJK�WKH�ILOWHU��FKDUDFWHULVWLF�UHVWULFWLRQ��DQG�WKH�UHVWULFWHG�NH\�ILJXUHV�RU�YDULDEOHV

� 7KHQ�LGHQWLI\�DOO�RI�WKH�,QIR3URYLGHUV RWKHU�FKDUDFWHULVWLFVWKDW�KDYH�QR UHVWULFWLRQ �³ ´��

:DUQLQJ�&KDUDFWHULVWLFV�WKDW�DUH�QRW�XVHG�DUH�ORFNHG�ZLWK�³ ´�� HYHU\WKLQJ��

�

� Whenever a user accesses plan data (in change mode), this data is locked against changes by other users. The locks will be held as long as the user is editing this data record; in other words, as long as the data is kept in the planning buffer. For this reason, the locks are only removed when the user exits planning.

� If you enter the plan data in a highly aggregated filter (that is, a filter that does not contain all the characteristics of the real-time InfoProvider), then the system has to aggregate the key figure values over all the characteristics that are not in the associated aggregation level.

� All the data records that are included in the aggregation influence the result (in other words, the sum) and thus the value that the user sees, as well as the value that the system uses for calculating the delta records after the data is changed. This means that all these records influence the result of the planning (and the delta records) and have to be locked against changes.

� Two filter selections lock each other if they contain (all) the same characteristic values and the same key figures and have at least one data record in common. However, this data record does not necessarily have to exist in the database.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-10

SAP AG 2006

6HOHFWLRQV�WR�EH�/RFNHG�IURP�WKH�3ODQ�4XHU\�3HUVSHFWLYH

)LOWHU�VHOHFWLRQ�± ZLWK�WHFKQLFDO�NH\V�±

:LWK�UHVWULFWLRQ��%$6(B820 3&�67$7B&855 (85�30B3/$9(5 ��

:LWKRXW�UHVWULFWLRQ�&RXQWU\� �'B&28175<'LVWU��FKDQQHO� �'B',6B&+$1

.H\�ILJXUHV�4X��LQ�EDVH�XQLWV� �'B48$17B%�

��

��

�� !#"%$�&�'(' )!#"%$*& ' ' )

+�,.-0/ 1 243�56,��*�4�87�9��9��4��:;��<=��4��> ��?��7��=��4��@'DWD�WR�EH�ORFNHG�GXH�WR�WKH�TXHU\�VHOHFWLRQ�

�

� This figure shows how a filter selection is derived from a plan query and leads over into the “/RFNLQJ�6HUYLFH”.

� The characteristic selections saved in the query definition need to be entered under “With restriction”.

� In the example above, there are no characteristic selections in the rows or columns, only in the filter area.

� Characteristics that have no restriction (selection), are entered under “Without restriction”. As far as locking is concerned, they are handled as if all the attributes were locked, that is “*”.

� Ultimately, the key figures that were recorded in the plan query remain. They are included in the “Key figures” area.

� The illustration above shows which data is locked because of the query definition.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-11

SAP AG 2006

/RFNLQJ�&RQFHSW��)LOWHUV�DQG�9DULDEOHV

9DULDEOH��

)LOWHU

9DULDEOH��

9DULDQW

'DWD�UHFRUGV

5HVWULFWLRQ�E\�HQG�XVHU

6HWWLQJ�WKH�ILOWHU�±YDULDEOHV�FDQ�EH�VHW�RQFH�IRU�HDFK�H[HFXWLRQ

/RFNLQJ�WKH�GDWD

'DWD�VHOHFWLRQ

�

� If you execute a planning function or query that uses a filter, first the variables in the filter are replaced. The replacement is either carried out automatically or the end user can set the variables manually.

� Manual means here that the user literally enters attributes of the variables manually; however, it is also possible to use a variant for variables if the variables are to be filled in the batch operation.

� The filter is used to lock the plan data. Here, the entire filter selection is locked, even if the user then later restricts the filter even further.

� Only the variables used to store the selection range are relevant to locking. However, the GHIDXOW�YDOXHV in the query (which can also be filled using a variable), are not used for locking; they are only used for data selection.

� Depending on the setting, the end user can restrict the filter further in the query or use “ default values” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-12

SAP AG 2006

*HQHUDO�&RQFHSW�RI�WKH�/RFNLQJ�&RQFHSW��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�FRQFHSW�RI�WKH�ORFN�ORJLF

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-13

SAP AG 2006

([HUFLVH�RQ�WKH�/RFNLQJ�&RQFHSW��8QLW�2YHUYLHZ�'LDJUDP



�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-14

SAP AG 2006

([HUFLVH�RQ�WKH�/RFNLQJ�&RQFHSW��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� &DUU\�RXW�DQ�H[HUFLVH�RQ�WKH�ORFNLQJ�FRQFHSW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-15

SAP AG 2006

([HUFLVH�RQ�WKH�/RFNLQJ�&RQFHSW��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�UHVSRQVLEOH�IRU�LPSOHPHQWLQJ�%,�LQWHJUDWHG�SODQQLQJ�DQG�ZDQW�WR�GR�DQ�H[HUFLVH�RQ�WKH�ORFNLQJ�FRQFHSW�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-16

SAP AG 2006

/RFNLQJ��([HUFLVH

'R�WKH�IROORZLQJ�ILOWHUV�ORFN�HDFK�RWKHU"�

,QIR&XEH��9(56,21��&86720(5��&28175<��5(9(18(��48$17,7<

$��9(56,21� �µ��¶��&86720(5� �µ��¶��5(9(18(%��9(56,21� �µ��¶��5(9(18(�

$��9(56,21� �µ��¶��&86720(5� �µ��¶��5(9(18(%��9(56,21� �µ��¶��5(9(18(�

$��9(56,21� �µ��¶��5(9(18(%��9(56,21� �µ��¶��48$17,7<�

$��&28175<� �µ*(5¶��5(9(18(%��&86720(5 �µ��¶��5(9(18(�

$��9(56,21� �µ��¶��&28175<� �µ*(5¶��5(9(18(%��9(56,21� �µ��¶��&86720(5� �µ��¶��5(9(18(�

�

� Assume that you are working in a real-time InfoProvider that was created with the characteristics 0VERSION, 0CUSTOMER and 0COUNTRY, as well as the key figures 0REVENUE and 0QUANTITY.

� In the first example, the planners are working in two different filters: filter A contains the characteristics 0VERSION and 0CUSTOMER and filter B contains the characteristic 0VERSION only.

� Have a look at the selections that are assigned to the characteristics and try to find out whether these selections lock each other or not.

� Proceed in the same way with the other filters.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-17

SAP AG 2006

/RFNLQJ��6ROXWLRQ

7KHVH�DUH�WKH�FRUUHFW�DQVZHUV�<HV1R1R<HV1R

�

� Solution:

Ÿ Like all data records with 0VERSION = 001 and 0CUSTOMER = 1000, these two filters lock each other. Furthermore, all the countries are contained in the selection and both filters are based on the same key figure.

Ÿ The two selections are using different versions. So there is no lock.

Ÿ The two selections are using different key figures and thus do not lock each other.

Ÿ This example is explained on the next slides.

Ÿ This example is explained on the next slides.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-18

SAP AG 2006

/RFNLQJ��7DEOH�IRU�([DPSOH��

�5(9(18(*(5��$OO�YHUVLRQV

,QWHUVHFWLRQ

�5(9(18( � DOO�� DOO�)LOWHU�%

�5(9(18(*(5 � DOO� � DOO�)LOWHU�$

.H\�)LJXUH�&28175<�&86720(5�9(56,21,QIR&XEH��9(56,21��&86720(5��&28175<��5(9(18(��48$17,7<

�

� The best way to find out whether two selections lock each other is to make a table and try to find common records.

� The table has to have a column for each of the InfoProvider’s characteristics and a column for the key figures.

� Enter the characteristic attributes in the table and for each column try to find a value that is contained in every filter in this column. If you can find at least one such value for every column, the selections lock each other. If you cannot find a common value for at least one column then the selections do not lock each other.

� In this example, the filters lock each other.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-19

SAP AG 2006

/RFNLQJ��7DEOH�IRU�([DPSOH��

�5(9(18(*(5��1R�VKDUHG�YDOXHV

,QWHUVHFWLRQ

�5(9(18( � DOO��)LOWHU�%

�5(9(18(*(5 � DOO��)LOWHU�$

.H\�)LJXUH�&28175<�&86720(5�9(56,21,QIR&XEH��9(56,21��&86720(5��),6&<($5��$02817��48$17,7<

�

� The best way to find out whether two selections lock each other is to make a table and try to find common records.

� The table has to have a column for each of the InfoProvider’s characteristics and a column for the key figures.

� Enter the characteristic attributes in the table and for each column try to find a value that is contained in every filter in this column. If you can find at least one such value for every column, the selections lock each other. If you cannot find a common value for at least one column then the selections do not lock each other.

� In this example, the filters lock each other.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-20

SAP AG 2006

([HUFLVH�RQ�WKH�/RFNLQJ�&RQFHSW��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� &DUU\�RXW�DQ�H[HUFLVH�RQ�WKH�ORFNLQJ�FRQFHSW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-21

SAP AG 2006

´/RFNLQJ�6HUYLFHµ /RFN�0DQDJHPHQW��8QLW�2YHUYLHZ�'LDJUDP



�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-22

SAP AG 2006

´/RFNLQJ�6HUYLFHµ /RFN�0DQDJHPHQW��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�WR�XVH�WKH�³/RFNLQJ�6HUYLFH´�ORFN�

PDQDJHPHQW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-23

SAP AG 2006

´/RFNLQJ�6HUYLFHµ /RFN�0DQDJHPHQW��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�UHVSRQVLEOH�IRU�LPSOHPHQWLQJ�%,�LQWHJUDWHG�SODQQLQJ�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�/RFNLQJ�6HUYLFH�ORFN�PDQDJHPHQW�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-24

SAP AG 2006

´/RFNLQJ�6HUYLFHµ /RFN�0DQDJHPHQW��

$GPLQLVWUDWRU�WUDQVDFWLRQ�

563/6(

³/RFN´�WDE�SDJH

�

� Before a plan query or planning function is executed, the selected data is automatically locked.

� The lock is carried out for each real-time InfoProvider, as shown in the figure above.

� To view the locked selections, go to the “ Lock” tab page and enter the name of the InfoProvider that the planning function or planning query referred to.

� The DJJUHJDWLRQ�OHYHO, the UHDO�WLPH�,QIR3URYLGHU itself or a 0XOWL3URYLGHU can be used as the ,QIR3URYLGHU.

� Please note that authorization object S_RS_PLENQ has to be maintained for the display/change mode of transaction RSPLSE.

� Also note that the locking concept in BW integrated planning has not changed from the concept in BPS planning and that the “ Locking Service” lock management can be used for both BW integrated planning and for BPS planning. The original locking technology from BPS planning is no longer used.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-25

SAP AG 2006

/RFNLQJ�6HUYLFH�DQG�'LVSOD\LQJ�6HOHFWLRQV�WR�EH�/RFNHG�LQ�WKH�([DPSOH

7KH�/RFNLQJ�6HUYLFHV�ORFN�PDQDJHPHQW

��

�;��A��

�� B�� !#"%$*& '(' )!C"D$�& '(' )

+�,�-E/�1 2�3�5F,��4�G7H9��9��:;��<A��> ��A?��I�� =7B�A��4��@

)LOWHU�VHOHFWLRQ�± ZLWK�WHFKQLFDO�NH\V�±:LWK�UHVWULFWLRQ��%$6(B820 3&�67$7B&855 (85�30B3/$9(5 ��

:LWKRXW�UHVWULFWLRQ�&RXQWU\� �'B&28175<'LVWU��FKDQQHO� �'B',6B&+$1.H\�ILJXUHV�4X��LQ�EDVH�XQLWV �'B48$17B%�

J KL�M�NO.P�Q*RAM�S8T�UVQ WOO.X

'DWD�WR�EH�ORFNHG�GXH�WR�WKH�TXHU\�VHOHFWLRQ�

&KDUDFWHULVWLFV�ZLWKRXW�D�UHVWULFWLQJ�VHOHFWLRQ�DUH�QRW�OLVWHG�LQ�WKH�/RFNLQJ�6HUYLFH

&DXWLRQ�

�

� In the above illustration, the box containing the filter selections and the associated table describe the data selection that is to be locked from the example on the “ Selections to be Locked from the Plan Query Perspective” slide.

� On the left, you can see how the Locking Service displays the locked selections in the form of a report.

� All the individual selections are displayed. In addition to this, the key figure is included as a value for the technical InfoObject 1KYFNM.

� The lock entries are displayed for each InfoProvider, as you can see in the report above from the Locking Service.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-26

SAP AG 2006

´/RFNLQJ�6HUYLFHµ /RFN�0DQDJHPHQW�DQG�'LVSOD\LQJ�WKH�/RFNHG�6HOHFWLRQV

(QWHU�WKH�QDPH�RI�WKH�,QIR3URYLGHU

+HUH�ZH�VHH�WKH�VHOHFWLRQ�E\�³/RFNLQJ�6HUYLFH´��• 7KH�VLQJOH�YDOXH�LV�GLVSOD\HG�DVDQ�LQWHUYDO��ZLWK�LGHQWLFDO�IURP��WR�YDOXHV��

• &KDUDFWHULVWLFV�ZLWK�QR�UHVWULFWLRQ�DUH�QRW�GLVSOD\HG�

• &KDUDFWHULVWLFV�WKDW�ZHUH�QRWXVHG�DUH�QRW�GLVSOD\HG�

�

� The following slides give you an overview of the Locking Service, with the focus on the locked data and using the information from the example shown above.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-27

SAP AG 2006

7DEOH�RI�/RFN�(QWULHV

$GPLQLVWUDWRU�WUDQVDFWLRQ�60��GLVSOD\V�WKH�ORFN�HQWULHV�DQG�HQDEOHV�\RX�WR�GHOHWH�ORFN�HQWULHV�

([HFXWH�WUDQVDFWLRQ�60��ZLWK�WDEOH�563/6B6B/2&.

7KH�UHVXOW�VKRZV�ZKLFK�XVHUV�WKHUH�DUH�ORFN�HQWULHV�IRU�EXW�WKH�ORFNHG�VHOHFWLRQV�DUH�QRW�GLVSOD\HG�LQ�D�IRUPDW�WKDW�FDQ�EH�DQDO\]HG�

"ZY[& 5]\ 1Z\�2�^��8��:*�� :�7I�I+�� @��8�`_�5�:��aH��>b�� c _43 ' de& ' f�_hg*,�f�&.i*,�d�j.d�,�k*,�\�d�1b\*20_4\�lnm�,f�,.l%lo1Z\�2*fE_�\plom�,q' _ c�r f�, 5Fi�, 5]s )

�

� You can use transaction SM12 to display the lock entries and then delete them as well.

� The table name selected reduces the display of the lock entries to the locked transaction data.

� For more information, see SAP Note 816730.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-28

SAP AG 2006

,I�D�ORFN�PHVVDJH�RFFXUV��WKHUH�DUH�WZR�ZD\V�RI�ILQGLQJ�RXW�ZKLFK�LQWHUVHFWLRQV�DUH�DIIHFWHG��!�$QDO\]LQJ�&XVWRPL]LQJ�± DV�GHVFULEHG�SUHYLRXVO\��!�8VLQJ�WKH�DQDO\VLV�WRRO SURYLGHG�E\�WKH

/RFNLQJ�6HUYLFH

´/RFNLQJ�6HUYLFHµ /RFN�0DQDJHPHQW�DQG�/RFNLQJ�,QWHUVHFWLRQV

�

� The above figure describes the two basic options for displaying selections that lock each other.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-29

SAP AG 2006

³/RFNLQJ�&RQIOLFW´�WDE�SDJH

6\VWHP�GLVSOD\V�VHOHFWLRQV�OLQNHG�WR�WKH�ORFN

8VHU�UHFHLYHV�ORFN�PHVVDJH�LI�KH�RU�VKH�ZDQWV�WR�SODQ

/RFNHG�VHOHFWLRQV�WKDW�WKH�XVHU�UHTXHVWV 8VHU�LV�DOUHDG\�SODQQLQJ�DQG�

WULJJHUV�ORFN��+HUH�\RX�FDQ�VHH�WKH�ORFNHG�VHOHFWLRQ�

´/RFNLQJ�6HUYLFHµ /RFN�0DQDJHPHQW�DQG�'LVSOD\LQJ�/RFNHG�6HOHFWLRQV�IURP�7ZR�8VHUV

�

� The figure above shows which users lock each other and which selections are locked, as well as who triggered the lock and who is affected by it.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-30

SAP AG 2006

5HOHDVLQJ�/RFNHG�6HOHFWLRQV

7KH�SODQQHU�ZDQWV�WR�GHOHWH�KLV�RU�KHU�ORFN�HQWULHV�VR�WKDW�DQRWKHU�SODQQHU�FDQ�VWDUW�FRQWLQXH�SODQQLQJ�7KH�IROORZLQJ�RSWLRQV�DUH�DYDLODEOH�� &ORVLQJ�WKH�SODQQLQJ�DSSOLFDWLRQ� 6DYLQJ�WKH�GDWD�WR�UHOHDVH�DOO�WKH�ORFN�HQWULHV�WKDW�DUH�QRW�QHHGHG�IRU�

WKH�FXUUHQW�GLVSOD\�RI�WKH�SODQ�GDWD�

�

� The figure above shows how planners can unlock selections planned by them.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-31

SAP AG 2006

/RFNLQJ�5HOHYDQW�&KDUDFWHULVWLFV��

1RUPDOO\��D�VPDOO�TXDQWLW\�RI�FKDUDFWHULVWLFV�LV�HQRXJK�WR�SUHYHQW�WKH�SODQQHUV�VHOHFWLRQV�IURP�RYHUODSSLQJ�,I�\RX�RQO\�XVH�WKLV�NLQG�RI�FKDUDFWHULVWLF�LQ�WKH�/RFNLQJ�6HUYLFH��WKH�ORFN�WDEOHV�ZLOO�EHFRPH�VPDOOHU�DQG�OHVV�FRPSOH[�7KLV�LV�D�YHU\�VLPSOH�ZD\�RI�NHHSLQJ�WKH�ORFN�VHUYHUV�ORDG�VPDOO�

([DPSOH�,Q�FRVW�FHQWHU�SODQQLQJ��WKH�FKDUDFWHULVWLFV�³FRVW�FHQWHU´��³FRVW�HOHPHQW´��³YHUVLRQ´�DQG�³ILVFDO�\HDU´�DUH�XVHG��,I�VHYHUDO�XVHUV�DUH�SODQQLQJ�IRU�WKH�VDPH�\HDU�DQG�WKH�VDPH�FRVW�HOHPHQWV��WKH�FKDUDFWHULVWLFV�³FRVW�FHQWHU´�DQG�³YHUVLRQ´�DUH�HQRXJK�WR�HQVXUH WKDW�VHOHFWLRQV�IRU�GLIIHUHQW�XVHUV�GR�QRW�RYHUODS�)RU�WKLV�UHDVRQ��RQO\�WKHVH�WZR�FKDUDFWHULVWLFV��FRVW�FHQWHU�DQG YHUVLRQ��DUH�VWRUHG�DV�ORFN�FKDUDFWHULVWLFV��

�

� The above illustration shows how you can identify which characteristics in a planning scenario contribute to the locking. These characteristics should therefore be modeled without overlapping if you want planners to work in parallel.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-32

SAP AG 2006

/RFNLQJ�5HOHYDQW�&KDUDFWHULVWLFV��

7KH�FKDUDFWHULVWLFV�WKDW�DUH�QRW�WR�EH�XVHG�IRU�ORFNLQJ�UHPDLQ�RQ�WKH�OHIW�KDQG�VLGH��7KH\�DUH�KDQGOHG�DV�WKRXJK�VHOHFWHG�ZLWK�³ ´��7KH�ORFN�FKDUDFWHULVWLFV�DUH�WKHQ�VKRZQ�RQ�WKH�ULJKW�KDQG�VLGH�

³/RFNLQJ�&KDUDFWHULVWLFV´�WDE�SDJH

&KDQJLQJ�WKH�ORFN�PRGH��SRVVLEOH�LI�QR�ORFNV�H[LVW�IRU�WKH�,QIR3URYLGHU��ZKLFK�LV�QHFHVVDU\�IRU�UHDVRQV�RI�FRQVLVWHQF\��

�

� The illustration above shows how to enter the characteristics that were defined in the concept as lock characteristics into a list in the “ Locking Service” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-33

SAP AG 2006

,PSOHPHQWDWLRQ�2SWLRQV�IRU�WKH�/RFNLQJ�6HUYLFH

'HIDXOW�VHWWLQJ

IDVWIDVWPHGLXP3HUIRUPDQFH

PHGLXPVPDOOVPDOO$GPLQLVWUDWLRQ�HIIRUW

PHGLXP�WR�ODUJHVPDOO�WR�PHGLXPVPDOO�WR�PHGLXP6L]H�RI�LPSOHPHQWDWLRQ

/LYH�&DFKH6KDUHG�2EMHFWV�0HPRU\

6$3�(QTXHXH�6HUYHU

,PSOHPHQWDWLRQ�7\SH

:KHQ�VKRXOG�\RX�XVH�ZKLFK�LPSOHPHQWDWLRQ�RSWLRQ"

�

t Since selection tables need to be saved and managed centrally for all users and for the application servers, there are different implementation variants of the Locking Service.

t The following implementation options are available:

y SAP Enqueue Server

y Shared Objects Memory

y Live Cache. t

The default setting as shown in the table above offers high performance and needs only a limited administrative effort.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-34

SAP AG 2006

6HOHFWLQJ�DQ�,PSOHPHQWDWLRQ�2SWLRQ

&KDQJLQJ�WKH�ORFN�PRGH��SRVVLEOH�LI�QR�ORFNV�H[LVW�IRU�WKH�,QIR3URYLGHU��ZKLFK�LV�QHFHVVDU\�IRU�UHDVRQV�RI�FRQVLVWHQF\�

'HIDXOW�VHWWLQJ

³/RFN�7DEOH´�WDE SDJH

�

t The figure above shows how you can set your implementation option.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-35

SAP AG 2006

$SSHQGL[��)XUWKHU�&XVWRPL]LQJ�7UDQVDFWLRQV�DQG�7DEOH�1DPHV�IRU�WKH�7KUHH�,PSOHPHQWDWLRQ�2SWLRQV

$EDS�VKDUHGBREMHFWVBVL]HB0%

(QTXH�WDEOHBVL]H,PSRUWDQW�3URILOH�3DUDPHWHU

/&$B*8,'B675563/6B6B/2&.B6<1&

563/6B6B/2&.7DEOH�1DPH�u v#wnx wnyoz { |~}4�#�C� �]��woz wC��{ } �� n�

/&��6+0$�� w]��#��w ��6�~� �V� � � �� 60��+HOSIXO�

7UDQVDFWLRQV

/LYH�&DFKH6KDUHG�2EMHFWV�0HPRU\

6$3�(QTXHXH�6HUYHU

,PSOHPHQWDWLRQ�7\SH

�

t Here is a collection of useful tables and transactions related to the implementation types.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-36

SAP AG 2006

´/RFNLQJ�6HUYLFHµ /RFN�0DQDJHPHQW��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�WR�XVH�WKH�³/RFNLQJ�6HUYLFH´�ORFN�

PDQDJHPHQW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-37

SAP AG 2006

/RFNLQJ�&RQFHSW�IRU�7UDQVDFWLRQ�'DWD��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�JHQHUDO�FRQFHSW�RI�WKH�ORFN�ORJLF� &DUU\�RXW�DQ�H[HUFLVH�RQ�WKH�ORFNLQJ�FRQFHSW� 8QGHUVWDQG�KRZ�WR�XVH�WKH�³/RFNLQJ�6HUYLFH´�ORFN�

PDQDJHPHQW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-38

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-39

�([HUFLVHV�

8QLW�� /RFNLQJ�&RQFHSW�IRU�7UDQVDFWLRQ�'DWD�/HVVRQ�� ([HUFLVHV�RQ�WKH�/RFNLQJ�6HUYLFH�/RFN�&RQFHSW�


• Understand the locking concept for transaction data and reproduce it using an example

• Test the “ Locking Service” for checking locks

You are a member of the project team responsible for implementing BI integrated planning and want to familiarize yourself with the lock logic of transaction data. This is why you are interested in the concept of the lock logic.

You then want to find out about using the Locking Service to display locks on transaction data.

1-1 The InfoCube contains the following characteristics and key figures: �9(56,21��352'8&7��),6&3(5��$02817�DQG��48$17,7<.��The following paragraphs tell you which filter selections lead to locks and which don’t. 1-1-1 The following filter selections are available:

A) 0VERSION = 001, 0PRODUCT = 4711, 0AMOUNT

B) 0VERSION = 001, 0AMOUNT

Do the filter selections from A) and B) lock each other? If so, why? _______________________________________________________________ _______________________________________________________________

1-1-2 The following filter selections are available:

A) 0VERSION = 001-003, 0PRODUCT = 4711, 0AMOUNT B) 0VERSION = 004, 0AMOUNT Do the filter selections from A) and B) lock each other? If so, why? _______________________________________________________________ _______________________________________________________________

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-40


A) 0VERSION = 001-002, 0AMOUNT

B) 0VERSION = 001, 0QUANTITY Do the filter selections from A) and B) lock each other? If so, why? _________________________________________________________ _________________________________________________________


A) 0FISCPER = 001.2010, 0AMOUNT

B) 0VERSION = 4711, 0AMOUNT Do the filter selections from A) and B) lock each other? If so, why? _________________________________________________________ _________________________________________________________


A) 0VERSION = 001, 0FISCPER = 001.2010, 0AMOUNT

B) 0VERSION = 002, 0PRODUCT = 4711, 0AMOUNT Do the filter selections from A) and B) lock each other? If so, why? _________________________________________________________ _________________________________________________________

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-41

1-2 You now want to use the /RFNLQJ�6HUYLFH in order to have the system display the respective locked data.

1-2-1 You are in the initial screen after logging on to the system and all other sessions are closed. Navigate to lock management via transaction 60�� and select your XVHU�QDPH and client ��and execute the transaction. You should not find any locked selections in the next screen. If you do, you should close all open applications. This procedure ensures that you only analyze locked segments that occur due to doing the exercise.

1-2-2 Now navigate to the Locking Service, that is, the lock settings for planning, using transaction 563/6(� and select your aggregation level from the CFO’s quantity planning 6��B$/B��via the /RFNV�tab page and for the “ InfoProvider” field. Leave the “8VHU” field blank. Press the “5HIUHVK” pushbutton. There should be no locks here either.

1-2-3 First of all, test the GDWD�ORFNV�IRU�WKH�WHVW�GDWD�RI�WKH�LQSXW�WHPSODWH. For this purpose, open a VHFRQG�VHVVLRQ and navigate to the 3ODQQLQJ�0RGHOHU for InfoProvider 7%:��6�� Execute sequence 6��B6B�� for fiscal year ��IRU�DJJUHJDWLRQ�OHYHO�6��B$/B�� For this test screen, increase the already available quantity for the VDOHV�TXDQWLW\ key figure for company code ��by ��units of measure and for company code ��by �� unit of measure, without saving this plan data. Following that, execute transaction 563/6(�again in a second session and take a look at the /RFNV tab page there. In the InfoProvider field, you select aggregation level 6��B$/B��. Which selections are locked? Enter them in the table below:

Characteristic C.Value Int. C.Value Int.

0co_area

0comp_code

0copaslqtu

0currency

0fiscvarnt

0fiscyear

0version

1KYFNM

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-42

These locked segments correspond to the filter selections of filter 6��B)B��from the above sequence for aggregation level 6��B$/B��. Please note that compared to the /RFNV tab page, the /RFN�&RQIOLFW�tab page is a KLVWRULFDO�GLVSOD\�and only has display functionality. It shows which user last triggered a lock with his selections. This is not relevant in our scenario. In the Customizing phase, this tab page is an important tool for modeling selections without overlaps for the planners.

1-2-4 Now test the GDWD�ORFN�IRU�DQ�DGGLWLRQDOO\�H[HFXWHG�SODQQLQJ�IXQFWLRQ of Planning Modeler. For the CFO, planning function 6��B3)B�� and filter 6��B)B��had been created in aggregation level 6��B$/B�� in order to copy data from version A to B. The filter and the function are summarized in sequence 6��B6B��. First of all, take a quick look at the selections of filter 6��B)B��and then�H[HFXWH the VHTXHQFH�ZLWK�WUDFH�for fiscal year��, without saving the data.

1-2-5 Use the /RFNLQJ�6HUYLFH to analyze the segments that have been locked up to now and enter the newly added locked segments from the execution of the planning function into the table below.


0co_area

0comp_code

0copaslqtu

0currency

0fiscvarnt

0fiscyear

0version

1KYFNM

Once again, you can see that exactly the selections of filter 6��B)B��are locked!

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-43

1-2-6 Logon on to the training system using the XVHU�DQG�SDVVZRUG�RI�WKH�SHUVRQ�WR�WKH�OHIW�RI�\RXU�ZRUNVWDWLRQ�Dnd navigate to 3ODQQLQJ�0RGHOHU. There, select \RXU structures again, that is InfoProvider 7%:��6��then aggregation level 6��B$/B�� and then execute sequence 6��B6B��, that is, the input template of task 1-2-3 once again. Which message do you get when you execute it: _______________________________________________________________ Since you cannot see the selections that have been locked by your user and that have been requested by your neighbor’s user, you want to use the Locking Service to obtain this information. Navigate back to the screen window with the Locking Service (the session refers to your own user) and press the 5HIUHVK pushbutton on the /RFN�&RQIOLFW tab page. Get an overview of the display using the displayed connections. Now close the training system to which you had logged on using your neighbor’s user. In your own system, close Planning Modeler without saving so that you only have the screen window that you get after logging on to the system. Close all other sessions of your system, including the session that you used for the Locking Service.

1-2-7 You now want to take a closer look at the ORFNV on transaction data that are triggered in a TXHU\� Navigate to 4XHU\�'HVLJQHU� call up plan query 6��B$/B��B3ODQTXHU\B��B6$/0$1 in the Customizing interface. In the query, look at the chosen selections in all areas of the query and then execute the query for fiscal year �� In order to analyze the resulting lock entries, open the Locking Service again, this time for aggregation level 6��B$/B��. Which selections are displayed on the /RFNV�tab page? Enter them in the table below:


0co_area

0comp_code

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-44

0copaslqtu

0currency

0fiscvarnt

0fiscyear

0version

0matl_group

1KYFNM

1-2-8 Navigate back to the Customizing of the query and change the following settings: In the “&KDUDFWHULVWLFV�OLPLW” remove the characteristic value �� for the company code. 6DYH the query, and execute it. Now open the /RFNLQJ�6HUYLFH, and 5HIUHVK. What can you see with regard to the lock entries on the /RFNV�tab page? _______________________________________________________________ _______________________________________________________________Enter your observations in the following table:


0co_area

0comp_code

0copaslqtu

0currency

0fiscvarnt

0fiscyear

0version

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-45

0matl_group

1KYFNM

1-2-9 Now return to the Customizing of the query and include company code ��in�addition WR�entry�1000 in the “ Characteristic limits” again and, in the “'HIDXOW�9DOXHV” �area, select company code 1000 as the start value for opening the query. Then VDYH�again, H[HFXWH the TXHU\�and then 5HIUHVK the /RFNLQJ�6HUYLFH. Enter the selections in the following table again.


0co_area

0comp_code

0copaslqtu

0currency

0fiscvarnt

0fiscyear

0version

0matl_group

1KYFNM

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-46

What do you observe with regard to the lock entries this time? _______________________________________________________________ _______________________________________________________________ Now stay in the executed query and set the filter for the Company Code characteristic at runtime: 'HVHOHFW��DQG�VHOHFW�� Following that, 5HIUHVK the /RFNLQJ�6HUYLFH. What do you notice this time? _______________________________________________________________ _______________________________________________________________

1-2-10 Navigate back to the Customizing of the query and remove the characteristic “&RPSDQ\�FRGH” from the “&KDUDFWHULVWLF�OLPLWV” . The “'HIDXOW�YDOXHV” �area for this characteristic should therefore not be filled either. Hence, the “&RPSDQ\�FRGH” �characteristic is only contained in the “ URZV” of the query. 6DYH�again, H[HFXWH the TXHU\�and then 5HIUHVK the /RFNLQJ�6HUYLFH. This time you see that the Company Code characteristic (0comp_code) no longer appears in the list of lock entries. How is this to be interpreted? What is this lock called? _______________________________________________________________ _______________________________________________________________ _______________________________________________________________

1-2-11 If you now limit the filter to company code 1000 in the executed query, will this result in a change with regard to the locked selections? _______________________________________________________________ _______________________________________________________________

1-2-12 Now reset your settings to the initial situation by including the FRPSDQ\�FRGH with selections ��and �� in the “&KDUDFWHULVWLF�/LPLWV” �area and not making a selection for the company code in the “'HIDXOW�9DOXHV” �area. 6DYH your query settings.

1-2-13 Which FRQFOXVLRQV do you reach with regard to the ORFN�EHKDYLRU�for the executed TXHU\�and how should you generally conceptualize a plan query with regard to locks on the planner?

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-47

_______________________________________________________________ _______________________________________________________________ _______________________________________________________________ _________________________________________________________ Following that, close Query Designer and return to the initial screen after logging on to the system. Close the mode for the Locking Service as well.

1-2-14 For which purpose can you use the /RFN�&KDUDFWHULVWLFV tab page in the Locking Service? ____________________________________________________________ ____________________________________________________________ ____________________________________________________________

Please note that a test for locking selections is briefly demonstrated in the context of the planning function in the exercises for Bex Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-48

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-49

6ROXWLRQV�

8QLW�� /RFNLQJ�&RQFHSW�IRU�7UDQVDFWLRQ�'DWD�/HVVRQ�� ([HUFLVHV�RQ�WKH�/RFNLQJ�6HUYLFH�/RFN�&RQFHSW�

1-1 The InfoCube contains the following characteristics and key figures: �9(56,21��352'8&7��),6&3(5��$02817�DQG��48$17,7<.��The following paragraphs tell you which filter selections lead to locks and which don’ t. 1-1-1 The following filter selections are available:

A) 0VERSION = 001, 0PRODUCT = 4711, 0AMOUNT

B) 0VERSION = 001, 0AMOUNT Do the filter selections from A) and B) lock each other? If so, why? /RFN because version and key figure are identical and 4711 is a subset of * (everything). Hence, there is no empty intersection.


A) 0VERSION = 001-003, 0PRODUCT = 4711, 0AMOUNT

B) 0VERSION = 004, 0AMOUNT Do the filter selections from A) and B) lock each other? If so, why? 1R�ORFN because the versions differ and thus result in an empty intersection.


A) 0VERSION = 001-002, 0AMOUNT

B) 0VERSION = 001, 0QUANTITY Do the filter selections from A) and B) lock each other? If so, why? 1R�ORFN because the key figures differ and thus result in an empty intersection.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-50


A) 0FISCPER = 001.2010, 0AMOUNT

B) 0VERSION = 4711, 0AMOUNT Do the filter selections from A) and B) lock each other? If so, why? /RFN because they have the same key figure. Furthermore 001.2010 is a subset of * (everything) [0FISCPER] and 4711 is a subset of * (everything) [0PRODUCT]. Hence, there is no empty intersection.


A) 0VERSION = 001, 0FISCPER = 001.2010, 0AMOUNT

B) 0VERSION = 002, 0PRODUCT = 4711, 0AMOUNT Do the filter selections from A) and B) lock each other? If so, why? 1R�ORFN because the versions differ and thus result in an empty intersection.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-51

1-2 You now want to use the /RFNLQJ�6HUYLFH in order to have the system display the respective locked data.

1-2-1 You are in the initial screen after logging on to the system and all other sessions are closed. Navigate to lock management via transaction 60�� and select your XVHU�QDPH and client ��and execute the transaction. You should not find any locked selections in the next screen. If you do, you should close all open applications. This procedure ensures that you only analyze locked segments that occur due to doing the exercise.

1-2-2 Now navigate to the Locking Service, that is, the lock settings for planning, using transaction 563/6(� and select your aggregation level from the CFO’ s quantity planning 6��B$/B��via the /RFNV�tab page and for the “ InfoProvider” field. Leave the “8VHU” field blank. Press the “5HIUHVK” pushbutton. There should be no locks here either.

1-2-3 First of all, test the GDWD�ORFNV�IRU�WKH�WHVW�GDWD�RI�WKH�LQSXW�WHPSODWH. For this purpose, open a VHFRQG�VHVVLRQ and navigate to the 3ODQQLQJ�0RGHOHU for InfoProvider 7%:��6�� Execute the input template for aggregation level 6��B$/B��in sequence 6��B6B�� for fiscal year �� (When entire sequences are executed, the input templates are ignored as a step.) For this test screen, increase the already available quantity for the VDOHV�TXDQWLW\ key figure for company code ��by ��units of measure and for company code ��by �� unit of measure, without saving this plan data. Following that, execute transaction 563/6(�again in a second session and take a look at the /RFNV tab page there. In the InfoProvider field, you select aggregation level 6��B$/B��. Which selections are locked? Enter them in the table below:


0CO_AREA 1000 1000

0COMP_CODE 1000 1000

2000 2000

0COPASLQTU PC PC

0CURRENCY USD USD

0FISCVARNT K4 K4

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-52

0FISCYEAR 2010 2010

0VERSION A A

1KYFNM 0COPAMRGN1 0COPAMRGN1

0COPAREVEN 0COPAREVEN

0COPASLQTY 0COPASLQTY

These locked segments correspond to the filter selections of filter 6��B)B��from the above sequence for aggregation level 6��B$/B��. Please note that compared to the /RFNV tab page, the /RFN�&RQIOLFW�tab page is a KLVWRULFDO�GLVSOD\�and only has display functionality. It shows which user last triggered a lock with his selections. This is not relevant in our scenario. In the Customizing phase, this tab page is an important tool for modeling selections without overlaps for the planners.

1-2-4 Now test the GDWD�ORFN�IRU�DQ�DGGLWLRQDOO\�H[HFXWHG�SODQQLQJ�IXQFWLRQ of Planning Modeler. For the CFO, planning function 6��B3)B�� and filter 6��B)B��had been created in aggregation level 6��B$/B�� in order to copy data from version A to B. The filter and the function are summarized in sequence 6��B6B��. First of all, take a quick look at the selections of filter 6��B)B��and then�H[HFXWH the VHTXHQFH�ZLWK�WUDFH�for fiscal year��, without saving the data.

1-2-5 Use the /RFNLQJ�6HUYLFH to analyze the segments that have been locked up to now and enter the newly added locked segments from the execution of the planning function into the table below.


0CO_AREA 1000 1000


2000 2000

0COPASLQTU PC PC

0CURRENCY USD USD

0FISCVARNT K4 K4

0FISCYEAR 2010 2010

0VERSION B B




I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-53

Once again, you can see that exactly the selections of filter 6��B)B��are locked!

1-2-6 Logon on to the training system using the XVHU�DQG�SDVVZRUG�RI�WKH�SHUVRQ�WR�WKH�OHIW�RI�\RXU�ZRUNVWDWLRQ�Dnd navigate to 3ODQQLQJ�0RGHOHU. There, select \RXU structures again, that is InfoProvider 7%:��6��then aggregation level 6��B$/B�� and then execute sequence 6��B6B��, that is, the input template of task 1-2-3 once again. Which message do you get when you execute it: “ Data in InfoProvider TBW370S## is locked by user xxx” or “ Die Daten des InfoProviders TBW370S## sind durch Benutzer xxx” . (## is \RXU monitor number; xxx is \RXU user name.) Since you cannot see the selections that have been locked by your user and that have been requested by your neighbor’ s user, you want to use the Locking Service to obtain this information. Navigate back to the screen window with the Locking Service (the session refers to your own user) and press the 5HIUHVK pushbutton on the /RFN�&RQIOLFW tab page. Get an overview of the display using the displayed connections. Now close the training system to which you had logged on using your neighbor’ s user. In your own system, close Planning Modeler without saving so that you only have the screen window that you get after logging on to the system. Close all other sessions of your system, including the session that you used for the Locking Service.

1-2-7 You now want to take a closer look at the ORFNV on transaction data that are triggered in a TXHU\� Navigate to 4XHU\�'HVLJQHU� call up plan query 6��B$/B��B3ODQTXHU\B��B6$/0$1 in the Customizing interface. In the query, look at the chosen selections in all areas of the query and then execute the query for fiscal year ��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-54

In order to analyze the resulting lock entries, open the Locking Service again, this time for aggregation level 6��B$/B��. Which selections are displayed on the /RFNV�tab page? Enter them in the table below:


0CO_AREA 1000 1000


2000 2000

0COPASLQTU PC PC

0CURRENCY USD USD

0FISCVARNT K4 K4

0FISCYEAR 2010 2010

2011 2011

0MATL_GROUP <blank> (same as #)

<blank> (same as #)

JUC JUC

TWAT TWAT

WAT WAT

0VERSION B B




I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-55

1-2-8 Navigate back to the Customizing of the query and change the following settings: In the “&KDUDFWHULVWLFV�OLPLW” remove the characteristic value �� for the company code. 6DYH the query, and execute it. Now open the /RFNLQJ�6HUYLFH, and 5HIUHVK. What can you see with regard to the lock entries on the /RFNV�tab page? You can see that only company code 1000 is locked, which is selected in the characteristic limits. Enter your observations in the following table:


0CO_AREA 1000 1000


0COPASLQTU PC PC

0CURRENCY USD USD

0FISCVARNT K4 K4

0FISCYEAR 2010 2010

0VERSION 2011 2011

0MATL_GROUP <blank> (same as #) <blank> (same as #)

JUC JUC

TWAT TWAT

WAT WAT

B B




1-2-9 Now return to the Customizing of the query and include company code ��in�addition WR�entry�1000 in the “ Characteristic limits” again and, in the “'HIDXOW�9DOXHV” �area select company code 1000 as the start value for opening the query. Then VDYH�again, H[HFXWH the TXHU\�and then 5HIUHVK the /RFNLQJ�6HUYLFH.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-56

Enter the selections in the following table again.


0CO_AREA 1000 1000


2000 2000

0COPASLQTU PC PC

0CURRENCY USD USD

0FISCVARNT K4 K4

0FISCYEAR 2010 2010

2011 2011

0MATL_GROUP <blank> (same as #) <blank> (same as #)

JUC JUC

TWAT TWAT

WAT WAT

0VERSION B B




What do you observe with regard to the lock entries this time? Both company codes – 1000 and 2000 – are locked again. For queries the locks are thus triggered by the characteristic limits (static filters) and not by the default values (dynamic filters). Now stay in the executed query and set the filter for the Company Code characteristic at runtime: 'HVHOHFW��DQG�VHOHFW��Following that, 5HIUHVK the /RFNLQJ�6HUYLFH. What do you notice this time? No change in the lock table, if you change the value of the company code to 2000 at runtime. The reason is that the data range is locked and not the default value.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-57

1-2-10 Navigate back to the Customizing of the query and remove the characteristic “&RPSDQ\�FRGH” from the “&KDUDFWHULVWLF�OLPLWV” . The “'HIDXOW�YDOXHV” �area for this characteristic should therefore not be filled either. Hence, the “&RPSDQ\�FRGH” �characteristic is only contained in the “ URZV” of the query. 6DYH�again, H[HFXWH the TXHU\�and then 5HIUHVK the /RFNLQJ�6HUYLFH.

This time you see that the Company Code characteristic (0COMP_CODE) no longer appears in the list of lock entries. How is this to be interpreted?

The company code is no longer included in the lock list because the data range for the company code is no longer limited. Hence, all company codes are locked. What is this lock called? This lock on all values of a characteristic is called a generic lock. This is indicated with the * icon. Characteristics that are not limited are generally not displayed in the lock list.

1-2-11 If you now limit the filter to company code 1000 in the executed query, will this result in a change with regard to the locked selections? This will QRW result in a change to the locked selections, because the FKDUDFWHULVWLF�OLPLWV�that are relevant for the lock�KDYH�QRW�EHHQ�FKDQJHG�

1-2-12 Now reset your settings to the initial situation by including the FRPSDQ\�FRGH with selections ��and �� in the “&KDUDFWHULVWLF�/LPLWV” �area and not making a selection for the company code in the “'HIDXOW�9DOXHV” �area. 6DYH your query settings.

1-2-13 Which FRQFOXVLRQV do you reach with regard to the ORFN�EHKDYLRU�for the executed TXHU\�and how should you generally conceptualize a plan query with regard to locks on the planner? Locks use the data range, that is, the characteristic limits (“ static filters” ) and the characteristic values and key figures selected in the drilldown (e.g. using structures). This happens LUUHVSHFWLYH�RI�WKH�GHIDXOW�YDOXHV (“ dynamic filters” ). For FKDQJHV�PDGH�WR�WKH�VHOHFWLRQ of the filter DW�UXQWLPH (which corresponds to the default values) the entire data range is also locked. The default values are not relevant for locking, neither at runtime nor as default settings. To lock the least number of planners possible, you should thus keep the data range in the query as small as possible! Following that, close Query Designer and return to the initial screen after logging on to the system. Close the mode for the Locking Service as well.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 6-58

1-2-14 For which purpose can you use the /RFN�&KDUDFWHULVWLFV tab page in the Locking Service? For many applications it is not necessary to check DOO characteristics for locking. It can make sense to specify only FHUWDLQ characteristics as relevant for locking. The other characteristics are not used in the collision check then. The selection tables of lock management become correspondingly smaller and less complex. This can reduce the load on the lock server significantly. (If no characteristic is defined a relevant for locking, the whole InfoCube is locked.) In cost center planning you use, for example, the characteristics “ Cost center” , “ Cost type” , “ Version” and “ Fiscal year” . If many users plan for the same year and the same cost types, the characteristics “ Cost center” and “ Version” might suffice for avoiding overlaps in the selections of the different users. In that case, specify only these characteristics as relevant for locking.

Please note that a test for locking selections is briefly demonstrated in the context of the planning function in the exercises for Bex Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-1

SAP AG 2006

&RQWHQW�� 'HVLJQ�,WHPV�RI�WKH�%([�$QDO\]HU� 6SHFLDO�7RROV�RI�WKH�%([�$QDO\]HU�IRU�3ODQQLQJ

&UHDWLQJ�DQG�8VLQJ�DQ�([FHO�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�WKH�%([ $QDO\]HU

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-2

SAP AG 2006

&UHDWLQJ�DQG�8VLQJ�DQ�([FHO�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�WKH�%([ $QDO\]HU��7RSLF�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�8QGHUVWDQG�WKH�IXQGDPHQWDO�'HVLJQ�,WHPV�RI�WKH�%([ $QDO\]HU8VH�VSHFLDO�WRROV�RI�WKH�%([ $QDO\]HU�IRU�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-3

SAP AG 2006

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�%([ $QDO\]HU��DQG�WKHQ�ZLWK�WKH�VSHFLDO�VHWWLQJV�IRU�SODQQLQJ�LQ�D�ZRUNERRN�

&UHDWLQJ�DQG�8VLQJ�DQ�([FHO�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�WKH�%([$QDO\]HU��%XVLQHVV�6FHQDULR

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-4

SAP AG 2006

&UHDWLQJ�DQG�8VLQJ�DQ�([FHO�%DVHG�3ODQQLQJ�$SSOLFDWLRQZLWK�WKH�%([ $QDO\]HU��2YHUYLHZ�'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-5

SAP AG 2006

'HVLJQ�,WHPV�RI�WKH�%([ $QDO\]HU��8QLW�2YHUYLHZ�'LDJUDP

8QLW�WLWOH� /HVVRQ��'HVLJQ�,WHPV�RI�WKH�%([ $QDO\]HU� /HVVRQ��6SHFLDO�7RROV�RI�WKH�%([ $QDO\]HU�IRU�3ODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-6

SAP AG 2006

'HVLJQ�,WHPV�RI�WKH�%([ $QDO\]HU��7RSLF�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�8QGHUVWDQG�DQG�XVH�WKH�EDVLF�VHWWLQJV�RI�WKH�%([$QDO\]HU

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-7

SAP AG 2006

'HVLJQ�,WHPV�RI�WKH�%([ $QDO\]HU��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�JHW�DQ�RYHUYLHZ�RI�WKH�'HVLJQ�,WHPV�RI�WKH�%([$QDO\]HU�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-8

SAP AG 2006

3ODQQLQJ�$SSOLFDWLRQV

�

� 3ODQQLQJ�DSSOLFDWLRQV are BI applications based on a planning model. In a planning application, the power user usually links the objects of the planning model into an interactive application so that the actual user can enter and change data manually and automatically.

� 2EMHFWV�RI�WKH�SODQQLQJ�PRGHO are

Data-carrying InfoProviders

Aggregation levels as InfoProviders that provide specific summarizations of data for entering and changing data

Input-ready queries that enable manual entries on the underlying aggregation level

Planning functions that enable automatic changing of the data on the aggregation levels and thus model parts of the data flow

Planning sequences �

For the creation of planning scenarios, the tools you know from reporting scenarios are available:

For Excel-based planning applications of the %([�$QDO\]HU�For Web-based planning applications of the %([�:HE�$SSOLFDWLRQ�'HVLJQHU�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-9

SAP AG 2006

'HVLJQ�,WHPV�LQ�WKH�%H[ $QDO\]HU

�� "!#�$��%�&��'%()��

�� *�,+�� -��.�,��/*�$��0'1�� 2��,+��3�

4�� .� ��,+'� ��5� �� +�6�.�� $��7��8�� $� �.� ��7 ��1,��,�-9��.��7�.��.&�� #��:1"��6�� ;��*��.��7�7��6<�� ;��*�#��4�� '��/��+�6��.�,�� $��

4�� .� ��,+'� ��5� ��6��$��7'� �� $��.��7 ��.� �$�� 7 ��3��1��,�-9�.��7��.��.&.� ��-�$1#��6�� ;�� .��7=7-��6�� ;��*� ��-�4�� '��/.6��$��7:� �� $�,�>:��.&�� :1"�� #/�� *�.�:&, ��.��/.��7:� �?&.1��$�@:��7$� �A&�1,�*��:�#�:��:1-�>:��.&�� :1"�� #/�� *�.�:&, ��.��/.��6��6-%�&��+B ��6�%�&-��+��:�3�:1-�

>:��.&�� :1"�� #/�� *�.�:&, ��.��/.��7$��:��7��!��&��-+��*�'��7��! � &-��+

C)� � �-!D� -�E1)�F��+-��6�1,�*�#� ��.� /�G�7-��/�� 7�6��.��.��7��:�)�5��=� ��1�� H�1,�*��:�

4.� �� .� �<��6�1-�I�3�.�,�5� ��6�� ;�� /�� *�.� �4�� '��/-��#/�� *�.�3�

J:��;�� 7.��6�6,��#�� 6��.��6��.�� ,�5� 6,� �.��7 ��F1�6,�51�� =� �"��0$1�.�3�5��$6��&��1��7 /*�$�-��;�� 5� �:�#�.��7��.��.� ��.� �K:�;.� �� :�#�.��

L ��-!D��3��1-� ��-/'��0$1�.� �M2N�� .��.� �� "�*�.&�� .� ��:�� $�O �*�-�P/��:�$��;�� .�� :�#�.��7�Q#4�CDJ /81-��6,�� $�,�

C"��.� �� .&�� 0HDQLQJ'HVFULSWLRQ'HVLJQ�,WHP

'HVLJQ�0RGH �

� The BEx Analzer is used to FUHDWH�D�SODQQLQJ�DSSOLFDWLRQ. A release should first be entered by means of ([WUDV��!�0DFUR��!�6HFXULW\. On the 5HOLDEOH�6RXUFHV tab page, you set the “7UXVW�DFFHVV�WR�9LVXDO�%DVLF�SURMHFW” flag.

� Then you create a QHZ�ZRUNERRN. If headings are necessary, you create them using Excel tools in the desired cell of the worksheet.

� The actual design of the workbook is performed in the 'HVLJQ�0RGH, whose system icons are represented in the upper illustration, and by means of which you go to the 6$3�/RJRQ dialog box and can logon to the desired BI server.

� The worksheet is designed by means of 'HVLJQ�,WHPV. �

'HVLJQ�,WHPV are objects that call data from DataProviders and represent it in worksheets of the BEx Analyzer. You can also navigate with most Design Items.

� Eleven Design Items are available, which you can use for the interface design of your queries, and which are represented in the above illustration.

� In the following, the most important Design Items are described, with the most important settings.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-10

SAP AG 2006

'HVLJQ�,WHP�$QDO\VLV�7DEOH��

� ,I�WKH�IODJ�LV�QRW�VHOHFWHG��WKHQ�WKH�FXUUHQWO\�H[HFXWHG�QDYLJDWLRQ�VWHSV�DUH�DOZD\V�VDYHG� 6HOHFWLQJ�WKH�IODJ�DOZD\V�UHVHWV�WKH�QDYLJDWLRQWR�WKH�RULJLQDO�VHWWLQJV

�

� The DQDO\VLV�WDEOH is the Design Item that provides the central analysis functions in the BEx Analyzer. It displays the results of a query in a table in which you can navigate and execute OLAP functions, and it allows you to enter plan data manually.

� You configure the properties of the analysis table on three different tab pages in the Properties of the Analysis Table dialog window

*HQHUDO – here you can configure DataProviders, the cell area, and the behavior options.

6L]H– here you can configure whether the table display should be clipped out or scrolled.

/LQNHG�FKDUWV – enables you to link diagrams from Microsoft Excel with the analysis table. �

If you have selected a Design Item analysis table, then you should choose the “&UHDWH�'DWD3URYLGHU” dialog window and select Query or Plan Query.

� If you are working in the formula mode and want to display the data without having to set up a connection to the server, you can select “'LVSOD\�UHVXOW�RIIOLQH”.

� You use the “5HIHUHQFH�YLHZ” selection if you want to automatically recall the original navigation status that was saved in the query or query view on the server for this Design Item every time you open the workbook. If this checkbox is not selected, then the current navigation status is saved as it is displayed in the BEx Analyzer, after you have navigated the view and therefore changed it, when you save the workbook.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-11

SAP AG 2006


R�S�T S�U�V:W?X:T W'Y?ZE[.S'\�]

^ Y=U�W�_.SA`�aNb$S�_�S�T S'U�V5c `dY'eX$\FS�f�S'Y�VEW'Y.W�T ]._$c _=W:Y.bY.W�f'c g'W.V�c `:Yhc Y�V8i�S=ZN[.S'\�]

j c _$X$T W�]?c U�ÈY._�aIÈ\b'S�U'\FS�W�_'c3Y'g?W'Y�bc Y�U.\FS�W�_:c3Y.gk_�`N\�V5c Y�gh`'aU.i.W$\FW.U�V�S$\5c _�V�c U�_kW�Y�bml�S�]a5c gE[$\IS�_?c3YAWA\FS:X�`N\�V

n�Y$T ]AbEc _$X$T W�]oc U.`NY�_�VIòS�p:X.W:Y.b`N\NU-ÈT T W$X._�S�Woi$c S�\FW'\IU.i.]oc YkW\�S�X�`N\�V�q

rDS�T T _AW�\FSk\IS'X$T W.U�S'bhs.]t p�U-S'T�aFÈ\8u?[ET W�_'q�vPU�S�T TU�W$Y?s.S�a�`:\8u=W�VFVIS�bwc3Y=W'Y.]x W�]=b'S�_$c \FS.b

- y `'f�S�W$Y.W'T ]�_'c _VIW�s$T Sz v"b'W'X�V:W�Y�W�T ]�_$c _=V�W$s$T SV�À_$c {�S | S-aFS'\FS�Y'U�S V�`h},W�\FS.W�~�q t p�S'U.[�VFS�bW�Y.W'T ]-_'c _=V�W�sNT Sks.S�gEc Y�_ x c V�i=V�i�SU-ÈT [:ukY?b$S�a�c3Y�S�bwc3Y�V5i'S �"��a5c S'T bo`NY

V�i.S�a�W�\�T S-a�V:�IÈ\EW-V$V8i.S�f�S$\�]AVF`NX'��eW�b��[._-V*_=VF`?V8i.SA\FS._'[:T V�_=VI`kV8i�S?\5c gNi�VE�I`:\b$` x Y x W'\Ib'_.��e.c Y=`N\Ib:S'\:VF`hbNc _$X$T W�] V8i�SS�Y�V5c \FS=U.ÈY�V�S:Y�V

j c _'X$T W�]-_o\5c gEi-VdW�Y'bmT S-a�Vd�F[$XEX.S$\$W'Y$bT ` x S�\I�:U-`$È\�bEc Y$W�VFS�_AV5i.W-VEW'\FS=U-`�Y�a5c gd[$\FS.bc Y=V�i.S��)��a5c S�T b:e�W�_ x S$T T�W-_�_�U.\I`NT3T-s.W'\�_x c V�i x i$c U'i�]�È[kU�W$Y�_�U�\5ÈT T�\5c gNi.V:W'Y$bT S�aFVE�F[EXAW�Y$bob:` x Y�� x c V�i$c Y�V5i'Sk\FS-_'[$T V�_rDS�T T x c b�V5ioc YkW'Y.W�T ]._$c _�V�W�s:T SW�b��8[�_.V*_�VI`?V�i.S�_�U.ÈX�SA`�a:V5i.S

U.ÈY�VFS'Y�V8q�v)b��[�_�V8u�S$Y�V$V5ùoc Y$c ukW�T�_'c {Soc YkÈ\�b'S'\:VF`bEc _$X$T W�]=V5i.S=S$Y-V8c \FS?U-`NT [EuoYU.ÈY�VFS'Y�V

�

� Please note that it is not only possible to change the size and position of an analysis table by means of the “$UHD” field, but also by means of Drag&Drop from the border of the analysis table. To move a Design Item to another worksheet, you put a prefix with the correct syntax before the values to indicate the sheet. For example, to move a Design Item from Sheet1 to Sheet2, you enter a value such as Sheet2!$E$5:$G$6.

� If you have switched from the design mode to the analysis mode and are filling the Design Items with results, the Design Items usually need more space than when they were originally added. In this case, the top left coordinate is fixed and the bottom right coordinate adjusts DXWRPDWLFDOO\ to the data returned.

� On the 6L]H tab page, when you set the clip characteristic to &OLS, depending on whether you selected “ Clip horizontally or vertically” , the area setting still remains as it was and the results outside the area are clipped out or not displayed!

� “8VH�IRUPXODV” on the *HQHUDO tab page is used to replace every cell in the analysis table with a Microsoft Excel formula. Cells can thus be formatted in any way desired. This property is only possible for queries with a structure in the rows, a structure in the columns, and if applicable, in all other dimensions in the free characteristics.

� “(QDEOH�FHOO�SURWHFWLRQ” locks all cells that are not defined as input-ready in the plan query. This property is mainly used in connection with planning functions, and it prevents you from entering data where it does not make sense.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-12

SAP AG 2006


� c Y:l bNc W�gN\FW�u=_Aa�\I`Nu y c U.\5`�_.`'aFV t p$U�S'T�VFÀV�i.S�W�Y�W'T ]-_$c _=V�W$s$T S$e�_.òV�i.W-VV�i.S=bNc W�gE\FW'u=_�W'T x W�]�_?\FS$X$\FS�_�S$Y�V$V�i$SA\FS�_'[ET V�_A`�aEV�i.SkZE[.S�\I]'q� i.SAY$W.uAS=`�aNW=bEc W.gN\FW$u�c _kbEc _'X:T W�].S.bwc3Y�V8i�So��'�:�E��F�-�o�-�$�-�� ?T c _-V8qRNS�V'V8i.S�a5T W.gms.S-_'c b'S�V5i�S=bNc W�gE\FW$uA�3_��dc a$].`�[ x W$Y�V$VI`hT c3Y:l�c V��3V5i�S�u�V�ÀV8i�SW�Y.W'T ]-_'c _�VFW�sET S'q� i.S'Y=]�`N[oT c3Y$l WAbEc W.gN\FW�u�V5ÀW�VIW's$T S.e-V�i.SkbEc W�gE\IW'u�c _kW�[�V5`:uAW�V�c U-W$T T ][$X�b�W�VFS.b x c V�i=V8i.S=U-S'T T�W�\FS�W�_kW'Y�bAf'W�T [.S._?c3Y�V�i�S�VIW�s$T S'e�S�f�S$Yoc a$V�i.S�_'c {�S`�a$V�i�S�V�W's$T S�W'Y'bkV�i�S=f.W�T ['S-_?c VdU�`NY.V�W'c Y�_kU'i.W�Y'g'S x i.S'Y=].`N[?Y.W�f:c g$W�VIS'q

�

� “$FFHSW�IRUPDWWLQJ” : If this flag has been deselected, the formatting display, including the symbols and background color, is switched off. The display of formatting in the navigation can be very time-consuming. You can therefore switch this off for performance reasons.

� “$FWLYDWH�QDYLJDWLRQ” . If this flag is deselected, the context menu and the drag&drop function are deactivated in the analysis mode. A similar option is provided in the navigation area.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-13

SAP AG 2006

'HVLJQ�,WHP�1DYLJDWLRQ�$UHD��

��w� �5�N�h�� o��$¡?¢��3£ ��¡N¤d¥N¤�¡$¥h¦§� ¨d©N£ ¥�ªw�E¢��'¡« $¥.¬d� E¥�� w¥E¤5¡'¥$®'��¥N¯'¨d�3 Eh��'¡��N�3¤8¦«�'��£�¯E°± m�:¢N��'¡« '¥�¬d� E¥��8� �� h¥N¤5¡�¥��±²:¡o¦�� ¨d©E£ ¥$ª$¡�¦´³

µ � °¶¡N .¨�� § $¨h�N¢E�·�:¡m¤8�'�k¨�¸��$�§£3¯$°¹ '¨.¸�¢·¤8¡'¡�E�$¥E¤5¥:��I¡N¤·� ¨$�·� �.¨º�3 o�·��¡w�E¯N¤�¤I¡� ��´ :¥�¬N� N¥.�� ¨'��¥.��¯'ö�N¢N��'¡o¥d �¥N£ ª�¨§� ¨w�I¥E²d£ ¡o¥E¤5¡w¦§� ¨�©E£ ¥�ª$¡�¦¹�3 �·�'¡« $¥�¬E� E¥.�·� �§ w¥N¤I¡'¥E³

�

� You configure the properties for the navigation area on four different tab pages in the dialog window 3URSHUWLHV�RI�WKH�1DYLJDWLRQ�$UHD��*HQHUDO�

Here you can configure DataProviders, the cell area, and options for the AutoFit.

'LPHQVLRQV�Here you can select the dimensions that you want to display in the navigation area.

'LVSOD\�VHWWLQJV�Enables you to make various settings that influence the display of the navigation area.

6L]H�Here you can configure whether the display of the navigation area should be clipped out or scrolled.

� On the 'LPHQVLRQV tab page, the “$YDLODEOH�GLPHQVLRQV” are automatically selected on the left side. These are all the characteristics that were selected in the underlying query that was created by means of the Query Designer, either in the drilldown or in the characteristic restrictions or default values. By default, all dimensions are displayed.

� If you select the DYDLODEOH�GLPHQVLRQV�LQWR�WKH�VHOHFWHG�GLPHQVLRQV, you specify which dimensions will be displayed in the navigation area.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-14

SAP AG 2006

'HVLJQ�,WHP�1DYLJDWLRQ�$UHD��

'LPHQVLRQV

» �'¡o¨��¥d $¦E¥E¤�¦«¦§� ¨d©E£ ¥$ªo�N¢d��:¡h¼�¦d¡�¢F¥�¯N£ �d¬:¥E£3¯$¡'¨$½��N¢��'¡w¾§¯$¡:¤�ªh¢��3£ �5¡N¤D�3 ?�·�N� ö��3¤5¦¶�$�§£3¯$°¿ o�N¢d��¡ '¥.¬d� E¥��·� �§ º²E£ ��:À'³Á ¢E�·�:¡k¨$¡N£ ¡'�.�·� �� $ö¥N¤5¡h�E�'¥d ::¡:¦m¥'�D¤·¯N '�·� °¶¡m�3 h��¡ '¥.¬d� E¥��·� �§ º²E£ ��:À.®��'¡?¬$¥N£3¯:¡�¨w�d��¥d :E¡N³

�D¡N£ ¡$�-�� § m�:¢��'¡m¼��:�:¥N¤�¥$�.�5¡E¤·� ¨��·� �m¤�¡�¨$��¤·� �.�8� �´ �¨:½ �·�$¥��¥E º²�¡h¦´� ¨d©N£ ¥�ª'¡:¦m¥d :¦º¤�¡:°º�:¬$¡:¦m¥'��¤�¯N $�·� °w¡¶�* k��:¡�·�E�3¤5¦º�'�§£�¯$°Â m�:¢N��'¡¶ $¥�¬N� N¥.�·� �� º²N£ ��EÀ�³

µ � ¨d©d£ ¥:ªk��'¡h¦N¥��I¥$Ë©$¥:�.¡h�N¢N��¡¼��E�$¥E¤5¥:��I¡N¤·� ¨'�·� �m¤8¡.¨'��¤·� �.�·� �� '¨'½�h� �·�o¨$¡N£ ¡:�.�·� �§ h�´©'�8� �§

�´¡N£ ¡'�.�� § $¨m¤5¡'¦´¯:�.¡w¦:¥$�I¥o¾´¯$¥d ��·� �Iªº�3 h¥d '¥N£ ª'¨�� ö�5¥N²N£ ¡d³

�

� The above illustration shows how the navigation block looks in an executed query, and explains the possible settings by the end user.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-15

SAP AG 2006

8VLQJ�WKH�1DYLJDWLRQ�%ORFN�LQ�WKH�([HFXWHG�4XHU\

» ¤5¥E '¨$¢F¡N¤§¦´� °m¡N $¨d� �´ .ö�8�¶�$�§£3¯:°Â w¦§¤��3£�£ ¦N�$�m E³�´¡N£ ¡'�.�5¡$¦«�E��¥N¤�¥:�.��¡E¤�� ¨'�8� �?¬:¥:£*¯'¡�¨h¥N¤5¡¦�� ¨d©N£ ¥�ª$¡:¦±²:¡E£ �'�Ã¡'¥$�N�o�N��$¡E¤·³

µ � °m¡N .¨§� �§ «� ¨h�$�� $�I¥N�3 '¡$¦±�� w�$�§£3¯$°¿ ¦�¤��3£ £ ¦��'�w w¥: E¦±� ¨h�5�Â²�¡¶¤5¡$°º�E¬'¡:¦§³

» ¤5¥E '¨$¢F¡N¤§¦´� °m¡N $¨d� �´ .ö�8�¶�$�§£3¯:°Â w¦§¤��3£�£ ¦N�$�m E³�´¡N£ ¡'�.�5¡$¦«�E��¥N¤�¥:�.��¡E¤�� ¨'�8� �?¬:¥:£*¯'¡�¨h¥N¤5¡¦�� ¨d©N£ ¥�ª$¡:¦± :¡�Ä$��I�m¡$¥$�E�w�E��¡N¤·³µ � °m¡N .¨§� �§ «� ¨h�$�� $�I¥N�3 '¡$¦±�� w�$�§£3¯$°¿ ¦�¤��3£ £ ¦��'�w w¥: E¦±� ¨h�5�Â²�¡¶¤5¡$°º�E¬'¡:¦§³

"

"

Å £ �F¡N¤· :¥��8� ¬:¡N£ ª$®�ª:��¯m��¥d ¯�¨$¡'¦ µ ¤5¥'�Æ µ ¤8��©o�I�¹©N¯d£�£¦§� °m¡N $Ë� �´ �ö¢�¤��d°Ç��'¡ '¥�¬N� E¥��8� �� «²d£ ��EÀk�* ��$¡?�:��£3¯E°¹ h¦�¤��3£3£ ¦d�:�o �³

�

� The above illustration analyzes the drilldown options of the navigation block and its effect on the analysis table.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-16

SAP AG 2006

'HVLJQ�,WHP�/LVW�RI�WKH�)LOWHUV��

/LVW�RI�WKH�ILOWHUV

�

� The Design Item /LVW�RI�WKH�)LOWHUV shows a list of all active filters for one or more dimensions. �

Because the Design Item 1DYLJDWLRQ�$UHD also displays current active filters, this item is useful if you have suppressed the filter display in the navigation area (by removing the Display Filter Texts flag in the properties of the navigation area), or if you do not want to display a navigation area in your workbook, but rather the current status of filters.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-17

SAP AG 2006

'HVLJQ�,WHP�/LVW�RI�WKH�)LOWHUV��

r"i.W'Y'g'S-_ou�W�b'SAW�T _�`?W$X$X:T ]�V�`kV5i�SbEc _'X:T W�]oc Y=V5i�SkY�W�f'c g'W.V�c ÈYos$T ÈU.l$È

É c S$T b'_=VF`ws'Skc Y�U.T3['b'S.bwc YV5i.S=U�`NT [$u?Y?bE\5c T T b$` x Y

É c S$T b�_oY�`'V:V�òs'Sc Y�U'T [�b$S.bwc3Y�V8i.SU-ÈT [$u?Y?bE\8c T T b$` x Y

�

� The Design Item /LVW�RI�WKH�)LOWHUV shows a list of all active filters for one or more dimensions. �

Because the Design Item 1DYLJDWLRQ�$UHD also displays current active filters, this item is useful if you have suppressed the filter display in the navigation area (by removing the Display Filter Texts flag in the properties of the navigation area), or if you do not want to display a navigation area in your workbook, but rather the current status of filters.

� If the list of the filters and the filter texts are maintained in the navigation block, both of course display the same selections, as the above illustration shows.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-18

SAP AG 2006

'HVLJQ�,WHP�%XWWRQ��

Á '¦E¡�Ä�Ê » �$¡?¨$¡$¾§¯$¡N :��¡m�* k�w�N� �E�o��:¡o�'��°º°m¥N :¦±� ö�5�Â²$¡o¡.Ä:¡$�E¯$�F¡$¦§³» �$¡?¨'��¥E¤��.��°«°«¥N $¦¹²�¡E��3 $¨k�h� ��hËE³Ì �´¯h�'¥E w�$�� $¢�� ´¯N¤�¡?¥'¨m°m¥N $ªh�$��°«°¶¥E E¦$¨h¥�¨wª'�´¯¶£3�3À�¡E³

Í �$¬'¡h¥N $¥N£ ª'¨N� ¨��¥N²N£ ¡w�§¤¥$¦.Î�¯$¨'�N¨d� Ï-¡

Ð ¥:°w¡h�N¢N��'¡²N¯'��8��

Ñ ¥N£3¯'¡�Ê » �:¡k¬$¥d£3¯'¡w�:¢��8�$¡w��°«°«¥N $¦Ð ¥:°¶¡dÊ » �$¡« '¥:°«¡o�:¢��$¡h�'��°º°m¥N E¦

�

� You use the Design Item %XWWRQ to define a particular command or a series of commands. �

In the syntax, which is based on the Web API reference, all the DataProvider-specific commands and parameters are supported, apart from functions for the export to Microsoft Excel.

� When you are defining a button individually, you have the same options as in the manual navigation in a query by means of the context menu. When you select the button, you execute the command or commands, and the query results are updated accordingly in the analysis table.

� In the “&RPPDQG�DUHD” field, you have the option of creating a three-columned cell area in the worksheet to contain the command parameters. These cells contain the same parameters (1DPH, ,QGH[ and 9DOXH) as the VWDWLF�SDUDPHWHUV (see below), but LQ�WKH�ZRUNERRN�WKH\�FDQ�EH�YDULDEOH�DQG�FDQ�FKDQJH�GXULQJ�WKH�QDYLJDWLRQ�RQ�WKH�EDVLV�RI�TXHU\�UHVXOWV�RU�D�YDOXH�WKDW�\RX�HQWHU�PDQXDOO\��

� When you select the button to execute a command, all the VWDWLF�SDUDPHWHUV are evaluated first, then all the parameters in the &RPPDQG�DUHD are added.

� In the “ 6WDWLF�SDUDPHWHUV” area, you configure the command(s) to be executed in order to send name-value pairs to the server.

� A command can consist of multiple name-value pairs; you configure one for each row in the table. All the DataProvider-specific commands in the Web API reference are supported (apart from functions for the export to Microsfot Excel).

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-19

SAP AG 2006

'HVLJQ�,WHP�%XWWRQ��

�

� Buttons can be useful for SODQQLQJ�IXQFWLRQV that are not executed in connection with a DataProvider, but rather in a workbook.

� Example:

In a revaluation scenario, you have created a planning function in the backend in which you have an increase, and in which your calculations increase by 1%. You can add a button to the worksheet to add this planning function.

� Although planning functions are modeled in the backend, they can have variables that you can also supply in the worksheet by means of the &RPPDQG�DUHD field.

� In the next lesson, this Design Item is dealt with in more detail with regard to planning. �

Please note that the above list does not contain all the possible names of the static parameters.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-20

SAP AG 2006

'HVLJQ�,WHP�'URSGRZQ�%R[��

�

� Use the Design Item 'URSGRZQ�ER[ to easily filter a selected dimension. �

Because you also have a filter function in the navigation area, you usually do not use a navigation area in the same worksheet as the Design Item “ Dropdown box” .

� For example, you use the Design Item “ Dropdown box” if you are not providing the entire navigation scope of the navigation area, but only want to set filters in a convenient way.

� In the properties of the dropdown box, you configure the values for the dimensions that are to appear in the dropdown list. If you then select a value from the dropdown box in the analysis mode, the dimension is filtered on the basis of your selection, and the query results are updated accordingly in the analysis table.

� The Design Items &KHFNER[�JURXS�and 5DGLR�EXWWRQ�JURXS provide similar functions, with the exception that the Design Item &KHFNER[�JURXS�enables you to select PXOWLSOH�ILOWHU�YDOXHV�DW�WKH�VDPH�WLPH.

� If you are working with the 5DGLR�EXWWRQ�JURXS, every value appears in the analysis mode beside a radio button in a group of radio buttons. If you then select a value from the radio buttons in the analysis mode, the dimension is filtered on the basis of your selection, and the query results are updated accordingly in the analysis table.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-21

SAP AG 2006

'HVLJQ�,WHP�'URSGRZQ�%R[��

6RXUFH�'DWD3URYLGHU

7DUJHW�'DWD3URYLGHU

�

� The ³UHDG�PRGH´ on the Dimensions tab page defines the method with which the list of filter values is called.

� 3RVWHG�YDOXHV�4��

Executes SELECT on the fact table in order to list the filter values that are currently returning data. Values that would return no results when filtered are not displayed in the list. This calculation can be very time-consuming, but it only supplies usable values to the list.

� 'LPHQVLRQ�WDEOH��'��

Performs SELECT on the dimension table in order to call the list of filter values. This calculation is less time-consuming that 3RVWHG�YDOXHV. The probability that it will return values is higher than with 0DVWHU�GDWD�WDEOH.

� 0DVWHU�GDWD�WDEOH��0��

Returns all members of the selected dimension that are displayed in the master data table. Because InfoCubes cannot be filled very much, this provides many selections that would not supply any results when filtered (1R�XVDEOH�GDWD�IRXQG), but the logic is simple, and therefore the performance is optimal.

� In the next lesson, this Design Item is also dealt with in more detail with regard to planning.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-22

SAP AG 2006

&RQGLWLRQV�DQG�'HVLJQ�,WHP�/LVW�RI�WKH�([FHSWLRQV�

4XHU\�'HVLJQHU

�

� You can formulate conditions for efficient GDWD�DQDO\VLV. The conditions themselves are created in the Query Designer and can be used in the BEx Analyzer. In this case, WKH�GDWD�UHFRUGV�QRW�UHOHYDQW�DFFRUGLQJ�WR�WKH�FRQGLWLRQ�DUH�KLGGHQ�

� You can define multiple conditions for a query. Conditions are evaluated independently of each other. Thus, the result set is independent of the evaluation sequence. The result is the intersection of the individual conditions, and multiple conditions are logically linked with AND. A characteristic value is only displayed if it fulfills all (active) conditions of the query.

� You can use FRQGLWLRQV to restrict the view of the data of a query by means of threshold values and ranked lists.

� 7KUHVKROG�YDOXHV� An entry is not displayed if its reference value is above or below a specific threshold value.

� The following UDQNHG�OLVWV are possible:

7RS�1��%RWWRP�1� The ranked list is based on a specific number.

7RS�3HUFHQWDJH��%RWWRP�3HUFHQWDJH� The ranked list is based on a specific percentage rate.

7RS�7RWDO��%RWWRP�7RWDO� The ranked list is based on a specific total value. �

The Design Item /LVW�RI�FRQGLWLRQV contains all the conditions that were defined in the Query Designer and allows you to activate or deactivate the conditions by means of the contex menu or a symbol.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-23

SAP AG 2006

([FHSWLRQV�DQG�'HVLJQ�,WHP�/LVW�RI�WKH�([FHSWLRQV�

�

� ([FHSWLRQV can be defined in the Query Designer. They are also used for the analysis in reporting. �

Exceptions are used to detect deviations from an expected value at a first glance. The deviations are displayed either in color or with symbols.

� The Design Item /LVW�RI�([FHSWLRQV within the BEx Analyzer contains all the exceptions defined in the query and allows you to activate or deactivate them by means of the context menu or a symbol.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-24

SAP AG 2006

'HVLJQ�,WHP�7H[W

³)L[HU´ ILOWHU�LV�GLVSOD\HG

�

� The Design Item 7H[W is used to display text-based information saved for the query, such as author, query description, InfoProvider, and the global filters configured in the query.

� On the &RQVWDQWV tab page, you can select the NH\�GDWH that contains the date for which time-dependent master data is selected. You either specify the key date in the query definition (query properties), or supply the value by means of a variable. If no key date has been defined, the system date is taken as the key date.

� On the &RQVWDQWV tab page, you can also specify the�VWDWXV�RI�WKH�GDWD. This is the time at which the data of the last request (which can be evaluated for the reporting) was posted in the InfoProvider. With MultiProviders, the respective current InfoPackages are determined from the individual BasisCubes, and from these the one with the oldest date is used for the status of the data. This provides the date and the time (in the local time zone).

� On the )LOWHU tab page, if global filters were configured in the query, you can list the dimensions for which they were configured. Then all the current filter values which were configured for the selected dimension are displayed in the text element.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-25

SAP AG 2006

'HVLJQ�,WHP�0HVVDJHV

�

� The Design Item 0HVVDJHV displays all messages that are relevant for your workbook, such as messages generated by the BEx Analyzer and messages from the system to which you are currently connected.

� You can configure which types of messages you want to display (warning messages, success messages, information, or all).

� BEx Analyzer messages, including the latest messages from the system to which you are logged on, are displayed in your worksheet.

� In contrast to other Design Items, messages are not connected to a particular DataProvider. �

In analysis mode, the messages are displayed in a list beside the symbol for the respective message type. If there are no messages since the last update of your query results, nothing is displayed.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-26

SAP AG 2006

'HVLJQ�,WHPV�RI�WKH�%([ $QDO\]HU��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�8QGHUVWDQG�DQG�XVH�WKH�EDVLF�VHWWLQJV�RI�WKH�%([ $QDO\]HU

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-27

SAP AG 2006

6SHFLDO�7RROV�RI�WKH�%([ $QDO\]HU�IRU�3ODQQLQJ��8QLW�2YHUYLHZ�'LDJUDP

8QLW�WLWOH� /HVVRQ��'HVLJQ�,WHPV�RI�WKH�%([ $QDO\]HU� /HVVRQ��6SHFLDO�7RROV�RI�WKH�%([ $QDO\]HU�IRU�3ODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-28

SAP AG 2006

6SHFLDO�7RROV�RI�WKH�%([ $QDO\]HU�IRU�3ODQQLQJ��/HVVRQ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�8VH�WKH�'HVLJQ�,WHPV�RI�WKH�%([ $QDO\]HU�IRU�SODQQLQJ�DQG�WKXV�XQGHUVWDQG�WKH�LQWHUDFWLRQ�EHWZHHQ�SODQQLQJ�DQG�%([

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-29

SAP AG 2006

6SHFLDO�7RROV�RI�WKH�%([ $QDO\]HU�IRU�3ODQQLQJ��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�OHDUQ�PRUH�DERXW�WKH�SODQQLQJ�ZLWKLQ�D�ZRUNERRN�DQG�XVH�WKH�'HVLJQ�,WHPV�IRU�WKLV�LQ�WKH�%([$QDO\]HU�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-30

SAP AG 2006

$GGLQJ�1HZ�5RZV�LQ�%([

F4 button

$SSHDUV�DXWRPDWLFDOO\

-> No hierarchies-> No characteristic derivation-> Redundant time

characteristics and navigation attributesmust not appear togetherin the drilldown

-> Max. 1 structure in rowsand columns if datarecords exist

-> Max. 1 structure in columnsif no data records exist

�

Ò New input-ready cells are always displayed under the table, as input-ready boxes with a black border. You can enter as many rows for input as you want by double-clicking or by means of the )��EXWWRQ�LQSXW�KHOS, in order to enter characteristic values in the corresponding characteristic cell of the new row.

Ò Regardless of whether data has already been posted, you can enter plan data. Ò

When entering the characteristic values, you can use both keys and texts. If you are working with texts, the system must be able to determine exactly one key from the text in the logon language. For this reason, we recommend working with keys. You set this up in the Query Designer for each characteristic, under Properties -> Display tab page in the “ Value display” area, display as “.H\” .

Ò Please make sure that in the Query Designer for each characteristic, under Properties -> Enhanced tab page, in the “ Access type for result values” , “3RVWHG�YDOXHV” is selected. For the “ Master data” and “ Characteristic relationship” variants, no new rows can be created.

Ò In the %([�$QDO\]HU, you must also note that the Design Item $QDO\VLV�WDEOH must be represented in full size. You can specify the corresponding settings in the Design Mode, on the 3URSHUWLHV�RI�WKH�DQDO\VLV�WDEOH dialog box, →on the 6L]H tab page. You select both KRUL]RQWDO�DQG�YHUWLFDO��)XOO�VL]H.

Ò To transfer one or more changed data records, or new data records, to the server for validation, you select 7UDQVIHU�YDOXHV with the right mouse-button. To save the data records entered on the database, you use the right mouse-button to select 6DYH�YDOXHV, or you create a 6DYH�EXWWRQ.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-31

SAP AG 2006

6HWWLQJ�8S�6DYH�DQG�5HIUHVK�%XWWRQV�IRU�7UDQVDFWLRQ�'DWD

�

Ò The above illustration shows you how to construct a Save button for transaction data and a Refresh button.

Ò Please also note that there is no “ Reset” function in the BEx Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-32

SAP AG 2006

,PSOHPHQWLQJ�3ODQQLQJ�)XQFWLRQV�LQ�%([

9DULDQW��Select planning function directly and enter “filter”.

Enter planning sequence without “filter”.

9DULDQW��

�

Ò If you want to include a planning function in the BEx Analyzer end user interface, you create a function button by means of the “ Button” Design Item. Within this item, you use the static parameters to refer to the function, either directly through the function or through a planning sequence. The above illustration shows how the static parameters have to be set.

Ò You use the Design Item %XWWRQ to address the prototype of a Wizard. Not all static parameters are to be used in connection with the planning function. Thus only “ Data_Provider_Filter” can be used for the planning function, but not “ Data_Provider” , even though it is contained in the Wizard. “ Data_Provider” is only used in the analysis table and the dropdown box! Please note that the sequence of the individual parameters is random and that “ CMD” means Command and is used to execute the function.

Ò For YDULDQW�� of the planning function, the Data_Provider_Filter refers to a query selected in the workbook for which the planning function is then executed. In this case, you must consider which data is to be used for executing the function. This is looked at on the next slide.

Ò In YDULDQW�� and the case of the sequence, only the sequence is selected, because it contains a filter already included in the Planning Modeler, for which the function is executed.

Ò Please note that at present you cannot yet access a filter directly from the modeler or query, but can only access the query itself.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-33

SAP AG 2006

0XOWLSOH�3ODQQLQJ�)XQFWLRQV�LQ�2QH�%XWWRQ�DQG�$XWRPDWLF�6DYLQJ

�

Ò The above illustration shows that it is technically possible to put multiple planning functions on the Design Item “ Button” , and then to automatically save directly after the button is executed.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-34

SAP AG 2006

'DWD�/RFNLQJ�DQG�'DWD�3URFHVVLQJ�LQ�%([ ��

Characteristic restrictions:Fiscal year: 2010, 2011Version: 1.2Currency: EUR

Default values:Fiscal year: 2010

Å °º�§¯� ��

Ð �§ EÓF¥E£ �'�§�:�§£�� Å £ ��E�§£3� �Ô ¤5�N¦�¯:�.�d�¤��§¯�©

Query ORFNV list of all segments exclusively for users.

Copy function from 2010 -> 2011

When the function is executed, are other selections locked in addition to the locked query selections?-> No in this example

Copy function refers to the above query as Data_Provider_Filter

Function is H[HFXWHG for the selections of the filter currently set (from default value or filter set at runtime, without restricted key figures). In this example, for the list of all segments specified by the query.

Copy function refers to the above query as Data_Provider_Filter

�

Ò While a function button that refers to a sequence has fixed, defined selections on the basis of the filter related to this sequence, the GDWDVSDFH�WR�EH�ORFNHG depends on the reference query (DATA_Provider_Filter) and also on whether there are characteristics of the reference query in restricted key figures.

Ò Characteristics contained in restricted key figures are always locked by means of * (all characteristic values) when the planning function is executed, thus increasing the lock entries already resulting from the query.

Ò The GDWD�VHOHFWLRQ�XVHG�WR�H[HFXWH�WKH�IXQFWLRQ results from the current filter. This can correspond to the “ default values” or can result from the filter selections set at runtime, and it is thus dynamic.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-35

SAP AG 2006

'DWD�/RFNLQJ�DQG�'DWD�3URFHVVLQJ�LQ�%([ ��

Characteristic restrictions:Fiscal year: 2010, 2011Currency: EURVersion: 1,2

Default values:Fiscal year: 2010

Õ Ë Õ'ÕÖ Ë Ö'Ö

Å °º�§¯� ��Ñ ¡N¤I¨N� �´ Ö

Õ Ë Õ�ÕÖ Ë Ö�Ö

Å °«��¯d '�Ñ ¡N¤F¨d� �´ Õ

Ð �§ EÓF¥E£ �'�§�:�§£�� Å £ ��E�§£3� �

Ô ¤5�N¦�¯:�.�d×k¤��§¯d©

Query ORFNV all segments exclusively for users by means of “characteristic restrictions”.

Revaluation by 10%

Because the version is contained in the restricted key figures, it is ignored and the planning function is executed for all version, but only for fiscal year 2010.

Planning function locks data selection with reference to current filter without restricted key figures.

Copy function refers to the above query as Data_Provider_Filter.

With respect to the locks by the query that apply to data records with versions 1 and 2, here the function also locks data records with all versions! (Version = *)

�

Ò As already described, a function is executed�IRU�WKH�FXUUHQWO\�VHW�ILOWHU�ZLWKRXW�WKH�UHVWULFWHG�NH\�ILJXUHV! In the above example, this means for version 1 and version 2. This applies to the case where no conditions are formulated in the planning function. At the same time, the IXQFWLRQ�LV�RQO\�H[HFXWHG�IRU�ILVFDO�\HDU��, because this is in the default values and was not reset when the query was run.

Ò Aside from revaluation functions, and here due to business motives, you should not enter conditions in the Planning Modeler when setting up planning functions, but should select the “ conditions” from the query. This simplifies the design and increases the transparency!

Ò However, if there were a condition in the planning function stating that the revaluation in the above example should only be executed for the data in version 1, this setting would dominate, so that the data in version 2 would not be revaluated as well.

Ò In the above example, if you had wanted to have the function only executed for version 1 without having to create any conditions, you would not have entered the version in a restricted key figure, but rather in the filter, and would have selected version 1 at runtime, or you would have had to design another query for the function to serve as a reference, and would only have entered version 1 here.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-36

SAP AG 2006

'HFHQWUDOL]HG�)LOOLQJ�RI�)RUPXOD�9DULDEOHV�LQ�WKH�3ODQQLQJ�)XQFWLRQ�RI�%([

Goal: To distribute goods group # to goods group Water and Juice

In the function definition, both distribution factors have formula variables, and they are to be set decentrally.

(QG�XVHU�YLHZ�

&XVWRPL]LQJ�YLHZ�

Reference

�

Ò The above illustration shows how formula variables can be incorporated into planning functions in BEx, so that it is possible to fill these variables decentrally. This variable type is often used in the revaluation and distribution functions by key, and in the formula editor. The above example shows how, when you enter multiple variables in a planning function at the same time, they are included in the planning function and the worksheet.

Ò First, in accordance with the above example of the distribution function, two formula variables are used, one for the weighting factor of water, and one for that of juice. Within the “ Button” Design Item, VAR_Name is used to include both formula variables with their technical name, and Index is used to enter a number sequence for the two variables.

Ò In the purely Excel area of the workbook, which is later hidden for the end user and which is referenced within the “ command area” of the “ Button” Design Item, you enter for the variable VAR_NAME, the index and the technical name of the variables in three adjacent cells, and directly under this you assign VAR_VALUE, the index and a cell reference to an area in which the end user will later plan a numeric value for each of the variables.

Ò Please note that if there is only one formula variable, you set the index to 0. If a variable requires an interval, then you must enter the parameters VAR_LOW and VAR_HIGH in the “ Button” Design Item. This is referenced in accordance with the above procedure.

Ò ,I�\RX�RQO\�XVH�RQH�YDULDEOH��\RX�ZRUN�ZLWK�9$5B1$0(�DQG�LQGH[��RWKHUZLVH�WKH�SURFHGXUH�LV�DV�GHVFULEHG�DERYH��,I�\RX�GR�QRW�ZDQW�WKH�YDULDEOHV�WR�EH�VHW�GHFHQWUDOO\��WKHQ�\RX�HQWHU�9DUB9DOXH�DORQJ�ZLWK�9$5B1$0(�LQ�WKH�:L]DUG��DQG�\RX�HQWHU�D�QXPHULF�YDOXH�IRU�9$5B9$/8(��

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-37

SAP AG 2006

'URSGRZQ�%R[�IRU�WKH�3DUDOOHO�)LOWHULQJ�RI�&KDUDFWHULVWLF�9DOXHVIRU�0XOWLSOH�4XHULHV�

�

Ò

The above illustration shows an application use of the dropdown box. It can be used to set the same filter criterion for multiple queries, and to display the corresponding data selection.

Ò In the above example, the dropdown box for the customer group (dimension) characteristic is created, and only “ posted values” are to be displayed as the selections for the customer group. The selection display of the customer group should display the technical name and the text.

Ò The query that contains the “ sender data” is selected on the *HQHUDO tab page, and this query must also be included in the 7DUJHW�'DWD3URYLGHU tab page, along with all the “ Receiver queries” supplied by the “ Sender query” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-38

SAP AG 2006

'URSGRZQ�%R[��)��+HOS�ZLWK�'HIDXOW�6HOHFWLRQ�5DQJH

6RXUFH�LQIRUPDWLRQ�IRU�)��VHOHFWLRQ�KHOS�E\�PDVWHU�GDWD�TXHU\�

0DWHULDO�JURXS

�-8&7:$7:$7

�

Ò The above illustration shows that the F4 help of the dropdown box can be defined, with regard to the selection offered.

Ò You can create a master data query for this purpose. A prerequisite for this is that the desired characteristic (which is later used to filter in the dropdown box) must be created as an InfoProvider and “ With master data” must be selected in its master record. The master data query is then the source DataProvider for the dropdown box. The master data query can later be hidden with Excel tools.

Ò Within the dropdown box, you then select ³SRVWHG�YDOXHV´ as the read mode, and on the General tab page, you select the master data query as the source DataProvider.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-39

SAP AG 2006

([HFXWH�WKH�ZRUNERRN��WKHQ([FHO� 'DWD��!�9DOLGDWLRQ��6HWWLQJV��!�$OORZ�/LVW��6HOHFW�6RXUFH�$UHD

([FHO�'URSGRZQ�%R[�IRU�WKH�6HOHFWLRQ�RI�9DULDEOH�9DOXHV�IRU�D�3ODQQLQJ�)XQFWLRQ

Fixed quantity of characteristic values for the variable on the Product characteristic:

Entered in Excel with technical key, may be hidden

Planning function contains variable filling of the variable by means of Excel dropdown box.

6RXUFH

Purely Excel dropdown box

�

Ò The above illustration shows that the characteristic values of a variable that was created in the Planning Modeler and is to be used in a planning function, can be made available in the BEx by means of an ([FHO�GURSGRZQ�ER[.

Ò A disadvantage of this concept is that the characteristic values provided in this way come from a IL[HG specified quantity that come from a master data query, for example, like in the previous slide, or from fixed characteristic values noted in the purely Excel area with their WHFKQLFDO key, and therefore preconceived characteristic values. The end user cannot add to the list. It would have to be enhanced by the administrator, and is always hidden for the end user.

Ò It is also a disadvantage that in the Excel dropdown box, you cannot select key and text, or only text, but rather only the technical key is always used.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-40

SAP AG 2006

'URSGRZQ�%R[�IRU�WKH�6HOHFWLRQ�RI�9DULDEOH�9DOXHV�IRU�D�3ODQQLQJ�)XQFWLRQ

Incorporate master data query by means of analysis table

Excel referencing to 1st row of the master data box:Cell J2 =….

�

Ò The above illustration shows the concept of a variable that is used in the planning function, when you do not want to use an Excel dropdown box to make a variable selection, but rather the tools of the BEx Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-41

SAP AG 2006

([FHO�'URSGRZQ�%R[�IRU�WKH�6HOHFWLRQ�RI�3ODQQLQJ�)XQFWLRQV

Button for executing a planning function of your choice:

([HFXWH�WKH�ZRUNERRN��WKHQLQ�([FHO� 'DWD��!�9DOLGDWLRQ

Fixed list of the planning functions

PF4 :Technical name of a planning function

�

Ò The above illustration shows the settings required to be able to use an ([FHO�GURSGRZQ�ER[ to select a planning function. Here you also work with a fixed list of functions, whose technical name must be noted in the purely Excel area. This area should be hidden later for the end user.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-42

SAP AG 2006

:KDW�0XVW�EH�&RQVLGHUHG�ZKHQ�([HFXWLQJ�D�3ODQQLQJ�)XQFWLRQ

%HIRUH�H[HFXWLQJ�D�SODQQLQJ�IXQFWLRQ��D�XVHU�PXVW�FOLFN�RQ�D�FHOO�LQ�D�SXUHO\�([FHO�DUHD�

�

Ò The above slide shows how you proceed when executing a planning function. Ò

It is important that the cursor is definitely not in the area of the analysis table, otherwise the message outlined above appears.

Ò Instead, you must click on a cell in the purely Excel area so that the function can be executed.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-43

SAP AG 2006

,QFOXGLQJ�*UDSKLFV�LQ�WKH�%([ $QDO\]HU

�

Ò The inclusion of graphics in the BEx is effected exclusively by means of Excel functions. There is no Design Item for graphics.

Ò To reference the graphics to the data of the analysis table, you enter the cell area in which the data of the analysis table is located.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-44

SAP AG 2006

'DWD�([FKDQJH�%HWZHHQ�:RUNERRN�DQG�6HUYHU

Multi-dimensional table = result set

ServerVariant 1

Cell in workbook

Server

Multi-dimensional table = result set

Explicit

synchronization

through Excel

formula

Data

reconciliationVariant 2

Cell in workbook

Data

reconciliation

Automatic

synchronization

through BEx Analyzer

�

Ò In the BW-integrated planning, there are two variants for the server and the workbook to exchange data. Ò

The ILUVW�YDULDQW uses a direct, mutual data exchange between the server and the workbook. Ò

$�GLVDGYDQWDJH�RI�WKLV�YDULDQW is that the SRVLWLRQ�RI�D�FHOO�FDQQRW�EH�FKDQJHG and that HPSW\�([FHO�URZV�FDQQRW�EH�DGGHG�WR�WKH�TXHU\. However, it is possible to FUHDWH�DGGLWLRQDO�URZV�ZLWKLQ�WKH�%,�LQWHJUDWHG�SODQQLQJ.

Ò In the VHFRQG�YDULDQW, the server and the workbook only communicate with one another through a multi-dimensional table, which will be subsequently known as a container or result set. The server reads the data into the container and the workbook collects it from there using Excel formulas. Each cell is thus given a formula.

Ò $Q�DGYDQWDJH�RI�WKLV�VHFRQG�YDULDQW is that HYHU\�FHOO�FDQ�EH�SRVLWLRQHG�LQ�([FHO�KRZHYHU�\RX�ZDQW, which has uses for planning which will be dealt with later. It is also possible to DGG�HPSW\�([FHO�URZV, but it is not possible to DGG�URZV�ZLWKLQ�WKH�%,�LQWHJUDWHG�SODQQLQJ��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-45

SAP AG 2006

5HTXLUHG�7HFKQLFDO�6HWWLQJV�IRU�9DULDQW��Setting the data exchange by means of containers in the “analysis table” Design Item

Or on-the-fly setting after executed query with the right mouse button and the context menu

�

Ø The above illustration shows where the settings can be made for variant 2. Ø

Please note that if you decide on the second variant and set it up, you cannot undo this conversion again! Ø

3UHUHTXLVLWHV�IRU�XVLQJ�YDULDQW�� It can only be used for queries with a maximum of one structure in the rows, one structure in the columns, and, if applicable, all other dimensions in the free characteristics. The function cannot be used for calculated key figures.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-46

SAP AG 2006

([FHO�)RUPXODV�IRU�WKH�&HOOV�RI�WKH�([HFXWHG�4XHU\�LQ�9DULDQW��

%([*HW'DWD��'$7$B3529,'(5B��8��,��

Systematic display of where the data is got from:

One formula per cell that gets data from the container

%([6HW'DWD��'$7$B3529,'(5B��8��,��For input cells:

For display cells:

7RROV��!�)RUPXOD�$XGLWLQJ��!�7UDFH�3UHFHGHQWV

�

Ø The above illustration shows that for variant 2, one Excel formula is created for each cell representing a pointer to the container.

Ø Formulas in the LQSXW�UHDG\�FHOOV contain BEx6HWData (numeric value of the cell, name of the DataProvider, cell reference) and pure UHDG�FHOOV contain BEx*HWData (name of the DataProvider, cell reference).

Ø Note that the formula is only displayed when you click on the cell, otherwise #NV is always displayed (NV = No Value).

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-47

SAP AG 2006

([FHO�)RUPXODV�IRU�WKH�&HOOV�RI�WKH�([HFXWHG�4XHU\�LQ�9DULDQW��

:RUNERRN

Plan revenue

Actual revenue 100000

Ù�Ú�Û�Ü 6HW Ý:Þ�ß*Þ�àIá<â�ã�ä å,Ý�æ§ç�æ:è:é:ê$ë�ìdí Ý Û ê.è:á<å�ä�î$ï�ð�ð�ä ï�í ñ�ð�ò

Plan cell

In this scenario, the set formula may not be entered directly in the input-ready cell, because this formula would be overwritten by the plan value.

Reference with Excel cell reference between input-ready cell and set formula

�

Ø You can use the SET formulas to create a free data structure in the frontend, independently of the query. The above diagram shows the related design.

Ø Note that the input-ready cell, which is positioned in the purely Excel area, is not directly filled with the SET formula, because a manual entry would overwrite the Excel formulas and you would thus lose the SET formula reference.

Ø For this reason, you select the referencing represented in the above illustration.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-48

SAP AG 2006

RevenueCustomer discountSales commissionSales direct costs

Net revenueMaterial direct costsManufacturing direct costs

Contribution margin IMaterial overhead costsManufacturing overhead costsContribution margin II

Deviations

Contribution margin III

Overhead costs

Operating income

$SSOLFDWLRQ�6FHQDULR�IRU�9DULDQW��Entering plan values in the purely Excel area

8VLQJ�%([6HW'DWD OLQN�WR�ZULWH�SODQ�GDWD�EDFN�WR�WKH�FRUUHVSRQGLQJ�SODQ�TXHU\

Granularity independent of vehicle model

Query 2:

Granularity dependingon vehicle model

Query 1:

�

Ø The above illustration shows a typical application use of the 2nd variant, namely a complex contribution margin scheme in which data from multiple queries with different granularities in the respective aggregation levels is read by means of a shared contribution margin scheme, or is manually planned, and is then written back to the queries held in the background by means of the cell reference. Please note that items such as net revenue, contribution margins I to III, and operating income are determined by means of planning functions or as calculated key figures. The other items are planned manually.

Ø Because typing numeric values into a cell with an Excel formula reference that is outsourced from the frontend area would delete this formula, you must ensure that in the above scenario you do not enter numbers directly into this cell, but first reference this cell by means of another Excel cell and then enter the plan data in this additional Excel cell.

Ø Thus the additional Excel cell with the numeric value points to the Excel cell with the Excel formula reference, which in turn communicates by means of the formula with the container and the plan query into which the data is to flow.

Ø You can also read data from the queries that is relevant to the further planning. If you do not want to see this data, it can be hidden with Excel tools.

Ø Because you usually only integrate the cells relevant to the query and do not require the remaining information in the query, which is not to be obtained by means of the container, you can delete it using Excel tools.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-49

SAP AG 2006

([DPSOH�RI�2IIOLQH�3ODQQLQJ�ZLWK�([FHO

([FHO�

�

Ø Using BEx Analyzer as the front-end system enables you to combine the advantages of Excel with those of the centrally managed planning model.

Ø For example, an Excel offline planning can be used for additional calculations in Excel, and the result data can then be written to the BI-integrated planning.

Ø The easiest way to create such an offline planning is to execute a workbook and then save the Excel data locally - the link to the central planning model is not lost in the process.

Ø The data input and the additional calculations are then performed in the Excel stand-alone, but the calculated values can be transferred back to the corresponding field in the workbook by means of the “ System Information” button in the workbook.

Ø Please note that the function buttons cannot be used by means of a local Excel, because they are executed by the server.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-50

SAP AG 2006

6SHFLDO�7RROV�RI�WKH�%([ $QDO\]HU�IRU�3ODQQLQJ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�8VH�WKH�'HVLJQ�,WHPV�RI�WKH�%([ $QDO\]HU�IRU�SODQQLQJ�DQG�WKXV�XQGHUVWDQG�WKH�LQWHUDFWLRQ�EHWZHHQ�SODQQLQJ�DQG�%([

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-51

SAP AG 2006

&UHDWLQJ�DQG�8VLQJ�DQ�([FHO�%DVHG3ODQQLQJ�$SSOLFDWLRQ�ZLWK�WKH�%([ $QDO\]HU��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�8QGHUVWDQG�WKH�IXQGDPHQWDO�'HVLJQ�,WHPV�RI�WKH�%([ $QDO\]HU8VH�VSHFLDO�WRROV�RI�WKH�%([ $QDO\]HU�IRU�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-52

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-53

�([HUFLVHV�

8QLW�� &UHDWLQJ�DQG�8VLQJ�DQ�([FHO�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�WKH�%([�$QDO\]HU�

/HVVRQ�� &UHDWLQJ�D�3ODQQLQJ�$SSOLFDWLRQ�8VLQJ�WKH�%([�$QDO\]HU�


• Create a planning application using the BEx Analyzer

• Create an Excel offline planning with integration to the BEx Analyzer

The planning application is to be set up for the Sales Planner, who will plan the price and quantities and execute various planning functions.

In the process, the queries and planning functions previously created are referenced.

Finally, an additional calculation is to be performed using the Excel offline planning.

1-1 Navigate to the %([�$QDO\]HU and create a SODQQLQJ�DSSOLFDWLRQ�IRU�WKH�TXDQWLW\�DQG�SULFH�SODQQLQJ�RI�WKH�6DOHV�0DQDJHU. To access the BEx Analyzer you click the “6WDUW” button within Citrix and then navigate as follows: 6WDUW��!�3URJUDPV��!�%XVLQHVV�([SORUHU��!�$QDO\]HU�. You then press the “1HZ” button in the pure Excel area. Please note that in the project you have to switch to the GHVLJQ�PRGH directly after you log on to the system, then under 7RROV��!�0DFUR��!�6HFXULW\�you must go to the 7UXVWHG�3XEOLVKHUV tab page and set the 7UXVW�$FFHVV�WR�9LVXDO�%DVLF�3URMHFW�flag. For this training course, this setting was entered for you centrally on Citrix, so this step is omitted.

1-1-1 First, you want to represent the TXDQWLW\�SODQQLQJ�RI�WKH�6DOHV�0DQDJHU in the BEx Analyzer. Switch to the GHVLJQ�PRGH and position the cursor in cell $�� and create an “$QDO\VLV�*ULG” design item. You assign to the analysis grid the plan query you previously created for the quantity planning of the Sales Managers, with the technical name 6��B$/B��B3ODQTXHU\B��B6$/0$1. Accept the standard settings and also select the setting “$XWR)LW” . You then VDYH the planning application as a ZRUNERRN and assign the description *URXS��B7%:��B%(;B6$/0$1��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-54

�3OHDVH�QRWH�WKDW�WKLV�TXHU\�LV�NQRZQ�DV�'DWDB3URYLGHUB��LQ�WKH�V\VWHP��,W�ZLOO�EH�UHIHUUHG�WR�LQ�VXEVHTXHQW�WDVNV��

1-1-2 You should now get the message “9DULDEOHV�H[LVW��&KDQJH�WKH�YDULDEOH�YDOXHV” , without the transaction data being displayed. Press the “&KDQJH�9DULDEOH�9DOXHV” button and on the next screen select .�� as the characteristic value for the Fiscal Year variable. You should now see an input-ready planning application with data for the fiscal years 2010 and 2011, which is accessed by the exception you configured (colored in red). Here is an excerpt:

1-1-3 Now switch to the GHVLJQ�PRGH again and position the cursor in cell $�, in which you create a EXWWRQ�WR�VDYH�GDWD by means of the “ ,QVHUW�%XWWRQ” design item. In the “ Button Text” field you write “6DYH” . You deselect the field “$GMXVW�5DQJH�WR�,WHP�6L]H” . In the 6WDWLF�3DUDPHWHUV area, you select &0' for the field “ Name” , � for the field “ Index” and 6$9(B$5($ for the field “ Value” . �6DYH your ZRUNERRN�and execute the planning application, setting your variable to ��In the analysis grid area for fiscal year ��, replace the old values for the VDOHV�TXDQWLWLHV with the QHZ�YDOXHV as follows:

1. Sales quantity in K4/2011 in company code X: 2. Old value 3. New value

4. Sales quantity in .�/�� in company code ��: 5. 150 6. 200

7. Sales quantity in .�/�� in company code ��: 8. 250 9. 300

You must press the “(QWHU” button after entering each value! Position your cursor outside the “$QDO\VLV�*ULG” and then press the “6DYH” button you created.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-55

1-1-4 Now open a VHFRQG�PRGH in parallel and navigate in the /LVW�9LHZHU�to your Realtime InfoProvider 7%:��6�� and check for fiscal year ��, goods group ��and version % whether the data you saved with the BEx Analyszer has appeared.

You should get the following results:

As you see, a delta of 50 units each was saved.

1-1-5 Now go back to the GHVLJQ�PRGH of the BEx Analyzer and insert the design items “/LVW�RI�&RQGLWLRQV“ and “/LVW�RI�([FHSWLRQV“ which were designed in the Query Designer for this query. Position the cursor in cell $��and select the corresponding design item for ([FHSWLRQV. In the “ DataProvider“ field, assign 'DWDB3URYLGHUB�, which is referenced by the query you had selected in the analysis grid design item. � Now position the cursor in cell $��and select the design item for &RQGLWLRQV. Assign the same DataProvider and select “$XWR)LW“ . 6DYH your ZRUNERRN again�

1-1-6 Now position the cursor in cell )��and configure the design item “0HVVDJHV” here. On the corresponding *HQHUDO�tab page, you select DOO�ILHOGV, otherwise you leave the standard settings. In cell )� you now write a header for the message area to identify it as such. Write “6\VWHP�PHVVDJHV�” . �6DYH�\RXU�ZRUNERRN�DJDLQ�and execute it for ��. You see that the planned data appears in version B on the granularity of goods group #. Set your &RQGLWLRQ and the ([FHSWLRQ�to LQDFWLYH and VDYH.

1-1-7 You now want to implement a 5HIUHVK�EXWWRQ in your planning folder. For this purpose, you create a “%XWWRQ” design item in cell $�. In the “ Button Text” field you write “8SGDWH” . 'HVHOHFW�“$GMXVW�5DQJH�WR�,WHP�6L]H” . In the 6WDWLF�3DUDPHWHUV area, you select &0' for the field “ Name” , � for the field “ Index” and &+(&.B9$/8(6 for the field “ Value” . �6DYH your ZRUNERRN�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-56

1-1-8 When you look at your workbook, you see two refresh buttons. The first button is the one you created, and the second looks like this:

and means “ Temporarily interrupt automatic update” .

What refresh activities are triggered by these two buttons: 7KH�UHIUHVK�EXWWRQ�\RX�FUHDWHG __________________________________ ______________________________________________________________

6\VWHP�LFRQ ______________________________________________ ______________________________________________________________

1-1-9 If a workbook has been executed, how do you confirm that if the plan query originally had input-ready cells and you include this plan query in a workbook, that these cells are still input-ready in the workbook? ______________________________________________________________ ______________________________________________________________ How could this activity be triggered, for example? ______________________________________________________________ ______________________________________________________________ Perform this activity to ensure that you really will subsequently be able to work with input-ready cells! Can this setting be entered for each analysis grid, or is it only performed once for each workbook? ______________________________________________________________

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-57

1-2 In the following section, your aim is to include in the planning application the planning functions for the quantity planning in version B which you set up in an earlier unit. This refers to the distribution function of goods group # to goods groups WAT and JUC, but only for the sales quantity key figure. The distribution factors were modeled as variables. Subsequently, the plan data of goods group WAT was reposted to TWAT for the sales quantity key figure.

1-2-1 You now want to integrate the distribution function into the planning application. In the GHVLJQ�PRGH, position the cursor in cell $�� and create the “%XWWRQ” design item. In the “5DQJH” field, enter �$��%��Select the flag “$GMXVW�5DQJH�WR�,WHP�6L]H” .� For the button properties, you write “)XQFWLRQ��GLVWULEXWLRQ�WR�JRRGV�JURXSV” in the “%XWWRQ�7H[W” field. In the 6WDWLF�3DUDPHWHUV area, you select the following:

10. Name 11. Index 12. Value

13. Planning_Function_Name 14. 0 15. 1. �3ODQQLQJB)XQFWLRQ! 2. Info Area: %:�7UDLQLQJ�!�%:�&XVWRPHU�7UDLQLQJ��!�%:��%,�,QWHJUDWHG�3ODQQLQJ��!��%:��*URXS�� 3. Select aggregation level 6��B$/B��4. Button “2SHQ” 3. Select the function 6��B3)B��5. Button “2SHQ”

16. Data_Provider_Filter 17. 0 18. Data_Provider_1

19. CMD 20. 0 21. Execute_Planning_Function

As you see, the BEx Analyzer uses the selection for the execution of the planning function that is contained in the query, and not the filter that was created for this function in the Planning Modeler. As you see, we are not going to deal here with the sequence relating to this function that was created in the Planning Modeler. This procedure will be shown at another time. 6DYH your ZRUNERRN�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-58

You now execute the�GLVWULEXWLRQ�IDFWRU for the fiscal year ��.

An excerpt of the data before the distribution:

An excerpt of the data after the distribution:

As you see, the distribution is performed for all fiscal years! The distribution is performed on the basis of the default values of the distribution variables! Do not�VDYH the WUDQVDFWLRQ�GDWD created and leave the BEx Analyzer without saving the VHWWLQJV�DQG�GDWD, in order to empty the working memory and thus be able to reverse the function. Then you open your workbook again and press the refresh button of the BEx Analyzer, “7HPSRUDULO\�LQWHUUXSW�DXWRPDWLF�XSGDWH” so that the buffer no longer contains the distributed data, but rather the original data before the distribution.

1-2-2 Now open a second mode and call the ORFNLQJ�VHUYLFH by means of transaction UVSOVH. Select InfoProvider 6��B$/B�� and display the locked selections. You should see the following:��

If you now executed the distribution function again (please do not execute it), no additional locked segment would result.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-59

If you look at the analysis grid, in the data columns you see the restricted key figures, which consist of the key figure itself and the fiscal year.

If the fiscal year in the underlying query was not also additionally restricted by means of the variable in the “ characteristic restrictions” , for which fiscal year would the planning function be executed, and why? ______________________________________________________________ Delete the mode for the locking service.

1-2-3 In the planning function, the distribution variables had the default setting 1:1 and were not queried any more when the distribution function was executed. The distribution variables for Water and Juice had the following names: 6��B9$5B'LVWULEB.(<:$7�6��B9$5B'LVWULEB.(<-8&��You now want to implement a variable query for the decentral controlling of variables. In the design mode, go to cell $��, in which you had positioned the “ Button” design item for your distribution function, and add �8��:�� to the “&RPPDQG�5DQJH” . (U and W are written in upper case). Then navigate to cell 8�� and enter the following:

22. 23. U 24. V 25. W

26. 13 27. VAR_Name_0 28. 0 29. S##_VAR_Distrib_KEYWAT

30. 14 31. VAR_Value_0 32. 0 33.

34. 15 35. VAR_Name_1 36. 0 37. S##_VAR_Distrib_KEYJUC

38. 16 39. VAR_Value_1 40. 0 41.

Then you position the cursor in cell $�� and write the following text: “9DULDEOH�IRU�GLVWULEXWLRQ�IDFWRU�:DWHU�” Now position the cursor in cell $�� and write the following: “9DULDEOH�IRU�GLVWULEXWLRQ�IDFWRU�-XLFH: ” The distribution factors, which are entered manually, are entered later on in cells C16 and C18 respectively. Now position the cursor again in cells :��and :��, and in each cell enter a reference to the cells in which you later want to enter the distribution factors

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-60

manually.

The following should now be appearing in the area U13 to W16:

42. 43. U 44. V 45. W

46. 13 47. VAR_Name_0 48. 0 49. S##_VAR_Distrib_KeyWAT

50. 14 51. VAR_Value_0 52. 0 53. =C16

54. 15 55. VAR_Name_1 56. 0 57. S##_VAR_Distrib_KeyJUC

58. 16 59. VAR_Value_1 60. 0 61. =C18

In cell &��you now enter distribution factor � and in cell &��distribution factor �. 6DYH your workbook� Please note: So that the end user will not see the variable table in the area U to W, you must hide columns U to W, but you do not do this yet because this area will be required in subsequent tasks! They are only hidden at the end!

�6DYH� the ZRUNERRN and stay in the execution mode.

1-2-4 Now�H[HFXWH the GLVWULEXWLRQ�IXQFWLRQ for factors 2 and 3, which have already been set. Before the distribution:

After the distribution:

6DYH the SODQ�GDWD. Which setting in the YDULDEOH�ZL]DUG makes the system use the manual entry instead of the default of 1 that was set in the Planning Modeler for both

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-61

variables? _____________________________________________________________

6DYH�the SODQ�GDWD. Your InfoProvider now contains the following plan data for version B:

1-2-5 You now want to integrate the UHSRVWLQJ�IXQFWLRQ�IRU�JRRGV�JURXS�:$7�WR�

JRRGV�JURXS�7:$7 into the planning application. To implement the reposting function, switch to the GHVLJQ�PRGH and position the cursor in cell $�� and create a “%XWWRQ” design item. In the “%XWWRQ�7H[W” field you enter the text “)XQFWLRQ��5HSRVW�**�:$7��!�7:$7” . Select the flag�“$GMXVW�5DQJH�WR�,WHP�6L]H” . For the field “5DQJH” , you write “ �$��%��“ . Select�“$GMXVW�5DQJH�WR�,WHP�6L]H” . Assign the following:





I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-62

6DYH the workbook and H[HFXWH the UHSRVWLQJ�IXQFWLRQ in the planning application. If a variable request appears, you select the fiscal year 2010.

��You should now see your plan data represented as follows – An excerpt of the data before the distribution:

You should now see your plan data represented as follows – An excerpt of the data after the distribution:

� Now�VDYH�the�SODQ�GDWD�in the�InfoProvider.

The InfoProvider should now contain the following data for version B

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-63

1-2-6 Based on the query executed, you now add to row $� the following text: “4XDQWLW\�SODQQLQJ�RI�WKH�6DOHV�0DQDJHU” . For this text, you select font size �� and the color UHG and make the text EROG. 6DYH the workbook. At this point, the quantity planning of the Sales Managers in Version B is complete for goods groups TWAT and JUC!

1-3 In the following section, the SULFH�SODQQLQJ�RI�WKH�6DOHV�0DQDJHUV is integrated into the workbook, both the plan query and the planning function for copying from version B1 to version B2, the conversion function with the two conversion variables, the delete function for version B2 and the copy function to version B2, which contains one variable.

1-3-1 First you write “3ULFH�SODQQLQJ�RI�WKH�6DOHV�0DQDJHUV” in cell $�� and select font size �� and color UHG to highlight the header. Make the text EROG.

1-3-2 Now you create the design item “$QDO\VLV�*ULG” in cell $�� Here you select the plan query of the price planning 7%:��B3��B$/��B34��B6$/0$1 and also the setting “$XWR)LW” . 7KH�TXHU\�LV�VXEVHTXHQWO\�UHIHUHQFHG�DV�'DWDB3URYLGHUB�� 6DYH�your workbook again�and execute it for ��. The prices and the costs of goods manufactured in version B were already planned for you! Here is an excerpt of what you should see:

1-3-3 In the following section, the planner is provided with the copy and delete

functions by means of an ([FHO�GURSGRZQ�ER[. First you must create the design item “%XWWRQ” in cell $�� and configure it there as follows: In the “5DQJH“ field you write: �$��$��. In the “%XWWRQ�7H[W” field you write “([HFXWH�SODQQLQJ�IXQFWLRQ” . Select�“$GMXVW�5DQJH�WR�,WHP�6L]H” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-64

In the 6WDWLF�3DUDPHWHUV area, you select the following:




In the “&RPPDQG�5DQJH” you write �&��(�� Now position the cursor in cell &��and write 3/$11,1*B)81&7,21B1$0( in this cell. In cell '�� you enter “ �” . Before you position an Excel dropdown box in cell E45, you first have to list the technical names of the desired planning functions below one another in cells *�� to *�� In cells +�� to +�� you then enter the respective descriptions. Enter the following:

83. 84. G 85. H

86. 87. P##_PF_01 88. Copy from version B1 -> B 2

89. 90. P##_PF_03 91. Delete the data within version B 2

1-3-4 Afterwards position the cursor in cell *��and write “)RU�FODULILFDWLRQ�” . Make the text EROG�and XQGHUOLQH it.��Now position the cursor in cell (��and write “6HOHFW�WKH�GHVLUHG�SODQQLQJ�IXQFWLRQ�” .�Make the text EROG and XQGHUOLQH it.��Now you create the ([FHO�GURSGRZQ�ER[ in cell (��. To do this, you position the cursor in the cell, and in Excel you select the menu path 'DWD��!�9DOLGDWLRQ« . On the next screen, you must enter /LVW in the “$OORZ” field and in the “6RXUFH” area you reference the area with the WHFKQLFDO name of the planning function, which means that you select �*��*�� here. Do not change any of the other settings on the screen. You now hide the content of cells &��WR�'�� by using Excel to change the WH[W in this area to ZKLWH�instead of black. Now�VDYH�your workbook, set the variable of the fiscal year to ��and click with the cursor in cell�(��. You should now see the Excel dropdown box that you always see when you click on the cell! Open the Excel dropdown box and check whether both functions were offered.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-65

Then H[HFXWH the FRS\�IXQFWLRQ�IURP�YHUVLRQ�%��!�%�.��

You should receive the following display - before copying (here is an excerpt):

You should receive the following display - after copying (here is an excerpt):

'R�QRW�VDYH�the SODQ�GDWD. Afterwards, you return to the GHVLJQ�PRGH and navigate again to the button of cell &��. Here, in the “5DQJH” of the button, you write �$��%�� instead of �$��$�� so that the description of the button will be completely visible later. You also select�“$GMXVW�5DQJH�WR�,WHP�6L]H” . OPTIONAL EXERCISES

1-3-5 You now have to model the two functions, conversion and copy to B, with variables. First, you implement the FRQYHUVLRQ�IXQFWLRQ, which includes two variables: 3��B9$5B5(9B&2*6B7:$7� 3��B9$5B5(9B&2*6B-8&��The technical name of the planning function is: 3��B3)B��To do this, create a new “EXWWRQ” design item in cell $�� and configure it as follows: “ Range” : �$��%�� “ Button Text” : )XQFWLRQ��&RQYHUVLRQ�LQ�YHUVLRQ�%��Select:�� “$GMXVW�5DQJH�WR�,WHP�6L]H” �

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-66


95. Planning_Function_Name 96. 0 97. 1. �3ODQQLQJB)XQFWLRQ! 2. Info Area: %:�7UDLQLQJ�!�%:�&XVWRPHU�7UDLQLQJ��!�%:��%,�,QWHJUDWHG�3ODQQLQJ��!��%:��*URXS�� 3. Select aggregation level 3��B$/B��4. Button “2SHQ“ 3. Select the function 3��B3)B��5. Button “2SHQ“



“ Command Range” :�� 8��:��

Now navigate into cell 8��and make the entries shown in the following table:

104. 105. U 106. V 107. W

108. 50 109. VAR_Name_0 110. 0 111. P##_VAR_REV_COGS_TWAT

112. 51 113. VAR_Value_0 114. 0 115. =C53

116. 52 117. VAR_Name_1 118. 0 119. P##_VAR_REV_COGS_JUC

120. 53 121. VAR_Value_1 122. 0 123. = C55

Now navigate to cell $�� and enter the following text: “9DULDEOH�IRU�FRQYHUWLQJ�WDEOH�ZDWHU�LQ�YHUVLRQ�%��” �

Now navigate to cell $�� and enter the following text: “9DULDEOH�IRU�FRQYHUWLQJ�MXLFH�LQ�YHUVLRQ�%�� ” �

In cell &��you now enter distribution factor � and in cell &��distribution factor �. Both values are already percentage values.

Now VDYH�the workbook and then execute the FRQYHUVLRQ�IXQFWLRQ for the variables set.

You should receive the following result - before the conversion (here is an excerpt):

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-67

You should receive the following result - after the conversion (here is an excerpt):

'R�QRW�VDYH your�SODQ�GDWD��

1-3-6 Because the planners want to edit the data manually after it is copied and converted in version B2, you should enter �� instead of 10.2 for the column 3ULFH�Version B2 for�-XLFH in��DQG��, and �� instead of 21 for 7DEOH�ZDWHU in ��DQG��. Do not change the cost of goods manufactured. After entering the plan data, take a look at the “ result rows“ . You see that at runtime, no plan data totaling was performed. When you press the “ Refresh” button that you created, the totaling is still not performed. So you position the cursor on a result row and use the right mouse-button to select “7UDQVIHU�YDOXHV” . You should see the following data situation:

6DYH�the SODQ�GDWD. Please note that you can use the Excel dropdown box to select the planning function P##_PF_03 at any time. You can use this function to reset the data planned in version B2 at any time. This resetting must be planned in the design phase. If necessary, use this function and go through the planning of the Sales Managers again! Go to the GHVLJQ�PRGH again.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-68

1-3-7 Explain how the “ ,QGH[” is used within the “%XWWRQ” design item. ______________________________________________________________ ______________________________________________________________ Complete the following table if the subsequent functions are to be used in accordance with the usage of the index:


127. DATA_PROVIDER_FILTER 128. 129. DATA_Provider_1

130. PLANNING_FUNCTION_NAME 131. 132. COPY_GROUP##

133. CMD 134. 135. EXECUTE_PLANNING_FUNCTION

136. DATA_PROVIDER_FILTER 137. 138. DATA_Provider_1

139. PLANNING_FUNCTION_NAME 140. 141. REVALUATE_GROUP##

142. CMD 143. 144. EXECUTE_PLANNING_FUNCTION

145. CMD 146. 147. SAVE_AREA

1-3-8 Now you want to include the FRS\�IXQFWLRQ�IURP�YHUVLRQ�"��!�% with the technical name 3��B3)B�� and the variables 3��B9$5B6HQGHUYHUVLRQBFRS\ in the workbook. Here the end user once again uses an Excel dropdown box to select the two possible sender versions. First create the “%XWWRQ” design item for cell�$��and configure it as follows: ” Range” : �$��%�� “ Button Text” : � � � � )XQFWLRQ��FRS\�YHUVLRQ�"�!�% “ Command Range” : �$��&�� Select “$GMXVW�5DQJH�WR�,WHP�6L]H” .




157. VAR_NAME 158. 0 159. P##_VAR_SENDERVERSION_COPY (manual entry)


I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-69

Now position your cursor in cell $�� and write 9$5B9$/8( there. Then go to cell %��and write “ �” . Now you KLGH�ERWK�FHOOV, by changing the FRORU�RI�WKH�WH[W to ZKLWH. Now navigate to cell�8�� and write “9HUVLRQV�IRU�FRS\�IXQFWLRQ� ” . Now position your cursor in cell 8�� and write %� there. In cell 8�� you write %�. You have now created a list of the characteristic values that can be selected by means of the subsequent Excel dropdown box. This area is again to be hidden from the end user, but this is only performed at the end of the exercise block. Now you have to create an ([FHO�GURSGRZQ�ER[ for selecting the versions. Now position the cursor in cell &��and enter: “6HOHFW�WKH�VHQGHU�YHUVLRQ�” . In cell &�� you create an ([FHO�GURSGRZQ�ER[, as shown before, which references range �8��8��, which is the manually created list of variable selections.

1-3-9 6DYH�your ZRUNERRN and execute it. For the copy function just created, select sender version %� and execute the copy process to version %. Before copying (here is an excerpt):

After copying (here is an excerpt):

You then�VDYH�your SODQ�GDWD� The price planning is now complete. Subsequent planning sessions only refer to the data of version B.

Your InfoProvider should now contain data records for versions B1, B2 and B:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-70

Under the analysis grids you should find a row outlined in black, which is used to DGG�QHZ�URZV:

For which setting in the query does it make sense to use this function, and why can the function not be used here? _______________________________________________________________ How do you proceed if you want to enter new rows? _______________________________________________________________ What do you have to consider if the property “ key and text” was selected for a characteristic of the “ row” of the query, when you want to use the function? _______________________________________________________________

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-71

1-4 Now you want to start an ([FHO�RIIOLQH�SODQQLQJ example, in which you determine the price of the table water in version B1 in fiscal year 2010 on the basis of the cost of goods manufactured and a profit percentage, performing this in an additional calculation in the local Excel. Then the price thus determined will be transferred to the workbook of the BEx Analyzer.

1-4-1 You are in the execution mode of your workbook *URXS��B7%:��B%(;B6$/0$1, and you save it on drive 1 of your computer. Give the file the following name: *URXS��B7%:��B([FHOB2IIOLQHB6$/0$1 and save it in the format “0LFURVRIW�2IILFH�([FHO�:RUNERRN” . 6DYH and FORVH your ZRUNERRN�LQ�WKH�%([�$QDO\]HU in order to avoid locking, then open the file in the local Excel. You get there by logging on to the BEx Analyzer again: 6WDUW�±!�3URJUDPV��!�%XVLQHVV�([SORUHU��!�$QDO\]HU. Then you press the Excel button “2SHQ” and select the file named above. When you open the file, the “ Security Warning” screen opens. Now select “'LVDEOH�0DFURV” so that you can access Microsoft Excel without a BI add-in!

1-4-2 Now position the cursor in cell $�� and enter the following text: “$GGLWLRQDO�FDOFXODWLRQ��FDOFXODWLRQ�RI�WKH�VDOHV�SULFH�LQ�YHUVLRQ�%��” . Then position your cursor in cell $�� and write: “([DPSOH�IRU�WDEOH�ZDWHU” . In cell $��write “0DQXIDFWXULQJ�FRVWV” and in cell $��“3URILW�SHUFHQWDJH” . In cell�$�� write “3ODQ�SULFH�IRU�7:$7�LQ�YHUVLRQ�%��DQG��“ . Position the cursor in cell�&�� and format this cell with Excel tools so that “1XPEHU” and “'HFLPDO�3ODFHV” “ �” is set with variant “ ��” , so that only absolute values can be entered in the cell! Then enter the profit percentage factor “ ��” in this cell. Now go to cell '��and�UHIHUHQFH cell “*��” , in which the manufacturing costs for 7:$7�and %� in ��are located. Then go to cell '��and store the formula for the profit percentage: ³ '�� &��” . In cell '��you write the formula for plan data to be calculated as follows: “ '��'��“ .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-72

Now the calculated value in cell�'�� must be transferred to the corresponding cell for (TWAT, 2010, B1). To do this, you position the cursor in cell '�� and reference as follows: “ ='��” . This procedure ensures that the start value of the calculation, namely the manufacturing costs, is planned manually, and the corresponding prices are obtained from an additional calculation. Therefore, in cell *�� you enter the value � for the manufacturing costs and then press Enter. You should then get 24 for the corresponding price in cell '��. You now use an�([FHO�IUDPH�to�RXWOLQH�area $�� to '�� and select for this area the text color “5HG” and “%ROG” . Save the Excel offline planning using the Excel save button “6DYH” .

1-4-3 Now you have two independent workbooks, and the result of the additional calculation in cell '�� of the Excel offline planning must be transferred back into the BEx workbook *URXS��B7%:��B%(;B6$/0$1. In the project, you would use a macro for this purpose. Instead, we will transfer the cell value manually using &RS\�DQG�3DVWH. To do this, you open the Excel offline planning and the above-named BEx workbook in parallel. First position your cursor in cell '�� of the ([FHO�RIIOLQH�SODQQLQJ and press the “&75/” and “&” keys on your keyboard at the same time. Then, within the %(;�ZRUNERRN� you go to cell '�� and write “ ” in order to create a reference; you then press “&75/” and “9” at the same time to insert the value copied from the Excel offline planning into the cell. The entry “ ��” should now appear in the Excel cell. 'R�QRW�VDYH�the SODQ�GDWD. 6DYH�the ([FHO�RIIOLQH�SODQQLQJ�and then leave it. Please note that if you want to refresh, you must not choose the system icon

, because this would cause the server to overwrite the frontend data. You can only use the “ Refresh” button you created yourself to update the data planned by means of the frontend.

This concludes the price planning of the Sales Managers. Now�FORVH the ZRUNERRN of the BEx Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-73

�6ROXWLRQV�

8QLW�� &UHDWLQJ�DQG�8VLQJ�DQ�([FHO�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�WKH�%([�$QDO\]HU�

/HVVRQ�� &UHDWLQJ�D�3ODQQLQJ�$SSOLFDWLRQ�8VLQJ�WKH�%([�$QDO\]HU�

1-1 Navigate to the %([�$QDO\]HU and create a SODQQLQJ�DSSOLFDWLRQ�IRU�WKH�TXDQWLW\�DQG�SULFH�SODQQLQJ�RI�WKH�6DOHV�0DQDJHU. To access the BEx Analyzer you click the “6WDUW” button within Citrix and then navigate as follows: 6WDUW��!�3URJUDPV��!�%XVLQHVV�([SORUHU��!�$QDO\]HU�. You then press the “1HZ” button in the pure Excel area. Please note that in the project you have to switch to the GHVLJQ�PRGH directly after you log on to the system, then under 7RROV��!�0DFUR��!�6HFXULW\�you must go to the 7UXVWHG�3XEOLVKHUV tab page and set the 7UXVW�$FFHVV�WR�9LVXDO�%DVLF�3URMHFW�flag. For this training course, this setting was entered for you centrally on Citrix, so this step is omitted.

1-1-1 First, you want to represent the TXDQWLW\�SODQQLQJ�RI�WKH�6DOHV�0DQDJHU in the BEx Analyzer. Switch to the GHVLJQ�PRGH and position the cursor in cell $�� and create an “$QDO\VLV�*ULG” design item. You assign to the analysis grid the plan query you previously created for the quantity planning of the Sales Managers, with the technical name 6��B$/B��B3ODQTXHU\B��B6$/0$1. Accept the standard settings and also select the setting “$XWR)LW” . You then VDYH the planning application as a ZRUNERRN and assign the description *URXS��B7%:��B%(;B6$/0$1��3OHDVH�QRWH�WKDW�WKLV�TXHU\�LV�NQRZQ�DV�'DWDB3URYLGHUB��LQ�WKH�V\VWHP��,W�ZLOO�EH�UHIHUUHG�WR�LQ�VXEVHTXHQW�WDVNV�

1-1-2 You should now get the message “9DULDEOHV�H[LVW��&KDQJH�WKH�YDULDEOH�YDOXHV” , without the transaction data being displayed. Press the “&KDQJH�9DULDEOH�9DOXHV” button and on the next screen select .�� as the characteristic value for the Fiscal Year variable. You should now see an input-ready planning application with data for the fiscal years 2010 and 2011, which is accessed by the exception you configured (colored in red). Here is an excerpt:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-74

1-1-3 Now switch to the GHVLJQ�PRGH again and position the cursor in cell $�, in

which you create a EXWWRQ�WR�VDYH�GDWD by means of the “ ,QVHUW�%XWWRQ” design item. In the “ Button Text” field you write “6DYH” . You deselect the field “$GMXVW�5DQJH�WR�,WHP�6L]H” . In the 6WDWLF�3DUDPHWHUV area, you select &0' for the field “ Name” , � for the field “ Index” and 6$9(B$5($ for the field “ Value” .

�6DYH your ZRUNERRN�and execute the planning application, setting your variable to ��In the analysis grid area for fiscal year ��, replace the old values for the VDOHV�TXDQWLWLHV with the QHZ�YDOXHV as follows:

6DOHV�TXDQWLW\�LQ�.��LQ�FRPSDQ\�FRGH�;� 2OG�YDOXH 1HZ�YDOXH Sales quantity in .�/�� in company code �� 150 ��Sales quantity in .�/�� in company code �� 250 ��

You must press the “(QWHU” button after entering each value! Position your cursor outside the “$QDO\VLV�*ULG” and then press the “6DYH” button you created.

1-1-4 Now open a VHFRQG�PRGH in parallel and navigate in the /LVW�9LHZHU�to your Realtime InfoProvider 7%:��6�� and check for fiscal year ��, goods group ��and version % whether the data you saved with the BEx Analyszer has appeared.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-75

You should get the following results:

As you see, a delta of 50 units each was saved.

1-1-5 Now go back to the GHVLJQ�PRGH of the BEx Analyzer and insert the design items “/LVW�RI�&RQGLWLRQV” and “/LVW�RI�([FHSWLRQV” which were designed in the Query Designer for this query. Position the cursor in cell $��and select the corresponding design item for ([FHSWLRQV. In the “ DataProvider” field, assign 'DWDB3URYLGHUB�, which is referenced by the query you had selected in the analysis grid design item. � Now position the cursor in cell $��and select the design item for &RQGLWLRQV. Assign the same DataProvider and select “$XWR)LW” . 6DYH your ZRUNERRN again�

1-1-6 Now position the cursor in cell )��and configure the design item “0HVVDJHV” here. On the corresponding *HQHUDO�tab page, you select DOO�ILHOGV, otherwise you leave the standard settings. In cell )� you now write a header for the message area to identify it as such. Write “6\VWHP�PHVVDJHV�” . �6DYH�\RXU�ZRUNERRN�DJDLQ�and execute it for ��. You see that the planned data appears in version B on the granularity of goods group #. Set your &RQGLWLRQ and the ([FHSWLRQ�to LQDFWLYH and VDYH.

1-1-7 You now want to implement a 5HIUHVK�EXWWRQ in your planning folder. For this purpose, you create a “%XWWRQ“ design item in cell $�. In the “ Button Text” field you write “8SGDWH” . 'HVHOHFW�“$GMXVW�5DQJH�WR�,WHP�6L]H” . In the 6WDWLF�3DUDPHWHUV area, you select &0' for the field “ Name” , � for the field “ Index” and &+(&.B9$/8(6 for the field “ Value” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-76

�6DYH your ZRUNERRN��

1-1-8 When you look at your workbook, you see two refresh buttons. The first button is the one you created, and the second looks like this:

and means “ Temporarily interrupt automatic update” . Which refresh activities are triggered by these two buttons: 5HIUHVK�EXWWRQ�FUHDWHG�E\�\RX: The refresh function is called, which means that changed data is transferred from an unput-ready query into the planning buffer. The data is therefore written from the frontend to the backend.

6\VWHP�LFRQ The query data is reloaded from the backend. Therefore, this is a refresh from the backend.

1-1-9 If a workbook has been executed, how do you confirm that if the plan query originally had input-ready cells and you include this plan query in a workbook, that these cells are still input-ready in the workbook? In the query properties (from the context menu, which is called with the right mouse-button), you go to “ Display options” and select “ Allow input of plan values” . In the analysis grid, go to any row and press the right mouse button: query properties, then to the Display options tab page and select “ Allow input of plan values” . This activity can be triggered by the following activites, for example: BEx Analyzer is opened twice, then you lock yourself and are in the BEx in the design mode. Then, once you save the workbook, the display mode is also saved and is retained every time you call the workbook, even after the locked selections are released. The query must therefore be “ released” again for the plan data input.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-77

Perform this activity to ensure that you really will subsequently be able to work with input-ready cells! Can this setting be entered for each analysis grid, or is it only performed once for each workbook? For each workbook.

1-2 In the following section, your aim is to include in the planning application the planning functions for the quantity planning in version B which you set up in an earlier unit. This refers to the distribution function of goods group # to goods groups WAT and JUC, but only for the sales quantity key figure. The distribution factors were modeled as variables. Subsequently, the plan data of goods group WAT was reposted to TWAT for the sales quantity key figure.

1-2-1 You now want to integrate the distribution function into the planning application. In the GHVLJQ�PRGH, position the cursor in cell $�� and create the “%XWWRQ” design item. In the “5DQJH” field, enter �$��%��Select the flag “$GMXVW�5DQJH�WR�,WHP�6L]H” .� For the button properties, you write “)XQFWLRQ��GLVWULEXWLRQ�WR�JRRGV�JURXSV” in the “%XWWRQ�7H[W” field. In the 6WDWLF�3DUDPHWHUV area, you select the following:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-78

1DPH ,QGH[ 9DOXH 3ODQQLQJB)XQFWLRQB1DPH 0 1. �3ODQQLQJB)XQFWLRQ!

2. Info Area: %:�7UDLQLQJ�!�%:�&XVWRPHU�7UDLQLQJ��!�%:��%,�,QWHJUDWHG�3ODQQLQJ��!��%:��*URXS�� 3. Select aggregation level 6��B$/B��4. Button “2SHQ” 3. Select the function 6��B3)B��5. Button “2SHQ”

'DWDB3URYLGHUB)LOWHU 0 'DWDB3URYLGHUB�

&0' 0 ([HFXWHB3ODQQLQJB)XQFWLRQ

As you see, the BEx Analyzer uses the selection for the execution of the planning function that is contained in the query, and not the filter that was created for this function in the Planning Modeler. As you see, we are not going to deal here with the sequence relating to this function that was created in the Planning Modeler. This procedure will be shown at another time. The configuration of the button for calling the plan function should look like this:

6DYH your ZRUNERRN� You now execute the�GLVWULEXWLRQ�IDFWRU for the fiscal year ��. An excerpt of the data before the distribution:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-79

An excerpt of the data after the distribution:

As you see, the distribution is performed for all fiscal years! The distribution is performed on the basis of the default values of the distribution variables! Do not�VDYH the WUDQVDFWLRQ�GDWD created and leave the BEx Analyzer without saving the VHWWLQJV�DQG�GDWD, in order to empty the working memory and thus be able to reverse the function. Then you open your workbook again and press the refresh button of the BEx Analyzer, “7HPSRUDULO\�LQWHUUXSW�DXWRPDWLF�XSGDWH” so that the buffer no longer contains the distributed data, but rather the original data before the distribution.

1-2-2 Now open a second mode and call the ORFNLQJ�VHUYLFH by means of transaction 563/6(. Select InfoProvider 6��B$/B�� and display the locked selections. You should see the following:��

If you now executed the distribution function again (please do not execute it), no additional locked segment would result. If you look at the analysis grid, in the data columns you see the restricted key figures, which consist of the key figure itself and the fiscal year. If the fiscal year in the underlying query was not also additionally restricted by means of the variable in the “ characteristic restrictions” , for which fiscal year would the planning function be executed, and why? Executed for all fiscal years because the filters from the planning model cannot

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-80

be stored in the configuration of a BEx button yet. The restrictions in the kex figures are ignored. Delete the mode for the locking service.

1-2-3 In the planning function, the distribution variables had the default setting 1:1 and were not queried any more when the distribution function was executed. The distribution variables for Water and Juice had the following names: 6��B9$5B'LVWULEB.(<:$7�6��B9$5B'LVWULEB.(<-8&��You now want to implement a variable query for the decentral controlling of variables. In the design mode, go to cell $��, in which you had positioned the “ Button” design item for your distribution function, and add �8��:�� to the “&RPPDQG�5DQJH” . (U and W are written in upper case).

Then navigate to cell 8�� and enter the following:

� 8 9 :

�� 9$5B1DPHB� �� 6��B9$5B'LVWULEB.(<:$7

�� 9$5B9DOXHB� ��

�� 9$5B1DPHB� �� 6��B9$5B'LVWULEB.(<-8&

�� 9$5B9DOXHB� ��

Then you position the cursor in cell $�� and write the following text: “9DULDEOH�IRU�GLVWULEXWLRQ�IDFWRU�:DWHU�” Now position the cursor in cell $�� and write the following: “9DULDEOH�IRU�GLVWULEXWLRQ�IDFWRU�-XLFH:” The distribution factors, which are entered manually, are entered later on in cells C16 and C18 respectively. Now position the cursor again in cells :��and :��, and in each cell enter a reference to the cells in which you later want to enter the distribution factors manually. The following should now be appearing in the area U13 to W16:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-81

� 8 9 :

�� VAR_Name_0 0 S##_VAR_Distrib_KeyWAT

�� VAR_Value_0 0 �&��

�� VAR_Name_1 0 S##_VAR_Distrib_KeyJUC

�� VAR_Value_1 0 �&��

In cell &��you now enter distribution factor � and in cell &��distribution factor �. 6DYH your workbook� Please note: So that the end user will not see the variable table in the area U to W, you must hide columns U to W, but you do not do this yet because this area will be required in subsequent tasks! They are only hidden at the end!

�6DYH� the ZRUNERRN and stay in the execution mode.

1-2-4 Now�H[HFXWH the GLVWULEXWLRQ�IXQFWLRQ for factors 2 and 3, which have already been set. Before the distribution:

After the distribution:

6DYH the SODQ�GDWD. Which setting in the YDULDEOH�ZL]DUG makes the system use the manual entry instead of the default of 1 that was set in the Planning Modeler for both variables? To enable this, the variable must be “ ready for input” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-82

6DYH the SODQ�GDWD.

Your InfoProvider now contains the following plan data for version B:

1-2-5 You now want to integrate the UHSRVWLQJ�IXQFWLRQ�IRU�JRRGV�JURXS�:$7�WR�

JRRGV�JURXS�7:$7 into the planning application. To implement the reposting function, switch to the GHVLJQ�PRGH and position the cursor in cell $�� and create a “%XWWRQ” design item. In the “%XWWRQ�7H[W” field you enter the text “)XQFWLRQ��5HSRVW�**�:$7��!�7:$7” . Select the flag�“$GMXVW�5DQJH�WR�,WHP�6L]H” . For the field “5DQJH” , you write “ �$��%��” . Select�“$GMXVW�5DQJH�WR�,WHP�6L]H” . Assign the following:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-83

1DPH ,QGH[ 9DOXH Planning_Function_Name 0 1. �3ODQQLQJB)XQFWLRQ!

2. Info Area: %:�7UDLQLQJ�!�%:�� &XVWRPHU�7UDLQLQJ��!�%:��%,�,QWHJUDWHG�3ODQQLQJ��!��%:��*URXS�� 3. Select aggregation level 6��B$/B��4. Button “2SHQ” 3. Select the function 6��B3)B��5. Button “2SHQ”

Data_Provider_Filter 0 'DWDB3URYLGHUB�

CMD 0 ([HFXWHB3ODQQLQJB)XQFWLRQ

6DYH the workbook and H[HFXWH the UHSRVWLQJ�IXQFWLRQ in the planning application. If a variable request appears, choose fiscal year ��.

�You should now see your plan data represented as follows – An excerpt of the data before the distribution:

You should now see your plan data represented as follows – An excerpt of the data after the distribution:

Now�VDYH�the�SODQ�GDWD�in the�InfoProvider.

The InfoProvider should now contain the following data for version B

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-84

1-2-6 Based on the query executed, you now add to row $� the following text:

“4XDQWLW\�SODQQLQJ�RI�WKH�6DOHV�0DQDJHU” . For this text, you select font size �� and the color UHG and make the text EROG. 6DYH the workbook. At this point, the quantity planning of the Sales Managers in Version B is complete for goods groups TWAT and JUC!

1-3 In the following section, the SULFH�SODQQLQJ�RI�WKH�6DOHV�0DQDJHUV is integrated into the workbook, both the plan query and the planning function for copying from version B1 to version B2, the conversion function with the two conversion variables, the delete function for version B2 and the copy function to version B2, which contains one variable.

1-3-1 First you write “3ULFH�SODQQLQJ�RI�WKH�6DOHV�0DQDJHUV” in cell $�� and select font size �� and color UHG to highlight the header. Make the text EROG.

1-3-2 Now you create the design item “$QDO\VLV�*ULG” in cell $�� Here you select the plan query of the price planning 7%:��B3��B$/��B34��B6$/0$1 and also the setting “$XWR)LW” . 7KH�TXHU\�LV�VXEVHTXHQWO\�UHIHUHQFHG�DV�'DWDB3URYLGHUB�� 6DYH�your workbook again�and execute it for ��. The prices and the costs of goods manufactured in version B were already planned for you! Here is an excerpt of what you should see:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-85

1-3-3� ,Q the following section, the planner is provided with the copy and delete functions by means of an ([FHO�GURSGRZQ�ER[. First you must create the design item “%XWWRQ” in cell $�� and configure it there as follows: In the “5DQJH” field you write: �$��$��. In the “%XWWRQ�7H[W” field you write “([HFXWH�SODQQLQJ�IXQFWLRQ” . Select�“$GMXVW�5DQJH�WR�,WHP�6L]H” . In the 6WDWLF�3DUDPHWHUV area, you select the following:

1DPH ,QGH[ 9DOXH 'DWDB3URYLGHUB)LOWHU 0 'DWDB3URYLGHUB�

&0' 0 ([HFXWHB3ODQQLQJB)XQFWLRQ

In the “&RPPDQG�5DQJH” you write �&��(�� Now position the cursor in cell &��and write 3/$11,1*B)81&7,21B1$0( in this cell. In cell '�� you enter “ �” .

Before you position an Excel dropdown box in cell E45, you first have to list the technical names of the desired planning functions below one another in cells *�� to *�� In cells +�� to +�� you then enter the respective descriptions. Enter the following:

� * +

�� 3��B3)B�� &RS\�IURP�YHUVLRQ�%��!�%�

�� 3��B3)B�� 'HOHWH�WKH�GDWD�ZLWKLQ�YHUVLRQ�%�

1-3-4 Afterwards position the cursor in cell *��and write “)RU�FODULILFDWLRQ�” . Make the text EROG�and XQGHUOLQH it.��Now position the cursor in cell (��and write “6HOHFW�WKH�GHVLUHG�SODQQLQJ�IXQFWLRQ�” .�Make the text EROG and XQGHUOLQH it.��Now you create the ([FHO�GURSGRZQ�ER[ in cell (��. To do this, you position the cursor in the cell, and in Excel you select the menu path 'DWD��!�9DOLGDWLRQ« . On the next screen, you must enter /LVW in the “$OORZ” field and in the “6RXUFH” area you reference the area with the WHFKQLFDO name of the planning function,

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-86

which means that you select �*��*�� here. Do not change any of the other settings on the screen. You now hide the content of cells &��WR�'�� by using Excel to change the WH[W in this area to ZKLWH�instead of black. Now�VDYH�your workbook, set the variable of the fiscal year to ��and click with the cursor in cell�(��. You should now see the Excel dropdown box that you always see when you click on the cell! Open the Excel dropdown box and check whether both functions were offered. Then H[HFXWH the FRS\�IXQFWLRQ�IURP�YHUVLRQ�%��!�%�.��You should receive the following display - before copying (here is an excerpt):


'R�QRW�VDYH�the SODQ�GDWD. Afterwards, you return to the GHVLJQ�PRGH and navigate again to the button of cell &��. Here, in the “5DQJH” of the button, you write �$��%�� instead of �$��$�� so that the description of the button will be completely visible later. You also select�“$GMXVW�5DQJH�WR�,WHP�6L]H” . SOLUTION FOR OPTIONAL EXERCISE

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-87

1-3-5 You now have to model the two functions, conversion and copy to B, with variables. First, you implement the FRQYHUVLRQ�IXQFWLRQ, which includes two variables: 3��B9$5B5(9B&2*6B7:$7� 3��B9$5B5(9B&2*6B-8&��The technical name of the planning function is: 3��B3)B��To do this, create a new “EXWWRQ” design item in cell $�� and configure it as follows: “ Range” : �$��%�� “ Button Text” : )XQFWLRQ��&RQYHUVLRQ�LQ�YHUVLRQ�%��Select:�� “$GMXVW�5DQJH�WR�,WHP�6L]H” �

Afterwards position the cursor in cell *��and write “)RU�FODULILFDWLRQ�” . Make the text EROG�and XQGHUOLQH it.��Now position the cursor in cell (��and write “6HOHFW�WKH�GHVLUHG�SODQQLQJ�IXQFWLRQ�” .�Make the text EROG and XQGHUOLQH it.��Now you create the ([FHO�GURSGRZQ�ER[ in cell (��. To do this, you position the cursor in the cell, and in Excel you select the menu path 'DWD��!�9DOLGDWLRQ« .

On the next screen, you must enter /LVW in the “$OORZ“ field and in the “6RXUFH” area you reference the area with the WHFKQLFDO name of the planning function, which means that you select �*��*�� here. Do not change any of the other settings on the screen.

You now hide the content of cells &��WR�'�� by using Excel to change the WH[W in this area to ZKLWH�instead of black. Now�VDYH�your workbook, set the variable of the fiscal year to ��and click with the cursor in cell�(��. You should now see the Excel dropdown box that you always see when you click on the cell! Open the Excel dropdown box and check whether both functions were offered. Then H[HFXWH the FRS\�IXQFWLRQ�IURP�YHUVLRQ�%��!�%�.��You should receive the following display - before copying (here is an excerpt):

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-88


'R�QRW�VDYH�the SODQ�GDWD. Afterwards, you return to the GHVLJQ�PRGH and navigate again to the button of cell &��. Here, in the “5DQJH” of the button, you write �$��%�� instead of �$��$�� so that the description of the button will be completely visible later. You also select�“$GMXVW�5DQJH�WR�,WHP�6L]H” . SOLUTION FOR OPTIONAL EXERCISE

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-89

You now have to model the two functions, conversion and copy to B, with variables. First, you implement the FRQYHUVLRQ�IXQFWLRQ, which includes two variables: 3��B9$5B5(9B&2*6B7:$7� 3��B9$5B5(9B&2*6B-8&��The technical name of the planning function is: 3��B3)B��To do this, create a new “EXWWRQ” design item in cell $�� and configure it as follows: “ Range” : �$��%�� “ Button Text” : )XQFWLRQ��&RQYHUVLRQ�LQ�YHUVLRQ�%��Seleect:�� “$GMXVW�5DQJH�WR�,WHP�6L]H” �


2. Info Area: %:�7UDLQLQJ�!�%:�&XVWRPHU�7UDLQLQJ��!�%:��%,�,QWHJUDWHG�3ODQQLQJ��!��%:��*URXS�� 3. Select aggregation level 3��B$/B��4. Button “2SHQ“ 3. Select the function 3��B3)B��5. Button “2SHQ“


CMD 0 Execute_Planning_Function

“ Command Range” :�� 8��:�� Now navigate into cell 8��and make the entries shown in the following table:

� 8 9 :

�� VAR_Name_0 0 3��B9$5B5(9B&2*6B7:$7

�� VAR_Value_0 0 �&��

�� VAR_Name_1 0 3��B9$5B5(9B&2*6B-8&

�� VAR_Value_1 0 �&��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-90

Now navigate to cell $�� and enter the following text: “9DULDEOH�IRU�FRQYHUWLQJ�WDEOH�ZDWHU�LQ�YHUVLRQ�%�� ” �

Now navigate to cell $�� and enter the following text: “9DULDEOH�IRU�FRQYHUWLQJ�MXLFH�LQ�YHUVLRQ�%��” �

In cell &��you now enter distribution factor � and in cell &��distribution factor �. Both values are already percentage values.

Now VDYH�the workbook and then execute the FRQYHUVLRQ�IXQFWLRQ for the variables set.

You should receive the following result - before the conversion (here is an excerpt):

You should receive the following result - after the conversion (here is an excerpt):

'R�QRW�VDYH your�SODQ�GDWD�

1-3-6 Because the planners want to edit the data manually after it is copied and converted in version B2, you should enter �� instead of 10.2 for the column 3ULFH�Version B2 for�-XLFH in��DQG��, and �� instead of 21 for 7DEOH�ZDWHU in ��DQG��. Do not change the cost of goods manufactured. After entering the plan data, take a look at the “ result rows“ . You see that at runtime, no plan data totaling was performed. When you press the “ Refresh” button that you created, the totaling is still not performed. So you position the cursor on a result row and use the right mouse-button to select “7UDQVIHU�YDOXHV” . You obtain the following data situation:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-91

6DYH the SODQ�GDWD.

Please note that you can use the Excel dropdown box to select the planning function P##_PF_03 at any time. You can use this function to reset the data planned in version B2 at any time. This resetting must be planned in the design phase.

If necessary, use this function and go through the planning of the Sales Managers again! Go to the GHVLJQ�PRGH again.

1-3-7 Explain how the “ ,QGH[” is used within the “%XWWRQ” design item. The index value enables you to sequentially process multiple functions by pressing one button. The commands are executed in the sequence of the increasing index values. Complete the following table if the subsequent functions are to be used in accordance with the usage of the index:

Name Index Value

DATA_PROVIDER_FILTER 1 DATA_Provider_1

PLANNING_FUNCTION_NAME 1 COPY_GROUP##

CMD 1 EXECUTE_PLANNING_FUNCTION

DATA_PROVIDER_FILTER 2 DATA_Provider_1

PLANNING_FUNCTION_NAME 2 REVALUATE_GROUP##


CMD 3 SAVE_AREA

Instead of 1, 2 and 3 you can also use the index values 0, 1 and 2.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-92

1-3-8 Now you want to include the FRS\�IXQFWLRQ�IURP�YHUVLRQ�"��!�% with the technical name 3��B3)B�� and the variables 3��B9$5B6HQGHUYHUVLRQBFRS\ in the workbook. Here the end user once again uses an Excel dropdown box to select the two possible sender versions. First create the “%XWWRQ” design item for cell�$��and configure it as follows: ” Range” : �$��%�� “ Button Text” : � )XQFWLRQ��FRS\�YHUVLRQ�"�!�% “ Command Range” : �$��&�� Select “$GMXVW�5DQJH�WR�,WHP�6L]H” .


2. Info Area: %:�7UDLQLQJ�!�%:�&XVWRPHU�7UDLQLQJ��!�%:��%,�,QWHJUDWHG�3ODQQLQJ��!��%:��*URXS�� 3. Select aggregation level 3��B$/B��4. Button “2SHQ” 3. Select the function 3��B3)B��5. Button “2SHQ”


9$5B1$0( �� 3��B9$5B6(1'(59(56,21B&23<��PDQXDO�HQWU\�

CMD 0 (;(&87(B3/$11,1*B)81&7,21

Now position your cursor in cell $�� and write 9$5B9$/8( there. Then go to cell %��and write “ �” . Now you KLGH�ERWK�FHOOV, by changing the FRORU�RI�WKH�WH[W to ZKLWH. Now navigate to cell�8�� and write “9HUVLRQV�IRU�FRS\�IXQFWLRQ� ”

Now position your cursor in cell 8�� and write %� there. In cell 8�� you write %�. You have now created a list of the characteristic values that can be selected by means of the subsequent Excel dropdown box. This area is again to be hidden from the end user, but this is only performed at the end of the exercise block. Now you have to create an ([FHO�GURSGRZQ�ER[ for selecting the versions. Now position the cursor in cell &��and enter: “6HOHFW�WKH�VHQGHU�YHUVLRQ�” . In cell &�� you create an ([FHO�GURSGRZQ�ER[, as shown before,

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-93

which references area �8��8��, which is the manually created list of variable selections.

1-3-9 6DYH�your ZRUNERRN and execute it. For the copy function just created, select sender version %� and execute the copy process to version %. Representation before copying (here is an excerpt):

Representation after copying (here is an excerpt):

You then�VDYH�your SODQ�GDWD� The price planning is now complete. Subsequent planning sessions only refer to the data of version B.

Your InfoProvider should now contain the following data records for versions B1, B2 and B:

Under the analysis grids you should find a row outlined in black, which is used to DGG�QHZ�URZV:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-94

For which setting in the query does it make sense to use this function, and why can the function not be used here? This setting makes sense if “ posted values” or “ characteristic relationships” was chosen for the properties of the cell characteristics. This is not possible here because the data range was restricted to the fiscal years 2010 and 2011. How do you proceed if you want to enter new rows? Use the F4 button or manual entries. What do you have to consider if the property “ key and text” was selected for a characteristic of the “ row” of the query, when you want to use the function? You either select the key and text using F4, or you enter them manually in the sequence set – text [key] or [key] text.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-95

1-4 Now you want to start an ([FHO�RIIOLQH�SODQQLQJ example, in which you determine the price of the table water in version B1 in fiscal year 2010 on the basis of the cost of goods manufactured and a profit percentage, performing this in an additional calculation in the local Excel. Then the price thus determined will be transferred to the workbook of the BEx Analyzer.

1-4-1 You are in the execution mode of your workbook *URXS��B7%:��B%(;B6$/0$1, and you save it on drive 1 of your computer. Give the file the following name: *URXS��B7%:��B([FHOB2IIOLQHB6$/0$1 and save it in the format “0LFURVRIW�2IILFH�([FHO�:RUNERRN” . 6DYH and FORVH your ZRUNERRN�LQ�WKH�%([�$QDO\]HU in order to avoid locking, then open the file in the local Excel. You get there by logging on to the BEx Analyzer again: 6WDUW�±!�3URJUDPV��!�%XVLQHVV�([SORUHU��!�$QDO\]HU. Then you press the Excel button “2SHQ” and select the file named above. When you open the file, the “ Security Warning” screen opens. Now select “'LVDEOH�0DFURV” so that you can access Microsoft Excel without a BI add-in!

1-4-2 Now position the cursor in cell $�� and enter the following text: “$GGLWLRQDO�FDOFXODWLRQ��FDOFXODWLRQ�RI�WKH�VDOHV�SULFH�LQ�YHUVLRQ�%��” . Then position your cursor in cell $�� and write: “([DPSOH�IRU�WDEOH�ZDWHU” . In cell $��write “0DQXIDFWXULQJ�FRVWV” and in cell $��“3URILW�SHUFHQWDJH” . In cell�$�� write “3ODQ�SULFH�IRU�7:$7�LQ�YHUVLRQ�%��DQG��” . Position the cursor in cell�&�� and format this cell with Excel tools so that “1XPEHU” and “'HFLPDO�3ODFHV” “ �” is set with variant “ ��” , so that only absolute values can be entered in the cell! Then enter the profit percentage factor “ ��” in this cell. Now go to cell '��and�UHIHUHQFH cell “*��” , in which the manufacturing costs for 7:$7�and %� in ��are located. Then go to cell '��and store the formula for the profit percentage: “ '�� &��” . In cell '��you write the formula for plan data to be calculated as follows: “ '��'��” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 7-96

Now the calculated value in cell�'�� must be transferred to the corresponding cell for (TWAT, 2010, B1).

To do this, you position the cursor in cell '�� and reference as follows: “ ='��” . This procedure ensures that the start value of the calculation, namely the manufacturing costs, is planned manually, and the corresponding prices are obtained from an additional calculation. Therefore, in cell *�� you enter the value � for the manufacturing costs and then press Enter. You should then get 24 for the corresponding price in cell '��. You now use an�([FHO�IUDPH�to�RXWOLQH�area $�� to '�� and select for this area the text color “5HG” and “%ROG” . Save the Excel offline planning using the Excel save button “6DYH” .

1-4-3 Now you have two independent workbooks, and the result of the additional calculation in cell '�� of the Excel offline planning must be transferred back into the BEx workbook *URXS��B7%:��B%(;B6$/0$1. In the project, you would use a macro for this purpose. Instead, we will transfer the cell value manually using &RS\�DQG�3DVWH. To do this, you open the Excel offline planning and the above-named BEx workbook in parallel. First position your cursor in cell '�� of the ([FHO�RIIOLQH�SODQQLQJ and press the “&75/” and “&” keys on your keyboard at the same time. Then, within the %(;�ZRUNERRN� you go to cell '�� and write “ ” in order to create a reference; you then press “&75/” and “9” at the same time to insert the value copied from the Excel offline planning into the cell. The entry “ ��” should now appear in the Excel cell. 'R�QRW�VDYH�the SODQ�GDWD. 6DYH�the ([FHO�RIIOLQH�SODQQLQJ�and then leave it. Please note that if you want to refresh, you must not choose the system icon

, because this would cause the server to overwrite the frontend data. You can only use the “ Refresh” button you created yourself to update the data planned by means of the frontend.

This concludes the price planning of the Sales Managers. Now�FORVH the ZRUNERRN of the BEx Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-1

SAP AG 2006

&RQWHQW�� 'HVLJQ�RI�DQ�,QIR3URYLGHU� 0XOWL3URYLGHU�LQ�3ODQQLQJ� $XWKRUL]DWLRQ�2EMHFWV�LQ�3ODQQLQJ

0RGHOLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-2

SAP AG 2006

0RGHOLQJ��7RSLF�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�8QGHUVWDQG�WKH�³NH\�ILJXUH�PRGHO´�DQG�³DFFRXQW�PRGHO´�PRGHOLQJ8QGHUVWDQG�PRGHOLQJ�FRQFHSWV�IRU�WKH�0XOWL3URYLGHU8QGHUVWDQG�WKH�DXWKRUL]DWLRQ�REMHFWV�LQ�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-3

SAP AG 2006

0RGHOLQJ��2YHUYLHZ 'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-4

SAP AG 2006

0RGHOLQJ��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�IRU�LPSOHPHQWLQJ�WKH�%:�LQWHJUDWHG�SODQQLQJ��DQG�\RX�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�PRGHOLQJ�RI�,QIR3URYLGHUV DQG�DOWHUQDWLYH�VFHQDULRV�IRU�0XOWL3URYLGHUV�

� <RX�DOVR�ZDQW�WR�JHW�DQ�RYHUYLHZ�RI�WKH�DXWKRUL]DWLRQ�FRQFHSWV�RI�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-5

SAP AG 2006

0RGHOLQJ��8QLW�2YHUYLHZ�'LDJUDP

8QLW�2YHUYLHZ� /HVVRQ��'HVLJQ�RI�DQ�,QIR3URYLGHU� /HVVRQ��0XOWL3URYLGHU LQ�3ODQQLQJ� /HVVRQ��$XWKRUL]DWLRQ�2EMHFWV�LQ�3ODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-6

SAP AG 2006

'HVLJQ�RI�DQ�,QIR3URYLGHU��7RSLF�2EMHFWLYHV

'LIIHUHQWLDWH�EHWZHHQ�D�NH\�ILJXUH�PRGHO�DQG�DQ�DFFRXQW�PRGHO/LVW�WKH�DGYDQWDJHV�DQG�GLVDGYDQWDJHV�RI�ERWK�PRGHOLQJ�DSSURDFKHV$VVHVV�WKH�SHUIRUPDQFH�DVSHFWV�RI�ERWK�PRGHOLQJ�DSSURDFKHV

%\�WKH�FRQFOXVLRQ�RI�WKLV�8QLW��\RX�ZLOO�EH�DEOH�WR�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-7

SAP AG 2006

'HVLJQ�RI�DQ�,QIR3URYLGHU��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�DOWHUQDWLYH�PRGHOLQJV RI�WKH�,QIR3URYLGHU�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-8

SAP AG 2006

'DWD�0RGHOLQJ��.H\�)LJXUH�0RGHO�DQG�$FFRXQW�0RGHO�

��3�0HDQ SULFH0DQXI��SULFH6DOHV�SULFH3URGXFW

.H\�)LJXUH�0RGHO

$FFRXQW�0RGHO

��0HDQ SULFH3��0DQXI��SULFH3��6DOHV�SULFH3�3ULFH3ULFH�FDW�3URGXFW

$OO�NH\�ILJXUHV�DUH�LQ�D�GDWD�UHFRUG

7KH�SULFH�FDWHJRU\�FKDUDFWHULVWLF�UHSODFHV�WKH�NH\�ILJXUHV�RI�WKH�NH\�ILJXUH�PRGHO��QDPHO\�LQ�FRQQHFWLRQ�ZLWK�RQH�VLQJOH�NH\�ILJXUH

�

� You can approach the planning with two different modeling strategies, although you must already decide

which of the modeling versions you want to use, the “NH\�ILJXUH�PRGHO” or the “DFFRXQW�PRGHO”, when you are creating an InfoProvider.

� The above illustration uses a simple example to show how the terms key figure model and account

model are defined. �

You should use the NH\�ILJXUH�PRGHO when

y you are working with a limited, and in particular a constant, number of key figures and

y all or at least a large proportion of these key figures of a data record are also used in the other data records.

� You should use the DFFRXQW�PRGHO when

y you are working with a high, and in particular a varying, number of key figures and

y most of the key figures within a data record would be empty in the key figure model. �

It is easy to add another price category (see example above) in the account model, because the data structure does not have to be changed. In the key figure model, on the other hand, an additional key figure must be added to the InfoProvider. The extent to which this difference can be seen as an advantage or disadvantage largely depends on the frequency with which the changes are to be expected.

� If your planning project requires this, you can of course also use different data models in different

InfoProviders. In this case, you can convert or transfer data from one data model to another, for example using FOX formulas, which carry out an assignment of the respective combinations.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-9

SAP AG 2006

3HUIRUPDQFH�DQG�5HTXLUHG�0HPRU\

5HDGLQJ�WLPHGHSHQGV�PRUH�RQ�WKH�QXPEHU�RI�GDWD�UHFRUGV�WKDQ�RQ�WKHLU�OHQJWK

0HPRU\�UHTXLUHPHQW�RI�WKH�DSSOLFDWLRQ�VHUYHUGHSHQGV�HTXDOO\�RQ�WKH�QXPEHU�DQG�OHQJWK�RI�WKH�GDWD�UHFRUGV

7KH�GHFLVLRQ�³NH\�ILJXUH�PRGHO�RU�DFFRXQW�PRGHO´�VKRXOG�JHQHUDOO\�EH�EDVHG�RQ�ZKLFK�PRGHO�LV�EHWWHU�VXLWHG�WR�WKH�UHVSHFWLYH�SODQQLQJ�SURFHVV��

�

� The transaction data is stored in the BW system. Investigations have shown that the UHDGLQJ�WLPH�ODUJHO\�GHSHQGV�RQ�WKH�QXPEHU�DQG�QRW�WKH�VL]H�RI�WKH�GDWD�UHFRUGV.

� The previous example shows that a switch from the key figure model to the account model increases the number of data records by a factor of 3, resulting in longer reading times. The increase factor depends on whether all key figures are used in every data record in the key figure model, because if you switch to the account model, only those data records are created for which the key figure is not equal to zero.

� The transaction data is VWRUHG�LQ�WKH�PDLQ�PHPRU\�RI�WKH�DSSOLFDWLRQ�VHUYHU�DIWHU�LW�LV�UHDG�IURP�WKH�%:�V\VWHP. The amount of memory required GHSHQGV��DPRQJ�RWKHU�WKLQJV��RQ�WKH�QXPEHU�DQG�OHQJWK�RI�WKH�GDWD�UHFRUGV, whereby the length is influenced by the selection of the data model: in the NH\�ILJXUH�PRGHO, the data records are longer than in the account model, and they therefore UHTXLUH�PRUH�PHPRU\�SHU�GDWD�UHFRUG.

� 'HSHQGLQJ�RQ�WKH�UHODWLRQVKLS�EHWZHHQ�WKH�GDWD�UHFRUG�OHQJWK�DQG�QXPEHU��HLWKHU�WKH�NH\�ILJXUH�PRGHO�RU�WKH�DFFRXQW�PRGHO�ZLOO�WDNH�XS�OHVV�PHPRU\�

� The SHUIRUPDQFH�RI�D�SODQQLQJ�IXQFWLRQ strongly depends on the QXPEHU�RI�GDWD�UHFRUGV. Therefore, it should be possible to execute it faster in a key figure-based model than in an account-based model. On the other hand, the data records in a key figure model can also become large, which also has an impact on performance. Thus a planning function sometimes can be slower in the key figure-based model.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-10

SAP AG 2006

'LUHFW�&RPSDULVRQ�RI�.H\�)LJXUH�0RGHO�DQG�$FFRXQW�0RGHO��

,QIR3URYLGHU UHTXLUHV�D�ODUJH�QXPEHU�RI�NH\�ILJXUHV��ZKLOH�D�PD[LPXP�RI��NH\�ILJXUHV�FDQ�EH�LQFOXGHG�SHU�,QIR3URYLGHU�

)RUPXODV�DUH�HDV\�WR�FUHDWH�

$�VHSDUDWH�NH\�ILJXUH�LV�UHTXLUHG�IRU�HYHU\�DFFRXQW�DQG�WRWDOLQJ�OHYHO��

&UHDWLRQ�RI�NH\�ILJXUHV�IRU�VSHFLILF�XVDJH�

7KH�VXEVHTXHQW�FUHDWLRQ�RI�NH\�ILJXUHV��DQG�WKH�UHPRYDO�DQG�DGGLWLRQ�RI�NH\�ILJXUHV�LQ�DQ�,QIR3URYLGHU LV�WLPH�FRQVXPLQJ��

1R�NH\�ILJXUH�� FKDUDFWHULVWLF�YDOXH�UHODWLRQVKLS�KDV�WR�EH�PRGHOHG

3RVVLEOH�SHUIRUPDQFH�ORVVHV�GXH�WR�ODUJHU�GDWD�UHFRUGV�LQ�GDWDEDVH�WDEOHV�DQG�SODQQLQJ�EXIIHUV

7KH�SODQ�TXHU\�VWUXFWXUH�LV�HDV\�WR�FUHDWH

&21352

.H\�)LJXUH�0RGHO

�

� The following table lists the advantages and disadvantages of the key figure model.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-11

SAP AG 2006

'LUHFW�&RPSDULVRQ�RI�.H\�)LJXUH�0RGHO�DQG�$FFRXQW�0RGHO��

$FFRXQW�0RGHO

/HVV�,QIR2EMHFWV WR�EXLOG�IRU�WKH�,QIR&XEH

3RVVLEOH�SHUIRUPDQFH�ORVVHV�GXH�WR�PRUH�GDWD�UHFRUGV�LQ�GDWDEDVH�WDEOHV�DQG�SODQQLQJ�EXIIHUV

$GYDQWDJHV�RI�XVLQJ�FKDUDFWHULVWLF�KLHUDUFKLHV�LQ�TXHULHV�E\�VLPSO\�DGGLQJ�WKH�KLHUDUFK\�QRGH

)HZHU�FROXPQV�LQ�WKH�IODW�ILOH0RGLILFDWLRQV�GXULQJ�FRQILJXUDWLRQ�DUH�VLPSOHU��6LPSO\�DGG�D�KLHUDUFK\�QRGH�RU�D�FKDUDFWHULVWLF�LQ�%:�

$FFRXQW�PDVWHU�GDWD�PXVW�EH�ORDGHG)HZHU�NH\�ILJXUHV�LQ�WKH�,QIR&XEH��IHZHU�FROXPQV�LQ�WKH�IODW�ILOH

&21352

�

� The following table lists the advantages and disadvantages of the account model.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-12

SAP AG 2006

'HVLJQ�RI�DQ�,QIR3URYLGHU��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�'LIIHUHQWLDWH�EHWZHHQ�D�NH\�ILJXUH�PRGHO�DQG�DQ�DFFRXQW�PRGHO/LVW�WKH�DGYDQWDJHV�DQG�GLVDGYDQWDJHV�RI�ERWK�PRGHOLQJ�DSSURDFKHV$VVHVV�WKH�SHUIRUPDQFH�DVSHFWV�RI�ERWK�PRGHOLQJ�DSSURDFKHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-13

SAP AG 2006

0XOWL3URYLGHU LQ�3ODQQLQJ��8QLW�2YHUYLHZ�'LDJUDP


�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-14

SAP AG 2006

0XOWL3URYLGHU LQ�3ODQQLQJ��7RSLF�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�8QGHUVWDQG�FRQFHSWV�IRU�SODQQLQJ�ZLWK�0XOWL3URYLGHUV$VVHVV�WKH�XVH�RI�0XOWL3URYLGHUV DQG�GDWD�WUDQVIHU�SURFHVVHV�IRU�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-15

SAP AG 2006

0XOWL3URYLGHU LQ�3ODQQLQJ��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�DUH�LQWHUHVWHG�LQ�DOWHUQDWLYH�PRGHOLQJ�VFHQDULRV�IRU�SODQQLQJ��<RX�SDUWLFXODUO\�ZDQW�WR�WDNH�D�FORVHU�ORRN�DW�WKH�XVH�RI�0XOWL3URYLGHUV�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-16

SAP AG 2006

0XOWL�3URYLGHUV

��

� ��

,QIR&XEH9LUWXDO3URYLGHU

� ��

$JJUHJDWLRQOHYHO

,QIR2EMHFW 'DWD6WRUHREMHFW ,QIR6HW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-17

SAP AG 2006

$GYDQWDJHV�DQG�'LVDGYDQWDJHV�RI�D�0XOWL3URYLGHU

��! ��"# $&% '

6XEVHTXHQW�LQFOXVLRQ�LQ�WKH�0XOWL3URYLGHU

)LOH�0DQDJHU

'DWD�VHOHFWLRQ�,QIR3URYLGHU�

'DWD�VHOHFWLRQ�,QIR3URYLGHU �

$W�UXQWLPH��VSOLW�ZKLFK�VHOHFWLRQ�UHODWHV�WR�ZKLFK�,QIR3URYLGHU

3DUDOOHO�UHDG�VWDWHPHQWV

�

� MultiProviders are used very often in practice because of their flexibility.

� $Q�DGYDQWDJH is that if new InfoProviders are created, they can very easily be included in the modeling of the MultiProvider, and that the queries already existing for the MultiProvider do not have to be adapted.

� New queries for the MultiProvider with reference to the subsequently integrated InfoProvider can be correctly addressed with reference to the "InfoProvider" field in the query.

� $�GLVDGYDQWDJH�with respect to a simple InfoProvider is that in a MultiProvider scenario, at runtime a split is always effected for all selections, as to which InfoProvider subordinate to the MultiProvider the selection comes from. In contrast to BW-BPS, the related read statements in the BW-integrated planning are not executed sequentially but in parallel, with the aid of the file manager.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-18

SAP AG 2006

0XOWL3URYLGHU LQ�3ODQQLQJ��0RGHOLQJ�,�� 3ODQQLQJ�IXQFWLRQV�DQG�TXHULHV�DUH�ORFDWHG�RQ�DQ�DJJUHJDWLRQ�OHYHO�

� 'DWD�XVHG�E\�SODQQLQJ�IXQFWLRQV�DQG�TXHULHV�KDV�WKH�VDPH�JUDQXODULW\�

5HDO�WLPH�,QIR3URYLGHU ,QIR&XEH 'DWD6WRUH

REMHFW ,QIR2EMHFW

$JJUHJDWLRQOHYHO

0XOWL3URYLGHU

�(�! �&") $% '

3ODQQLQJ�DQG�UHSRUWLQJ�RQ DQ�DJJUHJDWLRQOHYHO

�

� The above illustration shows a first modeling option for MultiProvider.

� As you can see, all the aggregation levels are created on the MultiProvider, so that both the planning - that is, the planning functions - and the plan queries can be set up on the same aggregation level. This reduces the frequency of errors and WKH�JUDQXODULW\�RI�WKH�SODQQHG�DQG�UHSRUWHG�GDWD�LV�WKH�VDPH!

� If reference data is required for the actual status, it can be read from the “ InfoCube” or the “ DataStoreObject” , for example.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-19

SAP AG 2006

0XOWL3URYLGHU LQ�3ODQQLQJ��0RGHOLQJ�,,

5HDO�WLPH�,QIR3URYLGHU ,QIR&XEH

$JJUHJDWLRQOHYHOV

0XOWL3URYLGHU


'DWD�IURP�SODQQLQJ�IXQFWLRQV�DQG�TXHULHV�FDQ�KDYH�GLIIHUHQW�JUDQXODULWLHV�

3ODQQLQJ�RQDJJUHJDWLRQOHYHOV

5HSRUWLQJ�RQ�0XOWL3URYLGHU

�

� The above illustration shows a second modeling option for MultiProvider.

� Here a MultiProvider is placed on at least one aggregation level, but otherwise also additionally on other InfoProviders, so that the above MultiProvider is only suitable for reporting.

� A planning function, on the other hand, must be created on an aggregation level - this is not possible directly on a MultiProvider.

� The advantage of this model approach is that the underlying aggregation levels and other InfoProviders and their data records can have a different granularity.

� Thus the plan data from real-time providers could be planned on a quarterly level, and the actual data of the InfoCube could be kept on a monthly level.

� In a query on the MultiProvider that combines this data, the JUDQXODULWLHV�FRXOG�EH�³PL[HG´, for example by corresponding selection in the data columns of the query.

� 3OHDVH�QRWH�WKDW�PXOWLSOH�DJJUHJDWLRQ�OHYHOV�FDQ�EH�XVHG�LQ�D�TXHU\�VLPXOWDQHRXVO\�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-20

SAP AG 2006

0RGHOLQJ�3UHUHTXLVLWHV�IRU�DQ�,QSXW�5HDG\�3ODQ�4XHU\


6LPSOH�DJJUHJDWLRQ�OHYHO

5HDO�WLPH�,QIR3URYLGHU ,QIR&XEH 'DWD6WRUH

REMHFW ,QIR2EMHFW

*,+.- /!0 1�24365.0 7.892

:<;�= ;�><= ?A@ B

&RPSOH[�DJJUHJDWLRQ�OHYHO

0$1'$725<�

�

� $JJUHJDWLRQ�OHYHOV are used as ,QIR3URYLGHUV IRU�DQ�LQSXW�UHDG\�TXHU\.

� In general, an aggregation level can be defined on a real-time InfoProvider. This is then known as a VLPSOH�DJJUHJDWLRQ�OHYHO.

� If an aggregation level is defined on a MultiProvider, this is known as a FRPSOH[�DJJUHJDWLRQ�OHYHO

y In this case, a simple aggregation level may not be subordinate to a MultiProvider. On the other hand, at least one real-time InfoCube (direct) must be subordinate to the MultiProvider.

� To define an input-ready query, you can choose between two basic models: 1.) Directly on a complex aggregation level 2.) Directly or by means of MultiProvider on a simple query.

� Please note that aggregation levels and MultiProviders FDQQRW be nested, which means that one aggregation level cannot be located in another aggregation level.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-21

SAP AG 2006

6LPSOH�$JJUHJDWLRQ�/HYHOV

C(DEFDG E

EFD.CHDEFD.CHDEFD.CHD

IJCIJCIJC

1LKMC1LKMC1LKNE

1�C1.E1.O

KM243P+6QR�S - 8UT

V�8 S 2I�892 TL0 3�W1P24397P+YXU/ZK[2�3P+6Q1�243L7Z+\X�/

OFDG E

EFD.CHDEFD.CHD

I]CI]C

19KMC19KNE

K[2�3P+6QR�S - 8YT

V�8 S 2I�892�T.0 3�W1�243L7Z+\X�/ZKM2^3Z+.Q

7KH�IROORZLQJ�H[DPSOH�VKRZV�KRZ�WKH�V\VWHP�RSHUDWHV�ZKHQ�D�NH\�ILJXUH�KDV�EHHQ�FKDQJHG��PDQXDOO\�RU�DXWRPDWLFDOO\��

_

1�243L7Z+\X�/

CHDEFD9C#DI`C19KMC

KM2�3P+.QRZS - 8UT

V�8 S 2IP892�TL0 3�W1�2^397Z+\X�/ZKM2^3Z+9Q

)DFW�WDEOH�RI�WKH�UHDO�WLPH�,QIR3URYLGHU

$JJUHJDWLRQ�OHYHO��DJJUHJDWRQ E\�PHDQV�RI�*URXS�6DOHV�NH\�ILJXUH��DJJUHJDWLRQ�680�

'HOWD�UHFRUG�LQ�IDFW�WDEOH�RI�WKH�UHDO�WLPH�,QIR3URYLGHU�!��)RU�SURGXFW�WKDW�ZDV�QRW�LQFOXGHG�LQ�SODQQLQJ�RI�DJJUHJDWLRQ�OHYHO

aPb

�

� A simple aggregation level can only be created on a real-time InfoProvider.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-22

SAP AG 2006

&RPSOH[�$JJUHJDWLRQ�/HYHOV

C(DEFD9C#DI]C1LKcC1�C

1P2436d!0 /V�8 S 2I�8.2 TL0 3PW1P2�3L7�+FX�/�Kc2^3�+6Q1�2^3.7P+YXU/

OFDEFD6CHDIJC19KMC

1P2436d!0 /V�8 S 2I�862�TL0 3�W1�243L7Z+FXU/�Kc2^3�+6Q

7KH�IROORZLQJ�H[DPSOHV�VKRZ�• KRZ�WKH�V\VWHP�HPEHGV�GDWD�UHFRUGV�IURP�WKH�,QIR3URYLGHUV FRQWDLQHG�LQ�D�0XOWL3URYLGHU LQWR�WKH�0XOWL3URYLGHUV DQG�

• KRZ�WKH�V\VWHP�ZULWHV�QHZ�RU�FKDQJHG�GDWD�UHFRUGV�RI�WKH�0XOWL3URYLGHU EDFN�LQWR�WKH�,QIR3URYLGHUV FRQWDLQHG�LQ�WKLV�0XOWL3URYLGHU

egfL��Lh��.��hZ�!hi�4jlk�jZm!��no��pZ�lqr�4jts��u�`�]��f.�]h�jZ�s��u��]�Pf.�JvJ�!�J��s�v]��h�j�� h��)� �uw

N� h�j��hL�Ahx��jik4jZm!�`ng��pP�ryi�4jis��&��N�Zf9�]vJ�&�]��siv]�uh�j�� h��)� �<w

z WUd{3.|N+.}\86Cz WUd{3.|N+.}\8UE

z WUd{3Z1P243\5L0 798.2

C(DOFD

EFD.CHDEFD.CHD

I]CI]C

1.K[C1.K[C

1�C_

1�2^36d!0 /V`8 S 2I�892�T90 3�W1Z2^3.7P+YXU/ZK[2�3P+.Q1�24397�+YXU/ ~ hL�<ht�<�PfZ�]��t��j��P�� !�� `��j��)�L��h�v�v]��vPhZ�� Jjl� �L�P��.��m�&�Z�t�r�� u�� P�

7KH�RULJLQ�RI�WKH�GDWD�UHFRUG�LV�DOZD\V�NQRZQ:KHQ�\RX�ZDQW�WR�FUHDWH�QHZ�GDWD�UHFRUGV�LQ�PDQXDO�SODQQLQJ�RU�E\�PHDQV�RI�SODQQLQJ�IXQFWLRQV��\RX�KDYH�WR�PRGHO�WKH�,QIR3URYLGHU FKDUDFWHULVWLF�DV�ZHOO�

�

� In the case of a PRUH�FRPSOH[�DJJUHJDWLRQ�OHYHO that is created on a MultiProvider (compare the figure “ Modeling Prerequisites for an Input-Ready Plan Query” ), the above figure shows that in the related aggregation levels, the �,QIR3URYLGHU��FKDUDFWHULVWLF must always be included in order to enable the reading and writing of data on a source-related basis.

� This characteristic of the MultiProvider enables you, for example, to copy actual data from one InfoProvider to another, whereby the copy function for the aggregation level of the MultiProvider must be created, of course.

� 7KH�0XOWL3URYLGHU�WHFKQRORJ\�LV�WKXV�DQ�RSWLRQ�LQ�%:�LQWHJUDWHG�SODQQLQJ�IRU�WKH�FURVV�,QIR3URYLGHU�SURFHVVLQJ�RI�GDWD�

� It is a prerequisite that the target InfoProvider must be a real-time InfoProvider.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-23

SAP AG 2006

0RGHOLQJ�WKH�6WRUDJH�RI�3ODQQHG�DQG�$FWXDO�'DWD

6HSDUDWH�'DWD�6WRUDJH 6KDUHG�'DWD�6WRUDJH

$FWXDO�GDWD

3ODQ�GDWD

3ODQQLQJ5HSRUWLQJ

$FWXDO�DQG�SODQ�GDWD

+RZ�ZDV�WKH�SODQ�GDWD�SXW�LQWR�WKH�,QIR3URYLGHU"�

'73&RS\IXQFWLRQ

3ODQQLQJ5HSRUWLQJ

3ODQ

3ODQ$FWXDO

$FWXDO

�

� $GYDQWDJHV�RI�VHSDUDWH�GDWD�VWRUDJH�

y No duplicate data storage

y Lower administrative overhead

y Is used when actual and plan data are structurally very similar, whereby the granularity of the actual or plan data can be finer or coarser

� 'LVDGYDQWDJHV�RI�VHSDUDWH�GDWD�VWRUDJH�

y Reporting is difficult if the granularity of actual and plan data differs too greatly �

$GYDQWDJHV�RI�VKDUHG�GDWD�VWRUDJH� y The structure of the data can be changed with respect to the original data, so that decoupled, shared

reporting of actual and plan data is possible �

'LVDGYDQWDJHV�RI�VKDUHG�GDWD�VWRUDJH� y Redundant data storage

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-24

SAP AG 2006

0XOWL3URYLGHU YHUVXV�'DWD�7UDQVIHU�3URFHVV��'DWD�WUDQVIHU�SURFHVV

0XOWL3URYLGHU ZLWK�SODQQLQJ�IXQFWLRQ

"

�

� $GYDQWDJHV�RI�WKH�GDWD�WUDQVIHU�SURFHVV

y Less memory is needed on the server as no buffering mechanism is used.

y Before writing into the database you can drop the database indices, write the data, and then create the indices again. This is considerably faster than updating the indices after each new data record.

y Due to the optimization of the parallelization, this process is faster than a planning function.

� 'LVDGYDQWDJHV�RI�WKH�GDWD�WUDQVIHU�SURFHVV

y As you are using a real-time InfoProvider as target you have to switch it to “ load enabled” before the staging process starts and back to “ planning enabled” afterwards. During that time and during the load process, nobody can perform planning on the InfoProvider.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-25

SAP AG 2006

0XOWL3URYLGHU YHUVXV�'DWD�7UDQVIHU�3URFHVV��'DWD�WUDQVIHU�SURFHVV

0XOWL3URYLGHU ZLWK�SODQQLQJ�IXQFWLRQ

"

�

� $GYDQWDJHV�RI�WKH�GDWD�WUDQVIHU�SURFHVV

y Less memory is needed on the server as no buffering mechanism is used.

y Before writing into the database you can drop the database indices, write the data, and then create the indices again. This is considerably faster than updating the indices after each new data record.

y Due to the optimization of the parallelization, this process is faster than a planning function. �

'LVDGYDQWDJHV�RI�WKH�GDWD�WUDQVIHU�SURFHVV y As you are using a real-time InfoProvider as target you have to switch it to “ load enabled” before

the staging process starts and back to “ planning enabled” afterwards. During that time and during the load process, nobody can perform planning on the InfoProvider.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-26

SAP AG 2006

0XOWL3URYLGHU LQ�3ODQQLQJ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�8QGHUVWDQG�FRQFHSWV�IRU�SODQQLQJ�ZLWK�0XOWL3URYLGHUV$VVHVV�WKH�XVH�RI�0XOWL3URYLGHUV DQG�GDWD�WUDQVIHU�SURFHVVHV�IRU�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-27

SAP AG 2006

0XOWL3URYLGHU LQ�3ODQQLQJ��8QLW�2YHUYLHZ�'LDJUDP


�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-28

SAP AG 2006

$XWKRUL]DWLRQ�2EMHFWV�LQ�3ODQQLQJ��7RSLF�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�8QGHUVWDQG�ZKLFK�DXWKRUL]DWLRQ�REMHFWV�WKH�SODQQLQJ�FRQWDLQV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-29

SAP AG 2006

$XWKRUL]DWLRQ�2EMHFWV�LQ�3ODQQLQJ��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�JHW�DQ�RYHUYLHZ�RI�WKH�DXWKRUL]DWLRQ�REMHFWV�RI�WKH�%:�LQWHJUDWHG�SODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-30

SAP AG 2006

$XWKRUL]DWLRQ�2EMHFWV�LQ�WKH�%,�,QWHJUDWHG�3ODQQLQJ

e,fL��Lh`�Zk�j�m<��n��p��N� h�jtk4jLm!�`n��pP�

�� N�u��

� �Z��<w

e�fL��Zh��Zk�jZm!��no��pZ� � h�jtk4jZm<�`n��p��

egv�v]�!��vPhL�&� �]j� �L�Z��

�� &��!��

� �L��!w

� h�jtk4jZm<�`n��pP�

e�v�vJ�!�Pv�h9�&� �`j� �L��P�

� ��Aw

Relevant for S_RS_COMP

Relevant for analysis authorizations

egv�vJ�<��vPhL�� ]j� �Z�Z��

�

� For the BI-integrated planning, the user basically needs the same authorizations as for the analysis of

data in a query. �

In addition, along with the authorization for displaying data, the authorization for changing data is also required in the analysis authorizations.

� There are two types of authorization check:

y Check for standard authorizations:

- The authorization object S_RS_COMP is checked with the activity ([HFXWH.

- The user requires the authorization for the InfoProvider on which the query is defined.

y Check for analysis authorizations:

- The user requires the authorization for the InfoProvider on which the aggregation level is based. �

For a query on an aggregation level that was itself defined on a MultiProvider, the aggregation level is authorized for the field RSINFOCUBE in S_RS_COMP. In the analysis authorizations, on the other hand, you use the MultiProvider.

� The above graphic illustrates the basic modeling options.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-31

SAP AG 2006

$XWKRUL]DWLRQ�2EMHFWV�LQ�3ODQQLQJ��2YHUYLHZ

$XWKRUL]DWLRQ�REMHFWV

$QDO\VLV�DXWKRUL]DWLRQ

&RPSDUH�%:��

$XWKRUL]DWLRQ�IRU�ZRUNLQJ�ZLWK�SODQQLQJ�IXQFWLRQ�W\SHV

6B56B3/67

$XWKRUL]DWLRQV�IRU�PDLQWDLQLQJ�DQG�GLVSOD\LQJ�ORFN�VHWWLQJV

6B56B3/(14

$XWKRUL]DWLRQ�IRU�ZRUNLQJ�ZLWK�WKH�SODQQLQJ�VHTXHQFH

6B56B3/64

$XWKRUL]DWLRQ�IRU�ZRUNLQJ�ZLWK�SODQQLQJ�IXQFWLRQV

6B56B3/6(

$XWKRUL]DWLRQ�IRU�ZRUNLQJ�ZLWK�DJJUHJDWLRQ�OHYHOV

6B56B$/9/

�

� The above illustration shows the authorization objects for business planning in object class RS.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-32

SAP AG 2006

$XWKRUL]DWLRQ�2EMHFWV�LQ�3ODQQLQJ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�ZKLFK�DXWKRUL]DWLRQ�REMHFWV�WKH�

SODQQLQJ�FRQWDLQV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-33

SAP AG 2006

0RGHOLQJ��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�³NH\�ILJXUH�PRGHO´�DQG�³DFFRXQW�

PRGHO´�PRGHOLQJ� 8QGHUVWDQG�PRGHOLQJ�FRQFHSWV�IRU�WKH�

0XOWL3URYLGHU� 8QGHUVWDQG�WKH�DXWKRUL]DWLRQ�REMHFWV�LQ�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-34

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-35

0RGHOLQJ�([HUFLVHV�

8QLW�� 0RGHOLQJ��/HVVRQ�� 0XOWL3URYLGHU�LQ�3ODQQLQJ�


• Understand the concept of the MultiProvider, its interaction with the aggregation levels, and its modeling for planning, and you will be able to follow it in the system.

In the following section, the aim is to use a MultiProvider to merge the data of the quantity planning and the price planning for the Sales Managers, whereby the different granularities of the planning must be considered in the modeling.

Subsequently, a plan query is created to provide an input option for the sales quantity and prices of version B, and in which the contribution margins and revenues calculated in the following unit are to be displayed.

1-1 MultiProvider 7%:��0�� has already been defined for you in the Administrator Workbench and it contains both quantity provider 7%:��6�� and price provider 7%:��3�� for your exercise scenario. Navigate to the 3ODQQLQJ�0RGHOHU and define for the MultiProvider with technical name 7%:��0�� an DJJUHJDWLRQ�OHYHO with the following name: Technical name: 0��B$/B�� Name: 7%:��B0��B$/��$V�\RX�FDQ�VHH��WKH�³,QIR3URYLGHU´�FKDUDFWHULVWLF�WKDW�HQDEOHV�\RX�WR�ZRUN�DFURVV�WKH�,QIR3URYLGHUV�LV�DOZD\V�VHOHFWHG��Select the following characteristics and key figures in the aggregation level and then DFWLYDWH them:

6DOHV�8QLW��&XUUHQF\�.H\��)LVFDO�<HDU�9DULDQW��)LVFDO�<HDU��6DOHV�3ULFH�SHU�8QLW�RI�0HDVXUH��7RWDO�9DULDEOH�&RVWV�RI�*RRGV�0DQXIDFWXUHG��&RQWULEXWLRQ�0DUJLQ��5HYHQXH��6DOHV�4XDQWLW\��&RPSDQ\�&RGH��&RQWUROOLQJ�$UHD��,QIR3URYLGHU��0DWHULDO�*URXS��9HUVLRQ� For the MultiProvider scenario, you do not have to define any filters or input templates in the following section. �Now exit the planning modeler.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-36

1-2 Now you navigate to the 4XHU\�'HVLJQHU and define a plan query on the basis of aggregation level 0��B$/B�� of the MultiProvider. The query should look like this:

)LVFDO��<HDU

0DW��*URXS

6DOHV�4W\��%.��

6DOHV�4W\��%.��

3ULFH 5H�YHQXH�%.��

5H�YHQXH�%.��

0DQXI�&RVWV

'%�%.��

'%�%.��

1-2-1 The data range of the “&KDUDFWHULVWLF�UHVWULFWLRQV” should be modeled as follows:

0DWHULDO�JURXS�� 7:$7��-8&�9HUVLRQ�� %�)LVFDO�\HDU�YDULDQW�� .��)LVFDO�\HDU�� ,QWHUYDO�IRU�YDULDEOHV�

��*URXS��B9$5B)<B��B30��2IIVHW��OHIW�ERXQGDU\�YDOXH��2IIVHW��ULJKW�ERXQGDU\�YDOXH��

Please note that the “ #” is only required for the FOX programming examples considered in the following unit. Position the ILVFDO�\HDU and PDWHULDO�JURXS fields in the rows.

6DYH�your plan query as follows: Description: 7%:��B0��B$/��B34��B0XOWL3 Technical name: 0��B$/B��B3ODQTXHU\B��B0XOWL3�

1-2-2 The design of the columns of the plan query must take into account the different granularity of the sales and price planning as well as the different origins of the data from the two real-time InfoProviders�7%:��6��DQG�7%:��3��. In the following, compare the two granularities:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-37

1-2-3 *UDQXODULW\�RI�WKH�VDOHV�SODQQLQJ��

g. Sales Unit h. Currency i. Revenue j. DB 1 k. Sales Quantity

Please note that the data records for sales quantity, revenue and contribution margin 1 contain both the unit of measure 67 and the currency 86' at the same time! *UDQXODULW\�RI�WKH�SULFH�SODQQLQJ��

l. Version m. Mat. Group

n. Fiscal Year Variant

o. Fiscal Year

p. Currency q. Price r. Manufacturing costs

�Define the eight columns in accordance with these granularities. Which selections must , for example, the data column “6DOHV�4XDQWLW\�%.��” and the data column “3ULFH” include? 6DOHV�TXDQWLW\�%.�� _________________________________________

3ULFH� _______________________________________________________

Note that when you are configuring the columns, the 5HYHQXH and &RQWULEXWLRQ�PDUJLQV columns cannot be filled manually, but RQO\�E\�PHDQV�RI�D�SODQQLQJ�IXQFWLRQ. It should be possible to fill�6DOHV�4XDQWLW\��3ULFH and 0DQXIDFWXULQJ�&RVW by means of both PDQXDO�SODQQLQJ�DQG�D�SODQQLQJ�IXQFWLRQ. Check whether the plan query is in FKDQJH�PRGH.

a. Version b. Company Code ...

c. Controlling Area

d. Mat. Group e. Fiscal Year Variant

f. Fiscal Year

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-38

1-2-4 Make sure that the SURSHUWLHV RI�WKH�GULOO�GRZQ�FKDUDFWHULVWLFV and the characteristics of the “&KDUDFWHULVWLF�UHVWULFWLRQV” are set to “5HSUHVHQW�DV�NH\V” . In the SURSHUWLHV, under “$FFHVV�W\SH�IRU�UHVXOW�YDOXHV” , you should select ”0DVWHU�GDWD” for ERWK drill-down characteristics.

Save the query and then execute it for fiscal year ��. Check whether it is possible to type an entry in the “6DOHV�4XDQWLW\�%.��” and “3ULFH” data columns. You should receive the following display (here is an excerpt):

As you can see, the plan data from the two InfoProviders is represented correctly, and it is also possible to type an entry in both InfoProviders. Now exit the Query Designer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-39

1-3 You now want to include the above plan query in a new workbook of the Bex Analyzer.

1-3-1 To do this, you navigate to the %([�$QDO\]HU,�call up the GHVLJQ�PRGH, and position your cursor in cell $�. Here you write the following: “0HUJLQJ�RI�WKH�TXDQWLW\�DQG�SULFH�SODQQLQJ�RI�WKH�6DOHV�0DQDJHUV��0XOWL3URYLGHU�VFHQDULR�±” . The text color is “5HG” , the font size “ ��” and the text “EROG” . 6DYH�the workbook in your favorites under the following description “*URXS��B7%:��B%(;B0XOWL3URY” .

1-3-2 Place the cursor in cell $� and define a 6DYH�EXWWRQ�with the button text “6DYH” and then create a 5HIUHVK�EXWWRQ in cell '� with the button text “5HIUHVK” . 6DYH your workbook again�

1-3-3 In cell *� you use the “0HVVDJHV” design item to show system messages generated by executing planning functions, for example. Within the design item and on the *HQHUDO tab page here, you select all fields. You do not change the settings on the 6L]H tab page. Now position the cursor in cell *��and write “6\VWHP�PHVVDJHV” . Then set the text to “EROG” .

1-3-4 Now place the cursor in cell $��and create the design item “$QDO\VLV�*ULG” . Use the plan query of the MultiProvider with the name “7%:��B0��B$/��B34��B0XOWL3³ as '$7$B3529,'(5B� and select $XWR)LW on the *HQHUDO tab page of this design item. The other settings remain unchanged. 6DYH the workbook and execute it for the fiscal year ��. Make sure that the plan query is also ready for input on the executed folder by checking whether “$OORZ�,QSXW�RI�3ODQ�9DOXHV” is set in the “/RFDO�TXHU\�SURSHUWLHV” for the analysis grid. If not, set it now please. You have thus created a plan query with which you can manually overwrite the previously planned quantities and prices and manufacturing costs in version B. The analysis grid should appear as follows in the workbook (here is an excerpt):

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-40

Planning functions will later be added to the workbook, and they are used to calculate the plan revenues and the contribution margins. 6DYH the ZRUNERRN again and leave the BEx Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-41

�6ROXWLRQV�

8QLW�� 0RGHOLQJ��/HVVRQ�� 0XOWL3URYLGHU�LQ�3ODQQLQJ�

1-1 MultiProvider 7%:��0�� has already been defined for you in the Administrator Workbench and it contains both quantity provider 7%:��6�� and price provider 7%:��3�� for your exercise scenario. Navigate to the 3ODQQLQJ�0RGHOHU and define for the MultiProvider with technical name 7%:��0�� an DUJUHJDWLRQ�OHYHO with the following name: Technical name: 0��B$/B�� Name: 7%:��B0��B$/��$V�\RX�FDQ�VHH��WKH�³,QIR3URYLGHU´�FKDUDFWHULVWLF�WKDW�HQDEOHV�\RX�WR�ZRUN�DFURVV�WKH�,QIR3URYLGHUV�LV�DOZD\V�VHOHFWHG��Select the following characteristics and key figures in the aggregation level and then DFWLYDWH them:

6DOHV�8QLW��&XUUHQF\�.H\��)LVFDO�<HDU�9DULDQW��)LVFDO�<HDU��6DOHV�3ULFH�SHU�8QLW�RI�0HDVXUH��7RWDO�9DULDEOH�&RVWV�RI�*RRGV�0DQXIDFWXUHG��&RQWULEXWLRQ�0DUJLQ��5HYHQXH��6DOHV�4XDQWLW\��&RPSDQ\�&RGH��&RQWUROOLQJ�$UHD��,QIR3URYLGHU��0DWHULDO�*URXS��9HUVLRQ��

For the MultiProvider scenario, you do not have to define any filters or input templates in the following section.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-42

�Now exit the planning modeler.

1-2 Now you navigate to the 4XHU\�'HVLJQHU and define a plan query on the basis of aggregation level 0��B$/B�� of the MultiProvider. The query should look like this:

)LVFDO��<HDU

0DW��*URXS

6DOHV�4W\��%.��

6DOHV�4W\��%.��

3ULFH 5H�YHQXH�%.��

5H�YHQXH�%.��

0DQXI�&RVWV

'%�%.��

'%�%.��

1-2-1 The data range of the “&KDUDFWHULVWLF�UHVWULFWLRQV” should be modeled as follows:

0DWHULDO�JURXS�� 7:$7��-8&�9HUVLRQ�� %�)LVFDO�\HDU�YDULDQW�� .��)LVFDO�\HDU�� ,QWHUYDO�IRU�YDULDEOHV��*URXS��B9$5B)<B��B30��2IIVHW��OHIW�ERXQGDU\�YDOXH��2IIVHW��ULJKW�ERXQGDU\�YDOXH�� Drag these characteristics into the “ Characteristic restrictions” area and restrict them as shown above. The result should appear as follows in the filter area of the Query Designer:

1RWH on the entry for the fiscal year: Show “ Value ranges” in the value selection and select “ between” as the operator.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-43

To define the value range, you use the input help , set the “ Show” field to “ Variables” , select the variable *URXS��B9$5B)<B��B30 in both cases, and confirm with OK.

To set the offsets, you choose the selection on the right side of the value

selection and click on the offset button . In the dialog window that appears, you leave the offset for the start of the value range to 0 and confirm with OK.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-44

Now the same dialog window opens again for you to enter the value for the end of the value range. Here you set the offset to “ 1” .

�Please note that the “ #” is only required for the FOX programming examples considered in the following unit. Position the ILVFDO�\HDU and PDWHULDO�JURXS fields in the rows. 6DYH�your plan query as follows: Description: 7%:��B0��B$/��B34��B0XOWL3 Technical name: 0��B$/B��B3ODQTXHU\B��B0XOWL3�

1-2-2 The design of the columns of the plan query must take into account the different granularity of the sales and price planning as well as the different origins of the data from the two real-time InfoProviders�7%:��6��DQG�7%:��3��. In the following, compare the two granularities: *UDQXODULW\�RI�WKH�TXDQWLW\�SODQQLQJ��VDOHV�SODQQLQJ��

Version Company Code ...

Controlling Area

Mat. Group

Fiscal Year Variant

Fiscal Year

Sales Unit

Curr-ency

Revenue DB1 Sales Quantity

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-45

Please note that the data records for sales quantity, revenue and contribution margin 1 contain both the unit of measure 67 and the currency 86' at the same time!

*UDQXODULW\�RI�WKH�SULFH�SODQQLQJ��

Version Mat. Group

Fiscal Year Variant

Fiscal Year

Currency Price Manufacturing costs

�Define the eight columns in accordance with these granularities. First drag all the key figures used into the “ Columns” area. A column structure is then automatically created with these key figures. The result is that the “ Rows/Columns” area should look like this:

Which selections must , for example, the data column “6DOHV�4XDQWLW\�%.��” and the data column “3ULFH” include? 6DOHV�4XDQWLW\�%.��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-46

3ULFH�

7LS: First restrict 6DOHV�4XDQWLW\, 5HYHQXH and '%� for only BK1000. Then copy them, and in the copies change the company code to “ 2000” . Note that when you are configuring the columns, the 5HYHQXH and &RQWULEXWLRQ�PDUJLQV columns cannot be filled manually, but RQO\�E\�PHDQV�RI�D�SODQQLQJ�IXQFWLRQ.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-47

It should be possible to fill�6DOHV�4XDQWLW\��3ULFH and 0DQXIDFWXULQJ�&RVW by means of both PDQXDO�SODQQLQJ�DQG�D�SODQQLQJ�IXQFWLRQ.

Check whether the plan query is in FKDQJH�PRGH.

1-2-3 Make sure that the SURSHUWLHV RI�WKH�GULOO�GRZQ�FKDUDFWHULVWLFV and the

characteristics of the “&KDUDFWHULVWLF�UHVWULFWLRQV” are set to “5HSUHVHQW�DV�NH\V” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-48

In the SURSHUWLHV, under “$FFHVV�W\SH�IRU�UHVXOW�YDOXHV” , you should select “0DVWHU�GDWD” for ERWK drill-down characteristics.

Save the query and then execute it for fiscal year ��. Check whether it is possible to type an entry in the “6DOHV�4XDQWLW\�%.��” and “3ULFH“ data columns. You should receive the following display (here is an excerpt):

As you can see, the plan data from the two InfoProviders is represented correctly, and it is also possible to type an entry in both InfoProviders. Now exit the Query Designer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-49

1-3 You now want to include the above plan query in a new workbook of the BEx Analyzer.

1-3-1 To do this, you navigate to the %([�$QDO\]HU,�call up the GHVLJQ�PRGH, and position your cursor in cell $�. Here you write the following: “0HUJLQJ�RI�WKH�TXDQWLW\�DQG�SULFH�SODQQLQJ�RI�WKH�6DOHV�0DQDJHUV��0XOWL3URYLGHU�VFHQDULR�±” . The text color is “5HG” , the font size “ ��” and the text “EROG” . 6DYH�the workbook in your favorites under the following description “*URXS��B7%:��B%(;B0XOWL3URY” .

1-3-2 Place the cursor in cell $� and define a 6DYH�EXWWRQ�with the button text “6DYH” and then create a 5HIUHVK�EXWWRQ in cell '� with the button text “5HIUHVK” . Configuration of “6DYH” button

Configuration of “5HIUHVK” button

6DYH your workbook again�

1-3-3 In cell *� you use the “0HVVDJHV” design item to show system messages generated by executing planning functions, for example. Within the design item and on the *HQHUDO tab page here, you select all fields. You do not change the settings on the 6L]H tab page. Now position the cursor in cell *��and write “6\VWHP�PHVVDJHV” . Then set the text to “EROG” .

1-3-4 Now place the cursor in cell $��and create the design item “$QDO\VLV�*ULG” . Use the plan query of the MultiProvider with the name “7%:��B0��B$/��B34��B0XOWL3” as '$7$B3529,'(5B� and select $XWR)LW on the *HQHUDO tab page of this design item. The other settings remain unchanged.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 8-50

6DYH the workbook and execute it for the fiscal year ��.

Make sure that the plan query is also ready for input on the executed folder by checking whether “$OORZ�,QSXW�RI�3ODQ�9DOXHV” is set in the “/RFDO�TXHU\�SURSHUWLHV” for the analysis grid. If not, set it now please. You have thus created a plan query with which you can manually overwrite the previously planned quantities and prices and manufacturing costs in version B. The analysis grid should appear as follows in the workbook (here is an excerpt):

Planning functions will later be added to the workbook, and they are used to

calculate the plan revenues and the contribution margins. 6DYH the ZRUNERRN again and leave the BEx Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-1

SAP AG 2006

&RQWHQW�� 3ODQQLQJ�)XQFWLRQV�± (QKDQFHPHQW

3ODQQLQJ�)XQFWLRQV�² (QKDQFHPHQW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-2

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�² (QKDQFHPHQW��7RSLF�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8VH�IROORZ�XS�SODQQLQJ�IXQFWLRQV��DQG�LQ�SDUWLFXODU�

DVVHVV�WKH�XVDJH�RI�WKH�IRUPXOD�HGLWRU�DQG�WKH�FXVWRPHU�VSHFLILF�SODQQLQJ�IXQFWLRQV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-3

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�² (QKDQFHPHQW��2YHUYLHZ�'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-4

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�² (QKDQFHPHQW��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�IRU�LPSOHPHQWLQJ�WKH�%,�LQWHJUDWHG�SODQQLQJ�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�IROORZ�XS�SODQQLQJ�IXQFWLRQV��

� <RX�DUH�SDUWLFXODUO\�LQWHUHVWHG�LQ�WKH�GLVWULEXWLRQ�EDVHG�RQ�UHIHUHQFH�GDWD�DQG�WKH�IRUPXOD�HGLWRU�)2;��DV�ZHOO�DV�WKH�RSWLRQ�RI�EHLQJ�DEOH�WR�ZRUN�ZLWK�FXVWRPHU�VSHFLILF�SODQQLQJ�IXQFWLRQV��

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-5

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�² (QKDQFHPHQW��8QLW�2YHUYLHZ�'LDJUDP

8QLW�2YHUYLHZ� /HVVRQ��3ODQQLQJ�)XQFWLRQV�� (QKDQFHPHQW

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-6

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�² (QKDQFHPHQW��7RSLF�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�8VH�IROORZ�XS�SODQQLQJ�IXQFWLRQV��DQG�LQ�SDUWLFXODU�DVVHVV�WKH�XVDJH�RI�WKH�IRUPXOD�HGLWRU�DQG�WKH�FXVWRPHU�VSHFLILF�SODQQLQJ�IXQFWLRQV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-7

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�² (QKDQFHPHQW��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�IRU�LPSOHPHQWLQJ�WKH�%,�LQWHJUDWHG�SODQQLQJ�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�IROORZ�XS�SODQQLQJ�IXQFWLRQV�

� <RX�DUH�SDUWLFXODUO\�LQWHUHVWHG�LQ�WKH�GLVWULEXWLRQ�EDVHG�RQ�UHIHUHQFH�GDWD�DQG�WKH�IRUPXOD�HGLWRU�)2;��DV�ZHOO�DV�WKH�RSWLRQ�RI�EHLQJ�DEOH�WR�ZRUN�ZLWK�FXVWRPHU�VSHFLILF�SODQQLQJ�IXQFWLRQV�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-8

SAP AG 2006

%ORFN�&RQFHSW�� ([DPSOH

��$02817�),6&<($5�3URGXFW

(PSW\

�),6&<($5

�3URGXFW

$OO��

��FDOOV��UHFRUGV��DQG��

�3URGXFW

��FDOO��DOO�UHFRUGV$OO

��FDOOV��UHFRUGV��DQG��

�),6&<($5

��FDOOV��RQH�UHFRUG�SHU�FDOO

(PSW\1XPEHU�RI�FDOOV�UHFRUGV³&+$1*('´ ILHOG

6DPSOH�GDWD�UHFRUGV�

�

� Technically, every planning function that is executed is called internally more than once. For this purpose, the data to be processed that is selected by the filter is divided into blocks - that is, smaller records. The planning function is called for each block.

� Every combination of characteristic values that appears in the data with regard to the block characteristics forms its own block (hence the name EORFN�FKDUDFWHULVWLFV), because the data of the filter is grouped according to the characteristics that were set as block characteristics in the “characteristics to be changed”. Therefore, all records in a block have the same characteristic values for those characteristics.

� Blocks are created internally by the system because they make the coding of planning functions of the types “user exit” and “FOX formulas” much easier.

� For example, for FOX formulas, a FOREACH instruction is created for every characteristic not contained in the characteristics to be changed.

� Please note that in FOX or EXIT, you cannot depend on the sorting sequence of the blocks.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-9

SAP AG 2006

3ODQQLQJ�)XQFWLRQ�7\SHV�RI�WKH�%,�,QWHJUDWHG�3ODQQLQJ

*HQHULF�3ODQQLQJ�)XQFWLRQV�RI�WKH�%,�,QWHJUDWHG�3ODQQLQJ

•• Copy• Revaluation • Delete• Repost

• &XUUHQF\�WUDQVODWLRQ• 8QLW�FRQYHUVLRQ• 'LVWULEXWLRQ�E\�NH\�• 'LVWULEXWLRQ�E\�UHIHUHQFH�GDWD�• )RUPXOD�• &XVWRPHU�GHILQHG�

SODQQLQJ�IXQFWLRQ�W\SHV��E\�XVHU�H[LW�

• *HQHUDWH�FRPELQDWLRQV• Repost on basis of characteristic

relationships• Deletion of invalid combinations

�

� The above illustration gives a highlighted overview of the planning functions that will be discussed in this unit.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-10

SAP AG 2006

� � � � � � � � � ��

'LVWULEXWLRQ�E\�.H\

(QWHUSULVH

&�723��

&�3/��

&�6(*�$

&�%$��

&�',9��

&�3/��

%XVLQHVVDUHD

&RUSRUDWLRQ

6HJPHQW

3HULRG

'LYLVLRQ

3URG��OLQH

3KDUPD��&KHPLVWU\

3KDUPD�6WDU

$QDOJHVLFV

0RQR &RPER� �

�

��

1HW�VDOHV��76'��!6DOHV�YROXPH��3&

� � � � � � � � � ��

� Using the GLVWULEXWLRQ�IXQFWLRQ, you can distribute values from one aggregation level to another aggregation level. Typically, this function is used for distributions from one organizational unit to another organizational unit. The distribution is performed for vertical reconciliation purposes. The above illustration shows two distributions: one from division to product line, the second from product line to periods.

� Because this function type writes credit and debit records, and a non-planned field is being written to, the “ �” is entered as a placeholder for the write access, namely in the product line characteristic for the first distribution, and in period for the second distribution.

� Please note that if the “ From” value is created in the function so that it could select data records that are not in the filter, the system does not output an error message. The data records are not included in the distribution. If the “ To” value is created in the function so that it could select data records that are not in the filter, the system terminates the entire planning function with an error message. Rounding differences are distributed equally across those target data records that are already not equal to zero. The same keys apply to all key figures to be distributed for each planning function.

� If the characteristic restriction of a “ To” value is not a single value, the key applies to every characteristic combination that corresponds to the characteristic restriction. The keys are normalized during processing, which means that they are converted to percentages corresponding to their value distribution: The sytem adds the distribution factors that are assigned to the individual characteristic values, first producing a total and then setting them in proportion to one another. This results in percentages that always add up to 100%.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-11

SAP AG 2006

'LVWULEXWLRQ�E\�.H\V�² 'HWHUPLQLQJ�WKH�'LVWULEXWLRQ�)DFWRUV

�� !��"�

#��#� !��$ �%'&)(+*�,.-0/0(��132 /0(+4 1.5��1�2 /�(+4 1.56 ( ,7&08

:93�3;0#��3��#�#393�3;) ��3��$ �

%<&)(+*.,.-./.(��132 /0(+4 105��1�2 /�(+4 1.56 ( ,7&08

��=�� "�

#��=#� ��> �%<&?(+*�,0-./.(�=1�2 /.(+4 105��1�2 /0(+4 1�56 ( ,<&08

@BA�C DFE3G3CIH>JKE!LNM$O+O P @7�RQ$O SUTVC D�E3G�C+HWJXEYLZJ>QXMFDFD>C [�Q�L�T$P

�W\�EYM>O^]U_F`�`

��GLVWULEXWLRQ�RI�PDWHULDO�JURXS�3�WR�PDWHULDOV�0��DQG�0�

$IWHU�GLVWULEXWLRQ $IWHU�GLVWULEXWLRQ

��9��$;W#3�3��#�9��$;) ��3��= �

%'&?(+*.,.-0/0(��132 /.(+4 105��1�2 /0(+4 1�56 ( ,<&08

��=��#��=#� ��> �%<&?(+*�,?-./.(�=1:2 /.(+4 1�5��132 /.( 4 1056 ( ,<&08

@Ba�M$Q>JXM$OKL�QFE�G!S�P

$IWHU�GLVWULEXWLRQ

��GLVWULEXWLRQ�RI�PDWHULDO�0��WR�PDWHULDOV�0��DQG�0��

9��;0#��3��=#�9��;) ��3��> �%<&?(+*�,0-./.(�=1:2 /.(+4 1�5��132 /.( 4 1056 ( ,<&08

�

� You can control the distribution procedure in different ways with this planning function:

y Manual entry

y Distribute all

y Only distribute unassigned �

The above illustration shows a numeric example for each of the three variants. The records are shown here from the viewpoint of the query, meaning the end user. This is why the debit records resulting from the distribution are not contained in the above illustration.

� The “ Only distribute unassigned” variant is a special case of the “ Manual entry” variant. The only difference is that in the “ Manual entry” , the sender is not “ #” , while in “ Unassigned” it is always “ #” . The “ Manual entry” variant could therefore be used for a cost center distribution, for example.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-12

SAP AG 2006

'DWD�WR�EH�GLVWULEXWHG

5HIHUHQFH�GDWD

5HVXOW�DIWHU�GLVWULEXWLRQ

'LVWULEXWLRQ�E\�5HIHUHQFH�'DWD

��'HF1RY2FW6HS$XJ-XO-XQ0D\$SU0DU)HE-DQ<HDU

7RWDO�DPRXQW�WR�EH�GLVWULEXWHG��



�bQUJWQFMXDFDWC [VQ�LFTM�cZ\�J>QFE�C DdM=O D=\TWC DFE3G3CIH>JKE!LFT�e

5HIHUHQFH�GDWD�WRWDO��&DOFXODWLRQ�IRU�-XQH��

�

� With the function type 'LVWULEXWLRQ�E\�UHIHUHQFH�GDWD you can generate, on the basis of the reference data, characteristic combinations to which the distribution is performed. The key figure values are distributed as percentages on the basis of the reference data.

� The above illustration shows a calculation example for distribution by reference data.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-13

SAP AG 2006

'LVWULEXWLRQ�E\�5HIHUHQFH�'DWD

�LXfgL$GYL>Q�hKLji^LXSkf3C [�J$GYLkM>Q�TGYLXfYL=GYL=Q=hXLkh$l�M=G!M�hKEgL$G3C DFE3C hXDm!H>O \>h=i�h>lFM$GYM�hXEnL$G�C D�E�C hBD=o

A�C DXE3G�C+HWJXE3C \WQU\�f�cUMFEYL�G�C M$OK[VG!\�J$pkE!\jcjMKE!L$G�C M$O

A�C DXE�G�C HWJXE�C \VQZGYL�h=C+p=C L$QKEYD

�

� The distribution of material group to material is modeled in the above illustration. All three key figures are distributed in relation to the key figure 0D_QUANT_B of the reference data of the year 2005. The distribution key is “ Distribute all” .

� The reference data is selected as follows: for all characteristics that are not indicated to be reference characteristics, the selection of the filter is used. For the reference characteristics, the reference value defined in the planning function is used.

� 5HIHUHQFH�NH\�ILJXUH��RSWLRQDO��You define the key figure to be used in the reference data to calculate the distribution keys. When such a key figure is selected, the system distributes all the key figures to be distributed according to this key, that is, according to this reference key figure. If QR reference key figure is selected, the system calculates the keys individually for each key figure to be distributed. In this case, the key figure used in the reference data is the same as the one that is distributed.

� As usual, a planning function is executed in blocks, including the distribution function. Reference data is read for each block. If no reference data exists for a block, then no distribution is performed for this block.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-14

SAP AG 2006

&XUUHQF\�7UDQVODWLRQ

�

� You can use the function type &XUUHQF\�7UDQVODWLRQ to translate currencies from key figures into other key figures.

� You generally have to consider whether to model a currency translation using a planning function, or perform a currency translation at runtime within the plan query. In the latter case, it is possible, for example, to enter plan data in USD in the input-ready cell and then see the corresponding value in Euro displayed online.

� If you require translated data for a follow-up calculation, you should use the planning function, or else execute the translation by means of the query.

� The H[FKDQJH�UDWHV are stored in tables of the type TCUR*. The rates are often loaded from SAP ERP, or they have to be maintained manually by means of the SAP IMG (transaction SPRO or directly by means of transaction OB08).

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-15

SAP AG 2006

0RGHOLQJ�WKH�&XUUHQF\�7UDQVODWLRQ��

��¼*HUPDQ\��*HUPDQ\

$PRXQW&XUUHQF\�!%UDQFK

([FKDQJH�UDWH��LPDJLQDU\�� ¼

�VW�H[HFXWLRQ�RI�WKH�FXUUHQF\�WUDQVODWLRQ

��*HUPDQ\��¼*HUPDQ\

��*HUPDQ\

�QG�H[HFXWLRQ�RI�WKH�FXUUHQF\�WUDQVODWLRQ

,I�\RX�H[HFXWH�WKH�FXUUHQF\�WUDQVODWLRQ�VHYHUDO�WLPHV��DOUHDG\�WUDQVODWHG�GDWDVHWV�DUH�DOVR�LQFOXGHG�DJDLQ�

3ODQQLQJ�VHTXHQFH��'HOHWH�IXQFWLRQ��&XUUHQF\�WUDQVODWLRQ

6ROXWLRQ�

2QH�NH\�ILJXUH

�

� Please keep in mind that planning functions may generate double data and often do not have any delta functionality.

� This is the case for the Currency Translation function too, as the above example describes. Therefore, you must bundle a Delete function and the Currency Translation function in a planning sequence.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-16

SAP AG 2006

0RGHOLQJ�WKH�&XUUHQF\�7UDQVODWLRQ��

��

$PRXQW��KRXVH�FXUUHQF\�

¼

+RXVH�FXUUHQF\

�*HUPDQ\

$PRXQW��JURXS�FXUUHQF\�

*URXS�FXUUHQF\

%UDQFK

([FKDQJH�UDWH��LPDJLQDU\�� ¼�qLBf!\VG!Ldh�J$G3G!L>Q�hKSrE:G!M=Q�D>O MKE�C \WQ

(YHQ�LI�\RX�H[HFXWH�WKH�FXUUHQF\�WUDQVODWLRQ�VHYHUDO�WLPHV��WKH�JURXS�DPRXQW�ZLOO�VWLOO�EH�FRUUHFW�

7ZR�NH\�

ILJXUHV

��

$PRXQW��KRXVH�FXUUHQF\�

¼

+RXVHFXUUHQF\

��*HUPDQ\

$PRXQW��JURXS�FXUUHQF\�

*URXS�FXUUHQF\

%UDQFK

��fnEYL$GWh$J$G�GnL$Q=hXSRE3G!M$QFD=O MXE�C \WQ�sl�M=G!M�hKEnL$G3C D�E3C hdG!L>O MXE�C \WQFDWl$C+p>tF��l=\VJ$O TuH�LRD�LXE�J>pND�\E3lXMXEVvRG:\VJWpk��J$G�G!L$Q�hXSkf:C L$O TuC DrMWJKE!\>cjMXE3C hXM$O O Skf�C O+O L�Tw lFL$QuO \>hFM=OBh$J>G3G!L�Q=hXSNM�cu\VJWQXE�C DdL$Q�EnL$G:LFT�e

�

� Please note that a characteristic derivation - as described in the design of the above illustration - is used

to automatically create a delta process for the currency translation.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-17

SAP AG 2006

8QLW�&RQYHUVLRQ

�

� You can use the function type 88QQLLWW��&&RRQQYYHHUUVVLLRRQQ to convert units from key figures into other key figures.

� In the table 6RXUFH�WDUJHW�NH\�ILJXUH�FRQYHUVLRQ�W\SH, you can enter multiple conversions. For each conversion you must select a unit or quantity conversion type. The value in the target key figure is overwritten. This also applies if the source key figure is empty.

� The conversion rates are stored in tables (T006*).�The rates are often loaded from the SAP ERP system or have to be maintained manually by means of SAP IMG (transaction SPRO or directly using transaction CUNI).

� The same rules apply to the currency translation as to the modeling: If a key figure is used, the “ Delete” function should be executed before the conversion of the units. If two key figures are being used, a characteristic relationship should be set up.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-18

SAP AG 2006

*HQHUDWH�&RPELQDWLRQV

xxy'x7x<z{|K}�{|�{xxy'x7x<z{|K}�{|Byxxy'x7x<z{|K}�y|B~xxy'x7x<z{|K}�y|^�

)LVFDO�<HDU 3URG��&RVWV9HUVLRQ3URGXFW�*URXS3URGXFW

4XHU\

��g�3��g�� I�g��

�g�� I�g��g��0� ��.�3�n�

�g�.��g�.��g�3�

� � ��3��.�� !� �0� ��3�!�'� � � ��0� ��3�3�n�� .�3�

Version: 1Fiscal year: 2009

0 0

0 0

0

0

0

0

All characteristic combinations are set upeven if there is no transaction data

“Generate Combinations”planning function

*URXS�6DOHV

�

� 'HDOLQJ�ZLWK�18//�UHFRUGV�Almost all planning function types do QRW read NULL records and do QRW write any NULL records to the buffer. Exceptions are the standard planning functions “&RS\´ and “*HQHUDWH�&RPELQDWLRQV” � Both read NULL records (in which all key figures are equal to zero) and write NULL records when the function is executed.

� In contrast to the BPS planning, these NULL records are not ignored in the BI-integrated planning. They are kept in the buffer, written to the database, and they can be used, for example, to display all characteristic combinations in the executed TXHU\ (in which the corresponding flag for displaying these NULL records has been set), even if no plan data exists for these combinations yet.

� With the function type *HQHUDWH�&RPELQDWLRQV, you can generate NULL records for an aggregation level for all the combinations permitted by the master data and characteristic combinations. These are precisely those combinations that are also valid in the check on this aggregation level.

� This function type does not permit any other settings: Because new records are always being created for the overall aggregation level, all characteristics must be set as “ characteristics to be changed” . Thus, this function type operates without block characteristics.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-19

SAP AG 2006

)RUPXODU (GLWRU�)2;

)R[�)RUPXODV

��h�hXLXD�DNDFE!MBEYL�cjL=QFEnDkE!\T=MXEnMZG:LXhF\VG�T=D

��M$O h=J$O MXE:C+\WQXD � QFfY\�G!cjMXE�C \�QrT>L$G�C ��MFE�C \�QmI��M$G3C M>H$O LXD=o

A�C fgfYL$GnL>QFE$EYS>pXL�Dk\$fO \=\�pFD

A�\�O \W\VpXD �G:\$[WG!M�cjc�CIQ�[U��M$G3C M>H>O LKD

>J$Q=hÊ3C \�QXD w C E3lp>GYL�hF\VQ�hKL$C ��L�T�H>JFD>C+QFLXDFDO \>[VC hrmIf:\VGVLB¡�M=c�p=O L$¢O+C+QFLFM$G�G:L�[VG!LKD�D>C \�Q�o

��E3G�C Q�[Z\�p�L$G!MKE�C \WQFD ��M$O+O+C Q=[U��

f3J=Q�hKE3C \�Qcj\$TWJ>O LXD

�

� With the function type )RUPXOD��FOX = Formula Extension�, you can use enhanced mathematical functions for calculating the plan data. ABAP knowledge is not required. From the FOX coding the system generates ABAP coding that is executed at runtime.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-20

SAP AG 2006

&XVWRPL]LQJ�RI�WKH�)2;��

�

� The above illustration and the following three illustrations show you how to proceed in creating a formula by means of the editor.

� As you see, you have to perform a calculation for the characteristic Z_PRODUCT for just one particular year, namely 2009.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-21

SAP AG 2006


"Transfer"

Control line of the InfoObjects that can be changed and which are used to set up the formula.

Specify the combination of the next pair {key figure, characteristic value},then press "Transfer" again.

{SEMPS_003, Mango Juice} = {SEMPS_003, Apple Juice} + …

�

� The calculation for the characteristic Z_PRODUCT is performed in combination with the key figure(s) of the aggregation level that is/are provided here in the “ Key Figure” area. As you see, the key figure field is always part of the subsequent formula to be set up.

� An expression in brackets - the operand - as seen in the formula editor area on the top left side of the screen, describes the formula components that logically belong together: operand: {characteristic 1, ..., characteristic n, key figure}.

� The characteristic value(s) of the expression in brackets is/are derived from the characteristics included in the “ Changed” area in the previous illustration and their characteristic values stored in the above illustration, in the “ Characteristics Text via Input Help” area.

� By means of the Transfer button you can transfer the characteristic value(s)/key figure(s) combination required by the formula into the editor.

� After this you can transfer the formula components required for the formula into the editor in the same way.

� When an instruction is complete, you must enter a point “ .” !

� In the lower part of the editor, under “ Operand” , you see the structure of the objects combined in a logical bracket.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-22

SAP AG 2006


5HIHUHQFH�FKDUDFWHULVWLFV�LQ�)2;5

o S5HIHUHQFH�FKDUDFWHULVWLFV�LQ�WKH�HGLWRU

�

£ The above example shows how reference data is integrated into the formula editor. The above illustration only represents the technical settings.

£ Business example:

y The turnover is determined from the plan quantity and the price, whereby the turnover and the quantity are in plan version 1 and the price is in actual version 0.

£ The version does not have to be indicated as changeable, as it can be included in the area of the reference charcteristics.

y Later, in the filter, the selection can be set to version 1 in order to enable write access to this version. Reference version 0 can be stored directly in the formula, as you can see from the following representation:

- Formula: {0REVENUE} = {0QUANTITY} * {0PRICE|0VERSION = 0}.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-23

SAP AG 2006

&XVWRPL]LQJ�RI�WKH�)2;��3URJUDP�HOHPHQWV�RI�WKH�)2;

5HVXOW�LQ�HGLWRU

&UHDWLRQ�RI�D�YDULDEOH�LQ�WKH�HGLWRU

�

£ The above illustration shows how you must proceed if you want to use the program elements of the FOX.

£ The area “ Input Help for Further Program Elements” is designated for this purpose. The above illustration shows the language elements available in FOX and explains with examples how you can define a variable in the formula editor.

£ A number of elements are highlighted under “ Program elements of the FOX” in the above illustration. They indicate newly developed language elements within the BI-integrated planning that were not available in the previous BPS planning!

£ Please note that the following ILQDQFLDO�IXQFWLRQV can be set up using the FOX:

y Perpetual bonds (using program element PERP)

y Currency translation (using program element CURC)

y Discounting (using program element DISC)

y Declining-balance depreciation (using program element DECD)

y Straight-line depreciation (using program element DECL) £

It is also possible to use FOX to determine the date (using program element C2DATE), to set up a rounding function (program element ROUND), and to read attributes and the time-dependent attribute (using program element ATRV and ATRVT). Time characteristics can be used to calculate (program element TMVL).

£ Please note that as a program element, “ Exit” describes the termination criterion of the loop command!

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-24

SAP AG 2006

3URJUDPPLQJ�/RRSV�LQ�)2;

• 'R�ORRSV�¤ 'R��¤ 'R�Q�WLPHV��

• )RUHDFK VWDWHPHQWV�¤ )RUHDFK �9DULDEOH!��¤ )RUHDFK �9DULDEOH!�LQ�5HIGDWD��¤ )RUHDFK �9DULDEOH!�LQ�

6HOHFWLRQ��¤ )RUHDFK �9DULDEOH!�LQ�9DULDEOH��

�

£ In the BI-integrated planning, there are various loop constructs for FOX.

£ The '2�ORRS “ Do n times” (n as a natural number) enables counting without a variable as counter.

£ There are various practical applications for the )25($&+�ORRS, which are described for the characteristic 0COUNTRY, by means of which the loop is executed, and the variable COUNTRY.

y )RUHDFK�&28175<:

- The loop runs through all characteristic values for 0COUNTRY that appear in the current block. In each loop instance, the variable COUNTRY is replaced by one of these values.

y )RUHDFK�&28175<�LQ�5HIGDWD:

- The formula specifies the reference data from the instruction on the right side of the formula for which the system then runs through all the values of 0COUNTRY from the reference data. COUNTRY is replaced in every loop instance.

y )RUHDFK�&28175<�LQ�6HOHFWLRQ� - The system reads the selections for 0COUNTRY, from the filter for example, and runs through all

the characteristic values with this selection. The execution of the formula does not depend on which data record exists or which records are contained in the current block.

y )RUHDFK�&28175<�LQ�9DULDEOH� - Similar to the previous variant. The characteristic values for 0COUNTRY are not read from the

selection, but from the specified variables.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-25

SAP AG 2006

&DOOLQJ�$%$3�)XQFWLRQ�0RGXOHV�IURP�)2;

• (QWHU�WKH�QDPH�RI�WKH�IXQFWLRQ�PRGXOH�LQ�WDEOH�563/)B)',5�

• 8VH�WKH�SURJUDP�HOHPHQW�³&$//�)81&7,21«´LQ�WKH�IRUPXOD�• <RX�FDQ�VWRUH�LPSRUWLQJ��H[SRUWLQJ��DQG�FKDQJLQJ�SDUDPHWHUV�• 7KLV�LV�OLPLWHG�WR�SDUDPHWHU�W\SHV�¥ )��,��'��RU�675,1*¥ &HUWDLQ�FKDUDFWHULVWLFV�DQG�DWWULEXWHV¥ 1R�VWUXFWXUHV�RU�WDEOHV• :KHQ�WKH�$%$3�IXQFWLRQ�PRGXOH�VHQGV�DQ�H[FHSWLRQ��³0HVVDJH�1XPEHU« 5DLVLQJ�1DPH«´ LV�XVHG��

�

£ The program element “&DOO�)XQFWLRQ” is used to integrate ABAP function modules into the FOX editor, so that FOX can indirectly access the ABAP coding.

£ However, no structured data formats such as structures or tables may be used, since only simple data formats are supported.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-26

SAP AG 2006

&XVWRPHU�6SHFLILF�3ODQQLQJ�)XQFWLRQ�7\SHV��(;,7�

¦�§X¨F©:ª>«d¬$¯®�¨W°�¬F±$² ³3² ±^®=´�µ+µ ª>±K¶X©�² ªV·u¸=§W·�±K©:²+ªW· Customer-specificplanning function type

�

£ The “ Exit” function previously familiar from BW-BPS no longer exists in the BI-integrated planning. Instead, you have the option of implementing FXVWRPHU�VSHFLILF�SODQQLQJ�IXQFWLRQ�W\SHV, which are then offered in the Planning Modeler, on the “ Planning Functions” tab page along with the other standard functions.

£ A separate interface must be implemented for such a function. Separate Web dynpros can be programmed.

£ It is not technically possible to integrate a customer-specific planning function into a FOX formula, because the interfaces are not coordinated.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-27

SAP AG 2006

&XVWRPL]LQJ�WKH�&XVWRPHU�'HILQHG�3ODQQLQJ�)XQFWLRQ�7\SH��

7UDQVDFWLRQ�563/)�

�

£ A FXVWRPHU�VSHFLILF�SODQQLQJ�IXQFWLRQ�W\SH is created when:

y no standard planning fucntion and no FOX can map the desired function and

y when the planning function should be used again.

y Examples:

- Copy and Revaluate are to be contained in a combined planning function.

- In a retail company, sales increase on Saturdays and on the day before a holiday. A distribution function is therefore required to distribute the sales over the calendar month on the basis of the number of Saturdays and holidays in the month.

- In the central IT department, certain planning functions are set up as content so that these functions can be used in different projects.

£ Every SODQQLQJ�IXQFWLRQ�W\SH consists of a GHILQLWLRQ�SDUW (meta data), which is created and changed in a transaction (RSPLF1), and an $%$3�22�FODVV, in which the actual procedure is programmed. The class name is part of the definition part.

£ Please note that all the planning functions supplied by SAP are defined in the same way, like the customer-specific planning function types, so that the former can be used as examples for creating customer-specific functions.

£ The function type 'HOHWH (0RSPL_DELETE) is a simple example. There is only one parameter (KYFSEL) for selecting the key figures to be deleted. In the related ABAP class, the two interfaces IF_RSPLFA_SRVTYPE_IMP_CHECK and IF_RSPLFA_SRVTYPE_IMP_EXEC are implemented.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-28

SAP AG 2006


1DPH�RI�WKH�FODVV�FRQWDLQV�WKH�FRGLQJ8VDJH�RI�UHIHUHQFH�GDWD�DQG�EORFNV

8VHU�LQWHUIDFH�FDQ�EH�VHW�XS�XVLQJ�:HE�'\QSUR LWVHOI

�

£ The above illustration shows the procedure for implementing a customer-defined planning function.

£ You first enter the name of the ABAP class that is doing the procedure. For this purpose, the ABAP class must implement one of these two interfaces: y IF_RSPLFA_SRVTYPE_IMP_EXEC y IF_RSPLFA_SRVTYPE_IMP_EXEC_REF .

£ The latter interface is relevant if you require reference data in your procedure. The implementation of the methods of the interfaces named is optional, with the exception of the method EXECUTE. If such data is required, the field “ Reference Data” must be selected in the above illustration.

£ The class can also implement specific check methods, which are executed at runtime. The interface IF_RSPLFA_SRVTYPE_IMP_CHECK is used for this purpose.

£ Planning functions normally use blocks. If you do not want to use this service, you select “ Without Blocks” . In this case, all the characteristics are automatically set as “ characteristics to be changed” .

£ Every planning function has two screens for its Customizing. On one, the characteristics are assigned to the “ Changed” or “ Conditions” area, and in the second, the parameters are entered for the function.

£ These two screens can be structured for customer-specific planning functions: # y The column in which you specify which characteristic is included in the “ changed” area can be

hidden, and the selection table for the “ conditions” is automatically set up. y You can change the sequence of the screens. y You can either have the system automatically generate the screens “ Characteristic Usage” and

“ Parameter Usage” , or you create your own Web dynpro windows.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-29

SAP AG 2006


�

£ On the 3DUDPHWHU�WDE�SDJH, you can define the parameters that will be relevant for the customer-specific planning function type. The following SDUDPHWHU�W\SHV are possible here:

£ (OHPHQWDU\� The value of a specific InfoObject, meaning that every elementary parameter is based on an InfoObject and thus inherits its technical properties. If the InfoObject is a characteristic, the system automatically uses the master data to check the admissibility of a value entered by the user.

£ ,QIR2EMHFW�RI�WKH�,QIR3URYLGHU� The name of an InfoObject from the current InfoProvider (aggregation level). The permissible InfoObjects are defined by means of the restriction for the InfoObject selection.

£ 'DWD�VHOHFWLRQ� Data selection parameters can include the selection criteria of multiple characteristics as they are required for defining filters. Therefore, this is a special selection table. The permissible characteristics are defined by the restriction for the characteristic selection.

£ 6WUXFWXUH� Parameters can be combined to create a structure. These parameters then form the components of the structure parameter. If you declare the structure parameter as a table, the structure then forms the row structure of the resulting table.

£ .H\�ILJXUH�VHOHFWLRQ� This parameter type is for selecting the key figures to be processed. It is therefore a special case of the type “ InfoObject” .

£ For more information, see the F1 help of the input field )XQFWLRQ�W\SH.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-30

SAP AG 2006


�

£ You can use the two arrows in the above illustration to change the sequence of the parameters. You can use “$VVLJQHG�6WUXFWXUH�3” to combine parameters already created. This is not a DataDictionary structure.

£ All the parameters can be used to make tables. A copy function therefore gets a table consisting of a structure containing two selection parameters, which in turn make up the source and target fields of the copy function.

£ Other settings can also be stored, such as whether to use variables for the parameterization or not.

£ If the parameters are fixed, the system generates an input mask from them.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-31

SAP AG 2006

3ODQQLQJ�)XQFWLRQV�² (QKDQFHPHQW��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�8VH�IROORZ�XS�SODQQLQJ�IXQFWLRQV��DQG�LQ�SDUWLFXODU�DVVHVV�WKH�XVDJH�RI�WKH�IRUPXOD�HGLWRU�DQG�WKH�FXVWRPHU�VSHFLILF�SODQQLQJ�IXQFWLRQV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-32

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-33

�([HUFLVHV�

8QLW�� 3ODQQLQJ�)XQFWLRQV�±�(QKDQFHPHQW��


• Configure the FOX formula editor, distribution by reference data and a currency conversion

You have created an input layout for quantity and price planning for the sales managers for an aggregation level in a MultiProvider. Now you want to determine revenues and contribution margins with the help of a FOX formula.

Then you want to distribute by reference data. You want the distribution to be from the material group granularity to the customer group granularity. The distribution is to take place using the actual data as reference data. In this way, the plan data (the distribution takes place in version C, not B) is available to the Key Account Manager as default values.

The Key Account Managers want to see the plan data in both USD and EUR in parallel; as a result, the currency needs to be converted.

1-1 Now you want to take on the role of sales manager and determine turnover and contribution margins and familiarize yourself with the basics of FOX programming.

1-1-1 Navigate to the planning modeler and, for your 7%:��0�� MultiProvider and�aggregation level 0��B$/B��, create a planning function of the type IRUPXOD that calculates the WXUQRYHU�IURP�SULFH �TXDQWLW\, but only for company code �� and material group -8&. Pay attention here to the different granularities of the two plans that were modeled in an earlier unit. Note that you do not need a filter in the planning modeler because we want to execute the planning function in the environment of the BEx Analyzer workbook that we created earlier. Enter the following descriptions for the function you are going to create: Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B)2;�B5(9��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-34

Which fields should be included in the selection as “ fields to be changed” if you need to take into account the different granularities of quantity and turnover on the one hand and price on the other? _____________________________________________________________ _____________________________________________________________ _____________________________________________________________ Which field must always be included due to the modeling of the planning function for the MultiProvider? _____________________________________________________________ Complete this example of how the turnover formula parameter for company code 1000, material group JUC is structured: Select 3& for the XQLW�RI�PHDVXUH. {Key figure 0COPAREVEN, company code 1000, _____________________ _______________________________________, material group JUC}_ Model the function in accordance with the information above. As the program lines appear in the “ IRUPXOD” area, you should first delete the sample code supplied for this area and then carry out the modeling as set out in the task. You do not need to test the function in the planning modeler. 6DYH the planning function.

1-1-2 Now you want to structure the function by executing it for company code �� and for DOO�PDWHULDO�JURXSV H[FHSW material group � (which are all selected in the workbook). To do this, copy the planning function you created in task 1-1-1 and assign the following descriptions: Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B)2;�B5(9�� To solve this task, write a program that creates a “SURJUDP�YDULDEOH” with the description 0* for the PDWHULDO�JURXS and which refers to the characteristic

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-35

�0$7/B*5283. Also implement a )25($&+�ORRS that refers to the program variable. As the function is to be executed for all material groups in the selection from the workbook except the # values, you need to implement an ,)�TXHU\ that excludes the # material group. Be aware in the subsequent formula that you need to set program variable 0* instead of material group JUC but that all the other parameterizations remain constant. 6DYH the planning function.

1-1-3 Copy the planning function that you created in tasks 1-1-2 and assign the following description: Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B)2;�B5(9� Enhance the program as follows: The function should also be executed for all FRPSDQ\�FRGHV and all FRQWUROOLQJ�DUHDV in the BEx Analyzer’s selection, except for company code � and controlling area �. This means that you have to add two further program variables, &R&G and &2�DUHD, including their associated ,)�TXHULHV. How should you model the FOREACH loop command that is to be executed for existing combinations of company code, controlling area and material group only; in other words, without creating zero records? ____________________________________________________________

Implement the program variables mentioned above into the formula. 6DYH the planning function.

1-1-4 To finish, implement an additional warning LQWR�WKH�SURJUDP�IURP�WDVN�� that occurs if the sales managers forget to plan the prices in version B. Start by familiarizing yourself with the warning message that was already created in message maintenance. Open a second mode and navigate as follows: 7RROV��!�$%$3�:RUNEHQFK��!�'HYHORSPHQW��!�3URJUDPPLQJ�(QYLURQPHQW��!�0HVVDJHV��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-36

Message class: =7B%:�� See message no. ��.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-37

1-1-5 Now add the following program lines directly after the actual formula that you created in task 1-1-3: IF {0BRT_PR_AVG,#,#,#,USD,TBW370P##,WG} = 0. MESSAGE E001 (ZT_BW370) WITH WG. ENDIF. 6DYH your planning function again.

1-1-6 You then need a planning function of the type IRUPXOD�HGLWRU to determine the FRQWULEXWLRQ�PDUJLQ for all FRPSDQ\�FRGHV, FRQWUROOLQJ�DUHDV and all PDWHULDO�JURXSV (except the # values in each case). From a business perspective, the contribution margin is calculated as follows: &RQWULEXWLRQ�PDUJLQ� �UHYHQXH�±�YDULDEOH�PDQXIDFWXULQJ�FRVWV� Model this kind of planning function, again paying attention to the different granularities, and using program variables and a FOREACH loop, as well as the corresponding IF queries. Enter the following descriptions: Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B)2;B&0 6DYH your planning function again and then exit the planning modeler.

1-1-6 Navigate to the %([�$QDO\]HU and open the *URXS��B7%:��B%(;B0XOWL3URY workbook in GHVLJQ�PRGH. You should include the first variant for determining revenue in the workbook. To do this, place the cursor in cell $�� and create a Design Item “EXWWRQ” . Make the following configuration: Area: �$��&�� Button text: )XQFWLRQ��UHYHQXH�%.��-8& Select: $GMXVW�DUHD�WR�LWHP�VL]H. In the Static Parameters area, select:

a. Name b. Index c. Value

d. DATA_PROVIDER_FILTER e. 0 f. DATA_PROVIDER_1

g. PLANNING_FUNCTION_NAME h. 0 i. M##_PF_01 (manual entry in uppercase)

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-38

j. CMD k. 0 l. EXECUTE_PLANNING_FUNCTI ON

6DYH your workbook and execute the SODQQLQJ�IXQFWLRQ for the fiscal year ��.

You should now receive the following results for the fiscal years 2010 and 2011 (here is an excerpt):

'R�QRW�VDYH the plan data.

1-1-7 Now you should implement the second variant for determining revenue, which determines the revenues for company code 1000 across all material groups except #. To do this, create a second “EXWWRQ” Design Item for cell $�� and maintain the following values: Area: �$��&�� Button text: )XQFWLRQ��UHYHQXH�%.��PDWHULDO�JURXS�ZLWKRXW�� Select: $GMXVW�DUHD�WR�LWHP�VL]H. In the Static Parameters area, select:

m. Name n. Index o. Value

p. DATA_PROVIDER_FILTER

q. 0 r. DATA_PROVIDER_1

s. PLANNING_FUNCTION_NAME

t. 0 u. M##_PF_02 (manual entry in upper case)

v. CMD w. 0 x. EXECUTE_PLANNING_FUNCTION

6DYH your workbook and execute it for the fiscal year ��. (You do not have to exit the planning session because the second planning function calculates additional values for TWAT and does not overwrite any of the data for JUC).

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-39

You should receive the following results (here is an excerpt):

Do QRW save the plan data. 6DYH�\RXU�ZRUNERRN and exit the planning session to flush the buffer. When asked if you want to save, select “1R” . Then call the ZRUNERRN again. If the buffered plan data is still displayed in the analysis table after you execute revenue determination, you should enable refreshing from the back end by clicking on the “$XWRPDWLF�XSGDWH�DQG�SDXVH” button.

1-1-8 According to task 1-1-3, planning function 0��B3)B�� is aimed at calculating revenues for all company codes except for # and also contains an error message informing the user if prices are not planned. First, include the function as another EXWWRQ in your workbook. To do this, place the cursor in cell $��.

Area: �$��&�� Button text: )XQFWLRQ��UHYHQXH��DOO�FRPSDQ\�FRGHV��HUURU�PHVVDJH Select: $GMXVW�DUHD�WR�LWHP�VL]H. In the Static Parameters area, select:

y. Name z. Index

aa. Value

bb. DATA_PROVIDER_FILTER cc. 0 dd. DATA_PROVIDER_1

ee. PLANNING_FUNCTION_NAME

ff. 0 gg. M##_PF_03 (manual entry in upper case)

hh. CMD ii. 0 jj. EXECUTE_PLANNING_FUNCTION

6DYH your workbook and execute it for the data from the fiscal year ��. Now UHPRYH the SODQ�GDWD�IRU�WKH�SULFHV from �� and ��, by setting the cell value to ]HUR. In this way, you can simulate forgetting to plan prices and

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-40

thereby cause the formula editor to output the error message when you execute the planning function. Execute the last function you executed. You should now receive the following messages:

([LW the VHVVLRQ again ZLWKRXW VDYLQJ your plan data.

When the system then queries whether you would like to save, select “1R” . Then open the workbook again and, if necessary, refresh it by clicking on the “$XWRPDWLF�XSGDWH�DQG�SDXVH,” in order to display the price planning data in the analysis table. 'R�QRW�H[HFXWH the IXQFWLRQ again.

1-1-9 Your aim now is to execute the functions for both revenue calculation and contribution margin accounting using a shared button. To do this, assign the planning function 0��B3)B�� to the existing “)XQFWLRQ��UHYHQXH��DOO�FRPSDQ\�FRGHV��HUURU�PHVVDJH” . The two functions are to be executed directly after each other in the correct business order (determining revenues before contribution margins) at the press of a button.� How should you proceed in the Statistic Parameters area? Explain this by entering the relevant tax information into the following table:

kk. Name ll. Index mm. Value

nn. oo. pp.

qq. rr. ss.

tt. uu. vv.

ww. xx. yy.

zz. aaa. bbb.

ccc. ddd. eee.

Transfer these settings to your EXWWRQ. Then change the EXWWRQ�WH[W for this button as follows: “)XQFWLRQ��UHYHQXH�DQG�GDWDEDVHV” . 6DYH your workbook and execute it for ��.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-41

You should receive the following results (here is an excerpt):

6DYH the SODQ�GDWD. Then exit the BEx Analyzer and return to the SODQQLQJ�PRGHOHU.

1-2 In the following, you should distribute the sales quantities, revenues and contribution margins planned at the product group granularity to the customer group granularity. This is the granularity of the Key Account Managers. The distribution will take place in a C version.

1-2-1 First, go to the SODQQLQJ�PRGHOHU�for aggregation level 0��B$/B��of InfoProvider 7%:��0��. Here, create a FRS\�IXQFWLRQ�that copies the data from version %�to version &, but only for the NH\�ILJXUHV�VDOHV�TXDQWLW\��UHYHQXH�DQG�FRQWULEXWLRQ�PDUJLQ. Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B&23<�� Place the “9HUVLRQ” field in the ILHOGV�WR�EH�FKDQJHG. Then, to ensure that the function will be executed for the data from InfoProvider 7%:��6�� only, include the “ ,QIR3URYLGHU” field in the FRQGLWLRQV. Configure the function using the above information and then VDYH it. Then exit the planning modeler�and return to the %([�$QDO\]HU and, from there, into your *URXS��B7%:��B%(;B0XOWL3URY workbook.

1-2-2 After you have created the copy function in task 1-2-1, you want to make the data for both the B and C versions visible in the analysis table. To do this, include the Design Item 1DYLJDWLRQ�DUHD in cell $��, referring to the '$7$B3529,'(5B�. If you look at the 'LPHQVLRQV tab page in the Design Item, the 9HUVLRQ dimension is not present because it is in the Query Designer and is only

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-42

assigned a single value here (version B) in the “ Characteristic Restrictions” area. This means that it is not possible to navigate. For this reason, leave the dimensions area empty in this Design Item. First, VDYH the ZRUNERRN and close it. Now, navigate in the 4XHU\�'HVLJQHU to your plan query with the technical name 0��B$/B��B3ODQTXHU\B��B0XOWL3 and limit the version to %�DQG & in the FKDUDFWHULVWLF�UHVWULFWLRQV area. 6DYH the plan query and exit the Query Designer. Navigate back to the BEx Analyzer and open your *URXS��B7%:��B%(;B0XOWL3URY workbook. Open the 1DYLJDWLRQ�DUHD Design Item again. Then select $XWR)LW. For the “$UHD” , write: �$��&�� Select “0DWHULDO�JURXS” , “9HUVLRQ” , “)LVFDO�\HDU” and “.H\�ILJXUHV” in the “6HOHFWHG�'LPHQVLRQV” area. All the other settings remain unchanged. 6DYH the workbook and execute it for the fiscal year ��. Set only the ILOWHU in the navigation to version &. You should receive the following display (here is an excerpt):

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-43

1-2-3 Now implement the copy function. To do this, create the EXWWRQ Design Item again for cell $�� and enhance it as follows:

Area: �$��&�� Button text: )XQFWLRQ��FRS\�YHUVLRQ�%�!&

Select: $GMXVW�DUHD�WR�LWHP�VL]H. In the Static Parameters area, select:

fff. Name ggg. Index

hhh. Value

iii. DATA_PROVIDER_FILTER

jjj. 0 kkk. DATA_PROVIDER_1

lll. PLANNING_FUNCTION_NAME

mmm. 0 nnn. M##_PF_05 (manual entry in upper case)

ooo. CMD ppp. 0 qqq. EXECUTE_PLANNING_FUNCTION

Then VDYH the workbook and execute it for the fiscal year ��. Version & should be set in the navigation block’s filter. Now H[HFXWH the FRS\�IXQFWLRQ. You should receive the following display (here is an excerpt):

Then VDYH the SODQ�GDWD and set the filter in the navigation block back to version %, so that the planner can later always view the data in the material group granularity. Then VDYH the ZRUNERRN.

1-2-4 Now you want to distribute the data from version C from the material group granularity to the customer group. You only want to distribute the key figures sales figures, revenue and contribution margin. The aim is to GLVWULEXWH�E\�UHIHUHQFH�GDWD, where the actual data at the customer group granularity that is contained in another InfoProvider and is present in version D is used as a reference.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-44

In general, you want to distribute the sales quantity in the plan in the same proportion as the sales quantity in the actual data. The same is true for the revenue in the plan and the actual revenue and the contribution margin in the plan and the actual contribution margin. The aim of distribution is not to distribute the sales quantity, the revenue and the contribution margin in the plan in proportion to the actual sales quantity. This has to be taken into account when modeling the planning function. The actual data used as reference data is contained in a query in InfoProvider 7B%:��B�, which all exercise groups should read-access in parallel. This query has the following descriptions: Technical name: ,B5()(5(1&(48(5<B&867*5283 Description: ´ 7%:��B,B54B&867*5283�� The query should appear as follows:

Include this query as an DQDO\VLV�WDEOH in your *URXS��B7%:��B%(;B0XOWL3URY workbook. Place this DQDO\VLV�WDEOH in cell $�� and, in the analysis table's $UHD field, write “ �$��/��” . This area size ensures that the reference data from both years can be displayed. Place the cursor in cell $�� and enter the following text in font size ��, the color UHG and EROG: “5HIHUHQFH�GDWD�LQ�FXVWRPHU�JURXS�JUDQXODULW\�IRU��SODQ�\HDUV” . 6DYH your workbook and execute it for the fiscal year ��. Then exit the BEx Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-45

1-2-5 Now you need to model the distribution function by reference data in the planning modeler. The distribution has to be modeled for the MultiProvider because the reference data is in another InfoProvider than the distribution data. As a result, InfoProvider T_BW370_4, which contains the reference data, was already included in MultiProvider 7%:��0�� for you. Open a second session and create a second aggregation level for your InfoProvider 7%:��0��. To do this, copy aggregation level 0��B$/B��, in which the distribution is modeled. Technical name: 0��B$/B�� Description: 7%:��B0��B$/��. Add the characteristic FXVWRPHU�JURXS to the aggregation level and activate this. Now create a planning function of the type “'LVWULEXWLRQ�E\�UHIHUHQFH�GDWD” for this aggregation level. Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B',675,%B5()�� Which field do you have to include in the fields to be changed if you want to distribute from the material group to the customer group? ___________________________________________________________ Include the characteristic ,QIR3URYLGHU in the fields for FRQGLWLRQV, so that you can later execute the planning function in the MultiProvider for the data from InfoProvider 7%:��6�� only. This means that you have implemented a safety check as described in the training materials. Only include the key figures VDOHV�TXDQWLW\, UHYHQXH and FRQWULEXWLRQ�PDUJLQ in the distribution. Leave the field “ Reference key figure (optional)” free to prevent all three key figures being distributed by one key figure (namely the key figure selected here). In the “5HIHUHQFH�YDOXHV�RQ�DQ\�EORFN�FKDUDFWHULVWLFV” , include the attribute ' for the version and include the attribute 7B%:��B� for the InfoProvider field.

Then select “&UHDWH�HQWULHV�PDQXDOO\” and click on the “&UHDWH�/LQH” button.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-46

In the “&KDQJH�)URP” field, select “ �” and include “ ��” in the “&KDQJH�7R” field. On the 6HOHFWHG�&RQGLWLRQ tab page, select InfoProvider 7%:��6��. 6DYH the function and exit the planning modeler.

1-2-6 In addition to the planning function, you also require a SODQ�TXHU\ in which you can later view the results of the distribution in version C. The planning function will refer to this plan query's selections. Create this query for your 0��B$/B�� aggregation level E\�FRS\LQJ it. After copying the plan query, you have to adjust the InfoProviders in the copied query. The query should appear as follows (here is an excerpt):

Note that the actual columns are not ready for input and the plan columns can only be filled by the planning function. Open a second session and navigate via %XVLQHVV�([SORUHU��!�4XHU\��!�&RS\ to the “&RS\LQJ�TXHULHV�IRU�,QIR3URYLGHUV” screen. Enter the following information in the input screen: Source InfoProvider: 0��B$/B��(aggregation level) Target InfoProvider: 0��B$/B��(aggregation level) The next screen displays the queries for the source InfoProvider. Select the query with the following descriptions: Description: 7%:��B0��B$/��B',675,%B5() Technical name: 0��B$/B��B'LVWULEB5().

When you copy, the system assigns a technical name, which results from the template query's technical description, and adds a number to it. Make a note of the new technical name for your plan query:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-47

___________________________________________________________ Now, navigate to the 4XHU\�'HVLJQHU and call your new query. On the “2SHQ�TXHU\��VHOHFW�TXHU\” screen, you should now set up the WHFKQLFDO�GHVFULSWLRQV (system icon at top right: “'LVSOD\�REMHFW�QDPHV�DV«” and then search for the query you noted down before. Next, call this query and change its GHVFULSWLRQ as described in the following. On the right-hand edge of the screen, you can see the “3URSHUWLHV” area. Here, select the top field in the query, then select the “*HQHUDO” tab page and enter the following new QDPH for the query in the “'HVFULSWLRQ” field: “7%:��0��B$/��B34B',675,%B5()” �� 6DYH the query. Then, in the “&KDUDFWHULVWLF�UHVWULFWLRQV” area, replace 7%:��6�� (the selection included in the query) with 7%:��6�� for the characteristic: ,QIR3URYLGHU. Selection T_BW370_4 also remains. Then navigate to the “&ROXPQV” area and replace the InfoProvider included in the columns “3ODQ�VDOHV�TXDQWLW\” , “3ODQ�UHYHQXH” and “3ODQ�FRQWULEXWLRQ�PDUJLQ” with your InfoProvider, 7%:��6�� 6DYH the query and execute it for the fiscal year ��. Actual data should be displayed for all the customer groups and plan data for the # customer group. Then exit the Query Designer.

1-2-7 Now, you should include the query that you created by copying in your *URXS��B7%:��B%(;B0XOWL3URY workbook. To do this, place the cursor in cell $�� and create another “$QDO\VLV�WDEOH” Design Item. Then select the query you created by copying, 7%:��0��B$/��B34B',675,%B5(). This query is known internally as DATA_PROVIDER_2. In Design Item “$QDO\VLV�WDEOH” , select “$XWR)LW” . Place the cursor in cell $�� and write the following: “$FWXDO�DQG�SODQ�GDWD�FRPSDUHG�WR�EHIRUH�DQG�DIWHU�GLVWULEXWLRQ�E\�FXVWRPHU�JURXS” . Select a UHG coloring, EROG and font size ��. 6DYH your workbook and execute it for ��.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-48

1-2-8 Now, you should include the distribution function with the technical name 0��B3)B�� into your workbook. To do this, place the cursor in cell $�� and create Design Item “%XWWRQ” for the cell. Make the following configuration: Area: �$��&�� Button text: )XQFWLRQ��GLVWULEXWLRQ�E\�UHIHUHQFH�GDWD Select: $GMXVW�DUHD�WR�LWHP�VL]H. In the Static Parameters area, select:

rrr. Name sss. Index ttt. Value

uuu. DATA_PROVIDER_FILTE R

vvv. 0 www.

xxx. PLANNING_FUNCTION_N AME

yyy. 0 zzz. M##_PF_06 (manual entry in upper case)

aaaa. CMD bbbb. 0 cccc. EXECUTE_PLANNING_FUNCTION

6DYH the workbook and execute it for the fiscal year ��. You should receive the following display before distribution (here is an excerpt):

Then H[HFXWH the GLVWULEXWLRQ�IXQFWLRQ. You should receive the following display after distribution (here is an excerpt):

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-49

6DYH your SODQ�GDWD.

1-3 The Key Account Managers want to also carry out JUDSKLF�UHSRUWV in the Bex Analyzer. The aim of this is that the user selects a customer group and the plan data for the customer group is then provided in a graphic.

1-3-1 To do this, first navigate to the 4XHU\�'HVLJQHU and save your 7%:��0��B$/��B34B',675,%B5() query there with the descriptions: Description: 7%:��B0��B$/��B''%B&867*53 7HFKQLFDO�QDPH�� 0��B$/B��B'''B&867553�� 6DYH the query that you created by copying. In the copied query, remove the characteristic FXVWRPHU�JURXS from the drilldown and make sure that this characteristic is contained in the characteristic restrictions with the attribute ��. Then drag the customer group into the “'HIDXOW�YDOXHV” area. It would also be possible to include the customer group in the free characteristics or the drilldown, so that you could then later select the customer group as a dimension in the dropdown box. Including the characteristic alone in the characteristic restrictions is not enough to be able to use the dropdown box. You could also have created a master data query for the customer group and then you could use this query as the basis for the dropdown box. We did not use this option. Then VDYH the query again and exit the Query Designer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-50

1-3-2 Return to your *URXS��B7%:��B%(;B0XOWL3URY workbook and navigate to the VHFRQG�ZRUNVKHHW named “6KHHW��” . The additional reporting is to take place here. Place the cursor in cell $�� and create another analysis table. Include the query with the technical name 0��B$/��B3ODQTXHU\B''%B&867*53 in this analysis table. Then select $XWR)LW again. This query is executed internally as DATA_PROVIDER_4. Now place the cursor in cell $� and create the Design Item GURSGRZQ�ER[ so that you can select a customer group for which the analysis table then displays the data and which is reported graphically. On the *HQHUDO tab page,�VHOHFW '$7$B3529,'(5B�, “'LVSOD\�/DEHO�” 'HVHOHFW the ³$GMXVW�DUHD�WR�LWHP�VL]H´ field. On the 'LPHQVLRQV tab page, select the characteristic &XVWRPHU�JURXS as the dimension and select read mode 3RVWHG�YDOXHV, as well as .H\�DQG�WH[W. On the 7DUJHW'DWD3URYLGHU tab page, select '$7$B3529,'(5B�. Create a 6DYH�EXWWRQ in cell $� and a 5HIUHVK�EXWWRQ in cell &��. 6DYH your workbook and execute it for the fiscal year ��. You should see the following display:

Change the customer group selection in the dropdown box and click on the “5HIUHVK” button. The data in the associated analysis table should be displayed according to the customer group selected. Place the cursor in cell $� and write “$GGLWLRQDO�UHSRUWV” in font size ��, EROG and UHG. Rename the worksheet with the description 6KHHW�� as “$GGLWLRQDO�UHSRUWV�DQG�JUDSKLFV” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-51

1-3-3 6DYH the workbook again and remain on the second worksheet in execution mode. +LGH the VXEWRWDOV�IRU�WKH�FROXPQV�³)LVFDO�\HDU´�WR�³0DWHULDO�JURXS´ for the graphic that is structured subsequently in the analysis table that you already built and executed. To do this, place the cursor on the title header for each of these columns, right-clicking and selecting “3URSHUWLHV«´. On the next screen, select “$OZD\V” in the “6XSSUHVV�UHVXOWV�URZV´ field. This procedure ensures that only the relevant data is linked into the graphic that is created next. 6DYH your workbook.

1-3-4 Now you want to link in an Excel graphic that displays the SODQ�YDOXHV for the selected customer group. In the workbook's execution mode, place the cursor in cell $�� and open the “&KDUW�ZL]DUG” . Select &ROXPQ as the “&KDUW�7\SH” and then select &OXVWHUHG�&ROXPQ�ZLWK�D��'�YLVXDO�HIIHFW. On the next screen and here on the 'DWD�5DQJH tab page, select &ROXPQV for the “6HULHV�LQ” field and select the data columns “3ODQ�VDOHV�TXDQWLW\” , “3ODQ�UHYHQXH” and “3ODQ�FRQWULEXWLRQ�PDUJLQ” as the 'DWD�5DQJH. On the 6HULHV tab page, first remove all the series in the “6HULHV” area. Then go to the “$GG” button and enter “3ODQ�VDOHV�TXDQWLW\” in the “1DPH” field. Then place the cursor in the “9DOXHV” field and select the entire data area for the analysis table that refers to the “3ODQ�VDOHV�TXDQWLW\” . Next, click on “$GG” to create a new series. In the “1DPH” field, enter the description “3ODQ�UHYHQXH” and in the “9DOXH” field, select the data area again under the “3ODQ�UHYHQXH” column in the analysis table. Proceed in the same way with the “3ODQ�FRQWULEXWLRQ�PDUJLQ” . On the next screen and here on the 7LWOHV tab page, write “3ODQ�GDWD�IRU�VHOHFW�FXVWRPHU�JURXS” for the “&KDUW�7LWOH” and leave all the other fields empty. On the $[LV tab page, deselect “&DWHJRU\��;��D[LV” and “9DOXH�=�D[LV” . On the *ULGOLQHV tab page, deselect all the fields. On the /HJHQG tab page, select “6KRZ�/HJHQG” and “%RWWRP". On the 'DWD /DEHOV tab page, select “9DOXH” . On the 'DWD�7DEOH tab page, deselect all the fields. On the last of the wizard's screens, “&KDUW�:L]DUG�±�6WHS��±�&KDUW�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-52

/RFDWLRQ” , select “$V�REMHFW�LQ” and then select the worksheet with the description “$GGLWLRQDO�UHSRUWV�DQG�JUDSKLFV” . You should now have run through the entire wizard and the graphic should appear. 0RYH the graphic that is now being built into cell $�� and drag the graphic to fit the entire column width in the analysis table. Color the “3ODQ�UHYHQXH” UHG, the “3ODQ�FRQWULEXWLRQ�PDUJLQ” JUHHQ and leave the color of the “3ODQ�VDOHV�TXDQWLW\” EOXH. 'UDJ the QXPHULFDO�YDOXHV from the three columns XSZDUGV to give you a better overview. 6DYH the workbook.

1-3-5 Now use the dropdown box to select a FXVWRPHU�JURXS�RI�\RXU�FKRRVLQJ, then click on the UHIUHVK�EXWWRQ and take a look at the data and the graphic which appear. Change the selection in the dropdown box again and take another look at the adjusted data in the analysis table and the graphic. You might, for example, receive the following display if you select customer group 02:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-53

1-3-6 Now remove the gridlines from the second worksheet. To do this, navigate along 7RROV��!�2SWLRQV on the subsequent screen to the 9LHZ tab page and deselect *ULGOLQHV. 6DYH the workbook.

1-4 Now return to the “6KHHW��” worksheet and rename it “0XOWL3URYLGHU�VFHQDULR” . To finish off, you want to model a currency conversion for the plan revenues and plan contribution margins from USD to EUR for the data in plan version C. You also want to ensure that, even if this planning function is triggered more than once, the currency is only converted once. To do this, you have to carry out various operations: 1. You have to copy the query for cell A112 and restructure it for a currency comparison of the plan data. 2. Then, you have to include the query in the BEx Analyzer. 3. You have to build a currency conversion function in the planning modeler, as well as a delete function that can undo the currency conversion. Both of these function are structured via the MultiProvider (it would also be possible to build them on InfoProvider TBW370S## ). As a result, you have to ensure that they are only executed for the InfoProvider. You achieve this by including the characteristic InfoProvider with the attribute TBW370S## in the conditions area for these functions. 4. You have to merge the two functions in the planning modeler, which means that you have to build a filter in the planning modeler. 5. You have to include the sequence in the BEx Analyzer and make a reference to the DATA_PROVIDER from step 2.

1-4-1 Navigate to the Query Designer and save your query with the description “7%:��B0��B$/��B34B',675,%B5()” under� the following descriptions� 'HVFULSWLRQ��7%:��B0��B$/��B34B&XUUHQF\B7 Technical name: 0��B$/B��B3ODQTXHU\B&XUUHQF\B7 . Make the following changes in the copied query: In the FKDUDFWHULVWLF�UHVWULFWLRQV area, add (85 to the characteristic &XUUHQF\, which already includes USD. 5HPRYH the “XQLW�RI�PHDVXUH” with “67” . 5HPRYH the ,QIR3URYLGHU “7B%:��B�” . 5HPRYH “9HUVLRQ�'” . In the &ROXPQV area, remove the WKUHH�DFWXDO�FROXPQV and the “3ODQ�VDOHV�TXDQWLW\” �SODQ�FROXPQ. In the two remaining plans, include the characteristic &XUUHQF\ and set 86'.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-54

Make a note in the KHDGLQJ for these columns that the amounts are displayed in GROODUV. 5HPRYH the characteristics “9HUVLRQ” and “ ,QIR3URYLGHU” from the two remaining columns. Now FRS\ both the UHYHQXH�FROXPQ and the FRQWULEXWLRQ�PDUJLQ�FROXPQ and FKDQJH the KHDGHU�WH[W in the copied columns to include (85. Then include the characteristic FXUUHQF\ with the attribute (85 in each of the copied columns. For the two data columns in “86'” , select “'DWD�FDQQRW�EH�FKDQJHG” and select “'DWD�FDQ�EH�FKDQJHG�E\�SODQQLQJ�IXQFWLRQV” for the two “(85” columns. Note that the query is based on a MultiProvider, as are the subsequent work steps. From a performance point of view, it would be better to create the query directly at an aggregation level of InfoProvider TBW370S## and to create the query on this. However, that option would be more complex and we therefore chose the method explained above. Next, VDYH the plan query and execute it for the fiscal year ��. Here is an excerpt of what you should see:

Now exit the Query Designer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-55

1-4-2 You should include this query in your workbook on the ILUVW�ZRUNVKHHW for cell $�� as an DQDO\VLV�WDEOH. Internally, this query corresponds to DATA_PROVIDER_5. Select “$XWR)LW” again. 6DYH your workbook and execute it for ��. Do not close the workbook.

1-4-3 Now, navigate to the SODQQLQJ�PRGHOHU and select your InfoProvider 7%:��0��. Then select the aggregation level with the technical name 0��B$/B��. Copy the aggregation level as follows: Technical name: 0��B$/B�� Description: 7%:��B0��B$/�� . Remove the key figures VDOHV�TXDQWLW\, SULFH, the PDQXIDFWXULQJ�FRVWV and the XQLW�RI�PHDVXUH from this level. $FWLYDWH the aggregation level. You need to create a ILOWHU for this aggregation level. The filter is to be used for converting the currency in the revenue and contribution margin plan data: Technical name: 0��B)B�� Description: 7%:��B0��B$/��B)�� Include DOO�WKH�FKDUDFWHULVWLFV in the filter and include the following selections: Customer group: �� Fiscal year variant: .� InfoProvider: 7%:��6�� Version: & Controlling area: �� Company code: �� Currency: 86'��(85 Material group: 7:$7��-8& Fiscal year: 9DULDEOH�*URXS��B9$5B)<B��B30 6DYH the filter.

1-4-4 Now create the FXUUHQF\�FRQYHUVLRQ�IXQFWLRQ for aggregation level 0��B$/B��. Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B&855B7 The currency field is automatically present in the ",V�FKDQJHG" area.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-56

Select “ ,QIR3URYLGHU” and “9HUVLRQ” in the “ ,V�XVHG�LQ�FRQGLWLRQ” area and select “7%:��6��” �DQG�“&” � Configure the concrete processing rule as follows:

dddd. Target Key Figure

eeee. Source Key Figure ffff. Currency Translation Type

gggg. Revenue hhhh. Revenue iiii. BPS (data record CUR to EUR)

jjjj. Contribution Margin 1

kkkk. Contribution Margin 1

llll. BPS (data record CUR to EUR)

1-4-5 In the same aggregation level, create a GHOHWH�IXQFWLRQ that deletes the data records in Euro. Technical name:��0��B3)B�� Description: 7%:��B0��B$/��B3)��B'(/B&855

Include the fields “ ,QIR3URYLGHU” , “9HUVLRQ” and “&XUUHQF\�.H\” in the FRQGLWLRQ�ILHOGV and select InfoProvider 7%:��6��, version & and the currency key (85. Select DOO�NH\�ILJXUHV and VDYH the planning function.

1-4-6 Then create a SODQQLQJ�VHTXHQFH, in which the delete function is positioned EHIRUH the currency conversion function. Both refer to the same filter, 0��B)B��, at aggregation level 0��B$/B�� . Technical name: 0��B6B�� Description: 7%:��B0��B$/��B6��

6DYH the planning sequence. Then exit the planning modeler.

1-4-7 Navigate to the %([�$QDO\]HU and open the ILUVW�ZRUNVKHHW in your workbook *URXS�B7%:��B%(;B0XOWL3URY. Now link the sequence of Design Item “%XWWRQ” into the workbook. Place the cursor in cell $�� and define the button as follows: Area: �$��&�� Button text: )XQFWLRQ��FXUUHQF\�FRQYHUVLRQ�86'�!(85 Deselect “$GMXVW�DUHD�WR�LWHP�VL]H”

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-57

mmmm. Name nnnn. Index oooo. Value

pppp. PLANNING_SEQUENCE_NAME qqqq. 0 rrrr. 0��B6B�� (manual entry)

ssss. DATA_PROVIDER tttt. 0 uuuu. DATA_PROVIDER_5

vvvv. CMD wwww. 0 xxxx. EXECUTE_PLANNING_SEQUENCE

6DYH your workbook and execute it for the fiscal year ��. Then execute the FXUUHQF\�FRQYHUVLRQ. You should receive the following display (here is an excerpt):

6DYH your plan data. Then H[HFXWH the FXUUHQF\�FRQYHUVLRQ DJDLQ. This should result in the same data as the first time you executed the function: there should be no “ double" calculations.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-58

1-5 To finish, you want to remove the gridlines from the first worksheet in your workbook. To do this, navigate along 7RROV��!�2SWLRQV on the subsequent screen to the 9LHZ tab page and deselect *ULGOLQHV. Select the file: 3LFWXUH�B7%:��SQJ as the EDFNJURXQG�FRORU for the ILUVW�ZRUNVKHHW and 3LFWXUH�B7%:��SQJ as the background color for the VHFRQG�ZRUNVKHHW. The files are in your system’s Business Workplace. To find these files, open a new session, then navigate via 0HQX��!�%XVLQHVV�:RUNSODFH to the “6KDUHG�)ROGHUV” and select “7UDLQLQJ��%:�0DWHULDO�IRU�%:�7UDLQLQJ” and then “%:��%:��0DWHULDO” . Export both of the files mentioned above to your computer's GHVNWRS. Assign them the following descriptions: 3LFWXUH�B7%:��B*URXS�� and 3LFWXUH�B7%:��B*URXS�� . Then return to your workbook and add the two background colors as described above. Then VDYH your workbook again and exit the BEx Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-59

�6ROXWLRQV�

8QLW�� 3ODQQLQJ�)XQFWLRQV�±�(QKDQFHPHQW��

1-1 Now you want to take on the role of sales manager and determine turnover and contribution margins and familiarize yourself with the basics of FOX programming.

1-1-1 Navigate to the planning modeler and, for your 7%:��0�� MultiProvider and�aggregation level 0��B$/B��, create a planning function of the type IRUPXOD that calculates the WXUQRYHU�IURP�SULFH� �TXDQWLW\, but only for company code �� and material group -8&.

Pay attention here to the different granularities of the two plans that were modeled in an earlier unit. Note that you do not need a filter in the planning modeler because we want to execute the planning function in the environment of the BEx Analyzer workbook that we created earlier. Enter the following descriptions for the function you are going to create: Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B)2;�B5(9�� Which fields should be included in the selection as “ fields to be changed” if you need to take into account the different granularities of quantity and turnover on the one hand and price on the other? Company code [0COMP_CODE], sales unit [0COPASLQTU], controlling area [0CO_AREA], currency[0CURRENCY], InfoProvider [0INFOPROV], material group [0MATL_GROUP] and key figure name.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-60

Which field must always be included due to the modeling of the planning function for the MultiProvider? InfoProvider [0INFOPROV] In the “ For Characteristic Usage” area, you should now see the following:

Complete this example of how the turnover formula parameter for company code 1000, material group JUC is structured: Select 3& for the XQLW�RI�PHDVXUH. Note that, after you select 3& (pieces), 67 (piece) still appears in the value help as the selected value. {Key figure name 0COPAREVEN, company code1000, sales quantity of measure PC, controlling area1000, currency USD, InfoProvider TBW370_S##,material group JUC} or: {Key figure name 0COPAREVEN, 0COMP_CODE 1000, 0COPASLQTU PC, 0CO_AREA 1000, 0CURRENCY USD, 0INFOPRO TBW370_S##, 0MATL_GROUP JUC} Model the function according to the information above. As the program lines appear in the “ IRUPXOD” area, you should first delete the sample code supplied for this area and then carry out the modeling as set out in the task. Do QRW use the “ Input help for operands” on the right-hand side of the FOX editor. Instead, enter the formula GLUHFWO\ in the large white “ Formula” input area.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-61

You can insert comment lines limited by into the documentation. Commands in the FOX editor can stretch over more than one line, so conclude each command with “ �” . Before saving, check whether the formula syntax is correct. Use the “&KHFN�IRUPXOD” button to do this.

Your window should now look like this:

Do not test the function in the planning modeler. 6DYH the planning function.

1-1-2 Now you want to structure the function by executing it for company code �� and for DOO�PDWHULDO�JURXSV H[FHSW material group � (which are all selected in the workbook). To do this, copy the planning function you created in task 1-1-1 and assign the following descriptions: Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B)2;�B5(9�� To solve this task, write a program that creates a “SURJUDP�YDULDEOH” with the description 0* for the PDWHULDO�JURXS and which refers to the characteristic �0$7/B*5283. Also implement a )25($&+�ORRS that refers to the program variable. As the function is to be executed for all material groups in the selection from the workbook except the # values, you need to implement an ,)�TXHU\ that excludes the # material group. Be aware in the subsequent formula that you need to set program variable 0* instead of material group JUC but that all the other parameterizations remain constant.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-62

$OVR�QRWH�WKH�IROORZLQJ: 1) You have to declare variable MG at the beginning. The syntax for this is: DATA [variable name] TYPE [techn. name of the characteristic used] 2) The FOREACH loop has to end with ENDFOR. 3) The IF statement has to end with ENDIF. At the end, the following content should be in the FOX editor:

6DYH the planning function.

1-1-3 Copy the planning function that you created in tasks 1-1-2 and assign the following description: Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B)2;�B5(9� Enhance the program as follows: The function should also be executed for all FRPSDQ\�FRGHV and all FRQWUROOLQJ�DUHDV in the BEx Analyzer’s selection, except for company code � and controlling area �. This means that you have to add two further program variables, &R&G and &2�DUHD, including their associated ,)�TXHULHV. How should you model the FOREACH loop command that is to be executed for existing combinations of company code, controlling area and material group only; in other words, without creating zero records? FOREACH 0COMP_CODE, 0CO_AREA, 0MATL_GROUP.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-63

Implement the program variables mentioned above into the formula.

6DYH the planning function.

1-1-4� To finish, implement an additional warning LQWR�WKH�SURJUDP�IURP�WDVN�� that occurs if the sales managers forget to plan the prices in version B. Start by familiarizing yourself with the warning message that was already created in message maintenance. Open a second mode and navigate as follows: 7RROV��!�$%$3�:RUNEHQFK��!�'HYHORSPHQW��!�3URJUDPPLQJ�(QYLURQPHQW��!�0HVVDJHV�� Message class: =7B%:�� See message no. ��. Now add the following program lines directly after the actual formula that you created in task 1-1-3: IF {0BRT_PR_AVG,#,#,#,USD,TBW370P##,WG} = 0. MESSAGE E001 (ZT_BW370) WITH WG. ENDIF.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-64

6DYH your planning function again.

1-1-5� You then need a planning function of the type IRUPXOD�HGLWRU to determine the FRQWULEXWLRQ�PDUJLQ for all FRPSDQ\�FRGHV, FRQWUROOLQJ�DUHDV and all PDWHULDO�JURXSV (except the # values in each case). From a business perspective, the contribution margin is calculated as follows: &RQWULEXWLRQ�PDUJLQ� �UHYHQXH�±�YDULDEOH�PDQXIDFWXULQJ�FRVWV� Model this kind of planning function, again paying attention to the different granularities, and using program variables and a FOREACH loop, as well as the corresponding IF queries.

Enter the following descriptions:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-65

Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B)2;B&0 6DYH your planning function again and then exit the planning modeler.

1-1-6 Navigate to the %([�$QDO\]HU and open the *URXS��B7%:��B%(;B0XOWL3URY workbook in GHVLJQ�PRGH. You should include the first variant for determining revenue in the workbook. To do this, place the cursor in cell $�� and create a Design Item “EXWWRQ” . Make the following configuration: Area: �$��&�� Button text: )XQFWLRQ��UHYHQXH�%.��-8& Select: $GMXVW�DUHD�WR�LWHP�VL]H. In the Static Parameters area, select:

1DPH� ,QGH[� 9DOXH�DATA_PROVIDER_FILTER 0 DATA_PROVIDER_1

PLANNING_FUNCTION_NAME 0 0��B3)B��PDQXDO�HQWU\�LQ�XSSHUFDVH� CMD 0 EXECUTE_PLANNING_FUNCTION

6DYH your workbook and execute the SODQQLQJ�IXQFWLRQ for the fiscal year ��.

You should now receive the following results for the fiscal years 2010 and 2011 (here is an excerpt):

'R�QRW�VDYH the plan data.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-66

1-1-7 Now you should implement the second variant for determining revenue, which determines the revenues for company code 1000 across all material groups except #. To do this, create a second “EXWWRQ” Design Item for cell $�� and maintain the following values: Area: �$��&�� Button text: )XQFWLRQ��UHYHQXH�%.��PDWHULDO�JURXS�ZLWKRXW�� Select: $GMXVW�DUHD�WR�LWHP�VL]H. In the Static Parameters area, select:


PLANNING_FUNCTION_NAME 0 0��B3)B��PDQXDO�HQWU\�LQ�XSSHU�FDVH� CMD 0 EXECUTE_PLANNING_FUNCTION

6DYH your workbook and execute it for the fiscal year ��. (You do not have to exit the planning session because the second planning function calculates additional values for TWAT and does not overwrite any of the data for JUC). You should receive the following results (here is an excerpt):

Do QRW save the plan data. 6DYH�\RXU�ZRUNERRN and exit the planning session to flush the buffer. When asked if you want to save, select “1R” . Then call the ZRUNERRN again. If the buffered plan data is still displayed in the analysis table after you execute revenue determination, you should enable refreshing from the back end by clicking on the “$XWRPDWLF�XSGDWH�DQG�SDXVH” button.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-67

1-1-8 According to task 1-1-3, planning function 0��B3)B�� is aimed at calculating revenues for all company codes except for # and also contains an error message informing the user if prices are not planned. First, include the function as another EXWWRQ in your workbook. To do this, place the cursor in cell $��.

Area: �$��&�� Button text: )XQFWLRQ��UHYHQXH��DOO�FRPSDQ\�FRGHV��HUURU�PHVVDJH Select: $GMXVW�DUHD�WR�LWHP�VL]H. In the Static Parameters area, select:



6DYH your workbook and execute it for the data from the fiscal year ��. Now UHPRYH the SODQ�GDWD�IRU�WKH�SULFHV from �� and ��, by setting the cell value to ]HUR. In this way, you can simulate forgetting to plan prices and thereby cause the formula editor to output the error message when you execute the planning function. Execute the last function you executed. You should now receive the following messages:

([LW the VHVVLRQ again ZLWKRXW VDYLQJ your plan data. When the system then queries whether you would like to save, select “1R” . Then open the workbook again and, if necessary, refresh it by clicking on the “$XWRPDWLF�XSGDWH�DQG�SDXVH,” in order to display the price planning data in the analysis table. 'R�QRW�H[HFXWH the IXQFWLRQ again.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-68

1-1-9 Your aim now is to execute the functions for both revenue calculation and contribution margin accounting using a shared button. To do this, assign the planning function 0��B3)B�� to the existing “)XQFWLRQ��UHYHQXH��DOO�FRPSDQ\�FRGHV��HUURU�PHVVDJH” . The two functions are to be executed directly after each other in the correct business order (determining revenues before contribution margins) at the press of a button.� How should you proceed in the Statistic Parameters area? Explain this by entering the relevant tax information into the following table:


PLANNING_FUNCTION_NAME 0 M##_PF_03


DATA_PROVIDER_FILTER 1 DATA_PROVIDER_1

PLANNING_FUNCTION_NAME 1 M##_PF_04


Transfer these settings to your EXWWRQ. Then change the EXWWRQ�WH[W for this button as follows: “)XQFWLRQ��UHYHQXH�DQG�GDWDEDVHV” . 6DYH your workbook and execute it for ��. You should receive the following results (here is an excerpt):

6DYH the SODQ�GDWD. Then exit the BEx Analyzer and return to the SODQQLQJ�PRGHOHU.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-69

1-2 In the following, you should distribute the sales quantities, revenues and contribution margins planned at the product group granularity to the customer group granularity. This is the granularity of the Key Account Managers. The distribution will take place in a C version.

1-2-1 First, go to the SODQQLQJ�PRGHOHU�for aggregation level 0��B$/B��of InfoProvider 7%:��0��. Here, create a FRS\�IXQFWLRQ�that copies the data from version %�to version &, but only for the NH\�ILJXUHV�VDOHV�TXDQWLW\��UHYHQXH�DQG�FRQWULEXWLRQ�PDUJLQ. Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B&23<�� Place the “9HUVLRQ” field in the ILHOGV�WR�EH�FKDQJHG. Then, to ensure that the function will be executed for the data from InfoProvider 7%:��6�� only, include the “ ,QIR3URYLGHU” field in the FRQGLWLRQV. Configure the function using the above information and then VDYH it. Then exit the planning modeler�and return to the %([�$QDO\]HU and, from there, into your *URXS��B7%:��B%(;B0XOWL3URY workbook.

1-2-2 After you have created the copy function in task 1-2-1, you want to make the data for both the B and C versions visible in the analysis table. To do this, include the Design Item 1DYLJDWLRQ�DUHD in cell $��, referring to the '$7$B3529,'(5B�. If you look at the 'LPHQVLRQV tab page in the Design Item, the 9HUVLRQ dimension is not present because it is in the Query Designer and is only assigned a single value here (version B) in the “ Characteristic Restrictions” area. This means that it is not possible to navigate. For this reason, leave the dimensions area empty in this Design Item. First, VDYH the ZRUNERRN and close it. Now, navigate in the 4XHU\�'HVLJQHU to your plan query with the technical name 0��B$/B��B3ODQTXHU\B��B0XOWL3 and limit the version to %�DQG & in the FKDUDFWHULVWLF�UHVWULFWLRQV area. 6DYH the plan query and exit the Query Designer. Navigate back to the BEx Analyzer and open your *URXS��B7%:��B%(;B0XOWL3URY workbook.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-70

Open the 1DYLJDWLRQ�DUHD Design Item again. Then select $XWR)LW. For the “$UHD” , write: �$��&�� Select “0DWHULDO�JURXS” , “9HUVLRQ” , “)LVFDO�\HDU” and “.H\�ILJXUHV” in the “6HOHFWHG�'LPHQVLRQV” area. All the other settings remain unchanged. 6DYH the workbook and execute it for the fiscal year ��. Set only the ILOWHU in the navigation to version &. You should receive the following display (here is an excerpt):

1-2-3 Now implement the copy function. To do this, create the EXWWRQ Design Item again for cell $�� and enhance it as follows: Area: �$��&�� Button text: )XQFWLRQ��FRS\�YHUVLRQ�%�!& Select: $GMXVW�DUHD�WR�LWHP�VL]H. In the Static Parameters area, select:



I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-71

Then VDYH the workbook and execute it for the fiscal year ��. Version & should be set in the navigation block’s filter. Now H[HFXWH the FRS\�IXQFWLRQ. You should receive the following display (here is an excerpt):

Then VDYH the SODQ�GDWD and set the filter in the navigation block back to version %, so that the planner can later always view the data in the material group granularity. Then VDYH the ZRUNERRN.

1-2-4 Now you want to distribute the data from version C from the material group granularity to the customer group. You only want to distribute the key figures sales figures, revenue and contribution margin. The aim is to GLVWULEXWH�E\�UHIHUHQFH�GDWD, where the actual data at the customer group granularity that is contained in another InfoProvider and is present in version D is used as a reference. In general, you want to distribute the sales quantity in the plan in the same proportion as the sales quantity in the actual data. The same is true for the revenue in the plan and the actual revenue and the contribution margin in the plan and the actual contribution margin. The aim of distribution is not to distribute the sales quantity, the revenue and the contribution margin in the plan in proportion to the actual sales quantity. This has to be taken into account when modeling the planning function. The actual data used as reference data is contained in a query in InfoProvider 7B%:��B�, which all exercise groups should read-access in parallel. This query has the following descriptions: Technical name: ,B5()(5(1&(48(5<B&867*5283�Description: 7%:��B,B54B&867*5283�� The query should appear as follows:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-72

Include this query as an DQDO\VLV�WDEOH in your *URXS��B7%:��B%(;B0XOWL3URY workbook. Place this DQDO\VLV�WDEOH in cell $�� and, in the analysis table’s $UHD field, write “ �$��/��” . This area size ensures that the reference data from both years can be displayed. Place the cursor in cell $�� and enter the following text in font size ��, the color UHG and EROG: “5HIHUHQFH�GDWD�LQ�FXVWRPHU�JURXS�JUDQXODULW\�IRU��SODQ�\HDUV” . 6DYH your workbook and execute it for the fiscal year ��. Then exit the BEx Analyzer.

1-2-5 Now you need to model the distribution function by reference data in the planning modeler. The distribution has to be modeled for the MultiProvider because the reference data is in another InfoProvider than the distribution data. As a result, InfoProvider T_BW370_4, which contains the reference data, was already included in MultiProvider 7%:��0�� for you. Open a second a mode and create a second aggregation level for your InfoProvider 7%:��0��. To do this, copy aggregation level 0��B$/B��, in which the distribution is modeled. Technical name: 0��B$/B�� Description: 7%:��B0��B$/��. Add the characteristic FXVWRPHU�JURXS to the aggregation level and activate this.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-73

Now create a planning function of the type “'LVWULEXWLRQ�E\�UHIHUHQFH�GDWD” for this aggregation level. Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B',675,%B5()�� Which field do you have to include in the fields to be changed if you want to distribute from the material group to the customer group? Customer group Include the characteristic ,QIR3URYLGHU in the fields for FRQGLWLRQV, so that you can later execute the planning function in the MultiProvider for the data from InfoProvider 7%:��6�� only. This means that you have implemented a safety check as described in the training materials. Only include the key figures VDOHV�TXDQWLW\, UHYHQXH and FRQWULEXWLRQ�PDUJLQ in the distribution. Leave the field “ Reference key figure (optional)” free to prevent all three key figures being distributed by one key figure (namely the key figure selected here). In the “5HIHUHQFH�YDOXHV�RQ�DQ\�EORFN�FKDUDFWHULVWLFV” , include the attribute ' for the version and include the attribute 7B%:��B� for the InfoProvider field. Then select “&UHDWH�HQWULHV�PDQXDOO\” and click on the “&UHDWH�/LQH” button. In the “&KDQJH�)URP” field, select “ �” and include “ ��” in the “&KDQJH�7R” field. On the 6HOHFWHG�&RQGLWLRQ tab page, select InfoProvider 7%:��6��. 6DYH the function and exit the planning modeler.

1-2-6 In addition to the planning function, you also require a SODQ�TXHU\ in which you can later view the results of the distribution in version C. The planning function will refer to this plan query's selections. Create this query for your 0��B$/B�� aggregation level E\�FRS\LQJ it. After copying the plan query, you have to adjust the InfoProviders in the copied query. The query should appear as follows (here is an excerpt):

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-74

Note that the actual columns are not ready for input and the plan columns can only be filled by the planning function. Open a second session and navigate via %XVLQHVV�([SORUHU��!�4XHU\��!�&RS\ to the “&RS\LQJ�TXHULHV�IRU�,QIR3URYLGHUV” screen. Enter the following information in the input screen: Source InfoProvider: 0��B$/B��(aggregation level) Target InfoProvider: 0��B$/B��(aggregation level) The next screen displays the queries for the source InfoProvider. Select the query with the following descriptions: Description: 7%:��B0��B$/��B',675,%B5() Technical name: 0��B$/B��B'LVWULEB5().

When you copy, the system assigns a technical name, which results from the template query's technical description, and adds a number to it. Make a note of the new technical name for your plan query: ___________________________________________________________ Now, navigate to the 4XHU\�'HVLJQHU and call your new query. On the “2SHQ�TXHU\��VHOHFW�TXHU\” screen, you should now set up the WHFKQLFDO�GHVFULSWLRQV (system icon at top right: “'LVSOD\�REMHFW�QDPHV�DV«” and then search for the query you noted down before. Next, call this query and change its GHVFULSWLRQ as described in the following. On the right-hand edge of the screen, you can see the “3URSHUWLHV” area. Here, select the top field in the query, then select the “*HQHUDO” tab page and enter the following new QDPH for the query in the “'HVFULSWLRQ” field:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-75

“7%:��0��B$/��B34B',675,%B5()” �� 6DYH the query. Then, in the “&KDUDFWHULVWLF�UHVWULFWLRQV” area, replace 7%:��6�� (the selection included in the query) with 7%:��6�� for the characteristic: ,QIR3URYLGHU. Selection T_BW370_4 also remains. Then navigate to the “&ROXPQV” area and replace the InfoProvider included in the columns “3ODQ�VDOHV�TXDQWLW\” , “3ODQ�UHYHQXH” and “3ODQ�FRQWULEXWLRQ�PDUJLQ” with your InfoProvider, 7%:��6�� 6DYH the query and execute it for the fiscal year ��. Actual data should be displayed for all the customer groups and plan data for the # customer group. Then exit the Query Designer.

1-2-7� Now, you should include the query that you created by copying in your *URXS��B7%:��B%(;B0XOWL3URY workbook. To do this, place the cursor in cell $�� and create another “$QDO\VLV�WDEOH” Design Item. Then select the query you created by copying, 7%:��0��B$/��B34B',675,%B5(). This query is known internally as DATA_PROVIDER_2. In Design Item “$QDO\VLV�WDEOH” , select “$XWR)LW” . Place the cursor in cell $�� and write the following: “$FWXDO�DQG�SODQ�GDWD�FRPSDUHG�WR�EHIRUH�DQG�DIWHU�GLVWULEXWLRQ�E\�FXVWRPHU�JURXS” . Select a UHG coloring, EROG and font size ��. 6DYH your workbook and execute it for ��.

1-2-8 Now, you should include the distribution function with the technical name 0��B3)B�� into your workbook. To do this, place the cursor in cell $�� and create Design Item “%XWWRQ” for the cell. Make the following configuration: Area: �$��&�� Button text: )XQFWLRQ��GLVWULEXWLRQ�E\�UHIHUHQFH�GDWD Select: $GMXVW�DUHD�WR�LWHP�VL]H.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-76

In the Static Parameters area, select:

1DPH� ,QGH[� 9DOXH�DATA_PROVIDER_FILTER 0 '$7$B3529,'(5B��PLANNING_FUNCTION_NAME 0 0��B3)B��PDQXDO�HQWU\�LQ�XSSHU�FDVH� CMD 0 EXECUTE_PLANNING_FUNCTION

6DYH the workbook and execute it for the fiscal year ��. You should receive the following display before distribution (here is an excerpt):

Then H[HFXWH the GLVWULEXWLRQ�IXQFWLRQ. You should receive the following display after distribution (here is an excerpt):

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-77

6DYH your SODQ�GDWD.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-78

1-3 The Key Account Managers want to also carry out JUDSKLF�UHSRUWV in the BEx Analyzer. The aim of this is that the user selects a customer group and the plan data for the customer group is then provided in a graphic.

1-3-1 To do this, first navigate to the 4XHU\�'HVLJQHU and save your 7%:��0��B$/��B34B',675,%B5() query there with the descriptions: Description: 7%:��B0��B$/��B''%B&867*53 7HFKQLFDO�QDPH�� 0��B$/B��B'''B&867553�� 6DYH the query that you created by copying. In the copied query, remove the characteristic FXVWRPHU�JURXS from the drilldown and make sure that this characteristic is contained in the characteristic restrictions with the attribute ��. Then drag the customer group into the “'HIDXOW�YDOXHV” area. It would also be possible to include the customer group in the free characteristics or the drilldown, so that you could then later select the customer group as a dimension in the dropdown box. Including the characteristic alone in the characteristic restrictions is not enough to be able to use the dropdown box. You could also have created a master data query for the customer group and then you could use this query as the basis for the dropdown box. We did not use this option. Then VDYH the query again and exit the Query Designer.

1-3-2 Return to your *URXS��B7%:��B%(;B0XOWL3URY workbook and navigate to the VHFRQG�ZRUNVKHHW named “6KHHW��” . The additional reporting is to take place here. Place the cursor in cell $�� and create another analysis table. Include the query with the technical name 0��B$/��B3ODQTXHU\B''%B&867*53 in this analysis table. Then select $XWR)LW again. This query is executed internally as DATA_PROVIDER_4. Now place the cursor in cell $� and create the Design Item GURSGRZQ�ER[ so that you can select a customer group for which the analysis table then displays the data and which is reported graphically. On the *HQHUDO tab page,�VHOHFW '$7$B3529,'(5B�, “'LVSOD\�/DEHO” . 'HVHOHFW�WKH�³$GMXVW�DUHD�WR�LWHP�VL]H´ field. On the 'LPHQVLRQV tab page, select the characteristic &XVWRPHU�JURXS as the dimension and select read mode 3RVWHG�YDOXHV, as well as .H\�DQG�WH[W.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-79

On the 7DUJHW'DWD3URYLGHU tab page, select '$7$B3529,'(5B�. Create a 6DYH�EXWWRQ in cell $� and a 5HIUHVK�EXWWRQ in cell &��. 6DYH your workbook and execute it for the fiscal year ��. You should see the following display:

Change the customer group selection in the dropdown box and click on the “5HIUHVK” button. The data in the associated analysis table should be displayed according to the customer group selected. Place the cursor in cell $� and write “$GGLWLRQDO�UHSRUWV” in font size ��, EROG and UHG. Rename the worksheet with the description 6KHHW�� as “$GGLWLRQDO�UHSRUWV�DQG�JUDSKLFV” .

1-3-3 6DYH the workbook again and remain on the second worksheet in execution mode. +LGH the VXEWRWDOV�IRU�WKH�FROXPQV�³)LVFDO�\HDU´�WR�³0DWHULDO�JURXS´ for the graphic that is structured subsequently in the analysis table that you already built and executed. To do this, place the cursor on the title header for each of these columns, right-clicking and selecting “3URSHUWLHV«” . On the next screen, select “$OZD\V” in the “6XSSUHVV�UHVXOWV�URZV” field. This procedure ensures that only the relevant data is linked into the graphic that is created next. 6DYH your workbook.

1-3-4 Now you want to link in an Excel graphic that displays the SODQ�YDOXHV for the selected customer group. In the workbook's execution mode, place the cursor in cell $�� and open the “&KDUW�ZL]DUG” . Select &ROXPQ as the “&KDUW�7\SH” and then select &OXVWHUHG�&ROXPQ�ZLWK�D��'�YLVXDO�HIIHFW. On the next screen and here on the 'DWD�5DQJH tab page, select &ROXPQV for the “6HULHV�LQ” field and select the data columns “3ODQ�VDOHV�TXDQWLW\” , “3ODQ�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-80

UHYHQXH” and “3ODQ�FRQWULEXWLRQ�PDUJLQ” as the 'DWD�5DQJH. On the 6HULHV tab page, first remove all the series in the “6HULHV” area. Then go to the “$GG” button and enter “3ODQ�VDOHV�TXDQWLW\” in the “1DPH” field. Then place the cursor in the “9DOXHV” field and select the entire data area for the analysis table that refers to the “3ODQ�VDOHV�TXDQWLW\” . Next, click on “$GG” to create a new series. In the “1DPH” field, enter the description “3ODQ�UHYHQXH” and in the “9DOXH” field, select the data area again under the “3ODQ�UHYHQXH” column in the analysis table. Proceed in the same way with the “3ODQ�FRQWULEXWLRQ�PDUJLQ” . On the next screen and here on the 7LWOHV tab page, write “3ODQ�GDWD�IRU�VHOHFW�FXVWRPHU�JURXS” for the “&KDUW�7LWOH" and leave all the other fields empty. On the $[LV tab page, deselect “&DWHJRU\��;��D[LV” and “9DOXH�=�D[LV” . On the *ULGOLQHV tab page, deselect all the fields. On the /HJHQG tab page, select “6KRZ�/HJHQG” and “%RWWRP” . On the 'DWD /DEHOV tab page, select “9DOXH” . On the 'DWD�7DEOH tab page, deselect all the fields. On the last of the wizard's screens, “&KDUW�:L]DUG�±�6WHS��±�&KDUW�/RFDWLRQ” , select “$V�REMHFW�LQ” and then select the worksheet with the description “$GGLWLRQDO�UHSRUWV�DQG�JUDSKLFV” . You should now have run through the entire wizard and the graphic should appear. 0RYH the graphic that is now being built into cell $�� and drag the graphic to fit the entire column width in the analysis table. Color the “3ODQ�UHYHQXH” UHG, the “3ODQ�FRQWULEXWLRQ�PDUJLQ” JUHHQ and leave the color of the “3ODQ�VDOHV�TXDQWLW\” EOXH. 'UDJ the QXPHULFDO�YDOXHV from the three columns XSZDUGV to give you a better overview. 6DYH the workbook.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-81

1-3-5 Now use the dropdown box to select a FXVWRPHU�JURXS�RI�\RXU�FKRRVLQJ, then click on the UHIUHVK�EXWWRQ and take a look at the data and the graphic which appear. Change the selection in the dropdown box again and take another look at the adjusted data in the analysis table and the graphic. You might, for example, receive the following display if you select customer group 02:

1-3-6 Now remove the gridlines from the second worksheet.

To do this, navigate along 7RROV��!�2SWLRQV on the subsequent screen to the 9LHZ tab page and deselect *ULGOLQHV. 6DYH the workbook.

1-4 Now return to the “6KHHW��” worksheet and rename it “0XOWL3URYLGHU�VFHQDULR” . To finish off, you want to model a currency conversion for the plan revenues and plan contribution margins from USD to EUR for the data in plan version C. You also want to ensure that, even if this planning function is triggered more than once, the currency is only converted once. To do this, you have to carry out various operations: 1. You have to copy the query for cell A112 and restructure it for a currency comparison of the plan data. 2. Then, you have to include the query in the BEx Analyzer. 3. You have to build a currency conversion function in the planning modeler, as well as a delete function that can undo the currency conversion. Both of these function are structured via the MultiProvider (it would also be possible to build them on InfoProvider TBW370S## ). As a result, you have to ensure that they are only executed for the InfoProvider.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-82

You achieve this by including the characteristic InfoProvider with the attribute TBW370S## in the conditions area for these functions. 4. You have to merge the two functions in the planning modeler, which means that you have to build a filter in the planning modeler. 5. You have to include the sequence in the BEx Analyzer and make a reference to the DATA_PROVIDER from step 2.

1-4-1 Navigate to the Query Designer and save your query with the description “7%:��B0��B$/��B34B',675,%B5()” under� the following descriptions� 'HVFULSWLRQ��7%:��B0��B$/��B34B&XUUHQF\B7 Technical name: 0��B$/B��B3ODQTXHU\B&XUUHQF\B7 . Make the following changes in the copied query: In the FKDUDFWHULVWLF�UHVWULFWLRQV area, add (85 to the characteristic &XUUHQF\, which already includes USD. 5HPRYH the “XQLW�RI�PHDVXUH” with “67” . 5HPRYH the ,QIR3URYLGHU “7B%:��B�” . 5HPRYH “9HUVLRQ�'” . In the &ROXPQV area, remove the WKUHH�DFWXDO�FROXPQV and the “3ODQ�VDOHV�TXDQWLW\” �SODQ�FROXPQ. In the two remaining plans, include the characteristic &XUUHQF\ and set 86'. Make a note in the KHDGLQJ for these columns that the amounts are displayed in GROODUV. 5HPRYH the characteristics “9HUVLRQ” and “ ,QIR3URYLGHU” from the two remaining columns. Now FRS\ both the UHYHQXH�FROXPQ and the FRQWULEXWLRQ�PDUJLQ�FROXPQ and FKDQJH the KHDGHU�WH[W in the copied columns to include (85. Then include the characteristic FXUUHQF\ with the attribute (85 in each of the copied columns. For the two data columns in “86'” , select “'DWD�FDQQRW�EH�FKDQJHG” and select “'DWD�FDQ�EH�FKDQJHG�E\�SODQQLQJ�IXQFWLRQV" for the two “(85” columns. Note that the query is based on a MultiProvider, as are the subsequent work steps. From a performance point of view, it would be better to create the query directly at an aggregation level of InfoProvider TBW370S## and to create the query on this. However, that option would be more complex and we therefore chose the method explained above. Next, VDYH the plan query and execute it for the fiscal year ��. Here is an excerpt of what you should see:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-83

Now exit the Query Designer.

1-4-2 You should include this query in your workbook on the ILUVW�ZRUNVKHHW for cell $�� as an DQDO\VLV�WDEOH. Internally, this query corresponds to DATA_PROVIDER_5. Select “$XWR)LW” again. 6DYH your workbook and execute it for ��. Do not close the workbook.

1-4-3 Now, navigate to the SODQQLQJ�PRGHOHU and select your InfoProvider 7%:��0��. Then select the aggregation level with the technical name 0��B$/B��. Copy the aggregation level as follows: Technical name: 0��B$/B�� Description: 7%:��B0��B$/�� . Remove the key figures VDOHV�TXDQWLW\, SULFH, the PDQXIDFWXULQJ�FRVWV and the XQLW�RI�PHDVXUH from this level. $FWLYDWH the aggregation level. You need to create a ILOWHU for this aggregation level. The filter is to be used for converting the currency in the revenue and contribution margin plan data: Technical name: 0��B)B�� Description: 7%:��B0��B$/��B)�� Include DOO�WKH�FKDUDFWHULVWLFV in the filter and include the following selections: Customer group: ��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-84

Fiscal year variant: .� InfoProvider: 7%:��6�� Version: & Controlling area: �� Company code: �� Currency: 86'��(85 Material group: 7:$7��-8& Fiscal year: 9DULDEOH�*URXS��B9$5B)<B��B30 6DYH the filter.

1-4-4 Now create the FXUUHQF\�FRQYHUVLRQ�IXQFWLRQ for aggregation level 0��B$/B��. Technical name: 0��B3)B�� Description: 7%:��B0��B$/��B3)��B&855B7 The currency field is automatically present in the “ ,V�FKDQJHG” area. Select “ ,QIR3URYLGHU” and “9HUVLRQ” in the “ ,V�XVHG�LQ�FRQGLWLRQ” area and select “7%:��6��” �DQG�“&” � Configure the concrete processing rule as follows:

7DUJHW�.H\�)LJXUH� 6RXUFH�.H\�)LJXUH� &XUUHQF\�7UDQVODWLRQ�7\SH�Revenue Revenue BPS (data record CUR to EUR)

Contribution Margin 1 Contribution Margin 1 BPS (data record CUR to EUR)

1-4-5 In the same aggregation level, create a GHOHWH�IXQFWLRQ that deletes the data records in Euro. Technical name:��0��B3)B�� Description: 7%:��B0��B$/��B3)��B'(/B&855

Include the fields “ ,QIR3URYLGHU” , “9HUVLRQ” and “&XUUHQF\�.H\” in the FRQGLWLRQ�ILHOGV and select InfoProvider 7%:��6��, version & and the currency key (85. Select DOO�NH\�ILJXUHV and VDYH the planning function.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-85

1-4-6 Then create a SODQQLQJ�VHTXHQFH, in which the delete function is positioned EHIRUH the currency conversion function. Both refer to the same filter, 0��B)B��, at aggregation level 0��B$/B�� . Technical name: 0��B6B�� Description: 7%:��B0��B$/��B6��

6DYH the planning sequence. Then exit the planning modeler.

1-4-7 Navigate to the %([�$QDO\]HU and open the ILUVW�ZRUNVKHHW in your workbook *URXS�B7%:��B%(;B0XOWL3URY. Now link the sequence of Design Item “%XWWRQ” into the workbook. Place the cursor in cell $�� and define the button as follows: Area: �$��&�� Button text: )XQFWLRQ��FXUUHQF\�FRQYHUVLRQ�86'�!(85 Deselect “$GMXVW�DUHD�WR�LWHP�VL]H”

1DPH� ,QGH[� 9DOXH�PLANNING_SEQUENCE_NAME 0 0��B6B�� (manual entry)

DATA_PROVIDER 0 '$7$B3529,'(5B��CMD 0 EXECUTE_PLANNING_SE

QUENCE

6DYH your workbook and execute it for the fiscal year ��. Then execute the FXUUHQF\�FRQYHUVLRQ. You should receive the following display (here is an excerpt):

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-86

6DYH your plan data. Then H[HFXWH the FXUUHQF\�FRQYHUVLRQ DJDLQ. This should result in the same data as the first time you executed the function: there should be no “ double” calculations.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-87

1-5 To finish, you want to remove the gridlines from the first worksheet in your workbook. To do this, navigate along 7RROV��!�2SWLRQV on the subsequent screen to the 9LHZ tab page and deselect *ULGOLQHV. Select the file: 3LFWXUH�B7%:��SQJ as the EDFNJURXQG�FRORU for the ILUVW�ZRUNVKHHW and 3LFWXUH�B7%:��SQJ as the background color for the VHFRQG�ZRUNVKHHW. The files are in your system’s Business Workplace. To find these files, open a new session, then navigate via 0HQX��!�%XVLQHVV�:RUNSODFH to the “6KDUHG�)ROGHUV” and select “7UDLQLQJ��%:�0DWHULDO�IRU�%:�7UDLQLQJ” and then “%:��%:��0DWHULDO” . Export both of the files mentioned above to your computer's GHVNWRS. Assign them the following descriptions: 3LFWXUH�B7%:��B*URXS�� and 3LFWXUH�B7%:��B*URXS�� . Then return to your workbook and add the two background colors as described above. Then VDYH your workbook again and exit the BEx Analyzer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 9-88

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-1

SAP AG 2006

&RQWHQW�� 8VH�RI�SODQQLQJ�VHTXHQFHV

3ODQQLQJ 6HTXHQFHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-2

SAP AG 2006

3ODQQLQJ 6HTXHQFHV��7RSLF�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG KRZ�SODQQLQJ�VHTXHQFHV�DUH�PRGHOHG� 8QGHUVWDQG WKH�GLIIHUHQW�SUDFWLFDO�DSSOLFDWLRQV�RI�

VHTXHQFHV� 5HFRJQL]H KRZ�SODQQLQJ�VHTXHQFHV�DUH�H[HFXWHG� .QRZ ZKDW�WKH�WUDFH�PRGH�PHDQV� 8QGHUVWDQG KRZ�D�SODQQLQJ�VHTXHQFH�LV�LQWHJUDWHG�

LQWR�D�SURFHVV�FKDLQ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-3

SAP AG 2006

3ODQQLQJ 6HTXHQFHV��2YHUYLHZ 'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-4

SAP AG 2006

3ODQQLQJ 6HTXHQFHV��%XVLQHVV�([DPSOH

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�SODQQLQJ�VHTXHQFH�DV�DQ�LPSRUWDQW�WRRO�IRU�WHVWLQJ�SODQQLQJ�IXQFWLRQV�

� <RX�DUH�DOVR�LQWHUHVWHG�LQ�LQFOXGLQJ�WKH�SODQQLQJ�VHTXHQFH�LQ�D�SURFHVV�FKDLQ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-5

SAP AG 2006

3ODQQLQJ�6HTXHQFHV��8QLW�2YHUYLHZ�'LDJUDP

8QLW�2YHUYLHZ� /HVVRQ��8VH�RI�3ODQQLQJ�6HTXHQFHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-6

SAP AG 2006

8VH�RI�3ODQQLQJ�6HTXHQFHV��7RSLF�2EMHFWLYHV

� 8QGHUVWDQG KRZ�SODQQLQJ�VHTXHQFHV�DUH�PRGHOHG� 8QGHUVWDQG WKH�GLIIHUHQW�SUDFWLFDO�DSSOLFDWLRQV�RI�



%\�WKH�FRQFOXVLRQ�RI�WKLV�8QLW��\RX�ZLOO�EH�DEOH�WR�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-7

SAP AG 2006

8VH�RI�3ODQQLQJ�6HTXHQFHV��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�SODQQLQJ�VHTXHQFH�DV�DQ�LPSRUWDQW�WRRO�IRU�WHVWLQJ�SODQQLQJ�IXQFWLRQV�

� <RX�DUH�DOVR�LQWHUHVWHG�LQ�LQFOXGLQJ�WKH�SODQQLQJ�VHTXHQFH�LQ�D�SURFHVV�FKDLQ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-8

SAP AG 2006

3ODQQLQJ�6HTXHQFHV

�

� Planning sequences combine planning functions and filters, whereby a sequence can comprise one or

more combinations of planning function and filter. �

A planning sequence is mainly defined for three reasons:

• To bundle multiple planning functions into one komplex function and automatically execute them in one step

• To test one or more planning functions at runtime

• To execute a planning function or a sequence as a batch process within a process chain �

Within a sequence, a combination of planning function/sequence is known as a “step”. �

For each step, you always have to enter the underlying aggregation level, the filter, and the planning function.

� You can use a planning sequence to bundle planning functions from different aggregation levels.

� It is not possible to include one planning sequence in another.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-9

SAP AG 2006

([HFXWLQJ�D�3ODQQLQJ�6HTXHQFH�DW�5XQWLPH

([HFXWLQJ�D�VWHS�RI�WKH�VHTXHQFH

([HFXWLQJ�WKH�HQWLUH�VHTXHQFH

9DULDEOH�UHTXHVW�

�

� A planning sequence can be executed in different ways.

� If you want to execute the entire sequence, you press the “Execute” button at the top of the screen. Then

the steps contained in the sequence are executed one after the other. �

On the other hand, if you only want to test a single step, you select this step, then press the “Execute” button in the middle of the screen.

� If the planning functions contain input-ready variables, you can set them manually before executing the

steps and store the value combinations of the variables as variants. Variables can also be personalized. �

The above illustration shows a variable for the revaluation factor within the revaluation function. �

If the sequence is executed, the data is changed and the result is written to the plan buffer. When you press the “Save” button, the changed transaction data is written from the buffer to the database.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-10

SAP AG 2006

6DYLQJ�3ODQQLQJ�6HTXHQFHV�DQG�6DYLQJ�3ODQ�'DWD�

6DYH�WKH�GHILQLWLRQ�RI�WKH�SODQQLQJ�VHTXHQFH

6DYH�WKH�GDWD�JHQHUDWHG�E\�WKH�VHTXHQFH�

�

� The saving of the sequence definition and the saving of the data in the provider are to be viewed

completely independently of one another. Saving the data does not save the sequence definition, and vice versa.

� When you leave the “ Planning Sequences” tab page, you have to save the definition or the changes to

the definition of the planning sequence, otherwise they will be lost. �

In accordance with the approach of the plan data buffer, on the other hand, when you leave the “ Planning Sequences” tab page, you do not have to save the plan data. Data is kept in the buffer as long as the planning modeler is open. If you close the Planning Modeler without pressing the “ Save Plan Data” button, you lose the plan data changed by the sequence.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-11

SAP AG 2006

7UDFH�0RGH�IRU�3ODQQLQJ�)XQFWLRQV

�

� The trace mode enables you to get detailed information on which data objects were changed, and in

which way, when a planning function was executed. You thus analyze the behavior of the planning function.

� This function is particularly helpful when you are setting up new planning fucntions and parameter

groups and want to check whether the function has the desired effects on the dataset. �

Planning functions are usually called up and executed in blocks. In trace mode, you can see the blocks and the selection criteria for the blocks.

� For each block selected, you can use the four tab pages to display the different views for the plan data.

You can thus analyze the following:

• Data before the changes made by the planning function

• Data after the changes made by the planning function

• Reference data that was read in by the planning function

• A view that compares the data records before and after the execution on a screen �

After the tracing, you can save the traced data. �

You can only start the tracing of the planning functions in the Planning Modeler.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-12

SAP AG 2006

3ODQQLQJ�6HTXHQFH�IRU�7HVW�3XUSRVHV�XVLQJ�WKH�,QSXW�7HPSODWH

�

�

�

�

Add a step for the input templateSelect the aggregation levelSelect your filterSave your selectionExecute

�

�

�

�

�

�

�

� A planning sequence can also be used to represent in a table all the data records selected in a filter. The

data can be changed manually in the table, and new data records can also be created. �

It is completely sufficient if you add a single input template for each sequence and aggregation level, because as soon as it has been executed once, it remains open and shows all the changes that result from executing any planning function in the sequence.

� Within a sequence, the input template can be positioned before or after planning functions.

� Please note that the input template is ignored if the entire seqence is executed at runtime or in a batch.

� The use of the planning sequence described on this slide was already represented in unit 2.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-13

SAP AG 2006

%DWFK�([HFXWLRQ�RI�D�3ODQQLQJ�)XQFWLRQ�:LWKLQ�D�3URFHVV�&KDLQ

3URFHVV W\SH

3URFHVV YDULDQW

�

� The batch processing of a planning sequence can be set up by means of a process chain, and here by

means of the process type “ planning sequence” . Within the process maintenance, you must maintain the name and description of the process, as well as select a variant and the desired planning sequence.

� The variant was created for the planning sequence in the Planning Modeler, and it is user-dependent and

contains all variables that are to be used for the planning sequence. �

The process chain can start immediately, be run at regular intervals, or be modeled as event-controlled. �

If you want to execute different sequences in a process chain, you must create a step for each planning sequence, and the steps are then combined. Every step has its own data buffer, and at the end of each step the data is automatically saved, after which the plan buffer is released and the data is unlocked.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-14

SAP AG 2006

2SWLPL]DWLRQ�RI�WKH�0HPRU\�5HTXLUHPHQW�3URFHVV VWDUW

3URFHVV VWHS6HTXHQFH

�� "!"!#! ��$

% !"&��&�' ��()&*��+ "&�, , �

% �- ��.��, �"&�!"��(�� (/�0�1�

/RQJ�WHUP PHPRU\ SUREOHPV

3URFHVV VWDUW

3URFHVV VWHS6HTXHQFH �

3URFHVV VWHS6HTXHQFH �

�3URFHVV VWHS6HTXHQFH Q

�2'*�.��()&*��+ �$3 &��"�*4�56��, ��&"! �

�2'*�.��()&*��+ �$3 &��"�*4�56��, ��&"! �

�2'*�.��()&*��+ �$3 &��"�*4�56��, ��&"! �

7 8:9�;<8>=@?�A

7 8:9�;<8>=@?�A

7 8:9�;<8>=@?�B

7 8:9�;<8>=@?�=

;

1R�ORQJ�WHUP PHPRU\ SUREOHPV

�

� The PHPRU\�UHTXLUHPHQW and the execution time expended by the planning function can be defined by

you in the design of the process chain, whereby a planning sequence with a very large memory requirement is split into two sequences. The two of them can then be executed one after the other in the process chain. The buffer is thus released again after the respective steps, and the total memory requirement is reduced.

� The above illustration shows the two modeling options. The left variant would eventually cause the

memory to fill up. �

In the right variant, the data quantity you select for each process step sequence should not be too small, so that you do not have to define too many sequences. The same data quantity should be selected as the basis for each sequence. Two sequences should not refer to the same data quantity. This is shown in the above illustration.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-15

SAP AG 2006

2SWLPL]LQJ WKH 5XQWLPH

C6�.�� D��!�!�!*�.��EF&��G+ &��"�IH

3 � J' �� )K

C6�.�� D��!�!�!*�.��3 � J' �� LH

CM�-�� ! !#!"�.��EN&��+ &��0O

3 � JI'�� *�)K

�

CP�-�� !"!�!"�.��E6&��+ &��6K

3 �"JI'"�� *�)K

QR�"��"��*�I��&��&��" "�I�-��!S�.�I�0�"&" ��&��G+ &��"�I� �I&S!�� JI'�� "�

T6�U, � �V*+R��W��"&� ��

3URFHVV��ZDLWVXQWLO�SURFHVVHV��WR��DUH�ILQLVKHG

3URFHVV VWDUW

3URFHVV VWHS6HTXHQFH

�� "!"!#! ��$

% !"&��&�' ��()&*��+ "&�, , �

% �- ��.��, �"&�!"��(�� (/�0�1�

/RQJ�WHUP PHPRU\ SUREOHPV

3URFHVV VWDUW

1R�ORQJ�WHUP PHPRU\ SUREOHPV

�

� The memory requirement and the H[HFXWLRQ�WLPH required by the planning function can be defined

when designing the process chain by splitting the data selection required in the planning sequence into multiple interval selections by means of the filter; variants of a sequence are created for these interval selections. The variants of the sequence are executed in parallel in the process chain, thus reducing the overall execution time.

� The right variant in the above graphic shows such a SDUDOOHO process modeling, in which subsequent

processes wait until the previous processes are complete. �

For forming variants within a sequence, the following scenario could apply: A sequence is to be executed for twenty cost centers. One variant is created for each cost center, and every variant is assigned a process step.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-16

SAP AG 2006

8VH�RI�3ODQQLQJ�)XQFWLRQV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG KRZ�SODQQLQJ�VHTXHQFHV�DUH�PRGHOHG� 8QGHUVWDQG WKH�GLIIHUHQW�SUDFWLFDO�DSSOLFDWLRQV�RI�



�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-17

SAP AG 2006

3ODQQLQJ 6HTXHQFHV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�8QGHUVWDQG�KRZ�SODQQLQJ�VHTXHQFHV�DUH�PRGHOHG8QGHUVWDQG�WKH�GLIIHUHQW�SUDFWLFDO�DSSOLFDWLRQV�RI�VHTXHQFHV5HFRJQL]H�KRZ�SODQQLQJ�VHTXHQFHV�DUH�H[HFXWHG.QRZ�ZKDW�WKH�WUDFH�PRGH�PHDQV8QGHUVWDQG�KRZ�D�SODQQLQJ�VHTXHQFH�LV�LQWHJUDWHG�LQWR�D�SURFHVV�FKDLQ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 10-18

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-1

SAP AG 2006

&RQWHQW�� &KDUDFWHULVWLF�UHODWLRQVKLSV�DQG�GDWD�VOLFHV

&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-2

SAP AG 2006

&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV��/HDUQLQJ�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�FKDUDFWHULVWLF�UHODWLRQVKLSV�DQG�

GDWD�VOLFHV�DUH�PRGHOHG�LQ�%,�LQWHJUDWHG�SODQQLQJ� &RPSDUH�WKH�XVH�RI�FKDUDFWHULVWLF�UHODWLRQVKLSV�DQG�

WKH�XVH�RI�QDYLJDWLRQ�DWWULEXWHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-3

SAP AG 2006

&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV��&RXUVH�2YHUYLHZ�'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-4

SAP AG 2006

&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV��%XVLQHVV�([DPSOH

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�ILQG�RXW�PRUH�DERXW�WKH�RSWLRQV�IRU�ORFNLQJ�GDWD�DQG�PRGHOLQJ�FKDUDFWHULVWLF�UHODWLRQVKLSV�

� <RX�DUH�DOVR�LQWHUHVWHG�LQ�QDYLJDWLRQ�DWWULEXWHV�DQG�WKHLU�XVH�FRPSDUHG�WR�FKDUDFWHULVWLF�UHODWLRQVKLSV�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-5

SAP AG 2006

&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV��8QLW�2YHUYLHZ�'LDJUDP

8QLW�2YHUYLHZ� /HVVRQ��&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-6

SAP AG 2006

&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV��/HDUQLQJ�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�FKDUDFWHULVWLF�UHODWLRQVKLSV�DQG�



�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-7

SAP AG 2006

&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV��%XVLQHVV�([DPSOH

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�ILQG�RXW�PRUH�DERXW�WKH�RSWLRQV�IRU�ORFNLQJ�GDWD�DQG�PRGHOLQJ�FKDUDFWHULVWLF�UHODWLRQVKLSV�

� <RX�DUH�DOVR�LQWHUHVWHG�LQ�QDYLJDWLRQ�DWWULEXWHV�DQG�WKHLU�XVH�FRPSDUHG�WR�FKDUDFWHULVWLF�UHODWLRQVKLSV�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-8

SAP AG 2006

&KDUDFWHULVWLF�5HODWLRQVKLSV

&KDUDFWHULVWLF�UHODWLRQVKLSV�� $UH�WKH�EDVLV�RI�WKH�GDWD�PRGHO� $SSO\�SHU�UHDO�WLPH�,QIR3URYLGHU DQG�VSHFLI\�UXOHV�EHWZHHQ�

FKDUDFWHULVWLF�DWWULEXWHV� (QVXUH�GDWD�FRQVLVWHQF\�UHJDUGLQJ�FRPELQDWLRQV�RI�FKDUDFWHULVWLFV

,I�\RX�DUH�ZRUNLQJ�ZLWK�0XOWL3URYLGHUV��WKH\�DUH�VXEMHFW�WR�WKH�FKDUDFWHULVWLFV�WKDW�ZHUH�VHW�XS�IRU�WKH�ORZHU�OHYHO�UHDO�WLPH�,QIR3URYLGHUV�

�

� &KDUDFWHULVWLF�UHODWLRQVKLSV relate characteristics with corresponding content to each other.

� You can use characteristic relationships to define rules to check for SHUPLVVLEOH�FRPELQDWLRQV�RI�FKDUDFWHULVWLF�YDOXHV per real-time InfoCube.

� Furthermore, you can define rules that the system can use to GHULYH�YDOXHV�IURP�FKDUDFWHULVWLFV�IRU�RWKHU�FKDUDFWHULVWLFV. This is useful if, for example, you want the derivable characteristics to be available for other evaluations.

� Characteristic relationships have to be created for a real-time InfoCube. They then affect every

InfoProvider that is relevant for planning and that references this InfoCube; they therefore also affect MultiProviders containing this kind of real-time InfoCube, for example.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-9

SAP AG 2006

7\SHV�RI�&KDUDFWHULVWLF�5HODWLRQVKLS��

� � � � � � � � � ��

([LW�

'DWD6WRUH REMHFW� � �� ! � � � � �" � # �� $� ��% � � � &!� ' � ( � ��%� � � � � � � ��

0DVWHU�GDWD�DWWULEXWHV

&KDUDFWHULVWLF�UHODWLRQVKLSV

)+* * , - .0/1* 2354�67, 678 * 20, - 9* - 8:;, <�=;/;8*?>;, <0/?@BA:;, <7=;/78 *C)D�EF)HG?IJ;KMLONQP5:D�EM)HG+RCL+S )QI

+LHUDUFK\

�

� There are four types of characteristic relationship: attributes, hierarchies, DataStore objects and exits.

� $WWULEXWHV�

• For characteristic relationships of the type DWWULEXWH, the target characteristic has to be defined as an attribute of the basic characteristic and must itself be contained in the InfoCube. You can select the attributes of the basic characteristic as a target characteristic (for example, the SURGXFW�JURXS characteristic is an attribute of the SURGXFW characteristic). The existing combinations of characteristic and attribute values are interpreted as valid combinations.

� +LHUDUFK\�

• For characteristic relationships of the type KLHUDUFK\, the target characteristic must be contained in the selected hierarchy and in the InfoCube.�Here, the permissible combinations are specified from the hierarchy. The hierarchy is principally designed for modeling a derivation relationship; for this reason, the hierarchy must not contain any end nodes or inside nodes more than once. Link nodes are not allowed either.

� All the characteristics contained in the hierarchy may be used as source or target characteristics. 7KH�KLHUDUFK\�PXVW�FRQWDLQ�DW�OHDVW�RQH�FKDUDFWHULVWLF�RWKHU�WKDQ�WKH�KLHUDUFK\�EDVLF�FKDUDFWHULVWLF��RWKHUZLVH�\RX�FDQQRW�XVH�WKH�KLHUDUFK\�IRU�FKDUDFWHULVWLF�UHODWLRQVKLSV� You may only use one characteristic each for the source and target characteristics (the higher-level characteristics in compound characteristics are not included in the calculation). You can use the same hierarchy in multiple relations: in a ILUVW�VWHS, you use the hierarchy basic characteristic to derive a characteristic for the next highest level; in a VHFRQG�VWHS you use this characteristic to derive another for the next highest level.

� You can parameterize the hierarchies you use with suitable variables depending on the hierarchy’s

properties.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-10

SAP AG 2006

7\SHV�RI�&KDUDFWHULVWLF�5HODWLRQVKLS��

� � � � � � � � � ��

([LW�

'DWD6WRUH REMHFW� � �� ! � � � � �" � # �� $� ��% � � � &!� ' � ( � ��%� � � � � � � ��

0DVWHU�GDWD�DWWULEXWHV

&KDUDFWHULVWLF�UHODWLRQVKLSV

)+* * , - .0/1* 2354�67, 678 * 20, - 9* - 8:;, <�=;/;8*?>;, <0/?@BA:;, <7=;/78 *C)D�EF)HG?IJ;KMLONQP5:D�EM)HG+RCL+S )QI

+LHUDUFK\

�

� Only VWDQGDUG�'DWD6WRUH�REMHFWV can be used in characteristic relationships, transactional ones are

invalid. This means that you can use all the methods for administering and monitoring the Data Warehousing Workbench.

� The data records contained in the 'DWD6WRUH specify the valid characteristic combinations or are used to

derive characteristics. �

The keys for the DataStore objects can be restricted in any case; the restricted part is then used for the combination check or derivation. The restrictions can be parameterized with variables that must be replaceable without a dialog. We recommend that you use only small DataStore objects (with few characteristics and few records).

� For the H[LW characteristic relationship, the valid characteristic combinations or derivable characteristic

values result from the customer-specific implementation of the specified exit class. The exit class must implement the ’IF_RSPLS_CR_EXIT’ interface; in maintenance, the system only offers you this type of class for processing.

� We recommend that you derive your own class from the example class ‘CL_RSPLS_CR_EXIT_BASE.’

You then only have to implement the methods ‘CHECK,’ ‘DERIVE,’ and, as the case may be, ‘CREATE.’ The class ‘CL_RSPLS_CR_EXIT_BASE’ itself can be used directly, but it does not execute an action.

� Also note the example source text (transaction SE80, SE24) that is commented out in the template class;

an infrastructure for buffering is offered here, for example.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-11

SAP AG 2006

)XQFWLRQDO�&RPSRQHQWV�RI�&KDUDFWHULVWLF�5HODWLRQVKLSV�

&KDUDFWHULVWLF�GHULYDWLRQ�± ILOOLQJ�WKH�PLVVLQJ�FKDUDFWHULVWLF�DWWULEXWH

&RPELQDWLRQ�FKHFN��!�RQ�PDQXDO�HQWU\�LQ�WKH�TXHU\

&RPELQDWLRQ�SURSRVDO��!�DXWRPDWLF�VWUXFWXULQJ�RI�WKH�FRPELQDWLRQV

3URFHVVRU0DWHULDO�*URXS

��07�B��$PRXQW0DWHULDO

3URFHVVRU0DWHULDO�*URXS

��07�B��$PRXQW0DWHULDO 9

0DWHULDO�07�B��07�B��07�B��0DWHULDO*URXS�3URFHVVRU��7HUPLQDO

7HUPLQDO07�B��3URFHVVRU07�B��3URFHVVRU07�B��

7HUPLQDO0DWHULDO�*URXS

��07�B��$PRXQW0DWHULDO

�

� The FKDUDFWHULVWLF�UHODWLRQVKLSV contain three functional components:

• A characteristic attribute for a characteristic is automatically derived from the characteristic attribute of another characteristic.

• If a data record is created containing both characteristics, the system checks if this is allowed for the planning combination.

• The system know which combinations of the corresponding characteristics the user wants and can propose them automatically.

• Each input-ready query and every planning function automatically takes the characteristic relationships into account.

� Cells in an LQSXW�UHDG\�TXHU\ for invalid characteristic combinations are not ready for input and it is

not possible to generate new data records with invalid characteristic combinations. �

3ODQQLQJ�IXQFWLRQV always check if new characteristic combinations are valid in their characteristic relationships. If there are any invalid combinations, the planning function terminates with an error message.

� The possible characteristic derivations take place in the delta buffer when the delta records are

determined. The possible source characteristics here are the characteristics from the real-time-enabled InfoCube filled from the aggregation levels involved.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-12

SAP AG 2006

5XOHV�IRU�8VLQJ�&KDUDFWHULVWLF�5HODWLRQVKLSVT 7KH�V\VWHP�FDUULHV�RXW�D�FRPELQDWLRQ�FKHFN�LI�DOO�WKH�FKDUDFWHULVWLFV�LQYROYHG�DUH�FRQWDLQHG�LQ�WKH�DJJUHJDWLRQ�OHYHO�T $�FKDUDFWHULVWLF�DWWULEXWH�LV�GHULYHG�LI�WKH�VRXUFH�FKDUDFWHULVWLF�LV�LQ�WKH�

DJJUHJDWLRQ�OHYHO�EXW�WKH�WDUJHW�FKDUDFWHULVWLF�LV�QRW�

<RX�FDQ�KDYH�PRUH�WKDQ�RQH�FKDUDFWHULVWLF�UHODWLRQVKLS�IRU�HDFK�UHDO�WLPH�,QIR3URYLGHU�

T $OO�FKDUDFWHULVWLF�UHODWLRQVKLSV�DUH�FDUULHG�RXW�VWHS�E\�VWHS�LQ WKH�VHTXHQFH�VSHFLILHG��

T )RU�%,�WLPH�FKDUDFWHULVWLFV��WKH�FKDUDFWHULVWLF�UHODWLRQVKLSV�SURYLGHG�ZLWK�WKH�V\VWHP�DUH�DOZD\V�DFWLYH��+RZHYHU��\RX�FDQQRW�VHH�WKHVH�LQ�WKH�OLVW�RI�FKDUDFWHULVWLF�UHODWLRQVKLSV��<RX�FDQQRW�GHDFWLYDWH�WKHP�HLWKHU��

T :KHQ�GHILQLQJ�FKDUDFWHULVWLF�UHODWLRQVKLSV��\RX�FDQ�PDS�³FDXVH�HIIHFW�FKDLQV´�([DPSOH�� 'HULYDWLRQ�VWHS��&LW\�Î 5HJLRQ

'HULYDWLRQ�VWHS��5HJLRQ�Î &RXQWU\

<RX�FDQ�GHDFWLYDWH�WKH�FKDUDFWHULVWLF�UHODWLRQVKLS�VWHSV�IRU�WHVW�SXUSRVHV�

�

��

3OHDVH�QRWH�WKDW�FKDUDFWHULVWLF�UHODWLRQVKLSV�IRU�WKH�%,�WLPH�FKDUDFWHULVWLFV�DUH�DOZD\V�DFWLYH� �

If the real-time-enabled InfoCube contains redundant time characteristics (such as 0FISCPER and the pair 0FISCPER3 and 0FISCYEAR), the system uses these relationships between target characteristics, as well as other relationships, for checking combinations or for derivation.

� You should note that the initial characteristic (# XQDVVLJQHG) plays a special role in a relation. This is

related to the fact that characteristics that are QRW in an aggregation level (and can QRW be derived) are updated with the initial value.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-13

SAP AG 2006

&XVWRPL]LQJ�WKH�&KDUDFWHULVWLF�5HODWLRQVKLSV��

� $WWULEXWHV� +LHUDUFKLHV� 'DWD6WRUH REMHFWV� ([LW

6HOHFWLQJ�WKH�FKDUDFWHULVWLFV�RI�WKH KLHUDUFK\�WKDW�WKH�FKDUDF�WHULVWLF UHODWLRQ�VKLS�LV�WR�EH�VHW�XS�IRU��

�

� The figure above shows the Customizing activities that the administrator has to carry out in the planning

modeler to set up the characteristic relationships. Note that you can only set up the characteristic relationships with the planning modeler, not with the wizard.

� If there is a FKDUDFWHULVWLF�UHODWLRQVKLS�ZLWKRXW�FKDUDFWHULVWLF�GHULYDWLRQ, you have to determine all

the characteristics between which a relationships is to be read; you also have to specify the type of characteristic relationships, such as hierarchy and attributes. Furthermore, you have to specify which characteristics you want characteristic combinations to be read between. In other words, if the hierarchy has several steps, you may only want the characteristics from three steps to be read, for example. You can use the “Selection” field to select this.

� You have to specify at least two characteristics in the “Selection” field for each step.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-14

SAP AG 2006

&XVWRPL]LQJ�WKH�&KDUDFWHULVWLF�5HODWLRQVKLSV��

�

� In the case of a FKDUDFWHULVWLF�UHODWLRQVKLSV�ZLWK�FKDUDFWHULVWLF�GHULYDWLRQ, the characteristic that is to

be derived must not be contained in the aggregation level. Only the basic characteristic may be in the aggregation level. It may be the case that multiple characteristics are derived because chain-shaped characteristic relationships are stored and their target characteristics are not in the aggregation level either. ��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-15

SAP AG 2006

$XWRPDWLF�6WUXFWXULQJ�RI�&KDUDFWHULVWLF�&RPELQDWLRQV

UWVYX7Z\[

]_â` bYZ

ccccccc

cUdVeX7Za[?fUdVeX7Za[7gUdVeX7Za[7hcikj\jal ZnmHâ` bYZo [;Vaprq_ZsmH^t` buZvtw_xyVYX7wkm+â` bYZz{Vaprq_w|m5â` bYZ

UdVeX7Za[?fUdVeX7Za[7gUdVeX7Za[7hikj\jal ZnmHâ` bYZo [;Vaprq_ZsmH^t` buZvtw_xyVYX7wkm+â` bYZz{Vaprq_w|m5â` bYZ

}~[Cw\��^�beX��{[?w�^\j��C}t�|�}�[;wa��^\beXt�;}��

&KDUDFWHULVWLF�UHODWLRQVKLS�ZLWKRXW�GHULYDWLRQ

&KDUDFWHULVWLF�UHODWLRQVKLS�EHWZHHQ�SURGXFW�DQG�SURGXFW�JURXS��$OO FKDUDFWHULVWLF�DWWULEXWHV�DUH�DOORZHG�LQ�WKH�ILOWHU�IRU�WKH�SURGXFW�DQG�SURGXFW�JURXS�

&KDUDFWHULVWLF�UHODWLRQVKLS�ZLWK�GHULYDWLRQ�³'HULYH�SURGXFW�JURXS�IURP�SURGXFW´

U�VYX0Za[

]\^_` beZ

cUWVYX7Z\[HfUWVYX7Z\[;gUWVYX7Z\[;hci{j_j\l ZnmHâ` bYZo [7V\p�qaZ�mH^_` bYZvtw_xyVeXCw|m+^_` beZzkVap�q_w{m+^\` bYZ

}�[Cwa��^�beXt�k[?w�âj��C}��n�}�[;w_�t^\buX��7}��

�3*�3��ZLWK��3��DQG��3*��

�3*�3��ZLWK��3*��RQO\

�

� Let us assume that there is a characteristic relationship between the product and product group of the

type hierarchy or attribution and that it was stored in the planning modeler. Both characteristics are selected in the aggregation level and all characteristic attributes are allowed for both characteristics; in other words, the hierarchy or attribution is not selected.

� If you had selected FRPELQDWLRQ�FKHFN�ZLWKRXW�FKDUDFWHULVWLF�GHULYDWLRQ, all the combinations

between the product and product group would be built up, as shown in the left-hand table. The # combinations of the product and the # combinations for the product group are therefore always valid and cannot be prohibited.

� If, on the other hand, you had chosen FRPELQDWLRQ�FKHFN�ZLWK�FKDUDFWHULVWLF�GHULYDWLRQ, the quantity

of valid combinations would be much smaller and there would be a stricter check of the combinations. This is because the characteristic derivation of product by product group would not find any # combination for the product group, since none was stored in the hierarchy or attribution, as the case may be. Conversely, the # combinations for the products cannot be suppressed because they are independent of the characteristic derivation.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-16

SAP AG 2006

5HSRVWLQJ�RQ�WKH�%DVLV�RI�&KDUDFWHULVWLF�5HODWLRQVKLSV

&RQVXOWLQJ-RKQ�6PLWK2UJDQL]DWLRQDO�8QLW(PSOR\HH

6DOHV-RKQ�6PLWK2UJDQL]DWLRQDO�8QLW(PSOR\HH

&RQVXOWLQJ2UJDQL]DWLRQDO�8QLW

¼ ��-RKQ�6PLWK6DODU\(PSOR\HH

6DOHV2UJDQL]DWLRQDO�8QLW

¼ ��-RKQ�6PLWK6DODU\(PSOR\HH

([HFXWH³5HSRVW�

FKDUDFWHULVWLF�UHODWLRQVKLSV´�

IXQFWLRQ

&KDQJH�WR�PDVWHU�GDWD �

�

0DVWHU�GDWD!

,QIR&XEH

([DPSOH��RUJDQL]DWLRQDO�XQLW�LV�GHULYHG�IURP�WKH�HPSOR\HH��7KH�HPSOR\HH�PRYHV�WR�D�GLIIHUHQW�RUJDQL]DWLRQDO�XQLW�

�

� The following problems can occur in connection with characteristic relationships:

Changes made in the data modeling area (such as a new assignment of attribute values or reorganizing a hierarchy) after planning has finished can lead to inconsistent data.

� You can use the 5HSRVW�RQ�EDVLV�RI�FKDUDFWHULVWLF�UHODWLRQVKLSV�function to repost transaction data so

that it is once again consistent with the characteristic relationships. In the process, the original records are deleted and reposted to the correct characteristic combinations.

� The above figure shows the data display from the query viewpoint.

� In the segment level characteristics, you can specify the characteristics for which values are reported.

This is only useful for characteristics that can be GHULYHG�DFFRUGLQJ�WR�WKH�FKDUDFWHULVWLF�UHODWLRQVKLSV.

� You have to comply with two technical prerequisites if you want to use this planning function:

• It can only be created on an aggregation level that refers directly to a real-time InfoCube; in other words, you cannot use it if the aggregation level is based on a MultiProvider.

• The aggregation level has to contain all the InfoObjects from the real-time InfoProvider that are valid in the aggregation levels.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-17

SAP AG 2006

'HOHWLQJ�,QYDOLG�&RPELQDWLRQV

6RXWK5HJLRQ

¼ ��6DOHV(QWHUSULVH

6RXWK5HJLRQ

¼ ��6DOHV(QWHUSULVH

([HFXWH�WKH�³'HOHWH�LQYDOLG�FRPELQDWLRQV´

IXQFWLRQ

,QIR&XEH

([DPSOH��LQ�WKH�,QIR3URYLGHU��\RX�ILQG�LQYDOLG�GDWD�WKDW�ZDV�HQWHUHG�E\�DFFLGHQW��EHIRUH�WKH�FKDUDFWHULVWLF�UHODWLRQVKLS�ZDV�DFWLYDWHG��7KH�LQYDOLG�GDWD�KDV�WR�EH�UHPRYHG�

�

� The following errors may occur with characteristic relationships: changes in the data modeling area can

lead to invalid data (particularly if characteristic relationships were added after going live). �

You can use the “'HOHWH�LQYDOLG�FRPELQDWLRQV” planning function to delete the key figure values for all the records that do not match the characteristic relationship.

� The above figure shows the data display from the query viewpoint.

� You have to comply with two technical prerequisites if you want to use this planning function:

• It can only be created on an aggregation level that refers directly to a real-time InfoCube; in other words, you cannot use it if the aggregation level is based on a MultiProvider.

• The aggregation level has to contain all the InfoObjects from the real-time InfoProvider that are valid in the aggregation levels.

��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-18

SAP AG 2006

1DYLJDWLRQ�$WWULEXWHV�YHUVXV�&KDUDFWHULVWLF�5HODWLRQVKLSV&KDUDFWHULVWLF�FRPELQDWLRQ��SURGXFW��SURGXFW�JURXS

� 'HILQH�SURGXFW�JURXS�DV�D�QDYLJDWLRQ�DWWULEXWH�RI�WKH�SURGXFW�FKDUDFWHULVWLF

� 'R�QRW�LQFOXGH�SURGXFW�JURXS�LQ�WKH�,QIR3URYLGHU� 3URGXFW�JURXS�FDQ�EH�GLVSOD\HG�LQ�DJJUHJDWLRQ�OHYHO�EXW�FDQ�QRWEH�SODQQHG

� ,QFOXGH�SURGXFW��SURGXFW�JURXS�LQ�,QIR3URYLGHU� 0RGHO�FKDUDFWHULVWLF�UHODWLRQVKLS� ,QFOXGH�SURGXFW��SURGXFW�JURXS�LQ�DJJUHJDWLRQ�OHYHO

<RX�FDQQRW�VHOHFW�YLD�GLVSOD\�DWWULEXWHV�

�!�6HOHFW�DQG�SODQ SURGXFW�JURXS�LQ�DJJUHJDWLRQ�OHYHO�!�6HOHFW�DQG�SODQ SURGXFW�DQG�SURGXFW�JURXS�LQ�DJJUHJDWLRQ�OHYHO

�!�3URGXFW�JURXS�FDQQRW�EH�SODQQHG�EXW�FDQ�EH�VHOHFWHG

�

�

�

� The figure above shows the different options for modeling business-relevant characteristic

combinations. �

In general, you can use either navigation attributes or characteristic relationships. �

The difference between them is that navigation attributes are only designed for selecting and as information but cannot be used for planning, whereas characteristic relationships can be used for both selecting and planning.

� Result: navigation characteristics (that were not additionally included in the real-time InfoProvider)

merely provide additional information; characteristics from the InfoProvider, on the other hand, are posted information.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-19

SAP AG 2006

'DWD�6OLFHV��

*HQHUDO�GDWD�SURWHFWLRQ�� $OO�,QIR3URYLGHUV H[FHSW�IRU�UHDO�WLPH�,QIR3URYLGHUV DUH�DOZD\V�

UHDG�RQO\�� ,Q�WKH�UHDO�WLPH�,QIR3URYLGHU��IRU�H[DPSOH��

� 'DWD�IURP�DGRSWHG�SODQ�YHUVLRQV�VKRXOG�QR�ORQJHU�EHFKDQJHG�

� $FWXDO�GDWD�VKRXOG�QRW�EH�RYHUZULWWHQ�

'DWD�VOLFHV�LQ�%,�LQWHJUDWHG�SODQQLQJ� 3URWHFWLRQ�DJDLQVW�PDQXDO�HQWULHV�IURP�SODQ�TXHU\�RU�SODQQLQJ�

IXQFWLRQ� 'DWD�VOLFHV�FDQ�EH�DFWLYDWHG�RU�GHDFWLYDWHG� <RX�FDQ�XVH�YDULDEOHV�IRU�GDWD�VOLFHV

�� "

�

� 'DWD�VOLFHV are a concept for protecting data in a real-time InfoProvider FHQWUDOO\ against being

changed. This protection affects input-ready queries and all planning functions that use this InfoProvider.

� If you want to ensure that certain plan versions can no longer be changed after a certain time or

overwritten with current data, for example, you can use a data slice containing these plan versions.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-20

SAP AG 2006

'DWD�6OLFHV��

'DWD�VOLFHV�QHHG�WR�EH�FUHDWHG�LQ�%,�LQWHJUDWHG�SODQQLQJ�IRU�WKH ,QIR3URYLGHU�

�

� There are WZR�W\SHV�RI�GDWD�VOLFH:

• Data slices based on a VHOHFWLRQ. Here you determine the restrictions for the characteristics that you wish to protect against changes.

• Data slices based on an H[LW�FODVV. In the exit class, you can implement a customer-specific logic to protect data records.

� In general, the following rules apply to data slices:

• If no data slice is defined for a real-time enabled InfoProvider, any valid characteristic combination can be posted in this InfoProvider.

• Every data record that is part of the selection of a data slice is protected against changes.

• Corresponding cells in input-ready queries can QRW be changed; this kind of record can QRW be changed or saved using planning functions.

� If a real-time-enabled InfoProvider contains a data slice that includes no characteristic value restrictions

at all, the data slice acts as a lock for postings of all types in the entire real-time-enabled InfoProvider. �

After you create a data slice, it is activated automatically. The settings made in the definition of the data slice have an immediate effect on the ability to update data.

� You can deactivate an existing data slice at any time (LQDFWLYH state); this data slice is then no longer

included.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-21

SAP AG 2006

&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�FKDUDFWHULVWLF�UHODWLRQVKLSV�DQG�



�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-22

SAP AG 2006

&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�FKDUDFWHULVWLF�UHODWLRQVKLSV�DQG�



�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-23

�([HUFLVHV�

8QLW��&KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV��


• Model characteristic relationships with and without characteristic derivations.

• Use the realignment function for characteristic derivations.

• Compare the usages of navigation attributes and characteristic relationships.

• Use data slices to block plan data.

You are a member of a project team that has the task of introducing planning and you want to familiarize yourself with the topic of characteristic relationships in order to be able to plan according to the correct business combinations. Firstly planning is to be modeled using a hierarchy and then attribute assignment is to be examined.

A characteristic derivation is to be defined for the attribute assignment scenario and the plan data is to be reposted.

Then the modeling navigation attribute is to be compared to the characteristic relationship.

Finally, the data slice is to be used to block the plan data.

The scenarios are presented in a new InfoProvider and are therefore independent of the previous exercise scenario.

1-1 Firstly ERWWRP�XS�SODQQLQJ�should be implemented XVLQJ�D�KLHUDUFK\. Two models are possible. Task 1-1 describes the first variant and Task 1-2 the second. In both models the hierarchy contains the basic characteristic “ Product” (technical name “=B352'8&7” ) and the node characteristic “ Product line” (technical name “=B352'/,1” )

1-1-1 In the Administrator Workbench, navigate to the basic characteristic and briefly examine the “ Hierarchy_with_two_characteristics” to see which business characteristics combinations it contains. Afterwards, take a look at InfoProvider 7%:��+�� this contains both the

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-24

product and product line characteristics. The InfoProvider is used for the first model. Then you return to the planning modeler.

1-1-2 A characteristic relationship must now be created for InfoProvider 7%:��+��, whereby it is planned to include the basic characteristic and the node characteristic in the aggregation level to be created afterwards and also in the query. :KLFK�YDULDQW�RI�WKH�FKDUDFWHULVWLF�UHODWLRQVKLSV�VKRXOG�EH�VHOHFWHG�RQ�WKH�&KDUDFWHULVWLF�5HODWLRQVKLS�WDE�RI�WKH�,QIR3URYLGHU"��

� Characteristic relationship without derivation

� Characteristic relationship without characteristic derivation

:K\�KDYH�\RX�RSWHG�IRU�WKHVH�YDULDQWV"� _____________________________________________________________ &UHDWH�the PXOWLOHYHO�FKDUDFWHULVWLF�UHODWLRQVKLS�between the product and product line in the system accordance with the specifications made above and then VDYH.

1-1-3 You now have to create an aggregation level on the basis of InfoProviders 7%:��+��. Technical name: +��B$/B�� Description: 7%:��B+��B$/�� Add the following integration objects to the aggregation level: FXUUHQF\��ILVFDO�\HDU�YDULDQW��ILVFDO�\HDU��DPRXQW��YHUVLRQ��SURGXFW�OLQH��SURGXFW�� $FWLYDWH the aggregation level. This aggregation level is later reserved for the query “ …_+LHUDUFK\ �” . It contains the product and product line characteristics. $FWLYDWH�this aggregation level and exit the Planning Modeler.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-25

1-1-4 Navigate to the 4XHU\�'HVLJQHU��Create a query for the DJJUHJDWLRQ�OHYHO�FUHDWHG�LQ�7DVN��.

Firstly the “ FKDUDFWHULVWLF�PRGHO” , that is the first model variant is to be modeled, this means that the hierarchy is not displayed in the query, however the two characteristics – product line and product – are used in the rows. The “ characteristic relationship” ensures that the correct combination is displayed. Proceed as follows: In the area “&KDUDFWHULVWLF�5HVWULFWLRQV” include the following: Fiscal year: 9DULDEOH�*URXS��B9$5B)<B��B30�Fiscal year variant: .��3URGXFW�OLQH� -8&��:$7�3URGXFW�� :DWHU��:DWHU��:DWHU�� $SSOH�-XLFH��7RPDWR�-XLFH�� 0DQJR�-XLFH��2UDQJH�-XLFH�Version: & Currency: 86' Please ensure that the characteristics product line and product are included here by selecting them accordingly in order to create a write access to these as described. In the area “&ROXPQV” you can include the key figure “$PRXQW” . Configure the key figure so that it can be LQSXW�PDQXDOO\�and also so that LW�FDQ�EH�ILOOHG�E\�H[HFXWLQJ�SODQQLQJ�IXQFWLRQV. In the area “ Rows” add the characteristic “3URGXFW�OLQH” EHIRUH�“3URGXFW” . Set “ Key and Text” for both. Select “&KDUDFWHULVWLF�UHODWLRQVKLSV” as “$FFHVV�W\SH�IRU�UHVXOWV�YDOXHV” in the “3URSHUWLHV” in the rows of the characteristics. 6DYH�your query under the following description: Description: 7%:��B+��B$/��B34B+,(5$5&+<B� Technical name: +��B$/B��B3ODQTXHU\B+,(5$5&+<�. Then H[HFXWH�it for the fiscal year ��. You should receive the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-26

Summary: In terms of characteristic relationships, the hierarchy is used in the Planning Modeler to determine the correct business combinations that are displayed in the query, they are not imported physically. Please remember that both characteristics must be included in your selection in the area of characteristic restrictions, as a characteristic relationship without characteristic derivation was selected in the Planning Modeler and therefore also in the aggregation level that is used as a basis for the query.

1-1-5 Ultimately you want to ensure that the characteristic combination is displayed as a kind of “ runtime hierarchy” and therefore make a drill down possible. For this purpose you should not click on one of the two characteristics, instead click in the empty area and thereby navigate to the *HQHUDO tab page in the area “3URSHUWLHV��URZV�DUHD�” and choose “$FWLYH” for “'LVSOD\�DV�KLHUDUFK\” and “3URGXFW” for the field “([SDQG�XS�WR” . Save the query and then execute it for fiscal year ��. You should obtain the following display:

1-2 The VHFRQG�PRGHO�the “%:�+LHUDUFK\” model will be described in the following section. In general, here you have two options with the InfoProvider modeling: - Product is included in the InfoProvider, product line is not. This means that no characteristic relationship is required in the Planning Modeler. The hierarchy comes into play later when the product characteristic is involved. Writing only takes place on the product. - Product and product line in the InfoProvider, this means that a characteristic relationship is required in the Planning Modeler. However, here it takes the form of a characteristic derivation, as only the product is included in the aggregation level and query. Writing only takes place in the product, product line combination due to the characteristic derivation.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-27

In both cases only the product is included in the aggregation level and then later the hierarchy is set to this characteristic in the query so that the product line is only indirectly involved.

1-2-1 For this purpose, use the InfoProvider 7%:��+��that you used previously��This contains the two characteristics – product and product line. Create a second FKDUDFWHULVWLF�UHODWLRQVKLS�LQ�WKH�3ODQQLQJ�0RGHOHU that is subject to the same basic conditions as in Tasks 1-1-1 and 1-1-2. This time set “&KDUDFWHULVWLF�5HODWLRQVKLS�ZLWK�&KDUDFWHULVWLF�'HULYDWLRQ” . The product is the source characteristic; the product line is the target characteristic. (You could also reset the characteristic relationship already present to characteristic derivation, as this would have the result that the derivation uses all aggregation levels in which the product line is missing and in such aggregation levels in which it is contained it will read out the combinations).

1-2-2 In the Planning Modeler for InfoProvider 7%:��+�� create a second DJJUHJDWLRQ�OHYHO�by FRS\LQJ�WKH�ILUVW�DJJUHJDWLRQ�OHYHO. Enter the following descriptions: Technical name: +��B$/B�� Description: 7%:��B+��B$/�� 5HPRYH�the characteristic of the SURGXFW�OLQH and DFWLYDWH�the aggregation level. Exit the planning modeler.

1-2-3 Navigate again to the 4XHU\�'HVLJQHU and create a new query for aggregation level +��B$/B��with the following configuration In the “&KDUDFWHULVWLF�UHVWULFWLRQV” include the following: Fiscal year: 9DULDEOH�*URXS��B9$5B)<B��B30�Fiscal year variant: .��3URGXFW�� :DWHU��:DWHU��:DWHU�� $SSOH�-XLFH��7RPDWR�-XLFH�� 0DQJR�-XLFH��2UDQJH�-XLFH�Version: & Currency: USD In the area “&ROXPQV” you can include the key figure “$PRXQW” . Configure the key figure so that it can be LQSXW�PDQXDOO\�and also so WKDW�LW�FDQ�EH�ILOOHG�E\�H[HFXWLQJ�SODQQLQJ�IXQFWLRQV.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-28

In the area “5RZV” add the characteristic “3URGXFW” . Set “.H\�DQG�7H[W” . Select “&KDUDFWHULVWLF�UHODWLRQVKLSV” as “$FFHVV�W\SH�IRU�UHVXOWV�YDOXHV” in the “3URSHUWLHV” of the rows of the characteristics. In the characteristic remaining for the rows – “3URGXFW” – choose the KLHUDUFK\�with the technical name “+LHUDUFK\BZLWKBWZRBFKDUV” in “3URSHUWLHV” . Set “([SDQGLQJ�XS�WR�OHYHO” to “ �” . Choose “$FWLYDWH�KLHUDUFK\�GLVSOD\” . You can leave other settings for the hierarchy and characteristic unchanged. 6DYH�your query as follows: Description: 7%:��B+��B$/��B34B+,(5$5&+<B� Technical name: +��B$/B��B3ODQTXHU\B+,(5$5&+<� . Execute the query for the fiscal year ��. You should now receive the following display:

As you can see, in the query area there is still a node for the “ Rest” , this means characteristic value #, this display setting can only be suppressed in the hierarchy maintenance. In this case, navigate to the hierarchy maintenance and then in change mode choose *RWR��!�+LHUDUFK\�$WWULEXWHV�and select the setting “6XSSUHVV�“1RW�$VVLJQHG” �1RGH” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-29

Please note that this setting is practical to improve performance, especially when there are many node levels. This setting should not be made during the exercises. Now exit the Query Designer.

1-2-4 Navigate to the %([�$QDO\]HU, to map the two model variants of the hierarchy together in a workbook. Create a new workbook with the following configuration: Place the cursor in cell $� and enter “3ODQQLQJ�ZLWK�KLHUDUFKLHV�DQG�FKDUDFWHULVWLF�UHODWLRQVKLSV” in UHG� font size ��EROG type. Afterwards create a VDYH�EXWWRQ for cell $��with the pushbutton text “6DYH” . In cell &� create a rHIUHVK�EXWWRQ with the pushbutton text “5HIUHVK” . Place the cursor in cell $��and type “9DULDQW��” in UHG, font size ��,�EROG�type. In cell $�� create an DQDO\VLV�WDEOH relating to the query with the technical name “+��B$/B��B3ODQTXHU\B+,(5$5&+<�” .Select “2SWLPXP�KHLJKW” . Afterwards place the cursor in cell $��and type “9DULDQW��” in UHG, font size ��,�EROG�type. In cell $�� create an DQDO\VLV�WDEOH relating to the query with the technical name “+��B$/B��B3ODQTXHU\B+,(5$5&+<�” . Select “2SWLPXP�KHLJKW” . 6DYH�the workbook under the following name: *URXS��B7%:��B+,(5$5&+<. ([HFXWH�the workbook for the fiscal year ��.��You should now receive the following display:��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-30

�

1-2-5 In one of the top analysis tables, plan ��units for the combination (juice, mango juice). Afterwards right-click in this cell and choose “7UDQVIHU�YDOXHV” ; this should have the result that you see a roll-up sum on the parent nodes. You should also be able to see the same reaction in the bottom analysis table. Afterwards enter ��units for the combination (juice, tomato juice) in the bottom analysis table. Afterwards right-click in this cell and choose “7UDQVIHU�YDOXHV” ; this should have the result that you see a roll-up sum on the parent nodes, this time in both the bottom and top analysis table. You should receive the following result:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-31

Please note that you do not receive a roll-up sum by choosing the “ Refresh” button or by choosing the “ Temporarily Interrupt Automatic Update” button! Now exit the BEx Analyzer without saving the data.

1-3 Now you will set up a scenario for FKDUDFWHULVWLF�GHULYDWLRQ�using the “0DWHULDO” characteristic (technically “0DWB%,” ) and the attribute “0DWHULDO�JURXS” (technically (“0$7B*5283” ). The following correct business characteristic combinations are present in the master data maintenance for the material characteristic:

i. Material ii. Attribute Material Group

iii. T1 iv. TWAT

v. T2 vi. TWAT

vii. T3 viii. TWAT

ix. T4 x. JUC

xi. T5 xii. JUC

xiii. T6 xiv. JUC

1-3-1 Navigate to the 3ODQQLQJ�0RGHOHU and choose the ,QIR3URYLGHU�with the technical name 7%:��'�� For this InfoProvider, set a FKDUDFWHULVWLF�UHODWLRQVKLS�LQ�WKH�IRUP�RI�D�FKDUDFWHULVWLF�GHULYDWLRQ on the &KDUDFWHULVWLF�5HODWLRQVKLS tab page. The characteristic relationship is based on an attribute assignment and the basic characteristic is called “0$7B%,” . The target characteristic is the “0DWHULDO�JURXS” . Navigate to the Administrator Workbench in the master data maintenance of the characteristic “0DWB%,” and check for yourself if the characteristic “0$7B*5283” is used as an attribute for the material characteristic. Examine the characteristic combinations between material and material group. Then exit the Administrator Workbench.

1-3-2 Now create an aggregation level with the following designations: Technical name: '��B$/B�� Description: 7%:��B'��B$/�� . Select the following characteristics and key figures in the aggregation level: YHUVLRQ��ILVFDO�\HDU��ILVFDO�\HDU�YDULDQW��PDWHULDO��FXUUHQF\�NH\��UHYHQXH. $FWLYDWH this aggregation level.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-32

1-3-3 Now FRS\�the DJJUHJDWLRQ�OHYHO�Dnd specify the following designations: Technical name: '��B$/B�� Description: 7%:��B'��B$/�� . 6XSSOHPHQW�the copied aggregation level with the characteristic 0DWHULDO�JURXS�and UHPRYH the characteristic 0DWHULDO�and DFWLYDWH�the aggregation level. Afterwards exit the planning modeler. The aim is to model a bottom-up roll-up in which a summarization of all materials for each material group is shown in the second aggregation level when the characteristic derivation writes the characteristic material group in the first aggregation level.

1-3-4 Now navigate to the 4XHU\�'HVLJQHU and VHDUFK�there for your aggregation level with the technical name '��B$/B��. Configure the query as follows: In the area “&KDUDFWHULVWLF�UHVWULFWLRQV” include the following fields and selections: )LVFDO�\HDU�� 9DULDEOH�*URXS��B9$5B)<B��B30�)LVFDO�\HDU�YDULDQW�� .��9HUVLRQ�� &�&XUUHQF\�� 86'�0DWHULDO�� 7��WR�7�� In the “5RZV” area include the field “0DWHULDO” and in the “&ROXPQV” area include the key figure “5HYHQXH” . In the “3URSHUWLHV” of key figure “ Revenue” , select “'DWD�FDQ�EH�FKDQJHG�E\�XVHU�LQSXWV�RU�SODQQLQJ�IXQFWLRQV” for planning. In the “3URSHUWLHV” of row characteristic “0DWHULDO” select “.H\�DQG�7H[W” under “'LVSOD\�DV” and “&KDUDFWHULVWLF�5HODWLRQVKLSV” under “$FFHVV�7\SH�IRU�5HVXOW�9DOXHV” . 6DYH�and specify the following descriptions for your query: Description: 7%:��B'��B$/��B'(5,9$7B� Technical name: '��B$/B��B'(5,9$7B� ([HFXWH�your query for fiscal year ��. You should now receive the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-33

As you can see, the system informs you that characteristics combinations have been created.

1-3-5 Now create a second query, this time for the aggregation level with the technical name '��B$/B�� that is to display an aggregation of all materials if the characteristic derivation accesses the first aggregation level. Conduct the following configurations: Include the following fields and selections in the “&KDUDFWHULVWLF�UHVWULFWLRQV” areas: )LVFDO�\HDU�� 9DULDEOH�*URXS��B9$5B)<B��B30�)LVFDO�\HDU�YDULDQW�� .��9HUVLRQ�� &�&XUUHQF\�� 86'�0DWHULDO�JURXS�� 7:$7��-8& In the “5RZV” area include the field “0DWHULDO�JURXSV” and in the “&ROXPQV” area include the key figure “5HYHQXH” . In the “3URSHUWLHV” of key figure “ Revenue” , select “'DWD�FDQ�EH�FKDQJHG�E\�XVHU�LQSXWV�RU�SODQQLQJ�IXQFWLRQV” for planning. In the “3URSHUWLHV” of row characteristic “0DWHULDO�JURXS” select “.H\�DQG�7H[W” under “'LVSOD\�DV” and “&KDUDFWHULVWLF�5HODWLRQVKLSV” under “$FFHVV�7\SH�IRU�5HVXOW�9DOXHV” . 6DYH�your query as follows: Description: 7%:��B'��B$/��B'(5,9$7B� Technical name: '��B$/B��B'(5,9$7B� ([HFXWH�it for ��. You should receive the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-34

Exit the Query Designer.

1-3-6 Navigate to the BEx Analyzer and create a workbook with the following names: Description: *URXS��B7%:��B'(5,9$7,21. Place the cursor in cell $��and enter “&KDUDFWHULVWLF�GHULYDWLRQ” in UHG, font size ��,�EROG�type. Place the cursor in cell $� and create a VDYH�EXWWRQ�with the designation “6DYH” in area: �$��$��. 'HVHOHFW�“$GMXVW�DUHD�WR�LWHP�VL]H". In cell '��create a rHIUHVK�EXWWRQ with the designation “5HIUHVK” in area �'��'��. 'HVHOHFW�“$GMXVW�DUHD�WR�LWHP�VL]H” . For cell +� create 0HVVDJHV�in area �+��/�� and VHOHFW�DOO�ILHOGV�on the *HQHUDO tab page. Type “6\VWHP�0HVVDJHV” in cell H6. 6DYH your workbook�

1-3-7 In cell $��in UHG, font size��, EROG�type��enter: “3ODQQLQJ�IRU�PDWHULDO�RQ�DJJUHJDWLRQ�OHYHO�ZLWKRXW�PDWHULDO�JURXS�±�PDWHULDO�JURXS�ZLOO�EH�GHULYHG” Place the cursor in cell $�� and create an analysis table relating to the TXHU\�RI�7DVN ��. Select “2SWLPXP�KHLJKW” in the definition of the analysis table. 6DYH your workbook�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-35

1-3-8 In cell $��in font size ��, EROG�and in UHG, enter: “6XPPDWLRQ�RI�DOO�PDWHULDOV�DV�WKH�PDWHULDO�JURXS�LV�GHULYHG” . Place the cursor in cell $��and create an DQDO\VLV�WDEOH�that relates to the TXHU\�RI�7DVN��. Select “2SWLPXP�KHLJKW” in the definition of the analysis table. �Save your workbook.

1-3-9 ([HFXWH�the workbook for the fiscal year ��. You should receive the following display – the figure below shows an excerpt –.

Make the following plan in the analysis table:

xv. Material xvi. Description xvii. Revenue

xviii. T1 xix. Table water 1

xx. 10

xxi. T2 xxii. Table water 2

xxiii. 20

xxiv. T3 xxv. Table water 3

xxvi. 30

xxvii. T4 xxviii. Juice 1 xxix. 100

xxx. T5 xxxi. Juice 2 xxxii. 200

xxxiii. T6 xxxiv. Juice 3 xxxv. 300

You should receive the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-36

Place the cursor at the intersection of “ Overall result” and “ Revenue” (this should be cell &��) and select “7UDQVIHU�YDOXHV” to display the WRWDO�RI�86'��. Afterwards examine the second analysis table with the aggregated data. According to the correct business assignment as initially described in Task 1-3, you receive the following aggregation values which result from the characteristic derivation modeled in the background:

1-3-10 6DYH�the plan data, exit the BEx Analyzer and check for yourself in InfoProvider 7%:��'�� that the plan data records are all stored depending on material and material group and therefore reporting of these correct business combinations is possible. The InfoProvider should display the following:��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-37

1-4 In the following task, the planning function “5HDOLJQPHQW�RI�&KDUDFWHULVWLF�5HODWLRQVKLSV” is used to apply changes in the plan data records after a realignment of materials and material groups which occurred after planning. Assume that the assignment of materials T1 to T3 is to be changed from material group table water to water and the values planned with the old, incorrect combination from Task 1-3-9 or 1-3-10 are now to be realigned with the new, correct combination.

1-4-1 Before the task begins, the instructor will conduct the realignment of materials T1 to T3 from material group TWAT to WAT in the master data of characteristic “ MAT_BI” ; this results in the following characteristic relationships:

Please inform your instructor that you have finished Task 1-3 so that he can start the realignment. The instructor will then activate the master data.

1-4-2 Define a new aggregation level for the realignment function by copying aggregation level '��B$/B��and making the following specifications:

Technical name: '��B$/B�� Description: 7%:��B'��B$/��. Add DOO�RI�WKH�LQIRUPDWLRQ�REMHFWV�WR�WKLV�OHYHO. $FWLYDWH this aggregation level.

1-4-3 Define a “5HDOLJQPHQW�RI�&KDUDFWHULVWLF�5HODWLRQVKLSV” planning function for the aggregation level you have just created. Technical name: '��B3)B�� Name: � � � � 7%:��B'��B$/��B3)��B5($/,*1��:KLFK�ILHOG�LV�WR�EH�LQFOXGHG�DV�WKH�ILHOG�WR�EH�FKDQJHG"��BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-38

�2WKHU�VHWWLQJV�DUH�QRW�SRVVLEOH��6DYH the planning function.

1-4-4 Create a ILOWHU�for aggregation level '��B$/B��; you will use this filter for the subsequent tracing of the function. Technical name: '��B)B�� Description: 7%:��B'��B$/��B)�� Include all LQIRUPDWLRQ�REMHFWV�in the filter and select the following characteristic values for the characteristic: )LVFDO�\HDU�YDULDQW��.��9HUVLRQ�� &�8QLW�RI�PHDVXUH�� 0DWHULDO�� 7��WR�7��)LVFDO�\HDU�� 9DULDEOH�*URXS��B9$5B)<B��B30�3RVWLQJ�SHULRG�� 0DWHULDO�JURXS�� 7:$7��:$7�&XUUHQF\�� 86'��Please remember that “3RVWLQJ�SHULRG” and “8QLW�RI�PHDVXUH” were not planned, however they must be included due to the property of the planning function “ Realignment of Characteristic Relationships” of checking the InfoProvider and not the aggregation level. Therefore the characteristic attributes are set to “ #” for “ not assigned” .��6DYH�the filter.

1-4-5 Now create a SODQQLQJ�VHTXHQFH�for aggregation level '��B$/B��for the filter and planning function with the following description: Technical name: '��B6B�� Description: 7%:��B'��B$/��B6��6DYH�the sequence and then WUDFH the planning function for the fiscal year ��. Do QRW�VDYH�the plan data and then exit the Planning Modeler.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-39

1-4-6 Navigate to the 4XHU\�'HVLJQHU and define a query for aggregation level '��B$/B��which you will use later to check if the realignment was successful.

In the area “&KDUDFWHULVWLF�UHVWULFWLRQV” add the filter '��B)B��. In the “5RZV” area include the field “0DWHULDO�JURXS” before “0DWHULDO” and in the “&ROXPQV” area include the key figure “5HYHQXH” . In the “3URSHUWLHV” of key figure “5HYHQXH” , select “'DWD�FDQ�EH�FKDQJHG�E\�XVHU�LQSXWV�RU�SODQQLQJ�IXQFWLRQV” for planning. In the “3URSHUWLHV” of row characteristic “0DWHULDO�JURXS” and “0DWHULDO” select “.H\�DQG�7H[W” under “'LVSOD\�DV” and “0DVWHU�'DWD” under “$FFHVV�7\SH�IRU�5HVXOW�9DOXHV” . 6DYH�your query as follows: Description: 7%:��B'��B$/��B5($/,*10(17 Technical name: '��B$/B��B5($/,*10(17 ([HFXWH�it for ��. You should now see the following display:

As you can see, the system has recognized the new, correct business combination! 6DYH�and then exit the Query Designer.

1-4-7 Navigate to the %([�$QDO\]HU and your workbook *URXS��B7%:��B'(5,9$7,21��Place the cursor in cell $��and, in UHG, font size ��, EROG�type, enter: “5HDOLJQPHQW�DV�D�UHVXOW�RI�UHDVVLJQPHQW�FDXVHG�E\�EXVLQHVV�FLUFXPVWDQFHV” . Create an DQDO\VLV�WDEOH�in cell $�� that relates to the TXHU\�IURP�7DVN��. Select “ RSWLPXP�KHLJKW” . This query is listed internally as '$7$B3529,'(5B�.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-40

Now place the cursor in cell $��and create a Design Item EXWWRQ. Make the following configuration Area: �$��%�� Pushbutton text: )XQFWLRQ��5HDOLJQPHQW�7:$7��!�:$7��Select “$GMXVW�DUHD�WR�LWHP�VL]H” .��In the VWDWLVWLFDO�SDUDPHWHUV�area, select your SODQQLQJ�IXQFWLRQ�IURP�7DVN�� and '$7$B3529,'(5B��that you have included in this task as “'DWDB3URYLGHUB)LOWHU” . 6DYH�the workbook and then execute it for fiscal year ��. The following display should appear:

Now execute the realignment function. You should receive the following results:

If you click on “6\VWHP�0HVVDJHV” you should receive the following message:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-41

6DYH�your SODQ�GDWD�and check in InfoProvider 7%:��'��, that three credit and debit lines have been written. In the List Viewer you should receive the following data records:

Please remember that the InfoProvider is compressed after the realignment function is executed and the transaction data has been saved. It is compressed with a zero elimination run to ensure that records with a zero balance are deleted from the database. This should not be conducted in this exercise.

1-5 Afterwards the QDYLJDWLRQ�DWWULEXWHV�IRU�SODQQLQJ�VHOHFWLRQ are to be enabled. Here, you are again working with the basic characteristic “3URGXFW” (technical name “352'8&7” ) and the navigation characteristic “3URGXFW�OLQH” (technical name “352'8&7/,1” ). The “ Product” characteristic has been included in InfoProvider 7%:��1�� that has been created for you, “ Product Line” is not present! Please remember that the navigation attribute must be activated in the InfoProvider.

1-5-1 Navigate to the 3ODQQLQJ�0RGHOHU and take a look at the ,QIR3URYLGHU tab page for InfoProvider 7%:��1�� In the bottom area of this tab page you will find the ,QIR2EMHFWV tab page. On this tab you can find the 1DYLJDWLRQ�$WWULEXWHV section. You should be able to see the navigation characteristic “ PRODUCTLN” and its basic characteristic. Create an aggregation level for this with the following description:

Technical name: 1��B$/B�� Description: 7%:��B1��B$/�� Include DOO FKDUDFWHULVWLFV�in the aggregation level and activate them. As you can see, the navigation characteristic is not addressable in the aggregation level as there is no write access for it.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-42

Afterwards exit the planning modeler.

1-5-2 Navigate to the 4XHU\�'HVLJQHU and create a query for your aggregation level 1��B$/B��. When it is used later in the BEx Analyzer, the query should display all products which you have selected with the navigation attribute for the corresponding product line. Make the following configuration: Include the following as stated below in the area “&KDUDFWHULVWLF�5HVWULFWLRQV” : Fiscal year: 9DULDEOH�*URXS��B9$5B)<B��B30�Fiscal year variant: .� Product: � � 7��WR�7��1$9B3URGXFWOLQH�� :$7��-8&�Version: & Currency: USD In the area “&ROXPQV” you can include the key figure “$PRXQW” . Configure the key figure both so that it can be LQSXW�PDQXDOO\�and also so that LW�FDQ�EH�ILOOHG�E\�H[HFXWLQJ�SODQQLQJ�IXQFWLRQV. Include the characteristic “3URGXFW” and the navigation attribute “1$9B3URGXFWOLQH” in the URZV; NAV_Productline should be added EHIRUH Product. Select “.H\�DQG�7H[W” and “0DVWHU�'DWD” in the properties of the characteristic “3URGXFW“ . Select “.H\” and “0DVWHU�'DWD” for navigation attribute “1$9B3URGXFWOLQH” . 6DYH�your TXHU\ as follows: Description: 7%:��B1��B$/��B1$9 Technical name: 1��B$/��B1$9 Execute the query for the fiscal year ��. You should receive the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-43

As you can see, plan data has already been entered. Now exit the Query Designer.

1-5-3 Navigate to the %([�$QDO\]HU and create a new workbook. Place the cursor in cell $��and, in UHG, font size ��, EROG�type, enter: “8VH�RI�QDYLJDWLRQ�DWWULEXWHV�LQ�SODQQLQJ” . Place the cursor in cell $� and create a VDYH�EXWWRQ with the description “6DYH” . In cell &� create a rHIUHVK�EXWWRQ with the designation “5HIUHVK” . In cell $�� add an DQDO\VLV�WDEOH that references the TXHU\�LQ�7DVN��. Select “2SWLPXP�KHLJKW” . This analysis table is listed internally as DATA_PROVIDER_1. 6DYH�the workbook under the following name: *URXS��B7%:��B1$9,*$7,21. Then execute�it for the fiscal year ��. You obtain the following display:

1-5-4 In cell $�� create the design item GURSGRZQ�ER[. On the ILUVW�WDE�SDJH�select DATA_PROVIDER_1 and the field “'LVSOD\�GHVFULSWLRQ” and GHVHOHFW�the fields “$GMXVW�DUHD�WR�LWHP�VL]H” and “ ,QSXW�0RGH” . On the VHFRQG�WDE�SDJH�select „1$9B3URGXFWOLQH” as „'LPHQVLRQ” (the navigation attribute) and select “3RVWHG�9DOXHV” as the “5HDG�0RGH” . Select “6WDQGDUG�7H[W” and “.H\�DQG�7H[W” . On the WKLUG�WDE�SDJH�select DATA_PROVIDER_1. 6DYH�again and execute the workbook for ��. You should now receive the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-44

Select product line “ -8&” , and choose the pushbutton “5HIUHVK” . The following display will appear:

Change the plan data as follows:

xxxvi. Product xxxvii. Old Value

xxxviii. New Value

xxxix. T4 xl. 40 xli. 50

xlii. T5 xliii. 50 xliv. 60

xlv. T6 xlvi. 60 xlvii. 70

Then switch to product line “:$7” and choose the pushbutton “5HIUHVK” and make the following plan:

xlviii. Product xlix. Old Value

l. New Value

li. T1 lii. 10 liii. 20

liv. T2 lv. 20 lvi. 30

lvii. T3 lviii. 30 lix. 40

6DYH�your SODQ�GDWD and navigate to the /LVW�9LHZHU of InfoProviders

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-45

7%:��1��Display the transaction data here. The following data should be displayed:

�As you can see, the product line is RQO\ read in the List Viewer at runtime (column NAV_ProductLine is colored blue) because the product line was not additionally included as a characteristic in the InfoProvider:

As the field “ Product line” was not included in the InfoProvider, the navigation attribute could RQO\ be read “ on the fly” to enable the selection of the products.

1-6 Afterwards place a data slice on the plan data so that nobody can replan the blocked segments either manually or automatically. Navigate to the 3ODQQLQJ�0RGHOHU and from there to InfoProvider 7%:��1��Create a data slice that blocks materials 7��7��and�7�. Then VDYH your InfoProvider. Navigate again to your workbook *URXS��B7%:��B1$9,*$7,21�and�examine the analysis table� The segments that relate to product line WAT should be blocked against manual and automatic planning whereas the planning should still be possible for products of product line JUC: The following data is displayed:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-46

��Now exit the BEx Analyzer and return to the screen that appears after logging onto the system.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-47

6ROXWLRQV�

8QLW�� &KDUDFWHULVWLF�5HODWLRQVKLSV�DQG�'DWD�6OLFHV��

1-1 Firstly ERWWRP�XS�SODQQLQJ�should be implemented XVLQJ�D�KLHUDUFK\. Two models are possible. Task 1-1 describes the first variant and Task 1-2 the second. In both models the hierarchy contains the basic characteristic “ Product” (technical name “=B352'8&7” ) and the node characteristic “ Product line” (technical name “=B352'/,1” )

1-1-1 In the Administrator Workbench, navigate to the basic characteristic and briefly examine the “ Hierarchy_with_two_characteristics” to see which business characteristics combinations it contains. Afterwards, take a look at InfoProvider 7%:��+��; this contains both the product and product line characteristics. The InfoProvider is used for the first model. Then you return to the planning modeler.

1-1-2 A characteristic relationship must now be created for InfoProvider 7%:��+��, whereby it is planned to include the basic characteristic and the node characteristic in the aggregation level to be created afterwards and also in the query. :KLFK�YDULDQW�RI�WKH�FKDUDFWHULVWLF�UHODWLRQVKLSV�VKRXOG�EH�VHOHFWHG�RQ�WKH�&KDUDFWHULVWLF�5HODWLRQVKLS�WDE�RI�WKH�,QIR3URYLGHU"��

_ Characteristic relationship without derivation

� Characteristic relationship without characteristic derivation

:K\�KDYH�\RX�RSWHG�IRU�WKHVH�YDULDQWV"� Because the node characteristic “ Product line” is present in the aggregation level and the query. &UHDWH�the PXOWLOHYHO�FKDUDFWHULVWLF�UHODWLRQVKLS�between the product and product line in the system accordance with the specifications made above and then VDYH.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-48

1-1-3 You now have to create an aggregation level on the basis of InfoProviders 7%:��+�� . Technical name: +��B$/B�� Description: 7%:��B+��B$/�� Add the following integration objects to the aggregation level: FXUUHQF\��ILVFDO�\HDU�YDULDQW��ILVFDO�\HDU��DPRXQW��YHUVLRQ��SURGXFW�OLQH��SURGXFW�� $FWLYDWH the aggregation level. This aggregation level is later reserved for the query “ …_+LHUDUFK\ �” . It contains the product and product line characteristics. Exit the planning modeler.

1-1-4 Navigate to the 4XHU\�'HVLJQHU��Create a query for the DJJUHJDWLRQ�OHYHO�FUHDWHG�LQ�7DVN��.

Firstly the “ FKDUDFWHULVWLF�PRGHO” , that is the first model variant is to be modeled, this means that the hierarchy is not displayed in the query, however the two characteristics – product line and product – are used in the rows. The “ characteristic relationship” ensures that the correct combination is displayed. Proceed as follows: In the area “ FKDUDFWHULVWLF�UHVWULFWLRQV” include the following: Fiscal year: 9DULDEOH�*URXS��B9$5B)<B��B30�Fiscal year variant: .��3URGXFW�OLQH� -8&��:$7�3URGXFW�� :DWHU��:DWHU��:DWHU�� $SSOH�-XLFH��7RPDWR�-XLFH�� 0DQJR�-XLFH��2UDQJH�-XLFH�Version: & Currency: 86' Please ensure that the characteristics product line and product are included here by selecting them accordingly in order to create a write access to these as described. In the area “&ROXPQV” you can include the key figure “$PRXQW” . Configure the key figure so that it can be LQSXW PDQXDOO\�and also so that LW�FDQ�EH�ILOOHG�E\�H[HFXWLQJ�SODQQLQJ�IXQFWLRQV. In the area “ Rows” add the characteristic “3URGXFW�OLQH” EHIRUH�“3URGXFW” . Set

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-49

“.H\�DQG�7H[W” for both. Select “&KDUDFWHULVWLF�UHODWLRQVKLSV” as “$FFHVV�W\SH�IRU�UHVXOWV�YDOXHV” in the “3URSHUWLHV” in the rows of the characteristics. 6DYH�your query under the following description: Description: 7%:��B+��B$/��B34B+,(5$5&+<B� Technical name: +��B$/B��B3ODQTXHU\B+,(5$5&+<� . Then H[HFXWH�it for the fiscal year ��. You should receive the following display:

Summary: In terms of characteristic relationships, the hierarchy is used in the Planning Modeler to determine the correct business combinations that are displayed in the query, they are not imported physically. Please remember that both characteristics must be included in your selection in the area of characteristic restrictions, as a characteristic relationship without characteristic derivation was selected in the Planning Modeler and therefore also in the aggregation level that is used as a basis for the query.

1-1-5 Ultimately you want to ensure that the characteristic combination is displayed as a kind of “ runtime hierarchy” and therefore make a drill down possible. For this purpose you should not click on one of the two characteristics, instead click in the empty area and thereby navigate to the *HQHUDO tab page in the area “3URSHUWLHV��URZV�DUHD�” and choose “$FWLYH” for “'LVSOD\�DV�KLHUDUFK\“ and “3URGXFW” for the field “([SDQG�XS�WR” . Save the query and then execute it for fiscal year ��. You should receive the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-50

1-2 The VHFRQG�PRGHO�the “%:�+LHUDUFK\” model will be described in the following section. In general, here you have two options with the InfoProvider modeling: - Product is included in the InfoProvider, product line is not. This means that no characteristic relationship is required in the Planning Modeler. The hierarchy comes into play later when the product characteristic is involved. Writing only takes place on the product. - Product and product line in the InfoProvider, this means that a characteristic relationship is required in the Planning Modeler. However, here it takes the form of a characteristic derivation, as only the product is included in the aggregation level and query. Writing only takes place in the product, product line combination due to the characteristic derivation. In both cases only the product is included in the aggregation level and then later the hierarchy is set to this characteristic in the query so that the product line is only indirectly involved.

1-2-1 For this purpose, use the InfoProvider 7%:��+��that you used previously��This contains the two characteristics – product and product line. Create a second FKDUDFWHULVWLF�UHODWLRQVKLS�LQ�WKH�3ODQQLQJ�0RGHOHU that is subject to the same basic conditions as in Tasks 1-1-1 and 1-1-2. This time set “&KDUDFWHULVWLF�5HODWLRQVKLS�ZLWK�&KDUDFWHULVWLF�'HULYDWLRQ” . The product is the source characteristic; the product line is the target characteristic. (You could also reset the characteristic relationship already present to characteristic derivation, as this would have the result that the derivation uses all aggregation levels in which the product line is missing and in such aggregation levels in which it is contained it will read out the combinations).

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-51

1-2-2 In the Planning Modeler for InfoProvider 7%:��+�� create a second DJJUHJDWLRQ�OHYHO�by FRS\LQJ�WKH�ILUVW�DJJUHJDWLRQ�OHYHO. Enter the following descriptions: Technical name: +��B$/B�� Description: 7%:��B+��B$/�� 5HPRYH�the characteristic of the SURGXFW�OLQH and DFWLYDWH�the aggregation level. Exit the planning modeler.

1-2-3 Navigate again to the 4XHU\�'HVLJQHU and create a new query for aggregation level +��B$/B��with the following configuration In the “&KDUDFWHULVWLF�UHVWULFWLRQV” include the following: Fiscal year: 9DULDEOH�*URXS��B9$5B)<B��B30�Fiscal year variant: .��3URGXFW�� :DWHU��:DWHU��:DWHU�� $SSOH�-XLFH��7RPDWR�-XLFH�� 0DQJR�-XLFH��2UDQJH�-XLFH�Version: & Currency: USD In the area “&ROXPQV” you can include the key figure "$PRXQW” . Configure the key figure so that it can be LQSXW PDQXDOO\�and also so that LW�FDQ�EH�ILOOHG�E\�H[HFXWLQJ�SODQQLQJ�IXQFWLRQV. In the area “5RZV” add the characteristic “3URGXFW” . Set “.H\�DQG�7H[W” . Select “&KDUDFWHULVWLF�UHODWLRQVKLSV” as “$FFHVV�W\SH�IRU�UHVXOWV�YDOXHV” in the “3URSHUWLHV” of the rows of the characteristics. In the characteristic remaining for the rows – “3URGXFW” – choose the KLHUDUFK\�with the technical name “+LHUDUFK\BZLWKBWZRBFKDUV” in “3URSHUWLHV” . Set “([SDQGLQJ�XS�WR�OHYHO” to “ �” . Choose “$FWLYDWH�KLHUDUFK\�GLVSOD\” . You can leave other settings for the hierarchy and characteristic unchanged. 6DYH�your query as follows: Description: 7%:��B+��B$/��B34B+,(5$5&+<B� Technical name: +��B$/B��B3ODQTXHU\B+,(5$5&+<� . Execute the query for the fiscal year ��. You should now receive the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-52

As you can see, in the query area there is still a node for the “ Rest” , this means characteristic value #, this display setting can only be suppressed in the hierarchy maintenance. In this case, navigate to the hierarchy maintenance and then in change mode choose *RWR��!�+LHUDUFK\�$WWULEXWHV�and select the setting “6XSSUHVV�³1RW�$VVLJQHG´�1RGH” .

Please note that this setting is practical to improve performance, especially when there are many node levels. This setting should not be made during the exercises. Now exit the Query Designer.

1-2-4 Navigate to the %([�$QDO\]HU, to map the two model variants of the hierarchy together in a workbook. Create a new workbook with the following configuration: Place the cursor in cell $� and type “3ODQQLQJ�ZLWK�KLHUDUFKLHV�DQG�FKDUDFWHULVWLF�UHODWLRQVKLSV” in UHG� font size ��, EROG�type. Afterwards create a VDYH�EXWWRQ for cell $��with the pushbutton text “6DYH” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-53

In cell &� create a rHIUHVK�EXWWRQ with the pushbutton text “5HIUHVK” . Place the cursor in cell $��and type “9DULDQW��” in UHG� font size ��, EROG�type. In cell $�� create an DQDO\VLV�WDEOH relating to the query with the technical name “+��B$/B��B3ODQTXHU\B+,(5$5&+<�” . Select “2SWLPXP�KHLJKW” . Afterwards place the cursor in cell $��and type “9DULDQW��” in UHG� font size ��, EROG�type. In cell $�� create an DQDO\VLV�WDEOH relating to the query with the technical name “+��B$/B��B3ODQTXHU\B+,(5$5&+<�” . Select “2SWLPXP�KHLJKW” . 6DYH�the workbook under the following name: *URXS��B7%:��B+,(5$5&+<. ([HFXWH�the workbook for the fiscal year ��.��You should now receive the following display:��

�

1-2-5 In one of the top analysis tables, plan ��units for the combination (juice, mango juice). Afterwards right-click in this cell and choose “7UDQVIHU�YDOXHV” ; this should have the result that you see a roll-up sum on the parent nodes. You should also be able to see the same reaction in the bottom analysis table. Afterwards enter ��units for the combination (juice, tomato juice) in the bottom analysis table.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-54

Afterwards right-click in this cell and choose “7UDQVIHU�YDOXHV” ; this should have the result that you see a roll-up sum on the parent nodes, this time in both the bottom and top analysis table. You should receive the following result:

Please note that you do not receive a roll-up sum by choosing the “ Refresh” button or by choosing the “ Temporarily Interrupt Automatic Update” button! Now exit the BEx Analyzer without saving the data.

1-3 Now you will set up a scenario for FKDUDFWHULVWLF�GHULYDWLRQ�using the “0DWHULDO” characteristic (technically “0DWB%,” ) and the attribute “0DWHULDO�JURXS” (technically (“0$7B*5283” ). The following correct business characteristic combinations are present in the master data maintenance for the material characteristic:

0DWHULDO Attribute Material group

T1 TWAT

T2 TWAT

T3 TWAT

T4 JUC

T5 JUC

T6 JUC

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-55

1-3-1 Navigate to the 3ODQQLQJ�0RGHOHU and choose the ,QIR3URYLGHU�with the technical name 7%:��'�� For this InfoProvider, set a FKDUDFWHULVWLF�UHODWLRQVKLS�LQ�WKH�IRUP�RI�D�FKDUDFWHULVWLF�GHULYDWLRQ on the &KDUDFWHULVWLF�5HODWLRQVKLS tab page. The characteristic relationship is based on an attribute assignment and the basic characteristic is called “0$7B%,” . The target characteristic is the “0DWHULDO�JURXS” . Navigate to the Administrator Workbench in the master data maintenance of the characteristic “0DWB%,” and check for yourself if the characteristic “0$7B*5283” is used as an attribute for the material characteristic. Examine the characteristic combinations between material and material group. Then exit the Administrator Workbench.

1-3-2 Now create an aggregation level with the following designations: Technical name: '��B$/B�� Description: 7%:��B'��B$/�� . Select the following characteristics and key figures in the aggregation level: YHUVLRQ��ILVFDO�\HDU��ILVFDO�\HDU�YDULDQW��PDWHULDO��FXUUHQF\�NH\��UHYHQXH. $FWLYDWH this aggregation level.

1-3-3 Now FRS\�the DJJUHJDWLRQ�OHYHO�Dnd specify the following designations: Technical name: '��B$/B�� Description: 7%:��B'��B$/�� . 6XSSOHPHQW�the copied aggregation level with the characteristic 0DWHULDO�JURXS�and UHPRYH the characteristic 0DWHULDO�and DFWLYDWH�the aggregation level. Afterwards exit the planning modeler. The aim is to model a bottom-up roll-up in which a summarization of all materials for each material group is shown in the second aggregation level when the characteristic derivation writes the characteristic material group in the first aggregation level.

1-3-4 Now navigate to the 4XHU\�'HVLJQHU and VHDUFK�there for your aggregation level with the technical name '��B$/B��. Configure the query as follows: In the area “&KDUDFWHULVWLF�UHVWULFWLRQV” include the following fields and selections: )LVFDO�\HDU�� 9DULDEOH�*URXS��B9$5B)<B��B30�)LVFDO�\HDU�YDULDQW�� .��9HUVLRQ�� &�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-56

&XUUHQF\�� 86'�0DWHULDO�� 7��WR�7�� In the “5RZV” area include the field “0DWHULDO” and in the “&ROXPQV” area include the key figure “5HYHQXH” . In the “3URSHUWLHV” of key figure “ Revenue” , select “'DWD�FDQ�EH�FKDQJHG�E\�XVHU�LQSXWV�RU�SODQQLQJ�IXQFWLRQV” for planning. In the “3URSHUWLHV” of row characteristic “0DWHULDO” select “.H\�DQG�7H[W” under “'LVSOD\�DV” and “&KDUDFWHULVWLF�5HODWLRQVKLSV” under “$FFHVV�7\SH�IRU�5HVXOW�9DOXHV” . 6DYH�and specify the following descriptions for your query: Description: 7%:��B'��B$/��B'(5,9$7B� Technical name: '��B$/B��B'(5,9$7B� ([HFXWH�your query for fiscal year ��. You should now receive the following display:

As you can see, the system informs you that characteristics combinations have been created.

1-3-5 Now create a second query, this time for the aggregation level with the technical name '��B$/B�� that is to display an aggregation of all materials if the characteristic derivation accesses the first aggregation level. Conduct the following configurations: Include the following fields and selections in the “&KDUDFWHULVWLF�UHVWULFWLRQV” areas: )LVFDO�\HDU�� 9DULDEOH�*URXS��B9$5B)<B��B30�)LVFDO�\HDU�YDULDQW�� .��9HUVLRQ�� &�&XUUHQF\�� 86'�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-57

0DWHULDO�JURXS�� 7:$7��-8& In the “5RZV” area include the field “0DWHULDO�JURXSV” and in the “&ROXPQV” area include the key figure “5HYHQXH” . In the “3URSHUWLHV” of key figure “ Revenue” , select “'DWD�FDQ�EH�FKDQJHG�E\�XVHU�LQSXWV�RU�SODQQLQJ�IXQFWLRQV” for planning. In the “3URSHUWLHV” of row characteristic “0DWHULDO�JURXS” select “.H\�DQG�7H[W” under “'LVSOD\�DV” and “&KDUDFWHULVWLF�5HODWLRQVKLSV” under “$FFHVV�7\SH�IRU�5HVXOW�9DOXHV” . 6DYH�your query as follows: Description: 7%:��B'��B$/��B'(5,9$7B� Technical name: '��B$/B��B'(5,9$7B� ([HFXWH�it for ��. You should receive the following display:

Exit the Query Designer.

1-3-6 Navigate to the BEx Analyzer and create a workbook with the following names: Description: *URXS��B7%:��B'(5,9$7,21� Place the cursor in cell $��and type “&KDUDFWHULVWLF�GHULYDWLRQ” in UHG� font size ��, EROG�type. Place the cursor in cell $� and create a VDYH�EXWWRQ�with the designation “6DYH” in area: �$��$��. 'HVHOHFW�“$GMXVW�DUHD�WR�LWHP�VL]H” . In cell '��create a UHIUHVK�EXWWRQ with the designation “5HIUHVK” in area �'��'��. 'HVHOHFW�“$GMXVW�DUHD�WR�LWHP�VL]H". For cell +� create 0HVVDJHV�in area �+��/�� and VHOHFW�DOO�ILHOGV�on the *HQHUDO tab page.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-58

Type “6\VWHP�0HVVDJHV” in cell H6. 6DYH your workbook�

1-3-7 In cell $��in UHG� font size ��, EROG�type��enter: “3ODQQLQJ�IRU�PDWHULDO�RQ�DJJUHJDWLRQ�OHYHO�ZLWKRXW�PDWHULDO�JURXS�±�PDWHULDO�JURXS�ZLOO�EH�GHULYHG” Place the cursor in cell $�� and create an analysis table relating to the TXHU\�RI�7DVN ��. Select “2SWLPXP�KHLJKW” in the definition of the analysis table. 6DYH your workbook�

1-3-8 In cell $��in UHG� font size ��, EROG�type, enter: “6XPPDWLRQ�RI�DOO�PDWHULDOV�DV�WKH�PDWHULDO�JURXS�LV�GHULYHG” . Place the cursor in cell $��and create an DQDO\VLV�WDEOH�that relates to the TXHU\�RI�WDVN��. Select “2SWLPXP�KHLJKW” in the definition of the analysis table. �6DYH your workbook�

1-3-9 ([HFXWH�the workbook for the fiscal year ��. You should receive the following display – the figure below shows an excerpt –.

Make the following plan in the analysis table:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-59

0DWHULDO Description 5HYHQXH

T1 Table water 1 ��T2 Table water 2 ��T3 Table water 3 ��T4 -XLFH�� T5 -XLFH�� T6 -XLFH��

You should receive the following display:

Place the cursor at the intersection of “ Overall result” and “ Revenue” (this should be cell &��) and select “7UDQVIHU�YDOXHV” to display the WRWDO�RI�86'��. Afterwards examine the second analysis table with the aggregated data. According to the correct business assignment as initially described in Task 1-3, you receive the following aggregation values which result from the characteristic derivation modeled in the background:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-60

1-3-10 6DYH�the plan data, exit the BEx Analyzer and check for yourself in InfoProvider 7%:��'�� that the plan data records are all stored depending on material and material group and therefore reporting of these correct business combinations is possible. The InfoProvider should display the following:��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-61

1-4 In the following task, the planning function “5HDOLJQPHQW�RI�&KDUDFWHULVWLF�5HODWLRQVKLSV” is used to apply changes in the plan data records after a realignment of materials and material groups which occurred after planning. Assume that the assignment of materials T1 to T3 is to be changed from material group table water to water and the values planned with the old, incorrect combination from Task 1-3-9 or 1-3-10 are now to be realigned with the new, correct combination.

1-4-1 Before the task begins, the instructor will conduct the realignment of materials T1 to T3 from material group TWAT to WAT in the master data of characteristic “ MAT_BI” ; this results in the following characteristic relationships:

Please inform your instructor that you have finished Task 1-3 so that he can start the realignment. The instructor will then activate the master data.

1-4-2 Define a new aggregation level for the realignment function by copying aggregation level '��B$/B��and making the following specifications:

Technical name: '��B$/B�� Description: 7%:��B'��B$/��. Add DOO�RI�WKH�LQIRUPDWLRQ�REMHFWV�WR�WKLV�OHYHO. $FWLYDWH this aggregation level.

1-4-3 Define a “5HDOLJQPHQW�RI�&KDUDFWHULVWLF�5HODWLRQVKLSV” planning function for the aggregation level you have just created. Technical name: '��B3)B�� Name: � � � � 7%:��B'��B$/��B3)��B5($/,*1��:KLFK�ILHOG�LV�WR�EH�LQFOXGHG�DV�WKH�ILHOG�WR�EH�FKDQJHG"��Material group [MAT_GROUP]��2WKHU�VHWWLQJV�DUH�QRW�SRVVLEOH��6DYH the planning function.

1-4-4 Create a ILOWHU�for aggregation level '��B$/B��; you will use this filter for the subsequent tracing of the function. Technical name: '��B)B�� Name: 7%:��B'��B$/��B)��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-62

Include all LQIRUPDWLRQ�REMHFWV�in the filter and select the following characteristic values for the characteristic: )LVFDO�\HDU�YDULDQW�� .��9HUVLRQ�� &�8QLW�RI�PHDVXUH�� 0DWHULDO�� 7��WR�7��)LVFDO�\HDU�� 9DULDEOH�*URXS��B9$5B)<B��B30�3RVWLQJ�SHULRG�� 0DWHULDO�JURXS�� 7:$7��:$7�&XUUHQF\�� 86'��Please remember that “3RVWLQJ�SHULRG” and “8QLW�RI�PHDVXUH” were not planned, however they must be included due to the property of the planning function “ Realignment of Characteristic Relationships” of checking the InfoProvider and not the aggregation level. Therefore the characteristic attributes are set to “ #” for “ not assigned” .��6DYH�the filter.

1-4-5 Now create a SODQQLQJ�VHTXHQFH�for aggregation level '��B$/B��for the filter and planning function with the following description: Technical name: '��B6B�� Name: 7%:��B'��B$/��B6��6DYH�the sequence and then WUDFH the planning function for the fiscal year ��. Do QRW�VDYH�the plan data and then exit the Planning Modeler.

1-4-6 Navigate to the 4XHU\�'HVLJQHU and define a query for aggregation level '��B$/B��which you will use later to check if the realignment was successful. In the area “&KDUDFWHULVWLF�UHVWULFWLRQV” add the filter '��B)B��. In the “5RZV” area include the field “0DWHULDO�JURXS” before “0DWHULDO” and in the “&ROXPQV” area include the key figure “5HYHQXH” . In the “3URSHUWLHV” of key figure “5HYHQXH” , select “'DWD�FDQ�EH�FKDQJHG�E\�XVHU�LQSXWV�RU�SODQQLQJ�IXQFWLRQV” for planning. In the “3URSHUWLHV” of row characteristic “0DWHULDO�JURXS” and “0DWHULDO” select “.H\�DQG�7H[W” under “'LVSOD\�DV” and “0DVWHU�'DWD” under “$FFHVV�7\SH�IRU�5HVXOW�9DOXHV” . 6DYH�your query as follows: Description: 7%:��B'��B$/��B5($/,*10(17 Technical name: '��B$/B��B5($/,*10(17

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-63

([HFXWH�it for ��. You should now see the following display:

As you can see, the system has recognized the new, correct business combination! 6DYH�and then exit the Query Designer.

1-4-7 Navigate to the %([�$QDO\]HU and your workbook *URXS��B7%:��B'(5,9$7,21��Place the cursor in cell $��and in UHG� font size ��, EROG�type, enter: “5HDOLJQPHQW�DV�D�UHVXOW�RI�UHDVVLJQPHQW�FDXVHG�E\�EXVLQHVV�FLUFXPVWDQFHV” . Create an DQDO\VLV�WDEOH�in cell $�� that relates to the TXHU\�IURP�7DVN��. Select “ RSWLPXP�KHLJKW” . This query is listed internally as '$7$B3529,'(5B�. Now place the cursor in cell $��and create a Design Item EXWWRQ. Make the following configuration Area: �$��%�� Pushbutton text: )XQFWLRQ��5HDOLJQPHQW�7:$7��!�:$7��Select “$GMXVW�DUHD�WR�LWHP�VL]H” .��In the VWDWLVWLFDO�SDUDPHWHUV�area, select your SODQQLQJ�IXQFWLRQ�IURP�7DVN�� and '$7$B3529,'(5B��that you have included in this task�as “'DWDB3URYLGHUB)LOWHU” . 6DYH�the workbook and then execute it for fiscal year ��. The following display should appear:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-64

Now execute the realignment function. You should receive the following results:

If you click on “6\VWHP�0HVVDJHV” you should receive the following message:

6DYH�your SODQ�GDWD�and check in InfoProvider 7%:��'��, that three credit and debit lines have been written. In the List Viewer you should receive the following data records:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-65

Please remember that the InfoProvider is compressed after the realignment function is executed and the transaction data has been saved. It is compressed with a zero elimination run to ensure that records with a zero balance are deleted from the database. This should not be conducted in this exercise.

1-5 Afterwards the QDYLJDWLRQ�DWWULEXWHV�IRU�SODQQLQJ�VHOHFWLRQ are to be enabled. Here, you are again working with the basic characteristic “3URGXFW” (technical name “352'8&7” ) and the navigation characteristic “3URGXFW�OLQH” (technical name “352'8&7/,1” ). The “ Product” characteristic has been included in InfoProvider 7%:��1�� that has been created for you, “ Product line” is not present! Please remember that the navigation attribute must be activated in the InfoProvider.

1-5-1 Navigate to the 3ODQQLQJ�0RGHOHU and take a look at the ,QIR3URYLGHU tab page for InfoProvider 7%:��1�� In the bottom area of this tab page you will find the ,QIR2EMHFWV tab page. On this tab you can find the 1DYLJDWLRQ�$WWULEXWHV section. You should be able to see the navigation characteristic “ PRODUCTLN” and its basic characteristic. Create an aggregation level for this with the following description:

Technical name: 1��B$/B�� Description: 7%:��B1��B$/�� Include DOO FKDUDFWHULVWLFV�in the aggregation level and activate them. As you can see, the navigation characteristic is not addressable in the aggregation level as there is no write access for it. Afterwards exit the planning modeler.

1-5-2 Navigate to the 4XHU\�'HVLJQHU and create a query for your aggregation level 1��B$/B��. When it is used later in the BEx Analyzer, the query should display all products which you have selected with the navigation attribute for the corresponding product line. Make the following configuration: Include the following as stated below in the area “&KDUDFWHULVWLF�5HVWULFWLRQV” : Fiscal year: 9DULDEOH�*URXS��B9$5B)<B��B30�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-66

Fiscal year variant: .� Product: � � � � 7��WR�7��1$9B3URGXFWOLQH�� :$7��-8&�Version: & Currency: USD In the area “&ROXPQV” you can include the key figure “$PRXQW” . Configure the key figure so that it can be LQSXW�PDQXDOO\ and also so LW�FDQ�EH�ILOOHG�E\�H[HFXWLQJ�SODQQLQJ�IXQFWLRQV. Include the characteristic “3URGXFW” and the navigation attribute “1$9B3URGXFWOLQH” in the URZV; NAV_Productline should be added EHIRUH Product. Select “.H\�DQG�7H[W” and “0DVWHU�'DWD” in the properties of the characteristic “3URGXFW“ . Select “.H\” and “0DVWHU�'DWD” for navigation attribute “1$9B3URGXFWOLQH” . 6DYH�your TXHU\ as follows: Description: 7%:��B1��B$/��B1$9 Technical name: 1��B$/��B1$9 Execute the query for the fiscal year ��. You should receive the following display:

As you can see, plan data has already been entered. Now exit the Query Designer.

1-5-3 Navigate to the %([�$QDO\]HU and create a new workbook. Place the cursor in cell $��and in UHG� font size ��, EROG�type, enter: “8VH�RI�QDYLJDWLRQ�DWWULEXWHV�LQ�SODQQLQJ” . Place the cursor in cell $� and create a VDYH�EXWWRQ with the designation “6DYH” . In cell &� create a rHIUHVK�EXWWRQ with the designation “5HIUHVK” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-67

In cell $�� add an DQDO\VLV�WDEOH that references the TXHU\�LQ�7DVN��. Select “2SWLPXP�KHLJKW” . This analysis table is listed internally as DATA_PROVIDER_1. 6DYH�the workbook under the following name: *URXS��B7%:��B1$9,*$7,21. Then execute�it for the fiscal year ��. You obtain the following display:

1-5-4 In cell $�� create the design item GURSGRZQ�ER[. On the ILUVW�WDE�SDJH�select DATA_PROVIDER_1 and the field “'LVSOD\�GHVFULSWLRQ” and GHVHOHFW�the fields “$GMXVW�DUHD�WR�LWHP�VL]H” and “ ,QSXW�0RGH” . On the VHFRQG�WDE�SDJH�select “1$9B3URGXFWOLQH” as “'LPHQVLRQ” (the navigation attribute) and select “3RVWHG�9DOXHV” as the “5HDG�0RGH” . Select “6WDQGDUG�7H[W” and “.H\�DQG�7H[W” . On the WKLUG�WDE�SDJH�select DATA_PROVIDER_1. 6DYH�again and execute the workbook for ��. You should now receive the following display:

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-68

Select product line “ -8&” , and choose the pushbutton “5HIUHVK” . The following display will appear:

Change the plan data as follows:

Product Old Value

1HZ�9DOXH

T4 40 ��T5 50 ��T6 60 ��

Then switch to product line “:$7” and choose the pushbutton “5HIUHVK” and make the following plan:

Product Old Value

1HZ�9DOXH

T1 10 ��T2 20 ��T3 30 ��

6DYH�your SODQ�GDWD and navigate to the /LVW�9LHZHU of InfoProviders 7%:��1��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-69

�Display the transaction data here. The following data should be displayed:

�As you can see, the product line is RQO\ read in the List Viewer at runtime (column NAV_ProductLine is colored blue) because the product line was not additionally included as a characteristic in the InfoProvider:

As the field “ Product line” was not included in the InfoProvider, the navigation attribute could RQO\ be read “ on the fly” to enable the selection of the products.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 11-70

1-6 Afterwards place a data slice on the plan data so that nobody can replan the blocked segments either manually or automatically. Navigate to the 3ODQQLQJ�0RGHOHU and from there to InfoProvider 7%:��1��Create a data slice that blocks materials 7��7��and�7�. Then VDYH your InfoProvider. Navigate again to your workbook *URXS��B7%:��B1$9,*$7,21�and�examine the analysis table� The segments that relate to product line WAT should be blocked against manual and automatic planning whereas the planning should still be possible for products of product line JUC: The following data is displayed:

��Now exit the BEx Analyzer and return to the screen that appears after logging onto the system.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-1

SAP AG 2006

&RQWHQW�� &UHDWLQJ�D�3ODQQLQJ�$SSOLFDWLRQ�8VLQJ�:$'�

&UHDWLQJ�DQG�8VLQJ�D�:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-2

SAP AG 2006

&UHDWLQJ�DQG�8VLQJ�D�:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'��7RSLF�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�D�:HE�DSSOLFDWLRQ�IRU�SODQQLQJ�LV�

VHW�XS��DQG�NQRZ�WKH�UHOHYDQW�VHWWLQJV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-3

SAP AG 2006

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�:$'��<RX�DUH�SDUWLFXODUO\�LQWHUHVWHG�LQ�WKH�LQFOXVLRQ�RI�WKH�SODQQLQJ�

&UHDWLQJ�DQG�8VLQJ�D�:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'��%XVLQHVV�6FHQDULR

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-4

SAP AG 2006

&UHDWLQJ�DQG�8VLQJ�D�:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'��2YHUYLHZ�'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-5

SAP AG 2006

&UHDWLQJ�DQG�8VLQJ�D�:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'��8QLW�2YHUYLHZ�'LDJUDP

8QLW�WLWOH� /HVVRQ��&UHDWLQJ�D�3ODQQLQJ�$SSOLFDWLRQ�8VLQJ�:$'��

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-6

SAP AG 2006

&UHDWLQJ�D�3ODQQLQJ�$SSOLFDWLRQ�8VLQJ�:$'��7RSLF�2EMHFWLYHV

$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�8QGHUVWDQG�KRZ�WR�VHW�XS�D�:HE�DSSOLFDWLRQ�IRU�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-7

SAP AG 2006

&UHDWLQJ�D�3ODQQLQJ�$SSOLFDWLRQ�8VLQJ�:$'��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�DQG�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�:$'�DQG�ZLWK�WKH�,QFRUSRUDWLRQ�RI�3ODQQLQJ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-8

SAP AG 2006

2SWLRQV�IRU�8VLQJ�WKH�%([ :HE

�

� BEx Web includes all the BEx tools used to create Web-based application, or which themselves

represent Web applications.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-9

SAP AG 2006

:HE�$SSOLFDWLRQ�'HVLJQ��%([ :HE�$SSOLFDWLRQ�'HVLJQHU

3UHYLHZ

3URSHUWLHV

:HE�,WHPV

�

� The BEx Web Application Designer can be used to create Web applications for HTML pages displaying

BI-specific content, such as tables, graphics and cards. This data refers to DataProviders that are included in what are known as Web Items. The finished application is known as a Web application.

� Web applications are based on a :HE�7HPSODWH that is created and maintained in the :$', the :HE�$SSOLFDWLRQ�'HVLJQHU.

� Web templates can be saved and used in a Web browser or portal. Once it has been executed, it is no

longer known as a Web template, but as a :HE�DSSOLFDWLRQ.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-10

SAP AG 2006

2YHUYLHZ�RI�WKH�:HE�,WHPV

:HE�WHPSODWH&RQWDLQHU�OD\RXW&RQWDLQHU5HJLVWHU�WDEV*URXS6LQJOH�GRFXPHQW/LVW�RI�GRFXPHQWV&DUG6\VWHP�PHVVDJHV,QIR�ILHOG

(QKDQFHG :HE�,WHPV'DWD3URYLGHU LQIRUPDWLRQ7H[W/LQN/LVW�RI�H[FHSWLRQV/LVW�RI�FRQGLWLRQV0HQX�EDU3URSHUWLHV�DUHD7LFNHU&RQWH[W�PHQX6FULSW

2WKHU :HE�,WHPV$QDO\VLV&KDUW5HSRUW1DYLJDWLRQ�DUHD)LOWHU�DUHD%XWWRQ�JURXS'URSGRZQ ER[5DGLR�EXWWRQ JURXS&KHFNER[�JURXS/LVW�ER[+LHUDUFKLFDO ILOWHU VHOHFWLRQ

6WDQGDUG�:HE�,WHPV

�

� :HE�,WHPV are objects that either visualize data in a Web application or are generally used to design

Web applications. At runtime, these objects are replaced by generated HTML. �

Web Items that visualize data must be connected to a DataProvider. �

All Web Items have parameters such as header, width, and height, which are used to specify the appearance of the Web Items and their behavior in the Web application. You can change the parameters as follows:

• During the design phase, in the Web Application Designer, by means of the parameter settings

• At runtime in Web application by means of the Properties dialogs of the Web Items, or using commands from the Web Design API

• If the data, the navigation status or the parameters change, the HTML is regenerated for the Web Item

� In the %([�:HE�$SSOLFDWLRQ�'HVLJQHU, in the :HE�,WHPV window, the Web Items represented in the

graphic are available to you as 0DVWHU�:HE�,WHPV. You select a Master Web Item from this list, assign a DataProvider to the Web Item if applicable, and set the parameters. By doing this, you create an individual Web item that you can insert into your Web template or save for reuse.

� The following slides show the PRVW�LPSRUWDQW�:HE�,WHPV�IURP�D�SODQQLQJ�YLHZSRLQW�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-11

SAP AG 2006

([DPSOH�RI�D�7\SLFDO�:HE�$SSOLFDWLRQ�IRU�3ODQQLQJ

�

� The above example shows a typical Web application from a planning viewpoint, with the most

important Web Items, which are later described in more detail with regard to planning. �

Please note that you can use WAD only to set up HTML interfaces, but you cannot include Excel HTML!

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-12

SAP AG 2006

&UHDWLQJ�D�'DWD3URYLGHU

'RXEOH�FOLFN

�

� When you want to set up a Web application, you first have to create a new Web template. The template

contains placeholders, the DataProvider that references the BI data, and commands. The placeholders are filled during runtime, and the Web Items, the DataProviders, and the commands are generated.

� Then a DataProvider of the type 4XHU\�9LHZ�'DWD�3URYLGHU�must be created.

� 'DWD3URYLGHUV are objects that deliver data at runtime for one or more Web Items. A distinction is

made between two types of DataProvider:

• 4XHU\�9LHZ - Delivers data for Web Items that visualize the result of a query or a query view, such as the

Web Items $QDO\VLV�DQG�&KDUW. - Is a DataProvider for Web Items that relate to the filtering of data (such as the Web Items

&KHFNER[�*URXS and 5DGLR�%XWWRQ�*URXS). - The initial status of a DataProvider of this type is defined by entering an InfoProvider, a query,

or a query view. • )LOWHU

- Usually delivers data for Web Items relating to the filtering of data, such as the Web Items 'URSGRZQ�%R[ and 5DGLR�%XWWRQ�*URXS, as well as the Web Item�%XWWRQ�IRU�GLVSOD\LQJ�D�SODQQLQJ�IXQFWLRQ.

- Because this type does not return the results of queries or query views, they cannot be used as DataProviders for Web Items such as Analysis, Chart, Report. The initial status of a DataProvider of this type is usually defined by entering a filter.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-13

SAP AG 2006

,QFOXGLQJ�WKH�:HE�,WHP�$QDO\VLV�LQ�WKH�:HE�7HPSODWH�

'UDJ��'URS

3URSHUWLHV�IRU�YLVXDOL]LQJ�D:HE�,WHP

�

� You can use Drag&Drop to include Web Items in the layout area of the WAD (Web Application

Designer) and position them there. �

The above illustration shows this by using the Web Item $QDO\VH�,WHP. �

You can see the structure of the WAD and also that all Web Items have a “Properties” area, where settings are entered for visualizing the Web Items.

� The properties that are most important from a planning point of view are briefly described here.

� 1XPEHU�RI�QHZ�URZV� With this parameter you can add any number of empty table rows. The default

value for the parameter is 0. Depending on the query settings, this parameter can be used to add columns instead of rows.

� 3RVLWLRQ�RI�WKH�QHZ�URZV� You can use this parameter to specify the position at which empty table rows

are added. The value range is %RWWRP�and 7RS��If the query settings are such that the parameter 1XPEHU�RI�QHZ�URZV adds columns instead of rows, then the value range is /HIW and 5LJKW instead of the values named above.

� 'DWD�3URYLGHU� With this parameter you assign a Data Provider to the Web Item. From the Data

Provider, the Web Item pulls data and meta data that is required to create the output and the commands.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-14

SAP AG 2006

:HE�,WHP�1DYLJDWLRQ�$UHD

�

� The 1DYLJDWLRQ�$UHD Web Item shows the navigation status of a Data Provider. All the characteristics

and structures of the data provider are listed there. �

You can change the navigation status by dragging & dropping characteristics or structures to an axis (rows or columns) of the table, or take them from the axes.

� You can use drag & drop to swap the axes in the navigation area, and the table changes accordingly.

� You can also use drag & drop to pull characteristics into the filter area.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-15

SAP AG 2006

:HE�,WHP�)LOWHU�$UHD

�

� You can use the Web Item )LOWHU�$UHD to set filters for single characteristics.

� The characteristic values are provided for selection for each characteristic in dropdown boxes.

� You can also use drag & drop to pull characteristics from the navigation area or the table to the filter

area.�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-16

SAP AG 2006

:HE�,WHP�'URSGRZQ�%R[��

- )LOWHUV�RI�FKDUDFWHULVWLF�YDOXHV- 3ODQQLQJ�IXQFWLRQV- 4XHU\�RU�FKDUW- 9DULDEOH�YDOXHV

6HOHFWLRQ�IURP�

�

� The Web Item�'URSGRZQ�%R[��can be used in accordance with the above illustration to filter

characteristic values, select planning functions, and include queries and graphics. In contrast to the BEx Analyzer, here variables can be assigned directly to a dropdown box.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-17

SAP AG 2006

:HE�,WHP�'URSGRZQ�%R[��

�

� The above illustration shows the most important settings for planning for this Web Item.

� 5HDG�0RGH� With this parameter you specify which values from the master data table are transferred as

filter values to the Web Item dropdown box.

• �0��$OO�YDOXHV�IURP�WKH�PDVWHU�GDWD�WDEOH� Some values may also be displayed that do not occur in the DataProvider under the current filter conditions, and which return the result “No relevant data found” after filtering. However, under certain conditions, this procedure is the fastest one.

• �'�� Generally posted values, although the current breakdown status is not completely considered.

• �4�� Only those values are displayed that are posted in the DataProvider within the framework of the currently valid filter conditions. Under certain conditions, this can take a long time.

� The read mode by “master data” can also result in displaying many unposted values. The read mode by

“posted values” can be slow! �

([HFXWLRQ�WLPH� With this parameter you specify the time when the changed command is executed.

• %HIRUH� If you select this option, the additional command is executed EHIRUH filtering.

• $IWHU� If you select this option, the additional command is executed DIWHU filtering.

• ,QVWHDG� If you select this option, the additional command is executed LQVWHDG�RI filtering. �

'DWD�ELQGLQJ�W\SH� You specify the content of the entries in the dropdown box. The variants were already mentioned on the previous slide, and they can also be obtained from the above illustration.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-18

SAP AG 2006

:HE�,WHP�%XWWRQ��

�

� You can use the Web Item %XWWRQ�*URXS to include planning functions in the WAD with regard to the

planning. �

In the properties area of this Web Item, you will see the “ Button list” area. After you create the different planning functions, they will appear as a list below this area.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-19

SAP AG 2006


1DPH�RI�WKH�EXWWRQ�RI�WKH�IXQFWLRQ

*R�WR�³&RPPDQG�:L]DUG´

�

� If you want to create a planning function from the list, you must click on the F4 help of the Button field

in the list. �

Then you click on the F4 button of the field ³$FWLRQ��FRPPDQG�WULJJHUHG�´ and select the variant ³&RPPDQG�YLD�&RPPDQG�:L]DUG��LQVWUXFWLRQ�´.

� Next, you click on the F4 button of the field ³&RPPDQG´, thus calling the &RPPDQG�:L]DUG.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-20

SAP AG 2006


��

�

� The above illustration shows the possible commands that can be used in combination with planning

applications. �

As you see, you can create buttons for updating, saving and resetting plan data, as well as for planning functions and sequences.

� It is also possible for the end user to change from the display mode to the change mode by means of a

button. This could be useful, for example, if the supervisor first wants to just look at the plan data, and only switches to the change mode if he wants to change the data. This switch also involves the locking and unlocking of the selections.

� If you have selected corresponding commands, then you will see them as defaults on the Favorite

Commands tab page. From there you can double-click to assign the desired planning function to the desired planning function button.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-21

SAP AG 2006


�

� You select the command ³([HFXWH�SODQQLQJ�IXQFWLRQ��VLPSOH�´ from the list of favorite commands

with a double-click if you want to include the planning function. In the subsequent screen, you then select the desired planning function with the related data connection.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-22

SAP AG 2006


�

� The above illustration shows an example of the procedure for creating the Save button. The Refresh and

Reset Data buttons are set up in the same way. �

Please note that the command 5HVHW�FKDQJHG�GDWD resets changes to data within a Web application. This resetting always refers to all data QRW�VDYHG which was FKDQJHG�E\�PDQXDO�LQSXWV�RU�E\�SODQQLQJ�IXQFWLRQV�RU�SODQQLQJ�VHTXHQFHV. Changes which you have saved by means of 6DYH�FKDQJHV�WR�GDWD FDQQRW be reset.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-23

SAP AG 2006

6LPSOH�3ODQQLQJ�)XQFWLRQ�

'DWD3URYLGHU �ILOWHU�*RRGV�JURXS��SHULRG�GLYLVLRQ

$JJUHJDWLRQ�OHYHO�RI�WKH�IXQFWLRQ*RRGV�JURXS��SURGXFW��ILVFDO�\HDU��SHULRG

�� !#"��$ %�"�$ �'&(�� *),+-%."�� !#"��$ %�"�$ �'&/0$ !#%�102435 #1*��6"7+5!# #)89$ :*$ !0$ �'&

/-��0;<8=15"�1*(7��6:'$ )0 -�(, -�>$ �-)/-��0;<8=15"�1*(7��6:'$ )0 -�?@1�"� *�>$ 1*2.A'��B+0C 6HOHFWLRQV&KDUDFWHULVWLFV

�

� Within the Web Items button, there is a list of commands which also includes ³([HFXWH�SODQQLQJ�IXQFWLRQ��VLPSOH�´ and ³([HFXWH�SODQQLQJ�VHTXHQFH��VLPSOH�´.

� For planning functions and sequences there is also the option - not included as a command in the list - to

select the variant “ Execute ...” . �

The above illustration and the following one show the conceptual difference between the two approaches.

� In the case of a simple planning function, you select a DataProvider of the “ filter” type. The planning

function is executed for this selection. However, the planning function itself can be based on a different aggregation level to the filter selection. In this case, the function being executed pulls the intersection of the characteristics of the aggregation level and the level of the filter of the planning function. The characteristics that are only in the aggregation level of the function are selected without restrictions, and the characteristics that are only contained in the filter, such as the division, are not used.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-24

SAP AG 2006

3ODQQLQJ�)XQFWLRQ�

5HSRVW�IXQFWLRQ

)LVFDO�\HDU

*RRGV�JURXS�7:$7*RRGV�JURXS�-8&

9

)LOWHU�RI�WKH�3ODQQLQJ�0RGHOHU

6HOHFWLRQ�YDULDEOH�RI�WKH�ILOWHU�WR�YHUVLRQ

D�E F G�H�I J5K H�L

M>N�O PRQ SRTU'V VRW

X-Y�Z V�[\

]5^�_ ` a b _�ca d _

d c `b _ e�f ` e c f

�

� For the commands ³([HFXWH�3ODQQLQJ�)XQFWLRQ´ and ³([HFXWH�3ODQQLQJ�6HTXHQFH´, it must be

defined for every characteristic where the characteristic is to be selected from. The above illustration shows an example of the different replacement paths of the characteristics.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-25

SAP AG 2006

5XQWLPH�,QIRUPDWLRQ�RQ�WKH�3HUIRUPDQFH

$GG�3URILOLQJ [�WR�WKH�85/

�

� When the Web application has been executed, the DGPLQLVWUDWRU can add the following identifier to the

end of the URL: (?)Profiling=x. �

This causes a permanent runtime statistic to appear which states how long the individual calls are taking. �

This identifier is used to set a link to “ Show statistics” . �

The BI-integrated planning is included in the technical content of the BW, and corresponding data can be called up with transaction RSTDSTAT.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-26

SAP AG 2006

&UHDWLQJ�D�3ODQQLQJ�$SSOLFDWLRQ�8VLQJ�:$'��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�8QGHUVWDQG KRZ�WR�VHW�XS�D�:HE�DSSOLFDWLRQ�IRU�SODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-27

SAP AG 2006

&UHDWLQJ�DQG�8VLQJ�D�:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�8QGHUVWDQG�KRZ�D�:HE�DSSOLFDWLRQ�IRU�SODQQLQJ�LV�VHW�XS��DQG�NQRZ�WKH�UHOHYDQW�VHWWLQJV

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-28

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-29

�([HUFLVHV�

8QLW�� &UHDWLQJ�DQG�8VLQJ�D�:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'�

�


• Create a web-based planning application.

• Use the most important web items as part of a planning scenario.

The planning structures of the Sales Manager are then to be included in a web-based planning application.

1-1 Navigate to the :HE�$SSOLFDWLRQ�'HVLJQHU. To access the Web Application Designer you click the ³6WDUW´ button within Citrix and then navigate as follows: 6WDUW��!�3URJUDPV��!�%XVLQHVV�([SORUHU��!�:HE�$SSOLFDWLRQ�'HVLJQHU. Choose the button “1HZ” and save the web template under the following designations: Description: *URXS��B7%:��B:$'B6$/0$1 Technical name: *URXS��B7%:��B:$'B6$/0$1. The aim is to map the results layout of the quantity planning and the price planning of the Sales Managers using WAD.

1-1-1 Double-click on “1HZ�'DWD�3URYLGHU” . In the subsequent screen 1HZ�'DWD�3URYLGHU select the type “'DWD�3URYLGHU�RI�7\SH�4XHU\�9LHZ” in the *HQHUDO�area and in the area 'HILQH�'DWD�3URYLGHU�7\SH�select the query created in the Query Designer for quantity planning with the designation “7%:��B6��B$/��B34��B6$/0$1” . This Data Provider is executed internally as '3B�. Create a second Data Provider with the same settings and which relates to the price planning query with the designation “7%:��B3��B$/��B34��B6$/0$1” . This Data Provider is executed internally as '3B�. Finally create a third Data Provider that relates to the ILOWHU 3��B)B��creating in

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-30

the Planning Modeler during price planning. In the screen “1HZ�'DWD�3URYLGHU” in the area “'DWD�3URYLGHU�3URSHUWLHV” , select “)LOWHU�>6HOHFWLRQB2EMHFW@” in the field “ ,QLWLDOL]H�:LWK” . For the field “)LOWHU” in FDSLWDO�OHWWHUV HQWHU�the WHFKQLFDO�QDPH�RI�WKH�ILOWHU�instead of “ Default” . This Data Provider is executed internally as '3B�. 6DYH�your web-based planning application. In the following exercise, your aim is to place quantity and price planning on various tab pages and provide planning functions such as saving, refreshing and resetting centrally for all tab pages. Only the specific planning functions of the quantity or price planning will later be provided on the corresponding tab pages.

1-1-2 In the “/D\RXW” area, enter “4XDQWLW\�DQG�3ULFH�3ODQQLQJ�RI�WKH�6DOHV�0DQDJHU” . Select font “$ULDO” , font size “ �” and “ UHG” �as the color. 6DYH�your web application. In order to ensure better integration of the web item, insert a table for the three functions that are relevant for all tab pages using the button “ ,QVHUW�7DEOH” . The table should be place directly beneath the heading “4XDQWLW\�DQG�3ULFH�3ODQQLQJ�RI�WKH�6DOHV�0DQDJHU” and consist of RQH�URZ�ZLWK�WKUHH�FROXPQV. For the field “:LGWK” select �� to keep the distance between the three buttons as small as possible. 6DYH�your web-based planning application.

1-1-3 Afterwards ensure that before creating the three buttons that you are actually in the cell of the table intended for this purpose. Place the cursor in the ILUVW�FHOO�RQ�WKH�OHIW�of the WDEOH you have created. The save button is to be installed here.� For this purpose, drag and drop the web item “%XWWRQ�*URXS” �into the cell named above and configure the web item parameters as follows:: :LWK�7UD\�� 6HOHFW�³2))´. Now click on the box at the right side of the field “ �%XWWRQ” . In the following screen “ Edit Parameter” select the following: &DSWLRQ�� 6DYH�3ODQ�'DWD�$FWLRQ��&RPPDQG�7ULJJHUHG�� &RPPDQG�YLD�&RPPDQG�:L]DUG�� ,QVWUXFWLRQ��Now click on the ER[�at the ULJKW�VLGH�RI�WKH�ILHOG�“&RPPDQG” and in the

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-31

subsequent “ Edit Command” screen, make the following selections:

After making your selection FOLFN�RQ�WKH�WH[W�“ Save Changed Data (SAVE_DATA)“ ,so that the button “ Next” is activated. Click the button “2.” twice to return to the initial screen of the properties. You should receive the following properties display:

Save your web-based planning application. Now place the cursor in the FHQWHU�FHOO�of the WDEOH�you created in Task 1-1-2. The Refresh button is to be installed here.��Proceed as described for the save button and select “ Refresh Data “ >5()5(6+B'$7$@” . Save your web-based planning application. Afterwards place the cursor in the cell on the right side of the table you created and install the reset button which is given the caption “5HVHW�3ODQ�'DWD” �and for which you enter “5HVHW�3ODQ�'DWD�>5(6(7B'$7$@” .� 6DYH�your web-based planning application.

1-1-4 The three web items you have created currently have the standard technical designation “ Button_Group_ITEM_1 to Button_Group_Item_3“ . These designations should now be changed to ensure better clarity. To do this, click on the first button group for the save button and then click “5HQDPH�:HE�,WHP” in the “3URSHUWLHV” area. In the following screen write 6DYH�in the field “1HZ�1DPH” . Proceed in the same way for refresh and reset and assign the names “5HIUHVK” and “5HVHW” . 6DYH�and H[HFXWH�your web application.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-32

1-2 Now you need to implement two tab pages. The first one is for quantity planning and the second for price planning. Drag and drop the web item “7DE�3DJHV” into the DUHD�EHQHDWK�WKH�WDEOH�to create the two tab pages. Change the internal technical designation of this web item to “7DE�3DJHV” .

1-2-1 Drag and drop the standard web item “$QDO\VLV” into the area of the tab pages. Change the internal technical designation of this web item to “4XDQWLW\3ODQQLQJ4XHU\” . Make the following selections in the Properties of these web items: Number of Lines: � Position of new Lines: %RWWRP Data Provider: '3B� . Do not make any changes to the other properties and VDYH�your web-based planning application. Now drag and drop a “&RQWDLQHU” web item into the area of the tab pages web items XQGHUQHDWK the existing “ Analysis” web item. Navigate to the properties of web item with the name “7DE�3DJHV” and create two tab pages. The web item “ Analysis” should be placed on the first tab page and the container on the second. For the first tab page, open the ER[�DW�WKH�ULJKW�HGJH�of the “ �7DE�3DQHO” . In the following screen enter “4XDQWLW\�3ODQQLQJ” for the field “&DSWLRQ” and for the field “6XERUGLQDWH�:HE�,WHP” select the container with the technical designation “4XHU\IRU4XDQWLW\3ODQQLQJ” . In this way you have created the first tab page, named it and assigned the web item “ Analysis” . In the area “3URSHUWLHV” for the web item with the designation “7DE�3DJHV” , open the ER[�RQ�WKH�ULJKW�HGJH�of the field “ �7DE�3DQHO” again. In the following screen enter “3ULFH�3ODQQLQJ” for the field “&DSWLRQ” and for the field “6XERUGLQDWH�:HE�,WHP” select the container with the technical designation “&217$,1(5B,7(0B�” . In this way you have created the second tab page, named it and assigned a container to it. The container is required because in addition to a query on the second tab page you also wish to include planning functions and variables and a dropdown box and it is only possible to assign just one object to a tab page. By assigning a container, it is possible to collect other objects that are thereby indirectly assigned to the tab page.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-33

1-2-2 Place the cursor in the container of the tab page “3ULFH�3ODQQLQJ” and drag and drop the standard web item “$QDO\VLV” into the container. Change the internal technical designation of this web item to “4XHU\IRU3ULFH3ODQQLQJ” . Make the following selections in the Properties of these web items: Number of Lines: � Position of new lines: %RWWRP Data Provider: '3B� . Do not make any changes to the other properties and VDYH�your web-based planning application. Execute the web-based application.��6DYH�your web-based planning application again and H[HFXWH it.

1-3 In the following steps restrict your work to the tab page "Price Planning" and the container included upon it. In this container, integrate an additional table by choosing the button “ ,QVHUW�7DEOH” . The table is to have RQH�URZ�and VL[�FROXPQV; enter ��for the field “:LGWK” . The table should be placed DERYH�the web item “ Analysis” that you created in Task 1-2-2. In the ILUVW�FHOO�RQ�WKH�OHIW�VLGH�RI�WKH�WDEOH, a dropdown box is to be installed that allows the selection of FRS\�DQG�GHOHWH�IXQFWLRQV. Both functions have no variables. To do this drag and drop the web item “'URSGRZQ�%R[” into the cell of the table named above. In this dropdown-box WKH�WZR�SODQQLQJ�IXQFWLRQV�QDPHG�DERYH�are to be integrated, each relates to the ILOWHU, that you included in Task 1-1-1- as the data provider, or more exactly as '3B�. Change the technical designation of the dropdown box to “'URSGRZQ%R[B�3ODQQLQJ)XQFWLRQV” . Navigate to the properties of the dropdown box and select the data binding type “)L[HG�/LVW�RI�2SWLRQV” . For the field “ �)L[HG�2SWLRQV” click on the ER[�on the ULJKW�VLGH�to access the screen “(GLW�3DUDPHWHU” . For the field “'HVFULSWLRQ�RI�6HOHFWLRQ” enter ”&RS\�9HUVLRQ�%��!%�” . For the field “$FWLRQ��&RPPDQG�7ULJJHUHG�” select “&RPPDQG�YLD�&RPPDQG�:L]DUG��,QVWUXFWLRQ�” . �For the field “&RPPDQG” click on the ER[�on the ULJKW�VLGH�to access the screen “(GLW�&RPPDQG” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-34

Here you navigate to the tab page $OO�&RPPDQGV�and select the execution of the planning functions in accordance with the following display:

Then FOLFN�on “([HFXWH�3ODQQLQJ�6HTXHQFH��6LPSOH�” , to then choose the button “1H[W” . In the next screen you select “'3B�” for the field “5HIHUHQFH�WR�'DWD�3URYLGHU�RI�7\SH�)LOWHU” and for the field “3ODQQLQJ�)XQFWLRQ” select “3��B3)B��” (the copying function of version B1->B2) using the search help which you can access at the right side of this field. Confirm with “2.” twice. You must now repeat this procedure for another “)L[HG�2SWLRQ” for the second planning function by again FOLFNLQJ�RQ�WKH�ER[�RQ�WKH�ULJKW�VLGH�of the field “ �)L[HG�2SWLRQ” to access the screen “(GLW�3DUDPHWHU” . For the field “'HVFULSWLRQ�RI�6HOHFWLRQ” enter “'HOHWH�'DWD�LQ�9HUVLRQ�%�” . Link filter '3B� with function 3��B3)B��, which provides the deleting function within Version B2. 6DYH�your web-based planning application again and then H[HFXWH it. Please observe that the execution of the selected function is automatic (HYHQW�FRQWUROOHG), further functions in addition to the dropdown box are not necessary. When you open the tab page for price planning, the copy function should be executed automatically. Therefore VHOHFW�the GHOHWH�IXQFWLRQ. As you can see, this is executed automatically and the data of Version B2 are reset.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-35

1-4 Now you need to integrate the UHYDOXDWLRQ�IXQFWLRQ�for the data within Version %��with your WZR�YDULDEOHV for 7:$7�and -8&. As the variables set up in the planning function of the Planning Modeler only enter the web-based planning application as import parameters, the web item “ ,QSXW�)LHOG” must be created twice as there are two variables.

1-4-1 Drag and drop the web item “ ,QSXW�)LHOG” in the VHFRQG�FHOO�IURP�WKH�ULJKW�RI�WKH�WDEOH. �The web item is later used to transfer the TWAT parameter values. Change the internal technical designation of the input field to “ ,1387B),(/'B,7(0B9$5B7:$7” . Maintain the properties of the “ ,QSXW�)LHOG” as follows: 9LVLELOLW\�� +LGGHQ��+,''(1��:LWK�7UD\�� 6HOHFW��³2))´�/DEHO��9LVLEOH�� 6HOHFW�³2Q´�/DEHO�� 9DULDEOH�7:$7�9DOXH�+HOS�%XWWRQ�LV�9LVLEOH�� 6HOHFW�³21´��Leave all other settings unchanged.� Now create a second “ ,QSXW�)LHOG” in the ILUVW�FHOO�IURP�WKH�ULJKW�RI�WKH�WDEOH. The web item is later used to transfer the JUC parameter values. Change the internal technical designation of the input field to “ ,1387B),(/'B,7(0B9$5B-8&” . Make the same settings as for the previous input field. The only difference is the field “/DEHO” where you enter “9DULDEOH�-8&“ . 6DYH�your web-based planning application.

1-4-2 Now you need to integrate the web item “%XWWRQ�*URXS” in WKH�VHFRQG�FHOO�IURP�WKH�OHIW�RI�WKH�WDEOH. Change the internal technical description of the button group to “5(9$/8$7,21B)81&7,21” . In the 3URSHUWLHV�of this web item, make the following configurations: For the field “ �%XWWRQ” ,�click on the�“ER[” on the right side to open the screen “(GLW�3DUDPHWHU” . For the field “&DSWLRQ” enter “5HYDOXDWLRQ�)XQFWLRQ�:LWKLQ�9HUVLRQ�%�” . For the field “$FWLRQ��&RPPDQG�7ULJJHUHG�” select “&RPPDQG�YLD�&RPPDQG�:L]DUG��,QVWUXFWLRQ�” . For the field “&RPPDQG” �click again on the ER[�on the ULJKW�VLGH to access the

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-36

screen “(GLW�&RPPDQG” . Here you make the following selections (if they are not already selected):

Then FOLFN on “([HFXWH�3ODQQLQJ�)XQFWLRQ��6LPSOH�” �to be able to choose the button “1H[W” . In the next screen make the following selections: 'LVSOD\�9DULDEOH�6FUHHQ�� ³21” 5HIHUHQFH�WR�'DWD�3URYLGHU�RI�7\SH�)LOWHU�� ³'3B�” 3ODQQLQJ�)XQFWLRQ: 3��B3)B�� Remain in this screen.

1-4-3 As two revaluation variables are to be used as import parameters, link the planning function and the import parameters. Place the cursor in the field “ �9DULDEOH�9DOXH” and click on the ER[�on the ULJKW�VLGH. This will bring you to the screen (GLW�3DUDPHWHU�where you make the following selections: 9DULDEOH:� �3��B9$5B5(9B&2*6B7:$7�9DULDEOH�7\SH� %LQGLQJ�W\SH�%LQGLQJ�7\SH�� ,WHP�,QSXW�6WULQJ�,WHP�%LQGLQJ�� ,1387B),(/'B,7(0B9$5B7:$7� Click the button “2.” repeatedly until you return to the screen (GLW�&RPPDQG. You should find a row there with the description “ ��9DULDEOH�9DOXH” which contains your selected variable. Place the cursor again in the field “ �9DULDEOH�9DOXH” to integrate the second variable. Proceed as described for the first import parameter but this time select “3��B9$5B5(9B&2*6B-8&” for the field “9DULDEOH” �and “ ,1387B),(/'B,7(0B9$5B-8&” for the field “ ,WHP�%LQGLQJ” . The two other settings correspond to those made for TWAT. Click the button “2.” repeatedly until your return to the initial screen of the Web Application Designer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-37

6DYH�your web-based planning application. ([HFXWH�your web-based planning application. The copy function should be executed immediately. Now choose the function key “5HYDOXDWLRQ�)XQFWLRQ�:LWKLQ�9HUVLRQ�%�” . A screen should open in which you can see a decentralized display of the two variants with the values of your choice. Execute the revaluation and then reset using the delete function.

1-5 Afterwards the FRS\�IXQFWLRQ�RI�9HUVLRQ�"�!% (the VHQGHU�YHUVLRQ was a YDULDEOH) is to be added in the web-based planning version. This variable for the characteristic 0VERSION can be optionally modeled with the web item “ Button Group” with an automatically opening variable screen to query the desired sender version or – as described in this exercise task – the variable and its possible characteristic values can be offered for selection to the end user by means of the dropdown box using a master data query. In this case the copy function should not conduct any further variable queries. As the second modeling variant is to be implemented, a master data query is set up fro the characteristic 0VERSION; this query enables the selection of the desired versions B1 and B2: 7HFKQLFDO�QDPH:� � 7%:��B0$67(5B48(5<B�9(56,21�'HVFULSWLRQ�� 7%:��B0$67(5B48(5<B�9(56,21

1-5-1 You need to include this query as a GDWD�SURYLGHU�RI�W\SH�TXHU\�in the web-based planning application. Internally, this data provider can be executed as DP_4. 6DYH�your web-based planning application again.

1-5-2 On the second tab page “ Price Planning” create a GURSGRZQ�ER[�within the container. This should be placed in the WKLUG�FHOO�from the OHIW�in the table in the container. Change the internal technical designation of the dropdown box as follows: ³'523'2:1B9(56,21B$86B48(5<´� Configure the properties of the dropdown box as follows: :LWK�7UD\:� � 6HOHFW��³2))´�'DWD�%LQGLQJ�7\SH�� &KDUDFWHULVWLF�6WUXFWXUH�0HPEHU�� &+$5$&7(5,67,&�� 6(/(&7,21��'DWD�3URYLGHU�� '3B��&KDUDFWHULVWLF�� 9(56,21�5HDG�0RGH�� 0DVWHU�'DWD�7DEOH��0�� $IIHFWHG�'DWD�3URYLGHU�� 'HIDXOW��$GGLWLRQDO�$FWLRQ�� &RPPDQG�YLD�&RPPDQG�:L]DUG�� ,QVWUXFWLRQ��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-38

([HFXWLRQ�3RLQW�RI�7LPH�� %HIRUH��GHIDXOW�YDOXH��6DYH�the web-based planning application.

1-5-3 Create the web item “%XWWRQ�*URXS” where the web item relates to the copy version and the variable to the version in the IRXUWK�FHOO�from the OHIW�of the table in the container. Change the internal technical designation of the button group as follows: “&23<B:,7+B9$5B9(56,21” . Configure the properties of this button group as follows: For the field “ ��""��%XWWRQ�” click on the ER[�RQ�WKH�ULJKW�VLGH�and in the next screen select the following : &DSWLRQ�� &RS\�RI�9HUVLRQ"�!% $FWLRQ��&RPPDQG�7ULJJHUHG�� &RPPDQG�YLD�&RPPDQG�:L]DUG�� ,QVWUXFWLRQ� Click again on the ER[�an the ULJKW�VLGH�of the field “&RPPDQG” and select:

In the next screen configure the following: 'LVSOD\�9DULDEOH�6FUHHQ�� ³2))” 5HIHUHQFH�WR�'DWD�3URYLGHU�RI�7\SH�)LOWHU�� '3B� 3ODQQLQJ�)XQFWLRQ:� � � � � � � 3��B3)B�� Please remember that the variable screen must be switched off, to prevent the variable screen being called immediately when the copy function is executed. The aim was to be able to select a variable using the dropdown box! For the field “ �9DULDEOH�9DOXH” , click on the ER[ on the ULJKW�VLGH�of this field and make the following selections: 9DULDEOH�� 3��B9$5B6(1'(59(56,21B&23<�9DULDEOH�7\SH�� %LQGLQJ�7\SH�%LQGLQJ�7\SH�� 'DWDB3URYLGHUB6HOHFWLRQ�'DWD�3URYLGHU�� '3B��&KDUDFWHULVWLF�� 9(56,21��HQWHU�PDQXDOO\�LI�QHFHVVDU\��Click the button “2.” repeatedly.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-39

6DYH�your web-based planning application again and then H[HFXWH it. Please remember that you do not need to create neither a dropdown box nor input help for the variable group and for the fiscal year “*URXS��B9$5B)<B��B30” , which is a query variable and not a function variable. Instead the query always takes place automatically according to query variables when executing the web query. In our example the query on the system side is not necessary because neither fiscal years are included in the rows or columns.

1-6 Navigate to the tab page “3ULFH�3ODQQLQJ“ and plan manually ��for -8&�and ��for 7:$7 for fiscal year �� exclusively in Version %�. 5HIUHVK�the SODQ�GDWD, to execute a summation of the plan data in Version B1 for fiscal year 2010. Use the GURSGRZQ�ER[ to select the GHOHWH�IXQFWLRQ and then the FRS\�IXQFWLRQ�WR�FRS\�WKH�GDWD�IURP�9HUVLRQ�%��WR�%�.�Both functions are automatically executed after their selection. Afterwards execute the UHYDOXDWLRQ�IXQFWLRQ. In the screen that then appears, select ��IRU�7:$7�DQG��IRU�-8&��for the revaluation variable.��Choose the button “2.” to execute the functions for the set parameter values.

Then revise the revaluated data of fiscal year ��in Version %�. For example, set the value for -8&�to ��and the value for 7:$7�to ��. Afterwards XSGDWH�WKH�SODQ�GDWD. Choose the button “5HVHW” . All numeric values of both versions are reset to the data of the plan data the last time it was saved. Afterwards manually plan ��for -8&�and ��for 7:$7�for fiscal year �� and Version %� and then select Version B2 for characteristic 0VERSION using the dropdown box and then select “&RS\�)XQFWLRQ�IURP�9HUVLRQ�"�!%” . Save your plan data and exit the web-based planning application and close the Web Application Designer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-40

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-41

�6ROXWLRQV�

8QLW�� &UHDWLQJ�DQG�8VLQJ�D�:HE�%DVHG�3ODQQLQJ�$SSOLFDWLRQ�ZLWK�:$'�

�

1-1 Navigate to the :HE�$SSOLFDWLRQ�'HVLJQHU. To access the Web Application Designer you click the ³6WDUW´ button within Citrix and then navigate as follows: 6WDUW��!�3URJUDPV��!�%XVLQHVV�([SORUHU��!�:HE�$SSOLFDWLRQ�'HVLJQHU. Choose the button “1HZ” and save the web template under the following designations: Description: *URXS��B7%:��B:$'B6$/0$1 Technical name: *URXS��B7%:��B:$'B6$/0$1 . The aim is to map the results layout of the quantity planning and the price planning of the Sales Managers using WAD.

1-1-1 Double-click on “1HZ�'DWD�3URYLGHU” . In the subsequent screen 1HZ�'DWD�3URYLGHU select the type “'DWD�3URYLGHU�RI�7\SH�4XHU\�9LHZ” in the *HQHUDO�area and in the area 'HILQH�'DWD�3URYLGHU�7\SH�select the query created in the Query Designer for quantity planning with the designation “7%:��B6��B$/��B34��B6$/0$1” >6��B$/B��B3/$148(5<B��B6$/0$1@. This Data Provider is executed internally as '3B�. Create a second Data Provider with the same settings and which relates to the price planning query with the designation “7%:��B3��B$/��B34��B6$/0$1” >3��B$/B��B3/$148(5<B��B6$/0$1@. This Data Provider is executed internally as '3B�. Finally create a third Data Provider that relates to the ILOWHU 3��B)B��creating in the Planning Modeler during price planning. Create a new data provider by double-clicking on “ New Data Provider” , but this time select “ Data Provider from Type Filter [SELECTOR_DATA_PROVIDER]” as the type as shown in the screenshot below.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-42

In the dialog window “1HZ�'DWD�3URYLGHU” in the area “'DWD�3URYLGHU�3URSHUWLHV” , select “)LOWHU�>6HOHFWLRQB2EMHFW@” in the “ ,QLWLDOL]H�ZLWK” field. For the field “)LOWHU” in FDSLWDO�OHWWHUV HQWHU�the WHFKQLFDO�QDPH�RI�WKH�ILOWHU�instead of “ Default” . This Data Provider is executed internally as '3B�. 6DYH�your web-based planning application. In the following exercise, your aim is to place quantity and price planning on various tab pages and provide planning functions such as saving, refreshing and resetting centrally for all tab pages. Only the specific planning functions of the quantity or price planning will later be provided on the corresponding tab pages.

1-1-2 In the “/D\RXW” area, enter “4XDQWLW\�DQG�3ULFH�3ODQQLQJ�RI�WKH�6DOHV�0DQDJHU” . Select font “$ULDO” , font size “ �” and “ UHG” �as the color. 6DYH�your web application. In order to ensure better integration of the web item, insert a table for the three functions that are relevant for all tab pages using the button “ ,QVHUW�7DEOH” . The table should be place directly beneath the heading “4XDQWLW\�DQG�3ULFH�3ODQQLQJ�RI�WKH�6DOHV�0DQDJHU” and consist of RQH�URZ�ZLWK�WKUHH�FROXPQV. For the field “:LGWK” select �� to keep the distance between the three buttons as small as possible. 6DYH�your web-based planning application.

1-1-3 Afterwards ensure that before creating the three buttons that you are actually in the cell of the table intended for this purpose. Place the cursor in the ILUVW�FHOO�RQ�WKH�OHIW�of the WDEOH you have created. The save button is to be installed here.� For this purpose, drag and drop the web item “%XWWRQ�*URXS” �into the cell named

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-43

above and configure the web item parameters as follows:: :LWK�7UD\�� 6HOHFW�³2))´. Now click on the ER[ at the ULJKW�VLGH�RI�the field “ ��""��%XWWRQ�” .

In the following screen “ Edit Parameters” select the following: &DSWLRQ�� 6DYH�3ODQ�'DWD�$FWLRQ��&RPPDQG�7ULJJHUHG�� &RPPDQG�YLD�&RPPDQG�:L]DUG�� ,QVWUXFWLRQ��Now click on the ER[�at the ULJKW�VLGH�RI�WKH�ILHOG�“&RPPDQG” and in the subsequent “ Edit Command” screen, make the following selections:

After making your selection FOLFN�RQ�WKH�WH[W�“ Save Changed Data (SAVE_DATA)“ ,so that the button “ Next” is activated. Click the button “2.” twice to return to the initial screen of the properties. You should receive the following properties display:

Save your web-based planning application. Now place the cursor in the FHQWHU�FHOO�of the WDEOH�you created in Task 1-1-2. The Refresh button is to be installed here.��Proceed as described for the save button and select “ Refresh Data “ >5()5(6+B'$7$@” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-44

Save your web-based planning application. Afterwards place the cursor in the cell on the right side of the table you created and install the reset button which is given the text “5HVHW�3ODQ�'DWD” �and for which you enter “5HVHW�3ODQ�'DWD�>5(6(7B'$7$@” .� 6DYH�your web-based planning application.

1-1-4 The three web items you have created currently have the standard technical designation “ Button_Group_ITEM_1 to Button_Group_Item_3“ . These designations should now be changed to ensure better clarity. To do this, click on the first button group for the save button and then click “5HQDPH�:HE�,WHP” (to the right of the dropdown box) n the “3URSHUWLHV” area. In the following screen write 6DYH�in the field “1HZ�1DPH” . Proceed in the same way for Refresh and Rest and assign the names “5HIUHVK” and “5HVHW” . (Umlauts are not permitted at this point). 6DYH�and H[HFXWH�your web application.

1-2 Now you need to implement two tab pages. The first one is for quantity planning and the second for price planning. Drag and drop the web item “7DE�3DJHV” into the DUHD�EHQHDWK�WKH�WDEOH�to create the two tab pages. Change the internal technical designation of this web item to “7DE�3DJHV” .

1-2-1 Drag and drop the standard web item “$QDO\VLV” into the area of the tab pages. Change the internal technical designation of this web item to “4XDQWLW\3ODQQLQJ4XHU\” . Make the following selections in the Properties of these web items: Number of Lines: � Position of new Lines: %RWWRP Data Provider: '3B� . Do not make any changes to the other properties and VDYH�your web-based planning application. Now drag and drop a “&RQWDLQHU” web item into the area of the tab pages web items XQGHUQHDWK the existing “ Analysis” web item. Navigate to the properties of web item with the name “7DE�3DJHV” and create two tab pages. The web item “ Analysis” should be placed on the first tab page and the container on

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-45

the second. For the first tab page, open the ER[�DW�WKH�ULJKW�HGJH�of the “ �7DE�3DJH” . In the following screen enter “4XDQWLW\�3ODQQLQJ” for the field “&DSWLRQ” and for the field “6XERUGLQDWH�:HE�,WHP” select the container with the technical designation “4XHU\IRU4XDQWLW\3ODQQLQJ” . In this way you have created the first tab page, named it and assigned the web item “ Analysis” . In the area “3URSHUWLHV” for the web item with the designation “7DE�3DJHV” , open the ER[�RQ�WKH�ULJKW�HGJH�of the field “ �7DE�3DQHO” again.

In the following screen enter “3ULFH�3ODQQLQJ” for the field “&DSWLRQ” and for the field “6XERUGLQDWH�:HE�,WHP” select the container with the technical designation “&217$,1(5B,7(0B�” . In this way you have created the second tab page, named it and assigned a container to it. The container is required because in addition to a query on the second tab page you also wish to include planning functions and variables and a dropdown box and it is only possible to assign just one object to a tab page. By assigning a container, it is possible to collect other objects that are thereby indirectly assigned to the tab page.

1-2-2 Place the cursor in the container of the tab page “3ULFH�3ODQQLQJ” and drag and drop the standard web item “$QDO\VLV” into the container. Change the internal technical designation of this web item to “4XHU\IRU3ULFH3ODQQLQJ” . Make the following selections in the Properties of these web items: Number of Lines: � Position of new Lines: %RWWRP Data Provider: '3B� . Do not make any changes to the other properties and VDYH�your web-based planning application. Execute the web-based application.�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-46

1-3 In the following steps restrict your work to the tab page "Price Planning" and the container included upon it. In this container, integrate an additional table by choosing the button “ ,QVHUW�7DEOH” . The table is to have RQH�URZ�and VL[�FROXPQV; enter ��for the field “:LGWK” . The table should be placed DERYH�the web item “ Analysis” that you created in Task 1-2-2. In the ILUVW�FHOO�RQ�WKH�OHIW�VLGH�RI�WKH�WDEOH, a dropdown box is to be installed that allows the selection of FRS\�DQG�GHOHWH�IXQFWLRQV. Both functions have no variables. To do this drag and drop the web item “'URSGRZQ�%R[” into the cell of the table named above. In this dropdown-box WKH�WZR�SODQQLQJ�IXQFWLRQV�QDPHG�DERYH�are to be integrated, each relates to the ILOWHU, that you included in Task 1-1-1- as the data provider, or more exactly as '3B�. Change the technical designation of the dropdown box to “'URSGRZQ%R[B�3ODQQLQJ)XQFWLRQV” . Navigate to the properties of the dropdown box and select the data binding type “)L[HG�/LVW�RI�2SWLRQV” .

For the field “ �)L[HG�2SWLRQV” click on the ER[�on the ULJKW�VLGH�to access the screen “(GLW�3DUDPHWHU” . For the field “'HVFULSWLRQ�RI�6HOHFWLRQ” enter ”&RS\�9HUVLRQ�%��!%�” . For the field “$FWLRQ��&RPPDQG�7ULJJHUHG�” select “&RPPDQG�YLD�&RPPDQG�:L]DUG��,16758&7,21�” . �For the field “&RPPDQG” click on the ER[�on the ULJKW�VLGH�to access the screen “(GLW�&RPPDQG” . Here you navigate to the tab page $OO�&RPPDQGV�and select the execution of the planning functions in accordance with the following display:

Then FOLFN�on “([HFXWH�3ODQQLQJ�6HTXHQFH��6LPSOH�” , to then choose the button “1H[W” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-47

In the next screen you select “'3B�” for the field “5HIHUHQFH�WR�'DWD�3URYLGHU�RI�7\SH�)LOWHU” and for the field “3ODQQLQJ�)XQFWLRQ” select “3��B3)B��” (the copying function of version B1->B2) using the search help which you can access at the right side of this field. Alternatively you can also enter the technical name of the planning function directly in the field “ Planning Function” . Confirm with “2.” twice. You must now repeat this procedure for another “)L[HG�2SWLRQ” for the second planning function by again FOLFNLQJ�RQ�WKH�ER[�RQ�WKH�ULJKW�VLGH�of the field “ �)L[HG�2SWLRQ” to access the screen “(GLW�3DUDPHWHU” . For the field “'HVFULSWLRQ�RI�6HOHFWLRQ” enter ”'HOHWH�'DWD�LQ�9HUVLRQ�%�” . Link filter '3B� with function 3��B3)B��, which provides the deleting function within Version B2. 6DYH�your web-based planning application again and then H[HFXWH it. Please remember that in the training system, the browser display must be updated with the Refresh button to display the changed version of the application. Please observe that the execution of the selected function is automatic (event-controlled), further functions in addition to the dropdown box are not necessary. When you open the tab page for price planning, the copy function should be executed automatically. Therefore VHOHFW�the GHOHWH�IXQFWLRQ. As you can see, this is executed automatically and the data of Version B2 are reset.

1-4 Now you need to integrate the UHYDOXDWLRQ�IXQFWLRQ�for the data within Version %��with your WZR�YDULDEOHV for 7:$7�and -8&. As the variables set up in the planning function of the Planning Modeler only enter the web-based planning application as import parameters, the web item “ ,QSXW�)LHOG” must be created twice as there are two variables.

1-4-1 Drag and drop the web item “ ,QSXW�)LHOG” in the VHFRQG�FHOO�IURP�WKH�ULJKW�RI�WKH�WDEOH. The web item is later used to transfer the TWAT parameter values. Change the internal technical designation of the input field to “ ,1387B),(/'B,7(0B9$5B7:$7” . Maintain the properties of the “ ,QSXW�)LHOG” as follows: 9LVLELOLW\�� +LGGHQ��+,''(1��:LWK�7UD\�� 6HOHFW��³2))´�/DEHO�YLVLEOH�� 6HOHFW�³2Q´�/DEHO�� 9DULDEOH�7:$7�9DOXH�+HOS�%XWWRQ�LV�9LVLEOH�� 6HOHFW�³21´��Leave all other settings unchanged.�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-48

Now create a second “ ,QSXW�)LHOG” in the ILUVW�FHOO�IURP�WKH�ULJKW�RI�WKH�WDEOH. The web item is later used to transfer the JUC parameter values. Change the internal technical designation of the input field to “ ,1387B),(/'B,7(0B9$5B-8&” . Make the same settings as for the previous input field. The only difference is the field “/DEHO” where you enter “9DULDEOH�-8&“ . 6DYH�your web-based planning application.

1-4-2 Now you need to integrate the web item “%XWWRQ�*URXS” in WKH�VHFRQG�FHOO�IURP�WKH�OHIW�RI�WKH�WDEOH. Change the internal technical description of the button group to “5(9$/8$7,21B)81&7,21” . In the 3URSHUWLHV�of this web item, make the following configurations: For the field “ ��""�%XWWRQ” ,�click on the�“ER[” on the right side to open the screen “(GLW�3DUDPHWHUV” . For the field “/DEHO” enter “5HYDOXDWLRQ�)XQFWLRQ�:LWKLQ�9HUVLRQ�%�” . For the field “$FWLRQ��&RPPDQG�7ULJJHUHG�” select “&RPPDQG�YLD�&RPPDQG�:L]DUG��,16758&7,21�” . For the field “&RPPDQG” �click again on the ER[�on the ULJKW�VLGH to access the screen “(GLW�&RPPDQG” . Here you make the following selections (if they are not already selected):

Then FOLFN on “([HFXWH�3ODQQLQJ�)XQFWLRQ��6LPSOH�” �to be able to choose the button “1H[W” . In the next screen make the following selections: 'LVSOD\�9DULDEOH�6FUHHQ�� ³21” 5HIHUHQFH�WR�'DWD�3URYLGHU�RI�7\SH�)LOWHU�� ³'3B�´�3ODQQLQJ�)XQFWLRQ� 3��B3)B��

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-49

Remain in this screen.

1-4-3 As two revaluation variables are to be used as import parameters, link the planning function and the import parameters. Place the cursor in the field “ �9DULDEOH�9DOXH” and click on the ER[�on the ULJKW�VLGH. This will bring you to the screen (GLW�3DUDPHWHUV�where you make the following selections: 9DULDEOH:� �3��B9$5B5(9B&2*6B7:$7�9DULDEOH�7\SH� %LQGLQJ�7\SH�%LQGLQJ�7\SH�� ,WHP�,QSXW�6WULQJ�,WHP�%LQGLQJ�� ,1387B),(/'B,7(0B9$5B7:$7� Click the button “2.” repeatedly until you return to the screen (GLW�&RPPDQG. You should find a row there with the description “ ��9DULDEOH�9DOXH” which contains your selected variable.

Place the cursor again in the field “ �9DULDEOH�9DOXH” to integrate the second variable. Proceed as described for the first import parameter but this time select “3��B9$5B5(9B&2*6B-8&” for the field “9DULDEOH” �and “ ,1387B),(/'B,7(0B9$5B-8&” for the field “ ,WHP�%LQGLQJ” . The two other settings correspond to those made for TWAT. Click the button “2.” repeatedly until your return to the initial screen of the Web Application Designer. 6DYH�your web-based planning application. ([HFXWH�your web-based planning application. The copy function should be executed immediately. Now choose the function key “5HYDOXDWLRQ�)XQFWLRQ�:LWKLQ�9HUVLRQ�%�” .

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-50

A screen should open in which you can see a decentralized display of the two variants with the values of your choice. Execute the revaluation and then reset using the delete function.

1-5 Afterwards the FRS\�IXQFWLRQ�RI�9HUVLRQ�"�!% (the VHQGHU�YHUVLRQ was a YDULDEOH) is to be added in the web-based planning version. This variable for the characteristic 0VERSION can be optionally modeled with the web item “ Button Group” with an automatically opening variable screen to query the desired sender version or – as described in this exercise task – the variable and its possible characteristic values can be offered for selection to the end user by means of the dropdown box using a master data query. In this case the copy function should not conduct any further variable queries. As the second modeling variant is to be implemented, a master data query is set up fro the characteristic 0VERSION; this query enables the selection of the desired versions B1 and B2: 7HFKQLFDO�QDPH:� � 7%:��B0$67(5B48(5<B�9(56,21�'HVFULSWLRQ�� 7%:��B0$67(5B48(5<B�9(56,21

1-5-1 You need to include this query as a GDWD�SURYLGHU�RI�W\SH�TXHU\�in the web-based planning application. Internally, this data provider can be executed as DP_4. 6DYH�your web-based planning application again.

1-5-2 On the second tab page “ Price Planning” create a GURSGRZQ�ER[�within the container. This should be placed in the WKLUG�FHOO�from the OHIW�in the table in the container. Change the internal technical designation of the dropdown box as follows: ³'523'2:1B9(56,21B$86B48(5<´� Configure the properties of the dropdown box as follows: :LWK�7UD\:� �� 6HOHFW��³2))´�'DWD�%LQGLQJ�7\SH�� &KDUDFWHULVWLF�6WUXFWXUH�0HPEHU�� &+$5$&7(5,67,&�� 6(/(&7,21��'DWD�3URYLGHU�� '3B��&KDUDFWHULVWLF�� 9(56,21�5HDG�0RGH�� 0DVWHU�'DWD�7DEOH��0�� $IIHFWHG�'DWD�3URYLGHU�� 'HIDXOW�9DOXH�$GGLWLRQDO�$FWLRQ�� &RPPDQG�YLD�&RPPDQG�:L]DUG�� ,QVWUXFWLRQ��([HFXWLRQ�3RLQW�RI�7LPH�� %HIRUH��GHIDXOW�YDOXH��6DYH�the web-based planning application.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-51

1-5-3 Create the web item “%XWWRQ�*URXS” where the web item relates to the copy version and the variable to the version in the IRXUWK�FHOO�from the OHIW�of the table in the container. Change the internal technical designation of the button group as follows: “&23<B:,7+B9$5B9(56,21” . Configure the properties of this button group as follows: For the field “ ��""��%XWWRQ�” click on the ER[�RQ�WKH�ULJKW�VLGH�and in the next screen select the following : &DSWLRQ�� &RS\�RI�9HUVLRQ"�!% $FWLRQ��&RPPDQG�7ULJJHUHG�� &RPPDQG�YLD�&RPPDQG�:L]DUG�� ,QVWUXFWLRQ� Click again on the ER[�an the ULJKW�VLGH�of the field “&RPPDQG” and select:

In the next screen configure the following: 'LVSOD\�9DULDEOH�6FUHHQ�� ³2))” 5HIHUHQFH�WR�'DWD�3URYLGHU�RI�7\SH�)LOWHU�� '3B� 3ODQQLQJ�)XQFWLRQ:� � � � 3��B3)B�� Please remember that the variable screen must be switched off, to prevent the variable screen being called immediately when the copy function is executed. The aim was to be able to select a variable using the dropdown box! For the field “ �9DULDEOH�9DOXH” , click on the ER[ on the ULJKW�VLGH�of this field and make the following selections: 9DULDEOH�� 3��B9$5B6(1'(59(56,21B&23<�9DULDEOH�7\SH�� %LQGLQJ�7\SH�%LQGLQJ�7\SH�� 'DWDB3URYLGHUB6HOHFWLRQ�'DWD�3URYLGHU�� '3B��&KDUDFWHULVWLF�� 9(56,21��HQWHU�PDQXDOO\�LI�QHFHVVDU\��Click the button “2.” repeatedly. 6DYH�your web-based planning application again and then H[HFXWH it.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 12-52

Please remember that you do not need to create neither a dropdown box nor input help for the variable group and for the fiscal year “*URXS��B9$5B)<B��B30” , which is a query variable and not a function variable. Instead the query always takes place automatically according to query variables when executing the web query. In our example the query on the system side is not necessary because neither fiscal years are included in the rows or columns.

1-6 Navigate to the tab page “3ULFH�3ODQQLQJ“ and plan manually ��for -8&�and ��for 7:$7 for fiscal year �� exclusively in Version %�. 5HIUHVK�the SODQ�GDWD, to execute a summation of the plan data in Version B1 for fiscal year 2010. Use the GURSGRZQ�ER[ to select the GHOHWH�IXQFWLRQ and then the FRS\�IXQFWLRQ�WR�FRS\�WKH�GDWD�IURP�9HUVLRQ�%��WR�%�.�Both functions are automatically executed after their selection. Afterwards execute the UHYDOXDWLRQ�IXQFWLRQ. In the screen that then appears, select ��IRU�7:$7�DQG��IRU�-8&��for the revaluation variable.��Choose the button “2.” to execute the functions for the set parameter values.

Then revise the revaluated data of fiscal year ��in Version %�. For example, set the value for -8&�to ��and the value for 7:$7�to ��. Afterwards XSGDWH�WKH�SODQ�GDWD. Choose the button “5HVHW” . All numeric values of both versions are reset to the data of the plan data the last time it was saved. Afterwards manually plan ��for -8&�and ��for 7:$7�for fiscal year �� and Version %� and then select Version B2 for characteristic 0VERSION using the dropdown box and then select “&RS\�)XQFWLRQ�IURP�9HUVLRQ�"�!%” . Save your plan data and exit the web-based planning application and close the Web Application Designer.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-1

SAP AG 2006

&RQWHQW�� 6WDWXV�DQG�7UDFNLQJ�6\VWHP

6WDWXV�DQG�7UDFNLQJ�6\VWHP

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-2

SAP AG 2006

6WDWXV�DQG�7UDFNLQJ�6\VWHP��7RSLF�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�&RQFHSW�RI�WKH�6WDWXV�DQG�7UDFNLQJ�

6\VWHP� 8QGHUVWDQG�WKH�&XVWRPL]LQJ�6HWWLQJV� 8QGHUVWDQG�WKH�/RFNLQJ�&RQFHSW�RI�WKH�6WDWXV�DQG�

7UDFNLQJ�6\VWHP

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-3

SAP AG 2006

6WDWXV�DQG�7UDFNLQJ�6\VWHP��2YHUYLHZ�'LDJUDP





�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-4

SAP AG 2006

6WDWXV�DQG�7UDFNLQJ�6\VWHP��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�IRU�LPSOHPHQWLQJ�WKH�6WDWXV�DQG�7UDFNLQJ�6\VWHP��<RX�ZDQW�WR�XQGHUVWDQG�WKH�FRQFHSW�RI�WKLV�RUJDQL]DWLRQ�DQG�FRQWURO�IUDPHZRUN�IRU�SODQQLQJ��<RX�WKHQ�ZDQW�WR�VHW�XS�RQH�RI�\RXU�RZQ�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-5

SAP AG 2006

6WDWXV�DQG�7UDFNLQJ�6\VWHP��8QLW�2YHUYLHZ�'LDJUDP

8QLW�2YHUYLHZ� /HVVRQ��6WDWXV�DQG�7UDFNLQJ�6\VWHP

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-6

SAP AG 2006


$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�&RQFHSW�RI�WKH�6WDWXV�DQG�7UDFNLQJ�


7UDFNLQJ�6\VWHP

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-7

SAP AG 2006

6WDWXV�DQG�7UDFNLQJ�6\VWHP��%XVLQHVV�6FHQDULR

� <RX�DUH�D�PHPEHU�RI�WKH�SURMHFW�WHDP�LPSOHPHQWLQJ�WKH�6WDWXV�DQG�7UDFNLQJ�6\VWHP�DQG�ILUVW�ZDQW�WR�XQGHUVWDQG�WKH�FRQFHSW�RI�WKLV�RUJDQL]DWLRQ�DQG�FRQWURO�IUDPHZRUN�IRU�SODQQLQJ��7KHQ�\RX�ZDQW�WR�VHW�RQH�XS�\RXUVHOI�

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-8

SAP AG 2006

$UHD�0DQDJHU

+LHUDUFK\�2ULHQWHG�3ODQQLQJ�DQG�6WDWXV�7UDFNLQJ

$UHD�0DQDJHU

5HJLRQDO�0DQDJHU

5HJLRQDO�0DQDJHU

5HJLRQDO�6DOHV�

0DQDJHU5HJLRQDO�6DOHV�

0DQDJHU

7LPH

7DUJHW��

7DUJHW�� 3ODQ��

3ODQ��

7RS�GRZQ�7DUJHW�6HWWLQJ %RWWRP�XS�3ODQQLQJ

�

� The 6WDWXV�DQG�7UDFNLQJ�6\VWHP serves as an environment for structuring and carrying out planning,

and also for monitoring the planning process. �

Using the Status and Tracking System has the following advantages:

• The possibility of iterative alignment of planning results within a subplan by defining different planning sessions

• The clear assignment of subtasks to the responsible persons within a planning session

• Performance of planning while considering clear deadline specifications

• Regulated planning workflow on the basis of a status management system �

The above illustration shows that the planning is generally on a hierarchical basis, so that a planning system must enable the use of hierarchies.

� A versioning concept for the planning process is necessary, since different plan data is usually generated

in bottom-up planning and top-down planning. �

To bring the plan data from the different versions together, the persons responsible must communicate with one another. This communication must be supported by the system. Each planner must be assigned a specific planning task. Each planning task must be assigned a status.

� In order to control the entire planning process, the system must provide monitoring tools. These tools

must provide filter and search functions for easily detecting problem areas in the planning process.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-9

SAP AG 2006

([DPSOH�3ODQQLQJ�3URFHVV

��

� � �� ! � � � �" � �#�$��

� � �� ! � � � �% �� &#��'��

� �( � � �)� ��* �� (� ��

�� (� � �� +� ��( �� $&'�� ,�*- ��

� �/.'��0�1�)� �

%32 �� +� ��( ��4� �� 5&#� �

�� (��- ��

$FFHSW�SODQ

�� #� � �� 6� ��# �� $&'�� (�*- ��

� � -� ��78��

� � -) ��78��

�

� This slide shows a very simple example of a ERWWRP�XS�SODQQLQJ�VHVVLRQ.

� The Sales Director Americas initiates the planning process by sending e-mail notifications to regional

Sales Managers in her region. �

The regional Sales Managers enter plan data and request the Sales Director to approve the estimates. �

The Sales Director either accepts or rejects the submitted plans. �

When a plan is rejected the responsible regional Sales Manager is requested to revise the first plan estimate until the Sales Director accepts the plan.

� When all planning tasks are approved the planning session is finished.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-10

SAP AG 2006

%XLOGLQJ��%ORFNV�RI�WKH�6WDWXV�DQG�7UDFNLQJ�6\VWHP

z 6LQJOH�UXQ�RI�WKH�LWHUDWLYH�SODQQLQJ�SURFHVVz ([DPSOHV��ERWWRP�XS�SODQQLQJ��WRS�GRZQ�SODQQLQJ

z 6SHFLILF�EXVLQHVV�DUHDz ([DPSOHV��VDOHV�SODQQLQJ��FRVW�FHQWHU�SODQQLQJ

96:<;<=<> ?<@

A > ?<@1@<B(@�CD�E)D)D B F�@

G4HIC1?<@<B J�?)KIBLFM@ ?1>N B E HO?1HIP N�Q z 5HIOHFWV�WKH�KLHUDUFKLFDO�VWUXFWXUH�RI�D�SODQQLQJ�SURFHVV��

$�QRGH�LV�DVVLJQHG�WR�HDFK�SODQQHU�z $UHD�RI�D�KLHUDUFKLFDO�RUJDQL]DWLRQDO�VWUXFWXUH�RI�D�FRPSDQ\z 'LIIHUHQW�KLHUDUFKLHV�FDQ�EH�DVVLJQHG�WR�GLIIHUHQW�VXESODQVz ([DPSOHV��UHJLRQDO�KLHUDUFK\��FRVW�FHQWHU�KLHUDUFK\

�

� Each planning process in the Status and Tracking System is based on a VXESODQ and one or more SODQQLQJ�VHVVLRQV. The subplan identifies one specific type of planning process.

� Different planning sessions with different parameters (for example, direction of planning workflow,

different owners, different planning tasks,…) may be assigned and executed individually, depending on the progress of the subplan.

� A planning session is started when either the administrator or the plan owner sends VWDUW�H�PDLOV.

Depending on whether it is a WRS�GRZQ�RU�D�ERWWRP�XS�SODQQLQJ�VHVVLRQ, an e-mail is sent to all participants in the session or only to the participants on the next lower level of the hierarchy. The e-mail includes a link to the Status and Tracking System and a direct link to the planning task.

� The planners navigate to the STS, get an overview of their area of responsibility, and start the planning.

When the planner has completed the planning, she/he sets the status, optionally enters comments, and saves everything.

� A planning session can use the IXQFWLRQ�6HQG�VWDUW�H�PDLO in the Customizing of the Status and

Planning System, or in the overview monitor of the planning co-ordinator, to get the system to send an e-mail to all employees participating in the planning session.

� In the second case, the e-mail sending is started automatically as a job executed immediately in the

background. For this e-mail, the system uses notification texts that contain a link to directly start the assigned data entry in the Web browser. �

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-11

SAP AG 2006

2UJDQL]DWLRQDO�+LHUDUFK\

&RXQWU\�0DQDJHU�(0($��5HJLRQ�

$UHD�0DQDJHU�6RXWK��$UHD�

$UHD�0DQDJHU�1RUWK��$UHD�

�

� The organizational hierarchy is another building block in the Status and Tracking System.

� The above illustration shows an example hierarchy in which “area” is the basis characteristic of the

hierarchy. The “region” characteristic is used as a node characteristic. �

Please note that the following hierarchy types are not permitted:

• Hierarchies with several top nodes

• Hierarchies with text nodes

• Hierarchies with interval nodes �

By setting up a connection between the characteristic values of the hierarchy and an assigned user, which is performed in the Customizing of the Status and Tracking System, you create the basis for the workflow (status mapping, notification of planners) of the Status and Tracking System.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-12

SAP AG 2006

,QWHJUDWLRQ�RI�WKH�676�+LHUDUFK\�DQG�WKH�6WDQGDUG�3ODQQLQJ�$UHD

�

� The Status and Tracking System is modeled within the BW BPS planning interface. For this reason, you

must use transaction BPS0 to select a previously created standard planning area in the Customizing of the Status and Tracking System.

� A standard planning area is an interface between the planning with BW BPS and the BW itself, and it

contains a real-time InfoProvider. You can thus access the characteristics and key figures of the planning area in the Status and Tracking System.

� Please note that multi-planning areas of BW BPS cannot be used in the Status and Tracking System.

� To be able to assign a hierarchy to a subplan, you must create a hierarchy in BW for a desired

characteristic from the real-time InfoProvider of the standard planning area. �

In accordance with the above illustration, you then have to go to the Customizing of the Status and Tracking System and assign the standard planning area, the characteristic with the hierarchy, and the hierarchy itself to the desired subplan of the Status and Tracking System. You then have to execute a “ hierarchy import run” .

� For the relationship between planning areas and subplans, a subplan is assigned to exactly one planning

area, or multiple subplans can be assigned to one planning area. This means that a planning area always has a clearly definable business task, corresponding to one subplan. The fact that a planning area can be referenced by multiple subplans adheres to the notion of planning integration. Thus, for example, the turnover plan figures resulting from the profit planning are also input into the P&L planning. It is therefore an option to at least partially combine the two subplans in the same planning area.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-13

SAP AG 2006

,QWHJUDWLRQ�RI�3ODQQLQJ�2EMHFWV�LQ�WKH�6WDWXV�DQG�7UDFNLQJ�6\VWHP

R�SUT ��

R�SUT ��

3ODQQLQJ�REMHFWV�RI�WKH�%:�%36�RU�WKH�%,�LQWHJUDWHG�SODQQLQJ�FDQ�EH�XVHG�

%36 ,QWHJUDWHG�3ODQQLQJ

�

� The above illustration refers to the follow-up Customizing, after the “ hierarchy import run” , which was

described on the previous slide. It shows, for one, that you can assign a planner and one or more substitutes to each element of the hierarchy. In the above illustration, this assignment to the hierarchy has already been performed. Follow-up settings will be described for this planner.

� You also see that each planner may be assigned a planning application (that is, layout or plan query), a

control report (that is, a reporting query) and possibly multiple planning sequences (for automatically executing planning functions within a status change). In the process, both structures of BW BRP and of the BI-integrated planning can be accessed.

� You also see that it should be possible to automatically execute a JOREDO�SODQQLQJ�VHTXHQFH during the

status change. Thus, for example, in the status change from “ for approval” to “ approved” , you can assign a sequence that automatically copies the approved data into another version.

� 7LPH�GDWD�LQ�WKH�PRQLWRU��FRPSOHWLRQ�WLPH��

Note that all time data in the monitor (such as the time a comment was entered) is displayed in the time zone which the logged-on user maintained in his/her user master data. If no time zone is maintained, the system time zone applies. An exception is the completion time: If no time zone is maintained, the system first checks whether Customizing contains an explicit time zone entry for the respective area of responsibility. If so, this time zone is used. Otherwise, the system time zone is used.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-14

SAP AG 2006

$WWULEXWHV�RI�3ODQQLQJ�6HVVLRQ��

�

� The above illustration shows special settings for combining a subplan and a planning session:

� 'LUHFWLRQ�RI�WKH�SODQQLQJ�VHVVLRQ�

• Specifies the direction in which the assigned organizational structure will run during the planning session: top-down or bottom-up. How the e-mails are sent and which statuses are available for the subtasks within the planning session depends on this setting (for example, the status “ approved” is only available in bottom-up planning). Note that with top-down planning, the start e-mail is sent to the hierarchically highest-level person responsible. In the bottom-up planning, the start e-mail goes to all persons responsible who were maintained for the hierarchy of the subplan.�

� 3ODQQLQJ�VHTXHQFH�LI�VWDWXV�FKDQJHV�

• Here you specify whether it should be possible to execute a global planning sequence automatically if the status changes. You can select whether to execute the global planning sequence synchronously or as a background job if the status changes.

� $XWRPDWLF�H�PDLO�GLVSDWFK�DFWLYH�

• Determines whether or not the automatic e-mail notification system should be used when a status change occurs.

� 8VH�WLPH�

• Specifies whether the time and the time zone are defined for the completion time along with the date. Only the time zone has an effect on monitoring the completion times. The time data that the system logs during the planning session (for example, time stamp for status change or comments) is always saved in system time.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-15

SAP AG 2006

$WWULEXWHV�RI�3ODQQLQJ�6HVVLRQ��

�

� 8VLQJ�D�FDVFDGLQJ�VWDWXV�FKDQJH�

• If you are assigned as a responsible person to a higher level in the organizational structure and have made the corresponding setting in Customizing, you can change the status of all tasks assigned to the employees subordinate to you with a single action. No global planning sequences are performed and no e-mails are sent; only the status of the areas of responsibility is set.�

� (QWHULQJ�D�WH[W�HOHPHQW�

• You can create a text element with additional information for the planning session of a subplan. You can see it in the detail view in the monitor of the Status and Tracking System. You can create this additional information text in the customer-specific namespace using transaction SE61, entering the document class “ general text” and the desired language. During execution, the system uses the notification texts in the language version maintained in the user data of the address data. If the language entry is missing from the user data, or if a language is entered for which no language version of the notification text is available, then the system uses the English language version, which definitely should be created to ensure optimal system behavior.

� (QWHULQJ�D�WKHPH�URRW�

• In every subplan and every planning session, different stylesheets can be used. SAP supplies different predefined theme roots, such as SAP_STANDARD, SAP_TRADESHOW or SAP_CHROME. If you do not make an entry here, the standard theme root set in the system is used.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-16

SAP AG 2006

$XWKRUL]DWLRQV�IRU�WKH�6WDWXV�DQG�7UDFNLQJ�6\VWHP

8VHU�JURXS$XWKRUL]DWLRQ�REMHFWV

3HUIRUP�WKH�&XVWRPL]LQJ�IRU�WKH�6WDWXV�DQG�7UDFNLQJ�6\VWHP�IRU�WHFKQLFDO�DGPLQLVWUDWRU�IXQFWLRQ�VFRSH�5B676B&867

$XWKRUL]DWLRQ�IRU�VSHFLDO�DFFHVV�WR�6WDWXV�DQG�7UDFNLQJ�6\VWHP�IRU�SODQQLQJ�FRRUGLQDWRUV�7KH\�WKXV�KDYH�QR�&XVWRPL]LQJ�DXWKRUL]DWLRQ��EXW�FDQ�YLHZ�DQG�XVH�WKH�PRQLWRU�

5B676B683

$XWKRUL]DWLRQ�IRU�SODQQLQJ�VHVVLRQ�DQG�VXESODQ IRU�UHVSRQVLEOH�SHUVRQV�RU�WKHLU�VXEVWLWXWHV�5B676B37

�

� In the Status and Tracking System, the WKUHH�DXWKRUL]DWLRQ�REMHFWV�QDPHG�DERYH are assigned to the

respective XVHU�JURXSV: • $GPLQLVWUDWRU�• 3HUVRQ�UHVSRQVLEOH�ZLWKLQ�D�VXESODQ�• 3ODQQLQJ�FRRUGLQDWRUV

� Depending on the user group, different requirements are made of the Status and Tracking System.

� The DGPLQLVWUDWRU is responsible for the Customizing of the STS.

� 3HUVRQV�UHVSRQVLEOH are assigned to an area of responsibility (hierarchy node) within a subplan, or

directly as substitutes. • The person responsible uses the STS to:

- branch from there to his/her planning application - set the status of his/her own planning - monitor and set the status of any subordinates

� 3ODQQLQJ�FRRUGLQDWRUV monitor the entire planning process of at least one subplan and therefore have

special access rights in STS. �

The Status and Tracking System presents those pages that belong to a planning task in practically identical form, regardless of whether you want to perform the planning or monitor the process. The only difference is that you are only allowed to set certain statuses of a task on the basis of the hierarchy level to which you are assigned (this means, whether you are executing or supervising a particular planning task).

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-17

SAP AG 2006

6WDWXVHV�LQ�WKH�0RQLWRU�RI�WKH�6WDWXV�DQG�7UDFNLQJ�6\VWHP

V C1C�H E C ?)K E�WXD K�?)K/: D ?M=1=YHIF1Z E W(in bottom-up planning session)V C1C�H E C ?)K E�WXD K�?)K/: D P F<[\=<> E K E�W ?Y@ W H E > E ? D�E W(in top-down planning session)

V C1C�H E C ?)K E�WXD K�?)K/: D @1F K]?1=Y=1H^F1Z E W(in bottom-up planning session)V C1C�H E C ?)K E�WXD K�?)K/: D @1F K�P)FM[_=1> E K E�W ?Y@ W H E > E ? D�E�W(in top-down planning session)

`+F<[a[ E @�K]P�FM>L:1[\@cbdB K Nfe :1[a=gKhFiP�FY[j[ E @�Kk=�?�C E

V C1C�H E C ?)K E�WXD K�?)K/: D @1F K]?1=Y=1H^F1Z E W ?Y@ W P�FY[a[ E @�K�l D m ; E > F1bnK N E P1:<HoH E @�Kk@�F W1E<p

V C1C�H E C ?)K E�WXD K�?)K/: D ?M=1=YHIF1Z E W ?1@ W P�F][a[ E @�KOl D�m ; E > F1bqK N E @1F WYE(in bottom-up planning session)V C1C�H E C ?)K E�WXD K�?)K/: D P F<[\=<> E K E�W ?Y@ W H E > E ? D�E W(in top-down planning session)

93Kh?�Ko: D F rMK N E P�FM[\=<> E KoB F3@cKoB [ EMs P1H^B K^B P)?Y> th@�F1KMP1HoB KoB P)?1>u F1P1v D K'?�Ko: D > F<P<v E�W th@�F<Kw> FMP1v E W

x E�D P1HoB,=�K^B F3@dF<r<K N E B P FM@ Dy P�F]@ D F1rYK N E 93K�?�Ko: D ?<@ Wz H�?�P1v)B,@ C{9 Q D K E [

�

� The above illustration presents a summary of all possible system icons in the monitor of the Status and

Tracking System.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-18

SAP AG 2006

,QWHJUDWLRQ�RI�WKH�6WDWXV�DQG�7UDFNLQJ�6\VWHP�ZLWK�WKH�%,�,QWHJUDWHG�3ODQQLQJ

�

� The BW BPS Status and Tracking System (STS) can be used together with the BI-integrated planning.

This is useful if you are already using BW BPS with STS and want to use additional functions from BI-integrated planning.

� If you want the lock check of STS to be active for the Web applications created in the BI-integrated

planning, an exit class (namely, CL_UPS_LOCK_DATASLICE) must be stored for the data slice in the Planning Modeler and here in the InfoProvider area, on the Data Slice tab page, for the STS lock check.

� In STS Customizing, you can then enter the URLs of Web applications created in BI-integrated

planning for the planning application and the control report. �

In addition, in a status change, you can enter either a global planning sequence created within BW BPS or a planning sequence (with a variant, if applicable) created within BI-integrated planning. Corresponding input help is available.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-19

SAP AG 2006

:KHQ�LV�DQ�(QG�8VHU�6SHFLILF�/RFN�LQ�WKH�%,�,QWHJUDWHG�3ODQQLQJ�7ULJJHUHG"

+HDGHU�VHOHFWLRQ )LOWHU�

+HDGHU�VHOHFWLRQ )LOWHU

+HDGHU�FKDUDFWHULVWLFV��ILVFDO�\HDU��

+HDGHU�VHOHFWLRQ )LOWHU

�

� If – as previously described – the exit class is set for the data slice, then the “ Header Selection” of the

Status and Tracking Systems is interpreted as a data slice by the system if a planner triggers a lock with this setting.

� Selections are locked on the basis of the characteristic values entered in the header selection.

� Thus only that planner is locked who triggered the status change.

� In the BI-integrated planning, a lock is triggered if the characteristic values of the header selection at

least partially overlap with the filter selections. This means that if fiscal years 2010 and 2011 were entered in the filter and 2010 is entered in the header selection area for this characteristic, only 2010 is in the intersection, meaning that all data records with the year 2010 are locked.

� Please note that if a planning function is executed with the filter that includes the selection 2010 and

2011, the planning function is locked for the entire selection of both values, because at least one data record (namely the one in the intersection) is locked.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-20

SAP AG 2006

3URFHGXUH�IRU�/RFN�9DOLGDWLRQ�LQ�WKH�6WDWXV�DQG�7UDFNLQJ�6\VWHP

<(6 12V H E N E ? W1E H3P N ?1HI?�P�K E H^B D KoB P D BL@g9 z 9|[i?<BL@)Kh?YB @ E1W<}

<(6 12

y D K N E rIBL> K E H D�E > E P�K/B F]@g?)K3> E ? D K3=�? HOKoB ?1>L> Q BL@�P1>,: W1E W BL@gK N E N E ? W1E H3P N ?<HI?�P�K E H^B D K^B P D1}

y D K N E : D E HM?cKO? D v4F�bX@ E H]F]H�? D :Y; D K^B Ko:�K E }<(6 12

<(6 12

y D F]@ E F<rYK N E @1F W<E�D ? D�D B C3@ E�W K�F~K N E : D�E H3> FMP v E WY}

<(6 12

y D K N E H E ?<>L�,K^B [ E y @�rIF A HIF1ZYB W1E H�: D�E W B,@X?c93K�?)K/: D ?Y@ W z HO?�P<v�BL@ C{9 Q D K E [ }

�

� First of all the system checks the authorizations of the user – the super user is always allowed to change

data that has been locked by STS. (He is not allowed to change data where he has no authorizations.) �

Then the system follows the routine described above. �

Note: if the user is assigned to more than one planning task in one subplan and one of his tasks is locked, he is also locked for all other tasks assigned to him (even if they have the status “ new” or “ in processing” ).

� Locks are set if either the person responsible for the task or a higher-level planner approves the task.

� Locks can be set independently from the status.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-21

SAP AG 2006

$GGLWLRQDO�)XQFWLRQV�DQG�3UHUHTXLVLWHV�RI�WKH�6WDWXV�DQG�7UDFNLQJ�6\VWHP

z 3UHUHTXLVLWHV�� Activation of HTTP services WXQJXVND and WXQJXVNDBGHWDLO� Authorization objects

$GGLWLRQDO�PHQX�HQWULHV�IRU�FXVWRPL]LQJ�WUDQVDFWLRQV

$GPLQLVWUDWLRQ� Deleting/copying

planning sessions� Deleting planning sessions� Transporting planning sessions� Sending reminder e-mails

�

� 5HPLQGHU�IXQFWLRQ

• In order to make sure that a planning session is completed at the planned deadline, you can schedule a report that checks the status of subtasks which belong to the planning session at the time of execution. You can use this to search for planning tasks that do not have the status DSSURYHG. If such planning tasks are found, the system automatically sends an e-mail to the persons responsible to remind them about completing tasks. You can change the predefined text of the e-mail message to suit your requirements ...

� Please note that you either execute the reminder function directly, or from the above screen by means of *RWR��9DULDQWV��6DYH�DV�YDULDQW�you can create a variant, and then create a job by means of 6\VWHP��6HUYLFHV��-REV��-RE�'HILQLWLRQ. You can then execute this job to run the report 836B676B5(0,1'(5 with the previously created variant at the desired time.

� Recommendation:

• The report should be planned so that it runs a few days before the deadline you defined for the planning session. This way, you give the persons responsible opportunity to complete the planning tasks not yet completed.

� The HTTP services are activated using transaction SICF.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-22

SAP AG 2006

$GMXVW�1RWLILFDWLRQ�7H[WV

� ��7� �� , � � ��& 6� � �� 7 � �� * �� 1�UPS_START_RUNDE_TOP_DOWN

� ��7� � � &h �� 2 �� ( � � ��& � ��78�� *�� )� � � ��

�1�UPS_START_RUNDE �

�(! �� )� � � �)� �)� ��#� � �� *�� (� )�� UPS_SEND_REMINDER

� �� -� �� .(�� 6��& � �� L�*- ��)�UPS_SEND_REJECTED

R�� )� �(��- �� &(�� L�*- �� & +�� *�� c � � � �*� �*� 7 � �)� �*�* ��

��UPS_SEND_CLOSED_TD

� �� ,��- � �% � ��&h �(� �� +��& ��)� �(��- �� *� � ��UPS_SEND_APPROVED

� � � �(� �� R��*� � 2 � � � �(� �� U��& ��,� ��7 2 � 2 7�� 5�� 6&'�� *�)� �(��- ��

UPS_SEND_RECALL

� FMH]?Y=<=YHhF1Z�?<>� �� &(�� L�*- �� & � �� (� � �� * �*��UPS_SEND_APPROVAL

2Q�VWDWXV�FKDQJH�WR

'HVFULSWLRQ6WDWXV7HFKQLFDO�QDPH

�

� Depending on the type of VWDWXV�FKDQJH and the KLHUDUFK\�OHYHO that is assigned to the subplan, the

system determines automatically which users will be sent an e-mail. The content of the e-mail is based on predefined templates delivered by SAP.

� It is possible to adapt the texts that are delivered by SAP or maintain your own customer-specific texts.

For example, you can add the telephone number of the responsible employee to the standard template, or information on how to contact the IT department if problems arise.

� The texts which the notification system uses for e-mails are SAPscript texts with the document class

“ general text” . To edit texts or create new ones, you need the corresponding authorizations for transaction SE61 (7RROV � $%$3�:RUNEHQFK � 8WLOLWLHV � 'RFXPHQWDWLRQ).

� If you want to maintain your own text, you use transaction SE16 to enter the technical name in table

UPS_CUSTTEXT (7RROV � $%$3�:RUNEHQFK � 2YHUYLHZ � 'DWD�%URZVHU). �

Note: You can also translate the texts into different languages if required.

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-23

SAP AG 2006


$W�WKH�FRPSOHWLRQ�RI�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�&RQFHSW�RI�WKH�6WDWXV�DQG�7UDFNLQJ�


7UDFNLQJ�6\VWHP

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 13-24

SAP AG 2006

6WDWXV�DQG�7UDFNLQJ�6\VWHP��6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�&RQFHSW�RI�WKH�6WDWXV�DQG�7UDFNLQJ�


7UDFNLQJ�6\VWHP

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 14-1

SAP AG 2006

$SSHQGL[��([HUFLVH 6FHQDULR

$SSHQGL[��([HUFLVH 6FHQDULR

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 14-2

SAP AG 2006

3ODQQHU�5ROHV�LQ�WKH�([HUFLVH�6FHQDULRV

&XVWRPHU�*URXS

*RRGV�*URXS&RPSDQ\�&RGH

&RQWUROOLQJ$UHD

.H\�$FFRXQW�0DQDJHU

*RRGV�*URXS&RPSDQ\�&RGH

&RQWUROOLQJ$UHD

6DOHV�0DQDJHU

&RPSDQ\�&RGH

&RQWUROOLQJ$UHD

&)2

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 14-3

SAP AG 2006

��

��

��

!!

"�#%$"�#&$

')( *,+�-/.�./013254�65-5.5./78:95;=<?> @BADC 95E

��=�F�� G�

HI� ��JHK�L��M��

��

NO�� JP � ��

QSR�TVU�W�U XZY�[]\3Y_^G[?`:aG^�b�cdR�^�eIWfR�U XgY�[LU�h�igY�U ^�Wkjlenm�U o�p3Y�U W�oVqd\3r:Y_^ []XgsG^ Wfo�^�^�R�Xfo [_^�i�but m3v3m�txwIq_^�[Gv3m�[dXGU ^ Wfyzw

{D|}~{?|)|�|{D|)|�|

�}�g�f��{?|)|�|{D|)|�|�)�}�f��{?|)|�|{D|)|�|{D| �}~{?|)|�|{D|)|�|

��f��

~

��g�3�3�n�S�l��3�

}}

�

��

�{?|)|�|{D|)|�|

�

�{?|)|�|{D|)|�|

{D|{?|)|�|{D|)|�|

�=}�� :�g�D� � �� G��G� � � �B��

Data record structure in the real-time InfoProvider –example for company code 1000

� ��J��

� � �_J�� #

��=��F� ¡O�=� � =��¢��g�_�u¡��¤£�� _J � � � �L� #¦¥�#¦§ NO� � ��J P � G��=£G��J�� ¨

© � �� J��¢� ¡��=� �=��Jª��M=�k« ��¬ �L� ¬ « �n¬® ¡��=£G��J�� = #¯

4XDQWLW\�3ODQQLQJ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 14-4

SAP AG 2006

0RGHOLQJ�4XDQWLW\�DQG�3ULFH�3ODQQLQJ

�� °��

H�� JHf��=M��

��=��

NO� � �gJP �G��

5HDO�WLPH�,QIR3URYLGHUIRU�SULFH�SODQQLQJ

5HDO�WLPH�,QIR3URYLGHUIRU�TXDQWLW\�SODQQLQJ

�� G� }�� }�{:± �G�B�]²�� }�³�± � � ��3²�� }=±:´ �G��3²

4XDQWLW\�3ODQQLQJ 3ULFH�3ODQQLQJH��GJHf��=M �

N�� JP � ��

��µ�� _��¶��_� �5� J��5� ¶ZJ�·

Goods groupCustomer groupControlling areaCompany code

¸ ��K¡5� ��M ��=·

Sales quantityRevenueContributionmargin 1

�nµ�� _��¶��]� �/� J��5� ¶3J�·

Goods groupCustomer group

¸ ��V¡�� M �L��·

Sales price per unit of quantityVariable cost of goods manufactured

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 14-5

SAP AG 2006

3ULFH�3ODQQLQJ 3URFHVV

¹ � �g��º��Z²� �Z�)�»�n¼��B�_²

¹ � �g��º��:²� �3�B�»� ¹Z� �)�:²

¹ � �g� ¹ �_� ´B�¹3� �)�3²

¹ � �g� ¹ �]� ´B�� G�x�3²

¹ � �g� ¹ �]� ´��¼��B�]²

�g�f��

¹ � �g�½ºO��Z²� �:�)�»� � �G��3²

��g��:�n�¾�»�G�Z�

H�� =�GJHf�L�¿M��

N � � �gJ P � ��

P � M�� G= ��»V£�� J�� ¿ #�Àk§ �¿�g�5� �� J�� ¶¢�� = �»G�

À�Á ��¿��V£�� J � � #�À ��g��®£�� _J�� #SÂu§��J�J � �°� J�� ¶K£G�G��J � ��

Â�Á�© ��£�� MG�g�5� �¿V¡�M��¶��5� �¿K¡��¿��Ãk��L��=��KÄ�M�� ¶g�z��g��£�� J=� �� #SÂ¥ ��¶3�=��L� �3¶��¿��5�L�¿�g��¡ �L��£G��»M�� V¡��G¶3�L�=��JG¨

Å�Á�P � �M��=�Z��Ä5M�J��®� ��G¡¿� ��_�ª�ª��_��/� ��£�� J=� �� #SÂ

¥dÆ�Á�" � � ��_�u� ��g��]�u¡��L�=�Ç£G� �]J�� = #SÂ ¨

��®�G¡�£�� J � �¿ #�À �� #�Â �»��L�£G��J�� #¯§ ¶��¿�JG�=�� g�L��®£�� ]J�� ¥ ��¶��G��L��Z¶�� g�5�L� �3��¡=J��G�� £G� �_J�� ¿�¨

�� G� }={ �� G� }G³ �� }

T T T

n

o

p

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 14-6

SAP AG 2006

� � ��J � � #

ÈgÉ:ÊË,Ì�Ë,ÍÎ]ÏlÏ_Ï

ÐË,Ì�Ë/ÍÑ_ÏlÏ_Ï

ÒG*?+D6Ó3Ô E/4Õ]Ö_× Ø

ÐË,Ì�Ë,ÍÑ_ÏlÏ_Ï

Ù,Ð ÓÚ?ÛO13Ú

ÜË/Ì�Ë,ÍÑ]ÏlÏ_Ï

' ÈZÉZÊË/Ì�Ë,ÍÎdÏdÏ]Ï

ÜË,Ì�Ë,ÍÎ]ÏlÏ_Ï

Ý�Ô?ÔxÞ EÝ C Ô A�ß

4XHU\

)2;


5HDO�WLPH�,QIR3URYLGHUIRU�SULFH�SODQQLQJ

�nµ�� ¶��]� �/� J��5� ¶3J�·

Goods groupCustomer groupControlling areaCompany code

¸ ��f¡5� ��M��_�=·

Sales quantityRevenueContributionmargin 1

�nµ�� _��¶��/� J�� ¶gJ�·

Goods groupCustomer group

¸ ��K¡�� ¿M ��·

Sales price per unit of quantityVariable cost of goods manufactured

0XOWL3URYLGHU

0XOWL3URYLGHU��&DOFXODWLRQ�RI�7XUQRYHU�DQG�&RQWULEXWLRQ�0DUJLQ

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 14-7

SAP AG 2006

0XOWL3URYLGHU��9HUVLRQ�&RS\�DQG�'LVWULEXWLRQ�RI�*RRGV�*URXSV�WR�&XVWRPHU�*URXSV�² 'LVWULEXWLRQ�ZLWK�5HIHUHQFH�'DWD�²

à�.5./.à�.5./.à�.5./.à�.5./.à�.5./.à�.5./.

ÓZÔ +/4 C Ô ( ( á> +,@�1�C 9/*

à�.5.5.à�.5.5.à�.5.5.à�.5.5.à�.5.5.à�.5.5.

Ó3Ôxâ ßD*/+,;Ó3ÔDÞ 9

ããããà�ä�-å,./../æÙ?Ð Óãããã-/ç�ää/æ/æ./-Ù?Ð Óãããã0?à-/./..?àÙ?Ð Ó

ããããä5å5-å,ç/../-ÚDÛO1gÚã

ã

ÈZÉè�é_ê ë�èLì

ã

ã

ÐZí ì è�î

ã

ã

Ðè�é_ê ë�è�ì

ï/-�0

å,-�0

ð í ì è�î

ãæ/./..?àÚDÛO1gÚ

ãä/ç/../æÚDÛO1gÚ

Üè�é�ê ëLè�ì

È3É:í ì è�îÓ A?E�4 Ôxâ 9/CÝ C Ô Axß

Ý�Ô?ÔxÞ EÝ C Ô Axß


5HDO�WLPH�,QIR3URYLGHUZLWK�DFWXDO�GDWD± UHIHUHQFH�GDWD�±

0XOWL3URYLGHU

� ¶�� Á£G��_J��

"¹ � �3�Sñ � ��3� ��

�

ò � ��£G� �]J�� ¿

�

ò � � £G��J��

#

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 14-8

SAP AG 2006

'LVWULEXWLRQ�ZLWK�5HIHUHQFH�'DWD�² 1XPHULF�([DPSOH��

-5./.�.à�å,.5.Ó A/E54 Ô�â 9,C@)C Ô A?ß

ó

ç5./.àL-/æ5æÓ A/E54 Ô�â 9,C@)C Ô A?ß

ó

ããããï5-/0ä�ç/../æÚDÛ�13Úà�./.�.à�.�./.

ãããããã.?àÙ?Ð Ó-5./.�.à�.�./.ãã

à�.�./.à�.�./.

à�.�./.à�.�./.à�.�./.

ÓZÔ +/4�C Ô ( á( > +,@1�C 9/*

à�./.�.à�./.�.

à�./.�.à�./.�.à�./.�.

Ó3Ôxâ ß?*,+,;Ó3ÔDÞ 9

ããããà�ä/-å5./../æÙ?Ð Óãããã-5ç/ää�æ/æ./-Ù?Ð Óãããã0,à-�./..?àÙ?Ð Ó

ããããä�å,-å5ç/../-ÚDÛ�13Úã

È3Éè�é_ê ë�è�ì

ã

Ðí ì è�î

ã

Ðè�é_ê ë�èLì

å/-/0

ð í ì è�î

ãæ�./..?àÚDÛ�13Ú

Ü è�é_ê ë�è�ì ÈZÉZí ì è�îÓ A/E54 Ô�â 9,CÝ C Ô ADß

Ý�ÔDÔDÞ EÝ C Ô ADß

�¿´ �L��3�)� � � �B�L� �G�x� ±³)|)|3±3{?³Bô)ô � {,|)|�õö{?÷ ² ³�ô�ø÷)ô)ô3±3{?³Bô)ô � {,|)|�õ � { ² ô�ô�øù |)|3±3{?³Bô)ô � {,|)|�õ¦ôB³ ² ù�ù ø

¹ � �g�n� � � �B�� ±ú3{:± � |)| � {D|�|�õû{D÷ ² ³xô�ø³ � ÷g± � |x| � {,|)|�õ � { ² ô)ô�ø{?÷)³g± � |x| � {,|)|�õüô�³ ² ù)ù ø

ý £G�G��¢þ3��V¡�� ¿M��L�¢��5µ��z�� F� J�¿� Jg�5�/�»ÿ Mg�L��¶�¶��=��ª��¢��£�� LþZ��K¡�� =M��z��u��µ��¶g��MG� �Z£�� LJ � �

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 14-9

SAP AG 2006

'HPR�6FHQDULR�LQ�6WDWXV�DQG�7UDFNLQJ�6\VWHP

&)2,GHV &RPSDQ\

6DOHV�6DOHV�0DQDJHU�86$�0DQDJHU�86$�

.H\�$FFRXQW�0DQDJHU�86$�1RUWK�

¸ �� ¶�¶�� M ��P �� ! N �ý ��J��

¸ �� ¶�¶�� M��P ��G� � ! N �«¦��J��

¸ �� ¶�¶�� M ��P � ��G� � ! N �NS�=M��5µ

NO� � �gJ P ��G��G� �ý M �L��G�

N � � ��J P � �� J=� �

�� í è5î��

� �� ë í� ë � ê �� ë í

9HUVLRQ�(

�� í è5î��

� �� î� � � �� î

5HVSRQVLELOLW\�KLHUDUFK\

3ODQQLQJ�KLHUDUFK\

3DUWLFLSDWLQJ�SODQQHUV

��=±)� }g�uô��B|:�! ¼¹ �B�)��" ±�� }��Vô��)|

��#��=±B��}��Vô$�B|��&% º �('¹ �B�)��" ±�� }g�Vô��)|

��)��±)�G}��Vô$��|�*#��+��=�¹ �B�B��" ±B��}��Kô��)|

)�\HDU��

�

I n t

e r

n a

l

U s

e

S A

P

P a

r t

n e

r

O n

l y I n

t e r n a l U

s e S A

P P

a r t n e r O

n l y

© SAP AG BW370 14-10

Date post:	14-Jun-2015
Category:	Technology
Upload:	maheshn
View:	1,583 times
Download:	1 times