Advantages of Lo cockpit extractors

Hi,
What are the Advantages of Lo cockpit extractors in bw ?

Hi Karthik,
Some of the advantages when compared to LIS and other extarction are as follows:
1.Improved performance and reduced volumes of data
a.Update using batch processes
b.LIS tables are not updated
c.Document changes - Only relevant changes to BW are captured
2. Simple handling
a. Simple Customizing Cockpit
b. Easy Enhancements
3. Standardized solution for all Logistics applications
4. No use of LIS functions
Bye
Dinesh

Similar Messages

Where should i find the LO-Cockpit Extractors.

Hi,
I am a new comer for SAP BW, can anyone tell me where can i find the LO-Cockpit extractors in IDEAS ..
Ravi..

hi
LO step by step mechanism:
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
Take a look at Roberto's weblogs on LO Cockpit(good material) :-
/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
when to go for direct delta, queued delta, unserialized V3:
During the first load, if it either init or full, data will come from setup table.
1. When number of document changes between two delta extractions is small, you go for direct delta. The recommended limit is 10000 i.e. if the No of doc changes (Creating, changing and deleting) between two successive delta runs is within 10000, direct delta is recommended.
Here the number of LUWs are more as they are not clubbed into one one LUW.
2. Queued delta is used if number of document changes is high ( more than 10000). Here data is wriiten into an extraction queue and from there it is moved to delta queue. Here upto 10000doc changes are cummulaed to one LUW.
3. Unserialized V3 upadte methos is used only when it is not important that data to be transferd to BW in the exactly same sequence as it was generated in R/3.
hope this helps!!!
Regards
Dhanya.

Delta Extractor Is not picking changed values

Hi All,
When the values or texts in a PO are changed the delta extractor is picking up the changed values as deltas (provided the changes where done in PO Header or Item Overview) but when a PO values or text that are changed in the Item Details the delta mechanism is not picking up the changed values (the fields whose values are changed were initially not in the LO Cockpit Extractor they where added and the values to these fields are populated using an ABAP Program)
Is there a reason that Delta mechanism doesn't work for fields that are not delivered by the SAP Extractor or do we need to modify the code in order to collect these changed values by Delta Mechanism (Direct Delta as the Update Mode).
Please let me know if anybody came across the same problem .
Thank you all in advance.
Regards,
Dhanam

Hi,
this is another story.....
You'll have to
- enhance the PO items table (EKPO) with your fields
- activate the right customer exit for purchase orders (search in SMOD; or in this forum..) and populate your fields during this exit. if the field needs to be maintainable by the R3 user, you'll have find a SAP exit (again SMOD) in order customize one of the screen and populate your fields in R3.
- use another exit to populate the new fields to LO delta queue
- enhance your BW extract structure (done)
- and so on...
As you can imagine, the above get quite more complicated (an expert in MM shall support you) and it needs to be approved by the PM since you'll modify R3.
But that's basically it!
hope this helps...
Olivier.

Changing the datasource of LO cockpit inR/3..need a backup plan

Hi gurus,
i am going to change the datasource in production system i have done everything in Dev and QAs but my client is asking for a backup plan if something goes wrong.
like if the transport fails he want everthing to normal without effecting the setup of deltas and data in BW
can somebody suggest me what i can do as a backup plan if something goes wrong.
thanks and regards
neelu

Hi Neel
If something goes wrong and it mess up your deltas in Production system then what is the backup plan?
This is what I think -
If your data source is LO cockpit extractor then ensure following -
Before your R/3 transports ,stop V3 batch job .
Lock the users (transaction lock) ,
Stop batch jobs that will update base tables of extracor
Drain the delta queue into BW till you get 0 LUWs in RSA7 for that datasource in R/3 system.
Activate the last request in ODS and also send the data into Infocube . Now you have all data till that time into BW.
Import your transports. Then execute V3 job in R/3 and run Info package from BW .
If something is messed up then immdiately push another transport that will repair it .Then do Init without data transfer and resume deltas.
For other extractors just ensure to Drain the delta queue into BW till you get 0 LUWs in RSA7 for that datasource in R/3 system.(I assume that you will take care of batch jobs /transactional update - they should be stopped for any extractor)
Hope this plan helps you .
Please let me know if you still have questions.
Best of luck
Pradip

