Background job - Event tiggering not happening

Hi All,
Background job X will run on daily basis and which in turn triggers two jobs say A and B.
The job X got finished successfully but jobs A and B havn't been triggered and so not running.
Please help me on this.
Thanks & Regards,
Gopi L.

HI,
Gopi check the start condition of job A & B, what event is triggering these jobs.
Also check SAP note 395170.
Regards,
Sachin Rane.

Similar Messages

BPM - Background Job for Reorganization = Not Scheduled

Good afternoon, first of all thank you very much for the support they can provide. I have developed a JDBC interface -> BPM (Multimapping) which works well. Modify a Message Mapping in the BPM that I use for an RFC Lookup, I have added the Configurable Parameters in the BPM and Integration Directory and everything works fine at design time. But when running the interface at run time the message reaches the BPM and the error "error in BPE inbound Permanent processing".
I have reviewed the Business Process Engine in the RWB and the item is Red Schedule Background Job for Reorganization and detail reads: "Background Job for Reorganization = Not Scheduled".
As I can solve this problem. Thank you very much.

Re: Importing trans request failed
Re: Transports Erroring
Re: What is RDDIMPDP .....
have a look it may help you
Message was edited by:
Vinod Udapudi
Message was edited by:
Vinod Udapudi

Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.

Dear Guru's,
                 I am having a problem during transportation. i am not able to transport to quality system.And the tp system logs shows following error messages:-
WARNING: System GNQ. Warning.        20071105123442 :
ERROR:       Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.
ERROR:       I'm waiting 100 sec (Count: 1).
WARNING:       (This warning is harmless if no further warnings follow.)
Please help.
Regards
Akif

Re: Importing trans request failed
Re: Transports Erroring
Re: What is RDDIMPDP .....
have a look it may help you
Message was edited by:
        Vinod Udapudi
Message was edited by:
        Vinod Udapudi

Triggering background job event from Unix script

Hi all,
I am having one question regarding triggering of background job in SAP using Events from Unix script. Is this possible? If so, can anyboy provide some sample code related to Unix script and how do we communicate to SAP from Unix system. Actually, here the backend of R/3 system is MSSQL. I am having a program in R/3 system which is scheduled as a background job based upon event trigger. I want to trigger that even from the unix script.
Appreciate for your help in advance.
Thanks,
Adithya K

Hi,
Check if this can help you
http://help.sap.com/saphelp_sm32/helpdata/en/fa/096e6b543b11d1898e0000e8322d00/content.htm
Regards,
Atish

Background jobs html output not allowed 1 MB size

hi experts,
We are facing an issue with backgrounds jobs HTML output. we are running some backgrounds jobs for Std reports, and we are facing if the HTML output is <1 MB, the std sap is cutting/reducing the content only 1 MB. I think somewhere the background jobs HTML output is fixed 1MB, request kindly let us know how & where we can modify/allow the HTML output <1 MB size for background jobs.
Please help.
thanks in advance
Srihari

thanx so much for the solution, but i wanted to fix permanently at the time of html output after the job is finished itself, but when i change the parameters from 1 to 9999 pages, it is showing information message and SAP recommends the spool output is fixed from 1 to 10 pages only, if i go beyond 10 pages, i get message memory slow and impact on memory, etc.,
I wud like to know expert opinion whether doing from 1 to 100 pages thru SP01, what are consequences are to be faced wrt to memory and other aspects. Also i wanted to know these permanent changes will affect entire system or only specific jobs?
I wanted for 2 to 5 background jobs, which are having more than 10 to 30 pages,
Please advise
thanx in advance
srihari

Error in TLB background job"Version does not exist"

Hi Gurus,
We are getting error of "Version does not exist " in TLB background run..The T-lane is between 2 DCs .we have checked everything but unfortunately
we are not able to detect the root cause for the error.
Your help will be appreciated.
Thanks in advance
Suyash

