Data selection error - peculiar problem

Hi Experts,
I have done a delta initialization with the selection as 05.2006 under the "from" field for "0calmonth".
I assumed that in the delta, the data will be loaded further from this date as i have not given any end date in the "to" field.
The delta loads are being done daily, and the data was being added in the infocube, but when we checked out the data in the cube there is no data for the june month(06.2006). And the selections fields in the "infopackage" and the "request tab" of the manage data screen show "05.2006" as the selection criteria even for the delta loads.
Now how can i get the data for the 06.2006 month without disturbing the delta, and can i change the initialization selection criteria.
Does the deletion of initialization in the infopackage effect the initial request and the delta loads in the cube.
Any help will be highly appreciated.
thanks & regards.

Hi brother(roman),
lots of thanks for ur prompt response.
just a simple clarification, i gave only the from date and not the to date, even then there were daily delta uploads only for the month of 05.2006.
how come this happen with out any changes in the data for that month in the source system being updated, but the records were being updated in the BW.
what might have occured.
thanks & regards

Similar Messages

Error in the Data Selection - Errors in Source System RSM 340

Hey Everyone,
I'm having an issue with loading a Delta for 0MAT_PLANT_ATTR. This is the second night it has happened, where I get the error "Error in the Data Selection". This error happens in the EXTRACTION part of the Monitor. And, we cannot run another Delta to see if it'll work, we have to delete the old Delta Init, and run a new one. The other error is "Errors in Source System - RSM340". That's as much it gives.
Could anyone suggest why this would be happening? I checked RSA3 in R/3, and no errors on the extraction. I also checked sm37 against the job that loads that data, and it completed successfully. I honestly don't think there's an issue with the data. We cannot have this happen often, and I just need to know if this is something that can be corrected.
Thanks,
John

There is nothing wrong with the TID's or anything like that. There is also no selection criteria in the infopackage.
When the Delta fails, the error occurs under EXTRACTION in the monitor. It seems to be successful under TRANSFER and PROCESSING in the monitor, which I find strange. Also, I run a new Delta Init with Data Transfer, and that works just fine.
So, I'm not sure what it could be?

Date selection error BI4 infoView

Hello community,
I’m facing a problem here and I am looking for your help
After migration to BI 4 I faced a problem with date selection prompt (In infoView) when I open or refresh a report.
For example, If I select 02/02/2013 00:00:00, the system change the input to 01/02/2013 23:00:00.
This is very urgent please help me

This is a bug in 4.1 which is logged with ADAPT01710199
Check the note below
930605 - BI4.1 - The time stamp in the prompt is changing every time on refreshing the report in HTML Mode of WebI Report
Following are the fixes for Business Intelligence Platform 4.1
BI 4.1 SP01 Patch05
BI 4.1 SP02 Patch01
BI 4.1 SP03
BI 4.1 SP03 Patch1
BI 4.1 SP04
For a possible workaround, the Java Application server hosting BI Launchpad can be set to run using the UTC timezone to prevent time offsets in the prompt.

Data Selection error

When i execute the infosetquery(sq01),it shows "no datawas selected".But when I check in SE16 by giving table name it showsthe number of enteries for patricular dates,and also i check in ODS by right click and manage,
showing data for particulr dates..here data was loading
in fullupdate..
Unable to get where the problem?

Hi BPNR,
Do you want to do a inner join or a outer join? Try changing the join to outer if you have defined it as an inner join to see if you get rows back.
You can change this by right clicking on the row that has been joined to, and choosing the join you wish to perform.
Cheers! Bill

"Error Occurred in the Data Selection" while excuting InfoPackage for DataSource(ORT_PA_TRAN_CONTROL)

Hi,
Can anyone help me out with the data selection error in InfoPackage, while I was trying to extract the DataSource(0RT_PA_TRAN_CONTRL) to BW./
I've tried with "Init With Data Transfer" and without the use of Conversion Routines.
Thanks,
Taehoon.

Hi,
Why your using conversion routine at info pack level?
Actually conversion routine already defined for info object 0MATERIAL, general tab.
at info pack level, remove conversion routine MATN1 and don't give any selections.
First try to run data source at source system RSA3. if it works then later you can trigger at info pack level without any selections.
Thanks

Unable to change date selections in data selection tab

Hi experts,
I'm new here, i scheduled the init load with date selections in the data selection tab, i successfully loaded the data and now i want to go for the delta but i'm unable to delete the date selection in the data selection tab. what problem is this.
can we load the data with the same selections in delta update ? how can we delete the date selections
orelse nothing happens even if there is a selection in the data selection tab? the date is a past one.
help me out plz
regards

