Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
'%:(
6$3 %, (QWHUSULVH 'DWD :DUHKRXVLQJ 'HOWD %: WR 6$3 1HW:HDYHU V %,
SAP AG 2006
2006/Q2
&RS\ULJKW
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
SAP AG 2006
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. 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.
&RXUVH 3UHUHTXLVLWHV
(VVHQWLDO
3DUWLFLSDQWV VKRXOG DOUHDG\ KDYH VRPH NQRZOHGJH RI WKH IHDWXUHV RI 6$3 %: % SDUWLFXODUO\ WKRVH UHODWLQJ WR %: :DUHKRXVH 0DQDJHPHQW
SAP AG 2006
7DUJHW $XGLHQFH
&XVWRPHUV
'XUDWLRQ GD\V
SAP AG 2006
8VHU QRWHV These training materials are QRW D WHDFK\RXUVHOI SURJUDP. They complement the explanations provided by your course instructor. 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.
&RXUVH 2YHUYLHZ
&RQWHQWV
&RXUVH *RDOV
&RXUVH 2EMHFWLYHV &RXUVH &RQWHQW &RXUVH 2YHUYLHZ 'LDJUDP 0DLQ %XVLQHVV ([DPSOH
SAP AG 2006
SAP AG
DBW70E
1-1
&RXUVH *RDOV
SAP AG 2006
SAP AG
DBW70E
1-2
(hgg i3f F Y1c1%E821T`3EP3!y8i%%21%qEy)p3!B#A 2 G d b R " 0 R A A W ' ( ( A " A ( ' " H ( h g g f v A Y i3%i%awTd F b R ' 6 $ " " ( ( ( 0 ' ( " @ A ' " H 1Bq"2 88%q"U2%11)q")3!2y8 U3y)q"pp3!B#A 2 G F I ( h g g f v A Y d b R " $ " r ( iE%i%awX18#%#qs)yXy8 V 9s23&3!B#A 2 G @ A A ' " H F ( 0 A R I r " A ' " ' " H 2%2E2Cq"33%3283!B#A 2 G ( h g g f v A Y d b R " 3i3%i3wTe18# F ( @ R W 6 ' ' 6 4 ( @ R A A W " ' " H 3`aT78%A ysq&c &yi%7&1CEEy%%1&3!B#A 2 G (hgg 2i3f F Y dbcy%y%"%!1p%q"1%acES3!2%&323q"E3P3!B#A 2 G R ' @ Y $ ( 0 ' A Y A A W ' A ( 0 ' " H ( 0 ' A Y A A W ' ( ( %a`Epy( !2!2" G 3V2ypi332A A %v VtC!( q"%p%"8)s32!T3%C1% EyPp3!2%xt w%%8&%v u F r A r A " 0 " A ( ' 6 v v " A F 0 ' A A A ' ( ( A $ " r A ' " H 3(1%2CaY`EWp%( !2!C" G %!2%pt3%2P%#s2S&q"pp3!B#A 2 G (hgg i3f F Y b " decRB#2'V &8%"#01%'2a`X)3( U2V" G U2%TSQ P3!B#A 2 G 6 $ ( A Y A A W A " R I ' " H D @ A @ 6 0 5 4 ( 0 ' $ " EC7 2B33 9871%3321)( !&%#!
SAP AG
SAP AG 2006
&RXUVH 2EMHFWLYHV
DBW70E
1-3
F F F F F F F F F F F F F F
" $ A " A i 5 p " A "I ( $ A P%33y7p y%i3C P1sC3p1t9E1C` 1%!( $ A R " p A d $ ( 0 ' A Y A A W ( ' H 31`3#TTo%q"31%7EP3( !2V" G 3iA p3VBq"2A 2 G " A !itn s!p%P1C3%21C2B( #y2&q"2A 2 G " A r " 0 A A r H ( h g g f Y d b R ' 6 A I ' " ' H 3ij1epq"! p1C 3h)3V2y%13B3VBq"2A 2 G 23y21C!3( 2q"me3!2y& ! qs223B3VBq"2A 2 G A r ' ( @ A A ' H (hggf Y d b R " ' 6 " 3fcB92! 8B1 ! ( 21he3EP) t3TEy%13B3VBq"2A 2 G 0 l A A W Q A k " ' H ( ! #s2238%3&i1t3C#1B3VBq"2A 2 G @ A A ( ( A A A r r ' H ( h g g f Y d b R ( 0 A A ' ( ( ' H 3fE2y82`q"y32&32C2p3VBq"2A 2 G (hggf Y fd b R ( ( b ( " A Q A A W ' " ( 0 A $ r " A ' ' H 1y&%2CTET`CT)3U`#P2Vt3&%q"92y23TCU2`3VBq"2A 2 G ( h g g f Y d b R " ( ( b ( " A Q A A W ' H ij1a1y231p32ETCi3E8Tp3VBq"2A 2 G " ( v " 0 ( A i " g H 1 22%13BC227Ey 2hPq"2A 2 G " $ " " A ( " A ' ( 3#%2&1 !P1C273!2y& ! qs223B3VBq"2A 2 G @ A A ' H ( h g g f Y d b R " ' 6 ( v R @ Y r " A ' ( f189! 8B EB2%iy3C&%cE2 p3!83q@Vy%TW (hggf Y d b R ( 3i3f11yp V qs223B32q"p 9CCiA !73!83q@Vy%TW @ A A A ' ( 0 21%( A Ari%3"2apA e33231 !iA Cp)Cd%iP3yiwTd " W v ( A @ A A r A " A ( 5 ( I ( h g g f v A Y b R " A " " " ( A @ A A r A " 6 ' ( &dC!`1 !331&%81p% 2 C3%S3q@Vy%TW
SAP AG
SAP AG 2006
&RXUVH 2EMHFWLYHV
DBW70E
1-4
3UHIDFH ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 'DWD 0RGHOLQJ 'DWD $FTXLVLWLRQ 7UDQVIRUPDWLRQ DQG 8QLW RI 0HDVXUH &RQYHUVLRQ 'DWD )ORZ &RQWURO $GPLQLVWUDWLRQ DQG 0RQLWRULQJ 3HUIRUPDQFH 2SWLPL]DWLRQ ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
1-5
<RXU FRPSDQ\ KDV EHHQ XVLQJ 6$3 %: [ DV D GDWD ZDUHKRXVH SODWIRUP 8VHUV KDYH PDGH JRRG XVH RI WKH H[LVWLQJ IXQFWLRQDOLW\ EXW DUH ORRNLQJ IRU WHFKQRORJLFDO HQKDQFHPHQWV WR LPSURYH HDVH RI PRGHOLQJ DQG DGPLQLVWUDWLRQ DQG PRYH WRZDUGV DQ HQWHUSULVHZLGH GDWD ZDUHKRXVH HQYLURQPHQW <RX KDYH EHHQ DVNHG WR HYDOXDWH WKH QHZ IXQFWLRQDOLW\ SURYLGHG E\ 6$3 1HW:HDYHU V ZLWKLQ WKH VFHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ WR GHWHUPLQH ZKLFK IHDWXUHV ZLOO EH PRVW YDOXDEOH WR \RXU FRPSDQ\ DQG KRZ WKH\ PD\ EH LQWHJUDWHG LQWR LWV GDWD ZDUHKRXVH VWUDWHJ\
SAP AG 2006
SAP AG
DBW70E
1-6
&RQWHQWV
SAP AG 2006
SAP AG
DBW70E
2-1
,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 8QLW 2EMHFWLYHV
*LYH EHQHILWV IRU WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
2XWOLQH WKH SURFHVV RI WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
([SODLQ WKH SXUSRVH RI WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
*LYH DQ RYHUYLHZ RI WKH PRVW LPSRUWDQW UXQWLPH DQG DGPLQLVWUDWLYH DVSHFWV RI WKH (QWHUSULVH 'DWD :DUHKRXVH
SAP AG 2006
SAP AG
DBW70E
2-2
,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V &RXUVH 2YHUYLHZ 'LDJUDP
3UHIDFH ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 'DWD 0RGHOLQJ 'DWD $FTXLVLWLRQ 7UDQVIRUPDWLRQ DQG 8QLW RI 0HDVXUH &RQYHUVLRQ 'DWD )ORZ &RQWURO $GPLQLVWUDWLRQ DQG 0RQLWRULQJ 3HUIRUPDQFH 2SWLPL]DWLRQ ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
2-3
,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V %XVLQHVV ([DPSOH
2QH RI WKH PDMRU FKDOOHQJHV %XVLQHVV ,QWHOOLJHQFH %, FXVWRPHUV IDFH WRGD\ LV WKH LQWHJUDWLRQ RI GLIIHUHQW VRXUFH V\VWHPV LQ RQH (QWHUSULVH 'DWD :DUHKRXVH ODQGVFDSH 7KH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ (': RI 6$3 1HW:HDYHU V HQDEOHV WKH %, FXVWRPHU WR FUHDWH DQG RSHUDWH D GDWD ZDUHKRXVH LQ DQ HQWHUSULVHZLGH KHWHURJHQHRXV HQYLURQPHQW 7KH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ VWUXFWXUHV LQWR WZR VFHQDULR YDULDQWV ZKLFK FRYHU GHVLJQ WLPH PRGHOLQJ LPSOHPHQWDWLRQ DQG UXQWLPH DVSHFWV RI D KLJKO\ IOH[LEOH UHOLDEOH UREXVW DQG VFDODEOH %, VROXWLRQ (': FRYHUV DOO VWHSV D V\VWHP DGPLQLVWUDWRU UHTXLUHV WR VHW XS VXFK D %, VROXWLRQ DQG HDVLO\ DGPLQLVWHU LW
SAP AG 2006
SAP AG
DBW70E
2-4
,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1: V 8QLW 2YHUYLHZ 'LDJUDP ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V
/HVVRQ ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1: V
SAP AG 2006
SAP NetWeaver is depoyed along IT practices, according to specific business objectives. One of those practices is Business Information Management. For organizations to manage the business information needs, they typically require three things: 1. Enterprise data warehousing 2. Enterprise reporting, query and analysis 3. A framework for business planning
In this lesson and throughout the coming units, we deal with the first aspect: Enterprise Data Warehousing
SAP AG
DBW70E
2-5
*LYH EHQHILWV IRU WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
2XWOLQH WKH SURFHVV RI WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
([SODLQ WKH SXUSRVH RI WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
*LYH DQ RYHUYLHZ RI WKH PRVW LPSRUWDQW UXQWLPH DQG DGPLQLVWUDWLYH DVSHFWV RI WKH (QWHUSULVH 'DWD :DUHKRXVH
SAP AG 2006
SAP AG
DBW70E
2-6
&RPELQHV VWUDWHJLF DQDO\VHV DQG RSHUDWLRQDO UHSRUWLQJ HQDEOLQJ WKH EXVLQHVV WR UHSRUW UHDOWLPH )DFLOLWDWHV GHVLJQWLPH DV ZHOO DV UXQWLPH RI %, PRGHOV DQG SURFHVVHV ,QWHJUDWHV KHWHURJHQHRXV V\VWHPV
&RYHUV DOO VWHSV DQ DGPLQLVWUDWRU UHTXLUHV WR VHW XS D KLJKO\ IOH[LEOH UREXVW DQG VFDODEOH %, VROXWLRQ DQG HDVLO\ DGPLQLVWHU LW
SAP AG 2006
Why Enterprise Data Warehousing? One of the major challenges Business Intelligence (BI) customers face today is the integration of different source systems in one Enterprise Data Warehouse landscape. Not only different heterogeneous technical platforms must be interfaced, but also different master and transaction data semantics must be consolidated. In addition, an Enterprise Data Warehouse must provide flexible structures and layers in order to adapt quickly to new business challenges (such as changed objectives, mergers, acquisitions etc) Beyond these designtime aspects, Enterprise Data Warehousing should facilitate the administration and monitoring of all processes (such as load processes, distribution of data etc) and proactively help with handling possible performance issues especially regarding increasingly sophisticated data volume requirements.
SAP AG
DBW70E
2-7
3URFHVVHV
0RQLWRULQJ
SAP AG 2006
There are two scenario variants: Modeling the Enterprise Data Warehouse Describes processes like data modeling, data acqusiition, data cleansing/transformation, data distribution and meta data and document management. This process variant requires BI usage type.
Running the Enterprise Data Warehouse Describes processes like controlling the data flow, administration and monitoring, performance optimization (including BI accelerator), information lifecycle management and user management (authorizations). This process variant requires BI and EP usage type.
SAP AG
DBW70E
2-8
'DWD $FTXLVLWLRQ DFFHVVLQJ DQG LQWHJUDWLQJ LQIRUPDWLRQ IURP KHWHURJHQHRXV GDWD VRXUFHV 7UDQVIRUPDWLRQ 0HWD 'DWD 'DWD 'LVWULEXWLRQ
'DWD 0RGHOLQJ
'RFXPHQW 0DQDJHPHQW
SAP AG 2006
Data Modeling Involves modeling / re-modeling (*) data warehouse layers Data Acquisition: Accessing and Integrating information from heterogeneous data sources Connectivity is made to virtually all data sources (enhanced data source concept) (*) Transformation Flexible Transformation capabilities (enhanced *) Data Distribution Open Hub Service Meta Data & Document Management Meta data integration from and to other SAP BI data marts Generation of documentation Sophisticated search functionality in conjunction with KM searching technology
SAP AG
DBW70E
2-9
$GPLQLVWUDWLRQ DQG 0RQLWRULQJ 'DWD $FTXLVLWLRQ DFFHVVLQJ DQG LQWHJUDWLQJ LQIRUPDWLRQ IURP KHWHURJHQHRXV GDWD VRXUFHV ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW 8VHU 0DQDJHPHQW 3HUIRUPDQFH 2SWLPL]DWLRQ
SAP AG 2006
Data Flow Control Defining the Data Transfer Process (*) Setting up process chains (enhanced *) Real-time data acquisition (*)
Performance Optimization BI Accelerator: Speeding up BI query performance by orders of magnitude (*) Aggregate Definition and Maintenance Caching DB Tool Support (statistics, indices etc)
Information Lifecycle Management Near-Line storage (*) and archiving User Management Standard authorizations for warehouse modeling and administration
Analysis authorizations (for end users) (revised *) (*) = New for SAP NetWeaver 2004s
SAP AG DBW70E 2-10
SAP AG 2006
The Corporate Information Factory defined by William H. Inmon and Claudia Imhoff is a common accepted fundament to define stable corporate information system architecture. CIF - The Data Warehouse 7KH 'DWD :DUHKRXVH LV D VXEMHFWRULHQWHG LQWHJUDWHG WLPHYDULDQW QRQYRODWLOH FROOHFWLRQ RI GDWD XVHG WR VXSSRUW WKH VWUDWHJLF GHFLVLRQPDNLQJ SURFHVV IRU WKH HQWHUSULVH ,W LV WKH FHQWUDO SRLQW RI GDWD LQWHJUDWLRQ IRU EXVLQHVV LQWHOOLJHQFH DQG LV WKH VRXUFH RI GDWD IRU WKH GDWD PDUWV GHOLYHULQJ D FRPPRQ YLHZ RI HQWHUSULVH GDWD CIF - Primary Storage Management 3ULPDU\ 6WRUDJH 0DQDJHPHQW FRQVLVWV RI WKH SURFHVVHV WKDW PDQDJH GDWD ZLWKLQ DQG DFURVV WKH GDWD ZDUHKRXVH DQG RSHUDWLRQDO GDWD VWRUH ,W LQFOXGHV SURFHVVHV IRU EDFNXS DQG UHFRYHU\ SDUWLWLRQLQJ VXPPDUL]DWLRQ DJJUHJDWLRQ DQG DUFKLYDO DQG UHWULHYDO RI GDWD WR DQG IURP DOWHUQDWLYH VWRUDJH CIF - Data Mart 7KH 'DWD 0DUW LV FXVWRPL]HG DQGRU VXPPDUL]HG GDWD GHULYHG IURP WKH GDWD ZDUHKRXVH DQG WDLORUHG WR VXSSRUW WKH VSHFLILF DQDO\WLFDO UHTXLUHPHQWV RI D EXVLQHVV XQLW RU IXQFWLRQ ,W XWLOL]HV D FRPPRQ HQWHUSULVH YLHZ RI VWUDWHJLF GDWD DQG SURYLGHV EXVLQHVV XQLWV PRUH IOH[LELOLW\ FRQWURO DQG UHVSRQVLELOLW\ 7KH GDWD PDUW PD\ RU PD\ QRW EH RQ WKH VDPH VHUYHU RU ORFDWLRQ DV WKH GDWD ZDUHKRXVH CIF - Operational Data Store (ODS) 7KH 2SHUDWLRQDO 'DWD 6WRUH LV D VXEMHFWRULHQWHG LQWHJUDWHG FXUUHQW YRODWLOH FROOHFWLRQ RI GDWD XVHG WR VXSSRUW WKH WDFWLFDO GHFLVLRQPDNLQJ SURFHVV IRU WKH HQWHUSULVH ,W LV WKH FHQWUDO SRLQW RI GDWD LQWHJUDWLRQ IRU EXVLQHVV PDQDJHPHQW GHOLYHULQJ D FRPPRQ YLHZ RI HQWHUSULVH GDWD
DBW70E 2-11
SAP AG
! ) ' 5%4 A% G $ # ) $ "aA) 2# $ c b $E SD Q P# W56 I # $ V U $ 6 $# R "50 %TS%5 G 6# X Wa`Y% G @ $ $ %9W %# ! Q 5$ (P 2 I $ ) %# HCF%5 G # $ E 5%FD
'DWD :DUHKRXVH
0RQLWRULQJ $GPLQLVWUDWLRQ
%, $UFKLWHFWXUH 3ODWIRUP
$QDO\WLF (QJLQH
'DWD :DUHKRXVH
SAP AG
SAP AG 2006
'DWD $FTXLVLWLRQ
DBW70E
2-12
%, $FFHOHUDWRU
SAP AG 2006
Now the InfoPackage only can load data from Source System to PSA - without any transformation From there onwards a Data Transfer Process handles data distribution within SAP NetWeaver BI. Features and benefits of this approach are Loading data from one (persistent) layer to others Separation of delta mechanism for different data targets Enhanced filtering in dataflow Improved transparency of staging processes across data warehouse layers (PSA, DWH layer, ODS layer, Architected Data Marts) Improved performance: optimized parallelization Enhanced error handling for DataStore object (error stack) Repair mode based on temporary data storage
SAP AG
DBW70E
,QIR6RXUFH
' $ # ) Q ! ) WI % 15H G
p $ 6 V ) $ # %A5H 1)
t p f 6 # q srqH# W5%1d
3URFHVV &KDLQ
Pw WHsk" & }w yx uwu y} { s &u k& yw rHP q {w y s &kH w P&P&P& Pk w }u | &Px&&C9 q y w }u "sw &x k& u y }kk k&u fu zv w ~ }| { yxwvvu ts P& qr
s }w ~ } 1sk & k&u | (y & yw { k Pu qzv kk k&u fu zv }w ~ }| { }s(P4sw s & q w yuyvw zs } y ys s"" H } q w t { y &x s &su zv yvw zs &4&w k P q s s& }w 4 Hw Ww u q yx } y Hr&4&w k P q y yvw zs &w %u zv yx { yv yvu t w &w &Pv kH w & ~ kW q y yx s d g e h f417&5
h n o l n r 3&r(kim
h h h j r 3 l iki 7&5
d 5 47&1s
%,
3,
z yz yxwvv u ts 5u WHskk q
(3 .0 75(;
SAP AG
SAP AG 2006
DBW70E
2-14
wx } Pw&Pkuk1P u PkCv ( yu &" y } vu } { xu u ky &x }u P } sv 4 y y ws s q wwx } P&ku w s&&ks q wxs
v skx wx } yws ku PP q v x y u (y k &kP H w } w {ws " y sw " v rP q ks ksuu v & s {u }w ~ }| { z } { y w {w s u P v rW q
d n kk 9l
k4 d sk(o f g h h n o r 3&7i(
g n go r(3rs0 "7s5
(3 .0 75(;
SAP AG
SAP AG 2006
%,
DBW70E
2-15
*LYH EHQHILWV IRU WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
2XWOLQH WKH SURFHVV RI WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
([SODLQ WKH SXUSRVH RI WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
*LYH DQ RYHUYLHZ RI WKH PRVW LPSRUWDQW UXQWLPH DQG DGPLQLVWUDWLYH DVSHFWV RI WKH (QWHUSULVH 'DWD :DUHKRXVH
SAP AG 2006
SAP AG
DBW70E
2-16
,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 8QLW 6XPPDU\
*LYH EHQHILWV IRU WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
2XWOLQH WKH SURFHVV RI WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
([SODLQ WKH SXUSRVH RI WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ RI 6$3 1: V
*LYH DQ RYHUYLHZ RI WKH PRVW LPSRUWDQW UXQWLPH DQG DGPLQLVWUDWLYH DVSHFWV RI WKH (QWHUSULVH 'DWD :DUHKRXVH
SAP AG 2006
SAP AG
DBW70E
2-17
SAP AG
DBW70E
2-18
'DWD 0RGHOLQJ
&RQWHQWV
SAP AG 2006
SAP AG
DBW70E
3-1
'LVFXVV WKH FKDQJHV DQG HQKDQFHPHQWV IRXQG LQVLGH WKH 'DWD :DUHKRXVLQJ :RUNEHQFK RI 6$3 1: V ([SODLQ WKH FRQFHSW RI 'DWD6WRUH 2EMHFWV ZLWKLQ 6$3 1: V
'HVFULEH WKH IXQFWLRQDOLWLHV RI WKH &RQWHQW $QDO\]HU DQG &RQWHQW %URZVHU ZLWKLQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
3-2
3UHIDFH ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 'DWD 0RGHOLQJ 'DWD $FTXLVLWLRQ 7UDQVIRUPDWLRQ DQG 8QLW RI 0HDVXUH &RQYHUVLRQ 'DWD )ORZ &RQWURO $GPLQLVWUDWLRQ DQG 0RQLWRULQJ 3HUIRUPDQFH 2SWLPL]DWLRQ ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
3-3
<RX QHHG WR H[SORUH WKH QHZ 'DWD :DUHKRXVLQJ :RUNEHQFK WR VHH KRZ WKLV KDV FKDQJHG IURP WKH [ $GPLQLVWUDWRU :RUNEHQFK <RX QHHG WR XQGHUVWDQG 'DWD6WRUH 2EMHFWV ZKLFK KDYH VXFFHHGHG [ 2'6 2EMHFWV
<RX ZLVK WR H[DPLQH KRZ ,QIR6HWV KDYH EHHQ HQKDQFHG ZLWKLQ 6$3 1: V <RX ZDQW WR VHH KRZ WKH 5HPRGHOLQJ 7RROER[ FRXOG DVVLVW \RX LQ FKDQJLQJ \RXU GDWD PRGHO LI QHZ LQIRUPDWLRQ UHTXLUHPHQWV UHTXLUH LW
SAP AG 2006
<RX QHHG WR ZRUN ZLWK WKH &RQWHQW $QDO\VHU DQG &RQWHQW %URZVHU WR VHH ZKDW FRQWHQW LV DYDLODEOH IRU D JLYHQ DUHD KRZ VWDQGDUG RU FXVWRPHUGHILQHG %, FRQWHQW LV EHLQJ XVHG LQ \RXU V\VWHP DQG FKHFN LQFRQVLVWHQFLHV
SAP AG
DBW70E
3-4
'DWD 0RGHOLQJ
/HVVRQ 'DWD :DUHKRXVLQJ :RUNEHQFK /HVVRQ 'DWD6WRUH 2EMHFWV /HVVRQ ,QIR6HWV /HVVRQ 5HPRGHOLQJ 7RROER[ /HVVRQ %XVLQHVV &RQWHQW
SAP AG 2006
SAP AG
DBW70E
3-5
/LVW WKH FKDQJHV DQG HQKDQFHPHQWV IRXQG LQVLGH WKH 'DWD :DUHKRXVLQJ :RUNEHQFK RI 6$3 1: V 5HFLWH WKH WHUPLQRORJ\ LQWURGXFHG LQ WKH 'DWD :DUHKRXVLQJ :RUNEHQFK
SAP AG 2006
SAP AG
DBW70E
3-6
'DWD PRGHOLQJ VXSSRUWV DQG IDFLOLWDWHV KLJKO\ IOH[LEOH DQG FRPSUHKHQVLYH LQIRUPDWLRQ PRGHOV 7KH 6$3 1: V WHFKQRORJ\ VXSSRUWV DQ HQKDQFHG XVHU LQWHUIDFH ZLWK D QXPEHU RI HQKDQFHG SHUVRQDOL]DWLRQ DQG QDYLJDWLRQ IHDWXUHV +HUH \RX ZLOO EH LQWURGXFHG WR WKHVH DQG DFFRPSDQ\LQJ WHUPLQRORJ\ QHZ LQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
3-7
2EVROHWH )HDWXUHV
SAP AG 2006
Reporting Agent functionality has moved to Information Broadcasting and for this see the scenario Enterprise Query, Reporting and Analysis Note: The Old Admin Workbench is still available via transaction RSA1OLD
SAP AG
1HZ REMHFW QDYLJDWLRQ REMHFW WUHH RQ OHIW VLGH DSSOLFDWLRQ 8, LQWHJUDWHG RQ ULJKW VLGH 'DWDIORZ H[SDQVLRQ LQ DOO WUHHV %URZVHUOLNH QDYLJDWLRQ ZLWKLQ REMHFW KLVWRU\ )DYRULWHV IRU XVHULQGLYLGXDO %, REMHFWV 3HUVRQDOL]HG YLHZ VHWWLQJV (QKDQFHG 6HDUFK FDSDELOLWLHV
,QIR3DFNDJH JURXS UHSODFHG E\ 3URFHVV &KDLQV (YHQW &KDLQV UHSODFHG E\ 3URFHVV &KDLQV 36$ WUHH 36$ GLUHFWO\ DFFHVVLEOH IURP 'DWD6RXUFH
DBW70E
3-8
SAP AG 2006
SAP Service Marketplace alias /bi Documentation Changed Terminology for SAP NetWeaver 2004s BI
SAP AG
DBW70E
3-9
'DWD :DUHKRXVLQJ :RUNEHQFK 0RGHOLQJ $GPLQ 9LHZ 'DWD :DUHKRXVLQJ :RUNEHQFK ZLWK 6$3 1HW:HDYHU V
0RGHOLQJ DQG $GPLQLVWUDWLRQ YLHZ
SAP AG 2006
In the 0RGHOLQJ and $GPLQLVWUDWLRQ functional areas you can display the navigation area and, if applicable, the corresponding object tree in the left-hand area of the screen when you call applications. This means that you can use the tree to start new applications, without leaving the application you are in.
SAP AG
DBW70E
3-10
'DWD :DUHKRXVLQJ :RUNEHQFK 6$3 1HW:HDYHU V DQG 6$3 %: [ 2EMHFWV
6$3 %: [ ,QIR6RXUFH
SAP AG 2006
In addition to new SAP NetWeaver 2004s technology, the SAP BW 3.x objects are still available and supported InfoSource DataSource Transformation / Update Rules etc.
SAP AG
DBW70E
3-11
'DWD6RXUFHV 7UHH
'DWD6RXUFHV 7UHH
SAP AG 2006
The DataSources tree replaces PSA tree. PSA maintenance is integrated in DataSources tree Via context menu Manage or Via DataSource Maintenance PSA The DataSource tree is shown for a particular source system
SAP AG
DBW70E
3-12
3HUVRQDOL]DWLRQ )DYRULWHV
)DYRULWHV
SAP AG 2006
In Favorites any kind of object (including application areas) can be included Via Drag & Drop or via button Add to Favorites
SAP AG
DBW70E
3-13
SAP AG 2006
You can hide navigation panes after navigation and / or hide the tree after navigation. A separate pushbutton allows for the hiding or showing of the navigator (see next slide).
SAP AG
DBW70E
3-14
SAP AG 2006
Additional Features
Browser-like navigation is available. Last Navigation step is stored and will be used as initial view for next login Hide empty tree folders icon: you can choose to hide or show application components and InfoAreas that do not have lower-level BI objects When in a detail screen you can access options to hide/show the navigator and to show/hide the tree display
SAP AG
DBW70E 3-15
SAP AG 2006
Now one can see the data flow expansion in one view from the object to the source. This also features components of MultiProviders, InfoSets, InfoObjects, Aggregation Levels etc.
SAP AG
DBW70E
3-16
SAP AG 2006
This also applies to lower level objects where from the DataSource one sees below it the data flow upwards to the InfoProvider
SAP AG
DBW70E
3-17
1DYLJDWLRQ
%DVLF 1DYLJDWLRQ
-XPS WR FRUUHVSRQGLQJ WUHH
SAP AG 2006
For each object that you select in the dataflow of a particular tree, you can choose a pushbutton to jump to the tree that contains the object. For example, in the InfoProvider tree, you can select a DataSource and jump straight to the corresponding position in the DataSource tree. The system displays the DataSource and its dataflow.
SAP AG
DBW70E
3-18
SAP AG 2006
Editing an InfoCube now resembles the maintenance dialog that will be familiar from 3.x ODS Objects (NW 2004s: DataStore Objects). The user interfaces for maintaining InfoCubes, DataStore objects, MultiProviders, and InfoObject Catalogs have been standardized for SAP NetWeaver 2004s. The screen is divided; the InfoObjects that can be transferred are displayed in a tree structure in the left-hand area of the screen and can be transferred to the right-hand area of the screen using drag and drop.
You access object maintenance as before in the 0RGHOLQJ area of the Data Warehousing Workbench.
SAP AG
DBW70E
3-19
SAP AG 2006
Key Figure Hierarchies within InfoCubes and DataStore Objects can also be used in Query Design
SAP AG
DBW70E
3-20
7UHH 6HDUFK
7UHH 6HDUFK
SAP AG 2006
A quick search within the tree is offered. The search function in the 0RGHOLQJ functional area allows you to search the object categories and object types for objects that contain a particular character string. The system displays the objects found, along with their dataflow.
SAP AG
DBW70E
3-21
*HQHULF 6HDUFK
*HQHULF 6HDUFK
SAP AG 2006
There is a generic search as seen in the navigation pane. This allows, for example, global (ie Source System independent) DataSource search.
SAP AG
DBW70E
3-22
/LVW WKH FKDQJHV DQG HQKDQFHPHQWV IRXQG LQVLGH WKH 'DWD :DUHKRXVLQJ :RUNEHQFK RI 6$3 1: V 5HFLWH WKH WHUPLQRORJ\ LQWURGXFHG LQ WKH 'DWD :DUHKRXVLQJ :RUNEHQFK
SAP AG 2006
SAP AG
DBW70E
3-23
SAP AG
DBW70E
3-24
'DWD 0RGHOLQJ
/HVVRQ 'DWD :DUHKRXVLQJ :RUNEHQFK /HVVRQ 'DWD6WRUH 2EMHFWV /HVVRQ ,QIR6HWV /HVVRQ 5HPRGHOLQJ 7RROER[ /HVVRQ %XVLQHVV &RQWHQW
SAP AG 2006
SAP AG
DBW70E
3-25
([SODLQ WKH FRQFHSW RI 'DWD6WRUH 2EMHFWV ZKLFK ZLOO UHSODFH 2'6 2EMHFWV LQ 6$3 1HW:HDYHU V
SAP AG 2006
SAP AG
DBW70E
3-26
7KH 2'6 2EMHFW SOD\HG DQ LPSRUWDQW UROH LQ IRUPHU YHUVLRQV RI %, :DUHKRXVH 0DQDJHPHQW 7KLV KDV EHHQ VXFFHHGHG E\ D FRPSDWLEOH EXW VXSHULRU REMHFW W\SH 'DWD6WRUH 2EMHFW LQ 6$3 1: V 7KH WHUPLQRORJ\ LV LQ OLQH ZLWK JHQHULF GDWD ZDUHKRXVLQJ DQG WKH 'DWD6WRUH 2EMHFW RIIHUV FHUWDLQ SHUIRUPDQFH LPSURYHPHQWV DV ZHOO DV HQKDQFHG FDSDELOLWLHV LQ DQDO\VLV
SAP AG 2006
SAP AG
DBW70E
3-27
'DWD6WRUH 2EMHFW IXOO\ FRPSDWLEOH WR IRUPHU 2'6 2EMHFW QR PLJUDWLRQ QHHGHG (QKDQFHG FDSDELOLWLHV
SAP AG 2006
The DataStore object with SAP NetWeaver 2004s BI is the successor object of the former ODSObject. The major enhancement is that there are various types to define the DataStore Object: Standard type with known tables (Active, Change Log and Activation table); Direct update with only the active table usable for analysis processes (Analysis Process Designer); Write optimized with only the active table usable as EDW layer or for large amounts of records.
Also there are some more technical enhancements: No join with Request SID table is necessary the surrogate ID remains within the activation queue instead of a GUID creation for the generated key Former releases did not allow a rollback in parallel the DataStore object allows for processing of an activation of data packages in parallel for every task There is a new monitor concept for administrative purposes Also there is a new concept for runtime parameters.
SAP AG
tu$VUVSS"%Bs'P&CTB0#H 04r4I7"P CB E0 ($C"4C%6C%Bp@CR%B C)D W3 &$ $ 3$ $ 35 & B5q i 0&B (CB%6d ($ $6h&1CEB 0CFG7B 6fCB e04($R4c! 14CB "R%B Cba4Y9 g ' $ &B D '$ S@B & $d 3& 3 0&B D `X W3$ S @ & DH 0 3&$ 8 4VUTSC%B6CEBI F%B1GD )4FEDC%BA@119 & $ $ $' @ & DH 0 3&$ 8 RB E0 H Q0#3 P($4"CEBI F%B1GD )4FEDC%BA@119
7HFKQLFDO HQKDQFHPHQWV
'DWD6WRUH 2EMHFW IRU GLUHFW XSGDWH UHSODFHV IRUPHU WUDQVDFWLRQDO 2'6 REMHFW
6XFFHVVRU REMHFW WR IRUPHU 2'6 2EMHFW 1DPH FKDQJH DOLJQV WR ZLGHO\VSUHDG 'DWD :DUHKRXVLQJ WHUPLQROJ\
'DWD6WRUH 2EMHFWV FDQ EH XVHG LQ DQDO\VHV UHJDUGOHVV RI VHWWLQJV DQG W\SH 1HZ 'DWD6WRUH 2EMHFW W\SH ZULWHRSWLPL]HG
DBW70E
3-28
SAP AG 2006
The DataStore navigation with its context sensitive menu is enlarged to provide more functionality In the same way as the InfoCube all basic functions are available at first: Display Change Copy Delete
To Copy an InfoCube is not necessary to use an InfoCube as template anymore. Also here there is a direct access from the context menu to display the data (via listcube functionality) without walking through the administrative monitor. Create Transformations is the way to perform the EDW modeling more detail about this in a later unit. Additional functions are available for Create update rules as in versions 3.x, Create Export DataSources as in versions 3.x and To maintain classic InfoSets.
New settings within SAP Netweaver 2004s BI: Whenever there is no data loaded into the DataStore object the type of this object can be switched (e.g. from standard to direct update or write-optimized).
SAP AG
2dqpsx fu w 6wx qyx #w9 g { z dd w w v po umjkRh Tgfpu# 7V7V4u 26 n l i e sg t s or p n j i e d qo umlkRh Vgf #12"26 & 3&5S$& 0' x CB e0#1CB Q0 C' yv ($4f#$ 1)%BI4 3 "4(Vwg v $' S 0' 3$3 0 t' @B& 0 0 1$ ES17b b 0@ 2U77 7~ G2&e0C% V0 S 0B B S$ 0 B 3&$ 5 $ V&0A47k4FEDC%BA@1f(F~ 0 '&$ B 3 S #1V&0C7Y)fTF44$ (%i S$H d@B & & V5h2g17r6B 04($ v %t4AIP(R%BRd ($4fIV&)($4' 3 }U $ g 0 $ B& 0 0 '&$ ) f(@ G173A IU C~$ A3~(#uPr(CEBRd ($4Yg v S&B & i 3 }U $
DBW70E 3-29
The generation of the SID values has the same meaning as BEx reporting on this DataStore Object.
Below the nodes of key fields there is the list of inserted keys for this DataStore object. Below the node of the data fields there is the list of inserted data fields nothing has changed here. Navigational attributes may be marked within the appropriate list. Indexes may be maintained for the DataStore object.
SAP AG
DBW70E
3-30
(Eq ( E 1 E e A y A A c e
SAP AG
SAP AG 2006
DBW70E
3-31
'HWDLOV
SAP AG 2006
Detailed information about the standard DataStore object: The activation process is enhanced technically Instead of a key field request GUID there is a key field request SID (domain RSSID) used within the activation queue Because of this structure change there is no expensive join to the request SID table necessary Also there is a package fetch used instead of a single dataset fetch during the activation process (in addition to that there is only one loop over the activation loop implemented now; for restarting there is no further loop necessary because the packages are stored temporarily in cluster tables).
The rollback of data packages is implemented in a different way: instead of rolling back in serial and in one transaction the rollback now is in parallel and for each data package there is a single task.
SAP AG
$FWLYDWLRQ SURFHVV LV RSWLPL]HG RQO\ LQVHUWV QR VRUWLQJ QR EHIRUH LPDJH 1RWH HUURU LI NH\ DOUHDG\ H[LVWV
)RU QRQUHSRUWLQJ VFHQDULRV ZULWHRSWLPL]HG 'DWD6WRUHV DUH UHFRPPHQGHG LQVWHDG RI VWDQGDUG 'DWD6WRUH REMHFWV ZLWK XQLTXH IODJ
,QVWHDG RI UROOLQJ EDFN LQ VHULDO DQG LQ RQH WUDQVDFWLRQ UROOEDFN QRZ LV LQ SDUDOOHO DQG IRU HDFK GDWD SDFNDJH WKHUH LV D VLQJOH WDVN
DBW70E
3-32
&KDQJH /RJ
SAP AG 2006
Structure for the DataStore object: Activation Queue It is used to store the data to be updated into the DataStore object which has not been activated, Shortly after the activation the data is deleted. The following key fields are defined technically: - Request surrogate ID - Package ID - Record number Semantically key fields are defined within the DataStore Object definition The active data table has the same structure as the DataStore Object definition Technical, semantic key fields and data fields are specified during activation
The Active table stores all active data (also called A-Table) The Change Log table stores all historical changes for Delta mechanism from the (actual) DataStore object into other InfoProvider The following key fields are defined technically: - Request GUID - Package ID - Record number
SAP AG
8VHG WR VWRUH GDWD WR EH XSGDWHG LQ 'DWD6WRUH 2EMHFW ZKLFK KDV QRW EHHQ DFWLYDWHG $IWHU DFWLYDWLRQ WKH GDWD FDQ EH GHOHWHG 7HFKQLFDO NH\ 5HTXHVW 6,' 3DFNDJH ,' 5HFRUG QXPEHU 6DPH VWUXFWXUH DV WKH 'DWD6WRUH 2EMHFW GHILQLWLRQ
&KDQJH KLVWRU\ IRU GHOWD PHFKDQLVP IURP WKH 'DWD6WRUH 2EMHFW LQWR RWKHU ,QIR3URYLGHU .H\ ILHOGV
DBW70E
3-33
t S &$ SU 3 i SU @5U 1B F773q ($kH E04$~4 7%$(@4F( 0 g d @ SU 5 0 68 46(gRYVX6C%BP %$(A@@ U pSVS S$H 0 @ SU 3$ W3 425r2&04 1#1R%Bk 1($kH c0# S3 D @ $W3$ S' '&$ ' ( 251EBkf(4 FF$
3DUDOOHO 3URFHVVHV
3 S S $ !' 0 @ & # 441%B7 VS7($($#Y V&c0P S3 0 $W3$ (4 V5~V&b77)(C%BRd & $ 3 d @ $W3$ HB '& CB e04pgC%BrYF$ $W3$8 4q71)7%3 55q & $ 3$@B &$3 SU t' B i S5 1~CB 0#H Q0qCf4I ($7(Rp4VS1
3HUIRUPDQFH ,PSURYHPHQWV RI DFWLYDWLRQ SURFHVV
0DLQ 3URFHVV
SAP AG
SAP AG 2006
Activation queue contains Request SID (instead of GUID) no join with request SID necessary
DBW70E
3DUDOOHO 3URFHVVHV
3DUDOOHO 3URFHVVHV
3-34
6FHQDULRV
)DVW (': LQERXQG OD\HU QR DFWLYDWLRQ QHHGHG
/RDG
SAP AG 2006
Possible scenarios for usage are: Enterprise Datawarehouse inbound layer in a multi layer architecture Where fast load is essential e.g. multiple loads per day or short source system access times (world wide system landscape) Very detailed information e.g. on document item level the DataStore object can have 16 key fields (if you want to have more you need to use concatenated key fields) and 749 data fields altogether a width of 1962 Bytes Data storage layer before transformations in a loading process over multiple layers or different application information In general large amount of data records For the accounting model in a specific business model Load of new records:
- When every new record has a new key - When there is no update of the key combination business wise - E.g. for receipts
SAP AG
'$ S S @ 0 ` 5 & 7B 15 2S75Ic rkV&0 CB v ($#R4uPr(R%BRd ($ YFC%Bfg v $' 3 }U $ g 0H 8 &5q U5 $' ' 17%B6C%B@ 2&6 C7 r(4 v 3 }U $ g 0 '$ S S5 4ukP%C%BRd E$46sEBqp&GB 2S1 v %$ "6CEBqC Y v $' d 8 @ ( V&) C%47y#aqF~ s%'CB () v 0 S&B $'5 B X W `& $ $ 3 H
'URS
t S @ $' S @ W i S 0 B 0 3 ( Cf 17' %0P($4I77T' 0P#bEr pU 7F f(5qQ5 7 0' v
| | | |
)RU ODUJH VHWV RI GDWD UHFRUGV RQ GHWDLOHG OHYHO HJ GRFXPHQW OHYHO
'HWDLOV
)XOO\ LQWHJUDWHG LQ GDWD IORZ XVDEOH DV GDWD VRXUFH DQG GDWD WDUJHW &DQ EH LQFOXGHG LQWR 0XOWL3URYLGHU RU ,QIR6HW &KHFNER[ 'R QRW FKHFN 8QLTXHQHVV RI GDWD 3HUIRUPDQFH LPSURYHPHQW GXULQJ GDWD ORDG
8QLTXHQHVV RI 'DWD
SAP AG 2006
Detailed information about the write-optimized DataStore Object Definitions: The data is stored simply in one version Only one table exists: the active table with key and data fields of its definition. There is no change log table delta capabilities are not needed - To access most recent data use a date field in the DataStore object definition. There is no SID generation during load BEx-Reporting is switched off It can be used for transformation upload scenarios. Also it is possible to extract data. There is direct reporting on this object possible without activation - also e.g. you can use an InfoSet to join the active table Also it is possible to include this object into a MultiProvider The Uniqueness of the data can be switched off with a check box Definition: This indicator is only relevant for write-optimized DataStore objects. The technical key for these objects in the active table always consists of the fields 5HTXHVW, 'DWD 3DFNDJH and 'DWD 5HFRUG. The InfoObjects that appear in the maintenance dialog in the folder .H\ )LHOGV from the semantic key of the write-optimized DataStore object. If this indicator is set, a unique index with the technical name "KEY" is generated for the InfoObjects in the semantic key. If this indicator is not set, the active table of the DataStore object could contain several records with the same key.
SAP AG
t bEDC%B@6C%B~q GVDE0 C"7 %Ur 1VU7) G2&Q0C6" 4 4Y9 3&$ @ ' 0 BB& 5 i S 0B 0 B! S HX
1R 6,' JHQHUDWLRQ
W &$ D 4b3 Q0 f &B ' 0 5 0&5 0 0$ $ 3B& Bg C~#p&fCq 1b2&($4V&fDq(4(767F49
5 0&5 0 WS$ 0&3 Cq b )4743 7" 55q & $ 3$ B& '&$ S &$3 B X #1CrCB Q0q7H 0qFG)B b17)9
DBW70E
2QO\ DFWLYH GDWD WDEOH NH\ UHTXHVW ,' 3DFNHW 1R 5HFRUG 1R
3-36
'HWDLOV
6FHQDULRV
$Q $3, LV DYDLODEOH ZLWK D VHW RI IXQFWLRQ PRGXOHV VRPH DUH 5)& HQDEOHG
SAP AG 2006
Detailed information about the DataStore object for direct update Definitions: The data is stored simply in one version Only one table exists: the active table with key and data fields of its definition. The DataStore Object for direct update can be used for analysis processes eg with the Analysis Process Designer (APD). It cannot be used for transformation upload scenarios there is no loading into the DataStore object for direct update within BI. But: it is possible to extract data. There is no direct reporting on this object possible yet - instead e.g. use an InfoSet to join the active table Also it is not possible to include this object into a MultiProvider The DataStore object for direct update can be used for transactional data The DataStore object for direct update is perfect for using it for external data There is an API available with various function modules: - (Obsolete from ODS-Objects: BAPI BAPI_ODSO_READ_DATA) - BAPI BAPI_ODSO_READ_DATA_UC - RSDRI_ODSO_INSERT - RSDRI_ODSO_INSERT_RFC - RSDRI_ODSO_MODIFY - RSDRI_ODSO_MODIFY_RFC - RSDRI_ODSO_UPDATE - RSDRI_ODSO_UPDATE_RFC - RSDRI_ODSO_DELETE_RFC
SAP AG DBW70E 3-37
5HQDPLQJ RI WUDQVDFWLRQDO 2'6 2EMHFW 2QO\ DFWLYH GDWD WDEOH &DQ EH XVHG DV GDWD WDUJHW ZLWKLQ $3'
&DQQRW EH XVHG IRU WUDQVIRUPDWLRQ XSORDG VFHQDULRV QR ORDGLQJ SURFHVV ZLWKLQ %, EXW H[SRUW LQWR QH[W ,QIR3URYLGHU LV SRVVLEOH 5HSRUWLQJ LV SRVVLEOH 8VHG IRU GLUHFW LQSXW RI H[WHUQDO WUDQVDFWLRQDO GDWD
)XQFWLRQDO FRQVWUDLQWV
5XQWLPH 3DUDPHWHUV
3HUIRUPDQFH RSWLPL]DWLRQ
SAP AG 2006
There is a new monitor concept installed for the DataStore Object administration: Load monitor like the earlier Monitor Logs for DSO-Request Processing
There are also some functional constraints for things which do not work at the same time. Also there are some runtime parameters which are called within a new transaction. Some performance hints help to optimize read- and loading time. The frames Contents and Reconstruction have not changed. A new feature is the Archiving frame to archive the DataStore Object contents.
SAP AG
'XULQJ DFWLYDWLRQ
DBW70E
3-38
SAP AG 2006
The log information can be called with the new transaction 562'62B6+2:/2*. Different entry points are possible via the transaction: Activation of data Loading data Delete data Rollback of data All operations
All operations are also displayed when clicking on the icon within the DSO administration Manage view. For each operation there is detailed information.
SAP AG
DBW70E
3-39
SAP AG 2006
DataStore object runtime parameters are either called with the new transaction RSODSO_SETTINGS or Following runtime parameters can be set for each DataStore Object: Edit object specific values Restore standard values STD Transport changes Each DataStore Object has its parameters for
-
Via menu Goto DSO Object Customizing within the DataStore Object definition (RSA1).
All of these parameters can change the settings with a pop-up dialog to define
-
With Maximum Package size it is possible to define how large a datapackage can be. With Maximum Wait Time for Process it is possible to define the waiting time of the main process for the current parameter until an error will be handled.
SAP AG DBW70E 3-40
Activation SID Generation Parameter for Rollback Serial or paralles processing Processing in Dialog processes or in background processes Also specific servers can be maintained
,QGH[LQJ
2QO\ DV PDQ\ GDWD ILHOGV DV QHFHVVDU\ /RDG RQO\ DV PDQ\ GDWD UHFRUGV DV QHFHVVDU\
1I1UT0(A"8E E SA) D R"8R% PI" 2 G3 9 9 D B 9 ' % '@ 9 ' 9 2 3 @ 3 5 ' Q D@ )3 !
SAP AG 2006
The administration points in the slide above should be noted for optimum performnce
SAP AG
3DUWLWLRQLQJ &OXVWHULQJ
7LPH FRQVXPLQJ FKDUDFWHULVWLF 6,' JHQHUDWLRQ LV DYRLGHG ZLWKLQ DFWLYDWLRQ 'DWDEDVH PDLQWHQDQFH IHDWXUHV IRU KDYLQJ EHWWHU UHDGZULWH DQG GHOHWH DFFHVV :ULWHRSWLPL]HG 'DWD6WRUH 2EMHFW LV DXWRPDWLFDOO\ SDUWLWLRQHG 0DQXDO 3DUWLWLRQLQJ DFFRUGLQJ WR 266 QRWHV DQG
,I UHSRUWLQJ VHOHFWLRQ FULWHULD GR QRW PDWFK WKH NH\ VSHFLILFDWLRQV VHFRQGDU\ LQGLFHV KHOS WR DSSURYH TXHU\ UHVSRQVH WLPH ,QGH[ PDLQWHQDQFH FDQ EH GRQH ZLWKLQ WKH 'DWD6WRUH 2EMHFW GHILQLWLRQ 2QO\ DV PDQ\ NH\ ILHOGV DV QHFHVVDU\
DBW70E
3-41
3HUIRUPDQFH
SAP AG 2006
The DataStore Object is a very powerful Enterprise Datawarehouse object. For every purpose there is its specific definition: Reporting SID generation for DataStore Objects to make the content available for query definitions or to include the object into a MultiProvider
Transactional or planning data DataStore Object with direct update Inbound layer object DataStore Object write-optimized EDW layer object Either reporting relevant or for staging purposes - for each area of interest different DataStore Objects are possible to use
Beside the purpose of its usage there are various performance hints to inprove loading and reading time Further information regarding terminology changes may be found via SAP Service Marketplace alias /bi Documentation SAP NetWeaver 2004s BI: Changed Terminology
SAP AG
DBW70E
3-42
([SODLQ WKH FRQFHSW RI 'DWD6WRUH 2EMHFWV ZKLFK ZLOO UHSODFH 2'6 2EMHFWV LQ 6$3 1HW:HDYHU V
SAP AG 2006
SAP AG
DBW70E
3-43
SAP AG
DBW70E
3-44
'DWD 0RGHOLQJ
/HVVRQ 'DWD :DUHKRXVLQJ :RUNEHQFK /HVVRQ 'DWD6WRUH 2EMHFWV /HVVRQ ,QIR6HWV /HVVRQ 5HPRGHOLQJ 7RROER[ /HVVRQ %XVLQHVV &RQWHQW
SAP AG 2006
SAP AG
DBW70E
3-45
SAP AG 2006
SAP AG
DBW70E
3-46
7KH ,QIR6HW RIIHUV D VHPDQWLF YLHZ IRU FHUWDLQ ,QIR3URYLGHUV DQG MRLQV EHWZHHQ WKHP ,Q 6$3 1: V WKHUH DUH SHUIRUPDQFH DQG XVDELOLW\ LPSURYHPHQWV DV ZHOO DV WKH DELOLW\ WR QRZ LQFOXGH ,QIR&XEHV LQ ,QIR6HWV
SAP AG 2006
SAP AG
DBW70E
3-47
,QIR6HWV 2YHUYLHZ
(QKDQFHG )XQFWLRQDOLW\
V
Overview of InfoSets with SAP Netweaver 2004s BI: InfoSet as InfoProvider There is no physical data storage on InfoSets a semantic view of DataStore objects, InfoObjects and InfoCubes that allows you to create reports on these objects, particularly on the joins between these objects. There is a new transaction available: RSISET
Some more new functionality enhances the object: InfoCubes are possible for joins Time dependencies can be defined for DataStore Objects and InfoCubes to treat these objects in a way as time dependent attributes. Some additional functions are enhanced within the InfoSet Builder
SAP AG
q r '5 ' 5 p D@ )e 6 2 B 3 W (b0 Y&0Pib' 1T9 X % 3 a D% D@ )e D5 10 FPhg P"IfPA) D dc1# TbY`"Y(IX 3 5 ' 3 a ' ) 5 ! %3 W
V V
DBW70E
3-48
,QIR6HWV 6FHQDULRV
,QIR6HW 6FHQDULRV
6ORZ6HOOHUV $QDO\VLV -RLQV YV 8QLRQ
V
SAP AG 2006
7UDQVLWLYH $WWULEXWHV
V
7HPSRUDO -RLQ
V
Business cases of where you might consider use of InfoSets are listed in the slide above.
SAP AG
)LQG DUWLFOHV WKDW KDYH QRW EHHQ VROG OHIW RXWHU MRLQ RI PDVWHU GDWD WR 'DWD6WRUH GHWDLOV &RPELQLQJ ,QIR&XEHV DQG GHWDLOHG 'DWD6WRUH 2EMHFWV LQ D 0XOWL3URYLGHU XQLRQ FDQ OHDG WR VHYHUDO QRW GHILQHG OLQHV LQ %, DSSOLFDWLRQV LI D YDOXH LV DYDLODEOH RQO\ LQ RQH RI WKH WZR ,QIR3URYLGHUV &RPELQLQJ ,QIR&XEHV DQG GHWDLOHG 'DWD6WRUH 2EMHFWV LQ DQ ,QIR6HW MRLQ RQO\ FRPELQHV YDOXHV WKDW H[LVW LQ ERWK ,QIR&XEH DQG 'DWD6WRUH 2EMHFW
%XVLQHVV SDUWQHU LV WKH FRQVROLGDWHG ,QIR2EMHFW ZKLFK UHIHUHQFHV ,QIR2EMHFWV YHQGRU FXVWRPHU HWF ,I \RX ZDQW WR XVH DWWULEXWHV RI FXVWRPHU LQ ,QIR&XEHV FRQWDLQLQJ EXVLQHVV SDUWQHU \RX FDQ PRGHO WKLV YLD ,QIR6HWV +5 UHSRUWLQJ 6KRZ HPSOR\HHV DQG WKHLU DVVLJQHG RUJDQL]DWLRQDO XQLW XVLQJ WLPHGHSHQGHQW PDVWHU GDWD
DBW70E
3-49
,QIR6HW 'HILQLWLRQ
s s s
SAP AG 2006
The InfoSet navigation within the Enterprise Data Warehousing Workbench with its context sensitive menu is enlarged to provide more functionality In the same way as the InfoCube all basic functions are available: Display Change Copy Delete
From the context menu it is possible now to view the data flow into the InfoSet object. The ADJUST functionality appears automatically if a used InfoProvider within the InfoSet has changed.
SAP AG
DBW70E
3-50
,QIR6HW 0DLQWHQDQFH
SAP AG 2006
Especially for graphic modeling as we have with InfoSets it is worth hiding the navigation bar and the InfoProvider tree display. When starting the first time (for each user) of the InfoSet maintenance the user is asked wheather the display is graphical or hierarchical this setting can be switched any time with the menu settings. As with InfoCubes and DataStore objects here you can select further InfoProviders within the left frame to join them into the InfoSet.
SAP AG
DBW70E
3-51
&RQWH[W 0HQX
V
6HOHFW EHWZHHQ LQQHU DQG RXWHU MRLQ 1RWH OHIW WDEOHV RI OHIW RXWHU MRLQ DUH FRORUHG ZKLWH
'HILQH WLPHGHSHQGHQF\ 'HILQH UHTXHVWV WKDW ZLOO EH UHDG IRU TXHULHV RQ ,QIR6HW
2Q 'DWD6WRUH 2EMHFWV
V
SAP AG 2006
The context menu is different -either for the object which has started the InfoSet the joining object (e.g. an InfoCube which has to be first anyway) or the joined object (e.g. a master data InfoObject). There are two new major functionalities: InfoCubes are able to join; Time dependencies for time dependent attributes or time dependent InfoCube values.
The InfoCube data can be set for its current state of uploaded data e.g. the last rolled up data into an aggregate (and not just loaded with a green traffic light). Definition of time dependency is possible either with a period and fixed dates valid from and valid until or a time interval e.g. 0CALMONTH. Also now it is possible to add filter values to a left outer join this setting has to be done within the global properties.
SAP AG
65%3 95 9 % 22 e 7wHF7Cw Y(Igf 9 5 ' # # # ' D ) 95 9 % 5 ! %% D ! 22 Pc1Y(% 1YUw""Y PcY(4&bi0' Ihi8w"Y&Y(T(% "Igf 22 e 95 9 % ) # 22 e 9 5 ' # # # ' D ) "Pb0w% 1ECdR E'(8YP"Y8P"071Y 2 Ph09 0' % G D5 9 ' '5 ' B 2 D% 5 D ) D 2 D 2 ' 9 5 '5 9 5 ) %% ! D5 B c&b0Y w$4b(10(R11PX 9 5 ' # # # ' @ D # ' 9 22 3 5 ) 5 D "Pc1Y(% 1EF06 I' 40(0B 9 22 ' YD I8) D R5 0Hdb0$9 E4$6 1) ) D 45 1I40 3 3 )3 @ 3 5 2 D 3 3 )3 @ % ' ) '5 9 B 2 D '5 ' B 22 D (100P01iH2 `P$(b0$1Y H&`
DBW70E
3-52
,QQHU -RLQ
V
5HVXOW FRQWDLQV DOO UHFRUGV ZKLFK DUH FRPPRQ WR ERWK ,QIR3URYLGHUV ZLWK UHVSHFW WR WKH MRLQ FRQGLWLRQ
l ~ x w r TSj q h} kz s q on m l j t or dp HS44{i
25 85
5HVXOW FRQWDLQV DOO UHFRUGV RI OHIW ,QIR3URYLGHU HYHQ LI WKHUH LV QR PDWFKLQJ UHFRUG ZLWK UHVSHFW WR WKH MRLQ FRQGLWLRQ LQ WKH ULJKW ,QIR3URYLGHU
l ~ x w r TSj q h} tz s q on m l j t or dp HS4Ri
25 0 85
SAP AG 2006
SAP AG
DBW70E
l ~ x w r z Tdj q h} |{dy
10 20 15 30 35
q s r I4t"u
s q on m l j t or dp HSSRki
3-53
$JJUHJDWHV
%, $FFHOHUDWRU
&DQ EH XVHG IRU ,QIR&XEHV ZLWKLQ ,QIR6HWV $JJUHJDWHV ZLOO EH DXWRPDWLFDOO\ XVHG LQ WKH JHQHUDWHG 64/ VWDWHPHQW %, $FFHOHUDWRU FDQQRW EH XVHG DV MRLQ LV H[HFXWHG RQ GDWDEDVH OHYHO
2QO\ VHOHFWHG UHFRUGV RI DJJUHJDWH LI IRXQG DQG QRW RI ,QIR&XEH EHFDXVH RI LWV DJJUHJDWHG YLHZ
SAP AG 2006
SAP AG
DBW70E
3-54
5HVWULFWLRQV
$Q ,QIR&XEH FDQQRW EH D ULJKW RSHUDQG RI D OHIW RXWHU MRLQ GXH WR SHUIRUPDQFH LVVXHV 7KHUH DUH RQO\ ,QIR&XEHV DOORZHG ZLWKLQ ,QIR6HW
SAP AG 2006
The more InfoCubes within an InfoSet the larger the SQL statement becomes there are restrictions to the length of it (64kb). Unlike the star schema of an InfoCube where the access plans for the data base are limited within an InfoSet with more InfoCubes or a join with a DataStore Object there are multiple big tables where no database access plan can be generated. If there are not all joined characteristics within the query result the key figures are multiplied for more InfoCubes this becomes more sophisticated.
SAP AG
DBW70E
3-55
7HPSRUDO -RLQ
j ~ w r FS {
10 10 10 20 20 20 4200 3200 4500 3500 4500 5800
10 10 10 20 20
SAP AG 2006
Example / Scenario A sales manager is assigned to a sales district; as the manager can change, this attribute is designed as time-dependent. Temporal Join combines InfoCube data with time-dependent master data and joins the time dimension to the validity period. Note: see the delta training lesson on BEx Query Designer for more information on joining time-dependent KLHUDUFKLHV.
SAP AG
DBW70E
j ~ w r FS
r wv F o} c
q s r I4tu
~r nh o} wdc S4R&j Skz v njvsv u l wv q onq o 4m HH4l i l wv j Skz '5 ' % 5 9 ' Q 5 ) ) B Q3 ("0F0PY"8FP"000E007C&
3-56
7HPSRUDO MRLQ
SAP AG 2006
Temporal Join Definition: Contains at least one time-dependent characteristic Based on time intervals of two objects
Time-dependent InfoObjects Real time-dependency: system guarantees contiguous and complete time span
SAP AG
DBW70E
3-57
7HPSRUDO MRLQ
V
6WDUW DQG HQG WLPH FDQ DOVR EH JLYHQ E\ WZR WLPH FKDUDFWHULVWLFV RI W\SH GDWH WKDW DUH SDUW RI WKH ,QIR&XEH'DWD6WRUH 2EMHFW
SAP AG 2006
SAP AG
DBW70E
3-58
7HPSRUDO MRLQ
V
SAP AG 2006
In BEx Query definition we note New Dimension Valid Time Interval Includes Valid From and Valid To fields
SAP AG
DBW70E
3-59
SAP AG 2006
Performance side note: key date derivation takes place in ABAP, not on database level
SAP AG
DBW70E
3-60
The use of the derivation type is determined via the Key Date flag. A key date is determined for time-dependent master data.
SAP AG
DBW70E
3-61
10 10
Stevenson Clark
01.01.2000 16.04.2003
15.04.2003 31.05.2003
04.2002 04.2003
SAP AG 2006
Join results would be such as the above. But be aware of join result interpretations. Also see notes 583249 and 592785
SAP AG
DBW70E
j ~ w r Fd |c
q s r du
r wv F o} S
~ n wv r o} S q s r I4tu
q o q o m In dl bi l wv Rj d{z
3-62
,QIR6HWV 6XPPDU\
V V
,QIR6HWV 6XPPDU\
7KH ,QIR6HW LV D SRZHUIXO DQG KLJKO\ IOH[LEOH PRGHOLQJ REMHFW
7HPSRUDO MRLQV RI WLPHGHSHQGHQW PDVWHU GDWD FDQ EH PRGHOHG YLD ,QIR6HWV WHPSRUDO MRLQV RI WLPHGHSHQGHQW KLHUDUFKLHV FDQ EH GLUHFWO\ GHILQHG LQ WKH 4XHU\ 'HVLJQHU
V
SAP AG 2006
SAP AG
DBW70E
3-63
SAP AG 2006
SAP AG
DBW70E
3-64
'DWD 0RGHOLQJ
/HVVRQ 'DWD :DUHKRXVLQJ :RUNEHQFK /HVVRQ 'DWD6WRUH 2EMHFWV /HVVRQ ,QIR6HWV /HVVRQ 5HPRGHOLQJ 7RROER[ /HVVRQ %XVLQHVV &RQWHQW
SAP AG 2006
SAP AG
DBW70E
3-65
3RVLWLRQ DQG H[SODLQ FDSDELOLWLHV RI WKH UHPRGHOLQJ WRROER[ RI 6$3 1HW:HDYHU V %, 'HILQH D UHPRGHOLQJ UXOH 6FKHGXOH DQG PRQLWRU D UHPRGHOLQJ UXOH
SAP AG 2006
SAP AG
DBW70E
3-66
,I D FRPSDQ\V EXVLQHVV VWUDWHJ\ RU VWUXFWXUH FKDQJHV HJ WKURXJK D PHUJHU RU DFTXLVLWLRQ WKHUH ZLOO EH DQ LPSDFW RQ LWV LQIRUPDWLRQ UHTXLUHPHQWV DQG KHQFH RQ LWV LQIRUPDWLRQ PRGHO GHVLJQ $ UHPRGHOLQJ WRROER[ LV QRZ SURYLGHG WR DVVLVW LQ DGMXVWLQJ WKH PRGHO WR WKH QHZ UHTXLUHPHQWV
SAP AG 2006
SAP AG
DBW70E
3-67
5HPRGHOLQJ
SAP AG 2006
As of SAP NetWeaver 2004s, you can change the structure of InfoCubes into which you have already loaded data, without losing the data
SAP AG
$ QHZ NH\ ILJXUH PXVW EH DGGHG WR D SDUWLFXODU ,QIR&XEH WKDW FDQ DOVR EH LQLWLDOL]HG $ QHZ FKDUDFWHULVWLF VKRXOG EH LQVHUWHG DQG PD\ UHSODFH DQ H[LVWLQJ RQH ,W FDQ EH ILOOHG EDVHG RQ WKH ROG FKDUDFWHULVWLF
DBW70E
3-68
bEH0k1 R 0H8Y4TEUI 1" YY1i1CTP"E& PI T"F18TP bEH0k1 R 0H8Y4TEUI 1" YY1i1CTP"E& PI T"F18TP Y Eh0(
bEH0k1 R 0H8Y4TEUI 1" YY1i1CTP"E& PI T"F18TP 108 F88YyE4TETbw{A1bIh0Y400TEYI0y8EYY 1T8 ACEYA41 "w{AEPiC0TE8(1Hd4w YH1Y db 40("(0YE$8E&c Eh0(
SAP AG
SAP AG 2006
Constants
Delete
Inserting:
Constants
Delete
5HPRGHOLQJ
&KDUDFWHULVWLF &RQYHUVLRQV
5HPRGHOLQJ 5XOH
'HOHWH &KDUDFWHULVWLF
DBW70E
3-69
,PSDFW
SAP AG 2006
'XULQJ WKH FRQYHUVLRQ SURFHVV UHDGLQJ TXHU\LQJ DQG FKDQJLQJ WKH ,QIR&XEH LV ORFNHG $OO GHSHQGDQW REMHFWV TXHULHV WUDQVIRUPDWLRQV 0XOWL3URYLGHUV HWF ZLOO EH GHDFWLYDWHG DQG KDYH WR EH DGMXVWHG PDQXDOO\ $JJUHJDWHV DQG %, DFFHOHUDWRU LQGH[HV PXVW EH UHEXLOW DIWHU WKH FRQYHUVLRQ
$XWKRUL]DWLRQ
266 FRPSRQHQW
%::+0'%$507
SAP AG
DBW70E
3-70
$FFHVV
SAP AG 2006
Access is via Context menu of InfoCube Administration view of Data Warehousing Workbench
SAP AG
DBW70E
3-71
5HPRGHOLQJ 5XOH
SAP AG 2006
Remodeling rule consists of one or more operations (like adding or deleting a key figure etc.)
SAP AG
DBW70E
3-72
SAP AG 2006
SAP AG
DBW70E
3-73
SAP AG 2006
SAP AG
DBW70E
3-74
SAP AG 2006
SAP AG
DBW70E
3-75
3DUDPHWHU
SAP AG 2006
The interface IF_RSCNV_EXIT should be used. Three parameters are given I_CNVTABNM: name of the table that will be converted (in case you need one remodeling rule for more than one InfoCube) I_R_OLD: structure of the table EHIRUH the conversion C_R_NEWFIELD: result of the routine which will be assigned to the new field
SAP AG
DBW70E
3-76
SAP AG 2006
SAP AG
DBW70E
3-77
$OO FODVVHV WKDW LPSOHPHQW WKH LQWHUIDFH ,)B56&19B(;,7 ZLOO EH DYDLODEOH LQ WKH )KHOS
SAP AG 2006
SAP AG
DBW70E
3-78
6FKHGXOLQJ
SAP AG 2006
Schedule the remodeling rule or start it immediately Periodic scheduling not useful Parallel execution is optional Supervising job splits and controls (background) processes for parallel table conversions Currently: only one single process is started in the parallel mode Recommendation: do not flag the parallel setting if you might have system constraints (or for debugging purposes)
SAP AG
DBW70E
3-79
0RQLWRULQJ
SAP AG 2006
SAP AG
DBW70E
3-80
2XWORRN
SAP AG 2006
SAP AG
DBW70E
3-81
3RVLWLRQ DQG H[SODLQ FDSDELOLWLHV RI WKH UHPRGHOLQJ WRROER[ RI 6$3 1HW:HDYHU V %, 'HILQH D UHPRGHOLQJ UXOH 6FKHGXOH DQG PRQLWRU D UHPRGHOLQJ UXOH
SAP AG 2006
SAP AG
DBW70E
3-82
'DWD 0RGHOLQJ
/HVVRQ 'DWD :DUHKRXVLQJ :RUNEHQFK /HVVRQ 'DWD6WRUH 2EMHFWV /HVVRQ ,QIR6HWV /HVVRQ 5HPRGHOLQJ 7RROER[ /HVVRQ %XVLQHVV &RQWHQW
SAP AG 2006
SAP AG
DBW70E
3-83
([SODLQ WKH IXQFWLRQDOLWLHV RI WKH &RQWHQW $QDO\]HU ZLWKLQ 6$3 1HW:HDYHU V
'HVFULEH WKH UHSRUWLQJ IXQFWLRQDOLWLHV RI WKH &RQWHQW %URZVHU ZLWKLQ 6$3 1HW:HDYHU V
SAP AG 2006
SAP AG
DBW70E
3-84
6$3 %: %XVLQHVV &RQWHQW GHOLYHUV SUHGHILQHG UROHEDVHG DQG WDVNRULHQWHG PRGHOV ZLWKLQ %: 7KLV HVVHQWLDOO\ PDNHV WKH PRVW UHOHYDQW LQIRUPDWLRQ DYDLODEOH WR VSHFLILF XVHU UROHV 1RWH RYHU EXVLQHVV FRQWHQW VFHQDULRV DUH HLWKHU QHZO\ GHYHORSHG HQKDQFHG RU LPSURYHG ZLWKLQ 6$3 1HW:HDYHU V VSHFLILFDOO\ YLD %, &RQWHQW $GG 2Q DOWKRXJK WKHVH DUH QRW H[DPLQHG LQ WKH FODVV :LWKLQ WKH &RQWHQW $QDO\]HU RI 6$3 1: V FKHFN SURJUDPV DUH SURYLGHG IRU FXVWRPHUV WR DQDO\]H LQFRQVLVWHQFLHV DQG HUURUV LQ WKHLU LQIRUPDWLRQ PRGHOV 7KH &RQWHQW %URZVHU RI 6$3 1: V KHOSV FXVWRPHUV WR GLVFRYHU LQIRUPDWLRQ DERXW ERWK FXVWRPHUGHILQHG DQG 6$3GHOLYHUHG FRQWHQW LQ WKHLU V\VWHP DQG DQVZHU TXHVWLRQV VXFK DV :KLFK 6$3 %XVLQHVV &RQWHQW LV DYDLODEOH LQ D JLYHQ DUHD" DQG :KLFK FXVWRPHUGHILQHG FRQWHQW H[LVWV LQ WKH WKH FXVWRPHU %, V\VWHP"
SAP AG 2006
SAP AG
DBW70E
3-85
&KHFN SURJUDPV IRU FXVWRPHU WR DQDO\]H LQFRQVLVWHQFLHV DQG HUURUV LQ PRGHO :LWK FHQWUDO WUDQVDFWLRQ 56%,&$ \RX FDQ
6FKHGXOH WKHVH GHOLYHUHG FKHFN SURJUDPV &XVWRPL]H WKH VFKHGXOLQJ RSWLRQV 'LVSOD\ WKH UHVXOWV
7KH UHVXOWV RI WKH FKHFN SURJUDPV FDQ EH ORDGHG LQWR WKH ORFDO RU UHPRWH %, V\VWHPV
SAP AG 2006
Check programs are provided to customer to analyze inconsistencies and errors of customer defined information models (InfoObjects, InfoProviders etc). With central transaction RSBICA you can Schedule these delivered check programs for the local system or remote system via RFC connection Customize the scheduling options Display the results of check programs by
-
The results of the check programs can be loaded into the local or remote BI systems, in order to get a single point of entry for analyzing the BI landscape.
SAP AG
DBW70E
3-86
SAP AG 2006
Customizing of Content Analyzer checks are found via transaction RSBICA -> Check execution of menu settings Define whether checks are for execution at once, are there other checks for the same job, execute checks for Content version or Active version?
SAP AG
DBW70E
3-87
SAP AG 2006
Which job do you want to start the check programs for? Jobname is a grouping of check programs eg object status checks. Also for which system are they to be run?
SAP AG
DBW70E
3-88
SAP AG 2006
To see the results of the check programs, the Content Analyzer may be started via the SAP user menu (role: SAP_BW_Content_Administrator) or calling transaction RSBICA
SAP AG
DBW70E
3-89
0RQLWRU
5HVXOW &RQWDLQHU
SAP AG 2006
The Monitor will give you an overview about the result The priority fields provide an aggregated view to the objects listed n the result container. In the Last Update field, the date and time of the oldest object which is available in the result container is displayed. The date and time of the the objects will be set during the runtime of the check programs.The values in the monitor will change if the filter restrictions has been changed.
SAP AG
DBW70E
3-90
SAP AG 2006
Here you can elect to see the results for a particular system / check category / priority
SAP AG
DBW70E
3-91
6\VWHP $
{ISfE
6\VWHP %
6\VWHP &
SAP AG 2006
SAP AG
DBW70E
3-92
1 0P"FbYw{1P"HhY 4 80bw{AEH
Y( & C S0" Hh
F71C0Y410AcY T71"f4bP&FbE7y
1w0y0Y410AcY 0w0E1f4bP&FbE7y
00 HEEb$ T(0$1f4bP&FbE7y
00 HEEb$ 0w001f4bP&FbE7y
"P14bd4XhPA"Y0(0PcP4 8y"YId
(14cd4&F1("0( RbYI
SAP AG
SAP AG 2006
Check categories mean different check programs. For details of what the check programs are doing please refer to the appendix
&KHFN &DWHJRULHV
DBW70E
3-93
SAP AG 2006
A priority can be assigned to every check category. A default priority setting will be delivered by SAP. It can be overwritten by customers. The priority can be changed referring to special system types also, eg Priority for Test Systems Priority for Development Systems
SAP AG
DBW70E
3-94
SAP AG 2006
SAP AG
DBW70E
3-95
6\VWHP $
{i` IYiXik
9LHZ
6\VWHP %
6\VWHP &
SAP AG 2006
How it works with the transport filter depends on whether the transport is available in local or in remote system will be displayed from local table view or from DSO.
SAP AG
DBW70E
3-96
SAP AG 2006
SAP AG
DBW70E
3-97
SAP AG 2006
SAP AG
DBW70E
3-98
SAP AG 2006
Information and help regarding the error and proposals for solving the problem are available if the spectacles symbol is displayed in the info column. The popup comes up after a double click on the row.
SAP AG
DBW70E
3-99
E
tc{tk| ("0TC 1HT 1 HItctYk{
4XHU\
SAP AG
SAP AG 2006
'DWD6RXUFH
55,
RSCONTENTCHECK_E
5HSRUW
DBW70E
'DWD6RXUFH
.H\ *8,'
3-100
SAP AG 2006
SAP AG
E
DBW70E
3-101
SAP AG 2006
Here is the web reporting of the Business Content Analyzer. To start the check program: RSBICA: execute the check reports. Start the check program: job name: the group of check types RFC destination: check programs can be executed remotely with the current customizing views. Results of the check programs are stored locally. RSBICA shows the result locally(current system, table rscontact) or the ODS object result (remote results). Only if the data is loaded centrally is web reporting is possible. The execution of the check program can be started remotely. The customizing settings are not necessary for transport. The customer can create their own query. To have the customizing settings for check program: Settings : check execution
SAP AG
DBW70E
3-102
7KLV 6WDQGDUG %XVLQHVV &RQWHQW FDOOHG &RQWHQW %URZVHU SURYLGHV WKH UHSRUWLQJ IXQFWLRQDOLWLHV WR HQDEOH WKH HQG XVHU WR GLVFRYHU LQIRUPDWLRQ DERXW WKH FXVWRPHUGHILQHG FRQWHQW DQG 6$3 GHOLYHUHG FRQWHQW LQ WKH V\VWHP ,W KHOSV WR DQVZHU WKH IROORZLQJ TXHVWLRQV :KLFK 6$3 %XVLQHVV &RQWHQW LV DYDLODEOH LQ D JLYHQ DUHD" :KLFK 6$3 %XVLQHVV &RQWHQW LV LQ XVH LQ WKH FXVWRPHU %, 6\VWHP" :KLFK FXVWRPHUGHILQHG FRQWHQW H[LVWV LQ WKH FXVWRPHU %, 6\VWHP"
SAP AG 2006
SAP NetWeaver2004s BI Content Add-On 2 is based on the technology release NetWeaver2004s BI. This Content Add-On was released to the ramp-up customers on 24/10/2005. Mass shipment of this content add-on started on the same date as NetWeaver2004s BI. About 43 business content scenarios were either newly developed, enhanced or improved within SAP NetWeaver 2004s BI Content Add-On 2. For details please refer to the business content list which is published on http://service.sap.com
SAP AG
DBW70E
3-103
R B "FEER aA T "i g(Yhh P A bFR p(1I4Ww aA T "i g(Yhh YbFR ` r r T S 7Y%Y1T w r T 4"a I1T Yb R P B f aA A cEe%(% Xd P A c(1HdWwX A v TA u Ts r 0 F1eigGq R A Ts r Y"TYYw1etGq
SAP AG
SAP AG 2006
This is the data flow for the Content Browser with the previous release (3.5.3 Add-on) where relevant BI object types are modeled as different master data.
5HOHYDQW %, 2EMHFW W\SHV DUH PRGHOHG DV GLIIHUHQW PDVWHU GDWD DQG WKH UHODWLRQVKLSV EHWZHHQ WKHVH REMHFWV DUH PRGHOHG DV WUDQVDFWLRQDO GDWD
0DVWHU 'DWD
7UDQVDFWLRQDO 'DWD
DBW70E
0DVWHU 'DWD
3-104
7&7%:2%-&7B$775
7&7%:2%-&7B7(;7
SAP AG 2006
Content Browser has been redefined in a more generic way under SAP NW 2004s BI. Previously each object type was modeled as one InfoObject. Now all BI Object types (DataSources, InfoProviders, Queries etc) and their relationships are modeled as the generic and consistent Master Data BI Object.
SAP AG
:LWK WKH UROH 6$3B%:B&217(17B%52:6(5 \RX FDQ DFFHVV WKH FRQWHQW EURZVHU UHSRUWV WR GLVFRYHU 6$3 GHOLYHUHG VWDQGDUG EXVLQHVV FRQWHQW DQG WKH H[LVWLQJ FXVWRPHUGHILQHG FRQWHQW LQ WKH FXVWRPHU V\VWHP 'XH WR WKH XQGHUO\LQJ WHFKQRORJ\ FKDQJH DQG WKH PRGHOLQJ IOH[LELOLW\ 6$3 UHGHVLJQHG WKH FRQWHQW EURZVHU DQG ZLOO GHOLYHU LW WR WKH FXVWRPHU ZLWK 1HW:HDYHU V %, &RQWHQW $GG2Q
7KHUH LV QR GLUHFW PLJUDWLRQ EHWZHHQ WKHVH WZR FRQWHQW PRGHOV :H UHFRPPHQG WKDW \RX DSSO\ WKH FRQWHQW EURZVHU ZKLFK LV GHOLYHUHG ZLWK 6$3 1HW:HDYHU V %, &RQWHQW $GG 2Q ,Q WKH HYHQW WKDW \RX KDYH DOUHDG\ DSSOLHG WKH &RQWHQW %URZVHU ZLWK %, &RQWHQW $GG2Q \RX QHHG WR GR WKH PDQXDO DGMXVWPHQW WR PLJUDWH WR WKH UHGHVLJQHG &RQWHQW %URZVHU
SAP AG 2006
SAP AG
DBW70E
3-106
SAP AG 2006
In this example this web template answers the question Which objects are available to a particular role?
SAP AG
DBW70E
3-107
7KLV :HE 7HPSODWH SURYLGHV LQIRUPDWLRQ DERXW ,QIR3URYLGHUV E\ ,QIR$UHD ,W SURYLGHV XVHUIULHQGO\ LQWHUIDFH LQFOXGLQJ LFRQV WR LQGLFDWH REMHFW W\SHV ,W DOORZV \RX WR GULOO GRZQ IURP WKH ,QIR$UHD WR UHODWHG ,QIR3URYLGHUV 7KH 0HWDGDWD 5HSRVLWRU\ LQIRUPDWLRQ IRU D SDUWLFXODU REMHFW FDQ EH UHDFKHG E\ FOLFNLQJ RQ WKH LFRQ QH[W WR WKH REMHFWV QDPH
SAP AG 2006
Another example this answers the question Which InfoProviders are available for a particular InfoArea?
SAP AG
DBW70E
3-108
SAP AG 2006
Content Analyzer can also analyze where Business Content is and is not used. See if the InfoProvider is the customers own or delivered by SAP.
SAP AG
DBW70E
3-109
6XPPDU\
&RQWHQW $QDO\]HU DQG &RQWHQW %URZVHU DUH GHOLYHUHG ZLWK 6$3 1HW:HDYHU V %, &RQWHQW $GG2Q ZKLFK ZLOO KHOS FXVWRPHUV HIIHFWLYHO\ DGPLQLVWHU PRQLWRU DQG LPSURYH TXDOLW\ RI FRQWHQW DQG DOVR SURYLGH FXVWRPHUV ZLWK D VWDWLVWLFDO RYHUYLHZ DERXW WKH FRQWHQW REMHFWV &RQWHQW $QDO\]HU $V %XVLQHVV &RQWHQW DV ZHOO DV D WRRO LW KHOSV ,7 'HSDUWPHQW PRQLWRU FRQWHQW TXDOLW\ LQ D FRPSOH[ V\VWHP ODQGVFDSH
&RQWHQW %URZVHU $V VWDQGDUG %XVLQHVV &RQHQW LW KHOSV ,7 'HSDUWPHQW JHW D FOHDU RYHUYLHZ DERXW WKH GHWDLOV DQG XVDJH RI FRQWHQW
SAP AG 2006
This content Add-on delivers the newly developed, enhanced or improved content features in almost 43 areas. For details please refer to the Business Content list published in the SAP Service Marketplace. The Content Browser and Content Analyzer can help the customer effectively administer, monitor and improve the quality of content and also provide the customer a statistical overview of the content objects
SAP AG
&RQWHQW GHYHORSHU ILQG RXW DQG FRUUHFW WKH HUURUV DQG LQFRQVLVWHQFLHV
&XVWRPHUV RU FRQVXOWDQWV WR HDVLO\ QDYLJDWH ILQG RXW WKH ULJKW %XVLQHVV &RQWHQW
DBW70E
3-110
([SODLQ WKH IXQFWLRQDOLWLHV RI WKH &RQWHQW $QDO\]HU ZLWKLQ 6$3 1HW:HDYHU V
'HVFULEH WKH UHSRUWLQJ IXQFWLRQDOLWLHV RI WKH &RQWHQW %URZVHU ZLWKLQ 6$3 1HW:HDYHU
SAP AG 2006
SAP AG
DBW70E
3-111
'LVFXVV WKH FKDQJHV DQG HQKDQFHPHQWV IRXQG LQVLGH WKH 'DWD :DUHKRXVLQJ :RUNEHQFK RI 6$3 1: V ([SODLQ WKH FRQFHSW RI 'DWD6WRUH 2EMHFWV ZLWKLQ 6$3 1: V
'HVFULEH WKH IXQFWLRQDOLWLHV RI WKH &RQWHQW $QDO\]HU DQG &RQWHQW %URZVHU ZLWKLQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
3-112
([HUFLVHV
/HVVRQ 8QLW 'DWD6WRUH 2EMHFWV 'DWD 0RGHOLQJ
6HFWLRQ
The ODS Object played an important role in former versions of BI Warehouse Management. This has been succeeded by a compatible but superior object type DataStore Object in SAP NW 2004s. You will observe similarities and differences between the two objects while creating a DataStore Object. You will use the DataStore Object you create here within a later exercise.
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1 Go to the Data Warehousing Workbench for Modeling and find the InfoProvider tree. Create a new DataStore Object within the InfoArea 7B'%:( which is under 7B%:B&867 (under 7B%:). The DataStore Object should be named 6LQJOH )OLJKW %RRNLQJV ;; with the technical name =6%.'6;; and copied from existing DataStore Object =6%.B'6. It should be a Standard type of DataStore Object. Have a look at the structure of the DataStore Object, including the settings, which you will leave unchanged. Check, Save and Activate the DataStore Object. Then find it in the InfoProvider Tree.
SAP AG
DBW70E
3-113
SAP AG
DBW70E
3-114
6ROXWLRQV
8QLW 'DWD 0RGHOLQJ
6HFWLRQ
/HVVRQ
'DWD6WRUH 2EMHFWV
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1 Go to the Data Warehousing Workbench for Modeling and find the InfoProvider tree. Create a new DataStore Object within the InfoArea 7B'%:( which is under 7B%:B&867 (under 7B%:). The DataStore Object should be named 6LQJOH )OLJKW %RRNLQJV ;; with the technical name =6%.'6;; and copied from existing DataStore Object =6%.B'6. It should be a Standard type of DataStore Object. Have a look at the structure of the DataStore Object, including the settings, which you will leave unchanged. Check, Save and Activate the DataStore Object. Then find it in the InfoProvider Tree. 1-1-1 1-1-2 1-1-3 1-1-4 1-1-5 1-1-6 1-1-7 1-1-8 From the SAP Easy Access menu select 0RGHOLQJ ! 'DWD :DUHKRXVLQJ :RUNEHQFK ! 0RGHOLQJ If you get a pop-up message about documentation select the check box to not show the question again and press <HV Expand the nodes 7B%: ! 7B%:B&867 Highlight the InfoArea 7B'%:(
On right-hand mouse context menu choose &UHDWH 'DWD6WRUH 2EMHFW Specify DataStore Object: =6%.'6;; Description: 6LQJOH )OLJKW %RRNLQJV ;; Copy From: =6%.B'6 Select +LGH6KRZ 1DYLJDWRU so that your (GLW 'DWD6WRUH 2EMHFW screen is in fullscreen mode Press &UHDWH ) The pop-up window (GLW 'DWD6WRUH 2EMHFW appears
Press Back to return to the screen 'DWD :DUHKRXVLQJ :RUNEHQFK 0RGHOLQJ Note that the DataStore Object appears in the tree display.
SAP AG
DBW70E
3-115
SAP AG
DBW70E
3-116
'DWD $FTXLVLWLRQ
&RQWHQWV
SAP AG 2006
SAP AG
DBW70E
4-1
'HFVULEH WKH 8' &RQQHFW DQG 6$3, LQWHUIDFHV ZLWKLQ 6$3 1: V +LJKOLJKW LPSRUWDQW IHDWXUHV RI :HE 6HUYLFHV ZLWKLQ 6$3 1: V 3URYLGH DQ RYHUYLHZ RI PLJUDWLRQ DVSHFWV FRQFHUQLQJ %, 'DWD 6RXUFHV LQ 6$3 1: V
'HVFULEH KRZ WR LPSOHPHQW D GDWDEDVH FRQQHFWLRQ IURP DQ 6$3 1HW:HDYHU V %, V\VWHP WR D UHODWLRQDO GDWDEDVH YLD '% &RQQHFW GDWD VRXUFH
([SODLQ WKH PRVW LPSRUWDQW DVSHFWV RI WKH 'DWD 6RXUFH FRQFHSW ZLWKLQ 6$3 1HW:HDYHU V
SAP AG 2006
SAP AG
DBW70E
4-2
3UHIDFH ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 'DWD 0RGHOLQJ 'DWD $FTXLVLWLRQ 7UDQVIRUPDWLRQ DQG 8QLW RI 0HDVXUH &RQYHUVLRQ 'DWD )ORZ &RQWURO $GPLQLVWUDWLRQ DQG 0RQLWRULQJ 3HUIRUPDQFH 2SWLPL]DWLRQ ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
4-3
'DWD VRXUFHV DUH PDGH WR UHDOLVH FRQQHFWLYLW\ WR DQ\ VRXUFH IRU RXU GDWD ZDUHKRXVH VROXWLRQ 7KH 36$ LV QRZ D PDQGDWRU\ SDUW RI WKH GDWD ZDUHKRXVH GHVLJQ LQ IDFLOLWDWLQJ WKH FRQQHFWLYLW\ WR WKH ZRUOG RXWVLGH WKH %, V\VWHP $OO W\SHV RI GDWD VRXUFH ZLOO QRZ EH VHPDQWLFDOO\ GHVFULEHG LQ WKH %, V\VWHP WKH VDPH ZD\ D RQH ILWV DOO DSSURDFK 7KH 'DWD 6RXUFH FRQFHSW LV D SDUW RI WKH 'DWD )ORZ FRQFHSW LQWURGXFHG LQ 6$3 1HW:HDYHU V 7KH 'DWD )ORZ FRQFHSW LV GHVFULEHG LQ D ODWHU XQLW
SAP AG 2006
SAP AG
DBW70E
4-4
'DWD $FTXLVLWLRQ
/HVVRQ &RQFHSW IRU %, 'DWD 6RXUFHV :LWKLQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
4-5
'HVFULEH KRZ WR LPSOHPHQW D GDWDEDVH FRQQHFWLRQ IURP DQ 6$3 1HW:HDYHU V %, V\VWHP WR D UHODWLRQDO GDWDEDVH YLD '% &RQQHFW GDWD VRXUFH
([SODLQ WKH PRVW LPSRUWDQW DVSHFWV RI WKH 'DWD 6RXUFH FRQFHSW ZLWKLQ 6$3 1HW:HDYHU V
'HVFULEH WKH 8' &RQQHFW DQG 6$3, LQWHUIDFHV ZLWKLQ 6$3 1: V +LJKOLJKW LPSRUWDQW IHDWXUHV RI :HE 6HUYLFHV ZLWKLQ 6$3 1: V 3URYLGH DQ RYHUYLHZ RI PLJUDWLRQ DVSHFWV FRQFHUQLQJ %, 'DWD 6RXUFHV LQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
4-6
'DWD PRGHOLQJ VXSSRUWV DQG IDFLOLWDWHV KLJKO\ IOH[LEOH DQG FRPSUHKHQVLYH LQIRUPDWLRQ PRGHOV 7KH 6$3 1: V WHFKQRORJ\ VXSSRUWV DQ HQKDQFHG XVHU LQWHUIDFH ZLWK D QXPEHU RI HQKDQFHG SHUVRQDOL]DWLRQ DQG QDYLJDWLRQ IHDWXUHV +HUH \RX ZLOO EH LQWURGXFHG WR WKHVH DQG DFFRPSDQ\LQJ WHUPLQRORJ\ QHZ LQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
4-7
SAP AG 2006
We are looking here at Data Acquisition within the context of Modeling the EDW. Here we see the conceptual layers of data warehousing. DataSources are provided to realize connectivity from any source for our data warehousing solution. The connection is made from the outside world to the PSA. The PSA is a must have part for the DataSource design.
SAP AG
DBW70E
4-8
'DWD6RXUFH36$
5HODWLRQDO 6RXUFH
6$3 6RXUFH
)LOH
;0/
SAP AG 2006
The entire architecture overview for this layer is above. There are a number of categories of source systems. The legaacy applications accessed via BAPI using ETL tools are not available for the SAP NW 2004s DataSources.
SAP AG
DBW70E
! "
(7/ 7RRO /HJDF\ $SSOLFDWLRQV
4-9
0 (' )& $ % #
i fU B e d c C C h gG44DE XB
+LJKOLJKWV
8QLTXH ORRN DQG IHHO IRU DOO RI WKH 'DWD6RXUFH 7\SHV 36$ PDQGDWRU\ 'LUHFWUHPRWH DFFHVV LV DOZD\V DQ RSWLRQ 3UHYLHZ IHDWXUH LV VWDQGDUG $XWRPDWHG FRYHUVLRQV HJ GDWH IRUPDW GHWHFWLRQ ,QIR3DFNDJHV RQO\ ZULWH LQWR 36$ 1HZ 7UDQVIRUPDWLRQ KDQGOLQJ 1HZ 'DWD 7UDQVIHU 3URFHVV ORJLF
SAP AG 2006
This slide brings together all the highlights of what is new inside the SAP NW 2004s DataSources.Direct/remote access was available previously for only UDCONNECT and not eg DBCONNECT DataSources. Now DBCONNECT can be used in this way. Preview offers a first check on accessibility and a look at the incoming data. No InfoPackage will be able to directly populate the DataStore Object layer or the InfoCubes for example. Therefore we have a new transformation concept (to replace transfer rules/update rules we do not have to decide between these two). Also there is a new Data Transfer Process to design and improve the dataflow.
SAP AG
DBW70E
4-10
SAP AG 2006
In the Source System tree in the Data Warehousing Workbench there is a categorisation of the DataSources that is clearly visible.
SAP AG
DBW70E
4-11
SAP AG 2006
In this tree the highlighted button would enable us to see only those folders where there are DataSources defined.
SAP AG
DBW70E
4-12
*HQHUDO ,QIRUPDWLRQ 'HVFULSWLRQV 5HFRQFLOLDWLRQ IODJ QRW IXQFWLRQDO 2SHQLQJ %DODQFH LQYHQWRU\ (UURU KDQGOLQJ GXSUHFV
SAP AG 2006
All types of DataSources will be defined in this way - a one-fits-all approach. Data Reconciliation is an information flag, ie that the DataSource is used for reconciliation purposes. (There is a How-to paper in SAP Service Marketplace with more information on using DataSources for reconciliation).
SAP AG
DBW70E
4-13
SAP AG 2006
In the 3.x world, you had to define InfoSources to bring data to the InfoCube, and everything was ruled by an InfoPackage running at run-time that could be scheduled, with optional involvement of the PSA. Optionally, process chains could be used for the scheduling.
SAP AG
DBW70E
' g & 6 2 g e d ' 6 7 "%4 ! 4 f57 bg%5448' p n s k li r 4 ' g "& 7 7 4 & & om m lj45qh557 7 p n k i ' g & v u t & ' g w54"qh&
4-14
y 7 x 6 Xl7 4 !
6$3 1HW:HDYHU %,
3URFHVV &KDLQ PDQGDWRU\
,PSURYHG WUDQVSDUHQF\ RI VWDJLQJ SURFHVVHV DFURVV GDWD ZDUHKRXVH OD\HUV ,PSURYHG SHUIRUPDQFH RSWLPL]HG SDUDOOHO SURFHVVLQJ (QKDQFHG HUURU KDQGOLQJ (QDEOHV QHDUUHDO WLPH XSGDWH
SAP AG 2006
Data Flow Control of SAP NW 2004s is covered in a later unit. Highlights are The Source System is still outside BI The DataSource is physically represented by a PSA table. This is generated together with a DataSource. On top we have the transformation which brings data from the PSA area to any kind of target (an InfoCube in this case). At designtime we mainly model the DataSource and the transformation. But additionally we see that the runtime must be modeled as well. We need an InfoPackage that is now only capable of bringing data from the external source to the DataSource/PSA level. The InfoPackage only can load data from Source System to PSA without any transformation From here a separate Data Transfer Process defines which way the data flows into the target areas. The DTP says by which transformation the data has to be passed into a certain target. Every path from persistent source to target is a Data Transfer Process. The key benefits are that we have improved transparency of the staging process across data warehouse layers. We have improved performance here via an optimized parallelization of the data processing. We have with the DTP new error-handling capabilities and we can also enable near-real-time staging scenarios (More on this in a later unit). All of these InfoPackages/Data Transfer Processes should be included into a process chain to automate the loading process. Now process chains are more important. They are manadatory in that we must bring two things together the InfoPackage and the Data Transfer Process. The InfoPackage is always PSA Only working with the new DataSource. A DTP is necessary to finalize your load process and to bring the data into a real operable target object like the InfoCube in this example..
SAP AG DBW70E 4-15
z ! } | z | ~ e 1 & { e p n j 4 ' g h& 47 7 4 & & s~457 7 p n ' g & v u t & ' g w54rh&
1RW RSWLPL]HG IRU PDVV GDWD WUDQVIHU 1R SDFNDJLQJ RI GDWD )XOO 0RGH 2QO\
SAP AG 2006
In some cases it is also an option to simplify this data flow concept. So a DataSource / PSA table is not always mandatory. In some scenarios it does not make sense eg master data. Normally master data is not mass data. In this case we do not have the possibility to package the data. Only full extraction mode is possible. Process chains would be optional here, although ususal.
SAP AG
DBW70E
5HVWULFWLRQV
'DWD6RXUFH
5HODWLRQDO 6RXUFH
6$3 6RXUFH
)LOH
SAP AG 2006
Via DB Connect / UD Connect we can reach any relational source on a standard platform. DB Connect still goes againsty the paltforms ported for the SAP NetWeaver Basis. UD Connect gives accessiblity to any kind of multidimensional sources
SAP AG
DBW70E
0 (' 98"& $ #
;0/
4-17
i fU B e d c C C h gG4XDE XB
+LJKOLJKWV
3RZHUIXO QDWLYH 64/ FRQQHFWLRQ WR DOO '% SODWIRUPV RI 6$3 1HW:HDYHU $6 (QDEOHG YLD PXOWL FRQQHFW IHDWXUH RI WKH 6$3 1HW:HDYHU $6 '% ,QWHUIDFH (QKDQFHG ZLWK SUHYLHZ IHDWXUHV QRZ 'LUHFW $FFHVV WR WKH H[WHUQDO '% LQ D UHPRWH VFHQDULR QRZ DOVR SRVVLEOH HYHQ IRU PDVWHU GDWD GXULQJ TXHU\ SURFHVVLQJ
SAP AG 2006
A real integration scenario is thus possible now with DB Connect, in terms of remote access (direct access) against transactional DQG master data.
SAP AG
DBW70E
4-18
SAP AG 2006
We go via a database table adapter type, and here we see the most important parameters to bring up the connection.
SAP AG
DBW70E
4-19
([WUDFWLRQ DGDSWHU W\SH '% 7DEOH FRQQHFWLRQ WR WDEOHYLHZ DXWKRUL]DWLRQ YLD '% XVHU LQ 6RXUFH 6\VWHP SDUDPHWHU
SAP AG 2006
Under Extraction we see the adapter type Database table and via this adapter we can examine tables or views on the database. In this case all tables or views for which the database user Rudi has authority can be chosen as an entry.
SAP AG
DBW70E
4-20
SAP AG 2006
In designtime you get a proposal, which gives metadata information of the table or view against which you are connected. You will see the database field names, internal/external data types to be mapped.The system will make a proposal for automatic data type conversions. This then can be reworked via the designer. Finally you copy the proposal into the field list.
SAP AG
DBW70E
4-21
SAP AG 2006
In the field list you can come up with template InfoObjects to offer different data types/lengths etc. Finally you decide the structure of your DataSource and which InfoObjects should be involved. The InfoObject is not mandatory here. This is a kind of modeling where you normally work with normal data types/descriptions
SAP AG
DBW70E
4-22
3UHYLHZ &KHFN WHFKQLFDO FRQYHUVLRQV GXULQJ GHVLJQ WLPH 6SRW WHVW IRU GDWD TXDOLW\
SAP AG 2006
During designtime after activation of the DataSource the Preview feature will be able to bring up the external data. This is the first look at it, and thus here at designtime you can check your technical conversions, by looking at, say, the first twenty data records. It is a spot test for data quality eg are all the order dates in the same format?
SAP AG
DBW70E
4-23
I q t s C C 8E DB
6$3 6RXUFH )LOH ;0/
i fU B e d c C C h gG4XDE XB
0XOWL 'LPHQVLRQDO 6RXUFH
0 (' 98"& $ #
SAP AG
SAP AG 2006
DBW70E
'DWD6RXUFH
4-24
+LJKOLJKWV
$UFKLWHFWXUH
%, -DYD &RQQHFWRUV
SAP AG 2006
The umbrella over UDC is UDI (Universal Data Integration). UDC is the implementation object of UDI in the BI area. We are working with industry standards.
SAP AG
)XOO\ OHYHUDJH WKH 6$3 1HW:HDYHU -(( FRQQHFWLRQ IUDPHZRUN DQG SURYLGH LQWHJUDWLRQ ZLWK GLYHUVH GDWD VRXUFHV ,Q FXVWRP DSSOLFDWLRQV LQ WKH 6$3 1HW:HDYHU (QWHUSULVH 3RUWDO
DBW70E
4-25
%XVLQHVV ,QWHOOLJHQFH
%, -DYD 6'.
'DWD6RXUFH
8QLYHUVDO 'DWD ,QWHJUDWLRQ -'%& &RQQHFWRU 2/( '% IRU 2/$3 ;0/ IRU $QDO\VLV &RQQHFWRU &RQQHFWRU 6$3 4XHU\ &RQQHFWRU
SAP AG 2006
An entire overview of UDI with everything in the SAP NW environment here J2EE server is involved. UDI is mainly part of the Java stack. We see several types of connectosr: JDBC Connector can run against non-SAP relational DataSources ODBO Connector can run against non-SAP multidimensional source systems XMLA Connector can run against non-SAP multidimensional source systems as well or against another BI system SAP Query Connector is designed to run against SAP source systems only this has a proprietary format, based on the SAP Query standards.
All these cannectors can help to do data acquisition handing over data to BI which hands it over to the data warehouse layer or to virtual InfoProviders as well. The BI Java SDK can help you to build your own applications within SAP NW against all these DataSources, based on the same UDI Connector types to run your own applications in a BI portal for example.
SAP AG
i fU B e d c C C 4h gG44XE XB
3VaXYDB T G%Q8@HaE XB ` V W VU S R H P I F C C
1RQ6$3 5HODWLRQDO
1RQ6$3 0XOWLGLPHQVLRQDO
6$3 1HW:HDYHU %,
6$3
$Q\ 6RXUFH
DBW70E
4-26
SAP AG 2006
If we want to create a Source System in BI that goes via this Java stack, we must specify the RFC destination first, and save against the J2EE engine. The J2EE server has a logical system name. Specify the JDBC type, and give it a name. Then the source system name is very important (JNDI Name) because this will point to the source from where we want to get the data.
SAP AG
DBW70E
4-27
SAP AG 2006
What is behind the JNDI Source System name? This is something already configured on the J2EE engine. To run this scenario, you must define the connector types on your J2EE engine. The connector configuration information here shows the detailed configuration properties JDBC driver, user, ip address, database name etc
SAP AG
DBW70E
4-28
In the BI DataSource definition in Modeling see the new adapter type (UDC for binary transfer). The UDC source object can be chosen now. Note the tables/views the BWALEREMOTE user owns on the system.
SAP AG
DBW70E
4-29
SAP AG 2006
After generation we see via this adapter type the same designtime features as for DB Connect. In this case the Source system is specified on the J2EE server. We see under Source System cell the RFC destination of the J2EE engine. NB some steps must be done on the J2EE server in the visual administrator of the J2EE engine. (This is described in a How-To paper on SAP Service Marketplace).
SAP AG
DBW70E
4-30
8 D
6$3 6RXUFH )LOH ;0/
gG4XD X
0XOWL 'LPHQVLRQDO 6RXUFH
aXY3 Ylu8 G X
5HODWLRQDO 6RXUFH
98"
55854 3
" @%98"
SAP AG
SAP AG 2006
DBW70E
'DWD6RXUFH
4-31
+LJKOLJKWV
2QO\ YHU\ OLWWOH LQIRUPDWLRQ RQ VRXUFH ILOHV QHFHVVDU\ +HOSIXO SURSRVDOV GXULQJ GHVLJQWLPH $XWRPDWHG FRQYHUVLRQ RI H[WHUQDO GDWD W\SHV DQG IRUPDWV SURYLGHG 3UHYLHZ RSWLRQ
SAP AG 2006
Also Direct Access will be an option data need not be available persistently in BI.
SAP AG
DBW70E
4-32
([WUDFWLRQ )LOH $GDSWHU 6RXUFH GHVWLQDWLRQ )LOH QDPH 1XPEHU RI KHDGHU URZV 'DWD IRUPDW 1XPEHU IRUPDW
SAP AG 2006
SAP AG
DBW70E
4-33
3URSRVDO )LOH $GDSWHU /RDG ([DPSOH GDWD )LHOG QDPHV IURP KHDGHU URZ 'DWD W\SH GHWHFWLRQ 'DWH IRUPDW GHWHFWLRQ &RQYHUVLRQ ([LW SURSRVDO
SAP AG 2006
Example data can be loaded directly. We can get the field names from the header row. Data type / date format detection eg here FLDATE we can see it is an external format and a conversion routine is thus proposed by the system.
SAP AG
DBW70E
4-34
SAP AG 2006
Here we can assign the right types and lengths, and choose between external / internal formats. We find the quantity and unit fields here in the right compounding. The system here found that WUNIT is the right unit for LUGGWEIGHT.
SAP AG
DBW70E
4-35
SAP AG 2006
Here we can read preview data and see that the data has been converted in the right way. The field compundings, eg for currency keys, have been detected in the right way. Design process for the DataSource will be finalised here. Based on that you can model your transformations and data transfer processes.
SAP AG
DBW70E
4-36
8 D
6$3 6RXUFH )LOH ;0/
gG4XD X
0XOWL 'LPHQVLRQDO 6RXUFH
aXY3 Ylu8 G X
5HODWLRQDO 6RXUFH
98"
55854 3
" @%98"
SAP AG
SAP AG 2006
DBW70E
'DWD6RXUFH
4-37
'DWD6RXUFH [
SAP AG 2006
We will consider how the classic DataSources available via Plug-in on the ERP side look now under the DataSource concept of SAP NW 2004s BI. If you implement SAP NW 2004s BI and replicate DataSources from the SAP ERP world into this environment or if you upgrade from 3.x then you will find the 3.x DataSources marked with a little square.
SAP AG
DBW70E
4-38
SAP AG 2006
The system will show these classic 3.x DataSources in the same way. It is an emulated view on those DataSources. Note the three tabstrips offered.
SAP AG
DBW70E
4-39
SAP AG 2006
Under the Extraction tabstrip there are the many known delta processes offered - no changes here.
SAP AG
DBW70E
4-40
SAP AG 2006
Consider the Adapter type name shown. Note that Real-Time Data Acquisition is not supported here. For that we would need another type of DataSource. Synchronous Extraction SAPI is possible here ie classic Remote Cube handling would be possible.
SAP AG
DBW70E
3l
4-41
SAP AG 2006
Under the Fields tabstrip we find the entire description of this DataSource in the same way.
SAP AG
DBW70E
4-42
SAP AG 2006
This is an overview of examples of DataSource lifecycles. A migration would be possible for the BW 3.x DataSource. You can undo the migration. But you have to decide on one way. XOR means a DataSource in SAP NW 2004s BI can either look like a SAP NW 2004s DataSource, or like a 3.x DataSource but ERWK is not possible. If you do an additional replication of your 3.5 DataSource from OLTP to SAP NW 2004s BI, then this additional replication will definitely lead you into a SAP NW 2004s (7.0) DataSource after the replication. A third possibility is that if you have your own DataSources not yet activated in the OLTP system, (customer-owned or another BCT DataSource in D version) when you replicate into a SAP NW 2004s environment the system must decide which way to go or will offer a dialog for a selection.
SAP AG
DBW70E
l lr r
4-43
r l% ~ 4r
G gaa Da q D
l rj l r h f
~4 r G4 a Dl r l
hA
&RQVHTXHQFH
$ 'DWD6RXUFH LQ RQH VSHFLILF /RJV\V LQ WKH %, V\VWHP FDQ HLWKHU H[LVW DV QHZ 'DWD6RXUFH RU [ 'DWD6RXUFH ERWK REMHFWV DW WKH VDPH WLPH DUH 127 DOORZHG $W UHSOLFDWLRQ WLPH D GHFLVLRQ IRU RQH REMHFW W\SH KDV WR EH WDNHQ +LHUDUFK\ 'DWD6RXUFHV DUH QRW \HW VXSSRUWHG LQ 6$3 1: V%, DV QHZ 'DWD6RXUFH DQG DUH WKHUHIRUH DOZD\V UHSOLFDWHG DV [ 'DWD6RXUFH ([SRUW 'DWD6RXUFHV LQ WKH 0\VHOI V\VWHP DUH DOZD\V UHSOLFDWHG DV [ 'DWD6RXUFH
7HFKQLFDO UHVWULFWLRQV
SAP AG 2006
This is the most important information comparing the two concepts. Only one format is allowed. If we replicate data a decision must be taken. Note the restrictions on the slide.
SAP AG
DBW70E
4-44
'9HUVLRQV RI %&7 'DWD6RXUFHV H[LVW LQ %, DIWHU UHSOLFDWLRQ RI 6RXUFH 6\VWHP RU $SSOLFDWLRQ &RPSRQHQWV ([FHSWLRQ )LOH 'DWD6RXUFHV DUH GHOLYHUHG ZLWK %, :KHQ JURXSLQJ %&7 2EMHFWV IRU DFWLYDWLRQ WKH %, V\VWHP FROOHFWV LQ %, WKH '9HUVLRQV RI WKH 'DWD6RXUFHV 'XULQJ FROOHFWLRQ WKH V\VWHP DOUHDG\ FKHFNV WKH DXWKRUL]DWLRQV UHPRWHO\ 'XULQJ DFWLYDWLRQ WKH 'DWD6RXUFHV LQ WKH VRXUFH V\VWHP DUH WUDQVIHUUHG WR WKH DFWLYH YHUVLRQ DQG UHSOLFDWHG LQ WKH %, V\VWHP 'HSHQGLQJ RQ WKH H[LVWLQJ %XVLQHVV &RQWHQW WKH V\VWHP GHFLGHV ZKLFK 'DWD6RXUFH W\SH KDV WR EH JHQHUDWHG 1HZ 'DWD6RXUFH 'DWD6RXUFH [ $FWLYDWLRQ YLD WUDQVDFWLRQ 56$ LQ WKH 6RXUFH 6\VWHP LV WKHUHIRUH REVROHWH QRZ
SAP AG 2006
SAP AG
DBW70E
4-45
None
Does the DataSource currently exist in the other object type
both (not allowed -> Content Governance) Exactly one Does the DataSource already exist? No Yes No
Does the caller (e.g. After-Import Method) prefer a version?
Yes
Yes
No
SAP AG 2006
Internally when deciding which way to go in many cases the system can decide. If not possible, a dialog will appear
SAP AG
DBW70E
) 9g ) 9 bX ) @ gaGb g9 5 5 g) g)3 9 g
Yes No Is it in a dialog? Yes
Ask the User and create the DataSource accordingly
No
Skip the DataSource and let the User replicate in Dialog
4-46
'DWD6RXUFH
5HODWLRQDO 6RXUFH
6$3 6RXUFH
)LOH
SAP AG 2006
Many things have changed in Web Services. XML formats are coming up increasingly. Especially the SAP PI (Process Integrator) is an example which delivers XML data formats.
SAP AG
DBW70E
" X
98"
;0/
4-47
55854 3
gG4XD X
+LJKOLJKWV
$GDSWHU 7\SH :HE 6HUYLFH SXVK LQWR 36$ ,QIR3DFNDJH PDQGDWRU\ VR FDOOHG 3XVK3DFNDJH 2QH 6WHS *HQHUDWLRQ RI $%$3 )XQFWLRQ 0RGXOH DQG 62$3 FRPSOLDQW :HE 6HUYLFH 1DYLJDWLRQ WR :HE 6HUYLFH $GPLQLVWUDWLRQ ZLWK 7HVW HQYLURQPHQW IRU HDUO\ SURWRW\SLQJ
SAP AG 2006
We stay with the PSA technique here, not in the delta queue as in 3.5. InfoPackage is thus mandatory known as Push-package. The incoming XML format will be transformed into ABAP format.
SAP AG
DBW70E
4-48
([WUDFWLRQ :HE6HUYLFH $GDSWHU JHQHUDWHG )XQFWLRQ $%$3 0RGXOH JHQHUDWHG 62$3 FRPSOLDQW :HE6HUYLFH
SAP AG 2006
This is the main part of the Web Service Adapter. We find the adapter type Web Service Push. Two objects are generated the function module and the web service object. Both are generated after the definition of the structure
SAP AG
DBW70E
4-49
SAP AG 2006
Here we see the field list. To design the structure of your Web Service DataSource you would start with your InfoObject templates, and then find field description and properties. So just define your structure via a list of InfoObjects, bring it in here, generate the structure and you will get the function module and web service as seen on previous slide
SAP AG
DBW70E
4-50
SAP AG 2006
Having defined your Web Service DataSource, and activated it you can navigate into the Web Service Administration and find this test tool. There is an input dialog so you can type in data and directly send it into your PSA table which has also been generated for your Web Service. This is an easy way to bring data in manually to the BI environment
SAP AG
DBW70E
4-51
0LJUDWLRQ 2YHUYLHZ
&ODVVLF [ GDWDIORZ PHFKDQLVPV DUH VWLOO HIIHFWLYH 0LJUDWLRQ WR QHZ 'DWDIORZ LV QRW PDQGDWRU\
0LJUDWLRQ RSWLRQDO
1HZ 7UDQVIRUPDWLRQ DQG 'DWD 7UDQVIHU 3URFHVV KDQGOLQJ FDQ EH LPSOHPHQWHG RQ WRS ZLWK QR FKDQJHV WR WKH [ 'DWD6RXUFH RQ GDWDEDVH OHYHO
(PXODWLRQ SURYLGHV [ 'DWD6RXUFHV LQ WKH VKDSH RI QHZ 'DWD6RXUFHV 1:V DV UXQWLPH REMHFW
/HDGV LQWR '% PLJUDWLRQ ZLWK GHOHWLRQ RI ROG [ 'DWD6RXUFH REMHFWV 'HOHWLRQ RI PDSSLQJ DQG WUDQVIHU UXOHV 0LJUDWLRQ RI ,QIR3DFNDJH DQG 36$ WDEOH
SAP AG 2006
SAP AG
DBW70E
4-52
36$
F 8' # API H@) G@4 ) Q 2 0 ( 0 C 4 # DE $" " @ ! ! C 7 @BD4 0 ) ! @B A' $'@9
'DWD6RXUFH
1RQ6$3
SAP AG 2006
Here we see both worlds in one view. In SAP NW 2004s BI on left is a 3.x inbound adapter involving an InfoSource. On the right we have a leaner solution. The inbound adapter could be a Web Service, Real-time Data Acquisition, Direct Access, Data Transfer Process, Direct Load or InfoPackage load into the PSA. The PSA is directly linked to the DataSource (whenever you activate a DataSource you normally get the generation of a PSA table). Based on the DataSource you then have a transformation, and a Data Transfer Process
SAP AG
DBW70E
,QERXQG $GDSWHU
4-53
'DWD6RXUFH
1RQ6$3
SAP AG 2006
If you upgrade 3.x -> SAP NW 2004s you see everythng as we see on left hand side. If you want to migrate your 3.x DataSource into a SAP NW 2004s BI DataSource, then use the inbound adapter functionality which will mean losing your DataSource, Transfer Rules and PSA. Bear this in mind if there is complicated logic within your transfer rules. You will need to migrate this earlier into a transformation. Then you can do the DataSource migration. This will mean a new PSA table will be generated. There should not be data in your PSA table when you do the migration, as it will be lost.
SAP AG
DBW70E
,QERXQG $GDSWHU
4-54
1RQ6$3
SAP AG 2006
Another option is the emulation of a 3.x DataSource. This means you not only will get an emulated view on the 3.x DataSource via the user interface. Emulation in the data flow design will mean that a transformation and a data transfer process can also be based on a classic 3.x DataSource and its PSA table / transfer rule mechanism.
SAP AG
DBW70E
4-55
'DWD6RXUFH [
This is how it appears in the system. Here a generic DataSource replicated from R/3 into SAP NW 2004s is marked with the square symbol. In the context menu, you will see that migration is offered here. Also InfoPackage and Transfer Rules can be created. And also a transformation can be created. So a transformation can be created with Data Transfer Processes on top of this DataSource if you want. But you can also go for the 3.x approach as well. If you go for migration the following slides will show the options
SAP AG
DBW70E
4-56
1HZ 'DWD6RXUFH
SAP AG 2006
In this case case after migration the DataSource will get the new icon without the square. If you look in the context menu there is only an option to Create Transformation and Create InfoPackage. A back migration is possible but this has to be chosen from the transaction RSDA.
SAP AG
DBW70E
4-57
SAP AG 2006
After migration the adapter type for this DataSource will be Access to SAP Data through Service API. Alternatively it is possible to choose Synchronous Extraction SAPI (for Virtual Cubes and Tests) .
SAP AG
DBW70E
4-58
SAP AG 2006
The source fields will appear in the same way after migration.
SAP AG
DBW70E
4-59
SAP AG 2006
For the adapter type Synchronous Extraction SAPI (for Virtual Cubes and Tests) it is also possible to look at the data directly via the Preview tabstrip.
SAP AG
DBW70E
4-60
SAP AG 2006
Hear we see the normal Read Preview Data option via the Preview tabstrip.
SAP AG
DBW70E
4-61
SAP AG 2006
Note the processing option for an InfoPackage designed for a new BI DataSource type. In this case we find Only PSA as the only option available here. So in the new Data Flow concept InfoPackages just bring data from the Source System into the PSA. From here DTPs have to bring data to the targets via the dedicated transformations.
SAP AG
DBW70E
4-62
([WUDFWLRQ 1HZ 'DWD6RXUFH FRQFHSW 7UDQVIRUPDWLRQ (QKDQFHG WUDQVIRUPDWLRQ HQJLQH /RDG 1HZ 'DWD 7UDQVIHU 3URFHVV FRQFHSW '73
SAP AG
R R R
8QLTXH ORRN DQG IHHO IRU DOO RI WKH 'DWD6RXUFH W\SHV %DVHG RQ SURYHQ 36$ WHFKQRORJ\ 'LUHFWUHPRWH DFFHVV FDSDELOLWLHV DUH DOZD\V DQ RSWLRQ 2SWLPL]DWLRQ RI SUHVHQW H[WUDFWLRQ FRQFHSWV ZKHUH QHFHVVDU\
,PSURYHG GHVLJQWLPH KDQGOLQJ ,PSURYHG ORDG SHUIRUPDQFH ,PSURYHG HUURU KDQGOLQJ )HDWXUHV '73 HUURU KDQGOLQJ
DBW70E
4-63
'HVFULEH KRZ WR LPSOHPHQW D GDWDEDVH FRQQHFWLRQ IURP DQ 6$3 1HW:HDYHU V %, V\VWHP WR D UHODWLRQDO GDWDEDVH YLD '% &RQQHFW GDWD VRXUFH
([SODLQ WKH PRVW LPSRUWDQW DVSHFWV RI WKH 'DWD 6RXUFH FRQFHSW ZLWKLQ 6$3 1HW:HDYHU V
'HVFULEH WKH 8' &RQQHFW DQG 6$3, LQWHUIDFHV ZLWKLQ 6$3 1: V +LJKOLJKW LPSRUWDQW IHDWXUHV RI :HE 6HUYLFHV ZLWKLQ 6$3 1: V 3URYLGH DQ RYHUYLHZ RI PLJUDWLRQ DVSHFWV FRQFHUQLQJ %, 'DWD 6RXUFHV LQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
4-64
'HVFULEH KRZ WR LPSOHPHQW D GDWDEDVH FRQQHFWLRQ IURP DQ 6$3 1HW:HDYHU V %, V\VWHP WR D UHODWLRQDO GDWDEDVH YLD '% &RQQHFW GDWD VRXUFH
([SODLQ WKH PRVW LPSRUWDQW DVSHFWV RI WKH 'DWD 6RXUFH FRQFHSW ZLWKLQ 6$3 1HW:HDYHU V
'HVFULEH WKH 8' &RQQHFW DQG 6$3, LQWHUIDFHV ZLWKLQ 6$3 1: V +LJKOLJKW LPSRUWDQW IHDWXUHV RI :HE 6HUYLFHV ZLWKLQ 6$3 1: V 3URYLGH DQ RYHUYLHZ RI PLJUDWLRQ DVSHFWV FRQFHUQLQJ %, 'DWD 6RXUFHV LQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
4-65
SAP AG
DBW70E
4-66
([HUFLVHV
/HVVRQ 8QLW &RQFHSW IRU %, 'DWD 6RXUFHV ZLWKLQ 6$3 1: V 'DWD $FTXLVLWLRQ
You need to familiarize yourself with the new DataSource creation process and in particular for DBCONNECT Source Systems.
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1 Go to the Data Warehousing Workbench for Modeling and find the Source Systems tree. Via the DB Connect context menu locate the source system with logical system name =066B and source system name ,'' 066 1: *URXS . You should get a message confirming the connection is OK. Then open the data source tree list via the context menu. Create a new DataSource within the application component =7B'%:( which is found under =%:B75$,1,1*. The DataSource should be called =066B'6B;; and be of type 7UDQVDFWLRQ GDWD. Select a full screen view by hiding the navigator. In the DataSource definition specify descriptions of 1: ,QYRLFHV ;;. In the Extraction tabstrip choose to select '% 9LHZV and the DB object 58',192,&(6. View the list of fields in the Proposal tabstrip. Here we could bring in adjustments of the DataSource structure. No additional changes are necessary for this exercise. Just 6DYH and $FWLYDWH the DataSource. Then go to the Preview and have a quick look at the data. .
1-2
1-3
1-4
1-5
SAP AG
DBW70E
4-67
SAP AG
DBW70E
4-68
6ROXWLRQV
8QLW 'DWD $FTXLVLWLRQ
/HVVRQ
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1 Go to the Data Warehousing Workbench for Modeling and find the Source Systems tree. Via the DB Connect context menu locate the source system with logical system name =066B and source system name ,'' 066 1: *URXS 1-1-1 1-1-2 1-1-3 1-1-4 1-1-5 1-1-6 From the SAP Easy Access menu select 0RGHOLQJ ! 'DWD :DUHKRXVLQJ :RUNEHQFK ! 0RGHOLQJ
If you get a pop-up message about documentation select the check box to not show the question again and press <HV Click on the +LGH6KRZ (PSW\ )ROGHUV icon so that all possible source systems groupings are visible Highlight '% &RQQHFW and on right-hand mouse context menu choose &UHDWH Specify Logical System Name: =066B;;, Source System Name: ,'' 066 1: *URXS ;;, Type and Release: (blank)
1-2
Via the context menu of the new system check the connection. You should get a message confirming the connection is OK. Then open the data source tree list via the context menu. 1-2-1 Highlight the source system ,'' 066 1: *URXS within the '% &RQQHFW grouping. On right-hand mouse context menu choose &KHFN. The message should appear Source system connection ZMSS_00 OK . On right-hand mouse context menu choose 'LVSOD\ 'DWD6RXUFH 7UHH. The list of DataSources should appear.
1-2-2
1-3
Create a new DataSource within the application component =7B'%:( which is found under =%:B75$,1,1*. The DataSource should be called =066B'6B;; and be of type 7UDQVDFWLRQ GDWD. 1-3-1 1-3-2 1-3-3 1-3-4 1-3-5 Expand the node =%:B75$,1,1* Highlight the application component =7B'%:( On context menu choose &UHDWH 'DWD6RXUFH Specify DataSource: =066B'6B;;, Source System: =066B, Data Type DataSource: 7UDQVDFWLRQ 'DWD. Press 7UDQVIHU (QWHU
SAP AG
DBW70E
4-69
1-4
Select a full screen view by hiding the navigator. In the DataSource definition specify descriptions of 1: ,QYRLFHV ;;. In the Extraction tabstrip choose to select '% 9LHZV and the DB object 58',192,&(6. 1-4-1 1-4-2 1-4-3 1-4-4 1-4-5 Select +LGH6KRZ 1DYLJDWRU so that your DataSource screen is in fullscreen mode Under tabstrip *HQHUDO ,QIR specify short, medium and long descriptions of 1: ,QYRLFHV ;;. Under tabstrip ([WUDFWLRQ click on the Table/View cell. Press the selector (F4 function key). Select Tables: 1R (uncheck the box), Select Views: <HV (check the box). Press ([HFXWH. In the list that appears, select 58',192,&(6 by double-click
1-5
View the list of fields in the Proposal tabstrip. Here we could bring in adjustments of the DataSource structure. No additional changes are necessary for this exercise. Just 6DYH and $FWLYDWH the DataSource. Then go to the Preview and have a quick look at the data . 1-5-1 1-5-2 1-5-3 1-5-4 1-5-5 1-5-6 Under tabstrip 3URSRVDO, view the list of fields and their settings. Press 6DYH. Press $FWLYDWH. Under tabstrip 3UHYLHZ select 5HDG 3UHYLHZ 'DWD. A list of data records with order data should appear. Keep pressing ([LW until you return to the SAP Easy Access menu
SAP AG
DBW70E
4-70
([HUFLVHV
/HVVRQ 8QLW &RQFHSW IRU %, 'DWD 6RXUFHV ZLWKLQ 6$3 1: V 'DWD $FTXLVLWLRQ
You need to familiarize yourself with the new DataSource creation process and in particular for File Source Systems.
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1
Go to the Data Warehousing Workbench for Modeling and find the Source Systems tree. Expand the )LOH grouping, and select source system ,B(;7(51. Open the DataSource tree list via the context menu. Create a new DataSource within the application component =7B),/(B'6 which is found under =7B'%:( within =%:B75$,1,1*. The DataSource should be called =),B'6B;; and be of type 7UDQVDFWLRQ GDWD. Select a full screen view by hiding the navigator. In the DataSource definition specify descriptions of )OLJKW 'DWD )LOH ;;. In the Extraction tabstrip choose the Adapter type /RDG 7H[W7\SH )LOH IURP $SSOLFDWLRQ 6HUYHU and select file GVDJFVY from ',5B75$16 ! 7UDLQLQJ ! &69 Complete the Extraction screen by choosing Header rows to be ignored as Data Format Data Separator as a semi-colon () Thousands Separator as period () Decimal Point Separator as comma () View the proposal data and fields under the Proposal tabstrip by selecting to load example data. In particular, look at the dates (field FLDATE) on the first few data records. In the Fields tabstrip ensure the proposals are copied into the field list. In here make a change to the field CARRID to make it data type &+$5. Also note the settings for the field FLDATE, in particular the field length and the required output field length (External Length). Then Save and Activate the DataSource.
1-2 1-3
1-4
1-5
1-6
1-7
SAP AG
DBW70E
4-71
1-8
View the preview data in the Preview tabstrip to see how the data will appear in BW. In particular, examine the data in the column FLDATE and consider if this is correctly interpreted? Make corrections under the Fields tabstrip, by setting the output (External) length to 10, reactivate the DataSource and then review the data under the Preview tabstrip. .
SAP AG
DBW70E
4-72
6ROXWLRQV
8QLW 'DWD $FTXLVLWLRQ
/HVVRQ
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1
Go to the Data Warehousing Workbench for Modeling and find the Source Systems tree. Expand the )LOH grouping, and select source system ,B(;7(51. 1-1-1 From the SAP Easy Access menu select 0RGHOLQJ ! 'DWD :DUHKRXVLQJ :RUNEHQFK ! 0RGHOLQJ
If you get a pop-up message about documentation select the check box to not show the question again and press <HV Click on the +LGH6KRZ (PSW\ )ROGHUV icon so that all possible source systems groupings are visible Highlight )LOH and expand the list of File Source Systems. Highlight Source System ,B(;7(51.
Open the DataSource tree list via the context menu. 1-2-1 On right-hand mouse context menu choose 'LVSOD\ 'DWD6RXUFH 7UHH. The list of DataSources should appear.
1-3
Create a new DataSource within the application component =7B),/(B'6 which is found under =7B'%:( within =%:B75$,1,1*. The DataSource should be called =),B'6B;; and be of type 7UDQVDFWLRQ GDWD. 1-3-1 1-3-2 1-3-3 1-3-4 1-3-5 1-3-6 Expand the node =%:B75$,1,1* Expand the node =7B'%:(
Specify DataSource: =),B'6B;;, Source System: ,B(;7(51, Data Type DataSource: 7UDQVDFWLRQ 'DWD.
1-4
Select a full screen view by hiding the navigator. In the DataSource definition specify descriptions of )OLJKW 'DWD )LOH ;;. In the Extraction tabstrip choose the Adapter type /RDG 7H[W7\SH )LOH IURP $SSOLFDWLRQ 6HUYHU and select file GVDJFVY from ',5B+20(. 1-4-1 1-4-2 1-4-3 1-4-4 Under tabstrip *HQHUDO ,QIR specify short, medium and long descriptions of )OLJKW 'DWD )LOH ;;. Choose the Adapter type /RDG 7H[W7\SH )LOH IURP $SSOLFDWLRQ 6HUYHU . DBW70E 4-73 Select +LGH6KRZ 1DYLJDWRU so that your DataSource screen is in fullscreen mode
SAP AG
1-4-5
Click on the cell 1DPH RI WKH )LOH. Press the selector (F4 function key). In the Select Input Help window choose AL11 Files. Select directory ',5B75$16 by double-click, then directory 7UDLQLQJ by double-click, then directory &69 by double-click. Scroll down till you find file GVDJFVY. Double-click on this. In the Selection window choose Copy Name.
1-4-6 1-5
Complete the Extraction screen by choosing Header rows to be ignored as Data Format Data Separator as a semi-colon () Thousands Separator as period () Decimal Point Separator as comma () 1-5-1 1-5-2 1-5-3 Specify Data Format: 6HSDUDWHG ZLWK 6HSDUDWRU IRU ([DPSOH &69. In the boxes that appear - specify Data Separator as semi-colon () Specify Number Format: 'LUHFW (QWU\. In the boxes that appear - specify Thousands Separator as period () Decimal Point Separator as comma () Specify Header rows to be ignored:
1-6
View the proposal data and fields under the Proposal tabstrip by selecting to load example data. In particular, look at the dates (field FLDATE) on the first few data records. 1-6-1 1-6-2 Under tabstrip 3URSRVDO, view the sample data records by pressing pushbutton /RDG ([DPSOH 'DWD. File output is produced, showing the first 20 data records. Below that you will see the field proposal, with field names and properties including conversion routines. All proposals can be changed in a later step.
1-7
In the Fields tabstrip ensure the proposals are copied into the field list. In here make a change to the field CARRID to make it data type &+$5. Also note the settings for the field FLDATE, in particular the field length and the required output field length (External Length). Then Save and Activate the DataSource. 1-7-1 Under tabstrip )LHOGV go to the row for the field &$55,'. Click on the cell 'DWD W\SH which should be offering the Data type UNIT. Via the selector (F4) choose Data type &+$5 via double-click. On the row for the field )/'$7(, length is , output length is not specified (blank), format is ([WHUQDO with conversion routine 56'$7. Make no changes to this row. Press $FWLYDWH. Press 6DYH.
View the preview data in the Preview tabstrip to see how the data will appear in BW. In particular, examine the data in the column FLDATE and consider if this is correctly interpreted? Make corrections under the Fields tabstrip, by setting the output (External) length to 10, reactivate the DataSource and then review the data under the Preview tabstrip. 1-8-1 Under tabstrip 3UHYLHZ, view how the sample data records will appear by pressing pushbutton 5HDG 3UHYLHZ 'DWD. A message should be shown indicating inbound processing of the data package is finished. The column FLDATE shows data fields in the format DD.MM.YYYY but the dates do not correspond to those you observed in the example data under the Proposal tabstrip. Go back to the settings by selecting tabstrip )LHOGV. Select the menu option 'DWD6RXUFH ! 'LVSOD\&KDQJH so that you are working in change mode.
Observe that for FLDATE the cell External indicates 8. Change this to . DBW70E 4-74
1-8-10
Keep pressing ([LW until you return to the SAP Easy Access menu
,I WKH 5HDG 3UHYLHZ 'DWD SXVKEXWWRQ LV QRW YLVLEOH SUHVV ([LW WZLFH WR UHWXUQ WR WKH6$3 (DV\ $FFHVV PHQX 7KHQ VHOHFW 'DWD :DUHKRXVLQJ :RUNEHQFK ! 0RGHOLQJ WR DJDLQ VHH WKH OLVW RI 'DWD6RXUFHV LQ 0RGHOLQJ SUHVV 5HIUHVK WUHH VWUXFWXUH DQG GRXEOH FOLFN RQ \RXU 'DWD6RXUFH =),B'6B;; 7KHQ WU\ WKH 3UHYLHZ WDEVWULS DJDLQ DQG WKH SXVKEXWWRQ 5HDG 3UHYLHZ 'DWD VKRXOG EH YLVLEOH Now try the above step again.
Select tabstrip 3UHYLHZ and view the sample data records again by pressing pushbutton 5HDG 3UHYLHZ 'DWD. The dates should now show correctly.
Press $FWLYDWH.
Press 6DYH.
SAP AG
DBW70E
4-75
SAP AG
DBW70E
4-76
([HUFLVHV
/HVVRQ 8QLW &RQFHSW IRU %, 'DWD 6RXUFHV ZLWKLQ 6$3 1: V 'DWD $FTXLVLWLRQ
Create a new DataSource for Source System type Web Services and push data via an XML interface into the PSA within BI.
You need to familiarize yourself with the new DataSource creation process and in particular for Web Services, including the push of data via XML into the PSA within BI.
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1
Go to the Data Warehousing Workbench for Modeling and find the Source Systems tree. Expand the :HE 6HUYLFH folder. Highlight the Source System =7B:6(59,&. Open the data source tree list via the context menu.
1-2 1-3
Create a new DataSource within the application component =7B:(%B6(59,&(6 which is found under =7B'%:( within =%:B75$,1,1*. The DataSource should be called =7B:6'6B;; and be of type 7UDQVDFWLRQ GDWD. Select a full screen view by hiding the navigator. In the DataSource definition specify descriptions of :HE 6HUYLFH '6 ;;. Go to the Fields tabstrip. Here define the structure of your Web Service by entering InfoObjects in the Template InfoObject column. In the first row specify &86720(5 as the template InfoObject and copy the InfoObject field properties to the DataSource. Likewise, further specify template InfoObjects 0$7(5,$/, &$/'$<, '2&B180%(5, 48$17,7<, 81,7, 1(7B35,&(, '2&B&855&< and ensure this sequence is observed. Change all field formats to ,QWHUQDO and DFWLYDWH the DataSource. Have a look at the generated function module via the Extraction tabstrip. Have a look at the PSA Administration. Look at the generated web service part of the DataSource.
1-4
1-5
SAP AG
DBW70E
4-77
Create an InfoPackage for your Web Service DataSource. Enter a description *HW ;0/ 'DWD ;; . Examine the screen contents in the Extraction tabstrip Make settings under the Processing tabstrip to put the automatic closure of the request to KRXU Also set the request size to rows. Launch the test of your Web Service. Enter test data Customer: Material: Calday: DocNumber: *URXS ;;B Quantity: Unit: 3& Net Price: DocCurrcy: 86' and send it. Then examine the results from this push into the BI PSA.
2-4 2-5
3-1
Monitor the request in the BI warehouse via the Manage PSA function.
SAP AG
DBW70E
4-78
6ROXWLRQV
8QLW 'DWD $FTXLVLWLRQ
/HVVRQ
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1
Go to the Data Warehousing Workbench for Modeling and find the Source Systems tree. Expand the :HE 6HUYLFH folder. Highlight the Source System =7B:6(59,&. 1-1-1 From the SAP Easy Access menu select 0RGHOLQJ ! 'DWD :DUHKRXVLQJ :RUNEHQFK ! 0RGHOLQJ
If you get a pop-up message about documentation select the check box to not show the question again and press <HV Click on the +LGH6KRZ (PSW\ )ROGHUV icon so that all possible source systems groupings are visible Highlight Source System =7B:6(59,&. Highlight :HE 6HUYLFH and expand the list of Web Service Source Systems.
Open the data source tree list via the context menu. 1-2-1 On right-hand mouse context menu choose 'LVSOD\ 'DWD6RXUFH 7UHH. The list of DataSources should appear.
1-3
Create a new DataSource within the application component =7B:(%B6(59,&(6 which is found under =7B'%:( within =%:B75$,1,1*. The DataSource should be called =7B:6'6B;; and be of type 7UDQVDFWLRQ GDWD. 1-3-1 1-3-2 1-3-3 1-3-4 1-3-5 1-3-6 Highlight the application component =7B'%:( Expand the node =%:B75$,1,1*
Specify DataSource: =7B:6'6B;;, Source System: =7B:6(59,&, Data Type DataSource: 7UDQVDFWLRQ 'DWD.
1-4
Select a full screen view by hiding the navigator. In the DataSource definition specify descriptions of :HE 6HUYLFH '6 ;;. 1-4-1 1-4-2 Under tabstrip *HQHUDO ,QIR specify short, medium and long descriptions of :HE 6HUYLFH '6 ;;. Select +LGH6KRZ 1DYLJDWRU so that your DataSource screen is in fullscreen mode
SAP AG
DBW70E
4-79
1-5
Go to the Fields tabstrip. Here define the structure of your Web Service by entering InfoObjects in the Template InfoObject column. In the first row specify &86720(5 as the template InfoObject and copy the InfoObject field properties to the DataSource. Likewise, further specify template InfoObjects 0$7(5,$/, &$/'$<, '2&B180%(5, 48$17,7<, 81,7, 1(7B35,&(, 0DOC_CURRCY and ensure this sequence is observed. Change all field formats to ,QWHUQDO and DFWLYDWH the DataSource. 1-5-1 1-5-2 1-5-3 1-5-4 1-5-5 1-5-6 1-5-7 1-5-8 1-5-9 Under tabstrip )LHOGV, in the first row enter &86720(5 in the cell Template InfoObject, and hit the HQWHU key. In the pop-up window select the pushbutton FRS\. Click on the ,QVHUW 5RZ button VHYHQ times. Press &KHFN which should result in a success message. In the new rows enter the following template InfoObjects in this sequence: 0$7(5,$/, &$/'$<, '2&B180%(5, 48$17,7<, 81,7, 1(7B35,&(, '2&B&855&< In the pop-up window select the pushbutton FRS\ (seven times).
For each row ensure that the field format is set to ,QWHUQDO by choosing this value using the selector.
Press the $FWLYDWH pushbutton, and accept any log display message by pressing &RQWLQXH HQWHU. You should receive a message to indicate the DataSource is activated.
1-6
Have a look at the generated function module via the Extraction tabstrip. 1-6-1 1-6-2 1-6-3 Select the tabstrip ([WUDFWLRQ. Observe the field )XQFWLRQ 0RGXOH and GRXEOHFOLFN on the Function Module name
Within the Function Module stay within the 6RXUFH FRGH tabstrip. On approximately the fifth line of coding consider the IMPORTING interface structure (beginning %,&:&4=7B:6'6). 'RXEOHFOLFN on the structure name. Then keep hitting %DFN until you return to the 'LVSOD\ 'DWD 6RXUFH screen
1-7
Have a look at the PSA Administration. 1-7-1 1-7-2 Still under the tabstrip ([WUDFWLRQ, click on the pushbutton 0DQDJH 36$. No data is present, which is as expected. Press &DQFHO )
1-8
Look at the generated web service part of the DataSource. 1-8-1 1-8-2 Still under the tabstrip ([WUDFWLRQ , click on the pushbutton :HE 6HUYLFH $GPLQLVWUDWLRQ. Expand the path under SOAP Application / Service Definition / Variant / Web Service Description, ie: 62$3 $SSOLFDWLRQ IRU 5)&&RPSOLDQW )0V ! %,&&4=7B:6'6 ! %,&&4=7B:6'6 ! :HE 6HUYLFH %,&&4=7B:6'6 Highlight this entry and then take the path :HE 6HUYLFH ! :6'/ (or press the WSDL pushbutton)
In the Settings pop-up that appears select the option 'RFXPHQW 6W\OH and press &RQWLQXH HQWHU
When prompted with the login popup, enter your :$6 8VHU 1DPH DQG 3DVVZRUG as given at the beginning of the class In the new browser session view the WSDL that appears When you have finished close the browser session by pressing ; in the top right-hand corner You will be in the :HE 6HUYLFH $GPLQLVWUDWLRQ IRU 62$3 5XQWLPH screen
SAP AG
DBW70E
4-80
1-8-9
Keep pressing %DFN until you return to the DataSource tree list within 'DWD :DUHKRXVLQJ :RUNEHQFK 0RGHOLQJ
2-1
Create an InfoPackage for your Web Service DataSource. Enter a description *HW ;0/ 'DWD ;;. 2-1-1
Highlight your Web Service DataSource =7B:6'6B;; and via the context menu select &UHDWH ,QIR3DFNDJH. In the InfoPackage pop-up enter a description *HW ;0/ 'DWD ;; , then press 6DYH HQWHU Note the name of the screen you are in 6FKHGXOHU ,QIR3DFNDJH IRU 5HDO7LPH 'DWD $FTXLVLWLRQ 3XVK Select +LGH6KRZ 1DYLJDWRU so that your DataSource screen is in fullscreen mode
2-1-2 2-1-3
2-2
Examine the screen contents in the Extraction tabstrip 2-2-1 2-2-2 2-2-3 2-2-4 View the General Adapter Attributes by pressing pushbutton 3URSHUWLHV, then press &RQWLQXH HQWHU Note the attributes for Real-Time Data Acquisition (Push enabled) Note that the Function Module and Web Service names are shown Select the ([WUDFWLRQ tabstrip
2-3
Make settings under the Processing tabstrip to put the automatic closure of the request to KRXU. Also set the request size to rows. 2-3-1 2-3-2 2-3-3 Under Automatic Closure of the Request set Hour to and Day to EODQN. Under Request Size: Number of Rows enter Select the 3URFHVVLQJ tabstrip
2-4
Launch the test of your Web Service. 2-4-1 2-4-2 2-4-3 Select the ([WUDFWLRQ tabstrip Press the pushbutton Web Service Administration. Expand the path under SOAP Application / Service Definition / Variant / Web Service Description, ie: 62$3 $SSOLFDWLRQ IRU 5)&&RPSOLDQW )0V ! %,&&4=7B:6'6 ! %,&&4=7B:6'6 ! :HE 6HUYLFH %,&&4=7B:6'6 Highlight this entry and then take the path :HE 6HUYLFH ! :HE 6HUYLFH +RPHSDJH (or press the Web Service Homepage pushbutton) In the Settings pop-up that appears select the option 'RFXPHQW 6W\OH and press &RQWLQXH HQWHU
When prompted with the authentication request in the new session, enter your :$6 8VHU 1DPH DQG 3DVVZRUG as given at the beginning of the class and press 6XEPLW Select the 7HVW option in the blue bar near the top of the screen A structure name is shown under the label Operations. &OLFN on the structure name (cursor will change to a hand pointer while you do this)
SAP AG
DBW70E
4-81
2-5
Enter test data Customer: Material: Calday: DocNumber: *URXS ;;B Quantity: Unit: 3& Net Price: DocCurrcy: 86' and send it. Then examine the results from this push into the BI PSA. 2-5-1 Enter the following test data: Customer: Material: Calday: DocNumber: ;;B Quantity: Unit: 3& Net Price: DocCurrcy: 86' Then press 6HQG 2-5-2 Examine the results from the Push, which should be seen in the two columns Request and Response that appear.
3-1
Monitor the request in the BI warehouse via the Manage PSA function. 3-1-1 From your session which shows the screen Web Service Administration for SOAP Runtime keep pressing %DFN until you return to the DataSource tree list within the screen 'DWD :DUHKRXVLQJ :RUNEHQFK 0RGHOLQJ. 'RXEOHFOLFN on your DataSource =7B:6'6B;; You should be in the screen 'LVSOD\ 'DWD6RXUFH There should be one visible request now in the 5HTXHVWV IRU 36$ pop-up. For this row click on the icon in the cell 0RQLWRU5HTXHVW6WDWXV The Monitor screen appears. Here click on the 36$ 0DLQWHQDQFH icon again You should then see the entered test data in your PSA table. For a detailed view select the row by pressing the left-most cell on the row and then press the FKDQJH pushbutton. Press &RQWLQXH HQWHU to leave this detailed view (pop-up is called Single record change ) Keep pressing %DFN (do not save) until you return to the 5HTXHVWV IRU 36$ pop-up. Press &DQFHO ) here Keep pressing %DFN until you return to the SAP Easy Access menu. In the PSA Maintenance pop-up screen press &RQWLQXH HQWHU in the bottom left-hand corner. Press the pushbutton 0DQDJH 36$ If you get a pop-up message asking if you want to save InfoPackage changes press <HV.
3-1-10 3-1-11
SAP AG
DBW70E
4-82
&RQWHQWV
7UDQVIRUPDWLRQ
SAP AG 2006
SAP AG
DBW70E
5-1
'HILQH WKH FDSDELOLWLHV RI WKH WUDQVIRUPDWLRQ HQJLQH LQ 6$3 1: V DQG SRVLWLRQ LW DJDLQVW WKH XSGDWH UXOHV WUDQVIHU UXOHV FRQFHSW RI %: [ ([SODLQ XQLW RI PHDVXUH FRQYHUVLRQ LQ ,QIR2EMHFW PDVWHU GDWD
SAP AG 2006
SAP AG
DBW70E
5-2
3UHIDFH ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 'DWD 0RGHOLQJ 'DWD $FTXLVLWLRQ 7UDQVIRUPDWLRQ DQG 8QLW RI 0HDVXUH &RQYHUVLRQ 'DWD )ORZ &RQWURO $GPLQLVWUDWLRQ DQG 0RQLWRULQJ 3HUIRUPDQFH 2SWLPL]DWLRQ ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
5-3
<RX ZLVK WR H[SORUH WKH HQKDQFHG IXQFWLRQDOLWLHV DYDLODEOH WR FRQYHUW PHDVXUHV ZLWK GLIIHUHQW XQLWV LQ D VRXUFH V\VWHP LQWR FRQVLVWHQW XQLWV RI PHDVXUH LQ WKH %, V\VWHP
<RX QHHG WR XQGHUVWDQG KRZ WKH SURFHVV IRU GDWD FRQVROLGDWLRQ FOHDQVLQJ DQG LQWHJUDWLRQ LQ WKH (QHWHUSULVH 'DWD :DUHKRXVH LV DFKLHYHG ZLWK WKH KHOS RI WKH WUDQVIRUPDWLRQ HQJLQH RI 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
5-4
SAP AG 2006
SAP AG
DBW70E
5-5
*LYH D UHVXPH RI DQFLOODU\ WUDQVIRUPDWLRQ IHDWXUHV LQ 6$3 1: V 3RVLWLRQ WKH WUDQVIRUPDWLRQ HQJLQH RI 6$3 1: V YLVjYLV WKH XSGDWH UXOHV WUDQVIHU UXOHV FRQFHSW RI HDUOLHU %: YHUVLRQV
SAP AG 2006
SAP AG
DBW70E
5-6
7UDQVIRUPDWLRQ LV WKH PDLQ SURFHVV IRU GDWD FRQVROLGDWLRQ FOHDQVLQJ DQG LQWHJUDWLRQ 'DWD IURP SRVVLEO\ KHWHURJHQHRXV VRXUFHV FDQ EH VHPDQWLFDOO\ V\QFKURQL]HG KHUH 7KH WUDQVIRUPDWLRQ FRQFHSW RI 6$3 1: V FRH[LVWV ZLWK WKH NQRZQ WUDQVIHU UXOH XSGDWH UXOH FRQFHSW +RZHYHU QHZ GHYHORSPHQWV ZLOO IRFXV RQ WKH WUDQVIRUPDWLRQ FRQFHSW RI 6$3 1: V DQG WKLV LV H[DPLQHG KHUH
SAP AG 2006
SAP AG
DBW70E
5-7
7UDQVIRUPDWLRQ 'DWD6RXUFH
6$3
SAP AG 2006
This is the Data Flow of SAP NW 2004s via InfoPackaes we bring data in now only to PSA layer. From the PSA, having defined a transformation, we load data from the PSA to the InfoProvider via the Data Transfer Process. This is a new method to distribute data within BI. We can also define transformations to other InfoProviders, loading data via DTP from one InfoProvider to another. You can also define an Open Hub destination, and derfine the transformation between the PSA and an Open Hub destination also scheduled via DTP which can then load data to outside the BI.
SAP AG
DBW70E
5-8
7UDQVIRUPDWLRQ
7DUJHW 7UDQVIRUPDWLRQ (QG 5RXWLQH ([SHUW 5RXWLQH
7UDQVIRUPDWLRQ W\SHV
7UDQVIRUPDWLRQ 5XOH
0RYH DJJUHJDWH FRQVWDQW PDVWHU GDWD ORRN XS %XVLQHVV UXOHV HJ XQLW FXUUHQF\ WUDQVODWLRQ )RUPXOD EXLOGHU ZLWK ULFK SUHGHILQHG IXQFWLRQV OLEUDU\ $%$3 URXWLQHV LQFO UHJXODU H[SUHVVLRQV
6HPDQWLF *URXSV
9 8 7 5 4 2 0 30 63@)
,QWXLWLYH 8, 8QLW FRQYHUVLRQ 8QLILHG WUDQVIHU XSGDWH UXOHV LQWR DOOLQRQH FDSDELOLW\
SAP AG 2006
This is the new transformation concept in more detail. The source is still packaged. There is a new optional possibility to define the packages the semantic groups. You can load the data package by package into an optional start routine, then define the transformation rules, and after they have been applied process the data in an optional end routine. Then the target is updated. Alternatively, you can use an expert routine complete coding of your transformation (no declarative assignments of targets). The major enhancements are firstly unification of transfer / update rules you have the allin-one capability of transformation. You define an easy data flow betwen a source and a target, applying a transformation in betweeen. And you apply a data transfer process responsible for the runtime of the data load. This is a significant simplification. Secondly you have an intuitive graphical UI for the transformation you can easily drag and drop sources to targets. You can include unit conversions as you could before with currency conversions. The Open Hub service is also integrated into the data flow.
SAP AG
DBW70E
5-9
U E6c'"V2 C 9 Y S U4 8 X 7 5 4 8 gS 0F T 7 8 30 6cb3bV'S h
U(bSEY3feEbF(7 d hHfge IF"7 d b4fg30tU30bPeR'4(RREdEb"7 d (VbE8 iB H 0 0 4 U 0 H U e S 4 8 8 U e Y 0F T4 U jS h U"H'SVY30feV0bF7 d '4(HUfge 0b7 d IHfg30t'S3b4P8'4(8fRRUREYdE0b(7 d (HbEY30se"'(f3((bEPWVG4 B F 4 U e U 0 e e F U S 84 8 T U HS Y 0 T S U x 4 U e 0 F (Vh"7 d W(bW3U DB U HS Y 0 T "TR730 564aHR7EGEWb4 E8 8 3yEVtf"'"3Wh6"("H B Y F 9 8 7 05 5 X X 5 Y 7 U g 4 w U4 7 0 H g 0 S F T T U H 7 0 5 7 5 4 8 g S 0F T 7 8S 4 U x 4 04 4 w U 7 US 8 Y v T 99 8 g 3"H c0 6ch3b"V'6yR6QbE"(c'VPuWtse B US 0 g i 7 8 iS 0 4 8 X 7 8 g 4 0 7 U HS Y 0 e 0F d '3r(Vqp3h(VRVc3Rc"'E3fEb"7 DB T 9 Y S U4 8 X 2 Y X 7 8 S UF T 7 8S 4 F 0 7 5 4 8 5 5 C U 6cbaERE`REWV'"E'6ERQP0 I((H GF E7 DB
SAP AG
A A A
SAP AG 2006
The former Update Rule icon is used for transformations. A small square is in addition used to indicate if it is a 3.x Update Rule. You see the link source target. A new source can be applied to the Transformation InfoSet. All the other sources eg DataStore Object, InfoOobject, InfoSource are still valid sources for the transformation. Also note there is a new target which is the Open Hub destination.
7UDQVIRUPDWLRQ 'HILQLWLRQ
1HZ WUDQVIRUPDWLRQ
DBW70E
5-10
7UDQVIRUPDWLRQ *UDSKLFDO 8,
6RXUFH ILHOGV
7DUJHW ILHOGV
1RWH .H\ ILJXUHV FKDUDFWHULVWLFV DQG GDWH ILHOGV DUH VKRZQ RQ WKH VDPH OHYHO WUDQVIRUPDWLRQ JURXS
SAP AG 2006
We see sources on the left, targets on the right, also the assignment rules for specific targets. Key figures, characteristics and date fuields are on the same level known as a transfrornmation group. In more than 90% of the cases the key figures are transformed the same way for all characteristics. This simplifies the definition.
SAP AG
DBW70E
5-11
'LVSOD\ RSWLRQV
6L]H
l
SAP AG 2006
SAP AG
l l
,PDJH 6L]H
DBW70E
5-12
7UDQVIRUPDWLRQ 5XOHV
5XOH W\SH
6RXUFH ILHOGV
l
7DUJHW ILHOGV
SAP AG 2006
The Transformation rule type is defined at the top, offering Constant Direct Assignment Reading master data Only available for InfoObject-based sources (not PSA) Routine Formula editor Time Conversion/Distribution Currency / Unit conversion Not available if the source of the transformation is a DataSource Aggregation Summation (+) / Minimum (<) / Maximum (>) Symbol for aggregation shown on the graphical UI Overwrite (for DataStore objects) Source fields Usually one source field (plus unit/currency) For routines/formulas, several source fields are possible Target fields Usually one target field (plus unit/currency) For return table, several fields are possible (return table is planned for the release after SAP NetWeaver 2004s)
DBW70E 5-13
SAP AG
,QIR6RXUFH
k k
7UDQVIRUPDWLRQV ,QIR6RXUFH
7UDQVIRUPDWLRQ GLUHFWO\ OLQNV IURP D VRXUFH ,QIR3URYLGHU RU 'DWD6RXUFH WR D WDUJHW ,QIR3URYLGHU
$Q ,QIR6RXUFH LV XVXDOO\ QRW QHHGHG 1HZ ,QIR6RXUFH DUFKLWHFWXUH LV XVHG IODW ,QIR2EMHFWEDVHG VWUXFWXUH
l k
1RWH IRU GLUHFW ,QIR6RXUFHV IRU PDVWHU GDWD XSGDWHV WKHUH LV QR GLIIHUHQFH EHWZHHQ ROG DQG QHZ ,QIR6RXUFH LH \RX FDQ GHILQH D WUDQVIRUPDWLRQ DV ZHOO DV WUDQVIHU UXOHV
l k
SAP AG 2006
The InfoSource is not mandatory anymore. However, they can be used eg where you need InfoObject based information and this is not part of the DataSource.
SAP AG
<RX FDQ XVH D IOH[LEOH ,QIR6RXUFH DV D XQLIRUP VRXUFH IRU VHYHUDO WDUJHWV WKH ,QIR6RXUFH FDQ EH WKH WDUJHW IURP GLIIHUHQW VRXUFHV VHH QH[W VOLGH
$ IOH[LEOH ,QIR6RXUFH LV QHFHVVDU\ LQ RUGHU WR XVH FXUUHQF\ RU XQLW FRQYHUVLRQ IURP WKH VRXUFH 'DWD6RXUFH 'HILQH ,QIR6RXUFH DV DQ LQWHUPHGLDWH VWUXFWXUH
DBW70E
5-14
,QIR6RXUFH
k
7UDQVIRUPDWLRQV ,QIR6RXUFH
6FHQDULR ,QIR6RXUFH DV D XQLIRUP VRXUFH IRU VHYHUDO WDUJHWV DQG DV WDUJHW IURP GLIIHUHQW VRXUFHV
6$3 1HW:HDYHU %XVLQHVV ,QWHOOLJHQFH ,QIR3URYLGHU ,QIR3URYLGHU 7UDQVIRUPDWLRQ ,QIR6RXUFH 7UDQVIRUPDWLRQ 'DWD6RXUFH 'DWD6RXUFH 'DWD6RXUFH 'DWD6RXUFH Q
,QIR3URYLGHU
,QIR3URYLGHU P
SAP AG 2006
So we can use an InfoSource as an optional structure between a transformation and another transformation. This is necessary, for example, to consolidate several sources into several targets or to use InfoObject-based information.
SAP AG
DBW70E
5-15
6WDUW 5RXWLQH
8VH
l
SAP AG 2006
([DPSOH
l l k
This is as in 3.x used for example to avoid single data reads. Although package-based, in SAP NW 2004s we have the possibility to define semantic groups, which means characteristic values belonging together and part of one package. For example, we want all records for one document to be in one package so we define a semantic group on the document level.
SAP AG
3UHSDUDWLRQ RI GDWD EHIRUH WUDQVIRUPDWLRQ 3DFNDJHEDVHG VHPDQWLF SDFNDJLQJ SRVVLEOH VHH GDWD WUDQVIHU SURFHVV IRU PRUH GHWDLOV 'HOHWLRQ RI UHFRUGV WKDW DUH QRW UHTXLUHG IRU XSGDWLQJ
3HUIRUPDQFH %XIIHULQJ WDEOHV LQWR LQWHUQDO WDEOHV WKDW FDQ EH XVHG IRU WKH WUDQVIRUPDWLRQ UXOHV UDWKHU WKDQ UHDGLQJ WKH GDWDEDVH WDEOHV RQH E\ RQH
DBW70E
5-16
(QG 5RXWLQH
8VH
l
SAP AG 2006
([DPSOH
l k
End routine is similar to the start routine. Use it for post-preparation after the data transformation. This is package based semantic packages are possible here. It is recommended if for example you need to delete records after the transformation.
SAP AG
l l
3RVWSUHSDUDWLRQ RI GDWD DIWHU WUDQVIRUPDWLRQ 3DFNDJHEDVHG VHPDQWLF SDFNDJLQJ SRVVLEOH VHH GDWD WUDQVIHU SURFHVV IRU PRUH GHWDLOV
'HOHWLRQ RI UHFRUGV DIWHU WUDQVIRUPDWLRQ WKDW DUH QRW UHTXLUHG IRU XSGDWLQJ HJ DIWHU GHWHUPLQLQJ PDWHULDO FDWHJRU\ IRU D SDUWLFXODU PDWHULDO HYHU\ PDWHULDO RI W\SH UHIXQG LV QRW XSGDWHG 9DOLGDWLRQ &KHFNV RI UHFRUGV DIWHU WUDQVIRUPDWLRQ HJ NH\ ILJXUH VDOHV YDOXH PXVW EH ELJJHU WKDQ SXUFKDVH YDOXH
DBW70E
5-17
([SHUW 5RXWLQH
8VH
l
SAP AG 2006
The expert routine is a means to define a transformation in a non-declarative way. Here you do not have the 1:1 assignments between targets and sources, you are purely coding the transformation.
SAP AG
k k
([DPSOH
3HUIRUPDQFH UHDGLQJ VHYHUDO GDWDEDVH WDEOHV FDQ EH LPSOHPHQWHG IDVWHU ZKHQ NQRZLQJ WKH DSSOLFDWLRQ ORJLF UDWKHU WKDQ XVLQJ WKH JHQHULF WUDQVIRUPDWLRQ IUDPHZRUN 3LYRWLQJ WUDQVSRVH D ZLGH GDWD UHFRUG LQWR VHYHUDO VPDOOHU UHFRUGV FDQ EH HDVLO\ LPSOHPHQWHG XVLQJ WKH H[SHUW URXWLQH
DBW70E
5-18
7UDQVIRUPDWLRQ *URXSV
l
SAP AG 2006
Here key figures, characteristics and time characteristics are all on the same level this is required in more than 90% of cases. If, however, you wish to update key figures depending on the characteristics you can create transformation groups.
SAP AG
DBW70E
5-19
l l k
SAP AG
SAP AG 2006
In 3.x you could define characteristic updates per key figure. In most cases this was the same for all key figures. To define one key figure different to the others you would in SAP NW 2004s use the concept of transformation groups. A standard group exists. If you change this all referencing groups could be changed as well.
7UDQVIRUPDWLRQ *URXSV
&RQFHSW
7KLV UHSODFHV WKH IRUPHU FRQFHSW RI NH\ ILJXUHVSHFLILF XSGDWHV IRU WKH FKDUDFWHULVWLFV
DBW70E
5-20
h s hVVVt`RV""R0 VnU 3j nR'(bV"VV'Vt"E3h3q30 6h3b"RV'6Qo B S U j 8 7 8 g X 7 8 U U i 9 2 g Uq X U4 8 S U 7 U j US 8 T 2 Y 0 S j 7 5 4 8 g S 0 F T 7 8S 4 0 4 7 8 9 US T Y 7 0 e S U j 8 7 8 g T (VRU W'"E3RrT bWVVct(8 T Y 7 0 e U U i 9 2 g U U x 4 F 0 } | z X U 7 5 T T 8 U e 995 U U i 9 2 g U U x 4 F 0 S U j 8 7 8 g U h "E3cT R"0 Vnq63~"{3j Eaoutp"R0 E`Ro6WEVRVtx B T Y 7 0 "E3Re S U xv 5 x S 0F 5 T 8 e U x 4 5 x 5 x U g Y9 0 T 9 8 T 75 84S U H 8 T U4 8S U 7 U j U U i 9 2 g U '(T Vs3boT V(R6T H VgR3U EoVbW(qt('('WVVQR0 E`RQ7 yB T U U i 9 2 g U 99 8 F 0 T 9 8 T 4 7 8 9 US x T Y 7 0 e 7 0 5 S U 0 5 S 8 7 U H "R0 VnR(VW(U VRERU 'h"E3RuU WpVRV"0 6EV(fe B A
7UDQVIRUPDWLRQ *URXSV
Source
Johnson
Employee
8VH ([DPSOH
Sales Volume
1000
Giles
SAP AG
SAP AG 2006
Giles
Johnson
Employee
Target
Bonus-relevant Sales
1000
100
Manager
DBW70E
7UDQVIRUPDWLRQ *URXS
7UDQVIRUPDWLRQ *URXS
5-21
5HVWULFWLRQV
l k
You do not have to migrate all your update/transfer rules to the new concept. You could still define tupdate/transfer rules in SAP NW 2004s, although this is a little more hidden available via Additional Functions in context menu.
SAP AG
k k k k
0DLQWHQDQFH RI WUDQVIHU DQG XSGDWH UXOHV SRVVLEOH YLD FRQWH[W PHQX $GGLWLRQDO IXQFWLRQV 0LJUDWLRQ QRW DYDLODEOH \HW 5HFRPPHQGDWLRQ
7KH IRUPHU FRQFHSW WUDQVIHU DQG XSGDWH UXOHV LV VWLOO VXSSRUWHG E\ 6$3 KRZHYHU QHZ GHYHORSPHQWV ZLOO RQO\ IRFXV RQ WKH QHZ WUDQVIRUPDWLRQ FRQFHSW
+LHUDUFKLHV FDQQRW EH ORDGHG EDVHG RQ WKH QHZ WUDQVIRUPDWLRQ FRQFHSW SODQQHG IRU WKH VXEVHTXHQW 6$3 1HW:HDYHU UHOHDVH
5HWXUQ WDEOH LV QRW DYDLODEOH LQ WKH QHZ WUDQVIRUPDWLRQ FRQFHSW SODQQHG IRU WKH VXEVHTXHQW 6$3 1HW:HDYHU UHOHDVH
DBW70E
5-22
SAP AG 2006
SAP AG
DBW70E
5-23
*LYH D UHVXPH RI DQFLOODU\ WUDQVIRUPDWLRQ IHDWXUHV LQ 6$3 1: V 3RVLWLRQ WKH WUDQVIRUPDWLRQ HQJLQH RI 6$3 1: V YLVjYLV WKH XSGDWH UXOHV WUDQVIHU UXOHV FRQFHSW RI HDUOLHU %: YHUVLRQV
SAP AG 2006
SAP AG
DBW70E
5-24
SAP AG 2006
SAP AG
DBW70E
5-25
SAP AG 2006
SAP AG
DBW70E
5-26
(QKDQFHG IXQFWLRQDOLWLHV LQ WKLV DUHD DUH RIIHUHG WR PHHW WKH FKDOOHQJH RI FRQYHUWLQJ PHDVXUHV ZLWK GLIIHUHQW XQLWV LQ WKH VRXUFH V\VWHP LQWR FRQVLVWHQW XQLWV RI PHDVXUH LQ WKH %, V\VWHP
SAP AG 2006
SAP AG
DBW70E
5-27
2YHUYLHZ
&KDOOHQJH &RQYHUW PHDVXUHV ZLWK GLIIHUHQW XQLWV LQ WKH VRXUFH V\VWHP LQWR D FRQVLVWHQW XQLW RI PHDVXUH LQ WKH %,6\VWHP 8QLW FRQYHUVLRQ LV VLPLODU WR FXUUHQF\ WUDQVODWLRQ
SAP AG
k k
7ULYLDO FRQYHUVLRQ
&RQYHUWLQJ PHDVXUHV ZLWKLQ D GLPHQVLRQ OHQJWK PDVV (J NLORPHWHU WR PHWHU JUDP WR NLORJUDP &RQYHUWLQJ RUGHU XQLWV LQWR XQLWV VWRUHG (J RUGHUHG RQH SDOHWWH VWRUHG DV ER[HV
DBW70E
5-28
2YHUYLHZ
&RQYHUVLRQ W\SHV
l
SAP AG 2006
,QWHJUDWLRQ
k k
SAP AG
5HXVDEOH FRQYHUVLRQV DUH VWRUHG DV &RQYHUVLRQ 7\SHV 7UDQVDFWLRQ 56820 DYDLODEOH LQ WKH 6$3 (DV\ $FFHVV 0HQX &RQYHUVLRQ 7\SHV FDQ EH XVHG IRU XQLW FRQYHUVLRQ ZLWKLQ WUDQVIRUPDWLRQ UXOHV %([ $QDO\]HU DQG ZLWKLQ SODQQLQJ IXQFWLRQV
DBW70E
5-29
5HIHUHQFH ,QIR2EMHFW 'DWD6WRUH 2EMHFW &HQWUDO 8QLWV 7 )DFWRU LQ VRXUFH &RQYHUVLRQ )DFWRUV
&RQYHUVLRQ 7\SH
6RXUFH 8QLWV ,QSXW 7DUJHW 8QLWV 2XWSXW
&RQYHUVLRQ
SAP AG 2006
SAP AG
DBW70E
5-30
SAP AG 2006
SAP AG
DBW70E
5-31
'HILQH WKH FDSDELOLWLHV RI WKH WUDQVIRUPDWLRQ HQJLQH LQ 6$3 1: V DQG SRVLWLRQ LW DJDLQVW WKH XSGDWH UXOHV WUDQVIHU UXOHV FRQFHSW RI %: [ ([SODLQ XQLW RI PHDVXUH FRQYHUVLRQ LQ ,QIR2EMHFW PDVWHU GDWD
SAP AG 2006
SAP AG
DBW70E
5-32
([HUFLVHV
/HVVRQ 8QLW 7UDQVIRUPDWLRQ 7UDQVIRUPDWLRQ DQG 8R0 &RQYHUVLRQ
6HFWLRQ
At the conclusion of this exercise, you will be able to: Create a transformation within the Data Warehousing Workbench of SAP NW 2004s BI
Transformation is the main process for data consolidation, cleansing and integration within SAP NW 2004s. It co-exists with the known transfer rule / update rule concept. However you need to familiarize yourself with the Transformation approach as new developments will focus on this approach rather than on transfer rules / update rules.
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1
Go to the Data Warehousing Workbench for Modeling and find the Source Systems tree. Via the )LOH context menu view the data source you will be working with, but do not change anything. From Source System ,B(;7(51, go to DataSource 'B6'B&B7' found under 6DOHV 'LVWULEXWLRQ within $SSOLFDWLRQ &RPSRQHQWV within 6$3 'HPR. Display the field attributes of this DataSource. By copying from DataSource 'B6'B&B7' of Source System ,B(;7(51, create a new InfoSource ,6B75$16;; under application component =7B'%:(. Use description '%:( ,QIR6RXUFH 6DOHV 'HWDLOV ;;. Change your InfoSource ,6B75$16;; by deleting InfoObjects 'B97<3(, 'B'2&&/$66 and 'B5(*,21. Activate your InfoSource Create a new transformation for your InfoSource ,6B75$16;; using as the source the DataSource 'B6'B&B7' based on Source System ,B(;7(51. Activate the transformation without any changes from the proposed values.
1-2
1-3
1-4
SAP AG
DBW70E
5-33
2-1
Create a new InfoCube 75$16B;; (Description: 6DOHV 'HWDLOV ;;) under InfoArea 7B'%:( (copied from existing InfoCube 30B6''(7). Activate the InfoCube.. Create a new transformation for your InfoCube 75$16B;; using as the source the InfoSource ,6B75$16;; . Make a change within the transformation to do the following link - Link 'B62/'B72 of the InfoSource as a source to 'B5(*,21 of the InfoCube as a target, using rule type Read Master Data. Make a change within the transformation to do the following - Set a constant value for 'B97<3( of the InfoCube. Make a change within the transformation to do the following For 'B9(56,21 define a formula transformation to just assign Version 000 whenever the source does not deliver any value here. Formula syntax is ,) 'B9(56,21 !
'B9(56,21
Make a change within the transformation to do the following For 'B48$17B%, change unit transformation settings to )URP FRQYHUVLRQ and enter conversion type =7B&219. Examine the details behind the conversion type Check the overview of your transformation, and then activate it. .
2-2
2-3
2-4
2-5
2-6
2-7
SAP AG
DBW70E
5-34
6ROXWLRQV
8QLW 7UDQVIRUPDWLRQ DQG 8R0 &RQYHUVLRQ
6HFWLRQ
/HVVRQ
7UDQVIRUPDWLRQ
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1
Go to the Data Warehousing Workbench for Modeling and find the Source Systems tree. Via the )LOH context menu view the data source you will be working with, but do not change anything. From Source System ,B(;7(51, go to DataSource 'B6'B&B7' found under 6DOHV 'LVWULEXWLRQ within $SSOLFDWLRQ &RPSRQHQWV within 6$3 'HPR. Display the field attributes of this DataSource. 1-1-1 1-1-2 1-1-3 1-1-4 1-1-5 1-1-6 1-1-7 1-1-8 1-1-9 1-1-10 From the SAP Easy Access menu select 0RGHOLQJ ! 'DWD :DUHKRXVLQJ :RUNEHQFK ! 0RGHOLQJ
If you get a pop-up message about documentation select the check box to not show the question again and press <HV Click on the +LGH6KRZ (PSW\ )ROGHUV icon so that all possible source systems groupings are visible Expand )LOH and highlight the Source System ,B(;7(51. On right-hand mouse context menu choose 'LVSOD\ 'DWD6RXUFH 7UHH. The list of DataSources should appear.
Expand the node 6$3 'HPR, then expand the node $SSOLFDWLRQ &RPSRQHQWV, then expand the node 6DOHV 'LVWULEXWLRQ. On right-hand mouse context menu choose 'LVSOD\ Highlight the DataSource 30B6'B&B7'
1-2
By copying from DataSource 'B6'B&B7' of Source System ,B(;7(51, create a new InfoSource ,6B75$16;; under application component =7B'%:(. Use description '%:( ,QIR6RXUFH 6DOHV 'HWDLOV ;;. 1-2-1 1-2-2 1-2-3 Click on ,QIR6RXUFHV in the Navigator. Expand the node =%:B75$,1,1*, then highlight the application component =7B'%:(.
SAP AG
DBW70E
5-35
1-2-4
InfoSource: ,6B75$16;; Long Description: '%:( ,QIR6RXUFH 6DOHV 'HWDLOV ;; Application Component =7B'%:( Copy From Object Type: 'DWD6RXUFH DataSource: 'B6'B&B7' Source System: ,B(;7(51 Select +LGH6KRZ 1DYLJDWRU so that your InfoSource screen is in fullscreen mode Press 7UDQVIHU HQWHU
1-2-5 1-3
Change your InfoSource ,6B75$16;; by deleting InfoObjects 'B97<3(, 'B'2&&/$66 and 'B5(*,21. Activate your InfoSource 1-3-1 1-3-2
Holding down the Control key, select fields 'B97<3(, 'B'2&&/$66 and 'B5(*,21 by pressing the left-most cell on each of those rows. Then press the 'HOHWH 5RZ pushbutton
1-4
Create a new transformation for your InfoSource ,6B75$16;; using as the source the DataSource 'B6'B&B7' based on Source System ,B(;7(51. Activate the transformation without any changes from the proposed values. 1-4-1 1-4-2 1-4-3 1-4-4 You should find your new InfoSource ,6B75$16;; in the tree structure under application component =7B'%:(. If not, press the 5HIUHVK VXEWUHH icon. Select +LGH6KRZ 1DYLJDWRU so that your InfoSource screen is no longer in fullscreen mode
In the pop-up window specify - Source of the Transformation Object Type: 'DWD6RXUFH DataSource: 'B6'B&B7' Source System: ,B(;7(51 Select +LGH6KRZ 1DYLJDWRU so that your InfoSource screen is in fullscreen mode Press &UHDWH 7UDQVIRUPDWLRQ HQWHU Press pushbutton $FWLYDWH.
Highlight your new InfoSource ,6B75$16;; and on right-hand mouse context menu choose &UHDWH 7UDQVIRUPDWLRQ
Select +LGH6KRZ 1DYLJDWRU so that your InfoSource screen is no longer in fullscreen mode
SAP AG
DBW70E
5-36
2-1
Create a new InfoCube 75$16B;; Description: 6DOHV 'HWDLOV ;; under InfoArea 7B'%:( (copied from existing InfoCube 30B6''(7). Activate the InfoCube. 2-1-1 2-1-2 2-1-3 2-1-4 2-1-5 Select ,QIR3URYLGHU from the Navigator.
Select +LGH6KRZ 1DYLJDWRU so that your InfoSource screen is no longer in fullscreen mode
Specify InfoCube: 75$16B;; Description: 6DOHV 'HWDLOV ;; Copy From: 30B6''(7 InfoProvider Type: 6WDQGDUG ,QIR&XEH Real Time: No (blank) You are in the screen Edit InfoCube. Press pushbutton $FWLYDWH. Press &UHDWH )
2-1-6 2-2
Create a new transformation for your InfoCube 75$16B;; using as the source the InfoSource ,6B75$16;; . 2-2-1 2-2-2 2-2-3
You should find your new InfoCube 75$16B;; in the tree structure under InfoArea 7B'%:(. If not, press the 5HIUHVK VXEWUHH icon.
In the pop-up window specify - Source of the Transformation Object Type: ,QIR6RXUFH InfoSource: ,6B75$16;; Press &UHDWH 7UDQVIRUPDWLRQ HQWHU
Highlight your new InfoCube 75$16B;; and on right-hand mouse context menu choose &UHDWH 7UDQVIRUPDWLRQ
2-3
Make a change within the transformation to do the following link - Link 'B62/'B72 of the InfoSource as a source to 'B5(*,21 of the InfoCube as a target, using rule type Read Master Data. 2-3-1 2-3-2 2-3-3 2-3-4 2-3-5 2-3-6 2-3-7 Select +LGH6KRZ 1DYLJDWRU so that your InfoSource screen is in fullscreen mode Within the Transformation Create screen highlight the line for 'B62/'B72. Holding down the cursor, draw an arrow from that line to the 'B5(*,21 line in the Standard Group box. Note that an symbol now appears in the left-most box of the Standard Group. Double-click on this line. A pop-up box Rule Details appears. Specify Rule Type: 5HDG 0DVWHU 'DWD. The system automatically detects that 0D_SOLD_TO has an attribute 0D_REGION which will be used for the transformation. Note that now the = symbol on 0D_REGION has changed to the $WWULEXWHV0DVWHU 'DWD symbol in the left-most box of the Standard Group. Press pushbutton 7UDQVIHU 9DOXHV.
2-4
Make a change within the transformation to do the following - Set a constant value for 'B97<3( of the InfoCube. 2-4-1 2-4-2 2-4-3 2-4-4 2-4-5 Within the Standard Group box find the line for 'B97<3(. Note that no rule is defined. 'RXEOHFOLFN on the line. Specify - Rule Type: &RQVWDQW The pop-up box 5XOH 'HWDLOV appears. Press pushbutton 7UDQVIHU 9DOXHV Constant Value:
Note that now the symbol on 0D_VTYPE has changed to the &RQVWDQW symbol in the left-most box of the Standard Group.
SAP AG
DBW70E
5-37
2-5
Make a change within the transformation to do the following For 'B9(56,21 define a formula transformation to just assign Version 000 whenever the source does not deliver any value here. Formula syntax is ,) 'B9(56,21 !
'B9(56,21
2-5-1 2-5-2 2-5-3 2-5-4 2-5-5 Within the Standard Group box, find the line for 'B9(56,21. Double-click on the line. The pop-up box Rule Details appears. Specify - Rule Type: )RUPXOD and press the &KDQJH 5XOH pushbutton (pencil icon) Note: You need to be in Expert mode to key in the formula directly. Press the ([SHUW PRGH pushbutton (spanner icon) to do this.
You want a formula transformation to just assign Version 000 whenever the source does not deliver any value here. Type in ,) 'B9(56,21 !
'B9(56,21
exactly in this format. Or use the offered fields and functions below the formula box. You can select from these as necessary, each with a GRXEOHFOLFN. Press the FKHFN pushbutton to check your entries. When correct, press the %DFN button and press pushbutton 7UDQVIHU 9DOXHV.
Make a change within the transformation to do the following For 'B48$17B%, change unit transformation settings to )URP FRQYHUVLRQ and enter conversion type =7B&219. Examine the details behind the conversion type 2-6-1 2-6-2 2-6-3 2-6-4 2-6-5 Within the Standard Group box find the line for 'B48$17B%. 'RXEOHFOLFN on the line. The pop-up box Rule Details appears. Specify Conversion type: =7B&219 Under Unit of measure change Unit of Measure setting via the selector to )URP FRQYHUVLRQ.
Press pushbutton 0DLQWDLQ &RQYHUVLRQ 7\SH (pencil icon) to examine the conversion type. When the screen Quantity Conversion Type appears, press pushbutton 'LVSOD\ ). Examine the settings under each of the tabs +GU GDWD, &RQYHUVLRQ IDFWRUV and 8R0. Do not change anything in here. Press pushbutton 7UDQVIHU 9DOXHV Keep pressing %DFN until you return to the Rule Details pop-up window.
Check the overview of your transformation, and then activate it. 2-7-1 2-7-2 2-7-3 Press the pushbutton $FWLYDWH. Examine the content of the screen 7UDQVIRUPDWLRQ &UHDWH
Keep pressing %DFN until you return to the SAP Easy Access menu
SAP AG
DBW70E
5-38
&RQWHQWV
'DWD 7UDQVIHU 3URFHVV DQG (UURU +DQGOLQJ 3URFHVV &KDLQV 'LUHFW $FFHVV
SAP AG 2006
SAP AG
DBW70E
6-1
'HVFULEH WKH GHVLJQ DQG DGPLQLVWUDWLRQ IHDWXUHV RI 3URFHVV &KDLQV LQ 6$3 1: V
([SODLQ WKH 'DWD 7UDQVIHU 3URFHVV FRQFHSW DQG LWV HUURU KDQGOLQJ IHDWXUHV ZLWKLQ 6$3 1: V
'HILQH WKH FRQFHSW RI 5HDOWLPH 'DWD $FTXLVLWLRQ DQG KRZ LW ZRUNV LQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
6-2
3UHIDFH ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 'DWD 0RGHOLQJ 'DWD $FTXLVLWLRQ 7UDQVIRUPDWLRQ DQG 8QLW RI 0HDVXUH &RQYHUVLRQ 'DWD )ORZ &RQWURO $GPLQLVWUDWLRQ DQG 0RQLWRULQJ 3HUIRUPDQFH 2SWLPL]DWLRQ ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
6-3
<RX QHHG WR NQRZ KRZ WR ORDG GDWD IURP RQH SHULVLVWHQW OD\HU WR DQRWKHU ZLWKLQ %, DQG WKHUHIRUH PXVW XQGHUVWDQG WKH GDWD WUDQVIHU SURFHVV <RX ZDQW WR DXWRPDWH FRPSOH[ VHULHV RI EDFNJURXQG %, DFWLYLWLHV DQG WKHUHIRUH PXVW VHH KRZ WKH SURFHVV FKDLQV IXQFWLRQDOLW\ LV HQKDQFHG
<RXU %, V\VWHP QHHGV WR DFFHVV UHPRWH GDWD EXW \RX ZDQW WR DYRLG WKH RYHUKHDG RI ORDGLQJ SK\VLFDO GDWD LQFOXGLQJ PDVWHU GDWD WR LW DQG VR PXVW JHW IDPLOLDU ZLWK WKH FRQFHSW RI GLUHFW DFFHVV 5HSRUWLQJ XVHUV DUH LQFUHDVLQJO\ ZDQWLQJ WR GHULYH LQIRUPDWLRQ IURP GDWD DV LW EHFRPHV DYDLODEOH MXVW WR WKH RSHUDWLRQDO DSSOLFDWLRQV 7HFKQLTXHV LQ UHDO WLPH GDWD DFTXLVLWLRQ ZLOO EH KHOSIXO WR DFKLHYH WKLV DQG \RX QHHG WR OHDUQ DERXW WKHP
SAP AG 2006
SAP AG
DBW70E
6-4
SAP AG 2006
SAP AG
DBW70E
6-5
SAP AG 2006
SAP AG
DBW70E
6-6
'DWD 7UDQVIHU 3URFHVV LV D SDUW RI WKH 'DWD )ORZ &RQWURO FRQFHSW RI 6$3 1: V 7KH 'DWD 7UDQVIHU 3URFHVV LV UHVSRQVLEOH IRU ORDGLQJ GDWD ZLWKLQ %, IURP RQH SHUVLVWHQW OD\HU WR WKH RWKHU HJ IURP 6WDJLQJ 36$ OD\HU WR (QWHUSULVH 'DWD :DUHKRXVLQJ OD\HU RU IURP (QWHUSULVH 'DWD :DUHKRXVLQJ OD\HU WR $UFKLWHFWHG 'DWD 0DUWV OD\HU /HDUQ DERXW WKH SURFHVVHV PHFKDQLVPV DQG IHDWXUHV KHUH
SAP AG 2006
SAP AG
DBW70E
6-7
SAP AG 2006
In Enterprise Data Warehousing there are several conceptual layers staging layer, data warehouse layer and architected data marts layer. Data flow concept will go through these layers and load data from any source to the target within the Enterprise Data Warehouse.
SAP AG
DBW70E
6-8
7UDQVIRUPDWLRQ 'DWD6RXUFH
6$3
SAP AG 2006
Data Flow control concept will go through all three conceptual layers.This slide illustrates the new data flow control concept in SAP NW 2004s. InfoPackages are now responsible for loading the data from the Source System to the DataSource. DTP is responsible for loading the data from DataSource to InfoProvider. In a more generic way DTP is responsible for loading data within BI from one persistent layer to another.By using InfoSpoke BI can be used as the source system, whereby the data can be loaded from BI to any other destination.
SAP AG
DBW70E
6-9
InfoPackage loads the data from Source to Target with or without PSA in the SAP BW 3.X Release. Transfer rule and update rule are defined for data conversion in the transformation. Process chain in SAP BW 3.X Release is optional.
SAP AG
DBW70E
G4 D ` G c A V 0 F'"a(db3B`
G 8 c 8 r 0E 7 bFsyQ"YX
6-10
Within the SAP NW 2004s release - InfoPackages can only load data from Source System to PSA without any semantic transformation. What can be done here is a technical transformation (e.g. conversion exit to transform data from external format to internal format). Transformations can be defined between a source and a target for data transformation or conversion. Details on how the transformations work are covered in a separate unit. Data Transfer Process is responsible for data loading from one persistent layer to the other. Every Path from persistent source to target is a Data Transfer Process. That means that besides InfoSource any other objects like InfoProviders, DataSources, DataStore Objects can be the source or target for the Data Transfer Process. Process Chains are now mandatory in this case. InfoPackages and Data Transfer Process should be included into a process chain to automate the loading process.
SAP AG
G 8 c 8 r 0E 7 Cs3QYX
DBW70E
6-11
,PSURYHG WUDQVSDUHQF\ RI VWDJLQJ SURFHVVHV DFURVV GDWD ZDUHKRXVH OD\HUV 36$ ':+ OD\HU 2'6 OD\HU $UFKLWHFWHG 'DWD 0DUWV (QKDQFHG HUURU KDQGOLQJ IRU 'DWD6WRUH REMHFW HUURU VWDFN (QDEOHV UHDOWLPH GDWD DFTXLVLWLRQ ,PSURYHG SHUIRUPDQFH RSWLPL]HG SDUDOOHOL]DWLRQ
SAP AG 2006
Key benefits are seen above. The new data flow control concept allows data to be loaded into the PSA table. Then Data Transfer Process will distribute data to different data targets. With this concept the delta mechanism is not dependent on the DataSource, which is available in the Source System. With this concept you can have different delta mechanisms for different Data Targets via Data Transfer Processes. You can also set a filter to load a set of data which is available in the PSA to Data Targets. With the concept of DTP, transparency of the staging process across different layers (PSA, DWH layer, DataStore layer and architected data marts layer) is improved. Via optimised parallelization the load performance of the DTP is improved. Also, DTP provides enhanced errorhandling features like the error stack and temporary data storage. DTP enables real-time data acquisition DTP can be defined as a real-time DTP via daemon, loading data from source to target. This is covered in detail in a later lesson.
SAP AG
DBW70E
6-12
SAP AG 2006
InfoPackages only can load data from Source System to PSA without any semantic transformation. PSA will physically store the data. You can load data from PSA to DSO via DTP. What can be done there is a technical transformation (e.g. conversion exit to transform data from external format to internal format). InfoPackages/Data Transfer Process should be included into a process chain to automate the loading process.
SAP AG
D D G c 0A r A GE D 7 8A @ 8 4 8 "(bQyBb'""CQa"d(ae G 8 c 8 r 0E 7 CCs3QYX
DBW70E
6-13
SAP AG 2006
If there are two available paths from source to target then two DTPs should be defined. InfoSource between DataSource and InfoProvider is not mandatory anymore. In case you would like to define a complex transformation or define automated unit or currency conversion, you need to define a SAP NW2004s BI InfoSource. Remember: every path from persistent source to target is a Data Transfer Process.
SAP AG
DBW70E
D D G c 0A r A GE D 7 8A @ 84 8 "(bQydC'("CQag'(Be
,QIR6RXUFH 1:V
f X @ t T ` t T e BvvFdB3B@
h X @ t T ` t T igaRRF13a@
G4 D ` G c A V 0 F'(a(db3B`
X @ t T ` t T f aRRCdB3@
D D G c 0 A r A GE D 7 8A @ 84 8 "("bdyBbQC'Bw'(ae G 8 c 8 r 0E 7 CCs3QYX
6-14
6$3 1HWZHDYHU %,
,QIR6RXUFH V
T B@ T @
3URFHVV &KDLQ
r @ aBe r @ BBe r @ ae r X u Rt a` sr Qp UG "c 'A bV 30 ` 8 '4 (8 a ysdg(Qs3B"'ae e u t ` rp G cA V 0 ` 84 8 h 4 c Gk j GA 04 ` 84 8 3FgQ3Qy"Q(Be h G4 D ` G cA V 0 m'"yw(QbyB` T B@ T a@
SAP AG 2006
Here is a more complex example where the data warehouse layer and architected data marts layer are modeled. The typical business scenario is for the sales order data and the delivery data distributed in different Source Systems. In BI they are brought together. Therefore we can implement DSO 1 and DSO 2 at the data warehouse layer, and DSO 3 at the Consolidated layer. The InfoProvider can be modeled at the architected data marts layer. DTPs shouldd be defined for different sources and targets in this case. Again, a process chain must be defined in this complex loading scenario
SAP AG
DBW70E
6-15
2QFH WKH WUDQVIRUPDWLRQ LV GHILQHG LW LV SRVVLEOH WR FUHDWH WKH GDWD WUDQVIHU SURFHVV
SAP AG 2006
Via RSA1 you can access the Data Warehousing Workbench. DTP is assigned to the target object. Once the transformation is defined it is also possible to define a DTP for this target object.
SAP AG
DBW70E
6-16
:LWK ILOWHU LW LV SRVVLEOH WR ORDG D VHW RI GDWD WR WKH GDWD WDUJHW LQVWHDG RI WKH FRPSOHWH YROXPH RI GDWD 'LIIHUHQW GDWD VHOHFWLRQV FDQ EH PDGH YLD GLIIHUHQW GDWD WUDQVIHU SURFHVVHV IRU WKH VDPH RU IRU GLIIHUHQW GDWD WDUJHWV
SAP AG 2006
With the extraction mode, you can decide whether the Data Transfer Process loads the data in Full or delta mode. For the delta loading, you need to define two Data Transfer Processes (one Full and one Delta DTP) to load the data from source to target. With the filter function it is possible to load a set of data to the data target instead of the complete volume of data. Different data selections can be made via different Data Transfer Processes for the same or for different data targets. You can define the package size, whether the currency conversion should be switched on or whether it is possible to load the data from the change log of the DataStore Object. Regarding the Update mode and Execution mode we first need to look into error handling features of DTP.
SAP AG
DBW70E
6-17
SAP AG 2006
This slide illustrates how error handling works with the DTP. You have the option to choose whether you want to switch on the error handling feature or not. If you choose option 2 or 3 it will work as follows Data is loaded via InfoPackage from Source System to PSA table. There is no error handling available for InfoPackage. In case of invalid records data needs to be reloaded from the Source System. You can load the data from PSA to Data Target via DTP. As you have switched on the error handling features, the invalid records will be updated into the error stack. The correct records will be updated into the Data Target. After you have corrected the records in the error stack, you can load these corrected data records to the Data Target via Error DTP. This is a special DTP which is responsible or loading data from the error stack to the Data Target.
SAP AG
DBW70E
r @ e A 0 A A aB3d6a{
h G4 D D G cA V 0 D G q 4 0A xF'"""(Qb3C6wsQ6E S G S 8 9 GA G j 0 4 D S G G 7 84 8 CC0 CQUvd"r'(CS u D S A 0 c GA 59 8 s 75 E 0 G D 8 c 7 Fd3"FtS gCF(aFw(gYX h G 8 c 8 r 0E 7X 7 8 A 0 E 9 j 95 8 s CCbs3QYxCs3dG bC8 CF8 759 S 7 8 q A 0A A G 0 7 5 GA G q FYWFCByQ6CUFrD U'ba@
r YX G4 D ` G c A V 0 F'(aw(db3B`
6-18
$ERUW SURFHVV ZKHQ HUURUV RFFXU 3URFHVV WKH FRUUHFW UHFRUGV EXW GR QRW DOORZ UHSRUWLQJ RQ WKHP 3URFHVV WKH FRUUHFW UHFRUGV DQG DOORZ UHSRUWLQJ RQ WKHP
1XPEHU RI ZURQJ UHFRUGV ZKLFK OHDG WR D ZURQJ UHTXHVW ,QYDOLG UHFRUGV FDQ EH ZULWWHQ LQWR DQ HUURU VWDFN .H\V VKRXOG EH GHILQHG IRU HUURU VWDFN WR HQDEOH WKH HUURU KDQGOLQJ RI 'DWD6WRUH REMHFW 7HPSRUDU\ GDWD VWRUDJH FDQ EH VZLWFKHG RQRII IRU HDFK VXEVWHS RI WKH ORDGLQJ SURFHVV ,QYDOLG UHFRUGV FDQ EH XSGDWHG LQWR GDWD WDUJHWV DIWHU WKHLU FRUUHFWLRQ
The three options at top of this slide are as per the options in the screenshot on the previous slide. In the DSO you have the option to choose the update mode Overwrite. In this case the sequence of the data is quite important. And so we would need to define a key for the error stack to ensure the right sequence of data to be written to the DSO.
SAP AG
| |
DBW70E
6-19
(UURU +DQGOLQJ
(UURU +DQGOLQJ 2QFH HUURUV RFFXU WKH ZKROH 'DWD 3DFNDJH LV WHUPLQDWHG 7KH UHTXHVW LV QRW UHOHDVHG IRU UHSRUWLQJ
| |
SAP AG 2006
9DOLG UHFRUGV DUH XSGDWHG $IWHU PDQXDO UHOHDVH RI WKH UHTXHVW GDWD LV YDOLG IRU UHSRUWLQJ 9DOLG UHFRUGV DUH XSGDWHG DQG DYDLODEOH IRU UHSRUWLQJ
|
The DTP process Update tab where we decide how to proceed on error handling.
SAP AG
DBW70E
6-20
(UURU 6WDFN
(UURU 6WDFN
$XWRPDWLF FKHFNV ([LVWHQFH RI PDVWHU GDWD FRQYHUVLRQ H[LW UHVWULFWHG HJ $OSKD &XVWRPHUGHILQHG FKHFNV LQ WUDQVIRUPDWLRQ URXWLQHV VHH DSSHQGL[ IRU PRUH LQIRUPDWLRQ
$IWHU FRUUHFWLRQ (UURU'73 XSGDWHV GDWD IURP HUURU VWDFN WR GDWD WDUJHW 1RWH 2QFH WKH UHTXHVW LQ WKH VRXUFH REMHFW LV GHOHWHG WKH UHODWHG GDWD UHFRUGV LQ HUURU VWDFN DUH DXWRPDWLFDOO\ GHOHWHG
.H\ RI HUURU VWDFN GHILQHV ZKLFK GDWD VKRXOG EH GHWDLQHG IURP WKH XSGDWH DIWHU WKH HUURQHRXV GDWD UHFRUG
SAP AG 2006
The first point describes how the data records can be defined as invalid. More details on this are in the appendix. Since DSO has update mode Overwrite so the sequence of the data records is very important for the DSO update. The related data records to the erroneous records will also be updated into the error stack.
SAP AG
DBW70E
6-21
(UURU 6WDFN
(UURU 6WDFN
}
SAP AG 2006
0D[ ILHOGV 'HILQHV ZKLFK GDWD VKRXOG EH GHWDLQHG IURP WKH XSGDWH DIWHU WKH HUURQHRXV GDWD UHFRUG IRU 'DWD6WRUH 2EMHFW 6HPDQWLF JURXSV EXQGOH UHFRUGV ZLWK WKH VDPH VHPDQWLF JURXS NH\ LQWR WKH VDPH UHTXHVW VHH 7UDQVIRUPDWLRQ XQLW IRU PRUH GHWDLOV IRU 'DWD6WRUH 2EMHFW DQG ,QIR3URYLGHU
} }
6HPDQWLF *URXSV
Define the key of the error stack as detailed as possible The bigger the key, the fewer records will be written to the error stack Example Selecting company code as error stack key if one record of a particular company code is wrong, all records belonging to this company code will be written to the error stack Default: Complete target key (key of the DataStore Object)
SAP AG
DBW70E
6-22
,Q FDVH WKH HUURU KDQGOLQJ LV VZLWFKHG RQ DQG WKHUH DUH ,QIR2EMHFWV ZKLFK KDYH WKH XSGDWH PRGH RYHUZULWH LQ WUDQVIRUPDWLRQ QHZ UHFRUGV ZLWK WKH VDPH NH\ ZLOO EH ILOWHUHG RXW GXULQJ WKH GDWD ORDGLQJ
SAP AG 2006
Within the tabstrip Execute you can see all the process steps during the data loading. Here you can see a process step filtering out your records with the same key. What that means is that once you have switched on the error handling features and there are InfoObjects available which have the update mode Overwrite in the transformation, so these new records with the same key as the incorrect record will be filtered out during data loading.
SAP AG
DBW70E
6-23
/HYHO RI GHWDLO
} }
7UDFLQJ WUDQVIRUPDWLRQ E\ SDFNDJH 7UDFLQJ WUDQVIRUPDWLRQ E\ UHFRUG :LWK UHTXHVW VWDWXV JUHHQ ,I UHTXHVW LV GHOHWHG $IWHU ; GD\V
} } } }
6ZLWFK RQRII WKH WHPSRUDU\ GDWD VWRUDJH IRU GDWD ORDGLQJ VWHSV
SAP AG 2006
Temporary Data Storage provides help for tracing the erroneous records and transformations. Data records from different steps within the data transfer process can be stored temporarily. Stores complete set of data (erroneous as well as valid records) unlike the Error Stack. The scenario recommended for using temporary data storage: If the debugging mode is switched on Trace the erroneous records Trace Transformation
Find the settings under the GoTo menu -> set at what detailed level you wish to trace the data. You can trace incorrect data, incorrect transformations by package or by record. You can also define when this temporary data storage should be deleted. Finally decide for which loading step you wish to define the temporary data storage. Some steps are already chosen automatically.
SAP AG
DBW70E
6-24
(UURU 6WDFN
SAP AG 2006
This is integrated in InfoProvider management screen and integrated in Data Transfer Process maintenance. Additional information: duration of each step. Temporary storage access if activated Error Stack is displayed in Data Transfer Process Monitor
In the temporary data storage you can see all records correct and incorrect. Incorrect records are marked with a special symbol. (In the error stack you can only see the incorrect records). Here you have the possibility to correct these records manually.
SAP AG
DBW70E
6-25
SAP AG 2006
In temporary data storage see all the records; incorrect records are marked with the special symbol. In the error stack you see only incorrect records. Here you have the possibility to correct these records manually.
SAP AG
DBW70E
6-26
'HEXJJLQJ 0RGH
'HEXJJLQJ
SAP AG 2006
Under the Execute tabstrip you can choose a processing mode of debugging, and a breakpoint.
SAP AG
DBW70E
6-27
(UURU +DQGOLQJ
&KHFN WDEOH IRU WKH LPSDFW RI WKH HUURU KDQGOLQJ VHWWLQJV IRU HUURQHRXV UHFRUGV
C 3Q Q Y 3Q6Bx
X X
X X
SAP AG 2006
Here is a summary of the different situations for the different modes within error handling. If you only apply InfoPackage then no error-handling feature is switched on. You will get the monitor entry in the case of incorrect records. The whole update will be aborted. You will get a status red for this request. If you apply DTP and choose No update, no reporting all other features stay the same as InfoPackage. The only difference is that via DTP you can switch on the temporary data storage. WIth this option you can see the data in temporary data storage. If you choose the option Update valid records, no reporting, valid records will be upadetd into InfoProvicers. Incorrect records will be updated into the error stack. You can also see the data in temporary data storage. You will get the status of red for this request. In this case, reporting based on valid requests is not possible. You need to activate these requests manually and then you can start reporting on this data. If you choose Update valid records, reporting possible data stays the same as in the last mode described. But the status will be green and reporting on valid records is possible. It is recommended to use option 3 Update valid records, no reporting so you can make use of the error handling features and start reproting on a consistent database. Appendix: Call Error Handling in Transformations To skip records from processing, raise exception cx_rsrout_skip_record You can raise the exception to skip a record with or without filling a message into table MONITOR. If you do not fill a message, the error handling will not be informed, the skip is silent (filter). If you do fill in a message, the corresponding data record will be stored in the error stack.
SAP AG
DBW70E
F aW3'ayQ"Yr' CR
F 3Q(r'
3 ' Y l R
""yBBC33 yR~
Q bF BC33
6"Cs3d b3
X X X green
6-28
You can also fill messages into table MONITOR without raising the exceptions. These messages will be stored by the error handling and e.g. displayed in the temporary storage (if it is switched on). However the record will NOT be stored in the error stack, but updated into the data target. You can abort the whole data package by raising exception cx_rsrout_abort.
SAP AG
DBW70E
6-29
6XPPDU\
'DWD 7UDQVIHU 3URFHVV $OORZV \RX WR GHILQH WKH GDWD IORZ EHWZHHQ RQH VRXUFH DQG RQH WDUJHW VRXUFH DQG WDUJHW VKRXOG EH WKH SK\VLFDO OD\HU LQ 'DWD :DUHKRXVH 0XOWLSOH '73V FDQ EH GHILQHG IRU RQH WUDQVIRUPDWLRQ UHJDUGLQJ GLIIHUHQW VHWWLQJV LQ '73 '73 FDQ EH VWDUWHG PDQXDOO\ RU DXWRPDWLFDOO\ YLD SURFHVV FKDLQ '73 FDQ VHSDUDWH GHOWD PHFKDQLVP IRU GLIIHUHQW GDWD WDUJHWV (QKDQFHG HUURU KDQGOLQJ YLD HUURU VWDFN DQG WHPSRUDU\ GDWD VWRUDJH LV SRVVLEOH
SAP AG 2006
The new data flow control concept allows data first to be loaded into the PSA table, then DTP will distribute data to different data targets. With this concept the delta mechanism is not dependent on the DataSource which is available in the Source System. With this concept you can have different delta mechanisms for different data targets via Data Transfer Process.
SAP AG
DBW70E
6-30
SAP AG 2006
SAP AG
DBW70E
6-31
SAP AG
DBW70E
6-32
SAP AG 2006
SAP AG
DBW70E
6-33
SAP AG 2006
SAP AG
DBW70E
6-34
3URFHVV FKDLQV DUH DQ LQYDOXDEOH DVSHFW RI %, IRU DXWRPDWLQJ VLPSOH RU FRPSOH[ VHULHV RI EDFNJURXQG DFWLYLWLHV (QKDQFHPHQWV KDYH EHHQ LQWURGXFHG WR ERWK GHVLJQWLPH DQG WKH DGPLQLVWUDWLRQ SDUW RI SURFHVV FKDLQV
SAP AG 2006
SAP AG
DBW70E
6-35
SAP AG 2006
SAP AG
5HSDLULQJ DQG UHSHDWLQJ LQVWDQFHV 6\QFKURQRXV H[HFXWLRQ +DQGOLQJ SURFHVVHV ZLWK HUURUV %DFNJURXQG XVHU
'LVSOD\ PRGH &KHFN RQ EDWFK SURFHVV FRQVXPSWLRQ $OHUWLQJ ZLWK SURFHVV FKDLQV
DBW70E
6-36
SAP AG 2006
In this example the process type decision has only two outcomes, but more could be possible. For example, to load data quarterly from four different markets
SAP AG
DBW70E
6-37
SAP AG 2006
8S WR UHVXOWLQJ HYHQWV SOXV DQ HUURU HYHQW FDQ EH GHILQHG $YDLODEOH LQ WKH *HQHUDO 6HUYLFHV PHQX
There are as many event numbers as IF/ELSEIF Commands. User can decide which Event will follow each command
Complex IF..THEN...ELSE... Decisions are possible. The logic behind each decision can be defined by using the SAP formula builder (see next slide).
SAP AG
DBW70E
!3
"(
l
6-38
SAP AG 2006
)RUPXOD 'LVSOD\ $YDLODEOH )XQFWLRQV HJ GDWH VWULQJ DQG PDWK IXQFWLRQV
In addition to the functions seen above, process chain functions are also available, eg to determine runtime parameter of direct predecessor.
SAP AG
DBW70E
6-39
)OH[LEOH ([HFXWLRQ 3DWK (YHQW ORJLF )RUPXOD %XLOGHU 6SHFLDO )XQFWLRQV 6SHFLDO IXQFWLRQV LQ IRUPXOD EXLOGHU
SAP AG 2006
$OORZ GHFLVLRQV EDVHG RQ WKH FXUUHQW VWDWH RI WKH UXQWLPH SURFHVV FKDLQ 3URFHVV FKDLQ
,QSXW KHOS 7LS 8VH WKH ILHOGV EXWWRQ IRU YDOXH KHOS RQ WKH SDUWLFXODU
When customizing a function which retrieves parameters of a process chain, an F4 help has been implemented by using the Constant-button. To make use of the F4-help, at first one of the function templates must be selected. Now the cursor must be positioned on the first empty field where the formula paramter has to be entered. After this the button for inserting constants must be pressed which serves here as the F4-help. By pressing the button a pop-up will occur displaying the values available for selection. It is vital to start filling the necessary function parameters one by one starting from the first field. Otherwise the F4-help will not retrieve values.
SAP AG
5XQWLPH SDUDWHPHUV RI D SURFHVV IRU WKH FXUUHQW FKDLQ 3URFHVV RI WKH FKDLQ KDV SDUDPHWHU YDOXH
DBW70E
6-40
SAP AG 2006
SAP AG
DBW70E
6-41
)OH[LEOH ([HFXWLRQ 3DWK 1HZ (YHQW IRU 3URFHVV 7\SHV 1HZ HYHQW IRU SURFHVV W\SHV
SAP AG 2006
Here it can be seen if a process type can have multiple events as a result, as seen in the field Possible Events.
SAP AG
DBW70E
6-42
SAP AG 2006
$ PRUH FRPSOH[ VWDWXV DV D UHVXOW RI SURFHVV W\SHV IRU ZKLFK IOH[LEOH H[HFXWLRQ SDWKV DUH LPSOHPHQWHG LV SRVVLEOH %\ QRZ WKH SURFHVV W\SHV 'HFLVLRQ EHWZHHQ PXOWLSOH DOWHUQDWLYHV DQG :RUNIORZ KDYH LPSOHPHQWHG WKHVH QHZ LQWHUIDFHV
If there is a successor, which waits for a special outcome, then all other possible outcomes must have successors, too. Otherwise a runtime error will occur if the non-caught outcome takes place. There will be no successor waiting for an outcome which is not declared. This may happen, if an outcome is removed from the process variant.
SAP AG
DBW70E
6-43
'LVSOD\ 0RGH
'LVSOD\ (GLW 0RGH
SAP AG 2006
'HIDXOW YLHZ GLVSOD\ QR ORFNLQJ LVVXHV 1R ORFNLQJ LVVXHV RQH XVHU PD\ FKDQJH WKH SURFHVV FKDLQ ZKLOVW DQRWKHU RQH LV MXVW GLVSOD\LQJ LW 3URFHVV FKDLQV FDQ EH VFKHGXOHG LQ GLVSOD\ PRGH VDYLQJDFWLYDWLQJ QRW QHFHVVDU\ (GLW'LVSOD\ EXWWRQ FKDQJHV WKH PRGH
A minor but useful enhancement. In 3.x an editing user locked the chain also for display. Now it is possible to display a chain design when another user is editing it.
SAP AG
DBW70E
6-44
SAP AG 2006
This functionality was available in earlier releases by using the OK-code =copy. The process chain is copied including the references to the process type variants of the source chain. If there are new variants for the copied chain required, the references must be adopted.
SAP AG
DBW70E
6-45
SAP AG 2006
In 3.x it was only possible by a customer-defined process type to analyze return values of the process type. In SAP NW 2004s it is possible to search for a particular string in the output of a system command and to trigger an error if this string is not found or to judge the process type as successfully ended if this string is found.
SAP AG
$FWLRQ FDQ EH GHILQHG E\ DQDO\]LQJ WKH UHVXOW VWULQJ ZLWK JLYHQ VHDUFK SDWWHUQV
,I ILOH QRW DYDLODEOH UHVXOW QRW IRXQG WU\ WR XSORDG LW DJDLQ HYHU\ KRXU
,I WKH ILOH 0'B0DWHULDOFVY LV DYDLODEOH RQ WKH VHUYHU WKH PDVWHU GDWD LV ORDGHG
DBW70E
6-46
SAP AG 2006
26 &RPPDQG
SAP AG
DBW70E
6-47
6FHQDULR FOLHQWGHSHQGHQW DSSOLFDWLRQV WKDW LQFRUSRUDWH 6$3 1HW:HDYHU %, HJ 6$3 6&0 SURFHVV FKDLQ FDQ RQO\ EH VHHQ LQ WKH VSHFLILHG FOLHQW
SAP AG 2006
This can be switched on by entering an editing client in the attributes of the process chain. BW uses a different client concept to other SAP applications. BW makes use of the logical transport objects. As a result of this there are objects which must not be client-dependent. Entering the editing client is optional. If no entry is made here the process chain can be seen in all clients of the clientdependent target system, where the chain is supposed to run after the transport. If the field is filled with the client the chain can only be seen, scheduled and maintained in the specified client. For example if a process chain in BW triggers data loading activities.
SAP AG
DBW70E
6-48
$IWHU WKH DVVLJQPHQW WKH SURFHVV FKDLQ ZLOO EH VFKHGXOHG DXWRPDWLFDOO\ ,Q WUDQVDFWLRQ 56735)& D GHVWLQDWLRQ PXVW EH PDLQWDLQHG LQ WKH WDUJHW FOLHQW
$IWHU WKH DVVLJQPHQW WKH SURFHVV FKDLQ FDQ RQO\ EH PRQLWRUHG LQ WKLV FOLHQW
1RWH 3URFHVV 9DULDQWV ZKLFK DUH XVHG LQ D FOLHQWGHSHQGHQW SURFHVV FKDLQ FDQQRW EH XVHG LQ D SURFHVV FKDLQ UXQQLQJ LQ DQRWKHU FOLHQW VLQFH WKH YDULDQW ZRXOG EH LQYLVLEOH
SAP AG 2006
After the asignment of the specified client the processs chain will be scheduled automatically. In order to do so a destination must be maintained in transaction RSTPRFC.
SAP AG
DBW70E
6-49
:KHQ WKH IODJ LV VHW WKH SURFHVV W\SH LV KLGGHQ LQ QRQ6$3 1HW:HDYHU %, FOLHQWV ,I VXFK D SURFHVV LV VXSSRVHG WR EH XVHG LQ D QRQ 6$3 1HW:HDYHU %, FOLHQW HJ EHFDXVH LW ZDV DFFLGHQWDOO\ LPSRUWHG ZLWK D WUDQVSRUW D FKHFN RI WKH FKDLQ ZRXOG UHVXOW LQ DQ HUURU
SAP AG 2006
SAP AG
DBW70E
6-50
SAP AG 2006
SAP AG
DBW70E
6-51
SAP AG 2006
SAP AG
DBW70E
6-52
1R GUDJ GURS QHFHVVDU\ 7KH FRQWH[W PHQX GLVSOD\V WKH YDULDQWV JURXSHG E\ W\SH WR ZKLFK D SURFHVV FRXOG EH FRQQHFWHG ,W SHUIRUPV FKHFNV RQ WKH SRVVLEOH OLQNV WKDW FRXOG EH GUDZQ IURP RQH SURFHVV WR DQRWKHU VR QR VXSHUIOXRXV WDUJHWV DUH RIIHUHG
SAP AG 2006
There are checks included in this functionality which ensure that only the variants are shown which are feasible for the particular process.
SAP AG
DBW70E
6-53
SAP AG 2006
7KUHH RSWLRQV
The two possibilities to resume a btroken process chain are seen above. In the second case the process is started within the same instance. Since for some new process types, eg the new data transfer process, the data is linked to the instance it is not possible to start the data loading process with a new request number because the data is compounded with the request. Therefore the repair function offers the possibility to execute the same instance of the process type again.
SAP AG
%H DEOH WR VHH ZKLFK XVHU KDV VFKHGXOHG D FHUWDLQ SURFHVV FKDLQ DQG LV LQ FKDUJH RI LW
%:5(027( GHIDXOW 8VHU DFWXDOO\ VFKHGXOLQJ WKH SURFHVV FKDLQ 0DQXDOO\ VSHFLILHG XVHU
DBW70E
6-54
6$3 %: [ RQO\ UHSHDW RI VLQJOH SURFHVV W\SH ZLWKLQ D IDLOHG SURFHVV FKDLQ ZDV SRVVLEOH )RUPHU UHVWDUW IXQFWLRQ
SAP AG 2006
A SURFHVV LQVWDQFH is a tangible object whose properties and functionality are given by the fact that it represents a particular process. In other words, you can think of a process instance as a material realization of the abstract definition provided by a process type.
SAP AG
5HVXPH WKH SURFHVV ZLWKLQ WKH VDPH LQVWDQFH 6RPH SURFHVVHV OLNH WKH QHZ GDWD WUDQVIHU SURFHVV XVH WKLV DQG RIIHU IHDWXUHV WR UHSDLU EURNHQ LQVWDQFHV
DBW70E
6-55
,Q D PHWD FKDLQ SUHYHQW WKH ZKROH FKDLQ IURP EHLQJ VWRSSHG GXH WR HUURUV ZKHQ RQO\ XQLPSRUWDQW SURFHVV VWHSV RI D VXE FKDLQ KDYH IDLOHG
7KH\ KDYH D VXFFHHGLQJ HYHQW IRU WUHDWLQJ HUURUV 7KH\ KDYH D VXFFHHGLQJ HYHQW WKDW VKRXOG EH VFKHGXOHG LQ DQ\ FDVH
SAP AG 2006
SAP AG
DBW70E
6-56
6\QFKURQRXV H[HFXWLRQ
(QKDQFHG $GPLQLVWUDWLRQ )HDWXUHV 6\QFKURQRXV ([HFXWLRQ 6FHQDULR 5HGXFWLRQ RI SURFHVV FRQVXPSWLRQ RI VPDOO SURFHVV FKDLQ
5HFRPPHQGHG IRU VLPSOH XSORDG SURFHVVHV 8VHG IRU VPDOO YROXPHV RI GDWD
3URFHVV FKDLQ LV SURFHVVHG V\QFKURQRXVO\ E\ RFFXS\LQJ RQH VLQJOH GLDORJ SURFHVV DQG LQ VHULDO ORVV RI LQWHUQDO SDUDOOHOLVP
3URWRFROV WR PRQLWRU WKH H[HFXWLRQ RI WKH FKDLQ DUH VWLOO EHLQJ FUHDWHG
7KH V\QFKURQRXV H[HFXWLRQ RI SURFHVV FKDLQV FDQ EH VWDUWHG IURP WKH PHQX EDU
SAP AG 2006
SAP AG
DBW70E
6-57
6\QFKURQRXV H[HFXWLRQ
%HQHILWV
$1' 6WDUWHU 3URFHVV 3URFHVV $1' $1' 5XQWLPH 3URFHVV 3URFHVV 'HVLJQ WLPH 3URFHVV
SAP AG 2006
This feature was available also in BW 3.x with hidden ok-codes synchron. The system processes synchronously by only using one dialog process, so the chain is executed serially.
SAP AG
DBW70E
6-58
(QKDQFHG $GPLQLVWUDWLRQ )HDWXUHV &KHFN RQ %DWFK 3URFHVV &RQVXPSWLRQ %DWFK 3URFHVV &RQVXPSWLRQ &KHFN 6FHQDULR
3UHYHQW SURFHVV FKDLQ IURP FRQVXPLQJ PRUH EDFNJURXQG SURFHVVHV WKDQ DYDLODEOH FRXOG OHDG WR ORFNLQJ LVVXHV :KHQ FKHFNLQJ WKH SURFHVV FKDLQ WKH QXPEHU RI SDUDOOHO SURFHVVHV ZKLFK ZRXOG EH XVHG LQ RSWLPDO FDVH LV FDOFXODWHG DOVR UHFXUVLYHO\ LQ FDVH RI VXEFKDLQV
,I LW H[FHHGV WKH QXPEHU RI EDWFK SURFHVVHV DYDLODEOH RQ WKH FKRVHQ VHUYHU WKH OHYHO ZKLFK H[FHHGV WKH UHVRXUFHV LV PDUNHG DV ZDUQLQJ 0HVVDJH 7RR PDQ\ SDUDOOHO %DWFK SURFHVVHV IRU 6HUYHU
&KHFN 266 QRWH IRU PRUH LQIRUPDWLRQ RQ WKH ORFNLQJ SUREOHP DQG WKH FDOFXODWLRQ RI KRZ PDQ\ EDWFK SURFHVVHV DUH QHHGHG WR UXQ D SDUWLFXODU FKDLQ
SAP AG 2006
In former releases, the user ran into the bottleneck described without being informed by the system.
SAP AG
DBW70E
6-59
6HWXS
$OHUWV FDQ EH FROOHFWHG LQ DOHUW LQER[ RI WKH XVHU ZKR VFKHGXOHG WKH SURFHVV FKDLQ WUDQVDFWLRQ FRGH $/57,1%2; $WWULEXWH RI SURFHVV FKDLQ $OHUW &DWHJRULHV
&DSDELOLWLHV
$ VWDQGDUGL]HG WH[W LV VHQW IRU HYHU\ HUURU ZLWK WKH UHOHYDQW GDWD (UURUV RI EDWFK PDQDJHPHQW DUH DOVR FDSWXUHG DQG DOHUWV DUH WULJJHUHG
$Q DOHUW LV VHQW IRU HYHU\ SURFHVV W\SH ZKLFK HQGV ZLWK DQ HUURU
SAP AG 2006
Now alert categories can be defined and assigned to a process type. The user can define his own alert categories for his own process types. To activate the alerting function set a flag in the attributes of the process chain.
SAP AG
DBW70E
6-60
7KH DOHUW FDWHJRU\ LV GHULYHG E\ WKH V\VWHP DV IROORZV ,I WKHUH LV DQ HUURU LQ WKH EDWFK PDQDJHPHQW WKH VWDQGDUG FDWHJRU\ %:$&B352&(66B&+$,1B)5$0(:25. LV XVHG 2WKHUZLVH WKH QHZ WDEOH 563&B$/(57B&$7 LV DFFHVVHG WR ILQG DQ DOHUW FDWHJRU\ IRU WKH SURFHVV ZKLFK UHVXOWHG LQ DQ HUURU
7KLV WDEOH FDQ EH XVHG E\ WKH FXVWRPHU WR DVVLJQ RZQ DOHUW FDWHJRULHV RU FXVWRPHU GHILQHG FODVVHV WR FXVWRPHUVSHFLILF DQG DOVR WR VWDQGDUG SURFHVV W\SHV ,Q WKH VHFRQG FDVH QR PRGLILFDWLRQ KDV WR EH PDGH ,I WKH 1R DOHUW IODJ LV VHW QR PHVVDJH LV VHQW WR WKH XVHU
,I WKHUH LV QR UHOHYDQW HQWU\ LQ WKLV WDEOH WKH VWDQGDUG DOHUW FDWHJRU\ $&B352&(66B&+$,1B(5525 LV EHLQJ XVHG
SAP AG 2006
The alert category is derived by the system as follows: If there is an error in the batch management the standard category BWAC_PROCESS_CHAIN_FRAMEWORK is used to send an alert. Here fixed alert texts are used which must be implemented in the system after an installation or upgrade to SAP Netweaver BI by following the note 601619. Otherwise the new table RSPC_ALERT_CAT is accessed to find an alert category for the process which has sent an error. With this table it is possible for the customer to assign their own alert categories to their own and also to standard process types. In the second case no modification has to be made. If the No alert flag is set, no message is sent to the user. The customer can assign their own classes (using the new interface IF_RSPC_EVENT_RESOLUTION) for the process types to send individual alert messages. If for a process type no customer defined class is entered in this table, the system uses the alert category assigned to this process type. If there is no entry for a particular process type at all, the system uses the alert category BWAC_PROCESS_CHAIN_ERROR to send an alert.
SAP AG
DBW70E
6-61
(QKDQFHG $GPLQLVWUDWLRQ )HDWXUHV $OHUWLQJ :LWKLQ 3URFHVV &KDLQV 0DLQWHQDQFH RI DOHUW FDWHJRULHV
8VHU DVVLJQPHQW
SAP AG 2006
By using transaction ALRTCATDEF the user can define the properties of the alert category. In the customizing of an alert category the users which are supposed to receive the alert messages of this category can be assigned by role assignments or by entering the user IDs directly. In the properties section a priority for alerts coming from this category can be defined as well as an escalation procedure. In the container section the fields can be defined which give more detailed information on the error. In the long and short text section the text for the message can be defined. Here a distinction is made between a short text for SMS or Pager messages and a long text for alerts sent by mail.
SAP AG
DBW70E
6-62
SAP AG 2006
SAP AG
DBW70E
6-63
SAP AG
DBW70E
6-64
SAP AG 2006
SAP AG
DBW70E
6-65
/LVW WKH LPSOHPHQWDWLRQ VWHSV IRU UHPRWH DFFHVV RI WUDQVDFWLRQ GDWD 'HVFULEH FDSDELOLWLHV IRU UHPRWH DFFHVV RI PDVWHU GDWD
2XWOLQH WKH FRQFHSW DQG SRVVLEOH VFHQDULRV IRU GLUHFW DFFHVV LQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
6-66
0DNLQJ XVH RI 9LUWXDO 3URYLGHUV IRU ERWK WUDQVDFWLRQ DQG PDVWHU GDWD ZH FDQ HQDEOH D GLUHFW DFFHVV OLQN EHWZHHQ DQDO\WLFDO VHUYLFHV DQG UHPRWH GDWD ZLWKRXW XWLOLVLQJ SK\VLFDO REMHFWV ZLWKLQ RXU GDWD ZDUHKRXVLQJ DUFKLWHFWXUH WKHUHE\ DYRLGLQJ V\VWHP SURFHVVLQJ RI DFWXDO GDWD ORDGV 7KLV PDLQO\ IRFXVHV RQ WKH IROORZLQJ VRXUFH W\SHV 5HODWLRQDO '% &RQQHFW 0XOWLGLPHQVLRQDO 8' &RQQHFW 6$3 6$3, DQG )LOH ,QWHUIDFH
SAP AG 2006
SAP AG
DBW70E
6-67
'LUHFW $FFHVV
SAP AG 2006
SAP AG
DBW70E
6-68
'DWD6RXUFH36$
Y C (F'b ' a ( pC R (b3R 1 "b3R R
5HODWLRQDO 6RXUFH
lY !CsCg!
6$3 6RXUFH
CB3F(
)LOH
SAP AG 2006
This is not a topic for XML or the classic BAPI ETL extraction from legacy systems by third party tools.
SAP AG
DBW70E
6-69
$QDO\WLFDO 6HUYLFHV ,QIR3URYLGHU 0HWD 'DWD 'RFX PHQWV 2SHUD WLRQDO 'DWD 6WRUH $UFKLWHFWHG 'DWD 0DUWV 'DWD :DUHKRXVH /D\HU 'DWD6RXUFH $Q\ 6RXUFH
;0,
9LUWXDO 3URYLGHU
0DVWHU 'DWD
SAP AG 2006
Via VirtualProviders we can find a way to integrate data into anlaytical services by direct access.
SAP AG
DBW70E
6-70
%:
C FQ 6
SAP AG 2006
A DataSource for Direct Access will not provide a PSA table as we do not want to store data persistently. Nothing is different from the transformation point of view. We work with the special type of Cube the VirtualProvider, and we use a special type of DTP for this Direct Access scenario.
SAP AG
DBW70E
BRR
'" a (Qby
Baa
6-71
F'F a (db3
C " ( ( " ( F d F(( ' Q " ' b 3 ' ( (Qs3 '" B '( C'" B "(( (' 3Q """b' b'"CQ '
B C Q 6 C
SAP AG
SAP AG 2006
An InfoSource in this case can introduce additional transformation rules. In this case we assume the BI system has master data involved available on the BI side.
%:
,QIR6RXUFH
DBW70E
0DS
SLQJ
6-72
,QWHJUDWLRQ RI H[WHUQDO GDWD LQWR %, $QDO\VHV ZLWKRXW VWRULQJ GDWD SHUVLVWHQWO\ LQWR %, ([DPSOH 7HUDGDWD ,QWHJUDWLRQ 6$3 1HW:HDYHU %, RZQV WKH GDWD PRGHO 3HUVLVWHQF\ RI WKH WUDQVLHQW GDWD PLJKW EH DQ RSWLRQ IRU WKH IXWXUH LQWHJUDWLRQ FDQ EH WKH ILUVW VWHS LQWR PLJUDWLRQ VFHQDULRV 0DVWHU GDWD RI WUDQVLHQW WUDQVDFWLRQDO GDWD KDV WR EH DYDLODEOH LQ WKH %, HQYLURQPHQW 0DSSLQJ GXULQJ 7UDQVIRUPDWLRQ SRVVLEOH
SAP AG 2006
SAP AG
DBW70E
6-73
&UHDWH 'DWD6RXUFH &UHDWH 5HPRWH ,QIR&XEH DV 9LUWXDO 3URYLGHU &UHDWH 7UDQVIRUPDWLRQ &UHDWH 'DWD 7UDQVIHU 3URFHVV &UHDWH 6RXUFH 6\VWHP $VVLJQPHQW &KHFN GLVSOD\ GDWD IXQFWLRQ RI ,QIR&XEH
SAP AG 2006
SAP AG
DBW70E
6-74
SAP AG 2006
This is a specific example showing the relevant objects from the implementation steps of the previous slide. The example cube is of Northwind invoice data accessed remotely. There is a transformation belonging to the cube, an InfoSource inbetween which introduces a second transformation. The data flow at the end is based on a DataSource which gives access to the Northwind invoices. The accompanying Data Transfer Process handles the data flow between the DataSource and the cube.
SAP AG
DBW70E
6-75
SAP AG 2006
Creating a VirtualProvider will lead you into the above dialog. The Virtual Provider can be related to a Data Transfer Process or to a 3.x InfoSource.
SAP AG
DBW70E
6-76
SAP AG 2006
It may be necessary to have several transformations in sequence. This can be done by involving a separate InfoSource. In our example we do this as the Northwind invoice data is incomplete since it has no unit (UoM / Currency). Hence here a specific InfoSource has been introduced. In the standard group we see that a fixed value for unit (PC) and for currency (EUR) has been set. In a second transformation we bring data onto the cube level via the transformation in the bottom part of the graphic. Here 0QUANTITY and 0NET_PRICE are each automatically compounded with the respective units.
SAP AG
DBW70E
6-77
SAP AG 2006
Under the Extraction tabstrip we use a special DTP Type DTP for Direct Access. The Adapter type Database Table is used with a specified table. In the Update tabstrip the VirtualProvider is specified. The Execute tabstrip shows the entire data flow.
SAP AG
DBW70E
6-78
PRUH WKDQ RQH 'DWD6RXUFH SRVVLEOH DVVLJQ PDQGDWRU\ DFWLYDWLRQ RI '73 RQO\ LV QRW VXIILFLHQW
SAP AG 2006
The definition of the data transfer process alone is not enough. We assign the Data Source to a pair of objects the data target and the related InfoSource which is an internal technical vehicle to get the data flow to run. So we choose this Remote DTP and assign it to the data target. Note there may be more than one entry here: you should choose one.
SAP AG
DBW70E
6-79
From the context menu of your cube and choose Display Data you should see the result of the direct access in the list of the data target browser ie here Northwind data directly accessed from BI.
SAP AG
DBW70E
6-80
SAP AG 2006
Direct Access of Master Data is new within SAP NW 2004s so now we can handle the entire integration scenario. Now, on the right hand side, in this case master data is in the external source system as well. We need remote access to this and hence need a direct access DataSource for this master data. We have a kind of remote InfoObject. Combining this remote InfoObject with the right transformation and another DTP for remote access we can arrange that a query running on a VirtualProvider (remote cube) can not only access transaction data but also the related master data.
SAP AG
DBW70E
'" CQ(
'
3 F"CQ
6RXUFH 6\VWHP
"((F F 3Q aB
C Fd F6
%:
,QIR6RXUFH
b a
6-81
SAP AG 2006
Here is the implementation overview. We see a Northwind customer remote InfoObject. Below, we find the texts DataSource for Northwind customer with the related transformation and DTP. This resides on the DataSource for the Northwind remote customer.
SAP AG
DBW70E
6-82
5HPRWH &KDUDFWHULVWLF
SAP AG 2006
Under this tabstrip Master data/texts there is a new characteristic type Remopte Characteristic which you must choose. The name of an ABAP class will then be automatically generated.
SAP AG
DBW70E
6-83
SAP AG 2006
In the following step we define the transformation between here the DataSource and the Northwind customer InfoObject. So in this example we choose medium text and Northwind Customer ID to make the right text available for us during query execution.
SAP AG
DBW70E
6-84
SAP AG 2006
This DataSource just has to be specified as connecting to the external data source check the preview tabstrip.
SAP AG
DBW70E
6-85
SAP AG 2006
In defining the DTP the type DTP for Direct Access must be specified. Here the data target is the InfoObject texts.
SAP AG
DBW70E
6-86
7UDQVDFWLRQ OLVWFXEH
SAP AG 2006
To test the ALV can show the master data texts. Start the transaction LISTCUBE and browse for the table name (PM_NWCUST in this case) and use the suffix $T.
SAP AG
DBW70E
6-87
SAP AG 2006
SAP AG
DBW70E
6-88
During query execution we should see a final result like the above.
SAP AG
DBW70E
6-89
,QWHJUDWLRQ FDSDELOLWLHV RI H[WHUQDO GDWD LQWR 1HW:HDYHU %, $QDO\VHV DUH NH\ LQ PDQ\ FXVWRPHU VFHQDULRV ([DPSOH 7HUDGDWD ,QWHJUDWLRQ 6$3 1HW:HDYHU %, RZQLQJ WKH GDWD PRGHO PLJUDWLRQ PLJKW EH DQ RSWLRQ IRU WKH IXWXUH 'LUHFW $FFHVV FDSDELOLWLHV IRU 0DVWHU 'DWD ZLWK WKH QHZ UHOHDVH OHDGLQJ WR D VRXQG LQWHJUDWLRQ VROXWLRQ IRU H[WHUQDO GDWD
SAP AG 2006
SAP AG
DBW70E
6-90
/LVW WKH LPSOHPHQWDWLRQ VWHSV IRU UHPRWH DFFHVV RI WUDQVDFWLRQ GDWD 'HVFULEH FDSDELOLWLHV IRU UHPRWH DFFHVV RI PDVWHU GDWD
2XWOLQH WKH FRQFHSW DQG SRVVLEOH VFHQDULRV IRU GLUHFW DFFHVV LQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
6-91
SAP AG
DBW70E
6-92
SAP AG 2006
SAP AG
DBW70E
6-93
2XWOLQH KRZ 5HDOWLPH 'DWD $FTXLVLWLRQ ZRUNV YLD :HE 6HUYLFHV /LVW IHDWXUHV RI WKH 'DHPRQ 0RQLWRU
'HVFULEH WKH SURFHVVLQJ RI 5HDOWLPH 'DWD $FTXLVLWLRQ YLD WKH 6HUYLFH $3,
SAP AG 2006
SAP AG
DBW70E
6-94
,QFUHDVLQJO\ FXVWRPHUV DUH VHHLQJ D QHHG IURP WKHLU UHSRUWLQJ XVHUV IRU GHULYLQJ LQIRUPDWLRQ IURP GDWD DV WKDW GDWD EHFRPHV DYDLODEOH 7KH GLVWLQFWLRQ EHWZHHQ UHSRUWLQJ LQ DQDO\WLFDO DSSOLFDWLRQV DQG UHSRUWLQJ LQ RSHUDWLRQDO DSSOLFDWLRQV LV JHWWLQJ EOXUUHG 0RUH IUHTXHQW XSORDG LV LQ LWVHOI QRW D VXIILFLHQW VROXWLRQ DQG UHSRUWLQJ UHTXLUHPHQWV RI GDWD OHVV WKDQ HJ RQH KRXU ROG FRXOG EH UHTXLUHG $ V\VWHP GDHPRQ LV QRZ GHSOR\HG WR LQLWLDWH DQG FRQWURO GDWD WUDQVIHU
SAP AG 2006
SAP AG
DBW70E
6-95
1XPEHU RI UHTXHVWV FDQQRW EH KDQGOHG E\ %, V\VWHP 5HSRUWLQJ UHTXLUHPHQWV RI GDWD ZLWK VXE KRXUV DFWXDOLW\
7KH FOHDU GLVWLQFWLRQ EHWZHHQ WRROV IRU DQDO\WLFDO DSSOLFDWLRQV DQG WRROV IRU RSHUDWLRQDO DSSOLFDWLRQV LV PRUH DQG PRUH GLIILFXOW 6HH WUDQVDFWLRQDO GDWD LQ UHSRUWLQJ DV LW LV FUHDWHG LQ VRXUFH V\VWHP SRVW VHH 8VH 3XVK PHFKDQLVP HJ 6$3 1: ;, 3ROOLQJ RU 7ULJJHU GDWD ORDG SURFHVV YLD HYHQW IURP VRXUFH V\VWHP
6SOLWWLQJ RI VWDJLQJ SURFHVVHV (': *HQHUDO EXVLQHVV UXOHV DUH SURFHVVHG GXULQJ WKH GD\ ZKHUHDV VFHQDULR VSHFLILF UXOHV GHILQHG E\ DSSOLFDWLRQ UHJLRQ WLPH ]RQH HWF DUH SURFHVVHG DW FXVWRPHU GHILQHG WLPHV
5HPRWH DFFHVV RI GDWD QRW IHDVLEOH GXH WR UHVRXUFH FRQVXPSWLRQ LQ VRXUFH V\VWHP DQG FURVV DSSOLFDWLRQ UHSRUWLQJ UHTXLUHPHQWV
SAP AG
DBW70E
6-96
:KDW LV UHDOWLPH"
5HDOWLPH GDWD ZDUHKRXVLQJ LV D IUDPHZRUN IRU GHULYLQJ LQIRUPDWLRQ IURP GDWD DV WKH GDWD EHFRPHV DYDLODEOH
SAP AG 2006
SAP AG
'HOWD 4XHXH
6HUYLFH $3,
$SSOLFDWLRQ
SAP AG 2006
If we have a regular loading mechanism it will upload the data to our PSA and then in a regular staging process to our data warehouse layer and eventually to data targets that are available for reporting. Real-time data acquisition comes into play in two ways: a web service could push data from external system into PSA and a S-API could fetch the data from the source system and store it in the PSA. A daemon kicks off the data load process from the InfoPackage, and it triggers the DTP for forwarding PSA data to the DataStore object to make it available for reporting.
SAP AG
DBW70E
bg c t r Rv2dq b h e c b Bp ig f u(a
36$ 'DWD6RXUFH
bg c t r Rv2usq b h e cb Pp ig f Yd(a
6-98
5'$ 6FHQDULRV
SAP AG 2006
$ V\VWHP 'DHPRQ LV XVHG WR LQLWLDWH DQG FRQWURO GDWD WUDQVIHU LQ ERWK VFHQDULRV
SAP AG
} }
,QFRUSRUDWHV XVDJH RI ,QIR3DFNDJH IRU 5HDOWLPH 'DWD $FTXLVLWLRQ VRXUFH WR 36$ 7KHQ OHYHUDJHV 'DWD 7UDQVIHU 3URFHVV IRU 5HDOWLPH 'DWD $FTXLVLWLRQ 36$ WR 'DWD6WRUH 2EMHFW ,QFRUSRUDWHV XVDJH RI :HE 6HUYLFHV WR SRSXODWH WKH 36$
7KHQ OHYHUDJHV WKH 5HDOWLPH '73 WR WUDQVIHU GDWD WR WKH 'DWD6WRUH 2EMHFW
DBW70E
6-99
'DHPRQ
}
SAP AG 2006
7KH 6$3 1HW:HDYHU %, 'DHPRQ SHUIRUPV WKUHH VWHSV GHSHQGLQJ RQ WKH VFHQDULR FKRVHQ
} }
,QLWLDWH 6HUYLFH$3, 6$3, GDWD SXOO YLD ,QIR3DFNDJH IRU 5HDOWLPH 'DWD $FTXLVLWLRQ LQWR 36$ 7UDFN VWDWXV RI GDWD WUDQVIHU IURP VRXUFH V\VWHP ,QLWLDWH XSGDWH RI 'DWD6WRUH 2EMHFW YLD '73
A daemon is a system process that runs at regular intervals, eg every 5 minuites it will look to check if a certain task must be fulfilled. The intervals can be specified in the InfoPackage for data load.
SAP AG
} }
$OORZV UHVWDUWLQJ LI QHFHVVDU\ 5HVWDUW FDQ EH LQLWLDWHG VR LW VWDUWV DW WKH QH[W VWHS DIWHU WKH ODVW VXFFHVVIXOO\ H[HFXWHG VWHS
DBW70E
6-100
'DHPRQ 0RQLWRULQJ
0DLQWHQDQFH VFUHHQ IRU GDHPRQ FRQWURO FDQ EH FDOOHG IURP WKH 'DWD :DUHKRXVLQJ :RUNEHQFK
}
7UDQVDFWLRQ 565'$
SAP AG 2006
The monitor is the main tool for controlling the daemon and assigning DTPs and InfoPackages to a certain daemon. There can be more than one daemon in a system and a daemon can process more than one DataSource.
SAP AG
DBW70E
6-101
5HDOWLPH IODJ PXVW EH VHOHFWHG IRU WKH ,QIR3DFNDJH ZKLFK WKH GDHPRQ ZLOO PRQLWRU 7KLV RSWLRQ LV RQO\ DYDLODEOH IRU RQH ,QIR3DFNDJH DWWDFKHG WR WKH 'DWD6RXUFH
SAP AG 2006
For the daemon to pick up the data from the source system we must create an InfoPackage for the real-time data acqusition. This is similar to the InfoPackage we create for our regular scheduled data loads. An additional flag is available in the InfoPackage creation screen only available if the Data Source is enabled to provide real-time data acquisition data. If it is not then this flag is not available. You can only create one InfoPackage for such a DataSource. It is not possible to create multiple InfoPackages with this real-time data acquisition flag. The reason is that we are specifying some settings in this InfoPackage that are particular to this real-time data acquisition.
SAP AG
DBW70E
6-102
5HDOWLPH H[WUDFWLRQ PXVW EH VHOHFWHG LQ WKH $GDSWHU VHFWLRQ RI WKH ,QIR3DFNDJH VHWWLQJV
SAP AG 2006
Other settings in the InfoPackage include the adapter (how the data is provided). The setting is Extraction from SAP System Using close to Real-time.
SAP AG
DBW70E
6-103
3HULRGLFLW\ LV GHWHUPLQHG E\ 8SGDWH 3HULRGV VHWWLQJ YLD 5HDO 7LPH 0RQLWRU 565'$ 'DWD 3DFNDJH 6L]H 1R RI 5RZV
' % " (Qi6C&n C% % ri$(&'&l&WB xbFY C&4&(6y3YY& rY6( 3qC ~ % U # U V # ' U % % # " V % % % # & b&F&$&' % ' U # ' U % U V # U F(2(&Y6 Rd C&2&&|Y$"i$"&'&3Fa$QlY3% ( ~
lEeEE&YuEl nu ei
SAP AG
SAP AG 2006
Under the Procesing tabstrip we have settings for the closure of the request either a certain time (in hours / days) or a max number of records per request before we close it. Other settings are for the data package size and the maximum number of times the daemon should try to retrieve data from the source system before it before it actually stops processing.
DBW70E
6-104
2Q WKH 6FKHGXOH WDE \RX FDQ MXPS YLD $VVLJQ WR WKH 5'$ 0RQLWRU 7KHUH \RX FDQ DVVLJQ WKH ,QIR3DFNDJH WR D GHDPRQ
SAP AG 2006
Under the Update tabstrip we specify where we get the data from. In this case we see only the option for delta update. To initiate the delta queue we must create an initialisation of delta package. Under the Schedule tabstrip there is no option to schedule the InfoPackage instead we have a Go to functionality via the Assign pushbutton which brings us to the daemon where we can assign our InfoPackage and the DTPs to a certain daemon.
SAP AG
DBW70E
6-105
7KH GDHPRQ PRQLWRUV WKH 36$ DQG LQLWLDWHV WKH '73 RQ D UHJXODU EDVLV YLD VHWWLQJV LQ 5HDOWLPH ,QIR3DFNDJH
SAP AG 2006
It does not matter to the daemon whether the data has been written from a web service or from the Service API. If a DTP exists it initiates that and the data is written to the DSO.
SAP AG
DBW70E
bg c t r d4dq b h e cb Bp eg f 4da
36$ 'DWD6RXUFH
} }
6-106
SAP AG 2006
This is a regular Web Service Data Source with no particular settings to be made for real-time data acquisition. It does not matter how the data gets into the PSA.
SAP AG
DBW70E
6-107
$Q ,QIR3DFNDJH LV QHHGHG IRU WKH :HE 6HUYLFH WR GHILQH SDUDPHWHUV VXFK DV WLPH UHFRUG WKUHVKROGV IRU UHTXHVW FORVXUH DQG WR DOORZ WKH DVVLJQPHQW RI D GDHPRQ YLD WKH 5HDOWLPH 0RQLWRU
SAP AG 2006
SAP AG
DBW70E
6-108
SAP AG
DBW70E
ljk 4q jns 2q 4g lk h h { z
vlnh q twk o { { Er n$
vg
w $ p jo | p z w nl2q ks {
ps x 4ws k m p ts pk jjIj l@ s { ss m v 9w Vnlk 4 v s{ n po { Us m 8 ms x xk @ ts k8oi m 1dy v l2 s p ( $k s t p Cs (s o t h{ y w xk h o { s nu2 k k y y Tm yS% g t{ s q t w R twk w ps tsm i xkox nnv 8 j{ s t v llx { v uq y 4 t p 0 s jx 4 t p { % t Q 1s pjk x lns 1llll(x jh t ( t h y 5 x { x k h h o p s v s t Q jlk 3 l$v 4 S% v y { t s m k p s k w R p mlnl ps 1{ k si &0$ pm ( k h 0k t x s p y v s ls m t 2 v P{ ( 0 9{ 6 %
EE4YnnRY i ii
EE4YnnRY d
s nllvlk tsmtwsmwom m @Is nlk k vls nd&'uq F vy tth tg tsq G E { 4 p{ lwlvH( k 6 $lk {nk (k ls {uq t k o 7 l y m t p k m v t x s i t sv v ( kD m { C@ t jo % p s 1@Aj pk lk jr9w dz k B m swk t xv s i 8 { v t (t v m x ( w s hh nkj|ok ln{ lk k d{g s 2ldq % t t s vk t{ k klwslk 14 p ns lk t7 ( 6 s s vg p( 5 p t w v { l2m nlk v 2 h % k3 x o w s p s l2$llx p s ll|(k p k ts q mki tx p ws lh
0 1{ )
& '%
b cg c #g h vd4&(dET ux Yq
%,
b cg c b x h vd4&(dEfdux Yq
2/73
2/73
EE2 EE e d Ed v
xm p ts s ss m
EEu el dE e E e u
w p no |j p z w uq ks {
SAP AG
SAP AG 2006
(i) Use two DataSources. Advantage keep existing data flow. New data provided with a separate data flow. The new data flow and DSO can be much leaner (fewer fields than regular DSO). But we must guarantee consistency between both DSOs. Maybe periodically delete data from the RDA DSO to avoid redundancy.
(ii) Use a single DataSource. When RDA comes into play the whole data flow is replaced by the one with the RDA. Advantage no need for realignment / consistency checking between the 2 DSOs. Disadvantage need to replace the existing data flow, and therefore need to rely on consistency and stability of data from the RDA.
We can have only one or the other scenario - ie that the DataSource can only have a single extraction mechanism. Both at the same time are not possible.
([WUDFWLRQ GRQH YLD 5'$ DQG ,QIR3DFNDJH VFKHGXOLQJ 1RUPDO 'HOWD FDQ FXUUHQWO\ QRW EH GRQH LQ SDUDOOHO
DBW70E
%,
6-110
'DHPRQ 0RQLWRU
7KH 5'$ 'DHPRQ PRQLWRU SURYLGHV DQ RYHUYLHZ RQ WKH VWDWXV RI HDFK GDHPRQ DQG DWWDFKHG
,QIR3DFNDJHV IRU 5'$ 'DWD 7UDQVIHU 3URFHVVHV IRU 5'$
,PSRUWDQW WR QRWH WKDW ERWK ORDGLQJ WR WKH 36$ DQG WKH 'DWD6WRUH 2EMHFW DUH PRQLWRUHG ZLWKLQ WKH 'DHPRQ 0RQLWRU 7UDQVDFWLRQ 565'$
SAP AG 2006
This is the main tool to Control the daemons processes Assign DataSources and DTPs to certain daemons
Every daemon can handle more than one DataSource, and there can be more than one daemon existing in a system.
SAP AG
DBW70E
( b hg e c b Pp ef d(a
6-111
b c c y 224uYYex w b h e cb Pp eg f Yda
b cg c dYdRd(
W W
'DHPRQ 6WDWXV
7KH 'DHPRQV FDQ KDYH WKH IROORZLQJ VWDWXVHV LGHQWLILHG E\ WKH LFRQ LQ IURQW
SAP AG 2006
Runtime information for the daemon can be accessed from the context menu. It displays some information about the job the daemon is running and other information relevant to the daemon.
SAP AG
DBW70E
6-112
SAP AG 2006
The daemon monitor does not provide any information on the quality of the data use the data load monitor for that. The daemon monitor only monitors and controls runtime of the daemon and the data load cycle.
SAP AG
DBW70E
6-113
'HWDLOHG GDWD WUDQVIHU SURFHVV VWHSV LQ '73 0RQLWRU 6LPLODU WR GHWDLOV RI ([WUDFWLRQ PRQLWRU
SAP AG 2006
Likewise, in order to monitor and control DTPs jump to the respective DTP monitor. The RDA monitor only shows you whether the processing from a daemon point of view has been completed successfully or not.
SAP AG
DBW70E
6-114
2XWOLQH KRZ 5HDOWLPH 'DWD $FTXLVLWLRQ ZRUNV YLD :HE 6HUYLFHV /LVW IHDWXUHV RI WKH 'DHPRQ 0RQLWRU
'HVFULEH WKH SURFHVVLQJ RI 5HDOWLPH 'DWD $FTXLVLWLRQ YLD WKH 6HUYLFH $3,
SAP AG 2006
SAP AG
DBW70E
6-115
'HVFULEH WKH GHVLJQ DQG DGPLQLVWUDWLRQ IHDWXUHV RI 3URFHVV &KDLQV LQ 6$3 1: V
([SODLQ WKH 'DWD 7UDQVIHU 3URFHVV DQG LWV HUURU KDQGOLQJ IHDWXUHV ZLWKLQ 6$3 1: V
'HILQH WKH FRQFHSW RI 5HDOWLPH 'DWD $FTXLVLWLRQ DQG KRZ LW ZRUNV LQ 6$3 1: V
SAP AG 2006
SAP AG
DBW70E
6-116
([HUFLVHV
/HVVRQ 8QLW 'DWD 7UDQVIHU 3URFHVV DQG (UURU +DQGOLQJ 'DWD )ORZ &RQWURO
6HFWLRQ
At the conclusion of this exercise, you will be able to: Create a Data Transfer Process, which is what is used within SAP NW 2004s BI to load data within BI from one persistent layer to another.
Data Transfer Process is part of the Data Flow Control concept of SAP NW 2004s. The Data Transfer Process is responsible for loading data within BI from one persistent layer to another eg from Staging (PSA) layer to Enterprise Data Warehousing layer, or from Enterprise Data Warehousing layer to Architected Data Marts layer.
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1 Go to the Data Warehousing Workbench for Modeling and select the InfoProvider tree. Locate your InfoCube 75$16B;;. Start creating the Data Transfer Process for your InfoCube 75$16B;;. Since DTP distributes data within BI, any DataSource and Data Provider could be defined as the source of DTP. Here the Source should be DataSource 'B6'B&B7' of Source System ,B(;7(51 Define Extraction and Update settings for your Data Transfer Process: Extraction Mode should be )XOO. Error handling should be 9DOLG 5HFRUGV 8SGDWH 1R 5HSRUWLQJ 5HTXHVW 5HG. All offered options for deleting and filling temporary storage should be selected. Specify execution settings. Accept the Processing Mode automatically offered by the system, which will be the best option for performance optimization. $FWLYDWH the DTP.
1-2
1-3
1-4
2-1 2-2
Note the program flow, then select ([HFXWH to manually start your DTP. Check out progress via the '73 0RQLWRU
SAP AG
DBW70E
6-117
SAP AG
DBW70E
6-118
6ROXWLRQV
8QLW 'DWD )ORZ &RQWURO
6HFWLRQ
/HVVRQ
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1 Go to the Data Warehousing Workbench for Modeling and select the InfoProvider tree. Locate your InfoCube 75$16B;;. 1-1-1 1-1-2 1-1-3 1-1-4 1-1-5 1-2
From the SAP Easy Access menu select 0RGHOLQJ ! 'DWD :DUHKRXVLQJ :RUNEHQFK ! 0RGHOLQJ
If you get a pop-up message about documentation select the check box to not show the question again and press <HV Expand node %: 7UDLQLQJ, expand node %: &XVWRPHU 7UDLQLQJ, expand InfoArea 7B%:(. Highlight your InfoCube 75$16B;;
Start creating the Data Transfer Process for your InfoCube 75$16B;;. Since DTP distributes data within BI, any DataSource and Data Provider could be defined as the source of DTP. Here the Source should be DataSource 'B6'B&B7' of Source System ,B(;7(51 1-2-1 1-2-2 On right-hand mouse context menu of InfoCube 75$16B;; choose &UHDWH 'DWD 7UDQVIHU 3URFHVV
In the pop-up box Creation of Data Transfer Process select Object type: 'DWD6RXUFH DataSource: 'B6'B&B7' source System: ,B(;7(51 Press &RQWLQXH (QWHU
1-3
Define Extraction and Update settings for your Data Transfer Process: Extraction Mode should be )XOO. Error handling should be 9DOLG 5HFRUGV 8SGDWH 1R 5HSRUWLQJ 5HTXHVW 5HG. All offered options for deleting and filling temporary storage should be selected. 1-3-1 1-3-2 1-3-3 1-3-4 1-3-5 Under the Update tab of your DTP, specify Error Handling setting - 9DOLG 5HFRUGV 8SGDWH 1R 5HSRUWLQJ 5HTXHVW 5HG via the selector. Return to select the ([WUDFWLRQ tabstrip and select the )LOWHU pushbutton. A selection pop-up will appear. Make no changes here so that you have an unrestricted selection, and press &RQWLQXH (QWHU. Under the ([WUDFWLRQ tabstrip of your DTP, specify Extraction Mode )XOO using the selector.
Choose settings for DTP Temporaray Storage via menu *RWR ! 6HWWLQJV IRU '73 7HPSRUDU\ 6WRUDJH. Insert a checkmark into the 7HPSRUDU\ 6WRUDJH checkbox for each of the following boxes 'HOHWH 7HPSRUDU\ 6WRUDJH :LWK 5HTXHVW 6WDWXV *UHHQ 'HOHWH 7HPSRUDU\ 6WRUDJH :LWK 5HTXHVW 6WDWXV 'HOHWHG )LOO 7HPSRUDU\ 6WRUDJH DIWHU ([WUDFWLRQ 'DWD6RXUFH 7UDQVDFWLRQ 'DWD 6DOHV 2YHUYLHZ )LOO 7HPSRUDU\ 6WRUDJH DIWHU )LOWHU )LOO 7HPSRUDU\ 6WRUDJH DIWHU 3UHSDUH (UURU +DQGOLQJ )LOO 7HPSRUDU\ 6WRUDJH DIWHU 56'6 'B6'B&B7' ,B(;7(51 ! 75&6 DBW70E 6-119
SAP AG
,6B75$16;; )LOO 7HPSRUDU\ 6WRUDJH DIWHU 75&6 ,6B75$16;; ! &8%( 75$16B;; Press pushbutton &RQWLQXH WR 'HWDLO 6FUHHQ (QWHU
1-4
Specify execution settings. Accept the Processing Mode automatically offered by the system, which will be the best option for performance optimization. $FWLYDWH the DTP. 1-4-1 1-4-2 Select the ([HFXWH tabstrip. Note the Processing Mode offered by the system, but make no changes to the option that is offered. Press the pushbutton $FWLYDWH $FWLYDWH 'DWD 7UDQVIHU 3URFHVV
2-1
Note the program flow, then select ([HFXWH to manually start your DTP. 2-1-1 2-1-2 Press pushbutton ([HFXWH ([HFXWH LQ %DFNJURXQG
Still under the Execute WDEVWULS, note the details of the Program Flow that are listed.
2-2
Check out progress via the '73 0RQLWRU 2-2-1 2-2-2 2-2-3 2-2-4
Select +HDGHU tabstrip within the screen 'DWD 7UDQVIHU 3URFHVV 0RQLWRU. Note the Header settings and status shown.
Keep pressing %DFN until you return to the SAP Easy Access menu.
Select 'HWDLOV tabstrip. Note the steps listed under Request Processing.
SAP AG
DBW70E
6-120
([HUFLVHV
/HVVRQ 8QLW 3URFHVV &KDLQV 'DWD )ORZ &RQWURO
6HFWLRQ
Loading data into BI (PSA) is a separate initial step from the transformation of data to its final data target. These two steps may be seamlessly combined via the Process Chain approach.
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1
Locate your DataSource =),B'6B;; in the DataSource tree below =7B),/(B'6 (within Application Component =7B'%:(). Create an InfoPackage for the DataSource Get flight data for Group XX . Make no changes to the existing settings in the InfoPackage. Do not execute, but simply save, the InfoPackage. Go to the InfoProvider tree and find the DataStore Object 6LQJOH )OLJKW %RRNLQJV ;; with the technical name =6%.'6;; under InfoArea 7B'%:( and create a transformation with your DataSource =),B'6B;; of Source System ,B(;7(51 as the source of the transformation. Map the fields of the flat file to the corresponding InfoObjects of the DataStore Object. Save and activate the transformation. Then return to the Modeling screen and note the entries now in the tree. Create the Data Transfer Process for the DataStore Object for a full extraction. Do not execute just Save and Activate. (We will execute later within a process chain). Then return to the Modeling screen and note the entries now in the tree.
1-2
1-3
SAP AG
DBW70E
6-121
2-1
We will now create a Process Chain in order to process the InfoPackage and the Data Transfer Process in one go. Leave Modeling and call the Process Chain Definition Menu (563&). Here create a new process chain =7B3&B;; Long Description: /RDG )OLJKW 'DWD IRU *URXS ;; and enter a Start Process =7B67$57B;; Long description: 6WDUW /RDGLQJ ;; IRU ,PPHGLDWH 6WDUW. We will now complete the steps to build the Process Chain. From the Start process make a connection to Load Data (InfoPackage *HW )OLJKW 'DWD IRU *URXS ;;) -> your 'DWD 7UDQVIHU 3URFHVV -> $FWLYDWH 'DWD6WRUH 'DWD. You will create a process variant for activating DataStore Object Data ($&7,9$7(B2'6B'%:(B;; ). Also bring in an option to &OHDU WKH 36$ 5HTXHVW GDWD and include this at the beginning of the Process Chain. Activate the process chain. Now execute the Process Chain in order to execute the load of your flat file data into the DataStore object in one go. Then switch to the log view to see the details of the run. Go back to the Modeling tree in the Data Warehousing Workbench. Find the DataStore object and via the Manage function check to find the active data.
2-2
2-3
2-4
SAP AG
DBW70E
6-122
6ROXWLRQV
8QLW 'DWD )ORZ &RQWURO
6HFWLRQ
/HVVRQ
3URFHVV &KDLQV
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1
Locate your DataSource =),B'6B;; in the DataSource tree below =7B),/(B'6 (within Application Component =7B'%:(). Create an InfoPackage for the DataSource Get flight data for Group XX . Make no changes to the existing settings in the InfoPackage. Do not execute, but simply save, the InfoPackage. 1-1-1 1-1-2 1-1-3 1-1-4 1-1-5 1-1-6 From the SAP Easy Access menu select 0RGHOLQJ ! 'DWD :DUHKRXVLQJ :RUNEHQFK ! 0RGHOLQJ
In the pop-up window enter InfoPackage Description: *HW IOLJKW GDWD IRU *URXS ;;. Also flag the line containing your DataSource name by pressing the left-most cell on that row. Then press 6DYH (QWHU Select +LGH6KRZ 1DYLJDWRU so that your InfoPackage screen is in fullscreen mode. Note the different tabstrips. You are under 'DWD 6HOHFWLRQ tabstrip initially. No changes are made here.
Under the 3URFHVVLQJ tabstrip note that now for this new DataSource type InfoPackages can only load data into the respective PSA table. Under the 6FKHGXOH tabstrip note we will make no changes and we will QRW execute, as we do not want to start the data load now. Select +LGH6KRZ 1DYLJDWRU so that your InfoPackage screen is no longer in fullscreen mode. 6DYH the InfoPackage. Under the 8SGDWH tabstrip we see that we will do a full update.
Press %DFN so that you have a fullscreen view of the Data Warehouse Workbench: Modeling screen, and note that your InfoPackage is now visible in the tree.
1-2
Go to the InfoProvider tree and find the DataStore Object 6LQJOH )OLJKW %RRNLQJV ;; with the technical name =6%.'6;; under InfoArea 7B'%:( and create a transformation with your DataSource =),B'6B;; of Source System ,B(;7(51 as the source of the transformation. Map the fields of the flat file to the corresponding InfoObjects of the DataStore Object. Save and activate the transformation. Then return to the Modeling screen and note the entries now in the tree. 1-2-1 1-2-2 1-2-3 1-2-4 Select ,QIR3URYLGHU from the Navigator. Expand the nodes 7B%: ! 7B%:B&867 ! 7B'%:( Highlight the DataStore Object =6%.'6;; From the right hand mouse context menu select &UHDWH 7UDQVIRUPDWLRQ DBW70E 6-123
SAP AG
1-2-5 1-2-6
A pop-up box &UHDWH 7UDQVIRUPDWLRQ appears. Specify Object Type:'DWD6RXUFH DataSource: =),B'6B;; Source System: ,B(;7(51 Map the fields of the flat file to the corresponding InfoObjects of the DataStore Object, as follows (Note that not all of the target structure fields need to be addressed): &$55,' ! $LUOLQH &RGH &211,' ! )OLJKW &RQQHFWLRQ )/'$7( ! )OLJKW 'DWH %22.,' ! %RRNLQJ 1R &86720,' ! &XVWRPHU 1R &8677<3( ! &XVWRPHU 7\SH 602.(5 ! 6PRNHU /8**:(,*+7 ! :HLJKW RI /XJJDJH :81,7 ! 8QLW RI 0HDVXUH ,192,&( ! ,QYRLFH )ODJ &/$66 ! )OLJKW &ODVV )25&85$0 ! %RRNLQJ 3ULFH LQ )& )25&85.(< ! &XUUHQF\ .H\ /2&&85$0 ! 3ULFH RI %RRNLQJ /2&&85.(< ! &XUUHQF\ .H\ IRU 7UDQVDFWLRQ &XUUHQF\ 25'(5B'$7( ! %RRNLQJ 'DWH
1-2-7 1-2-8
Note that the transformation appears below the DataStore Object. Also a new folder for 'DWD 7UDQVIHU 3URFHVV has been created,
Press 6DYH. Press $FWLYDWH. Press %DFN to return to the screen 'DWD :DUHKRXVLQJ :RUNEHQFK 0RGHOLQJ
1-3
Create the Data Transfer Process for the DataStore Object for a full extraction. Do not execute just Save and Activate. (We will execute later within a process chain). Then return to the Modeling screen and note the entries now in the tree. 1-3-1 1-3-2 Highlight the DataStore Object =6%.'6;;. Select &UHDWH 'DWD 7UDQVIHU 3URFHVV from the right-hand mouse context menu. In the pop-up box &UHDWLRQ 2I 'DWD 7UDQVIHU 3URFHVV select Source of DTP Object Type: 'DWD 6RXUFH DataSource: =),B'6B;; Source System: ,B(;7(51. Press &RQWLQXH (QWHU
Within the DTP, click into the tabstrip ([WUDFWLRQ and set the Extraction mode to )XOO. Accept other defaults. Click into each of the tabstrips 8SGDWH and ([HFXWH, and accept the given defaults. Do not execute, as we will do this later in a process chain. Press 6DYH and $FWLYDWH.
Press %DFN to return to the screen 'DWD :DUHKRXVH :RUNEHQFK 0RGHOLQJ. Expand the 'DWD 7UDQVIHU 3URFHVV to view the new entries.
SAP AG
DBW70E
6-124
2-1
We will now create a Process Chain in order to process the InfoPackage and the Data Transfer Process in one go. Leave Modeling and call the Process Chain Definition Menu (563&). Here create a new process chain =7B3&B;; Long Description: /RDG )OLJKW 'DWD IRU *URXS ;; and enter a Start Process =7B67$57B;; Long description: 6WDUW /RDGLQJ ;; IRU ,PPHGLDWH 6WDUW. 2-1-1 2-1-2 2-1-3 2-1-4 2-1-5 2-1-6 2-1-7 2-1-8 2-1-9 2-1-10 2-1-11 2-1-12 In the command box enter transaction code 563& Press ([LW to leave the Data Warehousing Workbench
In the screen 0DLQWDLQ 6WDUW 3URFHVV press pushbutton &KDQJH 6HOHFWLRQV Back in the screen ,QVHUW 6WDUW 3URFHVV press 6DYH and then %DFN
Specify Process Variants =7B67$57B;; Long description: 6WDUW /RDGLQJ ;;. Press (QWHU. In the pop-up box 6WDUW 7LPH press pushbutton ,PPHGLDWH and then press 6DYH
In the pop-up box specify Process Chain: =7B3&B;; Long Description: /RDG )OLJKW 'DWD IRU *URXS ;;
Now, within the Process Chain Display Planning View, press &UHDWH )
A pop-up box offers you the choice between Network and Tree display. You will already be familiar with 1HWZRUN GLVSOD\.
The pop-up box ,QVHUW 6WDUW 3URFHVV appears with your Start Process name shown. Press &RQWLQXH (QWHU The Start Process appears on the canvas
2-2
We will now complete the steps to build the Process Chain. From the Start process make a connection to Load Data (InfoPackage *HW )OLJKW 'DWD IRU *URXS ;;) -> your 'DWD 7UDQVIHU 3URFHVV -> $FWLYDWH 'DWD6WRUH 'DWD. Also bring in an option to &OHDU WKH 36$ 5HTXHVW GDWD and include this at the beginning of the Process Chain. Activate the process chain. 2-2-1 2-2-2 2-2-3 Switch to the Process Step Overview by pressing the pushbutton 3URFHVV 7\SHV. Expand the node /RDG 3URFHVV DQG 3RVW3URFHVVLQJ. Highlight ([HFXWH ,QIR3DFNDJH and drag and drop it onto the canvas. When the pop-up ,QVHUW ([HFXWH ,QIR3DFNDJH appears select your InfoPackage. You can search by entering your InfoPackage text *HW )OLJKW 'DWD IRU *URXS ;; in the find dialog (Binoculars icon). When you see the InfoPackage appear in the list select it with &RS\ (QWHU. The InfoPackage name will then appear in the Insert Execute InfoPackage pop-up. Press &RQWLQXH (QWHU The system offers the InfoPackage and the Data Transfer Process execution in combination, which makes sense in this case. Arrange the steps on the canvas in sequence in order to design the start of the load. Link the 6WDUW process to /RDG 'DWD via the right-hand mouse context menu from Start, so you have a series like this: 6WDUW ! /RDG 'DWD ! 'DWD 7UDQVIHU 3URF
2-2-4 2-2-5
2-2-6
From the menu on the left expand the node 'DWD 7DUJHW $GPLQLVWUDWLRQ, and choose $FWLYDWH 'DWD6WRUH 2EMHFW 'DWD to drag and drop it onto the canvas. The system offers you the chance to select or create such a step. Press Create. Enter $&7,9$7(B2'6B'%:(B;; as the Process Variant and Description. You will be taken into the screen 3URFHVV 0DLQWHQDQFH $FWLYDWH 'DWD6WRUH 2EMHFW 'DWD. In here use the selector (F4) to select 'DWD6WRUH 2EMHFW as the Object Type. Then in the field Object name use the selector (F4) to select DataStore Object =6%.'6;; (Single Flight Bookings XX) and press Enter (Transfer Selections). Back in the screen 3URFHVV 0DLQWHQDQFH $FWLYDWH 'DWD6WRUH 2EMHFW 'DWD now press 6DYH and %DFN. In the pop-up window Insert Activate DataStore Object Data press &RQWLQXH (QWHU to accept the inserted value ($&7,9$7(B2'6B'%:(B;;). If a pop-up 'LVSOD\ 0RUH &KDLQV is offered where you are asked if you want other chains to be displayed on the maintenance screen too, press 1R. DBW70E 6-125
2-2-7
SAP AG
2-2-8
If a pop-up appears for you to select an InfoPackage, search for yours by entering your InfoPackage text *HW )OLJKW 'DWD IRU *URXS ;; in the find dialog (Binoculars icon) and double-click the line to select it. Connect the new step to activate the DataStore data to the predecessor step - the Data Transfer Process. On the 'DWD 7UDQVIHU 3URF step use the right-hand mouse context menu and select &RQQHFW :LWK ! 'DWD6WRUH GDWD ! $&7,9$7(B2'6B'%:(B;;. An $FWLRQ pop-up appears select the option VXFFHVVIXO, and press 7UDQVIHU (QWHU We will also include the option to clear the PSA at the very beginning of the Process Chain. Under 2WKHU %: 3URFHVVHV from the left-hand menu, choose 'HOHWLRQ RI 5HTXHVWV IURP WKH 36$ and drag and drop this onto the canvas. The pop-up box appears ,QVHUW 'HOHWLRQ RI 5HTXHVWV IURP 36$. Press &UHDWH. Specify - Process Variants: 36$B'(/B;; Long Description: 'HOHWH 6)/,*+7 36$ *URXS ;;. Press &RQWLQXH (QWHU. By using the VHOHFWRU ), specify Object Type: 36$ 7DEOH Object Name: select the PSA table for your DataSource by entering and then selecting from the subsequent window your DataSource name =),B'6B;; The PSA technical name will be provided by the system and shown as the Object Name is visible in the cell on the main screen. Now press 6DYH and then %DFN. The pop-up ,QVHUW 'HOHWLRQ RI 5HTXHVWV IURP 36$ is offered with your deletion process step name. Press &RQWLQXH (QWHU.
2-2-9
2-2-10 2-2-11
2-2-12
2-2-13
Ensure that the Load Data step follows on from the PSA Deletion. On the link between the 6WDUW process and the /RDG 'DWD process, select the context menu option 5HPRYH /LQN to remove any link from the Start process to Load Data process. Via the 'HOHWH 36$ 5HTXHVW context menu select &RQQHFW :LWK ! /RDG 'DWD ! *HW )OLJKW 'DWD IRU *URXS ;;. Select the option VXFFHVVIXO in the $FWLRQ IRU pop-up. Your sequence of process steps should be as follows: Start -> Delete PSA Request -> Load Data -> Data Transfer Process -> Activate DataStore Data. Now press $FWLYDWH to activate the process chain.
Insert the PSA Deletion at the beginning of your Process Chain. Click on the 6WDUW process, and select using the right-hand mouse context menu &RQQHFW :LWK ! 'HOHWH 36$ 5HTXHVW ! 'HOHWH 6)/,*+7 36$ *URXS ;; If the $FWLRQ IRU pop-up box appears select the option VXFFHVVIXO
2-2-14
2-3
Now execute the Process Chain in order to execute the load of your flat file data into the DataStore object in one go. Then switch to the log view to see the details of the run. 2-3-1 2-3-2 2-3-3 Press 6FKHGXOH ). Assign Priority: 6WDQGDUG 3ULRULW\ &. Press 7UDQVIHU (QWHU. Press /RJ 9LHZ (scroll icon) to see the details of the run. In the date selection pop-up choose 7RGD\, and press 7UDQVIHU (QWHU. If a pop-up appears concerning Status Change press <HV. Your process will appear on the list as not yet finalized. Press the Refresh (F2) button from time to time, until finally the process is finished successfully.
2-4
Go back to the Modeling tree in the Data Warehousing Workbench. Find the DataStore object and via the Manage function check to find the active data. 2-4-1 2-4-2 Press ([LW to return to the 6$3 (DV\ $FFHVV PHQX. Select 0RGHOLQJ ! 'DWD :DUHKRXVLQJ :RUNEHQFK 0RGHOLQJ. Select ,QIR3URYLGHU. Find your DataStore object under 7B%:( which is under 7B%:B&867 within 7B%:. Highlight the DataStore Object =6%.'6;; and select 0DQDJH. Keep pressing ([LW until you return to the 6$3 (DV\ $FFHVV menu. Under the Contents tab press pushbutton $FWLYH GDWD and then press ([HFXWH to find the data.
2-4-3 2-4-4
SAP AG
DBW70E
6-126
([HUFLVHV
/HVVRQ 8QLW 'LUHFW $FFHVV 'DWD )ORZ &RQWURO
6HFWLRQ
InfoProviders may be created where the structure is created in the BI system but the data is remote. You may still read this data via the InfoProvider on the BI. You will learn how to build the appropriate type of InfoProvider and the other necessary steps to achieve this
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1 Go to the Data Warehousing Workbench for Modeling and find the InfoProvider tree. Create a new InfoCube within the InfoArea 7B'%:( which is under 7B%:B&867 (under 7B%:). The InfoCube should be named 5$,&B;; and copied from existing InfoCube 30B5$,&. It should be a 9LUWXDO3URYLGHU %DVHG RQ 'DWD 7UDQVIHU 3URFHVV IRU 'LUHFW $FFHVV :LWK ,QIR6RXUFH [ 30B5$,6. Have a look at the structure of the InfoCube, which you will leave unchanged. Activate the InfoCube. Then find it in the InfoProvider Tree with all related objects. Create a transformation for the new InfoCube 5$,&B;;. The Source of the transformation should be InfoSource 30B5$,6. A transformation is proposed which meets your needs, so you will leave it unchanged. Check, Save and Activate the transformation. Then find it in the InfoProvider tree with the related objects. Create a data transfer process (for Direct Access) for the InfoCube and accept the defaults Now activate direct access Check data belonging to your InfoCube
1-2
SAP AG
DBW70E
6-127
SAP AG
DBW70E
6-128
6ROXWLRQV
8QLW 'DWD )ORZ &RQWURO
6HFWLRQ
/HVVRQ
'LUHFW $FFHVV
1RWH ,Q WKH LQVWUXFWLRQV EHORZ UHSODFH ;; ZLWK WKH JURXS QXPEHU JLYHQ E\ WKH LQVWUXFWRU 1-1 Go to the Data Warehousing Workbench for Modeling and find the InfoProvider tree. Create a new InfoCube within the InfoArea 7B'%:( which is under 7B%:B&867 (under 7B%:). The InfoCube should be named 5$,&B;; and copied from existing InfoCube 30B5$,&. It should be a 9LUWXDO3URYLGHU %DVHG RQ 'DWD 7UDQVIHU 3URFHVV IRU 'LUHFW $FFHVV :LWK ,QIR6RXUFH [ 30B5$,6. Have a look at the structure of the InfoCube, which you will leave unchanged. Activate the InfoCube. Then find it in the InfoProvider Tree with all related objects. 1-1-1 1-1-2 1-1-3 1-1-4 1-1-5 1-1-6 1-1-7 1-1-8 From the SAP Easy Access menu select 0RGHOLQJ ! 'DWD :DUHKRXVLQJ :RUNEHQFK ! 0RGHOLQJ If you get a pop-up message about documentation select the check box to not show the question again and press <HV Expand the nodes 7B%: ! 7B%:B&867 Highlight the InfoArea 7B'%:(
Specify InfoCube: 5$,&B;; Description: 5HPRWH $FFHVV ,QIR&XEH *URXS ;; From: 30B5$,& Type: 9LUWXDO3URYLGHU %DVHG RQ 'DWD 7UDQVIHU 3URFHVV IRU 'LUHFW $FFHVV
:LWK ,QIR6RXUFH [ 30B5$,6 Press &UHDWH ) 1-1-9 1-1-10 1-1-11 1-1-12
Select +LGH6KRZ 1DYLJDWRU so that your (GLW ,QIR&XEH screen is in fullscreen mode Press Back to return to the screen 'DWD :DUHKRXVLQJ :RUNEHQFK 0RGHOLQJ Note that the InfoCube appears in the tree display with related objects Look at the structure, make no changes, then press $FWLYDWH
1-2
Create a transformation for the new InfoCube RAIC_XX. The Source of the transformation should be InfoSource 30B5$,6. A transformation is proposed which meets your needs, so you will leave it unchanged. Activate the transformation. Then find it in the InfoProvider tree with the related objects. 1-2-1 1-2-2 1-2-3 Highlight your new InfoCube 5$,&B;;
Look at the transformation, but make no changes. Press &KHFN, 6DYH and $FWLYDWH DBW70E 6-129
A pop-up window appears &UHDWH 7UDQVIRUPDWLRQ . Specify - Source of the Transformation Object Type: ,QIR6RXUFH Name: 30B5$,6 Press &UHDWH 7UDQVIRUPDWLRQ (QWHU fullscreen mode
Press Back to return to the screen 'DWD :DUHKRXVLQJ :RUNEHQFK 0RGHOLQJ Note that the transformation appears in the tree display with related objects.
Create a data transfer process (for Direct Access) for the InfoCube and accept the defaults 1-3-1 1-3-2 1-3-3 1-3-4 1-3-5 1-3-6 1-3-7 Highlight the folder 'DWD 7UDQVIHU 3URFHVV that appears below your InfoCube 5$,&B;; in the tree. Note that the DTP Type is set to '73 IRU 'LUHFW $FFHVV Select from the context menu &UHDWH 'DWD 7UDQVIHU 3URFHVV
Accept the following defaults Target Object type: ,QIR&XEH Name: 5$,&B;; Source of DTP Object Type: 'DWD6RXUFH DataSource: =066B'6B Source System: =066B. In the Change Data Transfer Process screen look at the details under each of the tabstrips ([WUDFWLRQ, 8SGDWH and ([HFXWH Press %DFN to return to the screen 'DWD :DUHKRXVLQJ :RUNEHQFK 0RGHOLQJ. Note that details of the Data Transfer Process are visible now in the tree. Press $FWLYDWH
1-4
Now activate direct access 1-4-1 1-4-2 Highlight the InfoCube 5$,&B;;. On the context menu select $FWLYDWH 'LUHFW $FFHVV. In the pop-up window that appears check under the tabstrip 'DWD 7UDQVIHU 3URFHVVHV to see that your Data Transfer Process is assigned. Select this line by pressing the leftmost cell and then press 6DYH $VVLJQPHQWV.
1-4-3
The window will close, returning you to the screen 'DWD :DUHKRXVLQJ :RUNEHQFK 0RGHOLQJ
1-5
Check data belonging to your InfoCube 1-5-1 1-5-2 1-5-3 1-5-4 1-5-5 1-5-6 Highlight the InfoCube 5$,&B;;. On the context menu select Display Data. In the main data target browser screen select the pushbutton Field Selection for Output Choose several fields from the list, eg &XVWRPHU 0DWHULDO &DOHQGDU 'D\. Press ([HFXWH. Then press ([HFXWH again when back in the main data target browser screen. Accept any system pop-up messages. Data should now be displayed. Keep pressing %DFN until you return to the 6$3 (DV\ $FFHVV menu.
SAP AG
DBW70E
6-130
&RQWHQWV
SAP AG 2006
SAP AG
DBW70E
7-1
'HVFULEH KRZ WR ZRUN ZLWK %, 6WDWLVWLFV 'DWD /RDG 6WDWLVWLFV *LYH DQ RYHUYLHZ RI WHFKQLFDO FRQWHQW IRU %, 6WDWLVWLFV 'DWD /RDG 6WDWXV
SAP AG 2006
SAP AG
DBW70E
7-2
3UHIDFH ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 'DWD 0RGHOLQJ 'DWD $FTXLVLWLRQ 7UDQVIRUPDWLRQ DQG 8QLW RI 0HDVXUH &RQYHUVLRQ 'DWD )ORZ &RQWURO $GPLQLVWUDWLRQ DQG 0RQLWRULQJ 3HUIRUPDQFH 2SWLPL]DWLRQ ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
7-3
$GPLQLVWUDWLRQ DQG 0RQLWRULQJ FRYHUV DOO VFKHGXOLQJ DQG PRQLWRULQJ DFWLYLWLHV LQFOXGLQJ GDWD TXDOLW\ IHDWXUHV 7KLV SURFHVV LV IRFXVHG RQ PLQLPDO 7&2 DQG KLJKHVW UHOLDELOLW\ LQ GDWD TXDOLW\ 7KH DGPLQLVWUDWRU FRFNSLW RI 6$3 1: V SURYLGHV HDV\ DGPLQLVWUDWLRQ IRU FRPSOH[ (QWHUSULVH 'DWD :DUHKRXVHV DQG YLD GHOLYHUHG WHFKQLFDO FRQWHQW IURP 6$3 WKH %, 6WDWLVWLFV LQ 6$3 1: V ZLOO DVVLVW LQ FDSWXULQJ GDWD WR VXSSRUW (': PDQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
7-4
SAP AG 2006
SAP AG
DBW70E
7-5
'HVFULEH KRZ WR ZRUN ZLWK %, 6WDWLVWLFV 'DWD /RDG 6WDWLVWLFV *LYH DQ RYHUYLHZ RI WHFKQLFDO FRQWHQW IRU %, 6WDWLVWLFV 'DWD /RDG 6WDWXV
SAP AG 2006
SAP AG
DBW70E
7-6
f e d SvB0
( ( e8 8 $ $ 8@ 8 44 j HvG " " I H 1 G 1 D C A 9 41 8 &FE1B @8 w t V p iv` &Pusr&bT q i Q R X cV V hfgSed&bFaSQ ` Y VTR Q S6XWUSP
(71654# ! ( ' $ ' $&% " " 3 1 0 2 ) " 1z 9 D' i D " v 1ky
9 4 e8 D v 11vv
1G 9 EFC D 9 0
8k8 jv @8 D Ai 9 W{ 9 Dz FD1A0 A 9 9 hWE " FB D D D j4 9@8 g@d g @d 14 9 130
SAP AG
SAP AG 2006
With SAP NetWeaver 2004s SPS 07, the $GPLQLVWUDWLRQ area of the Data Warehousing Workbench has been enhanced to include the function of the BI Administration Cockpit.
'DWD
$OHUW
DBW70E
7-7
(DV\ DGPLQLVWUDWLRQ IRU FRPSOH[ (QWHUSULVH 'DWD :DUHKRXVHV XVLQJ WKH %, $GPLQLVWUDWRU &RFNSLW
SAP AG 2006
The BI Administration Cockpit supports system administration with regard to status monitoring and performance optimization. You can use the new technical Content, on which the BI Administration Cockpit is based, to create additional evaluations and reports. The technical Content has been enhanced in the following areas: Complete redesign of query runtime statistics Enhancement of data-load statistics to include statistics for process chains and data transfer processes Current data-load status of process chains and processes Current status of loaded requests
SAP AG
DBW70E
7-8
6WUDWHJLF DGPLQLVWUDWLRQ
WR PDNH DGPLQLVWUDWLRQ HDVLHU DQG IDVWHU DQG WKXV WR ORZHU WKH 7&2
SAP AG 2006
Quality controlling: error-free transfer of business data. What is behind strategic administration? Observing how the usages of the BW system evolves. What optimizations and enhancements are relevant to be prepared for future usage. What were the examples for planning tasks to be monitored - e.g. performance of planning functions, data mining procedures?
SAP AG
DBW70E
LQ WKH DUHDV RI
3HUIRUPDQFH RSWLPL]DWLRQ
LQFOXGLQJ FRQWH[WVSHFLILF
'ULOOGRZQ WR GHWDLOV 3URFHVVLQJ RSWLRQV
| | | | | | | | |
7-9
*UDSKLFDO GLVSOD\
The BI Administration Cockpit provides central access to the most important BI monitoring information, including multiple BI systems in one view. Filtering is flexible eg it allows BI Application Type selection of Web Templates and / or Workbooks. A context menu gives access to more detailed information. Underlying BW technology is used here (InfoProviders and Queries). iViews in such a scenario could include: BW alerts, Response Times per Query in seconds, Data Load Time Monitor (comparing duration of last run of each process chain to average load times).
SAP AG
DBW70E
7-10
SAP AG
DBW70E
7-11
6RXUFHV
|
SAP AG 2006
&HQWUDOL]DWLRQ
| | |
'DWD 6WDJLQJ IRU KLVWRULFDO GDWD 5HPRWH $FFHVV IRU DFWXDO GDWD &URVV V\VWHP PRQLWRULQJ
(QYLURQPHQW
| |
SAP AG
DBW70E
1DYLJDWLRQ WR
$SSOLFDWLRQV
| |
0RQLWRUV
| | |
7-12
(YHQW &RQFHSW
| |
With the new architecture for BI reporting, collection of statistics for query runtime analysis has been enhanced.
SAP AG
| | | |
&XVWRPL]H WKH OHYHO RI GHWDLO RI VWDWLVWLF GDWD FROOHFWLRQ IRU D FHUWDLQ REMHFW ,QWURGXFLQJ WKH FRQFHSW RI WKH (YHQW ,' FKDUDFWHULVWLF )OH[LEOH DQG H[WHQVLEOH IUDPHZRUN
DBW70E
7-13
2/$3
4XHU\
'DWD 0DQDJHU
4XHU\
SAP AG
DBW70E
7-14
SAP AG 2006
SAP AG
DBW70E
7-15
6ZLWFK 6WDWLVWLFV GDWD FROOHFWLRQ RQ RU RII 6HW WKH VWDWLVWLF GHWDLO OHYHO $JJUHJDWHG GDWD RQO\ 1R GHWDLO RQ GDWD PDQDJHU 'HWDLO RQ DOO OHYHOV
DFFHVVLEOH IURP WKH 'DWD :DUHKRXVLQJ :RUNEHQFK 7RROV RU XVLQJ WUDQVDFWLRQ 56''67$7
SAP AG 2006
The information as to whether statistic data is collected for an object no longer depends on the InfoProvider. Instead, it depends on those objects for which the data is collected, which means on a query, a workbook or a Web template. The associated settings are maintained in the RSDDSTAT transaction.
SAP AG
DBW70E
7-16
'62 2EMHFW ,QIR&XEH $JJUHJDWH ,QIR&XEH +3$ ,QGH[ (YHQW VHF
SAP AG 2006
" WRWDO UXQWLPH RI WKH QDYLJDWLRQ VWHS LQ \RXU %, ZHE DSSOLFDWLRQ \RXU ZRUNERRN RU \RXU IURQWHQG IURP OHYHO VWDWLVWLFV VHH EHORZ
SAP AG
DBW70E
7-17
56''67$7,1)2
56''67$7+($'(5
56''67$7(9'$7$
56''67$7'0
56''67$7B'0
SAP AG 2006
The query runtime statistics are updated to other detailed tables, offering a more exact evaluation. As a result, the following InfoCubes for statistics are obsolete as of NW 2004s: 0BWTC_C02 and 0BWTC_C03. Statistics that you created before the upgrade can still be evaluated with these InfoCubes, while the new InfoProviders are only available for query-runtime statistics that are generated afterupgrading to NW 2004s. There is no provision for migrating old statistics into the new InfoCubes.
SAP AG
)( 2/$3
)( 2/$3
0XOWL3URYLGHU
4XHULHV
DBW70E
xq vs V X xq hnf pT ~ H)' }
q 6Qx px @hu pf pa gQ @ q juW pT Vq a rQo f q w yx6fx&XS pQ uW pT mu ySn ) X r V V t TRQ R V ba r r T c Q w SQ p &bV ` dy mR 7xg&Qg YX ngSQ x Q VXf x oX q VXf nq Shxg pR SQ S uxq SgxkW pT
6 3 D ~ H0' }
61 3 D ~ H0' }
'0
'0
7-18
7HFKQLFDO &RQWHQW IRU QHZ 4XHU\ 5XQWLPH 6WDWLVWLFV 7HFKQLFDO FRQWHQW TXHULHV IRU DQDO\]LQJ WKH UXQWLPH RI
4XHULHV %, :HE $SSOLFDWLRQV )URQWHQGWLPH 2/$3WLPH '0WLPH 3ODQQLQJ WLPH
EHLQJ FDOFXODWHG DV
SAP AG 2006
The new InfoProviders are: For more highly aggregated query-runtime statistics: 0TCT_C01, 0TCT_VC01 and 0TCT_MC01 (These replace InfoCube 0BWTC_C02) For more detailed query-runtime statistics: 0TCT_C02, 0TCT_VC02 and 0TCT_MC02 (These replace InfoCube 0BWTC_C02) For data manager statistics: 0TCT_C03, 0TCT_VC03 and 0TCT_MC03 (These replace InfoCube 0BWTC_C03) For data-load statistics of process chains and processes: 0TCT_C21, 0TCT_VC21 and 0TCT_MC21 For data-load statistics of data transfer processes: 0TCT_C22, 0TCT_VC22 and 0TCT_MC22 For data-load statistics of InfoPackages: 0TCT_C23, 0TCT_VC23 and 0TCT_MC23 These deliver essentially the same information as InfoCube 0BWTC_C05 but they use the new InfoObjects. The remaining new InfoProviders also use the new InfoObjects. For the current data-load status of process chains and processes: 0TCT_VC11 and 0TCT_MC11 For the current status of requests loaded to InfoProviders, InfoObjects that have been updated flexibly, and PSA tables: 0TCT_VC11 and 0TCT_MC11
SAP AG
| | | | | | | |
$YHUDJHV 'HYLDWLRQV 5DQNLQJV +RXUV SHU GD\ 'D\V SHU PRQWK :HHNV SHU TXDUWHU
DBW70E
7-19
'73
'DWD6RXUFH
SAP AG
DBW70E
9 ES2# #" 4 D 9{
ddvs&& S0
q Q xjxFQa q S6Xv Yq V R V
q Q xj6QhX gj Yq T uydnvxy mR Q fV q b ba
'73
,QIR3DFNDJH
7-20
56''67$7'73
56%.5(48(67
563&/2*&+$,1
563&352&(66/2*
56''67$7:+0
9B56''67$7'73
9B563&/2*&+$,1
567&B%:B*(7B'$7$B&
0XOWL3URYLGHUV
4XHULHV
SAP AG 2006
For data-load statistics of process chains and processes: 0TCT_C21, 0TCT_VC21 and 0TCT_MC21 For data-load statistics of data transfer processes: 0TCT_C22, 0TCT_VC22 and 0TCT_MC22 For data-load statistics of InfoPackages: 0TCT_C23, 0TCT_VC23 and 0TCT_MC23 These deliver essentially the same information as InfoCube 0BWTC_C05 but they use the new InfoObjects. The remaining new InfoProviders also use the new InfoObjects.
SAP AG
DBW70E
hhhUyyn Fh
7-21
yghyhn Fy
g h hUyn&S gyyyhn6
h h 1 yyy&S gyUhhn6
SAP AG 2006
SAP AG
DBW70E
7-22
9B560'$7$67$7(
567&B%:B*(7B'$7$B& 9B563&352&6767$786
0XOWL3URYLGHU
0XOWL3URYLGHU
4XHULHV
SAP AG 2006
For the current data-load status of process chains and processes: 0TCT_VC11 and 0TCT_MC11 For the current status of requests loaded to InfoProviders, InfoObjects that have been updated flexibly, and PSA tables: 0TCT_VC11 and 0TCT_MC11
SAP AG
DBW70E
x hgyUhyx Fy
7-23
560'$7$67$7(B(;7
560'$7$67$7(
zhgygU Ug
hx Ugn
" 14
ZLWK YDULRXV NH\ ILJXUHV DQG FKDUDFWHULVWLFV HDFK IRU WKH VHYHUDO FULWHULD
$OO UHTXHVWV
SAP AG 2006
SAP AG
| | | | | | | | |
4XDOLWDWLYHO\ QRW 2. UDQNLQJ FULWHULRQ QRW IRU 36$ 7HFKQLFDOO\ QRW 2. ILOWHU FULWHULRQ 1RW DFWLYDWHG RQO\ IRU 'DWD6WRUH REMHFWV 1RW FRPSUHVVHG RQO\ IRU ,QIR&XEHV 1RW DJJUHJDWHG RQO\ IRU ,QIR&XEHV
DBW70E
7-24
SAP AG 2006
SAP AG
DBW70E
7-25
'HVFULEH KRZ WR ZRUN ZLWK %, 6WDWLVWLFV 'DWD /RDG 6WDWLVWLFV *LYH DQ RYHUYLHZ RI WHFKQLFDO FRQWHQW IRU %, 6WDWLVWLFV 'DWD /RDG 6WDWXV
SAP AG 2006
SAP AG
DBW70E
7-26
'HVFULEH KRZ WR ZRUN ZLWK %, 6WDWLVWLFV 'DWD /RDG 6WDWLVWLFV *LYH DQ RYHUYLHZ RI WHFKQLFDO FRQWHQW IRU %, 6WDWLVWLFV 'DWD /RDG 6WDWXV
SAP AG 2006
SAP AG
DBW70E
7-27
SAP AG
DBW70E
7-28
3HUIRUPDQFH 2SWLPL]DWLRQ
&RQWHQWV
%, $FFHOHUDWRU
SAP AG 2006
SAP AG
DBW70E
8-1
3URYLGH D UDWLRQDOH IRU WKH %, $FFHOHUDWRU RI 6$3 1: V DQG GHVFULEH LWV FRQILJXUDWLRQ DQG DGPLQLVWUDWLRQ IHDWXUHV 'HVFULEH 6$3 1: V %, SHUIRUPDQFH RSWLPL]DWLRQ HQKDQFHPHQWV
SAP AG 2006
SAP AG
DBW70E
8-2
3UHIDFH ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 'DWD 0RGHOLQJ 'DWD $FTXLVLWLRQ 7UDQVIRUPDWLRQ DQG 8QLW RI 0HDVXUH &RQYHUVLRQ 'DWD )ORZ &RQWURO $GPLQLVWUDWLRQ DQG 0RQLWRULQJ 3HUIRUPDQFH 2SWLPL]DWLRQ ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
8-3
5HSRUWLQJ XVHUV DUH UHTXLULQJ LQFUHDVLQJO\ IDVW DFFHVV WR FRUSRUDWH LQIRUPDWLRQ DQG \RX QHHG WR XQGHUVWDQG KRZ WKH %, $FFHOHUDWRU ZLOO HQDEOH WKLV )XUWKHUPRUH \RX ZRXOG OLNH WR VHH ZKDW GHWDLOHG SHUIRUPDQFH HQKDQFHPHQWV KDYH DGGLWLRQDOO\ EHHQ LQWURGXFHG LQ 6$3 1:V %, LQ LWV UHSRUWLQJ ZDUHKRXVH PDQDJHPHQW DQG DGPLQLVWUDWLRQ DVSHFWV
SAP AG 2006
SAP AG
DBW70E
8-4
3HUIRUPDQFH 2SWLPL]DWLRQ
/HVVRQ %, $FFHOHUDWRU /HVVRQ 3HUIRUPDQFH 2SWLPL]DWLRQ 'HWDLOV
SAP AG 2006
SAP AG
DBW70E
8-5
3URYLGH D UDWLRQDOH IRU WKH %, $FFHOHUDWRU LQ 6$3 1: V 'HVFULEH FRQILJXUDWLRQ RI WKH %, $FFHOHUDWRU
SAP AG 2006
SAP AG
DBW70E
8-6
8VHUV UHTXLUH IDVWHU DQG IDVWHU DFFHVV WR FRUSRUDWH LQIRUPDWLRQ 7KH %, $FFHOHUDWRU LV WUDQVSDUHQW WR WKH %, XVHU DQG GRHV QRW FKDQJH WKH %, XVHU H[SHULHQFH +RZHYHU LW DFKLHYHV D SHUIRUPDQFH VSHHGXS IDFWRU RI EHWZHHQ DQG
SAP AG 2006
SAP AG
DBW70E
8-7
SAP AG
DBW70E
8-8
2YHUYLHZ
%, $FFHOHUDWRU $GPLQLVWUDWLRQ
SAP AG
DBW70E
8-9
SAP AG 2006
When data volumes increase, when numbers and sophistication of users increases, the challenges to maintaining consistently good query performance can be daunting. There are several factors naturally contributing to the accelerating growth of data: Enterprise Data Warehousing, where often very detailed historical data is stored on a long-term basis Retail, Point-of-Sale data flowing into SAP systems RFID (Radio Frequency technologies), large data volumes The mass deployment of SAP BI web applications as content in corporate portals
Maintaining Consistently good query performance is an ongoing challenge: Administration costs can be high: performance and administration team time and effort, as well as expertise required. Also, the processing costs for performance-related maintenance jobs can be high in some cases as well.
SAP AG
DBW70E
&KDOOHQJHV IRU UHVRXUFH DOORFDWLRQ XSGDWLQJ FDSDFLW\ SODQQLQJ PD\ UHVXOW LQ DGGLWLRQDO KDUGZDUH LQYHVWPHQW
5 G6$! & ))$G3F$A#E)60$D % D C & & C)2A76B()A#)@#6#( 9 & 5 & ' & & 8 & 5 & 4 % & 0# !$()!76)$() 32# 1 & ' % " 0)(& %#$#!
8-10
' 5 (h00(6 d h0!76 9 & 8 & 4 8 5 R v)$62E)w$2E)($!F& q 8 " 8 4 8 " 55 )!#$()((I#y 8 ' D & 8 p % 8 4 4 8 (F#$#AA0& P$7) #wT
5HSRUWLQJ $JHQW ,QIRUPDWLRQ %URDGFDVWLQJ
5 & VW (@(6 & " 5 ' & $#(02!(7$$ C & % 8 & q & 8 ()(20$ 02@)$p ' " q D & 8 p ()$0B0A$& 3)$7Y) %t 5 & 4 & & % & v$(2@002)& )
& D 8 5 20)!$ 9 5 R & % & #B& B$F x 3)0! & D 8 y & 6E$$ix h!w#8 `
SAP AG
SAP AG 2006
3HUIRUPDQFH )HDWXUHV
$JJUHJDWHV
%, $FFHOHUDWRU
DBW70E
2/$3 &DFKH
8-11
SAP AG 2006
$UH %, REMHFWV GHVLJQHG WR LPSURYH TXHU\ UHVSRQVH WLPHV 6WUXFWXUDOO\ ORRN WKH VDPH DV DQ ,QIR&XEH $UH VXEVHWV RI IDFW WDEOH GDWD
Aggregates use the same Star Schema design that cubes use Aggregates do not contain ALL data from InfoCubes, thus they cannot replace InfoCubes. Aggregates are for InfoCubes what indexes are for database tables When a query is executed or query navigation takes place, the OLAP Engine splits the request into several database queries. The system then looks for the best possible aggregate for each of the database queries. An easy way to conceptualize an aggregate is to think of it as providing a similar benefit as adding an additional index to a database table. Aggregates require no special knowledge by the end-user, as they are completely transparent. The only way an end-user might recognize the existence of an aggregate is by the performance gain that is observed. You can only create aggregates for BasicCubes. You do not have to create aggregates for MultiProviders because the system splits up a MultiProvider query into subqueries for the individual sub-InfoCubes. How many aggregates do you need? You have to decide which aggregates you need. To ensure good performance: Pre-calculate aggregates for main queries and reports; Restrict scope and frequency of reporting. This is a trade-off between flexibility and performance. You cannot create aggregates for all possible queries. Thus, the typical strategy is to build somewhat general aggregates that more queries can utilize, but the performance benefit per query is less significant
SAP AG
q G%)$ h0!Y60) A0(#2(3F$E$7$2A76v& G%)#EQ A20)$6$Q)75 9 % 8 & 8 & q & " C & 8 p & 5 % D & ' & ' '
7\SLFDOO\ VWRUH VXPPDU\ GDWD LQ QHZ VPDOOHU FKLOG ,QIR&XEHV $UH WUDQVSDUHQW WR XVHUV
DBW70E
8-12
$ QHZ DSSURDFK
7KH ODWHVW FRPSXWHU DUFKLWHFWXUHV PDNH PRUH LQWHQVLYH XVH RI LQFUHDVLQJO\ LQH[SHQVLYH PHPRU\ UHVRXUFHV 6HDUFK HQJLQHV GHOLYHU IDVW UHVSRQVHV E\ JLYLQJ UHDG DFFHVV SULRULW\ RYHU LQGH[ XSGDWHV %XW FDQ DQ HQJLQH ILUVW FRQFHLYHG IRU WH[W VHDUFK EH XVHG WR LPSOHPHQW IDVW VHDUFK IRU VWUXFWXUHG GDWD LQ WDEOHV" <HV 6$3 DGDSWHG LWV 75(; VHDUFK HQJLQH WR LPSOHPHQW 7KH %, DFFHOHUDWRU
SAP AG 2006
SAP AG
DBW70E
8-13
6WRUDJH
SAP AG 2006
Terminology: 75(; DQG %, $FFHOHUDWRU y TREX : Search and classification engine, mainly for unstructured data y BI Accelerator is built using TREX technology (indexing, retrieving, compression ...) to handle structured data y Note: BI Accelerator and TREX are two different installations - The BI Accelerator cannot be used for standard KMC functionality - A TREX installation cannot be used as a BI accelerator - Inside info: technically there is a lot of commonality but TREX-BI Accelerator role switching is not supported ,QGH[ y BI Accelerator index: Structure containing replicated data and indexes (one index per table) that represents the BI star schema for the BI Accelerator y Indexing: Transfer of InfoCube data to the BI Accelerator server and processing and compressing it into the BI Accelerator index
SAP AG
4XHU\ 3URFHVVLQJ
DBW70E
8-14
%, $FFHOHUDWRU $UFKLWHFWXUH
qrrv u Fgpdjh
,QGH[LQJ %, $FFHOHUDWRU
DBW70E
%, $QDO\WLF (QJLQH
'DWD $FTXLVLWLRQ
6$3 1HW:HDYHU %,
SAP AG 2006
Only one BI Accelerator server can be used for each BI system. This is because the master data tables stored in the BI Accelerator server can be used by multiple BI Accelerator indexes. However, this does not work if the data is distributed across various BI Accelerator servers. However, various BI systems can store their data on the same BI Accelerator server and access it there as long as there is enough room on the server. It is thus not necessary for each BI system in the productive landscape to have its own BI Accelerator server. The system ID is used to keep the indexes separate. %, $FFHOHUDWRU ,QGH[ A BI accelerator index contains all the data of a BI InfoCube in a compressed but not aggregated format. The BI accelerator index stores the data at the same level of granularity as the InfoCube. It consists of several, possibly split indexes that correspond to the tables of the enhanced star schema and a logical index which, depending on the star schema description, contains the metadata of the BI accelerator index.
SAP AG
4XHU\ 5HVSRQVH
& 8 & ' & ' ' 9 !GP3A@02)$6$@({$2z y & 8 p 4 & % & Y0& 3)$AhQ#(7(x602& )w & D 8 5 5 & s & 0$hF 9 6B0(0)( & & & 066B({02$2#}e
8-15
4XHU\ ([HFXWLRQ
3UHFDOFXODWLRQ ,QIRUPDWLRQ %URDGFDVWLQJ 2/$3 &DFKH 3UHFDOFXODWLRQ ,QIRUPDWLRQ %URDGFDVWLQJ 2/$3 &DFKH
$JJUHJDWH
%, $FFHOHUDWRU
,QIR3URYLGHU
7KH %, V\VWHP FKHFNV WKH OLVWHG UHSRVLWRULHV LQ WKH RUGHU VKRZQ WR REWDLQ WKH TXHU\ UHVXOW VHW
SAP AG 2006
BI accelerator is used to improve the read performance of BI queries on InfoCubes. It enables quick access to any data with a low amount of administrative effort and is especially useful for sophisticated scenarios with unpredictable query types, high data volume and high frequency of queries.
SAP AG
DBW70E
8-16
%, $FFHOHUDWRU 5DWLRQDOH
%, $FFHOHUDWRU
3ODQQHG VXSSRUW RI QHZ KDUGZDUH SDUDGLJPV OLNH JULGDGDSWLYH FRPSXWLQJ +LJK VFDODELOLW\ 6LJQLILFDQW 7&2 UHGXFWLRQ 1R DJJUHJDWH PDLQWHQDQFH PLQLPL]HG UROOXSFKDQJH UXQ /RZ PDLQWHQDQFH
SAP AG 2006
The benefits of the approach may be summarised as being scalable, fast and predictable.
SAP AG
DBW70E
8-17
%, $FFHOHUDWRU 6FHQDULRV
5HDG\ IRU KLJK GDWD YROXPHV
4XHULHV WKDW URXWLQHO\ LQYROYH DFFHVV WR PDQ\ PLOOLRQV RI UHFRUGV DQG PD\ LQYROYH XS WR ELOOLRQV RI UHFRUGV ([DPSOHV UHWDLO XWLOLWLHV WHOHSKRQH FRPSDQLHV ([DPSOH VHUYLFH OHYHO DJUHHPHQWV IRU FDOO FHQWHU RSHUDWRUV GHPDQG VKRUW UHVSRQVH WLPHV IRU JRRG FORVXUH UDWHV
SAP AG 2006
The administrator in the background will be able to switch servers on or off at will to scale the landscape to suit the current load. The BI Accelerator is predictable in that any requests that you send for data will get a response back in a reasonable time and in a time that is very similar each time you make the same request. This is in contrast to previous BI releases running on a relational database, where response times varied strongly depending omn whether a pre-existing aggregate was available for that query or not or whether the attribute had been cached etc.
SAP AG
([FHOOHQW UHVSRQVH WLPHV IRU DQ\ GULOOGRZQ VOLFH GLFH ([DPSOHV RQGHPDQG UHSRUWLQJ IRU GLIIHUHQW XVHU JURXSV DG KRF DQDO\VHV
)DU PRUH GLIIHUHQW GDWD VHWV DQG DJJUHJDWLRQV WKDQ WUDGLWLRQDO RSWLPL]DWLRQ DQG FDFKLQJ VWUDWHJLHV FDQ KDQGOH
DBW70E
8-18
SAP AG 2006
The BI Accelerator server is a specific part of the server for the SAP NetWeaver Search and Aggregation Engine (TREX). The data from the BI InfoCube is located in the BI Accelerator index in a compressed but not aggregated form. This means that the BI Accelerator index contains the data in the same granularity as the InfoCube. With an active BI Accelerator index, BI queries do not read the data from the database; instead they read it from the BI Accelerator server. Thus strategies for faster reads of data such as those in the first part of the slide will not normally be so essential. You can continue to also have relational aggregates for an InfoCube for which you have created a BI accelerator index. However, since queries always access the BI accelerator index first, this modeling is not worthwhile.
SAP AG
& %&0$w 9V &(3{w() %AG'(## 30)2)(w0($2(#( " " " % & 4 & 8 & ' " & & 4 & & s % & 6Fg)230${AGh$)02$#E IT $3)&20(@)$!& )E $6 1 4 q & 8 p % D & & % % 0A)8#S2$))& %)A `
~ ~ ~
DBW70E
8-19
+DUGZDUH H[DPSOH
,PSURYHPHQW IDFWRU
SAP AG 2006
SAP AG
$W 6$33+,5( LQ %RVWRQ 6$3 ([HFXWLYH %RDUG PHPEHU 6KDL $JDVVL GHPRQVWUDWHG WKH %, DFFHOHUDWRU E\ ODXQFKLQJ FRPSOH[ TXHULHV DJDLQVW D ELOOLRQ GDWD UHFRUGV DQG JHWWLQJ UHVXOWV EDFN LQ VHFRQGV )RU WKH GHPRQVWUDWLRQ WKH %, $FFHOHUDWRU UDQ XQGHU ELW /LQX[ RQ EODGHV HDFK ZLWK GXDO *+] ,QWHO ;HRQ SURFHVVRUV DQG *% RI 5$0 PRXQWHG DERYH D +HZOHWW3DFNDUG 3UR/LDQW VHUYHU ZLWK ,QWHO ,WDQLXP SURFHVVRUV UXQQLQJ 6$3 1HW:HDYHU V %, XQGHU +3 8; DQG DQ +3 6WRUDJH:RUNV ILOHU DOO LQ D VWDQGDORQH FDELQHW
DBW70E
8-20
3HUIRUPDQFH
6XPPDU\ 7DEOHV
/HVV IDVW
'DWDEDVH
5HXVDELOLW\ +LJK UHXVDELOLW\ 9HU\ IHZ VSHFLILF REMHFWV RU VHWV QHHG EH XVHG WR DFFHOHUDWH PDQ\ GLIIHUHQW TXHULHV
SAP AG 2006
/RZHVW
+LJKHVW
High reusability means that very few specific objects (or sets) need be used to accelerate many different queries.
SAP AG
DBW70E
8-21
SAP AG
DBW70E
8-22
2YHUYLHZ
%, $FFHOHUDWRU $GPLQLVWUDWLRQ
SAP AG
DBW70E
8-23
%, $FFHOHUDWRU ,QVWDOODWLRQ
,QVWDOODWLRQ RI WKH %, $FFHOHUDWRU 'XULQJ WKH UDPSXS RI 6$3 1HW:HDYHU V WKH %, $FFHOHUDWRU ZLOO RQO\ EH DYDLODEOH LQ D ER[ %, DFFHOHUDWRU DSSOLDQFH
7KH ER[ ZLOO EH GHOLYHUHG ZLWK WKH FRPSOHWH %, $FFHOHUDWRU SUHLQVWDOOHG
SAP AG 2006
SAP AG
7KH ER[ PD\ EH VWDQGDORQH RU ILW LQWR DQ H[LVWLQJ FXVWRPHU UDFN 7KH ER[ ZLOO FRQWDLQ EODGH VHUYHUV ZLWK ELW ,QWHO ;HRQ &38V LQ
+HZOHWW3DFNDUG RU ,%0 KDUGZDUH
DBW70E
8-24
SDUDOOHO XVHU VHVVLRQV PLOOLRQ URZV WRWDO E\WH URZ
SAP AG 2006
SAP AG
SDUDOOHO XVHU VHVVLRQV PLOOLRQ URZV WRWDO E\WH URZ
SDUDOOHO XVHU VHVVLRQV PLOOLRQ URZV WRWDO E\WH URZ
DBW70E
8-25
SAP AG 2006
A BI Accelerator index is a redundant data store of a BI InfoCube on the BI Accelerator server. The BI Accelerator server is a specific part of the server for the SAP NetWeaver Search and Aggregation Engine (TREX). With the new %,$ LQGH[ PDLQWHQDQFH ZL]DUG you can create, activate, fill and delete BI Accelerator indexes.
SAP AG
DBW70E
8-26
SAP AG 2006
,QLWLDO 6HWWLQJV Communication between the BI system and the BI accelerator server takes place using RFC modules. In order to connect a BI accelerator server to the BI system, first you have to maintain the following settings for the RFC destination: Set up the RFC destination for the BI accelerator server (transaction SM59) Set the RFC destination for the BI accelerator server (transaction RSADMIN, the parameter HPA RFC Destination has to correspond to the above RFC destination)
SAP AG
DBW70E
8-27
8SGDWH RI QHZO\ ORDGHG GDWD WR %, $FFHOHUDWRU LQGH[ 6LPLODU WR UROOXS SURFHVV IRU DJJUHJDWHV %XW WKHUH LV RQO\ RQH %, $FFHOHUDWRU LQGH[ WR DGMXVW 6R WKH SURFHVV LV PXFK HDVLHU DQG IDVWHU 6DPH SURFHVV IRU %, $FFHOHUDWRU DQG DJJUHJDWHV SURFHVV FKDLQV GR QRW QHHG WR EH FKDQJHG DIWHU LPSOHPHQWLQJ WKH %, $FFHOHUDWRU 8SGDWH %, $FFHOHUDWRU LQGH[ DIWHU PDVWHU GDWDKLHUDUFK\ FKDQJHV %, $FFHOHUDWRU LQGH[ KDV VDPH JUDQXODULW\ DV WKH ,QIR&XEH
&KDQJH 5XQ
%, $FFHOHUDWRU LQGH[ LQFOXGHV VRPH PDVWHU GDWD WDEOHV ZKLFK KDYH WR EH XSGDWHG ZLWKLQ PLQLPDO UXQWLPH $GMXVWPHQW RI %, $FFHOHUDWRU LQGH[ IRU NH\ GDWH FKDQJHV RI WLPHGHSHQGHQW DWWULEXWHV LV QRW QHFHVVDU\ 6DPH SURFHVV IRU %, $FFHOHUDWRU DQG DJJUHJDWHV SURFHVV FKDLQV GR QRW QHHG WR EH FKDQJHG DIWHU LPSOHPHQWLQJ %, $FFHOHUDWRU
SAP AG 2006
Roll-up and change run procedures will be involved with the BI Accelerator and there are similarities to those processes concerning aggregates on the relational database. With BI accelerator indexes you do not have to compress after rolling up data packages. The data on the BI accelerator server already exists in a read-optimized format. Because, like aggregates, BI accelerator indexes are affected by changes to master data, they are also affected by hierarchy/attribute change runs. If an InfoCube that forms the basis of a BI accelerator index is later compressed or data is deleted from it, we recommend that you rebuild the BI accelerator index.
SAP AG
e7IxIIgp7YYxwddIdYx7I
~ ~ ~ ~ ~ ~ ~ ~ ~ ~
DBW70E
8-28
75(;
%, $FFHOHUDWRU 4XHULHV UXQ DJDLQVW ERWK LQGH[HV
%HQHILWV
'HOWD ,QGH[
0DLQ ,QGH[
SAP AG 2006
SAP AG
DBW70E
8-29
SAP AG
DBW70E
8-30
2YHUYLHZ
%, $FFHOHUDWRU $GPLQLVWUDWLRQ
SAP AG
DBW70E
8-31
SAP AG 2006
SAP AG
DBW70E
02) 0 V
0RQLWRULQJ
6$3 1HW:HDYHU %,
75(;
8-32
%, $FFHOHUDWRU 0RQLWRU
%, $FFHOHUDWRU 0RQLWRU
,QWURGXFHG LQ 63
SAP AG 2006
The BI Accelerator monitor is used for technical administration and maintenance of the BI Accelerator. It provides an overview of the current status of the BI accelerator. The results of the consistency checks are displayed. These checks run periodically on the BI accelerator. If problems occur, the system automatically suggests appropriate actions. These actions involve BI Accelerator repair functions, which can be used to solve problems. To be able to estimate the status of the BI Accelerator quickly, there is a TXLFN RYHUYLHZ IXQFWLRQ for the BI Accelerator monitor that summarizes the most important check results. The detailed BI Accelerator monitor offers a detailed, technical overview of the hardware, BI Accelerator services, any trace files that may exist and the BI Accelerator indexes. You are in the Administration functional area of the Data Warehousing Workbench. In the navigation window, choose Monitors BI Accelerator Monitor. The quick overview of the BI accelerator monitor appears. Or You are in transaction RSDDV, in the BI accelerator index maintenance. From the menu, choose *RWR %,$ 0RQLWRU. The quick overview of the BI accelerator monitor appears.
SAP AG
4XLFN 2YHUYLHZ IXQFWLRQ DYDLODEOH $FFHVV YLD 'DWD :DUHKRXVLQJ :RUNEHQFK RU WUDQVDFWLRQ 56''9
DBW70E
8-33
SAP AG
DBW70E
8-34
2YHUYLHZ
SAP AG
DBW70E
8-35
%, $FFHOHUDWRU 6XPPDU\
4XHU\ SURFHVVLQJ LQ PHPRU\
6RSKLVWLFDWHG FRPSUHVVLRQ
7KH %, DFFHOHUDWRU LV WUDQVSDUHQW IRU WKH DSSOLFDWLRQV DQG UG SDUW\ WRROV
$YDLODEOH IRU DOO DSSOLFDWLRQV DQG WRROV WKDW
(DV\ PLJUDWLRQ IURP H[LVWLQJ DJJUHJDWH VHWXS WR WKH %, DFFHOHUDWRU 4XHULHV DXWRPDWLFDOO\ XVH WKH %, DFFHOHUDWRU
SAP AG 2006
SAP AG
8VH 6$3 1HW:HDYHU %, IRU UHSRUWLQJ DQG DQDO\WLFV $UH EDVHG RQ 6$3 1HW:HDYHU V
DBW70E
8-36
%, $FFHOHUDWRU 2XWORRN
3ODQQHG HQKDQFHPHQWV IRU WKH %, DFFHOHUDWRU LQ WKH URDGPDS
)XUWKHU KDUGZDUH SODWIRUPV
SAP AG 2006
SAP AG
0RYH PRUH DQG PRUH DQDO\WLF RSHUDWLRQV WKDW PDNH LQWHQVLYH XVH RI PHPRU\ VXFK DV 7RS 1 TXHULHV WR WKH %, DFFHOHUDWRU 0HUJH 6$3 1HW:HDYHU %, DQG 75(; FDFKH WHFKQRORJLHV
DBW70E
8-37
3URYLGH D UDWLRQDOH IRU WKH %, $FFHOHUDWRU LQ 6$3 1: V 'HVFULEH FRQILJXUDWLRQ RI WKH %, $FFHOHUDWRU
SAP AG 2006
SAP AG
DBW70E
8-38
3HUIRUPDQFH 2SWLPL]DWLRQ
/HVVRQ %, $FFHOHUDWRU /HVVRQ 3HUIRUPDQFH 2SWLPL]DWLRQ 'HWDLOV
SAP AG 2006
SAP AG
DBW70E
8-39
'HVFULEH 6$3 1: V SHUIRUPDQFH RSWLPL]DWLRQ HQKDQFHPHQWV LQ WKH DUHDV RI 2/$3 &DFKH DQG 4XHU\ ([HFXWLRQ
'HVFULEH 6$3 1: V SHUIRUPDQFH RSWLPL]DWLRQ HQKDQFHPHQWV LQ WKH DUHDV RI 3DUWLWLRQLQJ DQG 5HSDUWLWLRQLQJ 'HVFULEH 6$3 1: V SHUIRUPDQFH RSWLPL]DWLRQ HQKDQFHPHQWV LQ 5HTXHVW $UFKLYLQJ
'HVFULEH 6$3 1: V SHUIRUPDQFH RSWLPL]DWLRQ HQKDQFHPHQWV LQ WKH DUHDV RI 5ROOXS &KDQJH 5XQ &RPSUHVVLRQ DQG 6HOHFWLYH 'HOHWLRQ
SAP AG 2006
SAP AG
DBW70E
8-40
:LWK WKH RYHUDOO JRDO RI LPSURYLQJ SHUIRUPDQFH GXULQJ TXHU\ H[HFXWLRQ D QXPEHU RI PLVFHOODQHRXV HQKDQFHPHQWV KDYH EHHQ UHDOL]HG ZLWKLQ 2/$3 VHWWLQJV GDWD ORDGLQJ DQG DGPLQLVWUDWLRQ
SAP AG 2006
SAP AG
DBW70E
8-41
SAP AG
DBW70E
8-42
2YHUYLHZ
2/$3 &DFKH (QKDQFHPHQWV 4XHU\ ([HFXWLRQ &RPSUHVVLRQ 5ROOXS DQG &KDQJH 5XQ 6HOHFWLYH 'HOHWLRQ
5HTXHVW $UFKLYLQJ
SAP AG
DBW70E
8-43
2YHUYLHZ
SAP AG 2006
SAP AG
DBW70E
8-44
$ TXHU\ UHDGV GDWD IURP WKH 2/$3 &DFKH DV IDU DV SRVVLEOH $GGLWLRQDO UHTXHVWV ZLOO EH UHDG IURP WKH ,QIR&XEHV ) IDFW WDEOH 5HVWULFWLRQV
7KHVH DGGLWLRQDO UHTXHVWV ZLOO EH XSGDWHG LQWR WKH 2/$3 &DFKH
2/$3 &DFKH
,I WKH ,QIR&XEH LV FRPSUHVVHG GHOWD FDQQRW EH GHWHUPLQHG &DFKH HQWU\ ZLOO EH EXLOW XS FRPSOHWHO\
SAP AG 2006
SAP AG
DBW70E
'HOWD &DFKLQJ
,QIR&XEH )
8-45
'HOWD &DFKLQJ
6HWWLQJ SHU TXHU\
SAP AG 2006
On the 4XHU\ 3URSHUWLHV dialog box for the query monitor you can make settings for a BI query with regard to the UHDG PRGH, the FDFKH PRGH, the VHOHFWLRQ RI VWUXFWXUH HOHPHQWV, the RSWLPL]DWLRQ PRGH and the FDOFXODWLRQ DFFXUDF\. Activation of delta caching is also seen as a setting here.
SAP AG
7UDQVDFWLRQ 5657
DBW70E
8-46
*URXSLQJ RQH JURXS VWRUHV DOO ,QIR&XEH UHVXOWV RWKHU REMHFWV LQ RQH RU PRUH JURXSV XVHV GHOWD FDSDELOLWLHV RI LQIR&XEHV *URXSLQJ ZLWK VHSDUDWH EDVLV ,QIR&XEHV HYHU\ ,QIR&XEH UHVXOW LV VWRUHG VHSDUDWHO\ 6HSDUDWLRQ RI DOO ,QIR3URYLGHUV
SAP AG 2006
A query on a MultiProvider is deconstructed internally into sub-queries. These are processed in parallel by default. In most cases parallel processing has benefits in terms of performance. However, in some cases sequential processing can be more advantageous for query performance. You are able to switch parallel processing for a MultiProvider off in the RSADMIN table. You can switch off parallel processing for a query on a MultiProvider in the 4XHU\ 0RQLWRU. Settings can be made for the field partitioning type: 0 No Partitioning 1 Partitioning in Groups 2 Partitioning in Groups BasicCubes separate 3 Every Provider separate
SAP AG
DBW70E
8-47
4XHU\ ([HFXWLRQ
6SOLWV LQ DQDO\WLFDO HQJLQH FRQVWDQW VHOHFWLRQ FHOO FDOFXODWLRQV DUH SDUDOOHOL]HG ZLWK WKH H[FHSWLRQ RI QRQFXPXODWLYH FDOFXODWLRQV 1XPEHU RI SDUDOOHO SURFHVVHV PLQ PD[ IUHH SURFHVVHV QRW PRUH WKDQ SDUDOOHO SURFHVVHV
SAP AG 2006
SAP AG
DBW70E
p FEare
pgig0
0 pg(jG
) (
8-48
EF $gg# Fa
4XHU\ ([HFXWLRQ
SAP AG 2006
The change run, rollup, condensing and checking up multiple aggregates can be executed in parallel. Parallelization takes place using the aggregates. The parallel processes are continually executed in the background, even when the main process is executed in the dialog. This can considerably decrease execution time for these processes. You can determine the degree of parallelization and determine the server on which the processes are to run and with which priority. Parallelization of the change run according to SAP Note 534630 is obsolete and is no longer being supported.
SAP AG
DBW70E
8-49
2QFH RQH MRE LV ILQLVKHG WKH V\VWHP FKHFNV IRU WKH QH[W OHYHO RI DJJUHJDWHV
,Q WKH ILUVW VWHS DOO EDVLV DJJUHJDWHV KDYH WR EH FDOFXODWHG LI WKHUH DUH PRUH SURFHVVHV DYDLODEOH WKDQ EDVLV DJJUHJDWHV QRW DOO SURFHVVHV DUH XVHG 7KH IROORZLQJ JUDSKLF LV VLPSOLILHG DV QRW DOO MREV HQG DW WKH VDPH WLPH VRPH MREV PLJKW EH HQWDQJOHG
You can start multiple change runs simultaneously. The prerequisite for this is that the lists of the master data and hierarchies to be activated are different and that the changes affect different InfoCubes. After a change run, all affected aggregates are condensed automatically. SAP Note 583202 is obsolete.
SAP AG
DBW70E
6WHS
6WHS
Yd
8-50
Y$
d
gpii00 0g(
gpii00
gE7Ej
6WHS
&RPSUHVVLRQ
&RPSUHVVLRQ
SAP AG 2006
*HQHUDO 2SWLPL]DWLRQV
$XWRPDWLF '% SDUDOOHOLVP YLD 0(5*(836(57 QRZ DOVR DYDLODEOH IRU ,%0 '%
,QVHUWV ZLOO EH XVHG DXWRPDWLFDOO\ LQ FDVH ,QIR&XEH LV HPSW\ RU WKH UHVSHFWLYH WLPH YDOXH LV QHZ
SAP AG
*HQHUDWLRQ RI FRPSUHVVLRQ SURJUDPV KDV EHHQ UHGXFHG SHUIRUPDQFH LPSURYHPHQW HVSHFLDOO\ IRU VPDOO UHTXHVWV
DBW70E
8-51
6HOHFWLYH 'HOHWLRQ
SAP AG 2006
Selective Deletion Deleting in partitions System automatically detects a database partition which matches a subset of the records to be deleted Scenario: you archive a group of records and expect performance improvement by dropping complete partitions Recommendation: use this flag for large data sets; for small sets the selective deletion might work faster than the initial check for partitions
SAP AG
DBW70E
8-52
(QKDQFHG SDUWLWLRQLQJ
3DUWLWLRQLQJ
)@(0(){0$(0 ))2SG3E!)E2# $()( $t6{#$$2S(6BE 30 306S A60)0Y$ 3Ei 3$ )$32 0 )2E(B66 2It$)!0 ))2Y0$$) #0 )2@$2( 7 3 )6$6A )2Q$0 (( 3E ))rE 3)$( 002F#$(E)(gG)!#(E()@6$@)$7A$#(2Y # 30()I )t6@(){30w07 rA0Fi()2)(0(#Y7Y G!$)0A2$
##2)6B ))2$$
25$&/(
@$)$(Y(3 !S 3E g#2)#E0I 6 )$$$w$ #2d((w @ 3@(# 3 Pg$I $($( ()G3 32)
SAP AG
SAP AG 2006
There was previously a more limited list of database platforms supporting partitioning.
DBW70E
8-53
5HSDUWLWLRQLQJ
SAP AG 2006
Repartitioning - with SAP NetWeaver 2004s, the repartitioning of InfoCubes and DataStore objects on the database that are already filled is supported. Scenario: after the initial partitioning, you require additional partitions and you want to merge early partitions after archiving data
Three use cases of repartitioning tool: Append new partitions Merge partitions Complete repartitioning
SAP AG
DBW70E
8-54
5HSDUWLWLRQLQJ
5HSDUWLWLRQLQJ
SAP AG
SAP AG 2006
DBW70E
8-55
SAP AG
5HSDUWLWLRQLQJ
SAP AG 2006
5HSDUWLWLRQLQJ
0HUJH SDUWLWLRQV
DBW70E
8-56
5HSDUWLWLRQLQJ
5HSDUWLWLRQLQJ
&RPSOHWH UHSDUWLWLRQLQJ
SAP AG
SAP AG 2006
DBW70E
8-57
5HSDUWLWLRQLQJ
5HSDUWLWLRQLQJ 0RQLWRULQJ
'HWDLOHG 0RQLWRULQJ
SAP AG 2006
SAP AG
8QORFN
DBW70E
8-58
5HTXHVW $UFKLYLQJ
SAP AG 2006
SAP AG
DBW70E
8-59
5HTXHVW $UFKLYLQJ
SAP AG 2006
SAP AG
DBW70E
8-60
5HTXHVW $UFKLYLQJ
SAP AG 2006
SAP AG
DBW70E
8-61
5HTXHVW $UFKLYLQJ
SAP AG 2006
SAP AG
DBW70E
8-62
5HTXHVW $UFKLYLQJ
SAP AG 2006
SAP AG
DBW70E
8-63
'HVFULEH 6$3 1: V SHUIRUPDQFH RSWLPL]DWLRQ HQKDQFHPHQWV LQ WKH DUHDV RI 2/$3 &DFKH DQG 4XHU\ ([HFXWLRQ
'HVFULEH 6$3 1: V SHUIRUPDQFH RSWLPL]DWLRQ HQKDQFHPHQWV LQ WKH DUHDV RI 3DUWLWLRQLQJ DQG 5HSDUWLWLRQLQJ 'HVFULEH 6$3 1: V SHUIRUPDQFH RSWLPL]DWLRQ HQKDQFHPHQWV LQ 5HTXHVW $UFKLYLQJ
'HVFULEH 6$3 1: V SHUIRUPDQFH RSWLPL]DWLRQ HQKDQFHPHQWV LQ WKH DUHDV RI 5ROOXS &KDQJH 5XQ &RPSUHVVLRQ DQG 6HOHFWLYH 'HOHWLRQ
SAP AG 2006
SAP AG
DBW70E
8-64
3URYLGH D UDWLRQDOH IRU WKH %, $FFHOHUDWRU RI 6$3 1: V DQG GHVFULEH LWV FRQILJXUDWLRQ DQG DGPLQLVWUDWLRQ IHDWXUHV 'HVFULEH 6$3 1: V %, SHUIRUPDQFH RSWLPL]DWLRQ HQKDQFHPHQWV
SAP AG 2006
SAP AG
DBW70E
8-65
SAP AG
DBW70E
8-66
&RQWHQWV
1HDU /LQH 6WRUDJH ZLWKLQ WKH 6$3 &RQFHSW RI ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
9-1
'HVFULEH WKH FKDOOHQJHV IDFLQJ WKH LQIRUPDWLRQ OLIHF\FOH /LVW EHQHILWV IRU DQ ,/0 VWUDWHJ\ IRU %,
([SODLQ WKH ODWHVW (QWHUSULVH 'DWD :DUHKRXVLQJ 1HDU /LQH 6WRUDJH VWUDWHJLHV IRU SHUIRUPDQFH RSWLPL]DWLRQ DURXQG GDWD YROXPH PDQDJHPHQW 'HVFULEH D SRVVLEOH DUFKLYLQJ VFHQDULR LQ %,
SAP AG 2006
SAP AG
DBW70E
9-2
3UHIDFH ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 'DWD 0RGHOLQJ 'DWD $FTXLVLWLRQ 7UDQVIRUPDWLRQ DQG 8QLW RI 0HDVXUH &RQYHUVLRQ 'DWD )ORZ &RQWURO $GPLQLVWUDWLRQ DQG 0RQLWRULQJ 3HUIRUPDQFH 2SWLPL]DWLRQ ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
9-3
/HDYLQJ GDWD WKDW LV RQO\ RFFDVLRQDOO\ DFFHVVHG RQ GLVN VWRUDJH ZLOO GDPDJH SHUIRUPDQFH 7KLV LVVXH LV H[DFHUEDWHG E\ H[SRQHQWLDO GDWD JURZWK LQFUHDVLQJ OHJDO UHTXLUHPHQWV HJ 62$ DQG WHFKQRORJ\ SURFHVV FRVWV 7KH PDLQ LGHD RI 1HDU /LQH 6WRUDJH LV WKDW WKH DFFHVV IUHTXHQF\ IRU GDWD GHFUHDVHV RYHU WLPH WKH ROGHU GDWD JHWV WKH OHVV LW LV XVHG 1HDU /LQH 6WRUDJH DWWHPSWV WR ILOO WKH JDS EHWZHHQ RQOLQH PHPRU\ DQG FODVVLFDO DUFKLYHV 7HFKQRORJ\ DOORZV IRU GLUHFW 64/ DFFHVV WR EH JLYHQ WR YDULRXV FDWHJRULHV RI VWRUDJH PHGLD LQ WKLV PLGGOH JURXQG
SAP AG 2006
SAP AG
DBW70E
9-4
1HDU /LQH 6WRUDJH ZLWKLQ WKH 6$3 &RQFHSW RI ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW 8QLW 2YHUYLHZ 'LDJUDP
/HVVRQ 1HDU /LQH 6WRUDJH ZLWKLQ WKH 6$3 &RQFHSW RI ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
9-5
1HDU /LQH 6WRUDJH ZLWKLQ WKH 6$3 &RQFHSW RI ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW /HVVRQ 2EMHFWLYHV
'HVFULEH WKH FKDOOHQJHV IDFLQJ WKH LQIRUPDWLRQ OLIHF\FOH /LVW EHQHILWV IRU DQ ,/0 VWUDWHJ\ IRU %,
([SODLQ WKH ODWHVW (QWHUSULVH 'DWD :DUHKRXVLQJ 1HDU /LQH 6WRUDJH VWUDWHJLHV IRU SHUIRUPDQFH RSWLPL]DWLRQ DURXQG GDWD YROXPH PDQDJHPHQW 'HVFULEH D SRVVLEOH DUFKLYLQJ VFHQDULR LQ %,
SAP AG 2006
SAP AG
DBW70E
9-6
This lesson will cover the following topics: Lifecycles of data and information Archiving requirements in the data warehousing area Benefits of modern near-line storage concepts in the data warehouse environment Enhanced archive solutions for the new SAP NW releases using specific linking of partner
SAP AG
DBW70E
9-7
,/0 LV D VWRUDJH PDQDJHPHQW FRQFHSW WKDW DFWLYHO\ PDQDJHV DOO LQIRUPDWLRQ REMHFWV GXULQJ WKHLU HQWLUH OLIHF\FOH
,/0 LV D FRPELQDWLRQ RI SURFHVVHV DQG WHFKQRORJLHV ZKRVH JRDO LW LV WR SURYLGH WKH ULJKW LQIRUPDWLRQ DW WKH ULJKW WLPH LQ WKH ULJKW SODFH ZLWK WKH ORZHVW SRVVLEOH FRVWV
SAP AG 2006
ILM is mentioned very often nowadays. Everyone is talking about ILM. What is the definition? A number of people have only a partial view. Some say it is not only a product, some say it is not only software, a tool.
SAP AG
DBW70E
9-8
:H IURP 6$3 WKLQN ZH VKRXOG EH WDONLQJ DERXW LW WRR DQG RWKHU SHRSOH DUH WKLQNLQJ WKH VDPH
, GR QRW WKLQN PXFK RI ,/0 WRROV $Q 6$3 V\VWHP FDQ GR ,/0 PXFK EHWWHU WKDQ DQ\ RWKHU VRIWZDUH EHFDXVH LW NQRZV WKH LQIRUPDWLRQ UHSUHVHQWHG E\ LWV GDWD
&72 DQG &(2 RI D PDMRU *HUPDQ EDQN
SAP AG 2006
Other people as well as SAP are thinking the same thing. See the statement from the CEO of a major German bank. There is a distinction between information and data in this statement.
SAP AG
DBW70E
9-9
7HFKQRORJLFDO LQQRYDWLRQV
SAP AG 2006
Here we have a list of challenges/problem areas driving the ILM discussion. Amongst the technological innovations is NLS Near-Line Storage.
SAP AG
DBW70E
9-10
6$3 %,
$JJUHJDWLRQ
*UDQXODULW\
SAP AG 2006
Starting in ERP an entity, then change docs. Next layer is the extract layer we will need to extract data for BI. In BI the data model is different it is Multidimensional. The EDW layer consists of DSOs for example. There we see what is happening in ERP layer. Above that we can have operational reporting. Where we see Cubes we have multidimensional objects for strategic analysis. On top of that we could do data mining or business planning. As you go up, the aggregation level increases, and granularity decreases. This is what the information lifecycle is about. We need to understand which layers/models are affected? What is the typical data flow for a document ? for master data. etc?
SAP AG
6$3 (53
'DWD 0LQLQJ%XVLQHVV 3ODQQLQJ 6WUDWHJLF $QDO\VLV &XEHV '62 &KDQJH /RJV 2SHUDWLRQDO 5HSRUWLQJ (':/D\HU 0'0 +LHUDUFKLHV .H\ )LJV 'LPHQVLRQV 0DVWHU 'DWD 0DVWHU 'DWD 'HOWDUHFRUGV 'RFXPHQWV &KDQJH 'RFXPHQWV 'RFXPHQWV 5HODWLRQVKLSV &KDQJH 'RFXPHQWV 0DVWHU 'DWD (QWLWLHV ([WUDFWV (50
DBW70E 9-11
% # $"!
SAP AG 2006
We see above the archiving requirements for the various layers. In the BI layer EDW is the persistent inbound horizon: data is highly granular. We want to have this data directly available for ad-hoc analysis, data mining purposes etc So we need archiving the data volume will increase very fast. Above that direct availability is required here as well an additional challenge for archiving processes.
SAP AG
' (&
0 1)
'DWD 0LQLQJ %XVLQHVV 3ODQQLQJ 6WUDWHJLF $QDO\VLV 2SHUDWLRQDO 5HSRUWLQJ (': /D\HU ([WUDFWV 5HODWLRQVKLSV (QWLWLHV
3HUVLVWHQW %, LQERXQG KRUL]RQ +LJKYROXPH KLJKO\ JUDQXODU GDWD 'LUHFW DYDLODELOLW\ IRU GDWD WUDQVIHU UHTXLUHG 'DWD $UFKLYLQJ 3URFHVVHV 'HVFULSWLRQ RI H[WUDFWLRQ IRUPDWV '$57 'DWD 5HWHQWLRQ 7RRO 6HUYLFH $3, IRU %, ([WUDFWLRQ &ODVVLF DUFKLYLQJ $UFKLYLQJ 2EMHFWV /HJDO VWRUDJH UHJXODWLRQV &RVW UHGXFWLRQ
DBW70E
9-12
5HDOL]H
$QDO\]H &DWHJRUL]H
,/0
$SSO\ 3ROLF\
'HWHUPLQH SROLFLHV IRU DWWULEXWHV DQG FDWHJRULHV VXFK DV UHWHQWLRQ SHULRG OHJDO FRPSOLDQFH GDWD H[WUDFWV
This is a definition of ILM in the SAP environment in one view. We need to analyze... catageorize (what we saw in the previous slides - this is the starting point). Then we would define policies for these categories, you must know which are the most important business areas / data / InfoCubes, eg where there are special legal requirements. Applying that, it may mean that something from one InfoCube stays one year; from another InfoCube ten years because of legal requirements Realizing will mean automating archiving, deletion of data from operative systems and consider reload processes etc.
SAP AG
DBW70E
9-13
SAP AG 2006
The findings such as the above are driving the ILM discussion very strongly.
SAP AG
DBW70E
9-14
7KH DGPLQVWUDWLYH H[SHQVH IRU WHUDE\WH RI PHPRU\ LV ILYH WR VHYHQ WLPHV DV KLJK DV WKH PHPRU\ FRVW LWVHOI
SAP AG 2006
The increasing data volume is not only an issue of hardware costs consider memory, software too; but also environmental and personnel costs etc.
SAP AG
DBW70E
p q Sq SflSb
xv y y BxFy yw tu r p sq i
9-15
,QFUHDVH $YDLODELOLW\
2SWLPL]H 3HUIRUPDQFH
SAP AG 2006
With a fundamental ILM strategy it is possible to increase the volumes, reduce resource consumption, enable greater availability and speed up both data loading and querying.
SAP AG
,QIRUPDWLRQ DYDLODEOH IRU DQ\ WLPH IUDPH IRU DGKRF DQDO\VHV DQG UHEXLOGV
5HGXFWLRQ RI KDUGZDUH FRVWV IRU KDUG GULYH KDUGZDUH RQ WKH %: VLGH 0DLQ PHPRU\ DQG &38 DV ZHOO DV FRVWV IRU V\VWHP DGPLQLVWUDWLRQ
4XLFNHU VLPSOHU VRIWZDUH DQG UHOHDVH PDQDJHPHQW LQ %: 5HGXFHG EDFNXS DQG UHFRYHU\ WLPHV ,QWHOOLJHQW GDWD DFFHVV
DBW70E
9-16
Indeed, OHDYLQJ LQIUHTXHQWO\ DFFHVVHG GDWD RQ GLVN VWRUDJH JUHDWO\ +8576 SHUIRUPDQFH. DSS/data warehouse performance is hurt because mixing infrequently used data with actively used data is like adding lots of cholesterol into the blood stream.
,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW IRU 'DWD :DUHKRXVLQJ 0DWFKLQJ 7HFKQRORJ\ WR 5HDOLW\ An Introduction to SAND Searchable Archive By W.H. Inmon Copyright 2005 SAND Technology.
SAP AG 2006
It is important to distinguish between frequently accessed data and infrequently accessed data.
SAP AG
DBW70E
9-17
2QOLQH 'DWDEDVH )UHTXHQWO\ UHDG FKDQJHG GDWD 5DUHO\ UHDG GDWD 9HU\ UDUHO\ UHDG GDWD
1HDU/LQH 6WRUDJH
&ODVVLF $UFKLYH
9 9 9 9 9 9
SAP AG 2006
Think over and categorize your information according to its importance. For each category (frequency of data being read) we can suggest an appropriate storage.
SAP AG
DBW70E
9-18
5HDOL]H
$QDO\]H &DWHJRUL]H
,/0
$SSO\ 3ROLF\
'HWHUPLQH SROLFLHV IRU GDWD FDWHJRULHV DQG OD\HU W\SHV IRU H[DPSOH UHWHQWLRQ SHULRG WLPH VOLFHV IRU GLUHFW DFFHVV
SAP AG
DBW70E
9-19
2QOLQH 0HPRU\
2IIOLQH $UFKLYH
'D\V
0RQWKV <HDUV
&RVWV
SAP AG 2006
We will consider the latest NLS Strategies in SAP NW 2004s. The basic idea is that the access frequency for data decreases over time the older the data gets, the more infrequently used it is. Therefore NLS is aiming to fill the gap between online memory and classical offline archives. It will have direct SQL access, unlike classical offline archives which are not directly accessible. You must decide which are the appropriate device categories for your environment which performance quality do you want to accept?
SAP AG
DBW70E
k k B k g gs k B k k s wD wk
s uuws( lS(
3HUIRUPDQFH 7LPH
9-20
3HUIRUPDQFH &KDUDFWHULVWLFV
3HUIRUPDQFH DQG FRVWRSWLPL]HG PDQDJHPHQW to keep data in multi-layer, transparent storage systems &RPELQHG VWRUDJH V\VWHPV of disk, tape and optical storage media in different variations 'LUHFW URZRULHQWHG GDWD DFFHVV also to compressed archive data using all types of storage media $FFHVV VWUDWHJLHV and DJLQJ SDWWHUQ for logical grouping of data '\QDPLF PLJUDWLRQ on cost-effective storage media for data files with regressive access frequency $XWRPDWHG process for backup, shadowing, mirroring, recovery, etc.
SAP AG 2006
SAP AG
DBW70E
9-21
$'.EDVHG $UFKLYH 'HYHORSPHQW .LW DUFKLYLQJ VROXWLRQ IRU ,QIR&XEHV DQG 2'6 REMHFWV $UFKLYHG GDWD PXVW EH UHORDGHG LQWR WKH 6$3 1HW:HDYHU %, GDWDEDVH IRU DQDO\VLV SXUSRVHV
6$3 1HW:HDYHU %, DQDO\VHV KDYH GLUHFW DFFHVV WR 1/6 GDWD 5HORDGLQJ RI GDWD LQWR WKH ,QIR&XEH RU 'DWD6WRUH 2EMHFW RQO\ QHFHVVDU\ LQ H[FHSWLRQDO FDVHV
SAP AG 2006
In SAP BW 3.x archived data had to be loaded into the BI database for analysis purposes. Note the red curve access frequency is at zerpo when in the archive. In the future data will always be accessible if it is in Online database or if in NLS. Consider the curve. Costs for storing historic data can be reduced. There is a physical decoupling of frequently and not so frequently accessed data.
SAP AG
DBW70E
wYb sH
Du"
9-22
u s9 w D
l s Dw DwywswD swww D D
SAP AG 2006
Frequently used data remains in the database. Rarely used data is brought to the NLS devices. In the slide above non-archived means data in the database. Archived is used here to mean in NLS. Intelligent data acess the data manager of BI must know where the data resides. The mentioned partners will certify their products against our NLS interface
SAP AG
3%6 6RIWZDUH &%: )LOH7HN 6WRU+RXVH 2XWHU%D\ /LYH$UFKLYH 6$1'7HFKQRORJLHV 6HDUFKDEOH $UFKLYH
DBW70E
9-23
'DWD 0DQDJHPHQW
+LJK/HYHO ,QGH[
This is the entire story on NLS. The main feature of the NLS interface is that data archiving processes or data transfer processes can be defined to bring data from the BI database to teh NLS environment - or vice-versa. The data archiving process has split the data volume of the cube into two parts. If you run a query on it the data manager has to decide if the data that your query wants to see resides on the database or in the NLS environment. The high-level index is very important in this context. It works transparently as far as the user is concerned. Overall we reduce data volumes but we do not lose data accessibility.
SAP AG
DBW70E
YbS$Qb FSdhWPPS
D gWWB YDlgS
g SPsdW B
2QOLQH '%
SAP AG 2006
$UFKLYH
For both types of InfoProvider you define a data archiving process process steps that can be scheduled and be part of a process chain. You can choose an archive type. Which data is defined via the selection schema. When it is defined archive via this data archiving process using the process chain. Then when you run a query on the cube you can choose additional query properties ie Nearline Storage Should Be Read As Well . You should know that data in this cube has been archived and you must switch this flag on.
SAP AG
DBW70E
$UFKLWHFWXUDO 2YHUYLHZ
Legend
Information Consumer R
3rd party
Data Retrieval Manager R R Archive Partition Manager R R Data Relocation Manager R Near-Line Storage Interface (internal) R R Near-Line Adapter (internal) any R Near-Line Adapter (external) Web Service Archive Partition Info
BW Data Manager
InfoCubes/ DS Objects
Archive/ Restore
System Administrator
Archive Files
Archive Documents
Near-Line Data
Near-Line Data
SAP AG 2006
We see the NLS Interface on right. There are two technical realizations for that the partner solution could be ABAP based. Web services should also be available . We see also there is a connection to SAP ADK. Bringing an ADK file to NLS will involve a compression mechanism. Special indices will be built up so that the SQL access can then be managed.
SAP AG
DBW70E
9-26
GLIIHUHQW QHDUOLQH VWRUDJH OHYHOV KDYH WR IXOILOO WUDQVDFWLRQDO UHTXLUHPHQWV ZLWK UHJDUG WR PDLQWDLQJ FRQVLVWHQF\
$UFKLYLQJ DQG GHOHWLRQ RI GDWD LQ WKH RQOLQH GDWDEDVH IRUP D ORJLFDO XQLW RI ZRUN /8:
The processes are very complex. Archiving and deletion from the database must run in one LUW. We do not want to have duplicate data hence need for roll-back.
SAP AG
DBW70E
Bsw s w
7KH DUFKLYH JHWV WKH FKDUDFWHU RI D GDWDEDVH 7KH DUFKLYH GDWD DUH XVXDOO\ UHDG RQO\
9-27
5HDOL]H
$QDO\]H &DWHJRUL]H
,/0
$SSO\ 3ROLF\
'HWHUPLQH SROLFLHV IRU GDWD FDWHJRULHV DQG OD\HU W\SHV HJ UHWHQWLRQ SHULRG WLPH VOLFHV IRU GLUHFW DFFHVV
$SSO\ SROLFLHV WR OD\HU W\SHV DQG GDWD FDWHJRULHV GHILQLQJ 'DWD $UFKLYH 3URFHVVHV SHU &XEH RU 'DWD6WRUH 2EMHFW
SAP AG 2006
Now we know what a data archiving process is we can apply the policy. When implemented we know how to realize ie then connect BI to the partner system and schedule/monitor the data archiving processes.
SAP AG
DBW70E
9-28
SAP AG 2006
We will now consider archiving scenarios. Now the PSA is only to guarantee load quality the first persistent data layer is the EDW layer.It is the historical foundation for remodeling and reloading.
SAP AG
1(
1
'DWD 0LQLQJ %XVLQHVV 3ODQQLQJ 6WUDWHJLF $QDO\VLV 2SHUDWLRQDO 5HSRUWLQJ (': /D\HU 7\SLFDOO\ EXLOW ZLWK 2'6 2EMHFWV /DUJH GDWD YROXPHV WR EH H[SHFWHG $GKRF UHSRUWLQJ RQO\ IRU IHZ XVHUV XVXDOO\ QR 5HSRUWLQJ +LVWRULFDO IRXQGDWLRQ LQ FDVH RI UHPRGHOLQJ DQG UHORDGLQJ )LUVW SHUVLVWHQW GDWD OD\HU LQ 6$3 1HW:HDYHU %, ZLWK DUFKLYH RSWLRQ LQVWHDG RI 36$ (': OD\HU UHSUHVHQWV LQWHJUDWHG GDWD ([WUDFWV 5HODWLRQVKLSV (QWLWLHV
DBW70E 9-29
3 '&C
2 #D ( &@ ) C B A 2 60 864 ) ' & 864 '&% 'g$l9" 87& suww bHWs wuk
ss wws4uY u b
SAP AG
SAP AG 2006
36$ /D\HU
1/6 $UFKLYH
1/6 $UFKLYH
DBW70E
1/6 $UFKLYH
9-30
How to define the data archiving process? The above slide shows the step to initiate it.
SAP AG
DBW70E
9-31
SAP AG 2006
How to define the query properties? As mentioned in an earlier slide this is a flag to set in the Query Properties.
SAP AG
DBW70E
9-32
SAP AG 2006
Here are the query properties provided by transaction RSRV note the flag Nearline Storage Should Be Read As Well .
SAP AG
DBW70E
9-33
SAP AG 2006
How can I load it to a Cube? Here we see the definition of a DTP. If parts of the data reside in an NLS environment and we want to take that data with the DTP as well, we define an Extraction mode Full with NLS. So that data is available for data load processes.
SAP AG
DBW70E
9dQSDS
H
'DWD 7UDQVIHU 3URFHVV 8SGDWH 'DWD6WRUH REMHFW LQWR 'DWD 7DUJHWV ,QFOXGH 1/6$UFKLYHV
g BW
G
WSD
9-34
SAP AG 2006
Looking at the other persistent BI layers (analysis horizons) above the EDW layer we may be working with high-volume data sets. The three layers then are also candidates for ILM strategy resulting in a connection to NLS.
SAP AG
1(
1
'DWD 0LQLQJ %XVLQHVV 3ODQQLQJ 6WUDWHJLF $QDO\VLV 2SHUDWLRQDO 5HSRUWLQJ (': /D\HU 3HUVLVWHQW %, DQDO\VLV KRUL]RQ +LJK YROXPH GDWDVHWV 'LUHFW DYDLODELOLW\ GHVLUHG 'DWD DUFKLYLQJ SURFHVV UHTXLUHG ([WUDFWV 5HODWLRQVKLSV (QWLWLHV
DBW70E 9-35
So far we have given a recommendation to use MultiProviders. To use them efficiently we may have said as here - use 4 InfoCubes eg one cube holding data for a year. This is a form of logical partitioning. The oldest data (one on left shown here) could be a candidate for archive.
SAP AG
DBW70E
T W9 d9 b 9 DY h99 H b SP R b9TbD 9SWWb H b YdgSd W Q 9Sds k9 gY Y H Ph9d WBS H P
9-36
'HGLFDWHG TXHU\ VSOLW IRU DUFKLYHUHODWHG GDWD SRUWLRQ DV ZHOO &HQWUDO LQWHUIDFH IRU TXHU\LQJ HYHQ LI XQGHUO\LQJ GDWD PRGHOV FKDQJH
%HWWHU SHUIRUPDQFH LQ DGPLQLVWUDWLRQ RQ EDVLF ,QIR3URYLGHUV ,Q PRVW FDVHV TXHULHV DUH VSOLW DXWRPDWLFDOO\ DQG GLVWULEXWHG WR ,QIR3URYLGHUV IRU PRUH GHWDLOV RQ SDUDOOHO H[HFXWLRQ VHH 6$3 6HUYLFH 0DUNHWSODFH 1RWH
'LVDGYDQWDJHV
&KDQJHV WR WUDQVIRUPDWLRQ UXOHV KDYH WR EH GRQH PDQ\ WLPHV 5HPRGHOLQJ DW \HDU HQG QHZ FXEH IRU WKH QHZ \HDU 1HZ SURFHVV GHVLJQ DW \HDU HQG XQORDG QHZ DUFKLYH REMHFW
SAP AG 2006
SAP AG
DBW70E
9-37
<HDU &KDQJH $UFKLYH 'DWD $UFKLYLQJ 3URFHVV $UFKLYH 7\SH 1HDUOLQH VWRUDJH 6HOHFWLRQ 6FKHPD 7LPH VOLFHV $UFKLYH
6FKHGXOH -DQXDU\
SAP AG 2006
So how might it look in SAP NW 2004s We could have more data in one cube
Via data archiving , and a NLS, everything older than 3 years is brought to NLS device at year end Therefore schedule this archiving every 1 Jan and everything older than 2 years is written to an archive Automatically the data for the new year is populated into the cube Data for three years in one cube should not be a problem with BI Accelerator Thus this could be a replacement for the logical partitioning working with MultiProviders as suggested previously.
SAP AG
DBW70E
9-38
600.00
500.00
400.00
300.00
200.00
Without Archiving
First Archiving
100.00
DB Growth: ~7 GB/Month
01.02.2003
01.03.2003
01.05.2003
SAP AG 2006
Have a look at your data growth. Your data volumes may be projected similar to those in the graph.
SAP AG
DBW70E
01.01.2003
01.04.2003
01.06.2003
01.07.2003
01.08.2003
01.09.2003
0.00
9-39
'RQW VWDUW WKLQNLQJ DERXW GDWD DUFKLYLQJ ZKHQ \RXU V\VWHP LV DERXW WR FUDVK
SAP AG 2006
7LPHO\ 3ODQQLQJ
'DWD DUFKLYLQJ UHTXLUHV D ODUJH DPRXQW RI FRRUGLQDWLRQ EHWZHHQ ,7 DQG WKRVH UHVSRQVLEOH IRU DSSOLFDWLRQV
,QWHUGLVFLSOLQDU\ 3URFHVV
SAP AG
DBW70E
9-40
5HDOL]H
$QDO\]H &DWHJRUL]H
,/0
$SSO\ 3ROLF\
'HWHUPLQH SROLFLHV IRU GDWD FDWHJRULHV DQG OD\HU W\SHV HJ UHWHQWLRQ SHULRG WLPH VOLFHV IRU GLUHFW DFFHVV
SAP AG 2006
As a summary these are the steps as to how we can achieve increasing volumes, more effective use of resources, increase of availability and performance optimization with the help of an Information Lifecycle Management strategy.
SAP AG
$SSO\ SROLFLHV WR OD\HU W\SHV DQG GDWD FDWHJRULHV GHILQLQJ 'DWD $UFKLYH 3URFHVVHV SHU &XEH RU 'DWD6WRUH 2EMHFW
DBW70E
9-41
1HDU /LQH 6WRUDJH ZLWKLQ WKH 6$3 &RQFHSW RI ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW /HVVRQ 6XPPDU\
'HVFULEH WKH FKDOOHQJHV IDFLQJ WKH LQIRUPDWLRQ OLIHF\FOH /LVW EHQHILWV IRU DQ ,/0 VWUDWHJ\ IRU %,
([SODLQ WKH ODWHVW (QWHUSULVH 'DWD :DUHKRXVLQJ 1HDU /LQH 6WRUDJH VWUDWHJLHV IRU SHUIRUPDQFH RSWLPL]DWLRQ DURXQG GDWD YROXPH PDQDJHPHQW 'HVFULEH D SRVVLEOH DUFKLYLQJ VFHQDULR LQ %,
SAP AG 2006
SAP AG
DBW70E
9-42
'HVFULEH WKH FKDOOHQJHV IDFLQJ WKH LQIRUPDWLRQ OLIHF\FOH /LVW EHQHILWV IRU DQ ,/0 VWUDWHJ\ IRU %,
([SODLQ WKH ODWHVW (QWHUSULVH 'DWD :DUHKRXVLQJ 1HDU /LQH 6WRUDJH VWUDWHJLHV IRU SHUIRUPDQFH RSWLPL]DWLRQ DURXQG GDWD YROXPH PDQDJHPHQW 'HVFULEH D SRVVLEOH DUFKLYLQJ VFHQDULR LQ %,
SAP AG 2006
SAP AG
DBW70E
9-43
SAP AG
DBW70E
9-44
&RQFOXVLRQ
3UHIDFH ,QWURGXFWLRQ WR WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ LQ 6$3 1HW:HDYHU V 'DWD 0RGHOLQJ 'DWD $FTXLVLWLRQ 7UDQVIRUPDWLRQ DQG 8QLW RI 0HDVXUH &RQYHUVLRQ 'DWD )ORZ &RQWURO $GPLQLVWUDWLRQ DQG 0RQLWRULQJ 3HUIRUPDQFH 2SWLPL]DWLRQ ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW
SAP AG 2006
SAP AG
DBW70E
10-1
&RXUVH 6XPPDU\
([SODLQ WKH ,7 6FHQDULR (QWHUSULVH 'DWD :DUHKRXVLQJ ZLWKLQ 6$3 1: V ([SODLQ WKH PDLQ PRGHOLQJ DVSHFWV RI WKH (QWHUSULVH 'DWD :DUHKRXVH *LYH DQ RYHUYLHZ RI WKH PRVW LPSRUWDQW UXQWLPH DQG DGPLQLVWUDWLYH DVSHFWV RI WKH (QWHUSULVH 'DWD :DUHKRXVH ([SODLQ WKH XVHU LQWHUIDFH RI WKH 'DWD :DUHKRXVLQJ :RUNEHQFKRI 6$3 1: V ([SODLQ WKH FRQFHSW RI 'DWD6WRUH 2EMHFWV ZKLFK ZLOO UHSODFH 2'6 2EMHFWV LQ 6$3 1HW:HDYHU V ([SODLQ WKH HQKDQFHG ,QIR6HW IHDWXUHV
SAP AG 2006
SAP AG
DBW70E
10-2
&RXUVH 6XPPDU\
([SODLQ WKH PDLQ EHQHILWV RI WKH %XVLQHVV FRQWHQW RIIHULQJ ZLWKLQ 6$3 1HW:HDYHU V
'HVFULEH KRZ WR LPSOHPHQW D GDWDEDVH FRQQHFWLRQ IURP DQ 6$3 1HW:HDYHU V %, V\VWHP WR D UHODWLRQDO GDWDEDVH YLD '% &RQQHFW GDWD VRXUFH
([SODLQ WKH PRVW LPSRUWDQW DVSHFWV RI WKH 'DWD 6RXUFH FRQFHSW RI 6$3 1: V
SAP AG 2006
SAP AG
'HVFULEH WKH ORRN DQG IHHO RI :HE 6HUYLFHV ZLWKLQ 6$3 1: V ([SODLQ 8QLW RI 0HDVXUH FRQYHUVLRQ
DBW70E
10-3
&RXUVH 6XPPDU\
([SODLQ WKH HUURU KDQGOLQJ IHDWXUHV LQ WKH 'DWD 7UDQVIHU 3URFHVV RI 6$3 1: V
([SODLQ WKH SURFHVV FKDLQ IHDWXUHV RI 6$3 1: V ([SODLQ WKH GLUHFW GDWD DFFHVV FDSDELOLWLHV ([SODLQ WKH FRQFHSW RI 5HDO 7LPH 'DWD $FTXLVLWLRQ ZLWKLQ 6$3 1: V
SAP AG 2006
SAP AG
([SODLQ WKH FRQFHSW RI WKH %, $FFHOHUDWRU ZLWKLQ 6$3 1: V ([SODLQ WKH ODWHVW (QWHUSULVH 'DWD :DUHKRXVLQJ 1HDU /LQH 6WRUDJH VWUDWHJLHV IRU ,QIRUPDWLRQ /LIHF\FOH 0DQDJHPHQW ([SODLQ GHWDLOV DURXQG SHUIRUPDQFH RSWLPL]DWLRQ
DBW70E
10-4
*R WKURXJK WKH H[HUFLVHV XVLQJ ,'(6 GDWD RU \RXU RZQ GDWD 5HDG WKH RQOLQH GRFXPHQWDWLRQ 5HDG WKH ,PSOHPHQWDWLRQ *XLGH ,0*
SAP AG 2006
SAP AG
DBW70E
10-5
SAP AG
DBW70E
10-6
$SSHQGL[
SAP AG 2006
In this Appendix what the check programs do is explained, as well as what are the reasons for inconsistencies in InfoObjects. If you encounter errors via the Business Content Analyzer you may look into this appendix to get the detailed information.
SAP AG
DBW70E
11-1
SAP AG 2006
SAP AG
DBW70E
11-2
SAP AG 2006
SAP AG
DBW70E
11-3
6$' $YHUVLRQ QHZHU WKDQ 'YHUVLRQ 6'$ 'YHUVLRQ QHZHU WKDQ $YHUVLRQ 61$ 1R $YHUVLRQ DYDLODEOH
7KH VWDWXV FKHFNV FRPSDUHV WKH FRQWHQW WLPH VWDPS RI WKH $ DQG 'YHUVLRQ RI D %XVLQHVV &RQWHQW REMHFW 7KH FRQWHQW WLPH VWDPS LV DVVLJQHG WR HYHU\ %, REMHFW 7KH FRQWHQW WLPH VWDPS ZLOO EH FUHDWHG LI DQ REMHFW KDV EHHQ DFWLYDWHGVDYHG LQ D %, &RQWHQW 'HYHORSPHQW V\VWHP 7KH FRQWHQW WLPH VWDPS FDQ EH FKDQJHG LI DQ REMHFW KDV EHHQ FKDQJHG LQ D %, &RQWHQW 'HYHORSPHQW V\VWHP
SAP AG
DBW70E
11-4
'HYHORSHU GRHV QRW VHH WKH REMHFW YHUVLRQ ZKLFK ZLOO EH GHOLYHUHG
5HDVRQ 7KH 'YHUVLRQV DUH QRW VDYHG FRUUHFWO\ 0D\EH LQFRUUHFW V\VWHP VHWWLQJV
SAP AG
DBW70E
11-5
6WDWXV &KHFNV
$ QHZHU YHUVLRQ RI WKH REMHFW LV DYDLODEOH LQ WKH 'YHUVLRQ 3RVVLEOH UHDVRQV 7KH FRQWHQW LQVWDOODWLRQ IDLOHG 7KH FRQWHQW LQVWDOODWLRQ GLG QRW KDSSHQ XS WR QRZ 8QH[SHFWHG LPSRUWV WR WKH V\VWHP
SAP AG 2006
SAP AG
DBW70E
11-6
SAP AG 2006
SAP AG
DBW70E
11-7
7KH FROOHFWLRQ FKHFN LV D VLPXODWLRQ RI WKH REMHFW FROOHFWLRQ ZKLFK FDQ EH VWDUWHG E\ XVLQJ WUDQVDFWLRQ 5625 7KH LQWHQWLRQ LV WR LGHQWLI\ REMHFWV ZLWK UHIHUHQFHV WR PLVVLQJ RU ORFDOO\ VWRUHG REMHFWV
SAP AG
DBW70E
11-8
1RQH[LVWLQJ 2EMHFWV
SAP AG 2006
SAP AG
11-9
,QIR3URYLGHU
SAP AG 2006
SAP AG
DBW70E
11-10
2WKHU &KHFNV
,QDFWLYH 7UDQVIHU 6WUXFWXUH
QRW YDOLG LI WKH FRQWHQW LV EDVHG RQ %, WHFKQRORJ\ ,QIR2EMHFW ZLWKRXW ,QIR2EMHFW &DWDORJ 1DPLQJ &RQYHQWLRQ ,JQRUHG 4XHU\ (OHPHQWV ZLWK GRXEOH *8,'V 5ROHV KDYLQJ QRQH[LVWLQJ REMHFWV DVVLJQHG WR LW 5RXWLQHV ZLWK UHIHUHQFHV WR %: '',& VWUXFWXUHV
SAP AG 2006
SAP AG
DBW70E
11-11
SAP AG 2006
SAP AG
DBW70E
11-12
SAP AG 2006
SAP AG
DBW70E
11-13
SAP AG 2006
SAP AG
DBW70E
11-14
4XHU\ (OHPHQW
6\VWHP $
6\VWHP %
4XHU\ H[HFXWLRQ FKRRVHV WKH REMHFWV DW UDQGRP 123456789 or 987654321 /HDGV WR LQFRQVLVWHQFLHV LI TXHU\ GHILQLWLRQ FKDQJHV
SAP AG 2006
SAP AG
DBW70E
11-15
5ROHV +DYLQJ 1RQH[LVWHQW 2EMHFWV $VVLJQHG 7R 7KHP 4XHULHV 9LHZV RU 7HPSODWHV FDQ EH DVVLJQHG WR D UROH ,I REMHFW LWVHOI ZDV GHOHWHG EXW WKH DVVLJQPHQW WR WKH UROH ZDV QRW GHOHWHG WKLV OHDGV WR LQFRQVLVWHQFLHV 5HDVRQ 'HOHWLRQ RI REMHFWV 3UREOHP ,QFRQVLVWHQW REMHFW VWDWXV &ROOHFWLRQ HUURUV DUH SRVVLEOH 6ROXWLRQ 'HOHWH WKH DVVLJQPHQW WR WKH UROH GHILQLWLRQ LQ WUDQVDFWLRQ 3)&*
SAP AG 2006
SAP AG
DBW70E
11-16
3UREOHP Activation problems, if the routine is activated before the referenced object is activated. For A-version, importing problems if the referenced object is not available in the system.
SAP AG 2006
SAP AG
DBW70E
11-17
SAP AG 2006
SAP AG
DBW70E
11-18
$SSHQGL[
SAP AG 2006
SAP AG
DBW70E
12-1
SAP AG
DBW70E
12-2
0DVWHU 'DWD 6WDJLQJ RI &RQYHUVLRQ 'HWDLOV &RQYHUVLRQ )DFWRUV 6SHFLI\LQJ 6RXUFH7DUJHW 8R0V ([DPSOHV )L[HG 7DUJHW ([DPSOHV 5HIHUHQFH ,QIR2EMHFW
SAP AG
DBW70E
12-3
8QLWV RI 0HDVXUH &RQYHUVLRQ LQ ,QIR2EMHFW 0DVWHU 'DWD 0DVWHU 'DWD FDQ EH XVHG WR VSHFLI\ 8R0UHOHYDQW GHWDLOV IRU WKDW VSHFLILF &KDUDFWHULVWLF 0DVWHU 'DWD FDQ QRZ VSHFLI\
%DVH 820
SAP AG 2006
SAP AG
7KLV LV WKH UHIHUHQFH FKDUDFWHULVWLF IRU 8R0V 0XVW EH GHILQHG DV DQ DWWULEXWH RI WKH FKDUDFWHULVWLF
$Q\ ,QIR2EMHFW RI W\SH 81,7 FDQ EH XVHG ,QIR2EMHFW %$6(B8R0 GHOLYHUHG ZLWK %XVLQHVV &RQWHQW
DBW70E
12-4
SAP AG 2006
SAP AG
DBW70E
12-5
IRU FKDUDFWHULVWLF &KDUDFWHULVWLF FDQ KDYH RQH DQG RQO\ RQH 8R0 FRQYHUVLRQ 'DWD6WRUH REMHFW &RQYHUVLRQ 'DWD6WRUH REMHFW FDQQRW EH PRGLILHG YLD 'DWD6WRUH REMHFW PDLQWHQDQFH 'DWD6RXUFH 7UDQVIRUPDWLRQ ,QIR3DFNDJH DQG '73 PXVW EH PDLQWDLQHG PDQXDOO\ &KDQJHV WR FRQYHUVLRQ FRQILJXUDWLRQ
&RPSRXQGLQJ RI NH\V FKDQJH RI WKH EDVH XQLW RI PHDVXUH RU RWKHU VWUXFWXUDO FKDQJHV WR WKH 'DWD6WRUH 2EMHFW UHTXLUH GHOHWHUHFUHDWH RI WKH 'DWD6WRUH 2EMHFW VXSSRUWLQJ WKH FKDUDFWHULVWLF *HQHUDOO\ D UDUH RFFXUUHQFH
SAP AG 2006
SAP AG
DBW70E
12-6
8R0 'DWD6WRUH 2EMHFW FDQ EH YLHZHG LQ 'LVSOD\ PRGH WKURXJK VWDQGDUG 'DWD6WRUH 2EMHFW PDLQWHQDQFH VFUHHQ
SAP AG 2006
SAP AG
DBW70E
12-7
.* NLORJUDPV
$VVXPHV WKDW 81,7 LV WKH 8R0 IRU WKH DVVRFLDWHG .H\ )LJXUH IURP VRXUFH
SAP AG 2006
SAP AG
DBW70E
12-8
0$7(5,$/
8200$7(
1HZ 5659 FKHFNV DUH DYDLODEOH WR GHWHUPLQH FRQVLVWHQF\ RI GDWD LQ 8R0 'DWD6WRUH 2EMHFW DV FRPSDUHG WR WKH FXUUHQW PDVWHU GDWD ORDGHG IRU WKH DVVRFLDWHG FKDUDFWHULVWLF
SAP AG 2006
SAP AG
DBW70E
12-9
SAP AG
DBW70E
12-10
0DVWHU 'DWD 6WDJLQJ RI &RQYHUVLRQ 'HWDLOV &RQYHUVLRQ )DFWRUV 6SHFLI\LQJ 6RXUFH7DUJHW 8R0V ([DPSOHV )L[HG 7DUJHW ([DPSOHV 5HIHUHQFH ,QIR2EMHFW
SAP AG
DBW70E
12-11
5HIHUHQFH ,QIR2EMHFW 'DWD6WRUH 2EMHFW &HQWUDO 8QLWV 7 )DFWRU LQ VRXUFH &RQYHUVLRQ )DFWRUV
&RQYHUVLRQ 7\SH
&RQYHUVLRQ
SAP AG
DBW70E
12-12
SAP AG 2006
SAP AG
DBW70E
12-13
&RQYHUVLRQ )DFWRUV
7ZR RYHUDOO FKRLFHV LPSDFW WKH FRQYHUVLRQ
&RQYHUVLRQ )DFWRUV
SAP AG 2006
SAP AG
'\QDPLF FRQYHUVLRQ OHYHUDJHV WKH 8R0 'DWD6WRUH 2EMHFW FRQYHUVLRQ UDWHV GHVFULEHG SUHYLRXVO\ $Q DGGLWLRQDO NH\ ILJXUH ,QIR2EMHFW LV RQH ILHOG RI WKH VRXUFH URZV ,I &RQYHUVLRQ )DFWRU IURP ,QIR2EMHFW LV FKRVHQ WKLV NH\ ILJXUH LV WKH FRQYHUVLRQ IDFWRU WKDW ZLOO EH DSSOLHG IRU WKH 8R0 FRQYHUVLRQ
DBW70E
12-14
&0$7
4711
&)$.725
0.025
&)$.725)
1.7
&.<)
12 BOX
&.<)
?
$VVXPLQJ
&$8)15
1
SAP AG 2006
SAP AG
&0$7
4711
&)$.725
0.025
&)$.725)
1.7
&.<)
12 BOX
DBW70E
12-15
4711
&RQYHUVLRQ W\SH <xyz> &RQYHUVLRQ IDFWRUV from InfoObject C2FAKTORF 6RXUFH XQLW unit from data record 7DUJHW XQLW fixed unit: PAL
SAP AG 2006
SAP AG
DBW70E
12-16
$OORZV IRU GHWHUPLQDWLRQ WR FRPH IURP HLWKHU DQ ,QIR2EMHFW DQG WKH OLQNHG 8R0 'DWD6WRUH 2EMHFW RU WDEOH 7 RU ERWK ,I ERWK WKHQ RUGHU RI RSHUDWLRQV LV VHW DQG IDLOLQJ WR ILQG LW LQ WKH LQLWLDO VRXUFH WKH V\VWHP ZLOO VHHN WKH DOWHUQDWH VRXUFH IRU ILQDO GHWHUPLQDWLRQ 1RWH WKDW 7EDVHG FRQYHUVLRQV ZLOO QRW DOORZ FURVV GLPHQVLRQDO FDOFXODWLRQV IRU LQVWDQFH SLHFHV WR JUDPV RU ER[HV WR FXELF PHWHUV
SAP AG 2006
SAP AG
DBW70E
12-17
SAP AG 2006
SAP AG
7$ 7%
77 ,0* 6$3 1HW:HDYHU ! *HQHUDO 6HWWLQJV ! &KHFN 8QLWV RI 0HDVXUH 7UDQVDFWLRQ &81,
DBW70E
12-18
)URP 'DWD6RXUFH 0DLQWHQDQFH 8R0 LQIRUPDWLRQ FDQ EH WUDQVIHUUHG IURP VRXUFH V\VWHPV
SAP AG 2006
SAP AG
DBW70E
12-19
;<=
;<=
($
$$
($
&0
SLHFH JUDPV SLHFHV ILW LQ D ER[ HWF FP RI PDWHULDO $$ PHWHU QRWH WKDW WKLV LV D VSHFLDO FRQYHUVLRQ SXUSRVHO\ SODFHG LQ 0DVWHU 'DWD
SAP AG
FP
DBW70E
12-20
SAP AG
DBW70E
12-21
4711
&RQYHUVLRQ W\SH <xyz> &RQYHUVLRQ IDFWRUV determined dynamically via InfoObject: CMAT07, factors looked up solely in referenced InfoObject 6RXUFH XQLW unit from data record 7DUJHW XQLW fixed unit: PC &$8)15 &0$7 &)$.725 &)$.725) &.<) &.<)
1
SAP AG 2006
4711
0,025
1,7
18 PAL
? 172800 PC
(18 * 9600)
SAP AG
DBW70E
12-22
4711
&RQYHUVLRQ W\SH <xyz> &RQYHUVLRQ IDFWRUV factors looked up solely in central measurements (T006) 6RXUFH XQLW unit from data record 7DUJHW XQLW fixed unit: PC &$8)15 &0$7 &)$.725 &)$.725) &.<) &.<)
1
SAP AG 2006
4711
0,025
1,7
18 PAL
? conversion possible No
SAP AG
DBW70E
12-23
SAP AG
DBW70E
12-24
0DVWHU 'DWD 6WDJLQJ RI &RQYHUVLRQ 'HWDLOV &RQYHUVLRQ )DFWRUV 6SHFLI\LQJ 6RXUFH7DUJHW 8R0V ([DPSOHV )L[HG 7DUJHW ([DPSOHV 5HIHUHQFH ,QIR2EMHFW
SAP AG
DBW70E
12-25
SAP AG 2006
SAP AG
DBW70E
12-26
8R0 IURP 'DWD5HFRUG ZLOO EH WKH RSWLRQ VHOHFWHG LQ PRVW XVH FDVHV $Q\ RWKHU VHWWLQJ LQ WKLV VHFWLRQ HIIHFWLYHO\ RYHUULGHV DQ\ 8R0V FRPLQJ IURP WKH VRXUFH GDWD )RU )L[HG 8QLW RI 0HDVXUH
7KH YDOXHV VSHFLILHG LQ WKH LQSXW KHOS FRUUHVSRQG WR WKH YDOXHV LQ WDEOH 7 XQLWV RI PHDVXUH <RX PXVW VHOHFW D YDULDEOH FUHDWHG IRU ,QIR2EMHFW 81,7
SAP AG 2006
SAP AG
DBW70E
12-27
`83H3$#HH$#`DE 0B&@VV C # 6 F # 6 i 6 F P F 6 P% 6 F P x ' v C 6 I2 A E E 6 4 '2 i # P 2 6 R # ' 4 6 rC P F 6 E 1 x ' v 6 42 1 ' E 6 rC C E 1s 6 rC P P rC C A rC 6C ' p 8835VY' EV8&H`G$#h&yVwD85VSuH`V&&ctHfGE DE S`8H`q@SX" I P 2 ' i 2 I P2 1 F # P 2 6 R # ' 4 6 P a # 12 A 2 '% F 6 E 1 2 6 P R '2 U '% ! g#(TCVT6hg#f3' 3TEH8e$dcbCH3`Y5HH&XWFV5B(&$#" # P 2 6 R # ' 4 I P I AC E A 2 '% F 6 E 1 6 42 1 ' ) AC A 97 6 42 1 ' ) '% ! ' 3TE3S8&Q$#&@HG5&D&530&5&B@8&530(&$#"
SAP AG
SAP AG 2006
,QIR2EMHFW &0$7 DQG LWV DWWULEXWH $32B6725*8 DUH VHW DV WKH ,QIR2EMHFW IRU 8R0
'XULQJ FRQYHUVLRQ PDVWHU GDWD LV UHDG IRU D PDWFKLQJ NH\ 0DWHULDO 1XPEHU
4711
&0$7
PC
PAL
DBW70E
12-28
)RUFHV D UXQWLPH VHOHFWLRQ RI WKH WDUJHW 8R0 &RXOG \LHOG XQUHSRUWDEOH UHVXOWV LI WKH UHODWLRQVKLS RI VRXUFH XQLW WR WDUJHW XQLW LV QRW PDLQWDLQHG 1RW DYDLODEOH IRU VWDJHG FRQYHUVLRQV
SAP AG 2006
SAP AG
DBW70E
12-29
SAP AG
DBW70E
12-30
8R0 &RQYHUVLRQ 7\SH 7DUJHW IURP 9DULDEOH RU ,QIR2EMHFW 7DUJHW 4XDQWLW\ IURP 9DULDEOH
<RX PXVW VHOHFW D YDULDEOH FUHDWHG IRU ,QIR2EMHFW 81,7 'XULQJ FRQYHUVLRQ PDVWHU GDWD LV UHDG IRU D PDWFKLQJ NH\ 7KH 8R0 RI WKH DWWULEXWH LV DSSOLHG WR DOO RXWSXW UHFRUGV
SAP AG 2006
SAP AG
7KH ,QIR2EMHFW VHOHFWHG PXVW EH SUHVHQW GXULQJ WKH VWDJLQJ SURFHVV RU LQ WKH ,QIR3URYLGHU IRU UXQWLPH FRQYHUVLRQV
DBW70E
12-31
7DEOH)LHOG $OLDV ILHOGV DUH QHFHVVDU\ ZKHQ DQ ,QIR2EMHFW RU )LHOG DSSHDUV PXOWLSOH WLPHV LQ D JLYHQ ,QIR6HW 7KH $OLDV FDQ EH VSHFLILHG LQ RUGHU WR VHOHFW WKH GHVLUHG LQVWDQFH RI WKH ,QIR2EMHFW)LHOG
SAP AG 2006
SAP AG
DBW70E
12-32
0DVWHU 'DWD 6WDJLQJ RI &RQYHUVLRQ 'HWDLOV &RQYHUVLRQ )DFWRUV 6SHFLI\LQJ 6RXUFH7DUJHW 8R0V ([DPSOHV )L[HG 7DUJHW ([DPSOHV 5HIHUHQFH ,QIR2EMHFW
SAP AG
DBW70E
12-33
4711
&RQYHUVLRQ W\SH <xyz> &RQYHUVLRQ IDFWRUV determined dynamically via InfoObject: CMAT07 6RXUFH XQLW unit from data record 7DUJHW XQLW fixed unit: PC
SAP AG 2006
SAP AG
DBW70E
12-34
4711
&RQYHUVLRQ W\SH <xyz> &RQYHUVLRQ IDFWRUV determined dynamically via InfoObject: CMAT07 6RXUFH XQLW unit from data record 7DUJHW XQLW fixed unit: CS
SAP AG 2006
SAP AG
DBW70E
12-35
4711
&RQYHUVLRQ W\SH <xyz> &RQYHUVLRQ IDFWRUV determined dynamically via InfoObject: CMAT07 6RXUFH XQLW unit from data record 7DUJHW XQLW fixed unit: PAL
SAP AG 2006
SAP AG
DBW70E
12-36
0DVWHU 'DWD 6WDJLQJ RI &RQYHUVLRQ 'HWDLOV &RQYHUVLRQ )DFWRUV 6SHFLI\LQJ 6RXUFH7DUJHW 8R0V ([DPSOHV )L[HG 7DUJHW ([DPSOHV 5HIHUHQFH ,QIR2EMHFW
SAP AG
DBW70E
12-37
4711
7LHU [
7LHU
3&
3$/
&RQYHUVLRQ W\SH <xyz> &RQYHUVLRQ IDFWRUV determined dynamically via InfoObject: CMAT07 6RXUFH XQLW unit from data record 7DUJHW XQLW using InfoObject CRUOM1, associated attribut 0SALES_UNIT
SAP AG 2006
SAP AG
DBW70E
12-38
4711
7LHU [
7LHU [
3&
*
&RQYHUVLRQ W\SH <xyz> &RQYHUVLRQ IDFWRUV determined dynamically via InfoObject: CMAT07 6RXUFH XQLW unit from data record 7DUJHW XQLW using InfoObject CRUOM1, associated attribut 0UNIT
SAP AG 2006
SAP AG
DBW70E
12-39
4711
7LHU [
3&
&RQYHUVLRQ W\SH <xyz> &RQYHUVLRQ IDFWRUV determined dynamically via InfoObject: CMAT07 6RXUFH XQLW unit from data record 7DUJHW XQLW using InfoObject CRUOM1, associated attribut 0UNIT
SAP AG 2006
SAP AG
DBW70E
12-40
4711
&RQYHUVLRQ W\SH <xyz> &RQYHUVLRQ IDFWRUV determined dynamically via InfoObject: CMAT07 6RXUFH XQLW unit from data record 7DUJHW XQLW using InfoObject CRUOM1, associated attribut 0UNIT
SAP AG 2006
SAP AG
DBW70E
12-41
,Q WKLV H[DPSOH ZH FRXOG DGG &RXQWU\ WR WKH 8R0 'DWD6WRUH 2EMHFW %DVHG RQ WKH VRXUFH 0DWHULDO &RXQWU\ DQG 8QLW WKH FRUUHFW WDUJHW FRQYHUVLRQ FRXOG EH GHWHUPLQHG
&28175<
DE US
&0$7
4711 4711
SAP AG 2006
SAP AG
KG LB
820='
1 1
8201'
10 22
DBW70E
12-42
0DVWHU 'DWD 6WDJLQJ RI &RQYHUVLRQ 'HWDLOV &RQYHUVLRQ )DFWRUV 6SHFLI\LQJ 6RXUFH7DUJHW 8R0V ([DPSOHV )L[HG 7DUJHW ([DPSOHV 5HIHUHQFH ,QIR2EMHFW
SAP AG
DBW70E
12-43
8R0 &RQYHUVLRQV UHTXLUH DQ ,QIR2EMHFWEDVHG VRXUFH LH D 'DWD6RXUFH FDQQRW EH XVHG GLUHFWO\ EXW YLD DQ LQWHUPHGLDWH ,QIR6RXUFH
SAP AG 2006
SAP AG
DBW70E
12-44
&XVWRP URXWLQHV FDQ DOVR EH LQFRUSRUDWHG LQWR 7UDQVIRUPDWLRQV LI 8R0 FRQYHUVLRQV DUH QRW RU FDQQRW EH LQFRUSRUDWHG LQ FRQYHUVLRQ W\SHV RU WUDQVODWLRQ WDEOHV
3RVVLEOH 8VH &DVH <RXU VRXUFH FRQWDLQV VSDUVH 8R0V VRPH YDOXHV SRSXODWHG EXW VRPH 18//V $ URXWLQH FRXOG EH XVHG WR DSSO\ D VWDQGDUG 8R0 WR WKH 18// UHFRUGV ZKLOH SUHVHUYLQJ H[LVWLQJ SRSXODWHG YDOXHV LQ WKH VRXUFH
SAP AG 2006
SAP AG
DBW70E
12-45
SAP AG
DBW70E
12-46
0DVWHU 'DWD 6WDJLQJ RI &RQYHUVLRQ 'HWDLOV &RQYHUVLRQ )DFWRUV 6SHFLI\LQJ 6RXUFH7DUJHW 8R0V ([DPSOHV )L[HG 7DUJHW ([DPSOHV 5HIHUHQFH ,QIR2EMHFW
SAP AG
DBW70E
12-47
6\VWHP &KHFNV
5659 KDV EHHQ HQKDQFHG WR GR VRPH EDVLF 8R0 YDOLGLW\ FKHFNV
8R0 'DWD6WRUH 2EMHFW REMHFW LV FKHFNHG IRU NH\ YLRODWLRQV EHWZHHQ 0DVWHU 'DWD DQG 'DWD6WRUH 2EMHFW HQWULHV 'DWD6WRUH 2EMHFW FKHFNHG IRU GXSOLFDWH HQWULHV
SAP AG 2006
SAP AG
DBW70E
12-48
SAP AG 2006
SAP AG
DBW70E
12-49
SAP AG
DBW70E
12-50
$SSHQGL[
SAP AG 2006
In this Appendix examples are provided of how records may be written to the Error Stack.
SAP AG
DBW70E
13-1
SAP AG 2006
2QH UHFRUG LV PDUNHG UHG LQ D FXVWRPGHYHORSHG WUDQVIRUPDWLRQ URXWLQH 7KH NH\ RI WKH HUURU VWDFN LV RUGHU QXPEHU 5HFRUGV DQG ZLOO EH ZULWWHQ WR WKH HUURU VWDFN
5HVXOW
01 02 03
30 50 70
An example to see which data records will be updated into the error stack. There is an assumption that one record is marked red in a custom-developed transformation routine and the key of the error stack is the order number. So if the second record is supposed to be incorrect, then the next record (03) which has the same key (order number=1000) as the second record, then the second and third records will be updated into the error stack.
SAP AG
DBW70E
P H FE D 8 A88 QIG&CCB@97
"% '&$
" # !
21 ( 0 % )( !
6 %4 3 (5 0
13-2
SAP AG 2006
7KLV UHFRUG KDV EHHQ FUHDWHG LQ WKH WUDQVIRUPDWLRQ IURP WKUHH UHFRUGV RQ 6RXUFHOHYHO HJ E\ D URXWLQH RU E\ OHDYLQJ RXW D FKDUDFWHULVWLFV
5HVXOW
109882
109882 01 20050701 1000 30 109882 02 20050703 1000 50 109882 03 20050702 1000 70
01 02 03
30 50 70
1098 82
02
1000
150
109882 109882
Suppose that all three data records are OK, the aggregated recored in target is incorrect because e.g. SID-error, or missing master data etc. In this case all the three records which cause the wrong aggregated records will be written into the error stack to ensure the consistent data quality in the data target.
SAP AG
DBW70E
"% 'C$
2 1 0 X% !
%4 (5 3 0
U"C$ %
" T ! S
R
21 0 % )5 ! 5 0 %4 3
P H FE D 8 A88 WWGCV9G@97
$OO UHFRUGV ZKLFK KDYH EHHQ XVHG WR FUHDWH WKH ZURQJ UHFRUG DUH ZULWWHQ WR WKH HUURU VWDFN
13-3
SAP AG 2006
)LUVW UHTXHVW LV FRUUHFW IRU WKH VHFRQG UHTXHVW WKH UHFRUG LV ZULWWHQ WR WKH HUURU VWDFN
109882
02
1000
03.07.2005
50
109883
01
1000
02.07.2005
70
Here is an example with more requests. First request is correct. The only data record in the second request is supposed to be wrong. In this case only the incorrect records of the second request will be updated into the error stack.
SAP AG
DBW70E
P H FE D 8 A88 WI`CVCBY97
13-4
109882
01
1000
01.07.2005
30
"% 'V$
U"C$ %
" # ! V
" # ! V
6 R 6 R
21 0 % )5 !
21 0 % 5 !
6( %4 3 55 0
%4 3 (( ( 0
SAP AG 2006
$V WKH ILUVW UHTXHVW IRU RUGHU QXPEHU FRQWDLQV DQ HUURU DOO UHFRUGV ZLWK WKH VDPH NH\ RI WKH VDPH UHTXHVW DQG DOO UHFRUGV LQ VXEVHTXHQW UHTXHVWV ZLOO EH ZULWWHQ WR WKH HUURU VWDFN
109882 109882
01 02
1000 1000
01.07.2005 03.07.2005
30 50
109882 02 20050703 1000 50 109883 01 20050702 1000 70
109883
01
1000
02.07.2005
70
Another case where there are more requests. The example is the same as the first example - the second record will be updated into the error stack. The second request has all records correct, but because the first request is wrong, all records in the second request which have the order number 1000 will be updated into the error stack.
SAP AG
DBW70E
P H FE D 8 A88 WaG&V&B@97
13-5
"% 'V$
U"C$ %
" # ! V
" # ! V
6 R 6 R
21 0 % )5 !
21 0 % 5 !
6( %4 3 55 0
%4 3 (( ( 0
SAP AG
DBW70E
13-6
$SSHQGL[
SAP AG 2006
In this Appendix details are seen of how the system daemon works within Real-Time data Acquisition.
SAP AG
DBW70E
14-1
36$ 'DWD6RXUFH
" C B ) @ $ 7 E D'A3 9 5 $# 2 0 ) & $# 8 7 (6431(('%" !
,Q ERWK FDVHV WKH SURFHVV RI GDWD PRYHPHQW LV LQLWLDWHG E\ WKH V\VWHP GDHPRQ
'HOWD 4XHXH
6HUYLFH $3,
SAP AG 2006
It is a prerequisite that we are using only DataSources that popoulate the dellta queue. The daemon runs in the BI system amnd wil do certain processing on a regular basis. The daemon checks to see if a DTP exists and if so it triggers it so that the data is loaded from the PSA to the DataStore Object.
SAP AG
'DWD6WRUH 2EMHFWV
" C B ) @ 9 '$ E A3 'R8 7 (6 5 $# E E ) $5 & 5 # E " 5 G 'QHI(Q6'PI 'H F9
'DWD LV SXOOHG LQWR 36$ E\ 5HDO WLPH ,QIR3DFNDJH 'DWD LV WUDQVIHUUHG WR 'DWD6WRUH 2EMHFW YLD 5HDOWLPH '73
$SSOLFDWLRQ
14-2
6HUYLFH $3,
SAP AG 2006
SAP AG
DBW70E
14-3
%,
6HUYLFH $3,
SAP AG 2006
In this example, three records are written to the delta queue. Then the daemon comes into play. The shortest interval for the daemon here is one minute. We assume three minutes for every data load cycle. The daemon initiates an InfoPackage which looks into the delta queue and extracts the data from a source system to a BI system. Data available is records 1,2 and 3 here. The confirmation table is updated and data is written to the PSA table. After the commit of both tables, step 1 of the process is completed. In step 2 the daemon sends some status information to the source system. The data is then flagged in the source system as green. The same happens in the confirmation table. Afterwards, the daemon checks whether there is a DTP available for the update of some potential DSOs. If so, it initiates the DTP. After the data has been written successfully to a DSO step 2 of the process is completed.
SAP AG
6WHS FRPSO
8SGDWH 36$
7LPH
6WHS FRPSOHWHG 7,' RN 7,' 7,' RN 7,'
36$
&RPPLW
,QLWLDWH
7,' RN 7,'
'DWD WUDQVIHU
DBW70E
14-4
5XQWLPH 6WHSV ,
6WHS
S
SAP AG 2006
&DOO VRXUFH V\VWHP IRU QHZ UHFRUGV 6WDWXV XSGDWH RI WUDQVIHUUHG UHFRUGV LQ FRQILUPDWLRQ WDEOH
SAP AG
S S S
DBW70E
14-5
5XQWLPH 6WHSV ,,
6WHS
SAP AG 2006
SAP AG
S S S S S S
,I UHFRUGV DUH DYDLODEOH LQ FRQILUPDWLRQ WDEOH WKH FRUUHVSRQGLQJ UHFRUGV H[LVW DV ZHOO LQ 36$
,QLWLDWH '73 DIWHU WKH UHFRUGV DUH FRQILUPHG LQ FRQILUPDWLRQ WDEOH &RPPLW
*XDUDQWHHV UHVWDUW RI VWHS HYHQ ZKHQ WKH XSGDWH LQ WKH VRXUFH V\VWHP ZDV VXFFHVVIXO
DBW70E
14-6
7LPH
%,
6HUYLFH $3,
SAP AG 2006
After 3 minutes the daemon kicks in and checks to see ifg there is new data in the delta queue. There it finds records 4 and 5. The next data load cycle starts at 3:14. The data is processed in the same way in the PSA we see records 4 and 5 there. It is flagged in the source system and in the confirmation table.
SAP AG
,QLWLDWH
36$
$SSOLFDWLRQ
'HOWD 4XHXH
DBW70E
14-7
%HIRUH WKH QH[W GDWD ORDG F\FOH LV VWDUWHG The next request is opened for the next data load from source system (determined by update period of the daemon) 5HTXHVWV RI ,QIR3DFNDJH DQG '73V DUH V\QFKURQL]HG YLD GDHPRQ LH UHTXHVW LQ 36$ DQG 'DWD6WRUH 2EMHFW DUH DOLJQHG
S S
The same cycle would occur every 3 minutes. When would the request be closed? It is not happening on every data load cycle. It only happens if the request has a certain number of records or if a certain time is exceeded or in the worst case if the daemon stops. A new request is only opened when it is needed for the next data load.
SAP AG
DBW70E
14-8
7LPH
%,
6HUYLFH $3,
SAP AG 2006
The request is closed either die to the number of records in the DSO (there are 5 records there in our example) or if a certain time has been exceeded. We could define in the InfoPackage that a request be closed every day. As the request is closed the confirmation table is cleared, and therefore step 1 is completed. The opening of the next request request 2 is not within this process. That will happen when the daemon initiates the next data load cycle and calculates that it needs a request to write the data to.
SAP AG
5HTXHVW
,QLWLDWH
36$ 5HTXHVW FORVHG GXH WR WLPH RU Q RI UHFRUGV &RQILUPDWLRQ 7DEOH 7,' RN 7,' RN 7,' RN 6WHS FRPSOHWHG FRQW ZLWK ORDG
7,' RN 7,' RN
$SSOLFDWLRQ
'HOWD 4XHXH
DBW70E
14-9
SAP AG
DBW70E
14-10
$SSHQGL[
SAP AG 2006
SAP AG
DBW70E
15-1
To create a BI Accelerator index : Either Within the Data Warehousing Workbench in the 0RGHOLQJ functional area, in the navigation window, choose ,QIR3URYLGHU and in the InfoProvider tree, navigate to the InfoCube whose queries you want to optimize. In the context menu of the InfoCube choose 0DLQWDLQ %, $FFHOHUDWRU ,QGH[. The %, $FFHOHUDWRU ,QGH[ 0DLQWHQDQFHscreen appears.
Or (Access from Transaction RSDDV) On the $JJUHJDWH%, $FFHOHUDWRU ,QGH[ 0DLQWHQDQFH 6HOHFW ,QIR&XEH screen (transaction RSDDV), choose the InfoCube you require. Choose %, $FFHOHUDWRU ,QGH[. The %, $FFHOHUDWRU ,QGH[ 0DLQWHQDQFH screen appears. The user interface draws on the maintenance of relational aggregates: In the left side of the screen, the system displays ,QIR&XEHV IRU %, $FFHOHUDWRU ,QGH[HV with dimensions, characteristics and navigation attributes in a tree structure. Unlike the procedure with aggregates, it is not necessary to make specific selections and restrictions for the definition of the BI accelerator index. Instead, there is only one BI accelerator index for each InfoCube. This BI accelerator index contains all the data from the InfoCube. Select the InfoCube you require and choose &UHDWH.
SAP AG
I ' t ' @ Q CsA0s3 )RDT18r)!' !8Eqai%fEY4!4BTVdRWbF 7 9 ' 5 5 p h g e D 1 Q3 ) G 1 D De c) D F ' ' 3 F3 Q3 F D 1 Q 3 I I ' ) G F D a` H6YXWTVUD !E8T!HBC5 S Q 3 3 I D G F D 5 ' @ 9 7 53 1) ' RD P1 0HBECBA086420(&
'DWD $FTXLVLWLRQ
%, $FFHOHUDWRU
15-2
%, $QDO\WLF (QJLQH
'DWD $FTXLVLWLRQ
6$3 1HW:HDYHU %,
SAP AG 2006
To use a BI accelerator index for an InfoCube when you execute a query, you first have to activate it and then fill it with data The system performs the following steps in order to create an index on the BI accelerator server and make the data visible. The name of the index is generated from the 6\VWHP ,' and 7DEOH 1DPH: <<system ID>>_<<table name>>. The system deletes the first forward slash from the table name and replaces the second with a colon. &UHDWH: For a table, the system creates the index on the BI accelerator server in accordance with the table properties. The system also determines how many parts the index is to be split into, depending on the present size of the table. ,QGH[: The data is transferred and written to a temporary file on the BI Accelerator server. 3UHSDUH RSWLPL]H: The data in the temporary file is formatted (compressed, coded and so on) as required for search and aggregation. Depending on how the index is distributed, this step can take longer than the indexing step. &RPPLW RSWLPL]H: The previously optimized data is made visible. If you perform rollback for an index, the system rolls back the data to the last commit optimize.
SAP AG
p j i h m g p j i g f d hh g f d nkseuUBlksRU0qeRR!e(%iq F 7) D) G 9 @ ' 5 I ) D c) D F ' F Q3 7 F D1 Q3 t ' @ Q3 @ 7 D Q3 11 ' I c1) ' G D ) G srRBT!b' !%CCs!UBvy%wswwv0xTEvxA!svHC069 PWsv2ECdy0CRP!%
$ " %#!
'DWD $FTXLVLWLRQ
6$3 1HW:HDYHU %,
SAP AG 2006
SAP AG
$ " %#!
%, $FFHOHUDWRU
DBW70E
15-4
SAP AG 2006
The %, $FFHOHUDWRU VHUYHU is a TREX system as an installation of a BI accelerator engine. The data of the BI InfoCube is kept and processed entirely in the main memory of the BI accelerator server. The %, $FFHOHUDWRU HQJLQH is the part of the analytics engine that manages the BI accelerator index. This software allows the system to read data from the BI accelerator index, add data to the BI accelerator index, or change data. The %, $FFHOHUDWRU RSWLPL]HU is the part of the BI accelerator engine that ensures the best possible read access to a BI accelerator index.
SAP AG
DBW70E
T 4rT
r P TP#
t A s p
r T Pr #
4 r P rP# #
A}}z ~ | { tAvasr s ut s y x #s w v
5)&
6PDUW FRPSUHVVLRQ
SAP AG 2006
SAP AG
DBW70E
t | | t y{ As As B v !z
t ' @ Q A0svh
75(;
&RQWDLQV %, DFFHOHUDWRU
%, $FFHOHUDWRU
([HFXWHV MRLQV
15-6
&ODVVLFDO '%
7XSOH 7XSOH
SAP AG 2006
SAP AG
DBW70E
,I \RX GRQW KDYH D SUHGHILQHG LQGH[ UHDG\ \RX FDQ ZDLW D ORQJ WLPH
15-7
SAP AG
SAP AG 2006
TREX Services
Storage
DBW70E
15-8
'LFWLRQDU\EDVHG FRPSUHVVLRQ
The BI Accelerator can handle huge data volumes in main memory - without need for costly disk accesses
SAP AG
DBW70E
15-9
SAP AG 2006
SAP AG
DBW70E
t | | t { As As f v 0z
w s w }C
w s w
([SORLWV LQWHJHU FRGLQJ IRU PD[ VSHHG DQG PLQ ,2 'HVLJQHG WR UXQ RQ ODWHVW EODGH VHUYHUV DQG JULG ODQGVFDSHV 2SWLPL]HV XVDJH RI PHPRU\ DQG FDFKH UHVRXUFHV 2SWLPL]HG IRU %,
$XWRPDWLFDOO\ MRLQ UHTXLUHG LQGH[HV DV VSHFLILHG LQ WKH %, $FFHOHUDWRU LQGH[ $JJUHJDWH ODUJH DPRXQWV RI GDWD LQ SDUDOOHO 5HVWULFW DJJUHJDWHG URZV ZLWK ERROHDQ TXHU\ H[SUHVVLRQV 3URFHVV PRUH WKDQ RQH ERROHDQ H[SUHVVLRQ DW RQFH
0DQ\ PLOOLRQ GRFXPHQWV FDQ ILW LQ *% PHPRU\ &DQ VSOLW LQGH[HV KRUL]RQWDOO\ IRU SDUDOOHO SURFHVVLQJ (QDEOHV LQGH[LQJ RI KXJH YROXPHV RI VWUXFWXUHG GDWD .HHSV RQO\ UHTXLUHG FROXPQV LQ PHPRU\
75(;
15-10