Hi Suyash,
I hope than your planning version is active!
I also suppose than you have maintained mean of transport and products at Tr.Lanes level.
I think that you have some master data inconsistency in the version.
Please run the reports; /SAPAPO/OM17, /SAPAPO/TSCONS, /SAPAPO/TSLCREORGSNP
You can also run Model Consistency check (t.code /SAPAPO/CONSCHK). First you have to define the Model (t.code /SAPAPO/SCC07) and the Profile (t.code /SAPAPO/CONSPRF).
Thanks, Marius

Background job spool is not generated

Hi Guys,
I am facing the problem with when i execute the program in background,spool is not generated.
if execute it in foreground output is displaying.
Please help me on this issue.
Thanks,
Bala

Hi soumya,
after call transaction i have used write statement and submit the report in the BDC program.
BDC report is displaying the IM52 update budget orders in the output of the report.
Thanks,
Bala

Rule set import - Background job did not run

Hi,
I am setting up my CC 5.2 production system. I have downloaded from ruleset from the dev CC and imported it into production. However the background job generated did not run. I am implementing SAP note 999785 to fix this, but am wondering what should I do about the rule set? Do I need to delete the rule set and reimport it? As this background job did not run I notice that the permission rules did not generate.
Any advice is welcome.
Thanks

Hi,
as the backgorund job never ran and no rules were created, I can just reimport the ruleset and let the job run. I have tried this and the rules were created successfully

Inbound IDoc creating background job even for trigger immediately setup

All,
I have a very serious problem in our production system.
Scenario:
Vendor is chagend in system A (Outbound) and the same is interfaced to System B (Inbound) and i am using trigger immediately option, but still I am seeing a background job is created for 'RBDAPP01' and creating the spool request. The issue is I am sending 1000 of idocs and the spool number is increasing daily in system B.
So, can any one explain me why the background job is getting triggered even though I set the partner profile settings as 'Trigger Immediately'.
The above issue is not happening in our quality system it simply updagtes vendor information in system B with out creating any background job. Please note that the same settings are maintained in both the systems.
Your immediate inputs are really valuable for me.
Regards,
Suman

This is an performance issue on the receiving system. In case the system does not have enough resources to process the IDoc immediately it will always schedule a background job to ensure the processing of data.
You need to check whether the system has enough work processes available during the time when 1000 of IDocs are received or send the IDocs in packages with some time in between.
Regards,
Kai

To Check whether Background Job ran or no

How can we programatically check in a program whether a background job ran or not for a particular output type of invoice ?? Pls help me out

Hi,
This will probably work.
report zkiran_0001 .
data: xtbtco type tbtco .
parameters: p_job type tbtco-jobname.
start-of-selection.
clear xtbtco.
select single * from tbtco
 into xtbtco
 where jobname = p_job
 and status = 'R'. " running
if sy-subrc = 0.
 write:/ 'Job', p_job, ' is currently running'.
endif.
Statuses....
Status of background job
The following statuses are possible:
Scheduled: Job defined, but not yet eligible to run even if the start condition has been fulfilled.
Released: Job eligible to be started as soon as the start condition with which it was scheduled is fulfilled.
Ready: Job waiting to start. The job has been released and the job's start condition has been fulfilled.
Active: Job is currently running and can no longer be deleted or reset to scheduled.
Finished: Job has been successfully completed. All job steps completed successfully.
Note: the background processing system cannot always determine whether an external job step was successfully completed. In this case, the system assumes successful completion.
Terminated: Job was ended abnormally either through user action or through an error in running a job step.
Internal codes for these are as follows.
btc_running LIKE tbtco-status VALUE 'R',
btc_ready LIKE tbtco-status VALUE 'Y',
btc_scheduled LIKE tbtco-status VALUE 'P',
btc_released LIKE tbtco-status VALUE 'S',
btc_aborted LIKE tbtco-status VALUE 'A',
btc_finished LIKE tbtco-status VALUE 'F',
btc_put_active LIKE tbtco-status VALUE 'Z',
btc_unknown_state LIKE tbtco-status VALUE 'X'.
refer
https://forums.sdn.sap.com/click.jspa?searchID=4369376&messageID=1681128
Regards
Message was edited by:
 Kiran Sure(skk)

