About setup tables in R/3 system

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

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

Similar Messages

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

Setup table in LO Cockpit

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

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

Setup tables in Lo Cockpit

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

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

Is Oracle Partitioning req'd in the Source R/3 system for SBIW Setup Table?

We have ECC6.0 as our Source System. My BI team is trying to load 3 years of SALES history into the BI7.0 system, and then the APO system will pull 1 of those 3 years into it. To begin this process, they are using SBIW to Manage the Extract Structures and create the Setup Tables.
I got an alert that these Setup Tables were created with Partitions. We are not licensed for partitioning in our ECC(R/3) system, only in BI and APO.
1.) Is Partitioning really necessary for these Setup Tables?
2.) It appears that the Setup jobs create these tables by default as partitioned? How do I disable or change that?
Thanks,
Richard (Basis)

Hi Neeraj,
thank you for the reply.
Yes, i have checked tRFCs and logs , everything looks ok, we are getting expected records in BW but job is not ending in the backend system and BW load is always showing YELLOW.
looks like our developer using custom FM to extract data and i feel that something code issue which is going endless loop. they need to write code to terminate process after last record in the extract process. i will update you once i get root cause of the issue.
thanks again..
thanks
Venkata

Fill setup tables using Mirror systems

Hello BW Experts,
Could you provide the procedure how to do the fill of setup tables using mirror systems. This way i can avoid the downtime off the r/3 system.
Regards,
BWer

Hi,
What do you mean by mirror systems?
You can do an early initialization, which will fulfill your requirement of not shutting down R/3 system.
With Regards

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

Missing PO in 2lis_02_itm init extraction / setup tables

Hello Gurus,
could anyone please help me out with this toppic:
I want to extract Purchase Orders to BW via DS 2lis_02_itm. Source System is R/3 4.6c. Filling up the setup tables is working. My problem is, that there are several Purchase Orders which are not filled in the setup tables (so no extraction to bw)! I have checked these PO and for me they seem fine. I can´t find any reason why they aren´t extracted. Of course i am running all programms whithout any restrictions. I have debugged the programm rmceneua with one specific po which is not extracted but can not find a reason why it is not written to table MC02M_SETUP.
Did i miss some customizing settings? Are there some kind of PO which are not extracted because of there PO Type (ZCO/ZB) do they eventually have a wrong status?
I can not find any information about the functionality of programm rmceneua. Maybe you can help me out of this?
Thanks a lot
JANOS

Did you check whether the process key is maintained properly?

How to stop document posting when filling setup tables for logistic app.

Hello Boys
I've read several threads and weblogs about data extraction from logistic applications i.e the ones which uses the infosources like 2lis_13_vditm, 2lis_02, 2lis_03, etc, etc,and now almost every thing is clear to me but one thing: how do i actually "close the system" while the process of filling setup tables i.e MC03BF0SETUP, MC03BX0SETUP, MC13VD0ITMSETUP, are running?
So I have some questions
1) which is the procedure to prevent users from posting documents for an specific logistic applications (02,03, etc.) in a source system
3) For example when using TC OLI9BW for statistical setup from billing documents (app no. 13), there is a check box "Block all billing documents?". Is this option for such pourpose?
4) Every logistic applications has a different procedure??
thanks (with points of course) for any help
rgds
A. Garduñ

Hi Azael:
Q1: usually the BW team will inform basis/secuity about the deletion and performing of setup tables. they will fix a time after the normal hours where in all users are locked out from the system. in a sense, R/3 will be down for that time.
2. the check box which says, "block documents" is meant to block posting. for eg: you are doing setup tables late in the evening, and you assume that no user is assessing the system, but if there is a user(just by chance) who is doing some posting and when he try to save it, the system will not allow him to do save as you cheked this option.(normally we donot use this)
3. some LO may have different procedures, for eg IM. but most of them have the same functionality.
hope it helps.
assign points if helpful
kalyan

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

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

Data loading for Logistics Data Extraction 2LIS_06_INV through setup tables

Hi Guyz,
I have LO Datasource 2LIS_06_INV which I am using for extracting Invoice Verification Data.
I had intialized and loaded invoice data in BI system and was using chais to load daily.
Now I want to load data again from scratch from source system.
As of now I know we need to delete and fill up setup tables in source system keeping the users locked so that no new records are created that particular moment.
But what about the delta queue and extraction queues.
Do I need to do something over there because as I understand there will be records in both of them so before filling the setup tables I need to delete both the queues and then fill the setup tables so that duplicate records should be avoided.
Please let me know what exactly should I do in detail.
Appreciated in advance.
Regards,
raps.

hi,
this entirely depends upon the DS, if the DS delta type supports overwrite mode then you need not lock the users, you can start the setup job without deleting the delta queues as well coz even if the record is extracted twice the values won't mess up as the flow will be in overwrite mode. If delta type of DS is Additive in table ROOSOURCE then you need to lock down the users or run the job over a weekend when no users are logged in.
regard,
Arvind,

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

Block document when filling setup table

hi experts :
I have a question about blocking document ,do we have to block the document when filling the setup table and when doing initial extracion both ? or just filling the setup table?this confuess me .
in experiance ,how long will it take to fill the setup table if the total records reaches about 5 million .
thank you in advance
cindy

Hi,
It is recommended to fill the setup table after logging off all the transaction users, preferably during nights (basically you will have to take a down time of the R/3 system). if you have taken a down time then it is not necessary to block documents, since there would be no users posting transactions.
The blocking would be useful if you are trying to fill the setup table during the day time and there is possibility that users could post some documents. However by blocking documents, this would prevent the users from posting / creating documents and this could hamper the normal business (like creating billing documents, orders etc).
if you are doing the filling up at night after taking down time then the approx time could be 1 hour(my guess) again this could depend on the application servers, RAM etc. However if you are trying to do it during the peak hours, i.e when the users are doing transaction(which is not recommended), then it is very difficult to estimate the time.
Assign points if useful.
Regards
Venkata Devaraj

About setup tables in R/3 system

Similar Messages

Maybe you are looking for