Job getting scheduled twice

Hi Friends,
Its a FILE to IDOC interface. confirmation message back is needed to sender file, for that I followed the below link for Configuring the IDOC acknowledgment ALEAUD.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
As specified in point 7 and 8, used the transaction RBDSTATE & created the variant SAP_AUDIT_SEND for report RBDSTATE and scheduled a background job at receiver system.
Here the problem is, acknowledgment for ALEAUD getting scheduled twice, as a result two IDOCs ALEAUD is generated.Instead it should get scheduled only once.
Can any one tell me why the job is getting scheduled twice.
Thanks in advance.
Regards,
Meghna.

Hi,
in job_submit FM u hav an parameter PRIPARAMS which controls printing....
data wa_PRIPARAMS type PRI_PARAMS.
wa_PRIPARAMS-primm = ' '.
job_submit
exporting
PRIPARAMS = wa_PRIPARAMS
Cheers,
Will.

Similar Messages

Delta uploading job get cancelled in SAP R/3

question, during delta loading from SAP R/3 to BW, if the delta uploading job get cancelled twice for some reason, will I lost some delta data??
Pls advise!
Many Thanks!
rajatina.

Hi,
If your delta jobs are getting error out in BW then you don't need to worry about, because till that time your delta pointer in source system is not yet updated. But if you make any request green by chance in BW monitor then your delta pointer will get updated and you might loose some delta.
You can request repeat delta multiple times without any issue.
Regards,
Durgesh.

When I schedule a Job, the job is executed twice.

Post Author: sachinddalal
CA Forum: Data Integration
Hello,
I am using Data Integrator Ver 11.0.2.22. I have scheduled the job through Admin Console. When the job is executed it seems that the job is executed twice.
On the Status tab onDI Administrator, it shows that both the jobs started at same time. The end time of bot the job is different.
Any one have any idea how this happens?
Also any way to ensure that the job are not executed twice.
Thanks,
Regards
Sachin Dalal

Post Author: bhofmans
CA Forum: Data Integration
If you get this issue for a scheduled job only, I might be that the schedule is created twice in the OS scheduler. You could check the windows task scheduler (or cron on UNIX) to check for duplicate schedules.
If you see this issue also for jobs you execute manually (via webadmin or Designer), you can have this kind of problems if the same jobserver is registered multiple times in a repository. You can check the AL_MACHINE_INFO in your repository. It should have one line for each jobserver and one line for each administrator the repo is connected too. I suspect you have some duplicates there (you can just remove them - this table gets populated when adding a repo in the web admin and when adding a repo to a jobserver in the server manager).

Job getting cancelled in background scheduling

Hi,
I have written a report in the SAP HR system and it is to be scheduled in background. This program transfers the PERNRs from HR system to CRM system as partners in BUT000.The report works perfectly fine if it is run in foreground. When I run it in background the job gets cancelled and I get the job log having a message that it could not ascertain code page and the system exception ERROR_MESSAGE is raised. If anybody has any clues regarding this problem please help me.
Thanks & Regards,
Rahul.

Hi,
I Guess you are using container controllers in the Report, and all container contols requires help from Sap Gui for execution. I guess that is the reason it is failing in background . Please check on that aspect as well.
Hope this helps..

Certain Maintenance Plan not getting scheduled in the background job

Hi Gurus,
I am facing an issue here.
A weekly background job (RISTRA20) runs every weekend and schedules the maintenance plans.
But we have noticed that some maintenance plans are not getting scheduled. i.e no orders or schedule is getting generated.
When I run IP30 manually for these plans then the schedule gets generated and orders get called.
I have checked up the background job and it is running fine.
Also, i have noticed a similarity in all these plans which are not getting scheduled. There schedule has been restarted (through IP10) at somepoint or the other.
But i don't see any direct impact of this?
Can any of you provide some help on this?? Points will be rewarded.
Thanks and regards,
Nitin Saini

Hi Narender,
Thanks for replying.
The message number for 'Groups don't match' is ME303.
I think this does not have anything to do with the restart as i have done further investigation.
Whenever I run IP30 with sortfield input as AS02*, i get the error as mentioned above for a certain number of maintenance plans while the remaining plans get scheduled.
If i run IP30 for any other sort fields, it runs fine and i don't encounter the error
mentioned above.
If you send me ur email address, i could forward you screen-shots of the issue.

How to schedule a job to run twice within a request set?

How to schedule a job to run twice within a request set?

Create one more stage for the same concurrent program.
Thanks
Nagamohan

RSBKCHECKBUFFER job scheduled twice and both canceling suddenly with two er