delta loads copy the selections from the init load.
Often while scheduling delta loads u will see a message 'selections copied from the last init load'.
cheers,
Vishvesh
Message was edited by: Vishvesh

Error occurred in the data selection

Hi Expert,
I met issue when full loading data from R3 via customized datasource.
the error message in request monitor is:
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
I checked in RSA3, the data extraction is successful, but in BW, when execute the infopackage with or without data selection, both failed due to the same error.
I also checked the background job in SM37 in source system, the background BI* completed successfully, and the IDoc in both BW and source system processed successfully.
I also tried to replicate datasource and activate is using RSDS_DATASOURCE_ACTIVATE_ALL, delete infopackage and recreate it. but seems all this didn't work.
Could u pls tell me how to solve this issue? Thanks.
Eileen

Hello Eileen zhang,
I have exactly the same error as you, do you still remember how did you solved this problem?
Regards,
Thanks,
Maria João
Error message:
"Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request."

Cube to Cube "Error in data Selection" plz help

Hi this is Ajay Reddy
when am sending data from Cube to Cube am getting an error
"Error in data Selection" plz help

Hi,
It needs a Note implementaion. I got similar problem in version BIW 7 and SP 11. We got the solution with on of the note . I am not able to recollect the note number.
Any way check the notes 920971,155471 may help you or not.
With rgds,
Anil Kumar Sharma .P

Error occured in data selection!

Hi,
data request was failed in my case when i schedule the data .
in details tab of monitor screen , under extraction it is saying " error occured in data selection".
while scheduling, i had given only one selection range of the many available fields.
is it mandatory that we should select all the available selection values?
can any body here tell me what could be the problem?
Ravi

This would occur when corresponding job of BW is running at R/3 side.
How to identify that ?
1] find sm37 of BW job.
2] double click the job, click on 'job details' from tool bar.
3] from the pop up screen, note down the server and job id.
4] log in to R/3, tcode SM51. Double click the server which is mentioned in above step.
5] a list of running job would appear, find the job from job id as in step 3. double click that and clikc on cancel program to kill the job.
NOTE - if the job is already over then it would not appear in list..
now you can repeat the load.
this works, i have tried it.

Error occurred in the data selection,If i do Repeat, then it is working fin

Hi Freinds,
Here is the error message,
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Details Tab:
Extraction (messages): Errors occurred
Error occurred in the data selection ....
If i do Repeat Delta, then it is working fine.
As it is a daily load, manually repeating the load from the past 10 days.
Have tried using program RS_TRANSTRU_ACTIVATE_ALL.
Any inputs pls.....

Hi Friends,
Thanks for your valuable inputs, Problem is solved.
The Reason is that, there is a time difference in the r/3 system and bi system.
The tolerable time differene shud be only 60 seconds.
Basis guys took down time at the OS level and hav made the timers sync.....
The problem is on the source system GNP time differences
persists, which can cause the problem with delta upload .
Universal Time Coordinated UTC....: 1291187626
Date and time of database.........: 01.12.2010 12:46:59
Date and Time of R/3-Kernel.......: 01.12.2010 12:43:46
Date and Time of ABAP-Processor...: 01.12.2010 12:46:58
ABAP Time zone Setup ..............: 19800
Date and Time / local time ........: 01.12.2010 12:43:46
This leads to an exception of the delta processing, because this
tolerates a deviation of 60 seconds only (When the repeat is processed,
the "local time" in the ABAP is higher than the qrfc counter at the time when the delta was processed -> So a repeat works fine).
Please synchronize the timers like described in attached note 101726 and 741734 to eliminate the time difference .
With Regards
Badri Thiriveedhi.

Error occured in the data selection while extract data from Source system

Hello Friends
i am facing Problem while extracting data to Biw System from SAP R/3 system
The error mesage is 'Error occured in the data selection '
i.e. Monitoring - Details tab - Extraction - With error

Hi
The delta wil take the Last init selection for loading data in to the BW...
Did u check the IP at the Update tab is it the correct delta only.. or its a full..
better to go to the RSA3 and check the extractor in the Delta mode .. if u give ur delta mode it automatically takes the selction options.. so please try in RSA3..
regards
CK
PS: CHECK THE INIT SELECTIONS TOO or do an init with outdatatransfer and perform the delta...
Message was edited by:
BW Star

Runtime Error during Phase Start Data Selection

