Question regarding deltas and filling of setup tables

Hello Friends,
We are using the Sales Order Item Datasource 2LIS_11_VAITM. We have transported it to BI Production. We have initialized the delta and the deltas are running for the past 3-4 months.
Now we had a new requirement which was getting satisfied by the Sales Order Header and Sales Order Header Status DataSources, 2LIS_11_VAHDR & 2LIS_11_VASTH respectively.
Now we wan to transfer both these (header & header status) DataSources to BI Procution. My question is:
1) Do we have to refill the setup tables again in R/3 for the Sales (11) application?
2) Do we have to reload the entire Sales data again from scratch.
3) Is there any way to transport the 2 new DataSources to BI Production and without disturbing the already running deltas of Sales Order Item Datasource?
Regards,
Prem.

Hi,
1) Do we have to refill the setup tables again in R/3 for the Sales (11) application?.
Yes you need to refill the setuptables, because if you want to load deltas, you need to do Init then deltas, other wise first time when you are filled setup tables, (first load init with the existing data in setuptables) from that day to till date you can do full then you can set delta.
It is better and good to fill setup tables and load.
2) Do we have to reload the entire Sales data again from scratch.
Any way you need down time to load the other 2 datasources, and also for 11 application you are filling setuptables.So for perfectness it is better to load from first.
3) Is there any way to transport the 2 new DataSources to BI Production and without disturbing the already running deltas of Sales Order Item Datasource?
If you transport the new datasources then delta won't distrub in BW. If you did any changes to DataSource and trying to transport it to production then it will give error, because LBWQ and RSA7 will have data so first you need to clear it and then transport it.
Thanks
Reddy

Similar Messages

Duplicate records in RSA3 after filling of setup tables.

Hi All,
I had deleted the setup tables and filled the setup tables but when i go to check 2LIS_11_VAITM in RSA3 its populating duplicate records. Any idea of why its showing this discrepancy.
Regards,
Venu.
Edited by: Venu on Aug 13, 2008 11:38 AM

Hi Venu,
If you are using 2LIS_11_VAITM then you would have duplicate VBELN because you can have multiple items per transaction. The primary key of that datasource is VBELN and POSNR.
On the other hand if your using 2lis_11_vahdr then there shouldn't be any duplicate VBELN since there's No Item #.
- Kit

Taking long time filling the setup tables for sales and shipment

Hi ,
I am trying to fill the setup tables for sales and shipment and it is taking lot of time .
It took 16 hours just to bring 6 months of sales history data in the test environment .
Cn anybody help on this issue why it is taking that much of time ...
I am trying to load the sales data from R/3 into APO-BW from 2005 to 2007 .......
It is taking 16 hours to fill the data for only 6 months .

Hi,
1. delete data and refill the setuptables again by spliting to several small pieces.
2. compare the data. wht is the last Document numner in RSA3(Maximum one). Start from Maximum one. may be bit complex approch.
you need to check with PSA and base tables.
keep one thing in your mind you need to check againest MSEG and BSEG only. noy BKPF and MKPF.
correct if i'm wrong.
either refill or create a user exit to avoid duplicae records(you should have very good understanding of data, it will lead to inconsitent data for delta records).
User exit not a good solution. it's one possibility.
****Assign Points If Helpful****
Regards,
Ravikanth

Will delta disturb if we fill the Setup tables ??

Hi All,
In the process of R/3 upgradation we have deleted the Setup tables.
After that Deleta is running fine. But I am not able to see the data in RSA3.
Now I want to fill the Setup tables for that particular application
If I fill setup tables is it disturb the delta process ???
Regards
Sankar

Hi Sankar,
Filling up Set up Table will not effect Delta as Set up table is relateed to Full Load and Not Delta laod.
The Delta and Full Load are TWO different Routes.Both are not connected to each other.
Follow this procedure
For Delta Loads-Queued Delta
1)Do an Init Data load without data transfer .BI Side
2)Check whether the datasource is GREEN Status in RSA7
3)Run the Activate Transfer Structure Programme.-BI side
4)Run the V3 job-LBWE JOb Control or in SM37
5)Then check form the Delta in RSA7
6)Do a delta Load .
For Full Load
1)Delete Set Up Table-In r/3
2)Do an Init Data load without data transfer .BI Side
3)Fill Up Set up Table-In R/3
4)Full Repair -FullLoad -in BI
5)Then the delta Loads will follow.
Rgds
SVU

Emptying Delta queues before filling a setup table

How do I empty the delta queues? I want to carry out this task just prior to filling a setup table. Thanks

