Setup table in LO Cockpit

hi i have a very silly doubt,
which is a correct statement about setup tables:
1>setup tables are cluster tables, we can't see the data in the setup tables
2>data in setup table can be checked using SE11
can anyone please explain me significance of both the statements
Thank you,
sam

Hi dear,
yes, it's true, you can see data in setup tables, but you have to read as "you can see meaningful data in cluster tables".
In other words, data can be checked in SE16 (not in SE11 that contains only fields definition) as number of entries, but nothing more; in other words you can check if there is something or the table is emprty, but you cannot check directly if there is something you need (for this purpose you have to use RSA3 extraction simulation).
So, no contradiction in your two sentences !
Hope now is clearer...
Bye,
Roberto

Similar Messages

What does it mean by deleting the Content of the setup table when LO cockpi

Hi all:
what does it mean by deleting the Content of the setup table when LO cockpit ? why should we do it? why set up tables ?
Thank you very much!!!
Edited by: jingying Sony on Jun 7, 2009 4:46 AM

Hi Jingying Soni,
Data sources in LO cockpit have a seperate exctraction source during full update mode and delta update mode.
During delta update mode(when an transaction is posted in any particular application - like SD - sales orderm delivery) data is posted in application tables and updated alongside to the update table/extraction queue.
From the extraction queue this data is further transfered to the delta queue using periodic background jobs.The data is then upladed in BW. The delta lad always reads data from this delta queue.
However, when a full load is requested from the BW, the data is sourced by the set up table of the corresponding application.
The setup table is loaded/initalized first. In this initialization process , it reads data frm the corresponding application tables and stores it within this table. Later BW reads from this set up table whenever full/initial load is requested.
The process of filling set up able before full load request frrom BW is called set up run.
Before you run a set up to fill the set up tables you need to check that the set up table is empty.
If it is still containing data that was previously loaded in some other set up run. This data will als get loaded in BW unitinetionally/accidentally.
So, you need to ensure that you only get the intended data in BW. This can be done by proper selections to transfer data from application tale to set up table and from setup table to BW.
Along with this you hae to ensure that the set up table is either empty or you are using a disparate selection in the set up run and BW load which does not overlap with the previous set up runs data.
Hope it helps,
Best regards,
Sunmit.

Setup tables in Lo Cockpit

hi everybody,
i need information about SETUP TABLES in LO COCKPIT(i had some information like(temporary location where we can do INIT/FULL load to cube))
i need more information other than these

Hi,
U can find more information on SDn by giving a search word like ' Setup tables'
Thanks,
Message was edited by:
SDN BW

Strategy to fill setup table fo Logical Cockpit

Hi gurus,
I have to fill setup tables (i mean MC11Va1ITM and mc12vcoitm) and have a lot orders and deliveries on R3 side. The problem is a can't continue interupdted run (according to data in rmcw3 - table for counter readings of info structures re-setup) the documents started to reinitialize again in spite of unmarked flag.
So, any ideas about strategy'll be highly appreciated.

Hi Mikhail,
Kindly have a look at below links,
Part 1: SD Overview
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/1034bcbe-b459-2d10-2a89-ecdeb4e53ff1
Part 2: DB Update logic
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/804165a5-c081-2d10-39b4-af09a680f591
Part 3: Extractor Logic
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/1094e790-1d93-2d10-17ba-8b559bf0f75b
Part 4: Update Modes
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/5039632a-c398-2d10-0aaf-97167a3de753
Part 5: SD Datasource overview
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d07aa007-84ab-2d10-46ba-a5a2679f0d7b
Part6:Implementation methodology
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0508c20-84c1-2d10-2693-b27ca55cdc9f
Part7: LO datasource Enhancements
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c09d5356-d8c4-2d10-8b84-d24723fc1f0a
Hope this helps.
Regards,
Mani

Extraction Problem- while filling the setup table

Hi all,
I have a problem when i fill the setup table for LO cockpit Extraction on any SD datasources (2_LIS_VAHDR,2lis_13_vdkon etc.,). i am done with LBWQ successfully. i also verified the datasources in RSA6. They are in active status in RSA7-delta queue.
After i submit the request to fill the setup table, i am getting
"datasource 2_LIS_VAHDR contains data still to be transferred". if i check the extract checker (RSA3) i am getting the error msg "data source is not defined in the source system"
Can anybody help me on this?
one of my friend suggested that it could be the reason that some jobs are in active status that loads/updates data into base tables which the datasources refers.
Any idea on the reason and resolutions?
Greatly appreciated !

Hi Vijaya,
We too got the same Error : " the datasources are not defined in the source system".
This is source system connection problem. Check whether connection between R/3 and BW is active.
This error occurs when the connection is inactive.
Also, if it is copy client, then check data exists in other client. If so delete the setup tables data in that client as well.
This will resolve your issue.
Thanks
Edited by: Allen Fyne on Aug 9, 2008 6:47 PM

LO-COCKPIT: error in Filling Setup tables

