Sap bi setup tables

Hi Experts
i have a doubt
please tell me why setup tales in LO and why not setup tables in FI

Hello,
what is "lakhs" ?
Please use plain English words on a world wide forum...
Regards,
Olivier

Similar Messages

How can distribute 5 lakhs records from sap R/3 setup tables ?

How can distribute 5 lakhs records from sap R/3 setup tables in to multiple requests in sap BI?

Hello,
what is "lakhs" ?
Please use plain English words on a world wide forum...
Regards,
Olivier

SOME DOUBTS IN SETUP TABLES

HI,
TO ALL BW GURUS,
I WANT TO KNOW THE ARCHITECTURE OF SETUP TABLES.
WHAT IS THE MAIN DIFF'S BETWEEN NORMAL TABLES AND POOLED AND CLUSTERED TABLES.
2.
WHAT IS PSEUDODELTA.
WHERE IT IS USED AND WHAT IS THE PURPOSE OF THIS DELTA.
THANKS
ANAND.

Hi,
check the beow link for table types:
http://help.sap.com/saphelp_47x200/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
regards,
raju

Strange error while filling setup tables for purchasing

hi experts,
while filling setup tables, job is getting cancelled. when I check in sm37 message is
Enter rate GBP / SGD rate type M for 03.08.2009 in the system settings
Job cancelled after system exception ERROR_MESSAGE
It is for only the 8th month of 2009. If I run for other dates it is succesfull.
I am not able to understand what it mean.
Pls guide me how to resolve this.
regards,
rajesh.

hi
according to sven check this link
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/dc43c445-0d01-0010-23a1-ca348ff5f975?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0d5bf96-b19b-2c10-e3b6-e2f12a3de99a?QuickLink=index&overridelayout=true
EUR Conversion to USD
may help you.

Setup tables for invoices header data (2LIS_13_VDHDR)

Hi experts,
I am using 2LIS_13_VAHDR and 2LIS_13_VAITM to transfer data to SAP BW. Through the t-code SBIW, I I run the job to fill setup tables with invoices data. the job is completed succefully. when I check the extractors in RSA3, the extractor 2LIS_13_VAHDR doesn't bring any data while 2LIS_13_VAITM bring a set of items !!
I m wondering why I dont get invoices header data!
Thank's a lot for your help.
Abdess,

Hi,
Did you delete the old initialization request from BW and also delete old setup table.
Because the issue is strange, If you are able to see entries in item then header should also fetch data.
Repeat the steps again if you have time.
Use T-Code LBWG to delete setup table.
Delete MCXE13 entries in LBWQ.
Use T-Code OLI9BW to fillup setup table for 2lis_13.
Thanks,
Shakthi Raj Natarajan.

Problem with populating setup tables for purchasing