Background job name

Hi All,
Background job related info. not getting retrieved when using function module 'SAPWL_READ_STATISTIC_FILES' (version SAP ECC 5.0 compatible) in our SAP ECC 6.0 whereas if I use 'SWNC_STAD_READ_STATRECS' I'm getting the required info.
Can anyone let me know why FM 'SAPWL_READ_STATISTIC_FILES' doesn't give the required info. in SAP ECC 6.0?
Thank you.
Gandhi Subramani

Hi,
It would help you ,
Make your report automatically processed in background when it is being executed using JOB_OPEN, SUBMIT and JOB_CLOSE like following[example code],
DATA: d_jobcount LIKE TBTCJOB-JOBCOUNT,
d_jobname LIKE TBTCJOB-JOBNAME.
03
04 d_jobname = 'JOB1'. " Here you may give the job name what ever you insist.05
06 CALL FUNCTION 'JOB_OPEN'
07 EXPORTING
08 jobname = d_jobname
09 IMPORTING
10 jobcount = d_jobcount
11 EXCEPTIONS
12 cant_create_job = 1
13 invalid_job_data = 2
14 jobname_missing = 3
15 OTHERS = 4.
16
17 IF sy-subrc NE 0.
18 MESSAGE s368(00) WITH 'Error Creating Job'
19 sy-subrc.
20 EXIT.
21 ENDIF.
22
23 SUBMIT <REPORT_NAME>" call the same program in Background with different job names 24
VIA JOB d_jobname
25 NUMBER d_jobcount
26 AND RETURN.
27
28 CALL FUNCTION 'JOB_CLOSE'
29 EXPORTING
30 jobcount = d_jobcount
31 jobname = d_jobname
32 strtimmed = 'X' " Immediate
33 EXCEPTIONS
34 invalid_startdate = 1
35 jobname_missing = 2
36 job_close_failed = 3
37 job_nosteps = 4
38 job_notex = 5
39 lock_failed = 6
40 OTHERS = 7.
41
42 IF sy-subrc > 0.
43 MESSAGE s368(00) WITH 'Closing Job Failed'
44 sy-subrc.
45 EXIT.
46 ENDIF.

Error after a scheduling a background job

Hi all,
I'm trying to schedule an interface program in background which reads data from application server and posts a document in Finance through a BAPI funtion module.But after scheduling the job in the immediate mode,its getting canceled showing the error
"Could not ascertain code page"
"Job cancelled after system exception ERROR_MESSAGE" in the job log.
Please help me with this...
thanks

Hi ,
To decode the reason behind job failure , use ST22 Tcode with Exception Name as ERROR_MESSAGE ( as that is what is given in the Job log ) and User - SAP Logon Id
This would give the system dump log and tell you where exactly the job failed .
Please note this applies for any background job and is not specific for your case .
Do have a look at the dump in future ...
Thanks

QA Approval - importing queue with background jobs

Hi all,
I have activated the QA approval in my system and it all works fine. I have scheduled a background job via STMS to import the whole test system buffer each day and this works fine too. Now I want to schedule a background job to import the production buffer automatically too. This would allow us to have all approved transports automatically imported once a day (as QA approval is activated only approved transports would be imported).
Sounds simple, but with QA approval the production buffer displays approved and non-approved requests, so the background job fails as not all transports in the buffer are in the correct status.
Any suggestions on how I can get around this problem?
Thanks
Claire.

Hello Claire,
This issue has been described in SAP Note 313991. please check.
Regards,
Debasis

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
 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) 
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 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 - Event tiggering not happening

Similar Messages

Maybe you are looking for