Job terminated in source system - Request set to red during delta load

Hi All,
There is issue with the delta load where as full load works fine and it results in below job termination with below log.
Job started
Step 001 started (program SBIE0001, variant &0000000128086, user ID ALEREMOTE1)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 2LIS_13_VDITM
RLOGSYS    = BWP_010
REQUNR     = REQU_DA9R6Y5VOREXMP21CICMLZUZU
UPDMODE    = R
LANGUAGES = *
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 0                                       *
abap/heap_area_total.......... 17173577728                             *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 3000000                                 *
ztta/roll_extension........... 2000000000                              *
Object requested is currently locked by user ALEREMOTE1
Job cancelled after system exception ERROR_MESSAGE
Please help me to resolve this issue.
Thanks,
Madhu,

Hello,
As per the screen shot provided below, data soruce belongs to LO, so first check in RSA7, whether it has got mark in RSA7, for which you have entries in RSA7 against the data source. If you are not able to find the data source in RSA7, then you need to set-up the update methods, based on the requirement.
1) Direct Delta
2) Queued Delta
3) Unserialised V3 Update
Once it is done, Delete the Previous Initilisation, again perform the Re-Init With Out data and now schedule the Delta Data Loads
Hope this may Help you.
Thanks
PT

Similar Messages

Job terminated in source system -- Request set to red,SAPSQL_SQLS_INVALID_

