GRC 5.3 I get errors like this one. Anyone know how to solve them?

error 2011-06-15 10:34:20:188 WorkFlowEmailReminderManager.java@351:runEmailReminder() : Email Reminder is set to 0 for workflow type : RISK /Applications/AccessEnforcer com.virsa.ae.commons.AELogger sap.com/grc~aeear st000068 Server 1 0_72951

Vollstndiger Nachrichtentext

WorkFlowEmailReminderManager.java@351:runEmailReminder() : Email Reminder is set to 0 for workflow type : RISK

501 Views
o

Topics: Governance, Risk, and Compliance

Average User Rating (0 ratings)

Re: Error: Email Reminder is set to 0 for workflow type :

Kristian Madsen Jun 24, 2011 4:27 PM (in response to Kristian Madsen) Alose this error: com.virsa.ae.configuration.bo.BackgroundJobsBO : updateJobStatus(BackgroundJobPO) : : Exception occured while updating Background Job Status HR Triggers Load Data: Background job alreay in desired status. Is Running = true [EXCEPTION] com.virsa.ae.core.ObjectAlreadyExistsException: Background job alreay in desired status. Is Running = true * at com.virsa.ae.dao.sqlj.BackgroundJobDAO.updateJobStatus(BackgroundJobDAO.sqlj:245)* * at com.virsa.ae.configuration.bo.BackgroundJobsBO.updateJobStatus(BackgroundJobsBO.java:226)* * at com.virsa.ae.configuration.bo.BackgroundJobsBO.updateJobInitiation(BackgroundJobsBO.java:287) * * at com.virsa.ae.backgroundjobs.BackgroundTask.updateTaskInitiation(BackgroundTask.java:92)* * at com.virsa.ae.backgroundjobs.BackgroundTask.run(BackgroundTask.java:49)* * at java.util.TimerThread.mainLoop(Timer.java:432)* * at java.util.TimerThread.run(Timer.java:382)* Edited by: Kristian Madsen on Jun 24, 2011 4:27 PM
o

Report Abuse

o o

Like (0)

Re: Error: Email Reminder is set to 0 for workflow type :

Kannan Balasubramanian Oct 19, 2011 5:43 AM (in response to Kristian Madsen) Hi Kristain, just wondering if you get a fix for the issue you're facing? we have the same issue here started after upgrading our grc cup 5.3 to SP16. Thanks Kannan

Report Abuse

Like (0)

Re: Error: Email Reminder is set to 0 for workflow type :

Miguel Ibarra Feb 25, 2013 2:15 PM (in response to Kristian Madsen) Kristian, I'm with the same error you raise, what was the solution working applied

regards /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// ///////////////////////////////////////////////////////////////////////////// hi all need some information or the steps for Background Jobs Thank you Swapna Correct Answer by Dasari Narendra on Sep 19, 2007 11:28 AM hi <b>Creating a Background Job Using the Job Wizard</b> From the main menu select System>Services>Jobs>Define Job (transaction SM36). Press the Job Wizard button and step through the screens as follows: 1:Continue 2: Enter a name for your job. Continue. 3: Continue with ABAP Program Step selected 4: Enter the ABAP Program Name and variant name. Press the Print Parameters button, specify the required printer and set the "Time of Print" to "Send to Print Spooler for now".

Press green tick Continue 5: If more reports need to be added to the job tick the checkbox, press continue and repeat screens 3 and 4. 6: Select how the job is to scheduled (eg Date and Time) 7: Enter the required scheduling information ( eg Date and Time) and if required tick "Periodic Jobs" 8: If "Periodic Job" was selected select the frequency (eg Monthly) 9: Check the job details and press Complete ==== Viewing Background Jobs From the main menu select System>Services>Jobs>Job Overview (transaction SM37). Enter the required selection criteria and press Execute To view the job log, tick the required job and press the "Job Log" button. To view the output from the job, tick the required job and press the "Spool" button. ===== Scheduling Background Job http://help.sap.com/bp_lblv1500/LBL_UK/HTML/LBLUK_Solution_Map/5FF7FDF4F7734A2EA38 EF7898AB3621D.htm Background Processing http://help.sap.com/saphelp_nw04s/helpdata/en/ed/a9bb3f8e236d3fe10000000a114084/frameset.htm Debugging a Background Job http://searchsap.techtarget.com/tip/0,289483,sid21_gci933590,00.html Sample Screen Shots http://www2.warwick.ac.uk/services/finance/sap/help/howtoguides/backgroundjobs/ Reward if Useful Thanx & Regards Naren.. See the answer in context Helpful Answer by Pankaj Sharma

484 Views

Average User Rating (0 ratings)

Correct AnswerRe: Back ground Jobs

Dasari Narendra Sep 19, 2007 11:28 AM (in response to Swapna Latha) hi

