Job in Source system terminated - Request is set to red

Hi
I ran a process chain on the weekend which loaded several info packages into a cube. They all ran successfully except for one.
The error message said "Job in source system terminated - Request is set to red".
I've looked on Monitor and no records were extracted.
How can I find out more information as to why this failed ?
Sandra
thanks in advance

Hi sandra,
Suppose if the job in the source system is terminated then no extraction is possible.In order to see the job in the source system->in the process monitor tab->go to environment menu-->job overview>in the source system.so by following the above steps u can see the job in active r cancelled like that.by clicking on the job log u can see all the steps involved in that job.based on that u can take action.
what my suggestion to this issue is force the qmstatus to red and delete that incorrect request and perform again repeat.it will goes through successfully unless it is not a functional error.
assign points if it is useful...
regards,
sri

Similar Messages

Job in source system terminated

hi xperts,
     I am getting following error while loading from 2LIS_03_BX to 0IC_C03 CUBE.
i already put the GENERATE INITIAL STATUS.
<b>"Job in source system terminated --> Request is set to red."</b>
In the details TAB:
a)Requests (messages): Everything OK
   Data request arranged
Confirmed with: OK
b)Extraction (messages): Errors occurred
   Data request received
   Data selection scheduled
   Error occurred in the data selection
c)Transfer (IDocs and TRFC): Everything OK
Request IDoc : Application document posted
Info IDoc 2 : Application document posted
Info IDoc 1 : Application document posted
d)Processing (data packet): No data
Please help me,its really urgent.
Thanks in advance.

Hi,
     if you can not find any reason in sm21, st22, rsa3. then try as below:
    1. replicate the datasource;
    2. activate transfer rule;
    3. quit workbench
    4. entry workbench
    5. create a new data package
    6. load data with the new data package again;
hope you good luck;

How to start a Failed job in Source System?

Dear Experts,
I have a job running daily in the source system was cancelled at the step 10. Since it is successfull upto step 9 I would like to run the job from the step 10 onwards. The cancelled job details are given below -
Step 010 started (program XXXX, variant YYYYY, user name UUU)
ABAP/4 processor: YER_RSQL_SQL_ERROR
Job cancelled
Can any one respond to this with proper solution?
Thanks in Advance,
Raj

Dear Sam,
Thanks for your approach. Its not a single program but a set of programs listed like steps. Doing manually would be good proctice becuase I have more no. of programs from the program which is actually cancelled.
Now you can add comments to my explanation.
Thanks,

Unable to kill or cancel the job in source system

Hi gurus,
   got a error , while loading delta for line item ods in AR.
stating as the job is not ended in the source system.'
i find the job in the source system and it is active.
   i tried to kill that job from sm37, its not happening,
and tried to cancel from sm50 even its not happening.
kindly suggest how to cancel or kill that job.
its urgent plz.
pramod

Hi,
        Check If u r system is running on more than 1 server...kill your job with proper appropriate server in tcode SM51.And also after killing the job come to SM37 check that particular job, nd on top menubar,u will 'check job status'.Then do refresh.
Hope this helpful to you.
Regards,
Praveena.

Bw extraction process starting after a process/job in source system

Hello gurus,
I want to start a extraction process (a chain process) in BW system after a background program (job background process) has finished in the source system (which is an R/3 system).
My solution sound like this: I make a RFC function in BW that start the event XX, and planning the process chain to start at event XX (all this in BW side).
In source system I call the RFC function when the desired background process has finish.
I look for another solution (more simple maybe) for my task, or for any another suggestion.
thanks

Hi,
Refer the note :135637
(1) Create an event in the BW system
Define a system event (for example SAP_BW_TRIGGER) with Transaction SM62.
(2) Create a function module in the BW system
Create a function module (for example Z_BW_EVENT_RAISE) with the help of Transaction SE37. For the source code refer to the attachment of this note.
(3) Use the below code in code of the triggered job in the R/3 System.Here BIMCLNT000 is the logical system name of the BI system. you need to cange it to yours.
parameters: rfcdest like rfcdisplay-rfcdest default 'BIMCLNT000'.
call function 'Z_BW_EVENT_RAISE'
destination rfcdest
exporting
eventid = 'SAP_BW_TRIGGER'.
Regards,
Anil Kumar Sharma .P

Hold extraction job in source system

Hi All,
Is there a way to hold a an extraction job in R/3. We would like to force an idoc to unprocess status (64) in R/3. Please let me know if there is a way to do this.
Thanks a ton!

Hi,
     if you can not find any reason in sm21, st22, rsa3. then try as below:
    1. replicate the datasource;
    2. activate transfer rule;
    3. quit workbench
    4. entry workbench
    5. create a new data package
    6. load data with the new data package again;
hope you good luck;

An error occured in the source system