Hi All,
can any one help on this issue.
I run the BI statistics in production and found out the error while triggering the delta's
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.
Error msg : Job terminated in source system --> Request set to red
Message no. RSM078
Job started
Step 001 started (program SBIE0001, variant &0000000000756, user ID
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0TCT_DSA1
RLOGSYS = BCLNT300
REQUNR = REQU_D4GZHNLA3PSQ7XRNGL0EMV6AP
UPDMODE = D
LANGUAGES = *
Current Values for Selected Profile Parameters *
abap/heap_area_nondia......... 0 *
abap/heap_area_total.......... 2147483648 *
abap/heaplimit................ 40894464 *
zcsa/installed_languages...... ED *
zcsa/system_language.......... E *
ztta/max_memreq_MB............ 2047 *
ztta/roll_area................ 3000320 *
ztta/roll_extension........... 2000683008 *
ABAP/4 processor: SAPSQL_SQLS_INVALID_CURSOR
Job cancelled
But delta laoding for same is working in DEV...but not in prod...
Please suggest
Regards
Shweta

Swetha
finally found out the notes.
Please look into them and ask you basis to implemnt,
1161940
1106569
1145041
1146851
Please have a look and ask for implemtation in your system which are suitable for you
We also faced the same issue job termination in source system for BI Statistics
Regards#
Srini

Job terminated in source system -- Request set to red

Hi Developers and supporters can you any one help me.
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
Date        Time      Message
13.10.2010 16:48:01 Job started
13.10.2010 16:48:01 Step 001 started (program SBIE0001, variant &0000000024579, user ID RFCUSR)
13.10.2010 16:48:01 DATASOURCE = 0ACTIVITY_ATTR
13.10.2010 16:48:01 *************************************************************************
13.10.2010 16:48:01 *          Current Values for Selected Profile Parameters               *
13.10.2010 16:48:01 *************************************************************************
13.10.2010 16:48:01 * abap/heap_area_nondia......... 2000683008                              *
13.10.2010 16:48:01 * abap/heap_area_total.......... 2000683008                              *
13.10.2010 16:48:01 * abap/heaplimit................ 40894464                                *
13.10.2010 16:48:01 * zcsa/installed_languages...... 6EDGIJL                                 *
13.10.2010 16:48:01 * zcsa/system_language.......... E                                       *
13.10.2010 16:48:01 * ztta/max_memreq_MB............ 256                                     *
13.10.2010 16:48:01 * ztta/roll_area................ 6500352                                 *
13.10.2010 16:48:01 * ztta/roll_extension........... 2000683008                              *
13.10.2010 16:48:01 *************************************************************************
13.10.2010 17:57:09 ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
13.10.2010 17:57:09 Job cancelled

Hi SUSUSU,
The dump is related to temp table space issue.check the space for PSATEMP table.
Use tcode DB02 to check the table spaces, in the tree diaplayed on you left. try to see the % used for your ODS & FACT tablespaces. Incase the % are too high like 99% etc, get in touch with you BASIS team.
Request your basis team to increase the PSATEMP table space.
Or
Decrease the data packet size and run the info package.
to decreae the packet size -- in the IP screen menu --> schedular -->Datasource setting for sending data --> there change the parameter Maximum size of a data packet in kByte.
down you can find the area to enter the data packet size .
for ex if it is 20000 decrease it to 10000 and run the info package

RSM 078- Job terminated in Source System - Request set to Red

Hi,
We upgraded our system from BW 3.5 to BI 7.
Now when we load DELTA from one ODS to another ODS(within BW) through process chain i get above error message.
I manually deleted this requests from receiving ODS and repeated the delta and it works fine. But when i reload another Delta it fails again with the same error.
The error message suggests problem in the source system, however, we are moving data within BW.
Any ideas
Thank you
Umang

try to re-generate export data source again and do the delta. And also make sure the self source system is also active.
thanks.
Wond

Job termination in source system

Dear All,
I am trying to load payroll data using Datasource ZHR_PY_1 . I am doing init data for the first time using infopackage for this datasource. I have tried to pull a couple of years, 2 months, even 1 day of data, but all give me the same error.
The error is
1.The request turns red after a couple of hrs pulling zero records.
2. Error Message says Job terminated in source system.
3.Step by step analysis says
red - data selection successfully started
red - data selection successfully finished
red - processing error in source system.
Error says "error occured in data selection"
If I go to RSA7 in R/3, datasource ZHR_PY_1 has yellow status.
RSA6 shows everything active.
Can anybody make out what may be the reasons why BI system is not able to connect to pull R/3 data.
Regards,
Jack

Hi,
Some times the source system needs a lot of time to "prepare" the output records and will got through a lot of tables before getiing any result how small it may be.
But also try the options as given by the others consultants (as RSA3, checking the system connection, replicate and activae data source again.)
Your can also use tx SMQ2 u2013 qRFC-monitor in R/3 to see what happened.
Success,
Udo

Reg: job termination in source system

hi experts
can anyone tell me solution for this problem after loading infopackage, status of the infopackage is showing is like this "job termination in source system", but i checked with ss it showing job gets cancelled. but i am not assigned any to the data source, so how can eliminate this problem.
regards
harikrishna.N

HI
This can happen when request IDOC is sent source system, but the source system for some reason is not available.
Ensure that source system is available. Change technical status of request to red and delete request from datatarget. Trigger Infopackage again to get data from source system.
Cheers,
Raj

Job Termination in source system-Dataload failure

Hello Forum,
We are on BW 3.1 and our source is SAP R/3 Enterprise.
We have been facing a recurring problem for a dataload, that is JOB TERMINATION IN SOURCE SYSTEM.
Details of the load:
Target:Master Data
Full load
Processing: PSA and InfoObject table in se

Sorry, it got posted before I completed it.
Please find the full details here:
Hello Forum,
We are on BW 3.1 and our source is SAP R/3 Enterprise.
We have been facing a recurring problem for a dataload, that is JOB TERMINATION IN SOURCE SYSTEM.
Details of the load:
Target:Master Data
Update Mode: Full load
Processing: PSA and InfoObject table in series
Selections: None
Records Check:Terminate if errors occur; Aggregation permitted
Character Check: Switched off
This has been delaying the loads for a long long time.
Could you please suggest us the ways to fix this problem?
Thanks is advance,
Raj

RE:JOB TERMINATED IN SOURCE SYSTEM.

Hi Gurus,
In production environment while we are trying to load data we recived follwing 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.
We tried RFC checks, repliacted Data source and activation in BI and all other checks.It seems all OK in BI.When we tried to activate the Data Source in CRM(back end) transation RSA5 its prompting for Work Bench request.my question is are we allowed to create work bench request in production environment? This happens to us even in BI when we try to run an Info package manually I.Can you please advise me what could be othr reasons for the job failure.

Hi
We tried RFC checks, repliacted Data source and activation in BI and all other checks.It seems all OK in BI.When we tried to activate the Data Source in CRM(back end) transation RSA5 its prompting for Work Bench request.my question is are we allowed to create work bench request in production environment? This happens to us even in BI when we try to run an Info package manually I.Can you please advise me what could be othr reasons for the job failure.
Hope you have checked RFC at Source system side SM58/59/66 and IDOCs BD87,WE05 also.
Yes some times it will prompt the Work Bench Request at Source system side too. But do not create any new request for this. Try to see for the Request locks -- Check back with BASIS team for this-- Happens if the 2 or more process/jobs trying to hit at same point this will happen.
Better to cancel/delete the present request and Repeat Delta.
Hope it helps

Job termination in source system /Asynchronous transmission of info IDoc 2

Hi All,
We have certain loads that we do every 2 hours, which will run for 20 to 30 minutes to load current year BCS data into a Basic Cube. So, In total we schedule 12 times in a day. This is needed as we have users around the globe.
We have totally 10 BGD processes and 10 Dialog processes.
These loads are scheduled through a process chain and we submit three parallel jobs at a time based on the version and in total we have 15 loads, 5 per each parallel job.
We went live with this process yesterday and the jobs ran all well until today afternoon, when they started giving the following message and when I checked the log of the process chain, one of the InfoPackage did fail with job termination in the source system.
The job log is as follows:
Date       Time     Message text                                                                 Message class Message no. Message type
06/20/2007 13:55:47 Job started                                                                       00           516          S
06/20/2007 13:55:47 Step 001 started (program SBIE0001, variant &0000000014146, user ID RFCUSER)      00           550          S
06/20/2007 13:55:47 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)          R3           413          S
06/20/2007 13:55:47 DATASOURCE = 80BCS_VC10                                                           R3           299          S
06/20/2007 13:55:47 *************************************************************************         R8           048          S
06/20/2007 13:55:47 *          Current Values for Selected Profile Parameters               *         R8           049          S
06/20/2007 13:55:47 *************************************************************************         R8           048          S
06/20/2007 13:55:47 * abap/heap_area_nondia......... 2000683008                              *        R8           050          S
06/20/2007 13:55:47 * abap/heap_area_total.......... 2000683008                              *        R8           050          S
06/20/2007 13:55:47 * abap/heaplimit................ 40894464                                *        R8           050          S
06/20/2007 13:55:47 * zcsa/installed_languages...... EFD                                     *        R8           050          S
06/20/2007 13:55:47 * zcsa/system_language.......... E                                       *        R8           050          S
06/20/2007 13:55:47 * ztta/max_memreq_MB............ 2047                                    *        R8           050          S
06/20/2007 13:55:47 * ztta/roll_area................ 3000320                                 *        R8           050          S
06/20/2007 13:55:47 * ztta/roll_extension........... 2000683008                              *        R8           050          S
06/20/2007 13:55:47 *************************************************************************         R8           048          S
06/20/2007 13:58:04 NONE                                                                             UGBW          001          E
06/20/2007 13:58:04 Job cancelled after system exception ERROR_MESSAGE                                00           564          A
I do not have acceess in BWP to get you the Data Transfer Parameters within BW system.
Any suggestions would be greatly appreciated.
Thanks & Best Regards,
- Shashi

