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

Similar Messages

Could u please answer my question for filling the setup tables in SAP ECC purchasing the following error encountered..

Enter rate / USD rate type M for 00.00.0000 in the system settings
Message no. SG105
Diagnosis
For the conversion of an amount into another currency, an entry is missing in the currency conversion table.
Procedure
Add the missing entry in the currency conversion table.
Execute function
You can then continue to process the commercial transaction

Hi karim,
While posting thread here, please use proper headline instead of general sentence.
Issue: seems like some exchange rates issue at ecc side.
Seek your FI or functional team to maintain proper USD exchange rates/rate type For M.
Later you can try to fill set up tables.
Once FI team done exchange rates at ecc side, do transfer global setting to bw side.
Thanks

Program name for fill up setup table vistex agreement datasources

Dear all,
Am using the Vistex agreement data source in which i want to retrieve the data into BI landscape.
For my concern i have seen one article,
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/30a25b51-c5e8-2c10-d485-de4c69a78728
i can able to see in se38 we need to run program to fill up the set up table ,for different different extractors which is mentioned in the above articles.
but in my case am using ,
/IRM/LIS_RM_IPCRASP direct agreement condition
/IRM/LIS_RM_IPBBASP indirect agree condition
for the above mentioned two extractor wat is the program name to fill the set up table?
experts plz guide me its an urgent one,
regards
Edited by: gadhatharan thirunavukkarasu on Oct 17, 2011 2:35 PM

hi ,
this OSS notes belongs to ,use any standard SAP
BW objects from BI content for Vistex application
i dont wan to use satandard or existing bi content as per the suggestion,there is no std content is tehre for vistex application
am going customizes all upto Data target level
when i replicating the vistex datasources and try to cativate the system proposing error mesge,
The DataSource /IRM/LIS_RM_IPBBASP(D10CLNT730) does not exist in object version A
even the activation button is not highlighting
plz provide me solution its an urgent one,

How to reduce downtime for setup table

Scenario u2013According to system data, Setup table will normally take 5 days to fill but client agreed only for max 2 days downtime. User can do change only last 3 month documents not before that. For filling 3 month data in set up table 1 day required so I have to mange options accordingly.
Datasource u2013 2LIS_13_VDITM -> DSO u2013 ZBIllIG ->Info cube
I have to Reduce Downtime for Setup table so planning following optionsu2013
1.     First run the info package for Initialization without data transfer. Then start filling setup table without blocking the User. In case Users changes any document at the time of filling setup table then these changes will move to delta queue. Once setup table filled then execute full repair request and then Delta info package.
2.     Early delta initialization u2013 no idea how to perform steps.
Please share your views with detail steps.
OLI*BW doesnu2019t have any date range in selection criteria so manually I will find out document for particular dates and use these document range.
Checked lot of post in SDN but still expecting final answer to go ahead in Production.

Hi ,
Your requirement is Billing ODS and Cube - Reset up in R/3 SYSTEM & Initialization in BW SYSTEM .
Before starting find the previous data load volume and size.
1.Go to LBWG application value=13 (Always Schedule the job in the back-ground mode)
2.Verify using tcode u2018SE16u2019 that there are NO records in u2018MC13VD0ITMSETUPu2019 table after above delete job is complete.
3.Suspend the process chain job in BW.This is to avoid it getting kicked off while the reload process is still in progress.
4.Need to check LBWQ in R/3 system for MCEX13, unprocessed Outbound queue (records). This should be empty as the last delta would have processed all.
5.Delete the initflag in BW.
6.Need to check RSA7 in R/3 SYSTEM to verify that there is NO record for 2LIS_13_VDITM    (to be done right before the Setup job).
7.Create New Info Package for Info Source '2LIS_13_VDITM' for u2018Initialize without Data Transfer Optionu2019 .Execute the package.Re-establish the Delta processing flags in R/3 and BW for the Billing TD load .
8.Save the record count for table u2018VBRPu2019 using SE16 right before the setup job.
9.Schedule Billing Data Setup Job 'OLI9BW' in R/3 SYSTEM .
10.After the Billing Setup job is complete in R/3 system, get the record count of table u2018VBRPu2019 again using u2018SE16u2019
Expeted time in R/3:5 to 7 hrs(setupjobs)
Expeted time for init and fullload : 6 hrs
ODS activation : 3hrs
Cube and with agrregates fill all : 8hrs.
Thanks,
naidu.

Can you help with Tcode to fill this SETUP table? not working for me.

