Background jobs - AE session environment setup incorrect ?

Hi,
I am trying to accomplish a small email queue myself,
as due to the current privileges I have no access to the
HTML Mail queue myself.
Thus I stored emails to be send in a regular table..
Sofar so good.
In order to really email the pending messages, I have created a
procedure which loops through all the pending messages and pushes them into
the HTML email queue using :
htmldb_mail.send( p_to => '<'|| v_mail.eml_to ||'>',
p_cc => '<'|| v_mail.eml_cc ||'>',
p_from => '<'|| v_mail.eml_from ||'>',
p_SUBJ => v_mail.eml_subject,
p_body => v_mail.eml_body);
htmldb_mail.push_queue();
I have tested the procedure manually, and it works..
To be user independent I have created a DBMS_JOB which call above procedure once an hour,
but this will give me following error on all pending emails :
ORA-20001: This procedure must be invoked from within an application session.
So far I can interprete this message is that a specific session environment has to be setup,
which ofcourse DMBS_JOB is not doing.
Therefor I tried :
declare
v_job number;
begin
v_Job := htmldb_plsql_job.submit_process('mail_pkg.processMailQueue;');
end;
The job gets into the queue, and I suppose it will set the environment so that all will go ok.
Unfortunatly I do not see any activity on the pending emails.. It appears not to be executed at all,
and I do not see anything happening.
Now my question is how to submit a job using the correct HTMLDB session being setup ?
with kind regards,
Fred

Hi Jes,
By 'not having access to the mail queue' I mean I do not have the priveleges to look at the mail queue using the regular HTML DB userinterface....
HOME => Application Builder => Application Administration => Email configuration => Manage Email Queue
result :
You have requested access to a page which requires specific database privileges. Enter the credentials for a database account that has been granted the DBA role.
I can however submit new emails into the HMTL queue programmatically as described by using the HTMLDB api calls.
My programmed procedure just submits a new email to be send using the HTMLDB api calls.
If I call the amentioned procedure from within a 'legal' HTML session
HOME => SQL => SQL Commands
it is executed just fine...
Execution of amentioned procedure outside of a legal HTMLDB session, e.g. by a regular DBMS_JOB will give the amentioned error...
The question now is :
*) How to programmatically build or instate a valid HTMLDB session so the procedure being called will run as if it was called from within a legal session.
My procedure submitting the emails must first setup a valid HTMLDB session before
submitting any emails via the HTMLDB api.
I was thinking in lines of :
PROCEDURE myEmailProc IS
BEGIN
-- Instate session
HTMLDB_pkg.createValidSession(p_user => 'FRED', p_password=>'MyPassword');
-- Submit to the email queue
..................................... existing functionality comes here
END;
regards,
Fred