<b>Creating a Background Job Using the Job Wizard</b> From the main menu select System>Services>Jobs>Define Job (transaction SM36). Press the Job Wizard button and step through the screens as follows: 1:Continue 2: Enter a name for your job. Continue. 3: Continue with ABAP Program Step selected 4: Enter the ABAP Program Name and variant name. Press the Print Parameters button, specify the required printer and set the "Time of Print" to "Send to Print Spooler for now". Press green tick Continue 5: If more reports need to be added to the job tick the checkbox, press continue and repeat screens 3 and 4. 6: Select how the job is to scheduled (eg Date and Time) 7: Enter the required scheduling information ( eg Date and Time) and if required tick "Periodic Jobs" 8: If "Periodic Job" was selected select the frequency (eg Monthly) 9: Check the job details and press Complete ==== Viewing Background Jobs From the main menu select System>Services>Jobs>Job Overview (transaction SM37). Enter the required selection criteria and press Execute To view the job log, tick the required job and press the "Job Log" button. To view the output from the job, tick the required job and press the "Spool" button. ===== Scheduling Background Job http://help.sap.com/bp_lblv1500/LBL_UK/HTML/LBLUK_Solution_Map/5FF7FDF4F7734A2EA38 EF7898AB3621D.htm Background Processing http://help.sap.com/saphelp_nw04s/helpdata/en/ed/a9bb3f8e236d3fe10000000a114084/frameset.htm Debugging a Background Job http://searchsap.techtarget.com/tip/0,289483,sid21_gci933590,00.html Sample Screen Shots http://www2.warwick.ac.uk/services/finance/sap/help/howtoguides/backgroundjobs/

Reward if Useful Thanx & Regards Naren..

o

Report Abuse
o

Like (0)

Re: Back ground Jobs

VijayaSateeshKumar Kandula Sep 19, 2007 11:59 AM (in response to Swapna Latha) Hi Swapna Latha, BACKGROUND JOB PROCESS If its a custom program, your should talk to the programmer who wrote the program by finding out what is the program running behing the job. Aslo, if you want to find out on your own, you can try to run the SQL trace on it using ST05 and then analyze the trace for the expensive statements. Check the trace wherevere it shows the fetch time marked in RED and then, you can try to analyze the SQL statement running in the backgroung, to see if the programmer is doing an unnecessary select/fetch, reading too many records etc. Hope that helps.. You can try the following:

go to SM36 and create background job by giving job name,job class and job steps (JOB SCHEDULING) BATCH If the user forgets to opt for keep session then the session will be automatically removed from the session queue(log remains). However if session is processed we may delete it manually. ii)if session processing fails data will not be transferred to SAP database table. Direct Input. Without calling the screens but all the validations should be done and only for master datas upload.

Direct Input method: 1. Only for error free datas and also master data updation. 2. It will directly updates the database table. No screens involved. 3. Transaction BMVO or Program RBMVSHOW has been used. BDC(Batch Input Session): 1. Screens will be called programmatically. 2. First sessions will be created then we'll run the seesions in SM35 transaction. 3. Synchronous database update. After the processing the session only database update will occur.

Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System. Features: BDC is an automatic procedure. This method is used to transfer large amount of data that is available in electronic medium. BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system). BDC uses normal transaction codes to transfer data. Types of BDC: CLASSICAL BATCH INPUT (Session Method) CALL TRANSACTION BATCH INPUT METHOD: This method is also called as CLASSICAL METHOD. Features: Asynchronous processing. Synchronous Processing in database update. Transfer data for more than one transaction. Batch input processing log will be generated. During processing, no transaction is started until the previous transaction has been written to the database. CALL TRANSACTION METHOD : This is another method to transfer data from the legacy system. Features: Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement. Updating the database can be either synchronous or asynchronous. The program specifies the update type. Transfer data for a single transaction. Transfers data for a sequence of dialog screens. No batch input processing log is generated. Differences between Call Transaction and Sessions Method: Session method. 1) Synchronous processing. 2) Can transfer large amount of data. 3) Processing is slower. 4) Error log is created 5) data is not updated until session is processed. 6) Generally used for back ground jobs. 7) At a time we can update to more than one screens. Call transaction.

1) Asynchronous processing 2) can transfer small amount of data 3) processing is faster. 4) Errors need to be handled explicitly 5) data is updated automatically 6) for background n fore ground jobs. 7) At a time we can update to a single screen. Direct Input method: Without calling the screens but all the validations should be done and only for master datas upload. 1. Only for error free datas and also master data updation. 2. It will directly updates the database table. No screens involved. 3. Transaction BMVO or Program RBMVSHOW has been used. For BDC: http://myweb.dal.ca/hchinni/sap/bdc_home.htm https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc& http://www.sap-img.com/abap/learning-bdc-programming.htm http://www.sapdevelopment.co.uk/bdc/bdchome.htm http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.ht m http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

Check these link: http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm http://www.sap-img.com/abap/question-about-bdc-program.htm http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/ http://www.planetsap.com/bdc_main_page.htm call Transaction or session method ? Please Reward If Really Helpful, Thanks and Regards, Sateesh.Kandula
o

Report Abuse
o

Like (0)

Re: Back ground Jobs

venkata k Feb 29, 2012 11:07 AM (in response to Swapna Latha) dear swapna SM36 Define Background Job SM37 Background Job Overview SM39 Job Analysis

