cancel
Showing results for 
Search instead for 
Did you mean: 

LO Extraction

Former Member
0 Kudos

Hi All,

Do we need to use LO Extraction cockpit always for all logistic extractions from R/3?

Can't we just do that by activating all the required infocubes, infosources etc in BW and also by Transforming the required Data source(ex: 2LIS_02_ITM etc) in R/3 using RSA5 and then create an infopackage in BW and schedule the load.

If we cannot do that can u please explain me why?

Thanx in advance...

Best Regards,

Nimma.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

hi Nimma,

yes, we will need lo extraction customizing cockpit,

we will need this to maintain the structue, datasource, determine update mode, job control etc

Roberto's lo cockpit weblog series

/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/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis

/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it

hope this helps.

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Nimma,

You are right. We need to use LO Cockpit to extract data from the logistic applications.

As you have said to activate all the infocubes, infosources etc...and start loading data, in that case how come the system will decide what structure it has to use for extracting the data or we can say the maintenance of Extract structure as per the business requirement is done in LBWE, so we need to setup one environment to go ahead with the extraction. If we only activate and transfer the datasources, it will transfer all of the fields and we need to deal with those fields as well which are not required for your business need.

Hope it helps you!!!!

Regards,

Amit

Former Member
0 Kudos

Hi All,

Thankyou for your help. Very Helpful answers.

Assigned points to everyone.

Best Regards,

Nimma.

Former Member
0 Kudos

Hi,

Do we need to use LO Extraction cockpit always for all logistic extractions from R/3?

>> Answer is yes unless or untill you create your own datasources in R/3, which are called as Generic datasources & you can create these on table, view, function module, query etc. Or try loading data in cube by Flat file ( CSV or ASCII)

Can't we just do that by activating all the required infocubes, infosources etc in BW and also by Transforming the required Data source(ex: 2LIS_02_ITM etc) in R/3 using RSA5 and then create an infopackage in BW and schedule the load.

>> All the steps mentioned by you are fine, but how does your system know which data is to be collected from OLTP system (tables) for your cube in BW. LO Cockpit has all these program ready for you. to take it further you can enhance these to suit your requirement perfectly.

hope it helps.

VC

If we cannot do that can u please explain me why?

Former Member
0 Kudos

Hello Nimma,

Though you have installed everything on the BW side( including cubes, infosources etc), there are a few activities that need to be done on the r/3 side for Logistics applications.

These are done in the LO extraction cockpit.

The datasources on the r/3 side talk to the corresponding datasources/infosources on BW side.

But activities like activating extract structures, populating setup tables or scheduling v3-delta runs to populate delta queues on the R/3 side need to be done so that these datasources have data.

This then can be pulled in the BW side using BW-installed objects.

Hope it helps....

Regards,

(Please Dont forget to assign points if it helps....)

Former Member
0 Kudos

Hello Nimma,

This weblog should answer many of your questions.

/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis

Plese go through it and if you still have any questions, post them.

Regards,

Praveen