Regarding statistical setup running

Hai
iam loding data for purchasing data using 4 data sorses.(2lis_02_scn,2lis_02_cgr,2lis_02_sgr,2lis_02_itm) when i run the statistical setup by using OLI3BW i am geting data of ITM AND SGR data sorses into setup tables, but i am not getting data of remaining data sorses , data is present in the tables of that data sorses.what is the reason , pls provide solution its very very urgent. points will be assigned. and when i go to LBWE to see the structure the below error is coming, pls explain it.
*Structure maintenance not provided for extraction structure MC02M0CGR ->*_
Message no. MCEX152Diagnosis
Structure MC02M_0CGR concerns a technical extraction structure. The inclusion of additional fields by using the structure maintenance is not part of the procedure for this.
If an extraction structure is used for extracting transaction data from two different business events, then the generic filling of the extraction structure fields from the fundamental communication structure data does not normally occur. An enhancement of structure MC02M_0CGR could then cause the newly included fields from the different events to be filled differently or not at all.
Procedure
Use the fields delivered by SAP for the structure MC02M_0CGR. Check to see whether the additional information you want can be extracted using other structures.

If the SCN structure is anything like the CGR structure, then neither will load. To load into the setup tables, you need to have active structures.
It looks like someone was changing the CGR structure and somehow damaged it or deactivated it. You need to fix this and then reactivate the structure. Then you will get your data.
Good Luck,
Brian

Similar Messages

Statistical Setup failure - Purchasing application

We upgraded our R/3 Plug-In from 2002.1 to PI 2004.1. To test the setup and init process,we ran the statistical setup run for 02 application. The setup program is successful but the documents are not posted into the MC02....SETUP tables. Checked the NPRT transaction to check the log entries, it displays that 252,000 documents are selected. Checked the extraction using RSA3 as well, it returns 0 records. Are there any specific entries that needs to be checked or entered for PI 2004.1 upgrade with reference to Purchasing application? or should I check any table lock stuff with reference to MC02...SETUP tables?

MS,
sorry for being so insistent, but for an analysis it is really important to check, if the statistical setup run actually created any data in the setup table.
If there are no records in the setup table, then the RSA3 can not show any records.
Best regards,
Bernd Sieger

Lo statistical setup ?

Hi
I have faced a question: why SAP has recommended Statistical setup for filling setup tables.. any technical reason behind..
Thanks.

Hi,
*In Lo's all the data sources are based on cluster tables so we have to fill the statistical setup because cluster table will not allow Header,item, schedule Data sources in a single table ... All need to be maintained seperatly. Thats y we are going for statistical setup.*Regards,
Statistical setup means filling the setup table with historical data when we are working for the first time on any data source. Apart from data source 2LIS_02_BX ( its for stock initialization in Inventory here we have to use MCNB T-code).
When we are filling the setup tables we can fill Parellely for different document numbers( Eg. If it is sales document No or vendor a/c no etc....)
Setup tables are cluster tables where we can't see the data and we can find only count of the records in RSA3 extract checker.
Regards,
Uday.

Running Statistical Setup in producition

Dear experts,,
IS that mandatory when ever i run statistical setup need to lock the users or no need, can i go ahead deleted and and running setuptable in production
Regards
Radha

Hi Radha,
Consider the application '02' - It is for purchasing.
If there is no delta pointer in rsa7 for all the purchasing datasources. There is no need to lock the user while filling set-up table.
If delta pointer is there for datasources - data duplication will occur,
Any modification in transactions -> R/3 Base table> LBWQ(Extraction Queue)--> RSA7 (Delta Queue).
Set up table is a cluster table that is used to extract data from R/3 tables of same application.
If I start filling set-up table, records from relevant R/3 tables will be updated to set-up table. During that time, If I made any change in any document - the same records will be updated in set-up table as well as in delta queue. Then there is data duplication.
Edited by: Priya.D on Apr 13, 2010 1:39 PM

Statistical setup: New Run indicator

Hi,
I don't understand the New run indicator option in the statistical setup. For example the OLI9BW.
The following is stated about this indicator:
New run
Indicator that determines that a new run should be started.
Use
If you set this indicator, document processing begins even when the first document is chosen, if a restart entry under the run name in use still exists.
What I understand is that a document can exist in both runs if you set this indicator. But what's the purpose of it??
BR,
Brian.

