Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Find frequently asked questions regarding job management in this blog, addressing Solution Manager 7.1 and 7.2. Unless not otherwise specified, topics are release independent.

Getting started - Prerequisites

Job Request

Job Documentation

Job Scheduling via SM36

Job Scheduling via SAP Central Process Scheduling by Redwood

Job Scheduling via Job Document (integration BC-XBP & SAP Central Process Scheduling by Redwood)

Job Monitoring (also integrated with Business Process Monitoring)

Change Management

Upgrade of Solution Manager 7.1 to 7.2

Central Job Overview


What is the recommended procedure to start with Job Management?

A: Job Management is technically implemented through a Guided Procedure in Solution Manager configuration
As the implementation has numerous integration aspects with different business and IT areas, we recommend following a project approach guided by a RSLF Roadmap.
To get an comprehensive overview on the implementation, we recommend to attend an Expert Guided Implementation (EGI) for Job Management. Please check the prerequisites for attendance
back to top

If I want to use the integration between SAP Solution Manager and SAP Central Process Scheduling by Redwood, do I need to perform additional configuration steps?

A: SAP note 1729766 CPS - Solution Manager integration setup gives a general overview about the required activities. It adresses also both versions of SAP CPS. An integral part of this integration is the SMSE interface (Solution Manager Scheduling Enabler).
back to top

What kind of document is a Job Request?

A: The Job Request is a CRM document usually of transaction type SMIN. In Solution Manager 7.0 this was of type SLFJ, or SLFN, the normal Service Desk document. It is recommended to copy this Transaction type to an own transaction type, for e.g. ZMIN.
back to top

Which systems are shown in the value help of the Job Request form?

A: When you access a Job Request form it is automatically assigned to your CRM Business Partner. Now when opening the value help for System/Client you only get to see those systems where your Business Partner is assigned to, i.e. those system/client combinations that you see in transaction BP under general information in tab strip "Identification" for each entry IDType "CRM001".
back to top

What do I need to fill-out in order to send a Job Request?