I'm working on NW2004s.
Problem: Setup tables are not getting populated for 2lis_02_hdr, 2lis_02_item..
what all i've done so far:
1. Activated Data Sources in RSA5.
2. In LO Data Extraction, all the extract structure are active. (btw in job control i'm not sure what it does, i did make job parameter start date immediate, didnt set the print parms, schedule job gives an error.. anything here i may be messing it up?)
3. In SBIW initialization Deleted the contents of setup table and executed the 'Purchasing - perform setup'.
4. In NPRT i can see the log, the name of the source table EKKO, duration of run is 0.0 and no of docs 130.
5. In RSA3 for 2lis_02_hdr extraction process 0 records.
6. I look at SE11 for 'MC02M_0HDRSETUP' and table contents gives 0 records.
Any help is appreciated what i'm missing why the setup tables are not populating. I went thru the forum and did what was said but no sucess yet. I'm not an expert in SAP BW just been working for a year so pl dont be cryptic, explain u'r answers. Thanks for your time
Mayil

Hi,
All the active datasources will be available in RSA6, after that go to LBWE ,maintain Ex Stru, Maintain DS and make that active, then we go for statistical setup
have you done these things?
Did you put any filters while filling up the setup tables?
what is the transaction you used for Setup.
cheers
RK

2lis_02_itm setup table successfull but rsa 3 no data

Hi @all,
we have an problem with one R3 source system. Following Issue. The system connection is okay we get data from some FI extractors.
But the 2lis_02_itm extractor sends no data to bw:
Following is done:
1. we have datas (ekko,ekpo)
2. 2lis_02_itm Structure is active
3. Processkeys are maintained
4. setup table are built sucessful and he collects data(setuolog)
But the extractor checker doesn't work he collects 0 data.
Does anybody know where lost the datas? Why we don't get any datas ? For other application componnent like FI we can extract data.
Help would be great.
thanks in advance!
Br
rene
Edited by: Renè Lechtenböhmer on Aug 20, 2008 11:52 AM

Hi,
Can you please check if the following settings mentioned in the best practice document have been maintained,
3. Configuration
1. Customizing for the Extractors
1. Order Update Parameters Setting
Procedure
This step has to be carried out in the R/3 System.
R/3 Role Menu Order Update Parameters Setting
Transaction code OPL5
Carry out the following steps:
1. If the view is in Display mode, change it to change mode.
2. Select the lines in which there are transaction data you want to upload to BW.
3. Select the Details button.
4. Ensure that the four indicators (Update, Header, Item and Operation) are chosen.
5. Press F8 to choose the next entry.
6. Choose Save.
Here is the link for the best practice document.
http://www.google.com/url?sa=t&ct=res&cd=2&url=http%3A%2F%2Fhelp.sap.com%2Fbestpractices%2FBBLibrary%2Fdocumentation%2FB80_BB_ConfigGuide_EN_DE.doc&ei=ZmO6R5qKFaTsgQKBrtDoDQ&usg=AFQjCNGINah5eM2RYjnbp2d10VuwfsfyCQ&sig2=GyGDHsqg8FOL2BSdpWBsvA
From thread,
Re: No data in PP datasources
regards,
Raj

Trans Code to check the Date of Termination in Setup Tables-Very Urgent!!

Hello BW Gurus,
I need to check the date of termination I have given while filling up the setup tables to verify when my delta loads would stop running. NPRT transaction code just gives me the time it took to fillup the tables but the date of termination is given as zero's, so please can someone let me know how to see that.
Thanks in advance,
Anjali
Message was edited by: Anjali

Hi,
If I understood it right, you wanted to predict when the actual date of termination would occur or you wanted to know what parameter you did input on the job that is now running?
Case 1:
As far as I know, that Info cannot exactly be determined since it will depend on various factors e.g. CPU speed, I.O. Speed, Amount of data to be process etc. etc. which I dont think SAP could predict as exact as possible (if ever an option was provided).
During the early stages of our project, we did that but we base the run time from history. Meaning, we always log (on top of existing SAP Job Logs) the run times in Excel and we somehow use that data to predict the actual Date of Termination.
Case 2:
In case you wanted to see the parameter while its running, I have no suggestion but for you to debug the currently running program.
In SM51, click the Active job and choose menu Program/Mode->Debugging. On the fields on the lower left portion, type RMCSNEUA-DATUM (got this value when you execute the Table Setup, say OLI9BW; Press F1 on the date of termination field) this would give you the actual date you have provided.
If I have helped, please grant points...
--Jkyle

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.

How to Fill Setup tables for MAP (IS- Retail)

Hello,
I am working on MAP scenario, I found the following data sources as a part of it. Can anybody please tell me how to fill the setup tables for these and what are the base tables for it??
2LIS_40_REVAL
2LIS_40_S202
2LIS_40_S207
2LIS_40_S208
Your reply is highly appreciated.
Regards,
Naresh

Hi Naresh,
We cannot fill setup tables for each data source.
ORISBW -- This is the t-code to fill the setup tables for all the data sources which are related to application component 40.
If you want setup tables names of your data sources please check below.
2LIS_40_REVAL --- MC40RP0REVSETUP.
Comes to your second post.
2LIS_40_S202
2LIS_40_S207
2LIS_40_S208 these are LIS data sources, whic are replaced with LO data sources in SAP BI 7.0
If you are using LO data sources then no need to use LIS data sources.
Regards,
Venkatesh

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

hi experts
happt new year to u all in advance.
i want o know that weither their wil set up tables in fi/sl & copa extraction .
and for what this set up tables meant for.
plz send answers to my mail id
kalyan11069@gmail
with regerds,
lakshmi raj.

there will be no setup tables for FI/SL and COPA extractions..
Go through the link:
http://help.sap.com/saphelp_nw04/helpdata/en/f3/3a69377f2b8032e10000009b38f8cf/content.htm
Regards
Manga
Assign points if it helps

How downtime can be reduced for setup table update.

Hi;
Can anyone tell me various ways to reduced system downtime for setup table updates.
thanks
Warm Regards
Sharebw

Hi,
You will need to fill the set up tables in 'no postings period'. In other words when no trasnactions are posted for that area in R/3 otherwise those records will not come to BW. Discuss this with end user and decide. Weekends are a general choice for this activity.
try Early Delta Initialization
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
Extractors that support early delta initialization are delivered with Plug-Ins as of Plug-In (-A) 2002.1.
You cannot run an initialization simulation together with an early delta initialization.
hope this link may make you clear about early delta init
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
thanks,
JituK

Ways to reduce downtime for filling up setup table

Hi Experts,
Can anyone tell me the step by step process so that i can reduce downtime for filling up setup tables?
I know that setup tables can be filled by considering sales document numbers....but the further steps are not clear with me...........specially with data loadin till PSA and then to ODS/Cube
So plz throw some light on this.......
Regards,
Vaishnavi.

Hi,
You will need to fill the set up tables in 'no postings period'. In other words when no trasnactions are posted for that area in R/3 otherwise those records will not come to BW. Discuss this with end user and decide. Weekends are a general choice for this activity.
You can run them after business hours so that there wont be any transactions, or in the night times or you can do it on week ends so that there is no need to take down time.
Fill the setup tables with already closed values and then fill up again with open values.This will reduce the down time.
Initialize closed periods first in which users wont enter data ( for example in 2007 or 2006), this initializations can be done while users are working. Then the initialize last period at night/weekends.holidays etc.
If you know documents that are in closed periods, and you are sure that these documents can no longer be changed, you can only fill the SetUp tables for these documents or only for these periods, by continuing to post in open periods. You then initialize only for these intervals, delete the setup table, and only then do you fill the setup table with the rest of the documents this procedure can drastically reduce the downtimes of your system.
However, there is a risk that user exits (and in LIS, formulas and conditions) can be used to retrieve documents that are in periods that are already "closed periods".
One more thing what you need to bear in mind is, to check if there are any Scheduled jobs which are updating the transaction tables, which would definitely cause Data Reconciliation Issues.
Try Early Delta Initialization
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
Extractors that support early delta initialization are delivered with Plug-Ins as of Plug-In (-A) 2002.1.
You cannot run an initialization simulation together with an early delta initialization.
Hope this link may make you clear about Early Delta Initialization
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
http://www.allinterview.com/showanswers/2907.html
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/early-delta-initialization-459379
http://books.google.co.in/books?id=qYtz7kEHegEC&pg=PA293&lpg=PA293&dq=early+delta&source=web&ots=AM1PtX6wcZ&sig=xKOF85Gb8UtszY44zt06K6R0n3M&hl=en#PPA290,M1
http://www.blackwellpublishing.com/journal.asp?ref=1069-6563&site=1
EARLY DELTA
Early delta Initialization
How To Minimize Downtime For Delta Initialization
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6
How To Minimize Effects of Planned Downtime (NW7.0)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/901c5703-f197-2910-e290-a2851d1bf3bb
Note 753654 - How can downtime be reduced for setup table update
602260 - Procedure for reconstructing data for BW
437672 - LBWE: Performance for setup of extract structures
436393 - Performance improvement for filling the setup tables
Note 739863
/thread/756626 [original link is broken]
Re: How to Setup and INIT from 2LIS_13_VDITM with millions of records
How downtime can be reduced for setup table update.
Fill setup tables without locking users
Initialization Setup Tables.
Hope this helps.
Thanks,
JituK

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.

Sap bi setup tables

Similar Messages

Maybe you are looking for