Similar Messages

  • How to setup background job for QI06

    Dear all,
    We have massive QIR to create and the volumn is extremely big to run in foreground in QI06.
    Can you show me the steps to setup QI06 to run in background, and how to view if the background job is complete, etc.
    Appreciate millions.
    Tuffy

    Hello,
    Just enter all the details in QI06. like:
    Complete list of Materials in Material field +plant+ vendor. ( if you have one plant then its ok and if you have same material with different plant and vendor combination then better to set variants plant wise)
    ENter rlease until, model inspection type ( if you have any )
    Now. goto Program and there is an option for EXECUTE in BCKGRND. clcik on it .
    Provide background job name and time for its job start and period ( If you want periodic job like monthly, weekly or daily etc.)
    then execute it.
    and monitor the job via SM37.
    Regards

  • How to setup Background job to LSMW Object

    Hello,
       I have created the LSMW Object for the vendor balances.The requirement is to set up a backgroung job to LSMW.Is it possible to setup the background job to LSMW if yes what is the procedure to setup?
    Thanks.

    Hi,
    it is possible. It can be done by scheduling report /SAPDMC/SAP_LSMW_INTERFACE in SM36.
    Cheers

  • 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

  • Create a Excel File in a Background Job

    Hi SAP Gurus,
    I am trying to create an Excel file using a background job but it is not possible.
    In foreground mode i get a file.
    Can someone give an explanation for that? Or someone have a workaround ??
                   Best Regards
                          João Fernandes

    João,
    If you have successfully demonstrated that SAP can write an output to an excel file, then it can do this in background as well as foreground.  The problem is probably not with the fact that it is 'Excel', but that it is trying to write a file in the background to a destination file location that is unknown to the system.
    Generally, without special setup, SAP software is unaware of most file locations that are outside of the SAP system itself.  When you log on through the SAP Gui, the SAP back end can "learn" about certain additional file locations through your PC setup and the SAPGUI session.  This 'knowledge' is lost as soon as you commit your program to a background process.
    Talk to your Basis person, and tell him what you wish to do.  This functionality is possible to do, but probably not in the way you are expecting.
    Best Regards,
    DB49

  • F.13 - Background job

    Hi,
    I am trying to setup a background job to run F.13 to clear G/L accounts. In SM37 the job is displayed as 'run successfully'. however when i open the spool to see the messages it gives a message "No transaction code available; restart the program". There are many documents which meet the criteria for clearing but none of them get cleared. When I run the program using the same variant in the foreground all those documents get cleared without any problem
    Anyone came accross the same problem when running this job in the background. There is an OSS note(1376249) that details this problem. Please let me know if anyone has implemented this note or if there are any alternatives to solve this issue. Are there any affects on the system if this note is implemented.
    Any help will be greatly appreciated.
    Thanks
    Nick

    Stacy,
    Thanks for your reply. In the test environment - i created a variant and ran it myself both in background and in foreground. I am able to clear the documents in foreground. So it cannot be an authorization issue, and I am using the same variant for back ground and foreground so it cannot be variant issue.
    What exactly do you mean by job parameter?
    Thanks
    Nick

  • DP background jobs in local time zone

    We are using APO DP in an international environment (SCM 4.1). We have setup up the system, that is using the local time zone (personal user settings), which is working fine in interactive planning (data views & macros). But when executing the macros
    in background (APO background jobs triggered immediately by a process chain), the macro is run based on the server time and not in the local time zone. The ALEREMOTE user is set up in the same way online users regarding time zone settings.
    Can someone explain, why the local time zone isn't used in the macros when executing in background, and tell me which setting we have missed.
    Many thanks in advance
    Marco

    HI,
    I understand the issue, the issue is the Australia gets days very first from the world.. it almost GMT+11 hrs. will almost a day difference to US.
    I am not sure whether my proposal will make sense, but let me try
    As the month completes we will copy the sales history  for the closed month. where technically the the month is current month as per the system time.
    Why can not change the macro to copy current period and run at system time? i am not sure aobut the otherconstriantes.
    But looking at your question, it could be possible where your client has the local time zone defined. you can check the same from any APO screen, from menu > systems->status. you can see both time zone ( local) system time.
    I suggest you check with basis if we can use the local time zone, we can use the localtimezone but agian everyone has to use our local time.. NO SENSE i guess..
    Yarala

  • EWA Background job scheduling in solman

    HI
    I am working in solman4.0. I have configured EWA. I am able to get the report by manual processing, but I can't get the <b>automatic report</b> in Solman for satellite systems.
    In DSWP it is showing that "Data is available"
    <b>The background job is not running automatically "SM:EXEC SERVICE"</b>
    Please give me your inputs to generate the EWA report automatically in Solman.
    Regards
    Kumar

    Hello K Kumar,
    When you go to TCODE DSWP and you are at the SAP Solution Manager:Active Solutions screen, click on the Activities pencil icon. You are taken to the Change Solution Directory screen. In the main screen click on the Solution Settings tab. In the monitoring section select the 'Day to process EWA sessions'  and then click on the 'Setup EWA' button to select the systems for which EWA should be activated. Click Save when done.
    Hope this helps. Points are always welcome.
    Regards,
    Joe Hall

  • CCMS Monitor to Pager for Failed Background Jobs

    Hello Experts,
    I am currently leveraging Central CCMS monitoring to alert us via email whenever a background job fails in production using the MTE Class R3BPServerSpecAbortedJobs.
    I am trying to find a way that I can tweak the monitor to alert me ONLY when specific background jobs fail.
    We want this alert to notify the oncall pager only when a handful of critical jobs fail. Does anyone know how I can delimit this MTE?
    For example, we will be creating jobs that begin with Z_ALERT* that I will tie to an auto-react method that will email a pager.
    Thanks in advance.
    Bill

    Hi Sundara.
    From following link, you can download step by step setup information.
    So please check following documents.
    http://www.service.sap.com/bpm
    =>Media Library=>Technical Information
    =>1. Business Process Monitoring - Setup Roadmap
    =>2. Setup Guide - Business Process Monitoring
    Before you start setup, I recommend you to check
    SAP Notes 521820 to ensure whether you already fulfill
    prerequestions.
    Basically what you have to do is following.
    1. Describe your business process under following area.
       (T-CD DSWP =>Solution Landscape =>Solution landscape maintenance)
    2. Setup BPMon session.
       (T-CD DSWP =>Operation Setup => Solution Monitoring =>
        Business Process Monitoring)
       in BPMon session, select job monitoring. And define background
       job that you want to monitor.
       In BPMon job monitoring, you can monitor, cancel, delay, duration,
       unexpected parallelization, also job log and so on.
    I hope this information help you.
    Best Regards
    Keiji Mishima

  • CUP not pulling through Risks, linked to background jobs? GRC 5.3

    Hi guys,
    I have an annoying problem in GRC CUP, I am trying to set up the "Create Request" function for our Company.
    When I create a request for either a New User, or Change a User's Roles, then perform the Risk Analysis on this, the result is "0 Risk(s) found". I have added every single role in order to test, which should produce a risk, but still the same message.
    I therefore thought OK, maybe the risks are not loaded into CUP, so I had a look in the configuration, namely the background jobs. The SOD Review and the UAR review jobs were not setup, so I scheduled them for every day, roughly every hour. However, this produces an error on the system log as follows:
    2009-11-03 08:54:17,505 [Thread-8394] ERROR Service call exception; nested exception is:
    *     java.net.MalformedURLException: no protocol: 103*
    java.rmi.RemoteException: Service call exception; nested exception is:
    *     java.net.MalformedURLException: no protocol: 103*
    *     at com.virsa.ae.service.ccSODUsers.ConfigVirsaCCSODViolatedUsersBindingStub.execSODUserAnalysis(ConfigVirsaCCSODViolatedUsersBindingStub.java:90)*
    *     at com.virsa.ae.service.ccSODUsers.ConfigVirsaCCSODViolatedUsersBindingStub.execSODUserAnalysis(ConfigVirsaCCSODViolatedUsersBindingStub.java:99)*
    *     at com.virsa.ae.sodreview.SODReviewUserHandler.insertUsers(SODReviewUserHandler.java:123)*
    *     at com.virsa.ae.sodreview.SODReviewUserHandler.execute(SODReviewUserHandler.java:59)*
    *     at com.virsa.ae.sodreview.SODReviewBGTask.execute(SODReviewBGTask.java:69)*
    *     at com.virsa.ae.backgroundjobs.BackgroundTask.run(BackgroundTask.java:51)*
    *     at java.util.TimerThread.mainLoop(Timer.java:461)*
    *     at java.util.TimerThread.run(Timer.java:408)*
    Caused by:
    java.net.MalformedURLException: no protocol: 103
    *     at java.net.URL.<init>(URL.java:568)*
    *     at java.net.URL.<init>(URL.java:465)*
    *     at java.net.URL.<init>(URL.java:414)*
    *     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.createHTTPSocket(HTTPTransport.java:110)*
    *     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:319)*
    *     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:550)*
    *     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1433)*
    *     at com.virsa.ae.service.ccSODUsers.ConfigVirsaCCSODViolatedUsersBindingStub.execSODUserAnalysis(ConfigVirsaCCSODViolatedUsersBindingStub.java:83)*
    *     ... 7 more*
    Can anyone point me in the right direction as what could be the problem here?
    Very much appreciated!! Cheers

    Hi, OK, I have done as suggested, however the log is huge. I will paste some sections of the log relating to ther Risk Analysis. there's an error at the bottom relating to EJB?
    2009-11-03 14:32:10,364 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AEFrameworkServlet.java@531:logRequest() : role_action_PE1CLNT100!#!KEY!#!1480!#!KEY!#!CCF-S:BSCU_CUSTOMIZATION_DISP!#!KEY!#!0:0::ADD#
    2009-11-03 14:32:10,364 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AEFrameworkServlet.java@531:logRequest() : role_validto_PE1CLNT100!#!KEY!#!1481!#!KEY!#!CCF-S:BSCU_MAINT_NO_RANGES!#!KEY!#!0_display:0::12/31/9999#
    2009-11-03 14:32:10,400 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  NavigationEngine.java@85:execute() : Current Module: |AE| Conversation: |cnvCreateRequest| Screen: |scrRequestDetails|
    2009-11-03 14:32:10,401 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  NavigationEngine.java@105:execute() :  Module#AE#Conversation#cnvCreateRequest#Screen#scrRequestDetails#Action#loadSODAnalysis#
    2009-11-03 14:32:10,401 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  NavigationEngine.java@261:execute() : Handler found:class com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction
    2009-11-03 14:32:10,418 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RoleValidityHelper.java@157:isExpiredAsOfToday() : INTO the method : dt : Fri Dec 31 00:00:00 CET 9999
    2009-11-03 14:32:10,418 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RoleValidityHelper.java@167:isExpiredAsOfToday() : OUT of the method : boolResult : false
    2009-11-03 14:32:10,440 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  NavigationEngine.java@272:execute() : Target returned by execute action: success
    2009-11-03 14:32:10,441 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AEFrameworkServlet.java@452:service() : forwarding to:scrRiskAnalysis.load.do
    2009-11-03 14:32:10,441 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AEFrameworkServlet.java@515:logRequest() :
    2009-11-03 14:32:12,818 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RequestDetailsHelper.java@731:isRiskAnalysisEligible() : Prov Action is eligible for Risk Analysis : CHANGE_USER
    2009-11-03 14:32:12,818 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RequestDetailsHelper.java@739:isRiskAnalysisEligible() : OUT of the method : boolEligible : true
    2009-11-03 14:32:12,847 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@130:findViolations() : Starting Risk analysis.....
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@140:findViolations() : RiskAnalysis________ DAO level System : PE1CLNT100
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@141:findViolations() : RiskAnalysis________ Include Cross System : PE1CLNT100
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] INFO   SystemDAOFactory.java@73:getRiskAnalysisDAO() : EN
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] INFO   SystemDAOFactory.java@74:getRiskAnalysisDAO() : Locale ID is :1
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] INFO   SystemDAOFactory.java@75:getRiskAnalysisDAO() : Locale date time format is :MM/dd/yyyy HH:MM:SS
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AECacheUtil.java@882:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  SAPConnectorUtils.java@600:getConnectorInformation() : INTO the method : connectorId :PE1CLNT100
    2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] INFO  com.virsa.ae.service.sap.SystemDAOFactory : getRiskAnalysisDAO() :   : cc version : 5.3_WS
    2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] INFO  com.virsa.ae.service.sap.SystemDAOFactory : getRiskAnalysisDAO() :   : risk analysis dao is set to RiskAnalysisWS52DAO
    2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] INFO  com.virsa.ae.service.sap.SystemDAOFactory : getRiskAnalysisDAO() :   : cc uri : http://cvifxpsol.ks.franke.world:54000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
    2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  SystemDAOFactory.java@221:getRiskAnalysisDAO() : OUT of the method
    2009-11-03 14:32:12,857 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@158:findViolations() : RiskAnalysis________ Visible Roles : [com.virsa.ae.accessrequests.po.RolesPO@200f200f[system=PE1CLNT100,systemShortDesc=Production System PE1 - 100,accessType=Select,searchValue=,roleProfName=0,roleProfDispName=CCF-G_BC_BASIS_ADMIN,roleProfDesc=Competence Centre System Administrator,roleProfType=C,roleApproverId=NB014,roleApproverName=Ben Neesom(NB014),roleCriticalLevel=,reqPathId=,status=OPEN,oldStatus=OPEN,actionFlag=ADD,validFrom=11/03/2009,validTo=12/31/9999,selected=true,isReadOnly=false,isNew=true,expanded=true,isSimpleRole=false,isRiskAnalysisonAccessChanged=false,isEditable=true,isApplicable=false,altRoleApproverId=,detailDesc=,reaffirmPeriod=0,isLead=false,lastReaffirmDate=,funcArea=,roleIndex=0,companydesc=,fucntionalAreaDesc=,isExistingRole=false,roleProfIndicator=R,comments=,validityType=NO,actualDate=,years=0,months=0,days=0,URL=,customBAPI=,responsibilityId=0,commentsMandatory=No
    2009-11-03 14:32:14,401 [SAPEngine_Application_Thread[impl:3]_32] ERROR java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
    java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:511)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:455)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    2009-11-03 14:32:14,402 [SAPEngine_Application_Thread[impl:3]_32] ERROR Exception during EJB call, Ignoring and trying Webservice Call
    com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service : com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:295)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:511)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:455)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by:
    java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         ... 28 more
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisWS53DAO.java@632:determineRisks() : OUT of the method : com.virsa.ae.service.sap.dto.RiskWithCriticalActionsDTO@deb0deb[listRisks=[],listCriticalActions=[]]
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@190:findViolations() : RiskAnalysis___ Completd successfully!
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@221:findViolations() : RiskAnalysis________ Risk List Size : 0
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@225:findViolations() : RiskAnalysis________ Critical Actions Size : 0
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@227:findViolations() : Done Risk analysis.
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] INFO   MessagingHelper.java@99:addMessage() : @@@Adding msgValue: Code: 2200; Locale: en
    2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] INFO   MessagingHelper.java@109:addMessage() : @@@Creating new message list
    2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] INFO   MessagingHelper.java@119:addMessage() : Adding msg to msglist
    2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  NavigationEngine.java@272:execute() : Target returned by execute action: success
    2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AEFrameworkServlet.java@452:service() : forwarding to:/sod_analysis.jsp
    2009-11-03 14:32:15,519 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  PopupCalendarTag.java@180:doStartTag() : Date Format in PopUpCalendar Java :- M/d/yyyy

  • Background Job Workers

    Does anyone know of a way to restart the Background Job Workers for CC 5.1? I have tried restarting the java engine but to no avail. Without these workers running I am unable to execute any background jobs.
    I've tried restarting the workers from //server_name:port/virsa/CCADStatus.jsp using the "Start All" option. This does not work. The page does not resolve; the standard "page could not be found" error message is displayed.
    Help!

    Laziz,
    Thanks for that, but we have already defined those entries per the note that you mentioned. Further investigation has revealed that we have CC installed on a clustered environment for HA. I would think that this would be the standard setup though upon review of these nodes, after a restart, I noticed that some of the background services are running on different nodes. Yet for some reason, after a a period of time all of the services that did start (and not all start) they stop. I am at a lost. What would be cause these services to stop instead of returning to the idle status? I feel that this is related to our HA design as we have CC installed on our Development System which does not have a HA design, and that instance of CC does not reflect these same issues - but our QA and PRD instances do (both of which are HA enviornments). Any insight is appreciated. Thanks

  • Error while scheduling Background Job for User/Role Full Synchronization

    Hi all,
    We have installed RAR 5.3 Component and uploaded the authorization data & established the connectors to the backend system.
    We have performed all the post installation activities and everything is complete.
    When we have scheduled User -Full Synchronization with the Back End system as  a part of Post Installation Activity we are receiving the below error message
    "Error while executing the Job:Cannot assign an empty string to host variable 2."
    Also the VIEW LOG/ Terminate Job buttons are disabled  in this screen.
    Can somebody please help us in resolving the above issue
    Thanks and Best Regards,
    Srihari.K

    Hi,
    We are copy pasting the error log (Part as it is huge) below here. We could able to do Full Synch for Roles and also for Profiles. Only for User Synch we are getting this error and none of the users are sychronized to RAR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WILSONA of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WINDC of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WLADICHJ of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WUK of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user ZENGS of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user ZHENGL of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: All System Flag:false=====Last Batch Flag:true
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis loadUserData
    INFO: @@@ User sync completed for params true: Syskey List is [HL2-QAHR]
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob run
    WARNING: *** Job Exception: Cannot assign an empty string to host variable 2.
    com.sap.sql.log.OpenSQLException: Cannot assign an empty string to host variable 2.
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
         at com.sap.sql.types.VarcharResultColumn.setString(VarcharResultColumn.java:57)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:511)
         at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setString(PreparedStatementWrapper.java:355)
         at com.virsa.cscext.dao.CSCDAO.updateIgnoredUserData(CSCDAO.java:1388)
         at com.virsa.cscext.dao.CSCDAO.populateGenObjUser(CSCDAO.java:1169)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.populateGenObj(BatchRiskAnalysis.java:868)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.insertBAPIUserData(BatchRiskAnalysis.java:142)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.loadUserData(BatchRiskAnalysis.java:390)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1275)
         at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
         at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob setStatus
    INFO: Job ID: 13 Status: Error
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
    FINEST: --- @@@@@@@@@@@ Updating the Job History -
    2@@Msg is Error while executing the Job:Cannot assign an empty string to host variable 2.
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
    INFO: -
    Background Job History: job id=13, status=2, message=Error while executing the Job:Cannot assign an empty string to host variable 2.
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
    INFO: -
    Complted Job =>13----
    Please let us know how to resolve this error
    Thanks and Best Regards,
    Srihari.K

  • Background job- getting printed automatically

    In my BDC Program i have submitted  Session for Background Processing using
    Submit RSBDCSUB..........
    my code is also given below..The problem is after the user executes the program, background job is automatically going to his Local printer and getting printed. HOw to avoid this?
    CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname          = gf_jobname
           IMPORTING
                jobcount         = gf_jobcount
           EXCEPTIONS
                cant_create_job  = 1
                invalid_job_data = 2
                jobname_missing  = 3
                OTHERS           = 4.
    *-Submit the selected sales orders for changes.
      SUBMIT rsbdcsub AND RETURN
             WITH mappe = v_sess
             WITH von = sy-datum
             WITH bis = sy-datum
             WITH z_verarb = 'X'
             WITH fehler = space
             WITH batchsys = space
             WITH logall = space
             USER sy-uname VIA JOB gf_jobname NUMBER gf_jobcount.
      IF sy-subrc NE 0.
        MESSAGE i999 WITH text-013.
        EXIT.
      ENDIF.
    *-Close job and start immediately.
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                jobcount             = gf_jobcount
                jobname              = gf_jobname
                strtimmed            = 'X'
           IMPORTING
                job_was_released     = gf_release
           EXCEPTIONS
                cant_start_immediate = 1
                invalid_startdate    = 2
                jobname_missing      = 3
                job_close_failed     = 4
                job_nosteps          = 5
                job_notex            = 6
                lock_failed          = 7
                OTHERS               = 8.

    On SUBMIT use
    SUBMIT zxxxxxx TO SAP-SPOOL
                        WITHOUT SPOOL DYNPRO
                        IMMEDIATELY  ' '
                        KEEP IN SPOOL 'X'
                        DESTINATION printer
                         NUMBER  number
                        AND RETURN

  • Problems with background job

    Hi,
    I have problems when creating a job that is supposed to be run once in background. I use the common steps as described below. My problem is that the report is executed twice.
    - First it is executed synchronously when the job is created
    - Then it is executed in the normal job step as I want it to do
    I don't want it to be executed the first time because it creates data!!!
    Code:
    CALL FUNCTION 'JOB_OPEN'
         EXPORTING
              jobname  = w_jobid
         IMPORTING
              jobcount = w_jobnr
              sdlstrtdt = sy-datum
              sdlstrttm = sy-uzeit.
    SUBMIT (p_prog)
    WITH p_idocnr = p_idocno
               USER            p_user
               VIA   JOB       w_jobid
                     NUMBER  w_jobnr
                     AND       RETURN.
    CALL FUNCTION 'JOB_CLOSE'
         EXPORTING
              jobcount         = w_jobnr
              jobname          = w_jobid
              strtimmed        = 'X'
         IMPORTING
              job_was_released = w_jobrel.
    Does anyone have a clue of what I should do to prevent this?
    //  Regards  Hans

    Hi again,
    1. U are right.
    2. It will happen if we use SUBMIT.
    3. As per the help documentation,
        it will run the program in separate session,
       ( as soon as submit statement comes)
    4. and run the INITIALIZATION event.
    The VIA JOB addition also loads the program accessed in a separate internal mode when the SUBMIT statement is executed and the system performs all the steps specified before START-OF-SELECTION. This means the events LOAD-OF-PROGRAM and INITIALIZATION are triggered and selection screen processing is performed. If the selection screen is not processed in the background when VIA SELECTION-SCREEN is specified, the user of the calling program can eidit it and schedule the program accessed in the background request using the function Place in Job. If the user cancels selection screen processing, the program is not scheduled in the background job. In both cases, execution of the program executed is completed after selection screen processing and the system returns to the calling program due to the AND RETURN statement.
    regards,
    amit m.

  • Background Job processing

    After writing a report, I used this Function Module “LIST_TO_ASCI” to copy my report to an internal table (DOWNTAB) because I’ll use that internal table to download a text file on the server using dataset.
    Here is my code:
    FORM DL_REP_SERVER.
       DATA: ABAP_LIST LIKE ABAPLIST OCCURS 1,
            MV_FILE2 LIKE RLGRAP-FILENAME.
      DATA: BEGIN OF DOWNTAB OCCURS 1,
              LINE(150),
            END   OF DOWNTAB.
      CLEAR: MV_FILE2.
      MV_FILE2 = ‘J:/Downloads/Report.txt’.
      CALL FUNCTION 'LIST_TO_ASCI'
           EXPORTING
                LIST_INDEX         = SY-LSIND
           TABLES
                LISTASCI           = DOWNTAB
                LISTOBJECT         = ABAP_LIST
           EXCEPTIONS
                LIST_INDEX_INVALID = 1
                OTHERS             = 2. 
      OPEN DATASET MV_FILE2 FOR OUTPUT IN TEXT MODE.
      IF SY-SUBRC <> 0.
        IF SY-SUBRC = 8.
          MESSAGE E037 WITH 'File could not be opened'.
        ELSE.
          MESSAGE E037 WITH 'Error occurs in downloading the file'.
        ENDIF.
      ENDIF.
      LOOP AT DOWNTAB.
        TRANSFER DOWNTAB TO MV_FILE2.
      ENDLOOP.
      CLOSE DATASET MV_FILE2.
    ENDFORM.                    " DL_REP_SERVER
    My big problem is this, when I’m running my program ordinarily (not as background job), I’m getting all the pages downloaded correctly but when I run it as background job (using SM36), I’m only getting the last page of my report being downloaded. Definitely, I can’t debug it because it’s in background. I can’t figure out why. Hope that I stated my problem clearly. Any help would be greatly appreciated. Thanks.

    You can debug batch jobs by going to 'SM37', type in 'JDBG' in the
    command line ( no '/' ), put the cursor on the job and press enter - will
    take you to the job in debug mode.
    You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.
    So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.
    Steps
    1. Create variant called BACKGROUND for program to be debugged.
    2. Execute ZDEBUGBG (pgm code below) in background for immediate processing.
    3. Execute transaction SM50.
    4. Select process that runs ZDEBUGBG.
    5. Goto 'Program/Session' 'Program' 'Debugging'.
    A se80 debug session will open.
    6. Change variable W_EXIT to 'E'.
    7. Step thru (F6) until ZWBTEST comes up.
    1. Go to Transaction SM66 and find your work porocess.
    Select the line work process is on and click on the Debugging button.
    If this is a custom program, you can put a wait statement in the code to buy yourself sometime.
    2. Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging.
    goto SM37 and from Program menu(not sure.. try other menu's)
    -->Catchjob . it will goto the active job in debugging mode.

Maybe you are looking for

  • Cannot start Safari; crashes every time I try to start it

    Since today i cannot start Safari (2.0.4) at all; it crashes within 10-15 seconds after starting it. I tried all the things that were suggested in other articles that were mentioning similar behaviors without luck. Here's my crashlog: Date/Time: 2007

  • IK iRig stomp no sound from guitar

    I cannot get my IK iRig stomp to produce output from my guitar. I have my iPhone 5 and my guitar plugged into my iRig stomp and am using my headphones. The guitar signal from the iRig stomp does not play through my headphones. I can play the demos in

  • Adobe Air V16 - Win 7 /64

    Hey guys, I'm looking to share about a HP Gaming Computer - M/B  - Setup with 12 g ram and a 2.8 Ghz 6 core chip. A fast machine. Updated with latest windows security updates. I have not been able to get Adobe Air to function since August purchase. P

  • How to join two crosstabs such that they appear as one?

    Hi I tried to join two cross tabs such that they appear to be one. I tried the format the view of the cross tabs by setting the value of top and bottom padding as zero but it is not working. It is taking some default space between the cross tabs. Is

  • MS Excel Data Analysis toolpak question

    Attempted to add data analysis toolpak to MS Excel using MS Office 2004 for Mac. However, when I attempt to load/add the program, a folder is added containing Data Analysis is listed but "Data Analysis" does not show up in my MS Excel "Tools" tab. Pr