My process chain has been doing FULL load for COPA data in a ODS. It failed today saying
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.
When I click on indiv. Message tab I get "Job in source system terminated - Requests is set to red"
What should I do to resolve the problem.

For Source system R3 :
This particular problem "Job terminated in the source System" occurs when there are long running jobs in the backend.
In the monitor tab,
Environment --> Job Overview --> In the source system.
After logging into the source system, click execute
Check the status of the job i.e. active or failed.
Check the job log for the same.
If its " DBIF_SQL_..... " sort of error, then in this case, delete the request from the data target and reload again.
The load would be successful
Caller 09 error normally occurs when the source from which the datasource is picking up data may be in use on the R3 side.
Hope this helps!!!!!!!

Source system extraction job not starting

Hi,
I transported a CS,TR,UR from Development to Quality system and it worked fine.
Then i moved from Quality system to Test system .
Transports were successful.
I see UP,TR,CS in active state.
I checked the source system mapping and it is perfect.
I checked source system connection and its OK
I scheduled a IP from BI and the job did nt started any job in source system?
Request you to help me on this.

Are you scheduling the job in the foreground/Background.?.
Please schedule in foreground.
Once you are scheduling the info package go to monitor tab
and see how many records it is fetching.
Also make sure you have a immediate scheduling option.
Thanks,
Saveen Kumar

Job is not running in Source system.

Hi Experts,
One issue I have because of this I am not able to load data into Data sources.
I am in BI 7.0 environment.
when I execute infopackage, total and techinical status are in yellow.
I found in R/3 Job is not running, based on this statement in SM37. from the fallowing.
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 0 records
Result of customer enhancement: 0 records
IDOC: Info IDoc 2, IDoc No. 3136, Duration 00:00:00
IDoc: Start = 14.05.2009 07:23:39, End = 14.05.2009 07:23:39
Synchronized transmission of info IDoc 3 (0 parallel tasks)
IDOC: Info IDoc 3, IDoc No. 3137, Duration 00:00:00
IDoc: Start = 14.05.2009 07:23:39, End = 14.05.2009 07:23:39
Job finished
Job satrt time and end time are same, so job is not running in the sourcesystem, am i right. let me known if i am worng.
It is Standard Data source but in the above statement becasue *result of Customer enhancement:0 records.*
please help me to reslove this issue to load data into BI.
1. what I have to do to run job in source system side.
2. should I take any help from Basis.
Regards
Vijay
Edited by: vijay anand on May 14, 2009 3:02 PM
Edited by: vijay anand on May 14, 2009 3:04 PM

Hi Rupesh,
in RSA3 data is availbale,
but it is not coming to BI,
Messages from source system
see also Processing Steps Request
These messages are sent by IDoc from the source system. Both the extractor itself as well as the service API can send messages. When errors occur, several messages are usually sent together.
From the source system, there are several types of messages that can be differentiated by the so-called Info-IDoc-Status. The IDoc with status 2 plays a particular role here; it describes the number of records that have been extracted in a source system and sent to BI. The number of the records received in BI is checked against this information.
the abovemessage I am getting in details tab.
Regards
Vijay

Job-scheduling on a specific instance on source system

Hello All,
Is there any possibility to schedule an infopackage in BW and tell the job that the corresponding job on source system (e.g. R/3-system) should run on a specific instance?
Thanks,
Pavan

Hi,
I guess the job is related to extraction job in R/3 that relates to the BI load..
Here if this job runs on a particaular RFC user always , depending on the user u can resrtict the instance on which it is supposed to run...
Take the help from BASIS they can fix the issue....
rgds,

Source system jobs in ready status

Hi Gurus,
I am Extracting data from R/3 to BW, when i execute the infopackage the jobs in source system are in ready status and they are not moving to active & finished status.
Is there any method to make the jobs in source system active manually.
Thanks & Regards,
chinnu.

When you execute the infocpackage you must use the inmediatly option for execution or programmed job ...in your case is assume that you use the orogrammed job....if you use this last option...you must setup your job with init time...if you do not use the start time and hour the job will never starts....this could be your problem

How can we change the Job priority in the Source system

Hi All,
We are facing an issue with the process chain execution in the Production system. We have a process chain which runs daily in BI system and the chain is designed in such a way, that as soon as the chain starts in BI system, a corresponding job is triggered in the Source system (ECC 6.0system).
Now the issue is that after we have our Source system upgraded the memory allocation for the particular Job (FIGL )is reduced and due to which the FIGL job is failing frequently. When we have consulted some experts.They advised Us to increase the Priority of the Job in source system to A/1, as of now the job is running in B/2 priority.
Please let us know the way how we can increase the priority of the Source system Job, so that when the process chain triggers a job in source system and that particular jobs should run with Priority A/1.
Thanks in advance.
Regards,
Chandra.