Extraction from R/3 extractor to flat file

Hi,
I want to be able to extract data using r/3 extractors (LIS/Business Content extractor) into r/3 itself loading the data into a transparent table or loading the data into a flat file on the application server.
As an example, i want to extract data from 0MATERIAL_ATTR into a flat file.
I don't want to use BW or any other third party tools for that job, only R/3 6.4.
Is it possible ? Do i need to code and ABAP program for that ?
Thx fro your answer.
Ludovic

0MATERIAL_ATTR was just an example.
What i need is to extract data from LO-Cockpit 2lis_* extractor. In these case i don't have any table behind, data are being calculated in memory..therefore i really need to load the extracted data into flat file or transparent table.
Another point about RSA3, some LO-Cockpit extractor returns about 10'000'000 lines, so it makes impossible to run rsa3 correctly.
Do you have any other suggestion ?

Hi experts why we use set up tables in LO cockpit

please forward to my personal mail id
[email protected]

The logistic cockpit extractors are different from the others. They use setup tables and delta queues for initial loading and delta loading respectively. The delta queues act as a buffer area which is detatched from the business logic of the applications' operations (ref. <a href="/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146 COCKPIT DELTA MECHANISM - Episode one: V3 Update, the serializer</a>).
The other extractors read the application tables directly, both during the initial loading and during the delta loading. This means that whenever BW requests the data, a function module extracts the data from the R/3 tables.
I wonder why there is such a technological difference between the 2 classes of extractors. Could someone please shed some light on this? What considerations may have led to this kind of architectural choice? Is the number of transactions occurring in the applications covered by the LO extractors significantly greater than that occuring in other applications (e.g. FI, CO, etc.)? In this case, the ERP system could certainly benefit from a delta management buffer area.
Thanks&Regards, Davide

Follow-up on Ravi's User Exits example

Hi,
Ravi's user exit example:
You have a content data source with fields say customer,sale org, profit center and amount. You wish to add sales manager to this extractor. You locate the table and field name and append that field to the extractor and write a code to pick that field when the extractor extracts data. This piece of code is called exit. What it does is the system reads the customer code.
In the above example explaining customer exists, regarding the field, can you clarify locate the field. I read that if this field were available in the LIS communication structure that would be an enhancement to the structure where we only move the field from the left to the right (extract structure). In this case an append structure will be generated in the corresponding Include structure.
In the case of the user exit, my understanding is that the field in question, in this example, Sales Manager, is not available in the LIS Communication structure so I was expecting that you would state create the field but you said locate the field. Did you mean that, and if so, locate from where? Because if it is being located from the LIS communication structure then I would not expect a user exit, at least from my understanding.
Thanks.

Hi Amanda,
Yes, a field can be created when none of the SAP defined fields are solving the issue on hand. In this case too User exits are used. These fields are then appended to the tables.
So all fields are in some table or the other. The field that you require has to be located in these tables and appended to the extractor. This again requires User Exits.
For LO Cockpit extractors, if the field is already available in the extracstructure in LBWE then it can be moved from left to right and no extra coding is required.
Hope this helps.
Kumar

Deleted R/3 records Not coming to BI

I'm using the delivered LO cockpit extractor 2LIS_46_SCL for Global Trade Management (GTM). Its a LO Cockpit extractor, so I'm assuming it works the same way as all the other LO Cockpit extractors.
The user is creating a contract in R/3 with two line items (10 and 20) and saving it. Later that same day they delete line item 20 and create line item 30.
When I do the 'delta' extraction later that night, I get the 10, 20 and the 30 records loaded into the delivered ODS on the BI system. The delta ran again a day later and there still wasn't a delete for the 20 record.
My question is when will the line item 20 record get deleted in BI?
Regards,
Mike...