Hi Sekhar,
Thanks for that, I was on a flight anyway, just got home. I was thinking on the plane about the previous point that you mentioned wrt the collection run. I think I understand the point that you were trying to make is this a correct understanding
1) System is locked
2) Do a collection run - the reason for this is that there may be postings which have not been placed on the RSA7 queue since the last collection run
3) Do Delta load twice
Does that make sense. The points that you have raised otherwise, I will post a question otherwise on the steps I will look to take just to get confirmation I am not missing anything

Problem while filling the Setup Table for the DS 2LIS_02_SCL.

Hi All,
When I am trying to fill the Setup table for the DataSource 2LIS_02_SCL and only for one specific Purchase Order, it is showing me a message like
u201CDataSource 2LIS_02_ITM contains data still to be transferredu201D
I have deleted the Setup Table and I want to delete the entries from SM13, but I do not have Authorization.
Also, here I am trying to fill the Setup Table for 2LIS_02_SCL and not for 2LIS_02_ITM, but the message displayed above is showing as 2LIS_02_ITM DataSource. I think the Setup Table will be same for both the DataSources.
Waiting for your valuable inputs.
Thanks in Advance.

Hi,
When you want to fill the setup tables first you need to delete setup tables to avoid the duplicate entires in setup tables ( you can delete the setup tables by using t.code LBWG with application no is 02)
In your case, the data souce is 2LIS_02_SCL for purchasing.
when you want to delete the setup tables by using t.code LBWG with 02 application no it will delete all the purchasing related data from all the data sources like
2LIS_02_SCL
2LIS_02_ITM
Before the deletion of setup tables you need to clear the delta Queues and stop the V3 jobs, which loads the data to Delta Queues (RSA7) and Update tables(LBWQ).
you need to run the V3 jobs manually by using LBWE > Job control > and schedule the jobs until the delta queues will get 0 records. that means no data will be available in RSA7 and LBWQ
go to SM37 to see the jobs LIS-BW-VB_APPLICATION_02,
once the delta queues gets 0 records by running V3 Jobs manullay.
Then remove the released state jobs > remove from schedule means delete the jobs in LBWE > Go to job control > you can delete the released jobs.
Becuase No postings to be done in application tables, while running setuptable filling you should take some down time to fill the setup tables.( OLI*BW) *=Application number.
Once you clear the Queues and delete the v3 jobs, then you need to fill the setup tables after deletion of setup tables.
once you fill the setup tables , by running intialization to BW side the delta Queue is formed for the data source in R3 side
Now the postings can be done in R3 side, so you need schedule back the V3 jobs, which you already delted from LBWE to load the data from application tables to RSA7 or LBWQ.
I hope this may help yoou.
Regards.
Rambabu
Edited by: Rambabu velanati on Jun 9, 2010 4:41 PM
Edited by: Rambabu velanati on Jun 9, 2010 4:52 PM

Problem while filling the setup table

Hi experts,
i am extracting data from 2lis_12_vcitm, while filling the setup table it showing bellow error message,
NO EXTRACT STRUCTURE ACTIVATE OR NO BW CONNECTED
but i Extract structure is in active mode and BW connection also is there.
what is the problem,
please help me,
answer will be appreciated with full points,
regards,
venkat

Hi Venkata,
If u are looking for reinitialization to ur targets and which needs the refilling of setup tables then u need to perform the following activities.
Try to take the down time in R3 to stop the posting.
try to empty the queue(both the extraction and Delta queue in R3 and deeavtivate the V3 update) and then delte the data in ur targets in BW which are getting feeded from these Data sources and remove the init flag at the Infopackage level for the respective DS's.
And then check if there is any blocked records in SM13 for ur application.
Delete the existing set up for the application 12.
And then refill the setup tables (may be u can think of multiple setups to make this execution faster and to reduce the R3 load).
Once the setup is done.. then take init-without data transfer for ur DS's in BW and then activate the V3 in R3.Down time can be taken off here.
and then take repair full load(which carry all of ur Setup tables data to ur targets). Once the repair is done then u can look for the regular deltas...
For more information u can search SDN on the same..
thanks
Assign points if this helps

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

Advantages of filling of setup table ?

Hello ,
Could you please let me know the advantages of filling setup table ?
Regards

Hi,
Setup Tables are cluster tables. They 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. and 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 (These are like Cluster Tables ), 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 jb runs... and we can extract the delta records from Delta Queue.
once we succefully run the init, we can delete setup Tables also... no probs...
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.
Have a look at these discussions:
set up tables
Set up tables
Set up tables
view of set up tables data in se11??????????
Set Up tables..
lo: delete set up tables: DOUBT
Blogs of Roberto will be useful as well:
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it !
LOGISTIC COCKPIT: a new deal overshadowed by the old-fashioned LIS ?
Display Setup Table Data:-
Goto SE11 or SE16 -> MC*SETUP -> F4 you will get all the setup tables choose and display the data
To check completion of dta loading
NPRT t-code... Where u can see the entry with ur user and the Run of ur setup..
Regards
Tg

