Charms : Background job not scheduled (normal correction) ?

Hi,
I am trying to run a dry cycle for normal correction but when i go to task plan in any ticket to release a request. When i schedule this job " release a request" , i dont see any job running in background in SM37. I think job is not gettin sceduled properly.
Please help me out

Hi,
All right. We need to dig this one
I guess you schedule the import by going the the tasklist
and you get a red flag for this activity in the calendar ? do you have any error message ?
If the messagein the task-list is not self-explanatory you can check the SLG1 log in SOLMAN. Which error message do you get there. (select the correct time frame, the log could be big)
My guess is that some S_RFC authorisation is still missing there
This authorisation is outside SAP_ALL and is often the cause of this kind of issue
Tell me the error message and we will hopefully fix this (I had the same kind of issue when I started last year)
best regards Xavier

Similar Messages

Some background jobs not shown in SM37

Dear Friends,
Some of my background jobs are not shown or visible in SM37. But, it is available in TBTCO, TBTCP & TBTCS tables. These jobs are scheduled in daily basis. These tables having records for all days of missed jobs.
I dont know, why it is not comming in SM37. I tried in many search parameters in SM37 like prog. name, date and so on.
These missed background jobs are not comes in spooler (SP01) also.
Kindy, suggest me to find out the missed background jobs.
Thanks in advance
Regards,
Rajagopal
Chennai - INDIA.

Hi rajagopalan,
Normally this should not happen. Make sure the following in sm37:
a. The start date is : 01.01.1800
b. The end date is : 31.12.9999
c. All the checkboxes (six checkboxes) are ticked.
d. username = your username
e. jobname = *
SM37 gets records from the view V_OP (containing TBTCO and TBTCP)
and filters for username using the field SDLUNAME.
So you can basically cross-check if the count is atleast correct or the jobs were of different user (fieldname in the view/table) etc. (From SM37, you can export to excel and check the count)
regards,
amit m.

Background Job Not Reconnected After Offline Backup.

Hi all,
Background jobs which are scheduled before Databse Offline Backup are always cancelled. Reconnect WP does not happen even if following parameters are set.
We had set profile parameters in all Application Server like
   rsdb/reco_trials = 15
   rsdb/reco_sleep_time = 60
   rsdb/reco_add_error_codes = +3113 +3114 +1012 +1014 +1033 +1034 +1089 +1089 +1090 +1092
R3 Production server (640 Kernel, Patch 175 , SAP_BASIS 620 , SAP_APPL 470)
   Database : Oracle 9.2.0.6
SYSLOG Msg : SM21
<b>     Communication error, CPIC return code 020, SAP return code 497
       > CPI-C function: CMINIT(SAP)
       Operating system call gethostbyname failed (error no. 0 )
       Operating system call gethostbyname failed (error no. 0 )
       Communication error, CPIC return code 020, SAP return code 497
       > CPI-C function: CMINIT(SAP)
       Communication error, CPIC return code 020, SAP return code 497
       > CPI-C function: CMINIT(SAP)
       Communication error, CPIC return code 020, SAP return code 497
       > CPI-C function: CMINIT(SAP)                                   </b>
Thanks & Regards.
Naba

Looks like some Gateway error....though not sure...
Check Note 63347 - List: CPIC error codes and then u can try to troubleshoot further...

Background job not deleted

Hi Experts,
i want delete the "SM:SELFDIAGNOSIS" background job on solution manager system .
and i have deleted, go to next date and then delete the released job but after one day again its showing in released.
so how i can delete it properly .
Regards
jai kr.

Shiv,
First check the frequency of this job from SM37
Go to SM37 -> give your job name ->and select all the options like
delete the entries in start date and end date fileds. then execute.
If you find job in Released state ,simply go to menu Job -> click on release to schedule.
Now this job will in Schedule and won't run untill you release it.
Deleting the jobs is not good idea ,simply you can suspend it.
Regards,
Srinivas Chapa.

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

Background jobs are scheduled in future date

Hi
A system which is used by a customer test system was installed and scheduled the jobs in 2010( in future date).
Now we have changed the date to current date. But still all the background jobs are in future date.
There are around 500 jobs are scheduled. And it not possible to reschedule one by one.
Is there any way workaround to change it back to current date format.
Best Regards,
Jai