Mr. BW,
I'm a little closer to identifying the problem, but still not sure if the problem is in the R/3 process that creates the delta queue records or the BI processing of the delta records.
The R/3 process that is creating the delta records is a custom ticket application process. When there is a 10 and 20, it creates a 30 record and does a commit. It then has a followup step that deletes the 20 record and does a commit. I looked in RSA3 after this process ran and I see several records in the delta queue for or 20 record.
My followup question is this. When the records are created in the R/3 delta queue is there some kind of sequence number that is passed to the BI side to tell BI in what order to process them?
The additional complication to the this whole problem is that the 10, 20, and 30 records are all being created and deleted in R/3 on the same day. So, BI see a 10, 20 create, then a 30 create and then a 20 delete all in the same days processing.
Regards,
Mike...

LIS reports in BI

Hi,
Are there any LIS reports in the PP/MM/WM area which can be developed and run in BI ? My client wants to start expanding the use of BI. Is it even possible to move LIS reports to BI and if yes which ones would be moved first ?
Thanks
GS

Hi GS:
I suppose you're working with LIS on the R/3 side and your customer is planning to move to the "new" Logistics Cockpit Available for BW-BI. For starters I reccommend you to take a look at the excelent logistics blogs series provided by Roberto Negro. (Not to mention there's an excelent discussion about the differences and pros/cons related to LIS and Logistics Cockpit Extractors).
LOGISTIC COCKPIT: a new deal overshadowed by the old-fashioned LIS ?
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
After that you can continue with some more details on the links below:
SAP BW and Business Content Datasources: in pursuit of the origins
/people/sap.user72/blog/2005/09/05/sap-bw-and-business-content-datasources-in-pursuit-of-the-origins
LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it !
/people/sap.user72/blog/2005/02/14/logistic-cockpitwhen-you-need-morefirst-option-enhance-it
LOGISTIC COCKPIT DELTA MECHANISM - Episode one: V3 Update, the u2018serializeru2019
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
Regards,
Francisco Milán.

2lis_18* service orders/notification

I need to extract service orders and notification data and Im thinking of useing the 2lis_18* logical cockpit extractors but I cant find any documentation on them. Can anyone point me in the right direction to find the documentation on these or know of any white papers that covers these extractors as well as business content within BW for service orders/notification
thanks

You can search in help.sap.. you will get the relevant information...
CHk this links...
http://help.sap.com/saphelp_nw70/helpdata/en/f0/f61c3b83e6236de10000000a11402f/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/a7/fb0d3dbd82f72ce10000000a114084/content.htm

Why do we use Unserialized V3 update for Inventory Management?

Hello Experts,
I have question on LO Cockpit extractor.
Why do we use Unserialized V3 update for Inventory Management (2LIS_03_BF) ?
Are there any reasons behind?
thanks a lot
Padma

Hi,
V3 gives you good performance and you use it when the order of data is not important they way it was posted in OLTP, this method is used.
Cheers,
Kedar

Repeat delta are failing

Hello experts,
I have an imp production issue. We had delta failing in one of LO Cockpit extractor for last 4 days.
Message: Error occurred in the data selection
Job terminated in source system --> Request set to red
Message no. RSM078
I did repeat delta (by changing status to red and deleting requests). But still I get same message.
Please help.
Rita.