Hello,
This job RSBKCHECKBUFFER is scheduled to run two times in production system starting at same time 12:00 pm and it was running fine till 12.04.11 but both the jobs started failing suddenly since 12.05.11 with two different sql errors at times
DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
1. Database error text........: "SQL1224N The database manager is not able to
accept new requests, has terminated all requests in progress, or has
terminated the specified request because of an error or a forced interrupt.
SQLSTATE=55032 row=1"
2. Database error text........: "SQL0911N The current transaction has been rolled
back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001 row=1"
Also both the job is scheduled to run with two different parameters
Parameters
&0000000000001
&0000000000000
Can anyone let me know what could be the reason of sudden failure since 12.05.11.
Also if I schedule the job to run only once in the system will it solve the problem ?

Hello Shradha,
1. Database error text........: "SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt.
SQLSTATE=55032 row=1"
- As far as I know this is serious problem in production environment. Looks like your DB was being restarted at that time. Please have your DBA team to review db2diag.log for error details.
2. Database error text........: "SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001 row=1" .
- Looks like second job was overlapped with first one. Please try to run the job once in a day or change of schedule of both jobs to ensure no overlap.
Thanks,
Siva Kumar

Error while adding a job to scheduler

Hello,
I have a batch job that is running fine in both DEV and QA environment. In DEV, I am able to schedule and run it daily. I created a similar schedule in QA environment using BODS Mgmt Console/Administrator. However, upon Activating the schedule, I am getting the following error message. Would someone know why would this error be thrown and steps to troubleshoot this error?
Thanks.
[Repository:AECON_DW_REPOSITORY Schedule:Daily_Run_QA Error:Error while adding a job to scheduler]
When contacting the server above exception was encountered, so it will be assumed the schedule is not active anymore.

Hi Rizwan Tahir ,
Delete the job server associated with the current batch job and recreate it.
Then try creating a new schedule using the new job server.
And take care that job server is created in QA environment.
Hope this should work.
Regards,

Background Job get Cancelled when executing the report. Reason?

Hi All,
I have scheduled a Back ground Job and executed Immediately.
when checking transacion SM37 the job get canceled.
How to find out the problem for the Job Cancellation.
Regards,
Viji

hi
After scheduling back ground job ( give a time laps of 2 min )
then go to sm37 ( at this moment , the job is not yet started) .
select ur job in sm 37 and when job starts processing , type JDBG as the command and press enter.
Now it will go to the debugging screen, where u will find system program . Now set a break point at the stements used in ur program from the debugging screen itself.( menu - breakpoint- breakpoint at - statement ) and press F8 .
Now you can start debug ur code.
Revrt back if any issues.
Regards,
Naveen

Background job getting failed every day

Hi,
This background job getting failed every day.But this job was running fine initial periord.Please help me out this issue.
SAP_REORG_UPDATERECORDS
SAP_WP_CACHE_RELOAD_FULL
SLCA_LCK_SYNCHOWNERS
Regards
Naanas.

If this is R/3, then none of the above jobs should exist in the system, if scheduled by default with other standard jobs, then these should be removed
Note 1034532 - Changes for standard jobs
Note 931436 - SLCA_LCK_SYNCHOWNERS standard job terminates

Creating a job and scheduling a job error in OEM

