Professional Documents
Culture Documents
Applies to:
SAP BI – Logistic cockpit extraction. For more information, visit the Business Intelligence homepage.
Summary
This article involves customization of extract structures for Logistics. The LIS technique is not being used
and LO is the upgrade SAP solution for all Logistic extractions
Author: Sandeep Singh
Company: Accenture Services
Created on: 06 August 2008
Author Bio
Sandeep Singh has been working on SAP BI from last 4 years and is a certified NetWeaver 2004s
consultant.
Table of Contents
Logistic Extraction...............................................................................................................................................3
Step-by-Step Maintenance of LO Cockpit.......................................................................................................3
Related Content................................................................................................................................................13
Disclaimer and Liability Notice..........................................................................................................................14
Logistic Extraction
The aim of this document is to step by step help the new users working on the LO Cockpit
The LO cockpit configuration screen (LBWE) contains following key parameters:
1. Maintenance of extract structures
2. Maintaining InfoSources
3. Activating the update
4. Job control
5. Update Mode
a) Serialized V3 Update
The document data is collected in the order it was created and transferred into the BW as a batch job.
b) Direct Delta
The extraction data is transferred directly from document postings into the BW delta queue.
The transfer sequence is the same as the order in which the data was created.
c) Queued Delta
The extraction data from document postings is collected in an extraction queue, from which a periodic
collective run is used to transfer the data into the BW delta queue.
The transfer sequence is the same as the order in which the data was created.
d) Unserialized V3 Update
This method is opposite to the Serialized V3 Update. The BW delta queue does not have to be the
same as the order in which it was posted.
Click on the clock symbol to delete the existing contents from the setup table if any so that its free and we
can go ahead and make or configure our Logistic Datasources.
In the above screenshot: Click on the Update Overview text to reach the following screen. This will take you
to SM13 for any relative table updates and Execute.
This will take you to RSA7 transaction to view the delta queues if any
Click on Run and It will Prompt for confirming the entries in the Extract structure. Assign a request so that it
generates extract structure successfully.
Now on the Main LBWE screen, you can see RED status before the datasource
Assign a Request to have the Datasource screen where properties related to fields can be modified.
As you assign this and come back you will see a change in the status color as YELLOW.
Now go to the BW System and Replicate the related Datasource from the Exact Source system.
Now go back to the R/3 System and Click on the ACTIVE parameter under the Job Control, assign a request
Now you will see that the status color will turn as GREEN and then you can assign the update mode as well.
Now in the BW system create transformations from the datasource to the Infoprovider. Create an
infopackage and DTP to load the data.
Related Content
Refer to SAP Help site
Refer to https://sdn.sap.com
For more information, visit the Business Intelligence homepage.