Question Re: Errors in source system Message no. RSM340 in Technology Q&A

Errors in source system Message no. RSM340

Former Member — Fri, 13 Jan 2012 10:59:55 GMT

Hi Experts,

The below is the issue;

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.

This is delta load and it is failing daily from the recent times. A repeat of delta is successful. Again the next day normal delta is getting failed with the same error and again I have to repeat it. No short dump, no system log is generated in both the BW as well as R/3 system. The job in R/3 is in finished status. But it is not extracting any records.

1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA

IDOC: Info IDoc 2, IDoc No. 12920038, Duration 00:00:00

IDoc: Start = 01/13/2012 01:44:56, End = 01/13/2012 01:44:56

Synchronized transmission of info IDoc 3 (0 parallel tasks)

IDOC: Info IDoc 3, IDoc No. 12920041, Duration 00:00:00

IDoc: Start = 01/13/2012 01:47:14, End = 01/13/2012 01:47:14

Job finished

I have seen only few related issues which said, there could be time inconsistencies, but did not find the exact solution. I have checked OSS note: 1576331 but could not resolve. Also the extractor check for this datasource is also giving the error "Errors occurred during the extraction - Message no. RJ012". We have this issue in production system only and this started from recent days.

Please help me on this.

Sunil

Re: Errors in source system Message no. RSM340

john_lang — Sat, 14 Jan 2012 11:25:34 GMT

Hi Sunil,

1. Is your nightly load process chain trying to execute too many parallel jobs? The symptoms you describe are indicative of too many queued jobs for processing in the BW side. Ever since BW v2 there has always been an imtermitant bug in the queueing of background jobs related to extractors where the transfer of DataPackets will just silently disappear when BW is processing too much. Try re-arranging your process chain to ensure less resources are being used while that job runs. Did that make a difference?

2. How clean is the process chain design? Is the system trying to process an attribute change run on that cube when the transaction data load begins? This will pause any DataPacket processing within BW.

Yes, your error message says that the problem is in the source system but that could just be the extractor program in the source system not getting all of its idoc messages as expected from BW. The above 2 suggestions might not be the cause of your specific issue but you can at least eliminate these known causes from your investigation.

3. Are you using the PSA? If you are using the PSA then point 2 above (Attribute change run) is not the cause of the issue.

Kind Regards,

John.

Re: Errors in source system Message no. RSM340

Former Member — Sun, 15 Jan 2012 06:23:56 GMT

Hi John,

1. Yes, these loads are the part of nightly chain. But we are facing this particular issue from one week and before that loads were running smoothly. There was no change made to R/3 system also. So the design of the process chain may not be the cause.

2. Yes, these loads use PSA for staging.

As a first approach we have replicated the datasource and activated the transfer rules to see if this resolves the issue. I will let you know regarding the results soon.

Thanks & Regards,

Sunil

Re: Errors in source system Message no. RSM340

Former Member — Sun, 15 Jan 2012 08:25:11 GMT

hi,

try RSRV check.. see if you can get something

OSS note Note 1229437 can be helpful to you also since you mentioned when doing extractor it gave issue try debugging the code espically recent .append code segements even after replication doesnt work out

regards

laksh

Re: Errors in source system Message no. RSM340

Former Member — Mon, 16 Jan 2012 08:27:34 GMT

No results after replicating and activating. Still the same problem.

This issue is happening with various delta loads i..e one day one delta is failing and other day some other delta load fails and the next day both the delta loads fail with the same mentioned error. A repeat of those getting successful.

Please help.

Sunil

Re: Errors in source system Message no. RSM340

Former Member — Fri, 20 Jan 2012 10:40:21 GMT

Hi Experts,

Resolved.

OSS note "1576331 - Delta loads fail in the load monitor(RSMO) for timestamp based datasource's with 'Errors in source system' Message no.RSM340" helped to resolve the issue.

I ran the report RSDBTIME in R/3 system and found the time differences. Sent the OSS note to BASIS team. They corrected the time differences.

Thanks and Regards,

Sunil

Re: Errors in source system Message no. RSM340

Former Member — Fri, 25 May 2012 17:59:55 GMT

Hello Sunil Kumar,

Could you please explain how did you found the difference as I'm also facing same issue caller 09. I also ran the report in BI using SE 38, program RSDBTIME and also in R/3 system. There is time difference, but which time r u considering and what should I tell to Basis. Please reply me ASAP, appreciate it.

Thanks

Victor

Re: Errors in source system Message no. RSM340

shaik_sajeed2 — Tue, 12 Feb 2013 05:33:20 GMT

HI we also face same kind of error in our system.please run the RSDBTIME in your apllications system

then you will come to know that the system are in same time zone but they are not synchonized with each other ,their must delay between the systems.

So ask the basis people to apply the OSS note1576331.I hope it solves your problem.

Re: Errors in source system Message no. RSM340

Former Member — Thu, 28 Feb 2013 06:12:39 GMT

Hi Sajeed,

when run the RSDBTIME in both systems (ECC and BI) it saying that "No Time Inconsistencies detected". However Error is the same (Error in Source System Message no.RSM340)

Please kindly advise

Regards,

Somesh

Re: Errors in source system Message no. RSM340

Former Member — Tue, 05 Mar 2013 16:09:16 GMT

Hi,

We are having exactly the same issue.

RSDBTIME doesnt find any problem in the timstamp and our processes sometimes doesnt work for the first time only after repeat.

Did you find a solution for this problem?

Thanks,

Amir

Re: Errors in source system Message no. RSM340

Former Member — Fri, 12 Apr 2013 05:34:43 GMT

Hi ,

I am also facing the same issue where the Alternative Delta load is failing giving the same error message and RSDBTIME is also not giving any Time Inconsistencies .

Did you find a solution to this issue? If Yes , would request your reply as soon as possible.

Thanks.

Re: Errors in source system Message no. RSM340

Former Member — Mon, 15 Apr 2013 05:45:19 GMT

Hi,

In the end we found a small gap of time (less than a minute) in RSDBTIME and it fixed our problem.

Thanks,

Amir

Re: Errors in source system Message no. RSM340

salnuaimi — Tue, 05 Dec 2023 09:54:29 GMT

i am having the same issue but using DBCONNECT datasource. any clue how to proceed here? thanks