Thursday, July 31, 2008

LO-COCKPIT extraction


The first and the most important extraction method. LO-COCKPIT

Positioning of LO-COCKPIT:



What is Logistics Cockpit?
We can say that it’s a new technique to extract logistics information and consists of a series of a standard extract structures (that is, from a more BW perspective, standard datasources), delivered in the business content.

Mind you that, the navigation part will no be discussed here but only the theory part which is required for understanding LO extraction process. The navigation steps will be mentioned in brief.

Here we start...........

Data Extraction is the process of loading data from OLTP to OLAP (BW/BI). Here is an illustration...

I have a company, in which daily thousands of transactions happen all over the world. So to analyze my business on yearly or monthly basis, i am moving to SAP BW/BI, so that i can generate reports and take business decisions.

Tomorrow i am going to load all the data which was captured till yesterday, from SAP R/3 to BW/BI. I do a full load for this. After completing this task, i need to load the transactions that will happen from tomorrow to BW. This can be done either daily or weekly or monthy based on the volume of transactions.
If there are 1000s of transactions per day, i can use daily load, 10000s - weekly, if in lakhs- monthly.

So, in precise, data has to be extracted in two modes:

1. Full load - Entire data which is available at source is loaded to BW/BI
2. Delta load - Only the new/changed/deleted data is loaded.


Full Load Data FLow:
Let us see, how the data is loaded to BW in Full mode.

























Here we need to understand few basic things which happen on R/3 side.

Document Posting means creating a transaction, writing into the application/transaction tables.
So whenever sales order is created ( document posted), it transaction is written into the database tables/application tables/transaction tables (Ex. EKPO, EKKO, VBAK, VBAP)

Whenever you are doing a full load, setup tables are used.

setup tables:

Access to application tables are not permitted, hence setup tables are there to collect the required data from the application tables.


When a load fails, you can re-run the load to pull the data from setup tables. Data will be there in setup tables. Setup tables are used to Initialize delta loads and for full load. Its part of LO Extraction scenario.

With this option, you avoid pulling from R/3 directly as we need to bring field values from multiple tables. You can see the data in the setup tables.Setup table table name wiil be extract structure name followed by SETUP. Set up table names starts with 'MC' followed by application component '01'/'02' etc and then last digits of the datasource name and then followed by SETUP
Also we can say the communication structure (R/3 side,you can check it in LBWE also) name followed by 'setup'

example: MC13VD0HDRSETUP
  • If you want to check data in set up tables you better look at the transaction NPRT here you can see the table name from which data is picking.
  • Setup tables are cluster tables and are used to extract the data from R/3 Tables.(LO Extractors)
  • Basically, for entire application like SD-Billing we have got it's own setup Tables...so while filling the set-up tables, we usually fill for the entire application.
Ex: OLI7BW is for filling setup Tables for SD application.
OLI9BW T-code is for Billing Application,
  • When u fill the setup Tables, the data from different tables..VBAK, VBAP, VBRK, VBRP...etc will come through communication Structures and saved in SetupTables...
  • The main advantage of having setup Tables is, we can read the data in different levels..Header level as well as Item level.
  • when we run init load or Full load in BW, the data will be read from Setup Tables for the first time( Entire data will be read).... and the delta records will be updated to Delta Queue once the v3 job runs... and we can extract the delta records from Delta Queue.
  • once we succefully run the init, we can delete setup Tables.
  • Filling up the set up tables depends on the datasource.
There are different T-codes for the respective extract structures

OLIIBW transaction PM data
OLI1BW INVCO Stat. Setup: Material Movemts
OLI2BW INVCO Stat. Setup: Stor. Loc. Stocks
OLI3BW Reorg.PURCHIS BW Extract Structures
OLI4BW Reorg. PPIS Extract Structures
OLI7BW Reorg. of VIS Extr. Struct.: Order
OLI8BW Reorg. VIS Extr. Str.: Delivery
OLI9BW Reorg. VIS Extr. Str.: Invoices
OLIABW Setup: BW agency business
OLIFBW Reorg. Rep. Manuf. Extr. Structs
OLIIBW Reorg. of PM Info System for BW
OLIQBW QM Infosystem Reorganization for BW
OLISBW Reorg. of CS Info System for BW
OLIZBW INVCO Setup: Invoice Verification
OLI7BW is the tcode for Sales Order.

Steps for full load:

*************** This will be updated later - the navigation part*********************


Delta Load:

As a prerequisite we need to discuss various update methods for delta load.

  1. Serialized V3
  2. Queued Delta
  3. Direct Delta
  4. Unserialized V3
Before that we need to understand V1, V2, V3 updates. These are different work processes on the application server that makes the update LUW from the running program and execute it. These is separated to optimize the transaction processing capabilities.

These are different work processes on the application server that makes the update LUW from the running program and execute it. These is separated to optimize the transaction processing capabilities.

For Example :
If you create/change a purchase order (me21n/me22n), when you press 'SAVE' and see a success message (PO.... changed..), the update to underlying tables EKKO/EKPO has happened (before you saw the message). This update was executed in the V1 work process.

There are some statistics collecting tables in the system which can capture data for reporting. For example, LIS table S012 stores purchasing data (it is the same data as EKKO/EKPO stored redundantly, but in a different structure to optimize reporting). Now, these tables are updated with the transaction you just posted, in a V2 process. Depending on system load, this may happen a few seconds later (after you saw the success message). You can see V1/V2/V3 queues in SM12 or SM13.