Hello Forums,
We are using TDMS (2006_1_700) to extract a year's worth data from one client into a new client on the same ERP EhP4 system.
All the systems - central, sender and receiver are at the same DMIS levels(SP16) and all necessary notes have been applied.
During the Step 'Start Data Selection' of the Data Transfer Phase, we see around 60 of the ~12000 sub tasks abort with the below error:
Batch job for access plan calculation in sender system ended with errors
Message no. DMC_UTIL_MSG021
Diagnosis
The access plan calculation was executed as a background job in the sender system. In this background job, an error occurred.
Procedure
Check if a short dump occurred in the sender system while the access plan was calculated. If existing, this short dump contains further information about the cause of the problem.
A frequent error is that selection criteria for data reduction (for example selection groups) are wrongly defined which causes the database access that consideres these selection criteria to fail.
The corresponding dump in the Sender system is as below:
Runtime Errors         SAPSQL_WHERE_PARENTHESES
Exception              CX_SY_DYNAMIC_OSQL_SYNTAX
Error analysis                                                                                |
|    An exception occurred that is explained in detail below.                                      |
|    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not                |
|     caught in                                                                                |
|    procedure "/1CADMC/DMCACS00P000000001" "(FUNCTION)", nor was it propagated by a               |
|     RAISING clause.                                                                              |
|    Since the caller of the procedure could not have anticipated that the                         |
|    exception would occur, the current program is terminated.                                     |
|    The reason for the exception is:                                                              |
|    The current ABAP program has tried to execute an Open SQL statement                           |
|    which contains a dynamic condition. The part of the condition specified                       |
|    at runtime is incorrectly parenthesized.
Please suggest in case any of you have encountered similar error and possible resolution.
Thanks in advance,
Srikishan

Hi Suman,
Thanks a ton. I somehow missed this when searching on the SMP.
I will implement the steps and post it back by tomorrow.
Regards,
Srikishan

Extraction Error: ERROR occured in the data selection

Hello everybody,
I have made configurations for the BW connectivity. Finally I was able replicate data sources from R/3 to BW. But when I try to extract the data its giving me the error. In monitor details, in extraction node its showing like "Error occured in data selection."
Its not giving me any more messages. I think the problem is with the BW connectivity configurations. Its my guess only. Is that right? But I am able to replicate my data sources.
Please help me.
Thanks in advance.

Hi:
1)Try the RSA3 extractor in R/3.
2)Try simulate load in InfoPackage.
If RSA3 is good, and infopackage is giving error, then its connectivity.
Also, create another infopackage and try again just to make sure.
Ram Chamarthy

Peculiar problem in LDB ADA with company code selection

<h5>Hello Colleagues, </h5>
Faced a peculiar problem with company code selections in LDB ADA. Entered depreciation area, dep posting perios, lower and higher value of company code and would like to except few companies from selections. On pressing extension button, error message "Depreciation area 01 is not defined in chart of depreciation" is popping up and not allowing to provide exceptions for company codes. But working well in development systems. We are using ECC 6.0 systems and in both systems we have same lines of code for SAPDBADA.
During debug, found that in development system, control coming to initial statements after PAI event. But in other systems, control skips few initial commands after PAI and directly jumps to later commands. Due to this FNAME parameter in PAI subroutine setting with '*' in other systems and 'BUKRS' in dev system.
Could anybody give me some thoughts of why system behaving differently?
Thanks and Regards,
Prasanth

Some - or most? - ODBC driver, especially MS for SQLServer and Access, don't support these advanced JDBC features.
Like the messages says: they are optional features, and the driver doesn't implement them.
A good news:
you don't need them.
Just go through your ResultSets only forward by next(), and do all inserts, updates and deletes with executeUpdate() and SQL commands.

Process chains-Error occurred in the data selection-DBIF_RSQL_TABLE_UNKNOWN

Hi All,
The problem occurred in PC which was running smooth until now
Now I am getting message:
in BI : Error occurred in the data selection
When I went in R/3 it shows DBIF_RSQL_TABLE_UNKNOWN
Probably the only way to eliminate the error is to correct the program.
Please check the entries in the system log (Transaction SM21).
Internal call code.........: "[RSQL/READ/PA0009 ]"
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
DBIF_RSQL_TABLE_UNKN
SAPLXRSA" or "ZXRSAU
EXIT_SAPLRSAP_002"
Can anyone explain..

Hi ,
Check note 950317.
also check the blow forum having same kind of discussion :
Runtime Errors DBIF_RSQL_TABLE_UNKNOWN
Short dump error DBIF_RSQL_TABLE_UNKNOWN
DBIF_RSQL_TABLE_UNKNOWN
thanks,
Deepak

Data selection error - peculiar problem

Similar Messages

Maybe you are looking for