job management sap pi
DESCRIPTION
Job Management SAP PITRANSCRIPT
Business Process OperationsJob Scheduling ManagementSAP AGSeptember, 2011
© 2011 SAP AG. All rights reserved. 2
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.
© 2011 SAP AG. All rights reserved. 3
Agenda
Job Scheduling Management Suite Supporting the lifecycle of a background job (request, document, schedule,
monitor)
Getting control over End-User jobs Intercepting Jobs & Re-directing users from SM36 to the SAP Solution Manager
Job Scheduling Management Health Check Analyzing the respective backend workload caused by background jobs
Further Information SAP notes, SAP Service Marketplace links and SDN blogs Compare SM36 and SAP CPS
© 2011 SAP AG. All rights reserved. 4
Why Focus on Job Scheduling Management?Applications & Challenges
Goal Application Challenge
VisibilityJob Documentation
…provide standardized & web-based documentation…avoid unnecessary job processing (“forgotten” jobs)…avoid unnecessary slow support processes…”living” documentation vs. one-time documentation
Efficiency
SAP Central Process Scheduling by Redwood
... automate job processing where possible (job chains)…schedule across system boundaries…event-driven vs. time-driven scheduling…control end-user jobs (job interception)
Effectiveness
Business Process Monitoring
…ensure that jobs start/finish at the right time…ensure job processing within given time windows…correlate important jobs with business processes…management by exception
GovernanceJob Request
…provide standardized & web-based request form…integration with standard incident management process…integration with standard change management process…integration with documentation, scheduling & monitoring
Clean-up
Job Scheduling Management Health Check
…ensure even workload distribution…avoid unnecessary often job processing…discontinue jobs that are no longer needed …avoid redundant job processing
© 2011 SAP AG. All rights reserved. 5
Job Scheduling Management – Process View
IT Department
SAP Technical Operations
Business Department
Business ProcessOperations
Key User/End User Application Management
RCA process
Create Job Request Plan Job Request
Approve/Reject Job Request
Receive Approval/Rejection
Document Job
Test Job
Schedule Job
Run Job
Monitor Job
Document Job
Job Scheduling Management SuiteSupporting the lifecycle of a background job (request, document, schedule, monitor)
© 2011 SAP AG. All rights reserved. 7
Scenario Business Process ”Order to Cash” – Job Scheduling Management
CRM - C00
Create Sales Order
SAP ECC - SMY
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery
Post Goods Issue
Create Billing Document
Warehouse - TT5
Create Outbound Delivery
Create Picking Transfer Order
Confirm Picking
Transfer Order
Post Goods Issue
SAP ENTERPRISE
PORTAL - EPP
Create Sales Order
New job S_DE_PP_MRP_0001_D should run daily
Business Process Champion
We would like to schedule an MRP run once per day for our new German plant 0001
© 2011 SAP AG. All rights reserved. 8
Use Job Request Form for Requesting New Job (1/2)
Check for naming convention
Web form can be integrated in Enterprise Portal or intranet
© 2011 SAP AG. All rights reserved. 9
Use Job Request Form for Requesting New Job (2/2)
Web form can be integrated in Enterprise Portal or intranet
© 2011 SAP AG. All rights reserved. 10
Job Scheduling Management - Work Center
Information initially maintained in web form (e.g. by business) is saved as Job Request document in SAP Solution Manager and can be now picked up by IT via the Work Center UI.
© 2011 SAP AG. All rights reserved. 11
Job Request Message created with Context Information
The created Job Request is part of the Job Scheduling Management assignment block within a corresponding CRM incident (type SMIN). Here you are able to create a Job Document as follow-up document.
© 2011 SAP AG. All rights reserved. 12
Job Documentation – Overview
The Job Document contains all the information that was already maintained in the corresponding Job Request and the Job Document is also linked to the Job Scheduling Management assignment block.
© 2011 SAP AG. All rights reserved. 13
Planning – Check if New Job Request Fits Into Existing Schedule
Use BACKGROUND_JOB_ANALYSIS tool in transaction ST13 to check job distribution
HW & time restrictions scheduling at 5:30 might be a problem other less important jobs might need a rescheduling
© 2011 SAP AG. All rights reserved. 14
Job Documentation – Overview
The Job Document that was created in reference to the Job Request can also be picked up and further processed by IT via the Work Center UI.
© 2011 SAP AG. All rights reserved. 15
Job Documentation – Scheduling Maintenance
Configure corresponding job scheduling from within job documentation.
1
23
© 2011 SAP AG. All rights reserved. 16
Job Scheduling Management - Work Center
© 2011 SAP AG. All rights reserved. 17
Scheduling in SAP Central Process Scheduler (1/2)
© 2011 SAP AG. All rights reserved. 18
Scheduling in SAP Central Process Scheduler (2/2)
© 2011 SAP AG. All rights reserved. 19
Job Documentation – Monitoring Maintenance
1
23
Configure corresponding Business Process Monitoring alerts from within job documentation.
© 2011 SAP AG. All rights reserved. 20
SAP Solution Manager integration with SAP CPS Business Automation Enabler (BAE) interface
SAP Solution Manager 7.1
Business Process Monitoring
Job Request
Job Documentation SAP NW
7.0RedwoodProcessServer
Job Scheduling
SAP Central Process Scheduling by Redwood
Web FormEnterprise Portal/
IntranetEnd/Key user request – JR message creation in background
Job documentation automatically populated with respective CR data
Change Request Management
Transfer job documentation (incl. basic
scheduling)
Push Monitoring information
SAP System
BAE
BAE
BAE = Business Automation Enabler
© 2011 SAP AG. All rights reserved. 21
SAP Solution Manager Lean Job Request Scenario With Arbitrary Scheduling Tool
Business Process Monitoring
Job Request
Job Documentation
Web FormEnterprise Portal/
IntranetEnd/Key user request – JR
message creation in backgroundJob documentation automatically populated with respective job request data
External Job Scheduler
Pull Monitoring information from Back-end
Manual Transfer of job documentation (copy & paste)
SAP Solution Manager 7.1
SAP System
© 2011 SAP AG. All rights reserved. 22
SAP Solution Manager integration Solution Manager Scheduling Enabler (SMSE) interface
SAP Solution Manager 7.1
Business Process Monitoring
Job Request
Job Documentation Job
Scheduling
External Scheduler certified for SMSE
Web FormEnterprise Portal/
IntranetEnd/Key user request – JR message creation in background
Job documentation automatically populated with respective CR data
Change Request Management
Transfer job documentation (incl. basic
scheduling)
Push Monitoring information
SAP System
SMSE
SMSE
SMSE = Solution Manager Scheduling Enabler
© 2011 SAP AG. All rights reserved. 23
Job Management Suite SAP Solution Manager & SAP Central Process Scheduling by Redwood
SAP Solution Manager SAP Central Process Scheduling by Redwood
Standardized job request form (web-enabled)
Standardized, central job documentation
Job documentation templates
Business process-orientated job monitoring
Trend reporting based on monitoring data
Integrated change request management with approval process
SAP backend related job reporting
Central job scheduling
Event-driven scheduling
ABAP, JAVA, OS and non-SAP* scheduling
Job chain management across system boundaries*
Time-zone & calendar management
Job interception
Workload balancing
SAP Service Desk integration
Business Automation Enabler (e.g. Closing Cockpit)
Full control over end-user scheduling: Redirecting end-user into job request process & rule-based job interception
Request
Docu-ment
Monitor
Schedule
Optimize
Report
Job Management
* Chargeable SAP CPS version
Closed-loop integration
Getting control over End-User jobsIntercepting Jobs & Re-directing users from SM36 to the SAP Solution Manager
© 2011 SAP AG. All rights reserved. 25
One Main Challenge of Job Scheduling Management – Control Over End-User Jobs
Problem: Many customer systems “suffer” under a high number of background jobs scheduled by end-usersEnd-user jobs undermine central scheduling Workload balancing undermined Risk of system overload especially during Period End Closing No monitoring & error-handling procedures defined for end-user jobs, i.e. SLAs usually ignore the fact of end-user scheduled
jobs No documentation exists for end-user jobs End-user jobs do not follow general naming conventions
Challenge: Scheduling authorization (transaction SM36) cannot be taken away due to company policy or as the scheduling happens as part of a business transaction
Goal: Smooth transition from end-user scheduled jobs into a standardized & centralized Job Management processNo scheduling authorization should be taken awayAll periodic jobs should be documented and follow a standard procedureAll one-time jobs should bypass the formal process but should be controlled anyway (via job interception)
© 2011 SAP AG. All rights reserved. 26
Maintain table TBCICPT1 Go to transaction SE16
Enter table name TBCICPT1
Create a new entry which jobs and/or jobs of which user should be intercepted
An external scheduler like SAP Central Process Scheduling by Redwood would use function module BAPI_XBP_MODIFY_CRITERIA_TABLE in order to read or change table TBCICPT1
Job Interception Option 1: Maintenance via table TBCICPT1
© 2011 SAP AG. All rights reserved. 27
Execute program CRITERIA_MANAGER (transaction CRIT) Add a new Criterion of Type “Interception”
For this type: Add a new criterion specifying which jobs and/or jobs of which user and/or of which job calls should be included/excluded from job interception
Activate the newly created profile
An external scheduler like SAP Central Process Scheduling by Redwood would use function modules BAPI_CM_CRITERIA_SET, BAPI_CM_PROFILES_GET, BAPI_CM_PROFILE_CREATE, BAPI_CM_PROFILE_ACTIVATE in order to perform those activities
Job Interception Option 2: Maintenance via program CRITERIA_MANAGER
© 2011 SAP AG. All rights reserved. 28
Job Interception Job Overview SM37 in backend system
While user VONGLOEDEN was able to schedule, release and run jobs in the past, he is now only able to schedule them but they get all intercepted!
© 2011 SAP AG. All rights reserved. 29
Job Interception Configuring SAP Central Process Scheduler by Redwood
Within SAP CPS you can then define several different interception rules per backend system and configure how SAP CPS shall proceed with which intercepted jobs.
© 2011 SAP AG. All rights reserved. 30
Execute program CRITERIA_MANAGER (transaction CRIT) Add a new Criterion of Type “Creating Batchjobs via Solutionmanager”
For this type: Add a new criterion specifying which users should be included/excluded from re-direction
Activate the newly created profile
New: Re-directing end-users Maintenance via program CRITERIA_MANAGER
© 2011 SAP AG. All rights reserved. 31
An end-user fitting the criteria calls transaction SM36 The end-user doesn’t get to see the screen from transaction SM36 any longer
Instead the user gets to see a pop-up window referring to SAP Solution Manager
Confirming the pop-up window leads directly to the job request form in SAP Solution Manager
New: Re-directing end-users Calling transaction SM36
Technical prerequisite: See SAP note 1383398 “Integration of Job Request into transactions SM36 and SM37”
© 2011 SAP AG. All rights reserved. 32
New: Re-directing end-users Job Request Form
The first screen is used to provide scheduling information and shows basically all fields that are also available in transaction SM36
© 2011 SAP AG. All rights reserved. 33
New: Re-directing end-users Job Request Form
Depending on the scheduling, the SAP Solution Manager decides if the job is scheduled immediately or if a job request is created
User & Business Partner information is filled automatically
Job Request information is filled automatically, so that only process & requirement information needs to be provided by the user
© 2011 SAP AG. All rights reserved. 34
SAP Solution Manager Job Request Process for periodic jobs
SAP Solution Manager 7.1
Job Documentation
End-User calls transaction SM36
Job request creation in background
Schedule job directly via XBP or transfer job documentation (incl.
scheduling data) to SAP CPS
SAP System
Dialog pops-up & leads to Web Form which is autom.
filled with system & user data
Job documentation automatically populated with respective job request data
Schedule job centrally via SAP
CPS
Web Form
SAP NW 7.0
RedwoodProcessServer
Job Scheduling
SAP Central Process Scheduling by Redwood
Job Request
© 2011 SAP AG. All rights reserved. 35
SAP Solution Manager 7.1
SAP Solution Manager Job Request Process for one-time jobs
End-User calls transaction SM36
SAP System
Dialog pops-up & leads to Web Form which is autom.
filled with system & user data Web Form
One-time job is directly scheduled via XBP interface
Job is intercepted via XBP interface based on interception table
(Re-)Schedule job centrally via SAP CPS based on rules
Job Documentation
SAP NW 7.0
RedwoodProcessServer
Job Scheduling
SAP Central Process Scheduling by Redwood
Job Request
Job Scheduling Management Health Check Analyzing the respective backend workload caused by background jobs
© 2011 SAP AG. All rights reserved. 37
One Main Challenge of JSM – Transparency Over Total Background Job Workload
Problem: No sufficient transparency exists how much system workload is caused by background jobs and which jobs are causing most problemsOverall system workload that is caused by background jobs shall be reducedEnd user scheduled jobs that bypass central scheduling and cause high workload shall be identifiedSystem bottlenecks (like lack of work processes) shall be identifiedEnsure even workload distribution across servers
Goal: Provide SAP BW based bar charts for analysisIdentify Longest running jobs Jobs that run and/or cancel most often Jobs with longest Start Delay times
Show distribution of background jobs Across application servers Across creating/scheduling users
© 2011 SAP AG. All rights reserved. 38
Job Scheduling Management Health CheckArchitecture Overview
© 2011 SAP AG. All rights reserved. 39
Job Scheduling Management Health Check Technical Prerequisites
Minimum:
SAP Solution Manager 7.0 with SP23 & BI_CONT 7.04 SP07 (or higher) and ST-A/PI 01M* (or higher) on the respective backend system (SAP BASIS 620 or higher).
SAP Solution Manager 7.1 with SP01 & BI_CONT 7.05 SP01 (or higher) and ST-A/PI 01M* (or higher) on the respective backend system (SAP BASIS 620 or higher).
Recommended (if you also want to analyze job step data from table TBTCP):
SAP Solution Manager 7.0 with SP27 & ST-BCO 400 SP0 (or higher) and ST-A/PI 01M* (or higher) on the respective backend system (SAP BASIS 620 or higher with SAP Note 1564604 implemented).
SAP Solution Manager 7.1 with SP02 & ST-BCO 710 SP0 (or higher) and ST-A/PI 01M* (or higher) on the respective backend system (SAP BASIS 620 or higher with SAP Note 1564604 implemented).
See also SAP note 1516666 for details of the Setup Guide.
© 2011 SAP AG. All rights reserved. 40
Job Scheduling Management Health CheckDashboards
After the activation of the JSM Health Check, three different reporting views with different granularity can be accessed directly via the JSM Workcenter Daily view (containing data from actual day) Weekly view (aggregated, containing data from last week) Monthly view (aggregated, containing data from last six months)
Each view contains a set of key performance indicators (e.g. Top 10 Execution Server) with the following distinctions (Total) number (Total) duration Tabular Drilldown into details (which can be exported to Microsoft Excel)
The data transfer between the different Info Cubes used (aggregation) and the reorganization (housekeeping) is executed automatically in background.
© 2011 SAP AG. All rights reserved. 41
Example Screenshots 1/6Comparing Job Status: Finished vs. Canceled
© 2011 SAP AG. All rights reserved. 42
Example Screenshots 2/6Workload Distribution per Duration
© 2011 SAP AG. All rights reserved. 43
Example Screenshots 3/6Workload Distribution per Start Delay
© 2011 SAP AG. All rights reserved. 44
Example Screenshots 4/6Workload Distribution by User
© 2011 SAP AG. All rights reserved. 45
Example Screenshots 5/6Workload Distribution by Execution Server
© 2011 SAP AG. All rights reserved. 46
Example Screenshots 6/6Tabular Drilldown
Further InformationSAP notes, SAP Service Marketplace links and SDN blogs
Compare SM36 and SAP CPS
© 2011 SAP AG. All rights reserved. 48
Job Scheduling Management – Suite
© 2011 SAP AG. All rights reserved. 49
Job Scheduling Management – Suite
© 2011 SAP AG. All rights reserved. 50
Further Information – SAP Notes
1054005 - FAQ: Job Scheduling Management with SAP Solution ManagerDescribes roles and SPRO activities in order to get started with Job Management in SAP Solution Manager
1117355 - Job Scheduling Management: Work CenterDescribes steps in order to activate the Job Management Work Center
1111310 - Job Scheduling Management: Extended ConfigurationDescribes configuration steps for Service Desk so that Job Request and Job Documentation get linked
1122497 - Process scheduling for SAP Solution ManagerInformation around the Process Scheduling Adapter for SAP Solution Manager1265635 - How to setup BAE (Business Automation Enabler)
© 2011 SAP AG. All rights reserved. 51
Further Information – Links
Job Scheduling Management on SAP Service Marketplacehttps://service.sap.com/jsm
SAP Central Process Scheduling by Redwood on SDNhttps://www.sdn.sap.com/irj/sdn/nw-scheduling
Business Process Monitoring on SAP Service Marketplacehttps://service.sap.com/bpm
Business Process Monitoring on SDNhttps://www.sdn.sap.com/irj/sdn/nw-processmonitoring
White Paper & Best Practice about Job Scheduling ManagementLink to White Paper „Job Scheduling Management“Link to Best Practice „Job Scheduling Management“
© 2011 SAP AG. All rights reserved. 52
Further Information – SDN Blogs & Wiki
SAP is first vendor to provide a comprehensive Job Management Suite http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14621
FAQs about Job Scheduling Managementhttp://wiki.sdn.sap.com/wiki/display/SM/FAQ+Job+Scheduling+Management
Job Interception: Controlling end-user scheduled jobs http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14715
Re-directing transactions SM36, SM37, SA38: Controlling end-user scheduled jobs – Part 1 & 2http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17544 http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17799
Implementation of a naming convention in JSMhttp://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14716
© 2011 SAP AG. All rights reserved. 53
Comparison of SM36 and SAP CPS (1/2)
SM36 SAP CPS
Scheduling of SAP jobs only Scheduling of SAP & non-SAP jobs
Local Scheduling for one system only Central Scheduling for entire system landscape (SAP & non-SAP)
Mainly time-driven scheduling Mainly event-driven scheduling (higher throughput)
Only three different job classes A, B, C Job priorities between 1-100
Only two queues (class A vs. class B and C) Several logical queues can be created (e.g. per application)
No job chain functionality Job chain functionality within and across system boundaries
No automation possible Process automation depending on raised events across system landscape
© 2011 SAP AG. All rights reserved. 54
Comparison of SM36 and SAP CPS (2/2)
SM36 SAP CPS
Not possible to schedule periodic jobs only at certain time frames (business hours)
Several time windows & submit frames can be defined and included/excluded into each other
One job per variant (e.g. per plant) One job definition can be used with different parameters
Simple workload distribution (depending on free BTC work processes)
Sophisticated workload distribution (depending on CPU utilization, Memory paging etc. )
Job dependencies hardly considered Job dependencies across systems (SAP and non-SAP) considered
No control over jobs that are directly scheduled by end-users
End-user jobs can be intercepted
No control over parent-child jobs Possible to check if all related child jobs are successfully finished
Integrates with SAP Solution Manager Integrates with SAP Solution Manager
© 2011 SAP AG. All rights reserved. 55
Thank you for your attention
© 2011 SAP AG. All rights reserved. 56
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
© 2011 SAP AG. All rights reserved
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.