Dear Guru's:
While filling setup tables from tcode: sbiw, I am getting following error:
EXTRACT STRUCTURE NOT ACTIVE OR BW NOT CONNECTED.
Bw is connected with R/3- I also have checked the connection thr' SM59, its working.
And even Extract structure is Active.
Then why this error is coming?
Pls let me kno.
Points will be rewarded.
Thank you.

Are you on Developement? If it is, please go to RSA6, look for the data source, and see if the extract structure is actually active, there may be one or more includes, check each one of them, if everything is fine, I would just reactivate it and move it to quality and production. If that happens only in Production, but it is fine in development, then I would make sure the development and production sytem extract structure matchs. Sometimes, someone modifies the development but never moved it to production. Check the last transport created for that extract structure too.
thanks.
Wond

What are setup tables and why do you need to run it

Hello Gurus,
I know the steps for setting up the LO cockpit exactors.
My question is what are the parameters that you feed into the Setup table filling screen --- like the doc numbers, start date and end date.
Why do we have to run the setup tables?
If I give the start date for setup table run for SD as 08/24/06 and end time Nill and others parameters blank, then would the set up job run for ever. Is this how you set it up in production environment.
Does setup mean, bringing the data from application table to extraction structructure?
Regards
Simmi

Hi,
Look at the threads below :
SetUp Tables
setup tables
setup tables
setup tables
Cheers,
Kedar

How to initialize the setup table for GTMuFF08Global Trade ManagementuFF09?

hi experts,
I can find the datasource of GTM like 2LIS_46_SCL, 2LIS_46_ITM with rsa6.
But when I use rsa3 to do test it, nothing found. I try to initialize the setup table, but I can not find it under SBIW.
Please help me, many thanks.
Brgds/steve

Hi
These Data Sources are from LOGISTICS Try at Tcode.LBWE --Logistics **** Pit.
Here is LO Cockpit Step By Step
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
       SD Sales BW
            Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
       Select the fields of your choice and continue
             Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 u2013 Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders u2013 Perform Setup (T-Code OLI7BW)
        Specify a Run Name and time and Date (put future date)
             Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
Hope it helps

What is the use of setup tables in LO extraction

Hi Friends,
What is the use of setup tables in LO extraction, what is the functionality of setup tables
Thanks in advance

hi,
to prepare data to be extracted to bw,
more details take a look Roberto's weblog
/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.

SETUP tables steps required

<Moderator Message: Please search before posting. You can find a lot of information related to this issue searching the forums, the blogs and of course the online help.>
Hi friends,
I want do purchase extraction using LO cockpit extraction before doing this i want to know about R/3 steps & setting if any in R/3 system.
I know about LO extraction steps apart from that if we have any steps in R/3 setting kindly forward to me.
thanks
Siri
Edited by: Siegfried Szameitat on Jan 26, 2009 12:31 PM