to have an idea about the background scheduling let us take an example of a long report. Suppose we execute this report in interactive mode, it takes several minutes and during time the SAP System is blocked for any further input. As a result, you will not be able to interact with SAP sessions anymore. However, when you run the report non-interactively, you can interact with the SAP sessions while processing the report in the background. For executing jobs in non-interactive mode, schedule the job for background processing. To create a background processing job you should specify: The name of the report The name of any variant it needs What to do with output When to start it After this, the SAP system does not require users intervention and can proceed with the job even without you. It executes the report and prints the output using printer or output controller. While scheduling a job in background process, three parameters should be specified. These parameters are: Definition of programs Its start time The printing specification for getting the prints as required After this, you can check whether your job was executed successfully and display a log of any system messages. For scheduling background processing, you have to direct the system to process an ABAP/4 or external program in the background. This is a two-step process: Scheduling the program Releasing the job This needs to have a special authorization for releasing and scheduling the job. Generally, the system administrator, who organizes and monitors background processing, supervises the release of these jobs. Many users are also authorized to schedule background processing of reports. You cannot schedule a job unless and until you have a release authorization. If a user is authorized and has specified a start date or selected "start immediately," he or she can release the job. Authorized users can change start time. A program can be scheduled as a separate job or you can append it to an existing job, which has not yet been processed. Background process can be run while doing some other online work. However, this can adversely affect online operation and should be avoided. For example, if you run a program that locks the database, the work of online users will be hampered or stopped. Often, long-running reports are scheduled automatically or semi-automatically for background processing. First Step Initiate the job scheduling function. Standard job scheduling must be used in case of scheduling of an external command or external program as a background job and ABAP job scheduling function can be used to schedule ABAP programs. For starting a standard job scheduling function choose the following:

Administration menu bar option CCMS option Jobs option Definition option. For starting ABAP job scheduling function, navigate to ABAP Editor and choose Program menu bar option execute option Background option. Second Step now define a job. Using the Job Wizard you can define your job. From the Application toolbar, choose the wizard button. After this, the initial screen of the SAP Job Wizard appears. The Job Wizard is available only from the standard job scheduling function. Third Step Now, you have to save the job. When it displays the message "Job saved" it means the job has been successfully scheduled. We know that a job must be released before it is scheduled. Only authorized users can release the job, otherwise your system administrator will release your job. Fourth Step this is the last step of scheduling. In this step you have to check the status of your job. For this you need to choose System menu bar option Own jobs option. In SAP System, the background processing runs according to your instructions. In case a list is generated by the report, the report either prints directly or waits for you in the SAP output controller. The status of background processing can be checked for its correctness.

rewards if it helps siva

o

Report Abuse
o

Like (0)

Helpful AnswerRe: Back ground Jobs

Pankaj Sharma Feb 29, 2012 11:07 AM (in response to Swapna Latha) Hi Swapna, Please follow these steps ... 1. Call Transaction SM36 or choose CCMS Jobs Definition.

2. Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field. 3. Set the jobs priority, or Job Class: High priority: Class A

Medium priority: Class B

 4.

Low priority: Class C In the Target server field, indicate whether to use system load balancing.

For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty. To use a particular application server to run the job, enter a specific target server.

5. If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button. 6. Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen. 7. Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step. 8. Save the fully defined job to submit it to the background processing system.

9. When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview. Hope this will be useful award points if useful.. Cheerss!!! Pankaj Sharma
o

Report Abuse
o

Like (0)

Re: Back ground Jobs

Swapna Latha Sep 19, 2007 1:50 PM (in response to Swapna Latha) Thanks All Swapna /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////////////////////// Hi All, I have scheduled a backgroundjob, but it was cancelled with an error DBIF_RSQL_INVALID_RSQL the error analysis shows the reasons Possible errors: o The maximum size of an SQL statement has been exceeded.

o The statement contains too many input variables. o The space needed for the input data exceeds the available memory. o ... i don't think the first two resons are suitable bcoz , my select statement has got two fields selecting from a single table and has got two ranges in the where clause. can any one explain the meaning of the resons, I would appreciate for your help Regards, sre. Edited by: sre on Jan 13, 2009 10:17 AM Edited by: Julius Bussche on Jan 14, 2009 2:47 PM Removed greetings in the subject title 460 Views
o

Topics: ABAP

Average User Rating (0 ratings)

Re: Hi All, Runtime error in background job

Sandipan Ghosh Jan 13, 2009 10:20 AM (in response to s re) Hi, What are you doing after selecting data from the table? Are you displaying the selected data from the spool. Regards Sandipan
o

Report Abuse
o

Like (0)

Re: Hi All, Runtime error in background job

s re Jan 13, 2009 10:26 AM (in response to Sandipan Ghosh) Hi Sandipan, Thanks for your reply, after selctinf i am looping this internal table to cehck futher conditions on other tables tables. and then displaying the data. here is the code. if lv_port > 0. clear lv_port. sort i_portiona. select vkont gpart from fkkvkp into table i_gpart

where vkont in r_vkont and gpart in r_gpart. if sy-subrc = 0. loop at i_gpart. clear: lv_port_in, lv_port_out, lv_multi. read table i_portiona with key vkonto = i_gpart-vkont. if sy-subrc = 0. clear lv_port. lv_str_portion = i_portiona-portion. loop at i_portiona where vkonto = i_gpart-vkont. if i_portiona-portion in s_port. *-----flag to show that there is at least one portion that matches.................

can you please explain whetehr it is related to database problem or program problem regards, sre

Report Abuse

Like (0)

Re: Hi All, Runtime error in background job

