on 06-19-2007 8:11 AM
please exp of Lo extraction?
hi reddy,
Check these links:
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
cheers
Sunil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Also check
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
Eddy
-
PS. Reward useful answers and earn points yourself
hi dude,
LO->Logistics
steps to do lo
1.RSA5 TO TRANSFER DATA
2.LBWG TODELETE FOR SET UP DATA
3.LBWE MAINTAIN COMMUNICATION STRUCTURE(COCKPIT)* SELECTING MODES
R/3
SELECT SOURCE SYSTEM RC DATASOURCE OVER VIEW
REPLICATE ON PARTICULAR MODULE
ASSIGN DATASOURCE
RUN THE LOAD
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Krishna Reddy,
LO extraction is one stop shop for all the logistics extarctions .
LO dataosuurces come as a part of the business content in BW .
we need to transfer them from the BCT and then activate them from D version to the active Verion A .
Go to the tcode -- RSA5 -
Transfer the desired datasource .
and then LBWE to maintain the extract structure
LBWG -- to delete the setup tables -
why ... ?
OLI*bw -- Statistcal initialization .
LBWQ --- To delete the extractor queue
SM13 -- to delete the update queue .
LBWf -- to get the log .
its always recommended to have the Queued delta as an update method , since it uses the collective run to schedule all the changed records .
once the intial run is over set the delta method Queued to periodic for further delta loads .
why ..?
we need to delete the setup tables since we need to delete the data that is laready in them \ and also we bcoz we will change the ES by adding the required fields from the R/3 communuication structrure .
we can alos sel n hide the fields here .. all the filds in blue r mandatory ..
if the required firlds r not avilable we will go for the DS enhancments .
let us know if anny queries .......
drop in ur maid id will send some docs ...
regards -
Kumar Sarvepalli -
Honor points if useful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Kumar,
thanks for your valuable notes on LO, I am not able to differentiate the usefulness of the three different update methods, queued delta, direct delta and unserialized v3 update. What are the advantages of one update over the other update. Please send me if you have any documents on LO to my email id - vsangomula@yahoo.com.
Very much appriciated.
thanks
venkat
Hi Krishna...
here i'm giving step by step procedure.. plz go thru it...
1. Check & activate the datasource in R/3 with T-code= RSA5 ( if its not activated already)
2.Check in T-code= RSA6 for the required datasource ( you can get the information on which data source/infosource required for your Infocube /ODS from BI Content in http://help.sap.com
3.T-Code= LBWE in R/3 side & check if the data source is extracting data or not.
4.Check steup table using T-code=SE11
5. Delete the setup table... go for Extractor checker (RSA3) just to see the setup tables data (full/delta initialization).
6.Delete the setup tables data by using LBWG.
7.We need to fill the setup tables for the first time loading. In
filling the setup tables we can select between Full load and delta
initialization loads.
-
1.Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
2.Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
3.In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
4.Go to transaction RSA3 and check the data.
5.Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
6.Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
7.Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
8.Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
9.Now you can go to your data target and see the delta record.
-
T-Code: LBWE
First we need to check which data source suits the client's
requirements in LBWE.
Check whether it is in Active version/Modified version. If it is
in M version go to RSA5 and select our data source and press on
Transfer. Then go to RSA6 and see whether the datsource is been
transferred.
If the datasource is already in active version then we need to
check whether the datsource is already extracting data in to BW.
If the datasource is extracting the data then we need to check the
data existence in Setup tables (use SE11 to check the setup tables
data. For every extract structure one and only one setup table is
generated whose technical name is Extract structure name+ setup, for
eg. If extract structure name is MC11VAOHDR then set up tables name
is MC11VAOHDRSETUP) and Extraction Queue (LBWQ) and Update tables
(SM13) and Delta Queue (RSA7). If data exists in any of these T-
codes we need to decide whether we need the data in BW or not. If we
need the extract it as we do in LO-Extraction below. I f we don't
need delete the data.
The dataflow from R/3 into BW:
We nee to generate the extract structure by selecting the fields
from the communication structure in LBWE.
Generate the datasource and select the selection fields,
cancellation fields, hide fields that we want.
Replicate it into BW. Then we need to attach Info source(Transfer
rules/communication structure) to the datasource. We got 3 methods
to attach the infosource..
1) Business content:: Business content automatically proposes the
transfer rules and communication structure, we don't have to do
anything manually.
2) Application proposal: Here too proposal is done but some objects
will be missing which we need to assign in the transfer rules.
3) Others: here we need to create the transfer structure, rules,
comm. Strct from the scratch.
Modeling like infocube, Infosurce attachment, .
Then activate the extract structure.
We need to fill the setup tables for the first time loading. In
filling the setup tables we can select between Full load and delta
initialization loads.
Filling Set up table:
T Code : SBIW
Settings for Application-Specific DataSources (PI)->Logistics--
>Managing Extract Structures>Initialization>Filling in the Setup
Table -->Application-Specific Setup of Statistical Data --> in that
Youcan perform the Setup (Example : SD-Sales Orders - Perform Setup)
and execute .. or else direct T Code : OLIBW ( means based on your
application like sales order/billing/ purchase etc) For setup
tables T-Code is OLI*BW where * equals to application number like 02
fro purchasing,08 for shipment ..
First we need to decide whether we want delta loads to be
performed in the future. If we want to do delta loads, then we need
to go for Delta Initialization process or else do full load.
When we perform setup tables extraction, since setup tables are
cluster tables, we can't see the data in the setup tables. So we go
for Extractor checker (RSA3) just to see the setup tables data
(full/delta initialization).
Then create infopackage and select Full or Delta initialization in
Update tab and schedule it.
Delete the setup tables data by using LBWG.
Now we need to do delta loads.
Delta load data flow differs with various delta update methods. We
got 3 delta update methods as u know.
If we select "Queued Delta"update method then the data moves to
Extraction queue(LBWQ). Then run Collective update to move the data
from LBWQ into Delta Queue (RSA7). Then schedule the data using the
infopackage by selecting Delta Load in the update tab.
If we select "Direct delta" then the delta data moves into RSA7
directly.
If we select "Unserialized V3" method then the data goes
into "Update tables(SM13)", then run Collective update to move the
data from SM13 into RSA7. Schedule the data using infopackage.
If we click on Maintenance, we can generate the extract structure.
If we click on 2LIS_02_CGR button, then we we can generate data
source
Inactive under Update column: we can make a extract structure as
active or inactive.
If we click on Job control button the we can maintain the
collective update parameters like, start time, and is it hourly once
or dialy once
If we click on Queued delta button under Update mode then we can
select among 3 delta update methods.
Only Full/Delta initialization data loads only moves into setup
tables. Delta load data doesn't move into setup tables.
**RSA3 contains only setup table's data
Only Delta update data moves into RSA7/LBWQ/SM13 no full/delta
initialization loads data.
Thanks
@jay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
see this post
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/forums">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/forums</a>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.