Hi, Everyone,
I am trying to create and schedule a job thru OEM. In the the pl/sql block provide i have given my code like this
begin
SET SERVEROUTPUT ON;
SPOOL C:\RFV_PROFILE_REPORT.LOG APPEND;
SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL;
EXEC PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL;
SPOOL OFF;
end;
i have created the job and scheduled it but i am getting this error:
Error # 6550
Details ORA-06550: line 2, column 5: PL/SQL: ORA-00922: missing or invalid option ORA-06550: line 2, column 1: PL/SQL: SQL Statement ignored ORA-06550: line 3, column 7: PLS-00103: Encountered the symbol "C" when expecting one of the following: := . ( @ % ;
could anyone pls help as this is very urgent.
Thanks in advance

Ah, the problem is you are confusing SQLPlus commands with PL/SQL.
SET SERVEROUTPUT ON; -- This is a SQLPlus command, not necessary here.
SPOOL C:\RFV_PROFILE_REPORT.LOG APPEND; -- This is a SQLPlus command, in PL/SQL to write out to a file you will need to call the UTL_FILE package to open a file for writing to. Except that the file you write to will appear on the database server, not your workstation, when the scheduled job runs.
SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL; -- In PL/SQL you need to SELECT columns INTO variables FROM tables. But in fact I guess you want to write the time to file using UTL_FILE again. However, you don't really need to do this, since scheduler will log the start time and run duration itself.
EXEC PAC_RFV_PROFILE_REPORT.CALL_ALL (200910); -- This is the SQLPlus equivalent of the PL/SQL command:
BEGIN
PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
END;
SPOOL OFF; -- This is a SQLPlus command, not necessary here.
So to summarise, all you really need is:
BEGIN
PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
END;
And the scheduled job will log the start time and duration in the database, which you can find here:
SELECT * FROM USER_SCHEDULER_JOB_RUN_DETAILS

User Profile Syncrhonization Scheduling twice a day

Client wants to schedule User Profile Synchronization from AD scheduling twice a day at 12.00 AM and 12.00 PM which includes any update in the AD photos also. How can I achieve this ?

You cannot set multiple single run schedules for timer jobs within SharePoint. You can only do one of the following:
Run every X minute
Run between X and N minute every hour
Run daily [between times]
Run weekly [between days/times]
Run monthly [days/times]
There is nothing in CA that will allow you to input 'run at noon and midnight', so the other option is to control it via PowerShell/Task Scheduler.
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SAP Back ground Jobs getting cancel automatically

Hi All,
All schedule Background jobs getting cancel automatically in ECC 5 server. Also not getting any job log in respective schedule job. please help me out with expert suggestions.
Regards
Gyan

1)Are the bgd workprocess free in the system currently?Check if there are any long running jobs holding them.
Bgd Work process are free but with error code 373,223,007 etc for all 5 bg wp
error reports from work directory as per work process:---
wp 22 :Fri Sep 25 15:07:04 2009
A
A ABAP/4 Program SAPLSYDB                                .
A Source LSYDBU27                                 Line 7.
A Error Code DBIF_DSQL2_DEFAULT_CR_ERROR.
A Module $Id: //bas/640_REL/src/krn/runt/abexsql.c#5 $ SAP.
A Function DsqlErrorHandler Line 1986.
A COMMIT/ROLLBACK error on "DEFAULT" database connection..
A
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c   12289]
C Rollback Work (0)
M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 252]
B ComRolHook(BEFORE_COMMIT, free_all) failed
B db_con_commit received an error return code in before-commit action
M ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   12036]
WP23: Fri Sep 25 15:06:05 2009
B dbtran INFO (init_connection '<DEFAULT>' [MSSQL:640.00]):
B   max_blocking_factor = 50, max_in_blocking_factor      = 255,
B   min_blocking_factor =   5, min_in_blocking_factor      = 10,
B   prefer_union_all    =   1, prefer_union_for_select_all =   0,
B   prefer_fix_blocking =   0, prefer_in_itab_opt          =   0,
B   convert AVG         =   1, alias table FUPD            =   0,
B   escape_as_literal   =   0, opt GE LE to BETWEEN        =   0,
B   select *            =0x00, character encoding          = STD / []:X,
B   use_hints           = abap->1, dbif->0x1, upto->0, rule_in->0,
B                         rule_fae->0, concat_fae->0, concat_fae_or->0
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c   12289]
C Rollback Work (0)
M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 252]
B ComRolHook(BEFORE_COMMIT, free_all) failed
B db_con_commit received an error return code in before-commit action
M ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   12036]
wp 24:Fri Sep 25 14:33:10 2009
M *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 252]
B ComRolHook(BEFORE_COMMIT, free_all) failed
B db_con_commit received an error return code in before-commit action
B ***LOG BZY=> unexpected return code 32768      calling DBACDS     [dbacds#2 @ 1225] [dbacds 1225 ]
B
*WP25: *** ERROR => BtcCleanUp: BtcLgAp-call failed (rc = 4) [btcjcntl.c   1308]*
M ThCallHooks: call hook >ITSP: EndOfSession< for event BEFORE_SESSION_CANCEL
M ThCallHooks: call hook >RtmClearSession< for event BEFORE_SESSION_CANCEL
M ThCallHooks: call hook >HttpClearSession< for event BEFORE_SESSION_CANCEL
M ThCallHooks: call hook >SpoolHandleHook< for event BEFORE_SESSION_CANCEL
M ***LOG R47=> ThResFree, delete (001009) [thxxmode.c   1284]
M ThCallHooks: call hook >ASTAT-collect commit handling< for event BEFORE_COMMIT
M ThCallHooks: call hook >rsts_before_commit< for event BEFORE_COMMIT
M ThCallHooks: call hook >rsts_after_commit< for event AFTER_COMMIT
M ThCallHooks: call hook >ThNoClearPrevErr< for event AFTER_COMMIT
M ThCallHooks: call hook >SpoolHandleHook< for event AFTER_COMMIT
M ThCallHooks: call hook >SAP-Trace buffer write< for event BEFORE_TASK_SWITCH
M ThCallHooks: call hook >ImcResetPtr< for event BEFORE_TASK_SWITCH
M ThCallHooks: call hook >DbgBeforeTaskSwitch< for event BEFORE_TASK_SWITCH
M ThCallHooks: call hook >HttpResetPtr< for event BEFORE_TASK_SWITCH
B
B Fri Sep 25 14:47:04 2009
B Disconnected from connection con_da={R/3*WORKFLOWTRACE,26000006,1}
please let me know where i can send log file if req.
2)Check for the sm21/sm50 bgd wp traces.
Getting so may Tem se management errors.
Some TemSe objects are stored in files. To do this, a path name is set up from the TemSe object name. To be able to use this path, TemSe management requires a directory. It attempted to create it itself. However, this did not succeed.
3)Check if the filesystem is full as you suggest no logs are being written.
File system having free space
4)Check if the user who has scheduled the job is locked ?
user unlocked
please help me to resolv this issue.
thanks
Gyan
Edited by: Gyan Prakash on Oct 9, 2009 10:02 AM