Arun Ramachandran Jan 13, 2009 10:23 AM (in response to s re) Hi , Can you tell where does the error occurs , in an select statement or some other statement. Regards Arun o Report Abuse
o o

Like (0)

Re: Hi All, Runtime error in background job

s re Jan 13, 2009 10:33 AM (in response to Arun Ramachandran) Hi Arun, Thanks for your reply, the dump analysis shows that the error occurs on the select statement.

if lv_port > 0. clear lv_port. sort i_portiona. select vkont gpart from fkkvkp where vkont in r_vkont and gpart in r_gpart.

into table i_gpart

if sy-subrc = 0. loop at i_gpart. clear: lv_port_in, lv_port_out, lv_multi.

read table i_portiona with key vkonto = i_gpart-vkont. if sy-subrc = 0. clear lv_port. lv_str_portion = i_portiona-portion. loop at i_portiona where vkonto = i_gpart-vkont. if i_portiona-portion in s_port. *-----flag to show that there is at least one portion that matches the *-----selection criteria lv_port_in = 'X'. can you please give some idea on this issue. Regards, Sre. Edited by: sre on Jan 13, 2009 10:33 AM

Report Abuse

Like (0)

Re: Hi All, Runtime error in background job

Arun Ramachandran Jan 14, 2009 1:58 PM (in response to s re) Hi, In the statement select vkont gpart from fkkvkp into table i_gpart where vkont in r_vkont and gpart in r_gpart. Please check if the requiremnt is to select all the data in case there is no value in the ranges r_vkont and r_gpart. This might be casuing the error as it will select all the records in the table if the two ranges are initial. Regards Arun

Report Abuse

Like (0)

Re: Hi All, Runtime error in background job

Pawan Kesari Jan 14, 2009 2:05 PM (in response to s re) How many records were there in ranges r_vkont and r_gpart. If records exceeds a certain limit the SQL statement will not be passed to Database server. Check if number of records in r_vkont and r_gpart (taken together) doesn't exceed 500. You can try with more number of records if it works.. o Report Abuse
o o

Like (0)

Re: Hi All, Runtime error in background job

Michael Evershed Jan 14, 2009 9:20 PM (in response to Pawan Kesari) Anytime I see this in my system it's like Pawan Kesari suggests. Too many records in the ranges. I don't know what the exact limit is, but if there's more than about 1000 entries in the ranges that generally triggers the dump you're getting. Report Abuse

Like (0)

Re: Runtime error in background job

Micky Oestreich Jan 14, 2009 2:53 PM (in response to s re) When using the INTO TABLE statement, make sure that the internal table i_gpart has exactly those fields you are selecting from database. Otherwise, use the INTO CORRESPONDING FIELDS addition. o Report Abuse
o

Like (0)

Re: Runtime error in background job

Rajwin Singh Sood Jan 15, 2009 5:32 AM (in response to s re) this type of error normally comes up if the number of records are more to be displayed at runtime. I suggest that you to first ensure that the internal table which you are using is of the same structure if you are using only limited fields then please use SELECT INTO CORRESPONDING FIELDS. after ensuring this please also check whether in the where clause you have the used Primary Key fields in the proper order as originaly defined in the database table. this is one of the most common reason that this kind of dump is generated. if this is also proper then I suggest you use UPTO n RECORDS in the select query where n is the number limiting your records while selecitng it. Please try it and let me know whether you were successful.
o

Report Abuse
o

Like (0)

Re: Runtime error in background job

Mohammad MahaboobKhan Jan 15, 2009 6:31 AM (in response to s re) Hi, Check once to run in Back ground mode.

Regards Md.MahaboobKhan

Report Abuse
o

Like (0)

Re: Runtime error in background job

Venkateswararao korivi Jan 15, 2009 6:37 AM (in response to s re) HI, I too faced this kind of problem, what we did was , we removed the ranges and then placed all the records in an internal table and then used FOR ALL ENTRIES, after that we did not received any DUMP in the back ground job. Regards, Venkatesh
o

Report Abuse
o

Like (0)

Re: Runtime error in background job

Anil Nautiyal Jan 15, 2009 6:38 AM (in response to s re) Hi Sre, The problem is with the SQL Statement. This problem may arise when u have given wrong indexes to fetch the data from server. Try to run the same query at server part and then check whether it gives the dump or not?? Regards, Anil N.
o

Report Abuse
o

Like (0)

Re: Runtime error in background job

s re Jun 4, 2009 11:57 AM (in response to s re) thanks ////////////////////////////////////////////////////////////////////////////////// Troubleshooting Print Spool Authorization Errors for User with All the Required Authorizations created by Raghu Boddu on Nov 18, 2010 9:02 AM, last modified by Raghu Boddu on Aug 8, 2012 9:03 AM Version 3 inShare

This article will provide the troubleshooting steps to resolve an issue with Spool Authorizations for user with all the required authorizations View Document Topics: Identity and Access Management , Security Content Type: Article 113 Views //////////////////////////////////////////////////////////////////////////// Spool Error - Errors occurred processing this print request This question is Assumed Answered.

