EXSQL_DSQL_NOROLL-DP Background job not working as part of chain

Hi,
While running a background job as part of process chain, I am getting the error message which says:
ABAP/4 PROCESSOR: EXSQL_DSQL_NOROLL
Job Cancelled.
When run in the foreground in the interactive planning, it is running fine. Please let me know the way to bypass this error.
Regards,
Guru Charan.

Dont know why it has come that time, but now, it is running fine.

Similar Messages

Tcode MIGO Background Job Not working

Hi All,
I am facing problem in TCode : MIGO for Background JOB of BDC Program with below details,
CALL_TRANSACTION MIGO returncode: 1,001 RECORD:          0
MIGO                 017 S
The front end is not suitable for the transaction (see long text)
DC                   006 S
Control Framework: Fatal error - GUI cannot be reached
00                   341 A
Runtime error RAISE_EXCEPTION has occurred
Please let me know above error what needs to be done.
Thanks in Advance,
Mahesh Devershetty

I am facing the same problem while calling MIGO from RFC
CALL_TRANSACTION MIGO returncode: 1,001 RECORD: 0
MIGO 017 S
The front end is not suitable for the transaction (see long text)
DC 006 S
Control Framework: Fatal error - GUI cannot be reached
00 341 A
Runtime error RAISE_EXCEPTION has occurred
BDCMSGCOLL Returns the following :
TCODE                   MIGO
DYNAME               SAPLMIGO
DYNUMB               0001
MSGTYP               A
MSGSPRA            E
MSGID                  00
MSGNR                341
MSGV1                RAISE_EXCEPTION
please help me as soon as possible
giving thanks in advance
goutam roy

Background job not working for VF02

Hi,
When i give schedule RSNAST00 report in background for one output type its not generating spool, but the job status is in Complete. But in foreground it fine.
For another output type its working fine in background.
Is there any printer setting has to be done in driver program or in smartforms? Kindly help me on this.
Regards,
Vijay.

Hi,
Check whether u have assigned following values.
      l_wa_control_parameters-device      = 'PRINTER'.
      l_wa_output_options-tddest            = nast-ldest.
      l_wa_output_options-tdimmed         = nast-dimme.
      l_wa_output_options-tdnewid          = 'X'.
      l_wa_control_parameters-no dialog = 'X'.
CALL FUNCTION l_fnmod    "'/1BCDWB/SF00000149'
EXPORTING
control_parameters = l_wa_control_parameters
output_options       = l_wa_output_options
Still the problem exists then i wil send u the code.
Regards,
Vijay.

How to deactivate *Schedule Background Job for Work Items with Errors* SWU3

Hello Guys,
Can any one tell me how do I DEACTIVATE Schedule Background Job for Work Items with Errors in sap workflow SWU3.
Currently it is green which I don't want. I want to stop this service.
Regards
NK

Hello,
You could also just stop the job in tx SM37.
But why would you want to do this? As a test?
regards
Rick Bakker
hanabi technology

Database Scheduled Jobs not working

Hai All,
In my database Scheduled database jobs not working , but it work manullay fine...
All parameter are correct including job_queue_processes.. Where I can start troubleshoot for this problem.
Oracle: Oracle 9.2.0.1.0
Platform : AIX
Please help ...
Shiju

did you enabled the job?Unlikely. DBMS_SCHEDULER was a 10g innovation and as the OP mentioned, they're on 9i.
Oracle: Oracle 9.2.0.1.0Cheers, APC

Background job not automatically poopulating Dependant Demand

Hi Users,
We've recently set up a POS & PA using the DP-BOM selection and characteristics, manually created PPM's and generated CVC's using the BOMS. All of this is set up fine in our SCM 7.0.
The background job has created the forecasts for the ouptput products but NOT the input product.
Now if I call up the parent material, and then choose to show the input products the dependant demand is generated. If I now return to the material with the dependant demand, it now shows the demand from the parent.
Or, if the forecast is genereated interactively, then the dependant demand is poopulated.
Is there an automated method to populate the dependant demand when using background jobs? I would like to think that we don't have to query every sales BOM parent in DP and drill into the input products to load the dependant demand?
Please let me know if there is an easier way to do this as part of the background processing.
Thanks
Edited by: Paul_111 on Mar 31, 2011 4:20 PM

