Initialization Setup Tables.

Hi Gurus,
I have some doubts about filled of Setup Tables. Our case is that we don't have done any filled of setup tables for material document (MSEG table) and we want to do now but the problem is that the number of documents in MSEG table are around of 19.000.000 records and I think the ERP production system must be stopped around more than 10 hours to sure that any documents are posted during the initialization. Anybody knows how to do this without stopped the ERP system.
Thanks in advanded,
Best Regars,
Csr

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.
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
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
How to Minimize Effects of Planned Downtime (NW2004)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a02397f9-0d8d-2910-e5a0-b8241bbc9381
SAP Network Blog: SAP NetWeaver 7.0 BI: How To Minimize the Reporting Downtime during the initial data load
/people/community.user/blog/2007/09/23/sap-netweaver-70-bi-how-to133-minimize-the-reporting-downtime-during-the-initial-data-load
Hope this helps.
Thanks,
JituK

Similar Messages

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

8 hrs downtime, how to do the init setup tables

Hello BW Experts,
I have 8 hrs downtime per day and i have to do the fill of 30 million records to the init setup tables. If i could breakdown each day init setup table fill based on the company code + sales org.
day 1 fill cc1
day 2 fill cc2
How what happens if someone does any records changess in the cc1 on day2. how is that captured. what is the solution.
Please explain.
Regards,
BWer

After your initialization Setup Tables you must do a Init Delta Queue for that company only.....the delta load is cummulative respecto to the init delta loads....
If yo u have three init delta one for each company ...the delta loads load the data for alll three companies at same time.....you can initialize companies one by one and load delta..
This prevents lost changes in companies that you have setting up...
I hope this helps you
Regards
Message was edited by:
Oscar Díaz

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

How to fill setup table and initialization

Hi,
Can any body send me the document for filling the setup tables and initialization ?
My mail id is [email protected]
Regards,
Viren.

Hi
Please sent that doc. to me also.
[email protected]
Regards
Swetha

Initialization & fill up setup tables

Would it be good enough to initialize and fillup setup tables for different areas at once in PRD.
if yes Ok No pls let me know reasons
Regards
P

Hi
The application/live data would not be deleted, it is still available in application tables like for example if you have deleted set up tables for SD billing..It doesnt mean that data from VBRK, VBRP etc are gettting deleted.. It is only from setup tables the data gets deleted. You always reload from application tables to setup tables again
we can take the performance issue also,like better performance and also it will be useful for us wen we r doing the RDA i.e realtime data acquisition wen daemon works it will act as a reference for the daemon like once it is completed to load data to PSA from setup tables the daemon will delete the data in set up tables

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.

Error while filling setup tables for 2lis_13_vahdr

Dear friends,
I am getting below Error while filling setup tables for 2lis_13_vahdr.
More faulty documents found than the tolerated 0000000000
Message no. M2222
Can any one guide me how to address this issue.
Thanks and Regards
Nithya

Hello Nithya,
It seems the No of tolerated faulty documents that you have given is 0. So when you initialize try to these.
While executing OLI*BW including a value in the maintain "No. tolerated faulty documents" - 5000 or 10000.
Then execute the program in background.
Once the job is completed check the background job log if any errors.
Thanks
Chandran

Error when filling setup table

Hi!
I'm trying to fill the set-up table in R3 for SD Billing Documents.
SBIW (Display IMG (Settings for App Specific Datasources --> Logistics --> Managing Extract Structures --> Initialization --> Filling in the Setup Table --> App. specific setup of statistical data)..
When running the program i get this error msg:
"More faulty documents found than the tolerated 0000000000"
The result is that the program stops. Some of the data is coming into the set up tables, but this seems to be inconsistent.
Anybody know what I could do?
BR
Bjørn

Thanks a lot..
How can I find the log of dumped jobs?
BR
BJørn

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.

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

Delete setup table takes long time

Hi Experts,
I'm trying to use 2LIS_02_HDR data source to populate ODS 0BBP_PO, 0BBP_INV and 0BBP_CON as this is a basis for the spent analysis cube 0BBP_C01.
I'm pretty sure before i ran the setup i deleted the setup files. however when i loaded the data the number of docs shown in NPRT is 3429. however when i loaded the data to BI, it pulled in almost 10 million records for the datasource, which totally baffled me. Can anyone tell me why this is?
since this did not seem correct. i decided to do the initialization again so did a LBWG and this has been running for the last 2 days. Can anyone tell me why this is taking so long as well?
This is on the dev box and not even on production.
help please.
thanks
dilanke

Hi soma,
Thanks for you're reply but this is not a basis issue.
My main question is why only 10 Million records where pulled into BI when only 3500 docs were read into the setup table?
thanks
dilanke

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......

Setup table in LO

Hi All
Why do we need setup tables in LO? Or What is the purpose of having setup tables in LO extraction?
Regards
Saddy

The purpose of the setup tables is to allow you the capability of loading historical data from R/3 to BW. You can use the setup tables for full loads or for establishing your initialization, but they are used independently of collecting delta data. Thus you can collect historical data for different applications (even different datasources within the same application) without affecting delta's already setup for other datasources.
Hope this helps.

Initialization Setup Tables.

Similar Messages

Maybe you are looking for