Subramanya Srinivas Mullapudi May 2, 2008 11:44 PM Hi, I have a problem printing documents through spool. 1. I run a form from Form Builder, execute and select to print from spool 2. In SP02, I select the spool request created and Select Direct Printing. Spool request Status is changed to error and following is the error log. I get this for all print requests from spool. When I print these documents directly, I have no problem. I understand there is some problem with the spool server but do not know what it is. I also observed that when the spool access method is G - I have no problems in printing. Printer: HP HP laserJet PS (2430) Host Spool Access Method: L: Print Locally Using LP/LPR. Device Class: Standard Printer. ECC6.0 SAP spool error log ===================== Print request processing log The host spool is reporting errors Message from host spool: D:\usr\sap\BS9\DVEBMGS00\data\000001615100001.BS9 is currently being printed End of message Command used: print /d: bs107.platinumdb.com\HP01 D:\usr\sap\BS9\DVEBMGS00\data\000001615100001.BS9 Errors occurred processing this print request Error during print request output. l_rc = 1 There may be no printout Most important attributes of spool request

Request number 16151 Request name PBFORM HP01 SMULLAPUDI Client 800 Owner SMULLAPUDI Request attributes Time created 2008050118454600 Remaining life +00007235918 Dispo 1 (Go/Hold) H Dispo 2 (Keep/Delete) K Dispo 3 (Indirect/Direct) D Default output device HP01 Default no. copies 1 Format G_RAW Main print request characteristics Spool request number 16151 Print request number 1 Print request attributes Time created 2008050118471500 Output device HP01 Format G_RAW Character converter active when first problem occurred No information available I am working on this since 4 days with no solution. Kindly help. Thank you, Vasu 697 Views Average User Rating (0 ratings)

Re: Spool Error - Errors occurred processing this print request

Hariprasad kakumanu May 3, 2008 3:37 PM (in response to Subramanya Srinivas Mullapudi) Hi What about the other report's print out? are they coming ok?
o

Report Abuse

Like (0)

Re: Spool Error - Errors occurred processing this print request

Rahul Deo May 4, 2008 1:16 AM (in response to Subramanya Srinivas Mullapudi) Hi Please confirm that SAPLPD is functional on your system. If not try installing that.

Hope this helps. Regards Rahul

o

Report Abus

//////////////////////////////////////////////////////// BAP runtime errors "SPOOL_I/O_ERROR" This question is Assumed Answered.

Zulkarnain yusop May 7, 2010 10:19 AM Hi All, I had problem when run the job program "SAPFGRWE". Suddenly the job terminated and the error message appear is "ABAP runtime errors - SPOOL_I/O_ERROR" . I'm using DB Oracle. SAP Release is 40B. Please help me on this matter.

Thank You 1746 Views Average User Rating (0 ratings)

Re: ABAP runtime errors "SPOOL_I/O_ERROR"

Guest May 7, 2010 10:50 AM (in response to Zulkarnain yusop) Hi, Cleanup your old spool requests suing the report: RSPO1041. Please do a temse consistency check in txn. SP12 and then clearn the entire temse. Also, refer to SAP Note 1336 (Spooler reports data base I/O error) for this error. Regards, Shitij

Like (0)

//////////////////////////////////////////////////////////////////////////////////////////////////////////=================/////// ///////////////////////////////////////////////////////////////////////////// ckground job giving spool errors This question is Assumed Answered.

willard chingarande Feb 6, 2009 1:47 PM Hi gurus. i am executing a job in the background but its terminating with a SPOOL OVERFLOW ERROR even after cleaning the spool. i also tried to execute the job for only 2 records but its still terminating. Is it possible to stop a background job from writing to the spool and make the program create its own spool when executing in the background 631 Views o Topics: ABAP Average User Rating (0 ratings)

Re: background job giving spool errors

Gurpreet Singh Feb 6, 2009 2:29 PM (in response to willard chingarande) Hi, Background request is always store in TEMSE Buffer which hold spool request. So spool willl be always used for background and print job. You can increase the number of the spool. OSS NOTE: 48284 this note gives instructions on updating the SPO_NUM number range object. Regards, Gurpreet.
o

Report Abuse

o o

Like (0)

Re: background job giving spool errors

SRINIVAS RATHOD Apr 9, 2009 10:34 AM (in response to Gurpreet Singh) hello,

i written below coding. submit (progname) with pa_aennr eq 'X' sign 'I' to sap-spool new list identification 'X' without spool dynpro destination 'LOCL' immediately ' ' keep in spool ' ' via job l_jobname number l_jobnumber and return. and if i go to sm37 , it should show only one spool for job, but i got many spool with same number for one job. could you please helpme out. Report Abuse tp related errors This question is Assumed Answered.

stephen herky Nov 10, 2007 11:02 AM Hi, I faced the below errors in STMS a)Transport control program ended with error code 0208 msg no XT200 An error occured while opening a tp command command : SHOWPRAMAS SID pf= hostname\sapmnt\trans\bin\TP_DOM return code:0208 error text:error in transport profile(param missing ,unknown,request; b) when I ran RSTPTEST under transport profile i found tp profile - cannot be read version - tp profile has an invalid format under tp call : DB connect - link to DB failed offline call - error when opening an RFC connection c ) another important thing is, when I am opening SE01, system is not taking too much of time and eventually end with runtime exceeded message. gimme your valuable comments herky

1396 Views Average User Rating (0 ratings)