Hi Andand,
Thanks for your reply and sorry if my post is confusing.
As far as the PPM with imputs A & B, output C - I have this relationship working and calcuclating demand in DP no problems.
If I now add a new PPM combination inpput X, Y and output Z. Create the BOM CVC and TSO so its all set to go. Add to selection profiles and background jobs.
Now, if I run the background job to create the forecast and this runs successfully. Now I check my products.
Z has the forecast generated, X & Z have no dependant demand showing.
The only way I've found that pushes the demand to X & Z is:
- open product Z in demand planning and then choose the option to show input products from the header
OR - from demand planning, select the univariate forecast to run interactively.
My issue:
The background job (if run alone) does not push the forecast on Z to X & Y.
And if I show the input products or create forecast (as bove) the dependat demand is shown on X & Y.
This is going to be a slow process if we have to do this everytime we run the backgound job.
What am I missing when running the background job?

Background job not updating data for some steps of program

We have created a custom program and submitting the standard program RPRCCC_READ_KR1025
which is used for conversion of AMEX credit card files.
Since this program can update data for 1 company id at a time,we have created a background job
for that program with 10 steps and 10 variants of data related to 10 different company codes.
when this job is executed it is not updating data for all the 10 files , sometimes it updates 5,7,etc...
If we execute the other files which didnt update in job manually they are getting updated.
All the files executed with that program can be seen in PRTA transaction.
Regards,
Gautham.
Edit: Solved.
Since the standard program updates the database every time with commit work
there should be some time until the next database update,so we can use wait command
after the submit statement which will do the trick.
Edited by: Gautham Vangaveti on Aug 5, 2010 7:20 PM

Hi,
I mean B(Sub Assembly)
Item Rollup Flag
A No
--B Yes
---B1 No
---B2 No
---B3 No
--C Yes
In this case when we run cost rollup by giving item A, Oracle will consider below structure.
A
--C
Regards,
Sarvottam.

Background job not showing full output of Report

Dear Experts
we have created zpgm for stad report and try to take output as mail to particular user for future analysis bcaz stad gives only 2 days report only we need keep report for months together so when we run job in foreground it shows proper output but when same thing when we run from background it shows only some part of report in mail (we are unable to get full output through background job )
we send mail through spool receipts we have created folder and maintain user for getting mails through so15 distribution list
we need some input to come out of this major issue
if there is any other workaround let me know
Regards

Hello,
If a job is defined by transaction SM36, the print format parameters will only be taken into account, if they are saved as user specific print parameters of the batch user. If no user specific print format
is defined, the ALV standard logic will be processed adjusting the print format to the actual line size of the report.
For example, the list line size is about 132 characters, the widest available format of the chosen printer will be selected X_65_132.
The problem would be solved by defining a device type which is no format assigned to print, or by defining user specific print format parameters for the batch user, who creates the jobs in SM36 (see
SAP note 1179399, item 6).
Regards,
David

Background job not yet been Finished

Hi,
I have set a Background job today at 10:15 to start run at today 11:30 AM.
it is a periodic daily process at 11:30 am.
But when i checked the status of this job, its still in the status Released.
i know that, this job will not take more then 20 mins
what could be reason?
Regards,
Swetha

Hello Sweta,
As the job is in 'released' status so you can say that it has not started running, it will come to 'active' status as soon as it starts running, so you should not fear to cancel the job scheduled.
Answer to why in 'released' status for such a long time may be due to some network speed problem or due to some other jobs alreay running in the system which would be occupying all the work processes which are available in the system. If possible try to find the job which has taken more that 65 thousand seconds, kill that job and then refresh after 5-10 mins to see the status of your job.
Hope it helps.
Thanks,
Jayant

Background Job not Printing TOs immediately

Hello experts,
I am having an issue with printing Transfer Orders created by background job, the output requests are sent to the output controller with status '-' . It works when I manually create the TOs or if I run the RLAUTA10 program with my userID in SE38 .
I have set the background job user default print parameters in SU3 to print immediately.
Also in the Job step, I have set up the print parameters to 'print immediately'
I have assigned printer for sorce storage type & set the indicator to use the source sto type in OMLV, The printer seems to be determined correctly, I've checked the Spool request name & printer in the spool controller, only issue seems to be the print not being triggered immediately.
Not sure, if there is some other setting that I have to make to be able to print the TOs created by the background job immediately.
Any help would be appreciated.
Thanks
Kris T

whether the printer which you assigned is configured in SAP (network printer)? or LOCL?
printing may not happen if LOCL(background job)
Thanks

Background Job not running

