Lo extraction part 6 implementation methodology

LO Extraction - Part 6
Implementation Methodology

Applies to:
SAP BI, Business Intelligence, NW2004s. For more information, visit the EDW homepage.

Summary
This part of the article gives you about the implementation methodology in LO extraction.

Author : P Renjith Kumar
Company: SAP Labs India Pvt Ltd
Created on: 02 September 2010

Author Bio
P Renjith Kumar is presently working in SAP Labs India Pvt Ltd and specializes in
Extraction and Modeling areas of BI. Basically as an ABAP consultant, he has extensive
cross functional experience and has been with end to end SAP ERP and BI implementation
projects across manufacturing domain.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 1

LO Extraction - Part 6 Implementation Methodology

Table of Contents
Introduction ......................................................................................................................................................... 3
Steps in ECC system side .................................................................................................................................. 3
Activate datasource......................................................................................................................................... 3
Tr.RSA5 .............................................................................................................................................................. 3
Activate extract structure .................................................................................................................................... 5
Tr.LBWE ............................................................................................................................................................. 5
Filling setup table ................................................................................................................................................ 6
Tr.SBIW .............................................................................................................................................................. 6
Steps in BI side. ................................................................................................................................................ 10
Loading to cube ................................................................................................................................................ 14
Delta Update ..................................................................................................................................................... 20
Related Content ................................................................................................................................................ 23
Copyright........................................................................................................................................................... 24

© 2010 SAP AG 2


Introduction
First we will check the steps in ECC system followed by steps in BI system. Assume that you need to load
cube 0SD_C05. For this you need two datasource 2LIS_11_VAHDR and 2LIS_11_VAITM. As the name
depicts, it is of application component 11 and it belongs to VA (Sales) and HDR, ITM represents header and
Item data.

Steps in ECC system side
Activate datasource
Tr.RSA5

This will make the datasource to be activated from D version to A version. You can check this in table
ROOSOURCE.

You can see that DELTA is ABR, It means, this datasource supports delta and the Type is ABR (After,
before, reverse image). This is compatible with DSO and cube.

© 2010 SAP AG 3


To know more about delta check in table RODELTAM

Once datasource is activated, for any post processing actions like enhancements etc .. you can check in
RSA6

© 2010 SAP AG 4


Activate extract structure
Before filling setup table you need to activate the extract structure. Follow the steps given below
Tr.LBWE

You can see that the extract structure is inactive and the events are those will is used to populate the data.
You can know more about events in my previous article versions. The update is showing as inactive, now
click on that ‘inactive’.

© 2010 SAP AG 5


Now schedule the V3 job

Filling setup table
Once the activation is done, we can fill setup table from SBIW.
Tr.SBIW

© 2010 SAP AG 6


This invokes the report as shown below; the same screen can be called by transaction OLI7BW

Now provide the name of run and give the date in future. Selections can be provided. Execute

© 2010 SAP AG 7


Checking Extracted Data
Since the extract table is cluster table, it is meaningless to see in data dictionary, so we have some other
method to read data from extract structure.
Tr.RSA3 Give the datasource name to check the data that is extracted. Execute

© 2010 SAP AG 8


Select Display list
Double click on record

So 11 records are extracted.

© 2010 SAP AG 9


Steps in BI side.
Replicate the datasource from source system and follow the dataloading process.
Upload the data from setup table

Need to migrate this datasource, you can see datasource with square, this is 3.x datasource icon.

© 2010 SAP AG 10


Do this for both the datasource, now you can see the datasource like this

Create an Infopackage to load the data from setup table

For BI the processing of Infopackage is by default only to PSA

© 2010 SAP AG 11


The update is full upload; this will fetch data from setup table. For more info read my previous articles

Start the extraction

Once you get this, go to monitor, check for data in PSA

© 2010 SAP AG 12


Loading to cube
To load data to cube you need to create a DTP from datasource to cube.

© 2010 SAP AG 14


Similarly load the 2LIS_11_VAITM datasource from Infopackage

© 2010 SAP AG 15


Now create transformation for that too

Create a DTP for each datasource

Activate and start the execution

© 2010 SAP AG 16


Delta Update
Check RSA7 in source system, you will not find entries for this datasource as of now.

Now from Infopackage do and ‘Init without data transfer’, this will initialize the delta.

© 2010 SAP AG 20


Now create a Delta Infopackage for both the datasource and schedule it. You can group all these things in a
process chain and monitor the loads daily.
Now any change in the ECC system will trigger a delta record which will be picked by the delta Infopackage
and from there the DTP will send the delta data to cube.
This completes the LO extraction implementation methodology, this is very short overview, do read all the
previous articles to know in detail about each process.

© 2010 SAP AG 22


Related Content
SDN
SAP Help
Reference to my previous articles
LO Extraction Part 1 – SD Overview
LO Extraction Part 2 – Database Update Logic
LO Extraction Part 3 – Extractor Logic
LO Extraction Part 4 – Update Methods
LO Extraction Part 5 – DataSource Overview

© 2010 SAP AG 23


Copyright
© Copyright 2010 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.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

© 2010 SAP AG 24

Lo extraction part 6 implementation methodology

Recommended

More Related Content

What's hot (20)

Viewers also liked (14)

Similar to Lo extraction part 6 implementation methodology (20)

Recently uploaded (20)

Lo extraction part 6 implementation methodology