Re: tp related errors

Markus Doehr Nov 10, 2007 1:13 PM (in response to stephen herky) Check that the directory \usr\sap\trans\bin is mounted and contains your tp profile.

-Markus
o

Report Abuse

Like (0)

Re: tp related errors

Afi C Nov 11, 2007 6:23 AM (in response to stephen herky) Hi, Please check ur RFC connections. Ur RFC destination looks broken here. Also, are you up to date with patches and kernel? Thanks,
o

Report Abuse

Like (0)

Re: tp related errors

stephen herky Nov 12, 2007 7:48 AM (in response to stephen herky) I started to face this problem for the last 10 days earlier it was good
o

Report Abuse

Like (0)

Re: tp related errors

stephen herky Nov 12, 2007 9:38 AM (in response to stephen herky) I found there was no problem with RFC
o

Report Abuse

Like (0)

Re: tp related errors

Afi C Nov 12, 2007 7:08 PM (in response to stephen herky) HI, If your SE01 tcode comming back with runtime/timeout, Please check your support packs. You might need to apply patches.. Are you upto date with kernel and patches? go to tcode spam, check spam version and click package level.. let me know! Thanks,
o

Report Abuse

o o

Like (0)

Re: tp related errors

Markus Doehr Nov 12, 2007 7:22 PM (in response to Afi C) Did you check if your transport profiles are available under \usr\sap\trans\bin and if they can be access by user <sid>adm?

-Markus

Report Abuse

Like (0)

Check DB Errors This question has been Answered.

Shivam Mittal Feb 20, 2010 6:50 AM

Dears, We are facing below errors in CheckDB in DB13: BR0978W Database profile alert - level: ERROR, parameter: FILESYSTEMIO_OPTIONS, value: ASYNCH (<> SETALL) BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 14230528 (>< 4096,512 KB) BR0978W Database profile alert - level: WARNING, parameter: MAX_DUMP_FILE_SIZE, value: UNLIMITED (>< 100000,10000) BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (set in parameter file) BR0978W Database profile alert - level: WARNING, parameter: PARALLEL_EXECUTION_MESSAGE_SIZE, value: 2152 (>< 16384,4096) BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE) BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE (<> FALSE) BR0978W Database profile alert - level: WARNING, parameter: STAR_TRANSFORMATION_ENABLED, value: FALSE (<> TRUE) BR0978W Database profile alert - level: WARNING, parameter: STATISTICS_LEVEL, value: TYPICAL (set in parameter file) Please suggest reason and solutions of the issue. Shivam

Correct Answer by chaitanya nagalla on Feb 20, 2010 7:43 AM Hi, please check the note Note 830576 - Parameter recommendations for Oracle 10g for the oracle parameters and also install the intrem patches based on that you change the oracle parameters. Also as Bhavik G. Shroff said check the note 900522. Thanks, Chaitanya. See the answer in context

1817 Views Average User Rating (0 ratings)

Re: Check DB Errors tatus 56 - IDOC with errors added This question has been Answered.

Varun K Dec 12, 2007 11:18 AM

Hi everyone, I was configuring File to IDOC Scenario, in the receiving R/3 system, i am getting error as Status 56 - IDOC with errors added "<b>EDI: Partner Profile not available</b>". but i had already created Partner profile in WE20. Regards, Varun Reddy.K

Correct Answer by Jakub Turminski on Dec 14, 2007 10:07 AM Hi, Please, find out what is the value of SNDPRN and SNDPRT in your idoc and cofigure the corresponding partner profile. Please ref this doc too: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtr oot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34">A Beginners Guide to SAP XI Settings, Part II</a> Regards, Jakub See the answer in context Helpful Answers by Sai Ganesh, Vishal Kharat

1641 Views Average User Rating (0 ratings)

Helpful AnswerRe: Status 56 - IDOC with errors added

Vishal Kharat Dec 12, 2007 11:22 AM (in response to Varun K) Hi Varun Please look at the very important link:-

http://publib.boulder.ibm.com/tividd/td/ITMAN/SC23-4812-00/en_US/HTML/sa51mst256.htm Vishal
o

Reward points for useful Help

Report Abuse

Like (0)

Helpful AnswerRe: Status 56 - IDOC with errors added

Sai Ganesh Dec 12, 2007 11:23 AM (in response to Varun K) Hi Varun, The below link will help u in solving u r problem https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96b3d942bd1539 Just try follow the steps followed in above mentioned link

And also check u r RFC connection in TC "SM59".

Reward with ponits if helpful

Regards Sai Ganesh

Report Abuse

Like (0)

Re: Status 56 - IDOC with errors added

Mugdha Kulkarni Dec 12, 2007 11:34 AM (in response to Varun K) Have you maintained inbound partner profile? Find Logical system name from your sender service-->Adapter Specific identifiers. with this name Partner profile has to be created on R3 Refer Configuration steps required for posting idoc's(XI) /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi Report Abuse

Like (0)

Re: Status 56 - IDOC with errors added

Jakub Turminski Dec 12, 2007 11:37 AM (in response to Varun K) Hi,

On receiver system you must configure partner profile for your sender system - we20. Add your message type to inbound parameters and configure the appropriate process code. Regards, Jakub

Report Abuse

Like (0)

Re: Status 56 - IDOC with errors added