Statistical tables are for reporting on R/3 while update tables are for BW extraction. And is data stored redundantly in these two (three if you include application tables) sets of table.
Difference is the fact that update tables are temporary, V3 jobs continually refreshes these tables (as I understand). This is different from statistics tables which continue to add all the data. Update tables can be thought of as a staging place on R/3 from where data is consolidated into packages and sent to the delta queue (by the V3 job).

Update tables can be bypassed (if you use 'direct' or 'queued' delta instead of V3) to send the updates (data) directly to the BW queue (delta queue). V3 is however better for performance and so it is an option along with others and it uses update tables.

Statistical table existed since pre BW era (for analytical reporting) and have continued and are in use when customers want their reporting on R/3.

The structure of statistical table might be different from the update table/BW queue, so, even though it is based on same data, these might be different subsets of the same superset.
V3 collective update means that the updates are going to be processed only when the V3 job has run.

At the time of oltp transaction, the update entry is made to the update table. Once you have posted the txn, it is available in the update table and is waiting for the V3 job to run. When V3 job runs, it picks up these entries from update table and pushes into delta queue from where BW extraction job extracts it.

  • Synchronous update (V1 update): Statistics update is carried out at the same time (synchronous) as the document update (in the application tables).
  • Asynchronous update (V2 update): Document update and the statistics update take place in different tasks.
So, V1 and V2 updates don’t require any scheduling activity.
  • Collective update (V3 update):As for the previous point (V2), document update is managed in a separate moment from the statistics update one, but, unlike the V2 update, the V3 collective update must be scheduled as a job (via LBWE).
Remember that the V3 update only processes the update data that is successfully processed with the V2 update.

-------------------------------------------------------------------------------------
Serialized V3:

Take an example of the same PO item changing many times in quick succession.
V1 (with enqueue mechanism) ensures that the OLTP tables are updated consistently. Update table gets these update records which may or may not end up in correct sequence (as there is no locking) when it reaches BW. 'Serialized V3' was to ensure this correct sequence of update records going from update tables to delta queue (and then to BW).

Since update table records have the timestamp, when the V3 job runs, it can sequence these records correctly and thus achieve 'serialization'.

The problems in Serialized V3 update are:
  • Several changes in one second: For technical reasons, collective run updates that are generated in the same second cannot be serialized. That is, the serialized V3 update can only guarantee the correct sequence of extraction data in a document if the document did not change twice in one second.
  • Different instances and times synchronization: I think it’s easy to verify how much it is probable that in a landscape in which there are several application servers for the same environment different times can be displayed.The time used for the sort order in our BW extractions is taken from the R/3 kernel which uses the operating system clock as a time stamp. But, as experience teaches, in general, the clocks on different machines differ and are not exactly synchronized.The conclusion is that the serialized V3 update can only ensure the correct sequence in the extraction of a document if the times have been synchronized exactly on all system instances, so that the time of the update record (determined from the locale time of the application server) is the same in sorting the update data.

  • The V2 update dependence: Not to be pitiless, but the serialized V3 update have also the fault of depending from the V2 processing successful conclusion.Our method can actually only ensure that the extraction data of a document is in the correct sequence (serialized) if no error occurs beforehand in the V2 update, since the V3 update only processes update data for which the V2 update is successfully processed.Independently of the serialization, it’s clear that update errors occurred in the V2 update of a transaction and which cannot be reposted, cause that the V3 updates for the transaction that are still open can never be processed.This could thus lead to serious inconsistencies in the data in the BW system.














Example:

Take a case where the first update (based on earliest timestamp) to be processed is in language EN (for same PO item). V3 job is then going to process all the update records of language EN in chronological sequence before going to next language records. If another language update (for same PO item) happened in between two EN language updates, this is going to be processed later after all EN updates are processed and thus become out of sequence.















In the above figure, all the documents in red color (EN language) will be processed first and later blue colored (IT language), which is an inconsistancy in sequence.


Direct Delta ( 2nd delta update method in our list)

With this update mode,
  • Each document posting is directly transferred into the BW delta queue
  • Each document posting with delta extraction leads to exactly one LUW in the respective BW delta queues
Just to remember that ‘LUW’ stands for Logical Unit of Work and it can be considered as an inseparable sequence of database operations that ends with a database commit (or a roll-back if an error occurs).

Benifits:
  • There’s no need to schedule a job at regular intervals (through LBWE “Job control”) in order to transfer the data to the BW delta queues; thus, additional monitoring of update data or extraction queue is not required.
  • Logically, restrictions and problems described in relation to the "Serialized V3 update" and its collective run do not apply to this method: by writing in the delta queue within the V1 update process, the serialization of documents is ensured by using the enqueue concept for applications and, above all, extraction is independent of V2 update result.
Limits:
  • The number of LUWs per datasource in the BW delta queues increases significantly because different document changes are not summarized into one LUW in the BW delta queues (as was previously for V3 update).Therefore this update method is recommended only for customers with a low occurrence of documents (a maximum of 10000 document changes - creating, changing or deleting - between two delta extractions) for the relevant application. Otherwise, a larger number of LUWs can cause dumps during extraction process.
  • No documents can be posted during delta initialization procedure from the start of the recompilation run in R/3 (setup tables filling job) until all records have been successfully updated in BW: every document posted in the meantime is irrecoverably lost.
  • V1 update would be too much heavily burdened by this process.
(Remember that stopping the posting of documents always applies to the entire client).


------------------------------------------------------------------------------------------

Queued Delta ( the third update method)

With queued delta update mode, the extraction data (for the relevant application) is written in an extraction queue (instead of in the update data as in V3) and can be transferred to the BW delta queues by an update collective run, as previously executed during the V3 update.
After activating this method, up to 10000 document delta/changes to one LUW are cumulated per datasource in the BW delta queues.