Hi,
Say you have started a setup in R/3 for the first time. You give a name to the run and tick this checkbox and execute. The termination time you have set in the program has come and the setup is still not complete. The set-up job will terminate.
To restart the job, you enter ths same job name and you uncheck the new run checkbox. The setup will restart from where it terminated.
Cheers
Neeraj

"New Run?" in the statistical setup on R3 side

What is the function of "New run?" in the statistical setup on R3 side

Hi,
Say you have started a setup in R/3 for the first time. You give a name to the run and tick this checkbox and execute. The termination time you have set in the program has come and the setup is still not complete. The set-up job will terminate.
To restart the job, you enter ths same job name and you uncheck the new run checkbox. The setup will restart from where it terminated.
Cheers
Neeraj

Regarding Setup Run

Hi All,
Do we follow any naming convention for the name of the setup run while doing LO Extraction.
What are the names that we can give. Does it need to be referred at later point of time.
Regards
YJ

...ah, just to add some more info...
When you run a setup, flag 'new run' checkbox and insert a name (as you prefer) to the job.
If, for any reason, your job stops (for system down-time or for any other reason...), you don't need to start everything again, but it's enough to DO NOT flag 'new run' checkbox and to insert the same name of your first job: in this way the setup will restart from the same point where it has been blocked !

Errors in Statistical Setup for 2LIS_11 and 2LIS_13

Dear colleagues,
in the process of filling setup tables for SD Sales Orders (11) and SD Billing Documents (13) I have encountered some errors.
In order to investigate the problem further, we have increased the tolerance for the number of faulty documents.
For the billing documents (13) this allows me to consult the log file and to trace all faulty documents. For the sales orders (11) however, we have also increased this tolerance number (1000). The log shows only 1 faulty document, while 1000 errors are tolerated, and the runs fails with this 1 faulty document (job cancelled).
The full log description of the cancelled job is:
Job started
Step 001 started (program RMCVNEUA, variant &0000000000100, user name BExxxx)
Data source 2LIS_11_VAHDR contains data still to be transferred
Start of order processing
Error determining rate: foreign curr. local curr. EUR date 04.05.2006 (doc. 20149127)
Job cancelled
Context:
At this stage I do not want the delta queue to be emptied. That's why the error states that the 2LIS_11_VAHDR datasource still contains data.
My questions are:
- Is this normal behaviour for this setup (or this particular error), or is it likely to be a program error?
- If it is normal behavior, can I "force" this run to log more than 1 error, while 1000 are tolerated?
Kind regards,
PJ

Hi
It could be because of main memory problem... so Restrict your selections and do the statistical setup
by the way how many comp codes you have? restrict with comp codes or doc ranges
Thanks,

Statistical setup actine or not

Hi Team,
In the filling of setup tables.
How do we know if the statistical setup is active or not-Apart from checking the actual tables.? Is there another way?
What if there is no activity and the setup is actually pulling 0 records.HOw do we differentiate.?
What happens if we run it twice..?
does the records get duplicated.?
Thanks for your time.
Andy

hi andy,
there is no possibility to check the setup table fill up is in active state. but if your data source is active means that's enough, it will defiantly fill the setup table.
if you run the setup table twice means it won't send the copy of the same records(duplicate) again.The setup table fill up finished, you are checking the data in RSA3 it showing 0 records means that extract structure don't have any data with in it.
if helpful provide reward points
regards
harikrishna N

STATISTICAL SETUP- LO

Hi Gurus,
What is STATISTICAL SETUP in LO extraction.
Regards,RAMU>

Hello ram,
Please go thru this.
Setup of Statistical Data
During a setup (statistical setup), the information structures are filled with consistent and complete data.
The statistical setup of one or more information structures is necessary in the following cases:
     If an information structure was created using the Logistics Data Warehouse (statistical database)
     If the update for the information structures was activated after documents were already in the system that were meant to be included in the statistics
     If the statistical update in Customizing was changed
     If the statistical data is inconsistent
Preparation
To restart a statistical update after an termination, allocate a name to each background run of the setup.
If a statistical setup is then terminated or if a setup is interrupted from the archive documents, the status of the setup will then be saved under the name of this run.
When restarting under the same name, processing will continue from the intermediate status that was saved.
After the run is successfully completed, the intermediate status that was saved is deleted.
Recommendation
     The reports should run as a background job.
     You should not change the sequence of steps that describe the statistical setup of information structures (procedure).