Varun K Dec 14, 2007 9:17 AM (in response to Jakub Turminski) Hi Jakub Turminski, I had done all the configuration required for file to idoc scenario, defined Partner profile in Receiver system with sender file system name. But still i am getting the same error. Regards, Varun Reddy.K
o

Report Abuse

o o

Like (0)

Correct AnswerRe: Status 56 - IDOC with errors added

Jakub Turminski Dec 14, 2007 10:07 AM (in response to Varun K) Hi, Please, find out what is the value of SNDPRN and SNDPRT in your idoc and cofigure the corresponding partner profile. Please ref this doc too: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtr oot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34">A Beginners Guide to SAP XI Settings, Part II</a> Regards, Jakub

Report Abuse

Like (0) Go to original post

inShare Actions

ECC 5.0 Two Errors ..... This question is Not Answered.

Shailesh Mamdiwar Jul 30, 2007 12:46 PM Hi, I have installed system ECC 5.0 as sandbox. With Win 2003 Oracle 9.2.0.6 with 2 GB RAM. HDD 320GB 160+160 Two HDD's (one partiion on each HDD of 160GB) First Question : When i am trying to execute DB02 its giving me a pop up called "will take some time to collect from db monitors " when i said yes. The process is ending with TIME_OUT Error ? How to overcome this. I suppose 600sec is not enough for collecting stats. I tried to increase max runtime for dia process to 1000 but after restarting msg sever is not starting... Question Two : When i am tring to change any parameter in rz10. like changing no of wp, changing size of PHY_MEM etc. After restarting the server for changes to apply i am not getting any instance in MMC console. so that i can't start my sap. After i overwrite profiles from backup. then its working fine? What may be the cause ? Thanks in Advance. Helpful Answer by Ganesh Paisa

448 Views Average User Rating (0 ratings)

Re: ECC 5.0 Two Errors .....

Peter Simon Jul 30, 2007 2:07 PM (in response to Shailesh Mamdiwar) I don't like this RZ10 to maintain profile parameters.

you can do a lot of finger trouble which will result in non startable systems. first you have to import the profiles of the active servers. after that you can try to add/change profile parameters and activate them. peter
o

Report Abuse

Like (0)

Helpful AnswerRe: ECC 5.0 Two Errors .....

Ganesh Paisa Jul 30, 2007 2:11 PM (in response to Shailesh Mamdiwar) Hi, 1. Change parameter through RZ10 rdisp/max_wprun_time = 1200 or add above line in Instance profile from OS Level (Not preffered) 2. Check for profile consistency. Due inconsistency in profile parameters you will facing the problem. When change profile and save it all the parameters will be commented. So, system can't read parameter. Caution: Take backup of all profile and perform the job. Regards, Ganesh ****Reward points if Helpful*****
o

Report Abuse

o o

Like (0)

Re: ECC 5.0 Two Errors .....

Shailesh Mamdiwar Jul 30, 2007 3:24 PM (in response to Ganesh Paisa) Thank for your quick replies . I have already imported the active servers profiles. and tried to change the parameters. And checked consistency of profiles before restarting the server. And the solution about editing it at OS level is not much feasible.

And what about my first question? DB02 ? Plz Help.....

Report Abuse

Like (0)

Re: ECC 5.0 Two Errors .....

Shailesh Mamdiwar Jul 31, 2007 11:20 AM (in response to Shailesh Mamdiwar) Hello !!!!!!!!

My problems still not solved. someone give it a try.. Thanks in Advance

o

Report Abuse

o o

Like (0)

next try

Peter Simon Jul 31, 2007 1:47 PM (in response to Shailesh Mamdiwar) I did not remember the exact Oracle Versions, but there are some out which have a bug in calculating the freespace in the database (extreme long runtimes of special sql-statements) set parameter rdisp/max_wprun_time = 0 in the instance profile. restart the instance and run it again with patience. Peter

Report Abuse

Like (0)

Re: next try

Shailesh Mamdiwar Jul 31, 2007 2:04 PM (in response to Peter Simon) Thanks for reply, But i found your reply some what strange. What is the use of setting that parameter to 0 . then dialog process will not run more than 0 sec. Or there is any other logic behind that? Thanks in Advance

Report Abuse

Like (0)

Re: next try

Prince Jose Jul 31, 2007 2:14 PM (in response to Shailesh Mamdiwar) Hi Dialog workprocess wont timeout if the value is set to 0 Thanks Prince Jose

Report Abuse

Like (0)

Re: next try

Shailesh Mamdiwar Jul 31, 2007 3:09 PM (in response to Prince Jose) Thank you for your quick reply.. I think this problem is going to solved with this effort. And i would like to have answer to my first question. So can you plz look into it ...

And where can i get a good post installation steps for ECC 5.0. Like setting parameters,buffer tunning etc Plz help me with that. Thanks in Advance....

SAP Mobile App Program One contract. One place for E2E Enablement & support. One SAP Store. Legend

Correct Answers - 10 points Helpful Answers - 5 points

Follow SCN Site Index Contact Us SAP Help Portal Privacy Terms of Use

Like (0)

Dialog WP in R/3 due to XI RFC adapter This question is Assumed Answered.