Hi Shashi,
Check in st22 for any dumps, do you have any pointer there?
Also check sm21 to identify possible cause of errors.
Regards.

Job terminated in source system SAPSQL_SQLS_INVALID_CURSOR

Hi all,
can any one help on this issue.
I run the BI statistics and found out the error while triggering the delta's
Job started
Step 001 started (program SBIE0001, variant &0000000000756, user ID
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0TCT_DSA1
RLOGSYS    = BCLNT300
REQUNR     = REQU_D4GZHNLA3PSQ7XRNGL0EMV6AP
UPDMODE    = D
LANGUAGES = *
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 0                                       *
abap/heap_area_total.......... 2147483648                              *
abap/heaplimit................ 40894464                                *
zcsa/installed_languages...... ED                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 3000320                                 *
ztta/roll_extension........... 2000683008                              *
ABAP/4 processor: SAPSQL_SQLS_INVALID_CURSOR
Job cancelled
Edited by: BW User on Nov 10, 2008 11:41 AM

Hi Arun,
Source system is also BW itself..No idocs have been archived.
For other BI statistics its running fine only for this one,,,,it is getting error.
If i didi INIT W/O data tarnsfer and running the delta,,,delta is failing
If i did INIT With data then 20000 records are comming after trying to run the delta again the same error is ocmming
Regards

Long running job in BW source system - Urgent

Hello,
While loading BW data delta load for data source 0CO_OM_CCA_9 the
corresponding R/3 job is taking the long time to complete approximately
3 days.
When we checked the Job log in the Source sytem we found the following
entry
"2 LUWs confirmed and 2 LUWs to be deleted with function module
RSC2_QOUT_CONFIRM_DATA"
and job is taking too much time to complete this task.
Can you please help me out to resolve this issue at earliest?
Best Regards

Hi Venkata,
When you check indexes in SE11 -> COEP -> Index 4
You may see the status as "Active", but did u check the line below ?
it should read
"Index COEP~4 exists in database system"
If it reads
"Index does not exist in database system" , then the INDEX 4 is not active and not used.
Cheers,
Praveen.

Job is taking too much time during Delta loads

hi
when i tried to extract Delta records from R3 for Standard Extractor 0FI_GL_4 it is taking 46 mins while there are very less no. of delta records(193 records only).
PFA the R3 Job log. the major time is taking in calling the Customer enhacement BW_BTE_CALL_BW204010_E.
please let me know why this is taking too much time.
06:10:16 4 LUWs confirmed and 4 LUWs to be deleted with FB RSC2_QOUT_CONFIRM_DATA
06:56:46 Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 193 records
06:56:46 Result of customer enhancement: 193 records
06:56:46 Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 193 records
06:56:46 Result of customer enhancement: 193 records
06:56:46 Asynchronous sending of data package 1 in task 0002 (1 parallel tasks)
06:56:47 IDOC: InfoIDOC 2, IDOC no. 121289649, duration 00:00:00
06:56:47 IDOC: Begin 09.05.2011 06:10:15, end 09.05.2011 06:10:15
06:56:48 Asynchronous sending of InfoIDOCs 3 in task 0003 (1 parallel tasks)
06:56:48 Through selection conditions, 0 records filtered out in total
06:56:48 IDOC: InfoIDOC 3, IDOC no. 121289686, duration 00:00:00
06:56:48 IDOC: Begin 09.05.2011 06:56:48, end 09.05.2011 06:56:48
06:56:54 tRFC: Data package 1, TID = 3547D5D96D2C4DC7740F217E, duration 00:00:07, ARFCSTATE =
06:56:54 tRFC: Begin 09.05.2011 06:56:47, end 09.05.2011 06:56:54
06:56:55 Synchronous sending of InfoIDOCs 4 (0 parallel tasks)
06:56:55 IDOC: InfoIDOC 4, IDOC no. 121289687, duration 00:00:00
06:56:55 IDOC: Begin 09.05.2011 06:56:55, end 09.05.2011 06:56:55
06:56:55 Job finished
Regards
Atul

Hi Atul,
Have you written any customer exit code . If yes check for the optimization for it .
Kind Regards,
Ashutosh Singh

Deletion of request from init option for source system

Hello Experts,
Iam using 3 IP.
IP for init load with data transder, IP for init load without data transfer & Delta.
now with data transfer IP is not used.
i trigered "without data transfer IP", then accidentally "triggered with data transfer IP".
then manually made the request red & deleted data by right clicking datasource-->manage & deleted all the requests(2) available.
now before i load init without data transfer request exists in "init option for source system".
when trying to delete IP
"There are active init selections in source system for this data source. Therefore, only ALL init selections can be deleted at once. Do you want to delete all init selections (all channels)?"
when i choose yes....it takes a long time & gives run_time error status.
Guys, this issue is solved.
I deleted the without data transder first.
now when I load delta, I got error.
"Job terminated in source system --> Request set to red"
regards
KV
Edited by: K V on Apr 10, 2009 2:16 PM

Hi KV.........
U r doing init without data transfer..............it means it will not pick any records...........it will just set the init pointer and along with that Delta queue will get generated.........after that whenever any changes will be done.........or any new records will come.......it will get reflected in the Delta queue.......
So next time when u run the delta load..........data will be fetched from the Delta queue...........
So check the delta queue.......it may happen that there r no new or changed records..................
So check............may be delta queue is 0..............
Also check the update mode for the datasource in LBWE(if Logistic datasource)............if the update mode is Queued delta or unserialized V3 update........then data will first get accumulated in the Extract queue(LBWQ) or update table respectively.............so to fetch records in the Delta queue u hav to schedule the V3 jobs in LBWE............otherwise Delta queue will be empty and fetched records will be 0........
Regards,
Debjani......

Error with source system

hi alll,
I am working with BI.In that i am getting the following error while scheduling
"Job terminated in source system --> Request set to red"
no other error messages are displayed.any one know the reason why i am getting like this plz post reply..
thanks in advance
Naga

Hi,
The job has been been terminated in the source system.
Go to the source system sm37 and see the cancelled job list for the user name remote user name,
when we run an infopackage in the bw it will trigger a collection job in the source sytem so that collection job has been terminted in the source sytem
kindly c the job log and also the short dumps in st22.
Kindly tel us the message in that short dump r reason for cancellation int he job log
so that we can comment on that
Hope this helps
Janardhan Kumar

Dump in source system?

Hi all ,
i am loading the master data attributes full load , i got the short dump error in source system
says that ,
Job termination in source system
Diagnosis
The background job for data selection in the source system has been terminated. It is very likely that a short dump has been logged in the source system
Procedure
Read the job log in the source system. Additional information is displayed here.
To access the job log, use the monitor wizard (step-by-step analysis) or the menu path <LS>Environment -> Job Overview -> In Source System
Error correction:
Follow the instructions in the job log messages.
in the ST22 the error message is
unable to interpret "99.79 kg " as a number .
my questions is how to identify that particular record in source system , and how to correct it .
Thanks ,

Error analysis |
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was not
caught in
procedure "PUT_INTO_DATA" "(FORM)", 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 program attempted to interpret the value "99.79 kg " as a number, but
since the value contravenes the rules for correct number formats,
| this was not possible.
Thanks

Job terminated in source system - Request set to red during delta load

Similar Messages

Maybe you are looking for