Hi All,
A background job has been scheduled to run every minute.It was working fine but a few days back it did not get scheduled for 2 hours . Any suggestions as to why this might have happened.
TIA.
Vartika

Hi Manik,
The job started working fine after 2 hours. It was only for 2 hrs that it did not work. How to check if the userid was locked or not during that period.
Thanks
Vartika

Schedule background job for working days

Hi,
I would like to schedule a background job, but only runs on working days (from Monday to Friday), I am wondering whether it is possible to run as mentioned or not?
Kindly advise!
Thanks!!
br,
hy

hi
F9 - > click date/time, after the at operation mode tab, there is an arrow mark, click it, in taht mention your factory calendar id (which includes public holidays and specify from which workday it should start, time), then check and come back to the main screen, check periodic job, click the periodic values tab, in that specify it as daily...will solve your requirement
if helpful, reward
Sathish. R

Transaction SWPC when scheduled in Background is not working

Hi All,
I have scheduled the program RSWP_CONTINUE_WORKFLOWS_GRID behind the transaction : SWPC daily at 11 : 00 PM system time.
The creation date is selected as Creation date GE Sy-datum-1 dynamically and continue immediately option is also checked.
However the background job is not picking the list and restarting the workitems that are reported in system crash.
When executed the transaction in foreground , list is coming and I can able to restart the work items.
Is there any other setting which I am missing or Please let me know your inputs to solve the issue.
Many Thanks !
Thanks & Regards,
Preethi G.

Hi,
I have chcked the ST22, there is no short dump and move over the step where the processing is stopped is a backgroung step.
The same backgound step is execute fine for other workflow instances only few are getting strucked tp at this background step.
The Process :
when MIGO is perfomed, the euipments will be created.
once equipement is created, the customer workflow gets triggred and euipment is updated.
Suppose when MIGO is done 500 equipements gets created based on the quantity and 500 times the workflow gets triggered for the updation of the equipments.
sometimes, the backgroung job is working for around 495-497 , for remianing few euipments 2/3 , its getting struked up.
For few indtances all the 500 euipements gets updated with out any issues.
Only fews cases its getting down.
Is this something related to performace of the system or performance of the code which is wriiten for the backgroung job.
Please let me know your inputs.
Many Thanks !
Regards,
Preethi.

Java Job not working

We have a java job that sends an XML to remote URL by opening OutputStreamWriter to URL and receives the response XML from same URL using InputStreamWriter.
This Job is working fine, when running on Solaris Env. Now we have new server installed on Red Hat Linux. This job is not working on this new environment.
Error i am getting is as below:
<message>XML Parse Error</message>
- <message>XML Parse Error</message>
<reason>Error #-1072896680
- <reason>Error #-1072896680
XML document must have a top level element.
- XML document must have a top level element.
</reason>
- </reason>
<position src_code_pos="1"><line>0</line><column>0</column></position><src></src>
- <position src_code_pos="1"><line>0</line><column>0</column></position><src></src>
</RCP_CONTROL><SERVICE_INCIDENT Acknowledge="0"/><TRANSACTION/></RCP>
- </RCP_CONTROL><SERVICE_INCIDENT Acknowledge="0"/><TRANSACTION/></RCP>
java.io.IOException: Bad file descriptor
I Dont see any issue with code as it is still working fine from server installed on Solaris. Pls help

If Remote URL have received XML Successfully, then it creates some entries in its Database. But its not doing so. So i guess it is not even able to send the XML Successfully. And Since URL is not getting proper desired XML input so its returning error XML output.
But i am wondering same code is running smooth on Solaris Env.
Remote URL is part of 3rd party tool. so we even dont have much access on it so that we can determine what is received at their end, when we send an XML from our side.

Back Ground Job not Working

Hi,
I have watched all the threads regarding Back Ground job like SE36 & SE37. I have given a back ground job and its not working.
Its an ABAP Program which is creating an OLEDB Connection to MSACCESS and then retrieving and updating database table. The program is working very fine on foreground but when it is given to back ground job then it shows that the program is running, i mean in delay the time is ticking. But at last it is canceled by the system.
What's the thing i am missing or what should i do here? I have already set my program at high priority.
Thanks.

Hi Atish,
Are you sure that we cannot run in background? Can you please explain me why it cant be done.
Thanks,
Inder.

EXSQL_DSQL_NOROLL-DP Background job not working as part of chain

Similar Messages

Maybe you are looking for