David Encinas Nov 27, 2006 10:20 PM Hi All, We are having performance issues in SAP R/3 due to an interface heavy RFC adapter usage in XI. We'd like to limit the maximum number of dialog work process for the RFC user in order to avoid colapsing the machines as it has already happened in the past but we find no solution yet. Any help on this would be really apreciated. Regards, David Encinas. 345 Views Average User Rating (0 ratings)

Re: Dialog WP in R/3 due to XI RFC adapter

Krishna Moorthy P Nov 27, 2006 10:54 PM (in response to David Encinas) Hi, This tuning guide may help uhttps://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ada5ef-0201-0010-1f8bc935e444b0ad Try out changing the max.no. of connection in the RFC reciever Communication channel to more no. but it may hit no. of workprocess This SAP note on Virtual Memory settings may help u- 709140- If you get runtime JCO connection failure Increase the number of processes in VisualAdmin (VisualAdmin>JCO RFC Provider>AI_RUNTIME_<SID>) and see if that helps. Regards, Moorthy
o

Report Abuse

o o

Like (0)

Re: Dialog WP in R/3 due to XI RFC adapter

David Encinas Nov 30, 2006 6:35 PM (in response to Krishna Moorthy P) Hi, Thanks for your prompt response! However, the issue is that XI sends a lot of RFCs and once in SAP, this executes reports that require access to the database. As the RFC finish quickly, we see no issue in XI but on the R/3, the table get blocked. What I was looking is a way to limit the number of WP in SAP for the user that execute the report in order to avoid performance issues in SAP. Thanks any way, Encinas.

Report Abuse

Like (0)

Re: Dialog WP in R/3 due to XI RFC adapter

Daniel Guentner Nov 30, 2006 6:46 PM (in response to David Encinas)

Hi, To change your SAP ERP it is not the right way. In this case XI will get errors from SAP ERP and so your sender will get a problem. Try to modify your XI process. Use a timer function between each RFC call. Daniel
o

Report Abuse

Like (0)

Re: Dialog WP in R/3 due to XI RFC adapter

Tim Walker Nov 30, 2006 9:59 PM (in response to David Encinas) I believe the parameters you want are in RZ10 on the R/3 side. If it is not directly in RZ10, then it is accessible from RZ10 on the menu. There is a parameter to control percentage of total WP's available on an app server that can be used by RFC. Sorry, don't have access to the t-code here or I would be more specific. I originally had suggested RZ12, but correct t-code to make permanent change is RZ10.
o

Report Abuse

Like (0)

Re: Dialog WP in R/3 due to XI RFC adapter

Daniel Guentner Nov 30, 2006 9:57 PM (in response to David Encinas) Hi, What kind of RFC are you using? Is it a customer program or an SAP standard? For me it seems that your problem is not really an XI problem. You should do a performance test on SAP ERP by running the program with transaction SE37 also there is a performance test tool on SAP GUI. I think if you will start this program on SAP ERP several times you will have the same problem. The most SAP programmer does not watch about their Select statements if the result is what customer need they are happy. But they will never do performance tests Daniel
o

Report Abuse

Like (0)

Workprocess in Reconnect state This question is Not Answered.

Abdul Waseem Mohammed Sep 16, 2009 8:19 AM Hi All, Can someone please advice on the log of developer trace for the work process.

Wed Sep 16 08:59:57 2009 ***LOG BV4=> reconnect state is set for the work process [dblink#5 @ 1958] [dblink 1958 ] ***LOG BYY=> work process left reconnect status [dblink#5 @ 1959] [dblink 1959 ]

System information. Environment : MSCS cluster landscape Version: Ecc 6.0 Kernel release 700 Compilation NT 5.2 3790 Servic Sup.Pkg lvl. 179 ABAP Load 1563 CUA load 30 Mode opt

DB client lib. SQL_Server_8.00 DB releases MSSQL 7.00.699 or DBSL version 700.08 DBSL Patch Level 180

Points would be rewarded. Thanks and Regards Abdul 2364 Views Average User Rating (0 ratings)

Re: Workprocess in Reconnect state

mohit gupta Sep 16, 2009 9:14 AM (in response to Abdul Waseem Mohammed) Hi , There are two methods of reconnect for a workprocess :: 1.Reconnect with restart of the work process 2.Reconnect without restart of the work process In first case SAP internal reconnect mechanism is switched off using the profile parameter rsdb/reco_trials. A work process running with an error condition is restarted. This includes a rollback of the SAP logical unit of work (LUW) and a reconnect to the database. If the restart fails, the process terminates. You then have the following options to restart the process: If the application server is still running (that is, if the dispatcher, at least one dialog work process, and the SAP buffers are still available), you can use transaction sm51 to perform a u201Crestart after error.u201D You can restart the application server. A restart of the application server means that all SAP buffers on the affected application server are lost. In second case The reconnect is initiated if a request sent to the database by a work process returns one of the database errors included in the RECONNECT error group. The subsequent processing depends on the type of work process that sent the request. Thanks.. Mohit
o

Report Abuse

Like (0)

Re: Workprocess in Reconnect state

Anindya Bose Sep 16, 2009 9:28 AM (in response to Abdul Waseem Mohammed) Network problem suspected... Please check note https://service.sap.com/sap/support/notes/124562
o

Report Abuse

Like (0)

====================