Docstoc

tabw30

Document Sample
tabw30 Powered By Docstoc
					  TABW30 Business Information Warehouse -
  Extraction and Special Topics
    Business Information Warehouse -
                                   -
    Extraction and Special Topics




                        TABW30
                        BW 20B
                        BW 20B              50045517
                                             50045517
        © SAP AG 2001

12 March. 01
   Copyright



        Copyright 2001 SAP AG. All rights reserved.
        No part of this publication may be reproduced or transmitted in
        any form or for any purpose without the express permission of
        SAP AG. The information contained herein may be changed
        without prior notice.

        All rights reserved.




        © SAP AG 2001



Trademarks:
n Some software products marketed by SAP AG and its distributors contain proprietary software components of other
  software vendors.
n Microsoft ®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint ® and SQL Server® are registered trademarks of Microsoft
  Corporation.
n IBM ®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA ®, RS/6000®, AIX®, S/390®, AS/400®, OS/390 ®, and
  OS/400® are registered trademarks of IBM Corporation.
n ORACLE® is a registered trademark of ORACLE Corporation.
n INFORMIX ®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of
  Informix Software Incorporated.
n UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
n HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
  Massachusetts Institute of Technology.
n JAVA ® is a registered trademark of Sun Microsystems, Inc.
n JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
  implemented by Netscape.
n SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,
  SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com
  are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other
  products mentioned are trademarks or registered trademarks of their respective companies.
                                                                                 Contents
Course Overview......................................................................................................................................................................1
  Target Group ........................................................................................................................................................................2
  Course Prerequisites............................................................................................................................................................3
  Course Objectives I .............................................................................................................................................................4
  Course Objectives II............................................................................................................................................................5
  Course Objectives III..........................................................................................................................................................6
  Sections.................................................................................................................................................................................7
  Section: BW SAP OLTP Extraction ................................................................................................................................8
  Section: Currency Translation...........................................................................................................................................9
  Section: ASAP Implementations....................................................................................................................................10
Section: BW SAP OLTP Extraction...................................................................................................................................11
  Overall Business Scenario I.............................................................................................................................................12
  Overall Business Scenario II ...........................................................................................................................................13
  BW Overview - SAP R/3 Extraction .............................................................................................................................14
     BW Overview - SAP R/3 Extraction .........................................................................................................................15
     Overview of SAP R/3 Data Extraction:Unit Objectives ........................................................................................16
     Course Overview Diagram..........................................................................................................................................17
     BW Overview - SAP R/3 Extraction:Business Scenario .......................................................................................18
     Business Information Warehouse Architecture .......................................................................................................19
     Extracting Transaction Data........................................................................................................................................20
     Extracting Master Data.................................................................................................................................................21
     InfoSources in the R/3 OLTP System .......................................................................................................................22
     Effects of Subsequent Activities in SAP BW ..........................................................................................................23
     Business Content Extractors........................................................................................................................................24
     SAP BW Business Content Components ..................................................................................................................25
     Generic Extractors (application-specific) .................................................................................................................26
     Necessary Activities (application-specific) ..............................................................................................................27
     Generic Extractors (cross-application)......................................................................................................................28
     Necessary Activities (cross-application)...................................................................................................................29
     Function Enhancements for Extractors .....................................................................................................................30
     Delta Update ..................................................................................................................................................................31
     BW Overview - SAP R/3 Extraction: Unit Summary.............................................................................................32
     BW Overview - SAP R/3 Extraction - Exercises ....................................................................................................33
     BW Overview - SAP R/3 Extraction - Solutions.....................................................................................................37
  LIS Data Extraction...........................................................................................................................................................39
     LIS Data Extraction ......................................................................................................................................................40
     LIS Data Extraction: Unit Objectives........................................................................................................................41
     LIS Data Extraction: Overview Diagram..................................................................................................................42
     LIS Data Extraction: Business Scenario ...................................................................................................................43
     Updating Info Structures in BW .................................................................................................................................44
     LIS Data Flow................................................................................................................................................................45
     Set up LIS Environment...............................................................................................................................................46
     Set up the LIS Environment: Result ..........................................................................................................................47
     Generate InfoSource .....................................................................................................................................................48
     Generating an InfoSource: Procedure........................................................................................................................49
     Replicating DataSources ..............................................................................................................................................50
     Maintain Communication Structure ...........................................................................................................................51
     Maintain Transfer Rules...............................................................................................................................................52
     Maintain InfoCubes and Update Rules......................................................................................................................53
     Extracting Application Data........................................................................................................................................54
     LIS Delta Update...........................................................................................................................................................55
     Activating the Update...................................................................................................................................................56
     Creating an InfoPackage ..............................................................................................................................................57
     Initializing the Delta Process (Scheduler).................................................................................................................58
     Process: Initialization of Delta Update......................................................................................................................59
     Monitoring the Upload Procedure ..............................................................................................................................60
     Status Display in the Monitor.....................................................................................................................................61
     Delta Update (Scheduler).............................................................................................................................................62
     Process: First Delta Update .........................................................................................................................................63
     Process: Second Delta Update ....................................................................................................................................64
  Individual Steps in LIS Extraction.............................................................................................................................65
  LIS Data Extraction: Unit Summary..........................................................................................................................66
  LIS Data Extraction - Exercises .................................................................................................................................67
  LIS Data Extraction - Solutions..................................................................................................................................75
LO Data Extraction ...........................................................................................................................................................88
  LO Data Extraction.......................................................................................................................................................89
  LO Data Extraction: Unit Objectives.........................................................................................................................90
  LO Data Extraction: Overview Diagram..................................................................................................................91
  LO Data Extraction: Business Scenario ....................................................................................................................92
  LO Data Extraction: Data Flow into the BW System.............................................................................................93
  LO Extraction: IMG (SBIW) ......................................................................................................................................94
  Logistics Extract Structure - Customizing Cockpit .................................................................................................95
  Maintaining the Extract Structure ..............................................................................................................................96
  Maintaining DataSources.............................................................................................................................................97
  Maintaining DataSources: Procedure ........................................................................................................................98
  Replicating DataSources ..............................................................................................................................................99
  Maintaining the Communication Structure............................................................................................................ 100
  Maintaining Transfer Rules ...................................................................................................................................... 101
  Maintaining InfoCubes and Update Rules............................................................................................................. 102
  Activating Extract Structures ................................................................................................................................... 103
  V3 Update - Settings.................................................................................................................................................. 104
  Initialization/Simulation (OLI*BW)....................................................................................................................... 105
  Setup Extraction ......................................................................................................................................................... 106
  Creating InfoPackages............................................................................................................................................... 107
  Initializing the Delta Process (Scheduler).............................................................................................................. 108
  Monitoring the Upload Procedure ........................................................................................................................... 109
  Status............................................................................................................................................................................ 110
  Delta Update (Scheduler).......................................................................................................................................... 111
  Extracting Application Data..................................................................................................................................... 112
  Availability in the R/3 System................................................................................................................................. 113
  Individual Steps in LO Extraction........................................................................................................................... 114
  New LO Data Extraction: Why? ............................................................................................................................. 115
  Advantages I: Performance and Data Volumes .................................................................................................... 116
  Advantages II: Single Handling............................................................................................................................... 117
  Advantages III: Other................................................................................................................................................ 118
  LO Extraction: Conversion Scenario ...................................................................................................................... 119
  Example: Conversion in Sales ................................................................................................................................. 120
  Individual Steps: LIS ® LO Extraction.................................................................................................................. 121
  LO Data Extraction: Unit Summary ....................................................................................................................... 122
Extraction from CO-PA................................................................................................................................................. 123
  Extraction from CO-PA ............................................................................................................................................ 124
  Extraction from CO-PA: Unit Objectives.............................................................................................................. 125
  Course Overview Diagram....................................................................................................................................... 126
  Extraction from CO-PA: Business Scenario ......................................................................................................... 127
  Position of the CO-PA Application......................................................................................................................... 128
  Flow of Actual Values - Overview ......................................................................................................................... 129
  Basic Concepts ........................................................................................................................................................... 130
  Characteristics............................................................................................................................................................. 131
  Value Fields ................................................................................................................................................................ 132
  Organizational Structure ........................................................................................................................................... 133
  Database Structures in CO-PA................................................................................................................................. 134
  Storage Procedure ...................................................................................................................................................... 135
  Update Model - Overview ........................................................................................................................................ 136
  Data Staging - Overview........................................................................................................................................... 137
  Overview - BW-IMG in the R/3 System (TA SBIW) ......................................................................................... 138
  Introduction: Creating DataSources........................................................................................................................ 139
  DataSource: Header Information............................................................................................................................. 140
  DataSource: Characteristics ..................................................................................................................................... 141
  DataSource: Single Line item Characteristics....................................................................................................... 142
  DataSource: Vale Fields............................................................................................................................................ 143
  DataSource: Selection Fields ................................................................................................................................... 144
  DataSource Definition: Accounting CO-PA ......................................................................................................... 145
  BW: Replicating DataSources ................................................................................................................................. 146
  BW: Creating InfoSources........................................................................................................................................ 147
  BW: Attatching InfoSources.................................................................................................................................... 148
  BW: Setting up the Delta Upload............................................................................................................................ 149
  Delta Process (I) ......................................................................................................................................................... 150
  Delta Process (II)........................................................................................................................................................ 151
  BW: Selection Restriction ........................................................................................................................................ 153
  Individual Steps in CO-PA Extraction ................................................................................................................... 154
  Extraction from CO-PA: Unit Summary ................................................................................................................ 155
  Extraction from CO-PA (accrued) - Exercises...................................................................................................... 156
  Extraction from CO-PA (accrued) - Solutions...................................................................................................... 159
Data Extraction from FI-SL.......................................................................................................................................... 165
  Data Extraction from FI-SL (Special Ledger)....................................................................................................... 166
  Data Extraction from FI-SL: Unit Objectives ....................................................................................................... 167
  Data Extraction from FI-SL: Overview Diagram................................................................................................. 168
  Data Extraction from FI-SL: Business Scenario................................................................................................... 169
  FI-Special Ledger: Positioning ................................................................................................................................ 170
  FI-SL: Overview (I) ................................................................................................................................................... 171
  FI-SL: Overview (II) ................................................................................................................................................. 172
  FI-SL: Overview (III) ................................................................................................................................................ 173
  Data Flow FI-SL......................................................................................................................................................... 174
  Data Structures in FI-SL: Table Group ZZ............................................................................................................ 175
  Totals Table ZZT in FI-SL....................................................................................................................................... 176
  Ledger in FI-SL.......................................................................................................................................................... 177
  Difficulties Connecting FI-SL to BW..................................................................................................................... 178
  Updating the FI Special Ledger in BW .................................................................................................................. 179
  Setting Up an FI-SL DataSource (Step 1).............................................................................................................. 180
  Setting Up an FI-SL DataSource (Step 2).............................................................................................................. 181
  Transfer Structure Fields........................................................................................................................................... 182
  Extractor: Determining Key Figure Values ........................................................................................................... 183
  Extractor: Handling Currencies and Quantities .................................................................................................... 184
  Replicating DataSources in BW (Step 3)............................................................................................................... 185
  Assigning/Creating InfoSources (Step 4)............................................................................................................... 186
  Maintaining the Communication Structure (Step 5) ............................................................................................ 187
  Maintaining Transfer Rules (Step 6)....................................................................................................................... 188
  Maintaining InfoCubes and Update Rules (Step 7) ............................................................................................ 189
  Creating an InfoPackage (Step 8)............................................................................................................................ 190
  Monitoring the Upload Procedure ........................................................................................................................... 191
  Status Display in the Monitor.................................................................................................................................. 192
  Extracting Application Data..................................................................................................................................... 193
  Setting Up a Set Hierarchy DataSource ................................................................................................................. 194
  Steps to FI-ISL Extraction........................................................................................................................................ 195
  Data Extraction from FI-SL: Summary .................................................................................................................. 196
  Data Extraction from FI-SL - Exercises................................................................................................................. 197
  Data Extraction from FI-SL - Solutions................................................................................................................. 200
Tools for Generic Data Extraction............................................................................................................................... 213
  Tools for Generic Data Extraction .......................................................................................................................... 214
  Tools for Generic Data Extraction: Unit Objectives............................................................................................ 215
  Tools for Generic Data Extraction: Overview Diagram...................................................................................... 216
  Tools for Generic Data Extraction: Business Scenario ....................................................................................... 217
  Using the Tool............................................................................................................................................................ 218
  Transaction and Master Data.................................................................................................................................... 219
  Tools for Generic Data Extraction RSO2 .............................................................................................................. 220
  Creating DataSources for Transaction Data .......................................................................................................... 221
  Digression: Extraction Using View........................................................................................................................ 222
  Digression: Creating InfoSets .................................................................................................................................. 223
  InfoSets ........................................................................................................................................................................ 224
  InfoSet (here: using logical database)..................................................................................................................... 225
  InfoSet Maintenance.................................................................................................................................................. 226
  InfoSets: Additional Options.................................................................................................................................... 227
  Extract Structure/DataSource................................................................................................................................... 228
  Restrictions.................................................................................................................................................................. 229
  Generic Extractor and Delta Management............................................................................................................. 230
  Steps for Transaction Data Extractor...................................................................................................................... 231
  Steps for Master Data Extractor .............................................................................................................................. 232
  Class System: Overview (I)...................................................................................................................................... 233
  Class System: Overview (II) .................................................................................................................................... 234
  Extracting Classification Data ................................................................................................................................. 235
  Example: Material Classification ............................................................................................................................ 236
  Combining Master Data and Class Properties (Characteristics)........................................................................ 237
  Maintaining DataSources for Classification Data (I)........................................................................................... 238
  Maintaining DataSources for Classification Data (II) ......................................................................................... 239
  Special Features (I) .................................................................................................................................................... 240
  Special Features (II)................................................................................................................................................... 241
  Steps in Extracting Classification Data .................................................................................................................. 242
  Tools for Generic Data Extraction: Unit Summary.............................................................................................. 243
  Tools for Generic Data Extraction - Exercises...................................................................................................... 244
  Tools for Generic Data Extraction - Solutions...................................................................................................... 250
Enhancing Business Content ........................................................................................................................................ 268
  Enhancing Business Content.................................................................................................................................... 269
  Enhancing Business Content: Unit Objectives ..................................................................................................... 270
  Enhancing Business Content: Overview Diagram............................................................................................... 271
  Enhancing Business Content: Business Scenario ................................................................................................. 272
  Enhancing InfoSources in Business Content......................................................................................................... 273
  Data Enhancement in the Extraction Path.............................................................................................................. 274
  Enhanced Transaction Data Extraction .................................................................................................................. 275
  Creating and Maintaining Customer Appends...................................................................................................... 276
  Developing Function Enhancements ...................................................................................................................... 277
  Sample Coding ........................................................................................................................................................... 278
  Troubleshooting in Enhancements.......................................................................................................................... 279
  Important Points ......................................................................................................................................................... 280
  Steps for Data Extraction.......................................................................................................................................... 281
  How is Master Data Enhanced?............................................................................................................................... 282
  How is Master Data Enhanced?: Details ................................................................................................................ 283
  Method A: Creating Customer Appends................................................................................................................ 284
  Developing Function Enhancements for Attributes............................................................................................. 285
  Important Points ......................................................................................................................................................... 286
  Individual Steps in Enhancing Master Data .......................................................................................................... 287
  Individual Steps in Modifying Master Data .......................................................................................................... 288
  Changing Hierarchies ................................................................................................................................................ 289
  Digression: Data Enhancement in the Application .............................................................................................. 290
  What does.................................................................................................................................................................... 291
  Enhancements in LIS Update................................................................................................................................... 292
  LIS: Data Enhancement in the MC Structure........................................................................................................ 293
  Enhancements in Extracting HR Data .................................................................................................................... 294
  'Data Supply Program’ in the InfoSet..................................................................................................................... 295
  Enhancing Business Content: Unit Summary ....................................................................................................... 296
  Enhancing Business Content - Exercises ............................................................................................................... 297
  Enhancing Business Content - Solutions ............................................................................................................... 300
Special Topics: Delta Management............................................................................................................................. 308
  Special Topics: Delta Management ........................................................................................................................ 309
  Special Topics: Delta Management: Unit Objectives .......................................................................................... 310
  Special Topics: Delta Management: Overview Diagram.................................................................................... 311
  Delta Management: Data Flow................................................................................................................................ 312
  Data Extraction from R/3 OLTP ............................................................................................................................. 313
  DM: Update Modes ................................................................................................................................................... 314
  Full Update Mode ...................................................................................................................................................... 315
  Delta Update Mode.................................................................................................................................................... 316
  D-Scenario 1: Delta with Full Update ('Snapshot Scenario').............................................................................. 317
  D-Scenario 2: Delta Log in OLTP .......................................................................................................................... 318
  D-Scenario 3: Delta Log in OLTP ('Delta ODS')................................................................................................. 319
  SAPI-DM: Capabilities ............................................................................................................................................. 320
  SAPI-DM: Availability and Prerequisites.............................................................................................................. 321
  LIS: Delta Management............................................................................................................................................ 322
  CO-PA: Delta Management ..................................................................................................................................... 323
  Delta Management using SAPI Delta Queue........................................................................................................ 325
  Delta Management using ODS ................................................................................................................................ 326
      Delta and ODS: Special Features ............................................................................................................................ 327
      Delta Classification DataSource.............................................................................................................................. 328
      ODS and Delta Process............................................................................................................................................. 329
      Serialization of the Delta Process............................................................................................................................ 330
      Delta: Before/After Image ........................................................................................................................................ 331
      Special Topics: Delta Management: Unit Summary ............................................................................................ 332
    Excursus: OLTP Access via Remote Cubes .............................................................................................................. 333
      Excursus: OLTP Access via RemoteCubes........................................................................................................... 334
      Excursus: OLTP Acess via RemoteCubes: Objectives........................................................................................ 335
      Excursus: OLTP Acess via RemoteCubes: Business Scenario .......................................................................... 336
      RemoteCubes - Definition ........................................................................................................................................ 337
      RemoteCubes - Description...................................................................................................................................... 338
      Architecture................................................................................................................................................................. 339
      RemoteCubes - Uses.................................................................................................................................................. 340
      Creating RemoteCube Queries ................................................................................................................................ 341
      Transfer Rules............................................................................................................................................................. 342
      RemoteCubes - Restrictions..................................................................................................................................... 343
      SAP RemoteCube Query: Processing Steps.......................................................................................................... 344
      Supported DataSources............................................................................................................................................. 345
      Excursus: OLTP Acess via RemoteCubes: Unit Summary ................................................................................ 346
Section: Currency Translation .......................................................................................................................................... 347
  Currency Translation ..................................................................................................................................................... 348
     Currency Translation: Contents ............................................................................................................................... 349
     Currency Translation: Objectives............................................................................................................................ 350
     Currency Translation in BW - Overview............................................................................................................... 351
     Currency Translation in BW - Overview............................................................................................................... 352
     Currency Translation: Business Scenario .............................................................................................................. 353
     Currency Translation: Further Possible Scenarios ............................................................................................... 354
     Currency Translations in BW - Translations Keys............................................................................................... 355
     Currency Translations in BW - Translations Keys............................................................................................... 356
     Currency Translations in BW - Translations Keys............................................................................................... 357
     Currency Translations in BW - Currency Attributes ........................................................................................... 358
     Currency Translations in BW - Currency Attributes ........................................................................................... 359
     Currency Translations in BW - Translations Keys............................................................................................... 360
     Currency Translations in BW - Translations Keys............................................................................................... 361
     Currency Translations in BW - Translations Keys............................................................................................... 362
     Currency Translations in the BEx ........................................................................................................................... 363
     Currency Translation in the BEx............................................................................................................................. 364
     Currency Translation in the BEx............................................................................................................................. 365
     Currency Translation in the BEx : Query Definition........................................................................................... 366
     Currency Translation in the BEx : Query Definition........................................................................................... 367
     Currency Translation in the BEx: Query Definition ............................................................................................ 368
     Currency Translation in the BEx: Query Definition ............................................................................................ 369
     Currency Translation in the BEx: Query Definition ............................................................................................ 370
     Currency Translation in the BEx: Ad hoc.............................................................................................................. 371
     Currency Translation in the BEx: DB currency.................................................................................................... 372
     Currency Translation in the Bex: Restrictions...................................................................................................... 373
     Currency Translation in the Update Rules............................................................................................................. 374
     Currency Translation in the Update Rules............................................................................................................. 375
     Currency Translation in the Update Rules............................................................................................................. 376
     Currency Translation in the Update Rules............................................................................................................. 377
     Currency Translation in the Update Rules............................................................................................................. 378
     Currency Translation in the Update Rules............................................................................................................. 379
     Currency Translation in the Update Rules............................................................................................................. 380
     Currency Translation in the Update Rules - Routines ......................................................................................... 381
     Currency Translation in the Update Rules - Routines ......................................................................................... 382
     Currency Translation in the Update Rules - Routines ......................................................................................... 383
     Upload Exchange Rates from a Flat File ............................................................................................................... 384
     Upload Exchange Rate / Exrate Type from R/3................................................................................................... 385
     Upload Exchange Rate / Exrate Type from R/3................................................................................................... 386
     Upload Exchange Rate / Exrate Type from R/3................................................................................................... 387
     Currency Settings in the SAP BW IMG................................................................................................................. 388
        Currency Settings in the SAP BW IMG................................................................................................................. 389
        Currency Settings in the SAP BW IMG................................................................................................................. 390
        Currency Settings in the SAP BW IMG................................................................................................................. 391
        Currency Settings in the SAP BW IMG................................................................................................................. 392
        Inversion of Currency Translations......................................................................................................................... 393
        Inverted Exchange Rate ............................................................................................................................................ 394
        EURO Conversion in BW ........................................................................................................................................ 395
        Overview Currency Translation .............................................................................................................................. 396
        Currency Translation: Unit Summary .................................................................................................................... 397
        Exercises 1................................................................................................................................................................... 398
        Exercises 2................................................................................................................................................................... 399
        Exercises 3................................................................................................................................................................... 401
Section: ASAP Implementations...................................................................................................................................... 402
  ASAP Implementations................................................................................................................................................. 403
     SAP BW Implementation Methodology ................................................................................................................ 404
     ASAP Project Phases................................................................................................................................................. 405
     A Typical SAP BW Project Lifecycle.................................................................................................................... 406
     Why Use a the Specific SAP BW Implementation Method?............................................................................. 407
     BW Implementations................................................................................................................................................. 408
     BW Strategy................................................................................................................................................................ 409
     Phase 1: Project Preparation..................................................................................................................................... 410
     Phase 2: Business Blueprint ..................................................................................................................................... 411
     Phase 3: Realization................................................................................................................................................... 412
     Phase 4: Final Preparation ........................................................................................................................................ 413
     Phase 5: Go Live and Support.................................................................................................................................. 414
     Proposed BW Implementation Approach.............................................................................................................. 415
     SAP BW Specific Skills (Roles) ............................................................................................................................. 416
     Business Information Warehouse Project Roles................................................................................................... 417
     Business Information Warehouse Project Roles................................................................................................... 418
     Business Information Warehouse Project Roles................................................................................................... 419
     Business Information Warehouse Project Roles................................................................................................... 420
     Business Information Warehouse Project Roles................................................................................................... 421
     Project Organization .................................................................................................................................................. 422
     Using ASAP for SAP BW Implementation........................................................................................................... 423
     ASAP: Comprehensive Solution ............................................................................................................................. 424
     AcceleratedSAP Tools Approach: Offline............................................................................................................. 425
     ASAP Roadmap ......................................................................................................................................................... 426
     ASAP Knowledge Corner......................................................................................................................................... 427
     BW on ASAP CD....................................................................................................................................................... 428
     AcceleratedSAP Accelerators .................................................................................................................................. 429
     The SAP BW 2.0B Accelerators ............................................................................................................................. 430
     SAP BW Documentation Enhancements............................................................................................................... 431
     ASAP for SAP BW Rollout Strategy ..................................................................................................................... 432
     SAP BW in the SAP Service Marketplace ............................................................................................................ 433
     Key Success Factors .................................................................................................................................................. 434
     Key Success Factors Findings.................................................................................................................................. 435
     Key Success Factors Findings.................................................................................................................................. 436
     Primary Factors Impacting BW Project Length.................................................................................................... 437
  Global ASAP................................................................................................................................................................... 438
     Overview SAP BW Strategy.................................................................................................................................... 439
     Focus on SAP BW Strategy ..................................................................................................................................... 440
     Global ASAP and ASAP for BW ............................................................................................................................ 441
     Deliverables of the SAP BW Strategy.................................................................................................................... 442
     Global ASAP: Tasks of the SAP BW Strategy..................................................................................................... 443
     What Are Global SAP BW Implementations?...................................................................................................... 444
     Scope of SAP BW Roll-out Scenarios ................................................................................................................... 445
     Global Information Model........................................................................................................................................ 446
     Global Information Model........................................................................................................................................ 447
     Global and Local Information Models ................................................................................................................... 448
     Global Versus Local Data......................................................................................................................................... 449
     Information Model: Ownership of Data................................................................................................................. 450
     Global Information Supply Chain ........................................................................................................................... 451
 System Topologies..................................................................................................................................................... 452
 The mySAP.com Information Hub ......................................................................................................................... 453
 Architecture Scenarios .............................................................................................................................................. 454
 Data Flows................................................................................................................................................................... 455
 Data Mart Interface .................................................................................................................................................... 456
 Productive Environment: Single Global BW ........................................................................................................ 457
 Multi BW: Productive Environment Example I ................................................................................................... 458
 Multi BW: Productive Environment Example II .................................................................................................. 459
 Hub & Spoke: Multi BW Installations................................................................................................................... 460
 Example I: Development System Architectures ................................................................................................... 461
 Example II: Development System Architectures.................................................................................................. 462
 Example III: Development System Architectures ................................................................................................ 463
 Implementation Approach........................................................................................................................................ 464
 Implementation Approaches .................................................................................................................................... 465
 Iterative and Integrated Approach........................................................................................................................... 466
 Integration ................................................................................................................................................................... 467
 Global Data Warehouse Implementation Organization....................................................................................... 468
 Communication: Selling & Change Management................................................................................................ 469
BW Reviews.................................................................................................................................................................... 470
 Elements to Ensure Quality...................................................................................................................................... 471
 What are BW Project Reviews?.............................................................................................................................. 472
 BW Project Review Process..................................................................................................................................... 473
 SAP BW Review Program....................................................................................................................................... 474
 BW Project Review Objectives ............................................................................................................................... 475
 Benefits of the BW Project Reviews ...................................................................................................................... 476
 Who Carries Out Project Reviews?......................................................................................................................... 477
 Key Interviews............................................................................................................................................................ 478
 Key Documents to BW Review............................................................................................................................... 479
 SAP BW Project Review Focus Areas................................................................................................................... 480
 SAP BW Project Review Focus Areas................................................................................................................... 481
 SAP BW Project Review Focus Areas................................................................................................................... 482
 SAP BW Project Review Focus Areas................................................................................................................... 483
 Frequently Asked Questions .................................................................................................................................... 484
Course Overview




  © SAP AG 2001
    Target Group



         l Audience:
                n   Consultants from SAP Partners
                n   Project Team Members from SAP Customers


         l Duration: 5 days




        © SAP AG 2001




Notes to user
n   The training materials are not teach-yourself programs. They complement the course instructor's
    explanations. There is space on the sheets for you to write down additional information.
n   There may not be enough time during the course for you to complete all of the exercises. The
    exercises provide additional examples to be worked during the course. However, participants can
    also use them after the course to reinforce what they have learned.
Course Prerequisites




   l Required Knowledge
         n   Knowledge of course content of TABW10 and TABW20
         n   Basic knowledge in the area of Data Warehouse


   l Recommended Knowledge
         n   Experience in SAP R/3 environment
         n   Knowledge in at least one R/3 application




  © SAP AG 2001
Course Objectives I



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

                   l Explain the basic concept of OLTP extraction
                      from an SAP R/3 System
                   l Perform the transfer of data from self-defined LIS
                      information structures
                   l Set up the customizing of logistic extract
                      structures
                   l Perform the transfer of CO-PA data

                   l Perform the data extraction of FI-SL

                   l Use the generic extractor to retrieve master and
                      transaction data
                   l ...

   © SAP AG 1999
Course Objectives II



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

                   l Adapt and extend SAP's Business Content to suit
                      your company's needs,
                   l Create individual extraction techniques with the
                      help of function enhancements,
                   l Define delta management with OLTP extraction,

                   l Assess the use of direct accesses to the OLTP
                      with RemoteCubes.




   © SAP AG 1999
Course Objectives III




                   At the conclusion of this course, you will be able to:
                   l Handle currency translation within SAP BW
                   l Understand how to approach a BW implementation
                     using ASAP




   © SAP AG 2001
Sections




  Section         BW SAP OLTP Extraction
  Section         Currency Translation
  Section         ASAP Implementations




  © SAP AG 2001
Section: BW SAP OLTP Extraction



  Unit            BW Overview
  Unit            LIS Data Extraction
  Unit            LO Data Extraction
  Unit            Extraction from CO-PA
  Unit            Extraction from FI-SL
  Unit            Tools for Generic Data Extraction
  Unit            Enhancing Business Content
  Unit            Special Topics: Delta Management
  Unit            Excurses: OLTP Access via RemoteCubes




  © SAP AG 2001
Section: Currency Translation




  Unit             Currency Translation




   © SAP AG 2001
Section: ASAP Implementations




  Unit            ASAP Implementations
  Unit            Global ASAP
  Unit            BW Reviews




  © SAP AG 2001
Section: BW SAP OLTP Extraction



                      BW Overview -              Tools for Generic
                     SAP R/3 Extraction           Data Extraction

                                                    Enhancing
                     LIS Data Extraction
                                                  Business Content

                                                  Special Topics:
                     LO Data Extraction
                                                 Delta Management

                                               Excursus: OLTP Access
                   Extraction from CO-PA
                                                  via Remote Cubes


                  Data Extraction from FI-SL




  © SAP AG 2001
Overall Business Scenario I


                   l Your company has opted for the SAP Business
                      Information Warehouse as its data warehouse
                      solution and is using the data collection extractors
                      that are provided in the form of the Business
                      Content.
                   l In the OLTP, your company uses the Logistic
                     Information System (LIS) of the applications
                     Purchasing and Sales. You want to transfer data
                     from the user-defined information structures of
                     Purchasing into BW. Within Sales, data has already
                     been transferred with the extract structures; but for
                     various reasons you want to use the new LO
                     extractor, so you need to convert to the new
                     functionality.
                   l ...


   © SAP AG 1999
Overall Business Scenario II


                   l In addition, you want to use the CO-PA and FI-SL
                     data in the BW System, for which you have to
                     generate user-defined DataSources for the
                     individual results areas.
                   l Some of the tables in the R/3 System are supplied
                     with data by programs that were developed in-
                     house. Your company also wants to be able to
                     evaluate this data with BW.
                   l Your company is missing characteristics for the
                     report from some Business Content InfoSources,
                     which should be made available with the
                     enhancements in Business Content.




   © SAP AG 1999
BW Overview - SAP R/3 Extraction



                      BW Overview -              Tools for Generic
                     SAP R/3 Extraction           Data Extraction

                                                    Enhancing
                     LIS Data Extraction
                                                  Business Content

                                                  Special Topics:
                     LO Data Extraction
                                                 Delta Management

                                               Excursus: OLTP Access
                   Extraction from CO-PA
                                                  via Remote Cubes


                  Data Extraction from FI-SL




  © SAP AG 2001
BW Overview - SAP R/3 Extraction



      Contents:

       l The extraction process
       l Types of extractors
       l Enhancements to extractors (overview)
       l Delta management for extractors (overview)
       l Business Content




  © SAP AG 1999
Overview of SAP R/3 Data Extraction:
Unit Objectives



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

                   l understand the different concepts of and
                      options for extracting data from the R/3
                      System
                   l explain the concept of Business Content.




   © SAP AG 1999
    Course Overview Diagram


                                           Extractor Types

                   Application-specific                            Cross-application

         BW Content                     Generic                          Generic
          Extractors                   Extractors                       Extractors

              FI                        LIS                              Database
                    CO                                                   table/view
             HR
                   ...                        FI-SL
                                                                         SAP Query
          LO Cockpit                          CO-PA


          Transparent                 Transparent
                                                                        Data Source
             Table                       Table

                                          Enhancements
                                          Enhancements


        © SAP AG 1999



n   The transaction data entering the Business Information Warehouse by means of extractors originates
    from very different modules. Due to past developments, very different extraction mechanisms are
    necessary.
BW Overview - SAP R/3 Extraction:
Business Scenario

                  Before you start an SAP BW project (and also if BW
                  is already in productive use), you will probably
                  think about the reports you want to run and the
                  data you need from the R/3 System.
                  You will then have to take a look at the sources
                  shipped with SAP Business Content to decide
                  which ones meet your requirements and can be
                  used by default.
                  If you need data that cannot be supplied by the
                  standard sources, you can:
                   l Create new InfoSources

                   l Enhance the standard ones




  © SAP AG 1999
    Business Information Warehouse Architecture

                                                                                Business Explorer
      Web Browser        Web Design Tool                      Business Explorer Browser
                                                              Business Explorer Browser

                                                          BEx Analyzer
                                                          BEx Analyzer                 External
                                                                                        External
                                    Display views
          SAP Internet                                   (with MS Excel)
                                                         (with MS                     OLAP Client
                                                                                      OLAP Client
          Transaction
          Server
                                 HTML save
                                 templates
                                                                                           ODBO

     Administrator                                                                        BW Server
                               BDS         BW WEB Service
                                              WEB Service            OLAP Processor
     Workbench                 Business
                               Document
                               Service
          Manage
          Manage
                                           Metadata Manager          Data Manager          InfoCubes
                                           Metadata Manager          Data Manager
         Schedule
         Schedule            Metadata
                            Repository
                            Repository                                                    Operational
                                                          Staging Engine
                                                          Staging Engine
          Monitor                                                                         Data Store
                                                              BAPI
                                                              BAPI




                               Data Extractor for non-
                               Data Extractor for non-               Data Extractor for
                                                                     Data Extractor for      OLTP
                                                                                             OLTP
                                SAP Production Data                  Production Data
                                                                      Production           Reporting
                                                                                           Reporting

                            Non-SAP OLTP Applications
                            Non-SAP OLTP Applications                      R/3 OLTP Applications
                                                                           R/3 OLTP Applications


        © SAP AG 1999



n   As components of the Business Framework, OLTP applications and the Business Information
    Warehouse communicate via BAPIs (Business Application Programming Interfaces).
n   The extraction mechanisms that are used to prepare the production data in each application for the
    Business Information Warehouse are located in an R/3 OLTP System. The purpose of this course is
    to explain how these extraction mechanisms in the R/3 OLTP System work.
n   With non-SAP applications, the prerequisites for exchanging data between the application and the
    Business Information Warehouse can be met by separate installations from external suppliers.
    Extracting Transaction Data


                     Business Information
                      Warehouse Server:                 InfoCubes
                       Staging Engine
                                                       Update rules

                                                                                 InfoSource
      DataSource                                   Communication Structure
                                                   Communication Structure



                              Transfer Structure
                              Transfer Structure            Transfer Structure
                                                            Transfer Structure             Transfer Structure
                                                                                           Transfer Structure




                              Transfer Structure
                              Transfer                      Transfer Structure               Transfer Structure
                                                                                             Transfer Structure
                                                            Transfer Structure


                         Extraction Source Structure   Extraction Source Structure      Extraction Source Structure
                                                                                        Extraction Source Structure
                                                       Extraction Source Structure
                                                                                     Transaction
                                          Transaction Data                           data


                                            OLTP System 1                                   OLTP System 2




         © SAP AG 1999



n   A DataSource describes a type of infrastructure that allows information to be transported between
    OLTP Systems and BW. This infrastructure comprises various DDIC structures that are linked by
    means of transformation rules. DataSources, therefore, regula te the flow of data between the
    extraction source structure in the source system to the communication structure in BW, via which the
    respective data is supplied. DataSources can supply both transaction data (stored in InfoCubes) and
    master data (attributes, texts, and hierarchies - stored in separate, transparent tables). The structure of
    the DataSources for transaction and master data is almost identical.
n   DataSources describe the set of all available data for a business event, or type of business event (for
    example, Cost Center Accounting). For this reason, every operative SAP BW environment will
    contain a large number of DataSources that describe the individual operations within the applications
    that are to be analyzed.
n   Each time a DataSource is generated, the corresponding transfer and communication structures are
    also generated in the BW System. Transfer structures always exist in pairs - in a source system and
    in the associated SAP BW System. This transfer structure is used to transfer data in the format of the
    original application from a source system to BW, where it is forwarded to the communication
    structure of the InfoSource using transformation rules.
    The communication structure is independent of the source system and contains all of the fields in the
    InfoSource that it represents in BW.
    Extracting Master Data


                     Business Information
                      Warehouse Server:                  Attributes Hierarchies Master Data
                       Staging Engine
                                                              Texts


                                                                                   InfoSource
       DataSource
                                                        Communication Structure
                                                        Communication


                              Transfer Structure                                        Transfer Structure
                                                                                        Transfer Structure
                              Transfer Structure




                              Transfer Structure
                              Transfer Structure                                       Transfer Structure
                                                                                       Transfer Structure


                         Extraction Source Structure
                         Extraction Source Structure                              Extraction Source Structure
                                                                                  Extraction Source Structure


                                                       Master Data                                              Master Data
                           Attributes Hierarchies                                    Attributes Hierarchies
                                                                                                Hierarchies
                                 Texts                                                    Texts
                                                   OLTP System 1                                             OLTP System 2




         © SAP AG 1999



n   A DataSource describes a type of infrastructure that allows information to be transported between
    OLTP Systems and BW. This infrastructure comprises various DDIC structures that are linked by
    means of transformation rules. DataSources, therefore, regulate the flow of data between the
    extraction source structure in the source system to the communication structure in BW, via which the
    respective data is supplied. DataSources can supply both transaction data (stored in InfoCubes) and
    master data (attributes, texts, and hierarchies - stored in separate, transparent tables). The structure of
    the DataSources for transaction and master data is almost identical.
n   DataSources describe the set of all available data for a business event, or type of business event (for
    example, Cost Center Accounting). For this reason, every operative SAP BW environment will
    contain a large number of DataSources that describe the individual operations within the applications
    that are to be analyzed.
n   Each time a DataSource is generated, the corresponding transfer and communication structures are
    also generated in the BW System. Transfer structures always exist in pairs - in a source system and
    in the associated SAP BW System. This transfer structure is used to transfer data in the format of the
    original application from a source system to BW, where it is forwarded to the communication
    structure of the InfoSource using transformation rules.
    The communication structure is independent of the source system and contains all of the fields in the
    InfoSource that it represents in BW.
    InfoSources in the R/3 OLTP System




                                                                         Transfer Structure
                                                                                  Structure

                                                                         InfoObjects
                                                                         InfoObjects
                                               Assign


                                                                         Extraction Source Structure


                             Transparent Table, View,
                            Function Module, SAP Query                   Extractor
                                                                         Extractor



                         Transparent
                            Table             Transparent
                                                 Table
         © SAP AG 1999



n   Every DataSource gets its data in some form from transparent tables in the R/3 OLTP System. The
    database of such an extractor is therefore a transparent table.
n   The extractor now defines by which methods data will be extracted. Extraction can now take place
    directly from the transparent table. It can also take place with a database overview, a function
    module or SAP Query. This means you can use a view to go to several different database tables.
n   The extractor forwards the data to the extract structure. The extractor may be able to supply data to
    more fields than exist in the extract structure. But it may also be the case that the extract structure has
    more fields than the extractor can supply to. These fields can then be supplied with data using
    function enhancements (see unit on Enhancing Business Content).
n   Data elements of the respective SAP OLTP Data Dictionary describe the individual fields of the
    extract structure. For SAP BW, we also need a description of InfoObjects in the SAP BW Metadata
    Repository.
    The fields in the extract structure must then be assigned InfoObjects. Not all the fields in the extract
    structure have to be assigned InfoObjects. However, after a Metadata upload, only the fields that
    were assigned an InfoObject are made available in the template DataSource for creating the
    communication structure.
    Effects of Subsequent Activities in SAP BW


           l Replicating DataSources
                  n     The DataSource is replicated in BW.
                  n     Fields in the OLTP extract structure that have been assigned
                        InfoObjects are made available in a template DataSource in
                        BW.
           l Assigning InfoSources
                  n     The DataSource is assigned to an InfoSource.
           l Maintaining the Communication Structure
                  n     The communication structure is generated from the selected
                        fields in the template InfoSource in BW.
           l Creating Transfer Rules
                  n     The transfer structure is generated from the selected
                        InfoObjects in the template DataSource in BW and in the R/3
                        OLTP System.
        © SAP AG 1999



n   Once a DataSource has been generated in the OLTP system, the Metadata must be uploaded to the
    SAP BW System. During this process, a template DataSource for selecting the fields in the
    communication structure is created from the InfoObjects assigned to the extract structure.
n   The fields in the communication structure then have to be supplied with data by means of transfer
    rules. This can take place using a field in the template DataSource, a fixed value, or a function exit.
    The fields in the template DataSource that are used to populate the communication structure together
    define the transfer structure.
n   The transfer structure is generated automatically when the transfer rules are activated in SAP BW
    and in the R/3 OLTP System.
    Business Content Extractors


      DataSources that
                                               Extractor types
       can be activated
      for all applications

                        application-specific                           cross-application


            BW Content                     Generic                           Generic
             Extractors                   Extractors                        Extractors


                 FI                         LIS                               database
                      CO                                                     table/view
               HR
                                                  FI-SL
                      ...
                                                                            SAP Query
             LO Cockpit                           CO-PA



             transparent                   transparent
                 table                                                      data source
                                               table

        © SAP AG 1999



n   SAP provides extractors for almost all applications.
n   These extractors are programmed on a fixed basis and shipped with Business Content. However,
    some Business Conent extractors do use the technology of the cross-application generic extrractors.
n   Business Content is developed and enhanced with every new BW Release.
    SAP BW Business Content Components
                                                                                                    ~120
                                                                 Channels/Roles

                                                                                          ~800
                                                          Workbooks

                                                                                ~800




                                                                                                n
                                                                                              io
                                                                                            at
                                                     Queries




                                                                                         liz
                                                                                       ua
                                                                                    vid
       Import extractor




                                                                                  di
                                                                         ~240




                                                                                In
        CD into the
       OLTP System                           InfoCubes

                                    Update rules
                           InfoSources                 ~120




                                                                   n
                                                                tio
                            Customer


                                                             iza
                                             ~4200
       InfoObjects
                                                           rd
                            Order Quantities
                                                         da
                                                       an
                                                     St

                                                                                     BW2.0B

Extractor               ~800
        © SAP AG 1999



n   Business Content in BW Release 2.0B as of May 2000 contains:
         around 800 SAP standard extractors (for R/3, New Dimensions, external)
         around 120 SAP standard InfoSources
         around 240 SAP standard InfoCubes
         around 800 SAP standard queries (of which around 80 are Web-compatible)
         around 800 SAP standard workbooks
         around 180 channels / roles
n   SAP will continue to add further objects in all application areas.
    Generic Extractors (application-specific)

                                                                    Application
                                                                     enables
                                             Extractor types      you to generate
                                                                   DataSources

                    application-specific                              cross-application

          BW Content                     Generic                           Generic
           Extractors                   Extractors                        Extractors


               FI                         LIS                               database
                    CO                                                     table/view
             HR
                                                FI-SL
                    ...
                                                                           SAP Query
           LO Cockpit                           CO-PA



           transparent                   transparent
                                                                          data source
               table                         table
        © SAP AG 1999



n   In response to demands from our customers, SAP has designed the reporting facility in certain parts
    of the R/3 System in such a way that it can be easily customized. Information systems were
    developed in the R/3 System that can be adapted individually to the customer's requirements.
n   The Business Information Warehouse must be able to process this data, with the result that it must be
    possible to define generic extractors in certain applications. These applications are the Logistics
    Information System, profitability analysis and Special Ledger.
    Necessary Activities (application-specific)


         l Generate DataSource                             BW Link for LIS Info Structures
                                                              Link
           from a specified                                Information structure    S5nn
           application database                            Generate DataSource




         l Edit DataSource                                 Selecting Selection Fields




         l Define application-specific                     BW Link for LIS Info Structures
                                                           BW Link for LIS Info Structures

           settings                                         Information structure          S5nn
                                                                                                  R

                                                            Delta update in LIS
                                                            Activate/deactivate


        © SAP AG 1999



n   Each individual application provides tools for this purpose. But first, you have to generate a
    DataSource from a selected 'data base' in the application.
n   Following this, you have to assign attributes to the fields of the extract structure / DataSource (for
    example, selectability).
n   Depending on the application, certain settings may have to be made. In this example, activating the
    delta update in the LIS.
    Generic Extractors (cross-application)


                                                Extractor types


                   application-specific                                cross-application


         BW Content                       Generic                            Generic
          Extractors                     Extractors                         Extractors


              FI                          LIS                                 database
                   CO                                                        table/view
             HR
                                                 FI-SL
                   ...
                                                                            SAP Query
           LO Cockpit                            CO-PA
                                      Generate your own
                                    DataSources, based on
                                     anyother DataSources
           transparent                  Transparent
              table                                                         data source
                                           Table

        © SAP AG 1999



n   Data supplied to customer tables in an R/3 System by programs developed in-house can also be
    transferred to BW. This includes data in R/3 tables that are supplied by SAP programs but cannot be
    made available to the Business Information Warehouse with Business Content.
n   The tool for generic data extraction can be used here to generate an extractor for all applications. By
    assigning a database view or transparent database table, you can transfer data to BW without having
    to write your own programs. Furthermore, the generic extractor can also be used by SAP Query to
    retrieve data (note 144746).
n   These techniques are also used for some of the Business Content extractors.
    Necessary Activities (cross-application)


           l Call up tool for generic data extraction: Create DataSource.
                                                           Packet on generic data extraction
                                                           Packet on generic data extraction

                                                           Name of InfoSource               ZEBAN

                                                             Create


           l If necessary, create a database view or SAP Query.
                                                            Dictionary: Maintain VIEW ZEBAN

                                                            Database view           ZEBAN
                                                            Short description       Purchase requisitions


           l Assign InfoObjects to the fields in the DataSource.
                                                            Assigning DataSource Fields to InfoObjects
                                                                                 Fields to InfoObjects

                                                             DataSource ZEBAN
                                                                   Field     Data elem.   InfoObjectTYP
                                                                   MATNR     MATNR        0MATERIAL CHA
                                                                   WERK      EWERK        0PLANT    CHA
                                                                   ...       ...          ...            CHA
                                                                                                         KYF

        © SAP AG 1999



n   Several steps are also required to create extractors using the generic data extraction tool (transaction
    RS02). These are basically as follows:
n   Create a DataSource with the generic data extraction tool (transaction RSO2)
n   If necessary, create a view or an InfoSet (functional area).
n   The fields in the DataSource must then be assigned InfoObjects. If these InfoObjects are not
    available, they must be created.
    Function Enhancements for Extractors


                                               Extractor Types


                   Application-specific                                Cross-application




                             ü                           ü                                ü
                                                          OK                                 OK
                               OK
          BW Content                         Generic                         Generic
           Extractors                       Extractors                      Extractors


                                                                             Database
                                                                             table/view

                                                                            SAP Query
                                InfoObjects
    Assign              2

                               Extraction structure      Views as extractors
                   1                                     for transaction data
                                    3                          cannot be
          Attach                                               enhanced
                            Fill with
                            Function exit

        © SAP AG 1999



n   The Business Content shipped by SAP provides customers with a set of standard extractors for the
    R/3 System in the Business Information Warehouse. Every customer, however, has his or her own
    requirements when it comes to the data that is to be supplied by the extractors. For this reason, BW
    provides function exits for extending Business Content.
n   This procedure first involves extending the standard extraction structures. After this, the new fields
    must be assigned InfoObjects and then the function exit for enriching the data must be programmed.
n   Application-specific generic extractors in CO/PA, LIS, and FI-SL can also be extended.
n   This also applies to the cross-application generic extractors, with the exception that enhancements
    are not possible if a view is used to extract transaction data.
    Delta Update



                                                  Data Types


                      Transaction Data                                       Master Data


          BW Content                      Generic                              Generic
           Extractors                    Extractors                           Extractors
                                                                  If
                                                              change log




                                                                                            ü
                                                                  is
                                                                                             OK
                SD                            LIS              available       Attributes




                  ü
                HR                          CO/PA                                Texts




                                                  ü
                ...                          FI-SL
                                                                              Hierarchies
              OK
                                             OK



        © SAP AG 1999



n   Data can be imported into BW using two different update methods: a full update, in which all of the
    data is extracted, and a delta update, in which only the data that has been changed or added since the
    last import run is extracted.
n   Naturally, a delta update is particularly suitable for large quantities of data so that the same data does
    not have to be imported into BW several times. Unfortunately, not all of the extractors in Release
    2.0B support a delta process, such as FI-SL.
n   A delta management tool (change log) is provided for the most important master data, which can
    have a very large number of characteristic instances in the R/3 OLTP System. These characteristics
    are the material, batch number, plant, creditor, debtor, cost center, cost component, activity type and
    G/L account.
n   As far as the transaction data is concerned, Business Content is shipped with extractors in SD and
    HR, which support delta processes. Within the LO module, a central delta management is used. In
    LIS and CO/PA, all application-specific generated extractors support a delta process. Delta updates
    in the LIS are based on separate delta tables. The CO/PA module, on the other hand, uses a
    timestamp.
n   A delta process is not implemented for the cross-application generic data extraction tool. Delta
    extraction in this case can only be carried out by suitable selections using a creation and change date.
BW Overview - SAP R/3 Extraction:
Unit Summary



                  You are now able to:
                  l understand the different concepts of and
                     options for extracting data from the R/3
                     System
                  l explain the concept of Business Content.




  © SAP AG 1999
BW Overview - SAP R/3 Extraction - Exercises

           Symbols Used in the Exercises and Solutions

                       Exercises


                       Solutions


                       Objectives


                       Business scenario


                       Hints and tips


                       Warning or caution
                                                                                Exercises


              Unit:           BW Overview - SAP R/3 Extraction
              Topic:          Overview of Extractors



              At the conclusion of this exercise, you will be able to:
              • Discuss the various ways of extracting data from the R/3 System




              Before you start a BW project, you’ll probably think about the reports you will
              want to run and the data you will need from the R/3 System.

              You will then have to take a look at the DataSources shipped with Business
              Content to decide which ones meet your requirements and that can be used as
              standard DataSources.

              If you need data that cannot be supplied by default, you can:

              •   Create new DataSources
              •   Enhance standard DataSources



1-1   Using the following questions, check your understanding of the extractors in the
      R/3 OLTP System and their significance for the SAP BW System.
      1-1-1 What is the purpose of extract structures as far as DataSources in the OLTP
            System are concerned?
             _________________________________________________________

             _________________________________________________________

             _________________________________________________________

             _________________________________________________________

             _________________________________________________________
1-1-2 Does the transfer structure always contain the same fields as the extract
      structure of a DataSource?
       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

1-1-3 When does a transfer structure contain more fields than the communication
      structure of an InfoSource?
       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

1-1-4 What steps do you have to take to be able to use extractors from Business
      Content in the SAP BW System?
       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

1-1-5 Which applications provide customer-specific extractors and why was this
      done by SAP?
       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________
1-1-6 What is the purpose of the generic extractor? Is it a tool that is linked to
      certain applications?
       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

1-1-7 Why does SAP enable function enhancements to be provided for all types of
      extractors? For which extractors is this particularly significant? With which
      data and extraction method can function enhancements not be used?
       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________

       _________________________________________________________
BW Overview - SAP R/3 Extraction - Solutions


                Unit:          BW Overview - SAP R/3 Extraction
                Topic:         Overview of Extractors



  1-1   Using the following questions, check your understanding of the extractors in the
        R/3 OLTP System and their significance for the SAP BW System.
        1-1-1 What is the purpose of extract structures as far as DataSources in the OLTP
              System are concerned?
               Once the DataSources have been replicated to SAP BW, this information
               is used as an InfoSource template for defining the communication
               structure. A communication structure must contain the fields that can be
               supplied later with data from the OLTP System.
        1-1-2 Does the transfer structure always contain the same fields as the extract
              structure of a DataSource?
               If you do not use all of the fields in the DataSource template to define the
               communication structure, you do not need all of the fields in the transfer
               structure to supply them with data. The transfer structure, therefore, may
               only contain some of the fields from the extract structure.
        1-1-3 When does a transfer structure contain more fields than the communication
              structure of an InfoSource?
               If you use a routine to enhance a field in the communication structure
               from several fields in the transfer structure, the communication structure
               may contain more fields.
        1-1-4 What steps do you have to take to be able to use extractors from Business
              Content in the SAP BW System?
               First, you have to load the data from the extractor CD to the OLTP
               System. Then you have to activate the required application components
               from Business Content.
               R/3 System è BW IMG (SBIW) è Business Content DataSourcesè
               Transfer Business Content DataSources
               BW Server è Administrator Workbench è Monitoring è Source
               Systems. Context menu (right mouse-click) on source system
               T90CLNT090
               è Replicate DataSources
               or
               è DataSource Overview. Context menu (right mouse button) on
               application component è Replicate DataSources.
1-1-5 Which applications provide customer-specific extractors and why was this
      done by SAP?
       CO-PA, LIS, and FI-SL. In response to demands from our customers,
       SAP has designed the reporting facility in these areas of the R/3 System in
       such a way that it can be easily customized. Information systems were
       developed in the R/3 System that can be adapted individually to the
       customer's requirements. The Business Information Warehouse must be
       able to handle this data, with the result that it must be possible to define
       extractors in certain applications.
1-1-6 What is the purpose of the generic extractor? Is it a tool that is linked to
      certain applications?
       This tool is not linked to specific applications. If customer tables in the
       R/3 System are supplied with data by programs that were also written by
       the customer, it must also be possible to transfer this data to the BW
       System. This includes data in R/3 tables that are supplied by SAP
       programs but cannot be made available to the Business Information
       Warehouse with Business Content. You can use the generic extractor to
       create extractors for these tables.
1-1-7 Why does SAP enable function enhancements to be provided for all types of
      extractors? For which extractors is this particularly significant? With which
      data and extraction method can function enhancements not be used?
       By creating enhancements, you can enrich all of the extractors with data
       while the data is being uploaded. This is particularly significant for
       Business Content. Business Content shipped by SAP provides a standard
       set of extractors for the R/3 System in the Business Information
       Warehouse. Every customer, however, has his or her own requirements
       with regard to the data that is to be supplied by an extractor. For this
       reason, SAP provides function exits that can be used to enhance Business
       Content. The only case where enhancements cannot be used is with
       transaction data extractors that are supplied with data via a database view.
LIS Data Extraction



                       BW Overview -              Tools for Generic
                      SAP R/3 Extraction           Data Extraction

                                                     Enhancing
                      LIS Data Extraction
                                                   Business Content

                                                   Special Topics:
                      LO Data Extraction
                                                  Delta Management

                                                Excursus: OLTP Access
                    Extraction from CO-PA
                                                   via Remote Cubes


                   Data Extraction from FI-SL




   © SAP AG 2001
LIS Data Extraction



       Contents:
        l Linking R/3 information structures to BW
        l Filling InfoCubes using the delta update method




   © SAP AG 1999
LIS Data Extraction: Unit Objectives



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

                   l Perform the necessary Customizing for
                     transferring data from R/3 source system info
                     structures
                   l Map a DataSource to an InfoSource and maintain
                     their communication structures and transfer rules
                   l Build an InfoCube and maintain update rules,
                   l Supply an InfoCube with the initialization and
                     delta upload methods.




   © SAP AG 1999
    LIS Data Extraction: Overview Diagram


                                           Extractor Types
                                                     Types

                   Application-specific                            Cross-application


         BW Content                     Generic                          Generic
          Extractors                   Extractors                       Extractors

              FI                        LIS                              Database
                    CO                                                   table/view
             HR
                   ...                        FI-SL
                                                                         SAP Query
          LO Cockpit                          CO-PA


          Transparent                 Transparent
                                                                        Data Source
             Table                       Table

                                          Enhancements
                                          Enhancements


        © SAP AG 1999



n   The transaction data entering the Business Information Warehouse by means of extractors originates
    from very different modules. Due to past developments, very different extraction mechanisms are
    necessary.
LIS Data Extraction: Business Scenario



                   l Your company uses its own info structure to report
                     on incoming orders according to sales
                     organizations and customers.
                     You are responsible for extracting the data from
                     the R/3 System and transporting it into BW. To do
                     this, you have to create the necessary components
                     in the R/3 and BW Systems.
                     You have to use a delta update mechanism to
                     upload the data.




   © SAP AG 1999
    Updating Info Structures in BW

       BW System
                                                                         InfoCubes


                                                  Update rules


                                           Communication Structure
                                           Communication Structure


                                                  Transfer Rules
                           transfer structure
                            transfer                                    transfer structure
                                                                         transfer structure



      R/3 OLTP             transfer structure
                           transfer structure                           transfer structure
                                                                         transfer

                    Extraction Source Structure
                    Extraction Source Structure                  Extraction Source Structure
                                                                 Extraction Source Structure


                    S5nn      S5nnBIW1 S5nnBIW2                  S5nn      S5nnBIW1 S5nnBIW2


                    OLTP 1: LIS Info structure
                    OLTP             structure                OLTP 2: LIS Info structure
                                                              OLTP 2: LIS Info structure

        © SAP AG 1999



n   The BW InfoSources help prepare the data that is to be updated in the Business Information
    Warehouse.
n   The InfoSource allows the system to:
         import the extracted data from the extraction structure in the SAP R/3 OLTP System
         transfer the data to the BW transfer structure using the OLTP System transfer structure
         convert the data using the transfer rules in BW and
         transfer the data to the communication structure in BW.
         The InfoSource prepares the data for permanent storage in the InfoCube.
n   In addition to the LIS info structure, two additional tables are required as extractors in the OLTP
    System for the delta upload.
    LIS Data Flow


                                                                                                  Standard
                                                                                                   analysis
                                      analysis program        analysis program




      S...                                 S001                                                 Information
                                                                   S5nn
                                                                                                   structure

                                        S001/1                 S999/XYZ
                                                                                                    Update
                                        Qty     ...            Number ...                            rules
                                        Value   ...            Value ...




                                                      MCVBAK
                                                          MCVBAP                               LIS Interface


                                                Sales Order

                                                      VBAK                              VBAP
                                                                                        VBAP    Application
                                                                                                Application
                                                                                 VBAK
                                                                                 VBAK
     Sales                                                VBAP

        © SAP AG 1999



n   The LIS data flow can be described as follows:
    Ÿ Operative transaction data (for example sales orders, billing documents) is stored in application
      data tables (e.g. VBAK/VBAP for sales orders).
    Ÿ When the data is updated in LIS, the information is transferred from an operative document to
      'communication structures' (e.g. MCVBAK, MCVBAP).
    Ÿ This information is then written from the communication structures to the corresponding
      information structures using update rules.
    Set up LIS Environment


                        BW Link for LIS Info Structures
                                             Structures


                         Information structure      S5nn
                         Display settings


                         Set up LIS environment
                         Generate DataSource
                         Delete environment/DataSource


                         Delta update in LIS
                         Activate/deactivate
                         Generate update



        © SAP AG 1999



n   Before LIS info structures can be used as source tables, you have to define several settings.
n   First, you have to configure the LIS environment for the relevant info structures.
n   To do so, choose Administrator Workbench > Modeling > Source Systems (choose the relevant
    source system and click the right mouse button) > Customizing Extractors. > Generated
    DataSources > Logistics > Logistical Informatio n System > Attach Information Structures.
n   Alternatively, you can use the transaction SBIW in R/3 or start the report RMCSBIWC.
    Set up the LIS Environment: Result


    LIS application                                LIS Environment
                                                   for BW
                                                                       Transp. Table S5nnBIW1
                 LIS Info                           S5nnBIW1
                                                                     VKORG       KUNNR      MATNR
                 Structure
                 S5nn




                                                                       Transp. Table S5nnBIW2
            Transp. Table S5nn
                                                     S5nnBIW2        VKORG       KUNNR      MATNR
       VKORG        KUNNR         MATNR




                                                                          Structure S5nnBIWS
       Sales            Sold-to   Material           S5nnBIWS
    organization         party                       (Structure)     VKORG       KUNNR      MATNR


        © SAP AG 1999



n   Once the LIS environment has been configured, two transparent tables and one structure are
    generated for this special info structure.
n   The transparent tables 'S5nnBIW1' and 'S5nnBIW2' (S5nn = customer name range for information
    structures developed in-house) are used for the delta update in BW (see end of this unit). These
    tables are identical copies of the information structure.
n   The structure 'S5nnBIWS' is adapted to meet the requirements of BW and is used as an extraction
    structure.
    Generate InfoSource


                                             Structures
                        BW Link for LIS Info Structures


                         Information structure         S5nn
                         Display settings


                         Set up LIS environment
                         Generate DataSource
                         Delete environment/DataSource


                         Delta update in LIS
                         Activate/deactivate
                         Generate update



        © SAP AG 1999



n   A DataSource must be generated so that the info structures in the OLTP System can be used as
    source tables for the BW.
n   First, the fields in the extract structure must be assigned InfoObjects.
    Generating an InfoSource: Procedure



                                                          Structure S5nnBIWS
                                     S5nnBIWS
            S5nn
                                     (Structure)     VKORG          KUNNR   MATNR




        Selecting Selection Fields




                                                                     Selection:
                                                                     l Selection fields
                                                                     l Hide fields
                                                                     l Cancellation fields




        © SAP AG 1999



n   Each time a DataSource is generated for an info structure 'S5nn' in the OLTP System, the
    DataSource '2_LIS_01_S5nn' is created in the connected BW System.
n   A maintenance screen is displayed in which you can assign other properties to the fields of the
    extract structure (S5nnBIWS).
    Ÿ Selection fields
    Ÿ Hide fields
    Ÿ Cancellation fields (field is inverted when canceled (*-1))
    Replicating DataSources




        © SAP AG 1999



n   OLTP extraction tables make up the basis of a DataSource as far as BW is concerned. In some
    application areas, you can use separate generation tools. DataSources are created from the customer-
    specific information structures in the LIS environment, in this way, an interface is established
    between LIS and BW.
n   An R/3 System connected to BW provides a variety of DataSources. These can be uploaded into BW
    by replicating them in the source system tree.
n   The DataSources are delivered in a so-called 'D version' and can be transferred to the 'A version'
    when they are activated. They can be also changed and forwarded to the 'A version' (one that
    deviates from the default).
n   If DataSources have changed in the source system (for example, when your R/3 System is upgraded),
    you can decide if you want to activate them to the 'A version', or continue using the existing ones.
n   The DataSource must be replicated before it can be used in BW.
    To do this, choose the 'Source Systems' tabstrip in the BW Administrator Workbench. Select the
    relevant OLTP system and choose Replicate DataSources from the context menu. All the
    DataSources that do not yet exist in the BW are then transferred from the OLTP to the BW System.
    Maintain Communication Structure


                                                                 All of the fields in the
                                                                    extract structure
                                                             are shown with the assigned
                                                              InfoObjects in the template.




        © SAP AG 1999



n   Communication structures are created for InfoSources and thus represent part of an application in the
    OLTP System (for example, order data from Sales, purchase order data from Purchasing, and so on).
n   The total number of InfoObjects in the communication structure and extract structure may be
    different, since InfoObjects can be copied to the communication structure from all extract structures
    (several source systems).
    Maintain Transfer Rules



                                                                             Field from
                                                                         transfer structure




       Activate




                                                           Transfer             Fixed value
                                                           routine




         © SAP AG 1999



n   Transfer rules specify which fields in the transfer structure are to be transferred to which fields in the
    communication structure. You can create detailed conversion rules to change or add to data.
n   You can only choose one of the three types of transfer rules for each InfoObject in the
    communication structure:
    Ÿ The fields are copied from the transfer structure and not modified.
    Ÿ A field in the communication structure can be supplied with a fixed value for this source system.
    Ÿ A local transfer routine is used to supply the content of the communication structure with data
      when uploaded from this source system. The routine defined only applies to the selected
      InfoObject.
n   The transfer rules do not take effect until they have been activated.
    Maintain InfoCubes and Update Rules




                                                               ...
                                                               Create InfoCube...
                                                               ...
                                    ...
                                    Create update rules...
                                    ...




        © SAP AG 1999



n   Before data can be uploaded from the OLTP System to BW and evaluated in an InfoCube, the
    InfoCube must be created with the relevant update rules.
n   You maintain InfoCubes and update rules in the Administrator Workbench, Modeling > InfoCubes.
n   Update rules are always defined for a combination of an InfoCube and InfoSource. For this reason,
    an InfoSource can update several InfoCubes. An InfoCube, however, can be linked to several
    InfoSources via update rules.
n   There are various ways of updating InfoCube key figures into the update rules. Possible: Field to
    field assignment, formula and fixed value. You can also specify which date field in the InfoSource is
    to supply the time characteristics of the InfoCube with data. Similarly, a key figure can only be
    updated under certain conditions. In the same way, a currency translation can also be triggered when
    a key figure is updated to the InfoCube.
    Extracting Application Data


    R/3 OLTP System                                                Business Information
                                                                   Warehouse




                 Transaction               Full Extract
                    Data                 or Delta Extract
                                                                              Staging
                                                                              Engine
       Master                              Full Extract
        Data                             or Delta Extract



        © SAP AG 1999



n   When application data is extracted, the mater data must be transferred first.
    It is useful if the Business Information Warehouse knows attributes in addition to the vendor number,
    for example, vendor name, address or region.
    Hierarchy information such as product hierarchy for the material, and so on, must be accessible when
    you transfer data into BW.
n   Generally speaking, the volume of transaction data is considerably higher. A full update here is
    mostly only justified for the first time data is transferred or if the statistics data has to be rebuilt
    following a system failure.
    Delta update mechanisms that restrict the volume of data to within realistic limits, therefore, are
    required to implement a performance-oriented, periodical data transfer strategy.
    Therefore, when sales figures are updated every week in the Business Information Warehouse, only
    the sales document information that has been added or changed in the last week should be extracted.
    LIS Delta Update


            BW Link for LIS Info Structures


              Information structure            S5nn
                                                                          Activate/Deactivate
              Display settings
                                                                          is switched on/off
                                                                          for delta tables
              Set up LIS environment
              Generate DataSource
              Delete environment/DataSource

                                                                2            Update program for
              Delta update in LIS                                            LIS info structure
                                                                             is regenerated
              Activate/deactivate
                                                            1
              Generate update



        © SAP AG 1999



n   Before you start a delta update request in BW, you have to make sure that the delta update process in
    the OLTP System is supported.
n   To do this, you have to activate the 'Delta updating in the LIS' setting in the report 'RMCSBIWC'.
n   The 'Activate/deactivate' radio button activates or deactivates the update function to the delta tables
    S5nnBIW1 and S5nnBIW2. The active table for the delta update is defined in the table 'TMCBIW'.
n   'Generate updating' regenerates the update program (RMCX....) and ensures that a delta update is
    possible in the delta tables (S5nnBIW1/S5nnBIW2). (For this purpose, the original LIS update
    program ‘RMCX....’ was enhanced within the FORM routines ‘form S5nnbiw1_update_....' and
    ‘form S5nnbiw2_update_....').
n   Note: the update programs for an information structure can only be regenerated if the LIS updating
    function is inactive!
n   The update is regenerated in the customer name range only.
n   Note: delta updates are client specific!
    Activating the Update



                                Update Parameters
            Document
                                Info Str. Description
        Document
                                S001     Customer
          Document              S002     Sales office
                                S003     Sales organization
                                …                                S5nn           BW training group ##

                                S5nn     BW training group ##    Period split
                                                                     Posting period
                                                                     Month
                                                                     Week
                                                                     Day

        S001
                                                                 Update
                   S002                                              No update
                                                                     Synchronous update (1)
        S003
        S003
                                                                     Asynchronous update (2)
                                                                     Asynchronous update (3)




        © SAP AG 1999



n   The InfoStructures can then only be updated when you have activated the info structures. You can do
    this in the Customizing screen of BW in the OLTP System (transaction SBIW) under Generated
    DataSources > Logistics > Logistics Information System > Activate update.
n   You must activate the associated info structures that you want to fill with data for each application in
    LIS (for example, Sales and Distribution, Purchasing).
n   You enter the period split (for example, monthly, weekly) and specify the update mode (for example,
    synchronous or asynchronous).
n   Some info structures that are shipped by SAP especially for BW have to be activated in Customizing
    under Generated InfoSources > Logistics > Transaction Data > Managing Transfer Information
    Structures > Activate/Deactivate Update Rules.
    Creating an InfoPackage




                                                                ...
                                                                Create InfoPackage... .
                                                                ...




        © SAP AG 1999



n   Data requests sent to the source system are managed with the Scheduler. These requests are
    formulated for each InfoSource and source system and are divided into master and transaction data.
n   An InfoSource in a source system can have several different extraction jobs with different selection
    criteria. These are referred to as InfoPackages.
n   InfoPackages or groups of InfoPackages can be distributed to background processes using the R/3
    job planning facility. This means that you can fully automate the data transfer process and decide
    when and at what intervals data is to be extracted. Or, for example, you can use a factory calendar to
    specify that data is not to be extracted on public holidays, and so on.
n   The term 'transaction' in the Business Information Warehouse covers data retrieval in the OLTP and
    the successful updating of this data to the relevant InfoCubes. You can monitor the transfer and
    processing of the data closely using the Monitor function in the Administrator Workbench.
n   You can compile lists containing information on InfoPackage processing for each user, source
    system, day, etc.
    Initializing the Delta Process (Scheduler)




                                                               The selected dataset in OLTP
                                                              is completely updated into
                                                              BW and the delta process is
                                                                       initialized



        © SAP AG 1999



n   If you want to transfer data in the delta process, the process must be initialized in the first data
    request. In this process, the selection conditions for connecting delta uploads are set and its complete
    dataset is loaded into BW from the R/3 System.
n   To do this, you must select the checkbox Initialize delta process for the InfoPackage under the
    update parameters of the Scheduler.
    Process: Initialization of Delta Update

      R/3 OLTP System                                               Business Information
                                                                    Warehouse


           TMC2                                          Initialization               InfoSource
                                    S5nn                Delta update               2LIS_01_S5nn
      Control table
         No
         update




                                   S5nnBIW1
         TMCBIW
      Control table
      BIW Status '1'

                                   S5nnBIW2




         © SAP AG 1999



n   When the initialization of the delta update for an InfoSource is started, all the data from the
    associated info structure in the OLTP System is uploaded to BW and fills the specified InfoCubes
    specified in the InfoSource.
n   Make sure that update of the info structure in the OLTP System is inactive. This prerequisite is only
    necessary for the initialization run.
n   If one or more selective initialization runs (selection according to plant, for example) is carried out,
    all the selection conditions must be entered in the selection screen for the subsequent delta upload.
    Monitoring the Upload Procedure




         l Monitoring data requests and data processing
         l IDoc processing status display
                n   Info IDoc
                n   Data IDoc

         l Detailed displays for selective monitoring




        © SAP AG 1999



n   Enable communication and data transfer beyond the limits of the system. These IDocs are divided
    into info IDocs and data IDocs.
n   The task of the individual info IDocs is indicated by their status: Status 0: data request received by
    source system, source system starts to select data.
    Status 1: this status indicates a data IDoc that contains further data processing information.
    ....
    Status 5: an error has occurred in the source system.
    ...
    Status 9: data selection in the OLTP System has been successfully completed.
n   With data IDocs, you can display a list of the processing steps that have been carried out to date.
    These steps are described by call numbers, such as: 50: start of update 51: determine InfoCubes to be
    updated 52: InfoCube successfully updated
    .…
    70: end of IDoc processing
    Status Display in the Monitor



                            l Status OK
             green                 n   No errors occurred
                                   n   Data successfully transferred
                            l Status not defined
            yellow                 n   Data update not completed (all IDocs)
                                   n   Invalid number of data packages (updated IDocs,
                                       process still running)
                                   n   Invalid data request (Scheduler, transfer structure not
                                       active)
                                   n   No data in source system (general view)
                            l Status not OK or
              red                  n   Data loaded incorrectly
                                   n   Status not defined after timeout
                                   n   Data only posted to incoming ALE IDoc


        © SAP AG 1999



n   The traffic light changes color depending on the context.
n   Note that a red light does not necessarily mean that an error has occurred.
    Delta Update (Scheduler)




                                       Only the data
                                       since the last upload
                                       is requested



        © SAP AG 1999



n   Generally speaking, the volume of transaction data is considerably higher.
n   Delta update mechanisms that restrict the volume of data to within realistic limits, therefore, are
    required to implement a performance-oriented, periodical data transfer strategy.
    Therefore, when sales figures are updated every week in the Business Information Warehouse, only
    the sales document information that has been added or changed in the last week should be extracted.
n   In this case, you have to activate the 'Delta Update' checkbox for the InfoPackage in the updating
    parameters of the Scheduler.
    Process: First Delta Update

      R/3 OLTP System                                              Business Information
                                                                   Warehouse


                                      S5nn
                                                                                     InfoSource
                                                                                  2LIS_01_S5nn
                                                                 ate
                                                              upd
                                                          lta
                                                        De
       LIS update                                    1.
        process
                                  S5nnBIW1




          TMCBIW
       Control table
                                   S5nnBIW2
       BIW Status '2'



        © SAP AG 1999



n   When you start the delta update process from the OLTP to the BW, the tables S5nnnBIW1 and
    S5nnBIW2 are used.
n   The info structure in the OLTP is active. The data from S5nnBIW1 is transferred to the BW for the
    first delta update.
n   While the first delta update to the BW is being carried out, the LIS update process updates the LIS
    info structure in the OLTP system as well as the table S5nnBIW2, which is then used for the second
    delta update request to the BW.
n   At the start of each delta update request, the system switches between the S5nnBIW1 and S5nnBIW2
    tables to prevent inconsistencies while the data is being uploaded to BW. (The 'BIW status' flag in
    the 'TMCBIW' table on the OLTP system is automatically changed from 1 (for table S5nnBIW1) to 2
    (for table S5nnBIW2) during the delta update to BW.)
n   The data in a delta table remains in the table until the next delta upload to ensure that the data can be
    reloaded up to that point.
Process: Second Delta Update

 R/3 OLTP System                            Business Information
                                            Warehouse


                     S5nn
                                                        InfoSource
                                                     2LIS_01_S5nn




                                           ate
 LIS update




                                         pd
                   S5nnBIW1




                                       -U
  process




                                    lta
                                  De
    TMCBIW                     2.
 Control table
                   S5nnBIW2
  BIW Status '1'



   © SAP AG 1999
Individual Steps in LIS Extraction


                                      10. InfoPackage for the delta upload

                                  9. InfoPackage for the delta initialization

                              8. Activate delta update in LIS

                          7. Generate update of the LIS info structure

                      6. Maintain InfoCubes and update rules

                   5. Maintain transfer rules

               4. Maintain communication structure

           3. Replicate/assign DataSources

      2. Generate DataSources in the OLTP System

  1. Set up LIS environment

   © SAP AG 1999
LIS Data Extraction: Unit Summary



                  You are now able to:
                  l Prepare info structures in the R/3 source system,

                  l Maintain the communication structure and
                     transfer rules for an InfoSource,
                  l Build an InfoCube and maintain update rules,

                  l Supply an InfoCube with data using the delta
                     update method.




  © SAP AG 1999
LIS Data Extraction - Exercises


                Unit:     LIS Data Extraction
                Topic:          Linking Info Structures to BW



  1-1   To transfer the data from your LIS info structure to BW, you first have to prepare it
        for extraction from the info structure. Use the following number range for your info
        structure:

        Group numbers 00 to 24
        Info structure: S850 - S874
        Example:        Group 01 è S### = S851
                               Group 24 è S### = S874

        Group numbers 25 to 49
        Info structure: S930 – S955
        Example:        Group 26 è S### = S931
                               Group 31 è S### = S936
        1-1-1 In the Source System tab in Administrator Workbench, right-click
              T90CLNT090 and choose ‘Customizing for R/3 extractors…’ to call up the
              Implementation Guide for the SAP OLTP source system.

        1-1-2 Display the current settings for the link between your information structure
              and the Business Information Warehouse. What information is contained in
              the log?
               __________________________________________________________
               __________________________________________________________
               __________________________________________________________


                Field name                     Enter
                Information structure          S###
                Display settings               ü


        1-1-3 Set up the LIS environment for your info structure S###.
                Field name                     Enter
                Information structure          S###
                Set up LIS Environment         ü
      1-1-4 What happens after you have configured your LIS environment?
             __________________________________________________________
             __________________________________________________________
             __________________________________________________________
             __________________________________________________________
             __________________________________________________________


      1-1-5 Now generate the DataSource for your information structure S###. Copy the
            format of the selection fields; in the screen ‘InfoObject Assignment’, assign
            a corresponding InfoObject to every field in the DataSource. To do this,
            select all of the fields and assign the existing InfoObjects according to the
            same data elements. Check for assignment errors.
              Field name                    Enter
              Information structure         S###
              Generate DataSource           ü


      1-1-6 What information is contained in the log?
             __________________________________________________________
             __________________________________________________________
             __________________________________________________________



1-2   Once you have defined your DataSource at OLTP level, we can transfer the
      information to the BW System by means of replicating the DataSource, and
      maintaining the communication structure and transfer rules.
      1-2-1 To do so, choose the ‘T90CLNT090’ source system in the Administrator
            Workbench/Source systems and upload the Metadata in the foreground.
      1-2-2 Find your DataSource 2LIS_02_S### and create the InfoSource for the
            DataSource.

              Field name                    Enter
              Search string


              Field name                    Enter
              other                         ü
              InfoSource                    GR##_2LIS_02_MM
             Create
              Field name                    Enter
              InfoSource                    GR##_2LIS_02_MM
                                      m
        Long description              Gr##: InfoSource LIS
        InfoSource template


1-2-3 Now maintain your communication structure. This structure is filled with
      data from the source system using the transfer rules from the transfer
      structure. All of the fields from the InfoSource are proposed in the template.
      Copy all of these fields and activate the communication structure.

1-2-4 Then maintain the transfer rules for the assigned source system
      ‘T90CLNT090’ of your InfoSource.

             Note that only the period concept ‘day’ is updated in your LIS info
             structure S###. If you want the ‘Week’ and ‘Month’ to be filled out
             in the BW InfoCube, the period must be converted in the transfer
             rules. For this reason, you have to specify special transfer routines
             for the ‘0CALWEEK’ (calendar year / week) and ‘0CALMONTH’
             (calendar year / month) InfoObjects.


1-2-5 Create a transfer routine called ‘Week_from_day GR##’ for the InfoObject
      ‘0CALWEEK’. In this case, the calendar week is to be determined from the
      calendar day using the ‘DATE_GET_WEEK’ function module.

        Field name                    Enter
        Name                          Week_from_day GR##
       Enter the following ABAP 4 code.
       Check and save your routine.
1-2-6 Create a transfer routine called ‘Month_from_day GR##’ for the InfoObject
      ‘0CALMONTH’. In this case, the calendar month is to be determined from
      the calendar day field.

        Field name                    Enter
        Name                          Month_from_day GR##
       Enter the following ABAP 4 code.
       Check and save your routine.
1-2-7 Save and activate your transfer rules.
1-3   In the next step, you will create an InfoCube that is to contain data from the
      generated InfoSource.
      1-3-1 Before you create the InfoCube, create an InfoArea ‘IAGR##’ with the long
            description ‘InfoArea GR##’ under ‘Unassigned node(s) è ‘BW training’
            è ‘BW220 BW – OLTP Extraction’.

               Field name                    Enter
               InfoArea                      IAGR##
               Description                   InfoArea GR##


      1-3-2 Then create an InfoCube LISCUBE## with the description ‘GR## LIS
            Cube’ in the InfoArea with the name ‘InfoArea GR##’.

               Field name                    Enter
               InfoCube                      LISCUBE##
               Description                   GR## LIS Cube


      1-3-3 In the ‘Characteristics’ tab of your InfoCube, choose all the characteristics
            for the InfoSource ‘GRxx_2LIS_02_MM’ and copy all the InfoObjects to
            your InfoCube structure with the exception of ‘0REVERSEDOC’ and
            ‘0VTYPE’.

      1-3-4 Distribute the characteristics of your InfoCube among the dimension tables
            as follows:
               Dimension                        Characteristics
               Vendor                           0VENDOR
               Material                         0MATERIAL material number
               Purchasing area                  0PURCH_ORG Purchasing organization
                                                0MATL_GROUP Material group
               Version                          0VERSION: Version
               Plant                            0PLANT plant


               Field name                    Long description
               LISCUBE##1                    Vendor

             Choose ‘Create’
               Field name                    Long description
               LISCUBE##2                    Plant
             Choose ‘Create’
        Field name                    Long description
        LISCUBE##3                    Material
       Choose ‘Create’
        Field name                    Long description
        LISCUBE##4                    Purchasing area
       Choose ‘Create’
        Field name                    Long description
        LISCUBE##5                    Version


1-3-5 Under key figures, choose the InfoSource ‘GRxx_2LIS_02_MM‘ as a
      template and copy all of the key figures to the InfoCube structure.

1-3-6 Under time characteristics, select ‘Calendar day’, ‘Calendar year / week’,
      and ‘Calendar year / month’.

1-3-7 Check your InfoCube and activate it.

1-3-8 Create update rules for the InfoSource ‘GRxx_2LIS_02_MM’ of your
      InfoCube. You should not need to define any settings here. Check and
      activate the update rules.

        Field name          Enter
        InfoSource
              Unit:      LIS Data Extraction
              Topic:          Filling InfoCubes



1-4   To fill the InfoCube with data, you must first set up the delta update function in the
      OLTP System. A delta initialization run then updates the data from the info
      structure to the BW.
      1-4-1 On the Source System tab in Administrator Workbench, right-click
            T90CLN T090 and choose ‘Customizing for R/3 extractors…’ to call up the
            Implementation Guide for the SAP OLTP source system.

      1-4-2 Generate the delta update for your information structure S###. Describe the
            features of the update programs of the information structure.

               Field name                     Enter
               Information structure          S###
               Generate update                ü


      1-4-3 Once it has been generated, activate the delta update. What settings are
            made by this report?
               Field name                     Enter
               Information structure          S###
               Activate/deactivate            ü


      1-4-4 Then load the data from your info structure from the OLTP system to the
            BW System. To do so, create an InfoPackage with the name ‘Delta
            initialization’ for your InfoSource ‘GRxx_2LIS_02_MM’ and the source
            system ‘T90CLNT090’. Make sure that the update mode is set to
            ‘Initialization of delta procedure’. Schedule the InfoPackage to be loaded
            immediately. Use the Monitor function to monitor the data loading process.

               Field name                     Enter
               Name                           Delta initialization
             ‘Update parameters’ tab
               Field name                             Enter
               Initialization of the delta process    ü
             ‘Schedule’ tab
              Field name                              Enter
              Start loading data immediately          ü


      1-4-5 Once the data has been successfully loaded, you can take a closer look at the
            data in the InfoCube. To do so, choose the ‘Maintain InfoCube content’
            functio n in the InfoCube tab.

1-5   Once you have completed the delta initialization procedure for your InfoSource,
      you can carry out a delta update. To do so, you have to create a purchasing
      document (purchase order) in the OLTP to fill your info structure.
      1-5-1 First, however, you have to activate the info structure for the update
            procedure in the OLTP System so that the data is can be updated to the info
            structure. To do so, choose the asynchronous V2 update.

              Field name                         Enter
              Asynchronous update (2)            ü
      1-5-2 Create a purchase order document with the following data in the OLTP
            System.
              Field name                       Enter
              Company code                     1000
              Vendor                           R1005
              Document type                    NPO (normal purchase order)
              Purchasing organization          1000
              Purchasing group                 026
              Plant                            1200
              Storage location                 0001
              Material                         M-01, M-02, M-03......M-20
              Purchase order quantity          100


      1-5-3 Which control table is updated in the OLTP for BW delta extraction? Take a
            look at the contents of the table using transaction ‘SE16’.
             Transaction ‘SE16’

              Field name                         Enter
              Table name                         TMCBIW


              Field name                         Enter
              Info structure                     S###
        Field name                            Enter
        Table name                            S###BIW1
1-5-4 Now carry out a delta update in the BW System. To do so, create a new
      InfoPackage with the name ‘Delta update’ for your InfoSource
      ‘GR##_2LIS_02_MM’ and the source system ‘T90CLNT090’. Make sure
      that the update mode is set to ‘Delta update’. Schedule the InfoPackage to
      be loaded immediately. Use the Monitor function to monitor the data
      loading process.

        Field name                       Enter
        Long description                 Delta update


        Field name                               Enter
        Delta Update                             ü


        Field name                               Enter
        Instant loading of data online           ü
1-5-5 Once the data has been successfully loaded, you can take a look at the data
      in the InfoCube again. To do so, choose the ‘Maintain InfoCube content’
      function in the InfoCube tab. Take a look at the request that was created by
      the delta update.

        Field name            Enter
        RequestID (SID)       Enter the request ID ‘Delta Update’ from
                              the previous screen.
1-5-6 Check the settings in the control table ‘TMCBIW’ in the OLTP System.
      What has cha nged?

        Field name                            Enter
        Table name                            TMCBIW


        Field name                            Enter
        Info structure                        S###
1-5-7 Check the contents of the table ‘S###BIW1’. How do you explain the
      contents of the table?
       Transaction ‘SE16’
        Field name                            Enter
        Table name                            S###BIW1
LIS Data Extraction - Solutions


                  Unit:     LIS Data Extraction
                  Topic:          Linking Info Structures to BW



   1-1    To transfer the data from your LIS info structure to BW, you first have to prepare it
          for extraction from the info structure. Use the following number range for your info
          structure:

          Group numbers 00 to 24
          Info structure: S850 - S874
          Example:        Group 01 è S### = S851
                                 Group 24 è S### = S874

          Group numbers 25 to 49
          Info structure: S930 – S955
          Example:        Group 26 è S### = S931
                                 Group 31 è S### = S936
          1-1-1 In the Source System tab in Administrator Workbench, right-click
                T90CLNT090 and choose ‘Customizing for R/3 extractors…’ to call up the
                Implementation Guide for the SAP OLTP source system.
                 BW Administration è Administrator Workbench è Source Systems
                 Context menu (right mouse button) on source system ‘T90CLNT090‘ è
                 Extractor Customizing...
          1-1-2 Display the current settings for the link between your information structure
                and the Business Information Warehouse. What information is contained in
                the log?
                 Business Information Warehouse è Customer Defined DataSources è
                 Logistics è Logistics Information System è Attach Information
                 Structures

                  Field name                     Enter
                  Information structure          S###
                  Display settings               ü
                 Execute
                 010 Settings for Business Information Warehouse Customizing
                 011 Information structure: S###
                 013 LIS environment has not been set up.
                 003 InfoSource 2LIS_02_S### has not been generated.
          1-1-3 Set up the LIS environment for your info structure S###.
              Field name                    Enter
              Information structure         S###
              Set up LIS Environment        ü
             Execute
      1-1-4 What happens after you have configured your LIS environment?
             Once you have set up the LIS environment, 2 transparent tables and one
             extract structure are generated for this special info structure. You can
             display the tables ‘S###BIW1’, ‘S###BIW2’, and the structure
             ‘S###BIWS’ in the OLTP with transaction SE11.
      1-1-5 Now generate the DataSource for your information structure S###. Copy the
            format of the selection fields; in the screen ‘InfoObject Assignment’, assign
            a corresponding InfoObject to every field in the DataSource. To do this,
            select all of the fields and assign the existing InfoObjects according to the
            same data elements. Check for assignment errors.
              Field name                    Enter
              Information structure         S###
              Generate DataSource           ü
             Execute
             Save
             Answer the question ‘12B BW Systems connected, generate 12B
             Metadata?’ with NO.


      1-1-6 What information is contained in the log?


             010 Settings for Business Information Warehouse Customizing
             011 Information structure: S###
             017 DataSource 2LIS_01_S### has been generated successfully.




1-2   Once you have defined your DataSource at OLTP level, we can transfer the
      information to the BW System by means of replicating the DataSource, and
      maintaining the communication structure and transfer rules.
      1-2-1 To do so, choose the ‘T90CLNT090’ source system in the Administrator
            Workbench/Source systems and upload the Metadata in the foreground.
             BW Administration è Administrator Workbench è Source Systems
             Context menu (right mouse button) on source system ‘T90CLNT090‘ è
             DataSource Overview è Application Component MM è Replicate
             DataSources
1-2-2 Find your DataSource 2LIS_02_S### and create the InfoSource for the
      DataSource.
       Administrator Workbench è Source Systems

       Context menu (right mouse button) on source system ‘T90CLNT090‘ è
       DataSource Overview.

       Select the ‘T90CLNT090 list

       Find
        Field name                    Enter
        Search string                 2LIS_02_Sxxx

       Find
       Expand the tree
       Context menu (right mouse button) on DataSource ‘2LIS_01_S###‘ è
       Assign InfoSource.
        Field name                    Enter
        other                         ü
        InfoSource                    GR##_2LIS_02_MM
       Create
        Field name                    Enter
        InfoSource                    GR##_2LIS_02_MM
                                      m
        Long description              Gr##: InfoSource LIS
        InfoSource template
       Return key

       Confirm the message ‘Assign Data Source ‘2_LIS_02_S###’ to
       InfoSource ‘GRxx_2_LIS_02_MM’ with Yes.
1-2-3 Now maintain your communication structure. This structure is filled with
      data from the source system using the transfer rules from the transfer
      structure. All of the fields from the InfoSource are proposed in the template.
      Copy all of these fields and activate the communication structure.
       Context menu (right mouse button) on the InfoSource
       ’GRxx_2_LIS_02_MM‘ è Maintain update rules.

       Choose ‘Expand communication struct ure’
       Copy all InfoObjects
       Activate
1-2-4 Then maintain the transfer rules for the assigned source system
      ‘T90CLNT090’ of your InfoSource.
       Context menu (right mouse button) on source system ‘T90CLNT090‘ è
       Change transfer rules.
             Note that only the period concept ‘day’ is updated in your LIS info
             structure S###. If you want the ‘Week’ and ‘Month’ to be filled out
             in the BW InfoCube, the period must be converted in the transfer
             rules. For this reason, you have to specify special transfer rout ines
             for the ‘0CALWEEK’ (calendar year / week) and ‘0CALMONTH’
             (calendar year / month) InfoObjects.
1-2-5 Create a transfer routine called ‘Week_from_day GR##’ for the InfoObject
      ‘0CALWEEK’. In this case, the calendar week is to be determined from the
      calendar day using the ‘DATE_GET_WEEK’ function module.
       Select the ‘Calendar year / week’ row
       Choose the pushbutton ’TP‘
       Then choose the pushbutton         ‚‘Local routine‘and choose ‘create‘

       Confirm the message ‘Check the dependency of the routines from the
       transfer structure‘ and select the InfoObject ‘0CALDAY’ in the next
       screen, then confirm.

       Local transfer routine

        Field name                     Enter
        Name                           Week_from_day GR##
       Enter
       Position the cursor in row 790
       Add 7 rows
       Enter the following ABAP 4 code.
        0770 *$*$ begin of routine - insert your code only below this line    *-*
         790 call function 'DATE_GET_WEEK'
         800    exporting
         810      date       = tran_structure-sptag
         820    importing
         830      week       = result
         840    exceptions
         850      date_invalid = 1
         860      others     = 2.
         870 * Return code <> 0 means skip whole data package !!!
       880 returncode = 0.
       890 *$*$ end of routine - insert your code only before this line    *-*
       Check and save your routine.
       Check
             Save
      1-2-6 Create a transfer routine called ‘Month_from_day GR##’ for the InfoObject
            ‘0CALMONTH’. In this case, the calendar month is to be determined from
            the calendar day field.
             Select the row ‘calendar year/month’‘
             Then choose the pushbutton      ‚‘Local routine‘and choose ‘create‘

             Confirm the message ‘Check the dependency of the routines from the
             transfer structure‘ and select the InfoObject ‘0CALDAY’ in the next
             screen, then confirm.
             Local transfer routine
               Field name                    Enter
               Name                          Month_from_day GR##
             Enter
             Enter the following ABAP 4 code.
              770 *$ begin of routine - insert your code only below this line      *-*
              800 result = tran_structure-sptag(6).
              810 * Return code <> 0 means skip whole data package !!!
              820 returncode = 0.
              850 *$*$ end of routine - insert your code only before this line         *-*
             Check and save your routine.
             Check
             Save
      1-2-7 Save and activate your transfer rules.
             Save
             Activate

1-3   In the next step, you will create an InfoCube that is to contain data from the
      generated InfoSource.
      1-3-1 Before you create the InfoCube, create an InfoArea ‘IAGR##’ with the long
            description ‘InfoArea GR##’ under ‘Unassigned node(s) è ‘BW training’
            è ‘BW220 BW – OLTP Extraction’.
             BW Administration è Administrator Workbench è Data Targets
             Expand ‘Unassigned node(s)’ è ‘BW training’ in the hierarchy tree
             Context menu (right mouse button) on InfoArea ‘BW220 BW – OLTP
             Extraction’ è Create InfoArea...

               Field name                    Enter
               InfoArea                      IAGR##
               Description                   InfoArea GR##
             Enter
1-3-2 Then create an InfoCube LISCUBE## with the description ‘GR## LIS
      Cube’ in the InfoArea with the name ‘InfoArea GR##’.
       Context menu (right mouse button) on InfoArea ‘InfoArea GR##’ è
       Create InfoCube...
        Field name                     Enter
        InfoCube                       LISCUBE##
        Description                    GR## LIS Cube

       Choose ‘BasicCube’ as the InfoCube type
       Create .
1-3-3 In the ‘Characteristics’ tab of your InfoCube, choose all the characteristics
      for the InfoSource ‘GRxx_2LIS_02_MM’ and copy all the InfoObjects to
      your InfoCube structure with the exception of ‘0REVERSEDOC’ and
      ‘0VTYPE’.
       InfoSource
       Choose the application ‘Material Management (MM’.
       Place the cursor on InfoSource ‘GRxx_2LIS_02_MM’
       Enter
       Choose ‘No’
       Select all    ‘
       Deselect ‘0REVERSEDOC’ and ‘0VTYPE’
       Copy fields
1-3-4 Distribute the characteristics of your InfoCube among the dimension tables
      as follows:
         Dimension                        Characteristics
         Vendor                           0VENDOR
         Material                         0MATERIAL material number
         Purchasing area                  0PURCH_ORG Purchasing organization
                                          0MATL_GROUP Material group
         Version                          0VERSION: Version
         Plant                            0PLANT plant
       ‘Dimension’ pushbutton in the characteristics tab
       Choose ‘Create’
        Field name                     Long description
        LISCUBE##1                     Vendor

       Choose ‘Create’
        Field name                     Long description
        LISCUBE##2                     Plant
       Choose ‘Create’
        Field name                    Long description
        LISCUBE##3                    Material
       Choose ‘Create’
        Field name                    Long description
        LISCUBE##4                    Purchasing area
       Choose ‘Create’
        Field name                    Long description
        LISCUBE##5                    Version
       ‘Assign’ tab
       Select 0VENDOR è place cursor on the dimension vendorè Choose
       ‘Assign’
       Select 0PLANT è place cursor on the dimension plant è Choose
       ‘Assign’
       Select 0MATERIAL è cursor on the dimension material è Choose
       ‘Assign’
       Select 0PURCH_ORG, 0MATL_GROUP è cursor on the dimension
       purchasing area ### Choose ‘Assign’
       Select 0VERSION è place cursor on the dimension value/version è
       Choose ‘Assign’
       Continue
1-3-5 Under key figures, choose the InfoSource ‘GRxx_2LIS_02_MM‘ as a
      template and copy all of the key figures to the InfoCube structure.
       ‘Key figures’ tab
       InfoSource
       Select the application ‘Material Management MM’.
       Place the cursor on InfoSource ‘GRxx_2LIS_02_MM’
       Continue
       Choose ‘Yes’
1-3-6 Under time characteristics, select ‘Calendar day’, ‘Calendar year / week’,
      and ‘Calendar year / month’.
       ‘Time characteristics’ tab
       InfoSource
       Place the cursor on InfoSource ‘GRxx_2LIS_02_MM’
       Continue
       Choose ‘No’
       Select ‘0CALDAY’, ‘0CALWEEK’, and ‘0CALMONTH’ fields
       Copy fields
1-3-7 Check your InfoCube and activate it.
       Check
             Activate
      1-3-8 Create update rules for the InfoSource ‘GRxx_2LIS_02_MM’ of your
            InfoCube. You should not need to define any settings here. Check and
            activate the update rules.
              Context menu (right mouse button) on InfoCube ‘GR## LIS Cube’ è
              Create update rules...
               Field name          Enter
               InfoSource          ‚GRxx_2LIS_02_MM’
              Enter
             Check
             Activate




               Unit:     LIS Data Extraction
               Topic: Filling InfoCubes



1-4   To fill the InfoCube with data, you mus t first set up the delta update function in the
      OLTP System. A delta initialization run then updates the data from the info
      structure to the BW.
      1-4-1 On the Source System tab in Administrator Workbench, right-click
            T90CLNT090 and choose ‘Customizing for R/3 extractors…’ to call up the
            Implementation Guide for the SAP OLTP source system.
              BW Administration è Administrator Workbench è Source Systems
              Context menu (right mouse button) on source system ‘T90CLNT090’ è
              Customizing for R/3 extractors
      1-4-2 Generate the delta update for your information structure S###. Describe the
            features of the update programs of the information structure.
              In the OLTP è Business Information Warehouse è Customer-defined
              InfoSources è Logistics è Logistics Information System è Connect
              Information Structures

               Field name                     Enter
               Information structure          S###
               Generate update                ü
              Execute
              The update programs have been regenerated and extended to include the
              delta update for the BW. You can take a look at a program by placing the
              cursor on the program name and clicking the ‘Generated object’ button.
1-4-3 Once it has been generated, activate the delta update. What settings are
      made by this report?
        Field name                    Enter
        Information structure         S###
        Activate/deactivate           ü
       Execute
       The OLTP system has created an entry in the ‘TMCBIW’ control table
       automatically. Using transaction ‘SE16’ in the OLTP System, you can see
       that the ‘BIW active’ field for your info structure now has the value ‘X’
       and the ‘BIW status’ field has the value ‘1’ (refers to table S###BIW1).
1-4-4 Then load the data from your info structure from the OLTP system to the
      BW System. To do so, create an InfoPackage with the name ‘Delta
      initialization’ for your InfoSource ‘GRxx_2LIS_02_MM’ and the source
      system ‘T90CLNT090’. Make sure tha t the update mode is set to
      ‘Initialization of delta procedure’. Schedule the InfoPackage to be loaded
      immediately. Use the Monitor function to monitor the data loading process.
       BW-Administration è Administrator Workbench è InfoSources è
       Expand ‘Application component’ è ‘Material Management’ è
       ‘GRxx_2LIS_02_MM’
       Context menu (right mouse button) on source system ‘T90CLNT090‘ è
       Create InfoPackage....

        Field name                    Enter
        Name                          Delta initialization
       Enter       /Save
       ‘Update parameters’ tab
        Field name                            Enter
        Initialize delta process              ü
       ‘Schedule’ tab
        Field name                            Enter
        Start loading data immediately        ü
       Choose ‘Start’
       Monitor
       Check the Monitor to see if your request was loaded successfully
      1-4-5 Once the data has been successfully loaded, you can take a closer look at the
            data in the InfoCube. To do so, choose the ‘Maintain InfoCube content’
            function in the InfoCube tab.
             BW Administration è Administrator Workbench è Data Targets
             Expand ‘Unassigned node(s)’ è ‘BW Training’ è ‘BW220 BW – OLTP
             Extraction’ è ‘InfoArea GR##’ in the hierarchy tree
             Context menu (right mouse button) on InfoCube ‘GR## LIS Cube’ è
             Manage.
             Select your InfoCube
             Choose ‘Contents’
             Using the ‘Field selection for output’ button, choose the fields that are to
             appear in the result.
             Execute

1-5   Once you have completed the delta initialization procedure for your InfoSource,
      you can carry out a delta update. To do so, you have to create a purchasing
      document (purchase order) in the OLTP to fill your info structure.
      1-5-1 First, however, you have to activate the info structure for the update
            procedure in the OLTP System so that the data is can be updated to the info
            structure. To do so, choose the asynchronous V2 update.
             BW Administration è Administrator Workbench è Source Systems
             Context menu (right mouse button) on source system ‘T90CLNT090‘ è
             Extractor Customizing....
             In the OLTP è Business Information Warehouse è Customer-defined
             DataSources è Logistics è Logistics Information System è Activate
             Update
             Place cursor on Purchasingè Choose ‘Select’
             Place the cursor on the info structure S### è Choose ‘Select’

              Field name                         Enter
              Asynchronous update (2)            ü
             Enter
             Save
      1-5-2 Create a purchase order document with the following data in the OLTP
            System.
              Field name                       Enter
              Company code                     1000
              Vendor                           R1005
              Document type                    NPO (normal purchase order)
              Purchasing organization          1000
              Purchasing group                 026
        Plant                           1200
        Storage location                0001
        Material                        M-01, M-02, M-03......M-20
        Purchase order quantity         100


       OLTP System è Logistics è Material Management è Purchasing è
       Purchase orders è Create è Vendor/Vendor plant known
       Create the purchase order with the values specified above.
       Save
1-5-3 Which control table is updated in the OLTP for BW delta extraction? Take a
      look at the contents of the table using transaction ‘SE16’.
       Display the contents of the control table ‘TMCBIW’ for your info
       structure ‘S###’.
       Transaction ‘SE16’
        Field name                         Enter
        Table name                         TMCBIW
       Enter
        Field name                         Enter
        Info structure                     S###
       Execute
       The ‘BIW status’ field contains the value ‘1’, which means that the table
       ‘S###BIW1’ will be updated.
       Transaction ‘SE16’

        Field name                         Enter
        Table name                         S###BIW1
       Enter
       Execute
       All the purchase documents that are new since the last time the update
       was activated in the OLTP System are updated in the table.
1-5-4 Now carry out a delta update in the BW System. To do so, create a new
      InfoPackage with the name ‘Delta update’ for your InfoSource
      ‘GR##_2LIS_02_MM’ and the source system ‘T90CLNT090’. Make sure
      that the update mode is set to ‘Delta update’. Schedule the InfoPackage to
      be loaded immediately. Use the Monitor function to monitor the data
      loading process.
       BW-Administration è Administrator Workbench è InfoSource è
       Expand ‘Application component’ è ‘Material Management’ è ‘BW
       Training Group 02’
       Context menu (right mouse button) on source system ‘T90CLNT090‘ è
       Create InfoPackage....

        Field name                       Enter
        Long description                 Delta update
       Enter       /Save
        ‘Update parameters’ tab
        Field name                               Enter
        Delta Update                             ü
       ‘Schedule’ tab
        Field name                               Enter
        Instant loading of data online           ü
       Choose ‘Start’
       Monitor
       Choose ‘Execute’
1-5-5 Once the data has been successfully loaded, you can take a look at the data
      in the InfoCube again. To do so, choose the ‘Maintain InfoCube content’
      function in the InfoCube tab. Take a look at the request that was created by
      the delta update.
       BW Server è Administrator Workbench è Data Targets
       Expand ‘Unassigned node(s)’ è ‘BW Training’ è ‘BW220 BW – OLTP
       Extraction’ è ‘InfoArea GR##’ in the hierarchy tree
       Context menu (right mouse button) on InfoCube ‘GR## LIS Cube’ è
       Manage.
       Select your InfoCube
       Choose ‘InfoCube content’

        Field name            Enter
        RequestID (SID)       Enter the request ID ‘Delta Update’ from
                              the previous screen.
       Using the ‘Field selection for output’ button, choose the fields that are to
       appear in the result.
       Execute
1-5-6 Check the settings in the control table ‘TMCBIW’ in the OLTP System.
      What has changed?
       In the OLTP System è Choose transaction ‘SE16’
        Field name                            Enter
        Table name                            TMCBIW
       Enter

        Field name                            Enter
        Info structure                      S###
       Execute
       The ‘BIW status’ field now has the value ‘2’. This means that the table
       ‘S###BIW2’ is now updated.
1-5-7 Check the contents of the table ‘S###BIW1’. How do you explain the
      contents of the table?
       Transaction ‘SE16’
        Field name                          Enter
        Table name                          S###BIW1
       Enter
       Execute
       All the information on the updated purchase documents in the delta
       upload is still contained in the file. This information is not deleted until
       the next delta upload to the file ‘S###BIW2’. For safety reasons, the
       contents of the table are not deleted until this is required.
LO Data Extraction



                      BW Overview -              Tools for Generic
                     SAP R/3 Extraction           Data Extraction

                                                    Enhancing
                     LIS Data Extraction
                                                  Business Content

                                                  Special Topics:
                     LO Data Extraction
                                                 Delta Management

                                               Excursus: OLTP Access
                   Extraction from CO-PA
                                                  via Remote Cubes


                  Data Extraction from FI-SL




  © SAP AG 2001
LO Data Extraction



      Contents:
       l BW Customizing Cockpit
       l Comparing LO extraction with LIS extraction
       l Converting data extraction from LIS to LO method




  © SAP AG 1999
LO Data Extraction: Unit Objectives



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

                   l Make the settings you need for extracting in the 'LO-
                     BW Customizing Cockpit' of the R/3 System
                   l Display the different data extraction options in
                     Logistics and name the advantages of LO compared
                     to the LIS methods
                   l Take the necessary steps in converting from transfer
                     structure extraction to LO extraction.




   © SAP AG 1999
    LO Data Extraction: Overview Diagram


                                              Extractor types

                      Application-specific                            Cross-application


           BW Content                     Generic
                                          Generic                           Generic
            extractors                   extractors
                                         extractors                        extractors

                 FI                       LIS                                database
                        CO                                                  table/view
               HR
                      ...                       FI-SL
                                                                           SAP Query
             LO Cockpit                         CO-PA


             transparent                 transparent
                                                                          data source
                 table                      table

                                             enhancements
                                             enhancements

        © SAP AG 1999



n   The transaction data entering the Business Information Warehouse by means of extractors originates
    from very different modules. Due to past developments, very different extraction mechanisms are
    necessary.
LO Data Extraction: Business Scenario



                  l Your company uses the previous SD data extraction
                    with the LIS transfer structures S26*; the extraction
                    must be converted to the new LO extractor.
                    You are responsible for extractor conversion - you
                    still want the reports to be available in the BW
                    system.




  © SAP AG 1999
LO Data Extraction: Data Flow into the BW System


Sales  Communication Extract
document structure   structure         Data/InfoSource   Cubes & Queries

                          MC11VA0HDR     2LIS_11_VAHDR
Customer        MCVBAK    MC11VA0ITM     2LIS_11_VAITM
                                                            0SD_C04
  order             ...   MC11VA0SCL     2LIS_11_VASCL
                                                          0SD_C04
                          MC11V_0ITM     2LIS_11_V_ITM
                          MC11V_0SCL     2LIS_11_V_SCL     0SD_C05

                MCLIKP    MC12VC0HDR     2LIS_12_VCHDR
 Delivery
                    ...   MC12VC0ITM     2LIS_12_VCITM     0SD_C03
                          MC12VC0SCL     2LIS_12_VCSCL

               MCVBRK     MC13VD0HDR     2LIS_13_VDHDR
 Billing
                 ...      MC13VD0ITM     2LIS_13_VDITM


                                       R/3    BW
    © SAP AG 1999
LO Extraction: IMG (SBIW)




                            • Customizing Cockpit:
                                   LBWE

                            • BW Log:
                                  LBWF

                            • Delete setup tables:
                              LBWG

                            • Initialization/setup:
                                      OLI*BW


  © SAP AG 1999
    Logistics Extract Structure - Customizing Cockpit


                                                                             l   Extract structure
                                                                                 maintenance:
                                                                                   l   Field selection
                                                                                   l   Creating new fields


                                                                             l   DataSource
                                                                                 maintenance


                                                                             l   Activate the extract
                                                                                 structures


                                                                             l   Set up V3 update




          © SAP AG 1999



n   The Logistics Customizing Cockpit is the central administration tool for extract structures, which
    you use to transfer Logistics transaction data of the tool from OLTP into BW. The extract structures
    are filled with the communication structures of the individual Logistics applications.
n   The Cockpit contains the following functionality, as specified in the procedure sequence:
    n   Maintaining extract structures
    n   Maintaining DataSources
    n   Activating the update
    n   Controlling V3 update
    Maintaining the Extract Structure


                                                                                l   Extract structure
                                                                                    maintenance:
                                                                                      l   Field selection
                                                                                      l   Creating new fields




         © SAP AG 1999



n   The extract structure is filled with the assigned communication structures. You can only use selected
    fields from the communication structures (SAP internal control fields, for example, are not offered).
n   SAP already delivers extract structures, which you can enhance (by connecting to the communication
    structure). Every extract structure can be maintained by you and by SAP.
n   After you set up the extract structure, the system automatically generates it. This completes missing
    fields (their units and characteristics). The extract structure is created hierarchically according to the
    communication structures. Every communication structure leads to the generation of a substructure
    that belongs to the actual extract structure.
    Maintaining DataSources




                                                                             l   Maintain DataSource




        © SAP AG 1999



n   At this point, call up the general maintenance screen for DataSources by selecting the extract
    structure fields that you want to transfer into the BW System. This selection forms the basis for the
    generating process of the DataSource.
    Maintaining DataSources: Procedure


Communication structures                                                        Extract structure
                                               Structure MC11VA0ITM
              MCVBAK                        VKORG       KUNNR       MATNR
                    MCVBAP



           Selecting Selection Fields
           Selecting Selection Fields




                                                                       Selection:
                                                                       l Selection fields
                                                                       l Hide fields
                                                                       l Cancellation fields




        © SAP AG 1999



n   There is a DataSource (for example ‘2LIS_11_VAITM‘) for each extract structure that is made
    available (for example, ‘MC11VA0ITM‘) in the OLTP System.
n   A maintenance screen is displayed in which you can to assign other 'properties' to the fields of the
    extract structure (S5nnBIWS).
    Ÿ Selection fields
    Ÿ Hide fields
    Ÿ Cancellation fields (field is inverted when canceled (*-1))
    Replicating DataSources




        © SAP AG 1999



n   OLTP extraction tables make up the basis of a DataSource as far as BW is concerned.
n   An R/3 System connected to BW provides a variety of DataSources. These can be uploaded into BW
    by replicating them in the source system tree.
n   The DataSources are delivered in a so-called 'D version' and can be transferred to the 'A version'
    when they are activated. They can be also changed and forwarded to the 'A version' (one that
    deviates from the default).
n   If DataSources have changed in the source system (for example, when your R/3 System is upgraded),
    you can decide if you want to activate them to the 'A version', or continue using the existing ones.
n   The DataSource must be replicated before it can be used in BW.
    To do this, choose the 'Source Systems' tabstrip in the BW Administrator Workbench. Select the
    relevant OLTP system and choose Replicate DataSources from the context menu. All the
    DataSources that do not exist yet in BW are then transferred from the OLTP to the BW System.
    Maintaining the Communication Structure




                                                                    All the fields in the
                                                                     extract structure
                                                              are shown with their assigned
                                                                InfoObjects in the template




        © SAP AG 1999



n   Communication structures are created for InfoSources and thus represent part of an application in the
    OLTP System (for example, order data from Sales, purchase order data from Purchasing, and so on).
n   The total number of InfoObjects in the communication structure and extract structure may be
    different, since InfoObjects can be copied to the communication structure from all extract structures
    (several source systems).
    Maintaining Transfer Rules




                                                                            Transfer structure
                                                                                  field



       Activate




                                                           Transfer              Fixed value
                                                           routine




         © SAP AG 1999



n   Transfer rules specify which fields in the transfer structure are to be transferred to which fields in the
    communication structure. You can create detailed conversion rules to change or add to data.
n   You can only choose one of the three types of transfer rules for each InfoObject in the
    communication structure:
    Ÿ The fields are copied from the transfer structure and not modified.
    Ÿ A field in the communication structure can be supplied with a fixed value for this source system.
    Ÿ A local transfer routine is used to supply the content of the communication structure with data
      when uploaded from this source system. The routine defined only applies to the selected
      InfoObject.
n   The transfer rules do not take effect until they have been activated.
    Maintaining InfoCubes and Update Rules




                                                               ...
                                                               Create InfoCube...
                                                               ...
                                    ...
                                    Create update rules...
                                    ...




        © SAP AG 1999



n   Before data can be uploaded from the OLTP System to BW and evaluated in an InfoCube, the
    InfoCube must be created with the relevant update rules.
n   You maintain InfoCubes and update rules in the Administrator Workbench, Modeling > InfoCubes.
n   Update rules are always defined for a combination of an InfoCube and InfoSource. For this reason,
    an InfoSource can update several InfoCubes. An InfoCube, however, can be linked to several
    InfoSources via update rules.
n   There are various ways of updating InfoCube key figures into the update rules. Possible: Field to
    field assignment, formula and fixed value. You can also specify which date field in the InfoSource is
    to supply the time characteristics of the InfoCube with data. Similarly, a key figure can only be
    updated under certain conditions. In the same way, a currency translation can also be triggered when
    a key figure is updated to the InfoCube.
    Activating Extract Structures




                                                                               l   Activate the extract
                                                                                   structures




        © SAP AG 1999



n   When you activate the extract structure for updating, the data is written to the extract structures
    immediately - online as well as when you fill the tables for restructuring.
    V3 Update - Settings




                                                                             l   Set up V3 update
                                                                                  n   Define job parameters
                                                                                      (start time and print
                                                                                      settings)
                                                                                  n   Schedule batch jobs




        © SAP AG 1999



n   The data is updated with the V3 update and is ready to be transferred with the batch operator to the
    central delta management.
n   You need to define job parameters such as start time and printer settings, and schedule the batch jobs
    at this point.
    Initialization/Simulation (OLI*BW)




                                                                                    Simulation:
                                                                                    No update!


                                                                                          LBWF:




         © SAP AG 1999



n   You have to initialize ('build') the dataset for the respective extract structures before data can be
    extracted from the R/3 System.
n   The initialization is set up in the OLTP. The restructuring process fills restructuring tables that are
    read during the initialization.
n   It is recommended that you carry this out before, in the simulation mode. You have the option of
    checking the extract structure update, without actually updating the data. The results are recorded in
    a detailed simulation log.
    Setup Extraction


    R/3 OLTP System                                                                            Business Information
                                                                                               Warehouse




                                         Setup                                  Setup API
                                         tables



               Transaction                   D-Management
                                     -------------------------------------------------------
                  Data                       Delta extraction                                         Staging
                                                                                                      Engine

      Master                                   Full Extract
       Data                                  or Delta Extract




        © SAP AG 1999



n   When you extract transaction data with the LO method, you need a so-called extraction setup, which
    is similar in its usage to the LIS method for refreshing statistical data.
n   The extraction setup reads the dataset you want to edit (for example , customer orders with the tables
    VBAK, VBAP and so on) and fills the relevant communication structure. The data is stored in cluster
    tables (<Extract structure>_SETUP), from where they are read when initialization is run.
n   You can also carry out a full update into BW with the tables setup.
    Creating InfoPackages




                                                                ...
                                                                Create InfoPackage... .
                                                                ...




        © SAP AG 1999



n   Data requests sent to the source system are managed with the Scheduler. These requests are
    formulated for each InfoSource and source system and are divided into master and transaction data.
n   An InfoSource in a source system can have several different extraction jobs with different selection
    criteria. These are referred to as InfoPackages.
n   InfoPackages or groups of InfoPackages can be distributed to background processes using the R/3
    job planning facility. This means that you can fully automate the data transfer process and decide
    when and at what intervals data is to be extracted. Or, for example, you can use a factory calendar to
    specify that data is not to be extracted on public holidays, and so on.
n   The term 'transaction' in the Business Information Warehouse covers data retrieval in the OLTP and
    the successful updating of this data to the relevant InfoCubes. You can monitor the transfer and
    processing of the data closely using the Monitor function in the Administrator Workbench.
n   You can compile lists containing information on InfoPackage processing for each user, source
    system, day, etc.
    Initializing the Delta Process (Scheduler)




                                                              The selected dataset in the
                                                              OLTP is completely updated
                                                                into BW and the delta
                                                                  process is installed



        © SAP AG 1999



n   If you want to transfer data in the delta process, the process must be initialized in the first data
    request. In this process, the selection conditions for connecting delta uploads are set and its complete
    dataset is loaded into BW from the R/3 System.
n   To do this, you must select the checkbox Initialize delta process for the InfoPackage under the
    update parameters of the Scheduler.
    Monitoring the Upload Procedure




          l Monitoring data requests and data processing
          l IDoc processing status display
                 n      Info IDoc
                 n      Data IDoc

          l Detailed displays for selective monitoring




        © SAP AG 1999



n   The data transfer procedure is handled by a series of IDocs that facilitate communication and data
    transfer across system boundaries. These IDocs are divided into info IDocs and data IDocs.
n   The task of the individual info IDocs is indicated by their status: Status 0: data request received by
    source system, source system starts to select data.
    Status 1: this status indicates a data IDoc that contains further data processing information.
    ....
    Status 5: an error has occurred in the source system.
    ...
    Status 9: data selection in the OLTP System has been successfully completed.
n   With data IDocs, you can display a list of the processing steps that have been carried out to date.
    These steps are described by call numbers, such as: 50: start of update 51: determine InfoCubes to be
    updated 52: InfoCube successfully updated
    .…
    70: end of IDoc processing
    Status


                            l Status OK
             green                n   No errors occurred
                                  n   Data successfully transferred
                            l Status not defined
            yellow                n   Data update not completed (all IDocs)
                                  n   Invalid number of data packages (updated IDocs,
                                      process still running)
                                  n   Invalid data request (Scheduler, transfer structure not
                                      active)
                                  n   No data in source system (general view)
                            l Status not OK or
              red                 n   Data loaded incorrectly
                                  n   Status not defined after timeout
                                  n   Data only posted to incoming ALE IDoc


        © SAP AG 1999



n   The traffic light changes color depending on the context.
n   Note that a red light does not necessarily mean that an error has occurred.
    Delta Update (Scheduler)




                                           Only the data
                                       since the last upload
                                           is requested



        © SAP AG 1999



n   Generally speaking, the volume of transaction data is considerably higher.
n   Delta update mechanisms that restrict the volume of data to within realistic limits, therefore, are
    required to implement a performance-oriented, periodical data transfer strategy.
    Therefore, when sales figures are updated every week in the Business Information Warehouse, only
    the sales document information that has been added or changed in the last week should be extracted.
n   In this case, you have to activate the 'Delta Update' checkbox for the InfoPackage in the updating
    parameters of the Scheduler.
    Extracting Application Data


    R/3 OLTP System                                                                               Business Information
                                                                                                  Warehouse




                                     V3
                                                               ARFSCDATA
                                       VBDATA

                                                D-Management
                Transaction             -------------------------------------------------------
                   data                        Delta extraction
                                                                                                         Staging
                                                                                                         Engine
                                                  Full extract
       Master
                                                or delta extract
        data



         © SAP AG 1999



n   Generally speaking, the volume of transaction data is considerably high. A full update here is mostly
    only justified for the first time data is transferred or if the statistics data has to be rebuilt following a
    system failure.
    Delta update mechanisms that restrict the volume of data to within realistic limits, therefore, are
    required to implement a performance-oriented, periodical data transfer strategy.
    Therefore, when sales figures are updated every week in the Business Information Warehouse, only
    the sales document information that has been added or changed in the last week should be extracted.
n   This functionality is used by the central D-management with the LO extraction method.
n   According to how the V3 update is set up, document data (customer orders and so on) is processed
    when the update is started. That is, the relevant (active) communication structures are filled and
    forwarded to the central D- management.
n   The cDM then 'parks' it in the update table ARFCSDATA until it is requested by the BW System.
    The data remain in the table until the last request for it is successfully processed.
Availability in the R/3 System




                   available for    Prerequisite


                     R/3 4.0B          SP 40
                     R/3 4.5B          SP 22
                     R/3 4.6B          SP 07
                     R/3 4.6C          SP 01
                        ...
                                    or OSS (Online
                                   Service System)
                                      No. 194909




   © SAP AG 1999
Individual Steps in LO Extraction


                                       10. InfoPackage for the delta upload

                                   9. InfoPackage for the delta initialization

                               8. Set up periodic V3 update

                           7. Delete setup table / perform extraction

                        6. Activate extract structures

                      5. Maintain InfoCubes and update rules

                   4. Maintain transfer rules

            3. Assign InfoSources

        2. Replicate DataSource in BW

   1. Maintain extract structure

   © SAP AG 1999
    New LO Data Extraction: Why?




                         Performance &                             Simple
                             volume                               handling




                                         Advantages

                         Single Logistics                          No LIS
                             solution                           functionality



         © SAP AG 1999



n   Compared to the transfer and information structure extraction, the new LO extractor has the
    following advantages:
    Ÿ improved performance and reduced volumes of data
    Ÿ simple handling
    Ÿ single solution for all logistics applications
    Ÿ no use of LIS functionality
    Advantages I: Performance and Data Volumes




        l Detailed extraction: You can deactivate the extraction of, for
             example, scheduling data ('thin extractors' lead to small
             upload volumes)
        l Document changes: only BW-relevant data changes* are
             updated (smaller upload volumes)
        l LIS tables are not updated: Reduced data volumes due to
             removed redundant data storage
        l Update with batch processes: No overload of 'everyday work'




        © SAP AG 1999



n   *: BW-relevant data changes are changes to the contents of the fields that also exist in a relevant
    extract structure. (Not all document changes lead to a new/old posting for BW)
Advantages II: Single Handling




  l No LIS functionality: No knowledge of LIS Customizing,
      update settings, etc, required
  l Function enhancement: Creating simply and without
      modifications
  l BW Customizing Cockpit: Central, single, maintenance tool
      for Logistics applications




   © SAP AG 1999
    Advantages III: Other




       l (Design) Problems with transfer structures:
            Technical restrictions (OSS (Online Service System) note no.
            121196)
       l Delta tables (SnnnBIW1/-2): duplicated update, duplicated
            data storage




        © SAP AG 1999



n   or OSS (Online Service System) note no. 121196:
    Ÿ Because of technical restrictions, it is not possible to perform the update of S261/S263 in the V2
      update if the commissioning in a LUW is carried out when the delivery is saved.
    Ÿ Therefore, you must not use dispatch time 4 for ordering messages in the delivery when the info
      structures S261/S263 are actively updated.
    LO Extraction: Conversion Scenario


    BW System
                                                                           InfoCubes


                                                    Update rules

                                               Communication structure
                                               Communication


                                                    Transfer rules
                          Transfer structure                              Transfer structure
                                                                          Transfer structure



    R/3 OLTP              Transfer structure
                          Transfer structure                              Transfer structure
                                                                          Transfer structure

                    Extraction source structure
                    Extraction                                       Extraction source structure
                                                                     Extraction source structure


                   S260      S260BIW1     S260BIW1                 S263      S263BIW1    S263BIW2

                   OLTP 1: LIS info structure
                   OLTP 1: LIS info structure                        OLTP 2: LIS info structure
                                                                     OLTP 2: LIS info structure


        © SAP AG 1999



n   LO data extraction can be used to completely remove the extraction with transfer structures (for
    example, S260 - S264 in SD) and extraction using 'traditional' information structures in the LIS (for
    example, S001 - S006 in VIS), without missing out on any information.
n   This means that more information with more detail can be loaded into the SAP BW System with LO
    extraction.
    Example: Conversion in Sales


                                                         MC11VA0HDR       VA: Header
        S260            Sales order
                                                         MC11VA0ITM       VA: Item
                                                         MC11VA0SCL
                        Request                                           VA: Schedule
        S264
                                                         MC11V_0ITM       Item level
                                                         MC11V_0SCL       Scheduling level
        S263            Order/delivery
                                                         MC12VC0HDR       VC: Header
                                                         MC12VC0ITM       VC: Item
        S261            Delivery
                                                         MC12VC0SCL       VA: Schedule

                                                         MC13VD0HDR       VD: Header
        S262            Billing                          MC13VD0ITM       VD: Item

            old                                              new

        © SAP AG 1999



n   With the new LO extractor, every 'document level' (for example, document header/item/unit) has a
    communication structure, which serves as a basis for the relevant extract structure.
    Individual Steps: LIS ® LO Extraction

                                             11. InfoPackage for the delta upload

                                         10. Simulate delta initialization

                                    9. Set up/start periodic V3 update

                                8. Empty setup tables

                              7. Upload the open delta queue

                          6. Extract structure active and + LIS update off

                        5. Maintain InfoCubes and update rules

                    4. Maintain transfer rules

                 3. Assign InfoSources

           2. Replicate DataSource in BW

      1. Maintain extract structure
        © SAP AG 1999



n   To go from the InfoSources that you want to replace to the new Data/InfoSources, you must perform
    the steps as described below.
n   Steps 1-5:
    ŸTransfer new Content objects from Content (in OLTP (DataSources) and in BW (InfoSources,
    update rules, transfer rules, ...))
n   Find time frames in which there are no updates for the info structures you want to replace.
n   Steps 6-8:
    IMPORTANT: Make sure that no R/3 data updated for the DataSources in question when you
    carry out these steps.
    Switch off update for LIS extraction. Switch on update for LO extraction (TA SBIW).
    Load the delta queue of the old InfoSource into BW so that all delta records of the old source come
    into and are posted to BW (important so that no changes or new records are lost and that the data
    stays consistent).
    Do not refresh the statistics for the new DataSources, or else records will be posted twice in the
    InfoCube.
n   Steps 9-11:Simulate an initial load for the new InfoSources' delta upload (option in the InfoPackage).
    This simulation run must 'pass green'.
    The update can take place now. When the V3 update has been scheduled for the new DataSources,
    the delta queue is filled and the data can be loaded for the new DataSources.
LO Data Extraction: Unit Summary



                  You are now able to:

                  l Make the settings you need for extracting in the 'BW
                    Customizing Cockpit' of the R/3 System
                  l Display the different data extraction options in
                    Logistics and the advantages of LO compared to the
                    LIS method, and
                  l Take the necessary steps in converting from LIS to
                    LO data extraction.




  © SAP AG 1999
Extraction from CO-PA



                      BW Overview -              Tools for Generic
                     SAP R/3 Extraction           Data Extraction

                                                    Enhancing
                     LIS Data Extraction
                                                  Business Content

                                                  Special Topics:
                     LO Data Extraction
                                                 Delta Management

                                               Excursus: OLTP Access
                   Extraction from CO-PA
                                                  via Remote Cubes


                  Data Extraction from FI-SL




  © SAP AG 2001
Extraction from CO-PA




      Contents:
       l CO-PA: General overview
       l Generating and replicating DataSources in BW
       l Creating InfoSources
       l Notes on data modeling
       l Data transfer




  © SAP AG 1999
Extraction from CO-PA: Unit Objectives




                   At the conclusion of this unit, you will
                   be able to:
                   l Design and define DataSources in CO-PA
                   l Assign a DataSource to an InfoSource and maintain
                     their communication structures and transfer rules
                   l Build an InfoCube and maintain update rules
                   l Manage the CO-PA extraction process
                   l Use the CO-PA tools for BW.




   © SAP AG 1999
    Course Overview Diagram



                                           Extractor Types

                   Application-specific                            Cross-application

         BW Content                     Generic                          Generic
          Extractors                   Extractors                       Extractors

              FI                        LIS                              Database
                    CO                                                   table/view
             HR
                   ...                        FI-SL
                                                                         SAP Query
          LO Cockpit                          CO-PA


          Transparent                 Transparent
                                                                        Data Source
             Table                       Table

                                          Enhancements
                                          Enhancements

        © SAP AG 1999



n   The transaction data entering the Business Information Warehouse by means of extractors originates
    from very different modules. Due to past developments, very different extraction mechanisms are
    necessary.
Extraction from CO-PA: Business Scenario



                  l The ABC Company has implemented CO-PA and
                    wants to use this data in the SAP Business
                    Information Warehouse to compile reports for the
                    management.

                    The management requires analyses of the gross
                    and net sales figures from the individual sales
                    organizations.

                    You are responsible for extracting the data from
                    the R/3 System and importing it into BW. To do so,
                    you have to create the necessary components in
                    the R/3 and BW Systems.




  © SAP AG 1999
Position of the CO-PA Application


  l CO-PA collects all of the OLTP data for calculating contribution
    margins (sales, cost of sales, overhead costs)
  l CO-PA also features powerful reporting tools and planning
    functions
  l The CO-PA reporting facility, however, is limited in two
    respects:
         n   The integrated cross-application reporting concept is not as
             differentiated as in the SAP BW.
         n   The OLTP System is optimized for transaction processing, and a high
             reporting load would impact the overall performance of the system.
  l Using BW as a reporting solution for CO-PA eliminates these
    problems




   © SAP AG 1999
    Flow of Actual Values - Overview
                                                                                                  EC-
                                                                                                  PCA
               Profit Center Accounting
       CO
              Profitability Analysis                                          Profitability
                                                                               Segments



                   Overhead Cost                              Product Cost
                    Controlling
                    Controlling                                Controlling

                                 Processes                                Cost
          Internal
           Orders                                                        Objects


                                                             Standard
                        Cost Center                          cost of goods

                                Cost and Revenue Element Accounting
                                Cost and Revenue Element Accounting
                                                                                              R



        FI                                                              Revenues
                                                                                       SD
                                                                        Discounts
        © SAP AG 1999



n   During billing in SD, revenues and discounts are transferred to profitability segments in Profitability
    Analysis. At the same time, sales quantities are valuated using the standard cost of goods
    manufactured, as specified in the cost component split from CO-PC.
n   In Overhead Cost Controlling, primary postings are made to objects in Overhead Cost Controlling
    and assigned to the relevant cost object on a source-related basis. The actual cost of goods
    manufactured is also assigned to the cost object. At the same time, the performing cost centers are
    credited. From the point of view of profitability analysis, this leads to under or overabsorbtion of the
    performing cost centers and to production variances for the cost objects involved (such as production
    orders).
n   The production variances calculated for the cost objects (in this case, production orders), i.e. the
    difference between the actual cost of goods manufactured and the standard costs, are divided into
    variance categories and settled to profitability segments. The overhead costs remaining for the
    objects in Overhead Cost Controlling are assigned to the source profitability segments.
n   What are the top products and customers in our different divisions? This is just one of the typical
    questions that can be answered with the Profitability Analysis (CO-PA) module.
n   The wide variety of analysis and planning functions in CO-PA allow you to plan, monitor, and
    control the success of your company in terms of product-oriented, customer-oriented and
    organizational dimensions of multidimensional profitability segments.
    Basic Concepts


        l Characteristics
               n   Characteristics are levels on which information is required.
                   Example: Divisions, regions, customer groups
        l Characteristic values
               n   Characteristic values are values that can be assumed by a
                   characteristic.
                   Example for the characteristic 'region': eastern region, northern
                   region
        l Profitability segment
               n   A profitability segment is a combination of existing characteristic
                   values.
               n   Example: computer division, eastern region




        © SAP AG 1999



n   Characteristics are the fields in an operating concern according to which the data can be
    differentiated in Profitability Analysis.
n   Each characteristic in an operating concern has a series of valid characteristic values.
n   A profitability segment is a fixed combination of valid characteristic values.
    Characteristics


                SD                        FI                     CO-PC
                                                                 CO-PC                    CO-OM




                 Billing           Posting to a                Product               Cost Centers,
      R/3        Document          G/L Account                 Costing               Orders, Processes




          DB            Cust.   Product Cust. grp Product grp              .   ...

                        Characteristics                                                Value Fields

        In addition to 19 fixed characteristics, you can choose
        up to 50 further characteristics.
        © SAP AG 1999



n   Some characteristics are predefined in each operating concern. This includes customer, material,
    company code, and others. You can call up a full list of the fixed characteristics by displaying the
    data structures in the operating concern.
n   In addition to these fixed characteristics, you can define up to 50 of your own characteristics. In most
    cases, you will be able to satisfy your profitabilit y analysis requirements with between 10 and 20
    characteristics.
n   Descriptive attributes (customer, material, time) are stored as characteristics so that the data can be
    analyzed according to several dimensions.
    In addition to the independent characteristics which can be found on a sales document (customer,
    material, fiscal period, sales area, etc.), several characteristics can be derived from these (customer
    group, material hierarchy, sales hierarchy). When costs are posted from CO-OM, the most detailed
    characteristics are usually initial values (blank or zero) since the costs can only be properly assigned
    to objects that are less detailed. Marketing costs, for example, could be correctly assigned to the
    customer group and the article.
    Value Fields


                SD                        FI                   CO-PC                    CO-OM




                 Billing          Posting to a               Product             Cost Centers,
      R/3        Document         G/L Account                Costing             Orders, Processes




          DB                                            Sales ded.
                                          Quantity Rev. Sales ded. CGMV CGMF Overhead Con.

                        Characteristics    Value Fields




        © SAP AG 1999



n   Key figures (revenue, cost of goods sold, overhead costs) are stored in value fields to make the
    contribution margin more transparent. Depending on the data source, some value fields are equal to
    zero, while others are not. In a sales document, for example, the sales quantity, revenue, rebate, cost
    of goods sold, (calculated from the product costs in CO-PC) and any accruals are not equal to zero.
    When costs are posted from CO-OM, however, all of these value fields are equal to zero. Other fields
    that are used to record different cost elements (e.g. marketing costs) are not equal to zero in these
    data records.
    Organizational Structure



           Operating                                          Operating
           Concern                                            Concern
             0001                                               0002
      Profitability segment                              Profitability segment



         CO Area 0001                          CO Area 0002             CO Area 0003
           Profit Center                          Profit Center              Profit Center




           CCode 01                  CCode 02                     CCode 03
                                                                  CCode                  CCode 04
                                                                                         CCode




        Business Area 1
        Business Area 1           Business Area 2
                                  Business Area 2           Business Area 3
                                                            Business Area 3           Business Area 4
                                                                                      Business Area 4


        © SAP AG 1999



n   The value fields and characteristics that are required to conduct detailed analyses of the contribution
    margin vary considerably both from industry to industry and between individual customers. In CO-
    PA, therefore, you can configure the structure of one or more operating concerns in each individual
    installation. An operating concern is an organizational structure that groups controlling areas
    together in the same way as controlling areas group companies together. Each installation usually
    comprises only one operating concern.
n   Since value fields and characteristics can be defined individually in each customer installation, it is
    not possible to ship all of the required data structures (and the programs for accessing these
    structures) with the R/3 installation CD. Instead, these structures have to be generated when CO-PA
    is configured (similar to an InfoCube in BW).
    Database Structures in CO-PA


                                                                         Profitability
                                                                   Segment 7
                Segment Level                CE3                   Period      07.96
                                                                   Quantity 10
                                                                   Revenue        30,000.00

                                                                          Profitability
                                                                   Segment          7
                Segment Table                CE4                   Product        PC
                                                                   Customer        A
                                                                   Division Computers




              Actual Line Items              CE1                   Date       07.12.96
                                                                   Product         PC
                                                                   Customer          A
                                                                   Division Computers
                                                                   Quantity      10 pcs
                Plan Line Items              CE2                   Revenue    30,000.00




        © SAP AG 1999



n   Line items are stored in separate tables: CE1xxxx (xxxx is the name of the operating concern)
    contains the actual line items and CE2xxx the plan line items. Note that these tables contain the value
    fields and characteristics and, therefore, are generated tables.
n   Line items contain some information at document level (CO-PA document number, sales document
    number, posting date) that, in most cases, is too detailed for analysis purposes. CO-PA maintains an
    initial summarization of the data used by all CO-PA functions (reporting, planning, assessments,
    settlements, realignments, etc.).
n   The characteristics that describe the market are first separated from the rest of the line items. Each
    combination of characteristic values is coded in a profitability segment number. The link between the
    profitability segment number and characteristic values is maintained in a separate table - the segment
    table CE4xxxx. Certain characteristics can be excluded from this process. These are then stored in
    the line items only and not in the segment table. These characteristics can only be analyzed to a
    limited extent. Characteristics that are differentiated to a large extent (such as the customer order
    number) are usually excluded to reduce the volume of data.
n   The value fields are summarized at the profitability segment and period levels (as well as other
    characteristics at the business transaction level: plan/actual indicator, record type, and plan version)
    and stored together with these fields in a second table known as the segment level CE3xxxx. This
    table contains the total values of the period for each profitability segment number.
    Storage Procedure




            Characteristics
            ...




                                                     PALEDGER Currency type           Value Fields
         PAOBJNR                                     VRGAR    Processing type         ...
         No. Profitability Segment                   PLIKZ    Plan/actual ind.
                                                     VERSI    Plan version
                                                     ...




                                                                                         R




        © SAP AG 1999



n   You can compare an operating concern (which is represented by the associated segment table and
    segment level) with an InfoCube. The InfoCube comprises a dimension table (the segment table) and
    a fact table (the segment level). Unlike the fact table of an InfoCube, the segment level key contains
    other keys (e.g. the record type) in addition to the key field from the segment table.
n   Characteristics in CO-PA correspond to the characteristics (or attributes) in InfoCubes; the value
    fields can be regarded as key figures with an additional summarization in each characteristic.
n   Summarization levels for an operating concern have the same function as aggregates for an
    InfoCube. The only difference is that aggregates for InfoCubes are managed with the InfoCube itself
    (i.e. all aggregates always contain the same numbers as the InfoCube they are based on), while
    summarization levels are updated at regular intervals (usually every day).
n   Line items in CO-PA can be compared with the line items in the Operational Data Store (ODS).
    These are also comparable with line items in the communication structure directly before they are
    posted to an InfoCube.
    Update Model - Overview


    BW
                                       Delta update     Initial Loading Process Initial Loading Process
                                           and
                                Initial Loading Process




    R/3 OLTP
                                             Time stamp
               SD
                                CE1/
                                CE2
                                                              Cyclical
                                                              Update
                                                              (daily)
                                              CE4                                          Partitioning
                                                                                           Characteristic
              CCA
                                                     CE3
                                   Transaction-                          Summarization CE1: Actual line item
                                   based                                    Level      CE2: Plan line item
                                                                                               R


                                   Update                                              CE3: Segment level
                                                                                       CE4: Segment table

        © SAP AG 1999



n   To speed up access to data, CO-PA can also maintain summarized copies of segment tables and
    segment levels called "summarization levels". Each summarization level contains all of the value
    fields and a subset of the characteristics. To ensure that a correct aggregate is formed, some detailed
    characteristics are excluded in each summarization level. If a characteristic X (e.g. the customer
    number) is contained in a summarization level, all of the characteristics derived from X (e.g. the
    customer group) should also be contained in the same summarization level. Summarization levels are
    updated from time to time in a mass update run and not each time a line item is posted. The update
    procedure is controlled by time stamp information that is stored in each line item and in the
    summarization level catalog. You can use the time stamp to determine at any time whether a certain
    line item has already been entered in a specific summarization level.
n   In BW, you define an InfoPackage for the initial uploading process and further InfoPackages for a
    delta update from a CO-PA InfoSource. When an InfoPackage is executed, the SAP BW Staging
    Engine calls the CO-PA transaction data interface. When you have generated an InfoSource, you
    must then perform the initial loading process. Following this you can execute de lta updates. Note
    that the CO-PA extraction program for the SAP BW uses the same replication method as the update
    program for CO-PA summarization levels for updating summarization levels. On the BW side, only
    data that is "at least 30 minutes old" is received. Section 9 of note 21773 contains further details on
    this "safety delta", as it is known.
    Data Staging - Overview



             Query                                InfoCube
                                                                                             Metadata

                                      Update                                             transaction data
                                       rules

                        InfoSource / Communication structure                  ODS


         Mapping                                                 Transfer Rules


                           DataSource / Transfer structure                    PSA

         Replicate
                                                                                    BW
        DataSource

                           DataSource / Extract structure
                                                                                    R/3
          Generate                CO-PA                          CO-PA
         DataSource            DataSources                       Extractor
                                        CO-PA
                                                                                    source
                                                                                    system
                                                               Report


        © SAP AG 1999



n   To provide DataSources for BW, all CO-PA DataSources (and the operating concern itself) must be
    generated.
n   A CO-PA DataSource can be defined at the operating concern and client level.
n   The DataSource itself comprises the following information:
        Name of the operating concern
        Client
        Data source for full updates (summarization level, segment level, line item)
        Subset of the characteristics for defining the degree of detail for replication purposes
        Subset of the value fields
        Update status (InfoSource defined, full update running, delta update running, update completed,
        invalid)
        Time stamp, which can be used to determine which data has already been replicated to BW.
    Overview - BW-IMG in the R/3 System (TA SBIW)




        © SAP AG 1999



n   CO-PA in the BW IMG of the R/3 System (transaction SBIW ->Customer-defined DataSources ->
    Profitability and Market Sector Analysis):
    Ÿ Procedure for setting up the replication model
    Ÿ This written chapter delivers information needed at the beginning of the installation scenario.
    Ÿ Assigning Key Figures
      In this step you assign elements of an accounting schema to some of the predefined key figures.
      You can record these fields to DataSources.
    Ÿ Creating DataSources
      Create a DataSource to extract transaction data from accruing or accounting CO_PA.
    Ÿ Tools - Displaying detailed information on the DataSource
      Displaying details on the DataSource, such as header information, information on the delta process
      and the field list.
    Ÿ Tools - Simulating the initialization of the delta process
      Advanced tool to enable testing of existing CO-PA (with already high volumes of data).
    Ÿ Tools - Activating debugging support
      This transaction is exclusively used by the SAP support team.
    Introduction: Creating DataSources




                                                                             Operating concern




                                                                    Client
                                   System ID




        © SAP AG 1999



n   Since an InfoSource is always defined at the source system, operating concern and client leve l, a
    standard name is always generated such as 1_CO_PA_<%SY>_<%CL>_<%ERK>. You can change
    this name if necessary. The prefix 1_CO_PA, however, is mandatory. SAP recommends that you
    only extend the standard name.
        Example: in an R/3 System with the ID P31 and client 100, the standard name of the
        DataSource for the IDES operating concern is: 1_CO_PA_P31_100_IDES.
n   Modify the name of the DataSource, if necessary, to distinguish it from other DataSources. You can
    create a new DataSource with this name using the relevant button on the initial screen.
    DataSource: Header Information




        © SAP AG 1999



n   Some fields of the operating concern are not replicated 1:1 in BW.
    Ÿ The field PALEDGER (internal/external values 01/B0, 02/10, 03/B2, 04/12) is divided into
      currency type (field CURTYPE in the extract structure, InfoObject 0CURTYPE, values B0, 10)
      and reporting view (VALUTYP, 0VALUATION, values 0, 2).
    Ÿ The plan/actual indicator PLAID (values 0, 1) is converted into the currency type for the reporting
      system (VALTP, 0VTYPE, value 010, 020).
    Ÿ The week ALTPERIO (internal/external values YYYYWWW/WWW.YYYY) is converted in the
      calendar week (CALWEEK, 0CALWEEK, internal/external values YYYYWW/WW.YYYY).
    Ÿ The fiscal variant PERIV is added to the fiscal year FISY R to describe the period PERIO.
    Ÿ With accounting DataSources, the account plan ACCPL is added to cost accounting COACC to
      describe the cost type CSTTYP.
n   The name of the DataSource is not only maintained in the logon language.
n   The field name for partitionin g can be released.
    DataSource: Characteristics




        © SAP AG 1999



n   The Characteristics of the object table are the characteristics that are maintained in the transaction
    KEQ3 (characteristics of the results objects) and form the results objects.
n   By default, all the characteristics are selected, since it is based on the scenario "CO-PA Reporting in
    SAP BW", that is, "KE30 via BEx".
n   Exceptional cases with characteristics:
    Ÿ Customer hierarchy levels have KNA1 as their master data.
    Ÿ There is a special procedure for compound characteristics. You must create InfoObjects, master
      data and text extractors.
    Ÿ The company code (COMCO) is not a compulsory field but you must select it if the system
      contains an item with PALEDGER¹01, or if the DataSource is accounting-based.
    Ÿ You must also specify a controlling area for accounting-based DataSources.
    Ÿ The PSP element is shown as it appears externally (24 characters) in SAP BW, since there are no
      8-character PSP elements in SAP BW.
    DataSource: Single Line item Characteristics




         © SAP AG 1999



n   The units are selected automatically if you select their quantity field.
n   Characteristics from the single line items
    Ÿ In this area, all characteristics are displayed that were not selected for the operating concern in TA
      KEQ3, such as fields, which are only saved in single line items.
    Ÿ The system only shows these fields of the single line items that make use of the unique data in the
      database tables. Some fields are either redundant (for example, CLIENT), or only specific for CO-
      PA internal use (for example, PAOBJNR, AWSYS) or do not contain any relevant data. Please
      note that some of the fields shown are not relevant for customer installation (for example,
      STO_BELNR, RBELN).
    Ÿ Remember that all updates affect your data from the line items if you choose a field from this area.
      Delta updates always affect your data from the line items. It is of no consequence here, whether
      you select a single line item or not.
    Ÿ If you select the document number DOCNO, a non-aggregated replica usually appears in the Data
      Warehouse. This is generally seen as an incorrect way to use the Data Warehouse and mostly
      causes performance problems.
    DataSource: Vale Fields




        © SAP AG 1999



n   You usually select either all the fields or several calculated key figures (that were previously
    assigned to the rows and form an accounting schema). A mixed form can only rarely be of use.
    DataSource: Selection Fields




        © SAP AG 1999



n   The displayed field name is the name of the extract structure and can deviate from the CO-PA field
    names in some cases (see above).
n   If the checkbox in the column Selection is active, that is, shown in white, you can select it.
    Ÿ However, some fields cannot be selected: Especially fields that are to be worked on (currency,
      PALEDGER, PLIKZ, PERIV, KTOPL,..), units, currency, value fields and calculated key figures.
    Ÿ You should only select fields that divide your data if (a) there is a large volume of data for the first
      data transfer, or (b) there are business reasons and you need to select these in the future.
    Ÿ The selection in BW can only be a fixed value or an interval.
    Ÿ Never specify very large PERIO intervals (PERIO=001.1999..999.2999). The system will crash
      because the memory is overloaded. Use FYEAR intervals instead (FYEAR=1999..2999).
n   You can ignore the column Hide field since you have already selected the fields you want to
    replicate.
n   After making your selections, choose Generate. This ends the activities in the R/3 System.
n   Choose the detail view in the IMG to display the DataSources.
n   The next steps are made in the BW System. First load a newly defined DataSource into BW and
    create an InfoCube based on the DataSource.
    DataSource Definition: Accounting CO-PA




        © SAP AG 1999



n   Defining an accounting DataSource is not much different to defining accrued DataSources.
    Ÿ KOKRS, BUKRS, KSTAR are compulsory.
    Ÿ There are no characteristics available from the line items since accrued DataSources do not contain
      characteristics.
    Ÿ There is only one amount (in three currencies) and a quantity (together with the quantity unit).
    Ÿ There are no value fields or calculated key figures available.
    Ÿ KOKRS and PERIO must be selected as selection fields.
    Ÿ The special procedure for certain fields has already been described.
n   There are certain restrictions for the data upload, which are described in detail in the section on
    further update topics.
    BW: Replicating DataSources




        © SAP AG 1999



n   In this step, the definition of the DataSource that you just created is loaded into a SAP BW System.
n   You are recommended to start the replication from the most detailed node to obtain an optimum
    response time. The replication of the entire R/3 System takes a few minutes, but is started when you
    create a DataSource for the first time.
    BW: Creating InfoSources




        © SAP AG 1999



n   You are recommended to always create an InfoSource in the InfoSource screen in Modeling. Then
    change to the source system screen and connect the DataSource from there to the InfoSource.
    BW: Attatching InfoSources




        © SAP AG 1999



n   When a DataSource is assigned to an InfoSource, the system proposes the field assignment, and the
    transfer and communication structures. In addition, InfoObjects and DataSources are created on
    request.
    Ÿ For CO-PA fields (WW..., VV...) with names that consist of 5 characters, InfoObjects are created
      with the naming convention OG_Cxxxxx (characteristics), 0G_Axxxxx (amounts) 0G_Qxxxxx
      (quantities) and 0G_Uxxxxx (quantity units). xxxxx stands for the name of the relevant CO-PA
      field. These InfoObjects are automatically assigned to the fields in the DataSource. Example:
      VV007 / VV007_ME « 0G_QVV007 / 0G_UVV007.
    Ÿ Fields from the template operating concern (S_CP, S_GO, S_AL) and 0MB1 (Banking) and the
      retrieved key figures, use relevant InfoObjects in Business Content, which are automatically
      assigned to them. Please note that you must activate Business Content before assigning the
      DataSources. Example: KMKDGR « 0CUST_GROUP.
    Ÿ Fields that are clearly presented in other DataSource/InfoSource mappings, inherit this same
      mapping. Example: BUKRS « 0COMP_CODE.
    Ÿ To define or create missing InfoObjects, you can use the standard procedure used in SAP BW.
      Hierarchies are not supported as yet, but a complete hierarchy extraction with PI-2000.2 (2.1C
      extractors) is being programmed.
n   Choose Propose transfer rules to define unique rules and structures if the system has not yet defined
    them.
n   Please note that the procedure is considerably different to that in Release 1.2B.
    BW: Setting up the Delta Upload




        © SAP AG 1999



n   CO-PA DataSources support the delta method for a BW target system (see below for more details on
    transferring data in more than one BW System).
n   To apply the delta method you need two InfoPackages:
      - You can use the first InfoPackage to implement the initialization request. It is carried out at the
        beginning and then again after every assignment change in the source system.
      - The other InfoPackage (from the same selection) is for the delta transfer and is usually
        scheduled on a daily basis. You can create it as long as the first initialization request is
        successfully complete.
    Ÿ Please note that is not possible to repeat a delta request to CO-PA.
    Ÿ You can introduce the InfoPackage as an ABAP report with start variants, and a request as a
      scheduled execution of this report with the variant.
    Ÿ You no longer need RKEBW200 before a new initialization. As of PI-A99, the CO-PA replica
      status after every new initialization request is automatically reset.
n   After the system retrieves the data from the line item or the summarization levels, it aggregates the
    data, calculates the key figures and deletes the records with zero values. This is why the number of
    records that have been read and the number of records that are transferred into BW (both are
    displayed in TA KEB2) are considerably different.
    Delta Process (I)

           InfoPackages                                                                         I2 + D4
                                                I                   D                          + D5 + D6


    BW

           Requests       I1         D1      D2        D3           I2        D4        D5        D6
                                                                                                    Time
                            30 min

               I1
    Single line items           D1
                                           D2
    R/3                                              D3
                                                               R
                                     I2
Single line items                                                          D4
                                                                                     D5
                                                                                               D6
         © SAP AG 1999



n   By way of securing data integrity, a delta initialization or delta request replicates all the new line
    items that were previously posted from line items at the time t (t = 30 minutes).
n   This retention period of 30 minutes is often described as a "security delta" and is represented in the
    schema by the yellow bars.
n   Since a delta update is scheduled every night after the daily posting processes, the retention period
    does not disrupt the day's business.
    Delta Process (II)

           InfoPackages                                                                       I2 + D4
                                               I                   D                         + D5 + D6


    BW

           Requests       I1       D1          D2      D3          I2       D4        D5        D6
                                                                                                  Time
                                      30 min

          I1
Summarization level         D1
                                           D2
    R/3                                             D3
                                                              R
                                 I2
Summarization level                                                     D4
                                                                                   D5
                                                                                             D6
        © SAP AG 1999



n   The security delta also comes into use when you build summarization levels. If the delta initialization
    can be covered by the summarization level, the replica "inherits" the security delta from the
    summarization level.
n   Please note that D1 and D4 cover more data than before in the diagram above. However, the delta
    initialization is usually faster if the data can be retrieved from a summarization level.
n   Please also note that the availability of a summarization level is checked at the time of extraction.
    You must make sure,
    Ÿ that a relevant summarization level is active and available if the DataSource is using the required
      aggregation (> 1:3 compared to the single line items).
    Ÿ that the data on the "best" summarization level is up-to-date, so as to avoid unnecessarily large D1
      and D4.
    "Delta method" in Account-based CO-PA
                                     "Initialization "                           "Delta"
          InfoPackages                                                                           F1 + F2
                                                               F                                + F4 + F6


    BW

          Requests             F1                        F2        F3       F4         F5        F6
                                                                                                     Time
                               F1                        F2        F3                  F5
                                                                     F4                  F6
                                 always from summarization levels
    R/3
                           Period                 Period            Period                 Period
                           1.2000                 2.2000            3.2000                 4.2000

         © SAP AG 1999



n   The accounting-based DataSources only support the "Full" update mode.
    Ÿ The indicator is set for delta compatibility, but an attempt to load a delta or an initialization will
      trigger the error message RD150.
    Ÿ A delta process for medium-sized volumes of data can be simulated if you delete requests for the
      last period from the InfoCube and carry out another full update for the period.
n   A summarization level is required as the source for a full update. You cannot access line items
    directly.
n   Delta support is scheduled for R/3 ³ 4.0B with PI 2000.2 (2.1C).
n   You must select a fixed value for KOKRS and PERIO:
    Ÿ for KOKRS, because accounting-based summarization levels are always restricted to a controlling
      area (compulsory)
    Ÿ for PERIO, because only the most up-to-date completed periods are transferred.
    BW: Selection Restriction




         © SAP AG 1999



n   As of Release 2.0B, it is possible to make selections for the delta initialization, full and delta updates.
    Ÿ Full updates can be carried out with various selections; in a cycle in which the delta initializations
      and delta updates switch over, the selections must, however, be the same for all requests.
    Ÿ This is the exactly the same process that drilldown reporting in CO-PA would take on.
n   Please note that there may be performance problems because of the index structure in the CE1xxxx-,
    CE2xxxx- and CE4xxxx tables.
    Ÿ The extra index MANDT+PAOBJNR for CE1xxxx and CE2xxxx supports all types of requests as
      long as no selections are applied.
    Ÿ Selecting in InfoPackages requires additional indexing sometimes.
    Ÿ There may be situations where delta initializations and delta requests cannot be dealt with
      effectively with one index structure for the CO-PA tables.
    Ÿ In any case, you are recommended to carry out testing with productive data.
Individual Steps in CO-PA Extraction




                                   10. InfoPackage for the upload
                               7. InfoPackage for the deltadelta upload

                                  10. InfoPackage for the initialization
                             6. InfoPackage for the deltadelta upload

                         5. Maintaining InfoCubes and Update Rules

                     4. Maintain transfer rules

                   3. Maintaining Communication Structure

            2. Replicate/assign DataSources

        1. Generate DataSources in the OLTP System




   © SAP AG 1999
Extraction from CO-PA: Unit Summary




                  You are now able
                  to:
                  l Design and define DataSources in CO-PA
                  l Assign a DataSource to an InfoSource and maintain
                    their communication structures and transfer rules
                  l Build an InfoCube and maintain update rules
                  l Manage the CO-PA extraction process
                  l Use the CO-PA tools for BW.




  © SAP AG 1999
Extraction from CO-PA (accrued) - Exercises


                Unit:     Extraction from CO-PA (accrued)
                Topic:         Defining a CO-PA DataSource

                At the conclusion of this exercise, you will be able to:
                • Create a CO-PA DataSource in the R/3 System
                • Replicate this DataSource in the BW System
                • Schedule an initial loading process and a delta update


                The company ABC has implemented CO-PA and wants to use this data in
                the SAP Business Information Warehouse for reporting to the
                management.
                The management requires analyses of the gross and net sales figures from
                the individual sales organizations.
                You are responsible for extracting the data from the R/3 System and
                importing it into BW. To do so, you have to create the necessary
                components in the R/3 and BW Systems.
                Profitability analysis is an integrated component of the R/3 System. All
                of the data relating to profitability from the other R/3 applications is
                mapped in CO-PA in accordance with the underlying business
                transactions. In this process, you can transfer billing document data from
                SD, cost object costs from CO-PC and overall costs from overall cost
                Controlling into CO-PA. This makes it possible to make a complete
                analysis of all operation-specific revenue and costs. To keep it simple, the
                SAP BW example below will only show a section of the data processed
                in CO-PA. You can display the complete data records from CO-PA,
                including cost object costs and overall costs, by making the appropriate
                settings in BW.

  1-1   To create an DataSource for CO-PA, you have to follow the procedure described in
        the implementation guide in the SAP OLTP source system.
        1-1-1 Go to the source system T90CLNT090 in the Administrator Workbench, by
              choosing ‘Customizing extractors…’ to call up the CO-PA section of the
              Implementation Guide for the SAP OLTP source system. Choose ‘Create
              DataSource’ Enter the operating concern ‘IDEA’ (accrued).
        1-1-2 Give your DataSource the following name:
              1_CO_PA%CL_IDEA## (where ## is your group number and %CL
              represents the R/3 system client) and create the DataSource.
        1-1-3 Choose ‘Company code’ as the partitioning characteristic.
        1-1-4 Deselect all of the selected characteristics and value fields and choose the
              following ones.
              Field name characteristic     Characteristic description
              COCOD                         Company code
              COARE                         Controlling area
              DIVIS                         Division
              SLORG                         Sales organization
              Field name value fields       Description of value fields
              VV010                         Revenue
              VVIQT                         Invoiced quantity in sales unit
              VVOQT                         Sales order quantity
              VV030                         Customer discount
              VV040                         Material discount
              VV020                         Quantity discount
              VV070                         Accrued cash discount
              VV075                         Actual cash discount
              VV060                         Other discounts
             Enter ‘=init’ in the OK code field and confirm your entries.
      1-1-5 Check your DataSource.

1-2   In the next step, you maintain the DataSource you want to generate, by selecting the
      selection fields and the fields you want to hide.
      1-2-1 Start the InfoCatalog from the same program by choosing ‘InfoCatalog’.
            This now brings you to the maintenance program for the DataSource you
            want to generate.
             Do not specify any fields as selection fields and do not hide any fields. Save
             the DataSource. Do not generate any 12B Metadata.

1-3   In the final step, the DataSource is generated in the OLTP System.
      1-3-1 Generate the DataSource.
      1-3-2 Leave the program for creating the DataSource in the OLTP System and go
            back to the BW Implementation Guide.
      1-3-3 Check the status of your DataSource. Branch to the CO-PA section of the
            Implementation Guide in the SAP OLTP source system and display the
            detailed information on your DataSource.

1-4   To transfer the generated DataSource from the OLTP System into the BW System,
      you have to carry out a DataSource replication for your source system. Once the
      replication has been carried out, the CO-PA DataSource is recognized by BW and
      you have to assign an InfoSource to the new DataSource. Then activate the
      communication structure and the transfer rules.
      1-4-1 Carry out the DataSource replication for the application component CO-PS
            for the source system ‘T90CLNT090’.
             Check that your DataSource ‘1_CO_PA%CL_IDEA##‘ now appears in the
             DataSource list under the application component ‚CO-PA‘.
      1-4-2 Now assign an InfoSource to your DataSource ‘1_CO_PA%CL_IDEA##‘
             Copy the proposal over for the application: ‘1_CO_PA%CL_ IDEA##’ as
             the name for the new InfoSource.
      1-4-3 Then activate the communication structure and the transfer rules. Transfer
            all the InfoSource fields in the communication structure. Set up the transfer
            method ‘PSA’ for the transfer rules. Activate your settings.

1-5   In the next step, you upload data to the PSA.
      1-5-1 Schedule an InfoPackage ‘GR## Initialization’ for your InfoSource and the
            source system ‘T90CLNT090’. Use only the PSA as the data target and
            initialize the delta process.
      1-5-2 Now schedule an InfoPackage ‘GR## Delta’ for a delta upload.
                   Since no relevant documents have been posted in the OLTP System,
                   the delta upload will transfer 0 data records to the BW System.




      1-5-3 You can now display information on your uploading activities. Branch to
            the CO-PA section of the Implementation Guide in the SAP OLTP source
            system and display the detailed information on your DataSource.
Extraction from CO-PA (accrued) - Solutions


                Unit:    Extraction from CO-PA (accrued)
                Topic:          Defining a CO-PA DataSource



  1-1   To create an DataSource for CO-PA, you have to follow the procedure described in
        the implementation guide in the SAP OLTP source system.
        1-1-5 Go to the source system T90CLNT090 in the Administrator Workbench, by
              choosing ‘Customizing extractors…’ to call up the CO-PA section of the
              Implementation Guide for the SAP OLTP source system. Choose ‘Create
              DataSource’ Enter the operating concern ‘IDEA’ (accrued).
               BW Server è Administrator Workbench è Modeling è Source systems
               Context menu (right mouse button) on source system ‘T90CLNT090‘ è
               Extractor Customizing...
               Business Information Warehouse è Customer-defined DataSources è
               Profitability Analysis è Create DataSource
               Choose ‘Execute’
                Field name         Enter
                Operating          IDEA
                concern
               Choose ‘Enter’
        1-1-6 Give your DataSource the following name:
              1_CO_PA%CL_IDEA## (where ## is your group number and %CL
              represents the R/3 system client) and create the DataSource.
                Field name         Enter
                DataSource         1_CO_PA%CL_IDEA##
                Create             ü


               Execute
        1-1-7 Choose ‘Company code’ as the partitioning characteristic.
                Field name                    Enter
                Field name for partitioning   COCOD
      1-1-4 Deselect all of the selected characteristics and value fields and choose the
            following ones.
              Field name characteristic     Characteristic description
              COCOD                         Company code
              COARE                         Controlling area
              DIVIS                         Division
              SLORG                         Sales organization
              Field name value fields       Description of value fields
              VV010                         Revenue
              VVIQT                         Invoiced quantity in sales unit
              VVOQT                         Sales order qua ntity
              VV030                         Customer discount
              VV040                         Material discount
              VV020                         Quantity discount
              VV070                         Accrued cash discount
              VV075                         Actual cash discount
              VV060                         Other discounts
             Enter ‘=init’ in the OK code field and confirm your input with Enter. This
             brings you proposals for the texts: Short text, medium length text and long
             text.
             Select the listed characteristics and key figures.
      1-1-5 Check your DataSource.


             Check
             There must not be any inconsistencies.

1-2   In the next step, you maintain the DataSource you want to gene rate, by selecting the
      selection fields and the fields you want to hide.
      1-2-1 Start the InfoCatalog from the same program by choosing ‘InfoCatalog’.
            This now brings you to the maintenance program for the DataSource you
            want to generate.
             InfoCatalog
             Do not specify any fields as selection fields and do not hide any fields.
             Save the DataSource.


             Save DataSource
             Do not generate any 12B Metadata.
             Answer the popup “Generating 12B Metadata”.
             12B Systems connected?
             Generate 12B Metadata?
             with ‘No’
             Confirm the information popup with yes, saying that the matching process
             to the InfoCatalog was successful.

1-3   In the final step, the DataSource is generated in the OLTP System.
      1-3-1 Generate the DataSource.


             Generate
      1-3-2 Leave the program for creating the DataSource in the OLTP System and go
            back to the BW Implementation Guide.


             Back



             Back
      1-3-3 Check the status of your DataSource. Branch to the CO-PA section of the
            Implementation Guide in the SAP OLTP source system and display the
            detailed information on your DataSource.
             Business Information Warehouse è Customer-defined DataSources è
             Profitability analysis è Tools è Display detailed information on
             DataSource
             Choose ‘Execute’
              Field name         Enter
              DataSource         1_CO_PA%CL_IDEA##
             Choose ‘Execute’

1-4   To transfer the generated DataSource from the OLTP System into the BW System,
      you have to carry out a DataSource replication for your source system. Once the
      replication has been carried out, the CO-PA DataSource is recognized by BW and
      you have to assign an InfoSource to the new DataSource. Then activate the
      communication structure and the transfer rules.
      1-4-1 Carry out the DataSource replication for the application component CO-PS
            for the source system ‘T90CLNT090’.
             BW Server è Administrator Workbench è Modeling è Source systems
             Context menu (right mouse button) on source system ‘T90CLNT090‘ è
             DataSource Overview.
       Context menu (right mouse button) on application component ‘CO-PA’
       è Replicate DataSources.

       Check that your DataSource ‘1_CO_PA%CL_IDEA##‘ now appears in the
       DataSource list under the application component ‚CO-PA‘.


1-4-4 Now assign an InfoSource to your DataSource ‘1_CO_PA%CL_IDEA##‘
       Context menu (right mouse button) on DataSource
       ‘1_CO_PA%CL_IDEA##‘ è Assign InfoSource.

       Copy the proposal over for the application: ‘1_CO_PA%CL_IDEA##’ as
       the name for the new InfoSource.

       Save the assignment of the DataSource 1_CO_PA%CL_IDEA##

       to the InfoSource 1_CO_PA%CL_IDEA##, by confirming the popup with
       ‘Yes’.

1-4-5 Then activate the communication structure and the transfer rules. Transfer
      all the InfoSource fields in the communication structure.
       “Expand” the communication structure


       Copy all InfoObjects
       “Close” the communication structure
       Set up the transfer method ‘PSA’ for the transfer rules. Activate your
       settings.
        ‘Transfer method‘
        Field name                    Enter
        PSA                           ü


       Activate
1-5   In the next step, you upload data to the PSA.
      1-5-1 Schedule an InfoPackage ‘GR## Initialization’ for your InfoSource and the
            source system ‘T90CLNT090’. Use only the PSA as the data target and
            initialize the delta process.
             BW Server è Administrator Workbench è Modeling è InfoSources
             è Expand ‘Application components’ è ‘Controlling’ è ‘Profitability
             Analysis’ è ‘1_CO_PA%CL_IDEA##’
             Context menu (right mouse button) on source system ‘T90CLNT090‘ è
             Create InfoPackage....
              Field name                      Enter
              Long description                GR## Initialization


             Enter
             Choose the ‘Processing’ tab
              Field name                              Enter
              PSA only                                ü
             ‘Update parameters’ tab
              Field name                              Enter
              Initialization of the delta process     ü
             ‘Schedule’ tab
              Field name                              Enter
              Start loading data immediately          ü
             Choose ‘Start’


             Monitor


      1-5-2 Now schedule an InfoPackage ‘GR## Delta’ for a delta upload.
                   Since no relevant documents have been posted in the OLTP System,
                   the delta up load will transfer 0 data records to the BW System.




             Context menu (right mouse button) on source system ‘T90CLNT090‘ è
             Create InfoPackage....
              Field name                      Enter
              Name                            GR## Delta
       Enter
       Choose the ‘Processing’ tab
        Field name                          Enter
        PSA only                            ü
       ‘Update parameters’ tab
        Field name                          Enter
        Delta update                        ü
       ‘Schedule’ tab
        Field name                          Enter
        Start loading data immediately      ü
       Choose ‘Start’


       Monitor


1-5-3 You can now display information on your uploading activities. Branch to
      the CO-PA section of the Implementation Guide in the SAP OLTP source
      system and display the detailed information on your DataSource.
       Business Information Warehouse è Customer-defined DataSources è
       Profitability Analysis è Tools è Display detailed information
       Choose ‘Execute’
        Field name        Enter
        InfoSource        1_CO_PA%CL_IDEA##
       Choose ‘Execute’
Data Extraction from FI-SL



                       BW Overview -              Tools for Generic
                      SAP R/3 Extraction           Data Extraction

                                                     Enhancing
                      LIS Data Extraction
                                                   Business Content

                                                   Special Topics:
                      LO Data Extraction
                                                  Delta Management

                                                Excursus: OLTP Access
                    Extraction from CO-PA
                                                   via Remote Cubes


                   Data Extraction from FI-SL




   © SAP AG 2001
Data Extraction from FI-SL (Special Ledger)



       Contents:
        l FI-SL: Positioning and overview
        l Data structures in FI-SL
        l DataSource generation
        l Extractor: Special operation methods
        l Extracting application data
        l Generic DataSources for set hierarchies




   © SAP AG 1999
Data Extraction from FI-SL: Unit Objectives



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

                   l Position FI-SL in R/3
                   l Understand the FI-SL data structures
                   l Generate FI-SL DataSources
                   l Explain the particular operating methods involved
                     in FI-SL extraction
                   l Create generic DataSources for set hierarchies




   © SAP AG 1999
Data Extraction from FI-SL: Overview Diagram


                                     Extractor Types

             Application-specific                      Cross-application

   BW Content                   Generic                    Generic
    Extractors                 Extractors                 Extractors

        FI                      LIS                        Database
              CO                                           table/view
       HR
             ...                       FI-SL
                                                           SAP Query
    LO Cockpit                        CO-PA


    Transparent               Transparent
                                                          Data Source
       Table                     Table

                                    Enhancements
                                    Enhancements


  © SAP AG 1999
Data Extraction from FI-SL: Business Scenario



                   l Your company uses FI-SL and wants to use this
                     data in SAP BW.
                     You are the person responsible for extracting data from
                     the R/3 System, and importing it into SAP BW. You
                     therefore have to create in R/3 and BW, the
                     components you need to perform this task.




   © SAP AG 1999
    FI-Special Ledger: Positioning


         l FI-SL is a system that combines data (planned and actual)
           from different levels of OLTP applications (for example, FI-
           GL, EC-PCA, CO-CCA).
         l In R/3, FI-SL enhances the functions and usability of these
           applications, without restricting their operative functions in
           any way.
         l FI-SL has planning functions and reporting tools. FI-SL
           reporting is, however, restricted:
                n   Cross-application reporting is not as diverse as SAP BW reporting.
                n   The OLTP System is optimized for transaction processing, and a
                    high reporting load would impact the overall performance of the
                    system.
         l Solution: FI-SL reporting in SAP BW



        © SAP AG 1999



n   To better understand the processes of extracting and updating data from R/3 FI-SL into SAP BW, we
    will first take a closer look at the functions in the FI Special Ledger system.
FI-SL: Overview (I)



                                   MM              SD




                                                                Da nal
                                                                  ter




                                                                              ng t
                                                                   ta




                                                                           sti en
                   CO




                                                                Ex




                                                                         Po stm
                                                                                s
                                                                           ju
                                                                         Ad
  FI




                                           FI-SL




                   Information System (Report Painter / Report Writer)



   © SAP AG 1999
    FI-SL: Overview (II)


          l The special ledger system (FI-SL) is a receiver system, which
            records data form various other SAP applications. It is not a
            sender system for other SAP applications.
          l In FI-SL, you are able to use flexible data structures (with
            additional fields) that correspond to individual business
            requirements. This allows you to combine and summarize
            information for any number of code combinations, at any
            level of detail.
          l Selective data retrieval: The assignment of transactions to
            particular combinations of company code/ledger or
            company/ledger, determines which ledgers are updated
            using the data.




        © SAP AG 1999



n   These are the basic ideas behind the R/3 FI-SL system.
FI-SL: Overview (III)



    l Adjustment postings are possible in the FI-SL system (for
      example, when valuing currencies). You can post data in
      various versions.
    l In FI-SL, you are able to use alternative charts of accounts
      (operative, group-specific, and country-specific charts of
      accounts).
    l Using various fiscal year variants, enables you to create
      weekly or monthly reports, for example.
    l Validations or substitutions allow you to check or modify
      specifically the validity of the data, at the point when it is
      entered into the FI-SL system.




   © SAP AG 1999
    Data Flow FI-SL


                                  SAP R/3 Applications
                                                                                          External
                                                                         Direct            Data
               FI            CO            MM             SD
                                                                       data entry

                                          Actual data / planned data

                              Online                                Follow-up posting
                          Validation / Substitution / Ledger Selection / Field Transfer

                                                                                 Currency
              Allocation                                                        translation
                                                User-defined
                                                FI-SL Tables
                                                                                  Balance
               Roll up
                                                                               carry forward



                         Information System (Report Painter / Report Writer)


        © SAP AG 1999



n   In addition to data from FI, CO, MM, and SD, external data, and data that is entered directly into the
    system, can also be posted into FI-SL.
n   The update takes place either online or as subsequent processing. With subsequent processing, a
    predefined number of data records are transferred to the FI-SL database tables, at a certain point in
    time, independently of the time the original document was created.
n   You can activate various functions for the update in the FI-SL Special Ledger:
    Ÿ the validation can check the data that is going to be updated, according to a set of freely definable
      rules
    Ÿ the substitution can replace the data with changed data, according to particular rules, before the
      update takes place.
    Ÿ the ledger selection allows an update from only partic ular ledgers
    Ÿ transferring fields determines which characteristics / dimensions are used in the FI-SL system.
      You use these dimensions when you are defining your special ledger.
n   Available operations on FI-SL data:
    Ÿ The function Currency translation transla tes amounts that have been posted to the ledger in the FI-
      SL system.
    Ÿ At the fiscal year change, use the Balance carryforward function to transfer actual and plan values
      from the previous fiscal year into the new fiscal year.
    Ÿ Allocation (assessment/distribution) means the transfer of an amount that has already been posted,
      from a sender object to one or more receiver objects.
    Ÿ To get faster reporting processing times, create a roll up ledger containing totaled and summarized
      data from one or more ledgers.
    Data Structures in FI-SL: Table Group ZZ

                                                                 Client
                                                                 Obj.No. Sender / Receiver
          Object table _1               ZZO                      ...
                                                                 "additional characteristics"

                                                                 Client
                                                                 Obj.No.movement attributes
          Object table _2               ZZC                      ...
          (optional)                                             "additional characteristics"

                                                                 Client
                                                                 Ledger
                                                                 Record type
                                                                 Version
             Totals table                ZZT                     Fiscal year
                                                                 Obj.No. Sender
                                                                 Obj.No. Receiver
                                                                 Obj.No. movement attributes (optional)
                                                                 ...
                                                                 "Key figures..."

                                                                 Client
         Actual line items              ZZA                      Record no. for line item record
                                                                 Ledger
                                                                 Record type...
                                                                 Client
                                                                 Record no. for line item record
          Plan line items                ZZP                     Ledger
                                                                 Record type...

         © SAP AG 1999



n   When you create an FI-SL table group, up to 5 tables with fixed naming conventions are created
    (after the organizational unit is determined for unit or company): Totals table (...T), actual line items
    tables (...A), plan line item tables (...P), object table_1 (object/partner) (...O), and the optional object
    table_2 (movement attribute) (...C).
n   To evaluate these tables via reporting, ledgers are defined that refer to this kind of table group (with
    the total table in the middle).
n   The totals table contains fixed key fields, such as, client, ledger, record type, version, fiscal year,
    object number, sender (credited account assignment element), object number receiver (credited
    account assignment element), company code, account number, business area, cost center, function
    area for the credited account assignment element and company code, account number, business area,
    function area for the debited account assignment element and additional characteristics.
n   The object number sender indicates a credited account assignment element (for example, cost center,
    profit center, or project) with additional properties (additional characteristics) that are contained in
    the object table_1.
n   In the same way, the object number receiver indicates a debited account assignment element (for
    example, cost center, order, profit center, or project) with additional properties (additional
    characteristics) that are contained in the object table_1.
    Totals Table ZZT in FI-SL
                                Client
                                Ledger
                                Record type                                    to distinguish between plan/actual
                                Version
                                Fiscal year
                                Obj.No. Sender                                 display on object table_1
                                Obj.No. Receiver                               for connecting with additional chars
                                Obj.No. movement attributes (optional)
                                Currency key
                                Base unit of measure
                                Debit/credit indicator
                                RPMAX: Period                                  Period block: RPMAX contains
                                Company code                                   the period value for key figures
                                Account number                                 TSL16, HSL16 and KSL16
                                Business area
     Totals table   ZZT         ...
                                TSLVT balance carryforward in transaction c.
                                TSL01                                          Transaction totals
                                ...                                            for periods in
                                TSL16                                          Transaction currency =
                                HSLVT balance carryforward in 2nd currency
                                HSL01                                          Transaction totals
                                ...                                            for periods in
                                HSL16                                          2. currency (e.g. local currency)
                                KSLVT balance carryforward in 3rd currency
                                KSL01                                          Transaction totals
                                ...                                            for periods in
                                KSL16                                          3. currency (e.g. group currency)
                                MSLVT Quantity balance carryforward
                                MSL01         Transaction totals
                                ...          for periods in
                                MSL16         Base unit of measure
        © SAP AG 1999



n   A particular feature of data modeling in the totals table, is the period block: There is a key field
    RPMAX (period) that specifies the current meaning of the period for key figures TSL16, HSL16,
    and KSL16. The meaning or the periods for key figures *SL01 to *SL15 is then output. This means,
    when RPMAX has the value "016", the values for key figures TSL16, HSL16 and KSL16 refer to
    period "016" of the fiscal year variant set in Customizing.

    If the RPMAX has the value "064", the values for key figures TSL16, HSL16 and KSL16 refer to the
    period "064", the values for key figures TSL15, HSL15 and KSL15 to period "063", ... of the fiscal
    year variant set in Customizing.
    You can display the fiscal year variants with a period number > 16 and the key figure values are
    divided among various data records with different RPMAX values.
n   Currency handling is explained here: The key figures TSL01 to TSL16 always have the transaction
    currency, which is specified in the field RTCUR (currency key).
    The key figures HSL01 to HSL16 have the so-called second currency: this is specified in
    Customizing and can be, for example, the house currency.
    The key figures KSL01 to KSL16 have the so-called third currency: this is specified in Customizing
    and can be, for example, the company code currency.
    Ledger in FI-SL


                                                                    Table group ZZ
                     Ledger L1                                         Object table _1     ZZO
                    Account / cost center                              Object table _2     ZZC

                                                                     totals table          ZZT

                                                                      Actual line items    ZZA
                Ledger L2                                              Plan line items     ZZP
                 Cost center / plant



                                                                    Table group YY
                                                                       Object table _1     YYO
                                                                       Object table _2     YYC


                         Ledger L3                                    totals table         YYT

                         Product / product group                      Actual line items    YYA
                                                                       Plan line items     YYP




         © SAP AG 1999



n   A ledger is a closed reporting area, which always refers to exactly one totals table. You can think of
    a ledger as a logical part of a totals table.
n   Several ledgers can be defined for a totals table.
n   A ledger is created in Customizing in a totals table. The ledger contains Metadata, such as the set of
    rules by which it is updated.
n   A maximum of 4 different sender structures (MOVE or programable Exit) can update a ledger.
    Manual correction postings are also possible.
n   But the transaction data itself remains in the tables of the table group.
    Difficulties Connecting FI-SL to BW



           l The FI-SL transaction data is stored in a group of tables.
           l A ledger can refer to part of a table group.
           l The object numbers in the totals table are not 'expressive'.
           l The period block means that a key figure TSL01 can refer to
             two different totals records in two different periods.
           l The currency information is only partially stored in the table
             group.
           l Quantity key figures




        © SAP AG 1999
          SAP AG




n   Here are some of the difficulties that are overcome by generating FI-SL DataSources.
n   When you generate an FI-SL DataSource, a ledger, which is based on a totals table, proposes a
    combination of characteristics and key figures.
    Updating the FI Special Ledger in BW

      BW System                                                        InfoCubes


                                                  Update rules

                                                                         InfoSource
                                         Communication Structure
                                         Communication Structure

                                                              Transfer Rules


                                                 transfer structure
                                                 transfer structure
                                       DataSource
                                                                                DataSource
                                       Replication                               3FI_SL_L1
                                                 transfer structure
                                                 transfer structure
        R/3 OLTP                                                               for Ledger L1
                                               Extract Structure ZZB
                                               Extract Structure ZZB



                                Totals Table                Object                   Object
                                    ZZT                   table_1ZZO               table_2ZZC
                        FI-SL
                                       OLTP :: FI-SL Table Group ZZ with Ledger L1
                                       OLTP FI-SL Table Group ZZ         Ledger


        © SAP AG 1999



n   The BW DataSources help prepare the data that is to be updated in the Business Information
    Warehouse.
n   The InfoSource with a DataSource allows the BW system to:
    Ÿ import the extracted data from the extraction structure in the SAP R/3 OLTP System
    Ÿ transfer the data to the BW transfer structure using the OLTP System transfer structure
    Ÿ convert the data using the transfer rules in BW and
    Ÿ transfer the data to the communication structure in BW.
      The InfoSource prepares the data for permanent storage in the InfoCube.
n   FI-SL DataSources cannot be delivered by SAP with BW Business Content for non-standard ledgers,
    because the ledgers and their FI-SL totals tables may link to user-defined fields and structures.
n   All other FI DataSources (FI-GL, FI-AR, FI-AP) are delivered with Business Content.
n   To provide an FI special ledger DataSource for BW, an extract structure (=transfer structure) must be
    generated for the FI-SL totals table in question. You then have to define the DataSource for the totals
    table ledger.
n   These steps will now be explained one by one...
n   The resulting DataSources transfer the totals records from the FI-SL. No single line items are
    transferred.
    Setting Up an FI-SL DataSource (Step 1)
    (in the BW IMG of the OLTP system)



                 1. Generating an Extract Structure ZZB for a Totals Table ZZT




                                        Extract Structure ZZB
                                        Extract Structure ZZB




                         Totals Table          Object table_1            Object table_2
                             ZZT                   ZZO                       ZZC


                            OLTP : FI-SL Table Group ZZ with Ledger L1




         © SAP AG 1999



n   So that you can transfer transaction data from your customer-defined ledgers from the source system
    OLTP into the Business Information Warehouse, you must first carry out the following Customizing
    actions in the OLTP System:
n   Use the transaction /NSBIW to call the BW IMG of the OLTP System:
    -> Business Information Warehouse
    -> Customer-defined DataSources
    -> Financial Accounting - Special Ledger
         Step 1:
         -> Generate transfer structure (= extract structure) for totals table
n   In step 1, you generate a transfer structure for your totals tables. Use this structure to transfer
    transaction data from your ledgers into the Business Information Warehouse.
n   The transfer structure contains fields from the totals table, from the object table and derived fields
    from Customizing.
n   The system derives the name of the transfer or extract structure according to the following rule for
    naming totals tables: If the name of the table ends in a T, the T is replaced with a B.
    If the name does not end in T, a B is added to the end of the name of the totals table.
n   If the same totals table is regenerated, the existing structure is overwritten.
    Setting Up an FI-SL DataSource (Step 2)
    (in the BW IMG of the OLTP system)



       2. Definition and Assignment of a DataSource 3FI_FL_L1 for a Ledger L1



       BW: Replicated DataSource
       BW: Replicated DataSource
                                              transfer structure
                                              transfer structure


                                      DataSource
                                      Replication
                                                                                   DataSource
                                               transfer structure
                                               transfer structure
                                                                                   3FI_SL_L1
                                            Extract Structure ZZB
                                            Extract Structure



                         Ledger L1
                                                                    totals table

        OLTP: FI-SL Table Group ZZ with Ledger L1
        OLTP:                                  L1


        © SAP AG 1999



n   Use the transaction /NSBIW to call the BW IMG of the OLTP System:
    -> Business Information Warehouse
    -> Customer-defined DataSources
    -> Financial Accounting - Special Ledger
         Step 2: -> Create InfoSource (= DataSource) for ledger
n   In step 2 you define a DataSource for a ledger and assign the DataSource to the ledger. When you
    carry out this step, all non-standard ledgers are displayed first, which already have extract structures
    for their totals tables. Formulated differently: Reasons for which a ledger is not displayed in step 2
    could be:
    Ÿ The ledger is a standard ledger (starts with a figure, for example, 00=general ledger 0F=Sales
      costs. There are Business Content DataSources for these.
    Ÿ the ledger's totals table does not have an extract structure.
n   The column status shows whether a DataSource was already assigned to the ledger. If this is the case,
    the traffic light is green. Select the ledger to which you want to assign a DataSource. Enter the name
    of the DataSource you want to assign to the ledger.
n   Naming convention: The name must start with the number 3. The system proposes a name with the
    prefix 3FI_SL_ and the name of the ledger.
n   You cannot change the name once you have saved the assignment.
n   Please note that ledgers are client-specific and DataSources are cross-client objects. Within a client, a
    DataSource can only be assigned to one ledger.
n   Result: The DataSource delivers transaction data from an FI-SL ledger on a totals table level.
    Transfer Structure Fields


                                Company                                            0COMPANY
                                Company code                                       0COMP_CODE
                                Chart of accounts                                  0CHRT_ACC
          transfer structure
                                Currency type                                      0CURTYPE
           transfer structure
                                Valuation view                                     0VALUATION
                                Version                                            0VERSION
                                Reporting value type                               0VTYPE
                                ... "additional characteristics"

                                Fiscal year/period                                 0FISCPER
                                Fiscal year variant                                0FISCVARNT
                                Currency unit                                      0CURRENCY
                                Value unit                                         0UNIT
                                Document currency                                  0DOC_CURR

                                Cumulated balance                                  0BALANCE
                                Total credit postings for period                   0CREDIT
                                Total debit postings for period                    0DEBIT
                                Quantity                                           0QUANTITY
                                Period sales (debit+credit)                        0SALES



        © SAP AG 1999




n   In this overview you can see the descriptions of the fields in the transfer structure of a DataSource
    3FI_SL_L1, in the left column. The right-hand column shows the InfoObjects used for these fields in
    BW.

n   Only the characteristics that are always part of the DataSource are named here. Depending on how
    the FI-SL totals tables are defined, other characteristics can be added. As a rule, the system proposes
    useful InfoObjects for assigning these characteristics when the DataSource is defined. Under some
    circumstances, you have to create new InfoObjects, especially if you are working with customer-
    defined fields (beginning with ZZ...).

n   A so-called global ledger has the company as the organizational unit. The characteristic Company
    only appears in the transfer structure with DataSource for global ledgers. With global ledgers, you
    then have the option of the characteristic Company code.

n   Other comments on DataSource:

    Ÿ Account plan and Fiscal Year Variant cannot be used as selection conditions.

    Ÿ The field Version shows the FI-SL-led version.

    Ÿ The FI-SL characteristic Record type is based on the InfoObject Reporting value type. The
      extractor transforms 2 reporting value types from 4 different FI-SL record types: Plan and actual.
    Extractor: Determining Key Figure Values


                totals table          ZZT                  transfer structure
                                                           transfer structure


                                                        ...
                                                        0FISCPER   0.2000 1.2000 2.2000 3.2000 (Fiscal year/period)
                                                        0FISCVARNT K4     K4     K4     K4     (Fiscal year variant)
                   Debit record Credit record
                                                        ...
    Ledger                     L1           L1          0CURRENCY DEM     DEM DEM       DEM (Currency unit)
    Fiscal year                2000         2000
    Currency key               DEM          DEM
    Debit/credit indicator     S            H           0BALANCE     1000    700     800   600   (Cum.balance: 0BALANCE
    RPMAX: Period              16           16                                                   for prev. period +
    ...                         ...                                                              SALES current period)
    TSLVT(balance              1000         0           0CREDIT      0       - 300   0     - 400 (Total credit postings
    carryforward )                                                                               for period)
    TSL01                      0            - 300
    TSL02                      100          0           0DEBIT       1000    0       100   200   (Total debit postings
    TSL03                      200          - 400                                                for period)
    ...
                                                        0SALES       1000    - 300   100   - 200 (Sales for period :
                                                                                                 0CREDIT+0DEBIT)1




                                                    Extractor
          © SAP AG 1999




n   This example shows how the extractor uses the key figure values from an FI-SL totals table. The
    values that the extractor gets in the format of the transfer structure, are as follows:

    Ÿ The time characteristic values are brought into the transfer structure from the respective totals
      table key figure and the totals table field RPMAX.

    Ÿ The key figure values of the credit records flow into 0CREDIT. The key figure values of the debit
      records flow into 0DEBIT.

    Ÿ 0SALES is calculated by 0DEBIT + 0CREDIT during the extraction process.

    Ÿ 0BALANCE is also calculated: 0BALANCE of the previous period (!) + 0SALES of the current
      period. Therefore, to fill the fields of 0BALANCE, specific DB selections apply during extraction,
      since the records from the previous period also have to be accessed. In BW, the InfoObject
      0BALANCE is under the exception aggregation last value (ref. 0FISCPER).
    Extractor: Handling Currencies and Quantities


                totals table         ZZT                transfer structure
                                                        transfer structure

                                                     ...
                                                     0FISCPER     1.2000 1.2000 1.2000 (Fiscal year/period)
                                                     0FISCVARNT   K4     K4     K4     (Fiscal year variant)
                             Debit rec.Credit rec.   ...
    Ledger                     L1     L1             0CURTYPE     00      0       30      (Currency type: Differentiates
    Fiscal year                2000 2000                                                  TSL*, HSL* and KSL*)
    Currency key               DEM DEM               0CURRENCY    DEM     USD     EUR     (Currency unit)
    Base unit of measure       ST                    0UNIT        ST      ST      ST      (Unit of measure)
    Debit/credit indicator     S       H             0DOC_CURR    DEM     DEM     DEM     (Document currency)
    RPMAX: Period              16     16
    ...                                              0BALANCE     - 300   100     - 200   (Cum. balance)

     TSL01                      0      - 300         0CREDIT      - 300   0       - 400   (Total credit postings)
     HSL01                     100     0
     KSL01                     200    - 400          0DEBIT        0      100      200    Total debit postings)
     MSL01                      60
    ...                                              0SALES       - 300   100     - 200   (Sales for period)

                                                     0QUANTITY     60     60       60     (Qty)

    Customizing: HSL* => USD
                KSL* => EUR


                                                Extractor
         © SAP AG 1999



n   This example shows how the extractor uses the currencies and quantity key figures from an FI-SL
    totals table.
n   Currencies:
    Ÿ In 0DOC_CURR the currency key of the transaction currency always flows from the FI-SL totals
      table.
    Ÿ Characteristic 0CURTYPE differentiates between the currency types (document currency,
      company code currency).
    Ÿ The currency unit (DEM, USD, EUR) of the specified currency type flows into 0CURRENCY.
n   Quantities:
    Ÿ The quantity key figures MSL01, ..., MSL16 are based on the key figure 0QUANTITY, which
      shows the totals table base unit of measure in the InfoObject 0UNIT. Warning! The query creators
      must restrict the characteristic 0CURTYPE to a characteristic value if they want to report on the
      quantities (0UNIT), since the quantities are transferred many times.
    Ÿ The additional quantities (ASL01 to ASL16 in the totals table) do not go into BW at the moment.
    Replicating DataSources in BW (Step 3)




                                     ...
                                     Replicating DataSources
                                     ...




        © SAP AG 1999



n   The DataSource must be replicated before it can be used in BW.
n   To do this, choose the 'Source Systems' tabstrip in the BW Administrator Workbench. Select the
    relevant OLTP system and choose Replicate DataSources from the context menu. All the
    DataSources that do not exist yet in BW are then transferred from the OLTP to the BW System.
    Assigning/Creating InfoSources (Step 4)




                                                                          ...
                                                                          Assigning InfoSources ...
                                                                          ...




        © SAP AG 1999



n   When the DataSource is replicated in BW, you have to assign it to an InfoSource or create an
    InfoSource first, if necessary.
    Maintaining the Communication Structure (Step 5)




                                                                       All of the fields in the
                                                                          extract structure
                                                                   are shown with the assigned
                                                                    InfoObjects in the template.




        © SAP AG 1999



n   Communication structures are created for InfoSources and thus represent part of an application in the
    OLTP System (for example, order data from Sales, purchase order data from Purchasing, and so on).
n   The total number of InfoObjects in the communication structure and extract structure may be
    different, since InfoObjects can be copied to the communication structure from all extract structures
    (several source systems).
    Maintaining Transfer Rules (Step 6)



                                                                 Activate




                 InfoObject from
                transfer structure                            or: Transfer
                                      or: Fixed Value           routine
         © SAP AG 1999



n   Transfer rules specify which fields in the transfer structure are to be transferred to which fields in the
    communication structure. You can create detailed conversion rules to change or add to data.
n   You can only choose one of the three types of transfer rules for each InfoObject in the
    communication structure:
    Ÿ The fields are copied from the transfer structure and not modified.
    Ÿ A field in the communication structure can be supplied with a fixed value for this source system.
    Ÿ A local transfer routine is used to supply the content of the communication structure with data
      when uploaded from this source system. The routine defined only applies to the selected
      InfoObject.
n   The transfer rules do not take effect until they have been activated.
    Maintaining InfoCubes and Update Rules (Step 7)




                                                                   ...
                                                                   Create InfoCube...
                                                                   ...
                                         ...
                                         Create update rules...
                                         ...

        © SAP AG 1999



n   Before data can be uploaded from the OLTP System to BW and evaluated in an InfoCube, the
    InfoCube must be created with the relevant update rules.
n   You maintain InfoCubes and update rules in the Administrator Workbench, Modeling > InfoCubes.
n   Update rules are always defined for a combination of an InfoCube and InfoSource. For this reason,
    an InfoSource can update several InfoCubes. An InfoCube, however, can be linked to several
    InfoSources via update rules.
n   There are various ways of updating InfoCube key figures into the update rules. Possible: Field to
    field assignment, formula and fixed value. You can also specify which date field in the InfoSource is
    to supply the time characteristics of the InfoCube with data. Similarly, a key figure can only be
    updated under certain conditions. In the same way, a currency translation can also be triggered when
    a key figure is updated to the InfoCube.
    Creating an InfoPackage (Step 8)




                                                                                  ...
                                                                                  Create InfoPackage...
                                                                                  ...




        © SAP AG 1999



n   Data requests sent to the source system are managed with the Scheduler. These requests are
    formulated for each InfoSource and source system and are divided into master and transaction data.
n   An InfoSource in a source system can have several different extraction jobs with different selection
    criteria. These are referred to as InfoPackages.
n   InfoPackages or groups of InfoPackages can be distributed to background processes using the R/3
    job planning facility. This means that you can fully automate the data transfer process and decide
    when and at what intervals data is to be extracted. Or, for example, you can use a factory calendar to
    specify that data is not to be extracted on public holidays, and so on.
n   The term 'transaction' in the Business Information Warehouse covers data retrieval in the OLTP and
    the successful updating of this data to the relevant InfoCubes. You can monitor the transfer and
    processing of the data closely using the Monitor function in the Administrator Workbench.
n   You can compile lists containing information on InfoPackage processing for each user, source
    system, day, etc.
    Monitoring the Upload Procedure




          l Monitoring data requests and data processing
          l IDoc processing status display
                 n      Info IDoc
                 n      Data IDoc
          l Detailed displays for selective monitoring




        © SAP AG 1999



n   The data transfer procedure is handled by a series of IDocs that facilitate communication and data
    transfer across system boundaries. These IDocs are divided into info IDocs and data IDocs.
n   The task of the individual info IDocs is indicated by their status: Status 0: data request received by
    source system, source system starts to select data.
    Status 1: this status indicates a data IDoc that contains further data processing information.
    ....
    Status 5: an error has occurred in the source system.
    ...
    Status 9: data selection in the OLTP System has been successfully completed.
n   With data IDocs, you can display a list of the processing steps that have been carried out to date.
    These steps are described by call numbers, such as: 50: start of update 51: determine InfoCubes to be
    updated 52: InfoCube successfully updated
    .…
    70: end of IDoc processing
    Status Display in the Monitor


                            l Status OK
             green                n   No errors occurred
                                  n   Data successfully transferred
                            l Status not defined
            yellow                n   Data update not completed (all IDocs)
                                  n   Invalid number of data packages (updated IDocs,
                                      process still running)
                                  n   Invalid data request (Scheduler, transfer structure
                                      not active)
                                  n   No data in source system (general view)
                            l Status not OK or
              red                 n   Data loaded incorrectly
                                  n   Status not defined after timeout
                                  n   Data only posted to incoming ALE IDoc


        © SAP AG 1999



n   The traffic light changes color depending on the context.
n   Note that a red light does not necessarily mean that an error has occurred.
    Extracting Application Data



    R/3 OLTP System                                              Business Information
                                                                 Warehouse




                                          Full Extract
                 Transaction            or Pseudo Data
                    Data
                                          Full Extract                      Staging
                                        or Delta Extract                    Engine

      Master                           + Transfer of Set
       Data                               Hierarchies


        © SAP AG 1999



n   When application data is extracted, the master data must be transferred first.
    It is useful if the Business Information Warehouse knows attributes in addition to the vendor number,
    for example, vendor name, address or region.
    Hierarchy information such as product hierarchy for the material, and so on, must be accessible when
    you transfer data into BW.
n   In FI-SL, you have the option of creating generic DataSources for set hierarchies.
n   There is only the update mode "Full Update" for the transaction data DataSources 3FI_SL_*.
n   You can run a pseudo delta process with the following procedure:
    Ÿ It is recommended that you use a full update in the InfoCube(s) for all closed posting periods.
    Ÿ You can check whether a posting period is open or closed in the OLTP IMG under Financial
      Accounting > Special Ledger > Actual posting > Posting periods (shows open posting periods).
    Ÿ It is recommended that you use a full update in the ODS and the update of these records for all
      posting periods that are 'still' open.
    Ÿ If the transaction data records for the 'still' open posting periods in the OLTP have been changed,
      the records are transferred again into the ODS. You can now only update the new and changed
      records from the ODS (the delta) into the InfoCube(s) by using the delta functionality in the ODS.
    Setting Up a Set Hierarchy DataSource
(in the BW IMG of the OLTP system)

     You can use a generic set hierarchy DataSource to transfer set hierarchies
     for characteristics from R/3-FI-SL total tables into BW.


     Set hierarchies for characteristic      Extracting the set hierarchy using a generated
     "Business Area" (RBUSA):                DataSource 4R_GSBER_0000_HIER:




        © SAP AG 1999



n   Use the transaction /NSBIW to call the BW IMG of the OLTP System:-> Customer-defined
    DataSources
    -> Financial Accounting - Special Ledger -> Generate DataSources for Set Hierarchies
n   Prerequisites: You have already created set hierarchies in the R/3 System (of the set class 0000 =
    general sets) (Note: To create a set hierarchy, choose Accounting > Financial Accounting > Special
    Ledger > Tools > Set maintenance > Sets > Create.
n   Activities for generating a DataSource for a set hierarchy:
n   1. Enter the table that the set uses (for example, an FI-SL totals table GLFUNCT) and then select the
    table field (for example, RBUSA Business Area) for the set.
n   2. If the characteristic is compounded in the BW, which the hierarchy is based on, and if you want to
    transfer its compounding information on the source system to BW, select BW Characteristic is
    compounded. Enter the data element to which the hierarchy is compounded. When the hierarchy is
    loaded, the compounding information is taken into account in BW. If you want to extract the FI-SL
    set of a characteristic compounded in BW, you have to run the compounding process in a customer
    exit. In transaction CMOD, create a project for SAP enhancement RSAP0001 and program
    EXIT_SAPLRSAP_004 (ZXRSAU04).
n   3. Run the program to generate the DataSource for the set hierarchy.
n   4. The new DataSource is called 4R_GSBER_0000_HIER. GSBER is the data element of the field
    GLFUNCT-RBUSA and 0000 specifies the set class.
Steps to FI-ISL Extraction




                                8. Create InfoPackage


                            7. Maintaining InfoCubes and Update Rules

                         6. Maintain transfer rules

                     5. Maintaining communication structure

                   4. Assigning InfoSources

               3. Replicate DataSource in BW

          2. Defining/assigning a DataSource for a ledger

       1. Generating an extractor structure for a
          totals table


   © SAP AG 1999
Data Extraction from FI-SL: Summary



                  You are now able to:
                  l Position FI-SL in R/3
                  l Understand the FI-SL data structures
                  l Generate FI-SL DataSources
                  l Explain the particular operating methods involved
                    in FI-SL extraction
                  l Create generic DataSources for set hierarchies




  © SAP AG 1999
Data Extraction from FI-SL - Exercises


                  Unit:       Data Extraction from FI-SL (Special Ledger)
                  Topic:      Attaching the Special Ledger to BW



                  At the conclusion of this exercise, you will be able to:
                  • Generate an FI-SL DataSource to a ledger in the OLTP System and
                    replicate it into BW
                  • Create an InfoSource for the DataSource, maintain its communication
                     structure, transfer rules and update rules, and update data from a ledger
                     into BW.
                  Your company has implemented an FI-SL table group GLFUNC
                  and a ledger L#, which will be used to report on certain account
                  assignment operations. This ledger L# presents a view on the
                  credit and debit postings in the posting periods of the fiscal year
                  2000. Your company wants to use this data in the Business
                  Information Warehouse.
                  You have been given the task of extracting the data from the R/3
                  System, importing it into the BW and loading the data into an
                  InfoCube. To do so, you have to create the corresponding
                  components in R/3 and in BW.

    1-1   The table group GLFUNC has the totals table GLFUNCT. This totals table has
          various ledgers, LA, LB ... to LX. The group number is assigned to the following
          ledger:

          Group numbers     : 00 to 24
          Ledger            : LA to LX
•   For # = 01: Group 01 è L# = LA
•   For # = 02: Group 02 è L# = LB
•   For # = 03: Group 03 è L# = LC
•   For # = 04: Group 04 è L# = LD
•   For # = 05: Group 05 è L# = LE
•   For # = 06: Group 06 è L# = LF
•   For # = 07: Group 07 è L# = LG
•   For # = 08: Group 08 è L# = LH
•   For # = 09: Group 09 è L# = LI
•   For # = 10: Group 10 è L# = LJ
•   For # = 11: Group 11 è L# = LK
•   For # = 12: Group 12 è L# = LL
•   For # = 13: Group 13 è L# = LM
•   For # = 14: Group 14 è L# = LN
•   For # = 15: Group 15 è L# = LO
•   For # = 16: Group 16 è L# = LP
•   For # = 17: Group 17 è L# = LQ
•   For # = 18: Group 18 è L# = LR
•   For # = 19: Group 19 è L# = LS
•   For # = 20: Group 20 è L# = LT
•   For # = 21: Group 21 è L# = LU
•   For # = 22: Group 22 è L# = LV
•   For # = 23: Group 23 è L# = LW
•   For # = 24: Group 24 è L# = LX


          1-1-8 In the Source System tab in Administrator Workbench, right-click
                T90CLNT090 and choose ‘Customizing for extractors…’ to call up the
                Implementation Guide for the SAP OLTP source system (transaction
                SBIW).
                 Choose the path: Business Information Warehouse à Customer-defined
                 DataSources à Financial Accounting – Special Ledger.
                 The extract structure (transfer structure) GLFUNCB was already generated
                 for the totals table GLFUNCT. In a new session, call up the Data
                 Dictionary: Path: SAP Menu à Tools à ABAP Workbench à
                 Development à Dictionary and display the structure GLFUNCB.
                 Which key figures are in the extract structure?




          1-1-9 To generate a DataSource for your ledger L#, call up the IMG activity
                “Create InfoSource for Ledger”, from the BW IMG.
       Position the cursor on your ledger L# and select it (F2). Copy the ledger text
       “BW ledger L#” (F6) as the description. Copy the proposed DataSource
       name “3FI_SL_L#“. Enter. Select “Local object” (F7) in the popup for
       creating the object catalog entry.
       In the next screen, deselect “Select selection fields”.
       Select “VALUTYP“ (reporting view).
       Then save your entries.
       Do not generate the 1.2B Metadata. You have now created the DataSource
              3FI_SL_L# under the application component FI-SL.
1-1-10 Now replicate this DataSource into BW. BW path: Administrator
       Workbench à Modeling à Source Systems. Right mouse-click on source
       system T90CLNT090 à DataSource Overview. Then expand the
       application component SAP R/3 in the right part of the box. Right mouse-
       click on application component FI-SL à Replicate DataSources. This
       action will copy your DataSource 3FI_SL_L# under the application
       component FI-SL.

1-1-11 Now create a new InfoSource for DataSource 3FI_SL_L#. To do this, click
       the right mouse button on your DataSource à Assign InfoSource. In the
       popup “InfoSource for DataSource”, create the InfoSource FI_SL_L#. As a
       description, enter “InfoSource for ledger L# ”. Enter. Save your changes.
       This brings you to the maintenance screen for the communication structure
       and the transfer rules.
1-1-12 Expand the communication structure maintenance and transfer all
       InfoSource fields to the left in the communication structure. Close the
       communication structure maintenance screen again.
1-1-13 Activate the transfer rules, which base all transfer structure InfoObjects on
       the communication structure InfoObjects.
1-1-14 Still in Modeling, now change to the data targets. Find the InfoCube
       FISLCUBE2 (FI-SL InfoCube for table group GLFUNC). Click the right
       mouse button on the InfoCube à Create update rules. Assign your
       InfoSource FI_SL_L# and start maintaining the update rules. Only change
       the update rules for the characteristic “Version” and use the me thod
       “constant” to assign the value “L#” (for all key figures) on a fixed basis.
       Activate your transfer rules.
1-1-15 Still in Modeling, now change to the InfoSources. In this tree, find your
       InfoSource FI_SL_L#. Click the right mouse button on the source system
       T90CLNT09 (below the InfoSource FI_SL_L#) and create the InfoPackage
       IP for ledger L#. This InfoPackage extracts the data from your ledger L#
       from the OLTP System and updates it to the InfoCube FISLCUBE2. When
       you create the InfoPackage, do not enter any selection conditions under
       “Select data”. Under “Processing”, select the checkbox next to “data targets
       only”. Under “data targets”, select the InfoCube FISLCUBE2. Under
       “Update parameters”, choose “Full update” and “Always update data, even
       if no master data exists” and start loading the data immediately.
Data Extraction from FI-SL - Solutions


                Unit:        Data Extraction from FI-SL (Special Ledger)
                Topic:       Attaching the Special Ledger to BW



  1-1   This is a template solution using the ledger LZ.


        1-1-16 In the Source System tab in Administrator Workbench, right-click
               T90CLNT090 and choose ‘Customizing for extractors…’ to call up the
               Implementation Guide for the SAP OLTP source system (transaction
               SBIW).




               Choose the path: Business Information Warehouse à Customer-defined
               DataSources à Financial Accounting – Special Ledger.
The extract structure (transfer structure) GLFUNCB was already generated
for the totals table GLFUNCT. In a new session, call up the Data
Dictionary: Path: SAP Menu à Tools à ABAP Workbench à
Development à Dictionary and display the structure GLFUNCB.
       Which key figures are in the extract structure?
        BALANCE (cumulated balance)

        DEBIT (total debit postings)

        CREDIT (total credit postings)

        TURNOVER (sales for the period)

        QUANTITY (consumption quantity)




1-1-17 To generate a DataSource for your ledger LZ, call up the IMG activity
       “Create InfoSource for Ledger”, from the BW IMG.




       Position the cursor on your ledger LZ and select it (F2). Copy the ledger text
       “BW ledger LZ” (F6) as the description. Copy the proposed DataSource
name “3FI_SL_LZ“. Enter. Select “Local object” (F7) in the popup for
creating the object catalog entry.




In the next screen, deselect “Choose selection fields”.
Select “VALUTYP“ (reporting view).
Then save your entries.
       Do not generate the 1.2B Metadata. You have now created the DataSource
              FI_SL_LZ under the application component FI-SL.
1-1-18 Now replicate this DataSource into BW. BW path: Administrator
       Workbench à Modeling à Source Systems. Right mouse-click on source
       system T90CLNT090 à DataSource Overview. Then expand the
       applicatio n component SAP R/3 in the right part of the box. Right mouse-
       click on application component FI-SL à Replicate DataSources.




       This action will copy your DataSource 3FI_SL_LZ under the application
       component FI-SL.

1-1-19 Now create a new InfoSource for DataSource 3FI_SL_LZ. To do this, click
       the right mouse button on your DataSource à Assign InfoSource. In the
       popup “InfoSource for DataSource”, create the InfoSource FI_SL_LZ.




       As a description, enter “InfoSource for ledger LZ”. Enter. Save your
       changes. This brings you to the maintenance screen for the communication
       structure and the transfer rules.
1-1-20 Expand the communication structure maintenance and transfer all
       InfoSource fields to the left in the communication structure. Close the
       communication structure ma intenance screen again.




1-1-21 Activate the transfer rules, which base all transfer structure InfoObjects on
       the communication structure InfoObjects.
1-1-22 Still in Modeling, now change to the data targets. Find the InfoCube
       FISLCUBE2 (FI-SL InfoCube for table group GLFUNC). Click the right
       mouse button on the InfoCube à Create update rules.
Assign your InfoSource FI_SL_LZ and start maintaining the update rules.




Only change the update rules for the characteristic “Version” and use the
method “constant” to assign the value “LZ” (for all key figures) on a fixed
basis. Activate your transfer rules.
1-1-23 Still in Modeling, now change to the InfoSources. In this tree, find your
       InfoSource FI_SL_LZ. Click the right mouse button on the source system
       T90CLNT09 (below the InfoSource FI_SL_LZ) and create the InfoPackage
       IP for ledger LZ. This InfoPackage extracts the data from your ledger LZ
       from the OLTP System and updates it to the InfoCube FISLCUBE2.
When you create the InfoPackage, do not enter any selection conditions
under “Select data”. Under “Processing”, select the checkbox next to “data
targets only”. Under “data targets”, select the InfoCube FISLCUBE2. Under
“Update parameters”, choose “Full update” and “Always update data, even
if no master data exists” and start loading the data immediately.
Tools for Generic Data Extraction



                       BW Overview -              Tools for Generic
                      SAP R/3 Extraction           Data Extraction

                                                     Enhancing
                      LIS Data Extraction
                                                   Business Content

                                                   Special Topics:
                      LO Data Extraction
                                                  Delta Management

                                                Excursus: OLTP Access
                    Extraction from CO-PA
                                                   via Remote Cubes


                   Data Extraction from FI-SL




   © SAP AG 2001
Tools for Generic Data Extraction



       Contents:
        l DataSources for master data
        l DataSources for transaction data
        l Extraction types
        l Class system - overview
        l DataSources for classification data (special features)




   © SAP AG 1999
Tools for Generic Data Extraction:
Unit Objectives



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

                   l Create DataSources for master data
                   l Create DataSources for transaction data
                   l Use different extraction types to create generic
                     extractors
                   l Understand the class system overview

                   l Create DataSources for classification data and
                     explain their special features.




   © SAP AG 1999
    Tools for Generic Data Extraction: Overview
    Diagram


                                           Extractor Types

                   Application-specific                            Cross-application


         BW Content                     Generic                          Generic
          Extractors                   Extractors                       Extractors

              FI                        LIS                              Database
                    CO                                                   table/view
             HR
                   ...                        FI-SL
                                                                         SAP Query
          LO Cockpit                          CO-PA


          Transparent                 Transparent
                                                                        Data Source
             Table                       Table

                                          Enhancements
                                          Enhancements

        © SAP AG 1999



n   The transaction data entering the Business Information Warehouse by means of extractors originates
    from very different modules. Due to past developments, very different extraction mechanisms are
    necessary.
Tools for Generic Data Extraction: Business
Scenario

                   l Your company wants to analyze the purchase
                     requisitions created in R/3 in the Business
                     Information Warehouse. Since Business Content
                     does not include an InfoSource for this purpose, you
                     have been given the task of generating a DataSource
                     for purchase requisitions using the tools for generic
                     data extraction.
                      The requested quantities are to be analyzed
                      according to material. Similarly, reports are also to be
                      supported using the old material number that was
                      transferred from the legacy system to the material
                      master in the R/3 System.
                      The old material number is to be maintained as a
                      material attribute. In order to do so, you have to
                      generate a new InfoSource for the material
                      characteristic with the attribute "old material
                      number".
   © SAP AG 1999
Using the Tool



                  When should you use the tools for
          generic data extraction for creating a DataSource?


    l Business Content does not include a DataSource for
      your application.
    l The application does not feature its own generic data
      extraction method.
    l You are using your own programs in SAP R/3 to
      populate (fill) your tables.




  © SAP AG 1999
Transaction and Master Data


           InfoCube                                     Master Data Attributes
                                                                                 Texts
                     Update rules

             Communication Structure
             Communication Structure                          Communication Structure
                                                              Communication

                    Transfer Rules                                 Transfer Rules

                   transfer structure
                    transfer                                      transfer structure
                                                                  transfer structure
                                         Tools for generic
                                          data extraction
                                         Transaction RSO2
                   transfer structure
                   transfer structure                             transfer structure
                                                                   transfer

           Extraction Source Structure
           Extraction Source Structure                       Extraction Source Structure
                                                             Extraction Source Structure



                   ZKOPF                                         ZATTR
                                                   Master Data            ZTXT
 Transaction Data            ZITM
                                                     Texts


   © SAP AG 1999
    Tools for Generic Data Extraction RSO2



                                                                                  DataSource
                                                                             for transaction data,
       Maintain Generic DataSource                                           master data attributes
                                                                                   and texts




         © SAP AG 1999



n   The tools for generic data extraction are launched with the transaction RSO2.
n   You can use this transaction to create DataSources for both transaction and master data, and for texts.
n   The technical name of new characteristics (InfoObjects) must be between 4 and 9 characters long.
    The characteristics are created in two steps:
    First, the properties of the characteristics (the extractors) are defined with the relevant extractor type
    and characteristic compounding.
    Next, the InfoObjects (if they exist) are assigned to the characteristic attributes defined in the
    extractor. If these do not exist, they must be created using the 'Assign attributes' transaction.
    Creating DataSources for Transaction Data


                                                                                          Create
             Create DataSources for transaction data


              DataSource ZEBAN
                                                                   Extraction from view
              Application comp.   MM
                                                                   Extraction from query

              Extraction from DB view                       Extraction from SAP Query
               View/Table                                    InfoSet


              Texts
              Short description    Pur. req.
              Medium description Purchase requisitions
              Long description      Purchase requisitions




        © SAP AG 1999



n   When you create a generic InfoSource for transaction data you first have to enter the application
    component and texts for describing the InfoSource. The application component determines where the
    DataSource is stored in the DataSources tab in the Administrator Workbench after the DataSources
    have been replicated.
n   You can then select the data source for the generic DataSource. Here you can choose both
    transparent tables and database views. You can also use SAP Query InfoSets to extract data.
n   Choose the 'Extraction from view' button, if you want to extract the data from a transparent table or
    database view, and enter the name of the table or view. The extract structure of the generated
    DataSource is then identical to that of the view or table.
n   Choose the 'Extraction from Query' button if you want to use an SAP Query InfoSet as a data source.
    Then select the required InfoSet from the InfoSet catalog.
    You can go to the screen for maintaining an existing InfoSet by double -clicking on its name.
    Digression: Extraction Using View


         Dictionary: Maintain VIEW ZMATNRATTR
         Dictionary: Maintain VIEW ZMATNRATTR

          Database View        ZMATNRATTR
          Short text          Attributes material number

          Tables                                   Join conditions
          MARA              Table          Field name     = Table           Field name




                                                                    If data is extracted from
                           View fields
                                                                 several tables, the link between
           View field     Table          Field name
                                                                        the tables must be
           MANDT          MARA           MANDT
                                                                              defined.
           MATNR          MARA           MATNR
           BISMT          MARA           BISMT




        © SAP AG 1999



n   You create views with transaction SE11 (ABAP Workbench Dictionary). To do so, you have to
    choose the view type 'Database view'.
n   The tables must be joined by identical fields in the join conditions.
n   All of the key fields in the tables must be defined as view fields, otherwise some data records may
    overlap and the data will not be transferred to BW. Characteristics can be ignored if you are certain
    that they are not used in the table keys. If characteristics with only one attribute are used, they can be
    assigned selection conditions (Goto > Selection conditions). If the master data is time-dependent, the
    DATETO and DATEFROM fields have to be included in the view.
n   The sequence of fields for defining a database view for extracting texts is fixed.
    Ÿ Client
    Ÿ Language with the domain SPRAS, if the defined texts are language dependent
    Ÿ Key field: if compounding is used, all of the relevant characteristics have to be listed.
    Ÿ If the data is time-dependent, the DATETO and DATEFROM fields
    Ÿ Short, medium and long texts
n   If one of the text fields is not required, it must not be checked. If there is no medium-length text, the
    last two fields are the short text and long text fields.
    Digression: Creating InfoSets


             Create DataSources for transaction data                                            Extraction
                      Create                           Fill in the
                                                     required fields                           button from
                                3                                                                 query
               DataSource ZEBAN
                                                           1           Extraction from view
               Application comp.     MM                                                            2
                                                                       Extraction from query

               Extraction from DB view                          Extraction from SAP Query
                View/Table                                       InfoSet


               Texts
               Short description     Pur. req.
                                                                                  Keep the field
              Medium description Purchase requisitions
                                                                                 empty to create
         Create
         Create DataSource
              Long description   Purchase requisitions                            a new InfoSet
          DataSource ZEBAN
          InfoSet        ZEB
                                     Name
                                    InfoSet      4
               InfoSet Maint.


                             5
         © SAP AG 1999



n   SAP Query is a powerful tool for defining reports in the OLTP system and supports different forms
    of reporting. It allows users to define and execute their own reports on data in the SAP System
    without any knowledge of the ABAP programming language.
n   Reports are structured by entering texts and selecting fields and options in SAP Query. The relevant
    fields can be selected more easily using InfoSets (before Release 4.6C: functional areas) 'InfoSets'
    are seen as 'data sources'. These data sources can be used for extracting in BW.
n   The procedure for creating an InfoSet from the DataSource definition:
    1. Fill out all of the required entry fields (application component, descriptions).
    2. Choose the 'Extraction from query' button.
    3. Choose the 'Create' icon. A new screen is displayed.
    4. Enter a name for the InfoSet and press the 'InfoSet maintenance' button.
    5. In the screen that follows, press the 'Create' button.
    Then carry out the following steps:
    Ÿ Select the data source (DB tables/views, joins, logical DB)
    Ÿ Define the field groups and assign the fields
    InfoSets



        l InfoSets are the 'data sources' for SAP QUERY
        l InfoSets are 'semantic layers'
               n Conceal the technical properties of the physical data sources
               n Limit and extend existing physical data sources
        l Potential physical data sources
               n Database tables/views
               n Table joins (limited according to ABAP SELECT)
               n Logical databases
               n Data retrieval programs (freely coded accesses)




         © SAP AG 1999



n   'InfoSet' from OLTP Release 4.6C, until then the valid name is 'functional area'.
n   An InfoSet is a special view of a dataset (logical database, table join, table, sequential file) and is
    used by SAP Query as a data source. InfoSets, therefore, determine the tables or fields in these tables
    that can be referenced by a report. In most cases, InfoSets are based on logical databases.
n   SAP Query features a component for maintaining InfoSets. When you create an InfoSet, a data
    source in an application system is selected.
n   SAP Query is relevant for the Business Information Warehouse because it allows you to define the
    extract structure by selecting fields in a logical database, table join or other datasets in the form of an
    InfoSet. In this way, you can use the generic data extraction function for master or transaction data
    from any InfoSet. When you do so, a query is created for an InfoSet that retrieves data and transfers
    it to the generic extractor.
n   InfoSets represent an additional, convenient data source for extracting data generically. Logical
    databases in all R/3 applications, table joins and further datasets can be used as a data source for BW.
    InfoSet (here: using logical database)


               InfoSet: Title and Database
                Name                       Purchase requisitions
                Authorization group                                                    Name
                                                                                   of the InfoSet
                Data Source
                    Table join using basis table
                    direct reading of table
                    Logical data base
                              Selection screen ver.
                    Data retrieval using program
                                        Data structure

                                                                                   Choose a
                Options                                                             logical
                   no automatic text identification                                database
                 ! Fixed point arithmetic



                          Continue


        © SAP AG 1999



n   To create InfoSets with access to a logical database, you first have to make just two entries:
    Ÿ the name of the InfoSet
    Ÿ the logical database.
n   Note: the automatic text identification leads to the text being shown for table fields that support this
    function. It is deactivated for extraction purposes.
    InfoSet Maintenance

      Generate                                                          Additional fields, selection
                                                                                   fields, selection
       InfoSet                                                            conditions and so on
                                                                                            so on



      Available fields
                fields
        of the data
        of the data
          source
          source                                                                           Selected and
                                                                                           Selected and
                                                                                             grouped
                                                                                             grouped
                                                                                              fields
                                                                                               fields
      Transfer field




                                                                                                Field
                                                                                                 Field
          Texts are
          Texts are                                                                         information
                                                                                             information
       automatically
       automatically
        available (if
         available (if
          they are
           they are
       selected and
        selected and
            exist)
             exist)
        © SAP AG 1999



n   Since the number of fields in a data source (logical database) can be very high, fields can be
    combined in logical units called field groups. Field groups are groups of several fields representing a
    logical unit in an InfoSet. The extract structure is always formed from all of the fields in all of the
    field groups.
n   When you create an InfoSet, you have a choice of options for forming field groups ('read all table
    fields', 'read key fields' and 'create empty field groups'). You can create other field groups if you need
    to.
    The fields need in the extractor must be assigned from the the logical database to the field groups.
n   You then have to generate the InfoSet.
InfoSets: Additional Options



      l Additional calculated fields
             n     Single fields (with DDIC reference 'LIKE')
             n     Structures (as of 4.6C)
             n     Tables
      l Additional check of selection conditions
      l Defining table alias (with multiple use of a table)
      l Coding for different events




   © SAP AG 1999
    Extract Structure/DataSource




                Create DataSource (SAP Query)
                    DataSource           ZEBAN
                    InfoSet              ZEB

                        InfoSet Maint.
                1


                                                                            2       Edit
                                                                                 DataSource




        © SAP AG 1999



n   Once you have defined the InfoSet, return to the screen for creating DataSources.
n   'Continue' automatically creates the extract structure (and automatically gives it a name).
n   You get to the next screen where you can make further assignments for the DataSource (for example,
    defining the selection fields).
    Restrictions


        l No automatic delta management
          (delta management possible via data selection)
        l The data quantity for each request is limited
               n   A request can process several 100 MB of data
               n   -> very large quantities of data possible with suitable selections and
                   several requests
        l Maximum of 16 tables in joins (no cluster tables)
        l Up to 2.0B/P3: Selection only in fields of field group J
        l Optimum performance for complex requests can only be
          achieved with application-specific extractors




        © SAP AG 1999



J   As of 2.0B/Patch3, you can make selections for fields in the field group and for all the selection
    fields of an InfoSet; this applies particularly to the 'parameter fields' of logical databases.
    Generic Extractor and Delta Management




     R/3 OLTP                                        BW


                                                                                 l Delete last request
                                                                                   with the same
    Change/Create                                                                  selection
    only > '00                                                                   l Reload request
                                                   Full upload, selection '00
                              ‘00
                                                   Full upload, selection '99   Load request once
    98 and 99 =               ‘99
    closed
    periods                                        Full upload, selection '98 Load request once
                              ‘98

                        Source Table
                        Source




        © SAP AG 1999



n   A separate delta management facility is not available for the generic data extraction tools. A limited
    type of delta management is feasible in which periods or date fields (creation and change dates) can
    be restricted via selection criteria when the data is uploaded.
n   The example above shows that by selecting the period, only the period in which documents can be
    changed or posted is to be transferred to the BW. Naturally, any existing requests for this period in
    BW have to be deleted.
n   No changes can be made to the documents for periods that have already been closed. For this reason,
    there is no delta here between the OLTP and BW systems, with the result that the data does not have
    to be loaded again.
Steps for Transaction Data Extractor




                                 7. Schedule InfoPackage

                             6. Create InfoPackage

                         5. Maintain transfer rules

                      4. Maintain/activate communication structure

                   3. Replicate/assign DataSources

            2. (Create InfoSet / enhance table)

        1. Create DataSources for transaction data




   © SAP AG 1999
Steps for Master Data Extractor




                                     8. Schedule InfoPackages

                                 7. Create InfoPackage for texts

                             6. Create InfoPackage for Master Data

                         5. Maintain transfer rules

                      4. Maintain attributes (communication structure)

                   3. Replicate and assign DataSources

          2. Create DataSources for texts

      1. Create DataSources for master data attributes




   © SAP AG 1999
    Class System: Overview (I)


           l Task of the class system: Describe any object with the help of
             characteristics and group similar objects in classes.
           l Purpose of the class system: Optimum usage for searching
             objects
           l Creating in several steps:
                  n     Defining properties (using characteristics)
                  n     Creating classes and assigning characteristics to the classes
                  n     Assigning objects to the classes (objects are described by
                        characteristics)
                  n     Characteristics have values (valuation)
               Searching objects with characteristics as search criteria




        © SAP AG 1999



n   To help you grasp the DataSource maintenance for classification data from R/3, here is an overview
    of the cla ssification system in the R/3 system.
n   A class system has the role of describing any object with the help of characteristics and grouping
    similar objects in classes, to classify them, so that they can be found easier at a later date.
n   You can find an object by using the classes and the characteristics defined in the classes, which serve
    as search conditions. This means you can be sure to easily find identical or similar objects from the
    characteristic view.
n   You can classify any object type with the help of the class system.
n   A prerequisite for this is that the required settings are maintained in Customizing for the class
    system.
    Class System: Overview (II)


            Characteristic maint.                       Object: Monitor M-01
            - Price range                               Price range:                      02 Standard
            - Manufacturer                              Manufacturer:                     01 Sunny
            - Screen diameter                           Screen diameter:                  14 inches
            - Screen repetition frequency               Screen repetition freq.:          01 1024x768
            - Indicator and so on...                    ...
                   Characteristics                                       Properties


            Class maintenance               Classification                Object search
              Class type: Material
                                            Assignment of object M-01
                                                                         Find the initial class
              Class: Monitors               to monitor class

                                            Characteristic evaluation:
                - Price range                                            Object search using the
                                           Price range:   02 Standard
                - Manufacturer                                           initial class
                                           Manufacturer     01 Sunny
                - Screen diameter
                                           Screen diameter 14 inches
                - Screen rep. Freq.
                                           Screen rep. frequency: 01


                                      Functions in class system
        © SAP AG 1999



n   The process of building a class system consists of several steps:
n   Defining the properties:
    Ÿ The properties of an object are based on characteristics. The characteristics are created centrally in
      the R/3 System.
n   Creating classes:
    Ÿ The objects to be classified must be stored in classes. These classes must be created in the first
      step. The characteristics are assigned to the classes. Every class must be assigned to a class type.
      The class type controls the processing of classes as well as the classification and the object search
      in these classes. A class type always refers to a certain object type, for example, material. Objects
      of this type can then be classified in classes for this class type.
n   Assigning objects:
    Ÿ When the classes you want to classify have been created, the objects can be assigned to these
      classes. The objects are described by the characteristics contained in the class. Assigning the
      characteristic values is called 'characteristic evaluation'.
n   The data required to use the class system is thus made available. The system can then be used to find
    objects with very specific properties. The characterisics are used in the search as search criteria. The
    characteristics are evaluated and the entered values are compared to the values of the classified
    object.
Extracting Classification Data



                                   - Generic DataSources for extraction
                                     all classifiable objects
                                     all class types
                                   - User Exit no longer required
      - Not supported by
        BCT extractors             - automatic creation of text DataSources
                                     for those characteristics used
      - Extraction possible with     in the classification
        BCT enhancement:
        Enhancement of extract
        structures and use of
        User Exits to read
        classification data




BCT Rel. 1.2B                 PI-99               PI-2000


   © SAP AG 1999
    Example: Material Classification


                                                                      DataSource attribute:
         Material master data                                         Material classification
      Material:       M-01
                                                                  Material
      Material type:     HAWA
                                                                  DATETO
      Industry:       M
                                                                  DATEFROM
      Material group: 00207
                                                                  Price range
                                                                  Manufacturer
      ........
                                                                  Screen diameter
        Class type: 001 Material                                  ...

        Class: CL126 Monitors
                                                                  Text DataSource: Price range
      Price class:    02
      Manufacturer:    01                                         Text DataSource: Price range
      Screen diameter:    14
                                                                     Text DataSource: Screen
                                                                                      Screen
      ........                                                               diameter
                                                                             diameter

                                                                   Generated DataSources

        © SAP AG 1999



n   The characteristic evaluations of the classified objects in the R/3 System are made available to the
    Business Information Warehouse as attributes by a generated DataSource.
n   The above example uses the attribute DataSource "material classification".
n   Text DataSources are automatically created for the characteristics to be used in the classification,
    which can help extract the texts in the Business Information Warehouse.
n   The above example uses the text DataSources "price class", "manufacturer" and "screen diameter".
Combining Master Data and Class Properties
(Characteristics)


 BW                                                  0MATERIAL attributes:
                               InfoSource            • Material type
                                                     • Industry
                               0MATERIAL             • Material group
                                                     •....
                                                     • Price range
                                                     • Manufacturer
                                                     • Screen diameter

  R/3             DataSource                  DataSource (classification)

          0MATERIAL_ATTR                    1CL_OMAT001

        Fields                              Fields
        • Material type                     • Price range
        • Industry                          • Manufacturer
        • Material group                    • Screen diameter
        • ...


  © SAP AG 1999
    Maintaining DataSources for Classification Data (I)



         l Creating the DataSource in the BW IMG of the R/3 System
                 n   Entries:
                         w   a DataSource of a BCT characteristic is used as a basis (a so-
                             called Basis DataSource: for example, 0MATERIAL_ATTR for
                             material classification)
                         w   Client
                         w   Class type: (for example, 001 material class)
                         w   Object table (for example, MARA)

         l Specification for the DataSource characteristics
                 n   Enter the characteristic of a class from the selected class
                     type, which you want to extract as an attribute in the
                     DataSource for the basic characteristic.




         © SAP AG 1999



n   Make the following Customizing steps in maintaining a DataSource for classification data. Without
    this you cannot transfer attributes and texts for class system objects from the source system R/3 into
    the Business Information Warehouse.
n   Use the transaction /NSBIW to call the BW IMG of the R/3 System:
    Ÿ -> Business Information Warehouse
    Ÿ -> Customer-defined DataSources
    Ÿ -> Cross-application components
    Ÿ -> Class system
    Ÿ -> Maintain DataSources for classification data
n   1. Enter a basic DataSource that you want to enhance. Use exactly that BCT DataSource that selects
    the attributes for the class system attributes in BCT (for example, 0MATERIAL_ATTR).
n   2. Choose the client, the class type, (for example, 001 material class) and the object table (for
    example, MARA) from which the classification data is to be transferred.
n   3. Select the DataSource that you want to assign, and navigate to "characteristics" with a double -
    click.
n   4. Choose "New entries" to enter the characteristics and dimensions that you want to assign. You can
    take the correct IDs of the characteristics or dimensions from the classification master data. Path:
    Ÿ -> SAP Menu
    Ÿ -> Logistics ...
      Maintaining DataSources for Classification Data (II)



           l Resulting structures of the generated DataSources:
                  n   DataSource attribute:
                          w   Basic characteristic
                          w   Select characteristics from the selected class (attribute)
                          w   Time dependency
                  n   Every charateristic with the data type CHAR has a text
                      DataSource generated with the following structure:
                          w   Characteristic value
                          w   Date valid from
                          w   Date valid from
                          w   Language keys
                          w   Name of the characteristic value (text)



          © SAP AG 1999



...
      Ÿ -> Central functions
      Ÿ -> Class system
      Ÿ -> Master Data
      Ÿ -> Class administration
      Ÿ Enter the class type (for example, 001) and the class (for example, CL126 monitors) and display
        the relevant characteristics. This is where you will find the relevant characteristic IDs required for
        creating the DataSource. Please note that you can only transfer characteristics with single values in
        the DataSource. What is more, you cannot use interval values. You can check the evaluation by
        double clicking on a characteristic > basic data (in the master data). You are recommended also to
        only transfer characteristics in the DataSource that do not refer to the master data table. You can
        check the reference by double clicking on a characteristic > additional data (in the master data). If
        a characteristic links to a master data table field (for example, in the MARA), its attribute values
        can be extracted with the basic DataSource (for example 0MATERIAL_ATTR).
n     5. You can enter an item number if you want to define a sequence within the characteristics. The
      status is given automatically.
      Ÿ N= New, the status appears when a DataSource is created as new.
      Ÿ R = Ready, the status is automatically set to R after generation takes place.
      Ÿ If you want to change the characteristic, set the status back to N before generating it.
n     6. Choose "DataSource" to generate the DataSource. At the same time, the system generates the text
      DataSources for the characteristics of the data type CHAR.
n     7. The prefix 1CL_... is given to all DataSources generated in this way.
Special Features (I)



   l Only classifying charateristics without multiple
     evaluation and without intervals can be recorded as
     attributes in the DatSources.
   l Classifying characteristics that link to master data tables
     cannot be a part of a DataSource for extracting
     classification data. Attributes like this are extracted with
     the attribute DataSources of the BCT.
   l When you use classifying dimensions, no text
     DataSources are created. The DataSources entered
     under dimensions in Release 2.0B are only dummy
     entries.




   © SAP AG 1999
    Special Features (II)



         l Every DataSource for classification data is time-
           dependent. If the engineering change management in the
           classification for a special characteristic is activated, the
           DataSource can deliver historic constellations. If the
           engineering change management is not activated, the
           time interval is set to the maximum area. The text
           DataSources also always deliver time-dependent data.
         l Transport functions for the generated DatSources are
           available as of BW Release 2.1C
         l As of Release 2.1C, the generated attribute DataSources
           will be delta compatible for classification DataSources.




        © SAP AG 1999



n   Notes on time-dependency:
n   If there is no engineering change management activated in Customizing for the class for which you
    want to generate the DataSources, the time dependent fields (DATETO and DATEFROM) are
    brought into the extract structure and filled with the maximum number of area values. In this case,
    the time-dependent fields (DATETO and DATEFROM) are not visible in the transfer structure.
    Ÿ If the engineering change management is activated in Customizing for the class for which you
      want to generate the DataSource, the time dependent fields (DATETO and DATEFROM) are
      brought into the transfer structure for the User transparent.
n   When you create the classification DataSource, please note that you must either only enter
    characteristics in the DataSource that are time-dependent in BW, or, all the characteristics that you
    enter are not time-dependent. Avoid a combination of the two, since it could lead to inconsistencies
    in BW.
    Steps in Extracting Classification Data




                                    7. Create InfoPackages

                                6. Maintain transfer rules

                            5. Maintain communication structures

                          4. Assign InfoSources

                        3. Replicate DataSources in BW

                 2. Maintain DataSources for classification data

              1. Choose basic characteristic, object table, class
              type and characteristics to be extracted




        © SAP AG 1999



n   Here is a summary of the required steps towards extracting classification data.
n   Steps 1 and 2 were described on the previous slides.
n   After maintaining (=generating) the DataSources for the classification data, follow steps 3 to 7,
    which should be familiar to you from the other units in this course.
n   3. Replicating the DataSources that were created in the OLTP System into BW.
n   4. The generated attribute DataSource must be assigned to the InfoSource of the basic characteristic
    (for example, 0MATERIAL) and the generated text DataSources must each be assigned to the
    InfoSources of the classifying characteristics.
n   5. Maintain the communication structures for all the affected InfoSources.
n   6. Maintain the transfer rules for all the affected InfoSources.
n   7. Create an InfoPackage for every relevant InfoSource, and load the classifying attributes for your
    basic characteristic and the texts of the classifying attribute.
Tools for Generic Data Extraction:
Unit Summary



                   You are now able to:

                   l Create DataSources for master data
                   l Create DataSources for transaction data
                   l Use different extraction types to create generic
                     extractors
                   l Understand the class system overview
                   l Create DataSources for classification data and
                     explain their special features.




   © SAP AG 1999
Tools for Generic Data Extraction - Exercises


                Unit:     Tools for Generic Data Extraction
                Topic:          DataSources for master data attributes/texts



                At the conclusion of this exercise, you will be able to:
                • Create DataSources for master data and texts
                •   Load master data and texts from these DataSources into BW



                Your company wants to analyze the purchase requisitions from R/3 in the
                Business Information Warehouse. Since Business Content does not
                include a DataSource for this purpose, you have been given the task of
                generating one for purchasing requisitions using the tools for generic data
                extraction.

                The requested quantities are to be analyzed according to request days,
                plants, material groups, and materials. Similarly, reports are also to be
                supported using the old material number that was transferred from the
                legacy system to the material master in the R/3 System.

                The old material number is to be maintained as a material attribute. In
                order to do so, you have to generate a new InfoSource for the material
                characteristic with the attribute “old material number”.



  1-1   To be able to use the old material number as an attribute of the new material
        number, you have to create a new characteristic ‘material’ with the corresponding
        attribute ‘old material number’. For this purpose, a new view for the attributes and a
        new view for the texts of the characteristic are to be defined and then used for the
        extraction.
        1-1-1 Create a new database view ‘ZMAATT##’ with the short description
              ‘Attributes material number GR##’ in the ABAP Workbench Dictionary on
              your R/3 OLTP System.
        1-1-2 Integrate the ‘client’, ‘material number’, and ‘old material number’ fields
              from the table ‘MARA’ as fields in your view. Finally, activate the view as
              a local object.
        1-1-3 Now create a new database view ‘ZMATXT##’ with the short description
              ‘Texts material number GR##’ in the ABAP Workbench Dictionary for the
              texts of your new characteristic.
      1-1-4 The table ‘MAKT’ is to be used as the data source. The ‘client’, ‘material
            number’, ‘language keys’ and ‘material description’ in this table are
            required as view fields. Finally, activate the view as a local object.
      1-1-5 Once you have defined the database views, they can be used as extractors
            for BW when the new DataSources are created. To do so, go to the BW
            IMG (transaction SBIW) from your R/3 OLTP System and create the new
            DataSource for master data attribute ‘MATNRGR##’.
             Path: Business Information Warehouse è Generic DataSources è
             Maintain generic DataSource (or: directly over TA RS02).
             Note the following with the new DataSource ‘MATNRGR##’: It should be
             located later in the DataSource tab of the BW System, under the application
             component ‘LO-IO’. The extraction source is the view you defined before,
             ZMAATT##.
             Save your new DataSource (for ‘material number and for ‘old material
             number’ if you have the choice when you upload data at a later date) and go
             back to the initial screen.
      1-1-6 Follow the same procedure to create the DataSource for texts.
             R/3 OLTP System, TA RSO2:
             The new DataSource ‘MATNRGR##’ should be located later in the
             DataSource tab of the BW System, under the application component ‘LO-
             IO’. The extraction source is the view you defined before, ZMAATT##.
             Save your new DataSource, select the fields MATNR and SPRAS as
             selection fields and go back to the screen you came from.

1-2   Once you have fulfilled all of the necessary prerequisites in the R/3 OLTP System,
      you have to replicate both the DataSources and the actual master data and texts into
      the BW System.
      1-2-1 In the Administrator Workbench of your BW System, carry out a
            DataSource replication process in the foreground on the source system
            ‘T90CLNT090’.
                   The process replicates the DataSources ‘MATNRGR##‘ and
                   'MATXTGR##‘ for the entire application component LO-IO from
                   the OLTP System. If another course participant has already carried
                   out the DataSource replication, your objects will already be in the
                   BW.

      1-2-2 Now you have to assign an InfoSource to each of the DataSources. That is,
            in this case, create InfoSources based on the DataSources. Give the
            InfoSources the same name as the DataSources. Now create a new
            InfoSource for DataSource MATNRGR#.
             When you create the InfoSource MATNRGR##, the BW System
             automatically recognizes that its InfoObject MATNRGR## has been
             created. When you create the InfoObject MATNRGR##, enter ‘material
             number GR##’ as the description, and select CHAR as the data type and 18
             as the length.
             Enter the characteristic ZOLDMAT (old material number) as the attribute.
             Now activate the new InfoObject MATNRGR##.
       Now assign the InfoSource MATNRGR## to the DataSource MATNRGR#.
       Save your changes. This brings you directly to the transfer rules
       maintenance screen.
1-2-3 Now assign the transfer rules to the InfoSource MATNRGR## and the
      DataSource MATNRGR#. Choose the transfer method PSA.
       Enter the following InfoObjects in the ‘InfoObject assignment field’.
       Assign the InfoObject MATNRGR## to the field MATNR and
       assign the InfoObject ZOLDMAT## to the field BISMT.
       Activate your transfer rules. Ignore any warnings that appear and go back.
1-2-4 Now you have to assign an InfoSource to the text DataSource
      MATXTGR##. In the Administrator Workbench of your BW System, under
      the source system T90CLNT090, call up the context menu on the
      DataSource MATXTGR## in the application component LO-IO InfoObject
      and assign this DataSource to the InfoSource MATNRGR##.
       Now assign the InfoSource MATNRGR## to the DataSource MATXTGR#.
       Save your changes. This brings you directly to the transfer rules
       maintenance screen.
1-2-5 Now assign the transfer rules to the InfoSource MATNRGR## and the
      DataSource MATXTGR#. Choose the transfer method PSA.
       Enter the following InfoObject in the ‘InfoObject assignment field’.
       assign the InfoObject 0TXTSH to the field MAKTX.
       Activate your transfer rules. Ignore any warnings that appear and go back.
1-2-6 To fill the master data tables for your InfoObject MATNRGR##, you have
      to create an InfoPackage with the name GR## Material Master Data. Select
      the DataSource MATNRGR##. Update the data to ‘PSA and then to
      InfoObject’. Start the data request immediately on the ‘Schedule’ tab. Use
      the monitor functions to check whether all of the functions are carried out
      correctly.
1-2-7 Now you have to enter the texts. Create a further InfoPackage with the name
      ‘GR## Material Texts’. Select the DataSource MATXTGR##. Update the
      data to ‘PSA and then to InfoObject’. Start the data request immediately on
      the ‘Schedule’ tab. Use the monitor functions to check whether all of the
      functions are carried out correctly.
1-2-8 Now take a look at the master data for the material ‘BAR-001’ using the
      function for maintaining master data.
              Unit:     Tools for Generic Data Extraction
              Topic:          InfoSources for Transaction Data



              At the conclusion of this exercise, you will be able to:
              • Create a generic DataSource for transaction data
              •   Load this DataSource data into BW




1-3   Now that the master data for our new characteristic exists in the BW System, we
      have to define a DataSource for the purchase requisitions in the R/3 OLTP System.
      1-3-1 To do so, go to the BW IMG (transaction SBIW) from your R/3 OLTP
            System and call up the maintenance screen for generic DataSources again.
            Create the new DataSource for transaction data ‘ZPREQGR##’.
             Path: Business Information Warehouse è Generic DataSources è
             Maintain generic DataSource (or: directly over TA RS02).
      1-3-2 Assign the DataSource to the application component ‘MM’ and enter
            ‘Preq GR##’ as a text description. Choose ‘Extraction from query’ and
            create the DataSource.
      1-3-3 Create a functional area ‘GR##’ with the name ‘Purchase requisitions
            GR##’. Extract the data via the logical database ‘BAM’.
      1-3-4 Create the field group 10 ‘Item data’ and include the following fields from
            the table EBAN in this group.
              EBAN-MATNR               Material number
              EBAN-PLNTS               Plant
              EBAN-MATKL               Material group
              EBAN-QUANT               Purchase requisition quantity
              EBAN-QUNIT               Unit of measure of the purchase req.
              EBAN-REDAT               Request date
             Then generate your field group as a local object, ignore any warnings that
             appear and go back to the initial screen ‘Create DataSource (SAP Query)’.
      1-3-5 Save the extract structure, which you created with it, as a local object.
      1-3-6 This brings you to the screen ‘Select selection fields’ for the DataSource
            ZPREQGR##. Save the DataSource without making any entries. Then quit
            the DataSource maintenance screen.
1-4   You have now created your DataSource for the transaction data on the OLTP side.
      Next, you have to replicate the DataSource in the BW System and upload it to the
      PSA.
      1-4-1 In the Administrator Workbench of your BW System, carry out a
            DataSource replication process on the source system ‘T90CLNT090’ and in
            the application component ‘MM’..
                   If another course participant has already carried out the DataSource
                   replication, your DataSource will already be in BW.




      1-4-2 Now you have to assign an InfoSource to the DataSource ZPERQGR##.
            That is, in this case, create an InfoSource based on the DataSource.
             When you create the InfoSource, give it the description ‘PERQ GR##’.
             Now assign the InfoSource PERQGR## to the DataSource ZPERQGR#.
             Save your changes. This brings you directly to the communication structure
             and transfer rules maintenance screen.
      1-4-3 Now assign the communication structure and transfer rules to the
            InfoSource PERQGR## and the DataSource ZPERQGR#. Choose the
            transfer method PSA. Activate your transfer rules.
             Enter the following InfoObjects in the ‘InfoObject assignment field’.
             Assign the InfoObject 0CALDAY to the field REDAT.
             Assign the InfoObject 0MATL_GROUP to the field MATKL.
             Assign the InfoObject MATNRGR## to the field MATNR;
             Assign the InfoObject 0UNIT to the field QUNIT.
             Assign the InfoObject 0QUANTITY to the field QUANT.
             Assign the InfoObject 0PLANT to the field PLNTS.
             Delete all other entries from this assignment.
             Now maintain the communication structure. Only copy the 6 InfoObjects
             0CALDAY, 0MATL_GROUP, 0PLANT, 0QUANTITY, MATNRGR##
             and 0UNIT into the communication structure.
             Activate your transfer rules. Ignore any warnings that appear and go back.
      1-4-4 To load the transaction data into BW, you have to create an InfoPackage
            with the name ‘GR## Transaction Data’. Select the DataSource
            ZPERQGR##. Update the data to the PSA only. Update it, even if no master
            data exists for the data. Start the data request immediately on the ‘Schedule’
            tab. Use the Monitor functions to check whether all of the functions are
            carried out correctly.
      1-4-5 Go to the PSA and check whether your data has arrived OK.
Optional

                   Unit:       Tools for Generic Data Extraction
                   Topic:          Building an InfoCube



                   At the conclusion of this exercise, you will be able to:
                   • Create an InfoCube for the data of the generic transactio n data
                       DataSource




  1-5      Now that the master and transaction data is in the BW System, create an InfoCube.
           1-5-1 Create an InfoCube ‘PREQGR##’ of the InfoCube type “basis”, with the
                 name ‘GR## Purchase requisitions’ in your InfoArea ‘InfoArea GR##’
                 which you created in Unit 3 in the InfoArea ‘BW220 BW – R/3 OLTP
                 Extraction’. Copy all of the characteristics, time characteristics, and key
                 figures from your InfoSource ‘ZPREQGR##’ as a template. Distribute the
                 characteristics to the following dimensions and activate your InfoCube.
                    Dimension           Characteristic
                    Material            MATNRGR##
                                        0MATL_GROUP
                    Plant               0PLANT
           1-5-2 Now create the update rules for your InfoCube and InfoSource.
           1-5-3 Once you have built your InfoCube and activated the update rules, you can
                 update the data from the PSA to your InfoCube. Go to the PSA and use the
                 Scheduler to update the request. Update the data, even if there is no master
                 data.
Tools for Generic Data Extraction - Solutions


                Unit:     Tools for Generic Data Extraction
                Topic:          DataSources for master data attributes/texts



  1-1   To be able to use the old material number as an attribute of the new material
        number, you have to create a new characteristic ‘material’ with the corresponding
        attribute ‘old material number’. For this purpose, a new view for the attributes and a
        new view for the texts of the characteristic are to be defined and then used for the
        extraction.
        1-1-1 Create a new database view ‘ZMAATT##’ with the short description
              ‘Attributes material number GR##’ in the ABAP Workbench Dictionary on
              your R/3 OLTP System.
               R/3 OLTP System è Tools è ABAP Workbench è Development è
               Dictionary
                Field name                     Enter
                View                           ü
                Object name                     ZMAATT##
               Choose ‘Create’
                Field name                     Enter
                Database view                  ü
               Choose ‘Select’
                Field name                     Enter
                Short text                     Attribute material number GR##


        1-1-2 Integrate the ‘client’, ‘material number’, and ‘old material number’ fields
              from the table ‘MARA’ as fields in your view. Then activate the view as a
              local object.
                Field name                     Enter
                Table                          MARA
               Select the table ‘MARA’
               Toolbar ‘View fields’
               Choose ‘Table fields’
               Select the following fields
                Field name                     Short text
                MANDT                          Client
        MATNR                         Material number
        BISMT                         Old material number
       Choose ‘Copy’


       Activate
       Choose ‘Local object’


       Back
1-1-3 Now create a new database view ‘ZMATXT##’ with the short description
      ‘Texts material number GR##’ in the ABAP Workbench Dictionary for the
      texts of your new characteristic.
       R/3 OLTP System è Tools è ABAP Workbench è Development è
       Dictionary
        Field name                    Enter
        Object name                   ZMATXT##
        View                          ü
       Choose ‘Create’
        Field name                    Enter
        Database view                 ü
       Choose ‘Select’
        Field name                    Enter
        Short text                    Text material number GR##


1-1-4 The table ‘MAKT’ is to be used as the data source. The ‘client’, ‘material
      number’, ‘language keys’ and ‘material description’ in this table are
      required as view fields. Finally, activate the view as a local object.
        Field name                    Enter
        Table                         MAKT
       Select the table ‘MAKT’
       Toolbar ‘View fields’
       Choose ‘Table fields’
       Select the following fields
        Field name                    Short text
        MANDT                         Client
        MATNR                         Material number
        SPRAS                         Language keys
        MAKTX                         Material description
       Choose ‘Copy’


       Activate
       Choose ‘Local object’


       Back


1-1-5 Once you have defined the database views, they can be used as extractors
      for BW when the new DataSources are created. To do so, go to the BW
      IMG (transaction SBIW) from your R/3 OLTP System and create the new
      DataSource for master data attribute ‘MATNRGR##’.
       R/3 OLTP System
       Enter ‘/NSBIW’ in the OK code field and confirm your input with Enter.
       Path: Business Information Warehouse è Generic DataSources è
       Maintain generic DataSource (or: directly over TA RS02).


        Field name                   Enter
        master data attributes       MATNRGR##
       Choose ‘Create’
       Note the following with the new DataSource ‘MATNRGR##’: It should be
       located later in the DataSource tab of the BW System, under the application
       component ‘LO-IO’. The extraction source is the view you defined before,
       ZMAATT##.


        Field name                   Enter
        Application comp.            LO-IO
        View/Table                   ZMAATT##
        Short description            Old MatNr. GR##
        Medium description           Old material no. GR##
        Long description             Old material number GR##
       Save your new DataSource (for ‘material number and for ‘old material
       number’ if you have the choice when you upload data at a later date) and go
       back to the screen you came from.


       Save
       Choose ‘Local object’
       Select the checkbox ‘selection’ for fields MATNR and BISMT
       Save


       Back


1-1-6 Follow the same procedure to create the DataSource for texts.
       R/3 OLTP System, TA RSO2:
        Field name                   Enter
        Texts                        MATXTGR##
       Choose ‘Create’
       The new DataSource ‘MATNRGR##’ should be located later in the
       DataSource tab of the BW System, under the application component ‘LO-
       IO’. The extraction source is the view you defined before, ZMAATT##.
        Field name                   Enter
        Application comp.            LO-IO
        View/Table                   ZMATXT##
        Short description            OMatNr GR## - txt


        Medium description           Old material no. GR## - texts
        Long description             Old material number GR## -
                                     texts
       Save your new DataSource, select the fields MATNR and SPRAS as
       selection fields and go back to the screen you came from.


       Save
       Choose ‘Local object’
       Select the checkbox ‘selection’ for fields MATNR and SPRAS


       Save


       Back
1-2   Once you have fulfilled all of the necessary prerequisites in the R/3 OLTP System,
      you have to replicate both the DataSources and the actual master data and texts into
      the BW System.
      1-2-1 In the Administrator Workbench of your BW System, carry out a
            DataSource replication process in the foreground on the source system
            ‘T90CLNT090’.
                   The process replicates the DataSources ‘MATNRGR##‘ und
                   'MATXTGR##‘ for the entire application component LO-IO from
                   the OLTP System. If another course participant has already carried
                   out the DataSource replication, your objects will already be in the
                   BW.

             BW Server è Administrator Workbench è Monitoring è Source
             Systems. Context menu (right mouse-click) on source system
             T90CLNT090 è DataSource Overview. Context menu on application
             component LO-IO (under SAP-R/3/LO) è Replicate DataSources
      1-2-7 Now you have to assign an InfoSource to each of the DataSources. That is,
            in this case, create InfoSources based on the DataSources. Give the
            InfoSources the same name as the DataSources. Now create a new
            InfoSource for DataSource MATNRGR#.
             BW Server è Administrator Workbench è Monitoring è Source
             Systems. Context menu (right mouse-click) on source system
             T90CLNT090 è DataSource Overview. Context menu on DataSource
             MATNRGR## è Assign InfoSource


              Field name                           Enter
              other                                MATNRGR##


             Create
             When you create the InfoSource MATNRGR##, the BW System
             automatically recognizes that its InfoObject MATNRGR## has been
             created. When you create the InfoObject MATNRGR##, enter ‘material
             number GR##’ as the description, and select CHAR as the data type and 18
             as the length.
              Field name                           Enter
              Long description                     Material number GR##


             Continue
             ‘General’ tab
              Field name                           Enter
              Data type                            CHAR
              Length                               18
      Enter the characteristic ZOLDMAT (old material number) as the attribute.
      ‘Attributes’ tab
       Field name                           Enter
       Attribute                            ZOLDMAT
      Now activate the new InfoObject MATNRGR##.


      Activate


      Back
      Now assign the InfoSource MATNRGR## to the DataSource MATNRGR#.
      Save your changes. This brings you directly to the transfer rules
      maintenance screen.


      Copy
      Choose ‘Yes’
1-2-8 Now assign the transfer rules to the InfoSource MATNRGR## and the
      DataSource MATNRGR#. Choose the transfer method PSA.
      ‘Transfer method‘
       Field name             Enter
       PSA                    ü
      Enter the following InfoObjects in the ‘InfoObject assignment field’.
      Assign the InfoObject MATNRGR## to the field MATNR and
      assign the InfoObject ZOLDMAT## to the field BISMT.
       Field name             Enter
       InfoObject for the     MATNRGR##
       field MATNR
       InfoObject for the     ZOLDMAT
       field BISMT
      Enter
      Activate your transfer rules. Ignore any warnings that appear and go back.


      Activate


      Back
1-2-9 Now you have to assign an InfoSource to the text DataSource
      MATXTGR##. In the Administrator Workbench of your BW System, under
      the source system T90CLNT090, call up the context menu on the
       DataSource MATXTGR## in the application component LO-IO InfoObject
       and assign this DataSource to the InfoSource MATNRGR##.
       BW Server è Administrator Workbench è Monitoring è Source
       Systems. Context menu (right mouse-click) on source system
       T90CLNT090 è DataSource Overview. Context menu on DataSource
       MATXTGR## è Assign InfoSource


        Field name                           Enter
        other                                MATNRGR##
       Now assign the InfoSource MATNRGR## to the DataSource MATXTGR#.
       Save your changes. This brings you directly to the transfer rules
       maintenance screen.


       Copy
       Choose ‘Yes’
1-2-10 Now assign the transfer rules to the InfoSource MATNRGR## and the
       DataSource MATXTGR#. Choose the transfer method PSA.
       Transfer method
        Field name              Enter
        PSA                     ü
       Enter the following InfoObject in the ‘InfoObject assignment field’.
       assign the InfoObject 0TXTSH to the field MAKTX.
        Field name              Enter
        InfoObject for the      0TXTSH
        field MAKTX
       Enter
       Activate your transfer rules. Ignore any warnings that appear and go back.


       Activate


       Back
1-2-11 To fill the master data tables for your InfoObject MATNRGR##, you have
       to create an InfoPackage with the name GR## Material Master Data. Select
       the DataSource MATNRGR##. Update the data to ‘PSA and then to
       InfoObject’. Start the data request immediately on the ‘Schedule’ tab. Use
       the monitor functions to check whether all of the functions are carried out
       correctly.
       BW Server è Administrator Workbench è Modeling è InfoSources
       Expand ‘Application components’ è ‘Logistics - General’ è ‘Master
       data Logistics in general’ è ‘MATNRGR##’ in the hierarchy tree
       Context menu (right mouse button) on R/3 source system ‘T90CLNT090‘
       è Create InfoPackage....
        Field name          Enter
        Description         GR## Material master data
       Select the DataSource MATNRGR##.



       Save

       Choose the ‘Processing’ tab
        Field name                       Enter
        PSA and then in InfoObject       ü
        (by packet)
       ‘Schedule’ tab
       Start loading data immediately


       Start


       Monitor
1-2-7 Now you have to enter the texts. Create a further InfoPackage with the name
      ‘GR## Material Texts’. Select the DataSource MATXTGR##. Update the
      data to ‘PSA and then to InfoObject’. Start the data request immediately on
      the ‘Schedule’ tab. Use the monitor functions to check whether all of the
      functions are carried out correctly.
       BW Server è Administrator Workbench è Modeling è InfoSources
       Expand ‘Application components’ è ‘Logistics - General’ è ‘Master
       data Logistics in general’ è ‘MATNRGR##’ in the hierarchy tree
       Context menu (right mouse button) on R/3 source system ‘T90CLNT090‘
       è Create InfoPackage....
        Field name          Enter
        Description         GR## Material texts
       Select the DataSource MATXTGR##.



       Save
       Choose the ‘Processing’ tab
        Field name                       Enter
        PSA and then in InfoObject       ü
        (by packet)
       ‘Schedule’ tab
       Start loading data immediately


       Start


       Monitor
1-2-8 Now take a look at the master data for the material ‘BAR-001’ using the
      function for maintaining master data.
       BW Server è Administrator Workbench è Modeling è InfoSources
       Expand ‘Application components’ è ‘Logistics - General’ è ‘Master
       data Logistics in general’ in the hierarchy tree
       Context menu for InfoSource ‘MATNRGR0##’ è Maintain master data
        Field name          Enter
        Material            BAR-001


       Execute
              Unit:    Tools for Generic Data Extraction
              Topic:         InfoSources for Transaction Data



1-3   Now that the master data for our new characteristic exists in the BW System, we
      have to define a DataSource for the purchase requisitions in the R/3 OLTP System.
      1-3-1 To do so, go to the BW IMG (transaction SBIW) from your R/3 OLTP
            System and call up the maintenance screen for generic DataSources again.
            Create the new DataSource for transaction data ‘ZPREQGR##’.
            R/3 OLTP System
             Enter ‘/NSBIW’ in the OK code field and confirm your input with Enter.
             Path: Business Information Warehouse è Generic DataSources è
             Maintain generic DataSource (or: directly over TA RS02).


              Field name                   Enter
              Name of InfoSource           ZPREQGR##
             Choose ‘Create’
      1-3-2 Assign the DataSource to the application component ‘MM’ and enter
            ‘Preq GR##’ as a text description. Choose ‘Extraction from query’ and
            create the DataSource.
              Field name                   Enter
              Application comp.            MM
              Short description            Preq GR##
              Medium description           Preq GR##
              Long description             Preq GR##
             Choose ‘Extraction from query’


             Save
      1-3-3 Create a functional area ‘GR##’ with the name ‘Purchase requisitions
            GR##’. Extract the data via the logical database ‘BAM’.


              Field name                   Enter
              Functional area             GR##
             Choose ‘Functional areas’ (functional area maintenance)
             Choose ‘Create’
              Field name                   Enter
        Name                            Purchase requisitions GR##
        Logical data base               BAM


       Continue
1-3-4 Create the field group 10 ‘Item data’ and include the following fields from
      the table EBAN in this group.
        EBAN-MATNR              Material number
        EBAN-PLNTS              Plant
        EBAN-MATKL              Material group
        EBAN-QUANT              Purchase requisition quantity
        EBAN-QUNIT              Unit of measure of the purchase req.
        EBAN-REDAT              Request date
       Then generate your field group as a local object, ignore any warnings that
       appear and go back to the initial screen ‘Create DataSource (SAP Query)’.



       Create
        Field name                      Enter
        FGr                             10
        Meaning                         Item data


       Continue
       Open the Purchase requisition +
       Select the field EBAN-MATNR by dragging it to the field group 10
       Select the field EBAN-PLNTS by dragging it to the field group 10
       Select the field EBAN-MATKL by dragging it to the field group 10
       Select the field EBAN-QUANT by dragging it to the field group 10
       Select the field EBAN-QUNIT by dragging it to the field group 10
       Select the field EBAN-REDAT by dragging it to the field group 10


       Generate


       Ignore warnings by choosing ‘continue’.
       Choose ‘Local object’
             Back



             Back
             Now transfer the function area/InfoSet GR## that you just created, by
             choosing



             Continue
      1-3-5 Save the extract structure, which you created with it, as a local object.
             Choose ‘Local object’



             Continue
      1-3-6 This brings you to the screen ‘Select selection fields’ for the DataSource
            ZPREQGR##. Save the DataSource without making any entries. Then quit
            the DataSource maintenance screen.


             Save


             Back

1-4   You have now created your DataSource for the transaction data on the OLTP side.
      Next, you have to replicate the DataSource in the BW System and upload it to the
      PSA.
      1-4-1 In the Administrator Workbench of your BW System, carry out a
            DataSource replication process on the source system ‘T90CLNT090’ and in
            the application component ‘MM’..
                    If another course participant has already carried out the DataSource
                    replication, your DataSource will already be in BW.




             BW Server è Administrator Workbench è Monitoring è Source
             Systems. Context menu (right mouse-click) on source system
             T90CLNT090 è DataSource Overview. Context menu on application
             component MM è Replicate DataSources è
      1-4-3 Now you have to assign an InfoSource to the DataSource ZPERQGR##.
            That is, in this case, create an InfoSource based on the DataSource.
      BW Server è Administrator Workbench è Monitoring è Source
      Systems. Context menu (right mouse-click) on source system
      T90CLNT090 è DataSource Overview. Context menu on DataSource
      ZPERQGR## è Assign InfoSource
       Field name                           Enter
       other                                PREQGR##


      Create
      When you create the InfoSource, give it the description ‘PERQ GR##’.
       Field name                           Enter
       InfoSource                           PREQGR##
       Long description                     PREQ GR##


      Copy
      Now assign the InfoSource PERQGR## to the DataSource ZPERQGR#.
      Save your changes. This brings you directly to the communication structure
      and transfer rules maintenance screen.


      Copy
      Choose ‘Yes’


1-4-3 Now assign the communication structure and transfer rules to the
      InfoSource PERQGR## and the DataSource ZPERQGR#. Choose the
      transfer method PSA. Activate your transfer rules.
      ‘Transfer method‘
       Field name              Enter
       PSA                     ü
      Enter the follo wing InfoObjects in the ‘InfoObject assignment field’.
      Assign the InfoObject 0CALDAY to the field REDAT.
      Assign the InfoObject 0MATL_GROUP to the field MATKL.
      Assign the InfoObject MATNRGR## to the field MATNR;
      Assign the InfoObject 0UNIT to the field QUNIT.
      Assign the InfoObject 0QUANTITY to the field QUANT.
      Assign the InfoObject 0PLANT to the field PLNTS.
      Delete all other entries from this assignment.
       Field name              Enter
       InfoObject for the      0CALDAY
       field
        REDAT
        InfoObject for the      0MATL_GROUP
        field
        MATKL
        InfoObject for the      MATNRGR##
        field
        MATNR
        InfoObject for the      0UNIT
        field
        QUNIT
        InfoObject for the      0QUANTITY
        field
        QUANTITY
        InfoObject for the      0PLANT
        field
        PLNTS
       Enter
       Now maintain the communication structure. Only copy the 6 InfoObjects
       0CALDAY, 0MATL_GROUP, 0PLANT, 0QUANTITY, MATNRGR##
       and 0UNIT into the communication structure.
       “Expand” the communication structure
       Select the InfoObjects 0CALDAY, 0MATL_GROUP, 0PLANT,
       0QUANTITY, MATNRGR## and 0UNIT in the InfoSource fields and
       copy the selected InfoObjects into the communication structure.
       ‘Close’ the communication structure
       Activate your transfer rules. Ignore any warnings that appear and go back.


       Activate


       Back


1-4-4 To load the transaction data into BW, you have to create an InfoPackage
      with the name ‘GR## Transaction Data’. Select the DataSource
      ZPERQGR##. Update the data to the PSA only. Update it, even if no master
      data exists for the data. Start the data request immediately on the ‘Schedule’
      tab. Use the Monitor functions to check whether all of the functions are
      carried out correctly.
       BW Server è Administrator Workbench è Modeling è InfoSources
       Expand ‘Application component’ è ‘Materials Management’ è ‘PREQ
       GR##’ in the hierarchy tree
       Context menu (right mouse button) on R/3 source system ‘T90CLNT090‘
       è Create InfoPackage....
        Field name          Enter
        Description         GR## Transaction data


       Continue
      Choose the ‘Processing’ tab
        Field name                        Enter
        PSA only                          ü
      ‘Update parameters’ tab
        Field name                                  Enter
        Always update data, even if there is no     ü
        master data for the data
      ‘Schedule’ tab
      Start loading data immediately


      Start


      Monitor


1-4-5 Go to the PSA and check whether your data has arrived OK.
      BW Server è Administrator Workbench è Modeling è PSA
       Expand ‘Application component’ è ‘Materials Management’ è ‘PREQ
       GR##’ è source system in the hierarchy tree
       Context menu (right mouse button) on the request ‘GR## transaction
       data’ è Edit data
       Select data packet 000001


       Continue
Optional

                   Unit:       Tools for Generic Data Extraction
                   Topic:          Building an InfoCube



  1-5      Now that the master and transaction data is in the BW System, create an InfoCube.
           1-5-1 Create an InfoCube ‘PREQGR##’ of the InfoCube type “basis”, with the
                 name ‘GR## Purchase requisitions’ in your InfoArea ‘InfoArea GR##’
                 which you created in Unit 3 in the InfoArea ‘BW220 BW – R/3 OLTP
                 Extraction’. Copy all of the characteristics, time characteristics, and key
                 figures from your InfoSource ‘ZPREQGR##’ as a template. Distribute the
                 characteristics to the following dimensions and activate your InfoCube.
                    Dimension           Characteristic
                    Material            MATNRGR##
                                        0MATL_GROUP
                    Plant               0PLANT
                  BW Server è Administrator Workbench è Modeling è Data targets
                  Expand ‘InfoArea Customer Training’ è ‘BW Customer Training’ è
                  ‘BW220 BW – OLTP Extraction’ in the hierarchy tree
                  Context menu (right mouse button) on InfoArea ‘InfoArea GR##’ è
                  Create InfoCube...
                   Field name                    Enter
                   InfoCube                      PREQGR##
                   Description                   GR## Purchase requisitions
                   InfoCube type                 Basis


                  Enter
                  Copy the characteristics and key figure from the InfoSource


                  InfoSource
                  Place the cursor on InfoSource PREQGR##


                  Enter
                  The InfoObjects from the template are to be copied to the structure.
                  Click ‘Yes’
                  Choose ‘Dimensions...’ in the characteristics tab
       Choose ‘Create’
        Field name                    Enter
        PREQGR##1                     Material
       Choose ‘Create’
        Field name                    Enter
        PREQGR##2                     Plant
       ‘Assign’ tab
       Select ‘0MATL_GROUP‘, ‘MATNRGR##‘ è Cursor on dimension
       ‘Material’ è ‘Assign’ button
       Select ‘0PLANT‘ è Cursor on dimension ‘Plant’ è ‘Assign’ button


       Continue


       Activate
1-5-2 Now create the update rules for your InfoCube and InfoSource.
       BW Server è Administrator Workbench è Modeling è Data targets
       Expand ‘InfoArea Customer Training’ è ‘BW Customer Training’ è
       ‘BW220 BW – OLTP Extraction’ in the hierarchy tree
       Context menu (right mouse button) on InfoCube ‘PERQGR## è
       Purchase requisitions è Create update rules...
         Field name         Enter
         InfoSource         PREQGR##


       Enter
       Next screen


       Activate
1-5-3 Once you have built your InfoCube and activated the update rules, you can
      update the data from the PSA to your InfoCube. Go to the PSA and use the
      Scheduler to update the request. Update the data, even if there is no master
      data.
       BW Server è Administrator Workbench è Modeling è PSA
       Expand ‘Application component’ è ‘Materials Management’ è ‘PREQ
       GR##’ è source system in the hierarchy tree
       Context menu (right mouse button) on the request ‘GR## transaction
       data’ è Schedule update
       ‘Update parameters’ tab
 Field name                                Enter
 Always update data, even if there is no   ü
 master data for the data
‘Schedule’ tab


Start
Start immediately


Monitor
Enhancing Business Content



                      BW Overview -              Tools for Generic
                     SAP R/3 Extraction           Data Extraction

                                                    Enhancing
                     LIS Data Extraction
                                                  Business Content

                                                  Special Topics:
                     LO Data Extraction
                                                 Delta Management

                                               Excursus: OLTP Access
                   Extraction from CO-PA
                                                  via Remote Cubes


                  Data Extraction from FI-SL




  © SAP AG 2001
Enhancing Business Content




      Contents:
       l Enhancing DataSources for transaction data, master
         data and texts
       l Enhancing data with the function enhancements of
         the Service API.
       l Overview of the options in OLTP data enhancement.




  © SAP AG 1999
Enhancing Business Content: Unit Objectives




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

                  l Enhance Business Content DataSources according to
                     the demands of your company,
                  l Implement the data enhancements using the function
                    enhancements of the Service API,

                  l Name the function enhancements of the individual
                    applications.




  © SAP AG 1999
    Enhancing Business Content: Overview Diagram


                                            Extractor Types

                    Application-specific                            Cross-application

          BW Content                     Generic                          Generic
           Extractors                   Extractors                       Extractors

               FI                        LIS                              Database
                     CO                                                   table/view
             HR
                    ...                        FI-SL
                                                                         SAP Query
           LO Cockpit                          CO-PA


           Transparent                 Transparent
                                                                         Data Source
              Table                       Table

                                           Enhancements
                                           Enhancements


        © SAP AG 1999



n   The transaction data entering the Business Information Warehouse by means of extractors originates
    from very different modules. Due to past developments, very different extraction mechanisms are
    necessary.
Enhancing Business Content: Business Scenario




                  l Your company wants to include the old material
                    number as an additional characteristic for certain
                    DataSources from logistics. Some of the standard
                    extractors will have to be modified as a result. You
                    decide to enhance these extractors in Business
                    Content.
                  l Your company also wants the materials assigned
                    to a class of type '001' in the OLTP System to be
                    displayed as such in the material reports carried
                    out in BW. Here too, you decide to enhance
                    Business Content (0MATERIAL).




  © SAP AG 1999
Enhancing InfoSources in Business Content


  l Reasons:
         n   You want to add further attributes to the characteristics (master
             data) shipped with the system.
         n   You want to integrate additional characteristics in the
             DataSources for transaction data that are shipped with the
             system.

  l Prerequisites:
         n   The additional data is available when the extraction function is
             carried out.
         n   All of the keys required to read the additional data are part of the
             original data.




  © SAP AG 1999
    Data Enhancement in the Extraction Path


      Material master
      Time        Material Old material                              Time        Material Old material
                           number              Master data                                number
      01.01.99    M-01     A-01                 extraction           01.01.99    M-01     A-01
      01.06.99    M-01     B-01                                      01.06.99    M-01     B-01

                                                                              Time of
      Sales document
                                                                            master data
      Customer           1000                                                extraction
      Date               01.01.99
                                                Time of
      Material    Quantity    Price
                                              (statistics)
       M-01        10         1000.-
                                                update

      InfoStructure                                                ta
                                                               n da
      Date        Material Quantity    Old mat.no        sactio n
                                                     Tran tractio
                                                         ex
                                                                                    Time of
      01.01.99    M-01       10        A-01
                                                                                transaction data
      ...
                                                                                   extraction
      R/3 OLTP                                                      BW

        © SAP AG 1999



n   Time of statistics update
    Information systems such as the LIS or CO-PA allow you to enhance characteristics that are not
    contained in the documents by means of enhancements or other methods. Such characteristics are
    therefore always generated at the time when a document is posted.
n   Time of transaction data extraction (customer specific)
    When the transaction data is loaded from the OLTP systems to the BW System, fields that cannot be
    supplied with data by the documents are populated by means of a special enhancement. The
    customer determines when the data is enhanced, since it depends on the point at which the data is
    extracted.
n   Time of master data extraction (customer specific)
    Similarly, when master data is extracted, fields that cannot be supplied with data via the extractor are
    enriched by means of an enhancement when the data is loaded into BW. The customer determines
    when the data is enhanced here too, since it depends on the point at which the data is extracted.
n   The time for extracting texts and hierarchies is the same as for transaction and master data extraction.
    Enhanced Transaction Data Extraction


     BW                                                                         InfoObjects
                                                                                Transfer structure


                                                                          4          Load data


                                                                                   Replicate DataSources
                                                                          3

     OLTP                                                                       Transfer structure




                                                                               Extraction structure
                                                               1
                                                                               2               R
                                                      Attach
                                                                        Fill

        © SAP AG 1999



n   If your requirements are not covered completely by the DataSources supplied with Business Content,
    you can obtain additional information in the extraction routine by developing your own program and
    integrating it in a function enhancement.
n   Note the following four steps
      1. Define the required fields in an append structure that is appended to the extract structure of your
         DataSource.
      2. Write your function exit to call up the relevant data sources for your DataSource.
      3. Replicate the DataSource in BW.
      4. Extract the data for your 'enhanced Business Content'.
    Creating and Maintaining Customer Appends



                  In BW IMG                        Maintaining DataSources
                                                               DataSources
                  (TA SBIW)
                                                  Application component          SD


                                                            1



                                                                        Enhance extract structure
        4     Dictionary: Table/Structure: Change Fields
              Dictionary: Table/Structure:
                                                                2
                                                                        DataSource    2LIS_01_S001
      Name                 ZAS001BIWS
      Short description   Append structure for S001BIWS


       Field name         Data element                                          Structure
                                                                         Create Structure
        ZZBISMT           BISMT
                                                                        Structure name ZAS001BIWS
        ...

                                                                    3
        © SAP AG 1999



n   In the IMG for BW (transaction SBIW), choose Business Information Warehouse > Subsequent
    processing of DataSources > Edit DataSource
n   First, you have to generate the customer append for the extract structure of your DataSources. To do
    so, the system proposes a name starting with 'ZA' followed by the name of the extract structure.
n   Then maintain the fields that you want to enhance later. All of these fields should start with 'ZZ'.
n   Finally, generate your append structure.
    Developing Function Enhancements

     Maintaining DataSources

    Application component        SD                                 Function enhancement


                                                                     DataSource    2LIS_01_S001


                                              Project Management of SAP Enhancements
                                               Activate project

                                               Project   ZBW        BW Enhancements
     Enhancements and Components
     Enhancements                              Subobjects               Administrative information
     RSAP0001 Customer Function Calls                                  on the object (e.g. short text,
                                                 Attributes                last changed by, etc.)
              in the Service API                 SAP Enhancements
                                                 Enhancement components
                                                 Documentation

     Project Management of SAP Enhancements
     Components
     EXIT_SAPLRSAP_001 Transaction data supply                     Customer documentation
     EXIT_SAPLRSAP_002 Master data supply                           on the created projects
                                                                                           R



     EXIT_SAPLRSAP_003 Text supply
     EXIT_SAPLRSAP_004 Hierarchy supply
        © SAP AG 1999



n   In the second step, you must define the function enhancement for filling the new fields in the extract
    structure.
n   You have to create a project before you can use an enhancement like this. You can then integrate one
    or more enhancements into this project. For our task, SAP provides the enhancement RSAP0001.
    Remember that an enhancement cannot be used in two projects simultaneously.
n   There are four different enhancement components that can be used for the enhancement RSAP0001.
    Their INCLUDEs contain the code for filling the extract structure.
      - EXIT_SAPLRSAP_001 Transaction data supply
      - EXIT_SAPLRSAP_002 Master data and text supply
      - EXIT_SAPLRSAP_003 Texts supply
                  (Functionality as of BW 2.0B available with EXIT_SAPLRSAP_002!)
      - EXIT_SAPLRSAP_004 Hierarchy supply
n   Every enhancement project has documentation, which also explains the individual parameters of the
    function module.
n   To display documentation on the entire enhancement, choose Utilities > Display entire docu. in the
    Project Management of SAP Enhancements transaction (CMOD).
    Sample Coding

                        Project Management of SAP Enhancements

                        tables:   mara.
                        data:     l_s_s001 like s001biws,
                                  l_counter,
                                  l_tabix like sy-tabix.

                        case i_source.
                          when '2LIS_01_S001'.

                        * Endless loop for debugging *
                        *   l_counter = 7.
                        *   while l_counter = 7.
                        *   endwhile.

                        * Find material in the master data table MARA
                             loop at c_t_data into l_s001biws.
                                l_tabix = sy-tabix.
                                select single * from mara where matnr = l_s001biws-matnr.

                        * Fill fields with data from the master data table MARA
                                  if sy-subrc = 0.
                                      l_s001biws-zzbismt = mara-bismt.
                                      modify c_t_data from l_s001biws index l_tabix.
                                  endif.
                               endloop.
                        endcase.


        © SAP AG 1999



n   Important: always use a CASE statement to interrogate the DataSource, since this function exit is
    called with every DataSource.
    Troubleshooting in Enhancements


     l Extractors are executed as background tasks. This means that
       breakpoints do not have any effect.
     l Prerequisite
            n   Development authorization in the source system
            n   Troubleshooting authorization in the source system
     l Required steps
            n   Add and/or activate an endless loop in the extractor
            n   Log on to the source system
            n   Monitor running tasks (SM50)
            n   Start extraction with the Scheduler in BW
            n   Locate the process in the Monitor and start troubleshooting
     l Restart the Administrator Workbench after coding changes in
       the Customer Exit
        © SAP AG 1999



n   When monitoring the source system, make sure that the extractor is called with the ALE user.
n   As an alternative troubleshooting method, you can use breakpoints to detect errors in the
    enhancement. This procedure is described in greater detail in note 123085.
Important Points


        l Once the function exit is used, it is called up with each
          extraction ('CASE' statement required).
        l Key fields for the enhanced Content must be available.
        l User exit is only intended for append fields.
          Do not change the field contents and do not add data
          records!
        l The maximum field length is 32 characters.
        l Are all of the recommended units of measure included?
        l Further documentation is provided under the transaction
          CMOD.




   © SAP AG 1999
Steps for Data Extraction




                                 8. Schedule InfoPackage

                             7. Create InfoPackage

                         6. Maintain transfer rules

                      5. Maintain communication structure

                   4. Replicate DataSources

             3. Generate DataSource

         2. Edit code for data enhancement

   1. Append new fields to extract structure




   © SAP AG 1999
    How is Master Data Enhanced?



        l Enhancements (Method A)
               n   Enhance the standard extract structure with an append
                   structure.
               n   Fill the new fields with the function exit.

        l Modification (Method B)
               n   Create a new view or an ABAP Query InfoSet.
               n   Overwrite the extractor for BW and the extract structure in
                   the maintenance function for DataSources (master data
                   attributes).



        © SAP AG 1999



n   With method A, you can define your own coding for enhancements with a function enhancement.
n   Method B makes it relatively easy to select new fields without spending too much time on them.
    How is Master Data Enhanced?: Details


           DataSource maintenance                                    Fill extract structure
           Method A
                 Extractor for BW
                   1     2     3      4
                                                     fills
                                                         s
                 Extract structure                                       Extractor <> Structure
                   1     2     3      4     5    6                         1    2    3      4     5   6



                                          New fields                                 Function exit
                                          with append                                EXIT_SAPLRSAP_002

           Method B
                 Extractor for BW (modified)
                   1     2     3      4     5    6
                                                             fills
                 Extract structure (modified)                            View = Structure
                   1     2     3      4     5    6                         1    2    3      4     5   6


                                          New fields
                                          required


        © SAP AG 1999



n   Method A: Enhancing the extract structure with a customer append and filling the fields with a
    function exit. This method can be used with the 'view', 'ABAP Query', and 'Function module '
    extraction types.
    Procedure:
        Do not change the standard view.
        Create an append structure and define your new fields (attributes).
        Fill the appended fields using the function exit EXIT_SAPLRSAP_002. The original fields are
        filled by the extractor.
n   Method B: creating a new view or ABAP Query functional area. Overwrite the extractor for BW and
    the extract structure in the maintenance function for characteristics (RSO2).
    Procedure:
        Create a new functional area or view.
        Enter the functional area or view in the InfoObject maintenance facility as an extractor for the
        BW and an extract structure.
        All of the fields are inserted in the extract structure automatically by the generic extractor.
        This is referred to as a modification. At present, you have to reassign the view to the InfoObject
        after the next upgrade. This will be carried out in future by the version management function.
    Method A: Creating Customer Appends


                        In BW IMG
                        (TA SBIW)           Maintaining DataSources


                                            Application component       LO-IO

                                               1


                                                                    Enhance extract structure
       4     Dictionary: Table/Structure: Change Fields

                                                                      DataSource        0MATERIAL_ATTR
     Name                   ZABIW_MARA_S
     Short description      App. structure for BIW_MARA_S                         2

      Field name             Data element                                 Create Structure
       ZZCLASS             CLASS_D
                                                                         Struct. name   ZABIW_MARA_S
       ...

                                                                    3
        © SAP AG 1999



n   In the IMG for BW (transaction SBIW), choose Business Information Warehouse > Subsequent
    processing of DataSources > Edit DataSource
n   In the first step, enter the application component and choose the corresponding source.
n   Then choose Enhance extract structure and confirm (in most cases) the default name of the customer
    appends beginning with 'ZA'.
n   Then maintain the fields that you want to enhance later. All of these fields should start with 'ZZ'.
n   Finally, generate your append structure.
    Developing Function Enhancements for Attributes



     Choose Action
            Action

      Enhance attributes
      Maintain attributes for customer appends
      Develop function enhancement for attributes

      Select            Project Management of SAP Enhancements
                        Activate project

                        Project   ZBW         BW Enhancements

                        Subobjects
                          Attributes
                          SAP Enhancements
                          Enhancement components          Project Management of SAP Enhancements
                          Documentation                   Enhancements
                                                          EXIT_SAPLRSAP_001 Transaction data supply
                                                          EXIT_SAPLRSAP_002 Master data supply
                                                          EXIT_SAPLRSAP_003 Text supply
                                                          EXIT_SAPLRSAP_004 Hierarchy supply




        © SAP AG 1999



n   In the enhancement RSAP0001 you can use the enhancement component EXIT_SAPLRSAP_002
    for supplying master data (and texts as of 2.0B).
n   Transfer parameters:

    I_CHABASNM:              Name of basic characteristic.
    I_T_FIELDS:              List of transfer structure fields. Only these fields are filled in the data table and
                             can be addressed correctly in the program.
    I_T_DATA:                Table with the data obtained from the application API.
    I_UPDMODE:               Transfer mode, as requested in the Scheduler in the Business Information
                             Warehouse. Usually not required.
    I_T_SELECT:              Table with the selection conditions stored in the BW Scheduler. Usually not
                             required.
Important Points


       l Once the function exit is used, it is called with each
         extraction ('CASE' statement required).
       l Key fields for the enhanced Content must be available.
       l User exit is only specific to the append fields. Do not
         change field contents and do not add data records!
       l Maximum field length is 32 characters.
       l Text and master data may be time-dependent.
       l Texts may be language-specific.




   © SAP AG 1999
Individual Steps in Enhancing Master Data




                                 8. Schedule InfoPackage

                             7. Create InfoPackage

                         6. Maintain transfer rules

                      5. Maintain attributes (communication structure)

                   4. Replicate DataSources

              3. Edit code for data enhancement

          2. Append new fields in append structure

    1. Create append structure for extract structure




   © SAP AG 1999
    Individual Steps in Modifying Master Data




                                       8. Schedule InfoPackage

                                   7. Create InfoPackage

                              6. Maintain transfer rules

                           5. Maintain attributes (communication structure)

                        4. Replicate DataSources

                    3. Enter extractor for BW and extract structure

                2. Maintain DataSource

           1. Create new view or new InfoSet




        © SAP AG 1999



n   Remember that this is a modification. At present, you have to reassign the view to the InfoObject
    after the next upgrade. This will be carried out in future by the version management function.
n   The modification method has the advantage over the enhancement method in that accessing data
    directly via a new view or functional area is naturally faster than enhancing data in an exit.
    Changing Hierarchies



        l The extract structure for hierarchies is fixed.
        l Call the function exit EXIT_SAPLRSAP_004 for changing
          the hierarchy from the Implementation Guide.
        l Change the relevant fields in the internal tables.
        l The complete hierarchy is available in the function exit.




        © SAP AG 1999



n   The function exit EXIT_SAPLRSAP_004 allows you to change the contents of the transfer tables
    created for a hierarchy request. This can be useful for customer-defined hierarchy classes. This
    module, however, should not be used to change the contents of key fields; this should be done in the
    Business Information Warehouse!
n   You can use the following transfer parameters
n   C_T_HIETEXT:         Table with the description of the hierarchy in the requested languages.
    C_T_HIENODE:         Table containing the parts of the hierarchy
    C_T_FOLDERT:         Table containing the descriptions of all nodes that cannot be posted in the
                         hierarchy in the requested languages
    C_T_HIEINTV:         Table containing the hierarchy leaves that represent value intervals
    I_UPDMODE:           Transfer mode, as requested in the BW Scheduler. Is not usually required.
    I_S_HIER_SEL:        Structure containing the requested hierarchy
    I_T_LANGU:           Table with the languages for which the descriptions are requested
    Digression: Data Enhancement in the Application



                                                           SAP BW
                                                                                                       SAP BW
                                                                  analysis program


                                                                                                      R/3 OLTP


      S...                                    S012                     S999                        InfoStructure



                                           S012/SAP                S999/SAP
                                                                                                        Update
                                                                                                        Update
                                           Qty       ...           Number ...
                                                     ...
                                                                                                          rules
                                                                                                          rules
                                           Value                   ø-value ...

                                 USER-EXIT ZXY....
                                LOOP AT XMCEKPO.
                                                                MCEKKO
                                 SELECT SINGLE....                                                 LIS Interface
                                                                                                       Interface
                                 ........                           MCEKPO
                                 MODIFY XMCEKPO.
                                ENDLOOP.

                                                       Order

                                                            EKKO
                                                                                            EKPO    Application
                                                                                     EKKO
    Purchasing                                                  EKPO
         © SAP AG 1999



n   There are also options for enhancing data within the application runs in R/3, to help you update the
    data into BW.
n   This applies in particular to information (characteristics/key figures) that is available at that moment
    or that can be read easily.
n   Example in LIS (here: EKS):
n   You can derive data by using an enhancement for generating characteristics and key figures.
    Ÿ To do this, you have to fill the user-defined characteristics and key figures in the communication
      structure with values, using the relevant application enhancements when the data is updated.
    What does "User Exit" mean?

                        SAP standard                                                User-defined
                        program run                                                 sub-runs
                        PERFORM <subroutine>.
                        :
                        * user-enhancement no. 1
                        CALL CUSTOMER-FUNCTION '001'
                             EXPORTING                                               FUNCTION EXIT_USERDEF_001.
                               <Export Parameter> = <value>                            INCLUDE ZXnnnU02.
                             IMPORTING                                                 (user-defined Include)
                               <Import Parameter> = <value>   Customer Exit No. 1      .
                             TABLES
                               <Table structure>
                                                                                     ENDFUNCTION.
                             EXCEPTIONS
                               <result>.
                          .
                          .                                                          FUNCTION EXIT_USERDEF_002.
    predefined          * user-enhancement no. 2                                       INCLUDE ZXnnnU02.
    marker              CALL CUSTOMER-FUNCTION '002'
                                                                                       (user-defined Include)
                             EXPORTING                        Customer Exit No. 2
    points                   .
                                                                                       .
                             .                                                       ENDFUNCTION.
                             .
                                                                       .              .
                        PERFORM INTERMEDIARY PROCESS.                  .              .
                                                                       .              .
                                                                       .              .
                                                                       .
                                                                                     FUNCTION EXIT_USERDEF_00x.
                        * user-enhancement no. X                                       INCLUDE ZXnnnU0x.
                        CALL CUSTOMER-FUNCTION '00X'                                   (user-defined Include)
                             EXPORTING                        Customer Exit No. X      .
                             .
                             .
                                                                                     ENDFUNCTION.


                        PERFORM FINAL PROCESS.

        © SAP AG 1999



n   Use User exits to branch to predefined points from the SAP standard program run into user-defined
    subprograms. This completes the standard functionality by a few aspects.
n   This gives SAP software the highest possible flexibility.
    The user-defined codes are managed as isolated objects in the customer namespace, so there is no
    worry of complications with the next release or when correction statuses are implemented.
    Enhancements in LIS Update

                  Administrative information on object
                                                               Project Management of SAP Enhancements
            (for example, short text, last changed by, etc.)
                                                               Project   ZLISPROJ   LIS Project

                                                               Subobjects
    Enhancements and Components
                                                                 Attributes
    Enhancements
                                                                 SAP Enhancements
    LEINS001 Statistics update - purchasing docs
                                                                 Enhancement components
             Function exit                                       Documentation
             EXIT_SAPLEINS_001 USER-Exit for
             filling the communication structure
             purchasing information

                                                                                Customer documentation
                 Enhancements in statistics update                               on the created projects
                 Enhancements
                 MCS10001 VIS: Statistics update - Sales documents
                 MCS50001 VIS: Statistics update - deliveries
                 MCS10001 VIS: Statistics update - billing documents
                 V43MLIS Supplying appends to structure SADLSTLIS
                 LEINS001 Statistics update - purchasing documents
                 MCB10001 BCO: Statistics update - material documents
                          and stock
                 MCBR0001 BCO: Statistics update from invoice price
                          and evaluation
                 MCF20001 PPIS: Statistics update - production order

        © SAP AG 1999



n   You have to create a project before you can use an enhancement like this to fill the communication
    structure fields.
n   You can then integrate one or more enhancements into this project. Remember that an enhancement
    cannot be used in two projects simultaneously. LIS has the following enhancements for statistics
    updates.
    ŸMCS10001 VIS:         Statistics update - Sales documents
    ŸMCS50001 VIS:         Statistics update - deliveries
    ŸMCS10001 VIS:         Statistics update - billing documents
    ŸV43MLIS               Supplying appends to structure SADLSTLIS
    ŸLEINS001              Statistics update - purchasing documents
    ŸMCS10001 BCO: Statistics update - material documents and stock
    ŸMCBR0001 BCO: Statistics update from invoice price and evaluation
    ŸMCF20001 PPIS: Statistics update - production order
n   Every enhancement could have more than one enhancement component. These components have the
    code for filling the communication structure, stored in an INCLUDE.
    LIS: Data Enhancement in the MC Structure

      Application program MM purchasing
        EKKO
          ...   LIFNO     ...       ...           ...                                           EKKO
        EKPO
          ...   MATNO    QNTY       ...           ...
                                                                                                                Fills BISMT in the
                                                                                                EKPO
                LIS Interface MM purchasing                                                                      communication
                 MCEKKO                                                                                        structure MCEKPO
                   ...    LIFNO           ...           ...          ...

                 MCEKPO
                   ...    CLASS   MATNO            QTY               ...
                                                                                                            EXIT_LEINS_001
                                                                                                            EXIT_LEINS_001
                                                                                                  TABLES: MARA.
                * User exit for data enhancement:
                  Reading the class for material number                                           LOOP AT XMCEKPO.
                                                                                                   SELECT SINGLE * FROM MARA CLIENT SPECIFIED
                         Update InfoStructure S999                                                    WHERE MANDT = XMCEKPO-MANDT
                                                                                                      AND MATNR = XMCEKPO-MATNR.
                                XMCEKKO                                                            XMCEKPO-BISMT = MARA-BISMT.
                                  ...           LIFNO          ...         ...    ...              MODIFY XMCEKPO.
                                                                                                  ENDLOOP.
                                XMCEKPO
                                  ...           CLASS         MATNO        QTY    ...




                                          Individual InfoStructure S999
                                                Z099
                                                    ...         LIFNO       CLASS MATNO   ...   QTY
                                                                                                                         S999
        © SAP AG 1999



n   The user exits in the area of the LIS interface are called up by the application after the
    communication structures are filled.
    This means you can access the standard filled MC structure for your data enhancements.
n   Keep to the following procedure when enhancing the communication structures for new
    characteristics that need to be filled using an enhancement.
    Ÿ The new characteristic (data element) must be defined in an APPEND structure, which is attached
      to the relevant communication structure.
    Ÿ In a second step, the new communication structure characteristics must be read into a field catalog
      for the application, so that they can be selected in an information structure.
    Ÿ So that the new characteristics can be supplied with values in the communication structure, the
      ABAP code must be in the function enhancement. It must be stressed at this point that this is only
      necessary if you cannot transfer the information with a MOVE-CORRESPONDING from the
      relevant document file.
    Enhancements in Extracting HR Data



           l Time data extractor
                   SAP Enhancement HRPTDW01
           l Hours from personal schedule (0HR_PT_01)
                   EXIT_SAPLHRMS_BIW_PTDW_001
           l Personnel actual times (0HR_PT_02)
                   EXIT_SAPLHRMS_BIW_PTDW_002
           l Allocation transaction data (0HR_PT_03)
                   EXIT_SAPLHRMS_BIW_PTDW_003




        © SAP AG 1999



n   If you want to perform enhancements for the extraction of HR data into BW, you can use the ones
    mentioned above.
n   The procedure is the same for each:
    Ÿ 1. Create an enhancement project (transaction CMOD)
    Ÿ 2. Assign the SAP enhancement HRPTDW01 to the project
    Ÿ 3. Edit the function exit EXIT_SAPLHRMS_BIW_PTDW_001 (-002/-003)
    Ÿ 4. Document the project
    Ÿ 5. Activate the project
n   You can find further information in the documentation on enhancements HRPTDW01 and their
    function exits.
    'Data Supply Program’ in the InfoSet



      l The commentary
        <Query_Head>
        must be added after the data
        declaration

      l The specified DDIC
        structure must be filled
        within a LOOP (or SELECT)

      l The commentary
                                                                          DDIC structure
        <Query_Body>
        must be the last
        commentary before the end
        of the loop




        © SAP AG 1999



n   You can use the coding within an InfoSet for additional data enhancement.
n   It can contain native SQLs, special joins, and special aggregation methods.
n   Procedure:
    Ÿ Use an existing DDIC structure (or create a new one), which contains the required fields.
    Ÿ Write a (small) program in the ABAP Editor (SE38): The coding is generated in the query.
    Ÿ Define an InfoSet that is based on the structure.
Enhancing Business Content: Unit Summary




                  You are now able to:

                  l Enhance Business Content DataSources according to
                    the demands of your company,
                  l Implement the data enhancements using the function
                    enhancements of the Service API,

                  l Name the function enhancements of the individual
                    applications.




  © SAP AG 1999
Enhancing Business Content - Exercises


                Unit:         Enhancing Business Content
                Topic:        Enhancing an InfoSource for Transaction Data



                At the conclusion of this exercise, you will be able to:
                • Enhance a DataSource for transaction data




                Your company wants to transfer the data for the information
                structure S### from the R/3 System to BW. It also wants to keep
                the old material number as a characteristic for reports. This
                characteristic is not available, and not required, in the OLTP
                reports (info structure).



  1-1   In the OLTP System, enhance your InfoSource for transaction data
        ‘2LIS_02_S###’ that you created in the unit on ‘LIS Extraction’. Use the following
        number ranges again for your info structure:

        Group numbers 00 to 24
        Info structure: S850 - S874
        Example:        Group 01 è S### = S851
                               Group 24 è S### = S874
        1-1-24 Go to the IMG for BW in your OLTP System. Create a customer append
               with the description ‘Append Structure for S###BIWS’ and the proposed
               technical name for your InfoSource ‘2LIS_02_S###’. Insert the field
               ‘ZZBISMT’ with the data element ‘BISMT’. Activate your customer
               append as a local object.
        1-1-25 Next, maintain the InfoSource. Assign the InfoObject ‘BISMT220’ to the
               new field.
        1-1-26 Now take a look at the coding for the enhancement component
               ‘EXIT_SAPLRSAP_001’ in the project ZZTEST ‘Enhancements for BW’.
               Why was the code for determining the ‘old material number’ included in a
               CASE statement?


  1-2   Once you have fulfilled all of the prerequisites in the R/3 OLTP System, you have
        to load both the Metadata and the transaction data into BW.
        1-2-1 Carry out a Metadata upload to your source system ‘T90CLNT090’ for your
              existing InfoSource ‘2LIS_02_S###’ only.
1-2-2 Enhance the communication structure to include the InfoObject
      ‘BISMT220’ and activate it.
1-2-3 Then maintain your transfer rules. Copy the InfoObject from the model
      InfoSource to your transfer structure and assign it to the InfoObject of the
      communication structure. Choose the loading method ‘TRFC with ODS’
      and activate your transfer rules.
1-2-4 To load the transaction data to BW, you have to create an InfoPackage with
      the name ‘GR## ODS only’. Update the data into the ‘ODS only’ and
      update it, even if there is no master data. Start the data request immediately
      on the ‘Schedule’ tab. Use the Monitor functions to check whether the
      process ran OK.
1-2-5 In the ODS, check whether the ‘old material number’ has been enhanced by
      the function enhancement in the OLTP system. To do so, find a data record
      that contains the material ‘M-01’.
              Unit:        Enhancing Business Content
              Topic:       Enhancement with the InfoSet/Data Retrieval
                           Program


2-1   In the OLTP System, create a data retrieval program that makes use of the InfoSet
      assignment for data extraction.


      2-1-1 Go to the ABAP Editor (TA SE38) and create the program
            Z_DATA_RETRIEVAL_GR## as a local object (under a template of the
            program Z_DATA_RETRIEVAL_BW220); check and activate the
            program.
      2-1-2 Call up the query maintenance screen (TA SQ02) and create the InfoSet
            ZMATERIAL_DR_GR##, to which the program you created links.
      2-1-3 For the sake of simplicity, delete the predefined field group ‘General
            material data’, create it again and assign the following fields to it:
             Material number MARA-MATNR
             Material type    MARA-MTTYP
             Industry MARA-MAIND
             Material number MARA-MATKL
             Old material number  MARA-BISMT

2-2   You now have to create a DataSource for the InfoSet you just created. Now carry
      out the necessary steps in the BW IMG. Now that you have fulfilled all of the
      prerequisites in the R/3 OLTP System, you have to load both the DataSource and
      the transaction data to BW.
      2-3-1 Call up the BW IMG (TA SBIW) and create a generic DataSource
            (ZMATERIAL_DR_GR##) for transaction data, which refers to the InfoSet
            you just created. Save it as a local object. You should be able to use the
            characteristic ‘material number’ with later data uploads for restricting your
            selection.

2-3   Once you have achieved all the prerequisites in the R/3 OLTP System, you can
      carry out a test to see if the data was loaded correctly.
      2-3-1 Call up the transaction RSA3 and test your DataSource. Restrict the dataset
            that you want to load to materials 300-100 to 300-999.
Enhancing Business Content - Solutions


                Unit:        Enhancing Business Content
                Topic:       Enhancing a DataSource for Transaction Data



  1-1   In the OLTP System, enhance your DataSource for transaction data
        ‘2LIS_02_S###’ that you created in the unit on ‘LIS Extraction’. Use the following
        number ranges again for your info structure:

        Group numbers 00 to 24
        Info structure: S850 - S874
        Example:        Group 01 è S### = S851
                               Group 24 è S### = S874
        1-1-1 Go to the IMG for BW in your OLTP System. Create a customer append
              with the description ‘Append Structure for S###BIWS’ and the proposed
              technical name for your InfoSource ‘2LIS_02_S###’. Insert the field
              ‘ZZBISMT’ with the data element ‘BISMT’. Activate your customer
              append as a local object.
               R3 OLTP System
               Enter ‘/NSBIW’ in the OK code field and confirm your input with Enter.
               Business Information Warehouse è Subsequent processing for
               DataSources è Edit DataSources
                Field name                   Enter
                Application component        MM
               Execute
                Field name                   Enter
                2LIS_02_S###                 ü
               Choose ‘Enhance extract structure’
               Confirm the proposed structure (continue        )
               Entries
                Field name                   Enter
                Short text                   Append Structure for S###BIWS
                Component                    ZZBISMT
                Component type               BISMT
               Activate
               Choose ‘Local object’
               Go back to the ‘Subsequent processing for DataSources’ screen
             Choose ‘Maintain DataSources’.
             Deselect the checkbox ‘Hide field’ for the field BISMT and select
             ‘Selection’
             Save
             Back


      1-1-2 Now take a look at the coding for the enhancement component
            ‘EXIT_SAPLRSAP_001’ in the project ZBW220 ‘Enhancements for BW’.
            Why was the code for determining the ‘old material number’ included in a
            CASE statement?
             Choose ‘Function enhancement’
              Field name                    Enter
              Project                       ZBW220
              Components                    ü
             Choose ‘Change’
             Continue
             Double-click the component ‘EXIT_SAPLRSAP_001’
             Double-click on the include ‘ZXRSAU01’
             Since this function exit is called each time data is extracted, the CASE
             statement specifies the DataSources for which a data enhancement is to
             be carried out and how this is carried out for the individual DataSources.

1-2   Now that you have fulfilled all of the prerequisites in the R/3 OLTP System, you
      have to load both the DataSource and the transaction data to BW.
      2-3-1 In the Administrator Workbench of your BW System, carry out a
            DataSource replication process in the foreground on the source system
            ‘T90CLNT090’.
             BW è Administrator Workbench è Monitoring è Source Systems.
             Context menu (right mouse-click) on source system T90CLNT090 è
             DataSource Overview. Context menu on DataSource 2LIS_02_S###
             (under application component SAP R/3/MM) è Replicate DataSources
      1-2-2 Enhance the communication structure to include the InfoObject
            ‘BISMT220’ and activate it.
             Context menu (right mouse button) on DataSource ‘2LIS_02_S###‘ è
             Change transfer rules...
             Expand ‘communication structure’è Attach InfoObject ‘BISMT220‘
             Activate
      1-2-3 Then maintain your transfer structure and transfer rules. Assign the
            InfoObject BISMT220 to the field BISMT and copy it to the transfer rules.
            Activate your transfer rules.
       Context menu (right mouse button) on DataSource ‘2LIS_02_S###‘ è
       Change transfer rules...
       Select the InfoObject BISMT and copy it to the transfer structure.
       ‘Transfer rules’ tabè Assign InfoObject BISMT220 to the field BISMT
       è ‘Propose transfer rules’
       Activate


1-2-4 To load the transaction data to BW, you have to create an InfoPackage with
      the name ‘GR## PSA only’. Update the data to the ‘PSA only’. Update the
      data even if it has no master data. Start the data request immediately on the
      ‘Schedule’ tab. Use the Monitor functions to check whether the process ran
      OK.
       InfoSources è Application components è MMè InfoSource
       2LIS_02_S### è Context menu (right mouse-click) on R/3 source system
       T90CLNT090 è Create InfoPackage...

         Field name                   Enter
         InfoPackage name             GR## - PSA only
       Enter
       Choose the ‘Data target’ tab
         Field name                        Enter
         PSA only                          ü
       ‘Update parameters’ tab
         Field name                                     Enter
         Always update data, even if there is no        ü
         master data for the data
       ‘Schedule’ tab
       Start
       Monitor
       Execute
       Refresh if necessary
1-2-5 In the PSA, check whether the ‘old material number’ has been enhanced by
      the function enhancement in the OLTP system. To do so, find a data record
      that contains the material ‘M-01’.
       BW Server è Administrator Workbench è PSA tab
       Expand ‘Application components’ è ‘Sales and distribution’ è
       InfoSource ‘2LIS_02_S###’ è Source system in hierarchy tree
       Context menu (right mouse button) on the request ‘GR## PSA only’ è
       Display/change request data
       Select data packet 000001
       Continue
Find
 Field name           Enter
 Find by              M-01
Find
Double-click the first hit.
              Unit:          Enhancing Business Content
              Topic:         Enhancement with the InfoSet/Data Retrieval
                             Program


2-1   In the OLTP System, create a data retrieval program that makes use of the InfoSet
      assignment for data extraction.


      2-1-1 Go to the ABAP Editor (TA SE38) and create the program
            Z_DATA_RETRIEVAL_GR## as a local object (under a template of the
            program Z_DATA_RETRIEVAL_BW220); check and activate the
            program.
             R3 OLTP System
             Tools è ABAP Workbench è Development
              Field name                    Enter
              Program                       Z_DATA_RETRIEVAL_BW22
                                            0
             Copy
              Field name                    Enter
              Target program                Z_DATA_RETRIEVAL_GR##
             Copy
             Copy
             Choose ‘Local object’
             Check
             Activate
             Enter


      2-1-4 Call up the query maintenance screen (TA SQ02) and create the InfoSet
            ZMATERIAL_DR_GR##, to which the program you created links.
             Info systems è Ad-hoc Reports è SAP Query è Environment è
             InfoSets
             Make sure that you create the InfoSet in the global area (cross-client:
             Environment è Work areas è Double-click on global area (cross-client)
              Field name                    Enter
              InfoSet                       ZMATERIAL_DR_GR##
             Create
              Field name                     Enter
              Name                           InfoSet GR## (Data retrieval
                                             program)
              Data retrieval using           Z_DATA_RETRIEVAL_GR##
              program
              Data structure                 MARA
             Continue
      2-1-5 For the sake of simplicity, delete the predefined field group ‘General
            material data’, create it again and assign the following fields to it:
             Material number         MARA-MATNR
             Material type           MARA-MTTYP
             Industry                MARA-MAIND
             Material number         MARA-MATKL
             Old material number     MARA-BISMT
             Select the field group ’01 – General material data’
             Delete      Field group
             Create
              Field name                     Enter
              FGr                            01
              Meaning                        General material data
             Continue
             Select the fields above by using the <Ctrl> key
             Select the field group 01
             Add fields to the field group
             Check
             Generate

2-2   You now have to create a DataSource for the InfoSet you just created. Now carry
      out the necessary steps in the BW IMG. Now that you have fulfilled all of the
      prerequisites in the R/3 OLTP System, you have to load both the DataSource and
      the transaction data to BW.
      2-3-1 Call up the BW IMG (TA SBIW) and create a generic DataSource
            (ZMATERIAL_DR_GR##) for transaction data, which refers to the InfoSet
            you just created. Save it as a local object. You should be able to use the
            characteristic ‘material number’ with later data uploads for restricting your
            selection.
             R3 OLTP System
             Transaction SBIW è Generic DataSources è Maintain generic
             DataSources
              Field name                   Enter
              Transaction Data             ZMATERIAL_DR_GR##
             Create
              Field name                   Enter
              Application comp.            MM
              Short description            GR##: InfoSet/DVP
              Medium description           Grp. ##: InfoSet/DVProgram
              Long description             Group ## InfoSet/Data retrieval
                                           program
             Choose ‘Extraction from query’

              Field name                   Enter
              InfoSet                      ZMATERIAL_DR_GR##
             Save
             Select the checkbox ‘selection’ for the field MATNR
             Save
             Back

2-3   Once you have achieved all the prerequisites in the R/3 OLTP System, you can
      carry out a test to see if the data was loaded correctly.
      2-3-1 Call up the transaction RSA3 and test your DataSource. Restrict the dataset
            that you want to load to materials 300-100 to 300-999.
             R3 OLTP System
             Transaction RSA3
              Field name                   Enter
              DataSource                   ZMATERIAL_DR_GR##
              Request number               TEST
              Data records / call up       100
              Number of extractor calls    10
              Update mode                  F
              Number of extract calls      10


              Field name                   Enter
              Field                        MATNR
              From value                   300-100
              To value                     300-999
             Start extraction
Confirm the popup with continue
Display list
Choose ‘Detail’
Special Topics: Delta Management



                      BW Overview -              Tools for Generic
                     SAP R/3 Extraction           Data Extraction

                                                    Enhancing
                     LIS Data Extraction
                                                  Business Content

                                                  Special Topics:
                     LO Data Extraction
                                                 Delta Management

                                               Excursus: OLTP Access
                   Extraction from CO-PA
                                                  via Remote Cubes


                  Data Extraction from FI-SL




  © SAP AG 2001
Special Topics: Delta Management



      Contents:

      l Concept, technology, and implementation of delta
        management in SAP BW
      l Delta management for applications




  © SAP AG 1999
Special Topics: Delta Management: Unit Objectives




                   At the conclusion of this unit, you will be able
                   to:
                   l explain the concept of and the technology
                       behind delta management for data extraction
                       out of R/3 OLTP
                   l explain the different approaches to delta
                       management for the applications




   © SAP AG 1999
    Special Topics: Delta Management: Overview
    Diagram

                                                                              Business Explorer
      Web Browser        Web Design Tool                      Business Explorer Browser
                                                              Business Explorer Browser

                                                         BEx Analyzer
                                                         BEx Analyzer                  External
                                                                                        External
                                    Display views
          SAP Internet                                  (with MS Excel)
                                                        (with MS                      OLAP Client
                                                                                      OLAP Client
          Transaction
          Server
                                 Save HTML
                                 templates
                                                                                           ODBO

     Administrator                                                                       BW Server
                               BDS         BW WEB Service
                                              WEB Service           OLAP Processor
     Workbench                 Business
                               Document
                               Service
          Manage
          Manage
                                           Metadata Manager         Data Manager           InfoCubes
                                           Metadata Manager         Data Manager
         Schedule
         Schedule            Metadata
                             Metadata
                            Repository                                                    Operational
                                                         Staging Engine
                                                         Staging Engine
          Monitor                                                                         Data Store
                                                             BAPI
                                                             BAPI




                                Extractor for non-SAP
                                Extractor for non-SAP                Extractor for
                                                                      Extractor for         OLTP
                                                                                            OLTP
                                  Production Data
                                   Production                       Production Data
                                                                    Production Data       Reporting
                                                                                          Reporting

                            Non-SAP OLTP Applications
                            Non-SAP OLTP Applications                     R/3 OLTP Applications
                                                                          R/3 OLTP Applications


        © SAP AG 1999



n   As components of the Business Framework, OLTP applications and the Business Information
    Warehouse communicate via BAPIs (Business Application Programming Interfaces).
n   The extraction mechanisms that are used to prepare the production data in each application for the
    Business Information Warehouse are located in an R/3 OLTP System.
n   With non-SAP applications, the prerequisites for exchanging data between the application and the
    Business Information Warehouse can be met by separate installations from external suppliers.
    Delta Management: Data Flow


                                      Attributes Hierarchies
                                      Attributes Hierarchies
        BW System
                                            Texts
                                            Texts


                         Request
                                                                       Data                ODS




                  SAPI                    D-Management
                         Request

                                                                                         Data
                                           Data                 Data
                ARFCSDATA
                                                                 D-Extractor
                                                                 D-Extractor           Batch Job
                                                                                       Batch Job

                                                    Updater
        R/3 OLTP                                                         OLTP Process
                                                                         OLTP Process


        © SAP AG 1999




n   SAPI delta management describes the functions that are offered as a generic service in SAP BW
    warehouse management, to ensure that changes to relevant datasets for an extracor are replicated
    consistently in a BW.
n   There are three different scenarios for delta extraction, and each uses a different method to transfer
    the delta information into BW. The three scenarios are:

      - Scenario 1: Delta with full update ('Snapshot scenario')
      - Scenario 2: Delta-log in OLTP
      - Scenario 3: Delta-log in BW ('delta-ODS')

n   The data that you want to extract is made available by the OLTP in the following ways:
      - using the update
      - using jobs scheduled at regular intervals
      - using a delta extractor
    Data Extraction from R/3 OLTP



                                                                     Transfer Structure
                                                                     Transfer Structure
                        Request IDoc
                        Request IDoc

                                             Asynchronous
                                                                                   via
                                             Data Transfer                       ALE/IDoc
                                                                                    or
                                                                                tRFC/ODS
                  Request ID
                  DataSource
                  Selection
                                                                     Transfer Structure
                                                                     Transfer Structure
                  Update Mode


                          Start Extraction
                          Start Extraction       Extractor
                                                                     Extract Structure
                                                                     Extract Structure

                                                  Transaction Data
                                                  Master Data
                                                  Texts
                                                  Hierarchies
                                                  Change Logs




        © SAP AG 1999



n   The BW delta queues (and the data records they contain) are determined using transaction RSA7.
n   The recommended size for data packets is between 20-50 MB, with a maximum of 100 MB.
    DM: Update Modes



           l Full Update
           l Delta Update
                  n     Initialization run
                  n     Delta transfer
                  n     Repeat (repeat the last delta)
           l     Transferring an opening balance




        © SAP AG 1999



n   Central delta management supports various update methods:
    Ÿ Full update (independent, freely chosen selection)
    Ÿ Delta update - with the methods belonging to it
        • initialization run (to determine the selection conditions)
        • Delta transfer (at regular intervals)
        • Repeat (repeats the last delta, if errors occur) and
    Ÿ Transfer of an opening balance (for stock values).
    Full Update Mode




       R/3 OLTP                                           BW




                            ‘00/N                                        Selection 1:
                                                                         Sales Area: North
                            ‘00/S


                            ‘99/N


                            ‘99/S                                        Selection 2:
                                                                         Periods 01-12 1999
                    Source Table(s)
                    Source Table(s)




        © SAP AG 1999




n   With a full update, the extractor delivers all the data for the selection you have defined; you can
    change this selection independently of the loading processes that have taken place so far.

n   You can carry out a full update, independently of other loading processes, for the same DataSource.
n   Application:
    Ÿ if a delta method is not supported
    Ÿ as a 'pseudo-delta' with a 'snapshot scenario' (delta using selection)
Delta Update Mode


                                         Initialization 1:
                                         Sales Area: North
   R/3 OLTP                         BW   Periods 01-12 2000

                                         Delta 1:
                                         Sales Area: North
                                         Periods 01-12 2000
                       ‘00/N
                                         Initialization 2:
                       ‘00/S             Sales Area: South
                                         Periods 01-12 2000
                       ‘99/N
                                         Delta 2:
                                         Sales Area North +
                       ‘99/S
                                         South
                                         Periods 01-12 2000
                  Source Table(s)
                  Source Table(s)




  © SAP AG 1999
    D-Scenario 1: Delta with Full Update ('Snapshot Scenario')




       R/3 OLTP                                           BW




      Update
                            ‘00                          Full Update:
      only > '98
                                                         Selection ‘1999 - 2000’          deletion and loading at
                            ‘99                                                           regular intervals


                                                          Full update: Selection '1998'
      Closed period         ‘98                                                           one-off loading

                                                         Full update: Selection '1997'    one-off loading
      Closed period
                            ‘97


                        Source Table(s)
                        Source Table(s)




        © SAP AG 1999




n   With a 'snapshot scenario', the extractor supports only the full update method.
n   The whole amount of data that can have been changed is always loaded as a 'delta', for example, all
    the data for a period that is still open for update.
n   With transaction data, the data that has been loaded so far for this period has to be deleted, otherwise
    the update will be carried out repeatedly. This is not necessary with master data, because master data
    is generally overwritten, rather than aggregated.
    For this scenario, the last data request can be deleted in BW automatically. Scheduling this loading
    process at regular intervals is also supported. The selection can be made dynamic by using variables
    in the InfoPackage (for example, you could make you selections always with the current date using
    the change date in a master data table).
    D-Scenario 2: Delta Log in OLTP




                                                                                       BW
      R/3 OLTP


                 Old/new data

                                                                                    Old: Reverse posting
                                                                                    Key figures can be
       Preparing the delta:
                                                                                    converted into SAPI
       • using online update                                                        if necessary
       or
       • triggered by a BW request                      ARFCSDATA
       or
       • at regular intervals, independently
       of BW                                   • Generic data store for qRFC
                                               • Administration of several target
                                               systems
                                               • Serialization




            © SAP AG 1999




n   The extractor supports the delta update method.
n   With transaction data, the extractor is also able to deliver the old data status (before-image)
    whenever necessary.
    Ÿ There are three ways of preparing the delta records for transfer:
      • using a connection to the update with every relevant change

      • the delta is prepared at regular intervals, independently of the BW request

      • the delta is triggered by the BW request

n   To support these three methods, a delta queue is managed for each DataSource that operates
    according to this scenario. The table ARFCSDATA serves as a generic storage place (generally
    stores temporarily the data for all tRFC calls). The new 'queuing tRFC' technology (qRFC) makes it
    relatively easy to supply several target systems with deltas.
n   The delta queues are supported only from OLTP Release > = 4.0B!
    D-Scenario 3: Delta Log in OLTP                         ('Delta ODS')




                                             BW
           R/3 OLTP


            Only new or changed
            data status                                        Old/new data    Transfer Rules



                                           New                Old (reversal)




                                                 Old data
                                                 status




        © SAP AG 1999



n   The 'delta ODS scenario' is interesting only for transaction data.
n   The extractor supports the delta update method. The extractor is, however, only able to deliver the
    new status for the changed data records. The last data to be loaded are stored in BW. When loading
    the data, the records that have already been loaded ('pre-images') are included automatically as
    reverse postings in the update.
n   The scenario presupposes the following:
    Ÿ Delta ODS with unique ID for single records
      -> Obligatory fields in the transfer structure, secondary indexes for delta ODS
    Ÿ Reading on demand of the last data status, passed on as a reverse posting
    Ÿ Cannot be posted in the InfoCube bypassing the delta ODS
    Ÿ No changes to delta ODS
n   Advantages:
      - Can be used with 'non-R/3'
      - Implementation as a BW tool / less strain on extractors
      - Makes delta with generic extraction possible
n   Disadvantages:
      - Deletion possible only with 'dummy' changes
      - Changes restricted to the transfer structure
      - Volume of data in BW / performance of the loading process
SAPI-DM: Capabilities



     l Managing a delta queue per DataSource with delta
       option
     l Managing several target systems
     l Possible to supply the delta queue independently of the
       BW request
     l Supports the 'Repeat mode'
     l Defined commit point after initialization phase
     l Most recently loaded data stored in BW, and merged
       automatically ('delta ODS')




   © SAP AG 1999
SAPI-DM: Availability and Prerequisites



    l Availability for the following applications
           n   LO Extraction
           n   Profitability analysis (CO-PA)
           n   FI/CO line items
           n   Accounts receivable and accounts payable accounting (FI-
               AP/AR)


    l OLTP prerequisites
           n   4.0B/SP40, 4.5B/SP22, 4.6B/SP07, 4.6C/SP01
           n   OSS No. 194909




   © SAP AG 1999
    LIS: Delta Management


        OLTP                                                                                    BW

                                                          Complete update

                                     Snnn
                 LIS
                 Update
                                                                                    InfoSource
                                                                                    '2LIS_01_Snnn'

                                                             Delta update


                                                             Change before every
        Generate update             SnnnBIW1                 transfer
        Activate update

                                                             Delta update

                                     SnnnBIW2


        © SAP AG 1999



n   The tables SnnnnBIW1 and SnnnBIW2 are used for delta management in the LIS.
n   The info. structure in the OLTP is active; the data is loaded from SnnnBIW1 into BW for the first
    delta update.
n   While the first delta update to the BW is being carried out, the LIS update process updates the LIS
    info structure in the OLTP system as well as the table S5nnBIW2, which is then used for the second
    delta update request to the BW.
n   At the start of each delta update request, the system switches automatically between the S5nnBIW1
    table and the S5nnBIW2 table to prevent data inconsistencies arising when the data is being
    uploaded to BW.
n   The data in a delta table remains in the table until the next delta upload, to ensure that the data can be
    reloaded up to that point.
n   When you start the second delta update process from the OLTP System to the BW, the table
    S5nnBIW2 is used.
n   This means that the table S5nnBIW1 is used for the general LIS update, while the contents of the
    table S5nnBIW2 are loaded to the corresponding InfoCube in BW.
n   The contents of the 'S5nnBIW1' table are initialized before the second delta update to BW is started.
n   The tables in the OLTP are automatically switched for the delta update to BW. This ensures that one
    table is used for the delta upload in BW, while the other table is used for the general LIS update
    process.
n   The table that is currently active for the delta update is shown in the table 'TMCBIW' (field Status).
    CO-PA: Delta Management


           InfoPackages                                                                      I2 + D4
                                              I                   D                         + D5 + D6


    BW

           Requests       I1         D1     D2        D3          I2       D4        D5        D6
                                                                                                 Time
                            30 min

              I1
    for line items               D1
                                          D2
    R/3                                            D3
                                                             R
                                     I2
    for line items                                                       D4
                                                                                  D5
                                                                                            D6
        © SAP AG 1999



n   To guarantee the consistency of the data, only those line items in the OLTP that are at least 30
    minutes old (t - 30 min.) are created for initialization requests and delta requests.
n   This 30 minute time period is known as a "safety delta", and is depicted as yellow bars in the above
    diagram.
n   Since transfers usually take place with a frequency of once a day, the safety delta does not affect the
    up-to-dateness of the data in the SAP BW.
    "Delta" in Account-based CO-PA (among others)

                                  "Initialization "                       "Delta"
     InfoPackages                                                                        F1 + F2
                                                           F                            + F4 + F6


    BW

         Requests           F1                        F2       F3     F4        F5      F6

                                                                                                Time
                            F1                        F2       F3               F5
                                                                 F4               F6
                                           always from summarization
    R/3                                    level

                          Period                 Period        Period               Period
                          1.2000                 2.2000        3.2000               4.2000


        © SAP AG 1999



n   Only full uploads are supoorted in account-based CO PA, which means that a pseudo-delta has to be
    carried out in a snapshot scenario.
n   The same goes for FI SL and FI AP /AR.
    Delta Management using SAPI Delta Queue


         R/3 OLTP                                                                         BW

         After-image of the changed data                  After-image of the changed data

         Describe delta queue with
         FB RSC1_TRFC_QUEUE_WRITE
         Input Parameters:
            • DataSource name                                    • generic data storage (qRFC,
            • Extract structure               ARFCSDATA            queuing RFC)
                                                                 • administration of several target
                                                                   systems
                                                                 • serialization




        © SAP AG 1999



n   You can set up a delta upload process using the SAPI delta functions in the applications FI AP/AR in
    particular.
Delta Management using ODS

                   Key       Status          Dunning level Amount
          ...            1            open               1        100    ...   OLTP
   Old


                                                  Incremental load

  New 1            Key       Status          Dunning level Amount
          ...            1            open               2        100    ...
                                                                               PSA
  New 2
                   Key     Status      Dunning level Amount                    Delta queue
          ...            1     cleared             2        100          ...




                                                  Transfer/Update

                   Key       Status      Dunning level Amount
          ...            1       cleared             2        100        ...   ODS (modified)
                   Key       Status        Dunning level Amount
          ...            1            open             1        100      ...   ODS (active)

                                                  Create delta
                   Key       Status          Dunning level Amount
          ...            1            open               1        -100   ...

                   Key     Status      Dunning level Amount
                                                                               ODS
          ...            1     cleared             2        100          ...


   © SAP AG 1999
Delta and ODS: Special Features



      l Extractor is delta-capable
              n   Extraction logic has a delta process
              n   DataSource is or is not delta-capable


      l Data target is delta-capable
              n   Data target is able to process delta information from an
                  update (semantically correct).
              n   Data target itself is able to pass on data as a delta.




  © SAP AG 1999
Delta Classification DataSource



       l Every source system that has DataSources for use in
         the extraction process, classifies the delta process it
         uses.
       l Delta process
              n    Additive delta
              n    Before image / after image
              n    After image
              n    Nonspecific delta
              n    ODS or InfoCube delta (request-orientated)




   © SAP AG 1999
ODS and Delta Process



     l When delta information is updated in an ODS object, the
       delta process that is used plays a considerable role.
            n     Additive delta
                  Delta in key figures is added to the data target, and not overwritten.
            n     Before image and/or after image
                  Delta in key figures is overwritten, and not added to the data target.
            n     Nonspecific delta
                  Cannot be updated in an ODS.




  © SAP AG 1999
Serialization of the Delta Process




                                                            1             2
          D-Management                                      2   Staging   4
  -------------------------------------------------------
                                                                Engine        ODS
         Delta Extraktion                                   3             1
                                                            4             3


                                     Data Packets                Parallel
                                                                Processes



   © SAP AG 1999
Delta: Before/After Image




                   2
         Staging   4
         Engine                   ODS
                   1
                   3



                   2               1
         Staging   4               2
         Engine    1        PSA         ODS
                                   3
                   3               4




   © SAP AG 1999
Special Topics: Delta Management: Unit Summary




                  You are now able to:

                  l explain the concept of and the technology
                    behind delta management for extracting data
                    out of R/3 OLTP
                  l and the different approaches of delta
                    management for the applications




  © SAP AG 1999
Excursus: OLTP Access via Remote Cubes



                      BW Overview -              Tools for Generic
                     SAP R/3 Extraction           Data Extraction

                                                    Enhancing
                     LIS Data Extraction
                                                  Business Content

                                                  Special Topics:
                     LO Data Extraction
                                                 Delta Management

                                               Excursus: OLTP Access
                   Extraction from CO-PA
                                                  via Remote Cubes


                  Data Extraction from FI-SL




  © SAP AG 2001
Excursus: OLTP Access via RemoteCubes



      Contents:
       l Technology and implementation of data access using
         RemoteCubes




  © SAP AG 1999
    SAP AG
Excursus: OLTP Acess via RemoteCubes:
Objectives



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

                  l Explain the technology behind OLTP direct
                    access using RemoteCubes, and assess how this
                    technology is used




  © SAP AG 1999
    SAP AG
Excursus: OLTP Acess via RemoteCubes:
Business Scenario


                  l Management wants to have access to certain
                    relevant information. How relevant a query is must
                    be displayed every time the query is accessed. You
                    have to be able to access queries at any time.




  © SAP AG 1999
    SAP AG
RemoteCubes - Definition



   l A RemoteCube is an InfoCube with transaction data that is
       managed externally, and not in the Business Information
       Warehouse.

   l Only the structure of the RemoteCube is defined in BW.

   l The data for reporting is read from another system using a
       BAPI.




  © SAP AG 1999
RemoteCubes - Description



  l Using Reporting Tools in OLTP Systems
        n   standardized and modern user interface
        n   cross-application reporting

  l real-time access to transaction data from operative systems
        n   direct access rather than redundant data storage

  l Using existing BW infrastructure
        n   Extractors
        n   Service API
        n   BW Metadata model
        n   Transfer rules


  © SAP AG 1999
    Architecture



                                                                         Transaction Data
                                                                          Transaction Data
                              Transfer    Master Data
                                          Master Data
      ODS
                 Stagine
                 Stagine       Transfer
                               Rules                        BasicCube            RemoteCube
                                Rules                        BasicCube
                 Engine
                  Engine
                                                                                               Non-R/3
                                            Master                Fact         SAP
                                                                                SAP            Source
                                                                            RemoteCube
     BW                                      Data                Table
                                                                 Table       RemoteCube        System




                                            Transfer Structure                                 e.g. Nielsen DB


                                                                           RemoteCube IF
     OLTP                                       Service API
                                                Service API
                                                                            RemoteCube IF

                                                                                            Extract Structure

                                          MD-Extractor
                                          MD-Extractor             TD-Extractor
                                                                    TD-Extractor

                                          Master Data              Transaction
                                                                   Transaction
                                             (MD)                   Data (TD)


        © SAP AG 1999




n   When you are reporting using a RemoteCube, the Data Manager calls the RemoteCube BAPI,
    instead of a BasisCube filled with data, and transfers the parameters.
    Ÿ Selection
    Ÿ Characteristics
    Ÿ Key figures
n   The external system then transfers the requested data to the OLAP processor.
    RemoteCubes - Uses



         l Real-time Reporting
                n   Direct access means that up-to-date transaction data is available
         l Prototyping
                n   In prototyping, cubes and queries can be created and supplied
                    with data very quickly
                n   Reduced administration costs
                n   Less memory space
         l (Performance advantages)
                n   Compared with frequent data uploads
                n   Particularly with BW/BW connections




        © SAP AG 1999



n   With the help of a RemoteCube, you can carry out reporting using data from external systems,
    without having to physically load the transaction data into BW. You can use a RemoteCube to
    include, for example, external sytems from market data.
n   This reduces the amount of administration required in BW, and saves memory space.
n   As a rule, SAP RemoteCubes do not improve performance in the source system. This is the price you
    have to pay for up-to-date data.
    Losses in performance are relative, however, if the source system is a BW, and you are able to use
    aggregates in the data source. On the plus side, data is not stored redundantly in BW. The overall
    performance (source system + targte system) is better, if a very large amount of data (for example,
    line items) is accessed sporadically and selectively.
    Creating RemoteCube Queries



         l Prerequisites
                n   DataSource supports RemoteCubes
                        (RSOLTPSOURCE-VIRTCUBE = ‘1’ or ‘2’)

                n   active transfer rules for the InfoSource

         l Step 1: Creating the RemoteCube
                n   SAP or general RemoteCube (*)

                n   system-dependent or system-independent

         l Step 2: Creating queries




        © SAP AG 1999



n   Create RemoteCubes in the 'Data targets' menu:
    Ÿ Context menu for InfoArea (Create InfoCube...)
    Ÿ Create the InfoCube as a SAP RemoteCube or a General RemoteCube
    Ÿ Activate the InfoCube
n   For a general RemoteCube, the BAPI BAPI_INFOCUBE_READ_REMOTE_DATA has to be
    implemented in the source system, meaning that it has to be coded. With SAP RemoteCubes this is
    not necessary.
Transfer Rules


  BW                                                                          OLTP
                                                       Inverse Transfer Rules

                                                                              Field      S          Opt         Low        High
                                 InfoObject   S      Opt     Low      High
                                                                              YEAR       I          EQ      2000
   Selections                    0FISCPER     I      BT 1.2000 5.2000
                                                                              PERIOD     I          BT      1          5
                                                                                                         SELECT
  Query
  Account   May2000   2000 YTD
                                                                                         OLTP Table

  100000     100.00     800.00                                                                           FETCH
  110000     600.00    1,900.00 0ACCOUNT          0FISCPER     0AMOUNT        Account        Year        Period       Amount

                                    100000        2.2000            700.00      100000       2000          2           700.00
                                    100000        5.2000            100.00      100000       2000          5           100.00
            Data                                                                110000       2000          3          1,300.00
                                    110000        3.2000           1,300.00
                                    110000        5.2000            600.00      110000       2000          5           600.00



                                                              Transfer Rules


  © SAP AG 1999
RemoteCubes - Restrictions



   l Only for Transaction Data
          n   no application for master data, texts and hierarchies

   l Only for small volumes of data

          n   because of reduced performance

   l Can be used by only a small number of end users

   l DataSource has to be released for direct access

   l No function enhancements (in SAPI)

   l Available as from R/3 Release 4.0B




  © SAP AG 1999
    SAP RemoteCube Query: Processing Steps


          (source sytem-independent and [source system-independent])




                                 5. Define a query
                                7. Generate update of the LIS info structure
                           4. [Link source system ID with RemoteCube]

                        3. [Maintain Transfer Rules]

                    2. [Create source system ID]

               1. Create SAP RemoteCube




        © SAP AG 1999



n   The (points in parentheses) have to be carried out only for source system-dependent RemoteCubes.
    Supported DataSources



        l All generic DataSources (view, query)                  ?
        l Extractor CATS                                         0CATS
        l Profit-center: Transaction data                        0EC_PCA_1
        l Profit-center: Statistical key figures                 0EC_PCA_2
        l Vendors: Single records                                0FI_AP_3
        l Customers: Single records                              0FI_AR_3
        l General ledger: Transaction data                       0FI_GL_1
        l General ledger: Transaction data - COS-Ledger          0FI_GL_2
        l Special ledger: All DataSources                        3*


        (Status: OLTP 4.0B, BW 2.0B)


        © SAP AG 1999



n   Technical classification: ROOSOURCE-VIRTCUBE = ‘1‘ or ‘2‘.
Excursus: OLTP Acess via RemoteCubes: Unit
Summary



                  You are now able to:
                  l Explain the technology behind OLTP direct
                     access using RemoteCubes, and assess how this
                     technology is used




  © SAP AG 1999
Section: Currency Translation




                   Currency Translation




   © SAP AG 2001
Currency Translation




                  Currency Translation




  © SAP AG 2001
Currency Translation: Contents



  l     Overview Currency Translation in BW
  l     Maintenance and usage of translation keys
  l     Overview Currency Settings in the BW IMG
  l     Special and related topics




  © SAP AG 2001
Currency Translation: Objectives



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

                   l Create translation keys
                   l Translate currencies in the BEx Analyzer
                   l Translate currencies in the Update Rules
                   l Upload currency settings from a R/3 source
                     system
                   l Maintain currency settings in the BW IMG




   © SAP AG 2001
Currency Translation in BW - Overview




   l In BW, currencies can basically be translated at two
     different times:
          n   When updating data into the InfoCubes or ODS Objects (with
              2.0B)
          n   When analyzing data in the BEx Analyzer




  © SAP AG 2001
    Currency Translation in BW - Overview


     Business
     Explorer
                                                          Currency translation



                    InfoCube


                                           Update Rules
                                           Update Rules   Currency translation

                                     ODS


                                           Update Rules
                                           Update         Currency translation
                                       Transfer Rules
                                       Transfer Rules


                                     PSA



                        DataSource
                        DataSource
        © SAP AG 2001



n   Currencies can be translated…
    Ÿ in the Update Rules
    Ÿ in the Business Explorer Analyzer
Currency Translation: Business Scenario



                  l In your cube, you store all values in the document
                    currency. You want to translate all values to a
                    group currency in your queries. To do this, you use
                    a specific translation key.
                  l You want to compare values with current exchange
                    rates and historical exchange rates. This way you
                    want to analyze the influence of exchange rate
                    changes




  © SAP AG 2001
Currency Translation: Further Possible Scenarios




    l You want to compare actual exchange rates with those
      valid at the posting date. This way you want to analyze the
      influence of exchange rate changes between the posting
      date and today
    l You get values in different currencies from your source
      systems. In the InfoCube you want to store all values in the
      document currency and in your group currency (p.eg. EUR)
    l In your InfoCube you store all values in one currency.
      Subsidiaries want to translate these values ad hoc in BEx
      to their local currency using the exchange rate of the
      current day



   © SAP AG 2001
Currency Translations in BW - Translations Keys


   l The translation key is a combination of different parameters
     that establish how the exchange rate for the translation is
     executed.
   l The parameters that determine the exchange rate are the
     source and the target currency, the exchange rate type and
     the time reference for the translation.

                            Target currency   Exchange rate type
                                                                                     Translation
                                                                                     key
          Source currency                                          Time reference



   Value in                                                                Value in
                                      Exchange rate
   source currency                                                         target currency




   © SAP AG 2001
Currency Translations in BW - Translations Keys



    l The source currency is determined from the data record or
      dynamically from the master data of the specified
      InfoObject (currency attribute)




                                 Target currency   Exchange rate type


               Source currency                                          Time reference



   © SAP AG 2001
Currency Translations in BW - Translations Keys



    l The target currency can either be fixed in the translation
      key or selected at the time of translation.
    l You can also use an InfoObject (currency attribute) to
      determine the target currency.




                                 Target currency   Exchange rate type


               Source currency                                          Time reference


   © SAP AG 2001
Currency Translations in BW - Currency Attributes




                                            n   A currency attribute is
                                                defined in the
                                                InfoObject
                                                maintenance

    l The currency attribute has to be a unit InfoObject of type
      currency
    l The unit InfoObject must be an attribute of the
      characteristic
    l The currency attribute should be filled in the master data
      table of the corresponding InfoObject (manual
      maintenance or upload via InfoSource)
   © SAP AG 2001
    Currency Translations in BW - Currency Attributes




          l Only InfoObjects with a currency attribute can be used in
            translation keys (p.eg. 0COMP_CODE)
          l At the time of currency translation the value for the source
            currency / target currency is then derived for every record
            from the master data table of the specified InfoObject




        © SAP AG 2001



n   Example:
n   You load the following record to your InfoCube:
n   Company Code:        1000
n   Amount in Source Currency: 500,-
n   Source Currency:     FRF
n   Target Currency:     ?
n   In the Update rules, you are now using a translation key which derives the target currency from the
    InfoObject 0COMP_CODE. During the Update Process the target currency will then be read for
    Company Code 1000 from the master date table of 0COMP_CODE.
Currency Translations in BW - Translations Keys


    l The exchange rate type distinguishes exchange rates that
      are valid in the same time frame next to each other, for
      example, the bid rate, ask rate or middle rate. The exchange
      rate types are stored and can be maintained in a central
      table (TCURV).




                                 Target currency   Exchange rate type


               Source currency                                          Time reference


   © SAP AG 2001
Currency Translations in BW - Translations Keys



    l The time reference for the currency translation can be
      either fixed or variable.




                                Target currency   Exchange rate type


              Source currency                                          Time reference



   © SAP AG 2001
Currency Translations in BW - Translations Keys



   l The fixed time reference can either be a fixed key date that
     is stored in the translation type, or be determined using the
     system date when executing the currency translation.
   l If the time reference is variable, then the point in time for
     the exchange rate determination comes from the value of a
     time characteristic (InfoObject). The reference can, for
     example, be the end or the start of a fiscal year or a
     calendar year, a period and a month – or even to the exact
     day. It can also be determined using a customer-specific
     InfoObject (for example, trading day).

                                 Target currency   Exchange rate type


               Source currency                                          Time reference



   © SAP AG 2001
Currency Translations in the BEx



 l In the BEx Analyzer, there are two possibilities for
   handling different currencies :
       n   Definition of a currency translation per key figure
           in the query definition




   © SAP AG 2001
Currency Translation in the BEx



 l In the BEx Analyzer, there are two possibilities for
   handling different currencies :
       n   Ad hoc currency translation in the Workbook
           (after having executed the query)




   © SAP AG 2001
Currency Translation in the BEx




    l The ad hoc currency translation offers only restricted
      functionality (selection of translation key and target
      currency) compared to the currency translation in the
      query definition
    l Do not forget to create your translation keys before
      starting your work in the Business Explorer Analyzer !




   © SAP AG 2001
    Currency Translation in the BEx : Query Definition


      l Enter the currency translation
        key in the properties of the
        key figure
      l The translation keys can be
        different for the key figures /
        restricted key figures in the
        query (no currency translation
        on calculated key figures
        possible)




        © SAP AG 2001



n   In a formula different key figures in different currencies could be mixed. That is why a currency
    translation on formulas is not allowed. In such a case you should first create restricted key figures
    which you translate to a common target currency and then using them in a formula.
    Currency Translation in the BEx : Query Definition




          l When selecting a translation key with a fixed target currency
            this currency will be added automatically to the query
            definition
          l Also, you can use translation keys selecting their target
            currency at the time of translation. These can be applied in
            two different ways:
                n   selection of a specific target currency in the query definition (1)
                n   define an entry by variable (2)




        © SAP AG 2001




n   The variable has not to be created. It will be added automatically to the query when executing it.
    Currency Translation in the BEx: Query Definition




                                            (1)



                                               (2)                    (2)




        © SAP AG 2001




n   The variable has not to be created. It will pop up automatically when executing the query. This
    feature is only available after BW 2.0B, Frontend Patch 6
    Currency Translation in the BEx: Query Definition



      l In the query definition you can use translation keys
        where the target currency will be derived from the
        currency attribute of an InfoObject:
            l this InfoObject is read automatically (in background)
              from the InfoCube / ODS Object
            l for each value (p.eg. Company Code = 1000) the
              target currency will be read from the corresponding
              master data table
            l Please note: the InfoObject has to be part of the
              Cube or the ODS Object and has to be filled !




        © SAP AG 2001



n   Please remember that the currency attribute has to be filled in the master data table, too.
Currency Translation in the BEx: Query Definition



 l In the query definition you can use translation keys
   getting their time reference from an InfoObject:
       l this InfoObject is read automatically (in background)
         from the InfoCube / ODS Object
       l Please note: the InfoObject has to be part of the
         Cube / the ODS Object and has to be filled !




   © SAP AG 2001
Currency Translation in the BEx: Ad hoc




l All values for a query are
  translated ad hoc (after
  having executed the query)
  using a translation key


l Depending on the
  translation key a fixed
  target currency will be
  used for translation or you
  will be able to select the
  target currency




   © SAP AG 2001
Currency Translation in the BEx: DB currency




   l After having executed the query you can always
     return to the database currency (disactivation of the
     current currency translation)
   l The database currency is the original currency in
     which the value of the key figure is saved in the
     database (InfoCube / ODS Object)


   © SAP AG 2001
    Currency Translation in the Bex: Restrictions




          l With the currency translation in the Business Explorer, the
            source currency can currently only be determined from the
            data record.
          l Only translation keys with a fixed exchange rate type can
            be used in the BEx
          l Translation keys with a dynamic time reference (from an
            InfoObject) can only be used in the query definition. It is
            not possible to fill the InfoObject by a variable !
          l Translation keys getting their target currency from a
            currency attribute can only be selected in the query
            definition


        © SAP AG 2001



n   When getting the dynamic reference from an InfoObject (p.eg. 0CALDAY) the currency translation
    will apply to each record read from the database. That means it will use the date in this record for the
    currency translation.
n   When using a variable you will restrict the output of your query to a certain amount of data. For
    example, you would translate all invoices of March 11 with the translation date March 11
n   This means, the requirement “show me all invoices in my cube in group currency, conversion date:
    14.07.2001” could not be solved by a varaible input for 0CALDAY
n   This information is valid for BW 2.0B, Patch 11
Currency Translation in the Update Rules



  l   Currency translation in the update process can happen in two
      ways:
             •     using translation keys previously defined




             •     using user-defined subprograms (routines)




   © SAP AG 2001
Currency Translation in the Update Rules




    l When using translation keys in the Update Rules, there are
      certain things to keep in mind:
           n   You need key figures with currency objects that are different
               in the cube definition and the communication structure
           n   You need to enter the translation key
           n   You can only select translation keys which contain
               InfoObjects of the communication structure:
                   w   Example: a translation key uses as variable time reference
                       InfoObject 0PSTNG_DATE (Posting date)
                   w   If 0PSTNG_DATE is not part of the communication
                       structure this translation key can not be selected in the
                       Update Rules


   © SAP AG 2001
    Currency Translation in the Update Rules




                                                     (1)

                            (2)
                                                            (3)

                                         (1)
                                                                    (3)



       l After having entered the translation key the system
         displays...
             l the Source currency object (1)
             l the Target currency object (2)
             l the Source unit from conversion (3)


        © SAP AG 2001



n   The Source currency object is the InfoObject belonging to the key figure of the communication
    structure. Even if the source currency ( = value of the source currency ) is derived from a currency
    attribute this referenced currency object ( = metadata) stays the same.
n   The Target currency object is the InfoObject belonging to the key figure of the data target (InfoCube,
    ODS Object).
n   The Source Unit from conversion can be either a fixed value (USD, GBP, …) or the name of the
    currency object which will contain the currency (USD, GBP,…) after the currency conversion.
Currency Translation in the Update Rules




   l When using translation keys selecting the target currency at
     the time of translation:
         n   The target currency object has to be part of the communication
             structure and has to contain a value there
   l When using translation keys selecting the source currency
     from the data record:
         n   The source currency object has to be part of the communication
             structure and has to contain a value there




   © SAP AG 2001
    Currency Translation in the Update Rules




        l When using translation keys with a fixed target currency...
              n   the target currency object has not to be part of the
                  communication structure
              n   the system will always translate to the target currency defined in
                  the translation key, even if the target currency object is included
                  in the communication structure and contains a value there




        © SAP AG 2001



n   Problems when working with translation keys using a fixed target currency are solved with BW 2.0B
    Patch 8. Please refer to note 337081
Currency Translation in the Update Rules




  l When using translation keys getting their source or target
    currency from an InfoObject...
         n   the InfoObject (p.eg. 0COMP_CODE) has to be part of the
             communication structure
         n   the currency attribute has to be filled in the master data table of
             the InfoObject




   © SAP AG 2001
Currency Translation in the Update Rules




  l When using translation keys getting their time reference
    from an InfoObject
         n   this InfoObject (p.eg. CALDAY) has to be part of the
             communication structure
         n   the InfoObject has to contain a value in the communication
             structure




   © SAP AG 2001
Currency Translation in the Update Rules -
Routines




    l You have to use routines when you are facing the following
      situations:
           n   You are using different key figures in the communication
               structure and in the cube, but they have the same currency
               object assigned.
           n   You are using the same key figure in the communication
               structure and in the cube.
    l In a routine you need therefore to determine:
           n   the amount ( target currency )
           n   the target currency




   © SAP AG 2001
Currency Translation in the Update Rules -
Routines




    l In these cases, you select „Unit calculation in the routine“
      in your update method.
    l This will give you an additional field in the interface of your
      routine. The value of this field determines the target
      currency.




   © SAP AG 2001
    Currency Translation in the Update Rules -
    Routines

                        PROGRAM UPDATE_ROUTINE

                         DATA:    s_amount type f,
                                   t_amount type f.

                        MOVE COMM_STRUCTURE-/BIC/CCVALTC to s_amount.

                        CALL FUNCTION 'RSW_CURRENCY_TRANSLATION'
                         EXPORTING
                          I_CTTNM   = 'ZRHTEST01'
                          I_AMOUNT = s_amount
                          I_SCUR    = COMM_STRUCTURE-CURKEY_TC
                          I_TCUR    = COMM_STRUCTURE-CURKEY_LC
                         IMPORTING
                          E_AMOUNT = t_amount
                          E_TCUR    = UNIT
                             .

                        MOVE t_amount to RESULT.

                        * if the returncode is not equal zero, the result will not be updated
                         RETURNCODE = 0.
                        * if abort is not equal zero, the update process will be canceled
                          ABORT = 0.




        © SAP AG 2001



n   Function module RSW_CURRENCY_TRANSLATION uses the following parameters
    Ÿ Import parameters
      - I_CTTNM                     Currency translation key (optional)
      - I_AMOUNT                    Amount in source currency (not optional !!)
      - I_SCUR                      Source currency (optional)
      - I_TCUR                      Target currency (optional)
      - I_TIME_IOBJVL               InfoObject for determination of the time reference (optional)
      - I_SCUR_IOBJVL               InfoObject for determination of the the source currency
                                    (p.eg. 0COMP_CODE) (optional)
      - I_TCUR_IOBJVL               InfoObject for determination of the the target currency
                                    (p.eg. 0COMP_CODE) (optional)
      - I_PERIV                     Fiscal year variant (optional)
      - I_RATE                      Exchange rate (optional)
    Ÿ Export parameters
      - E_AMOUNT                    Amount in target currency
      - E_RATE                      Exchange rate
      - E_SCUR                      Source currency
      - E_TCUR                      Target currency
    Upload Exchange Rates from a Flat File


        l You can transfer exchange rates from a flat file by selecting
          „transfer exchange rates“ in the pop-up menu of the desired
          flat file source system.
        l Exchange rates can be uploaded from the application server
          or the client workstation
        l The flat file should be of type *.csv (maintenance of field
          separator)




        © SAP AG 2001



n   For further details please refer to SAPNet note 355990. The note contains details about the structure
    of flat files for the upload of exchange rates.
Upload Exchange Rate / Exrate Type from R/3



   l You can transfer exchange rates from an R/3 system by
     selecting „transfer exchange rates“ in the pop-up menu of
     the desired source system.
   l Then you can select exchange rates of a certain exrate type
     and validity.
   l The transfer can be simulated.




  © SAP AG 2001
Upload Exchange Rate / Exrate Type from R/3



   l You can transfer exrate types from an R/3 system by
     selecting „transfer global settings“ in the pop-up menu of
     the desired source system.
   l Then you select „currencies“ as the content to be
     processed.
   l The transfer can be simulated.




  © SAP AG 2001
    Upload Exchange Rate / Exrate Type from R/3



         l The following tables are affected:
             Table      Content                                 Transferred with
             TCURR Exchange Rates                               Exchange rates
             TCURC Currency Codes                               Exrate types
             TCURF Conversion Factors                           Exrate types
             TCURS Rate Spreads                                 Exrate types
             TCURT Currency Code Names                          Exrate types
             TCURV Exchange rate types for currency translation Exrate types
             TCURW Exchange rate type usage                     Exrate types
             TCURZ Exchange rate type usage                     Exrate types
             TCURN Standard quotation for exchange rates        Exrate types




        © SAP AG 2001



n   Upload of Table TCURN is only supported after having applied BW 2.0B Patch 10 and (a source
    system dependent) R/3 Basis Support Package. Please refer to note 355305.
Currency Settings in the SAP BW IMG



  l Acces via Tools – Business Engineer – BW Customizing (SPRO)




                                           Display /
                                           Maintenance of
                                           Currency settings
                                           (TCUR* tables)




  © SAP AG 2001
Currency Settings in the SAP BW IMG




 l Exchange rates can be
   displayed / modified /
   entered in the BW
   Customizing (Maintenance
   of table TCURR)




  © SAP AG 2001
    Currency Settings in the SAP BW IMG




        l    Indirect quotation: Currency value expressed in units of the local
             currency per unit of the foreign currency (cf. direct quotation).
             Indirect quotation is also known as volume notation.
        l    Direct quotation: Currency value expressed in units of the local
             currency per unit of foreign currency (cf. indirect quotation). Direct
             quotation is also known as price notion.




        © SAP AG 2001



n   Example Indirect Quotation
n   Local currency: EUR
n   Foreign currency: USD
n   For one unit of the local currency EUR you will receive the displayed number of units of the foreign
    currency, i.e. 1.0808 USD.


n   Example Direct Quotation
n   Local currency: EUR
n   Foreign currency: USD
n   One unit of foreign currency USD costs the displayed number of units of local currency, i.e. 0.92524
    EUR
    Currency Settings in the SAP BW IMG




     l For each currency pair you
       can define either the
       indirect quotation or the
       direct quotation as the
       standard quotation for the
       exchange rate




        © SAP AG 2001



n   For further information please check the documentation in the System.
    Currency Settings in the SAP BW IMG




         l Alternative exchange
           rate types are used to
           process currency
           translations for
           certain currency pair
           combinations from a
           given date using a
           different exchange
           rate type.



        © SAP AG 2001



n   By using alternative exchange rate types you can reduce the number of exchange rates to be
    maintained !
n   Example
n   As of 01.01.1999 (when European Monetary Union begins) a given exchange rate type can be used
    as an alternative exchange rate type for EMU currencies for which exchange rates are fixed.
    Alternative exchange rates enable you to deal with currencies of the EMU member states in a special
    way.
    Inversion of Currency Translations



          l This flag in the translation key enables you to invert /
            annulate in the BEx an initial currency translation in the
            Update Rules
          l The usage of such translation keys is very restricted due to
            the following reasons:
                n   Currency translations with a dynamic time reference can not
                    be inverted (only fix date currency translations can be
                    inverted)
                n   Restricted use when working with multiple / dynamic source
                    or target currencies




        © SAP AG 2001



n   Example for a restriction:
n   Data is uploaded to BW in different transactions currencies and is translated in the Update Rules to
    one single group currency. How to invert the data in the BEx to the initial transaction currency ? This
    would be only possible when the Data could be inverted using currency attributes (p.eg. from
    0COMP_CODE for local subsidiaries)
    Inverted Exchange Rate



          l This setting in table TCURV is not the inversion of an
            exchange rate !
          l It is an Indicator that in the case of a missing exchange rate
            entry in the system for the required translation from one
            currency into another, the inverted exchange rate
            relationship may also be used.




        © SAP AG 2001



n   Example
n   If an entry is missing for the translation of USD into DEM in the system, then the translation takes
    place by means of the entry for the tranlsation of DEM into USD, providing the indicator is set.
    EURO Conversion in BW


      l Data in the BW can be converted to EURO on database level
      l ABAP RSEURO in BW-
        System
      l    Two-Step Procedure:
            l Selection of Key figures
              and InfoCubes
            l Execution of the Euro-
              Conversion in a
              background process




        © SAP AG 2001



n   With the EURO solution for BW you can decide yourself which key figures are to be converted to
    Euro. You can call the program RSEURO and the corresponding documentation via Transaction
    SE38.
n   More detailed information can be found in a presentation in SAPNet, under alias BW → Service &
    Support → Know How Network → EURO Solution for SAP BW-
n   Please refer to SAPNet Note 327741 and check SAPNet regularly for notes about report RSEURO.
    Overview Currency Translation




                                               BEx      BEx              Update       Update
                                               Workbook Query            Rules        Rules
                                               ad hoc   Definition       Standard     Routines
       Source currency      from data record   X            X            X            X
                            from IO            N/A          N/A          X            X
       Target currency      fixed              X            X            X            X
                            from IO            N/A          X            X            X
                            selection          X            X            X            X
       Exchange rate        fixed type         X            X            X            X
                            from IO            N/A          N/A          N/A          X
       Time reference       fixed              X            X            X            X
                            dynamic            N/A          X            X            X




        © SAP AG 2001



n   This slide gives an overview of available translation key features ( = X) in the BEx Analyzer and in
    the Update Rules (BW 2.0B, SP 14). Future developments can affect this table.
Currency Translation: Unit Summary




                  You are now able to:
                  l Create translation keys
                  l Translate currencies in the BEx Analyzer
                  l Translate currencies in the Update Rules
                  l Upload currency settings from a R/3 source
                    system
                  l Maintain currency settings in the BW IMG




  © SAP AG 2001
Exercises 1


                Unit: Currency translation in BW
                Topic: Translation keys



                At the conclusion of this exercise, you will be able to:
                • Create your own translation keys


  1-1   Create your first translation key:
        1-1-1 In the Easy Access Menu, select the SAP standard menu
              BW administration – translation keys – Create.
        1-1-2 The name for your first translation key should be CT_1_GRXX (XX is your
              group number). Enter a meaning for this translation key, e.g. “Currency
              translation 1, Group XX” (XX is your group number).
        1-1-3 In the first tab, Exchange rate, select “Dynamic exrate determination with
              exrate type”. Enter the exrate type M (Standard translation at average rate).
        1-1-4 In the second tab, Source Currency, select “Source currency from data
              record”.
        1-1-5 In tab Target Currency, select “Fixed target currency”.
              Enter USD (American Dollar) as the target currency.
        1-1-6 In the tab Time reference, select “Fixed time reference” and “Current date”
              as the reference.
        1-1-7 Save your translation key.

  1-2   Create another translation key:
        1-2-1 The name for your second translation key should be CT_2_GRXX
              (XX is your group number). Enter a meaning for this translation key, e.g.
              “Currency translation 2, Group XX” (XX is your group number).
        1-2-2 Use this data for the translation key:
              Exchange rate       dynamic, M
              Source currency from data record
              Target currency fixed, EUR (Euro)
              Time reference fixed, specific date, 01.01.1999
        1-2-3 Save this translation key, too.
Exercises 2


                Unit: Business Scenarios
                Topic: Maintaining a group currency

                At the conclusion of this exercise, you will be able to:
                • Use a translation key to translate all document currencies to a group
                  currency in your reporting.
                • Change this group currency very easily.

  1-1   Create a new query first:
        1-1-1 Start the BEx Analyzer and create a new query for the cube 0SD_C01
              (Customer). The cube can be found under InfoArea Logistics - Sales and
              Distribution.
        1-1-2 Set a filter for your query: Use characteristic “Sales Organization” and
              restrict it to the values “Retail GER” and “Retail USA”.
        1-1-3 Add the characteristic “Sold-to-party” to the rows. Add “Material” as a free
              characteristic
        1-1-4 Add the key figure “Sales Volume” to the columns.
        1-1-5 Save and execute the query. The name for your query should be
              CT_Q1_GRXX (XX is your group number). Enter a meaning for this query,
              e.g. “Currency translation 1, Group XX” (XX is your group number).
        1-1-6 You will see mixed currencies in your report.

  1-2   Maintain a group currency for your reporting:
        1-2-1 Change your query.
        1-2-2 In the properties of your key figure, select your translation key
              “CT_1_GRXX” (XX is your group number) for automatic currency
              translation. The fixed target currency should be USD (American Dollar).
              Otherwise, please change your translation key.
        1-2-3 Save and execute the query again. This time you will see that all currencies
              will be translated to your group currency: American Dollar.

  1-3   Change the group currency to Euro.
        1-3-1 Change your translation key “CT_1_GRXX” (XX is your group number). To
              do that, you have to enter the Admin Workbench again. Set the fixed target
              currency to “EUR” (Euro).
        1-3-2 Save your translation key.
      1-3-3 After that, change the definition of your query. Take a look at the properties
            of your query to check if the target currency changed there, too. You must
            take this step, as otherwise the system will not realize that the target
            currency of your key figure changed.
      1-3-4 Save and execute the query again. Your group currency will now be Euro.

1-4   Switch back to database currency.
      1-4-1 You can still switch back to the currencies that were saved in yo ur cube.
            To do that, simply select “Currency Translation” from the pop- up menu in
            your query and then select “to DB currency”.
      1-4-2 To see your group currency again, select “as defined in query” in the menu
            just mentioned.
Exercises 3


                Unit: Business Scenarios
                Topic: Comparing actual and historical exchange rates

                At the conclusion of this exercise, you will be able to:
                • Use different translation keys with different reference dates in your
                  queries.
                • Make use of this information.

  1-1   Copy your old query:
        1-1-1 Change your old query. Save it as a new query named CT_Q2_GRXX
              (XX is your group number).
        1-1-2 Rename the key figure in the columns to “Sales Volume actual”.

  1-2   Calculate the exrate variance:
        1-2-1 Add the key figure “Sales Volume” to the columns a second time.
              Rename this key figure to “Sales Volume hist.”. In the properties of this
              second key figure, select your other translation key, CT_2_GR GRXX
              (XX is your group number), as the translation key for automatic translation.
        1-2-2 In your key figure structure, create a new formula named “Exrate variance”.
              The formula should be “Sales Volume actual” minus “Sales Volume hist.”.
        1-2-3 Save and execute the query. You will see the influence of exrate changes on
              your results.
Section: ASAP Implementations




                  ASAP Implementations



                      Global ASAP



                      BW Reviews




  © SAP AG 2001
ASAP Implementations




                  ASAP Implementations



                      Global ASAP



                      BW Reviews




  © SAP AG 2001
SAP BW Implementation Methodology




   SAP BW Implementation Methodology

   Using ASAP for SAP BW implementation


   Key Success Factors




  © SAP AG 2001
ASAP Project Phases




    Project                                                                        Continuous
  Preparation                                                                     Improvement
                                                           Final
                                                        Preparation   Go Live &
                  Business      Realization                            Support
                  Blueprint


Project
Project
Start Up
      Up



          End of                                                In Final
                                        During cycle
         phase 1                                              Preparation
                                        configuration
                         After Data
                          Design
     Conceptual
     Conceptual                        Configuration        Performance
                                                            Performance
                                       Configuration
      Review
       Review                            Review               Review
                                                               Review
                         Design
                         Design
                         Review
                         Review
  © SAP AG 2001
A Typical SAP BW Project Lifecycle...

  Continuous Business Information Reengineering


                                                          Implementation Cycle 3




 Implementation Cycle 2
  Implementation Cycle 2

                                                          Roll-Out
                                                    ...
                                                                     Implementation Cycle 1
                                                                     Implementation Cycle 1
                       Prototyping                         5
                                              4                Planning & Strategy:
                   1         2        3                        Concept for Rollout
      Evaluation &                    Pilot                    and Further Planning
       Feasibility               Implementation    Go Live
                                                  & Support

   © SAP AG 2001
Why Use a the Specific SAP BW Implementation
Method?


   l Pre-configured Business Content
          n   SAP BW is not just a Data Warehouse…
          n   It requires a specific methodology to benefit from Business
              Content
          n   SAP BW uses a very specific data model
   l SAP BW speaks “business language”
          n   Early Success is possible
          n   Iterative Approach – Implement in cycles
   l SAP recommends a three layer model (see next foil)
                  w   1st layer: BW Strategic Planning
                  w   2nd layer: BW implementation
                  w   3rd layer: BW Project Mgmt.

  © SAP AG 2001
BW Implementations




  © SAP AG 2001
BW Strategy


  PROJECT PREPARATION                 l   Communication Strategy
  l Project Management                l   Program Management
  l Kick-Off                              Approach & Risk Assessment

  STRATEGY BLUEPRINT
                                      PROGRAM CHARTER
  l First Analysis of situation and
     preparation for Workshops        l Timetable of BW projects
  l Executive Workshops               l Staffing of Coordination
     (Requirements & Commitment)        Teams
  l Scope of implementation           l Requirements for
                                        Implementation Teams
  PROGRAM DEFINITION
  l Further Analyses Sessions
  l Information Model: Global
    structures: Information
    Requirements & Info Supply
    Chain
  l SAP BW System Landscape
  l Implementation Approach


  © SAP AG 2001
Phase 1: Project Preparation

  INITIAL PROJECT PLANNING                 ESTABLISH SYSTEM
  l    Project start up session               LANDSCAPE STRATEGY
  l    Project charter
  l    Team working environment            TRAINING PROJECT PLANNING
  l    Project organization (roles)        l Project team training plan
  l    Implementation strategy             l End user training &
  l    Project plan                           documentation strategy

  PROJECT PROCEDURES                       PROJECT KICKOFF
  l  Management standards
  l  Implementation standards              TECHNICAL REQUIREMENTS
         n   System configuration             PLANNING
         n   Post-Implementation service   l Identify requirements
             and support strategy          l Procure initial hardware
         n   System problem standards         (optional)
             and error handling
         n   System enhancement and
             modification approval         BW REVIEW - PROJECT
             process                         PREPARATION PHASE
         n   Naming standards
         n   Data administration
   © SAP AG 2001
Phase 2: Business Blueprint


  TRAINING                              BW DESIGN
  l Conduct project team training       l Data design
  l Prototype end user                  l Data access design (BEX and
     deliverables                         Non-SAP)
                                        l Authorization design
  BUSINESS REQUIREMENTS                 l System landscape strategy
    ANALYSIS                            l Technical design
  l Requirements workshops              l Procure technical components
  l Assess current data                   for Dev/QA/Prod (optional)
    warehouse and information
    access environments                 ESTABLISH DEVELOPMENT
                                           ENVIRONMENT
  BUSINESS CONTENT CHECK                l Prototype
  l Assess requirements
        n    SAP & non-SAP sources      DEFINE SYSTEM
        n    Master data                   ADMINISTRATION
        n    Data Access
  l    Identify data requirements for   BW REVIEW - BUSINESS
       each end user category             BLUEPRINT PHASE
  © SAP AG 2001
Phase 3: Realization


  DEVELOPMENT CONFIGURATION          TEST PLANS
  l Configure development            l Define system test plans
     environment                     l Define data test plans
  l Configure data access            l Define data access test plans
     environment (BEX & Non-SAP)     l Define authorizations test
  l Implement & validate                plan
     authorization concept (Dev)
  l Test BW environment              DEFINE SYSTEM PROCEDURES
                                     l Service level commitment
  DEVELOPMENT CONFIGURATION          l BW administration
     WORKSHOPS                          procedures
  l Prototyping solutions
                                     BW REVIEW – REALIZATION
  TRAINING                             PHASE
  l Define/develop/finalize end
     user training & documentation



   © SAP AG 2001
Phase 4: Final Preparation



    TUNING                           DETAILED PROJECT PLANNING
    l Mass Tests                     l Refine cutover
    l Database Tuning                l Refine production support
    l BW Tuning                         plan

    TRAINING
                                     CUTOVER
    l Conduct pre-go-live end user
       training                      l   Cutover
                                     l   Final approval for going live
    SYSTEM MANAGEMENT
    l Establish production system
       administration                BW REVIEW - FINAL
    l Conduct system tests             PREPARATION PHASE




   © SAP AG 2001
Phase 5: Go Live and Support



   PRODUCTION SUPPORT
   l Go live Checks
   l Support review
   l Provide production support
   l Validate live business
     process results
   l Conduct post-go-live end
     user training

   STRATEGIC BW PLANNING

   PROJECT END




  © SAP AG 2001
    Proposed BW Implementation Approach


               Cycle1: 1-3 Months



          Rapid Implementation
                                            Option 1: Add Externally Purchased Data



    l   Delivered InfoSources
    l   Delivered InfoCube
    l   Delivered Queries              or   Option 2: Extend Standard InfoCube
    l   Limited Number of Users
    l   Stable Technical Environment



                                       or   Option 3 : Integrate Legacy Data



                                                 3-6 Months


         © SAP AG 2001



n   In contrast to other data warehouse solutions BW offers the BW Business Content. The BW Content
    makes it possible to go life in a short period of time. If BW is connected to an R/3 OLTP, the BW
    Content includes the data extraction, staging and reporting.
n   In the first stage of a data warehouse project you should pick a limited subject area and use
    exclusively the BW content (extraction, infoobjects, sources and cubes) that are delivered with the
    standard BW and go for a life start in a period of only 4-8 weeks. The advantage of this approach is
    to feed back very fast to the report owners and work from the experiences gained in this short time
    frame.
n   In the next stages you can add to the BW content info cubes, either bring in external data, legacy data
    or extend the infocubes. The time periods of the subsequent projects can differ in intensity and
    duration.
SAP BW Specific Skills (Roles)




    l Five BW specific roles have been identified for a
      successful implementation
           n   BW Data Extraction
           n   BW Data Access (Frontend, Web)
           n   BW Data Architect, Administrator
           n   BW Application
           n   BW Basis
    l BW Project Team member can have one or more roles




   © SAP AG 2001
Business Information Warehouse Project Roles




   l BW Data Extraction
   l Responsible for identifying and obtaining the data required
     to satisfy the requirements of the BW project.
          n   SAP R/3 Data
          n   New Dimension Product Data
          n   Data external to SAP within the organization (legacy data)
          n   Data external to SAP from outside the organization (provider
              data - D&B, Nielson)
          n   ABAP




  © SAP AG 2001
Business Information Warehouse Project Roles




   l BW Data Access
   l Responsible for assessing the business requirements, and
     designing and developing a data access solution for the
     BW project.
          n   BW’s Business Explorer
          n   Certified ODBO clients: Non-SAP data access tools
                                                                       Author
          n   Visual Basic development                                  10%
          n   Web development                                             Analyst
                                                                           20 %
                                                            Consumer
                                                              70%




  © SAP AG 2001
Business Information Warehouse Project Roles




   l SAP BW Data Architect
   l Responsible for the overall design of the BW project
          n   BW InfoCubes
          n   Logical models
          n   BW process models
          n   BW enterprise models
   l Responsible for Administration




  © SAP AG 2001
Business Information Warehouse Project Roles




   l BW Application
   l Responsible for utilizing BW to satisfy the business
     requirements identified for the project
   l If the scope of the BW project is tightly controlled and can
     use standard BW Business Content, InfoCubes, and
     Queries, the BW Application Consultant may assume the
     responsibility to perform several roles concurrently to
     include




  © SAP AG 2001
Business Information Warehouse Project Roles




   l BW Basis
   l Responsible for the the BW infrastructure and Tuning
          n   BW Installation and Basis Parameters, Patches, Support
              Packages
          n   BW Landscape, Correction and Transportation Settings
          n   BW Sizing
          n   BW Performance & Tuning
          n   BW Authorizations




  © SAP AG 2001
    Project Organization


                                                                            Info Owners
                                       Information owner (business users)


                            Data
                        Architecture
                         & Adminis-                                   Frontend
                           tration                Steering              Team
                            Team                 Commitee

                                                 Project
                                                 Mgmt.
                           Data                  Executive
                        Extraction               Sposors              BW Basis
                          Team                                         Team




                                          Contacts: source systems




        © SAP AG 2001



n   Parallel work is possible in a BW project.
Using ASAP for SAP BW Implementation




   SAP BW Implementation Methodology

   Using ASAP for SAP BW implementation


   Key Success Factors




  © SAP AG 2001
ASAP: Comprehensive Solution


   l Roadmap
          n   Step-by-step project plan and explanations of tasks and
              activities
          n   Foundation of project plans (Microsoft project)
   l Tools and Accelerators
          n   Attached to the roadmap
          n   For project estimation and to set expectations (scope, time,
              resources)
          n   For project management: method/roadmap, spreadsheets,
              documentation templates
          n   For the BW consultant and customer: questionnaires,check
              lists, tools
   l Implementation Assistant
          n   Project Management Tool: combines project management
              with SAP BW specific accelerators and how-to’s.
  © SAP AG 2001
    AcceleratedSAP Tools Approach: Offline


                              Hide     Back Forward      Refresh     Print Options

                            Contents     Search
                                   Home Page                       Welcome to AcceleratedSAP
                                  What’s New
                                  Roadmap
                                  Implementation Accelerators
                                  Project Plan
                                  Question and Answer Database
                                  Issues Database
                                  Business Process Procedures

    The Implementation            Knowledge Corner
                                  Glossary
                                                                                                                      Continuous
    Assistant is the              Help
                                                                                                                       Change
    primary tool and                                                 Project
                                                                                                       Final
    framework in ASAP                                              Preparation
                                                                                                    Preparation Go Live &
                                                                             Business Realization
                                                                                                                Support
                                                                             Blueprint




                                                                   Version




            Implementation Assistant contains
            Roadmap, QADB, Knowledge Corner
        © SAP AG 2001



n   The Implementation Assistant is:
      - A PC tool that can run completely independently of the BW System
      - The one-stop collection of all tools and methods developed for the ASAP methodology
      - Network- capable
    ASAP Roadmap



                        Phase



                           Work Packages



                                     Activities              l Accelerators



                                              Tasks




        © SAP AG 2001



n   The ASAP Roadmap, regardless of the method of access, is divided into four types of organizational
    folders:
      - Phase - The major organizational steps of the ASAP Roadmap.
      - Work package - A group of activities designed to accomplish a major portion of a Roadmap
        phase. A work package is assigned to a project team for completion.
      - Activity - A group of tasks. The results of an activity can produce certain deliverables and can
        be accomplished by one or more project team members. Several activities comprise a work
        package.
      - Task - A specific event to be performed by a project team member.
        Tasks contain the important How To instructions needed for task completion and provide access
        to the accelerators:
        - How-To - Explanation of how to perform a process, activity , or task.
        - Accelerator - Documents, templates, tips and tricks used to accelerate task completion.
    ASAP Knowledge Corner


        l The Knowledge Corner contains a number of Consulting
          Guides written by consultants

     Contents   Search
            Home Page
           What’s New
           Roadmap
              Phase 1: Project Preparation
              Phase 2: Business Blueprint
              Phase 3: Realization
              Phase 4: Final Preparation      l Sizing Estimators
              Phase 5: Go Live and Support
           Implementation Accelerators        l BW Prototyping
           Project Plan
           Knowledge Corner                   l BW Presentations
           Glossary
           Help                               l Best Practice Examples




        © SAP AG 2001



n   The Knowledge Corner contains many consulting guides.
    BW on ASAP CD



          l CD includes implementation roadmaps for all mySAP.com
            applications
          l You can choose mySAP.com application BW as a flavor
            when installing ASAP activities → create a BW specific
            roadmap
          l Allows to choose more than one flavor




        © SAP AG 2001



n   The methodology will be provided to trained BW Consultants. They can use AcceleratedBW to plan
    and discuss with customers
AcceleratedSAP Accelerators




  AcceleratedSAP Accelerators
                 Accelerators
     Examples of Accelerators
     • Project Plan
     • Workshop Agenda
                                        Fill in the Blank
                                         Fill in the Blank
     • Questionnaires
     • End User Procedures                    versus
                                               versus
     • Technical Procedures            Start from Scratch
                                       Start from Scratch
     • Made Easy guide Books

     • Written by experienced SAP BW
       consultants




  © SAP AG 2001
The SAP BW 2.0B Accelerators

  l   Phase 1 Project Preparation                l   Phase 3 Realization
       n   BW Methodology Overview                    n   BW Excel Features
       n   Project Start Up (Workshop                 n   Issue log database (QADB)
           Template)
                                                      n   Frequently asked questions
       n   Roles & Skills in SAP BW Projects
                                                      n   Hierarchies in BW
       n   Project Charter for SAP BW Projects
                                                 l   Phase 4 Final Preparation
       n   Project Plan
                                                      n   SAP BW Performance / Tuning
  l   Phase 2 Business Blueprint
                                                 l   Phase 5 Going Live
       n   Business Blueprint Methodology
           (Information Requirements Analysis)        n   BW Operational Support
       n   Multidimensional Data Modeling with   l   BW Strategy Phase
           SAP BW
                                                      n   BW Strategy (Global Rollout)
       n   Templates Business Blueprint
                                                      n   BW SEM
       n   Sizing Tool
                                                      n   BW APO
       n   SAP BW Hardware Sizing
       n   SAP BW System Lanscape &
           Transport
       n   Authorizations in SAP BW
       n   Documentation Templates for SAP
           BW Authorizations
       n   ODS-Whitepaper
  © SAP AG 2001
SAP BW Documentation Enhancements




   l …several enhancements to the Online Documentation
   l …will be incorporated in Online Documentation of next
     release
   l Can be found on the SAP Service Marketplace
     (http://service.sap.com/BW/product
     background/Documentation Enhancements)




  © SAP AG 2001
ASAP for SAP BW Rollout Strategy




   l ASAP for SAP BW 2.0B is included on ValueSAP Edition 2
     CD
   l Release: January 2001
   l Online
          n   Accelerators, Documentation Enhancements
          n   http://service.sap.com/BW → Service&Support/BW ASAP




  © SAP AG 2001
SAP BW in the SAP Service Marketplace




          http://service.sap.com/bw
  © SAP AG 2001
Key Success Factors




   SAP BW Implementation Methodology

   Using ASAP for SAP BW implementation


   Key Success Factors




  © SAP AG 2001
Key Success Factors Findings



   l     Prepare information engineering in your organization
          n   SAP BW is more than a SAP module
          n   Use the power of SAP BW for your enterprise
   l     90-day rule
          n   Finish within 90 days and demonstrate!
          n   Use Business Content
   l     Consider the business processes
          n   Understand the process - understand the data
   l     Define scope and stay with scope
          n   Discuss and nail down real user requirements
          n   Implement in cycles




  © SAP AG 2001
Key Success Factors Findings




   l You need project skills
          n   Committed management, good core SAP BW team in-house!
          n   Manage expectations and communicate
          n   Let the projects be reviewed by SAP BW experts
   l You need business skills
          n   Involve the business (end user) from day one!
   l You need BW skills
          n   technical skills




  © SAP AG 2001
Primary Factors Impacting BW Project Length



   l In General, a BW Project Will Be of Shorter Duration and
     Will More Likely Be Successful if:
          n   The Project Uses Delivered Business Content
          n   Minor Modifications in R/3
          n   The BW Team is Skilled and committed
          n   The Team Consists of End Users that Understand the
              Business Process and their Data
          n   There is a Clear, Valuable Objective of the Project
          n   Executive Level Support is Strong
          n   The R/3 Environment is Stable
          n   The Technical Support Team is Strong (Data Modeling and
              Basis)
          n   The Organization has a Long-Term, Strategic Commitment
              to SAP
  © SAP AG 2001
Global ASAP




                  ASAP Implementations



                      Global ASAP



                      BW Reviews




  © SAP AG 2001
Overview SAP BW Strategy



   Overview SAP BW Strategy

   Global Information Model

   System Topologies


   Implementation Approach




  © SAP AG 2001
Focus on SAP BW Strategy

SAP BW Strategy
SAP BW Strategy

                                                             2.
                     Enterprise wide
                     Enterprise wide


                                                             SAP BW Strategy & Coordination
                        Global //
                        Global




                                                         Enterprise wide Implementation Guidelines




                                                                                        3.
Implementations
Implementations




                                       Pilot
                                       project(s)                             Project

                                                    1.
                     Local




                                                                                 Project
                     Local




                                                                                        Project

                                                                                             Project




                  © SAP AG 2001
Global ASAP and ASAP for BW

BW Strategy (Global ASAP)
l Provides Global Strategy definition before starting
  mySAP.com Application implementation program
l Opportunity to integrate information and business
  reengineering and benchmarking of value chain
  improvements
l Global information management



BW implementation (ASAP)
l Clear local focus of BW
  implementation
l Information optimization on
  local level
l Benefits on local level




   © SAP AG 2001
Deliverables of the SAP BW Strategy


  l   (Global) Information Model
       n   Business Requirements
       n   Information Supply Chain


  l   System Architecture and SAP BW landscapes
       n   Productive and Development System Architectures
       n   Heterogeneous Architectures
       n   Integration Issues


  l   Implementation approach
       n   SAP BW Roll out
       n   SAP BW and mySAP.com components


  l   Program Management Approach
       n   Organization
       n   Project Management


  © SAP AG 2001
Global ASAP: Tasks of the SAP BW Strategy

                                       Accelerators (for BW) :
                                       n Planning for global SAP BW
                                         Implementations
                                       n SAP BW & SAP APO System
                                         landscape and interface
                                         considerations
                                       n SAP BW & SAP SEM System
                                         landscape
               l Preparation
  Activities




               l Strategy Blueprint

               l Executive Workshops

               l Program Definition

               l Program Charter

                                                  max. 10-15 weeks




  © SAP AG 2001
What Are Global SAP BW Implementations?




   l     ENTERPRISE - wide Roll-out           l   GLOBAL SAP BW
   l     “Subsidiary” scope                   l   “Headquarters” scope
          n   local & corporate processes          n   corporate processes
          n   mostly local users                   n   global & local users
          n   detailed data                        n   consolidated data
          n   usually wide scope                   n   usually narrow scope
          n   operational & strategic needs        n   tactical & strategic needs
          n   data sources : local                 n   data sources: international
   l     Implementation                       l   Implementation
          n   Template (Company Content)           n   Stand-alone implementation
          n   Roll Out of Template                 n   User Roll out
          n   multi BW                             n   Usually single BW
   l     Transparancy                         l   Consolidation of information



  © SAP AG 2001
Scope of SAP BW Roll-out Scenarios

                                                      Enterprise wide
  Geographical Roll Out                               Information Manage
                                                      ment


        Corporate
        Corporate     B         U
                                U           S
                                            S           II


             JP
             JP        N
                       N        E
                                E           S
                                            S           S
                                                        S


             US
             US       C         O
                                O           N           T
                                                        T


             UK
             UK        E
                       E        N           T
                                            T

        Business
        Business    Business Business
                    Business Business   Business
                                        Business   Business
                                                   Business
         Area 1
         Area 1      Area 2
                     Area 2   Area 3
                              Area 3     Area 4
                                         Area 4     Area 4
                                                    Area 4

                                    Functional Organizational Roll out
  © SAP AG 2001
Global Information Model



   Overview SAP BW strategy

   Global Information Model

   System Topologies


   Implementation Approach




  © SAP AG 2001
Global Information Model


  l Global Business Requirements
        n   Business Areas and Key Processes
        n   Key Players and their tasks
        n   Performance Indicators

  l Global Information Supply Chain
        n   Looking at information as a resource
        n   Information Management Process as business process
        n   Sources, Transformations, Distribution, Value Adding


  l SAP BW Business Content as a reference
        n   best practice business information
        n   based on processes, not on departments
        n   designed enterprise wide



  © SAP AG 2001
Global and Local Information Models


l Global needs will have
  implications on          Global
  local models
l Best practice
  models increase
  transparency across
  systems...
                                            Best
                                           Practice
l ...and make central
  adaptation
  easier
                  Local
                                      Processes
                                      Roles
                                      Information

  © SAP AG 2001
Global Versus Local Data



l Data Harmonization
l Responsibilities
l Ownership            Global Data

                             Best Practice
                  Local Data     Data

                                 Process Data
                                 Master Data
                                 Organisational Data


  © SAP AG 2001
Information Model: Ownership of Data



 l   Ownership of Meta data                          ent
                                                 mitm
      n   Definition of KPIs                  Com

      n   Changing metadata
      n   Changing masterdata
 l   Ownership of data                                     Aut
                                                              hor
                                       lity                      isat
      n   Department                Qua                              ion
                               Data
      n   Country
      n   Centrally

 l   Ownership of info management
      n   Country                                   nge
                                                 Cha ment
                                                   age
                                                Man
      n   Centrally



  © SAP AG 2001
Global Information Supply Chain

   Current Warehouse Activity
   Data Source                Web Access



                                   ODS
                                   ODS                      Local
                                                            Local
     OLTP 1
     OLTP         Transformation                                                               BW
                                                                                               BW
                                   BW                        BW




                                         Transformation
                                    BW                       BW




                                                                              Transformation
                                   ODS
                                   ODS
     OLTP 2
     OLTP                          BW
                                    BW                               Global
                                                                     Global                    BW
                                                                                               BW
                                                                      BW
                                                                      BW


                                                            Local
                                                            Local
                                                             BW
                                                             BW

     OLTP 3
     OLTP                                                                                      BW
                                                                                               BW




                                                          Global Meta Data
                                                          Global

  © SAP AG 2001
System Topologies



   Overview SAP BW strategy

   Global Information Model

   System Topologies


   Implementation Approach




  © SAP AG 2001
The mySAP.com Information Hub

 l High performance
 l High performance
   data warehouse
   data warehouse                                          l Business performance
                                                           l Business performance
                                                             management
                                                             management
 l Active repository
 l Active repository
                                                           l Operational reporting
                                                           l Operational reporting
 l OLAP with specifics
 l OLAP with specifics
 l Frontend for                                            l Closed loop
                                                           l Closed loop
 l Frontend for
   consumer and
   consumer and                                              applications
                                                             applications
   professional
   professional                                              (e.g. campaign
                                                             (e.g.
                                                             management)
                                                             management)
 l Web deployment
 l Web deployment




                   l Platform for supply chain planning (SAP APO)
                   l Platform for supply chain planning (SAP APO)
                   l Platform for strategic planning (SAP SEM)
                   l Platform for strategic
                   l Platform for business consolidation (SAP SEM)
                   l Platform for business

   © SAP AG 2001
Architecture Scenarios


                                  l   Evolution
    l     Aggregation                  n   mySAP.com
           n   Mergers                 n   Migration to R/3
           n   Consolidation
                                  l   Integration
    l     Distribution                 n   Knowledge Management
           n   Hub and Spoke           n   Transactions and
                                           Information
           n   “Close the Loop”
                                       n   information in context
           n   Data Mining

                                  l   Multi - vs. Single SAP BW
    l     Globalization               Scenario
           n   Performance
           n   Standards
                                  l   Development vs. Productive
           n   Benchmarking           Landscape


   © SAP AG 2001
Data Flows


           3rd
           party
                                                   APO     SEM
                                            BW
                  Bapi                                  BW

                                       Data mart

           Drill Through                                      3rd
                                  BW                Odbo     party
           Plug In (Extractors)
   R/3
                                   Html


                         B2B                Web/
                                            Wap
                                                           MP
       CRM                                         WP


  © SAP AG 2001
Data Mart Interface

    Enterprise
      Data
                                                    l Extraction of data
                         SAP
    Warehouse            BW
                         BW                             n   Full and delta loads
                                                        n   multiple deltas possible
                                            SAP
                                            BW
                                            BW      l Data Mart Interface
    R/3
                                        Data Mart       n   across sytems for
                                  SAP
                                  SAP                       Cubes and ODS
                                  BW
                                  BW                    n   within system for ODS
                                                    l Benefits
Old
System                                  Special         n   Performance
                                        Data Mart
                                                        n   Flexibility

                    Exist. Data
                    Warehouse




    © SAP AG 2001
Productive Environment: Single Global BW


                                  l Separation OLTP - OLAP
                                  l Integration solved in OLTP
                   Global
                   Global         l Quick Roll-out of Info Users
                    BW
                                  l Performance improvement




                    R/3
                    R/3

             R/3
             R/3            R/3
                            R/3



  © SAP AG 2001
Multi BW: Productive Environment Example I


                  Global            l Global Model embedded into
                                      local implementations
                   BW
                                    l Global headstart
                                    l Harmonization done in local
                                      SAP BWs

  BW US
     US           BW UK
                  BW       BW Ger
                           BW Ger


  Source
  Source          Source   Source
                           Source
    US
    US              UK
                    UK       Ger
                             Ger


              Local

              global

  © SAP AG 2001
Multi BW: Productive Environment Example II


                  Global
                   BW
                                    l   Evolutionary process
                                    l   Globally predefined
                                        structures
                                    l   Local buy in
  BW US
     US           BW UK
                  BW       BW Ger
                           BW Ger
                                    l   clear separation

  Source
  Source          Source   Source
                           Source
    US
    US              UK
                    UK       Ger
                             Ger


              Local

              global

  © SAP AG 2001
Hub & Spoke: Multi BW Installations


           SAP
           SAP            SAP
                          SAP         SAP
                                      SAP           SAP
                                                    SAP   SAP
                                                          SAP
           APO            BW
                          BW          BW
                                      BW            BW
                                                    BW    SEM
                                                          SEM




                                            Integrated Landscape
                                            Distribution Scenario
                                SAP
                                SAP
                                BW
                                 BW         Analytical Applications




          SAP      SAP
                   SAP                      SAP
                                            SAP
          BBP
          BBP      R/3
                    R/3                     CRM
                                            CRM




   © SAP AG 2001
Example I: Development System Architectures

Global
Template
system               D   C   P   Global environment


        D            D   C   P
                                 Local environment


                     D   C   P
                                 Local environment



                                                D Development
            Local                               C Consolidation
                                                P Production
            global
                                                      Transportation
  © SAP AG 2001
Example II: Development System Architectures

Global
Development
system                 C    P   Global environment


        D              C    P
                                Local environment


                       C    P
                                Local environment



                                               D Development
            Local                              C Consolidation
                                               P Production
            global
                                                     Transportation
  © SAP AG 2001
Example III: Development System Architectures

Global consolidation system


                  D                          P   Global


                              C


                  D                          P
                                                 Local

                                      es!
                                       es!
                                  ntag
                               dva               D Development
            Local
                           Disa
                                                 C Consolidation
                                                 P Production
            global
                                                    Transportation
  © SAP AG 2001
Implementation Approach



   Overview SAP BW strategy

   Global Information Model

   System Topologies


   Implementation Approach




  © SAP AG 2001
Implementation Approaches



  l   Top Down                                 l   Bottom Up


             J integrated                             J fast
             J no redundancy                          J local motivation
             J changes                                J ROI

             L long implementation                    L redundancies
             L overhead/ costly                       L no integration
             L difficult to get local buy in          L control


                                     SAP BW Strategy is top down
                                            Strategy is top down
                                the SAP BW Implementation bottom up!
                                        BW Implementation bottom up!


  © SAP AG 2001
    Iterative and Integrated Approach



      Scope: Business
      Areas/ Countries
      live

                                                                  BW users

                        S
                        T
                        R
                        A
                        T
                        E
                        G
                        Y


        © SAP AG 2001



n   After establishing a big overview in phase 1 and partly in phase 2, you start „mini-projects“, so-
    called delivery cycles. (phases 3,4,5)
n   During the cycles, the skill set at the customer will improve and the consultancy effort and skills
    requirement will change during a roll-out.
Integration


   l    Sequential implementations
         n   R/3 -> BW -> SEM           data warehouse approach
                                        budget & committment vs. stability
         n   BW -> R/3                  migrations to R/3
         n   BW -> new mySAP.com Apps   first to market


   l    Parallel implementations
         n   R/3, BW -> BW              information and processes
                                        phase dependent
         n   BW, APO                    global supply chain mgmt.
         n   BW, SEM                    consolidation, mgmt reporting

         n   BW, Workplace, KW          increasing trend




   © SAP AG 2001
Global Data Warehouse Implementation
Organization



Information Integration
Information Integration
   and Management
       Management                                                Sponsor(s)
                                                                 Sponsor(s)
                                      Corporate/
                                       Corporate/
     Review board
     Review board
                                    Subsidiary BW
                                    Subsidiary BW
                                   Integration Team
                                   Integration

                   Local change                   Local change
                      agents                         agents


                    Local / Business Area
                    Local                     Local // Business Area
                                              Local Business Area
                   Implementation Team II
                   Implementation Team       Implementation Team II
                                             Implementation Team II




   © SAP AG 2001
Communication: Selling & Change Management


   V     Information hiding
   V     Organizational difficulties
   V     Acceptance
   l Interface Management
   l Internal Marketing
   l Intranet, newspapers, top management


          Early and efficient communication
             is the key to success for an
                enterprise wide project


  © SAP AG 2001
BW Reviews




                  ASAP Implementations



                      Global ASAP



                      BW Reviews




  © SAP AG 2001
Elements to Ensure Quality



   l Use of the AcceleratedSAP Roadmap
          n   A tried-and-tested approach
          n   Integrated quality checks and knowledge transfer
   l SAP Review Program
          n   Review people
              SAP Reviewers (project executives)
          n   Review processes
              Interviews, analyses, risk assessment,
              recommendations
          n   Review products
              Analysis tools, checklists, reports




  © SAP AG 2001
What are BW Project Reviews?



   l     Independent and objective project
         reviews by SAP BW experts
   l     Consistent review approach worldwide
   l     Scope of review
          n   Conceptual and Design issues
          n   BW specific Technical areas
          n   Project management areas
          n   Assessment of potential risk factors
              (scope, communication, documentation, motivation, etc)
          n   Advice on which areas to focus on
              (project success factors)
          n   Review of implementation method




  © SAP AG 2001
BW Project Review Process



   l Independent and objective reviews by BW experts
   l Scheduled visits with agenda and timetable
   l One or two days on site
   l Interviews with project team, management, and end users
   l Study project documentation
   l Present findings and recommended solutions to
     management




  © SAP AG 2001
SAP BW Review Program




Sales                                Implementation                  Continuous improvement


                              ASAP Roadmap Quality checks
 Project
Estimator


   Project Start-up Session
                                                              GoingLive Check
                                                              GoingLive

                   Yes
                   Y      o
                         No      Project reviews                               s   No
    Yes
    Y      o
          No                                                                 Ye
                         1       2          3         4          5

                                                                             EarlyWatch
                                                                             EarlyWatch

                   Conceptual Review            Configuration Review
                                                Configuration

                                         Design Review
                                                Review       Performance Review

   © SAP AG 2001
BW Project Review Objectives



   l Strengthen customer relationship management
   l Ensure successful project implementation
   l Global standardization for BW Reviews
   l Ensure BW Tool is used most efficiently for supplying
     customer requirements
   l Compliance with ASAP standards




  © SAP AG 2001
Benefits of the BW Project Reviews



    l Supports successful implementations
    l Early identification of project risk factors
    l Continuous improvement of the SAP BW product
    l Ensure success of BW base for future New Dimension
      Products
    l Lower implementation costs
    l Reduce implementation time
    l Increased customer satisfaction
    l Co-operation with Implementation partner




   © SAP AG 2001
Who Carries Out Project Reviews?



   l BW Regional Implementation Groups
   l Available worldwide (rollout in progress)
   l Consistent review approach worldwide
   l Partner involvement




  © SAP AG 2001
Key Interviews



   l Key persons to be interviewed:
          n   Project sponsor
          n   Project management
          n   team leads
          n   team members
          n   Business consultant
          n   Power/End users
          n   Technical team leader
   l Agenda and Questionnaire
     are used as a guideline




  © SAP AG 2001
Key Documents to BW Review



   l     Project charter
   l     Project scope document
   l     Project organization
   l     Budget and resource plan
   l     Project plan and status reports
   l     Project standards
   l     Project issue log
   l     End user requirements
   l     Data Model documentation
   l     Sizing document




  © SAP AG 2001
SAP BW Project Review Focus Areas




                       Conceptual Review
                        •   Project Scope
                        •   Project plan
                        •   Resource planning
                        •   Defined KPIs
                        •   High level sizing




  © SAP AG 2001
SAP BW Project Review Focus Areas




                               Design Review
                               •    SAP BW data model
                               •    System landscape
                               •    Knowledge transfer
                               •    User Roles
                               •    End user requirements




  © SAP AG 2001
SAP BW Project Review Focus Areas




                               Configuration Review
                               •    Authorisation Concept
                               •    Aggregates
                               •    Enhancement of Business
                                    Content
                               •    Configuration of data flow
                                    (update Rules & staging)
                               •    Transport Concept


   © SAP AG 2001
SAP BW Project Review Focus Areas




                  Performance Review
                  •   Database analysis
                  •   Tuning parameters
                  •   Sizing check
                  •   Hardware setup
                  •   Loading process




  © SAP AG 2001
Frequently Asked Questions

   l     Who can order SAP's project reviews?
          n   All partners and customers
   l     What do partners think of this?
          n   QA helps the partner with the implementation
          n   Independent and objective review
   l     Why will customers accept project reviews?
          n   They involve SAP as a coach during implementation
          n   They will accelerate their implementation project
          n   They provide advice on improvements
          n   They focus on critical success factors
   l     What about SAP's own implementation projects ?
          n   These will also be reviewed
   l     Where can you order project reviews?
          n   tobias.dosch@sap.com for Europe
          n   margaret.anderson@sap.com for Americas
  © SAP AG 2001

				
DOCUMENT INFO
Shared By:
Tags:
Stats:
views:1743
posted:2/25/2010
language:English
pages:493