IDoc getting scheduled in stead of processed due to no resources available

I know this is supposed to go into Basis-forum, but I can't find applicable one. If you can redirect me please do so.
Setup:
Solution Manager, CUA & ECC6
Issue:
Sometimes when triggering changes from CUA to an ECC client several IDocs are fired towards that client.
(User Master Record changes, unlocks, role assignments, etc.).
Looking in BD87 I sometimes see that of these IDocs, some are processed directly (transferred to application),
However some of them remain in Status 64 (IDoc ready to be transferred to application).
If I Right-Click -> Process, they are handled perfectly so why did they have to be waiting?
The reason SAP throws for these IDocs is:
Immediate Processing in Job '0000000000005010 '
Message no. EA187
Diagnosis
At the time of IDoc generation, there were no resources for immediate processing and your system is configured so that if this happens, IDoc processing should be started in a job. Therefore, the job '0000000000005010' was started.
Procedure
If the IDoc still has status 64, look for the cause of the error in the log for that job.
Question:
We have via WE20 profiles set to process all IDocs immediately, then why do some of them still get
scheduled in jobs? (Due to lack of resources for immediate processing?).
Where can I check these 'resources' ?
Edited by: Mujo on Jan 4, 2012 2:41 PM

Hey Alex,
Yes, I have been looking into both available worker processes all seem fine. Also I've been checking to pick up
those IDocs that are in wait-status to be picked up by a (to be) scheduled job.
However a few questions:
- is it common that CUA changes fire multiple IDocs? (in my case 3, only for something trivial as removing 1 composite role
on a CUA-child system with 1 end user
- what I don't really understand yet is if this is fired in batches of (in this case) only 3 IDocs, how come the first is processed and
the other 2 are not? What is blocking that? Is 1 worker process used for processing each IDoc or 1 worker process for all 3 IDocs? To jump into your comment of "when a lot of IDocs are fired", as said: they're only 3.
- can it be that the 'program" that processes the 1st IDoc change to the user master record is then 'occupying' the change mode and that therefore the other 2 are not able to being processed or can it be that the changes just come too fast after one another?
- I would think that when CUA is installed and RFCs and IDoc types are correctly configured this resource problem
should not act up with standard SAP ECC6 settings, for firing something trivial/simple as a composite role change
- last question: if I should schedule a job to pick up the IDocs that are in waiting-to-be-processed status, what is common
interval for this? (every minute? every 5 minutes?) and what's the program to schedule?
EDIT: found at least answer to this question:
RBDAPP01. Processes inbound IDocs (status 64) that have been buffered to support mass
processing. The use of RBDAPP01 in the process flow is described in Chapter 4, "The Inbound EDI
Process." Steps to execute the RBDAPP01 program are listed in Chapter 10, "Testing the EDI
Interface."
Looks strange to me as then the point of CUA making direct changes is somewhat undermined. In this case our CUA is being fed from a Sun IDM system, and the changes on SAP landscape will be 'less near-realtime', if I express that correctly.
Your thoughts are highly appreciated.
Edited by: Mujo on Jan 5, 2012 9:47 AM
Edited by: Mujo on Jan 5, 2012 10:21 AM

Po message getting triggered twice

Hi,
recently we have upgraded SRM5.0 to SRM7.0 with ECC6.0 EHP pack4 .
we have a problem when we create PO from SRM shopping cart in ECC.PO message is getting triggered twice. Th issue was not there before upgrade.
Can anyone please help me resolving this.
Thanks & Regards,
Beena.

Hi,
While making a purchase requisition, you can refer to either last purchase or can take a reference of blanket purchase agreement, just check for that particular supplier that whether in the requisition table while importing requisition from maximo, there exist a reference of any last purchase or any blanket purchase agreement. If yes then autocreate workflow will get trigger automatically which might be schedule on your instance, which will create a purchase order for that particular supplier.
Thanks & Regards
Ankur Dawra

Job getting scheduled twice

Similar Messages

Maybe you are looking for