Hi,
For the datasource 2LIS_11_VASCL (SD Sales: Schedule Line Item), I need to fill the Setup Tables via OLI*BW
I understand the * to be the application number, which in this case it is 11 but I get a message that OLI11BW does not exist.
1. Can you help me with the tcode to fill the setup table for 2LIS_11_VASCL?
2. Since there are several datasources with the same application number 11, how do I fill only 2LIS_11_VASCL without filling the others:
2LIS_11_VAHDR                     Sales Document Header Data
2LIS_11_VAITM                     Sales Document Item Data
2LIS_11_VAKON                     Sales Document Condition
2LIS_11_VASCL                     Sales Document Schedule Line
2LIS_11_VASTH                     Sales Document Header Status
2LIS_11_VASTI                     Sales Document Item Status
2LIS_11_V_ITM                     Sales-Shipping Allocation Item Data
2LIS_11_V_SCL                     Sales-Shipping Allocation Schedule Line
2LIS_11_V_SSL                     Sales Document Order Delivery
Thanks

Ok,
I tried that and it basically bring you to OLI7BW as suggested above.
1. At this point, how do you know which of these it is actually filling:
2LIS_11_VAHDR Sales Document Header Data
2LIS_11_VAITM Sales Document Item Data
2LIS_11_VAKON Sales Document Condition
2LIS_11_VASCL Sales Document Schedule Line
2LIS_11_VASTH Sales Document Header Status
2LIS_11_VASTI Sales Document Item Status
2LIS_11_V_ITM Sales-Shipping Allocation Item Data
2LIS_11_V_SCL Sales-Shipping Allocation Schedule Line
2LIS_11_V_SSL Sales Document Order Delivery
2. Also, what does it mean when after running OLI7BW wide, with no restriction on my system, still rsa3 shows no records for 2LIS_11_V_SCL?
Any other way to confirm that there may not be any data in 2LIS_11_V_SCL?
Or any way, to make an entry which reflect in 2LIS_11_V_SCL so that I can verify if OLI7BW actually fills the setup table?
Thanks

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

Best practices to reduce downtime for Database releases(rolling changes)

Hi,
What are best practices to reduce downtime for database releases on 10.2.0.3? What DB changes can be rolling and what can't?
Thanks in advance.
Regards,
RJiv.

I would be very dubious about any sort of universal "best practices" here. Realistically, your practices need to be tailored to the application and the environment.
You can invest a lot of time, energy, and resources into minimizing downtime if that is the only goal. But you'll generally pay for that goal in terms of developer and admin time and effort, environmental complexity, etc. And you generally need to architect your application with rolling upgrades in mind, which necessitates potentially large amounts of redesign to existing applications. It may be perfectly acceptable to go full-bore into minimizing downtime if you are running Amazon.com and any downtime is unacceptable. Most organizations, however, need to balance downtime against other needs.
For example, you could radically minimize downtime by having a second active database, configuring Streams to replicate changes between the two master databases, and configure the middle tier environment so that you can point different middle tier servers against one or the other database. When you want to upgrade, you point all the middle tier servers against database A other than 1 that lives on a special URL. You upgrade database B (making sure to deal with the Streams replication environment properly depending on requirements) and do the smoke test against the special URL. When you determine that everything works, you configure all the app servers to point at B and have Streams replication process configured to replicate changes from the old data model to the new data model), upgrade B, repeat the smoke test, and then return the middle tier environment to the normal state of balancing between databases.
This lets you upgrade with 0 downtime. But you've got to license another primary database. And configure Streams. And write the replication code to propagate the changes on B during the time you're smoke testing A. And you need the middle tier infrastructure in place. And you're obviously going to be involving more admins than you would for a simpler deploy where you take things down, reboot, and bring things up. The test plan becomes more complicated as well since you need to practice this sort of thing in lower environments.
Justin

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

Issue while filling Inventory setup tables.

Hi,
Here we are facing a critical issue, while filling Inventory setup tables, we have done BX setup successfully. Not able complete BF and UM because of performance issues.
We filled 40% of BF and UM, since we dont have system downtime and stoped the setup at that movement. Shall we do BF & UM setup without R/3 system downtime. Is there any other way we can fill the BF, UM setup tables.
Your help is really appreaciated.
Thanks
BK

Hi BK,
Ideally you need the downtime when doing the setup for current and previous period as these are the only open ones where you can expect changes to happen due to user postings. What selection did you give when doing the set up? One idea is to break up the set up job so that each job loads for a week and then run the jobs in parallel. This would work for BF and then for UM of course you need to run it per company code. Are you using on ODS in your data model?

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

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

Filling billing setup table with documents from a given date

Hi
I would like to fill the setup table in R/3 with SD Billing Documents which have been created from 01/05-2007 until now. Is this possible somehow?
(SBIW --> Business Warehouse --> Settings for App Specific Datasources --> Logistics --> Managing Extract Structures --> Initialization --> Filling in the Setup Table --> App. specific setup of statistical data --> Perform Setup - SD Billing Documents)
The only fields I see are:
- Archiving run
- Sales organization
- Company code
- Sales document
Kind regards,
Torben

Hi Torben,
I dont think if you dont have option to see the date to select, probably you wont be able to fill your setup table based on date. Otherwise you can pull in the data from R/3 based on this date restriction in your infopackage after filling your setup table without any restriction.
Regards.

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

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

Ways to reduce downtime for filling up setup table

Similar Messages

Maybe you are looking for