on 07-26-2011 11:55 AM
Hi,
I am facing an error while triggering infopackage of copa, error is Error occurred in the data selection .
can any one suggest me what is the reason of the error and steps to resolve it.
thanks,
Bharath.
Hi,
Might be their any issue with extraction job in source system please check whether the related job is in release state,if so schedule it so that it goes in active mode.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
Can you check the mapping of source system field with the infoobject in Transformation logic.
Or you can check by doing this
"This can occur due to either bug in the info package or incorrect data selection in the info package.
Data selection checked in the info package and job is started again after changing the technical status to red and deleting the error request from the data target"
Thanks,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Replicate the data source once and try extracting the data again and verify the R3 Job related to data extraction.
If the error still persists, Check whether you are getting data records in R3 system in RSA3.
If you are getting records in RSA3, then it may be the authorization issue with background user used in RFC.
Provide the necessary auth to background user and proceed further.
Regards,
Rangz
Hi,
RSCUSTV6 is used for PSA partitioning
Please refer the below threads
[http://wiki.sdn.sap.com/wiki/display/profile/BWsystemtuning]
By Using T Code RCUSTV6 is usefull for Package Size and Partition size esp..
Frequency with which status Idocs are sent
Dependencies
.
Standard settings
Frequency 1 means, for example, that there is an Info IDoc for every data IDoc. In general, you should choose a frequency between 5 and 10 but not greater than 20.
Recommendation
The larger the packet size for a data IDoc, the smaller you should set the frequency. By doing this, you make it possible to get information on the respective data load status in relatively short time periods when uploading data.
PACKET SIZE
Number of Data Records per Package
This option refers to the number of data records that are delivered with every upload from a flat file within a packet. The basic setting should be between 5000 and 20000 depending on how many data records you want to load.
Activities
If you want to upload a large quantity of transaction data, change the 'number of data records per packet' from the default value of 1000 to between 10000 (Informix) and 50000 (Oracle, MS SQL Server).
Dependencies
The data packets can be imported in parallel in BW in the background. With an improved use of system resources (uploading is divided up into several work processes), uploading in parallel is the most cost-effective from a performance point of view.
Recommendation
You should not divide up the quantity of data into too large a number of packets since this reduces performance when uploading. The number of data packets should not be more than 100 per loading process.
Size of PSA partition
You can determine here after how many records you want to create a new partition. By default, this value is set to 1,000,000 records
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The data size might have crossed the threshold limit. RSCUSTV6
Regards,
Suman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.