Job Scheduling Integration API

I want to integrate ORACLE Job scheduling with my Visual Basic program. While going through ORACLE Enterprise Manager Application Developer's Guide I found out that there is an API which provides Commit, DeleteJob etc. commands to manage jobs. From where can download the API and if there are any sample programs available in CPP or VB?
Appreciate your help.
Thanks.

try using DBMS_JOB package. It has all the necessary API's for your VB development. Enterprise Manager uses this package for it's Job Scheduler.

Similar Messages

  • Is there a Business Objects Data Integrator API / SDK to "execute" DI jobs?

    Hello,
    I am searching for a Business Objects Data Integrator API / SDK that can be used to remotely execute BOBJ DI jobs (like in scheduling BOBJ XI docs).
    I found AdapterSDK from BOBJ DI but this is used to create adapters usable with DI (for various sources and targets). I am interested only in executing an already created job...
    Thank you in advance,
    Adrian Mitrica

    You'll probably be better off posting here:
    [SAP Community Network Forums » Enterprise Information Management » Data Integration and Quality Management|
    I'm just going by the description of the forum but that looks better than this one(?):
    This forum is dedicated to topics related to Data Integration (Data Integrator, Data Federator, Text Analysis for Data Integrator, Rapid Marts, and Integration for PeopleSoft Enterprise), Data Quality (Data Quality and Data Insight), and Metadata Management.
    I'd move your thread but I do not have the rights to do this move...
    Good luck,
    - Ludek

  • SSIS Package compiled successful, in SQL Server Integration Service package executed sucessful, But fail to run in MS SQL Job Scheduler

    Hi Everyone,
    I having a problem to transfer data from MS SQL 2005 to IBMAS400. Previously my SSIS was running perfectly but there is some changes I need to be done in order for the system to work well. Considers my changes are minimal & just for upgrades (but I did
    include DELETE statements to truncate AS400 table before I insert fresh data from MS SQL table to the same AS400 table), so I compile my SSIS package & it run successfully & I passed it into MS SQL Integrated Service as 1 of the packages & manually
    executed the package & the result is the same, that mean it was successful again but when I try to run it in a MS SQL Job Scheduler, the job failed with these message shown below as extracted from the job View history. 
    Date today
    Log Job History (MSSQLToAS400)
    Step ID 1
    Server MSSQLServer
    Job Name MSSQLToAS400
    Step Name pumptoAS400
    Duration 00:00:36
    Sql Severity 0
    Sql Message ID 0
    Operator Emailed
    Operator Net sent
    Operator Paged
    Retries Attempted 0
    Message
    Executed as user: MSSQLServer\SYSTEM. ... 9.00.4035.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    
    Started:  today time  
    Error: on today time     
    Code: 0xC0202009     Source: SSISMSSQLToAS400 Connection manager "SourceToDestinationOLEDB"     
    Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. 
    Error code: 0x80004005.  An OLE DB record is available.  
    Source: "IBMDA400 Session"  
    Hresult: 0x80004005  
    Description: "CWBSY0002 - Password for user AS400ADMIN on system AS400SYSTEM is not correct ".  End Error  
    Error: today     
    Code: 0xC020801C     
    Source: Data Flow Task OLE DB Destination [5160]     
    Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "DestinationClearData" failed with error code 0xC0202009.  There may be error messages posted before
    this with more information on why the AcquireConnection method ca...  The package execution fa...  The step failed.
    So I hope somebody can shed some hints or tips for me to overcome time problem of mine. Thanks for your help in advance. As I had scoured thoroughout MSDN forums & found none solution for my problem yet. 
    PS: In the SQL Integrated Services when I deployed the package I set the security of the packages to Rely on server... 
    Hope this will help.

    Hi Ironmaidenroxz,
    From the message “Executed as user: MSSQLServer\SYSTEM”, we can see that the SQL Server Agent job ran under the Local System account. However, a Local System account doesn’t have the network rights natively, therefore, the job failed to communicate with
    the remote IBMAS400 server.
    To address this issue, you need to create a proxy account for SQL Server Agent to run the job. When creating the credentials for the proxy account, you can use the Windows domain account under which you executed the package manually.
    References:
    How to: Create a Credential
    How to: Create a Proxy
    Regards,
    Mike Yin
    TechNet Community Support

  • Integration wth outide Job Scheduler.

    We are looking at integrating the Vinizant Global ECS Job scheduler with SAP.   We need to know how to start and monitor sap jobs and chains from unix level. Any suggestions would be appreciated.

    How do you on unix level without actually getting into the SAP GUI start and monitor SAP jobs?
    There is no standard SAP tool to schedule jobs from the command line. A control program called sapxpg is used to execute external commands(which is scheduled internally). You can monitor the execution of external commands by setting up a trace for sapxpg and the data is written to the files dev_xpg(output of external command) and dev_cp(control program).
    Nelis

  • Job Scheduler DS consumes all connections in Pool.

    Hi all,
    I use Weblogic 12.1.3.
    My objective is to create a job scheduler, with commonj Timer API to run a in a cluster environment.
    For this, I created a cluster with two node servers (I created this in the integrated weblogic server in Jdeveloper, for simplicity).
    Then I created the DataSource which points to the table where the weblogic_timers and active tables are, which are needed for persistance of the timers, targeted this DS on the nodes in the cluster, and then went to the Cluster -> Configuration -> Scheduling and selected the respective data source as "Data Source For Job Scheduler".
    After I do this and the servers are up, all the connections in the DS pool are consumed. It seems like connections are continuosly made from weblogic to the database.
    The connection itself seems ok, since I can connect from SQLDeveloper and also tested it when I created the DataSource.
    If I have a look in the logs of the two servers, I see errors like this:
    <BEA-000627> <Reached maximum capacity of pool "JDBC Data Source-2", making "0" new resource instances instead of "1".>
    Can you give me an idea of what the issue might be?
    Please let me know if I should provide more information.
    Thanks.

    It's not an issue WebLogic can address. The thortech application is independently using
    the UCP connection pool product, not WebLogic connection pooling, so Thortech APIs
    would be the only way to debug/reconfigure the UCP.

  • ANNOUNCE:::::::: EJB job scheduler for Weblogic

    Paramus, NJ - June 26, 2001 - Indus Consultancy Services today announced
    an upgrade release of its Java scheduling product. Kronos Enterprise
    Scheduler is a full-featured job scheduling system written for the
    Enterprise Java (J2EE) environment.
    As a J2EE application, Kronos Enterprise Scheduler is able to achieve a
    high degree of portability, scalability, and reliability, features which
    are critical to an enterprise system.
    Additionally, Kronos Enterprise Scheduler provides a comprehensive set
    of scheduling options, powerful holiday definitions, job dependencies,
    administrative alerts, J2EE security integration, monitoring
    capabilities, Web and "rich client" user interfaces, and an open
    developer API. The combination of these features make Kronos Enterprise
    Scheduler one of the most complete solutions on the market today.
    Version 2.10 contains a number of minor enhancements and bug fixes and
    is a free upgrade for current customers.
    For more information on Kronos, please visit our products page at
    www.indcon.com

    I would hope that BEA will step up and develop a replacement for their
    deprecated APIs. It is unfair to ask their customers to buy something they
    got previously for free. I also understand that the future EJB spec will
    contain scheduling features.

  • KRONOS JOB Scheduler For WEBLOGIC CUSTOMERS

    Paramus, NJ - June 26, 2001 - Indus Consultancy Services today announced
    an upgrade release of its Java scheduling product. Kronos Enterprise
    Scheduler is a full-featured job scheduling system written for the
    Enterprise Java (J2EE) environment.
    As a J2EE application, Kronos Enterprise Scheduler is able to achieve a
    high degree of portability, scalability, and reliability, features which
    are critical to an enterprise system.
    Additionally, Kronos Enterprise Scheduler provides a comprehensive set
    of scheduling options, powerful holiday definitions, job dependencies,
    administrative alerts, J2EE security integration, monitoring
    capabilities, Web and "rich client" user interfaces, and an open
    developer API. The combination of these features make Kronos Enterprise
    Scheduler one of the most complete solutions on the market today.
    Version 2.10 contains a number of minor enhancements and bug fixes and
    is a free upgrade for current customers.
    For more information on Kronos, please visit our products page at
    www.indcon.com

    Paramus, NJ - June 26, 2001 - Indus Consultancy Services today announced
    an upgrade release of its Java scheduling product. Kronos Enterprise
    Scheduler is a full-featured job scheduling system written for the
    Enterprise Java (J2EE) environment.
    As a J2EE application, Kronos Enterprise Scheduler is able to achieve a
    high degree of portability, scalability, and reliability, features which
    are critical to an enterprise system.
    Additionally, Kronos Enterprise Scheduler provides a comprehensive set
    of scheduling options, powerful holiday definitions, job dependencies,
    administrative alerts, J2EE security integration, monitoring
    capabilities, Web and "rich client" user interfaces, and an open
    developer API. The combination of these features make Kronos Enterprise
    Scheduler one of the most complete solutions on the market today.
    Version 2.10 contains a number of minor enhancements and bug fixes and
    is a free upgrade for current customers.
    For more information on Kronos, please visit our products page at
    www.indcon.com

  • What is the spool, what is its role in background job scheduling

    Hi,
    I want to know what is meant by Spool request and spool number generated.
    Tell about transaction SP01.
    How it is linked to Background job scheduling.
    thanks.
    sam.

    Hi,
    Refer this link.
    https://www.sdn.sap.com/irj/sdn/inf?rid=/library/uuid/7a5f4061-0a01-0010-c9bc-a4e4cb100438
    About SP01.
    Printing does not work in SAP. There is a printer definition for your local printer, but it does not work. Presuming that you use the program SAPLPD on your computer.
    Boot your computer and start only the SAPLogon and the SAPLpd program.
    Delete all of your old print jobs in the SAP system (Transaction SP01).Generate only one new print job.
    Check that there is enough resource in your computer. Check the free memory (Win 3.1x) and the free disk space (The lists are temporarily saved on your disk).
    Open the SAPLPD and read the print log in the window. The printer definition must correspond with the parameters shown here.
    Check that the standard printer is on the same lpt (Win 3.1: Control panel, Printer) as defined for the printer (usually lpt1).
    In Transaction SP01 read the protocol of your print job. Do not generate new print jobs! Wait till the SAP system changes the status of the print job.
    If you can not find the print job in SP01 anymore, then the print job was successfully printed out. If it didn't come out on your printer and the SAPLpd didn't indicate an incoming print job, then the connection was realised with another PC. Then SAP printer definition you used, does not correspond with your computer.
    Scheduling Background Jobs:
    1.        Background jobs are scheduled by Basis administrators using transaction SM36.
    2.        To run a report in a background, a job needs to be created with a step using the report name
    and a variant for selection parameters. It is recommended to create a separate variant for each
    scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
    company codes).
    3.        While defining the step, the spool parameters needs to be specified
    (Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
    to find the spool request. The following parameters needs to be maintained:
    a.        Time of printing: set to u201CSend to SAP spooler Only for nowu201D
    b.        Name u2013 abbreviated name to identify the job output
    c.        Title u2013 free form description for the report output
    d.        Authorization u2013 a value defined by Security in user profiles to allow those users to access
    this spool request (authorization object  S_SPO_ACT, value SPOAUTH).  Only users with matching
    authorization value in their profiles will be able to see the output.
    e.        Department u2013 set to appropriate department/functional area name. This field can be used in
    a search later.
    f.        Retention period u2013 set to u201CDo not deleteu201D if the report output needs to be retained for more
    than 8 days. Once the archiving/document repository solution is in place the spool requests could
    be automatically moved to the archive/repository. Storage Mode parameter on the same screen
    could be used to immediately send the output to archive instead of creating a spool request.
    Configuring user access:
    1.        To access a report output created by a background job, a user must have at
    least access to SP01 (Spool requests) transaction without restriction on the user
    name (however by itself it will not let the user to see all spool requests). To have
    that access the user must have S_ADMI_FCD authorization object in the profile with
    SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
    2.        To access a particular jobu2019s output in the spool, the user must have
    S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
    in the Print Specifications of the job (see p. 3.d above).
    3.        Levels of access to the spool (display, print once, reprint, download, etc) are
    controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
    BASE access (display).
    On-line reports:
    1.        Exactly the same configuration can be maintained for any output produced
    from R/3. If a user clicks u201CParametersu201D button on a SAP Printer selection dialog, it
    allows to specify all the parameters as described in p. 3 of
    u201CScheduling background jobsu201D section. Thus any output created by an online report
    can be saved and accessed by any user authorized to access that spool request
    (access restriction provided by the Authorization field of the spool request
    attributes, see p. 3.d of u201CScheduling background jobsu201D section).
    Access to reportu2019s output:
    1.        A user that had proper access (see Configuring user access above) can
    retrieve a job/report output through transaction SP01.
    2.        The selection screen can be configured by clicking u201CFurther selection
    criteriau2026u201D button (e.g. to bring u201CSpool request name (suffix 2)u201D field or hide other
    fields).
    3.        The following fields can be used to search for a specific output (Note that
    Created By must be blank when searching for scheduled jobu2019s outputs)
    a.        Spool request name (suffix 2) u2013 corresponds to a spool name in p. 3.b in
    u201CScheduling background jobsu201D section above).
    b.        Date created u2013 to find an output of a job that ran within a certain date range.
    c.        Title u2013 corresponds to spool Title in p. 3.c in u201CScheduling background jobsu201D
    section above).
    d.        Department - corresponds to spool Department in p. 3.e in u201CScheduling
    background jobsu201D section above).
    4.        Upon entering selection criteria, the user clicks the Execute button   to
    retrieve the list of matching spool requests.
    5.        From the spool list the user can use several function such as view the
    content of a spool request, print the spool request, view attributed of the spool
    request, etc. (some functions may need special authorization, see p.3 in
    Configuring user access)
    a.        Click the Print button   to print the spool request with the default attributes
    (usually defined with the job definition). It will print it on a printer that was
    specified when a job was created.
    b.        Click the u201CPrint with changed attributedu201D button   to print the spool request
    with the different attributes (e.g. changing the printer name).
    c.        Click the u201CDisplay contentsu201D button   to preview the spool request contents. A
    Print    and Download   functions are available from the preview mode.
    Exporting the Contents of a Spool Request
    Use
    You want to export the contents of a spool request as a text file to the SAP GUI working directory or to a directory of your choice. The content of the spool request is downloaded as plain text without, for example, graphics, images, or specific fonts.
    The following procedures are irrelevant for the PDF-based form printing integrated as of SAP Web Application Server 6.40, since the print data can be opened and stored as a PDF. See also Displaying and Printing PDF-Based Forms.
    Procedure
    Exporting to the SAP GUI Working Directory:
    Choose Spool Request ® Forward® Export as Text.
    The entire text is stored in your SAP GUI working directory in ASCII format.
    A file of this type is named using the following pattern:
    .txt
    Example: ABC0000004327.txt
    You require appropriate authorization for this function.
    Exporting to a Directory of Your Choice:
    With this method of exporting a spool request, the content of the spool request is first displayed and you then download the screen list as a text file to the directory of your choice.
           1.      Select the spool request to be exported and choose  Display Contents.
           2.      In the case of SAPScript/Smart Forms documents, activate list display by choosing Goto.
           3.      Choose System ® List ® Save ® Local File.
           4.      Choose one of the available formats and confirm your choice.
           5.      Choose a directory and save the spool request.
    By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto ® Display Requests ® Settings and making the desired entries in the Display Area group box.

  • Third party Job Scheduling?

    Hi P6 Guru.
    Our customer is looking for the solution of job scheduling to control the jobs for P6 Web services API programs with other Web services programs outside P6. Some jobs would be triggered by scheduled date&time, some would be triggered by success states of predecessor jobs.
    IBM Tivoli workload scheduler(TWS), HP OpenView are what I can image easily for the solution. But I'm wondering it is popular to use such kind of system.
    Do you have any experiences or idea about how you or your customers control the job scheduling of running tasks or programs?

    AppWorx, now UC4, is one possibility but there is little, if anything, they can do that can not be done through the proper use of the DBMS_SCHEDULER package.
    I would suggest that, before you spend or waste money, you look at the docs on DBMS_SCHEDULER and determine that there is something you need that you have not already purchased. Using OEM to schedule jobs is far from giving you access to the full functionality.

  • Job Schedule Management

    Hi,
    We recently upgraded our Sol Man system to EHP1 and we are in the process of Job Shedule Management. We imported few jobs from managed system and while monitoring ,getting error Business Proccess not created.
    Could any one please tell me one thing, shall we need to setup Business Process Monitoring prior to setup Job Schedule Management? Please explain high level end to end Job Schedule Management steps.
    Thanks & Regards
    Srinivas.

    Hi Srinivas,
    please have a llok under https://service.sap.com/jsm to find further links to important SAP notes that explain a lot. You can also find iTutors about JSM under https://service.sap.com/rkt-solman.
    Generally speaking BPMon is NO prerequisite for JSM. But as you probably saw during the import you have to assign your documented job either to a logical component (esp. meaningful for system related jobs like housekeeoing spool or dumps) or you assign to  a business process step. An assignment to a logical component is a minimum requirement!
    For a business process step assignment you need to maintain processes either in the project part or in the solution directory of SAP Solution Manager.
    An active BPMon is only needed if you want to monitor background jobs and want to make use of the integration between JSM and BPMon.
    You should also look for Blog and Forum entries of Martin Lauer in order to get further JSM insights.
    By the way: If you  should encounter some functional problems you can open an OSS message on SV-SMG-PSM.
    Best Regards
    Volker

  • ASE 15.7 Job Scheduler won´t start again

    Hi,
    we encoutered the following problem in our ECC6.0 / EHP5 on ASE 15.7 PL 122 System:
    DBACockpit / Collector Configuration shows the warning "The ASE-Job Scheduler is not active". The log SID_JSAGENT shows the following entries:
    00:11704:12104:2014/09/01 08:00:35.78 jamain  Opening jsagent connection.
    00:11704:12104:2014/09/01 08:00:35.78 jamain  Agent will listen on <IP>
    00:11704:12104:2014/09/01 08:00:35.78 jamain  SYB_JSAGENT waiting for connection
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Job Scheduler Agent connected with Job Scheduler Task on port 4903
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Initializing SYB_JSAGENT
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Allocating list resources.
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Allocating queue resources.
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Allocating thread resources.
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Initializing connection pool.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  Client message: ct_connect(): user api layer: external error: The connection failed because of invalid or missing external configuration data.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  ct_connect() failed.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  jsj_AddConxs: jsd_MakeConnection() failed for user jstask to server SID
    00:11704:12104:2014/09/01 08:00:36.99 jamain  jsj_CreateConxPool: jsj_AddConxs() failed
    00:11704:12104:2014/09/01 08:00:36.99 jamain  Initialization failed initializing connection pool
    00:11704:12104:2014/09/01 08:00:36.99 jamain  Jsagent failed to handle INIT message.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  JS Agent aborting. Cancel all running jobs.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  Job Processing failed.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  JS Agent exiting.
    Restarting the scheduler on ISQL doesn´t seem to work. Any ideas?
    Many thanks & greetings
    Vierengel Stefan

    Hi,
    thank you. Problem was solved by performing the following steps
    1.     deleting the following file: DRIVE:\sybase\SID\OCS-15_0\ini\ocs.cfg
    2.     Stop / Start Job Scheduler
             exec sybmgmtdb..sp_sjobcontrol '','stop_js'
            go
             exec sybmgmtdb..sp_sjobcontrol '','start_js'
            go
    3.     Refresh DBACockpit
    Greetings
    Vierengel Stefan

  • Job Scheduling Management vs SAP CPS

    Hi Guys
    I am trying to find out what are the differences between using the Job scheduling management tool in Solution manager and SAP CPS integrated into Solution manager. What are the benifits of using CPS as opposed to using the "standared" job scheduling tool.
    santosh

    Hello Santosh,
    the link that you already got is good. Perhaps you also want to check out [http://wiki.sdn.sap.com/wiki/display/SM/FAQJobSchedulingManagement|http://wiki.sdn.sap.com/wiki/display/SM/FAQJobSchedulingManagement] and [SAP is first vendor to provide a comprehensive Job Management Suite |SAP is first vendor to provide a comprehensive Job Management Suite] for further information.
    In short SAP CPS is an advanced scheduling tool like which competes against other like UC4, Control-M from BMC etc. But all these tools do not provide any real job documentation or job request functionality in order to get the process governance right. That's where the SolMan gets into the game.
    Best Regards
    Volker

  • KRONOS - EJB Job scheduler for Weblogic

    Paramus, NJ - February 22, 2002 - Indus Consultancy Services (ICS) today
    announced the latest in a series of improvements to Kronos Enterprise
    Scheduler, a full-featured job scheduling system written for the
    Enterprise Java (J2EE) environment.
    This version fixes some minor bugs reported by customers, and adds a new
    security feature to control user visibility to jobs, tasks, and
    schedules. A new environment setting allows the Kronos Enterprise
    Scheduler administrator to restrict users to seeing only those items
    which they have created. Administrators still have full visibility to
    all items.
    ICS is also proud to have Kronos Enterprise Scheduler competing in the
    Java Developer's Journal 2002 Readers' Choice Awards. Every year, Java
    Developer's Journal holds voting for products in a variety of
    categories. This year, Kronos Enterprise Scheduler is nominated in
    three of those categories:
    · Best Java Application (Standing as of 2/22/02 : 16th out of 69
    products with votes.)
    · Best Java Component (Standing as of 2/22/02 : 10th out of 26 products
    with votes.)
    · Most Innovative Java Product (Standing as of 2/22/02 : 21st out of 63
    products with votes.)
    To vote, visit the Java Developer's Journal website at
    <http://www.sys-con.com/java/readerschoice2002>
    To find out more about Kronos Enterprise Scheduler, and learn why
    companies around globe are selecting this powerful product to handle
    their scheduling needs, visit the ICS website at <http://www.indcon.com>
    and request a FREE 30-day evaluation.
    © 2002 Indus Consultancy Services, Inc. All rights reserved. Java and
    all Java-based marks are trademarks or registered trademarks of Sun
    Microsystems, Inc. in the U.S. and other countries. All other product
    and company names are trademarks of their respective owners.

    I would hope that BEA will step up and develop a replacement for their
    deprecated APIs. It is unfair to ask their customers to buy something they
    got previously for free. I also understand that the future EJB spec will
    contain scheduling features.

  • Job scheduling

    Hi Friends,
             i have a problem with job scheduling.
    two jobs need to be scheduled. (job1 and job2)
    i used
    job_open.
    submit job1 using parameters.
    job_close.
    then for second job.
    job_open.
    submit job2 using parameter2.
    job_close.
    when i go and look in sm37. i see when job1 is running the job2 is in release status.
    but what we need is when job1 is running job2 should be in schedule status. it should start only after job1 is completed.
    in the job2 job_close i used job1 as the PRED_JOBNAME.
    but i when i run the program job2 is in released status , not in schedule mode.
    is there any way we can make the job2 in scheduled mode instead of release.
    can we use event to control this. if yes please let me know how we can do it.
    Thanks

    Hi,
    As Appana wrote - i'm not sure there's a problem, but why don't u make one job with 2 steps? this way u will be perfectly sure that job2 (2nd step in the new job) will run only after job1 (1st step n the new job)...
    Good luck
    Igal

  • Internal error occurs in background job scheduling

    Hi Experts,
    We are facing an error message "Internal error occurs in background job scheduling" while trying to execute a custom report(Z report) in background in SA38.
    Please find the following observation on our side on this message.
    1) This message is not coming for only one report not for others.
    2) SU53 screen shot shows that SE38 check is failed, but the weird thing is not happening for other report.
    3) Persons having SE38 auhtorization are able to run this report.
    Please advise.
    Thanks in advance,
    Viven

    What is the message ID and number? Have you tried OSS search and debugging?
    What does this program do, in a nutshell?

Maybe you are looking for