Dear Jai,
The jobs scheduler should have this dates changed to current. If its a third party system which are running these batches, then be careful to convey the same message to the 3rd party.
If its in SAP, then the schedule change date should execute your jobs. At the same time, ensure that the transports between the test systems match to the destination.
Do let me know for any clarification.
Thanks
Madhu

Background job not executing... pls help

I want to schedule and execute a batch job with the start date and time with another program.
In program1 im doing the below.
job_open
   getting job_count
CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
      no_dialog              = abap_true
    IMPORTING
      out_parameters         = ls_params
      valid                  = lv_valid
    EXCEPTIONS
      archive_info_not_found = 1
      invalid_print_params   = 2
      invalid_archive_params = 3
      OTHERS                 = 4.
SUBMIT (c_test)                 VIA JOB lv_jobname
                                  NUMBER lv_jobcount
                               TO SAP-SPOOL WITHOUT SPOOL DYNPRO
                                   SPOOL PARAMETERS ls_params
                                   AND RETURN.
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
      JOBCOUNT             = lv_jobcount
      JOBNAME              = lv_jobname
      LASTSTRTDT           = p_sdate
      LASTSTRTTM           = p_stime
     targetserver         = lv_targetserver
    EXCEPTIONS
      CANT_START_IMMEDIATE = 1
      INVALID_STARTDATE    = 2
      JOBNAME_MISSING      = 3
      JOB_CLOSE_FAILED     = 4
      JOB_NOSTEPS          = 5
      JOB_NOTEX            = 6
      LOCK_FAILED          = 7
      INVALID_TARGET       = 8
      OTHERS               = 9.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
in the job_closei gave start date and time, but the job is getting scheduled but not to released/cancelled status.
I want the job to happen at that given time and date,
is there anything im missing,
pls help

Rajan,
In the same documentation it says : Note:  if a user does not have the authorization to release a job, then the job is scheduled with the status planned.
Now after i run this program , and check SM37, the status is scheduled. so this tells not an authorization issue.
Also i can go and schedule on a given time from SM36.
Now after reading that i also passed the parameter JOB_WAS_RELEASED importing it is geting blank value.
but documentation says, it shud be X if Job is released.
any idea pls....
Niraja

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 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 run properly

Hi,
When an infopackage is triggred through process chain in BI a background job will be exeuted at R/3 to fetch data from R/3.
But the bakground job did not execute properly hat is it did not fetch any data but ot finished.
But when the infopackage is executed manually the background job fetches the data from R/3.
Why the job is not fetching data when triggered through process chain.
Please help me to sole this issue.
Regards,
Indhu

Hi Induja,
In your case, you will have to debug the background job that is activated through BI. Check if proper data is coming from BI.
You can only debug a background job if it is created under your user id. Thus, to debug the job you first have to own it and then debug by selecting it and either typing 'JDBG' in the command field or through menus available on the top.
Job overview transaction code - SM37.
Hopefully the issue is in Development/Test/Quality system and not in Production.
Hope that helps!.
Regards,
Saba

Background job not generating spool

Hi all,
I am calling a report from another report. The called report will display the final output list.
Here, the called report will be executed in background.
here the job is completing but the spool is not generated.

Hi,
It seems that the final internal table which has the output data is empty & hence write statements are not executed ( assuming all the write statements are inside a loop).
Place one write statement outside loop like
write :/ 'Following is the result :'.
& check whether spool is generated. If yes, then the problem is of empty internal table.
You can select the job in SM37 & type JDBG in command prompt to debug a background job.
Debug & check the issue.
Best regards,
Prashant

Background job not invoking in CC.

hi,
I am facing a problem in running background job in CC. Actually its invoking a wrong url and when i am checking in application deployed url is different.
We are at CC SP9.
Url invoked is "is http://hostname:51700/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=/usr/sap/FAP/DVEBMGS17/j2ee/cluster/server1/.&threadId=4&daemonType=WS
As per deployment
Url should be "http://chmsxp41.eame.syngenta.org:51700/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart"
Please suggest.
Thanks & Regards,
Pravin

Please check SAP Note 999785.
Somewhere between SP04 and SP06 the URL changed, and you need to re-configure that on database level (change "virsa/ccappcomp" to "sap.com/grc~ccappcomp").
Frank.

Charms : Background job not scheduled (normal correction) ?

Similar Messages

Maybe you are looking for