Change print recipient in scheduled jobs (SM37)

Is it possible to change the print recipient in multiple scheduled jobs (SM37) at the same time?
Thanks,
Mark

You have to change it manually one by one... it is not possible to change it in a multiple jobs at a same time.

Similar Messages

  • Change user for backup scheduled job

    Hi all,
    In our ecc 6.0 system is cluster controlled.i have scheduled regular br offline backup @ night for this month in db13.In a particular day for some reason i have removed the scheduler in db13 and also delete the associated released background job in sm37.On the next day after restarting the system i change the user for backup background job in sm37 for the current day but i need the changes for all rest of the day of this month.One option is that delete from db13 and recreate again with required usreid.
    without recreate could anyone tell me how to change the user for background job for the other day also?? 
    Regards
    Pinaki

    Hi
    In order to change the user id in SM37 to run under different user you can highlight the background job which is scheduled to run, double click on that and click on STEP in task bar.
    Click on USER and you would have a change pencil icon.
    Click on Pencile Icon and It would take you to another pop up were you can have the user name entered.
    In this way job would would show some other user name who is creator but would run under the person whom we have entered above.
    Thanks and Regards
    Arun R

  • How to change userid/owner of scheduled jobs

    I can see the 'userid' of the scheduled jobs using sm37.
    This are the BASIS jobs setup during installation/upgrade last year.
    I would like to reassign the userid of to my own userid...as the consultand userid no longer exists.
    Please advise
    Maria

    hi,
    T code SU01 and give user name which u want 2 create and then click on create option.......
    enter the reqired field.... save
    as u enter the client using ur user id and then system will ask 2 give ur new password...
    if useful assign points...
    regards,
    santosh kumar

  • Changing the timing in scheduler jobs

    Hi All,
    In the below code I have given the execution timing as 2:15. But next run date value is showing as 3:00 AM. What is wrong here?. I created this job at 2:00 AM
    SQL> select owner,LAST_START_DATE,NEXT_RUN_DATE from dba_Scheduler_jobs where JOB_NAME='job2' and owner='owner1';
    OWNER LAST_START_DATE NEXT_RUN_DATE
    owner1 08-DEC-12 03.00.00.000000 AM -
    05:00
    SQL> BEGIN
    2 DBMS_SCHEDULER.create_job (
    3 job_name => owner1.job2',
    4 job_type => 'PLSQL_BLOCK',
    5 job_action => job2();',
    6 start_date => '08-Dec-12 2.15.00AM',
    7 repeat_interval => 'freq=hourly; byminute=0; bysecond=0;',
    8 end_date => NULL,
    9 enabled => TRUE,
    10 comments => 'None');
    11 END;
    12 /

    the start_date defines the point in time when the schedule becames active. But the time of the next execution is determined by the repeat_interval - in your case: byminute=0; bysecond=0:
    BEGIN
      DBMS_SCHEDULER.create_job (
      job_name => 'test_job',
      job_type => 'PLSQL_BLOCK',
      job_action => 'begin null; end;',
      start_date => to_date('08.12.2012 02:15', 'dd.mm.yyyy hh24:mi'),
      repeat_interval => 'freq=hourly; byminute=0; bysecond=0;',
      end_date => NULL,
      enabled => TRUE,
      comments => 'None');
    END;
    select job_name
         , start_date
         , repeat_interval
         , next_run_date
      from dba_scheduler_jobs
    where job_name like '%&job_name%'
       and owner not like 'SYS%'
    order by owner
            , job_name
    JOB_NAME   START_DATE                          REPEAT_INTERVAL                      NEXT_RUN_DATE
    TEST_JOB   08.12.12 02:15:00,000000 +01:00     freq=hourly; byminute=0; bysecond=0; 08.12.12 12:00:00,000000 +01:00

  • Change variant for background scheduled jobs

    Hi experts,
    I want to schedule the report RKO7KO8G in background.
    Two of the selection parameters of this report are Settlement period & Settlement year.
    This report should be executed in the background every month. For this the period parameter should change every month
    , like for example when the report executes in background in May then period should be 05, June - period should be 06
    and so on.
    i.e. the variant should change.
    For this how do i create a dynamic variant. I tried to create dynamic variant but it says that the parameter
    should be a date field. However, the settlement period field over has input from 001 to 999 & not date field.
    I want to schedule this report in background on a monthly basis and change its input parameter Settlement period
    as per the month.
    Please suggest.
    Regards,
    Priti.

    Links to sap.technical are NOT permitted. Even via Tiny.
    Hi,
    Have a look at the below tutorial;
    [Dynamic Variant|http://joyjitghosh.blogspot.com/2008_09_01_archive.html]
    Regards,
    Karthik D
    Edited by: Matt on May 27, 2010 10:57 AM - changed url to the source

  • Material Document schedule job printing.

    Dear All ,
      I had configured all configuration to print the material document details in a smartofrm . All details are copied in the material document from output determination.
    if i set printing preference  4.send immediately (when saving the application) i am getting the output in the printer. Here the status is green .
    Here my user want to set the preference as 1.send with periodically scheduled job , so that all the material documents will be printed at the same time.
    How to schedule this in back ground job . I had tried in MB90 its not working there.
    Thanks in advance.
    Regards
    Srihari.P

    Hi,
    You can schedule the Job for the Despatch time  3. Send with application own transaction  also, for this you have to select the program to run for the Job, as you said you can schedule the JOB on the program of MB90
    for Using the Despatch time 1. 1. Send with periodically scheduled job, you have to run or setup job for the Program RSNAST00
    Manually you can also run the program RSNAST00 in SE38 to chcek whether the OUTPUT was processed or not
    Goto SE38 and with the RSNAST00 ,, execute and enter the Details of Application area ME and OUTPUT type and the Document number.
    Then  in the Menu click on Program--Exdcute in Back ground. It will run and in SM37 you can find the Processed outputs or Logs if any in case if they are not processed. you can then trace the error
    In the foreground you cant identify the eror or reason of why it was not processed.
    regards,
    santosh

  • SMD: E2E_CONTROLLER jobs do not schedule in SM37

    Hi!
    I fighting with set up of SMD functions Workload Analysis, Change Analysis in SAP Solution Manager.
    The set up of all the steps (SMD for Managing System, SMD for Managed system are in status "green", Wily 8 is installed, SMD agent is running) run succesfully. 
    Unfortunately I cannot detect valid E2E_CONTROLLER jobs in SM37. As a result no current data are available.
    I recently updated my SOLMAN from SP18 to EhP1 and Wily Introscope from version 7.2. to 8.
    Questions:
    Are there any changed regarding the E2E_CONTROLLER jobs with SOLMAN 7.0 EHP1?
    Is it possible to re schedule the E2E_CONTROLLER jobs in order to see current data in tabs WA and CA?
    Thank you very much!
    regards
    Jürgen

    Hi Jürgen,
    with EhP1 the Extractor Framework has been changed, there is a new job "EFWK Resource Manager" which takes care of the ressources used for data extraction. You can use the "Extractor Framework Administration" in the Root Cause Analysis Workcenter to check if the extractors are running.
    More information can be found in the Workload Analysis User Guide for EhP1 under:
    http://service.sap.com/diagnostics --> User Guides --> Workload Analysis.
    Best regards
    Michael

  • Changing the job priority of scheduled job

    Hi gurus,
           Please let me know how to change the priority of a already scheduled job.I mean to say if a job is scheduled with priority A,now i want to change it to some B or C .How can i do that.Please guide in step wise.....
    Thanks in advance.
    Regards,
    Rakesh.

    A little tip which might help you in future: If the user only has the authority for object S_BTCH_JOB and not S_BTCH_ADM... then they will only ever be able to schedule class "C" jobs.
    When you trace or debug SM37, do not be mislead by the check on S_BTCH_ADM... the user does not need it with the correct S_BTCH_JOB authority. It is only being checked to over-ride the S_BTCH_JOB authority for admins!
    Cheers,
    Julius

  • Printing of changed line item in scheduling agreement  smart form.

    Hi experts,
    I am facing problem in printing of changed line item in schedule agreement.
    can any body tell me how to find the line item has been changed through programming?what is the procedure to fetch the data for new line item.its
    very urgent for me.
    Please help me in this regard.
    Priti Shrivastava

    Hi
    with the help of  T180-TRTYP field you know if that doc has been changed or created.
    If it is not equal to H it is changed. H means created.
    pass the TCODE of Sched Agreement and check this field.
    You can use the CDHDR and CDPOS table s to get the changed values of new item.
    Reward points if useful
    Regards
    Anji
    Message was edited by:
            Anji Reddy Vangala

  • Dynamically Set date not changing in schedule Job

    Hi,
    I have created a report with "Order Date" as one of the parameters on the selection screen. I have created a variant, say 'X' , to set this date parameter dynamiccaly as "Current date - 31 days".
    I have scheduled this program to run in background with the 'X' variant daily at certain time.
    Now, for the day on which I created this job , the Order Date is set to correct date . For ex if I am scheduling the job tdy it will be set to 06/10/08. However, for next day , that is tom this date is not getting changed. i.e Tommorrow again Order date is 06/10/08 but it should have been 07/10/08.
    So basically this dynamically set date is not chaning in the scheduled job.
    Any idea why this is happening and what is the corrective measure for this.
    Thanks!

    There is an INITIALIZATION event in the program.......
    Do the processing your date in that event only....
    for ex....
    select-options: date for order-date.
    INITIALIZATION.
    date-low = sy-datum or wat ever.
    Thanks
    Saurabh

  • Which scheduled job to which process chain on SM37

    Hi all ,
    I'm checking scheduled jobs on SM37 screen. I see many BI_PROCESS_TRIGGER jobs scheduled and realesed . But I don't know  which process chain is the owner of these jobs. Does anyone knows how to check whic job belongs to which process chain ?
    Thanks in advance

    Hi,
    By using BI_PROCESS_TRIGGER job we can find the chain name..
    Below is the procedure..
    1.Double click on the job BI_PROCESS_TRIGGER
    2.Then goto "STEP"
    3. In "STEP"---goto 'GOTO' tab in the MENU....select "maiatain variants"
    Then it will take to SE38 screen---Click the DISPLAY
    It will give the Chain name and all the details.
    If u have any doubts plz let me know...
    i think this will clear...
    Mohan

  • KM Scheduler job

    Hi
    I created several KM scheduler jobs.
    The problem is that they are running in the context of Guest user, and i could find any way to change this.
    Because of that when i try to call new InitialContext () for calling some remote ejbs i get caller not autorized.
    So does somebody know how i can change this?
    Florin

    hi,
    if you ejb connect to backend, you need to configure an service user who has authorized to call
    the rfc functions in R/3.
    Kind regards
    Ben.J.

  • Error messege in Background Job(SM37) -  Please enter a valid date

    Hi all,
    background job which is scheduled in sm37 is giving error for dated 01.01.2009 to 30.01.2009.
    But before 31.12.2008 it was working fine
    error messege-
    This is happening in Production and developement  client.
    While running the report it showing the error messege- Please enter a valid date
    One function module is used in the report for geting fiscal year from date.
    it is showing the following error messege for perticular date range- 01.01.2009 to 30.01.2009.
    GM_GET_FISCAL_YEAR
    Error
    Fiscal year variant V3 not defined or maintained for date 01.01.2009
    Thanks
    Susanta

    Hi,Because this datein the past

  • Background Processing? how schedule job for "System Error" Message .

    Hello everyone,
    in sap help i have read.
    http://help.sap.com/saphelp_nw04/helpdata/en/5a/f72040599a8f5ce10000000a155106/frameset.htm
    PCK> Monitoring>Message Monitoring-->Background Processing
    you can schedule jobs for various background processing:
    ●     Archiving of messages processed successfully
    ●     Deletion of messages that are not to be archived
    ●     Restarting of messages with errors
    ●     Rescheduling of lost messages
    can anyone understand this docu?
    give me some introduction, how can i define and schedule these jobs ?
    thx in advance!!
    best regards
    Yaning

    Background Processing
    Prerequisites
    You have started the message monitor on the initial screen of the PCK and are in Background Processing.
    Features
    Archiving
    You require two archiving sessions to archive messages:
    ●     One session to write the messages to the archive
    ●     One session to delete the persisted messages that have been archived
    To do this, you schedule an archiving job, which implicitly schedules the sessions to write to the archive and delete the archived messages.
    You can define one or more rules for each archiving job; these rules contain conditions that a message must meet in order to be archived by the job. At least one of the defined rules must be met for archiving to take place.
    All information that is displayed for a message in message monitoring is archived, in addition to the audit log for each message.
    Deleting
    A standard delete job is created automatically. It runs once a day. You can schedule additional delete jobs; however, you cannot define rules for them.
    Restarting
    Instead of restarting messages with errors manually with message monitoring, you can schedule a job to automatically restart these messages. This is possible for all messages for which the number of defined restart attempts has been exceeded (messages with the system error status).
    You can define one or more rules for each job to restart messages; these rules contain conditions that a message must meet in order to be restarted by the job. At least one of the defined rules must be met for archiving to take place.
    Rescheduling
    A standard job to reschedule messages is created automatically. The job runs once a day and ensures that messages lost as a result of database failure, for example, are rescheduled. You can schedule additional rescheduling jobs; however, you cannot define rules for them.
    Thx Aamir.
    But I mean the messages with errors in Adapter Engine , not in Intergrations Engine.
    the situation is like Naveen Pandrangi's WebLog
    II. Errors in Adapter Engine [XI :  How to Re-Process failed XI Messages Automatically|XI :  How to Re-Process failed XI Messages Automatically]
    I
    Till now we have seen how to resubmit/restart message that failed in Integration Engine.  One a message makes it from Integration Engine to Adapter Engine, the message is flagged as checked in Integration Engine. The status of the message in Adapter engine does not effect the processed state in Integration Engine. Now if this message was asynchronous, XI will by default try to restart the message 3 times at intervals of 5 minutes before the status of the message is changed from Waiting to System Error .
    *how can i schedule a job to automatically restart these messages with errors?
    best regards
    Yaning
    Edited by: Yaning Liu on Aug 18, 2008 1:43 PM

  • OIM 11g-Error During Creating a new Scheduler Job

    Hi Experts,
    I am trying to create a new scheduled job. I imported the job by using the 'weblogicImportMetadata.sh'.
    But when I click on the task lookup while creating a job using UI, I am getting the following error in the logs. Please let me know if anyone faced this error before and how can it be resolved.
    <Oct 22, 2012 1:59:22 PM EDT> <Error> <oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator> <BEA-000000> <ADF_FACES-60096:Server Exception during PPR, #6
    javax.servlet.ServletException: java.lang.AssertionError
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:341)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447)
    at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
    at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.iam.platform.auth.web.PwdMgmtNavigationFilter.doFilter(PwdMgmtNavigationFilter.java:122)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthContextFilter.java:109)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:176)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: java.lang.AssertionError
    at org.apache.myfaces.trinidad.component.ChildArrayList.__removeFromParent(ChildArrayList.java:191)
    at org.apache.myfaces.trinidad.component.ChildArrayList.add(ChildArrayList.java:53)
    at org.apache.myfaces.trinidad.component.ChildArrayList.add(ChildArrayList.java:69)
    at org.apache.myfaces.trinidad.component.ChildArrayList.add(ChildArrayList.java:33)
    at oracle.iam.consoles.faces.render.canonic.UIValue$UIEntitySelector.search(UIValue.java:1670)
    at oracle.iam.consoles.faces.render.canonic.UIValue$UIEntitySelector.access$2400(UIValue.java:1467)
    at oracle.iam.consoles.faces.render.canonic.UIValue$EntitySelectorQueryListener.processQuery(UIValue.java:1787)
    at oracle.adf.view.rich.event.QueryEvent.processListener(QueryEvent.java:67)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcast(UIXComponentBase.java:675)
    at oracle.adf.view.rich.component.UIXQuery.broadcast(UIXQuery.java:108)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96)
    at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:93)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96)
    at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:902)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:313)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:186)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447)
    at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
    at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.iam.platform.auth.web.PwdMgmtNavigationFilter.doFilter(PwdMgmtNavigationFilter.java:122)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthContextFilter.java:109)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:176)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

    I am afraid you might have made some undesirable changes in the /db/tasks.xml..... And don't go via plugin route... Instead
    Please restore the backup of /db/tasks.xml...
    The better alternative would be:
    (1) Create a separate /db/ABCDMyCustomScheduler.xml (Remember the /db part... This should be the folder...
    /home/oracle/Oracle/Middleware/MYPROJECTMDSFILES/import/db/ABCDMyCustomScheduler.xml
    Then in the weblogicImportMetadata.sh, import path should be till:
    /home/oracle/Oracle/Middleware/MYPROJECTMDSFILES/import
    If it does not begin with /db, the job will not appear when you would try to create new job for it via Web GUI
    (2) Upload Jar.sh as Scheduler task...
    (3) Restart and all that...

Maybe you are looking for