If you use this method, it will be necessary to schedule a job to regularly transfer the data to the BW delta queues

As always, the simplest way to perform scheduling is via the "Job control" function in LBWE.
SAP recommends to schedule this job hourly during normal operation after successful delta initialization, but there is no fixed rule: it depends from peculiarity of every specific situation (business volume, reporting needs and so on).

Benifits:

  • When you need to perform a delta initialization in the OLTP, thanks to the logic of this method, the document postings (relevant for the involved application) can be opened again as soon as the execution of the recompilation run (or runs, if several and running in parallel) ends, that is when setup tables are filled, and a delta init request is posted in BW, because the system is able to collect new document data during the delta init uploading too (with a deeply felt recommendation: remember to avoid update collective run before all delta init requests have been successfully updated in your BW!).
  • By writing in the extraction queue within the V1 update process (that is more burdened than by using V3), the serialization is ensured by using the enqueue concept, but collective run clearly performs better than the serialized V3 and especially slowing-down due to documents posted in multiple languages does not apply in this method.
  • On the contrary of direct delta, this process is especially recommended for customers with a high occurrence of documents (more than 10,000 document changes - creation, change or deletion - performed each day for the application in question.
  • In contrast to the V3 collective run (see OSS Note 409239 ‘Automatically trigger BW loads upon end of V3 updates’ in which this scenario is described), an event handling is possible here, because a definite end for the collective run is identifiable: in fact, when the collective run for an application ends, an event (&MCEX_nn, where nn is the number of the application) is automatically triggered and, thus, it can be used to start a subsequent job.
  • Extraction is independent of V2 update.
Limits:
  • V1 is more heavily burdened compared to V3.
  • Administrative overhead of extraction queue.
Note:
  1. if you want to take a look to the data of all extract structures queues in Logistic Cockpit, use transaction LBWQ or "Log queue overview" function in LBWE (but here you can see only the queues currently containing extraction data).
  2. In the posting-free phase before a new init run in OLTP, you should always execute (as with the old V3) the update collective run once to make sure to empty the extraction queue from any old delta records (especially if you are already using the extractor) that, otherwise, can cause serious inconsistencies in your data.
  3. Then, if you want to do some change (through LBWE or RSA6) to the extract structures of an application (for which you selected this update method), you have to be absolutely sure that no data is in the extraction queue before executing these changes in the affected systems (and especially before importing these changes in production environment !).
    To perform a check when the V3 update is already in use, you can run in the target system the RMCSBWCC check report.


--------------------------------------------------------------------------------------
Unserialized V3 : (The last one)

With this update mode, that we can consider as the serializer’s brother, the extraction data continues to be written to the update tables using a V3 update module and then is read and processed by a collective update run (through LBWE).
But, as the name of this method suggests, the V3 unserialized delta disowns the main characteristic of his brother: data is read in the update collective run without taking the sequence into account and then transferred to the BW delta queues.

Issues:

  • Only suitable for data target design for which correct sequence of changes is not important e.g. Material Movements
  • V2 update has to be successful
When this method can be used ?

Only if it’s irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence (serialization) in which the data was generated in R/3 (thanks to a specific design of data targets in BW and/or because functional data flow doesn’t require a correct temporal sequence).




Here ends the update methods.

************************************************************

Some important points :

  • The setup tables are the base tables for the Datasource used for Full upload.So if you are going for only full uploadfull update is possible in LO extractors.
  • Full update is possible in LO extractors.In the full update whatever data is present in the setup tables(from the last done init) is sent to BW.
  • But setup tables do not receive the delta data from the deltas done after the init.So if ur full update should get ALL data from the source system,u will need to delete and re-fill setup tables.
**************************************************************
Some Questions:

Question:
The serialized V3 update can guarantee the correct sequence for the extraction data of a document only if there were no errors in the V2 update. This is because the V3 update only processes update data for which a V2 update has be carried out successfully.
Why is V3 dependent on V2, what is V2 and V1 update?

Answer:
V1 - Synchronous update

V2 - Asynchronous update

V3 - Batch asynchronous update

These are different work processes on the application server that takes the update LUW (which may have various DB manipulation SQLs) from the running program and execute it. These are separated to optimize transaction processing capabilities.

Taking an example -
If you create/change a purchase order (me21n/me22n), when you press 'SAVE' and see a success message (PO.... changed..), the update to underlying tables EKKO/EKPO has happened (before you saw the message). This update was executed in the V1 work process.

There are some statistics collecting tables in the system which can capture data for reporting. For example, LIS table S012 stores purchasing data (it is the same data as EKKO/EKPO stored redundantly, but in a different structure to optimize reporting). Now, these tables are updated with the txn you just posted, in a V2 process. Depending on system load, this may happen a few seconds later (after you saw the success message). You can see V1/V2/V3 queues in SM12 or SM13.

V3 is specifically for BW extraction. The update LUW for these is sent to V3 but is not executed immediately. You have to schedule a job (eg in LBWE definitions) to process these. This is again to optimize performance.

V2 and V3 are separated from V1 as these are not as realtime critical (updating statistical data). If all these updates were put together in one LUW, system performance (concurrency, locking etc) would be impacted.

Serialized V3 update is called after V2 has happened (this is how the code running these updates is written) so if you have both V2 and V3 updates from a txn, if V2 fails or is waiting, V3 will not happen yet.

BTW, 'serialized' V3 is discontinued now, in later releases of PI you will have only unserialized V3.
--------------------------------------------------------------------
Question:

There are following tables
1. Application tables (R/3 tables)
2. Statistical tables (for reporting purpose)
3. update tables
4. BW queue

For Application tables its V1 update, statistical tables its V2 update and is it that the same information is again redundantly stored in update tables?

How are statistical tables different from update tables? I mean i understood what statistical tables are, my question is "Is the same information again redundantly stored in update tables for Collective V3 update to pull the records to BW Queue".

I mean is V3 collective update same as Synchronous V3 update? How does the records get saved in update tables?

Answer:

Statistical tables are for reporting on R/3 while update tables are for BW extraction. Is data stored redundantly in these two (three if you include application tables) sets of table?, yes it is.
Difference is the fact that update tables are temporary, V3 jobs continually refresh these tables (as I understand). This is different from statistics tables which continue to add all the data. Update tables can be thought of as a staging place on R/3 from where data is consolidated into packages and sent to the delta queue (by the V3 job).

Update tables can be bypassed (if you use 'direct' or 'queued' delta instead of V3) to send the updates (data) directly to the BW queue (delta queue). V3 is however better for performance and so it is an option alongwith others and it uses update tables.

Statistical table existed since pre BW era (for analytical reporting) and have continued and are in use when customers want their reporting on R/3.

The structure of statistical table might be different from the update table/BW queue, so, even though it is based on same data, these might be different subsets of the same superset.

V3 collective update means that the updates are going to be processed only when the V3 job has run. I am not sure about 'synchronous V3'. Do you mean serialized V3?

At the time of oltp transaction, the update entry is made to the update table. Once you have posted the txn, it is available in the update table and is waiting for the V3 job to run. When V3 job runs, it picks up these entries from update table and pushes into delta queue from where BW extraction job extracts it.
-----------------------------------------------------------------------------------
Question:

what do you mean by serialization?is it the serialization beween sequence of records in update tables to the sequence in BW Queue?
and
Can you explain little more about the Collective run performance with different languages.

Answer:

The requirement in 'delta' capturing on R/3 side is to be able to capture the delta 'exactly once in order'.

Take an example of the same PO item changing many times in quick succession.

V1 (with enqueue mechanism) ensures that the OLTP tables are updated consistently. Update table gets these update records which may or may not end up in correct sequence (as there is no locking) when it reaches BW. 'Serialized V3' was to ensure this correct sequence of update records going from update tables to delta queue (and then to BW).

Since update table records have the timestamp, when the V3 job runs, it can sequence these records correctly and thus achieve 'serialization'. However, there is a technical problem with this. The timestamp recorded in update record is sent by the application server (where user executed the txn) and if there are multiple app servers there might be some inconsistency in their system time which can cause incorrect serialization.

Another problem is in the fundamental design of the V3 process. V3 Job sequences the updates on timestamp, and then processes the update records from update table (to send it to delta queue), but it does so for one language at a time (update record also has user logon language stored). Why this is done is not clear to me, but it is a basic design feature and can not be subverted.

This causes a potential issue if multiple logon languages are used by users. Serialization may not happen correctly in such a case. Take a case where the first update (based on earliest timestamp) to be processed is in language EN (for same PO item). V3 job is then going to process all the update records of language EN in chronological sequence before going to next language records. If another language update (for same PO item) happened in between two EN language updates, this is going to be processed later after all EN updates are processed and thus become out of sequence. The weblog mentions this scenario.

These two constraints remain for 'serialized V3' where 'serialization' couldn't be truly achieved. Hence newer PIs have discarded 'serialized V3' altogether and now you do not have this option (if you are using a newer PI).

If you use 'serialized V3', you have to be clear that the 'serialization' may not always work in the above two scenarios (multi language environment, and multiple app servers or updates to same records in same second(as timestamp has granularity upto second level only)).

***************************************************************************

Now we will discuss about the functions of LO-COCKPIT:
  • Maintain Extract Strucutres: Here you can add additional fields from the communication structures available to the extract structure.
  • Maintain Data Sources: In the Data source maintenance screen, you can customize the data source by using the following fields: field name, short text, selection, hide field, inversion or cancellation field or reverse posting, and field only known in customer exit.
  • Activating update: By Setting as active, data is written into extract structures both online as well as during completion of setup tables or restructure table or LO initialization tables. Depending on the update mode a job has to be scheduled with which the updated data is transferred in the background into the central delta management (Delta Queue).
  • Controlling update:This talks about the delta update mode you are using and how do you control the data load based on the volume of data. LO Cockpit supports 4 types of update modes ( delta modes, which we have already discussed):Serialized V3 update,Direct Delta,Queued Delta,Unserialized V3 update.
***************************************************************************

With this the theory what ever is required for LO-COCKPIT ends here. If you need navigation steps, please give comments.

To download Ebook version of the above content, click here.

123 comments:

Unknown said...

Hi Sateesh,
I liked the documentation of LO extraction. When can we expect the step by step process in the Blog?

Regards,
David

sateesh bandi said...

Hi David,

Thanks for the feedback.
Do you want the step by step navigation of LO?

-Sateesh

Unknown said...

Hi,

I need step by step navigation of LO.

Pavanl

Unknown said...

Hi Sateesh,

Your documentation is excellent.
Please add LO Navigation also to this blog.

Thanks & Regards,

Jareena

Unknown said...

great job sateesh....

Unknown said...

Hi,
I liked the documentation of LO extraction.
Can u tell me, What is batch data in lo- Extraction.

Unknown said...

Hi Sateesh,

thanks for this excellent document , its cleared my all the doubt.

Unknown said...

Hi Satessh,

I like the documentation of LO Extraction, it's excellent one.

Regards,
Rafi

Rahm said...

Its is the best document,I have read so far,regarding LO extraction.It clarifies a lot of doubt.
Thanks Sateesh.

sateesh bandi said...

I thank all of you, for your feedback. I am out of this SAP BW as of now. But, for you all, i will provide the step by step navigation of LO soon.

After a long long time i checked this blog. Sorry for not respsonding soon.

Sharanya said...

Hi Sateesh,
Thanks for all the valuable information on LO extraction, it sure has cleared lot of doubts i had.
Excellent documentation !

Regards,
Sharanya.

sateesh bandi said...

Hi,

I am in the process of preparing the navigation part of LO COCKPIT. Please wait for some more days.

Thanks for all your comments.

Sateesh

Unknown said...

Hi Sateesh,

The Document is sooo nice.It has cleared soo many theoritical doubts i have.This doc really rocks...... We are all looking for the next blast.....

Kiran said...

Hi Satheesh

Thanks for the Document... Its very Good..

Unknown said...

Document is excellent and too good.

Thanks and keep write the good blogs.

C'est LazziMic said...
This comment has been removed by the author.
Unknown said...

hi,
i liked his documentation of lo extraction , it's clear all my doubt s

Unknown said...

hi satheesh the doc is vey good i liked the way it is presented

Unknown said...

Hi sateesh,

very easy to understand.It helped me a lot.If u share some more topics on Aggregates,that will be great.

regards,
Britney

KamalapuriSubha said...

Hi Sateesh,

good job Sateesh...

We are eagerly waiting for Step by step (navigation part of LO COCKPIT)...

Unknown said...

Hi Sateesh,

Thanks for the wonderfull document. I dont think no one has ever written such a clear and step by step process for LO extractions.
WOnderfull job. Thanks

Regards,
Liju

Unknown said...

Hai sathesh
its is really awesome, actually am searching from long time for this information.Thank u so much.

Unknown said...

Thanks for all the valuable information on LO extraction

sangetha said...

Hi this post is very nice....
Fabulous document...

Extractors

Kavyanjali said...

Thanks for the document....
It very useful to all....

Felix said...

Excellent SAP Guru!

Felix said...

Excellent SAP Guru! Do you have similar thing for FI

Manish said...

Hi sateesh,
Indeed it shown your very clear understanding....to me!!
Thanks a lot bro !!
Regards Manish...

srinivas k said...
This comment has been removed by the author.
Shazee said...

Hi Sateesh,

You done a great job by posting this document. I saw so many documents about LO but this is one is awesome.

Thanks for your post.

KRRISHNA said...

Hi Sateesh,

I like the content you provided for us.It is very helpful the People who are aspiring to learn SAP BI.
It would be great help if you provide Lo Navigation Step in detail.

Thanks,
Krishna Porandla

KRRISHNA said...

it was to great tutorail for begginer like me.It would be great help if provide LO Navigation steps in detail.


Thanks,
Krishna Porandla

yaseen said...

hii..sateesh

really great job

can u give me the step by step

Nari said...

Sateesh, Thanks for your Blog.
Really Cool and Clear Stuff...Waiting for your latest Release....

bobby said...

Hi Sateesh Garu..
i am expecting your from Andhra..

me document chala chala superb inka meru elane chala post cheayali ani koruthunnam..
inka velite infopackage level lo full load /init load kuda konchem explain cheayandi pls

From
santosh

anbu said...

hi sateesh ,
u have done a wonderful job ur doc is very clear and easy to understand once again thank u
do u know anything about BO if so u can help me pls

anupama said...

Hi Sateesh,
I liked u'r lo extraction documentation, it was great, easily understandable.can i get the step by step process.
Thanks & Regards,
Anupama.

Manish said...

hi satish ur post was damn good but can u please help me out in routines concept. Could you please explain how and when to write a routine.

gangadhar said...

nice

Unknown said...

hi sateesh,

This is really nice piece of work...thank you so much for doing this
It would be great if we get chance to view more documents like this on different topics from you.


Regards,
Rupali

Anonymous said...

Good Job Bro....
I like the person like u who share their knowledge....Good Work ...keep it up

Nani said...

Hi

u have done a great job....
If u dont mind can u plzz post the documentation for generic delta also.

thanks
Nani

Unknown said...
This comment has been removed by the author.
Unknown said...

HI I WANT LO-EXTRACTION NAVIGATION STEP BY STEP PROCESS

Syed Minaz said...
This comment has been removed by the author.
Syed Minaz said...

Excellent Explanation.Very clearly explained the concepts of Update.

venki54 said...

Hi bandi,
nice explanation.
actually i am looking for navigational steps for Lo extraction in BI, hope you will help me.
thanks in advance bandi.
with Regards,
venki
venkatonline54@gmail.com

Unknown said...

Hi Sateesh,

Very useful document.

Thanks
Chandra

Unknown said...

Hi Satish,
Very useful document and one can understand it very easily.....Thanks once again dude.

Unknown said...

Thanks for clear explanation...!!!

CoolDip said...

Hi,

Excellent blog, I not only refreshed my concepts Learned new things also...

A very good write-up. Please keep drafting other topics of SAP BI as well...

Regards,
Kuldeep

Unknown said...

Hi..i am shobhan thanks for your clear Explanation..

ravi said...

hi,
I am new to SAP bw , need to now the difference why un-serialized update is dependent on v2 update and this is not the case with queued delta?

Is it like in queue delta statistic update v2 will not be happened?

Unknown said...

very nice article.Thanks for sharing the post...!
Training

Unknown said...

Training

Unknown said...

Good article, thanks for the information. We also provide SAP BW online training. Go to Tekslate for indepth SAP BW training.

Unknown said...

I am very greatful to you that you share very informative post with us...
SAP MM Online Training | SAP SD Online Training

Unknown said...

Thanks for sharing this document.it cleared my all doubts about lo extraction.

Unknown said...

Thanks for sharing this document.it cleared my all doubts about lo extraction.

Pauline BPO Solutions said...

data extraction services are available

Test My internet Speed said...

Your Blog was Superb. thank you for sharing.
SAP BW training institutes in Noida

Unknown said...

It's A Great Pleasure reading your Article, learned a lot of new things, we have to keep on updating it Learn Tibco Online Thanks for posting.

Unknown said...


Its really nice and informative.. Thanks for sharing

Best Web Design Training Institutes in Noida

Best Hadoop Training Institutes In Noida

Best Digital Marketing Training Institute in Noida

Sap Training Institute in Noida

Best Java Training Institute in Noida

SAP SD Training Institute in Noida

Best Auto CAD Training Institute In Noida

jyothi kits said...

I am waiting for your more posts like this or related to any other informative topic.
Python Interview Questions and Answers
QlikView Interview Questions and Answers

jameswill11 said...

An additional common issues are: facing problem while upgrading QuickBooks Customer Support Number to the newest version. There could be trouble while taking backup within your data, you could not be able to open your organization file on multi-user mode.

QuickBooks Payroll Support said...

QuickBooks is an accounting software program generated by Intuit. In QuickBooks Payroll Tech Support Number, can help you all the billing, bookkeeping, and invoicing at one place. You can track sales and expenses, accept payments etc. This accounting software has scores of consumer over the world just because of their smart products and versions.

jameswill11 said...

QuickBooks Customer Support Number software package is developed this kind of a fashion that it will give you the most effective account management mention of this era. However, you can face the issue along with your QuickBooks software and begin trying to find the solution.

kevin32 said...

The QuickBooks Enterprise Tech Support Number industry specific versions add cherry regarding the cake. For such adaptive accounting software, it really is totally acceptable to throw some issues at some instances.

accountingwizards said...

We possess the most customer friendly tech support team team made to provide you with the most wonderful technical assistance in QuickBooks Online. Simply call QuickBooks Support Number; we assure you the complete satisfaction by providing you the worth of each single penny.

kevin32 said...

QuickBooks software package is developed this kind of a manner that it will give you the greatest account management reference to this era. However, you could face the problem with your QuickBooks Support Phone Number software and begin looking for the solution.

xpert said...

Consist of a beautiful bunch of accounting versions, viz., QuickBooks Pro, QuickBooks Premier, QuickBooks Enterprise, QuickBooks POS, QuickBooks Mac, QuickBooks Windows, and QuickBooks Payroll, QuickBooks has grown to become a dependable accounting software that one may tailor depending on your industry prerequisite. As well as it, our QuickBooks Support Phone Number will bring in dedicated and diligent back-end helps for you for in case you find any inconveniences in operating any of these versions.

Mathew said...


Probably one of the most trustworthy software to help us call at immediate past may be the wondrous application of QuickBooks Customer Support Number. Running a business, it offers revolutionized our banking and changed the messy way we do finances. However, probably the best software often faces many errors during its functioning.

Mathew said...


Probably one of the most trustworthy software to help us call at immediate past may be the wondrous application of QuickBooks Customer Support Number. Running a business, it offers revolutionized our banking and changed the messy way we do finances. However, probably the best software often faces many errors during its functioning.

steffan said...

Are you scratching the pinnacle and stuck along with your QuickBooks related issues, you are just one click definately not QuickBooks Help & Support for your QuickBooks related issues. We site name, are leading tech support team provider for your entire QuickBooks related issues.

kevin32 said...

Let’s update you aided by the proven fact that this matter is immensely faced by our customers. Do not worry most likely and e-mail us at our QuickBooks Phone Support Number.

kevin32 said...

Our experts team at QuickBooks Payroll Tech Support Number is going to make you understand its advanced functions and assists someone to lift up your business growth.

jameswill11 said...

QuickBooks Desktop installation file that has QuickBooks’ license information. The license information should be retrieved each time, the QuickBooks Desktop is created active. QuickBooks Error 3371 Desktop will likely not open if the file is damaged.

jameswill11 said...

QuickBooks Payroll Support Phone Number has emerged one of the better accounting software that has had changed this is of payroll. Quickbooks Payroll Support contact number will be the team that provide you Quickbooks Payroll Support. This software of QuickBooks comes with various versions and sub versions.

Jamess said...

QuickBooks Enterprise Support contact number is assisted by an organization this is certainly totally dependable. It is a favorite proven fact that QuickBooks Enterprise Support Phone Number has had about plenty of improvement in the area of accounting.

jameswill11 said...

QuickBooks Payroll Support Phone Number has emerged one of the better accounting software that has had changed this is of payroll. Quickbooks Payroll Support contact number will be the team that provide you Quickbooks Payroll Support.

kevin32 said...

QuickBooks Payroll Support Phone Number can either perform payment processing in desktop or cloud, both ways are only just a little different but provde the same results.

accountingwizards said...

QuickBooks, an application solution which is designed in such a way as you are able to manage payroll, inventory, sales and every other need of a small company. Each QuickBooks software option would be developed according to different industries and their needs to be able to seamlessly manage all of your business finance at any time as well as in one go. You should not worry if you should be stuck with QuickBooks issue in midnight as our technical specialists at QuickBooks Technical Support Number can be obtained round the clock to serve you using the best optimal solution right away.

kevin32 said...

all at one place. Are QuickBooks Enterprise Tech Support Number errors troubling you? Are you currently completely fed up with freezing of QuickBooks? If yes, afterward you have browsed off off to the right place.

steffan said...


QuickBooks Enterprise Support Number assists anyone to overcome all bugs from the enterprise forms of the applying form. Enterprise support team members remain available 24×7 your can buy facility of best services.

QuickBooks Support Phone Number said...

However exceptions are typical over, sometimes it generates the down sides and user wants QuickBooks Support client Service help. Call our QuickBooks Support number in virtually any trouble Our professionals are terribly dedicated and might solve your entire issues without the fuss.

QuickBooks Support Phone Number said...

You can now get an amount of benefits with QuickBooks Pro Support Phone Number. Proper analyses are done first. The experts find out from the nature related to trouble. You're going to get an entire knowledge as well. The support specialist will identify.

Jamess said...

QuickBooks Payroll has emerged among the best accounting software which has had changed the meaning of payroll. QuickBooks Payroll Support Number will be the team that provide you Quickbooks Payroll Support.

jameswill11 said...

You really need to decide the QuickBooks Enterprise Technical Support Number the terribly second you get a slip-up in your screen. it’s potential that you just may lose information, or get corruption in your record or company file if the error prolongs.

QuickBooks Support Phone Number said...

These were the ways with the help of which you can resolve the QuickBooks Support balance sheet issues and if you are not able to solve the problem on your own, then you can go to the official website from where you can take the help of the help and support team.

QuickBooks Payroll Support said...

You may want to send the files directly without converting them into portable file documents. QuickBook Support software has proved to be quite convincing and beneficiary for individuals who run their businesses.

JimGray said...

The principal intent behind Support Number For QuickBooks is to provide the technical help 24*7 so as in order to avoid wasting your productivity hours. This is completely a toll-free QuickBooks client Service variety that you won’t pay any call charges. Of course, QuickBooks is one among the list of awesome package in the company world. The accounting part of the many companies varies according to this package. You'll find so many fields it covers like creating invoices, managing taxes, managing payroll etc. However exceptions are typical over, sometimes it generates the down sides and user wants QuickBooks client Service help.

JimGray said...

Various sorts of queries or QuickBooks related issue, then you are way within the right direction. You simply give single ring at our toll-free QuickBooks Payroll Tech Support Number . we shall help you right solution according to your issue. We work online and can take away the technical problems via remote access not only is it soon seeing that problem occurs we shall fix the same.

steffan said...

Payroll management is truly an essential part these days. Every organization has its own employees. Employers have to manage their pay. The yearly medical benefit is important. The employer has to allocate. But, accomplishing this manually will need the full time. Strive for QuickBooks Payroll Support Number. This can be an excellent software. You'll be able to manage your finances here. This is certainly right after your accounts software. You'll be able to manage staffs with ease.

Jamess said...

based on this package. You will find so many fields it covers like creating invoices, managing taxes, managing payroll etc. However exceptions are typical over, sometimes it creates the negative aspects and user wants QuickBooks Tech Support

HP Printer Support Number said...

Therefore, it is expected that you should have never to take technical risk in your hand. Otherwise, you would have to make the HP Printer Tech Support Number final farewell the basic function of the HP Printer. However, nobody can compare the way of fixing the technical glitches as veteran and experience team will do.

accountingwizards said...

QuickBooks Payroll Support has developed the program form with almost evolution to try all checks and taxes issues. Since no one is well in this globalization. In most cases when individuals are protesting about incorrect calculation and defaults paychecks results. Similarly fixing QuickBooks structure of account might be a confusing attempt to do and tough to handle dozens of for a normal user.

accountingwizards said...

If you need the assistance or perhaps the information about it, our company will be here now to do business with you with complete guidance combined with the demo. Interact with us anytime anywhere. Only just e mail us at QuickBooks Payroll Tech Support Number. Our experts professional have provided all the required and resolve all style of issues pertaining to payroll.

Blogsilly said...

“Just dial our QuickBooks Payroll Customer Service to inquire of about for Quickbooks Payroll customer care to get rid of payroll issues. We take advantage of startups to small-scale, medium-sized to multinational companies.”

kevin32 said...

The error will likely not fix completely until you comprehend the main cause connected with problem. As company file plays a truly crucial role in account management, such that QuickBooks Support becomes a little tough to identify. File corruption issue is a bit tricky.

accountingwizards said...

Our Experts are available 24*7 to fix your issue. Contact QuickBooks Support team to have instant solution.

QuickBooks Payroll Support said...

Each time you dial QuickBooks Customer Support Phone Number, your queries get instantly solved. Moreover, you can get in touch with our professional technicians via our email and chat support options for prompt resolution on most related issues.

rdsraftaar said...

Even though you are feeling that the full time is odd to call for help, just pick up your phone and dial us at QuickBooks Support Number because we offer our support services 24*7. We genuinely believe that the show must go ahead and thus time seriously isn't an issue for all of us because problems try not to come with any pre-announcements.

kevin32 said...

The error will likely not fix completely unless you comprehend the main cause connected with problem. As company file plays a really crucial role in account management, so that QuickBooks Technical Support Phone Number becomes only a little tough to identify.

QuickBooks Support Phone Number said...

Intuit has developed QuickBooks Payroll Support Number Online to create the web-based features into the users. The QuickBooks Online comes with a monthly subscription. A person can get access to QBO through a protected log-in via an internet browser.

QuickBooks Support Number said...

Because of this we at QuickBooks Enterprise Support Number gives you the main reliable solution of the every single QuickBooks Enterprise errors.

QuickBooks Support Phone Number said...

So, you can find loads of solutions by visiting their site and seeking at their online forum page. Contacting QuickBooks Payroll Support Phone Number experts via e-mail If you are having concerns, you'll get support by sending your queries through e-mail towards the QuickBooks Payroll support experts.

steffan said...

Let’s see some awesome features that could have caused it is so popular. If you are also a QuickBooks user and wants to get more information concerning this software you may read the QuickBooks Enterprise Support Number.

steffan said...

Dial QuickBooks Tech Support Number to deal in such situation which requires top quality Data services and data recovery tools with expertise to diagnose the problems. Dial QuickBooks Helpline and get your business file data related issues resolved from highly experienced certified Pro-Advisors.

jameswill11 said...

QuickBooks Enterprise Support Number also extends to handling those errors that usually occur when your version of QuickBooks has been infected by a malicious program like a virus or a spyware, which might have deleted system files, or damaged registry entries. Moreover, our QuickBooks Enterprise Customer Support Team also handle any kind of technical & functional issue faced during installation of drivers for QB Enterprise; troubleshoot any other glitch that may arise in this version or the multi-user one.

tom wick said...

QuickBooks Tech Support Number get you one-demand technical help for QuickBooks. QuickBooks allows a number of third-party software integration. QuickBooks software integration is one of the most useful solution offered by the software to manage the accounting tasks in a simpler and precise way. No need to worry about the costing of this software integration as it offers a wide range of pocket-friendly plans that can be used to manage payroll with ease.

Bryan Willson said...

Common problems addressed by the consumer care unit that answers calls include Returns, Cancel order, Change order, QuickBooks Premier Support Phone Number, Track order as well as other customer service issues. In the place of trying to call QuickBooks we recommend you inform us what issue you will be having and then possibly contact them via phone or web or chat.

accountingwizards said...

Not really Small And Medium Company But Individuals Too Avail The Services Of QuickBooks. It Is Manufactured By Intuit Incorporation And Has Been Developing Its Standards Since Then. QuickBooks Enterprise Tech Support Phone Number Is A Software Platform On Which A User Can Manage Different Financial Needs Of An Enterprise Such As Payroll Management, Accounts Management, Inventory And Many Other Things. It Provides Necessary Features In Real Time When It Comes To Enterprises.

QuickBooks Payroll Support said...

There are many and varied reasons behind a QuickBooks made transaction resulting in failure or taking time for you to reflect upon your bank account. QuickBooks Support phone number can be obtained 24/7 to provide much-needed integration related support. Get assistance at such crucial situations by dialing the QuickBooks Support Number and let the tech support executives handle the transaction problem at ease.

steffan said...

The QuickBooks Desktop Technical Support Number could also be used to get rid of your questions associated with using various attributes of this remarkable product from QuickBooks.

Bryan Willson said...

The QuickBooks Support Phone Number could be reached all through night and day as well as the technicians are particularly skilled to manage the glitches which are bugging your accounting process.

QuickBooks Payroll Support said...

Whatever the case, if you're not ready to get in touch with us through the QuickBooks Technical Support Number then you can certainly dial our other number that will be QuickBooks Tech Support Phone Number. The QuickBooks ProAdvisors are working a day reliably to pass at the top notch QuickBooks Error Support.

kevin32 said...

QuickBooks Support Number Premier is a popular product from QuickBooks known for letting the business people easily monitor their business-related expenses; track inventory at their convenience, track the status of an invoice and optimize the data files without deleting the data. While integrating this particular product with other Windows software like MS Word or Excel, certain errors might happen and interrupt the file from opening up.

Arthur morgan said...

Quickbooks Support Telephone Number
QuickBooks has completely transformed the way people used to operate their business earlier. To get familiar with it, you should welcome this positive change.Supervisors at QuickBooks Technical Support Number have trained all of their executives to combat the issues in this software. Utilizing the introduction of modern tools and approaches to QuickBooks, you can test new techniques to carry out various business activities. Basically, this has automated several tasks that have been being done manually for a long time. There are lots of versions of QuickBooks and each one has a unique features.

Unknown said...

Want to grow your business ?? just log on to http://www.mistyinfotech.com. We are the fastest growing business outsourcing company and sanitary napkin vending machine manufacturer in India.

Blogsilly said...

QuickBooks error 9999 can occur while you are installing a program or Intuit Inc. related software program (e.g. QuickBooks) is running. Also, it might occur to take place during Windows startup or shutdown, and even if the Windows operating system will be installed. This is why you should keep an eye on when and where the 9999 error takes place which acts as a very crucial bit of information in troubleshooting the problem. If you would like to take a shot to Troubleshoot QuickBooks Error 9999 yourself, you can continue reading this blog.

Shilpi Chaudhary said...

It gives us some information which is very knowledgeable for us.thanks for posting this for us.Good job....
https://www.mistyinfotech.com

Blogsilly said...

This way, we hope you have been able to resolve your problem. In case, you still haven’t been able to do so, we would like to recommend you to contact our experts for their guidance and assistance. If you would like to learn how to troubleshoot Quickbooks Error 9999, you can continue reading this blog.

divya said...


Your good knowledge and kindness in playing with all the pieces were very useful. I don’t know what I would have done if I had not encountered such a step like this.
AWS training in chennai | AWS training in annanagar | AWS training in omr | AWS training in porur | AWS training in tambaram | AWS training in velachery