SM 37 LOG:
Job started
Step 001 started (program SBIE0001, variant &0000000017045, user ID ALEREMO
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 2LIS_18_I0NOTIF
RLOGSYS    = PRODCLNT200
REQUNR     = REQU_D4VWYY4JTTY9ODFHL16WPLR5M
UPDMODE    = R
LANGUAGES = *
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 0                                       *
abap/heap_area_total.......... 8588886016                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... 123ACEFIJKLMNOPSUVc                     *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 1,491 records
Result of customer enhancement: 1,491 records
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 1,491 records
ABAP/4 processor: COMPUTE_INT_TIMES_OVERFLOW
Job cancelled

Oli*bw transactions for sd,mm,pur,

Hi,
can anybody tell me the various oli*bw transactions to fill setup tables
and pls explain the difference between when we are going to fill setup tables of sd by oli7bw and when gponig through sbiw wat is the difference and wat to enter in the information structure field pls let me know
points promised

Hi Rubane
If you are referring to LO cockpit extractors (ex. 2LIS_11_VAITM, 2LIS_12_VCITM) then there is no difference.
For SD Sales orders tcode is OLI7BW
SBIW PATH is tcode SBIW->Business Information Warehouse->Settings for Application-Specific DataSources->Logistics->Managing Extract Structures->Initialization->Filling in the Setup Table->Application-Specific Setup of Statistical Data->Perform Setup - SD Sales Orders
Check both these in your R/3 system and you will find there is no difference.
When you are mentioning about "we need to give the information structure name" then you are talking about LIS extractors and not LO cockpit extractors.
Please note that LIS extractors are now obsolete and are replaced by LO cockpit extractors.
Hope it helps.
Regards
Pradip

Process keys

Hi gurus
i need the process keys related to issues and receipts for the below mentioned stocks
I also need to stock types and the stock categories for the same.
I can get the process keys data in SBIW, but i am unable to find the exact keys related to the below stocks.
The below fields are from MARD table
LABST - Unrestricted
UMLME - Stock in Transfer
EINME - Restricted Use
SPEME - Blocked
RETME - Return
Please help me...
Thanks & Regards
Seshu

Hi Bhima,
look at OSS Note 353042 'How to Activate transaction key PROCESSKEY'...
However, Logistic Cockpit extractors represent, in principle, structures that collect document-specific information from the logistics application and transfer it to the SAP BW.
Many key figures are yielded from the application. These must be transferred to the SAP BW with the help of the extractors. SAP ensures that document information is interpreted in advance with the help of a 'process key' so that key figures, which describe and measure the particular processes, can be more easily derived for customers.
In the 2LIS_02_SCL, for example, this means that the rows to be transferred only contain transfer quantities and value fields. The actual key figure is hidden behind the process key. There are generic key figures (transfer quantities and transfer values) that have a significance when combined with the process keys.
Process keys must, during the update, be resolved into corresponding key figures at the time of query creation at the latest, you must have a precise knowledge of the process keys for the creation of customer-specific infocube updates or the creation of the query.
Example: Update routine for the key figure 'Order Volume Quantity (External Vendor)'(pseudo-coding):
IF COMM_STRUCTURE-PROCESSKEY = `001`.
RESULT = COMM_STRUCTURE-TRANS_AMOUNT.
ELSE.
CLEAR RESULT. no update of key-figure
ENDIF.
Look at MCB0 transaction !!!
Hope it helps!
(Bhima, don't forget to reward the answers !!!)
Bye,
Roberto

Datasource 2LIS_01_S260 / 1 / 2 / 3

Hi all,
I'm using BI 7.0 my source system is SAP ECC 6.0 SR2
I'm going to use Sales: Overview cube (0SD_C03) but under this cube we have these datasource: 2LIS_01_S260, 2LIS_01_S261, 2LIS_01_S262, 2LIS_01_S263.
but we can not see it in source system side (trans RSA5 in source system side). then the infopackage didn't work.
I want to know:
1. do I need these datasource?
2. if yes, then how can I have these data source in Source system side?
Regards,
Chuong Hoang

Hi Chuong,
Follow these threads on Standard LO extractors,
Re: types of extractors used in LO'S
LIS info structures and their LO standard Extractors.
Re: Where should i find the LO-Cockpit Extractors.
Thanks

Advantages of Lo cockpit extractors

Similar Messages

Maybe you are looking for