Hi Chandra,
First please find the job name in SM37 for FIGL and check the job status to be in "released" status. Select that job and go to job menu and click on change. then it will take you to the job screen where you have "job class". Here you can change the job class to "A" to get to high priority.
If you are unable to edit the job then create a new job with the same variants by clicking STEP button in the Job screen.
Try these steps, let me know if are able to do so.
Regards,
Ravi Kanth

When exactly source system recognizes the last delta is succesfull/failed.

When exactly does the source system recognizes the last delta is successful/failed?
Case -1: In logistic applications..
             What if I changed quality status to red for a successfully completed delta, and then requested new delta?
Case -2 : In Financial applications..
              When exactly BWOM2_TIMEST fields updated. I mean BW acknowledges to the delta load immediately saying it is successful or fail, or at the time when we request the next delta?
              What if I changed quality status to red for a successfully completed delta, and then requested new delta? It executes repeat or returns 0 records.

Hi,
Here's the explanation:
Scenario 1 -Logistics Delta
Sinc logistics delta comes from Delta Queue (RSA7) and IP takes daa from Delta queue so betwen RSA7 and BW, IDocs are transferred which sends messages for successful completon of extraction. As soon as extraction is over and a particular IDoc is sent to BW the BW marks the delta s successful. This happenes exactly when job is Source system completes Now if you make a successful delta as red then the IP identifies that last delta was not successful and requestes a repeat of last delta which again goes to RSA7 and picks the last delta and also the new deltawhich has come in RSA7. Note: RSA7 stores both new delta records and one last successful delta records(for delta repeat)
Scenario 2 - FI Delta
Sinc FI deltas are based on timestamp mechanism there are 2 possibilities:
a) The extraction fails while picking records from R/3 table (G/L, Ap and AR tables). In this case the timestamp isnot registered in BWOM2_TIMEST table and arepeat will work fine.
b) The load fails during procssing in BW (e.g update rules processing) and the job has completed in R/3 and has set the timestamp in table BWOM_TIMEST. In this case we will have to reetthe tmestamp and run the delta again.

Error message from source system

Hi All,
We have an infocube and ods which is being loaded from another ods. This is included in a process chain.
In the process chain the Infopackage execution step has failed. When I right click and go for display messages, I found the following message in Messages tab:
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
And in Indiv Messages tab,
Delta upload is only possible after successful initialization.
Errors in source system.
I tried to update the data targets from the initial ODS manualy but in vain.
Any Help is awarded with points.
Thanks
AP

Hi,
Goto Info pack -> on menu bar select scheduler -> select init options for source system -> one request with green status -> select it and click on delete symbol , it will delete the init. you can cross verify this in the base ODS where you dint find data mart status(after refresh). now select init delta process under that select init without data transfer and schedule the load it will update one record and init flag to your source ODS.
Note: if the last request is not updated from soruce ods to targets for that also you will find data mart status for this select the particular data mart -> click on delete symbol it will delete for the particular request (if it is updated to target it will not allow you to delete) then do delta load it will update the request which is not loaded from source ods to next targets.
Regards
Sankar

New source system

We've just copied the BW Production system onto a new server (Test BW).
The BW Production is pointing to Production ECC6.
We're have created a new RFC in the Test BW, which point to Test ECC system.
We have also perform the source system conversion via BDLS.
In RSA1 ->Source System, I can see name of the source system has been changed to Test ECC6.
However, when I right click on Source System ->Connection Parameter, I can see that
the Source System is still linked to the old RFC which is pointing to the Production ECC6.
How can I change this RFC so that it is pointing to the new RFC that we just created?
Please help, thank you.

in the monitor screen, check the complete error message in status tab.you will find a button below the message, click on that to get the detailed message.
then goto details and see in which step you are getting the error(extraction/processing etc).
Or...
in the menu , Environment ->job overview->Source System and then also it will take u to R/3 side .
Check the job status...finished/cancelled etc.
If cancelled, then reload .
In any case, read the log what is getting displayed.
1.Please replicate and activate the data source in bw side under the appropriate source system
and then try loading.
or
2.In the processmonitor of the info package, (in details tab) when you right click on the red ststements and select displaying messages, there will be a question mark appearing at the right hand side.
or
3.check whether all the objects all active or not.
4.check if data source is active on R/3 side or not...if no...activate the same.and reload.
Is it happening for the first time...if yes...were there any transports on R/3 or BW containing these objects
5.Also, goto BD87, in both R/3 and BW side...check if there are any idocs stuck...if yes...manually process them...
6.Check in sm58 in R/3 or BW....if there are any entries there for this...if yes...select them and press F6...
Edited by: Ananda Theerthan on Mar 3, 2010 1:23 AM
Edited by: Ananda Theerthan on Mar 3, 2010 1:27 AM

Job in Source system terminated - Request is set to red

Similar Messages

Maybe you are looking for