Procedure
The following steps are necessary to perform a complete statistical set up:
1. Initialize version for statistical setup
For reasons of security, the statistical data determined during a setup is not directly written into an information structure, but are saved instead under a separate version name. This version must be activated for intermediate storage before the statistical setup is carried out.
For this purpose, the report RMCSISCP is available.
The actual data is saved under the version name "000".
2. Save actual data
The actual data in the system should be saved for safety reasons.
Again, use report RMCSISCP for this purpose.
3. Edit all archived documents
To do this, you can use the various reports that are available in the individual applications.
4. Edit all documents in the system
This also takes place via the various reports that are available in the individual applications.
5. Transfer the data which was obtained in the statistical setup from the statistical setup version to the actual version
The data obtained is only imported to the actual version instead of the existing data after the successful completion of the statistical setup.
The report RMCSISCP is again used for this purpose.
Note
You can see the versions of the standard information structures by using the standard analyses. Here are the following possibilities:
a) You can allocate the version number of the version as a value to the user parameter "MCR" that you would like to see.
On the selection screen of the standard analysis, the field Version under Parameters is automatically completed with the given version number. The version number can be changed simply by overwriting it.
This setting is user-dependent and applies to all standard analyses.
b) If you assign the value "X" to the user paramter "MCR", the version "000" will generally appear on the selection screen of the standard analyses. Even in this case, the version number can be overwritten.
This setting is also user-dependent and applies to all standard analyses.
If you want to use either one of these functions, select System -> User profile -> User parameters. You can select this function from any menu.
Recommendation
You should change the user parameters in an alternative session, as it is not possible to return to the starting point from the user parameters maintenance screen.
c) Via "User settings", you can also make specifications for the versions, which are also user-dependent, but also only refer to one particular standard analysis.
To do this, in the selection screen of the standard analysis, select Goto -> User settings.
You are now in the standard drill-down. Select Goto ->Parameters.
If you set the indicator "Selectable version", the field "Version" with the version number "000" will also appear on the selection screen. This version number can be overwritten at any time and thus changed.
6. Follow-up processing
After successfully completing the statistical setup, you can then delete data that is no longer needed by deleting the version under which this data is saved.
These include:
o     Safety copy
o     Version for statistical setup
The report RMCSISCP can be used for this purpose.
Activities
To carry out a statistical setup, procede as follows:
1. Enter your selection requirements.
2. Save your entries.
3. Select Program -> Execute.
Description of the report RMCSISCP
The report RMCSISCP is used in all information systems in Logistics. For this reason, the report is described below.
You can use report RMCSISCP you can copy or delete versions from information structures under which statistical data has been saved.
The data, that has been saved in an information structure, is different due to the version under which they have been saved.
The version "000" includes the actual data, i.e., the data that was written into the information structure as a result of the statistical update.
The intermediate results are stored in the versions that begin with "&(" and that are created when an information structure is setup.
Planning data is stored under all other versions (that means version A000 and all numerical versions except version 000).
The statistical setup of an information structure is carried out just like the online update, with the difference being that the data is not usually written into version "000" first, but rather into a version that you choose, that begins with "&(". The data is only copied from this version into the "000" version after the successful completion of the initial transfer.
Note
While copying into the "000" version, you must not carry out any postings that update the respective information structure.
To keep the old version "000" (the existing actual data) from being lost, save it under another version. This "safety copy" is also generated with report RMCSISCP.
You can use the indicator "Initialize target version" to delete data data stored until now under this version. If the indicator "Do not copy initial records" is set, data records are only set if at least one key figure is not initial.
Attention
The report RMCSISCP should only be used for copying, deleting and for copying + deleting. Copy Management should be used to meet more complex requirements (Tools -> Copy Management).
Activities
1. Enter the name of the information structure that is to be copied/deleted.
2. Choose a processing type.
The Copy Management screen is called up. The processing type that you have selected is already set.
3. Here you make all the remaining entries required for selection.
Additional functions
You can also call up a log which contains detailed information about all of the completed setup runs.
This function allows you to make restrictions by specifying the start date of a run, the run name, the user and the application.
You can also either print the list of selected setup runs or the detail screen for a setup run.
Thanks,Ramoji.

Help!!! Purchasing setup run takes long time