No data coming while filling up setup table

Hi All,
We have to two datasources
1. 2LIS_12_VCSCL Sales-Shipping Schedule Line Delivery
2. 2LIS_12_VCITM Delivery Item Data
When i am filling up setup table it is only filling it for Delivery Item datasource, its not filling up for Schedule line datasource.
Is there any setting to be done before filling up the setup ???
Regards,
Viren.

Hi Anil,
Thank you very much...
Now its working. I have another problem my extraction is still running .
I have selected status to ok automatically,activate the ods data automatically, and update data target automatically.
when i checked sm50 in source as well bw system its not showing any thing.then i checked job in monitor, it showing transfered records in yellow and updated records in greeen.
Can anybody tell me how to change extraction status from yellow to green??
I dont want to do it mannually..
Regards,
Viren.

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

Error while Filling Up setup table

Hi All,
When i try to Fill the Setup table i am getting error message as below
Error determining rate: foreign curr. local curr.
INR date 25.03.2008 (doc. 11990)
Help us,
Regards,
Hari

Hi Hari,
the reason for the error is, some set up fillings covert the currency while copying from base table to set up table.
This is the case here.
So get in touch with your Fi resource of ERP to maintain the currency translation giving those detail.
I think this filling is not being done in production.
So further not to get such error ask thgem to copy all exhange rates from Production to this system.
Otherwise, if the setup doent find someother exhange rate, then again it would fail. and the same procedure needs to be repeated.
Naveen.A

CONVT_NO_NUMBER dump while filling PURCHASING setup tables

hi experts,
I have deleted the setup tables in lbwg and try to fill the setup tables again, it is running like 6-7 secons and giving the the below dump,
CONVT_NO_NUMBER. dont understand why it is giving the dump.
plz provide the solution to solve the above dump,i need to fill the setup tables and extract the data into PRODUCTION SYSTEM.
pl check the below error analysis.
Error analysis
    An exception occurred that is explained in detail below.
    This exception cannot be caught in the context of the current statement.
    The reason for the exception is:
    The program attempted to interpret the value "P" as a number, but
    since the value contravenes the rules for correct number formats,
    this was not possible.
Regards
venuscm

Hi,
I received the same runtime error "CONVT_NO_NUMBER" after I start the application specific setup of statistical data - perform setup purchasing. The short text of the runtime error describes that "P" is not recognized as a number.
In my case the ABAP-program "SAPLEINS" was interrupted because the function module "ME_STATISTICS_LIS_NEW" could not be processed successfully in line "341".
So I set a break point in this line and start the perform setup for purchasing (LIS-application 02) again. The debugging mode showed me the dataset of purchasing document that was responsible for the program abort. In the table "ekbe" (History per Purchasing Document) exists one or more purchasing documents who has as transaction/event type (ekbe-vgabe) an alphabetic character. But alphabetic and numeric characters are absolutely correct for the data maintenance of transaction/event type in the purchasing document.
In my case the ABAP statement in line 341 (... WHERE vgabe = 1.) could not be interpreted the dataset with the alphabetic transaction/event type "P" (invoice parking).
The sap-Note 1548467 resolved my problem and I was able to perform the setup for purchasing successfully.
* LOOP at t_ekbe WHERE vgabe = 1.                      " 1548467
LOOP at t_ekbe WHERE vgabe = '1'.                    " 1548467
Best regards
Michael

Filling up setup table

Hi all,
Is it possible to fill up the setup table during night only ?? What i mean can use continue from where i left from the previous day ??
Because we were not extracting any data for delivery till date. Now we want delivery data in the production system.To fillup the setup table i think we have to make users lock for more than one day.. that is not possible... Can i run filling up the setup table for two-three nights only ?? because during 8:00 PM to 8:00 AM there are no users.
please suggest something..
Regards,
Viren.

Hi,
but this should not be a problem.
If you want to fill your setup table, you should fill it up until say 3 months ago (check what time frame is safe to use where noone will change the documents) and then make a full load, and then you empty your setup tabl and make a second fill with only the latest say 3 months and this will be loaded very fast and then you load ths as an initial load to BW and there's no need for locking the users for a whole day.
Kind regards
/martin

Error while Filling a setup table

Hi,
While i filling a setup table, i got this error message,
"Error determining Rate:foreign curr .local curr
INR date 27.06.2007 (doc.8166) "
any body tell me the meaning of this and how to rectify it.
-Arun.M.D

Hello Arun
You are getting this error because Currency Exchange Rate is not being loaded to your system for INR. Ask FI team to maintain this.
Reward points if it is helpfull.
Thanks
Tripple k

Question regarding deltas and filling of setup tables

Similar Messages

Maybe you are looking for