Setup table - Archiving run option

Hi all,
I want to check my inventory data have archiving run while filling setup table. Also archiving run data in which table i can find. If required R3 data in archiving table, we no need to think about backup data in BW.
thanks

Hey Raj,
Your question is not clear?
If you are talking about archived data
- Archived data will be not be present in the source tables, you need to perform special mechanism to retrieve the archived data.
- if you want to extract the data using the data source to BW you will not be able to extract the archived data.
For this you need to write a exit in CMOD for that particular data source to additionally extract archived data where for example BSID-XARCH =x or BSEG-XARCH=X etc.
or
one more way is to extract the archived data by creating a generic data source on top of the archived tables for only those records which are archived (XARCH = X).
Just perform a full update as the archived documents does not have updated records. you can go for creation of generic data source it would be a better option to extract the archived data instead of disturbing the existing data flow.
Regards
KP
Edited by: prashanthk on Nov 17, 2011 11:58 AM

Similar Messages

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

What are setup tables and why do you need to run it

Hello Gurus,
I know the steps for setting up the LO cockpit exactors.
My question is what are the parameters that you feed into the Setup table filling screen --- like the doc numbers, start date and end date.
Why do we have to run the setup tables?
If I give the start date for setup table run for SD as 08/24/06 and end time Nill and others parameters blank, then would the set up job run for ever. Is this how you set it up in production environment.
Does setup mean, bringing the data from application table to extraction structructure?
Regards
Simmi

Hi,
Look at the threads below :
SetUp Tables
setup tables
setup tables
setup tables
Cheers,
Kedar

Error when running setup table for 2LIS_03_UM

Hi experts,
When running the setup table for 2LIS_03_UM, we got the error message "Plant FP01 does not exist." Any suggestions on how we can fix this?
Thanks,
Donna

check if this plant has been maintained in source system or not. If not, ask the concerned team to maintain it.
Another way may be to allow error records which should ignore errornous records and rest should be filled in setup table.
Regards,
Gaurav

How to run the setup tables in CRM for 0CRM_LEAD_I datasource.

Hi all,
How to run the setup tables in CRM for 0CRM_LEAD_I datasource.
what is the tcode and steps to follow.
Thankyou.

you dont have to do set up tables for 0CRM_LEAD_I.
run the init infopack in BW and then subsequent delta's

Inventory Load - Running Init of Setup tables

I'm planning the initial load of Inventory data and want to make sure that I understand what needs to be done.
Question 2 - To save time can I run the initialization of the setup tables for 2LIS_03_BX,BF,UM in parallel. Or do I have to wait for one to finish before I submit the next?
Thanks,
Chris

Chris,
Question 2 - To save time can I run the initialization of the setup tables for 2LIS_03_BX,BF,UM in parallel. Or do I have to wait for one to finish before I submit the next?
--> You can run parallel, you can also run parallel for each datasouce(eg: BF) by providing proper selection(like, Plant, date..ect)
Hope it Helps
Srini

Why we give run name while filling setup tables

Dear Experts!!!
In LO Extraction , while performing setup tables filling, why we have to give some run name like zrun/ ztest ?
cant we do it without giving any run name for filling the setup tables.
Your help will be appreciated.
thanks in advance!!!

Hi Anil,
The run name is the name under which the determined data is saved.
If you restart a run that has been terminated, rather than executing a new run, it will use the data that has already been determined, i.e. the next run will be carried out with the data that was selected up to the specified termination date and time.
Regards,
Mansi

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.

Timeout error while filling setup tables

HI all
I am getting timeout error while filling setup tables(OLI1BW).I clicked on execute button on hte screen.Its not scheduled as a background job.
Going through threads i have come to know that to solve this issue
1.BASIS team have to increase backgroung processses or memory
2.run it as a background job.
When I went to Program->Executein the backgroundPrint background parameters window has popped up.
What to do in there?I am afraid if I include parameters like printer name....what is it and how long is it going to print?
Please let me know.
Thanks,
Harika.

thanks for the reply.
it was set to LOCL only.
But i have 3 options in the dropdown windowsprinter :Send to onenote2007
Microsoft XPS document writer
OUrprinteraddress
WHich one to choose here?
Edited by: harikag on Aug 10, 2011 8:47 AM

Filling of setup table

Hi,
I got the error message while filling the data in setup table.
i got message is follows in Joblog.
Program terminated, time limit exceeded: 3,795,659 document item(s) updated
Message no. M2227
Diagnosis
The setup run exceeded the specified termination time.
System response
The run was terminated.
My doubt is if i check the option Rerun and i will give my jobname.
it will start the job where the job was terminated its correct.
if they wont provide time to fill the setuptable, i mean they asking me, is it ok to do 2 users in transaction after 9 P.M., the time in which iam going to fill the setuptable.
I told to our client, no should lock the user. document mismatching will happen.
Is it any other way is there user to allow transaction the time in which iam filling the setuptable..

Hi,
These are related links:
Time Limit Exceeded Error Encountered
Termination message for an attribute change run "Time limit exceeded."
Extraction Error : Time limit exceeded
XI : How to Re-Process failed XI Messages Automatically

How to activate Purchase datasource without deleting setup table for others

Hi Gurus,
In developement system purchasing datasources 2LIS_02_HDR, 2LIS_02_ITM and 2LIS_02_SCN are active and deltas are also running for these.
Now acccording to the requirement We need to activate other datasources as well like 2LIS_02_CGR and SGR .........
To so this do we have to run the setup table again or any other option is there for this??
As this step would take lots of time in Production and for this downtime would be required which is not feasible.
Please suggest some solution.
Thanks in Advance,
Uday Shankar.

Hi,
We will do the setup (Filling and Deleting) concept based on application component it's not based on DS .S you don't have other way.
Regards
Ram.

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.

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

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

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

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

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 - Archiving run option

Similar Messages

Maybe you are looking for