This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
SAP jobs been deleted doesn't have any control from scheduling tool
SAP Jobs being constantly deleted or manually released by the end-user, causing the job in TWS side to loose its reference with the SAP job and failing, impacting the business.
We'd like to have a solution developed and embedded in TWS to either synchronizing jobs, meaning that the external scheduler reads all jobs from the SAP system, which have been created from a certain point of time on. Thus, the external scheduler can synchronize its jobs with the job database of an SAP system. Or, instead of creating the jobs in SAP system, TWS would store all the configuration within TWS and only at the time of execution, the job would be created and released.
I prefer the last option since it would solve many issues we currently have by having the jobs created in "Scheduled" status in SAP.
Do not place IBM confidential, company confidential, or personal information into any field.