A: The following SDN Blog explains the major sections that a Job Request contains and what it takes to fill them out Creating a Job Request with SAP Solution Manager . Generally speaking you need to fill out the basice information required for a CRM document, i.e. the System/Client information which results in an IBase, the Short and Long Text (could be pre-filled when influencing the layout of the request form - see some question below) and the Business Partner for a reporter (automatically derived from the usere that calls the application) and sold-to-party (normally automatically derived in the background.
back to top

Is the Job Request a necessary prerequisite for creating a Job Document?

A: No, the Job Documentation application can also be used stand-alone. You can directly create/change/delete a Job Document. But in order to streamline and standardize the process of how job requirements from the business department or project team can be brought into the backend system, it is recommended to use the Job Request and Job Documentation application in an integrated manner.
back to top

Can I influence the layout of the Job Request form?

A: Yes, on the one hand you can configure static F4 value helps for selected fields. This can be defined in transaction SPRO under SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Extended Configuration > Adapt Organization Data.
On the other hand you can hide or pre-fill selected fields or declare selected fields as mandatory. This can be defined in transaction SPRO under SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Integration with Service Desk > Adapt Job Request Form > Create WebDynpro Component Configuration. More information can be found here How to configure SAP's standard Job Request form - Part 1 and How to configure SAP's standard Job Request form - Part 2
back to top

Can I create a Job Request from the "outside"?

A: Yes, function module AGS_EJR_CREATE_JOB_REQ can be used to create Job Requests from remote systems. You can also refer SAP note 1327024 - "Integration into and Migration to Job Documentation"
back to top

What kind of document is a Job Document - is it a CRM document like the Job Request?

A: No, the Job Document is no CRM document. The Job Document is a "normal" document stored in a flat table. Both the job request and the incident have an own number assigned.
By the way it is also no document in the Knowledge Warehouse of SAP Solution Manager.
back to top

Can I influence the layout of the Job Document?

A: Yes, you can decide whether the respective tab strip of the Job Document shall be visible or not. This can be defined in transaction SPRO under SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Extended Configuration > Adapt Job documentation > Adjust Job Documentation Tab Visibility.
back to top

Can I change the building blocks that are proposed as naming convention for the background job?

A: Yes, the proposed naming convention can be adjusted to your company's needs. For this purpose you need to implement a corresponding BAdI. This can be defined in transaction SPRO under SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Extended Configuration > Adapt Job documentation > Set Up Own Naming Convention for Job Documentation. More information can be found in the SDN Blog Implementation of a naming convention in Job Management .
back to top

Are there also Job Templates available?

A: Yes, SAP also provides Job Templates in order to ease the documentation of background if the same documentation can be applied to several systems, processes, or even customers. For more information refer to the SDN Blog Job Documentation Templates
back to top

In case I have to create many Job Documents. Is there some automatic help to fill-out some reoccurring information?

A: Yes, you can use macros in order to assign Contact Persons, Organizations, Logical Components (i.e. Systems) automatically. For more information refer to the SDN Blog Creation of Job Documentation Macros
back to top

Can I see, within the respective backend system, whether a Job Document exists for the respective job or not?

A: Yes, if your backend system runs on a recenter SAP NetWeaver support package then transaction SM37 provides an additional column that indicates if a corresponding Job Document exists. By clicking on this new icon you can directly access the Job Document. Details can be found in the SDN Blog A new column in transaction SM37 - Job Documentation
back to top

Can I delete a Job Document?

A: Yes and no. You can use the activity "Delete Job Documentation" from within the "Job Management" Work Center or you can directly set the Document Status "Deleted" within the Job Document itself. Then a corresponding deletion indicator is set in some database table and hence the Job Document disappears from all document lists, i.e. it is no loger displayed in those lists. But the document is actually not deleted from the database as there may be references to other (still) existing documents like Job Requests, Issues, Service Desk or Change Request messages.
back to top

Can I import / mass create Job Documents?

A: Yes, you can import jobs from your managed system as described here. With Solution Manager 7.2 SP08 (chargeable down port is possible) report AC_JSM_JOBDOC_MASS_MAINTENANCE will be delivered, that offers an excel based creation and mass maintenance of job documents.
back to top

Can I export a Job Document?

A: Yes, you can export a Job Documentation as an XML file. Please refer SAP note 1327024 - "Integration into and Migration to Job Documentation"
back to top

If I a job is scheduled via a Job Document (type BC-XBP) which interface is used and is SAP Solution Manager then controlling this job?

A: As the name implies the SAP Solution Manager uses the BC-XBP interface, just like any other external scheduling tool, in order to schedule the job. But unlike other scheduling tools the SAP Solution Manager "fires and forgets", i.e. the SAP Solution Manager is only creating the job in the respective backend system but does not control it. The full control is taken over by the CCMS infrastructure of the respective backend system. Hence the SAP Solution Manager cannot be considered a real scheduling tool.
The preferred SAP scheduling tool is SAP Central Process Scheduling by Redwood as this tool also provides many additional features that transaction SM36 does not provide, e.g.

  • Handling job interceptions
  • Providing logical queues and priorities from 1-100
  • Enhanced workload balancing based on CPU and memory consumption
  • Providing job chain functionality allowing complex job dependencies and event-based scheduling

back to top

Is Job Management providing event-driven capabilities without SAP CPS?

In general, Job Management in Solution Manager is acting as governance level, expert scheduling is provided through SAP CPS. This implies, that
Job Management in Solution Manager does not provide event driven scheduling dependencies. You can schedule Jobs or Job Chains through Job Management either directly on ABAP Systems (like SM36, using BC-XBP interface), or using Schedulers, like SAP CPS. SAP CPS itself provides powerful event control capabilities, like file events for e.g. It is not planned to provide this within Job Management, as this is provided through SAP CPS.

I am using an external job scheduling tool. Can I somehow identify whether end users are bypassing my central scheduling?

A: Yes, actually there is a rather easy way to identify end user scheduled jobs that are bypassing your central scheduling efforts. The key to the solution is the job status "Released". The exact details are described in the SDN Blog An easy way to identify end-user scheduled jobs which bypass your central scheduling tool
back to top

Can I somehow control jobs that are (de-centrally) scheduled by end users without taking scheduling authorization away?

A: Yes, that is possible. A quite common customer scenario is how to control end user jobs bypassing the central scheduling. There are two main features available: The redirect and the intercept. The redirect offers the possibility to redirect users to a job request form in Solution Manager. The intercept occurs once a job is ready to be executed. The intercept makes only sense with an external scheduler. See also Job Control in SAP Online Help (redirect) and Intercepting SAP Jobs .

However, please consider that the redirect is not catching job from application transactions, but only from basis transaction SM36, SM37, SA38. therefore, in addition refer to SAP Note 1716340: By setting “Restrict Generation of Periodic Jobs”, only one time jobs are allowed to be scheduled in Managed systems, but no periodic ones. According to the note, authorization checks also cover report transactions, i.e. a big portion of real  problem cases are already addressed, i.e. the use of redirect or even intercept might not be required.

back to top

What is the difference between Chargeable and OEM Version of SAP BPA and SAP CPS?

Redwood has introduced a new scheduler Version 9, distributed via the SAP price list as 'SAP Business Process Automation by Redwood' (SAP BPA). See also SAP Note 2005087 - SAP BPA V9 for further information regarding improved features.
This version is available only as Chargeable version, whereas the OEM version (free version) delivered with SAP Netweaver Java 7.3 stack is still the previous Version 8, named 'SAP Central Process Scheduling by Redwood' (SAP CPS). Technically it is also possible to run the OEM version with a chargeable license.

Feature overview in Chargeable and OEM version

To make it more convenient, we have published an overview on our SCN Wiki: Overview SAP BPA / SAP CPS

back to top

How many Systems can be connected and licensed with SAP CPS?

Licensing goes per process Server, that is required to connect any productive SAP or legacy system for scheduling and monitoring.
The license covers for a defined number of process servers to connect to scheduling systems a set of 4 CPS licenses, covering 2 non-prod sets of licenses, and one set that can be used for either non-prod or failover for production.

For each of the CPS environments, it is possible to install even several CPS Servers, but the total number of connected SAP or legacy systems cannot exceed the defined no. of process servers over the whole of productive CPS Servers.

So for example, you can install 1 prod CPS Server connecting to 10 SAP systems, or 2 prod CPS servers connecting to 5 each (or 6 and 4 etc), but you cannot install 2 prod CPS servers connecting to for example 6 each as the total would exceed the 10 for production.

If you run jobs against prod and non-prod systems from the same CPS, the entire CPS counts as production, so counts against the 10 production. So this is not recommended from licensing point of view, also from technical point of view it will be hard to test patches because you patch the entire CPS in one go.

In general, the recommendation is to separate the production CPS from any DEV or QA Landscape

back to top

How many Solution Managers can be connected to SAP CPS?

In the Basic Version 1 Sol Man can be connected.

In the Full Version, Several Sol Mans can be connected. This is defined in the parameter ProcessServerService.SAP.BAEConnector.limit . The BAE connection is typically the same number like process servers, as it is not only used for SolMan but also for BW and FCC integration.

So for scheduling and monitoring is possible to connect two Solman to one CPS, but from license and setup perspective it is questionable. In general, the recommendation is to separate the production CPS from any DEV or QA Landscape

back to top

Where can I find more information about SAP Central Process Scheduling by Redwood?

A: Please refer to http://scn.sap.com/docs/DOC-26195 for more information about the tool SAP Central Process Scheduling by Redwood. Please note that a new version is available, called SAP Business Process Automation (Version 9) An upgrade from SAP CPS cause minor efforts, but requires NW 7.30 Java Stack as platform
back to top

Which external scheduling tools can be integrated with SAP Solution Manager?

A: The SAP Central Process Scheduling by Redwood is tightly integrated with SAP Solution Manager. Meanwhile furher scheduler are also certified for the SMSE interface, namely CA Workload Automation Advanced Integration, IBM Tivoli Workload Scheduler and Automic One Automation. Nevertheless you can of course also use Job Request, Job Documentation and Job Monitoring functionality in combination with other every other external scheduling tool. But then you have to transfer scheduling information manually from the Job Document to your respective scheduling tool (like you probably transfer data nowadays from MS Excel to your scheduler). And other external scheduling tools do not provide any feedback loop to SAP Solution Manager like SAP Central Process Scheduling by Redwood does.
back to top

Where can I find answers to FAQs around the job scheduling itself in the SAP system?

A: SAP note 31503 "FAQ: Background jobs" answers frequently asked questions around background jobs in general in the SAP system, e.g. "Can I reserve background work processes for individual applications or users?" or "Can job definitions be transported into other clients or systems?"
back to top

Where can I find some help for troubleshooting if I encounter problems with SM36/SM37 scheduling?

A: SAP note 37104 "Error analysis: Background processing system" helps with analyzing the most typical error situations when it comes to problems with SM36/SM37 scheduling.
back to top

Can I monitor non-SAP jobs with Solution Manager Job Monitoring?

A: Only if you use the integration between SAP Central Process Scheduling by Redwood (SAP CPS) and SAP Solution Manager and only if you bought licenses that allow to schedule also non-SAP jobs with SAP CPS, then you can extend the Job Monitoring also to non-SAP jobs. 
back to top

Can I monitor complete BW Process Chains?

A: Yes, you can use Job Monitoring in order to monitor complete BW Process Chains (identified by the respective chain ID) and monitor specific elements within a chain. This was described in the two blogs Best Practice: BW Process Chain monitoring with SAP Solution Manager - Part 1 and Best Practice: BW Process Chain monitoring with SAP Solution Manager - Part 2: Setup example . The setup has to be done directly in the Job Monitoring setup and not within a Job Documentation. The Job Documentation application cannot really be used (yet) for BW Process Chains as those chains are always using generic job names.
back to top

Can I monitor job run-times, and report on the trend over the last couple weeks and see, which jobs deteriorated?

A: Yes, this kind of trend reporting is possible, even without configuring job monitoring by making use of the job health check (setup guide available at Job Management) that collects job data into SAP BW and setup dashboards. As of Solution Manager 7.2 SP08 the "ABAP Job - Health Status (cross system)" dashboard is available in your system (https://<server>:<port>/sap/bc/ui2/flp?sap-client=<client>&sap-language=EN#Action-SMConfKPIVisualization --> Business Process Operations). For details on the dashboard, please see here
back to top

Can I monitor jobs for "Cancellation" and "Delay" without setting up job monitoring?

A: Yes, you can activate the job health check (setup guide available at Job Management) data extraction and build a dashboard that show you cross system job cancellations, technical delays and even run-time deterioration of jobs. Via such a dashboard you have no automated alerting though. As of Solution Manager 7.2 SP08 the "ABAP Job - Health Status (cross system)" dashboard is available in your system (https://<server>:<port>/sap/bc/ui2/flp?sap-client=<client>&sap-language=EN#Action-SMConfKPIVisualization --> Business Process Operations). For details on the dashboard, please see here
back to top

What happens when I activate Change Control for some Job Document?

A: If the Change Control is activated for some Job Document then this document can only be changed together with a valid Change Document as part of the Change Request Management. So only if your CRM Business Partner is assigend as processor for the Change Document then you can change the corresponding Job Document. All other users have no authorization to perform any changes on the Job Document.
back to top

Is a transport mechanism with Versioning available with Job Management?

This is partly provided through Job Management in Solution Manager. In Job Management, you can use versioning for job documentations. This is a manual process, versions are not created automatically.
ABAP based reports for Jobs / Variants need to be transported via Transport Management. For SAP BPA (successor of SAP CPS, prerequisite is NW 7.30 Java Stack) an integration to CTS+ is available. Without that, job  definitions need to be transported through export/import on SAP CPS.
back to top

Is Job Management in SAP Solution Manager SOX compliant?

Regarding the Sarbanes-Oxley Act (see SOX in SAPedia) there is no formal statement for Solution Manager SOX compliance in place, as SolMan is typically not affecting financial transactions directly.
With regards to Job Management, it might happen that jobs with financial impact can be scheduled, and therefore there might be a need for governance and logging.

In Solution Manager Job Management there should be sufficient features to fulfill SOX compliance, such as change governance through an ITSM process, or even ChaRM, also change logs for every job documentation used for scheduling through Solution Manager.
In case SOX compliance need to be fulfilled, requirements need to tested and approved by the customer and/or the certification auditing authority.

back to top

Can Job Documentations be transferred from 7.1 to a greenfield 7.2 Solution Manager?

You have a 7.1 SOLMAN with active Job Documentation and scheduling and intend to start on 7.2 from scratch and transfer 7.1 process documentation (via project download and upload) and perform Solution Documentation content activation as suggested by SAP.
1. Will the job documentation content be included in the transport of the 7.1 project?
2. Will it be activated by content activation?

A: In principle yes, but you need to transfer on top your job documentations on DB level using reports RAGS_JOBDOC_DOWNLOAD_ALL and RAGS_JOBDOC_UPLOAD_ALL (please note, that job monitoring is not transferred): 

Step 1: Use reports RAGS_JOBDOC_DOWNLOAD_ALL and RAGS_JOBDOC_UPLOAD_ALL to download the job documentation tables content into an XML file and upload them again. Via this approach you do a DB level copy, i.e. all document IDs stay, but attachments are lost. In a greenfield 7.2 Solution manager the resulting job documentations will point not existing logical components, solution directory contexts or technical scenarios. Consequently access to the related systems (e.g. for scheduling) will not be possible.

Step 2: Restore the system relationship:

Case a: Job Documentations were not referenced to solution directory contexts, but only to logical components or technical scenarios.
→ Execute report AGS_EJR_SMUD_MIGRATION. The report will try to map the logical components to new logical component groups and where this is not possible offer you to map logical components to technical scenarios

Case b: Job Documentations were referenced to solution directory contexts (and also to logical components or technical scenarios)
-→ On 7.1 copy the relevant solution directory contexts into a SOLAR project, to get the link between Job Documentation and process context persisted in the project. Then transfer the project content to the greenfield 7.2 Solution Manager and execute content activation. After content activation execute report AGS_EJR_SMUD_MIGRATION.  

Step 3: Migrate scheduling information (as on 7.2 there is only one scheduling version for a JD)

By executing report RAGS_EJR_MIG_SYSTEM_SCHE_INFO the job documentations with scheduling information in more than one version will be adapted.

back to top

After upgrade to Solution Manager 7.2 are my job documentations already usable or is a migration needed?

A: There are two major changes, that require a migration of job documents. First, logical components are replace in 7.2 by logical component groups and second the scheduling information within a job document is not versioned any more. For the migration of the pointer to logical components you need to execute report AGS_EJR_SMUD_MIGRATION and for the migration of the scheduling information you need to execute report RAGS_EJR_MIG_SYSTEM_SCHE_INFO. The process in detail is:

Step 0: Prepare content activation on your Solution Manager 7.1 (if you want to reuse process documentation and related job monitoring that you defined on 7.1 also on your 7.2 Solution Manager)

Step 1: Upgrade your Solution Manager to 7.2 and implement notes relevant to reports AGS_EJR_SMUD_MIGRATION and RAGS_EJR_MIG_SYSTEM_SCHE_INFO.

Step 2: Make sure you have logical component groups containing the scheduling relevant systems. This means, you either perform content activation or you create a solution with logical component groups containing the scheduling relevant systems in the correct system role (so that a automatic mapping is possible). Note that if you did content activation as post upgarde activity, accessible from Solution Manager configuration, you did a mapping of the obsolete logical components to new logical component groups.

Step 3: Execute report AGS_EJR_SMUD_MIGRATION

Step 4: Execute report RAGS_EJR_MIG_SYSTEM_SCHE_INFO

back to top

For job scheduling I am using a Redwood (CPS) scheduler, but also schedule ABAP jobs directly in the managed systems. How can get an overview on all my ABAP Jobs?

A: We recommend to use the Central Job Overview (CJO) application, that provides you with an overview of the status of the jobs scheduled in your Managed ABAP System as well as those scheduled with the external scheduler SAP Central Process Scheduling by Redwood (SAP CPS). This is a unified application provides an overview of the scheduled jobs in all the ABAP systems and CPS systems. On how to enable CJO on your Solution Manager, please refer to SCN Job Management --> Configuration Guide for Central Job

back to top

I use Central Job Overview as kind of cross system SM37, but I am not satisfied with its performance, what can I do? Also, I am not able to see CPS job chain hierarchy for jobs in status scheduled.

A: To see also job chain hierarchy information for scheduled jobs and in order to improve the performance we recommend to fill a buffer table (i.e. SJO_HIERARCHY) with a regular job the executes report SJO_EXT_SDL_BUFFER_FILL for every SAP system that is connected to your Redwood scheduler with following input:

a) specify the relevant system and client

b) Option "Full Load"


back to top

We scheduled job SAP_WORKFLOW_ACTION from Solution Manager Job Document and it started to run under the user maintained in the TMW RFC connection. However, soon the scheduling switched back to user DDIC. How can this happen?

A: If your managed system is an S/4HANA onPremise system, there is a new feature called “Technical Job Repository” which automatically schedules technical  jobs from “Job Definition” objects. The Job Definition objects can be viewed in transaction SJOBREPO. There are seven SAP_WORKFLOW* job defs.

Background info is here: https://launchpad.support.sap.com/#/notes/2190119

Jobrepo uses an automatic mechanism which schedules/unschedules jobs every hour. This mechanism is present in every SAP S/4HANA system (cloud and onPremise).

You can monitor what jobrepo is doing in SLG1 (application log), use JOB_ACTIVATION as object. If jobrepo changed your job of same name, you will find a message there.

In case of conflicts (because e.g. you do not want Jobrepo to schedule/change certain jobs)  you can disable a job definition (i.e. make jobrepo ignore this job definition) in transaction SJOBREPO (must do that in the client where the jobdef is relevant, e.g. SAP_WORKFLOW* job definitions are only relevant for a business client).

You can control which user Jobrepo uses to schedule its jobs: https://launchpad.support.sap.com/#/notes/2339022

DDIC is indeed the default if no specific user has been set via above method.

back to top

I have a frequently executed job. I want to get alerted only, if the job fails for a longer time period. How can I achieve this?

A: Use the Table Entry Counter, which is part of the Business Process Monitoring framework within SAP Solution Manager, to get alerted, if the number of successful executions of a job drops below a certain number. For details please refer to this document.

back to top

I monitor a job. The job fails and in the monitoring application, I see that the summary status is red. The next execution of the job is successful. In the monitoring application, I see that the summary status is still red! Why?

A: The job monitoring application displays as summary rating the worst rating of any job in the list of job instances. The job instances listed in the monitoring application, depends on two parameters that you can configure in the configuration UI:

     1. Total number of instances

     2. Data Retention Period (in days)”

When you create a new job monitoring object the number of job instances is defaulted to 12 and the data retention period to 2 days. This means that for an hourly job, you will see typically 12 instances in the monitoring application and for a daily job 2 instances. Why is 12 defaulted? As the default data collection period is 60 min, the data collector will return 12 job instances for a job that runs every 5 min. In this case for the summary rating all 12 job instances are relevant.

For the cases, where the job frequency is lower than the data collection frequency and the status of the last job execution is relevant for the status of the job, setting the number of instances to 1 is the right choice. So please decide yourself and specify the number of job instances relevant for the summary rating of the job. Make sure the number is at least the number of expected job instances between two data collections, as otherwise you might not be alerted for a failed job instance.

back to top

If a job is scheduled via a Job Document (type BC-XBP) it can not be changed in the managed system's SM37. At system upgrade we need to de-schedule all jobs though. How can we handle this?

As part of production downtime activities, Service Management teams perform pre and post downtime background job manipulation. These activities are detailed below:

Pre-Downtime
1. Jobs are manually moved from “Released” Status to “Scheduled” status via SM37 by Service Management
2. Priority Jobs are taken into account
3. Non-Priority jobs that are scheduled to run during the course of the downtime are taken into account

Post-Downtime
1. Priority Jobs are supposed to be released, meaning moving the status from “Scheduled” to “Released” status manually in SM37
2. Non-priority jobs that are scheduled to run during the course of the downtime are re-scheduled to run on its next effective schedule after the downtime

In the event that Solution Manager is down, changes cannot be made in the jobs that are linked to a Job Documentation. While it is possible to move jobs linked to Job Documentation from “Released” status to “Scheduled” status manually via SM37, moving them back to “Released” status is not possible. Is there any way to enable this in the managed systems?

A: Before downtime execute report BTCTRNS1 to put all jobs that are in status "Released" to status "Released/Susp". After downtime execute report BTCTRNS2 to put jobs of status "Released/Susp" to status 'Released' again.

back to top

When I schedule two jobs with a predecessor-successor relationship (start condition "Start after job"), I can schedule the predecessor periodically, but not the successor! Is there a better solution?

A: BTC_EVENT_RAISE program is available to solve this technical problem. Background info is here: https://launchpad.support.sap.com/#/notes/919458

back to top

We use the Job Management functionality in SAP Solution Manager, i.e. document our jobs and schedule them centrally from Solution Manager. Now we have a new project, which makes a set of jobs obsolete and requires a new set of jobs to be scheduled at go live. How can we mass schedule / de-schedule documented jobs?

A: You can use the mass scheduling report RAGS_JSM_MASS_SCHEDULE available as of 7.2 SP07. Background info on the tool can be found here: https://blogs.sap.com/2018/02/21/job-management-mass-scheduling-tool/

back to top


 

If you are interested in further reading. The following blogs provide further details about Job Management functionalities within the SAP Solution Manager.