Hi Siri........
U want to extract Logistic data........
The following section describes the steps that are necessary to configure a data
flow for logistics data extraction.
1. Transfer the logistics DataSource for transaction data from Business Content
With the transfer of the DataSource, the associated extraction structure is
also delivered, but the extraction structure is based on LIS communication
structures. Furthermore, based on the extraction structure for the DataSource,
a restructuring table that is used for the initialization and full update to BI
is generated.
Naming convention:
DataSource 2LIS_<Application>_<Event><Suffix>; where <Event> is
optional
Examples:
2LIS_11_VAITM: 11 = SD Sales VA = sales order, delivery schedule ITM
(u2192 ITEM) = document position
2LIS_02_HDR: 02 = MM purchasing HDR (u2192 HEADER ) = Document
header
Extraction structure MC<Application><Event/group of
events>0<Suffix>; where MC is derived from the associated communication
structures and <Suffix> is optional
Examples:
MC11VA0ITM: Extraction structure for the DataSource 2LIS_11_VAITM
MC02M_0HDR: Extraction structure for the DataSource 2LIS_02_HDR,
where M_ indicates the group for the events MA (order), MD (delivery
schedule), ME (contact) and MF (request).
Restructuring table (= setup table) <Extraction structure>SETUP
Example:
Extraction structure: MC11VA0IT u21D2 Restructuring table:
MC11VA0ITSETUP
2. Maintain extraction structure (transaction LBWE)
This means that fields can be added to the extraction structure that is
delivered with the DataSource without modifying anything. On the one
hand, fields from the LIS communication structures that are assigned to the
extraction structure can be used, that means standard fields that SAP has
not selected, and on the other hand, customer fields that were attached to
the LIS communication structures with the append technique can be used.
After the extraction structure is created, it is generated automatically and the
associated restructuring table is adapted.
3. Maintain/generate DataSource
In the DataSource maintenance, you can assign the properties Selection,
Hide, Inversion (= Cancellation) and Field Only Known in Customer Exit to
the fields of the extraction structure. After enhancing the extraction structure,
the DataSource always has to be generated again!
4. Replicate and activate DataSource in SAP BI (=metadata upload)
5. Maintain Data Target (Data Store Object, InfoCube)
6. Maintain Transformations between DataSource and Data Target
7. Create a Data Transfer Process
the Data Transfer Process will be used later to update the data from the PSA
table into the Data Target.
8. Set extraction structure for updating to active (transaction LBWE)
In this way, data can be written to the restructuring table or the delta queue
from then on using the extraction structure (see following steps).
9. Filling the restructuring table/restructure (OLI*BW)
During this process, no documents should be created or changed in the
system! In some applications, it is possible to fill the restructuring table
beforehand in simulation mode. These results are listed in a log (transaction
LBWF). Before filling the restructuring table, you must ensure that the
content of the tables is deleted (transaction LBWG), preventing the table
from being filled multiple times. Once the restructuring tables are filled,
document editing can resume as long as Unserialized V3 Update or Queued
Delta is selected in the next step. Be absolutely sure that no V3 collection
run is started until the next successful posting of an InfoPackage for delta
initialization (see step 11).
10. Select update method
Unserialized V3 update
Queued delta
Direct delta
11. Create an InfoPackage for the DataSource and schedule the Delta
Initialization in the Scheduler
This updates the BI-relevant data from the restructuring table to the
PSA table. Since the restructuring table is no longer needed after delta
initialization, the content can be deleted (transaction LBWG).
Use the Data Transfer Process created in step 7 to update the data from
the PSA table into the Data Targets. After successful delta initialization,
document editing can resume, as long as the direct delta update method
was selected in step 13. This means that BI-relevant delta data is written
directly to the delta queue.
Note:
If the DataSource supports early-delta initialization, the delta data can
be written to the delta queue during delta initialization. This feature is
controlled with an indicator in the Scheduler.
12. Start V3 collection run (transaction LBWE)
This step is only necessary when the update method unserialized V3 Update
or Queued Delta was selected in step 10. By starting a corresponding job for
an application, the BI-relevant delta data is read from the update tables or
extraction queue and written to the delta queue.
13. Create an InfoPackage for the DataSource in BI and schedule the Delta
Update in the Scheduler
The BI-relevant delta data from the delta queue for the DataSource is updated
to the PSA table. Use the Data Transfer Process created in step 7 to update
the data from the PSA table into the Data Targets.
Hope this helps.......
Regards,
Debjani......

About setup tables in R/3 system

Hello BI Gurus,
During Production Support, if a requirement arises where new fields have to be included in a Datasource that is covered by the LO Cockpit, then in such a case do we need to necessarily delete the setup tables and reload.
regards,
gaurav

Hi Guarav,
As you need to clear setup tables, before transporting these changes to production system.
After import changes, need to setup to load historic data into BW.
Check: [How to retain deltas when you change LO extractor in Production system|http://sapbwneelam.blogspot.com/2007/09/how-to-retain-deltas-when-you-change-lo.html]
Hope it Helps
Srini

Setup table Administration with Direct Delta mode

Hi guys,
I have a direct delta as update mode for my 2LIS_11_VAITM extractor in R/3.
I'd like to know if I have to manage the relative setup table (MC11VA0ITMSETUP) with this update mode also.
For instance, If I delete an ODS content and restart a new INIT on BW system, do I need to delete and then to fill the setup table?
In general, Do I need always to menage the setup table with each kind of update mode (direct delta, queued delta and V3 update)?
if you know the answers, please reply me direcly without insert link.
Many Thanks.

yes, you do....the initial loads for lo datasources are completely independent of the delta loads and hence of the delta method...
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
M.

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 <i>buffer area</i> 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

2LIS_06_INV - Records not getting into the setup table ..Please help..

Hello Gurus,
I am trying to setup 2lis_06_inv but i am not able to understand why i am not able to get any records in the setup table.The job shows finished in few seconds.
What can be the possible reason for this?
I activated the datasource using RSA5. I setup the Update Mode to 'Direct Delta' in LBWE ( Extraction Cockpit). I deleted the data in the setup table and then ran the OLI6BW tcode and gave tomorrow's date for finishing the job and then ran the job. The job shows finished in a few seconds but no data gets into the setup tables.
Error message in log says:
Recompilation has not selected anything -> Refer to error log
Message no. MRBW015
Diagnosis
This error message was issued for one of the following reasons:
No documents exist
No selection criteria were entered
BW updating has not been activated
Any help is deeply appreciated.

Hi,
Check table RBEX on R/3 side whether any entries exists in that or not.
if it does not contain any entry it will not bring any data.
Check the link.
2LIS_06_INV Extractor problem
Regards
SH

Why we use Setup Table.

Hi All,
Can u plz tell me why do we use setup table and what is flow of data from R/3 2 BI?
Please search the forum before posting a thread
Edited by: Pravender on Sep 16, 2010 11:45 AM

Hi Sonal
The kind of exractors largely depends on the application due to the way they were developed
/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
Check the above weblogs
Regards
Naveen
PS: Assigning point to the helpful answers is the way of saying thanks in SDN

Setup table in LO Cockpit

Similar Messages

Maybe you are looking for