Hi Experts,
I'm pulling purchasing data into BI from R/3. I'm having a problem where the setup run takes an extremely long time. we have approximately 3 years of data on R/3. when i look at EKBE table, there are clost to 5 Million records.
Basically when i run the scedule it took atleast 3 weeks and still did not complete. even when i run it only for 2008 it took 6 days but still didnt complete. so today i ran it for one month (Jan 2008) and its been running for the last 3 hours without completing.
has anybody come up with an issue like this?
I'm not sure if there is something wrong with the setup run as in im wondering if the job is hanging or something? is there anyway to figure this out?
I'm stuck with this at the moment, ive looked around but to no avail.
would really appreciate you're help as deadlines on this are looming.
thanks,
dilanke
Points will be rewarded.

Hi,
5 million purchasing records should take max 6 hour and it seems that you have a problem with problem which is filling setup table.Did you check OSS notes? There should be something pointing this isssue.
You can run NPRT transaction in order to see how long it took in the previous jobs.
Regards.

Statistical Setup Tables and Full Extractions

For Full Extractions what is the relationship with the statistical setup tables i.e. no of records in the table = no of records to be extracted? Thanks

Hi,
The relationship is 1 -> 1 you have to fill the setup table, the full load only reads this structure. So if you would like to load a 2LISxx full load every night, you have to delete and refill the setup table in R/3.
Kind regards, Patrick Rieken.

Regd Statistical setup - Shipment of DS - 2LIS_08TRTLP

Hi Experts,
Can u tell steps for filling Statistical setup - Shipment data from R/3.we used Lbwe,Lbwg and OLIE for filling setup tables.Eventhough we are getting zero records.Plse anybody can guide the required steps and transaction codes.
with regards,
Sailaja Mandapaka

Hi Sailaja:
To fill the Setup tables of the 2LIS_08TRTLP, 2LIS_08TRTS and 2LIS_08TRTK Extractors (Shipment Documents) you can use the VTBW Transaction Code.
To fill the Setup tables of the 2LIS_08TRFKP and 2LIS_08TRFKZ Extractors (Shipment cost Documents) you can use the VIFBW Transaction Code.
Regards.

Statistical Setup (OLI3BW tcode)

Hi all,
Can anyone please explain me what the below fields mean and what should I select to do a Statistical setup ie to do a full update.
Control of Recompilation run
1. Name of Run(New Run)
2. Termination date, Termination time
3. block all documents
4. Extraction structres BW
Document data restriction
1. Archiving Session
2. Purchase Org
3. Purchase document
4. Document date
I am trying to extract data from datasource 2lis_02_hdr using lo-cockpit and I have followed the below steps
1. LBWE transaction - inactivate update, deleted setup tables in application component 02(MM) and also deleted any delta queue in /nrso2
2. Maintain extract structure and datasource
3. Activated the update(Is this necessary to do before replicating the datasources ?)
4. Replicated the datasource in BW
5. Assigned infosource and created a infopackage to load the data to PSA.
6. Set up statistical update(tcode OLI3BW). I am not sure if I have to do this before step 5. I am struck here and unable to understand the fields to do a statistical update
Please help me.
Thanks,
Sabrina.

Hi Sabrina,
1. Name of the run - You can put in any name here. It does not matter. You can call it 'RUN1' or 'TEST1' whatever. It is just for you to differentiate between different runs.
2. Termination Date and Time - When it is filling up the setup tables, it might go on for a long time. So you can put in a time beyond which if the set up runs, the system must teminate it. Normally if you know that if it runs for more than 2 hours there is something wrong, you specify a time 2 hours from the current time as the 'safety upper limit'.
3. Block all documents - If you set this, all the records are blocked in the database from changes during the setup run.
4. Not sure...
You can break up your setup run in parts broken down by date ranges or document numbers etc. For eg. set up for all records with dates from Jan to March, do full upload into BW, delete setup tables, run setup again for March to May etc. For this you have the rest of the selections.

Rmceneua - statistical setup of info structures from purchasing documents

Hi all,
I run the program rmceneua for a specific purchasing document number. The line on this PO has been selected for deletion. LOEKZ = 'L'. When S011 and S012 are populated, will this line be taken into consideration when calculating the effective order value, etc.
I am new to SAP, so any help will be welcome.
Thank you in advance,
Rivaaj

hi,
the statistical setup will setup all PO-related extractors (2LIS_02_*) - so you only need one setup. =)
at this point all you need to do is to replicate the datasource in your BW system, create and activate (or transport) transfer rules, assign update rules for this infosource in whichever infoproviders, create an infopackage, and load away. =)
ryan.

Regarding statistical setup running

Similar Messages

Maybe you are looking for