Tadm12_1 en Col99 Fv Part Ltr

TADM12_1 SAP NetWeaver AS – Implementation & Operation II SAP NetWeaver

Date Training Center Instructors Education Website

Participant Handbook Course Version: 99 Course Duration: 10 Days Material Number: 50118034

An SAP course - use it to learn, reference it for work

Copyright Copyright © 2013 SAP AG or an SAP affiliate company. All rights reserved. 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.

Trademarks Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. Bluetooth is a registered trademark of Bluetooth SIG Inc. Citrix, ICA, Program Neighborhood, MetaFrame now XenApp, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. Edgar Online is a registered trademark of EDGAR Online Inc., an R.R. Donnelley & Sons Company. Facebook, the Facebook and F logo, FB, Face, Poke, Wall, and 32665 are trademarks of Facebook. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik, and Android are trademarks or registered trademarks of Google Inc. HP is a registered trademark of the Hewlett-Packard Development Company L.P. HTML, XML, XHTML, and W3C are trademarks, registered trademarks, or claimed as generic terms by the Massachusetts Institute of Technology (MIT), European Research Consortium for Informatics and Mathematics (ERCIM), or Keio University. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. INTERMEC is a registered trademark of Intermec Technologies Corporation. IOS is a registered trademark of Cisco Systems Inc. The Klout name and logos are trademarks of Klout Inc. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Mozilla and Firefox and their logos are registered trademarks of the Mozilla Foundation. Novell and SUSE Linux Enterprise Server are registered trademarks of Novell Inc.

g201331611644

OpenText is a registered trademark of OpenText Corporation. Oracle and Java are registered trademarks of Oracle and its affiliates. QR Code is a registered trademark of Denso Wave Incorporated. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld are trademarks or registered trademarks of Research in Motion Limited. SAVO is a registered trademark of The Savo Group Ltd. The Skype name is a trademark of Skype or related entities. Twitter and Tweet are trademarks or registered trademarks of Twitter. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Wi-Fi is a registered trademark of Wi-Fi Alliance. SAP, R/3, ABAP, BAPI, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, Sybase, Adaptive Server, Adaptive Server Enterprise, iAnywhere, Sybase 365, SQL Anywhere, Crossgate, B2B 360° and B2B 360° Services, m@gic EDDY, Ariba, the Ariba logo, Quadrem, b-process, Ariba Discovery, SuccessFactors, Execution is the Difference, BizX Mobile Touchbase, It's time to love work again, SuccessFactors Jam and BadAss SaaS, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany or an SAP affiliate 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.

Disclaimer These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

g201331611644

g201331611644

About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal and external.

2013/Q1

Example text

Emphasized words or phrases in body text, titles of graphics, and tables

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text

Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.



Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

v

About This Handbook

TADM12_1

Icons in Body Text The following icons are used in this handbook. Icon

Meaning For more information, tips, or background

Note or further explanation of previous point Exception or caution Procedures

Indicates that the item is displayed in the instructor's presentation.

vi

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

Contents Course Overview ......................................................... xv Course Goals ...........................................................xv Course Objectives .....................................................xv

Unit 1: Overview and Architecture of SAP Systems ............... 1 Overview of SAP Systems .............................................6 Technical Architecture of SAP Systems............................ 13

Unit 2: Preparing an Installation...................................... 27 Introducing SAPinst................................................... 28 General Preparation for Installation ................................ 36 Additional Preparation for Installation on Windows............... 54 Additional Preparation for Installation on UNIX ................... 64

Unit 3: Installing SAP Solution Manager ........................... 73 Installation of SAP Solution Manager .............................. 75 Installation of a Secondary Application Server.................... 90

Unit 4: Planning an Installation ...................................... 101 Planning the Installation.............................................102

Unit 5: Installation of SAP ECC (AS ABAP)....................... 123 Installation of SAP ECC .............................................126

Unit 6: Installation of SAP XSS (AS Java)......................... 139 Installation of SAP XSS .............................................141

Unit 7: Performing Post-Installation Activities................... 155 Overview of Post-Installation Steps ...............................158 Completing the Installation of SAP Enhancement Packages 6 for SAP ERP 6.0 .....................................................167 SAP License, Online Documentation, Remote Connection to SAP Support ............................................................173 Initial Configuration for an AS ABAP based SAP System ......192 Initial Configuration of an AS Java based SAP System ........221 Appendix: Installation of Standalone SAP Gateway ............229

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

vii

Contents

TADM12_1

Unit 8: Installation of SAP GUI....................................... 243 Optional: Installation of SAP GUI for Windows and SAP GUI for Java ................................................................244 Optional: Installation and Usage of SAP GUI Installation Server..............................................................255

Unit 9: Patching SAP Systems....................................... 271 Software components of SAP systems that can be patched...275 Patching SAP Solution Manager 7.1, Initial Shipment Stack...278 Patching SAP Systems..............................................306 SAP Notes and SAP Support Packages ..........................322 Preparation for Software Maintenance............................331 Support Package Manager (SPAM) and Software Update Manager (SUM) ..................................................357 Applying SAP Support Packages ..................................367 Java Support Packages, Stacks and Patches ...................383 Importing Corrections with SUM for AS Java ....................389 Appendix: Importing Corrections with JSPM .....................404 SAP Enhancement Packages ......................................416

Unit 10: Output Management......................................... 427 Configuring Printers in AS ABAP ..................................429 Concept of Logical Spool Servers .................................455 Managing Spool Requests..........................................467 Printing Assistant for Landscapes (PAL)..........................476

Unit 11: Scheduling Background Tasks ........................... 501 Fundamentals of Background Processing ........................503 Time-Based Scheduling of Jobs ...................................517 Event-Based Scheduling of Jobs ..................................531 Background Processing: Further Topics ..........................543 Job Scheduling with SAP Central Process Scheduling by Redwood ..........................................................561 Appendix: Job Management .......................................583

Unit 12: SAPconnect and SMTP ..................................... 591 Communication with SAPconnect .................................592 Communication Using SMTP.......................................600

Glossary................................................................... 635 Index ....................................................................... 639

viii

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

Course Overview TADM12 complements the knowledge and skills gained in TADM10. Courses TADM10 and TADM12 are largely independent of the type of operating system and database technology. Like the other TADM courses, TADM12 comprises several individual courses (or parts thereof), which are arranged here in a way that will enable you to gain the knowledge you require as an SAP Technology Consultant as efficiently as possible. Week 1 of course TADM12 is based on content taken from the following courses: 1. 2. 3. 4. 5.

ADM110 ADM800 ADM100 ADM102 - updated exclusively for TADM12 TADM12 also contains elements that are not part of any other training course (2 lessons in Unit 9)

Week 2 of course TADM12 is based on content taken from the following courses: 1. 2. 3.

ADM325 ADM103 ADM900/GRC100 Caution: Special note on the schedule/flow of activities in this part of your education track. The first week of TADM12 is a challenge to your wits, you will learn more than you thought. In its first half, the training material describes, in logical sequence, all necessary steps for the planning and execution of SAP system installations and post-installation activities. During the installation and patch activities you will encounter lengthy periods of system activity without required input from your part. Those “non-interactive” installation times will be used for covering other topics contained in this training handbook. Therefore, the actual sequence in which the training material will be covered will be different from the logical sequence of the units in this training handbook.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

ix

Contents

TADM12_1

We do this to use otherwise long periods of “non-activity” for passing on knowledge to you. After this weeks training, for your personal rehearsal, it will help you to work through the training material in its original, logical order. Please take some minutes to take note of the following. During TADM12, first week, your tasks will include the installation of several SAP systems: 1. 2. 3.

S00, an SAP MaxDB-based SAP Solution Manager 7.1 system E00, an Sybase ASE-based SAP ECC 6.06 (-ready) system X00, an SAP MaxDB-based SAP XSS system

In addition to that you will learn (among several other tasks): 1. 2. 3.

How to use the Printing Assistant for Landscapes (PAL) to manage printer definitions for several SAP systems from one central SAP system How to use SAP Central Process Scheduling (SAP CPS) to define and trigger jobs in remote SAP systems, using an AS Java-based application How to send SMTP-based e-mails from an SAP system to an external mail infrastructure

Those latter three tasks require some special setup in the SAP systems in which you would like to execute them. To let you configure that setup within the “own-installed” SAP systems would be very time-consuming and is not possible within this week. Therefore, the setup you will be using for this weeks training looks somewhat advanced. The server that you will be using hosts initially (start of the training week) several SAP systems, as follows: 1. 2. 3. 4. 5. 6. 7. 8.

x

DCC, an SAP MaxDB-based SAP ECC 6.06 (-ready) system, preconfigured for the tasks in units 10, 11 and 12. QCC, an SAP MaxDB-based SAP ECC 6.06 (-ready) system, preconfigured for the tasks in units 10, 11 and 12. PCC, an SAP MaxDB-based SAP ECC 6.06 (-ready) system, preconfigured for the tasks in units 10. PSM, an SAP MaxDB-based SAP Solution Manager 7.1 system, preconfigured for the tasks in units 10 and 11. DEP, an SAP MaxDB-based SAP NetWeaver Portal 7.31 system, not required during TADM12, first week. QEP, an SAP MaxDB-based SAP NetWeaver Portal 7.31 system, not required during TADM12, first week. PEP, an SAP MaxDB-based SAP NetWeaver Portal 7.31 system, not required during TADM12, first week. NDI, an SAP MaxDB-based SAP NWDI system,

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Contents

9.

not required during TADM12, first week. TRX, an SAP TRex system, not required during TADM12, first week. Note: Before your training starts, your instructor will execute some scripts that prepare all systems listed above, as required for this week of TADM12. Caution: Available disk space will become an issue during the first week of TADM12, unless the following steps are executed. Note: Before you start the installation of the first new SAP system (SID: S00), please follow the procedure that your instructor demonstrates to remove (COMPLETELY) the SAP systems named DEP, QEP, PEP and NDI (including their corresponding databases and file system structures). Those instructions will include the script-based full shutdown of all existing SAP systems (including the databases) on your training server. Note: After the successfully finished installation of the first SAP system (S00), you will follow the advice of your instructor to remove the then no longer required Installation media to free up disk space, take care not to delete files that you will need later on. This is described at the start of Unit 5. Caution: During the long-running non-interactive phases of the installation/patch procedures, your instructor will cover material from several units and you start using the already available SAP ECC systems (DCC) to cover some content - e.g. - lessons 1 to 3 from unit 10 and lessons 1 to 4 from unit 11. This will require the startup of SAP system DCC, while in parallel some non-interactive installation steps are executed on your hardware as described at the start of Unit 5. The systems DCC, QCC, PCC and PSM are updated and technically configured for Units 10, 11 and 12. Theoretically, you could reach this state of configuration with your own-installed SAP systems as well, but this would require significant time and more knowledge than is the scope of this weeks training. Lessons 4 of unit 10, 5 of unit 11 and unit 12 require the startup of additional SAP systems (QCC, PCC, PSM) and should be executed without parallel installation or patch processes running. This schedule requires quick-thinking from you - as do real-life projects that you will encounter as an SAP Technology Consultant. So, take the challenge!

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

xi

Contents

TADM12_1

Sequence of installation-related activities - Schedule Unit number

Remarks

Unit 2: Preparing an Installation

Lesson: General Preparation for Installation, Execute Exercise 1, using the OS-user “TADM12”. Consider the changes to Exercise 1 given at the start of Unit 2.

Unit 3: Installing SAP Solution Manager

Lesson: Installation of SAP Solution Manager, Execute Exercise 3, using the OS-user “TADM12”. Consider the changes to Exercise 3 given at the start of Unit 3. –> Take care NOT to run two installation procedures at the same time on the same server Take care NOT to run two installation procedures at the same time on the same server Download SAP Note. Enter the SAP Note number and choose Execute.

Check the downloaded SAP Note. a)

Select the SAP Note and choose the Check SAP Note button. You can find the SAP Note in the New folder. Confirm the popup with Continue.

Task 2: Implement the downloaded SAP Note Implement the downloaded SAP Note with the SAP Note Assistant. 1.

Implement the SAP Note. a)

Select the SAP Note and use the Set Processing Status button to set the processing status to In Processing.

b)

Select the SAP Note and choose the Implement SAP Note button. You can find the SAP Note in the In Processing folder. Confirm that you have read the SAP Note with Yes.

c)

Confirm the popup about the repairs with Continue. Press the Create Request button in the Prompt for transportable Workbench request popup. Enter a short description for the transport request and create the transport request by choosing the Save button. Press Continue to confirm the Prompt for transportable Workbench request popup.

d)

Confirm the Confirm Changes popup with Continue. Activate any inactive items by confirming the Inactive Objects for ... popup with Continue.

Continued on next page

328

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: SAP Notes and SAP Support Packages

2.

2013/Q1

Complete the SAP Note implementation. a)

The SAP Note is implemented now. If you are satisfied with the result in the DCC system, select the SAP Note and use the Set Processing Status button to set the processing status to Completed.

b)

The next steps would be to release the corresponding transport request via transaction SE09 in the DCC system and to import the transport request into the QCC system. Here it would be tested. After a positive test result the transport request can be imported into the PCC system. Imports are done via transaction STMS. But transporting and testing is not part of this exercise.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

329

Unit 9: Patching SAP Systems

TADM12_1

Lesson Summary You should now be able to: • Describe the concept of SAP Notes and SAP Support Packages

330

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

Lesson: Preparation for Software Maintenance Lesson Overview This lesson discusses the use of the SAP Solution Manager – Maintenance Optimizer (MOpz) to request Support Packages within a maintenance transaction To implement Support Packages into an SAP system this system must have installed a valid maintenance certificate. How to ensure that this is present in the target system is explained in the second section.

Lesson Objectives After completing this lesson, you will be able to: • • •

Explain the functions of the Maintenance Optimizer (MOpz) Describe and execute a maintenance transaction Explain the concept of maintenance certificates

Business Example You want to import Support Packages into your SAP system. You want to request these with the help of your Solution Manager

Preparing Software Maintenance In 2003, the SAP Support Package strategy was extended for certain product versions to Support Package Stacks (SP Stacks). The new strategy supports the actual way in which the majority of customers apply Support Packages (SPs). Quality and service can be further improved and therefore total cost of ownership can be reduced. The customer has a complex system landscape with different systems, software products, versions, and components installed. SAP offers different Support Packages, Stacks, and Enhancement Packages for maintenance. Maintenance Optimizer guides you through the procedure for planning and downloading SAP support packages and patches for your systems.

Why Maintenance Optimizer (MOpz) Maintenance Optimizer in SAP Solution Manager is the central point of access for all maintenance activities

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

331

Unit 9: Patching SAP Systems

TADM12_1

Figure 166: Why Maintenance Optimizer

It powerfully supports the installation of updates and upgrades and completely manages the maintenance activities for your whole solution, centrally accessible from inside SAP Solution Manager. It controls the maintenance activities for your entire SAP solution, centrally accessible from the SAP Solution Manager. The software maintenance is supported for all SAP product releases and automatically calculates all the files required for maintenance operation, confirm the file selection and adds them automatically to the download basket of the registered S-user.

Features and Benefits of Maintenacne Optimizer (MOpz) The following functions (calculation of the required files) the MOPz have: • • • • •

332

Installation of Support Packages (SPs) Installation of Support Package Stacks (SPS) Installation of SAP ERP HCM Legal Change Packages Installation of Enhancement Packages Upgrade of SAP Solutions

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

MOpz offers you the following benefits: • • • • • •

Seamless software maintenance procedure increases transparency and traceability of software changes Automatic delta calculation of all relevant maintenance files Installed add-ons on the system are supported and automatically included in the maintenance (as of SAP NetWeaver 7:02 + 7.3) For Java systems the existing Java patches for the software components are detected and added to the selection. Detection of landscape dependencies. Maintenance Optimizer can also calculate necessary updates for connected systems Integration of application logs and traces. Generates system-dependent XML stack files for maintenance

Prerequisites for using the Maintenance Optimizer (MOpz) All SAP systems that are part of the system landscape of the customer in SAP Solution Manager registered. With the Maintenance Optimizer (MOpz) as a functional part of the SAP Solution Manager, this information can then be processed

Figure 167: Prerequisites to start the maintenance transaction

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

333

Unit 9: Patching SAP Systems

TADM12_1

To perform a maintenance transaction, which then selects the required support packages, the following steps are required: 1.

2.

3.

4. 5.

To use the baseline scenario of SAP Solution Manager (which includes the Maintenance Optimizer is one), the following configuration scenarios to succeed: The System Preparation makes settings that are required for the configuration of SAP Solution Manager. In the basic configuration, all required steps for be able to use the baseline scenario in the SAP Solution Manager are performed. This is done in the SAP Solution Manager system with the transaction SOLMAN_SETUP In the configuration of managed systems you connect managed systems with SAP Solution Manager. You must run this scenario for each managed system separately. In this configuration scenario you define, among other things, the product version of the system to be managed. They also specify landscape pattern. It defines whether a technical system is closely associated with one product system (= sidecar) or more product systems (= hub). Thus, the Maintenance Optimizer recognizes the system dependencies, and the maintenance transaction into account. These configuration steps are performed also in the SAP Solution Manager system with the transaction SOLMAN_SETUP. Thus a system user in the SAP Solution Manager system could perform a maintenance transaction he must have an S-User in SAP Support Portal. This S-User needs the following additional authorization objects: Activity: Execute Maintenance Optimizer Authorization: SWCATALOG: Order Software in Software Catalog S-users are managed in SAP Support Portal at the URL http://service.sap.com/user-admin. To connect the S-user with the system user within the SAP Solution Manager System the transaction AISUSER is used. The selected support packages can be stored in the download basket of the S-user. This Download Basket needs to install locally. For details, please refer to SAP Note 330793: Download patches. The download basket can be downloaded and configured using the URL: http://service.sap.com/download-basket → Get Download Basket. Please note the installation instructions. Then the support packages will be automatically approved during the maintenance transaction so that they can be downloaded with the Download Manager from the SAP Service Marketplace. Optionally they can be downloaded via the SLM functionality (Software Lifecycle Manager)

For more details about the functionality of the Maintenance Optimizer to visit his website: http://service.sap.com/mopz

334

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

Perform Maintenance Transaction To start the maintenance transaction calls the transaction SM_WORKCENTER within the SAP Solution Manager System

Figure 168: Starting the Maintenance Optimizer (MOPz) transaction

1.

2. 3.

After calling the transaction SM_WORKCENTER navigate to Work Center Change Management. To use the function you need a system user with the SAP composite role SAP_MAINT_ADMIN_COMP. This allows the system user to use the work center, as well as maintenance transaction and to start to work. For further details please refer to the Security Guide for SAP Solution Manager. This is on the side http://serivce.sap.com/instguides → SAP Solution Manager → Release. To work with existing maintenance transactions, which have been created by your system user navigate to Maintenance Optimizer in the navigation tree on the left hand side. To start a new maintenance transactions choose New Maintenance transaction in the typical tasks section. In the window that opens, select the product version you want to maintain. Also please assign a priority for your maintenance transaction and enter a meaningful description. Hint: The solution is to specify is optional

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

335

Unit 9: Patching SAP Systems

4.

TADM12_1

Then in the underlying table all systems that match the selection appears. Here select all the systems that you want to maintain with the selection button in front of the system ID. Confirm your selection with the button Next Hint: Usually you want to maintain all systems with the same product version (meaning DEV, QAS and PRD system). So you would select all systems of the same product version as they belong together within the system landscape. Caution: To find all systems with the same product release this information has to be maintained correctly within the LMDB (Landscape Management Database) of the SAP Solution Manager System. For further maintenance transaction also all other information needs to be set up correctly (for example, product instances installed add-on products, etc The function Landscape Verification will help you to find errors regarding the setup of your systems within the LMDB and fix them. In the end, the system settings in your LMDB should find a corresponding entry in the PPMS (Product and Production Management System) at SAP to be able to download all needed files for the maintenance. See also: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Maintenance+of+Product+in+the+System+Landscape and the Maintenance Planning Guide for your SAP Solution Manager Version which could be found on this page. Hint: Hinweis: To check whether the definition in your LMDB is correct, you can use the link [Display System in Product System Editor] as shown in the picture Hint: More information about LMDB and Landscape Verification you will receive in the course SM100.

In the course of maintenance, all of the files for this product version relevant are selected, provided in the download basket of S-user and confirmed. You see its number top right of the picture On the next screen, you specify the file selection mode.

336

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

Figure 169: MOPz – Select Files

The recommendation is to calculate the required files for the maintenance transaction automatically. Radio button: Calculate Files Automatically (Recommended) If you want to download individual files or support packages you can do this with the radio button Select Files Manually. Confirm your selection with Next Caution: The calculation of the required files for the maintenance can only work if the system settings in the LMDB for these systems are maintained correctly. See also: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Maintenance+of+Product+in+the+System+Landscape as well as the Maintenance Planning Guide for your SAP Solution Manager Version which could be found on this page

Figure 170: MOPZ Update Options

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

337

Unit 9: Patching SAP Systems

TADM12_1

As shown in the text of the picture: Here you found all possible maintenance options which are available for the selected Product Version. Which means: maintenance (import Support Packages Support Packages or stacks), and upgrade and/or enhancement package installation.

Figure 171: MOPZ Choose Stack

Within the step Choose Stack you select a Target stack for your product version and confirm with the Continue button. Usually you would select the highest available Support Package Stack (SPS).

Figure 172: MOPZ Choose Add-On Products

338

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

At this point already installed add-ons are automatically detected and selected to update (as is seen in the picture). In addition, new add-on products available for your product version could be selected manually if available

Figure 173: MOPZ Select OS/DB dependent files

In this step you have to manually select the correct kernel files for your SAP system. Note that they may have installed instances on different operating systems. Hint: You can read this information for each instance using the transaction SM51. Then choose: Goto → Server → Information → Release Information. If you are choosing your SAP kernel the system automatically selected the appropriate database-independent kernel. Also choose the SAP IGS kernel and optional the SAP HOST AGENT.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

339

Unit 9: Patching SAP Systems

TADM12_1

Figure 174: MOPZ Select Stack-Independent files

In step stack independent files make sure that in the case of an ABAP system, the entry SAP SPAM/SAINT update is selected. This should be done automatically. Please also note that stack independent files are not deployed automatically. You need to import them manually.

Figure 175: MOPZ Select Stack-dependent files

340

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

The next step, called Select Stack-Dependent Files check in the field File name if all check boxes have been selected automatically. Hint: It’s not recommended to deselect any files. If non-ABAP components are selected (often these are Java software components) here the optional capability to select the latest patches for the Java support packages automatically add into the download basket. Go by doing as follows: 1.

2. 3.

4.

Press the button Add Java patches. This means that for all these software components, a check will be performed automatically if there are patches to these Java software components. With the radio button Select All you select all found Java patches. This will include all these java patches to your download basket. Then select the radio button Include Selected Java patches to stack xml. Thus, the patches are also written to the XML file to be automatically deployed later when performing the maintenance itself on the system(s). To confirm the selection press OK.. Hint: Note the warning on the selection screen.

To move to the next step, press next

Figure 176: MOPZ Confirm selection and download files

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

341

Unit 9: Patching SAP Systems

TADM12_1

In the step Confirm selection you see the download tool which is used to download the selected files within a later step. If no Software Lifecycle Manager (SLM) has been installed and configured, which can automatically download these files, the download basket of the S-user which is shown on top is selected here. Press Next to proceed to the next step Download Files. Now download these files using your local installation of the download basket. The SAP Solution Manager has confirmed the files in the download basket of the used S-user already. The downloaded files must then manually put to the appropriate directories of the SAP system(s) which have been selected in the first step In addition, the SAP Solution Manager produced a txt-file as well as a xml file for each system and store them into the file system of the SAP Solution Manager itself: \\ \ sapmnt \ trans_ \ eps \ in. These files must also be distributed to the appropriate directories of the SAP system(s). Only then you can start the implementation of these file with the appropriate (SPAM, SAINT, JSPM, SUM ..). Caution: It is not the job of the Maintenance Optimizer to deploy the files. This must be done with the appropriate tools on the satellite systems.

Figure 177: MOPZ Implement & End Maintenance

After the files have been successfully implemented in the selected systems, you can set the implementing status within the step implement. Here it is possible to provide each system with the current status (New, In Progress, and Complete) Hint: You can only continue to when the status of all listed systems is set to Completed. After this has been done you need to press save to go to the next step.

342

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

In the final step End Maintenance you can finish maintenance transaction. Please note that you can then no longer change the maintenance transaction. Hint: For example, to import support packages, it is recommended to create a maintenance transaction with the Maintenance Optimizer. This maintenance transaction is used firstly to calculate a consistent combination of support packages for the selected systems in the system landscape. On the other hand the files need to be approved before downloading. This is part of the maintenance transaction, too. Caution: All support packages for SAP NetWeaver 7.0 (or higher) based systems need to be requested using the Maintenance Optimizer. In each step, you get more tabs with the specified options: • • • •

use tab Systems to view the target constellation for your systems use tab Log to display the accumulated warnings and errors within tab stack files you can manually download the generated XML files to update the managed system within tab documentation you can get general information about enhancement packages the Maintenance Optimizer

For more information about Maintenance Optimizer (MOpz), please visit: http://servie.sap.com/mopz For more information about configuration of the SAP Solution Manager and connecting the satellite systems can be found in the SAP training SM100

Maintenance Certificates A maintenance certificate enables the SAP software logistics tools (for example, SPAM, SAINT, JSPM and SUM) to identify the system to be maintained and to determine the extent of maintenance required. It is also used to ensure that only customers with a valid maintenance contract can perform the relevant maintenance transactions. Hint: As of January 2009, the software logistics tools can only maintain a system if a valid maintenance certificate is available As of SPAM/SAINT Version 7.00/0034, a valid maintenance certificate is a prerequisite for importing Support Packages. Java Support Packages (these are imported with JSPM) in the near future, a maintenance certificate may be required. Currently (as of end of 2012) the system only shows a warning.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

343

Unit 9: Patching SAP Systems

TADM12_1

Similarly behaves the Software Update Manager (SUM), which depends on the selected target release for upgrades (= new release) updates (= installation of enhancement packages), as well as for the import of support packages is responsible. For further information please refer to the following information: SAP Note 1236587: JSPM/SUM - JSPM/SUM - No valid maintenance certificate found SAP Recommends definitely also for Java systems to import a valid maintenance certificate. Hint: Basically (as of end of 2012) all SAP products based on SAP NetWeaver AS ABAP 7.0 and higher require a maintenance certificate. (Except SAP BusinessObjects Products) Maintenance certificates are valid for a period of three months, after which time they must be renewed. To keep costs to a minimum, a SAP Solution Manager system can be used to automate the process of generating maintenance certificates. For this purpose, a SAP Solution Manager system must have release 7.0 and Support Package Stack level 16 or higher (recommended: 23). Hint: The SAP Solution Manager system requires both a connection to the SAP Service Marketplace and the SAP system to be patched. Moreover, the basic configuration of the SAP Solution Manager system to be completed and the configuration of managed systems must be carried out. Hint: When performing a release upgrade or importing SAP enhancement packages, Support Packages are incorporated into the update process. A maintenance certificate is usually not required here.

Automatic distribution of maintenance certificates (prerequisites and implementation) The following are the prerequisites are discussed that must be met for the automatic distribution of maintenance certificates.

344

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

Figure 178: Automatic distribution of maintenance certificates (prerequisites)

1.

2. 3.

4.

To ensure the automatic distribution of maintenance certificates for ABAP systems from the perspective of the SAP Solution Manager SAP Solution Manager at least version 7.0 SP 16 is required. To the automatic distribution of maintenance certificates for Java systems needs at least the SAP Solution Manager Version 7.0 SP 23. Through the basic configuration of the SAP Solution Manager System and the configuration of managed systems the target system will automatically receive an 18-digit number system. These can be found in the transaction LMDB in the system overview of the SAP Solution Manager System. Also through the basic configuration SAP Solution Manager, a background job named REFRESH_ADMIN_DATA_FROM_SUPPORT is scheduled to ensure that the maintenance certificates are requested in the SAP Support Portal. This also guarantee that the maintenance certificates further processed in the SAP Solution Manager System.

In the following figure you get an overview how the automatic distribution of maintenance certificates has been implemented technically

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

345

Unit 9: Patching SAP Systems

TADM12_1

Figure 179: Maintenance Certificate – Automatic Distribution

1.

2. 3. 4.

The SAP Solution Manager system requests a maintenance certificate for all managed systems, where the maintenance certificate is expiring. (6 weeks before expiring date) The maintenance certificates are generated in the SAP Global Support Backbone. The SAP Solution Manager system contains the maintenance certificates the next time a connection is established (every 24 hours). The managed systems receive the maintenance certificates from the SAP Solution Manager System.

For Troubleshooting see SAP Note 1280664: Distribution of maintenance certificates: Troubleshooting

Status check of maintenance certificates in the connected systems To see the status of the managed systems in SAP Solution Manager you open the transaction SM_WORKCENTER there. Navigate to the Change Management work center. Here you can view the status of all connected systems with respect to a valid contract, licenses and maintenance certificates.

346

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

Figure 180: Status of connected systems with respect to the maintenance certificates

Within the field Status of automatic distribution can be inferred that the automatic distribution is enabled for this system. This usually happens automatically when the SAP system is connected to the SAP Solution Manager (transaction SOLMAN_SETUP). If this is not the case, the automatic distribution will be activated with the push button automatic distribution. If the field maintenance validity has a red status, this means that this system do not have a valid contract at SAP. The fields for the connected system have the following meaning: Status

License

Maintenance certificate

Red

Valid to have been exceeded.

Valid to have been exceeded. A system check has rated the maintenance Certificate as nonexistent

Yellow

Valid to will be reached in less than 30 days.

Valid to will be reached in less than 30 days. A system check would still rate the maintenance certificate as existing.

Green

License is valid.

Maintenance certificate is installed and valid

Gray

No data. Rating is not possible. No data. Rating is not possible.

The following table shows the status of the system within the SAP Solution Manager and if the SAP Solution Manager has received a license as well as a maintenance certificate from the SAP global support backbone.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

347

Unit 9: Patching SAP Systems

TADM12_1

Status

Received License

Received Maintenance certificate

Red

Valid to have been exceeded.

Valid to have been exceeded. A system check has rated the maintenance Certificate as nonexistent

Yellow

Valid to will be reached Valid to will be reached in less than in less than 30 days. 30 days. A system check would still rate the maintenance certificate as existing.

Green

License is valid.

Maintenance certificate has been received and is valid

Gray

No data. Rating is not possible.

No data. Rating is not possible.

In the details of the selected system can see the following information: • •

The data received from the SAP Support Backbone The data received from the connected system

Respectively with respect to key number, hardware key and the exact expiration date as well as the type (license or maintenance certificate) Hint: Using the button download licenses you can get licenses and maintenance certificates as a download file. This file you could implement manually using the transaction SLICENSE. This is useful when the communication between SAP Solution Manager and the managed system is disturbed. For more information, visit http://service.sap.com/maintenancecertificate

Manual download and import of maintenance certificates If connections between the SAP Solution Manager and the managed system, for example, due to security restrictions, not allowed, or if there are problems in the automatic distribution of maintenance certificates, the maintenance certificate still could requested manually via the SAP Service Marketplace and downloaded.

348

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

Figure 181: Manual download of the maintenance certificate

Log in with your S-user on the page http://service.sap.com/licensekey and proceeds according to the figure. The import of the downloaded file into an ABAP system will be done with the Transaction SLICENSE. In Java systems it’s installed on the function of the Licensing Adapter. Learn more in the course SM100.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

349

Unit 9: Patching SAP Systems

350

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM12_1

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

Exercise 12: Execute a Maintenance Transaction Exercise Objectives After completing this exercise, you will be able to: • Create and execute a maintenance transaction for Support Packages in the SAP Solution Manager system.

Business Example You want to update the SAP systems in your company to the latest Support Package level. You want to use a maintenance transaction in the SAP Solution Manager system to determine the Support Packages.

Task: Create and execute a maintenance transaction for Support Packages in the SAP Solution Manager System. 1.

Create and execute a maintenance transaction for Support Packages in the SAP Solution Manager System. Caution: This tutorial was written for both ABAP and Java-based SAP systems and is marked in the appropriate places. Please choose depending on what training you are the Corresponding tasks. Hint: If, caused by system configuration issues are errors, please make a new group of 2 separate groups and select the product version of the SAP Solution Manager.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

351

Unit 9: Patching SAP Systems

TADM12_1

Solution 12: Execute a Maintenance Transaction Task: Create and execute a maintenance transaction for Support Packages in the SAP Solution Manager System. 1.

Create and execute a maintenance transaction for Support Packages in the SAP Solution Manager System. Caution: This tutorial was written for both ABAP and Java-based SAP systems and is marked in the appropriate places. Please choose depending on what training you are the Corresponding tasks. Hint: If, caused by system configuration issues are errors, please make a new group of 2 separate groups and select the product version of the SAP Solution Manager. a)

Log on to the SAP Solution Manager System. User: - Password:

b)

Start the transaction SM_WORKCENTER

c)

Navigate to the work center Change Management

d)

In the area Common Tasks choose New Maintenance Transaction.

e)

In the window that opens called Maintenance Optimizer Transaction select the product version of your SAP satellites system. Caution: ABAP Courses using the product version SAP ERP 6.0 Java Courses the product version Enterprise Portal.

f)

The table shows the results of your choice under then choose either the SAP ECC system , or the SAP Enterprise Portal system which is assigned to your group.

g)

Press Continue

h)

In Step Select Files choose in the option Calculate Files Automatically – Recommended in the area Choose File Selection Mode. Press Continue

Continued on next page

352

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

i)

This point may take some time to complete because it’s now calculated, which update’s and upgrades are available for the selected product version Hint: This is also depending on which load is present at this moment to the OSS system in the SAP. Maintenance transaction remembers the step you currently working with. So you could close the window and then at this point continuing the maintenance operation

j)

Choose the option Maintenance and confirm your selection with Continue.

k)

The next step is to choose the highest Support Package Stack for your product version and confirm it with the button Continue

l)

The next step is to confirm your mayor target (this point may take some time to complete). Here you can see a summary on which stage your product version will be, after you perform the deployment to this product version. Confirm this with Continue

m)

The next step shows you the available add-on products offered for your product version. Either these already installed and there is a new version for this component (if this is the case, they are already selected) or they are optionally selectable because they are not yet installed. This point may take some time to complete. If they are new Add-Ons available for your product version do not select it and confirm with Continue.

n)

In the step Select DB / OS dependent files please choose the following: In the File Name column to follow this path: → Windows on X64 64-bit → Max DB → SAP Kernel 7.xx 64-bit Unicode, select this kernel. Automatically the correct Database Independent kernel is chosen. In addition, select at least another Windows on x64 64-bit from the SAP IGS 7.xx kernel. In order to avoid later a warning also choose the SAP HOST AGENT 7:xx Hint: You can find this information in the ABAP satellite system. Call transaction SM51 and choose: Goto → Server Name → Information → Release Notes Hint: Whether you choose the SAP Host Agent file or not depends on your individual kernel release strategy for the SAP Host Agent. Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

353

Unit 9: Patching SAP Systems

TADM12_1

o)

Confirm your selection with Continue.

p)

In the step select stack independent files make sure that in the case of an ABAP system, the entry SAP SPAM / SAINT update is selected and click on Continue

q)

In the step Select Stack dependent files. Check if in field File Name all check boxes are selected. Here is not recommended to deselect any files. If you are in ABAP training, confirm with Continue Hint: If NON-ABAP components are selected (this means in Java trainings) here it’s possible to select the latest patches for the Java support packages automatically and add them into the download basket. Press the button Add Java patches. This means that for all these software components, a check will be performed automatically if there are patches to these Java software components. With the radio button Select All you select all found Java patches. This will include all these java patches to your download basket. Then select the radio button Include Selected Java patches to stack xml. Thus, the patches are also written to the XML file to be automatically deployed later when performing the maintenance itself on the system(s). To confirm the selection press OK. To move to the next step, press Continue. Hint: Note the warning in the selection screen.

r)

In Step Confirm Selection the radio button Download Basket should be selected already. Press Continue.

s)

Within step Download Files all files should be downloaded and distributed to the appropriate directories of the SAP systems. In addition, the SAP Solution Manager System produced a .txt and an xml file for all systems which was selected in the first step. The SAP Solution Manager system store this files into the directory \\ \ sapmnt \ trans_ \ eps \. These must also be distributed to the appropriate directories of the SAP systems. Only then the implementation of these files can take place. Caution: It is not the job of the Maintenance Optimizer to deploy the files. This must be done with the appropriate tools on the satellite systems.

Continued on next page

354

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Preparation for Software Maintenance

Caution: In the training system these files are NOT used for the implementation. Therefore a download is NOT necessary. t)

Press Continue

u)

In the next step (Implement) you can only continue to when the status of all listed systems is set to Completed. After this has been done you need to press save to go to the next step. Therefore select in the field Status of Implementation the option Completed and press save. Hint: This, of course, you would do so only if the deployment was completed successfully to all systems!

2013/Q1

v)

Press Continue

w)

In the final step finish the maintenance transaction. Please note that you can then no longer change to the maintenance transaction. Press Complete Transaction.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

355

Unit 9: Patching SAP Systems

TADM12_1

Lesson Summary You should now be able to: • Explain the functions of the Maintenance Optimizer (MOpz) • Describe and execute a maintenance transaction • Explain the concept of maintenance certificates

356

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Support Package Manager (SPAM) and Software Update Manager (SUM)

Lesson: Support Package Manager (SPAM) and Software Update Manager (SUM) Lesson Overview In this lesson you will be introduced to the Support Package Manager. You will learn what a SPAM/SAINT update is and how to apply it. A SPAM/SAINT update may be required before you can import new SAP Support Packages.

Lesson Objectives After completing this lesson, you will be able to: •

Explain the use of the Support Package Manager and import a SPAM/SAINT update.

Business Example Functional enhancements to an SAP system can affect not only the applications, but also the actual tools that you use to import the SAP Support Packages.

SPAM/SAINT Update Most standard software components of an SAP system are installed during the initial installation process. Additional software components can be imported afterwards, if required. These are referred to as add-ons. Examples of add-ons are plug-ins or industry-specific components (industry solutions) that are not part of the standard installation. These add-ons are imported with the help of the Add-On Installation Tool (transaction SAINT). The Add-On Installation Tool and add-ons themselves will not be dealt with in detail in this lesson. The tool for importing SAP Support Packages is the Support Package Manager, transaction SPAM.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

357

Unit 9: Patching SAP Systems

TADM12_1

Figure 182: Support Package Manager: SPAM/SAINT Update

The Support Package Manager offers the following functions: You can use the Support Package Manager (transaction SPAM) to import individual SAP Support Packages for individual components. You can also import several consecutive SAP Support Packages for a software component. Furthermore, you can import several SAP Support Packages for various software components (a vector). If you want to import such a vector of SAP Support Packages, you can either switch to All Components in the selection dialog box for the queue or you can choose Extras → Settings → Define Queue to switch to the vector selection view. Hint: You should always apply a complete SAP Support Package Stack in one step, not only SAP Support Packages for one software component. When the Support Package Manager imports SAP Support Packages into the SAP system, it follows a fixed sequence of steps. If the process of implementing the SAP Support Package terminates, processing can be restarted at the break-off point. The process restarts at the point at which it was terminated. A special import procedure keeps downtime to a minimum. (Extras → Settings → Import Queue → Import Mode: Downtime-minimized) The individual phases of the Support Package Manager are grouped into four modules. You can determine the start times of the modules individually. The individual modules can also be scheduled for background processing.

358

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Support Package Manager (SPAM) and Software Update Manager (SUM)

These four modules will be discussed in the next lesson. The Support Package Manager can recognize dependencies between SAP Support Packages and take account of these (but not the side-effects, however). To remain up-to-date and to be able to use the new functions of the Support Package Manager too, you should update the Support Package Manager itself before you import SAP Support Packages. Since transactions SPAM and SAINT are closely related from a technical point of view, a shared patch, the SPAM/SAINT update, is supplied at unregular intervals to upgrade the tools. You can find out the version from the short description of transaction SPAM (for example, SPAM/SAINT update - Version 7.31/0046). Hint: The update for the Support Package Manager (SPAM/SAINT update) is only delivered in German and English. You are therefore recommended to log on in English or German when working with the Support Package Manager. The SPAM/SAINT update is imported using the transaction SPAM. You can only import a SPAM/SAINT update if there are no aborted SAP Support Packages in the SAP system. If there are aborted SAP Support Packages, a dialog box informs you of this. You then have two options: • •

2013/Q1

You first import the complete queue of SAP Support Packages and then the SPAM/SAINT update. You reset the status of the queue, import the SPAM/SAINT update first and then the SAP Support Package queue. You can reset the status of the queue by choosing Extras → Reset status → Queue.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

359

Unit 9: Patching SAP Systems

TADM12_1

Procedure for importing a SPAM/SAINT update: 1.

2.

3. 4. 5.

6.

Check whether the SPAM/SAINT update currently offered on SAP Service Marketplace is newer than the one imported into the SAP system (the SPAM/SAINT version of the SAP system is displayed in the title bar of the Support Package Manager). Download the latest SPAM/SAINT update from SAP Service Marketplace. As part of a maintenance transaction, the Maintenance Optimizer can be used for this purpose. Extract the downloaded file to the transport directory of the relevant SAP system, subdirectory EPS, subdirectory in. Log on to client 000 in the SAP system and call transaction SPAM. Communicate the patch (the SPAM/SAINT update) to the Support Package Manager: SAP Support Package → Load packages → From Application Server. This is a notification for the Support Package Manager and does not import the SPAM/SAINT update. No packages are loaded. And they are not searched for on the application server, but rather on the host, the application server runs on. To import the SPAM/SAINT update, choose SAP Support Package → Import SPAM/SAINT Update.

In a multi-SAP system landscape you have to carry out this import procedure in each SAP system. In a three system landscape, the most practical sequence is development system, quality assurance system, and then production system. Since the SPAM/SAINT update is a full delivery of transactions SPAM and SAINT, you can import the latest available SPAM/SAINT update immediately. For example, for an existing version 7.31/0040, you can directly import version 7.31/0046.

Software Update Manager (SUM) A second possibility to apply SAP Support Packages is to use the Software Update Manager (SUM). The SUM was designed as a tool for upgrading an SAP system and to install SAP enhancement packages. The SUM is a further development of the tools SAPup and SAPehpi. The same as SAPehpi in the past, the SUM can also be used to import SAP Support Packages - without performing an SAP system upgrade or to install an SAP enhancement package. In contrast to the Support Package Manager (SPAM), SUM is not a transaction, but a stand alone tool.

360

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Support Package Manager (SPAM) and Software Update Manager (SUM)

Figure 183: Software Update Manager: Sequence

In November 2012 you can download the newest SUM package from SAP Service Marketplace, Quick Link /swdc -> PatchesSupport Packages and Patches -> A - Z Index -> SL TOOLSET -> SL TOOLSET 1.0 -> Entry by Component -> Software Update Manager (SUM). The steps to start the SUM are as follows: 1. 2. 3. 4. 5.

copy the SUM package to the host of the SAP system, for example into the sapmnt\SYS\ directory extract the SUM package - which will result in around 3500 files start the SUM controller by starting a startup script from the SUM root directory connect via a browser to http://:4239 - now the SUM start page and the SUM front end start log on to the SUM front end

The same as with SPAM, these steps would be performed first on the development system, then on the quality assurance system, then on the productive system. When should SPAM, when should SUM be used to apply SAP Support Packages?

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

361

Unit 9: Patching SAP Systems

TADM12_1

Figure 184: SPAM versus SUM

Note: For SUM for AS ABAP based SAP systems, a stack.xml file created by Maintenance Optimizer - is mandatory to apply SAP Support Packages! As a conclusion you can say: use SPAM in normal cases, use SUM if you have to apply a huge number of SAP Support Packages in a very downtime critical SAP system. Hint: Use SUM if you have to apply a huge number of SAP Support Packages in a very downtime critical SAP system.

362

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Support Package Manager (SPAM) and Software Update Manager (SUM)

Exercise 13: Support Package Manager (SPAM) Exercise Objectives After completing this exercise, you will be able to: • Apply a SPAM/SAINT update

Business Example To apply SAP Support Packages, you often need to first update the tool that you are using for the import. This may be necessary in order to read current attributes from the new SAP Support Package, for example.

Task: Apply a SPAM/SAINT Update Apply a SPAM/SAINT update. Caution: This exercise must be performed by the DCC group first and then by the QCC group. In the first step, a SPAM/SAINT update is applied to the SAP system DCC. After it has been applied successfully, the SPAM/SAINT update is applied to the SAP system QCC. Your instructor will show you the downloaded file you require for the SPAM/SAINT update. 1.

Check the current SPAM/SAINT version in your SAP system.

2.

Extract the file that contains the SPAM/SAINT update at operating system level. This file is located on the ADM share at S:\Maintenance\SPAM_731. Hint: Remember that this step only needs to be performed once for each transport directory.

2013/Q1

3.

Log on to the correct client.

4.

Load the SPAM/SAINT update using transaction SPAM; that is, declare the file to the SAP system.

5.

Apply the SPAM/SAINT update into your SAP system. Note any possible errors.

6.

Check the import process log for errors.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

363

Unit 9: Patching SAP Systems

TADM12_1

Solution 13: Support Package Manager (SPAM) Task: Apply a SPAM/SAINT Update Apply a SPAM/SAINT update. Caution: This exercise must be performed by the DCC group first and then by the QCC group. In the first step, a SPAM/SAINT update is applied to the SAP system DCC. After it has been applied successfully, the SPAM/SAINT update is applied to the SAP system QCC. Your instructor will show you the downloaded file you require for the SPAM/SAINT update. 1.

Check the current SPAM/SAINT version in your SAP system. a)

Call transaction SPAM. The SPAM/SAINT version is displayed in the title bar (for example, “Support Package Manager - Version 7.31/0046).” To see whether SPAM/SAINT updates have already been applied, select the Imported Support Packages radio button and choose Display. The system displays an overview of the previously applied SPAM/SAINT updates, called SAP_OCS (SAP Online Correction System) here. Note: You can also skip individual SPAM/SAINT updates, which means that you can switch directly from version 7.31/0046 to the newest version corresponding to SAP_BASIS release 7.31.

Continued on next page

364

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Support Package Manager (SPAM) and Software Update Manager (SUM)

2.

Extract the file that contains the SPAM/SAINT update at operating system level. This file is located on the ADM share at S:\Maintenance\SPAM_731. Hint: Remember that this step only needs to be performed once for each transport directory. a)

Go to operating system level. Copy the file KD731.CAR to the transport directory (for example, D:\usr\sap\trans). stands for the (latest) version of the SPAM/SAINT update. At operating system level, open a command prompt in the transport directory and use the command sapcar -xvf KD731.SAR to extract the file you have just copied. This extracts the file to the directory \EPS\in. It should now be in D:\usr\sap\trans\EPS\in, for example.

3.

Log on to the correct client. a)

4.

Log on to client 000. You can only apply a SPAM/SAINT update from client 000.

Load the SPAM/SAINT update using transaction SPAM; that is, declare the file to the SAP system. a)

Transaction SPAM: Support Package → Load packages → From Application Server. Confirm the dialog box for the “upload”. See that the SPAM/SAINT update was recognized. Go back to the initial screen of SPAM Hint: Remember that - although the menu path may suggest it - no package is uploaded or applied here, and it is not searched for on the application server, but rather on the host, the application server is running on.

5.

6.

Apply the SPAM/SAINT update into your SAP system. Note any possible errors. a)

In transaction SPAM, choose Support Package → Import SPAM/SAINT Update. Confirm the dialog box to apply. In case the import process terminates due to an error, just restart it with transaction SPAM. A termination is not unusual, because you are patching the tool with itself.

b)

Then call transaction SPAM again.

Check the import process log for errors. a)

2013/Q1

Call transaction SPAM and choose Goto → Import Logs → SPAM/SAINT Update. No errors should be displayed.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

365

Unit 9: Patching SAP Systems

TADM12_1

Lesson Summary You should now be able to: • Explain the use of the Support Package Manager and import a SPAM/SAINT update.

366

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Applying SAP Support Packages

Lesson: Applying SAP Support Packages Lesson Overview In this lesson you will learn how SAP Support Packages are imported into your SAP systems.

Lesson Objectives After completing this lesson, you will be able to: • •

Import SAP Support Packages with transaction SPAM Provide a explanation of the import process for SAP Support Packages

Business Example Applying SAP Support Packages is a task for the SAP system administrator. The new versions of SAP objects in the SAP Support Packages stabilize and extend the functional scope of the SAP system. They are also needed in regard of legal changes.

Applying SAP Support Packages The SAP Support Package Stacks represent combinations of SAP Support Packages recommended by SAP for the respective product version, and you are advised to import these regularly. When importing SAP Support Packages you should observe the instructions for the SAP Support Package Stack and import all the SAP Support Packages of the SAP Support Package Stack in one step, if possible. A kernel patch often is part of the SAP Support Package Stack, too. This should be implemented before you import the SAP Support Packages (not covered in this lesson). If you have installed an SAP enhancement package in your SAP system, you must use the Maintenance Optimizer, as part of SAP Solution Manager, to calculate a SAP Support Package Stack. In any case you should use the Maintenance Optimizer.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

367

Unit 9: Patching SAP Systems

TADM12_1

Figure 185: Applying SAP Support Packages

The procedure for applying SAP Support Packages should be as follows: 1.

2. 3. 4. 5.

6.

368

Create a maintenance transaction in the Solution Manager Maintenance Optimizer. The Maintenance Optimizer calculates the necessary combination of SAP Support Packages (SAP Support Package Stack) for the SAP system you want to patch. You should also make sure you have the latest SPAM/SAINT update applied. The Maintenance Optimizer approves the selected SAP Support Packages for the download, and places them in the download basket for the Download Manager. You can download the required SAP Support Packages from SAP Service Marketplace using the Download Manager. The downloaded files need to be unpacked to the transport directory of the relevant SAP system, subdirectory \EPS\in. Log on to client 000 in the SAP system and call transaction SPAM. The new SAP Support Packages are announced to the Support Package Manager: SAP Support Package → Load Packages → From Application Server. This is simply a notification for the Support Package Manager and does not import the SAP Support Packages. If the compressed files are on the front-end servers host and are smaller than around 10 MB, you can also transfer these files to the application servers host and decompress them directly from the Support Package Manager. Make settings for the import procedure (see below).

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Applying SAP Support Packages

7.

You define the queue for the SAP Support Packages to be imported. This can choose SAP Support Packages for one single software component as well as SAP Support Packages for several components. The Support Package Manager checks the consistency of the queue. The Support Package Manager ensures that only SAP Support Packages that match the SAP system are displayed in the queue. SAP Support Packages that are intended for a different release or a software component that is not installed, or whose predecessor relationships are not fulfilled, do not appear in the queue, even if these have been specified in the SAP system. Hint: You should always apply all SAP Support Packages of an SAP Support Package Stack in only one step, in only one queue!

8. 9. 10. 11. 12.

13.

To import the SAP Support Package queue, choose SAP Support Package → Import Queue. Choose the start conditions for the four import modules (see below). Start the import process. One or two modification adjustments may arise during the import (see below). These must be executed at the specified point. Once the SAP Support Packages have been imported successfully, check the logs: Goto → Import Logs → Queue After the SAP Support Packages have been imported to the development system, the developers can check the objects. After the SAP Support Packages have been imported to the quality assurance system, an acceptance test should be carried out by subject matter specialists. You can then import the SAP Support Packages to the production system. If the import has been completed successfully, the imported queue has to be confirmed in the relevant SAP system: SAP Support Package → Confirm

There are a number of possible settings for the import procedure (Extras → Settings). Under Import Queue → Scenario, you can define the actions to be carried out during the import: •

•

Standard: The standard scenario is used to import SAP Support Packages completely; all steps are performed. The import mode Downtime-minimized can be used here (see below). Test: You can use the test scenario to observe whether a modification adjustment is required before you import the SAP Support Package, or to check whether conflicts occur that must be resolved before the import. No data or objects are imported to the SAP system during the test scenario. There is no test scenario for SPAM/SAINT updates. The selection you make here is ignored when importing a SPAM/SAINT update.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

369

Unit 9: Patching SAP Systems

TADM12_1

There are many steps (phases) to the import procedure. These are subdivided into four modules. • • •

The modules can be executed individually in the correct sequence. The modules can be started in a background process. The start time of the module can be controlled flexibly.

The four modules execute the following steps: 1.

2.

3.

Preparation module: All the preparatory steps and check steps (such as the test import, add-on conflict check) are performed in this module. The module can run during production operation. Once the preparation module has been completed, you still have the option of resetting or deleting the queue. If you continue with the Import 1 module, data is changed on the database and the queue can no longer be reset or deleted. Import 1 module: In this module, the objects of the SAP Support Packages are imported. If the import procedure is carried out in Downtime-minimized mode, programs are inactively imported. The runtime system cannot “see” these changes yet. Dictionary objects are inactive when imported, independent of the import mode. The manual modification adjustment of the Dictionary objects is performed at the end of this module, if required (SPDD modification adjustment). If you can guarantee that no manual changes are required for the SAP system and no transports are imported into the SAP system during this time, up to here this module can run during production operation. Import 2 module: Now the dictionary objects are activated. The remaining import steps are carried out in this module. If you use the Downtime-minimized import mode, inactive programs are activated in this module as well. During this module production operation is not permitted to avoid inconsistencies and data loss. As a result, this module always means SAP system downtime. Hint: The SAP system administrator is responsible for achieving the downtime window: log off all users from the SAP system, stop all background processing, stop all RFC communication to the SAP system. These actions are not performed by SPAM automatically!

4.

370

Clean Up module: In this module, all the clean-up steps are processed. The modification adjustment of the non-Dictionary repository objects is performed in this module (SPAU modification adjustment). When all modifications have been adjusted, production operation can continue.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Applying SAP Support Packages

Figure 186: Import Mode Downtime-minimized

Caution: The SAP system administrator must manage the downtime manually! This means, that the administrator is responsible for locking the SAP system, logging og the users, stopping batch processing, invalidating RFC connections to the SAP system and so on. With the Downtime-minimized import mode, the ABAP programs in the Import 1 module are inactive when imported. Advantages of the Downtime-minimized import mode: Since you can stop the import of SAP Support Packages after each module, you can run the Preparation and Import 1 modules up to the first modification adjustment during production operation. After the scheduled switch to non-production operation, you can run the Import 2 module and the modification adjustments, if required. After that, production operation can resume. Note: You can considerably reduce SAP system downtime by selecting Downtime-minimized. However, this makes the overall import procedure longer because the ABAP programs still need to be activated in module Import 2. Additionally, module Import 1 will take longer to run because the imported objects must be kept in addition to the previous versions of the objects using the version administration tools.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

371

Unit 9: Patching SAP Systems

TADM12_1

The setting for the Downtime-minimized import mode also influences the default setting for the start conditions of the four import modules. If you selected the conventional import procedure (Downtime-minimized import mode not activated), the following settings appear by default: 1. 2. 3. 4.

Preparation: Start in dialog immediately Import 1: Continue in dialog immediately Import 2: Continue in dialog immediately Clean Up: Continue in dialog immediately

If you selected the Downtime-minimized import mode, the following settings appear by default: 1. 2. 3. 4.

Preparation: Start in dialog immediately Import 1: Continue in dialog immediately Import 2: Continue manually Clean Up: Continue manually

Figure 187: Modification adjustment when importing SAP Support Packages

If SAP objects were modified by the customer and then imported with a SAP Support Package, the objects have to be adjusted when they are imported. If these objects are not adjusted, the customer's modifications that have been made to the

372

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Applying SAP Support Packages

SAP objects are reset to the SAP delivery status. Use transaction SPDD to adjust Dictionary repository objects, and transaction SPAU to adjust non-Dictionary repository objects. The modification adjustment for Dictionary repository objects is performed using transaction SPDD. This modification adjustment must be carried out completely before you can continue with the import. Otherwise, the modifications to the Dictionary repository objects are lost. This can then lead to data loss. Caution: The SPDD adjustment should be performed manually in each SAP system in the landscape and not be replaced by importing a transport request. Importing a transport request can lead to inconsistencies and is not recommended. Note: As of SPAM/SAINT Version 7.00/0024, you can bind transport requests that contain the modification adjustments from the development system into the SAP Support Package queue for the subsequent SAP systems. This means that the modification adjustments only need to be carried out once in the development system, and are then implemented automatically in the quality assurance and production systems by the modification adjustment transports. This is a similar procedure as in a release upgrade. The modification adjustment for non-Dictionary repository objects is performed using transaction SPAU. You can perform the SPAU adjustment in each SAP system of a multi-SAP system landscape manually. Or this modification adjustment can be performed once in the development system and imported to the following SAP systems using the resulting transport request (which is not possible in transaction SPDD). To do this, however, you should compare the modification status of the individual SAP systems in the landscape beforehand. You can check these at any time with the Modification Browser (transaction SE95). Note: As of SPAM/SAINT Version 7.00/0024, you can bind transport requests that contain the modification adjustments from the development system into the SAP Support Package queue for the subsequent SAP systems.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

373

Unit 9: Patching SAP Systems

TADM12_1

To perform an SPDD or an SPAU modification adjustment, proceed as follows: 1.

2.

To enable developers to perform the modification adjustment, create a transport request in the Transport Organizer, and under the transport requests, create tasks for the developers. You are advised to create only one transport request for the adjustment of Dictionary repository objects (SPDD) and one second transport request for the adjustment of non-Dictionary repository objects (SPAU). The developers can now perform the modification adjustment. They can use transactions SPDD and SPAU to do this. After the adjustment is complete, the developers must release the tasks and transport requests. Hint: Although transaction SPAM is used in client 000, the modification adjustment must take place in the development client, for example client 100.

3.

4. 5.

If you are using a SPAM/SAINT version 7.00/0024 or above, you can flag the adjustment transport requests (select Select for Transport in the transactions SPDD and SPAU). This is possible as of Basis Release 7.00. This enables you to perform the modification adjustments manually in the development system only. When you import the SAP Support Packages to the subsequent SAP systems of the landscape, these adjustment transports can be included in the SAP Support Package queue. This means manual modification adjustments are no longer required in the subsequent SAP systems. Now choose Confirm Adjustment and confirm the prompt. To continue the import process, choose SAP Support Package → Import Queue.

The Support Package Manager continues the processing and displays the status.

374

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Applying SAP Support Packages

Figure 188: Additional Hints

Hint: For some SAP systems, for example SAP CRM Server, an advanced version of SPAM is used: in Transaction SPAM choose Environment →Support Package Manager for EBP/CRM. It is more interactively and besides others - helps the SAP system administrator to manage the SAP system downtime.

SUM It is also possible to import SAP Support Packages with the Software Update Manager (SUM). Importing SAP Support Packages with SUM is by far more difficult and complex for the SAP system administrator, but leads to a shorter downtime! So this method should be used, if you have to apply a huge number of SAP Support Packages in a very downtime critical SAP system.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

375

Unit 9: Patching SAP Systems

TADM12_1

Figure 189: Applying SAP Support Packages with SUM

Especially when using the SUM 'advanced mode', SAP system downtime can be reduced significantly! For a comparison of SPAM and SUM see the previous lesson.

376

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Applying SAP Support Packages

Exercise 14: Applying SAP Support Packages Exercise Objectives After completing this exercise, you will be able to: • Applying SAP Support Packages with transaction SPAM

Business Example You need to apply the most recent SAP Support Packages to update the SAP system.

Task: Applying an SAP Support Package Caution: This exercise must be performed first by the DCC group and then by the QCC group. It must not be performed by both groups at the same time. Note: Information only applicable for the current training environment: The applying of the single SAP Support Package takes about 6 minutes. Of this time, most is spent with some preliminary checks (about 5 minutes). Apply the SAP Support Package named by your instructor. In the first step, the available SAP Support Package is applied to the SAP system DCC. After this applying is successfully completed, the SAP Support Package is applied to the SAP system QCC. The file required for the SAP Support Package has already been requested. It is located on the ADM share at S:\Courses\ADM100_col99\SP_TRAINING_620 1.

Check which SAP Support Packages have already been applied to your SAP system. Have these been confirmed?

2.

Extract the files that contain the new SAP Support Package at operating system level. Note that this step only needs to be performed only once for each transport directory.

3.

Log on to the correct client.

4.

Load the SAP Support Package, that is, inform the SAP system about the files. Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

377

Unit 9: Patching SAP Systems

378

TADM12_1

5.

Check the settings for the applying of the SAP Support Packages in transaction SPAM.

6.

Define the queue for applying the SAP Support Package in transaction SPAM.

7.

Import the SAP Support Package queue to your SAP system. Note any possible errors.

8.

Check the log for the import process for errors.

9.

Confirm the applied SAP Support Package after successfully applying.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Applying SAP Support Packages

Solution 14: Applying SAP Support Packages Task: Applying an SAP Support Package Caution: This exercise must be performed first by the DCC group and then by the QCC group. It must not be performed by both groups at the same time. Note: Information only applicable for the current training environment: The applying of the single SAP Support Package takes about 6 minutes. Of this time, most is spent with some preliminary checks (about 5 minutes). Apply the SAP Support Package named by your instructor. In the first step, the available SAP Support Package is applied to the SAP system DCC. After this applying is successfully completed, the SAP Support Package is applied to the SAP system QCC. The file required for the SAP Support Package has already been requested. It is located on the ADM share at S:\Courses\ADM100_col99\SP_TRAINING_620 1.

Check which SAP Support Packages have already been applied to your SAP system. Have these been confirmed? a)

Transaction SPAM: Select the Imported Support Packages radio button and choose Display. Result: SAP Support Packages have already been applied. They have also already been confirmed. You can tell this, for example, from the green traffic light on the initial screen of transaction SPAM.

2.

Extract the files that contain the new SAP Support Package at operating system level.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

379

Unit 9: Patching SAP Systems

TADM12_1

Note that this step only needs to be performed only once for each transport directory. a)

Go to file system level. Copy the relevant file to the transport directory (for example D:\usr\sap\trans). At operating system level, open a Command Prompt in the transport directory (for example D:\usr\sap\trans). Extract the file you have just copied there using the command sapcar -xvf . This extracts the file to the relative directory \EPS\in (for example D:\usr\sap\trans\EPS\in).

3.

Log on to the correct client. a)

Log on to client 000. It is only possible to apply SAP Support Packages from client 000.

4.

Load the SAP Support Package, that is, inform the SAP system about the files. a)

Transaction SPAM: Support Package → Load packages → From Application Server. Smile about the misleading named menu path and confirm the dialog box to “upload”. See that the new SAP Support Package was recognized. Go back to the initial screen of SPAM.

5.

Check the settings for the applying of the SAP Support Packages in transaction SPAM. a)

Transaction SPAM: Extras → Settings Leave the settings at their default values.

6.

Define the queue for applying the SAP Support Package in transaction SPAM. a)

Transaction SPAM: Choose the Display/define button. Choose the required software component (TRAINING) and the required SAP Support Package. You can confirm the queue with Enter. There are no adjustment transports that could be included: You should therefore confirm the system prompt Do you want to add Modification Adjustment Transports to the queue now? with No Continued on next page

380

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Applying SAP Support Packages

7.

Import the SAP Support Package queue to your SAP system. Note any possible errors. a)

In transaction SPAM, apply the queue by choosing Support Package → Import Queue. Retain the default values for the start conditions of the four modules. Confirm the dialog box to start the applying. Follow the individual steps of the import process, as far as possible, in the status line. If errors occur, check these by opening the error log. In this case, repeat the applying of the SAP Support Package. The import process can be repeated beginning with the step it failed. Confirm the dialog box informing you that the import was successful.

8.

Check the log for the import process for errors. a)

Check the import logs in transaction SPAM by choosing Goto → Import Logs → Queue. No return code values of 8 or higher should be displayed.

9.

Confirm the applied SAP Support Package after successfully applying. a)

2013/Q1

Finally, confirm the queue in transaction SPAM by choosing Support Package → Confirm

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

381

Unit 9: Patching SAP Systems

TADM12_1

Lesson Summary You should now be able to: • Import SAP Support Packages with transaction SPAM • Provide a explanation of the import process for SAP Support Packages

382

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Java Support Packages, Stacks and Patches

Lesson: Java Support Packages, Stacks and Patches Lesson Overview [Enter a brief overview of the lesson.]

Lesson Objectives After completing this lesson, you will be able to: • •

Describe the relationship between Support Packages, Patches, Support Package Stacks and Support Packages with Patchs Describe the relationship between Product Version, Product Instance, Software Component and Support Package

Business Example You have to apply Support Packages, Stacks or Patches to a AS Java system. You need to know, what the relationship between these are and which Support Packages are installed in the AS Java system.

Support Packages Support Packages are corrections that SAP supplies to customers. The component model used by SAP in the context of Java development is used both in delivery (installation) and in the context of maintenance (import of Support Packages).

Figure 190: Component Model in Delivery and Maintenance

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

383

Unit 9: Patching SAP Systems

TADM12_1

Software maintenance is organized into three tiers: •

•

A product consists of one or more software components that represent related business scenarios. Products are installed or undergo an upgrade to a new release. A release is a full delivery of software components that provides new functions (and possibly user interfaces) or improvements. Software components contain a set of development components. Support Packages are delivered in the context of software maintenance. A Support Package (SP) is (unlike ABAP) a full delivery of one (or more) software component(s) and contains a number of patches. If sources are delivered with Support Packages, the SPs must be transported using the NWDI's Change Management Service (CMS). The usual file format of an SP is the SCA format. SAP does not advise you to import Support Packages individually for each software component; rather you are advised to import them as uniformly as possible for an entire system or even entire applications (comprising several systems). Therefore, SAP provides the MOpz in the Solution Manager which composes the individual Support Packages together as a Support Package Stack for the respective system.

•

Patches are full deliveries of a development component that allow a quick error correction, before the complete SP is available. The usual file format is the SDA format. If patches include sources, they must also be imported using the resources of the CMS.

Product, Product Instance, Support Packages, and their relationship In the LMDB of the SAP Solution Manager, there are often used the terms Product, Product Version and Product Instance. There are a lot of Products for an SAP System. “SAP NetWeaver” is a Product and “SAP NetWeaver 7.3” or “SAP Enhancement Package 1 for SAP NetWeaver 7.3” are “Product Version” of “SAP NetWeaver”. A Product Version consists out of one or more Product Instances. During the installation of an SAP System (we call it here Technical System and it's identified by a ) you choose one or more Product Instances. However, it is not possible to install every Product Instance you like in an Technical Systeme, there are restrictions described in the installation Master Guide.

384

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Java Support Packages, Stacks and Patches

Figure 191: Product Versions and Software Components in a Technical System

In Figure Product Versions and Software Components in a Technical System you can see, that there are only some Product Instances of the “SAP Enhancement Package 1 for SAP NetWeaver 7.3” are installed in the Technical System. So it's not necessary to install all Product Instances of a Product Version in a Technical System (but there are dependencies which are described in the installation Master Guide). During the installation of a SAP NetWeaver system you choose “Usage Types” and the appropriated Product Instances are taken. There are also Product Instances of the Product Version “Portal Add-On-SAP NW 7.3 EHP1” installed on the same Technical System (see restrictions in the installation Master Guide). Such additional Product Instances are installed with special tools e.g. SUM, SAINT and are called Add-On. Product Instances consists of one or more Software Components (SC's) and during the installation thease are deployed in the system. A Software Componet can belong to different Product Instances. But if such Product Instances are installed in a system, they exists only once in a system. Software Components have a common name and a technical name. The technical name of a Software Component you can find in an AS Java system in the SAP NetWeaver Administrator /nwa/sysinfo → Components Info. The name of a Support Packages (SP) can be construred form the technical name of the Software Component. The Support Package name for the Software Component “J2EE Engine Servercore 7.31” beginns with SERVERCORE_... where is a two digit number (it is Support Package for SC “J2EE Engine Servercore 7.31”) and the Support Package name for

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

385

Unit 9: Patching SAP Systems

TADM12_1

the Software Component “KMC UI Layer 7.31” beginns with KMCUI_... (no dashes). Thease numbers can be different between different Software Components. The MOpz knows, which numbers belong together. Beside the Software Components and their Support Packages there a other components like the Kernel, IGS, SAP Host Agent and so on, which also belong to a Technical System and have to be updated. All thease components which have to be updated are collected by MOpz during a Maintenance Transaction an entered in the Stack configuration XML file (or short Stack XML). The Stack configuration XML file is used to apply the Support Packages in a system. If errors occur in a Software Component after the delivery of a Support Package, a patch can be created to fix the bug. If several bugs are fixed, a Support Package including the patches are delivered by SAP. The name of a Support Package with Patches beginns with SERVERCOREP_... and the P indicates that patches are included. The Support Package number does not increase in this case but the increase with every Support Package with patches what is delivered for this Support Package.

Figure 192: Support Packages and Support Packages with Patches

If a new Support Package (without patches) for the Software Component is delivered, the number of the Support Package increases. For the new Support Package 05 (see figure “Support Packages and Support Packages with Patches” ) now Support Packages with Patches are delivered and still Support Package with Patches for the “older” Support Package (here 04). If the latest Support Package with Patch is deployed in your system (here servercore04P_2..) and you will apply Support Package 05 for these Software Component, it can make sense, to apply the latest Support Package with Patches for Support Package 05 (here servercore05P_1.. or servercore05P_2...). During the Maintenace Transaction in the MOpz you can choose to include Support Packages with Patches in the download basket (Button: Java Patches).

386

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Java Support Packages, Stacks and Patches

In LMDB of the SAP Solution Manager you can find which Product Instance is installed on your Technical System. You can use the Software Catalog in the System Landscape Directory (SLD) to drill down to find the name of the Software Component and their Support Package name..

Figure 193: Product Instance and Software Component determination

Call the SLD where your AS Java is connected to and choose in the Software Catalog Products. Search for the Product Portal ADD-ON SAP NW 7.3 EHP1 for example and expand Portal ADD-ON SAP NW 7.3 EHP1: Forum, then the Software Components (here called: Software Units) Forums 7.31 and KMC UI LAYER 7.31 are shown. Select the Software Component KMC UI LAYER 7.31 and you jump in the Software Component view. Choose the tab Support Packages an you find the name KMC-UI. The contrariwise way is a little bit more difficult. In the SAP NetWeaver Administrator you can find all the installed Software Components in nwa/sysinfo → Components Info. You can search in the Software Component view of the Software Catalog of the SLD for the name of a Software Component e.g KMC-UI. Select the correct version. In the tab Products you can now find to which Product Version the Software Component belongs. Select the Product Version an you can see which Product Instances could contain the Software Component. In our example we find the Product Instances Forums and Wiki. If we drill down, we can see, that KMC-UI belongs to both Product Instances. In this case we can not know, which Product Instance is installed (or both) on our Technical System. We have to check for a Product Instance every Software Component, to be sure, that thease Software Component is installed. But we can find out the Product Version this way.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

387

Unit 9: Patching SAP Systems

TADM12_1

Lesson Summary You should now be able to: • Describe the relationship between Support Packages, Patches, Support Package Stacks and Support Packages with Patchs • Describe the relationship between Product Version, Product Instance, Software Component and Support Package

388

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Importing Corrections with SUM for AS Java

Lesson: Importing Corrections with SUM for AS Java Lesson Overview This lesson presents the updating of an AS Java 7.3x-based SAP system, by installing a current Support Package Stack with the Software Update Manager (SUM) which is part of the SL Toolset.

Lesson Objectives After completing this lesson, you will be able to: • •

Call the Software Update Manager (SUM) Import Support Packages and Support Package Stacks for SAP NetWeaver AS Java 7.3x-based systems.

Business Example Quality control of the petrochemistry company XYZ AG has detected an error in an important business process. This error can be traced back to an incorrect delivery of an SAP software component. You must import the latest Support Package Stack to eliminate this error.

Software Update Manager for AS Java regarding applying of Support Packages In the past there were several different tools for applying Support Packages for an AS Java or an AS ABAP or applying of Enhancement Packages for AS Java or AS ABAP and so on. The aim of the Software Update Manager is to provide one tool for these tasks regardless if the system is based on AS Java or as ABAP. However, in this lesson we conentrate on the use case of applying Support Package Stacks or Support Packages to an AS Java. In the past, this was done by a tool called JSPM. The JSPM was part of the AS Java system and there were differences between various releases. The SUM is not a part of the SAP system and is delivered seperately, so for applying Support Packages and Support Package Stacks the latest version of SUM can be used. It is possible to use the same version of SUM for applying Support Packages and Support Package Stacks for a SAP NetWeaver 7.0x AS Java System and a SAP NetWeaver 7.3x AS Java System. However, it is also possible to Upgrade these AS Java Systems (as of AS Java 7.0x) with the same SUM version, but that is not part of this lesson.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

389

Unit 9: Patching SAP Systems

TADM12_1

Figure 194: Benefits and Use Cases of the Software Update Manager.

See SAP Note 1589311 for replacement of JSPM by SUM. For practical information concerning SUM call SAP Service Marketplace quick linkhttp://service.sap.com/sltoolset. The SL Toolset is a name for a collection of several tools. The above mentioned quick link also provides access to a Central SAP Note, which covers important information about release restrictions and is mandatory before executing this tool. Also a direct link to the download of the SUM and the other tools of the SL Toolset are placed here. However, you can select the SUM during the Maintenance Transaction of MOpz as well. If you apply Support Package Stacks or Support Packages to a system landscape, you always start with the development system. First, apply the Support Package Stack to the DEV (Development) system and after finishing, test the system. Second, apply the Support Package Stack to the QAS (Quality Assurance) system and after finishing, let the user department make a functional test of the system. third, apply the Support Package Stack to the PRD (Productiv) system.

390

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Importing Corrections with SUM for AS Java

Figure 195: SL Toolset maintenance strategy

This is the maintenance strategy for the maintenance tools. Use the latest SL Toolset Stack when you start your project! Still it is possible to continue a running project with the SUM version initially used. Note that a SUM SP version will be supported for a maximum of 12 months (4 months maintenance phase plus 8 months patch on request phase). As soon as the next SL Toolset Stack is available, its predecessor passes into „patch on request“ mode immediately. The documentation guides available on SAP Service Market Place cover the latest version only. It is recomended, that SUM is extracted to the folder below directory \usr\SAP\\SUM. To do this, plase the SUM archive in the directory \usr\SAP\ of the Primary Application Server instance (PAS) and extract it with the command sapcar -xvf . The PAS is the instance on the host, where the Central Services instance is installed. The folder SUM is created direct below the directory . Start the SUM with the script startup.bat or startup.sh. The SL Controller is started on the host of the PAS-instance. The SL Controler controls the apply of Support Packages or Support Package Stacks to the AS Java. During this procedure, the SL Controler stops and starts the AS Java. After applying the Support Packages the AS Java is up and running.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

391

Unit 9: Patching SAP Systems

TADM12_1

Figure 196: Installing and starting the SUM

If the SUM is started on the server, in a command prompt the ports for the browser (httpport=4239) and the SUM GUI (guiport=4241) are listed. To start the SUM GUI, connect via browser to the HTTP port (default: 4239) and the browser starts the SUM GUI which connects to the SL Controller. Follow the SUM Documentation to apply the Support Package Stacks. If the AS Java is installed on a Windows operating system, make sure, that the SAP MMC is stopped. Remove all unnecessary profiles from directory \usr\SAP\\SYS\profile. However, it is always a good idea to make a copy of the profile directory before you clean up this directory. You can remove the old backup profiles which end with .1, .2 and so on. During the Select Target step you can decide either you wont to apply a Support Package Stack with the StackXML file or single Support Packages (e.g. in case of applying Support Packages with Patches to the same Support Package Stack which is installed already) by a manually prepared download directory. The Support Packages have to be in the same folder as the StackXML file. It's not necessary for SUM, that this is the EPS\in directory. But it is not recomended to use another directory than a local for the Support Packages and the StackXML file. Also, this directory must be a flat directory. Subdirectories are ignored. If you have started the SUM GUI you are guided through the following roadmap steps. The roadmap step that is currently running is highlighted. Note that the roadmap step Execute Process... is broken down into 7 roadmap steps numbered from 5.1 to 5.7 as visualized in the following figure.

392

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Importing Corrections with SUM for AS Java

Figure 197: SUM Roadmap

As described in figure “SUM Roadmap”, make sure in the end of the Preparation step that you have all necessary backups before entering the downtime and execution step. In the Execute Process... step you can set breakpoints. The SUM will wait if a breakpoint is reached. At the end of the step Summary there is a ProcessOverview.zip file for download. At the end of the last step the ProcessOverview.html is started in the browser which gives full information about timings, the SC's which where applied and so on.

Figure 198: ProcessOverview timings

However, if you forgot to save the ProcessOverview.zip file, you can still find it in the SUM directory in the subfolder \sdt\htdoc.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

393

Unit 9: Patching SAP Systems

394

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM12_1

2013/Q1

TADM12_1

Lesson: Importing Corrections with SUM for AS Java

Exercise 15: Importing corrections with SUM for AS Java Exercise Objectives After completing this exercise, you will be able to: • Implement corrections for SAP NetWeaver AS Java with SUM

Business Example SAP NetWeaver Application Server Java is used as the runtime environment for applications that conform to the Java EE standard. You can use Support Packages to correct errors and implement new functions for SAP NetWeaver AS Java.

Task 1: Preparations for applying Support Package Stacks Provide the required Support Packages, the corresponding file stack.xml in a stack directory for the Software Update Manager (SUM). Extract the SUM Software to \usr\SAP\\SUM, where is the SID of your AS Java system. Delete unnecessary profiles and stop the SAP MMC. 1.

Log on to the operation system, where your AS Java system is installed.

2.

Create a Stack directory for your System in folder \usr\sap\ e.g. _SUM_Stack_directory

3.

Copy your Stack.xml file (the file for your system beginning with SMSDXML__....xml) from the directory \usr\SAP\trans\EPS\in to the previous created folder. If the XML file does not exist, ask your trainer.

4.

Copy all files, which belong to the Stack.xml from the course folder on the trainings share to your created Stack directory _SUM_Stack_directory. The Stack directory must not contain subfolders. The files for your Stack.xml are stored under the course folder on the training share in the following path Maintenance\Files_for_StackXML.

5.

Copy the SUM....sar file to the folder \usr\sap\ of your system. Extract the SUM....sar file with the command sapcar -xvf SUM...sar. A new directory is generated \usr\SAP\\SUM with the content of the Software Update Manager. SAP recomends, that the SUM directory is located as subdirectory below the path \usr\sap\. The SUM....sar file is located in the course directory of the trainings share in the folder Mainenance\SUM_Software.

6.

Make a copy of your profile directory. Delete unnecessary profiles in the original profile directory. Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

395

Unit 9: Patching SAP Systems

7.

TADM12_1

Make sure, that the “SAP MMC” and all other tools which are not necessary are closed.

Task 2: Appying a Support Package Stack with SUM Appy a Support Package Stack with SUM for your System. 1.

Start the “SL Controller” for your system. The recommended procedure is: First, apply the Support Package Stack to the DEV (Development) system and after finishing, test the system. Second, apply the Support Package Stack to the QAS (Quality Assurance) system and after finishing, let the user department make a functional test of the system. third, apply the Support Package Stack to the PRD (Productiv) system. Only for training purpose we will run SUM in concurrent and apply the SP Stack to the training systems in parallel, thereforewe have to give the SL Controler different ports for the QEP and PEP system. Open a command prompt for the folder \usr\SAP\\SUM for your system. DEP systems type: startup.bat. Be aware, that the standard ports are: httpport=4239 guiport=4241 QEP systems type: startup.bat httpport=4439 guiport=4441. PEP systems type: startup.bat httpport=4539 guiport=4541.

2.

Start the SUM GUI for your system.

3.

Enter a user for the Administrator Role. For user enter sumadmin where is the SID of your system. For the password enter sum.

4.

In the Welcome step press Next.

5.

In the Specify Credentials step enter the password from adm which the trainer provided to you and press next.

6.

In the Select Target step browse to your Stack configuration XML file, which is located in \usr\SAP\\_SUM_Stack_directory. Select the SMSDXML__....xml file.

7.

Enter the Keyword the trainer provided for you and press Next.

8.

In the Execute Process .. step continue til the Begin Downtime, this is in substep Preprocessing.

Continued on next page

396

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Importing Corrections with SUM for AS Java

You have to enter a AS Java Administrator User Name an his password. The AS Java Administrator User Name is your course-user with his password. 9.

Before you enter the Downtime, log off all user from the system. Make sure, that you have a Backup of your Database and Backup of the directory \usr\SAP\ and the direcory of the SUM himself. However, in this training class only log off all user in your system.

10. Now choose Continue and Next to enter the substep Execution. This will take a long time. 11. After finishing the Excecution step choose Next to enter the Postprocessing. 12. In the Postprocessing step you should do again a backup. Choose Continue and Next. 13. In the Summary step you get information like the Process Runtime and the System Downtime. Also some questions are asked which you can fill out and send to SAP. Choose Next and you can find a .zip file for download. This contains the ProcessOverview.html and the ProcessOverview.xml. Choose Next and SUM GUI and SL Controler are closed and the ProcessOverview.html is started in your browser which shows all information about the applying of the Support Package Stack. 14. Rename the \usr\sap\\SUM directory to SUM_Nr1.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

397

Unit 9: Patching SAP Systems

TADM12_1

Solution 15: Importing corrections with SUM for AS Java Task 1: Preparations for applying Support Package Stacks Provide the required Support Packages, the corresponding file stack.xml in a stack directory for the Software Update Manager (SUM). Extract the SUM Software to \usr\SAP\\SUM, where is the SID of your AS Java system. Delete unnecessary profiles and stop the SAP MMC. 1.

Log on to the operation system, where your AS Java system is installed. a)

2.

Create a Stack directory for your System in folder \usr\sap\ e.g. _SUM_Stack_directory a)

3.

See the description in the exercise.

Copy all files, which belong to the Stack.xml from the course folder on the trainings share to your created Stack directory _SUM_Stack_directory. The Stack directory must not contain subfolders. The files for your Stack.xml are stored under the course folder on the training share in the following path Maintenance\Files_for_StackXML. a)

5.

Navigate with the explorer to the folder \usr\sap\ for your system and select this folder. Use the right mouse button to open the context menu and select New → Folder and enter _SUM_Stack_directory where is the SID of your system.

Copy your Stack.xml file (the file for your system beginning with SMSDXML__....xml) from the directory \usr\SAP\trans\EPS\in to the previous created folder. If the XML file does not exist, ask your trainer. a)

4.

If not already clear, which tool is to used, ask your trainer.

The StackXML file and the related files have to be in the same folder. Copy the files in your folder _SUM_Stack_directory.

Copy the SUM....sar file to the folder \usr\sap\ of your system. Extract the SUM....sar file with the command sapcar -xvf SUM...sar. A new directory is generated \usr\SAP\\SUM with the content of the Software Update Manager. SAP recomends, that the SUM directory is

Continued on next page

398

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Importing Corrections with SUM for AS Java

located as subdirectory below the path \usr\sap\. The SUM....sar file is located in the course directory of the trainings share in the folder Mainenance\SUM_Software. a)

Copy the SUM....sar e.g. SUM10SP06...SAR to the directory \usr\sap\. You can choose the latest version which is provided in this folder.

b)

Select the folder \usr\sap\ and use the right mouse button to open the context menu. Choose CMD Promt Here.

c)

Enter sapcar -xvf SUM and use the tabulator button for autocompleting the name of the SUM....sar file and press enter to extract the archives. The subdirectory SUM is created below the directory .

6.

Make a copy of your profile directory. Delete unnecessary profiles in the original profile directory. a)

Navigate to the folder \usr\sap\\SYS of your system and copy the folder profile to a new folder e.g profile - Copy. Enter the original folder profile and delete all unnecessary profiles which end with .1, .2 and so on.

7.

Make sure, that the “SAP MMC” and all other tools which are not necessary are closed. a)

Close the SAP MMC.

Task 2: Appying a Support Package Stack with SUM Appy a Support Package Stack with SUM for your System. 1.

Start the “SL Controller” for your system. The recommended procedure is: First, apply the Support Package Stack to the DEV (Development) system and after finishing, test the system. Second, apply the Support Package Stack to the QAS (Quality Assurance) system and after finishing, let the user department make a functional test of the system. third, apply the Support Package Stack to the PRD (Productiv) system. Only for training purpose we will run SUM in concurrent and apply the SP Stack to the training systems in parallel, thereforewe have to give the SL Controler different ports for the QEP and PEP system.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

399

Unit 9: Patching SAP Systems

TADM12_1

Open a command prompt for the folder \usr\SAP\\SUM for your system. DEP systems type: startup.bat. Be aware, that the standard ports are: httpport=4239 guiport=4241 QEP systems type: startup.bat httpport=4439 guiport=4441. PEP systems type: startup.bat httpport=4539 guiport=4541. a)

Select the folder \usr\sap\\SUM and use the right mouse button to open the context menu. Choose CMD Promt Here.

b)

Enter the following command according to the SID of your system: DEP systems type: startup.bat. Be aware, that the standard ports are: httpport=4239 guiport=4241 QEP systems type: startup.bat httpport=4439 guiport=4441. PEP systems type: startup.bat httpport=4539 guiport=4541. If some of the ports are already used, replace the ports by unused ports. You can find unused ports with the tool CurPorts, which is located in the Trainings Menu → Tools → CurPorts.

2.

Start the SUM GUI for your system. a)

Open the Internet Explorer. Enter the URL according to the SID of your system: DEP systems type: http://.wdf.sap.corp:4239. QEP systems type: http://.wdf.sap.corp:4439. PEP systems type: http://.wdf.sap.corp:4539.

b) 3.

Choose Open to open the sdtdsu.jnlp SUM GUI. Select I accept .. and Run.

Enter a user for the Administrator Role. For user enter sumadmin where is the SID of your system. For the password enter sum. a)

Enter user and password in lowercase and press OK.

4.

In the Welcome step press Next.

5.

In the Specify Credentials step enter the password from adm which the trainer provided to you and press next. Continued on next page

400

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Importing Corrections with SUM for AS Java

6.

7.

In the Select Target step browse to your Stack configuration XML file, which is located in \usr\SAP\\_SUM_Stack_directory. Select the SMSDXML__....xml file. a)

Make sure, that Stack configuration file (XML) is selected.

b)

Choose Browse... and browse to the folder \usr\SAP\\_SUM_Stack_directory on the D: drive and expand this.

c)

Select the SMSDXML__....xml file and choose OK.

d)

Enter the next step by choosing Next.

Enter the Keyword the trainer provided for you and press Next. a)

8.

You now start the Execute Process ... step with the Initialization.

In the Execute Process .. step continue til the Begin Downtime, this is in substep Preprocessing. You have to enter a AS Java Administrator User Name an his password. The AS Java Administrator User Name is your course-user with his password.

9.

a)

In substep Initialization choose Next

b)

In substep Extraction choose Next

c)

In substep Configuration enter the AS Java Administrator User Name which is your course-user with his password and choose Continue. You have to choose Continue several times til you are shown the System Parameters.. Choose Continue and Next to enter the substep Checks.

d)

In substep Checks choose Next

e)

After the substep Preprocessing you enter the Execution step. Don't choose next. Go further with the next step in this task description.

Before you enter the Downtime, log off all user from the system. Make sure, that you have a Backup of your Database and Backup of the directory \usr\SAP\ and the direcory of the SUM himself. However, in this training class only log off all user in your system. a)

Log on to the SAP NetWeaver Administrator and use the /nwa/sessionmgt quick link. Select user by user and choose Terminate. You can not terminate your own session. If every user is logged out, log off yourself by choosing Log Off.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

401

Unit 9: Patching SAP Systems

TADM12_1

10. Now choose Continue and Next to enter the substep Execution. This will take a long time. a)

The Software Components, Kernel etc. will be deployed. During this step the system is stopped and started again at the end.

11. After finishing the Excecution step choose Next to enter the Postprocessing. 12. In the Postprocessing step you should do again a backup. Choose Continue and Next. a)

Again in this training environment we skip this step. In your company you should do the backup.

13. In the Summary step you get information like the Process Runtime and the System Downtime. Also some questions are asked which you can fill out and send to SAP. Choose Next and you can find a .zip file for download. This contains the ProcessOverview.html and the ProcessOverview.xml. Choose Next and SUM GUI and SL Controler are closed and the ProcessOverview.html is started in your browser which shows all information about the applying of the Support Package Stack. a)

Congratulation!

14. Rename the \usr\sap\\SUM directory to SUM_Nr1. a)

402

See description above.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Importing Corrections with SUM for AS Java

Lesson Summary You should now be able to: • Call the Software Update Manager (SUM) • Import Support Packages and Support Package Stacks for SAP NetWeaver AS Java 7.3x-based systems.

Related Information •

2013/Q1

http://service.sap.com/sltoolset.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

403

Unit 9: Patching SAP Systems

TADM12_1

Lesson: Appendix: Importing Corrections with JSPM Lesson Overview This lesson presents the updating of an AS Java 7.1x-based SAP system, for example SAP NetWeaver CE 7.1x or SAP NetWeaver PI 7.1x, by installing a current Support Package Stack.

Lesson Objectives After completing this lesson, you will be able to: • •

Call the Java Support Package Manager (JSPM). Import Support Packages and Support Package Stacks for SAP NetWeaver AS Java 7.1x-based systems.

Business Example Quality control of the petrochemistry company XYZ AG has detected an error in an important business process. This error can be traced back to an incorrect delivery of an SAP software component. You must import the latest Support Package Stack to eliminate this error.

Introduction: Java Support Package Manager As of SAP NetWeaver 7.0, the Java Support Package Manager (JSPM) is used to import Support Packages for SAP NetWeaver Application Server Java (AS Java) and all the Java-based software components running on it. There are two additional tools, CEUPDATE and the Update Management Service, for SAP NetWeaver CE 7.1x only. Both serve as user interfaces to facilitate the import of a Support Package Stack. •

Updating: –

• •

404

Kernel, Internet Graphic Server (IGS), SAP JVM and other native AS Java operating system binaries – JSPM itself – All Java software component installed in the system – Modified software components (integration with NWDI) Deployment of SAP and third-party software components Deployment, update and upgrade of Business Packages in the SAP Business Suite

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Appendix: Importing Corrections with JSPM

JSPM can import either individual Support Packages or a complete Support Package Stack SAP recommends that you always implement the complete Support Package Stack in a Java system. This is the only way to ensure the consistency of the system and the application. Java Support Package files (SCAs) contain all the software objects and the associated software components (Full Patch). As a result, it is sufficient to update the Java system with the required Support Package Stack. It is not necessary to import all the Support Package Stacks from the start Support Package Stack level through to the target Support Package Stack level one after the other. JSPM provides a simple, intuitive graphical user interface (GUI). JSPM only displays those components for which an update is possible. You can also see the current Support Package level in JSPM. JSPM simplifies the Support Package management process for Java applications by recognizing and taking account of dependencies and reducing manual activities. JSPM works together with the SAP NetWeaver Development Infrastructure (NWDI), thus making it possible to identify modified components. In NWDI development (DEV) and consolidation systems (CONS), JSPM detects modified software components and transports them for deployment to the NWDI system. In NWDI test (TEST) and production systems (PROD), JSPM detects and deploys modified software components. The AS Java must be started for JSPM to start. Hint: The user adm should start JSPM. You start JSPM using an instance file system script from the directory /usr/sap///j2ee/JSPM. The script is called go.bat (Windows) or go (Unix). You now have to enter the user ID and password of an administration user of the AS Java, for example Administrator or j2ee_admin. JSPM writes all its log files to the directory /usr/sap///j2ee/JSPM/log. Hint: Before you use the Java Support Package Manager, read SAP Note 1147119. If you use SAP systems on iSeries then you can find additional information in SAP Note 1066038.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

405

Unit 9: Patching SAP Systems

TADM12_1

JSPM: Preparatory Steps for SP Stack You should note the following steps before using JSPM: 1. 2.

Before the update: Check the entire functional capability of the system Download the Support Package Stack (for all installed Usage Types) and the corresponding Support Package Stack definition file (SPSTab.xml). You should do this with the Maintenance Optimizer in SAP Solution Manager.

3.

Storage location of the files (Support Packages and Support Package definition file): JSPM Inbox (Default: /usr/sap/trans/EPS/in) The storage location of the JSPM Inbox is defined via the parameter DIR_EPS_ROOT.

4.

Check the free space in the file system for the directory /usr/sap///j2ee/JSPM/temp. Temporarily available disk space: approximately 3 times the size of the Support Package files

If JSPM is to recognize the Support Package Stack correctly, both the Support Package files and the corresponding Support Package Stack definition file (SPSTab.xml) must be downloaded and available in the JSPM Inbox.

406

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Appendix: Importing Corrections with JSPM

JSPM: Importing an SP Stack You perform the following steps to import SP Stacks using JSPM. 1.

Log on as user adm to the instance host. Close all SAP MMC and services consoles under Windows.

2.

Start JSPM and log on with an administration user of the AS Java. Start JSPM from /usr/sap///j2ee/JSPM using the script go or go.bat.

3.

Update JSPM itself (you do not have to perform this step separately since JSMP is also contained in the SP Stack). The JSPM update can be imported at runtime.

4. 5.

a) Select the Start Deployment tab. b) Select the option Java Support Package Manager (JSPM). Call and log on to JSPM again. In the Start Deployment tab, select the option Support and Enhancement Package Stack followed by Next. In this step, JSPM performs a number of status checks and displays the result for each individual software component in the following screen. The following status can be reported:. • •

OK: SP can be imported. WARNING: The software contains customer modifications in a system monitored by NWDI Deployment can be performed. WARNING may also mean: the software components contain lower versions of development components than are available in the system.

REVISE: Indicates inconsistencies with the corresponding software component. A deployment cannot be performed until all the problems have been eliminated. Select Next if the SP Stack has the appropriate status. This starts the updating of the software component and the status of the JSPM changes to SCHEDULED. •

6.

JSPM starts and stops the AS Java several times during this procedure.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

407

Unit 9: Patching SAP Systems

TADM12_1

Figure 199: Import Support Package Stacks

There are different ways to import Support Package Stacks. A significant difference is whether or not patches are applied. In particular, you apply patches if patches have already been applied on the current system. If the patch that has already been applied is of a younger date than the delivery date of the Support Package for the software components, the correction of the patch may not be contained in the Support Package for the software components. If you decide to apply patches, you can do this in one or two steps. The option to apply patches with the Support Package of the SPS in one step has been available as of 7.0 SPS 14. Before you decide on this option, read SAP Note 1080821 carefully. You start JSPM from the file system and log on with an administration user of the AS Java.

408

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Appendix: Importing Corrections with JSPM

Figure 200: Starting JSPM

The step Specify Queue displays the (highest) Support Package Stack level available in the JSPM Inbox. Then, in the Check Queue step, JSPM checks the deployment queue and every software component in the stack is assigned a status.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

409

Unit 9: Patching SAP Systems

TADM12_1

Figure 201: Support Package Stack: Specify Queue, Check Queue

In the Deploy Queue step, JSPM starts the deployment of the software components in the selected stack. When this is done, the status is set to SCHEDULED. The Completed step displays the status of the software components after deployment.

410

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Appendix: Importing Corrections with JSPM

Figure 202: Support Package Stack: Deploy Queue, Completed

After import, the Support Packages can have the following status: • • • •

DEPLOYED DEPLOYED WITH WARNING: The Support Packages have been deployed but might possibly not function correctly with other deployed components. ERROR: An error occurred during deployment and must be eliminated before continuing with the import of the Support Package. NOT DEPLOYED: For certain reasons, JSPM has not attempted to deploy the software components. Eliminate the problems and restart the import.

If the Support Package Stack contains a Kernel Update, JSPM starts with the Kernel Update. JSPM updates the kernel binaries in the global kernel directory. When the instances are restarted, the kernel is then copied locally to all instances via sapcpe. In general, corrections can be imported individually or in the stack. SAP urgently recommends you to use Support Package Stacks in order to ensure the consistency of the system and the applications.

JSPM: Importing Individual Support Packages If you want to update only individual software components and not all the components of the SP Stack, choose the option Single Support Packages and Patches (advanced use).

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

411

Unit 9: Patching SAP Systems

TADM12_1

Caution: Before starting the import of Support Packages at a given level, you must make sure that the JSPM has at least the same level.

Figure 203: Single Support Package: Select Package Type, Specify Queue

In the next step, you specify the queue by choosing the required SP level or skip (do not import) for each software component. In the case of modified software components and systems monitored by NWDI, there is also the setting , Modified by NWDI. JSPM now checks the validity of the deployment queue and outputs the status OK, WARNING or REVISE accordingly.

412

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Appendix: Importing Corrections with JSPM

Figure 204: Single Support Package: Check Queue

In the fourth step, deployment is started and the status of all the components changes to SCHEDULED or IN PROGRESS. In the last step, the final status is displayed (DEPLOYED, DEPLOYED WITH WARNINGS, NOT DEPLOYED, ERROR)

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

413

Unit 9: Patching SAP Systems

TADM12_1

Figure 205: Single Support Package: Deploy Queue, Completed

414

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Appendix: Importing Corrections with JSPM

Lesson Summary You should now be able to: • Call the Java Support Package Manager (JSPM). • Import Support Packages and Support Package Stacks for SAP NetWeaver AS Java 7.1x-based systems.

Related Information • • •

2013/Q1

SAP NetWeaver Support Package Stack Guide SAP Service Marketplace: Quick Link /sp-stacks

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

415

Unit 9: Patching SAP Systems

TADM12_1

Lesson: SAP Enhancement Packages Lesson Overview In this lesson you will learn about the concept of SAP enhancement packages.

Lesson Objectives After completing this lesson, you will be able to: •

Understand the concept of SAP enhancement packages

Business Example New functions are required for an existing SAP system. There are no plans for a complete SAP system upgrade. New functions are delivered in SAP enhancement packages.

SAP Enhancement Package In the past, new functions for an existing release were “hidden” in SAP Support Packages. This meant that SAP Support Packages did not just consist of legal changes and error corrections, but also imported new functions. However, not all new functions were delivered by SAP Support Package. The really “large” new functions were only available with a new release. Therefore, an SAP system upgrade was necessary every few years. An SAP system upgrade (for example, from SAP ECC 5.0 to SAP ECC 6.06) is a complete delivery of all software components in the new release. After the upgrade, the SAP system behaves according to the new release. Before it can be used in production operation you therefore need to make numerous adjustments. These include modification adjustments, delta customizing, delta developments for customer developments, and enhancements. The functional acceptance test is also very time-consuming. You normally need to allow a period of several months for an upgrade project of an SAP system landscape. An SAP system upgrade is thus quite expensive. To reduce the cost and effort involved, SAP is delivering SAP enhancement packages for all SAP solutions. This began with SAP ERP 6.0 in 2007. The current SAP ERP Enhancement Package in 2012 is Enhancement Package 6 for SAP ERP 6.0. SAP enhancement packages are complete deliveries of several software components of different SAP systems within one SAP solution. In other words, they are a partial upgrade of several SAP systems.

416

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: SAP Enhancement Packages

The Switch Framework is used to deliver the new functions in a “hidden” way. The Switch Framework allows changes to be made to repository objects without these changes becoming effective immediately. If you need to use the new functions, you have to activate these changes first. It is even possible to make various changes to a single repository object and activate the one individual changes required. Hint: The switch framework is only available in some AS ABAP-based SAP systems, AS ABAP 7.00 and higher, not in AS Java-based SAP systems. In some AS ABAP-based SAP systems, it is therefore possible to import parts of an SAP enhancement package without any immediate functional change. This means no further actions are necessary after the import, unlike a complete SAP system upgrade. In a second step you can activate the needed functions by activating Business Function sets (BC sets). As a result, the time needed for implementation and testing is kept to a minimum. Caution: In real live you always have to bind SAP Support Packages to the SAP enhancement package installation process. SAP Support Packages are not switchable. So you need to perform a complete regression test even if you do not activate any Business Function sets! Just as if you would import SAP Support Packages only. Hint: Therefor SAP recommends to supplement the applying of SAP Support Packages once a year by updating to the newest SAP enhancement package together with its corresponding SAP Support Packages.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

417

Unit 9: Patching SAP Systems

TADM12_1

Figure 206: SAP Enhancement Packages and Software Components

SAP enhancement packages are therefore an upgrade of individual software components with the advantage that the new functions can be activated when required. Note: Selective activation of business functions of an SAP enhancement package is only possible in certain AS ABAP-based SAP systems! The advantages of SAP enhancement packages are: • • • •

Simple adaptation to legal requirements Easier to maintain and plan Fewer complete SAP system upgrades necessary The new function can be activated as and when required (only possible in some AS ABAP-based SAP systems) Note: An SAP enhancement package not only delivers software components of an SAP system, but also different SAP systems of an application, for example SAP ERP.

As such, SAP Enhancement Package 6 for SAP ERP 6.0 contains some software components of an SAP ECC 6.06 system, and additional software components or content of an SAP NetWeaver Portal 7.03 system, and components of an SAP XSS 606 system. An SAP enhancement package can therefore include elements for various components in an application.

418

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: SAP Enhancement Packages

Since SAP enhancement packages are complete deliveries of the software components they contain, they are cumulative. This means that SAP Enhancement Package 6 for SAP ERP 6.0, for example, contains SAP Enhancement Package 5 for SAP ERP 6.0. SAP enhancement packages therefore do not need to be updated in a specific sequence (as is the case with SAP Support Packages). You can implement the latest SAP enhancement package directly (as is the case with an SAP system upgrade). The selected elements of an SAP enhancement package are imported with the Software Update Manager (SUM). Note: Importing elements of an SAP enhancement package causes a technical downtime comparable to the downtime of a complete SAP system upgrade. The project length and project costs are much lower, however, due to less testing effort. Hint: SAP Support Packages should always be selected corresponding to the release level of their software component. For example, if SAP_APPL is of release 606, and SAP_HR is of release 604, then you need to import release 606 SAP_APPL Support Packages and release 604 SAP_HR Support Packages. Hint: The SUM can also be used to import SAP Support Packages only! The effort and complexity is higher compared to importing SAP Support Packages with transaction SPAM. But the downtime is much shorter!

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

419

Unit 9: Patching SAP Systems

TADM12_1

Lesson Summary You should now be able to: • Understand the concept of SAP enhancement packages

Related Information SAP course ADM328 - SAP Enhancement Packages and SAP System Upgrade

420

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Unit Summary

Unit Summary You should now be able to: • List the most important software components in and around SAP systems that can be patched. • Apply different types of patches to software used by an SAP Solution Manager system • Explain how to apply a kernel patch • Explain how to apply a SAP Support Package for AS ABAP based SAP systems • Explain how to apply a SAP Support Package for AS Java based SAP systems • Explain what an SAP Support Package Stack is • Describe the concept of SAP Notes and SAP Support Packages • Explain the functions of the Maintenance Optimizer (MOpz) • Describe and execute a maintenance transaction • Explain the concept of maintenance certificates • Explain the use of the Support Package Manager and import a SPAM/SAINT update. • Import SAP Support Packages with transaction SPAM • Provide a explanation of the import process for SAP Support Packages • Describe the relationship between Support Packages, Patches, Support Package Stacks and Support Packages with Patchs • Describe the relationship between Product Version, Product Instance, Software Component and Support Package • Call the Software Update Manager (SUM) • Import Support Packages and Support Package Stacks for SAP NetWeaver AS Java 7.3x-based systems. • Call the Java Support Package Manager (JSPM). • Import Support Packages and Support Package Stacks for SAP NetWeaver AS Java 7.1x-based systems. • Understand the concept of SAP enhancement packages

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

421

Unit Summary

422

TADM12_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Test Your Knowledge

Test Your Knowledge 1.

What are the steps to manually apply a kernel patch?

2.

For what purpose are SAP Support Packages used? Choose the correct answer(s).

3.

□ □

A B

□

C

□ □

D E

To enter user data. To import SAP objects to keep the SAP system at the latest maintenance level. To implement adjustments in the SAP system due to changes in legal requirements. To transport programs developed by the customer. To import all the transport requests that SAP makes available on the SAP Service Marketplace.

What can be done with a maintenance transaction? Choose the correct answer(s).

□ □ □ □ □ 4.

A B C D E

Import Support Packages. Calculate Support Package Stacks for your SAP systems. Approve objects in your download basket. Import SAP Notes. Import SAP enhancement packages

You always have to import all available SPAM/SAINT updates in order, since they build up on one another. Determine whether this statement is true or false.

□ □ 5.

True False

The queue for importing the SPAM/SAINT update must be confirmed manually. Determine whether this statement is true or false.

□ □

2013/Q1

True False

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

423

Test Your Knowledge

6.

TADM12_1

A prerequisite for importing a SPAM/SAINT update is that the SAP system must not have any terminated import procedures for SAP Support Packages. Determine whether this statement is true or false.

□ □ 7.

True False

SAP Support Packages can be imported in any order. Determine whether this statement is true or false.

□ □ 8.

True False

SAP enhancement packages are imported in order to implement new functions. For these new functions to be effective in an SAP ECC system, they must be . Fill in the blanks to complete the sentence.

424

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Test Your Knowledge

Answers 1.

What are the steps to manually apply a kernel patch? Answer: 1. 2. 3.

2.

Stop the SAP system (Windows OS: including Windows services). Copy and paste the kernel patch to the central kernel directory. Start the SAP system (Windows OS: first start the Windows services).

For what purpose are SAP Support Packages used? Answer: B, C SAP Support Packages are not used to enter user data. Customer developments are transported to other SAP systems using transport requests. Transport requests from SAP are imported with the Transport Management System (TMS).

3.

What can be done with a maintenance transaction? Answer: B, C A maintenance transaction can not import SAP Notes, Support Packages and SAP enhancement packages. SAP Notes are imported via the Note Assistant, Support Packages for AS ABAP based systems via transaction SPAM, Support Packages for AS Java based systems via tool JSPM, SAP enhancement packages via the tool SAPehpi.

4.

You always have to import all available SPAM/SAINT updates in order, since they build up on one another. Answer: False The SPAM/SAINT update is a 100% delivery of the transactions SPAM and SAINT. It is therefore not necessary to follow any particular order.

5.

The queue for importing the SPAM/SAINT update must be confirmed manually. Answer: False It is neither necessary to define a special queue, nor to confirm this non-existent queue.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

425

Test Your Knowledge

6.

TADM12_1

A prerequisite for importing a SPAM/SAINT update is that the SAP system must not have any terminated import procedures for SAP Support Packages. Answer: True This is true, the SAP system must not have any terminated import procedures for SAP Support Packages.

7.

SAP Support Packages can be imported in any order. Answer: False SAP Support Packages must be imported in ascending order, without any gaps.

8.

SAP enhancement packages are imported in order to implement new functions. For these new functions to be effective in an SAP ECC system, they must be activated. Answer: activated Importing elements of an SAP enhancement package in an SAP ECC systems does not change the existing function until activation.

426

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

Unit 10 Output Management Unit Overview In this unit, you learn about the output processing architecture in the SAP system. You learn how to define printers and spool servers in the system and how to manage spool and output requests. You also learn how to set up central printer administration. Caution: This unit (and the following units) takes place on the SAP systems named DCC, QCC, PCC and PSM. The activities in these units are not using the freshly installed SAP systems S00, E00 and X00. This is necessary, because configuring the newly installed SAP systems in such a way that the related exercises can take place would require significant work before you could start the actual exercises. If you like, you can shut down the freshly installed SAP systems S00, E00 and X00. It is necessary, that you start the SAP systems DCC, QCC, PCC and PSM before proceeding with this unit.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • •

Describe the architecture and data flow of output processing in ABAP-based SAP systems Create output devices and spool servers in the SAP system List important access methods Describe the concept of logical spool servers Set up logical spool servers Manage spool requests and output requests Name the prerequisites for using the Printing Assistant for Landscapes (PAL) Explain the terms in the PAL environment Set up and use a PAL landscape

Unit Contents Lesson: Configuring Printers in AS ABAP ...................................429

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

427

Unit 10: Output Management

TADM12_1

Exercise 16: Configure Printers ..........................................443 Lesson: Concept of Logical Spool Servers ..................................455 Exercise 17: Logical Spool Servers ......................................463 Lesson: Managing Spool Requests ..........................................467 Exercise 18: Managing Spool Requests ................................473 Lesson: Printing Assistant for Landscapes (PAL) ..........................476 Exercise 19: Central Administration of Output Devices (PAL)........483

428

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Lesson: Configuring Printers in AS ABAP Lesson Overview In this lesson, you will learn about the output processing architecture. You will learn how to set up output devices (printers) in the SAP system.

Lesson Objectives After completing this lesson, you will be able to: • • •

Describe the architecture and data flow of output processing in ABAP-based SAP systems Create output devices and spool servers in the SAP system List important access methods

Business Example The administrator sets up output devices in the SAP system and monitors the output of spool requests.

Printing from SAP Systems There are various document classes in the SAP system (such as report lists, SAPscript or SAP Smart Forms documents). Although the way in which documents are created may be completely different, the output on paper is always performed using the same mechanism in two steps: •

•

2013/Q1

First a spool request is created. The spool request contains device-independent print data and includes administrative information (such as author, date, number of copies) and the actual print data. Only when the spool request is to be output on a particular device is an output request created. The device-independent print data from the spool request is converted to the printer language that the selected output device understands.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

429

Unit 10: Output Management

TADM12_1

Figure 207: Data Flow During Printing

This procedure allows the user to display a spool request before output. There can also be several output requests for one spool request. This can avoid the user having to recreate (possibly with a great deal of effort) a spool request, if, for example, the toner in a printer is exhausted, or the wrong paper was in the tray. The user can of course create a spool request and an output request at the same time (immediate print) by choosing the Print out immediately option. The actual document content of a spool request is stored in TemSe (for temporary sequential objects), for which you define the storage location with the profile parameter rspo/store_location. • •

Value db (the default value): Spool requests are stored in database table TST03 (advantage: backup as part of the database). Value G: Storage at operating system level in the (global) directory /usr/sap//sys/global (advantage: performance).

SAP Note 20176 – Where is the spool request saved? contains additional possible values for rspo/store_location. Note: You can also specify the storage location individually for each output device in transaction SPAD (enter the list or the details of output device and choose the menu path Edit → Data Storage).

430

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Creating an output request prompts the SAP spool system to send a (usually) printer-dependent, completely formatted data stream to a printer through an operating system spooler (OS spool). This means that the addressed printer model must be known to the SAP system. Definitions of printer types in the SAP system are described as device types. If a printer cannot be controlled at operating system level, it cannot be used from the SAP system, either. There are several ways in which a spool work process can reach an operating system spooler. The most important of these connections, described as access methods, are introduced in the following sections.

Local Printing

Figure 208: Local Printing

In local printing, the spool work process and operating system spool run on the same host. It is irrelevant whether the printer is directly connected to this host, or is reached over a network (and possibly another print server). The spool work process passes on its data locally, that is on the same host. •

•

On UNIX systems, the print data with access method L is output using operating system methods (for example, with the commands lp or lpr). The specific syntax is stored in profile parameters (see SAP Note 15355 – Command line parameter for access type L). Under Microsoft Windows, the data with access method C is passed directly to the operating system print API.

Local printing is the fastest and most reliable connection from the SAP system to the operating system spooler. As soon as the spool work process has transferred its data, it can deal with new output requests, even if the operating system spooler is still occupied.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

431

Unit 10: Output Management

TADM12_1

You can configure multiple spool work processes for an SAP instance. Regardless of the access method, this affects the output sequence: Different spool requests for the same printer may be printed in a different order to that in which they were created. If you require output in sequence, you can specify this for individual printers. However, a setting of this type reduces the ability to process printouts in parallel. For more information about this topic, see SAP Note 108799 – How many spool work processes for each instance?

Remote Printing With remote printing, the spool work process and operating system spooler run on different hosts. In the same way as with local printing, it is irrelevant from the SAP system's point of view whether the printer is directly connected to the remote host, or is reached using a network connection.

Figure 209: Remote Printing

432

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Typical scenarios for remote printing are: •

•

•

Network printers provide their own operating system spoolers, and are directly connected to a computer network. Printers of this type are directly addressed from the SAP system using their names (access method U). Access method U is also used if the remote host is a UNIX system. SAP Note 39405 – Print on UNIX LPD: Malformed Address describes how access method U can be used for the various UNIX versions. SAP provides the SAPSprint program for all hosts running on Microsoft Windows operating systems. SAPSprint is a Windows service capable of multi-threading. Each output request is processed in a separate, isolated thread. The output requests that SAPSprint receives from the SAP system can thus be transferred to a particular printer individually. If the printer is not working, this does not disturb the printing of other output requests on the other printers. Access method S is usually used here (SAP protocol), but access method U (UNIX Berkeley protocol BSD) is also supported.

For performance reasons, you should only use remote printing in a LAN environment (not WAN), and ensure that the operating system spoolers are available.

Front-end Printing SAP users can output documents on their local printers using front-end printing. These local printers do not need to be individually defined in the SAP system. Rather the system administrator only needs to create a representative output device for each operating system platform.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

433

Unit 10: Output Management

TADM12_1

Figure 210: Front-end Printing with Control Technology (Access Method G)

As of SAP Basis Release 4.6C, a new procedure is available for front-end printing: front-end printing using control technology with access method G. Controls are DLLs that run in the process context of the SAP GUI. The new print control receives the print data and transfers it to the printing system for the operating system (OS spool). Note: In contrast to previous front-end printing with access method F, front-end printing with control technology and access method G offers the advantage that front-end printing using SAP GUI for Java can be set up irrespective of the platform. Printing using the Windows Terminal Server is also made easier with front-end printing using control technology. SAP Note 821519 – Front-end printing with control technology contains useful information about front-end printing using control technology including the exact system requirements. Additional options can be found in SAP Note 1149136 – Options for front-end printing (access method G). The processing of front-end printing is also performed, as with the other output methods, using a spool work process. There can, therefore, be conflicts between regular and front-end print requests. The profile parameter rdisp/wp_no_spo_Fro_max allows you to define the maximum number of spool work process for front-end printing for each SAP instance (the standard value is 1).

434

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Front-end printing is suitable for output on local printers; however, it is not for production or mass printing. However, this method cannot be used for the printing of lists in background processing: front-end printing requires a connection to the front-end PC. For more information, see SAP Composite Note 128105 – Front-end printing (collective note). SAP Note 771683 – Front-end printing for SAP GUI for HTML (as of Release 6.40) describes front-end printing with the integrated ITS (for SAP systems as of AS ABAP 6.40) when using the SAP GUI for HTML. SAP Note 150533 – Printing in Windows Terminal Server (WTS) finally contains information about front-end printing when using Windows Terminal Server. If you are using the SAP GUI for HTML and want to print on your front end, this is also possible through access method G. The print data is sent to the browser and displayed using this print method. You can then print the document on your front end. SAP recommends that you configure at least one spool work process on each application server that (end) users log onto. If no work process is running on the application server that a user wants to use for front-end printing, the system selects that available spool server to process the print request which shows the least load. You can define a spool server specifically for front-end printing by setting the profile parameter rspo/local_print/server to the required server name.

Creating Output Devices The configuration of the spool system is a system administration task. The central tool for this is transaction SPAD (menu path Tools → CCMS → Print → Spool Administration). Creating Output Devices Local

Device Device Type Attributes Spool Server Access Method

2013/Q1

Remote



Host Spool L (Unix) Access Method C (Windows)

S or U

Front end (Microsoft Windows) SWIN – G

Host Printer



__DEFAULT

Host

fix

–

–

Destination Host

–



–

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

435

Unit 10: Output Management

TADM12_1

With front-end printing with control technology (access method G), the printer is given a generic name in the SAP system, and (for Microsoft Windows front ends) is assigned to the physical device __DEFAULT (starting with 2 underscores). Since the models used as front-end printers can vary considerably, the device type SWIN is often assigned for Microsoft Windows front ends. When printing with SAP GUI for Java on other operating systems, you have to use a corresponding device type, such as POST2 (for PostScript) or PDF1. If you are using SAP GUI for HTML for front-end printing, the device type PDF1 is suitable. The print data is then transferred to the front-end browser as a PDF document, and can be printed locally. Output Devices for Front-end Printing SAP GUI for Windows

SAP GUI for Java

SAP GUI for HTML

SWIN



PDF1

Host Spool Access G Method

G

G

Host Printer





Device Type

__DEFAULT

To create an output device, call transaction SPAD. On the the Devices / Servers tab page choose Display in the Output Devices line. If there are a large number of devices in your system already, you can restrict the output list in the field next to the button (for example PR*). Important information for an output device: Output device Name in SAP system, maximum of 30 characters long (case-sensitive). Users in the SAP System use this name to select a particular output device. Short name For internal system purposes (can be automatically generated). Device type Printer model/family (more information about this below). The device type SWIN transfers the spool data from the SAP system to the Microsoft Windows printer driver. This is useful, for example, if various printers are used for front-end printing in a Microsoft Windows environment. Spool server SAP application server with spool work processes or logical server. Location For example, building and room number (so that users can find their output).

436

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Message Used to temporarily override the text in the location field (for example “Is currently in maintenance”). Lock printer in SAP system Output requests for printers for which this indicator is selected are created but not transferred to the printer. The user receives the message ...no immediate printing. Host spool access method Specifies how the spool work process transfers data to the host spool system (OS spooler) for this printer. Host printer Name of the printer at operating system level (in the host system). Note that this name is case-sensitive. Under Microsoft Windows, there must not be a space in the printer name, and network printers are addressed using their UNC names (in the format \\R12345\P42). The entry __DEFAULT (starting with two underscores) controls the Windows default printer (for front-end printing using SAP GUI for Windows). Host name Only for local printing, is calculated automatically from the spool server. Destination host Only for remote printing. Name of the host on which the operating system spooler is running and which receives the data for output.

Device Types A device type indicates the type of the printer in question. The SAP system uses a device type to format the output device-specific print output. Hint: When reference is made to an output device in the SAP environment, it does not necessarily mean a printer. An output device can also be, for example, an Output Management System or an archiving system. When the spool work process generates an output request, it uses the specifications of the device type. That is, the device type describes how print data should be formatted for a particular output device. You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. The following figure illustrates how a device type is created.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

437

Unit 10: Output Management

TADM12_1

Figure 211: What Is a Device Type?

The following list explains the terms from the above graphic: Page format A page format describes the format of a printable page in the SAP system. A large number of standard page formats are predefined in the system. If a device is to support additional format that are not delivered, you can define new formats. Consider when doing so that your output device must, of course, be able to use the new format. Format type A format type describes how output should appear on paper. It primarily contains the page format. Format A format is a device-specific implementation of a format type. That is, the SAP system can use the description in a format to control a device correctly to, for example, perform an output on a page with the Letter format. A format type is therefore not device-specific; the format, on the other hand, is a device-specific implementation of a format type. Character set A character set contains the characters that can be output by a particular output device. That is, to be able to use a particular character set for a selected printer model in the SAP environment, the device type assigned to this printer model must contain this character set.

438

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Print control Print controls allow the control of particular display options of output devices, such as boldface, changing the font size, changing the font, and so on. Print controls use device-specific control character sequences. That is, to create a new device type, the display options offered in the SAP system must be stored with the control character sequences that the selected printer model supports. The control character sequences to be used can be found in the device vendor's documentation. You can find additional information on device types in the online documentation for SAP NetWeaver 7.3 Including Enhancement Package 1 in the area SAP NetWeaver → Administration Information → Technical Operations for SAP NetWeaver → (Link to) Administration of Application Server ABAP → SAP Printing Guide (BC-CCM-PRN) → Device Types for SAP Output Devices (Detail Information). You can see that using devices for which no suitable device type exists in the SAP system may mean a significant effort.

Figure 212: Selecting an Appropriate Device Type

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

439

Unit 10: Output Management

TADM12_1

How do you assign the correct device type to your printer? •

•

•

•

•

In the ideal situation, there is already a device type in your SAP system. Note that a separate device type is not required for every printer model of a vendor, but just for each model family. Several printer manufacturers participate in the SAP Printer Vendor Program. It is easy to import the corresponding device types for the supported printer models using the Wizard (available in transaction SPAD for output devices). For many printers, you can use a generic format (such as PostScript) for which device types exist. It is also possible that your printer can be addressed in the same way as another model that is supported by SAP (compatibility mode). There are drivers for the Microsoft Windows operating systems for practically all printers on the market. You can use these printers as output devices with device type SWIN. The conversion to a print data stream is performed by the Microsoft Windows driver in this case. The SAP system contains all of the tools required to create your own device types or to adjust copies of existing device types. Detailed knowledge of the SAP spool system and the printer control are required to do this. You should weigh up the expense against the purchase of supported printers.

Device Type Wizard The following figure shows a roadmap with the major steps if you want to create an output device in your SAP system for output devices which are supported by the SAP Printer Vendor Program:

440

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Figure 213: Roadmap: Using the Device Type Wizard

To start the Device Type Wizard, launch transaction SPAD and navigate to the list of Output Devices. Double-click an existing ouput device, or create a new one. On the tab Device Attributes you will find a button Device Type Selection (icon with magic wand). The major steps are: 1. 2. 3. 4. 5. 6. 7.

Within the Device Type Wizard, check if your printer shows up in the list of known printers. If necessary, download the attachment tspopi-.zip from SAP Note 1036961 – Device type selection wizard in transaction SPAD. Unzip that file and import the XML file tspopi-.xml into the Device Type Wizard. Find and double-click the printer in question in the Device Type Wizard. In case of status “device type not exist on the system”, open the SAP Note for that device. Using the Device Type Wizard, download the SAP Note for the printer in question. Within the Device Type Wizard, import the proper SAP Note for your printer.

Now you can either create new ouput devices (or change exising ones) which make use of the new device type.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

441

Unit 10: Output Management

442

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM12_1

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Exercise 16: Configure Printers Exercise Objectives After completing this exercise, you will be able to: • Create output devices in the SAP system

Business Example The administrator sets up printers in the SAP system.

Task 1: Check the Print Environment First check the print environment of your SAP system. 1.

How many spool work processes are set up for the application server to which you are currently logged on?

2.

How many spool work processes are configured in your entire SAP system?

3.

How many spool servers are available in your SAP system?

4.

As the default setting for your SAP user, change the settings so that an output request is not created immediately for a spool request.

5.

Which printers are defined at operating system level of your server? Where do they print?

6.

(If possible) Which printers are defined at operating system level of your front-end PC in the training room? Where do they print to?

Task 2: Local Printing Create an output device with a local host spool access method. 1.

In your SAP system, create a local output device Local## with the short name LO## (where ## denotes your group number) that controls one of the previously defined printers.

2.

Output any list (Suggestion: All profile parameters that begin with “rspo”) without immediate printing on the output device Local##.

3.

Check your output.

4.

Optional: Display the generated print data.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

443

Unit 10: Output Management

TADM12_1

Task 3: Remote Printing Install SAPSprint, and create an output device with a remote host spool access method. 1.

Install and start SAPSprint on your server. Caution: This exercise section should only be performed once for each host: Please coordinate with your partner group(s) who should perform this exercise.

2.

In the SAP system, create a remote output device Remote## with the short name RE## that controls a printer on a remote server. Note: These exercise sections should be performed by both participants groups again.

3.

Change the default setting for your SAP user so that an output request is created immediately for a spool request.

4.

Print the list of work processes (transaction SM50) with immediate printing on the output device Remote##.

5.

Check your output.

Task 4: Front-End Printing Create an output device for front-end printing with the SAP GUI for Windows. 1.

In the SAP system, create a front-end output device Frontend## with the short name FR## that controls the default printer of a Microsoft Windows front-end PC (## denotes your group number).

2.

Print the list of work processes (transaction SM50) with immediate printing on the output device Frontend##.

Task 5: Optional: Web Printing Create an output device for front-end printing with the SAP GUI for HTML.

444

1.

Create a copy of the output device Frontend## you created before and name this device Webprint## with the short name WP## (## denotes your group number). Change the device type to PDF1.

2.

Log on to the SAP GUI for HTML with your course user -##.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Solution 16: Configure Printers Task 1: Check the Print Environment First check the print environment of your SAP system. 1.

2.

How many spool work processes are set up for the application server to which you are currently logged on? a)

Logon to the training system that is assigned to you.

b)

Call transaction SM50, and count the number of work processes of type SPO.

How many spool work processes are configured in your entire SAP system? a)

Start transaction SM66. If you do not see any work processes at first, choose Select process and also select wait in the Status area. Hint: The number of spool work processes cannot be changed by operation mode switches.

3.

How many spool servers are available in your SAP system? a)

4.

A (real) spool server is an SAP application server with at least one spool work process. You can display this information with transaction SM51 more easily than with transaction SM66: All application servers that provide the service Spool (column Message Types) are spool servers.

As the default setting for your SAP user, change the settings so that an output request is not created immediately for a spool request. a)

To do this, choose System → User Profile → Own Data in the menu bar (transaction SU3) and enter the Defaults tab there. Ensure that Print Immediately is not checked and save your changes, if necessary. Hint: This default setting can be overridden with the settings in the print dialog screen at any time.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

445

Unit 10: Output Management

5.

TADM12_1

Which printers are defined at operating system level of your server? Where do they print? a)

Choose Start → Devices and Printers at the operating system level of your server. There should be printers (such as Printer1 for the group working on the DCC system, and Printer2 for the group working on the QCC system) that each print to a file. Hint: You can get the name of this file by double-clicking on the printer in question and then choosing Customize your Printer. Then switch to the Ports tab. Note: Printer Command Language (PCL) is a command language for controlling printers. It was developed by Hewlett-Packard to cotrol all printer types with the help of a command standard language. PCL 5 is used (among others) for HP (Color) Laserjets. In this training, Printer1 and Printer2 are used to control printing devices of type HP Laserjet 4.

6.

(If possible) Which printers are defined at operating system level of your front-end PC in the training room? Where do they print to? a)

If possible on your front-end PC, choose Start → Devices and Printers.

Continued on next page

446

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Task 2: Local Printing Create an output device with a local host spool access method. 1.

In your SAP system, create a local output device Local## with the short name LO## (where ## denotes your group number) that controls one of the previously defined printers. a)

In the SAP system, choose SAP Menu → Tools → CCMS → Print → Spool Administration (transaction SPAD).

b)

On the Devices / servers tab, choose the Display pushbutton in line Output Devices (leave the input field to the left empty).

c)

If you cannot see a Create pushbutton, choose Change to switch to change mode. Now create the output device Local## with the following specifications: • • •

Output Device: Local## Short name: LO## DeviceAttributes tab:

•

Device Type: Should match the previously determined printer (e.g. HPLJ4) – Spool Server: Any spool server from your system (use F4 help) – Location: Any text Access Method tab: –

– –

Host Spool Access Method: C for Windows Host printer: Name of the previously determined printer (Printer1 or Printer2)

Do not change the entries for the other fields and save your entries. 2.

Output any list (Suggestion: All profile parameters that begin with “rspo”) without immediate printing on the output device Local##. a)

To create the proposed list, call transaction RSPFPAR in your training system. Enter rspo* as Profile Parameters and choose Execute again.

b)

On the following screen select Print pushbutton. On the following popup choose the output device Local## (select it using the F4 help). Choose Continue (you may need to confirm another popup). In the status line you can see the message that the spool request was created without immediate output.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

447

Unit 10: Output Management

3.

4.

TADM12_1

Check your output. a)

Call transaction SP01. Enter the Spool requests tab and choose Execute. You get a list of your spool requests.

b)

Select your spool request and choose Print directly. As a result, an output request is created for this spool request.

Optional: Display the generated print data. a)

At operating system level, you can use Notepad for example (for this choose Start → Run... and then enter notepad) to view the file C:\temp\Printer1.txt or C:\temp\Printer2.txt respectively (you may want to use File → Open... for this). Note that Notepad cannot display all printer-specific control characters.

Task 3: Remote Printing Install SAPSprint, and create an output device with a remote host spool access method. 1.

Install and start SAPSprint on your server. Caution: This exercise section should only be performed once for each host: Please coordinate with your partner group(s) who should perform this exercise. a)

On your server, navigate to the directory S:\Courses\ADM100_99\SAPSprint.

b)

Using a double-click, start the most recent installation program listed (naming convention xSPrint_.exe). You may need to confirm a popup with Run.

c)

Run through the installation (and be sure to select SAP Print Service for installation). Retain the default values for all other prompts.

d)

Optional: You can use the Windows Service Manager to verify that a SAPSprint has been created and started as a Windows service.

Continued on next page

448

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

2.

In the SAP system, create a remote output device Remote## with the short name RE## that controls a printer on a remote server. Note: These exercise sections should be performed by both participants groups again. a)

In the SAP system, choose Tools → CCMS → Print → Spool Administration (transaction SPAD).

b)

On the Devices / servers tab, choose the Display pushbutton in line Output Devices (leave the input field to the left empty).

c)

If you cannot see a Create pushbutton, choose Change to switch to change mode. Now create the output device Remote## with the following specifications: • • •

Output Device: Remote## Short name: RE## DeviceAttributes tab:

•

Device Type: Should match the previously determined printer (HPLJ4) – Spool Server: Any spool server from your system (use F4 help) – Location: Any text Access Method tab: –

– – –

Host Spool Access Method: S for the SAP printing protocol Host printer: Name of the previously determined printer (Printer1 or Printer2) Destination Host: twdf****.wdf.sap.corp (where twdf**** should be replaced with the host name on which SAPSprint was installed)

Do not change the default values for the other values and save your entries. 3.

Change the default setting for your SAP user so that an output request is created immediately for a spool request. a)

In the menu bar, choose System → User Profile → Own Data (transaction SU3), and choose the tab Defaults. Ensure that Print immed. is checked (in the Spool Control area) and save your changes. Hint: This default setting can be overridden with the settings in the print dialog screen at any time. Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

449

Unit 10: Output Management

4.

TADM12_1

Print the list of work processes (transaction SM50) with immediate printing on the output device Remote##. a)

In your training system enter transaction SM50.

b)

Choose Print. On the following popup choose the output device Remote## by using the value help for this field.

c)

Choose Properties (you many need to confirm a popup concerning the formatting). Check that in the General Properties area the parameter Time of printing is set to Print out immediately. Choose Continue. Hint: By choosing Show Selected Print Parameters on Initial Screen in the Properties window, you can maintain some parameters directly on the print dialog box in future.

d) 5.

Start the creation of the spool request and the output request by choosing Continue on the Print ALV List screen.

Check your output. a)

Call transaction SP01. Make sure that your are on the Spool requests tab and choose Execute.

b)

You get a list of your spool requests. Select the line of the newly created spool request and choose Output requests.

c)

In the list of output request mark the newly created output request and choose Display contents.

Continued on next page

450

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

Task 4: Front-End Printing Create an output device for front-end printing with the SAP GUI for Windows. 1.

In the SAP system, create a front-end output device Frontend## with the short name FR## that controls the default printer of a Microsoft Windows front-end PC (## denotes your group number). a)

In the SAP system, choose Tools → CCMS → Print → Spool Administration (transaction SPAD).

b)

On the Devices / servers tab, in line Output Devices choose the Display pushbutton (leave the input field to the left empty).

c)

If you cannot find the Create pushbutton, choose Change to switch to change mode. Now create the output device Frontend## with the following specifications: • • •

Output Device: Frontend## Short name: FR## DeviceAttributes tab:

•

– Device Type: SWIN – Location: here Access Method tab: – –

Host Spool Access Method: G Host Printer: _ _DEFAULT (without spaces between the two underscores)

Do not change the default values for the other values and save your entries.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

451

Unit 10: Output Management

2.

TADM12_1

Print the list of work processes (transaction SM50) with immediate printing on the output device Frontend##. a)

In your training system enter transaction SM50.

b)

Choose Print. On the following popup choose the output device Frontend## by using the value help for this field.

c)

Choose Properties (you many need to confirm a popup concerning the formatting). Check that in the General Properties area the parameter Time of printing is set to Print out immediately. Choose Continue.

d)

Start the creation of the spool request and the output request by choosing Continue on the Print ALV List popup.

e)

Call transaction SP01. Make sure that your are on the Spool requests tab and choose Execute.

f)

You get a list of your spool requests. Select the line of the newly created spool request and choose Output requests.

g)

In the list of output request mark the newly created output request and choose Display contents.

Task 5: Optional: Web Printing Create an output device for front-end printing with the SAP GUI for HTML. 1.

Create a copy of the output device Frontend## you created before and name this device Webprint## with the short name WP## (## denotes your group number). Change the device type to PDF1. a)

In the SAP system, choose Tools → CCMS → Print → Spool Administration (transaction SPAD).

b)

On the Devices / servers tab, choose the Display pushbutton in the Output Devices line (leave the input field to the left empty).

c)

If you cannot find the Create pushbutton, choose Change to switch to change mode.

d)

Select the line for the output device Frontend##, and choose the pushbutton Create using template.

e)

Enter Webprint## as the name of the new output device. Change the short name to WP## (## denotes your group number). On the DeviceAttributes tab, change the field Device Type to PDF1. Save the output device without further changes.

Continued on next page

452

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Configuring Printers in AS ABAP

2.

Log on to the SAP GUI for HTML with your course user -##. a)

Enter the following URL in your web browser directly: http://twdfSSSS.wdf.sap.corp:/sap/bc/gui/sap/its/webgui (twdfSSSS denotes the host name of the training system that is assigned to you). Hint: You can determine the ICM HTTP port (of the ICM of the instance to which you are currently connected) in transaction SMICM by choosing Goto → Parameters → Display – the standard value is 80$$, where $$ denotes the instance number.

b)

In your web browser, log on to the SAP system with your course user -## (you may need to confirm a popup).

c)

Send any list to the output device Webprint## for immediate printing. Hint: You can view the print dialog box in Menu → List → Print. It might take a few seconds until the generated PDF document is displayed in a new browser window. Maybe you need to start the print dialog again.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

453

Unit 10: Output Management

TADM12_1

Lesson Summary You should now be able to: • Describe the architecture and data flow of output processing in ABAP-based SAP systems • Create output devices and spool servers in the SAP system • List important access methods

Related Information •

•

Online documentation for SAP NetWeaver Including Enhancement Package 1, path SAP NetWeaver → Administration Information → Technical Operations for SAP NetWeaver → (Link to) Administration of Application Server ABAP → SAP Printing Guide (BC-CCM-PRN). SAP Notes 118057: Flexible Configuration of the Spool Service 19706: Tuning the Spooler 128105: Frontend printing (collective note) 150533: Printing in Windows Terminal Server (WTS) 1130927: SAP Printer Vendor Program 1100779: Participants in the SAP Printer Vendor Program 1097990: List of Printer Vendor Wizard Notes

•

454

1036961: Device type selection wizard in transaction SPAD SAP Community Network, Quick Link /output-management (http://scn.sap.com/community/output-management)

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Concept of Logical Spool Servers

Lesson: Concept of Logical Spool Servers Lesson Overview In this lesson, you will learn about the concept of logical spool servers, and how to set them up.

Lesson Objectives After completing this lesson, you will be able to: • •

Describe the concept of logical spool servers Set up logical spool servers

Business Example You want to set up logical spool servers in your AS ABAP based SAP system because of load balancing and safeguarding against failure.

Concept of Logical Spool Servers The SAP printing concept introduced up to now envisages a fixed assignment of an output device to a spool server. A spool server, on the other hand, can be assigned multiple output devices, which raises the risk of this server becoming overloaded. Therefore it is desirable to have a mechanisms for load balancing across multiple servers. It is also advisable to set up groups of spool servers (also known as “logical spool servers” or – for short – “logical servers”) to ensure reliability. Both aspects are considered in this introduction to logical spool servers. Hint: Include logical servers from the outset when planning your printer landscape. When scaling your SAP system later (additional instances with spool work processes), logical spool servers make it easier to adapt the printer landscape.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

455

Unit 10: Output Management

TADM12_1

Figure 214: Logical Spool Server: Concept

A (real) spool server is an SAP application server with at least one spool work process. Every output request is processed on a “real” spool server of this type. An output device created in the SAP system can be assigned a real spool server directly. However, there are many advantages associated with an additional logical layer between the output device and the spool server. You can use logical (spool) servers for this purpose. These stand for a hierarchy of other logical servers and/or “real” spool servers.

Creating a Logical Spool Server You can maintain the spool server in transaction SPAD on the Devices / Servers tab page in theSpool Servers area. Important information for a spool server: Server Name Name of the spool server, maximum of 20 characters (case-sensitive). The field below is intended for a short description. Server Class Classify the spool server here (for example, for mass printing). Logical Server Select this field when you create a logical server. Allow Load Balancing You use this field to control which method the system uses to determine a spool server for processing of output requests. If this field is selected, the system searches for the server with the lowest load in the hierarchy of logical and alternative servers you defined.

456

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Concept of Logical Spool Servers

Alternative Server The server that should be used if the specified server is down or not available. Mapping Name of a real or logical server to which this logical server refers. Additional information is presented below.

Figure 215: Creating a Logical Server

Hint: If you expect a significant workload due to front-end printing, you should configure at least one additional spool work process for each front-end printing spool server for other tasks. You can classify output devices and spool servers, for example, for test printing or production printing. To classify an output device, select it (in transaction SPAD under Output Devices) and choose the menu path Edit → Classification. The SAP system checks the classifications when saving, and displays a warning message if there are deviations. For example, the system warns you if you attempt to assign a high volume printer to a production print server.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

457

Unit 10: Output Management

TADM12_1

Advantages of Logical Spool Servers Safeguarding Against Failure When creating a spool server (either a logical server or a real spool server), you can specify an alternative server. If the normal server is not available, the SAP system attempts to use this alternative.

Figure 216: Safeguarding Against Failure

You must ensure that all output devices that may be used by a different spool server can be controlled in the same way by every spool server. For example, if the output device Test 1 in the above example points at operating system level to a printer P42 that is controlled locally, an operating system printer P42 must be available on servers twdf5000 and twdf5001. You cannot define more than two spool servers for a logical server. Since a logical server can itself reference logical servers, extensive spool server hierarchies are also possible.

Load Balancing You can allow load balancing for every spool server with an alternative server (to do this, select the field Allow Load Balancing). The load of a spool server is calculated from the number of spool work processes, output requests, and printed pages.

458

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Concept of Logical Spool Servers

Figure 217: Load Balancing

For an output request for a spool server with load balancing (this setting can be made for logical servers and real spool servers), the system determines the server with the smallest load. The algorithm is recursive: The same selection criteria are used on the mapping and the alternative server (both could be logical servers themselves). Note: Sequential request processing (property of an output device) has priority over the load balancing shown here (property of a spool server). This means that output requests for an output device with sequential request processing would not be distributed in accordance with the current load, although assigned to a spool server with load balancing.

Transporting the Print Landscape The concept of logical servers supports you when defining a consistent, transportable print landscape. Unlike real spool servers, logical servers can have the same name in various SAP systems. In this way, you can define a consistent SAP print architecture in the development system and then transport it to other systems. After the transport, all you need to do is adjust the mapping of the logical servers to the real spool servers of the new system.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

459

Unit 10: Output Management

TADM12_1

Figure 218: Transporting the Print Landscape

There are functions for the manual transport of output devices and logical spool servers in transaction SPAD. Note: Note that with the help of Printing Assistance for Landscape (transaction PAL) there is another option to distribute output devices within an SAP system landscape.

460

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Concept of Logical Spool Servers

Planning the SAP Print Architecture You should plan especially carefully if you want to print time-critical documents (for example delivery notes; if these are note added to the delivery, the product cannot be sent) or if you want to print large print requests (for example long monthly lists). 1.

Determine the most important print requirements. To do this, answer the following questions: • • •

2.

Who prints time-critical documents, such as delivery notes? Who prints large documents, such as ABAP list reports? What is the expected total quantity of output requests that will occur in your SAP System? Using the print requirements, determine how important the respective printers are. Important printers are, for example, printers whose output is time-critical. You should consider the following points: •

3.

4.

2013/Q1

Can the existing printers handle the expected print workload, or should you purchase additional output devices? • Would a faster line printer be able to speed up printing of long lists yet provide the print quality you require? • Would a central print department be more cost-effective than setting up small line printers in individual departments? Optional: Classify the printers: Although classifying printers is optional, it provides this advantage: If you also classify your spool servers, the spool system checks that the device and server classifications match. This helps to ensure an optimal output configuration. Assign every print group to one or more spool servers, if you have set up three or more spool servers in your SAP System.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

461

Unit 10: Output Management

462

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM12_1

2013/Q1

TADM12_1

Lesson: Concept of Logical Spool Servers

Exercise 17: Logical Spool Servers Exercise Objectives After completing this exercise, you will be able to: • Set up logical servers and assign output devices.

Business Example You want to set up logical spool servers in your ABAP-based SAP system to ensure load balancing and reliability.

Task: Create a Logical Spool Server Create a logical spool server and assign an output request that already exists to this spool server.

2013/Q1

1.

Create a logical server Logical## (## denotes your group number). If possible, enter two different real spool servers as mapping and alternative servers and activate load balancing. Classify Logical## as a test server.

2.

Change the output device Local## so that the logical server Logical## is used as the spool server in future. Classify Local## as a test printer.

3.

Send any list to the printer Local## for immediate printing (suggestion: all profile parameters that begin with rspo).

4.

Check your output. Which real spool server was used?

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

463

Unit 10: Output Management

TADM12_1

Solution 17: Logical Spool Servers Task: Create a Logical Spool Server Create a logical spool server and assign an output request that already exists to this spool server. 1.

Create a logical server Logical## (## denotes your group number). If possible, enter two different real spool servers as mapping and alternative servers and activate load balancing. Classify Logical## as a test server. a)

In the SAP system, choose Tools → CCMS → Print → Spool Administration (transaction SPAD).

b)

On the Devices / servers tab page, choose Display in line Spool Servers (leave the input field to the left empty).

c)

If you cannot see a Create pushbutton, choose Change to switch to change mode. Choose Create. Now create a logical server Logical## with the following settings and finally save your changes: • • • • • • •

2.

Server Name: Logical## (## denotes your group number) Description: Server class: T Logical Server: select this field Allow load balancing: select this field Mapping: Alt. server:

Change the output device Local## so that the logical server Logical## is used as the spool server in future. Classify Local## as a test printer. a)

Enter transaction SPAD. On the Devices / servers tab page choose the Display button in the Output Devices line (leave the input field at the left empty).

b)

By double-clicking on the output device Local##, you can edit your output device (switch to change mode if necessary). On the Device Attributes tab page, enter the logical spool server Logical## as the Spool Server. To classify the output device, choose the menu path Edit → Classification → Test print. Save your changes.

Continued on next page

464

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Concept of Logical Spool Servers

3.

Send any list to the printer Local## for immediate printing (suggestion: all profile parameters that begin with rspo). a)

To create the proposed list, call transaction RSPFPAR. Enter rspo* as Profile Parameters and choose Execute again.

b)

In the resulting list choose Print. Choose Local## as the output device (select it using the F4 help). Choose Continue without making any additional entries (you may need to confirm another popup). Hint: Settings from previous exercises may mean that Output Immediately is proposed as the time of printing. The user can make this (and other) settings in the print dialog box by choosing Properties.

4.

2013/Q1

Check your output. Which real spool server was used? a)

Enter transaction SP01. Switch to the Output requests tab and choose Execute.

b)

In the resulting list select your output request and choose Choose Detail. You can find the server name at the bottom of the list (Server Name line).

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

465

Unit 10: Output Management

TADM12_1

Lesson Summary You should now be able to: • Describe the concept of logical spool servers • Set up logical spool servers

Related Information •

•

466

SAP Library for SAP NetWeaver 7.3 Including Enhancement Package 1, area SAP NetWeaver → Administration Information → Technical Operations for SAP NetWeaver → (Link to) Administration of Application Server ABAP → SAP Printing Guide (BC-CCM-PRN) → Spool Server. SAP Note 118057: Flexible Configuration of the Spool Service

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Managing Spool Requests

Lesson: Managing Spool Requests Lesson Overview In this lesson, you will learn about managing spool and output requests.

Lesson Objectives After completing this lesson, you will be able to: •

Manage spool requests and output requests

Business Example As a spool administrator, you maintain the spool and output requests in your SAP system.

Managing Spool and Output Requests To maintain spool and output requests, call the Output Controller (transaction SP01 or choose System → Services → Output Controller). If you only want to check the status of your own spool requests, choose System → Own Spool Requests (transaction SP02).

Figure 219: Selecting Spool or Output Requests

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

467

Unit 10: Output Management

TADM12_1

Transaction SP01 provides many selection criteria for selecting particular spool or output requests. The Further selection criteria... function is simple to use and allows each user to define their own selection criteria.

Figure 220: Monitoring Spool and Output Requests

The displayed list shows all spool or output requests that match your selection criteria. The list is created using the SAP List Viewer (ALV). This allows you to change the appearance of the list as you desire. This means that you can show and hide columns, sort columns, or create variants. The following indicators specify the status of a spool request: Not yet sent to the operating system (no output request exists). + Spool request is just being created (stored in spool system). Waiting The output request has not yet been processed by the spool system. Waiting in host spooler The output request is to be sent or is being sent to the spool work process, or for formatting, in the host spool system. Processing A spool work process is formatting the output request for printing.

468

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Managing Spool Requests

Printing The request has been passed to the host spooler or to an output device, and a final status has not yet been returned to the SAP spool system. Complete The output request has been printed. If the query at the host spooler is not activated, the status changes to Compl. as soon as the output request is transferred to the host spooler. There are (at least two) output requests with various statuses. Problem Indicates an error not of a serious nature (such as incomplete character set). This request was still printed. Error Indicates a serious error (such as a network error). Time A particular time was specified for the output of the request by the request creator. Archive The spool request has been processed by the spool system and is waiting to be archived (for spool requests sent to an archiving device). If you double click the status of a spool request, the system displays the associated output requests. To view the output requests of multiple spool requests, select these and choose Output Requests (or choose F5). For every unsuccessful output request, a log is written that you can use for error analysis.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

469

Unit 10: Output Management

TADM12_1

Figure 221: Maintaining the Spool Database

The system administrator is responsible for regularly deleting old spool requests and monitoring the consistency of the spool database. To delete old spool requests, schedule the ABAP program RSPO1041 with an appropriate variant as a periodic job. For more information about the RSPO1041 program, see SAP Note 130978 – RSPO1041 - Replacement for RSPO0041. To check the consistency of the spool database, schedule the ABAP program RSPO1043 with an appropriate variant as a daily job. For more information about the RSPO1043 program, see SAP Note 98065 – Spool consistency check with RSPO1043 as of 4.0A. You can also start spool administration tools (in the dialog) in transaction SPAD in the Admin. tab page. However, the functions provided in transaction SPAD for deleting spool requests and running consistency checks are limited compared to the other programs available. For information about the reorganization of TemSe and spool, see also SAP Note 48400 – Reorganization of TemSe and Spool.

Appendix: Other Print Scenarios The following figure gives an overview of other print scenarios:

470

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Managing Spool Requests

Figure 222: Appendix: Other Print Scenarios

External Output Management Systems (OMS) can be addressed from the SAP system using a defined interface (BC-XOM) (access method E). This method is of particular interest if you have a very large volume, or the output of multiple systems (SAP systems and others) is to be centrally controlled and monitored. In addition you can send print output by e-mail to a user (access method M). The e-mail is sent using SAPconnect. For more information, see SAP Notes 311037 – Printing using e-mail and 513352 – Printing by e-mail (update). A user can also be connected to an SAP system from a web browser using SAP GUI for HTML. This type of connection can be set up in the SAP system with the integrated ITS as of AS ABAP 6.40. What options does this user have for print output? One option is the print output by e-mail as described above. The so called e-mail. Web printing on the other hand does not require an e-mail client. For this, the system administrator must set up an output device with device type PDF1 and the access method G. If the user selects this output device, a PDF document appears in a new browser window. The user can then print this PDF document locally. SAP Note 771683 – Front-end printing for SAP GUI for HTML (as of Release 6.40) describes the exact prerequisites and contains additional information about Web printing.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

471

Unit 10: Output Management

472

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM12_1

2013/Q1

TADM12_1

Lesson: Managing Spool Requests

Exercise 18: Managing Spool Requests Exercise Objectives After completing this exercise, you will be able to: • Manage spool and output requests

Business Example You want to delete unwanted spool requests from TemSe.

Task: Deleting spool requests Evaluate and delete spool requests.

2013/Q1

1.

Display all the spool requests you have created today.

2.

Run the report RSPO1041 (in the dialog) to delete all of your spool requests with successful output requests.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

473

Unit 10: Output Management

TADM12_1

Solution 18: Managing Spool Requests Task: Deleting spool requests Evaluate and delete spool requests. 1.

Display all the spool requests you have created today. a)

Choose System → Services → Output Control (transaction SP01).

b)

Restrict the output to your spool requests from today (this is the default selection (restricted to the current client)).

c)

Choose Execute (F8). Hint: To view the output requests for a spool request: • •

2.

Double click the Status field, or Select a spool request, and press Output requests (F5).

Run the report RSPO1041 (in the dialog) to delete all of your spool requests with successful output requests. a)

Call transaction SA38.

b)

In the Program field, enter RSPO1041, and choose Execute (F8).

c)

Deselect the fields Without Output Request, In Processing, and Incorrect. In the Completed area only check the Completed field, and in the older than ... days field, enter 0. In the Further conditions area, enter your course user -## in the Creator field (## represents your group number) and choose Execute (F8).

d)

You can see which spool requests were deleted in the log. Note: In practice, you will schedule the RSPO1041 report as a periodic background job with an appropriate variant.

474

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Managing Spool Requests

Lesson Summary You should now be able to: • Manage spool requests and output requests

Related Information •

•

Online documentation for SAP NetWeaver 7.3 Inlcuding Enhancement Package 1, areaSAP NetWeaver → Administration Information → Technical Operations for SAP NetWeaver → (Link to) Administration of Application Server ABAP → SAP Printing Guide (BC-CCM-PRN) → Maintaining the Spool Database. SAP Notes: 130978: RSPO1041 - Replacement for RSPO0041 98065: Spool Consistency Check with RSPO1043 as of 4.0A 48400: Reorganization of TemSe and Spool 48284: System can no longer create spool requests 311037: Printing via e-mail 771683: Front-end printing for SAP GUI for HTML (as of Release 6.40)

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

475

Unit 10: Output Management

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL) Lesson Overview In this lesson, you will learn about the Printing Assistant for Landscapes (PAL). After learning the concepts and terms, you will learn about administrative tasks in transaction PAL.

Lesson Objectives After completing this lesson, you will be able to: • • •

Name the prerequisites for using the Printing Assistant for Landscapes (PAL) Explain the terms in the PAL environment Set up and use a PAL landscape

Business Example Your company uses several ABAP-based SAP systems, each with several output devices. To keep administration tasks to a minimum in the event of changes, you want to use the Printing Assistant for Landscapes.

Prerequisites for Using PAL You can use the Printing Assistant for Landscapes to simplify the administration of output devices in ABAP-based SAP systems. To do this, output devices are maintained in one system (normally the central system), and their definition is then distributed across any number of additional systems (target systems) over RFC. SAP recommends using PAL if at least one of the following criteria applies: • • •

You manage several output devices in a few SAP systems. You manage a few output devices in several SAP systems. You manage several output devices in several SAP systems.

The following diagram is based on a small PAL landscape, and shows the release requirements of the systems involved: Hint: In contrast to transaction SPAD which uses the term output device for a printing device in the SAP system, transaction PAL uses the term printer. A printer in transaction PAL therefore corresponds to an output device in transaction SPAD.

476

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL)

Figure 223: PAL Landscape

The central system must be based on an AS ABAP 7.00 (or higher) with an up-to-date patch level. Since the SAP Solution Manager system also supports you to manage other functions centrally, you can use and SAP Solution Manager 7.1 system as the central system for PAL. The target systems must have a minimum release level of AS ABAP 6.20 with certain Support Package levels. Hint: See SAP Note 964501: Printing Assistant for Landscape (PAL) for the precise system requirements. PAL currently supports the following access methods: • • • • •

L and C: Local printing U and S: Remote printing F and G: Front-end printing M: E-mail based printing E: External output management systems

Restrictions exist for some of these access methods: For details see the SAP online documentation for SAP NetWeaver 7.3 Including Enhancement Package 1 in area SAP NetWeaver → Administration Information → Technical Operations for SAP NetWeaver → (Link to) Administration of Application Server ABAP → SAP Printing Guide (BC-CCM-PRN) → Printing Assistant for Landscapes (PAL) .

Setting Up and Using PAL Before introducing the configuration steps, some central terms will be explained first:

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

477

Unit 10: Output Management

TADM12_1

Figure 224: PAL Terminology

(PAL) Printer The first step in the Printing Assistant for Landscapes is to create an output device (using transaction SPAD). This output device must then be designated as a PAL printer (often simply referred to as a “printer” below). Printer Group A printer group normally comprises several printers that are jointly distributed later. Target System A target system in a PAL environment refers to an RFC connection (which is maintained in the central system). This RFC connection contains connection and log on data for a suitable ABAP-based SAP system in the PAL landscape. Target System Group Printer groups are always distributed in a target system group, which usually consists of several target systems. The following diagram shows the steps for defining and using a PAL printer landscape:

478

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL)

Figure 225: Roadmap for PAL

The following sections explain the individual steps in more detail.

Maintaining a PAL System Landscape Printer definitions are distributed from the central system to the target systems across RFC. You therefore need an RFC connection in your central system to each target system. SAP recommends setting up a dedicated system user for spool administration in every target system. This user has authorization to the following authorization objects Authorization Object

Values

S_TCODE

SPAD, PAL

S_ADMI_FCD

SP01, SPOR, SPAA, SPAB, SPAC, SPAD

To ensure a target system is recognized by PAL, it must be created with transaction PAL (to start it in the central system). Printers are then always distributed using target system groups that define a logical collection of target systems. A target system group could consist of all production systems for example. Note: A target system cannot belong to multiple target system groups.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

479

Unit 10: Output Management

TADM12_1

Key steps of the initial set up: 1. 2. 3. 4.

In the central system create one RFC connection for each target system. Call transaction PAL in the central system. Under Show, choose the option Target System, and choose Create. Enter a target system name and select the corresponding RFC destination. Under Show, choose the option Target System Group, and choose Create. Enter a target system group name. You can add the target systems you want to include now or later.

Create and Distribute PAL Printers PAL allows you to manage and distribute Printers (“PAL printers”) that you defined in the central system or a target system as a output device earlier (in transaction SPAD). You can then subsume these PAL printers in printer groups. A printer group could incorporate all test printers for example. You can then distribute printer groups across target system groups. Note: A PAL printer cannot belong to multiple printer groups. Key steps during set up: 1. 2.

3.

4. 5.

Call transaction PAL in the central system. Under Show, choose the option Printers, and choose Create. The Wizard will ask you whether you want to specify output devices from the central system or a target system as a printer. Under Show, choose the option Printer Group, and choose Create. Enter a printer group name. You can select the printers you want to include now or later. In the view Printer Group, select a printer group, and choose Distribute. Select one (or several) target system group(s). After you have distributed the printer group, check the Distribution Status.

PAL printers in the target system can only be displayed in transaction SPAD, not changed. When a printer is distributed to a target system for the first time, an arbitrary (physical) spool server is assigned to the output device. Using the report SPCPC_SPOO_SERV_MASS_CHANGE in the target system, you can assign a (logical or physical) spool server to some or all PAL printers. The only mandatory input field is New Spool Server. The checkbox Confirm before change is selected as a default. If you use the default setting, a list of affected PAL Printers will be displayed. You can check first if the new spool servers are correct before you execute the report.

480

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL)

Changing of PAL Objects When you create a printer from a target system in transaction PAL, this output device is then also known in transaction SPAD on the central system. The maintenance of this output device then takes place in the central system. In this way, changes to a PAL printer can be distributed to the target systems. Note: The transfer of a PAL printer which was created in a target system back to the same target system is successful only when the corresponding output device has been deleted in the target system. Otherwise the printing assistance for landscape returns that there already exists an output device with the same name in the target system (as a non-PAL printer). Hint: The error message “Lock failed, unknown lock” (the error message can be a little bit different) indicates that the selected output device is maintained in change mode at the moment. To delete the lock, quit transaction SPAD (or switch to the display mode). It is also possible to schedule the distribution as a background job (via report SPCPC_DIST_PRG_TO_TSG). See SAP Note 1476793: PAL Printer Distribution in Background for the (minimum system requirements).

Deleting PAL Objects You can also delete objects from the PAL landscape. There are some points to consider. To delete an (existing) printer, proceed as follows: 1. 2. 3.

4. 5.

2013/Q1

Call transaction PAL in the central system. Delete the relevant printer from the printer group. Call the distribution status: changes that have not yet been distributed are displayed. Distribute the relevant printer group across the listed target system group(s). The deleted printer no longer appears in transaction SPAD for the target systems. Delete the (PAL) printer. If required, delete the output device using transaction SPAD in the central system.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

481

Unit 10: Output Management

TADM12_1

To delete a target system, proceed as follows: 1. 2. 3.

4. 5. 6.

482

Call transaction PAL in the central system. Delete the required target system from the target system group. Call the distribution status: changes that have not yet been distributed are displayed. Distribute the relevant printer group across the listed target system group(s). Delete the target system. If required, delete the RFC destination using transaction SM59 in the central system. If required, delete the relevant system user using transaction SU01 in the target system.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL)

Exercise 19: Central Administration of Output Devices (PAL) Exercise Objectives After completing this exercise, you will be able to: • Set up a PAL system landscape • Distribute the definition of output devices within a PAL system landscape

Business Example Your company uses several ABAP-based SAP systems, each with several output devices. To keep administration tasks to a minimum in the event of changes, you want to use the Printing Assistant for Landscapes (PAL). Caution: All training groups working on the same server will work together for this exercise. • •

The SAP Solution Manager system plays the role of the central system. The SAP ECC systems on the same host fill the role of the target systems.

The following steps should therefore be executed together. The aim of the exercise is to transfer the output devices from the SAP ECC systems (DCC, QCC) to the central printer administration of the PSM system and then to transfer these output devices into the PCC system.

Task 1: PAL System Landscape Checking the prerequisites and defining the PAL landscape. 1.

Verify that in the central system (the SAP Solution Manager system) there is an RFC connection of the type Partner_ defined to each target system for example Partner_DCC100. This RFC connection should contain the logon credentials of a (dialog or system) user with spool administration rights. Hint: If these RFC connections do not yet exist, create them using transaction SM59. For details consult your instructor.

2.

In the central system, configure all three SAP ECC systems as PAL target systems. Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

483

Unit 10: Output Management

3.

TADM12_1

In the central system, create a target system group ProdSystems, and add the PCC system to this group.

Result You have created a target system group ProdSystems, and assigned the PCC system to it. In practice, you would manage multiple target system groups and/or define more systems for each target system group.

Task 2: Distribute of Local Printers Defining local printers as PAL printers, and distribute them. Note: This task assumes that a local output device Local## with access method “local” has been created in the SAP ECC systems (## denotes your respective group number). 1.

In the central system, define the local printers Local## – which were defined in the target systems DCC and QCC – as PAL printers.

2.

In the central system, create a printer group ProdPrinters, and add the printers Local## to this group. Then distribute the printer group ProdPrinters to the system group ProdSystems.

3.

In the target system PCC, check whether the output devices Local## are known.

Result You have successfully distributed local printers into a target system using PAL.

Task 3: Distribute of Remote Printers Defining remote printers as PAL printers, and distribute them. Note: This task assumes that a remote output device Remote## with access method “local” has been created both in the DCC system and in the QCC system (## denotes the group number of the DCC group or the QCC group respectively). 1.

In the central system, define the remote printers Remote## – which were defined in the target systems DCC and QCC – as PAL printers.

2.

Add the PAL printers Remote## to the printer group ProdPrinters that you created earlier. Then distribute the printer group ProdPrinters to the system group ProdSystems (again).

Continued on next page

484

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL)

3.

In the target system PCC, check whether the output devices Remote## are known.

Result You have successfully distributed remote printers into a target system using PAL.

Task 4: Distribution via Report Perform and distribute changes via report. 1.

On the PSM system, perform a change to the output device Local## (e.g. change the Location on tab Device Attributes).

2.

Using report SPCPC_DIST_PRG_TO_TSG in the central system , perform a distribution of printer group ProdPrinters to system group ProdSystems.

3.

In the target system, check whether the change of output device Local## is recognized.

Result You have performed a distribution of a printer group to a system group via a report. Hint: You could schedule SPCPC_DIST_PRG_TO_TSG as a periodical background job as well.

Task 5: Optional: Mass Change of Spool Server(s) Changing the spool servers of all distributed PAL printers. 1.

Preparation: In the PCC system, create a logical server Logical_Test which peforms load balancing between the two application servers of the PCC system.

2.

Using report SPCPC_SPOO_SERV_MASS_CHANGE, assign the logical spool server Logical_Test to all PAL printers in the target system PCC.

3.

Check the spool server of all PAL printers in the target system PCC.

Result You have adjusted the spool server of the distributed PAL printers.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

485

Unit 10: Output Management

TADM12_1

Solution 19: Central Administration of Output Devices (PAL) Task 1: PAL System Landscape Checking the prerequisites and defining the PAL landscape. 1.

Verify that in the central system (the SAP Solution Manager system) there is an RFC connection of the type Partner_ defined to each target system for example Partner_DCC100. This RFC connection should contain the logon credentials of a (dialog or system) user with spool administration rights. Hint: If these RFC connections do not yet exist, create them using transaction SM59. For details consult your instructor.

2.

a)

Logon to the SAP Solution Manager system (system PSM) that is assigned to you with your course user -##.

b)

Start transaction SM59.

c)

Under ABAP Connections (Type 3), you should see the RFC connections Partner_ that lead to the DCC system, QCC system and PCC system respectively and which contain a user with the profile SAP_ALL in the corresponding target system.

In the central system, configure all three SAP ECC systems as PAL target systems. a)

In the SAP Solution Manager system start transaction PAL.

b)

In the Show field, choose the option Target System, and press Create.

c)

Populate the Create Target System window as follows: Field

Input

Target System Name

DCC

Description



RFC destination

use the value help to select Partner_ (for example Partner_QCC100).

Then use the Check pushbutton to verify that the target system can be accessed. Then press OK. d)

Repeat these steps for the remaining two SAP ECC systems. Continued on next page

486

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL)

3.

In the central system, create a target system group ProdSystems, and add the PCC system to this group. a)

If you have not yet already done, enter transaction PAL in the SAP Solution Manager system.

b)

In the Show field, choose the option Target System Group, and press Create.

c)

Populate the Create Target System Group window as follows: Field

Input

Target System Group Name

ProdSystems

Description



Select the line for the target system PCC, and confirm with OK.

Result You have created a target system group ProdSystems, and assigned the PCC system to it. In practice, you would manage multiple target system groups and/or define more systems for each target system group.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

487

Unit 10: Output Management

TADM12_1

Task 2: Distribute of Local Printers Defining local printers as PAL printers, and distribute them. Note: This task assumes that a local output device Local## with access method “local” has been created in the SAP ECC systems (## denotes your respective group number). 1.

In the central system, define the local printers Local## – which were defined in the target systems DCC and QCC – as PAL printers. a)

If you have not yet already done so, enter transaction PAL in the central system.

b)

In the Show field, choose the option Printer, and press Create.

c)

In the window Select - Source of Output Devices, select the option Target System, in the Name field select the system DCC with the help of the value help. Confirm your settings with OK. On the following popup choose Next.

d)

In the window Select - Output Devices in Target System “”, select the device Local##, ## denotes the group number of the DCC group) and choose Next.

e)

In the window Create PAL printers, select the line with the output device Local## and choose Finish.

f)

Confirm the prompt (with information about the access method) with Yes. Hint: An error message “Lock failed. Foreign lock.” indicates that the selected output device is currently processed in change mode. To release the lock, leave transaction SPAD (or switch to the Display mode).

g)

The printer assistant issues a log detailing the (hopefully successful) creation of the PAL printer, which you can Close.

h)

Repeat the previous steps in the same way for the output device Local## of the QCC system (## now denotes the group number of the QCC group) which you also define as PAL printer in the SAP Solution Manager system.

Continued on next page

488

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL)

2.

In the central system, create a printer group ProdPrinters, and add the printers Local## to this group. Then distribute the printer group ProdPrinters to the system group ProdSystems. a)

If you have not yet already done so, enter transaction PAL in the central system.

b)

In the Show field, choose the option Printer Group, and press Create.

c)

Populate the Create Printer Group window as follows: Field

Input

Printer Group Name

ProdPrinters

Description



Select the lines for the PAL printers Local##, and press OK. d)

In transaction PAL, select the printer group ProdPrinters, and choose Distribute.

e)

If the system displays a prompt on the access method of the selected printer(s), confirm it by pressing OK.

f)

In the window Distribute Printer Group, select the target system group ProdSystems you just created, and choose Next.

g)

Check the result of the Device Type Check in Target System – if this was successful, choose Next. Confirm another popup with Yes.

h)

The printer assistant issues a log about the distribution, which you can Close now.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

489

Unit 10: Output Management

3.

TADM12_1

In the target system PCC, check whether the output devices Local## are known. a)

Logon with your course user -## to the PCC system and start transaction SPAD in this system.

b)

Check that the definition of the output devices Local## is correctly recognized in the PCC system. Note • • •

that you can not change the definition in the target system. the description “Centrally-Administered Device”. the spool server of the output device.

Result You have successfully distributed local printers into a target system using PAL.

Continued on next page

490

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL)

Task 3: Distribute of Remote Printers Defining remote printers as PAL printers, and distribute them. Note: This task assumes that a remote output device Remote## with access method “local” has been created both in the DCC system and in the QCC system (## denotes the group number of the DCC group or the QCC group respectively). 1.

In the central system, define the remote printers Remote## – which were defined in the target systems DCC and QCC – as PAL printers. a)

If you have not yet already done so, enter transaction PAL in the central system.

b)

In the Show field, choose the option Printer, and press Create.

c)

In the window Select - Source of Output Devices, select the option Target System, in the Name field select the system DCC with the help of the value help. Confirm your settings with OK. On the following popup choose Next.

d)

In the window Select - Output Devices in Target System “”, select the device Remote##, ## denotes the group number of the DCC group) and choose Next.

e)

In the window Create PAL printers, select the line with the output device Remote## and choose Finish.

f)

Confirm the prompt (with information about the access method) with Yes. Hint: An error message “Lock failed. Foreign lock.” indicates that the selected output device is currently processed in change mode. To release the lock, leave transaction SPAD (or switch to the Display mode).

g)

The printer assistant issues a log detailing the (hopefully successful) creation of the PAL printer, which you can Close.

h)

Repeat the previous steps in the same way for the output device Remote## of the QCC system (## now denotes the group number of the QCC group) which you also define as PAL printer in the SAP Solution Manager system.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

491

Unit 10: Output Management

2.

3.

TADM12_1

Add the PAL printers Remote## to the printer group ProdPrinters that you created earlier. Then distribute the printer group ProdPrinters to the system group ProdSystems (again). a)

If you have not yet already done so, enter transaction PAL in the central system.

b)

In the Show field, choose the option Printer Group, and select the line ProdPrinters.

c)

In the section shown below, switch to the Members tab. Choose the Add pushbutton. Select the lines for the printers Remote##, and choose OK.

d)

In transaction PAL, select the printer group ProdPrinters, and choose Distribute.

e)

If the system displays a prompt on the access method of the selected printer(s), confirm it by pressing OK.

f)

In the window Select - PAL Target System Group, select the target system group ProdSystems, and choose Next.

g)

Check the result of the Device Type Check in Target System – if this was successful, choose Next.

h)

Confirm the system message about the distribution of the printer group(s) with Yes.

i)

The printer assistant issues a log about the distribution, which you can Close now.

In the target system PCC, check whether the output devices Remote## are known. a)

If you have not yet already done, logon with your course user -## to the PCC system and start transaction SPAD in this system.

b)

Check that the definition of the output devices Remote## are correctly recognized in the PCC system. Note • • •

that you can not change the definition in the target system. the description “Centrally-Administered Device”. the spool server of the output device.

Result You have successfully distributed remote printers into a target system using PAL. Continued on next page

492

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL)

Task 4: Distribution via Report Perform and distribute changes via report. 1.

2.

3.

On the PSM system, perform a change to the output device Local## (e.g. change the Location on tab Device Attributes). a)

If you have not yet already done, logon to the PSM system with your course user -##. In this system enter transaction SPAD.

b)

On the Devices / servers tab, choose Display in line Output Devices (leave the input field to the left empty).

c)

Double click the entry Local##.

d)

If you are in display mode, choose Change to switch to change mode.

e)

On the DeviceAttributes tab, enter a new or change an existing the Location.

f)

Press save (and note the popup).

g)

Ensure that all locks are released, e.g. by leaving transaction SPAD.

Using report SPCPC_DIST_PRG_TO_TSG in the central system , perform a distribution of printer group ProdPrinters to system group ProdSystems. a)

In the central system (PSM), start transaction SA38.

b)

As Program, enter SPCPC_DIST_PRG_TO_TSG and press Execute (or the F8 key).

c)

As Printer Group, select ProdPrinters. As Target System Groups, select ProdSystems. When done, press Execute (or the F8 key).

In the target system, check whether the change of output device Local## is recognized. a)

If you have not yet already done, logon to the PCC system with your course user -##. In this system start transaction SPAD.

b)

Verify that the output device Local## comes with the changed property.

Result You have performed a distribution of a printer group to a system group via a report. Hint: You could schedule SPCPC_DIST_PRG_TO_TSG as a periodical background job as well.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

493

Unit 10: Output Management

TADM12_1

Task 5: Optional: Mass Change of Spool Server(s) Changing the spool servers of all distributed PAL printers. 1.

Preparation: In the PCC system, create a logical server Logical_Test which peforms load balancing between the two application servers of the PCC system. a)

If you have not yet already done, logon to the PCC system with your course user -##. In this system, choose Tools → CCMS → Print → Spool Administration (transaction SPAD).

b)

On the Devices / servers tab page, choose Display in line Spool Servers (leave the input field to the left empty).

c)

If you cannot see a Create pushbutton, choose Change to switch to change mode. Choose Create. Now create a logical server Logical_Test with the following settings and finally save your changes: • • • • • • •

2.

Server Name: Logical_Test Description: Server class: T Logical Server: select this field Allow load balancing: select this field Mapping: Alt. server:

Using report SPCPC_SPOO_SERV_MASS_CHANGE, assign the logical spool server Logical_Test to all PAL printers in the target system PCC. a)

In the PCC system, start transaction SA38.

b)

Enter Program SPCPC_SPOO_SERV_MASS_CHANGE (you may enter spcpc* and use the F4 help), and press Execute (F8).

c)

For New Spool Server, choose Logical_Test (you may use the F4 help).

d)

Keep all other fields with their default value, and press Execute (F8).

e)

Check the window Confirm Spool Server Change, and press Change Spool Server. A log with detailed information regarding the spool server change is displayed.

Continued on next page

494

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Printing Assistant for Landscapes (PAL)

3.

Check the spool server of all PAL printers in the target system PCC. a)

In the PCC system, start transaction SPAD.

b)

On the Devices / servers tab page, choose Display in line Output Devices (leave the input field to the left empty).

c)

In the overview of output devices, note the column Spool servers. For the output devices created by PAL, you should see the value Logical_Test.

Result You have adjusted the spool server of the distributed PAL printers.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

495

Unit 10: Output Management

TADM12_1

Lesson Summary You should now be able to: • Name the prerequisites for using the Printing Assistant for Landscapes (PAL) • Explain the terms in the PAL environment • Set up and use a PAL landscape

Related Information •

• • • • •

496

SAP online documentation for SAP NetWeaver 7.3 Including Enhancement Package 1 in area SAP NetWeaver → Administration Information → Technical Operations for SAP NetWeaver → (Link to) Administration of Application Server ABAP → SAP Printing Guide (BC-CCM-PRN) → Printing Assistant for Landscapes (PAL) SAP Community Network, Quick Link /output-management (http://scn.sap.com/community/output-management) SAP Note 964501: Printing Assistant for Landscape (PAL) SAP Note 1240633: PAL: Transferring the spool server SAP Note 1476793: PAL Printer Distribution in Background SAP Note 1054170: FAQ: Frequently Asked Questions Regarding PAL

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Unit Summary

Unit Summary You should now be able to: • Describe the architecture and data flow of output processing in ABAP-based SAP systems • Create output devices and spool servers in the SAP system • List important access methods • Describe the concept of logical spool servers • Set up logical spool servers • Manage spool requests and output requests • Name the prerequisites for using the Printing Assistant for Landscapes (PAL) • Explain the terms in the PAL environment • Set up and use a PAL landscape

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

497

Unit Summary

498

TADM12_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Test Your Knowledge

Test Your Knowledge 1.

Which of the following access methods exist in the SAP system? Choose the correct answer(s).

□ □ □ □ 2.

A B C D

Remote printing Front-end printing Instance printing Local printing

Which of the listed states can a spool request have? Choose the correct answer(s).

□ □ □ □ □ □

2013/Q1

A B C D E F

Complete Canceled Error Waiting Active Print.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

499

Test Your Knowledge

TADM12_1

Answers 1.

Which of the following access methods exist in the SAP system? Answer: A, B, D Instance printing does not exist.

2.

Which of the listed states can a spool request have? Answer: A, C, D, F The incorrect options canceled and active are possible status messages from job monitoring. Other possible statuses of a spool request are -, +, Proc., , Problem, and Time.

500

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

Unit 11 Scheduling Background Tasks Unit Overview This unit deals with the basics of background processing, and the scheduling and monitoring of jobs. You also learn about special functions and extension options of background processing. Caution: This unit takes place on the SAP systems named DCC and PSM. The activities in this unit are not using the freshly installed SAP systems S00, E00 and X00. This is necessary, because configuring the newly installed SAP systems in such a way that the related exercises can take place would require significant work before you could start the actual exercises. If you like, you can shut down the freshly installed SAP systems S00, E00 and X00.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • • •

Describe the uses of background processing Schedule and monitor jobs Schedule time-dependent jobs Schedule standard jobs Schedule event-dependent jobs Define and trigger events Use additional, special functions of background processing Explain how to use SAP Central Process Scheduling by Redwood Name the most important features of SAP CPS Use the Work Center Job Management to schedule and monitor background jobs

Unit Contents Lesson: Fundamentals of Background Processing ........................503 Exercise 20: Optional: Fundamentals of Background Processing...513 Lesson: Time-Based Scheduling of Jobs ....................................517

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

501

Unit 11: Scheduling Background Tasks

TADM12_1

Exercise 21: Time-Based Jobs ...........................................523 Lesson: Event-Based Scheduling of Jobs ...................................531 Exercise 22: Event-Dependent Jobs.....................................537 Lesson: Background Processing: Further Topics ..........................543 Exercise 23: (Optional) Other Topics in the Area of Background Processing...................................................................555 Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood .........................................................................561 Exercise 24: Job Scheduling with SAP CPS............................577 Lesson: Appendix: Job Management ........................................583

502

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Fundamentals of Background Processing

Lesson: Fundamentals of Background Processing Lesson Overview In this lesson, you will learn about the basics of background processing.

Lesson Objectives After completing this lesson, you will be able to: • •

Describe the uses of background processing Schedule and monitor jobs

Business Example Reports that are to run on a regular basis and long-running programs are scheduled as jobs in the SAP system. The administrator schedules jobs and monitors the system's background processing to ensure that it is running correctly.

Basics The following questions are answered in the course of this lesson: • • • • • •

Why do you need background processing? What is a job? What can be performed in the background? What start criteria are there? How are jobs scheduled and monitored? What status can a job have?

Dialog work processes should be quickly (i.e. without any noticeable wait time) available for the processing of requests of end users. Dialog resources should therefore be used for short-running requests so the processes become quickly available again for other tasks. The system profile parameter rdisp/max_wprun_time exists for this reason. It limits the maximum runtime of a dialog step within a dialog work process. This should ensure that dialog work processes are not blocked by long-running programs, interfering with online operation. After the maximum runtime has elapsed, the program is terminated. Note: The way in which the parameter rdisp/max_wprun_time works is described in detail in SAP Note 25528: Parameter rdisp/max_wprun_time.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

503

Unit 11: Scheduling Background Tasks

TADM12_1

Figure 226: Why Background Processing?

You can use the background work processes for long-running tasks. These are sometimes also called batch work processes. Normally, background processing is used not only for long-running, but also for recurrent tasks. Examples of this type of task are the daily database backup or the month-end work for financial accounting.

Figure 227: What Is a Job?

504

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Fundamentals of Background Processing

A job comprises one or more steps (known as job steps). A step can be: • • •

An ABAP program An external command An external program

Every job is processed without interruption by one single background work process. Background jobs can be scheduled with different priorities: • • •

Class A (highest priority) Class B (medium priority) Class C (normal priority)

If a job should be executed on a particular server or server group, it is handled preferentially compared to other jobs with the same class. This preference only applies if multiple jobs of various priorities request background processing at the same time, for example, because they are scheduled for the same time. Hint: You should ensure that a large share of all background tasks are normally scheduled as a job with class C without target server specification. This share can include 90% (or more) of all tasks. System background tasks are also executed in this way, such as the tasks that you schedule with transaction DB13.

Figure 228: What can be Performed in the Background?

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

505

Unit 11: Scheduling Background Tasks

TADM12_1

A step within a job can call one of three actions: •

•

•

Every ABAP program can be scheduled as a step of a job. If the ABAP program has one or more selection screens, you might be required to create the necessary input in advance in the form of a variant. A variant makes it possible to run an ABAP program in the background although the program requires input. The values stored in the variant are then used during the execution of the program. If an ABAP program has a screen output as its result, this is saved in a spool list. You can specify an (e-mail) recipient for this spool list when defining the job. This recipient then receives the job output by e-mail after the job has been executed. You must also specify a printer for the creation of spool lists even though, as a result of background processing, there is not necessarily any direct output to a printer (this depends on the printer's access method). This may have to be explicitly started later. An external command is a call of a predefined script, a command, or a program at operating system level. With external commands, you can mask operating system calls and store them in the SAP system under an arbitrary name. You can also use the SAP authorization concept to protect the execution of an external command. This enables you to determine which users are allowed to execute which external commands (on which target hosts and/or operating systems). An external program is any operating system command. The SAP authorization concept only specifies whether a user can call external programs or not. A more detailed authorization assignment, for example at the level of program names, is not provided; use external commands for this.

Figure 229: Start Criteria for a Job

506

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Fundamentals of Background Processing

A job can be triggered: •

•

By scheduling it on a particular date at a particular time (this includes the start time “immediately”, if there are no free background work processes available when the job is scheduled). By the occurrence of a particular event defined in the SAP system (this includes jobs that are to start after other jobs or at operation mode changes, or jobs with immediate start if there are free background work processes available when the job is scheduled).

Scheduling and Monitoring Use transaction SM36 to define new jobs. You can also call the Job Wizard (transaction SM36WIZ) from transaction SM36. Alternatively, the scheduling of background jobs is also possible using SA38 and many functions within business applications. Note: Please note that background activities usually will be scheduled by experts within the business departments. As an system administrator you are responsible for enabling the system to execute all scheduled jobs (e.g. by appropriately configuring the system).

Figure 230: Job Scheduling

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

507

Unit 11: Scheduling Background Tasks

TADM12_1

Required specifications when defining a job are: • • •

General specifications such as job name, job priority (Default: C) and (optionally) target server (group) Definition of one or more job steps Definition of start conditions (time-dependent or event-dependent)

The Job Wizard supports you when defining jobs, by guiding you easily through the creation process. The way in which a job is created (“classic” or using the Job Wizard) has no bearing on the result. Some functions (specifying an SAP user for each step, swapping steps) are not available with the Job Wizard, however. Use transaction SM37 to monitor jobs. You can select jobs using a diverse range of criteria on the initial screen of this transaction. In this way, you can display all jobs that contain a particular job step, that have a particular status, or that react to a defined event (for this, you must select a particular event or “*”).

Figure 231: Job Monitoring

508

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Fundamentals of Background Processing

After you have chosen Execute, a job overview appears that is realized by the SAP List Viewer (ALV). By choosing Settings from the menu you can determine the columns that are displayed and the sort order, amongst other things. You can set this layout as the standard layout (for the current user or for all users). Hint: The transaction SM37 offers the following two ALV-based display types: • •

LIST: offers a quick list structure (standard setting) GRID: enables you to change the layout easily (required for accessibility)

Using the report BTC_SWITCH_LIST_GRID, a batch administrator can determine the display type for individual users or all users. You can navigate to other job-specific views from the job overview shown above: • • •

The spool list contains the output lists for ABAP programs (if they exist). The job details contain, among other information, the job definition, duration of the processing of the job, and the start time of the job. All messages output by a background program are stored in the job log. You can display this log to obtain information about a program that terminated with errors or to perform a detailed investigation about a background processing run.

Figure 232: Status of a Job

A job can have the following status:

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

509

Unit 11: Scheduling Background Tasks

TADM12_1

Scheduled The steps that make up the job have already been defined, however the start condition still needs defining. This job will not be performed without further activities from your side. Released The job has been completely defined, including its start condition. A job cannot be released without a start condition. Only an administrator or a user with the relevant authorizations for background processing can release a job. This ensures that unauthorized users cannot execute jobs without approval. Ready The start condition of a released job has been fulfilled. A job scheduler has placed the job in the request queue of background work processes. Active The job is currently being executed and cannot be deleted or changed. If an active job does not seem to be running correctly (for example, it is running for an unusually long time), you can terminate it in a background work process in debugging mode, analyze it, and then either release it again or terminate it completely. To do this, call transaction SM37 and choose Job → Capture: active job. Hint: To capture a job, you must be logged on to the instance on which the job is running. Finished All steps of this job were successfully completed. Canceled The job aborted. This can happen in two ways: • •

An administrator deliberately terminates the job in transaction SM37 by choosing Job → Cancel active job. A job step is terminated with an error. Note: If a job remains in status ready or active for longer than expected and you would like to check if the displayed status still is reflecting the actual state of the job, you can use the following function within transaction SM37: Job → Ceck status. By using this function, the status of the selected job will be checked and updated to the actual status, if necessary.

You can still change a job as long as the job still has the status Scheduled or Released.

510

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Fundamentals of Background Processing

If the execution of the job has already begun, you can monitor the processing in the job log. If the job contains ABAP programs that create output lists, these are stored in spool lists. You can create a new job by copying an existing job. From the menu, choose Job → Copy. For checking the consistency of the background processing environment, you can also use a simple Analysis Tool – Background Processing (transaction SM65)

Figure 233: Analysis Tool – Background Processing

Please note also the advanced analysis features, that you can access through Goto → Additional tests.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

511

Unit 11: Scheduling Background Tasks

512

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM12_1

2013/Q1

TADM12_1

Lesson: Fundamentals of Background Processing

Exercise 20: Optional: Fundamentals of Background Processing Exercise Objectives After completing this exercise, you will be able to: • Determine the configuration of your SAP system with regard to background processing.

Business Example Reports that are to run on a regular basis and long-running programs are scheduled as jobs in the SAP system. The administrator schedules jobs and monitors the system's background processing to ensure that it is running correctly.

Task: Checking the Configuration Check the way that background processing is configured in your SAP system. The following steps will make you familiar with the SAP system settings that are relevant for background processing.

2013/Q1

1.

How many background processes are currently configured in your SAP system? To answer this question use the place the (global) work process overview.

2.

What determines the number of available background work processes? Use the opportunity to search over all the profile parameters or the documentation of individual, known profile parameters.

3.

Call the transaction SM65 and complete Basic tests for all background server.

4.

Assume that all background work processes in your system are currently processing and there are, therefore, no free resources for other jobs. Can you provide additional background work processes without restarting the SAP system?

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

513

Unit 11: Scheduling Background Tasks

TADM12_1

Solution 20: Optional: Fundamentals of Background Processing Task: Checking the Configuration Check the way that background processing is configured in your SAP system. The following steps will make you familiar with the SAP system settings that are relevant for background processing. 1.

How many background processes are currently configured in your SAP system? To answer this question use the place the (global) work process overview. a)

Start transaction SM66.

b)

Choose the Select Process pushbutton to make the following selections: • •

c) 2.

3.

Choose Continue and count the number of work processes displayed.

What determines the number of available background work processes? Use the opportunity to search over all the profile parameters or the documentation of individual, known profile parameters. a)

The parameter rdisp/wp_no_btc initially specifies the number of available background work processes on the current instance.

b)

You can check the value of the parameter with transaction RZ11 or the report RSPFPAR.

c)

If you have defined operation modes (transaction RZ04), this value can be overwritten.

d)

In this case, use the CCMS Control Panel (transaction RZ03) to determine the currently used operation mode.

e)

Use transaction RZ04 to display the distribution of work processes for the currently used operation mode.

Call the transaction SM65 and complete Basic tests for all background server. a)

4.

Type: Background only Status: choose the status Wait in addition to the already selected fields

Follow the exercise description.

Assume that all background work processes in your system are currently processing and there are, therefore, no free resources for other jobs.

Continued on next page

514

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Fundamentals of Background Processing

Can you provide additional background work processes without restarting the SAP system?

2013/Q1

a)

Using the concept of operation modes, you can define an operation mode with additional background work processes in transaction RZ04.

b)

You can perform a manual operation mode switch using transaction RZ03.

c)

You do not need to restart your system when doing this.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

515

Unit 11: Scheduling Background Tasks

TADM12_1

Lesson Summary You should now be able to: • Describe the uses of background processing • Schedule and monitor jobs

Related Information Further information: SAP Note 25528: Parameter rdisp/max_wprun_time SAP Note 37104: Error analysis: Background processing system SAP Note 519059: FAQ: Background Processing System SAP Note 1439806: Listing jobs according to their frequency

516

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Time-Based Scheduling of Jobs

Lesson: Time-Based Scheduling of Jobs Lesson Overview In this lesson, you will learn about time-based scheduling of jobs.

Lesson Objectives After completing this lesson, you will be able to: • •

Schedule time-dependent jobs Schedule standard jobs

Business Example The administrator schedules jobs and monitors the system's background processing to ensure that it is running correctly.

Time-Based Scheduling

Figure 234: Time-Dependent Start of a Job

A job can be started in a time- or event-dependent manner. In the case of a time-dependent start of a job, you can choose between the following options: • • •

2013/Q1

The job should be executed immediately The job should be executed at a particular date/time The job should be executed on a particular work day

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

517

Unit 11: Scheduling Background Tasks

TADM12_1

You can choose to make all time-based start conditions for jobs recurrent. This means that the job is executed again after a defined period of time has elapsed. You can specify exceptions (such as postponement to the following work day in the case of holidays in the factory calendar). The job is started at the specified date and time, in accordance with the job priority and availability of background work processes. You can also specify a time period during which the job should be executed. To do this, you specify a time after which the job should no longer be executed. With this function, you prevent periodic jobs being executed at an undesirable time, among other things. For example, a reorganization job that should only be executed at night is delayed. With a start time window, you can avoid this job being executed during the day, when the dialog users are active and there are fewer system resources available. Using periodic job scheduling, it is not possible to define an end date for the periodic execution. For example, a definition like “each day until the end of the current year” is currently not supported.

Load Balancing The profile parameter rdisp/bctime specifies the time period in which the time-dependent job scheduler is active (see the next figure). Executing jobs with the start condition immediate usually avoids the time-dependent scheduler. In this case, the dialog work process of the scheduling user performs the job scheduling. Only if no free resources are found, is the job concerned scheduled in a time-based way. The scheduled start time then corresponds to the time point at which it should have started.

518

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Time-Based Scheduling of Jobs

Figure 235: Scheduling Jobs and Load Balancing

Background work processes can be configured on every instance of the SAP system using the profile parameter rdisp/wp_no_btc. The number of background work processes required in the SAP system depends on the number of tasks to be performed in the background. If the transport system is used, there must be at least two background work processes in the system. The combination of job ID and job name define the job uniquely in the system. On every SAP instance on which background work processes are defined, the time-dependent job scheduler runs every rdisp/btctime seconds (default value: 60 seconds). This is an ABAP program (SAPMSSY2 - an auto ABAP program) that runs automatically in a dialog work process. Please note, that the job-sheduler should run every 60s (per default), these executions, however, generally don’t take place to the full minute, but on the one instance, for example, always at the 42nd second of every minute and on another instance at the 9th second of every minute. You cannot influence this number, it

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

519

Unit 11: Scheduling Background Tasks

TADM12_1

changes at the latest after restarting an instance and depends on, at which time certain activities of the system will be executed for the first time after an instance start - from then on the job-scheduler will be started every 60 seconds. Hint: Since SAP NetWeaver 7.0, the job scheduler also starts after a job has finished. This increases the throughput for background processing considerably (depending on how many jobs there are). SAP Note 923228: Background job sched.: using processes that have become free describes this changed behavior and its requirements. The time-dependent job scheduler checks the job scheduling table in the database for jobs that are waiting for processing. These jobs are transferred to free background work processes in the SAP instance, in accordance with their priority and execution target. •

•

Jobs that are not assigned any particular execution target can be executed with any free background work process. This means that the workload is automatically distributed between the SAP instances. If a job is explicitly assigned an execution target (such as a selected instance or a group of instances), the special properties of the execution target can be used (for example, you can ensure that a job is performed on a particular operating system, or that the job is executed by a background work process that is running on the same host as the database). This means, however, that you do not have the advantages of automatic load balancing.

Standard Jobs Standard jobs are background jobs that should run regularly in a production SAP system. These jobs mainly perform certain clean up tasks in the system, such as the deletion of obsolete spool requests.

520

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Time-Based Scheduling of Jobs

Figure 236: Scheduling Standard Jobs

In the job definition transaction (SM36), you can access a selection of important standard jobs that you can schedule, monitor, and edit by choosing Standard Jobs (see figure). •

• •

If you want to schedule all standard jobs, choose Default Scheduling. All standard jobs that are defined in table REORGJOBS are scheduled with the specified variant and period. If other jobs exist that execute one of the programs of the standard jobs, the system informs you of this. To schedule individual jobs, choose the selected job with the input help and specify an execution period. To define an additional standard job that is not yet available in the selection (table REORGJOBS), choose Predefine new job. Note: For information about standard jobs, see also the following SAP Notes SAP Note 16083: Standard jobs, reorganization jobs SAP Note 1034532: Changes for standard jobs SAP Note 1411877: New standard jobs SAP Note 1440439: New Standard Jobs (2) SAP Note 1610282: Problems when scheduling standard jobs

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

521

Unit 11: Scheduling Background Tasks

522

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM12_1

2013/Q1

TADM12_1

Lesson: Time-Based Scheduling of Jobs

Exercise 21: Time-Based Jobs Exercise Objectives After completing this exercise, you will be able to: • Schedule and monitor time-dependent jobs

Business Example The administrator schedules jobs and monitors the system's background processing to ensure that it is running correctly. In this exercise you will perform the following activities: 1. Create a periodic time-based job using transaction SM36 2. Learn the use of the job overview transaction SM37 3. Optional: Create a variant of a program using transaction SA38 4. Optional: Schedule a job with a variant using transaction SA38 and consider using transaction SM37 5. Optional: Create a job using job-Wizards

Task 1: Scheduling Jobs Job creation 1.

Use the transaction SM36 (without the wizard) to create a job with the following characteristics: Job name

TIME-##, ## = group number.

Job class C Exec. target

Leave empty

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

523

Unit 11: Scheduling Background Tasks

TADM12_1

First Step

Program RSPFPAR with variant SAP&LOGIN.

Start condition



Period value

Daily

Hint: Bear in mind that the system time (System → Status) is the relevant time for jobs.

Result You can schedule time-dependent jobs.

Task 2: Monitor Jobs Use the Simple Job Selection to monitor jobs. 1.

Display the jobs you have created earlier.

2.

Find out details for the job you have created earlier such as the priority, client, job ID, user who scheduled and released the job and the work process that executed the job.

3.

Take a look at the spool list for your job.

4.

Determine whether your job was delayed, and if so, the length of the delay.

5.

In SM37, why don’t you see the next scheduled start of your previously created job?

Task 3: Optional: Variants, SA38 and Job-Wizard In this optional exercise you will learn additional possibilities to work with background jobs 1.

Create a variant DISP_## for the program RSPFPAR (## stands for your group number) which only shows parameters for the ABAP dispatcher.

2.

Use transaction SA38 to run the report RSPFPAR in the background (start time: Execute immediately). For Variant Name, select the name of the variant you have created before.

3.

Use transaction SM36WIZ to create a job with the following properties:

Continued on next page

524

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Time-Based Scheduling of Jobs

Job Name

TIME-WIZ-##, ## = group number.

Job Class

C

Exec. target

leave empty

First Step

Program RSPFPAR, if you want, with the specification of your variant

Start condition

Immediate

Period value

Hourly

Result You have learned additional possibilities to work with background jobs.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

525

Unit 11: Scheduling Background Tasks

TADM12_1

Solution 21: Time-Based Jobs Task 1: Scheduling Jobs Job creation 1.

Use the transaction SM36 (without the wizard) to create a job with the following characteristics: Job name

TIME-##, ## = group number.

Job class C Exec. target

Leave empty

First Step

Program RSPFPAR with variant SAP&LOGIN.

Start condition



Period value

Daily

Hint: Bear in mind that the system time (System → Status) is the relevant time for jobs. a)

Start transaction SM36.

b)

For Job Name, enter TIME-##.

c)

Choose Step.

d)

Enter the specifications for the step that are listed in the task description (above) and choose Save.

e)

Then choose Back (

f)

Choose Start Condition.

g)

Choose Date/Time and enter a time .

h)

Select the Periodic Job checkbox.

i)

Under Period Values, select Daily.

j)

Then choose Save.

k)

Finally, on the initial screen of transaction SM36, choose Save once.

).

Continued on next page

526

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Time-Based Scheduling of Jobs

Result You can schedule time-dependent jobs.

Task 2: Monitor Jobs Use the Simple Job Selection to monitor jobs. 1.

2.

3.

Display the jobs you have created earlier. a)

Start transaction SM37.

b)

Include scheduled jobs in the selection, too.

c)

Leave the other selection criteria on default values.

d)

Choose Execute.

Find out details for the job you have created earlier such as the priority, client, job ID, user who scheduled and released the job and the work process that executed the job. a)

In transaction SM37, double-click the job name.

b)

Choose Job Details to display a dialog box that contains all the information you require.

Take a look at the spool list for your job. a)

In transaction SM37, select your job.

b)

Use the Spool pushbutton to go to the spool request that was generated.

c)

Select the spool request and choose Display contents (

).

Note: Spool lists are only created for job steps that contain ABAP programs with output. They are only printed immediately if you have made the appropriate setting in the printer settings during the definition of the job step or in your user profile defaults (transaction SU3). 4.

Determine whether your job was delayed, and if so, the length of the delay. a)

Depending on the setting, you will already see a column headed Delay in SM37.

b)

After you have selected the your job, you can choose Job Log to display the job’s progress over time. Note: Delays could be due to busy background work processes or due to the fact that the time-dependent Job Scheduler runs periodically but not at the exact point in time at which your job should have started. Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

527

Unit 11: Scheduling Background Tasks

5.

TADM12_1

In SM37, why don’t you see the next scheduled start of your previously created job? a)

With the default values, the job monitor SM37 displays jobs of the current day.

b)

If you adjust the selection accordingly, the next execution of the periodic job (released for the following day) is displayed too. Note: Since a periodic job is always scheduled by its DIRECT predecessor during execution, only the next execution will be shown - which, in this case, is tomorrow.

Task 3: Optional: Variants, SA38 and Job-Wizard In this optional exercise you will learn additional possibilities to work with background jobs 1.

Create a variant DISP_## for the program RSPFPAR (## stands for your group number) which only shows parameters for the ABAP dispatcher. a)

Start the transaction SA38.

b)

Enter RSPFPAR as the Program.

c)

Choose Execute.

d)

Enter rdisp/* at Profile Parameters.

e)

Choose Save as Variant. (

f)

Under Variant Name enter DISP_##.

g)

Under Description enter Parameters of the dispatcher.

h)

Leave the other fields unchanged and Save the new variant.

).

Note: You can also create variant in the ABAP editor (transaction SE38) 2.

Use transaction SA38 to run the report RSPFPAR in the background (start time: Execute immediately).

Continued on next page

528

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Time-Based Scheduling of Jobs

For Variant Name, select the name of the variant you have created before.

3.

a)

Start the transaction SA38.

b)

Enter RSPFPAR in the field Program.

c)

Choose Background.

d)

Select the variant you have created (using the F4 help).

e)

Choose Execute immed.

f)

Use the Job overview pushbutton to go to transaction SM37

g)

Choose to display your job

Use transaction SM36WIZ to create a job with the following properties: Job Name

TIME-WIZ-##, ## = group number.

Job Class

C

Exec. target

leave empty

First Step

Program RSPFPAR, if you want, with the specification of your variant

Start condition

Immediate

Period value

Hourly

a)

Start transaction SM36WIZ.

b)

Choose Continue.

c)

Fill the screens as specified in the task. Use the F4 Help wherever possible. Where no values have been specified in the list above, use the default values.

d)

Choose Complete to finish.

Result You have learned additional possibilities to work with background jobs.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

529

Unit 11: Scheduling Background Tasks

TADM12_1

Lesson Summary You should now be able to: • Schedule time-dependent jobs • Schedule standard jobs

Related Information SAP Notes: • • • • • •

530

SAP Note 16083: Standard jobs, reorganization jobs SAP Note 923228: Background job sched.: using processes that have become free SAP Note 1034532: Changes for standard jobs SAP Note 1411877: New standard jobs SAP Note 1440439: New Standard Jobs (2) SAP Note 1610282: Problems when scheduling standard jobs

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Event-Based Scheduling of Jobs

Lesson: Event-Based Scheduling of Jobs Lesson Overview In this lesson, you learn about event-based scheduling of jobs.

Lesson Objectives After completing this lesson, you will be able to: • •

Schedule event-dependent jobs Define and trigger events

Business Example The administrator schedules background jobs and monitors the correct process of the system's background processing.

Event-Based Scheduling An event is a signal to the background processing system that a particular status has been achieved in the SAP system. The background processing system receives events and then starts all jobs that are connected with this event.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

531

Unit 11: Scheduling Background Tasks

TADM12_1

Figure 237: Event-Dependent Start of a Job

Hint: The parameter rdisp/btcname is no longer evaluated in newer releases and has no ongoing significance. For more information, see SAP Note 1035355: Background processing events: handling of target server . Event-dependent jobs can be scheduled with one of the following three start conditions: After event The job starts after a defined event is received by the SAP system. At operation mode With this option, you can link a job to the activation of an operation mode when scheduling the job. After job In this way, you can create simple job chains where the execution of the successor job can be made dependent on the status of the predecessor job.

Events You can create and trigger events with the function Background Events: Overview and Administration (transaction SM64). There is a distinction between system events and user events. System events are events predefined by SAP that you cannot modify and should not trigger manually.

532

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Event-Based Scheduling of Jobs

Figure 238: Definition and Triggering of Events in transaction SM64

Events can be triggered in various ways: • • •

Manually through transaction SM64 Through the ABAP program BTC_EVENT_RAISE At operating system level using the program sapevt. Note: Further possibilities are: the function module BP_EVENT_RAISE or the RAISE method for the CL_BATCH_EVENT class. Note: Please consider in this context SAP Note 1645120: Trigger of a background event is unknown.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

533

Unit 11: Scheduling Background Tasks

TADM12_1

Figure 239: The syntax for the program sapevt

Note: The syntax for the program sapevt is described in SAP Note 802172: sapevt (Version 4): Release-independent version . It explains the individual parameters in detail. For example: The output of sapevt event=MYEVENT name=SID mshost=twdf9999.wdf.sap.corp is send to a trace file dev_evt in the directory in which sapevt was called. To be able to react to external events, the SAP system must be active. Otherwise an event triggered by an external program is lost. Hint: If the name of the event contains a blank character, you must specify it in quotation marks when you call sapevt, for example, sapevt "MY EVENT" name=SID mshost=twdf9999.wdf.sap.corp. Note: If you want to call sapevt from a remote host, read SAP Note 374379: Triggering SAPEVT from a remote host.

534

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Event-Based Scheduling of Jobs

Figure 240: Examples for calls of sapevt

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

535

Unit 11: Scheduling Background Tasks

536

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM12_1

2013/Q1

TADM12_1

Lesson: Event-Based Scheduling of Jobs

Exercise 22: Event-Dependent Jobs Exercise Objectives After completing this exercise, you will be able to: • Schedule event-dependent jobs • Define and trigger events

Business Example The administrator schedules background jobs and monitors the correct process of the system's background processing.

Task: Events and event-dependent jobs In this exercise you will perform the following activities: 1. Create a customer event 2. Copy an existing job 3. Give the created event as the start condition to the copied job 4. Trigger the created event using CCMS 5. Optional: Trigger the created event at the operating system level Caution: Don’t change any system events. 1.

Create a customer event EVENT_##.

2.

Copy the job TIME-## that you created in a previous exercise to EVENT-##. Note: If there is no job TIME-## in your system, you can also - as specified by the trainer- copy a different job or create a new one.

3.

Schedule the job EVENT-## periodically to the event EVENT_##.

4.

Trigger the event EVENT_## in a new session using CCMS tools and refresh the job overview.

5.

(Optional): Trigger the event EVENT_## at operating system level for your SAP system and refresh the job overview. Hint: If the name of the event you defined, contains a blank character, you must specify the event name in quotation marks when you call sapevt. Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

537

Unit 11: Scheduling Background Tasks

TADM12_1

Result Congratulations! You can now create and trigger events to start scheduled jobs at them.

538

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Event-Based Scheduling of Jobs

Solution 22: Event-Dependent Jobs Task: Events and event-dependent jobs In this exercise you will perform the following activities: 1. Create a customer event 2. Copy an existing job 3. Give the created event as the start condition to the copied job 4. Trigger the created event using CCMS 5. Optional: Trigger the created event at the operating system level Caution: Don’t change any system events. 1.

2.

Create a customer event EVENT_##. a)

Start transaction SM64.

b)

Choose Create.

c)

Under Event enter EVENT_##

d)

Under Description enter any descriptive text.

e)

Do not select the System checkbox.

f)

Save the event definition.

Copy the job TIME-## that you created in a previous exercise to EVENT-##. Note: If there is no job TIME-## in your system, you can also - as specified by the trainer- copy a different job or create a new one. a)

Call transaction SM37.

b)

Use the relevant selection criteria to view the job TIME-##.

c)

Select the job TIME-##.

d)

Choose Job → Copy.

e)

Enter EVENT-## as the New job name.

f)

Choose Copy.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

539

Unit 11: Scheduling Background Tasks

3.

TADM12_1

Schedule the job EVENT-## periodically to the event EVENT_##. a)

Call transaction SM37.

b)

Use the relevant selection criteria to view the job EVENT-## (display jobs with the status Sched.).

c)

Select the job EVENT-##.

d)

Choose Release.

e)

Choose the After Event pushbutton.

f)

Select the event EVENT_##.

g)

Leave the Parameter field empty.

h)

Select the Periodic Job checkbox.

i)

Save the start condition. Hint: If the system does not display the job EVENT-## in the job overview after its release, you need to adapt the selection criteria on the initial screen of transaction SM37: In the Job Start Condition area under or after event, select the following entries: EVENT_## (or *).

4.

Trigger the event EVENT_## in a new session using CCMS tools and refresh the job overview. a)

Start the transaction SM64 in a new session window.

b)

Select your event EVENT_##.

c)

Choose Trigger.

d)

Leave the Parameter field empty.

e)

Choose Trigger again.

f)

Switch to the session window with the job overview.

g)

Refresh the job overview.

h)

The job EVENT-## should have run successfully and been rescheduled.

Continued on next page

540

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Event-Based Scheduling of Jobs

5.

(Optional): Trigger the event EVENT_## at operating system level for your SAP system and refresh the job overview. Hint: If the name of the event you defined, contains a blank character, you must specify the event name in quotation marks when you call sapevt. a)

Log on to your SAP system at operating system level.

b)

Open a Command Prompt (Execute the command cmd).

c)

Execute the following command: sapevt event=EVENT_## name= mshost=twdfXXXX.wdf.sap.corp where ## stands for your group number, for your system name XXXX for the server number (e.g: sapevt event=EVENT_00 name=DCC mshost=twdf9999.wdf.sap.corp).

d)

Open the trace file dev_evt that was created in the current directory.

e)

Refresh the job overview.

f)

The job EVENT-## should have run successfully and been rescheduled.

Result Congratulations! You can now create and trigger events to start scheduled jobs at them.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

541

Unit 11: Scheduling Background Tasks

TADM12_1

Lesson Summary You should now be able to: • Schedule event-dependent jobs • Define and trigger events

Related Information SAP Notes: • • • •

542

SAP Note 104574: Error when starting server: rdisp/btcname is not defined SAP Note 802172: sapevt (Version 4): Release-independent version SAP Note 1021079: Event history SAP Note 1038669: Background jobs with start condition 'Event' do not start

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Background Processing: Further Topics

Lesson: Background Processing: Further Topics Lesson Overview In this lesson, you learn about further, special functions for background processing.

Lesson Objectives After completing this lesson, you will be able to: •

Use additional, special functions of background processing

Business Example You want to use the background processing resources more efficiently.

Reservation for Class A Jobs In normal operation, every background work process processes jobs of every priority. You can, however, reserve a number of the configured background work processes as desired for high priority jobs, that is, jobs of class A. The reservation of work processes for class A jobs does not reserve any particular work processes. Rather it ensures that a particular number of background work processes is kept free, if possible, for jobs of class A. Jobs in job classes B and C can only be started if the defined number of work processes for possible class A jobs remains free.

Figure 241: Reservation for Class A Jobs

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

543

Unit 11: Scheduling Background Tasks

TADM12_1

To set the number of reserved background work processes for class A, you can define an operation mode in transaction RZ04 (maintenance of operation modes and instances) and maintain the work process distribution for this operation mode.When doing so, you have the option of reserving work processes. If the class A workload is small, or bottlenecks rarely occur in background processing - in other words, at least one background work process is usually free there are probably no advantages to reserving a work process for class A jobs. In this case, reservation will simply mean that a work process is seldom used. We recommend that you do not reserve more than one background work process for processing class A jobs for each instance. If you want to use the functionality of reserving background work processes for jobs of class A, it is usually sufficient to reserve one background work process per system for processing class A jobs.

Execution Targets Only instances with background work processes or a job server group can be used to specifically schedule a background task. A job server group contains one or more instances with available background work processes. Groups of this type can be used in the same way as logon groups for dialog users. It is also possible to process background tasks from different applications on selected instances.

Figure 242: Execution Targets and Job Server Groups

544

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Background Processing: Further Topics

You can set up a job server group in transaction SM61 (menu path: Tools → CCMS → Background Processing → Background Objects). To do this, call the transaction and then choose the Job Server Groups. You can then define your job server group and assign your instances. There is a default job server group, that you can use as described in SAP Note 786412: Determining execution server of jobs w/o target server.

Background Users With the classic definition of jobs using transaction SM36, you can assign each step of the job to a (execution-) user (see the figure). The specified user is used for the authorization checks during the execution of the step. By default, the name of the logged-on user appears in this field, and your job is performed using your authorizations. Enter a different user name, if your job should not be performed using your own authorizations. To be able to do this, you must, however, have the appropriate authorization (authorization object S_BTCH_NAM) to enter names other than your own in the User field.

Figure 243: Background User

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

545

Unit 11: Scheduling Background Tasks

TADM12_1

It is useful to set up background users for various work areas that have the necessary authorizations for the required activities, and that can be used by users with the same authorizations to schedule background tasks in this work area (such as for system administration). Background users have user master records that are specifically intended for background processing authorizations. Note: An end user should not be allowed to use a user as background user, which has more permissions as his dialog user. Otherwise, this might pose a security risk. When creating background users, use the user type System. A dialog logon with a user of this type is not possible. In the same way, users of this type are exempt from the usual settings for the validity period of a password. The password of a system user can only be changed by user administrators using transaction SU01 (Users → Change Password). When using the Job Wizard to define a job, the name of the user who is logged on is included in the authorization check for each step.

Using External Programs The background processing system differentiates between external commands for normal users and external programs, which mainly should only be used by system administrators. The purpose of this differentiation is to give system administrators the option to run any required external program, while normal users are restricted to external commands for which there are name-based authorization checks. In both cases, the program sapxpg is called at operating system level. sapxpg then starts the relevant program at operating system level.

546

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Background Processing: Further Topics

Figure 244: Using External Programs

External commands are specific commands or programs called at operating system level, predefined in the SAP system by an system administrator. They are protected by authorizations so that end users can only schedule the commands for which the system administrator has assigned them the authorization explicitly. You can, therefore, provide functions outside the SAP system, at operating system level, for users of the SAP system. External programs are unrestricted commands that are neither predefined nor restricted by authorizations. A user with administration authorization can enter any external program in a job step. No further authorization check is performed against the user master data before the execution of the command. External programs provide an administrator (user with administration authorization for external commands (authorization object S_RZL_ADM: Background Processing: Background Administrator)) the flexibility to run any required host system command in the SAP system without administrative preparation.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

547

Unit 11: Scheduling Background Tasks

TADM12_1

Figure 245: Definition and Use of External Commands in transaction SM69

548

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Background Processing: Further Topics

The creation of external commands requires the following steps: 1. 2. 3.

Call the transaction SM69 (Tools → CCMS → Configuration → Display/Change External Commands). Choose Create. Make entries for the new command. • •

•

•

•

4.

External commands are uniquely identified with a name (beginning with Y or Z) and an operating system type. The Type field fills automatically. Specify an executable operating system command (if required with the complete path) and specify any additional required or optional parameters. Select the Additional Parameters Allowed checkbox if users are allowed to specify additional parameters when they execute the external command later or schedule it in a job. The additional parameters are added to parameter strings that may already be specified under Parameters for Operating System Command. The Trace field should usually be left blank. To follow the execution of an external command, use the trace parameter for the function module SXPG_COMMAND_EXECUTE. If you have defined an additional authorization check, enter the name of the function module that performs the check in the Check Module field. This is usually a customer copy of the function module SXPG_DUMMY_COMMAND_CHECK. The system calls the function module automatically if a user tries to execute the external command or schedule it in a job.

Choose Save. To return to the command overview, choose Back (

).

Control Flags You can make specifications about the task and other runtime options using control flags. You do not normally need to change the default values.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

549

Unit 11: Scheduling Background Tasks

TADM12_1

Figure 246: Control Flags for External Programs/Commands

You can, for example, specify: •

•

Whether the process is to be logged. The output data is written to the log as it is output by the external program. The language can differ here from your logon language. You can also call additional information about the data of an external program in the job log. How the SAP control program should end and whether the external program triggers an event. After you have started service programs with the background processing system (such as daemons in UNIX systems), they remain active after the start. They are not ended and do not return to the SAP background processing system, as is the case with other programs. If you start a service program, you should not use the control flag setting Job waiting for ext. termination when scheduling the job.

You can use the F1 help to display additional information about the meaning of the control flags on the Edit Control Flags for External Programs screen.

Extending the Standard The job scheduling options described in the previous lessons do not cover all possible requirements. You can implement more complex scenarios – in addition to the use of SAP Central Process Scheduling (SAP CPS) – in the following ways:

550

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Background Processing: Further Topics

The SAP system has various internal function modules that support you when defining your own job processes. These function modules are in the function groups BTCH and BTC2. You can define any complex scenarios with the help of these function modules. SAP provides a set of interfaces that enable other system management environments to be connected to the SAP Computing Center Management System (CCMS): • •

The eXternal Monitoring Interface API (XMI-API) interface logs the activities of external users and programs. The eXternal interface for Background Processing (XBP-API) interface allows the use of external job scheduling programs.

With these tools, you can schedule background jobs beyond the boundaries of the SAP system and include non-SAP systems.

Figure 247: Extending the Standard

For a list of certified solutions, see the software category Job Scheduling in the Software Partner Directory. In addition to conventional, local SAP background processing (transactions SM36/SM37), you can use a job scheduler for cross-landscape background processing. Information about SAP Central Process Scheduling by Redwood (SAP CPS) is available in the SAP Community Network under http://scn.sap.com/community/cpsby- redwood. Furthermore, SAP Solution Manager provides some central functions for job scheduling in the Job Management work center.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

551

Unit 11: Scheduling Background Tasks

TADM12_1

Frequently asked questions about background jobs Note the answers given in SAP Note 31503: FAQ: Background jobs. How can I debug programs that run in background? Note the procedure given in SAP Note 573128: Debugging programs in the background. Identify jobs with deleted users Check the solution given in SAP Note 1533612: Identify jobs with deleted users. How often do which jobs run? Note the solution given in in SAP Note 1439806: Listing jobs according to their frequency. Transaction SM37C (Extended Job Selection) offers you an additional option to get this valuable information: Goto → Jobstatistics. Why does my job not start? Note the procedure described in in SAP Note 165084: Why does my job not start?. How can I see who has deleted which job? Note the solution given in SAP Note 850885: Logging the deletion of jobs. How can I log calls of external commands? Note the solution given in SAP Note 1663158: Logging calls of external commands. Job selection by step user, SM37C Note the solution given in SAP Note 1742282: Job selection by step user. Meaning of program BTC_OPTIONS_SET The program BTC_OPTIONS_SET offers you versatile options for background processing in your system. For each option in this report, the SAP note is mentioned, which provides additional information for the according function. Use of transactions SMX, SM37DISP to display jobs Note the solution given in SAP Note 1458243: SMX displays jobs from other clients and SAP Note 1665057: Display transaction for background jobs. Job in status ‘released/suspended’ cannot be descheduled Note the solution given in SAP Note 1685229: Job in status ‘released/suspended’ cannot be descheduled. Background processing: Problems using more than 99 work processes Note the solution given in SAP Note 1731654: Problems when more than 99 work processes.

552

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Background Processing: Further Topics

Deleting jobs using RSBTCDEL2 takes a lot time, what should I do? Note the solution given in SAP Note 1751810: Performance problems when deleting jobs using RSBTCDEL2. Faulty multiple scheduling of periodic jobs Note the solution given in SAP Note 1130883: Periodic job is scheduled several times. My job uses a printer that does not exist anymore and reports errors Note the porcedure given in SAP Note 1226171: Identifying jobs with deleted printer. In which job has this spool request been created? Note the procedure given in SAP Note 1145265: In which job has this spool request been created?. Alternatively you can access this functionality in the transaction SM37C following the menu path Goto → Further Selections. This path only exists in newly patched SAP systems, for example an SAP NetWeaver 7.3 Enhancement Package 1 with support package 5 (concerning SAP_BASIS). Can I read job logs of jobs from deleted clients? Note the method given in SAP Note 1125558: Logs of jobs from deleted clients cannot be read. Why are background processing jobs not generally transportable? Note the procedure described in SAP Note 51135: Why are bkgd processing jobs not generally transportable?.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

553

Unit 11: Scheduling Background Tasks

554

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM12_1

2013/Q1

TADM12_1

Lesson: Background Processing: Further Topics

Exercise 23: (Optional) Other Topics in the Area of Background Processing Exercise Objectives After completing this exercise, you will be able to: • Check whether background work processes for class A jobs have been reserved • Create external commands • Schedule external commands and external programs as job steps

Business Example The administrator schedules jobs and monitors the system's background processing to ensure that it is running correctly.

Task 1: Reservation for Class “A” Jobs Check the current setting for reserving background work processes for class “A” jobs. 1.

Find out if background work processes are reserved for class “A” jobs in your system.

Task 2: Using External Programs Use an external program as a job step. 1.

Use the transaction SM36 to create a job with the following characteristics: Job Name

EXT-PROG-##

Job Class

C (Default)

Execution target

Leave empty (Default)

1. Step

Program whoami

Start Condition

Event EVENT_##

Period

None

2.

(Optional) Create an external command Z_OSUSER_## that executes the operating system command whoami.

3.

Use the transaction SM36 (without the wizard) to create a job with the following characteristics:

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

555

Unit 11: Scheduling Background Tasks

4.

TADM12_1

Job Name

EXT-CMD-##

Job Class

C

Target Server

Leave empty

1. step

Command Z_OSUSER_## or ZKERNEL

Start Condition

After Job EXT-PROG-##

Period

none

Trigger the event EVENT_## in a new session using CCMS tools and refresh the job overview.

Result Congratulations! You can now create external commands and schedule external programs as job steps.

556

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Background Processing: Further Topics

Solution 23: (Optional) Other Topics in the Area of Background Processing Task 1: Reservation for Class “A” Jobs Check the current setting for reserving background work processes for class “A” jobs. 1.

Find out if background work processes are reserved for class “A” jobs in your system. a)

You can only check whether you have defined background work processes for jobs of job class A using transaction RZ04 (Maintain Operation Modes and Instances). Choose Instances/Operation Modes there and check column BPA.

Task 2: Using External Programs Use an external program as a job step. 1.

Use the transaction SM36 to create a job with the following characteristics: Job Name

EXT-PROG-##

Job Class

C (Default)

Execution target

Leave empty (Default)

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

557

Unit 11: Scheduling Background Tasks

TADM12_1

1. Step

Program whoami

Start Condition

Event EVENT_##

Period

None

a)

Start transaction SM36.

b)

Under Job Name, enter EXT-PROG-##.

c)

For the Job Class, select A.

d)

Choose Step. Choose External Program. Enter the specifications for the step that are listed in the task and choose Save. Note: You can analyze the control flags here – retain the default values. Then choose Back (

2.

).

e)

Choose Start Condition. Choose After Event and select EVENT_##. Leave the Parameter field empty, do not select the Periodic Job checkbox, and choose Save.

f)

Finally, on the initial screen of transaction SM36, choose Save once.

(Optional) Create an external command Z_OSUSER_## that executes the operating system command whoami. a)

Start transaction SM69.

b)

Choose Create.

c)

Under Command Name, enter Z_OSUSER_##, and under Operating System Command, enter whoami. Do not change the other default values and save the command. You could also go back to the overview and execute your command to test it.

3.

Use the transaction SM36 (without the wizard) to create a job with the following characteristics: Job Name

EXT-CMD-##

Job Class

C

Target Server

Leave empty

Continued on next page

558

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Background Processing: Further Topics

1. step

Command Z_OSUSER_## or ZKERNEL

Start Condition

After Job EXT-PROG-##

Period

none

a)

Call transaction SM36.

b)

Under Job Name, enter EXT-CMD-##.

c)

Choose Step. Select External Command. Make the entries for the step that are specified in the task. Under Operating System, select Windows NT and choose Save. Note: You can analyze the control flags here – retain the default values. Then choose Back (

4.

).

d)

Choose Start Condition. Choose After Job and under Name, enter EXT-PROG-##. Then choose Save.

e)

Finally, on the initial screen of transaction SM36, choose Save once.

Trigger the event EVENT_## in a new session using CCMS tools and refresh the job overview. a)

Start the transaction SM64 and select your event EVENT_##.

b)

Choose Trigger, leave the Parameter field empty, and choose Trigger again.

c)

After you have refreshed the job overview, the jobs EXT-PROG-## and EXT-CMD-## should each have run once successfully.

Result Congratulations! You can now create external commands and schedule external programs as job steps.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

559

Unit 11: Scheduling Background Tasks

TADM12_1

Lesson Summary You should now be able to: • Use additional, special functions of background processing

Related Information SAP Notes: SAP Note 24092: Distribution of background jobs on application server SAP Note 101146: Batch: Authorization object S_BTCH_JOB, S_BTCH_NAM SAP Note 677435: Overview: external programs and external commands SAP Note 686765: Security check when you execute external commands SAP Note 854060: Authorizations for external commands SAP Note 859104: Authorizations for external programs

560

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood Lesson Overview In this lesson the job scheduling capabilities of SAP Central Process Scheduling are introduced. You will learn about some features offered by SAP CPS.

Lesson Objectives After completing this lesson, you will be able to: • •

Explain how to use SAP Central Process Scheduling by Redwood Name the most important features of SAP CPS

Business Example In every system landscape you have the need to run and monitor background processes. SAP Central Process Scheduling by Redwood is an additional tool that became available with SAP NetWeaver 7.0.

SAP Central Process Scheduling by Redwood The SAP Central Process Scheduling application by Redwood (SAP CPS) is a solution that centrally manages and orchestrates the underlying processes that need to take place across multiple applications and organizations. It supports event-driven and dynamic processes by automatically monitoring your environment and starting or managing processes and process chains. It offers complete, centralized management of all business processes, including scheduled or batch processes. It is seamlessly integrated with the native SAP management tools within SAP NetWeaver and SAP Solution Manager and provides integration with SAP- and non-SAP applications.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

561

Unit 11: Scheduling Background Tasks

TADM12_1

Job Scheduling Management with SAP Central Process Scheduling by Redwood (SAP CPS): •

Centrally manage and orchestrate the individual process steps that are required to take place across different applications and organizational units in order to complete a complex business process. –

• •

Process automation connects IT infrastructure and the business user environment. – Process automation ensures reliable delivery of services to business users and customers. Seamless integration with SAP and non-SAP applications. Seamless integration with: – –

SAP NetWeaver AS ABAP SAP Solution Manager

In the graphic below you see the features SAP CPS offers in the free-of-charge version on the one hand and in the full version (at cost) on the other hand. Main differentiators between the basic and the full version are event-driven job scheduling, the job handling on OS level and the ability to run jobs or job chains across systems.

Figure 248: Features of SAP CPS - Comparison of Basic and full Version

In the figure below the technical architecture of SAP CPS is shown. SAP CPS is a Java application that runs on top of an SAP NetWeaver AS Java and saves all its configuration data in the Java schema of the database (1). All SAP CPS related tables have the prefix “JCS_” in their name.

562

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

Figure 249: SAP CPS - Architecture

The so called Process Servers (2) are RFC-clients running within SAP CPS. Each Process Server can connect to exactly one RFC server (equivalent to a client in an SAP system). The appropriate interfaces XBP, BW-SCH, and JXBP are their counterparts on the connected remote systems. If a non-SAP system has to be connected, an RFC server is required on that remote host. On these systems the so called Platform Agent (3) has to be installed to enable SAP CPS to connect to them. A browser-based Web UI (4) is used to access SAP CPS.

Figure 250: Integration of SAP Central Process Scheduling by Redwood with SAP Solution Manager

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

563

Unit 11: Scheduling Background Tasks

TADM12_1

SAP Solution Manager and SAP CPS interact by using the Application Scheduling API. The request for a job can be managed by SAP Solution Managers Change Request Management process. Job descriptions can be kept centrally in SAP Solution Manager. Job status results can be analyzed and presented in SAP Solution Managers Business Process Monitoring. • • • • • •

Job request via web form Change request management for Job Scheduling Central documentation of jobs Integration of SAP CPS Integration of the job monitoring into business process monitoring Automated data exchange between job request, change request management, job documentation, SAP CPS and business process monitoring

For details on how to install and customize the Process Scheduling Adapter see https://service.sap.com/rkt → SAP Solution Manager → SAP Solution Manager Extensions → Process Scheduling Adapter for SAP Solution Manager. SAP CPS: free version and full version, a simple comparison referring to Isolations Groups Isolation Groups in the free version In the free version an isolation group can hold exactly one connection definition to a client of an SAP system and manage and control jobs there. Isolation Groups in the full version In the full version an isolation group can hold several connection definitions to clients of SAP systems and manage and control jobs there.

First Steps in SAP CPS: Logon, Isolation Groups, System Definition SAP CPS is an application, which in previous releases had to be deployed initially with the Software Deployment Manager (SDM). It is now part of the delivery of SAP NetWeaver AS Java and will be patched using the SDM. In AS Java the three following (SAP CPS related) actions are available in UME (User Management Engine): • • •

Redwood.com/Scheduler/AccessScheduler Redwood.com/Scheduler/ManageScheduler Redwood.com/Scheduler/ManageSchedulerIsolation

To grant administration access to SAP CPS, you need to define an UME role with those actions or assign those actions to an existing role. A user having the assigned actions can start the scheduler of SAP CPS in a Web Browser with the URL http://:/scheduler.

564

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

When you log on for the first time to the "free version” of SAP CPS, you have the option to store license data. Basic functions (e.g. the communication of SAP CPS with a client of an SAP system) are available when you proceed as presented in the following figure.

Figure 251: First Logon to SAP CPS, Free Version

Please note the following sources which provide fundamental information for working with SAP CPS: • • • •

2013/Q1

SAP Community Network: http://scn.sap.com/community/cps-by-redwood SAP CPS Administration Guide: http://scn.sap.com/docs/DOC-4989 Further documents on SAP CPS: http://scn.sap.com/community/cps-byredwood/content SAP Note 1616638: SAP CPS license key activation of additional functionality

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

565

Unit 11: Scheduling Background Tasks

TADM12_1

Working with the basic version of SAP CPS, you can only deal with one system per logon. Every system of the system landscape needs a so called isolation group with assigned users. This means, as a first step you have to create the isolation group and assign the user(s) that are allowed to schedule jobs on the system assigned to this isolation group. Hint: You have to add your own user to the isolation group, too, if you want to schedule jobs on the system assigned to this isolation group.

Figure 252: Creating an Isolation Group

1. 2. 3. 4. 5. 6.

Log on to SAP CPS Go to the area Security. Use the context menu for the entry Isolation Groups. Choose the entry New Isolation Group. Choose a Name and Description for the new isolation group. Save your entries using Save and Close.

After creating an isolation group, you need to assign one or more users to it.

566

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

Figure 253: Import User (for an Isolation Group)

Importing users into an isolation group: 1. 2. 3. 4.

Log on to SAP CPS. Choose the area Security. Choose the entry Isolation Groups. Select on the right-hand side of your screen the newly created isolation group and open the context menu. 5. Choose Import Users from the context menu. 6. Enter search criteria for the user to be imported on the next screen. 7. Mark the user, after successful search. 8. Choose Import. 9. Check the feedback from the system, OK means that the import was successful. 10. Import further user data or end this activity by choosing Cancel. After you have created the isolation group and assigned users to it, you have to log off and on again to work with this isolation group.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

567

Unit 11: Scheduling Background Tasks

TADM12_1

Figure 254: Logon to SAP CPS with more than one Isolation Group

If a user has been assigned to more than one isolation group (see above, Import), you can choose the isolation group you wish to work for during logon. In the “Free Version” this will also determine the client of an SAP system for which you can control jobs. The next step is to create an SAP system definition within the isolation group.

Figure 255: Creating an SAP system in an Isolation Group

568

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

Creating an SAP system within an isolation group: 1. 2. 3. 4.

Choose the area Environment. Choose the entry SAP. Select New SAP System (from Wizard)... from the context menu. Using the wizard, enter the following data: •

For Name you will give a denomination for the client to connect to of the SAP system Caution: It is important to choose this name identical to the name of the isolation group to which your SAP system belongs. If you choose a new name, a new isolation group with this name will be created!

• • • • 5. 6. 7.

Default Job Time Zone: Choose a time zone of according to your needs Connection Type: Choose (e.g.) Application Server Application Server Host: Enter the fully qualified name of your server System Number: Provide the two-digit instance number of the instance to be connected. Execute Check Connection for the first time. After successful check, the lower part the entry screen becomes accessible. Using the wizard, enter the following data:

• • • • • 8. 9.

2013/Q1

Client Number: Enter the client to connect to. Username: Provide a user name within the client of the SAP system. Password: Enter the password of the chosen user. Default Client: Enter the client that you would like to connect to. SAP Language: Select a language supported by your SAP system or leave the default. Execute Check Connection for the second time. Choose Save & Close if the check was successful.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

569

Unit 11: Scheduling Background Tasks

TADM12_1

Figure 256: Assigning an SAP system to an Isolation Group

For job control, the process server connects to the SAP system using the connection data provided.

Figure 257: Started Process Servers

Create a simple Job Definition Create a job definition that will be submitted to the connected SAP system.

570

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

Figure 258: Define a job 1/7

Creating a job 1/7 1. 2. 3. 4.

Select the area Definitions. Choose the entry Job Definitions. Select the entry SAP_AbapRun on the right-hand side of the screen. Select the value Submit from the context menu of this entry.

Figure 259: Define a job 2/7

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

571

Unit 11: Scheduling Background Tasks

TADM12_1

Creating a job 2/7 1. 2. 3.

SAP-System from the input help. SAP Client from the input help. SAP Job Name: a denomination of your choice. Note: If you would like to be able to distinguish jobs in your SAP system (using transaction SM37), that have been created by SAP CPS from those jobs that have been created within the SAP system, then you might want to think about using prefixes for jobs created by SAP CPS.

4. 5. 6. 7.

ABAP Program: enter the name of the program to be executed within the SAP system. ABAP Variant: if required, you can provide the name of a variant that is known in the SAP system (for the program you entered). The other fields can be left on default values. Choose Next >. Note: Further information on the possible input values can be found in the documentation on SAP CPS.

Figure 260: Define a job 3/7

572

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

Creating a job 3/7 1. 2. 3.

Select the start conditions according to your needs. You can use the default values for the other fields. Choose Next >. Note: Further information on the possible input values can be found in the documentation on SAP CPS.

Figure 261: Define a job 4/7

Creating a job 4/7 1. 2.

2013/Q1

Use the default settings. Choose Next >.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

573

Unit 11: Scheduling Background Tasks

TADM12_1

Figure 262: Define a job 5/7

Creating a job 5/7 1.

2.

Select which action should be executed after the job has been transferred to the SAP system. For example, you can choose Show Job, if you scheduled a short-running job with start condition Now. Choose Submit.

Figure 263: Define a job 6/7

574

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

Creating a job 6/7 1.

Refresh the resulting display using Actions → Refresh.

Figure 264: Define a job 7/7

Using transaction SM37 you can now find your scheduled job. Now you can start working with SAP CPS. A full overview on the functions offered by SAP CPS can be found in the Administration Guide, which can be accessed by using the button Product Information in the upper right-hand corner of your SAP CPS interface

Further Infomation: Import Jobs from the ABAP System (Optional) If you want to run and control background jobs you have previously submitted in your SAP system via transaction SM36 now by SAP CPS, you can use the function ImportCCMSJobs. You can import CCMS job steps as separate job definitions or just make the job chains use the SAP_AbapRun job definition; the latter keeps the number of job definitions in SAP CPS low and allows you have a better overview. The downside is that you cannot easily schedule a step on its own without filling in the parameters yourself or submitting the job chain with steps disabled.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

575

Unit 11: Scheduling Background Tasks

TADM12_1

To import your CCMS jobs from an SAP System: 1. 2. 3.

Choose Definitions → Job Definitions and locate the job definition SAP_ImportCCMSjobs. From the context menu, choose Submit. Fill in the corresponding information in the tabs Parameters and Generation Settings. The following fields are mandatory on the Parameters tab: • • •

SAP System SAP Client SAP Job Name

The following fields are mandatory on the Generation Settings tab:

4. 5.

576

• Name for the generated job definition • Overwrite existing job definitions? • Application • Create a job definition for each step? • Add step numbers to SAP job names? • Retrieve joblog? • Retrieve spoollist? • Delete job when finished? Choose scheduling on the left-hand side and choose the queue belonging to the SAP System. Choose Submit.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

Exercise 24: Job Scheduling with SAP CPS Exercise Objectives After completing this exercise, you will be able to: • Create an isolation group for your user and assign an SAP system. • Create a job in SAP CPS and submit it to the SAP system.

Business Example To use the basic version of SAP CPS you have to create a separate isolation group for each system you want to schedule jobs in. Hint: For this exercise you will be using the AS Java of the SAP Solution Manager system within your training system landscape for scheduling a job for your SAP ECC system. Your partner group(s) will also use the same SAP CPS of SAP Solution Manager, to schedule a job on their SAP ECC system. This means that there will be two isolation groups with one assigned SAP ECC system each, within the SAP CPS of the AS Java of your SAP Solution Manager.

Task 1: Isolation Group and System Connection Create an isolation group in SAP CPS and assign your user and your system to it. 1.

Access SAP CPS using an URL like this http://twdf#####.wdf.sap.corp:58000/scheduler. Log on with your course user. After the first log on you might be required to create a license. Create an isolation group and assign your user to this group.

2.

In the new isolation group, create an entry for your SAP ECC system.

Result You have successfully connected an SAP system to SAP CPS.

Task 2: Create and schedule a Job using SAP CPS Create and submit a simple Job from SAP CPS to your SAP ECC system. 1.

2013/Q1

In case you are no longer logged on to SAP CPS, please log on again. Use SAP CPS to create a simple job definition, named CPS_Job_1. This job should immediately execute the report RSPFPAR without variant and SAP CPS should display the status of this job after execution. Check the successful execution of this job using the job overview in your SAP ECC system (transaction SM37).

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

577

Unit 11: Scheduling Background Tasks

TADM12_1

Solution 24: Job Scheduling with SAP CPS Task 1: Isolation Group and System Connection Create an isolation group in SAP CPS and assign your user and your system to it. 1.

Access SAP CPS using an URL like this http://twdf#####.wdf.sap.corp:58000/scheduler.

Continued on next page

578

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

Log on with your course user. After the first log on you might be required to create a license. Create an isolation group and assign your user to this group.

2.

a)

Open the following URL in a browser window on your training server (host): http://twdf#####.wdf.sap.corp:58000/scheduler. Replace #### with your actual server number.

b)

Log on to SAP CPS using your training user.

c)

After logging on you may need to create a license. To do this, enter SAP AG (e.g.) as Company Name.

d)

Choose Activate Free of Charge License.

e)

Deactivate the check-box for regular update checks.

f)

Select the area Security.

g)

Open the context menu for the entry Isolation Groups.

h)

From the context menu, choose New Isolation Group....

i)

Create the isolation group _##, where you replace by the SID of your SAP ECC system and ## with your group number.

j)

Enter a description for your new isolation group.

k)

Save your entries using Save & Close.

l)

Select your isolation group from the right-hand side of the screen and open the context menu.

m)

Choose Import Users from the context menu.

n)

Enter a search string for your course user name - this will be the user to be imported.

o)

Mark your course user, when it has been found successfully.

p)

Choose Import.

q)

Check the feedback from SAP CPS, OK means that the import was finished successfully.

r)

Choose Cancel because you don't want to import further users.

s)

Log off from SAP CPS.

In the new isolation group, create an entry for your SAP ECC system. a)

Open the following URL in a browser window on your training server (host): http://twdf#####.wdf.sap.corp:58000/scheduler. Replace #### with your actual server number.

b)

Log on to SAP CPS using your training user. Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

579

Unit 11: Scheduling Background Tasks

TADM12_1

c)

You might be required to select a specific isolation group. Choose the isolation group that you created earlier.

d)

Open the area Environment.

e)

Select the entry SAP.

f)

Choose New SAP System (from Wizard)... from the context menu.

g)

Enter the following data with the help of the Wizard: •

• • • •

Name: Enter _##, where you replace by the SID of your SAP ECC system and ## with your group number. Make sure that you enter the same name here as for the name of the isolation group. Default Job Time Zone: Choose a time zone according to your needs. Connection Type: Choose Application Server. Application Server host: Enter the fully qualified name of your server. System Number: Enter the two-digit instance number for the Primary Application Server of your SAP ECC system.

h)

Execute Check Connection a first time.

i)

After successful connection check, the second entry area becomes available.

j)

Enter the following data: • • • • •

Client Number: Enter 100. Username: Enter your username in client 100 of the SAP ECC system. Password: Enter the password for your course user. Default Client: Mark the check box. SAP Language: Enter one of the supported logon languages of your SAP ECC system, e.g. EN.

k)

Execute Check Connection a second time.

l)

After successful connection check, choose Save&Close.

m)

Once the system is created, SAP CPS automatically creates a process server for the system and a job queue.

Result You have successfully connected an SAP system to SAP CPS.

Continued on next page

580

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood

Task 2: Create and schedule a Job using SAP CPS Create and submit a simple Job from SAP CPS to your SAP ECC system. 1.

In case you are no longer logged on to SAP CPS, please log on again. Use SAP CPS to create a simple job definition, named CPS_Job_1. This job should immediately execute the report RSPFPAR without variant and SAP CPS should display the status of this job after execution. Check the successful execution of this job using the job overview in your SAP ECC system (transaction SM37). a)

Choose the area Definitions.

b)

Select the entry Job Definitions.

c)

In the right-hand side of your screen select the entry SAP_AbapRun.

d)

Choose the value Submit from the context menu.

e)

Enter the following data on the tab Parameters: • • • • • •

SAP System: Select from from input help. SAP Client: 100. SAP Job Name: CPS_Job_1. ABAP Program: RSPFPAR. ABAP Variant: Leave blank. Leave the remaining fields on this tab on default.

f)

Choose Next >.

g)

Leave the default values for Time and Dates.

h)

Choose Next >.

i)

Leave the default values for Scheduling.

j)

Choose Next >.

k)

Select Show Job on the screen for Submit Summary.

l)

Choose Submit.

m)

Refresh the resulting display by choosing Actions → Refresh.

n)

Check in your SAP ECC system the successful execution of this job by using transaction SM37.

Result Congratulations! You have successfully scheduled a job from SAP CPS within your SAP ECC system.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

581

Unit 11: Scheduling Background Tasks

TADM12_1

Lesson Summary You should now be able to: • Explain how to use SAP Central Process Scheduling by Redwood • Name the most important features of SAP CPS

582

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Appendix: Job Management

Lesson: Appendix: Job Management Lesson Overview This lesson gives you an overview of the Work Center Job Management.

Lesson Objectives After completing this lesson, you will be able to: •

Use the Work Center Job Management to schedule and monitor background jobs

Business Example You want to get a general survey about the jobs in your system landscape by using the work center Job Management.

Work Center: Job Management The work center Job Management is the central access to all functions for documenting, scheduling, and monitoring background jobs. It comprises views to display and edit job requests, job documentation, scheduled jobs, and job alerts. You can perform typical tasks in job scheduling. As a prerequisite to use this work center, a business partner is assigned to your system user.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

583

Unit 11: Scheduling Background Tasks

TADM12_1

Figure 265: Work Center Job Management

Caution: To use the functions offered by this Work Center in conjunction with the features of SAP CPS, you need to follow SAP Note 1729766: CPS - Solution Manager integration setup. Please also follow the information given in SAP Note 1616638: SAP CPS license key activation of additional functionality. The work center Job Management offers the following features; Overview information Overview information is available for the following views: • • • • •

Job requests Job Documentation Central process scheduling Job Scheduling Task Inbox

Job Requests

584

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Appendix: Job Management

Job Requests are listed. You see: • • •

All job requests you created All job requests you are assigned to as processor All Service Desk messages from Job Monitoring that the system reports in the context of Business Process Monitoring

Job Documentation You get a list of job documentation. You can define queries and set filters to select data. When you select job documentation from the list, the system displays details of the job documentation below the list, for example, further information about the steps. To reach job documentation, select the job documentation and choose Display. If authorized, you can edit job documentation. Job Monitoring • • •

Gives an overview about background jobs. Provides Job Analysis, Job Scheduling, Display of Job Logs, and the Job Documentation Overview SAP Central Process Scheduling by Redwood is integrated here as well.

Common Tasks The following functions could be performed from any view in the work center: • • • • • •

2013/Q1

Create a Job Request for a new job Create Job Documentation Call a template Analyze jobs Scheduling Jobs Directly Importing Jobs into Job Documentation

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

585

Unit 11: Scheduling Background Tasks

TADM12_1

Job Scheduling Management The Job Scheduling Management component enables you to do the following: • •

Central and complete job documentation Management of jobs using, for example, the following standardized workflow:

•

Scheduling of jobs (according to authorizations with or without release) centrally from the SAP Solution Manager system to connected SAP systems. You can import jobs from systems connected using SAP Solution Manager into job documentation. You can import jobs from job documentation into systems connected using SAP Solution Manager.

• • •

You can monitor jobs and see in the analyses to which business processes and business process steps the job belongs.

Figure 266: Workflow for Managing Jobs

Note: Additional information about the Job Scheduling Management standard is available under http://service.sap.com/supportofferings SAP Support Offerings → Support Standards → Media Library → Job Scheduling Management .

586

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Appendix: Job Management

Lesson Summary You should now be able to: • Use the Work Center Job Management to schedule and monitor background jobs

Related Information •

SAP Education Course SM100 SAP Solution Manager Operation and Configuration SAP Library for SAP Solution Manager 7.1, SAP Solution Manager → Using the Work Center

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

587

Unit Summary

TADM12_1

Unit Summary You should now be able to: • Describe the uses of background processing • Schedule and monitor jobs • Schedule time-dependent jobs • Schedule standard jobs • Schedule event-dependent jobs • Define and trigger events • Use additional, special functions of background processing • Explain how to use SAP Central Process Scheduling by Redwood • Name the most important features of SAP CPS • Use the Work Center Job Management to schedule and monitor background jobs

588

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Test Your Knowledge

Test Your Knowledge 1.

A job contains one or more . An ABAP program or an command or program can be executed in such a A job can be triggered at a particular or when a defined occurs.

.

Fill in the blanks to complete the sentence.

2.

What status can a job have? Choose the correct answer(s).

□ □ □ □ □ □ 3.

A B C D E F

Running Released Waiting Finished Error Active

Which of the listed options for time-dependent scheduling of a job can be implemented with the standard resources of the SAP system? Choose the correct answer(s).

□ □ □ □ □ 4.

A B C D E

Daily at 1500 The second-last working day of every month Every nine days, but not on Sundays Only tomorrow at 2355 Every year on April 1 at 0800

If one of the system's ten background work processes is reserved for class A jobs, and jobs are being processed in the other nine work processes, the reserved work process remains free even if a class A job is waiting for execution. Determine whether this statement is true or false.

□ □

2013/Q1

True False

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

589

Test Your Knowledge

TADM12_1

Answers 1.

A job contains one or more steps. An ABAP program or an external command or program can be executed in such a step. A job can be triggered at a particular time or when a defined event occurs. Answer: steps, external, step, time, event After the job is triggered, it is processed without interruption by a single background work process.

2.

What status can a job have? Answer: B, D, F In addition to the three correct answers, a job could have the status Scheduled, Ready, or Canceled.

3.

Which of the listed options for time-dependent scheduling of a job can be implemented with the standard resources of the SAP system? Answer: A, B, C, D, E You can implement all the options mentioned with standard AS ABAP tools.

4.

If one of the system's ten background work processes is reserved for class A jobs, and jobs are being processed in the other nine work processes, the reserved work process remains free even if a class A job is waiting for execution. Answer: False The work processes that are reserved for class A jobs process class A jobs. The option to reserve work processes for class A jobs should only prevent all work processes being occupied with class B or C jobs.

590

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

Unit 12 SAPconnect and SMTP Unit Overview The connection of external communication systems is important in many business processes. This unit discusses the connection of different communication systems to SAP systems using SAPconnect. First, the functions of SAPconnect will be discussed. The SAP system will then be configured for sending and receiving e-mails in SMTP format. Caution: This unit takes place on the SAP system named DCC. The activities in this unit are not using the freshly installed SAP systems S00, E00 and X00. This is necessary, because configuring the newly installed SAP systems in such a way that the related exercises can take place would require significant work before you could start the actual exercises. If you like, you can shut down the freshly installed SAP systems S00, E00 and X00.

Unit Objectives After completing this unit, you will be able to: • • • •

Outline the function of SAPconnect Create a node for sending a remote mail to a different SAP system List the steps required to connect the AS ABAP to an SMTP mail server Configure the AS ABAP for the connection to an SMTP mail server

Unit Contents Lesson: Communication with SAPconnect ..................................592 Lesson: Communication Using SMTP .......................................600 Exercise 25: Sending and Receiving E-Mails by SMTP with AS ABAP ......................................................................... 611

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

591

Unit 12: SAPconnect and SMTP

TADM12_1

Lesson: Communication with SAPconnect Lesson Overview SAPconnect is a standard interface for external communication that enables data to be sent via telecommunication services, such as fax, text messages (pager / SMS), Internet e-mail, and X.400, as well as to printers and between different SAP systems. It allows you to connect external communication components to the SAP system. In this lesson, you will learn the fundamentals of SAPconnect.

Lesson Objectives After completing this lesson, you will be able to: • •

Outline the function of SAPconnect Create a node for sending a remote mail to a different SAP system

Business Example As a member of the system administration team, you want to enable the connection of SAP systems to external communication services.

Overview of the Message Flow in ABAP-based SAP Systems An ABAP-based SAP system offers application developers many ways in which messages can be created and processed. For example, there could be a need to automatically send a confirmation message to the sold-to party after the creation of a sales order.

592

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication with SAPconnect

Figure 267: Message Flow in the AS ABAP

Business Communication Services (BCS) are of central importance in message processing. As of AS ABAP 6.10, these services allow application developers to integrate sending messages internally and externally in their applications without any great effort. In addition to controlling sending and receiving, BCS takes on extensive status handling and makes available all sending information about of an application object. Business Communication Services are the successor to the Business Communication Interface (BCI) and offer the advantage of an object-oriented interface. The sending of messages from SAP applications can be performed directly using BCS. Alternatively, the Post Processing Framework (PPF) can also be addressed first. The PPF provides a uniform interface for generating actions in response to certain conditions (such as printing delivery notes, faxing order confirmations, or triggering approval processes). The PPF is the successor to message control and provides a greater range of functions, simpler connection to the applications, and greater flexibility than its predecessor. BCS (and its predecessor, BCI) can also be used from the tool for forms, SAP Smart Forms (and its predecessor, SAPscript). In addition to automated message creation and processing, you can, of course, also create messages manually using the Business Workplace (previously known as SAP Office). The Business Workplace (transaction SBWP) provides a standard working environment in which every SAP user can perform his or her part of the business and communication processes in the company.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

593

Unit 12: SAPconnect and SMTP

TADM12_1

Figure 268: Transaction SOADM: BCS Administration

As of AS ABAP 7.02, a new transaction SOADM for the administration of Business Communication Services is available. From this new transaction you can access a collection of settings, reports, views and further functions in the area of BCS. BCS forwards external messages to SAPconnect.

Features of SAPconnect SAPconnect is the central interface for external communication in SAP systems. SAPconnect supports the use of telecommunication services such as fax, text messages (pager / SMS), Internet e-mail, and X.400, as well as sending data to printers and between different SAP systems. SAPconnect allows you to connect external communication components to an ABAP-based SAP system. SAPconnect provides a direct connection to the Internet using the SMTP plug-in of the ICM. The SMTP plug-in for Internet e-mail is available as of AS ABAP 6.10.

594

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication with SAPconnect

Figure 269: SAPconnect: Communication Possibilities

As you can see from the figure above, there are different ways of producing the same result (such as sending mail over the Internet). It has been possible to use external communication systems for many years; however, the use of plug-in technology requires the Internet Communication Manager (which is available as of AS ABAP 6.10). Note that the use of RFC connections for SAPconnect is deprecated. In case RFC connections for SAPconnect are required (for example because an external communication systems does not offer HTTP or SMTP connectivity), you have to configure SAPconnect in transaction SCON (which offers a user interface similar to transaction SCOT in former releases of AS ABAP). Note: See SAP Note 1236270 about the support for the RFC interface of SAPconnect.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

595

Unit 12: SAPconnect and SMTP

TADM12_1

The following list clarifies the process of a generic communication step in SAPconnect. 1. 2. 3.

A message is created, for example as a WebFlow item, in the Business Workplace (transaction SBWP) or by an application. The message is assigned to a node based on the selected communication type and address area stored in the queue. The send process (report RSCONN01 – should run periodically in the background) starts, reads the message from the queue, and transfers it to the SMTP plug-in or an RFC destination.

Administration of SAPconnect To be able to send messages using a communication type, you must perform the following steps: 1. 2.

You require at least one configured (communication) node for the communication type if you want to use it to send documents. All external programs that may be required must be available and configured.

You have the following optoins to configure and monitor SAPconnect: • • •

Transaction SOADM (requires AS ABAP 7.02 or higher, for SMTP nodes only) Transaction SCOT (corresponds to transaction SOADM, path Administration → Settings → Outbound Messages → SMTP Node) Transaction SCON (support all communication types)

The first two options are the recommended ones. You should use transaction SCON only to for communication types different from SMTP.

596

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication with SAPconnect

Troubleshooting Various troubleshooting tools are available, some of which are mentioned as examples: •

• •

For outbound messages, you can use routing tests to check whether the error during the node determination was caused by the recipient address. This test checks whether routing for outgoing messages runs correctly in the communication environment. The test provides information on how the appropriate node is determined using the specified recipient address and whether fax and paging numbers are converted according to the rules for recipient number adjustment. A trace can be activated for incoming and/or outgoing messages. The messages that are sent can be evaluated according to their current status. For example, all documents with transmission errors can be displayed and resent. This report can be used to create overviews of the documents that have been sent in the current client. Overviews can be limited according to send times, communication methods, and send status. The entire send history of each document can also be called up. Overviews enable recipients to be notified and documents to be sent again.

Frequently Asked Questions How do I configure SAPconnect in the context of system monitoring so that an auto-reaction (sending mail) runs correctly? If an alert occurs in a system according to transaction RZ20, and a correctly set up auto-reaction method is assigned, the following happens: 1. 2.

The alert is marked red in transaction RZ20 shortly after it occurs. This red alert must be recognized by the AutoABAP SAPMSSY8, which runs every five minutes. The AutoABAP then starts the assigned auto-reaction method. Caution: Since SAPMSSY8 is executed in client 000, SAPconnect must also be correctly configured in client 000.

3.

After the auto-reaction method is active, there is a message that is ready to send in client 000. This message is sent the next time that report RSCONN01 runs. That is, the send process must be scheduled periodically. Caution: Documents are only sent correctly if the send user (which is declared in the auto-reaction method) is assigned a mail address in client 000.

For more information, see SAP Note 176492 – Automatic email when an alert occurs (RZ20). How can I connect Microsoft Exchange Server to my SAP systems?

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

597

Unit 12: SAPconnect and SMTP

TADM12_1

The SAP Exchange Connector connects the MS Exchange Server to the SAPconnect mail interface. However, the SAP Exchange Connector is no longer delivered by SAP. Instead, it has been replaced by the SMTP plug-in. See also SAP Note 122657 – SXC: Version overview and history.

598

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication with SAPconnect

Lesson Summary You should now be able to: • Outline the function of SAPconnect • Create a node for sending a remote mail to a different SAP system

Related Information •

•

• • • • • • • • •

2013/Q1

SAP NetWeaver 7.31 online documentation, path NetWeaver Library: Function-Oriented View → Application Server → Application Server ABAP → Other Services → Services for Application Developers → Generic Business Tools for Application Developers (BC-SRV-GBT) SAP NetWeaver 7.31 online documentation, path NetWeaver Library: Function-Oriented View → Application Server → Application Server ABAP → Other Services → Services for Business Users → SAPconnect (BC-SRV-COM) SAP Note 455127: E-mail (SMTP) in different SAP releases SAP Note 17194: Telefax in various SAP Releases SAP Note 455129: Paging/SMS in different SAP releases SAP Note 312690: SAPconnect: Collective note SAP Note 455140: Configuration of e-mail, fax, paging or SMS using SMTP SAP Note 455142: SAPconnect: Configuration paging/SMS via HTTP SAP Note 598718: SAPconnect - Performance SAP Note 1637415: S/MIME integration in SAPconnect SAP Note 1236270: Support for SAPconnect RFC interface

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

599

Unit 12: SAPconnect and SMTP

TADM12_1

Lesson: Communication Using SMTP Lesson Overview Connecting an SAP system to a mail server has become significantly easier due to the ICM process with SMTP plug-in available as of AS ABAP 6.10. This lesson provides you with an overview of configuring the SAP system for SMTP. We will discuss both sending and receiving e-mails.

Lesson Objectives After completing this lesson, you will be able to: • •

List the steps required to connect the AS ABAP to an SMTP mail server Configure the AS ABAP for the connection to an SMTP mail server

Business Example Your company uses ABAP-based SAP systems. As a member of the system administration team, it is your task to implement the exchange of e-mails between an AS ABAP and an SMTP-compatible mail server without external components.

Introduction to Communication Using SMTP As of AS ABAP 6.10, SMTP (Simple Mail Transfer Protocol) is supported directly by the ICM process. This means that it is possible to exchange e-mails between the SAP system and any SMTP-compatible mail server without using additional external components (such as connectors or gateways). You can use any product that meets the SMTP standard as a mail server. The following figure shows a simplified e-mail system landscape for a company. If an e-mail is sent to the address [email protected], it first reaches a Mail Transfer Agent (MTA). This is a program (such as sendmail) that is responsible for forwarding and delivering e-mails: When a mail is received from a Mail User Agent (MUA) (the actual e-mail program) or a different MTA, the MTA analyzes the mail and either sends it to the local user (that is, his or her MUA) or forwards it to a different MTA (if alias rules have been defined, for example). In the example shown here, the inbound e-mail is forwarded to the SAP CRM system with the local domain crm.sap.com.

600

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Figure 270: Task of a Mail Transfer Agent (MTA)

As of AS ABAP 6.20, faxes and text messages (pager / SMS) can be exchanged using SMTP. Faxes and text messages are packed into e-mails for this purpose. For receipt, the fax/text message server or provider sends e-mails to addresses with the SAP system domain (such as to [email protected]).

Restrictions of the AS ABAP with Regard to Receiving SMTP Mails As of AS ABAP 7.02, in the outbound direction the SAP system can transfer mails that were created in one client to different mail servers. You can specify the host address and port number of this mail servers in the definition of the SAPconnect SMTP node. The AS ABAP can receive e-mails via SMTP and redistribute these e-mails to Business Workplace (previously: SAP Office) users. In the inbound direction, the SAP system can receive mails from any number of mail servers. Each client can be reached by a separate virtual mail server (host name, port number) that is configured in transaction SICF. The best approach to addressing the SAP system and its clients is to use a separate subdomain for each client (such as domain100.sap.com). These subdomains are assigned to host names and port numbers using routing rules on the mail servers. The following restriction applies: SAPconnect cannot be an MTA itself, that is, it cannot forward the mails to other mail servers.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

601

Unit 12: SAPconnect and SMTP

TADM12_1

Configuring the AS ABAP for SMTP If you want to use the SMTP function, you have to set the following profile parameters for the AS ABAP. Note: The following restriction applies: The SAPconnect send job can only be scheduled for application servers on which SMTP is activated. You should therefore activate SMTP on all application servers of the SAP system. •

rdisp/start_icman = true This parameter starts the ICM process automatically during the system startup.

• •

exe/icman = icm/server_port_ = PROT=SMTP,PORT= This parameter opens a TCP/IP port for receiving mails using the SMTP plug-in. describes the port number. If no mails are to be received in this SAP system, set to zero. Hint: The parameter is/SMTP/virt_host_ defines a virtual mail host for receiving mails. If all inbound mails (including status notifications) are to be received and processed in a single client of the SAP system, this parameter is not required and is/SMTP/virt_host_0 = *:*; is taken as the default. If multiple clients are intended as receivers, you must create a virtual host for each client.

To avoid performance bottlenecks due to high numbers of SMTP requests (or, optionally, HTTP/S), you can use parameters to restrict the context usage in the backend SAP system for a protocol. You specify the percentage of all available contexts that can be used for the relevant protocol. In the SAP system, the maximum number of contexts in the system is limited by the profile parameter value of rdisp/tm_max_no (this parameter restricts the maximum number of users per instance). If the following quotas are exceeded, the requests are rejected in the ICM. • •

icm/HTTP(S)/context_quota icm/SMTP/context_quota

For example, with the setting icm/SMTP/context_quota = 20, you specify that only 20 percent of the available contexts can be used for SMTP (mail functions). This means that you have more capacity for HTTP(S) requests if there is a high workload.

602

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Sending E-Mails from AS ABAP E-mails are created either automatically using an application or manually in the SAP mail client (Business Workplace, transaction SBWP), and are sent to a mail server by SMTP. These e-mails can now also be displayed with a suitable mail client for this mail server, as shown in the following figure.

Figure 271: Outbound Mails: Process

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

603

Unit 12: SAPconnect and SMTP

TADM12_1

Note: Short explanations of the abbreviations used in the figure: •

•

•

•

POP is the abbreviation for Post Office Protocol. POP was defined in 1984 in connection with TCP/IP and allows the receipt of e-mails even on systems that cannot guarantee permanent connection to the mail server. POP3 is, therefore, together with SMTP (for sending messages), the standard protocol for most mail clients in the Internet. The POP3 protocol can delete messages on the server or leave them there, and can delete messages directly without first transferring them from the server. If more is required, such as hierarchical mailboxes, or filters, you should use the functions of the client; the protocol does not provide anything of this sort - you may have to use IMAP. IMAP: is the abbreviation for Internet Message Access Protocol. This is an e-mail protocol that allows the client to process mails on the server. You can also create folders on the mail server (remote mailboxes) to sort mails. IMAP was developed to transfer messages only when required: The user can choose (unlike with POP3) which data he or she actually wants to transfer to his or her own computer. SMTP: This is the abbreviation for Simple Mail Transfer Protocol. SMTP is the standard for exchanging e-mails between servers in the network. Mail clients use SMTP to send e-mails to a server, but not to receive e-mails. MIME: This is the abbreviation for Multipurpose Internet Mail Extensions. It consists of Internet extensions (coding procedures) for including binary data in Internet mails. In addition, MIME supports multipart mails to allow different data types in a mail or binary attachments, and mails in HTML format.

Follow the procedure below to configure a send process for SMTP: 1.

2.

As described in the section Restrictions of the AS ABAP with Regard to Receiving SMTP Mails, the key profile parameters for SMTP must be maintained. Maintain the user addresses, as every user that wants to send e-mails requires an Internet e-mail address. This is used as the sender address. You can use transaction SU01 to enter the Internet address under E-Mail on the Address tab page. For security reasons, if a user is maintaining his or her own data (transaction SU3), he or she cannot maintain the entries for the communication types E-mail (INT or SMTP) and Remote Mail (RML). Note: You can use report RSADRCK7 to create e-mail addresses of type @ automatically for all (SU01) users in your client. This report is described in more detail in SAP Note 104263.

604

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

3.

In transaction SOADM, path Settings → Outbound Messages → Settings → Outbound Settings → Default Domain, define the default domain of the current SAP system client. You need to do this for the following reasons: • • •

The SMTP plug-in logs onto the mail server with the domain as an ID. The message ID of the outbound e-mails is compiled using this domain. If an SAP user sends an e-mail without an Internet e-mail address, a sender address consisting of the SAP user name and this domain is generated. Note: You must make SAPconnect settings in transactionSOADM for every client from which you send messages.

4.

The following steps are required to configure an SMTP node to send a Internet mail: •

5.

(If not already existing) Create an SMTP note in transaction SOADM (with or without wizard). • In the Mail Host and Mail Port fields, specify the mail server to which the outbound mails are to be transferred. It is also useful to schedule a send job, as e-mails sent from an SAP application are initially placed in a wait queue. A background job that runs periodically, the SAPconnect send job, collects e-mails from the wait queue and sends them to the mail server. In transaction SOADM, at path Settings → Outbound Messages → Send Jobs, create a background job, for example with the variant SAP&CONNECTINT, and schedule it periodically (with a period value of, for example, 10 minutes). Hint: Make sure that you schedule the job on an instance in which an ICM process is also configured and active.

You can also configure the node for sending faxes or text messages in the same way. The figure below shows the wizard-based configuration of an SMTP node in transaction SOADM.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

605

Unit 12: SAPconnect and SMTP

TADM12_1

Figure 272: Configuring an SMTP Node

Receiving E-Mails in an SAP System When you send an e-mail from a mail client to a user in an SAP system, the e-mail is first forwarded to a mail server and then forwarded to the SAP system by the MTA. The e-mails are sent to the mail client in the SAP system (Business Workplace) on a client-dependent basis using SAPconnect. This is illustrated by the following figure.

606

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Figure 273: Incoming Mails: Process

Follow the procedure below to configure the process for receiving SMTP mails: 1. 2.

3.

4.

5.

2013/Q1

As described in the section Configuring the AS ABAP for SMTP, some key profile parameters for SMTP must be maintained. In addition, a user is required for processing inbound mails in each client. Use transaction SU01 to create a system user with the authorization profile S_A.SCON (which is shipped by SAP). You need to maintain an Internet mail address for every user that is to receive e-mails in an SAP system. This is also used as the sender address. Enter the Internet mail address in transaction SU01 on the Address tab page under E-Mail. For security reasons, if a user is maintaining his or her own data (transaction SU3), he or she cannot maintain the entries for the communication types E-mail (INT or SMTP) and Remote Mail (RML). In transaction SOADM, define the domain of the SAP system client under Settings → Outbound Messages → Settings → Outbound Settings → Default Domain. For every client of an SAP system in which inbound mails (or status notifications for sent mails) are to be received and possibly processed, you must create an SMTP server for which an assignment to a virtual mail host and logon data are stored. In transaction SICF, SAP already ships an SMTP server note for every SAP system. Use this for the first client that you want to be able to receive mails, and create a new SMTP server for each additional client. If you are working with multiple clients, you must create a virtual host for each client in which messages are received using the SMTP plug-in. Make the following settings in transaction SICF by double-clicking the SAPconnect menu entry (see also SAP Note 546147):

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

607

Unit 12: SAPconnect and SMTP

•

TADM12_1

On the Host Data tab page, maintain the parameter is/SMTP/virt_host_= :,,...; This parameter defines a virtual mail host for receiving mails. If all inbound mails (including status notifications) are to be received and processed by a single client in the SAP system, this parameter is not required. In this case, is/SMTP/virt_host_0= :; is used as the default. If multiple clients are intended as receivers, you must create a virtual host for each client. and describe the name of the host and the port to which inbound mails are addressed.

•

•

On the Logon Data tab page, enter the client to which the mails received by the virtual mail host are to be forwarded and maintain the logon data of the system user that was created in this client for the inbound mails. On the Handler List tab page, add (if it does not already exist) CL_SMTP_EXT_SAPCONNECT at position 1. Note: As of AS ABAP 6.20, every SMTP server must be activated (in transaction SICF under Service/Virtual Host → Activate or by clicking the right mouse button and using the context menu) after it has been created or changed.

The steps required to configure the mail connection in the SAP system are summarized again in the figure below.

Figure 274: Configuring the Mail Connection via SMTP

608

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Administration of SAPconnect SAPconnect has a uniform administration interface which can help set up the external communication of an SAP system using SMTP and monitor its running send operation. You can navigate from here to all settings relevant for SAPconnect. In addition to this, you are offered some function that help you to maintain and manage your SAPconnect environment. Use transaction SOADM to configure SAPconnect for communication type Internet e-mail via SMTP. You can use various views of the communication infrastructure in transaction SOADM. You usually start with the view Administration → System Status.

Figure 275: Transaction SOADM: Maintenance of SMTP Node(s)

Note: You can easily schedule the send process periodically in transaction SOADM, by choosing Settings → Outbound Messages → Send Jobs. Caution: SAPconnect must be set up client dependent. Note: External communication systems log onto the SAP system as a system user. The authorizations for this user are contained in the profile S_A.SCON. The SAPconnect administrator requires the authorizations for the system user and the authorizations for table maintenance, which are checked using the authorization object S_TABU_DIS. These authorizations are contained in the roles SAP_BC_SRV_COM_ADMIN and SAP_BC_SRV_GBT_ADMIN.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

609

Unit 12: SAPconnect and SMTP

610

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM12_1

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Exercise 25: Sending and Receiving E-Mails by SMTP with AS ABAP Exercise Objectives After completing this exercise, you will be able to: • Send e-mails from AS ABAP using SMTP • Receive e-mails in AS ABAP using SMTP

Business Example As a member of the system administration team, you want to implement the exchange of e-mails between an ABAP-based SAP system and an SMTP-compatible mail server without external components.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

611

Unit 12: SAPconnect and SMTP

TADM12_1

Task 1: Check the Training Infrastructure

Figure 276: Overall Scenario of the Training Landscape for the Outbound Mail

Access to your external mail inbox. Note: For the purposes of this training course, we will use the JAMES mail server that is running on your training server twdfSSSS. Access is via a prepared Web Dynpro ABAP application ZMAIL. 1.

In your ECC system, call the Web Dynpro ABAP application to access “your” mail inbox -##@training.sap.com on the JAMES mail server. In standard course setups, the -## users have a prepared menu entry to launch transaction ZMAIL in their role-based SAP Easy Access user menu (in the folder that corresponds to this unit of the course). Double-click this menu item. In case this entry is missing, enter the following URL manually: http://twdfSSSS.wdf.sap.corp:80$$/sap/bc/webdynpro/sap/zmail. Note: Note that this URL is case-sensitive. When the course materials are published, a hyphen “-” may be displayed at the end of the line. This hyphen is not part of the URL. If you see a message regarding an inactive service, start transaction SICF and activate the ICF service /sap/bc/webdynpro/sap/zmail. Continued on next page

612

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Result You can see the incoming mails for your e-mail recipient on the JAMES mail server. In practice, SAP customers will run a different SMTP mail server (in training: JAMES) and a different mail client (in training: Web Dynpro ABAP application ZMAIL).

Task 2: Check the SMTP Configuration of Your SAP System Check whether your SAP system has been configured for SMTP. If this is not the case, configure your SAP system accordingly. 1.

For each instance of your SAP ECC system, determine the port at which requests in the SMTP protocol are processed.

2.

If your SAP ECC system has not yet been configured for SMTP, use transaction RZ10 to add the parameter icm/server_port_ for your default profile and assign it the value PROT=SMTP,PORT=250$$. Save and activate the profile and then restart all the ICM processes of your system in transaction SMICM. Then repeat the first step of the task.

Task 3: Setting Up the Sending of E-Mails in AS ABAP Generate Internet addresses, set the default domain and receipt confirmation, and configure the SMTP node. 1.

Assign all users in client 100 of your SAP ECC system the Internet address @domain##.sap.com, where ## is your (two-digit) group number. Afterwards, check the changes performed for your user -##.

2.

In client 100 of your SAP ECC system, enter domain##.sap.com as the default domain.

3.

Configure SAPconnect so that no confirmation of receipt is expected for Internet mails. Hint: This setting means that sent messages of the type Internet mail are immediately assigned the status “Completed” (otherwise, they remain in the status “In transit” until a confirmation of receipt is received). In the SAP system, the sending application determines whether a confirmation of receipt is actually requested.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

613

Unit 12: SAPconnect and SMTP

4.

TADM12_1

Using the wizard, create a new SMTP node in your SAP system so that e-mails addressed to recipients in the mail domain training.sap.com can be sent to the JAMES mail server. Do achieve this, use the following settings: Node Name

SMTP##

Description

any

Mail Host

twdfSSSS.wdf.sap.corp

Mail Port

25

Address Type

SMTP / Internet

Address Area

*@training.sap.com

Output formats

keep default values

Maximum waiting time...

30 minutes

Hint: If the external mail server also operates as a Mail Transfer Agent (MTA) and you have specified only one SMTP node, you could also use enter * as address area. However, in the training landscape, the mail server does not forward any e-mails, but rather processes only the specified domain.

Result Your SMTP node SMTP## is now ready for use and is responsible for all e-mails sent to the specified address range. It is this easy to connect to an SMTP-compatible mail server.

Task 4: Sending E-Mails from AS ABAP Create an e-mail and start the send process. 1.

In your SAP ECC system, create an e-mail to the (external) recipient -##@training.sap.com.

2.

In the system status of SAPconnect, check if there is at least one waiting message of type Internet.

3.

Start the SAPconnect send process manually.

4.

Check the external mail server to see whether your mail has arrived.

5.

Schedule the send process for Internet mails periodically (every five minutes).

6.

Optional: Send a list output (such as report SHOWCOLO) to recipient -##@training.sap.com and observe how the output is sent during the next send process. Continued on next page

614

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Result Congratulations on successfully connecting your SAP system to a mail server.

Task 5: Receiving E-Mails in AS ABAP Setting up the SAP system for receiving e-mails.

Figure 277: Overall Scenario of the Training Landscape for Inbound Mail

1.

In your SAP ECC system, create a user MAILDISP##, to distribute e-mails in the current client. This user should be of the type System. The user should have the initial password chosen by you and it should have the authorization profile S_A.SCON provided by SAP.

2.

Enter the user that you have just created in the virtual host for SAPconnect (transaction SICF). Remember to activate the virtual host after changing it.

3.

Using the Web Dynpro ABAP application ZMAIL, send an e-mail to “your” AS ABAP system, either as a “Reply” to an e-mail received previously or as a “New” message. Fill in the mail popup as follows:

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

615

Unit 12: SAPconnect and SMTP

616

TADM12_1

To

-##@domain##.sap.com

Subject

arbitrary

Mail server

twdfSSSS.wdf.sap.corp: (the ICM SMTP Port should be 250$$ where $$ is an instance of your ECC system)

Message

arbitrary

4.

Check the inbound send requests of SAPconnect.

5.

Check your inbox in the SAP system.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Solution 25: Sending and Receiving E-Mails by SMTP with AS ABAP Task 1: Check the Training Infrastructure

Figure 278: Overall Scenario of the Training Landscape for the Outbound Mail

Access to your external mail inbox. Note: For the purposes of this training course, we will use the JAMES mail server that is running on your training server twdfSSSS. Access is via a prepared Web Dynpro ABAP application ZMAIL. 1.

In your ECC system, call the Web Dynpro ABAP application to access “your” mail inbox -##@training.sap.com on the JAMES mail server. In standard course setups, the -## users have a prepared menu entry to launch transaction ZMAIL in their role-based SAP Easy Access user menu (in the folder that corresponds to this unit of the course). Double-click this menu item.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

617

Unit 12: SAPconnect and SMTP

TADM12_1

In case this entry is missing, enter the following URL manually: http://twdfSSSS.wdf.sap.corp:80$$/sap/bc/webdynpro/sap/zmail. Note: Note that this URL is case-sensitive. When the course materials are published, a hyphen “-” may be displayed at the end of the line. This hyphen is not part of the URL. If you see a message regarding an inactive service, start transaction SICF and activate the ICF service /sap/bc/webdynpro/sap/zmail. See the task description. ZMAIL is a Web Dynpro ABAP application that has been created especially for this course.

a)

Result You can see the incoming mails for your e-mail recipient on the JAMES mail server. In practice, SAP customers will run a different SMTP mail server (in training: JAMES) and a different mail client (in training: Web Dynpro ABAP application ZMAIL).

Continued on next page

618

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Task 2: Check the SMTP Configuration of Your SAP System Check whether your SAP system has been configured for SMTP. If this is not the case, configure your SAP system accordingly. 1.

For each instance of your SAP ECC system, determine the port at which requests in the SMTP protocol are processed. a)

Logon to client 100 of your ECC system with your user -##.

b)

There are a number of ways to determine the port responsible for SMTP. The simplest method is to call transaction SMICM and choose Services. You can see the number under which the SMTP service is running in the system in the first column (it is represented here by xx). The associated profile parameter is called icm/server_port_. You can also find the value of this parameter, for example: • • •

c)

2.

In transaction SMICM, by choosing Goto → Parameters → Display on the start screen By calling report RSPFPAR In Profile Maintenance (transaction RZ10)

Note that the port determined in this way (such as 25011) applies only for the application server to which you are currently logged on. Log on to the other instance of your SAP ECC system (for example using transaction SM51: select an application server and choose Goto → Monitors → ICM Monitor), to determine the port that is set there.

If your SAP ECC system has not yet been configured for SMTP, use transaction RZ10 to add the parameter icm/server_port_ for your default profile and assign it the value

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

619

Unit 12: SAPconnect and SMTP

TADM12_1

PROT=SMTP,PORT=250$$. Save and activate the profile and then restart all the ICM processes of your system in transaction SMICM. Then repeat the first step of the task. a)

If, during the previous step of this exercise, you discovered in transaction SMICM that SMTP is not configured, start transaction RZ10 and open the Extended maintenance of the DEFAULT profile in change mode. Hint: If the profile is not available in the F4 help, you have to load the profiles by choosing Utilities → Import profiles → Of active servers.

b)

Choose Create Parameter. Enter icm/server_port_ as the parameter name and PROT=SMTP,PORT=250$$ as the parameter value.

c)

Save your changes by choosing Copy → Back → Copy → Back → Save. If a dialog box appears with information about an incorrect parameter value, choose Yes and ensure that the new parameter icm/server_port_ is displayed correctly (ignore warnings on other parameters). If you are prompted to do so, activate the profile at operating system level. Confirm the following dialog boxes by choosing Continue.

d)

Instead of restarting the entire SAP system now, you can just start the ICM processes. To do so, call transaction SMICM and choose Administration → ICM → Restart → Yes and then Administration → ICM → Exit Hard → Global. Confirm the query by choosing Yes. Then choose Services again and check whether your changes have been made.

Continued on next page

620

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Task 3: Setting Up the Sending of E-Mails in AS ABAP Generate Internet addresses, set the default domain and receipt confirmation, and configure the SMTP node. 1.

2.

3.

Assign all users in client 100 of your SAP ECC system the Internet address @domain##.sap.com, where ## is your (two-digit) group number. Afterwards, check the changes performed for your user -##. a)

Start the report RSADRCK7 (using transaction SA38, for example).

b)

In the Domain field, enter domain##.sap.com (where ## is your group number). Deselect the Keep existing addresses and Test mode checkboxes and select the Use user IDs checkbox.

c)

Press Execute and note the log which is displayed.

d)

In transaction SU01, enter the user -## and choose Display. On the Address tab, the E-Mail field should contain the value -##@domain##.sap.com (where ## is your group number).

In client 100 of your SAP ECC system, enter domain##.sap.com as the default domain. a)

Start transaction SOADM.

b)

Navigate to Settings → Outbound Messages → Settings.

c)

On the Outbound Messages tab, for Default Domain enter the value domain##.sap.com (where ## is your group number).

d)

Choose Save.

Configure SAPconnect so that no confirmation of receipt is expected for Internet mails. Hint: This setting means that sent messages of the type Internet mail are immediately assigned the status “Completed” (otherwise, they remain in the status “In transit” until a confirmation of receipt is received). In the SAP system, the sending application determines whether a confirmation of receipt is actually requested. a)

In transaction SOADM, navigate to Settings → Outbound Messages → Settings.

b)

On the Status Requests tab, check the field Do not request read confirmatns generally.

c)

Choose Save. Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

621

Unit 12: SAPconnect and SMTP

4.

TADM12_1

Using the wizard, create a new SMTP node in your SAP system so that e-mails addressed to recipients in the mail domain training.sap.com can be sent to the JAMES mail server. Do achieve this, use the following settings: Node Name

SMTP##

Description

any

Mail Host

twdfSSSS.wdf.sap.corp

Mail Port

25

Address Type

SMTP / Internet

Continued on next page

622

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Address Area

*@training.sap.com

Output formats

keep default values

Maximum waiting time...

30 minutes

Hint: If the external mail server also operates as a Mail Transfer Agent (MTA) and you have specified only one SMTP node, you could also use enter * as address area. However, in the training landscape, the mail server does not forward any e-mails, but rather processes only the specified domain. a)

In transaction SOADM, navigate to Settings → Outbound Messages → SMTP Node (alternatively, start transaction SCOT).

b)

If there is already an SMTP node, delete it (in this training, we want to start from a defined state).

c)

Press the Create Node Using Wizard button.

d)

As Node, enter SMTP##. Provide a short Description and press Continue.

e)

As Mail Host, enter twdfSSSS.wdf.sap.corp. As Mail Port, enter 25 and press Continue.

f)

As Address Type, select SMTP / Internet and press Continue.

g)

As Address Area, enter *@training.sap.com and press Continue.

h)

Keep the default settings for the conversion of SAP internal formats and press Continue.

i)

When you are asked if you want to set further address types, select N (for “No”) and press Continue.

j)

As Maximum waiting time for failed send attempts, enter 30 minutes. Ensure that Node is ready for use is checked and press Continue.

Result Your SMTP node SMTP## is now ready for use and is responsible for all e-mails sent to the specified address range. It is this easy to connect to an SMTP-compatible mail server.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

623

Unit 12: SAPconnect and SMTP

TADM12_1

Task 4: Sending E-Mails from AS ABAP Create an e-mail and start the send process. 1.

In your SAP ECC system, create an e-mail to the (external) recipient -##@training.sap.com. a)

Call the SAP Business Workplace (transaction SBWP) and choose New message.

b)

In the new window, create a message (using any title and content).

c)

As Recipient, type -##@training.sap.com. When you press Enter to transfer the address, the SAP system identifies from the structure of the address that it is an Internet address. Messages can be sent to different types of address (see the F4 help for the Recip. Type field).

d) 2.

3.

Finally, choose Send.

In the system status of SAPconnect, check if there is at least one waiting message of type Internet. a)

Start transaction SOADM.

b)

Navigate to Administration → System Status. For the address type Internet, you should see at least one message in status Waiting.

Start the SAPconnect send process manually. a)

Start transaction SOADM.

b)

Navigate to Administration → Outbound Send Requests (alternatively, start transaction SCST).

c)

The waiting message should show up here. Note the select options.

d)

Press Start Send Process for Selection.

e)

View the status once the send process is completed In case of an error, you may • •

4.

click on the Msg link to access details of the error message. click on the Trace button to access the workflow trace.

Check the external mail server to see whether your mail has arrived. a)

If the window is still open from the first task of this exercise, simply click on the Last refreshed at [...] link. If it is not, repeat the first task of this ecercise.

Continued on next page

624

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

5.

6.

Schedule the send process for Internet mails periodically (every five minutes). a)

Start transaction SOADM.

b)

Navigate to Settings → Outbound Messages → Send Jobs.

c)

Press Schedule Job for INT.

d)

A popup “Send Job: Select Variant” is displayed. You may keep or change the proposed values, and then press Continue.

e)

On the “Define Background Job” screen, press Save.

f)

Back in transaction SOADM, you can check (as well as change and delete) the send job.

Optional: Send a list output (such as report SHOWCOLO) to recipient -##@training.sap.com and observe how the output is sent during the next send process. a)

Call any list display in the SAP system (proposal: use transaction SA38 to execute report SHOWCOLO). Choose System → List → Send and enter ##@training.sap.com as the Recipient. The system proposes the report title as the default Title of the message. If desired, enter some text as the Document contents. Choose Send to transfer your message to SAPconnect.

b)

The message is processed by the send process during the following five minutes. If the e-mail finally is displayed in the browser, the attachment is displayed in the bottom area of the browser screen. Note: By default, ABAP lists are converted to HTML format – which is an option in the Output Formats for SAP Documents. In transaction SOADM, navigate to Settings → Outbound Messages → SMTP Node and double-click on your SMTP## node. Press Set for address type Internet and note the alternative options for Output Formats for SAP Documents. Feel free to change the format for ABAP lists from HTM to PDF.

Result Congratulations on successfully connecting your SAP system to a mail server.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

625

Unit 12: SAPconnect and SMTP

TADM12_1

Task 5: Receiving E-Mails in AS ABAP Setting up the SAP system for receiving e-mails.

Figure 279: Overall Scenario of the Training Landscape for Inbound Mail

1.

In your SAP ECC system, create a user MAILDISP##, to distribute e-mails in the current client. This user should be of the type System. The user should have the initial password chosen by you and it should have the authorization profile S_A.SCON provided by SAP. a)

Start transaction SU01.

b)

For User, enter MAILDISP## and press Create.

c)

On the Address tab, enter at lease a Last name.

d)

On the Logon Data tab, choose System as User Type. Also enter a password (twice). Hint: Users of the type System are intended for dialog-free communication between different systems and are excluded from the checks for expired passwords. For more information, see SAP Note 622464: Change: Password change req. entry for “SYSTEM” user type.

e)

On the Profiles tab, select the authorization profile S_A.SCON.

f)

Press Save.

Continued on next page

626

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

2.

Enter the user that you have just created in the virtual host for SAPconnect (transaction SICF). Remember to activate the virtual host after changing it. a)

Start transaction SICF.

b)

On the initial screen of transaction SICF, select the hierarchy type SERVICE and choose Execute.

c)

On the following screen, double-click the SAPconnect entry.

d)

On the Logon Data tab, switch to change mode.

e)

Enter the data for user MAILDISP## (client, user, password, and language). Leave all other fields unchanged and save your changes. Hint: If you receive an error message when you select the language for the user because a code page is not supported, you have to activate your language using report RSCPINST. To do so, add your language on the left-hand side of the initial screen of this report and then choose Activate.

f)

Click the SAPconnect entry (still in transaction SICF) with the right mouse button, choose Activate SMTP Host and confirm the subsequent dialog box by choosing Yes here (it does not matter which Yes ;-)). Hint: An SMTP server is required for each client of an SAP system in which e-mails can be received. You have now created the connection to a virtual mail host. If e-mails were also to be delivered to other clients in your SAP system, you would have to create additional virtual mail hosts for these clients in transaction SICF.

3.

Using the Web Dynpro ABAP application ZMAIL, send an e-mail to “your” AS ABAP system, either as a “Reply” to an e-mail received previously or as a “New” message. Fill in the mail popup as follows:

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

627

Unit 12: SAPconnect and SMTP

To

-##@domain##.sap.com

Subject

arbitrary

Mail server

twdfSSSS.wdf.sap.corp: (the ICM SMTP Port should be 250$$ where $$ is an instance of your ECC system)

Message

arbitrary

a)

Call the Web Dynpro ABAP application ZMAIL, as described in the first task of this exercise.

b)

Choose one of the following two functions: • •

4.

TADM12_1

Send a New mail message, or Reply, after selecting a message received previously

c)

Fill in the fields as mentioned in the exercise.

d)

Choose OK to send the message.

Check the inbound send requests of SAPconnect. a)

Start transaction SOADM.

b)

Navigate to Administration → Inbound Send Requests. You should see an inbound send request. For each of them, you can launch further features such as display details, display request or display trace.

5.

Check your inbox in the SAP system. a)

As user -## in your SAP ECC system, call the SAP Business Workplace (transaction SBWP). You should find your e-mail in the Inbox area.

Result You are now able to connect SMTP for an SAP system in both directions. We wish you every success in implementing this in your company.

628

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Lesson: Communication Using SMTP

Lesson Summary You should now be able to: • List the steps required to connect the AS ABAP to an SMTP mail server • Configure the AS ABAP for the connection to an SMTP mail server

Related Information •

• • • • • • • •

2013/Q1

SAP NetWeaver 7.31 online documentation, path NetWeaver Library: Function-Oriented View → Application Server → Application Server ABAP → Other Services → Services for Business Users → SAPconnect (BC-SRV-COM) SAP Note 455140: Configuration of e-mail, fax, paging or SMS using SMTP SAP Note 455127: E-mail (SMTP) in different SAP releases SAP Note 312690: SAPconnect: Collective note SAP Note 546147: SMTP plug-in: MS Exchange sends only to port 25 SAP Note 104263: Generating Internet addresses for users SAP Note 690020: SAPconnect send process hangs with large mails SAP Note 607108: Problem analysis when you send or receive e-mails SAP Notes 633265, 664833, 694151 and 883840: SMTP PlugIn: Multi-codepage ability

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

629

Unit Summary

TADM12_1

Unit Summary You should now be able to: • Outline the function of SAPconnect • Create a node for sending a remote mail to a different SAP system • List the steps required to connect the AS ABAP to an SMTP mail server • Configure the AS ABAP for the connection to an SMTP mail server

630

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Test Your Knowledge

Test Your Knowledge 1.

Which of the following statements regarding SAPconnect are correct? Choose the correct answer(s).

2.

□

A

□

B

□

C

□ □

D E

As of AS ABAP 6.10, a Microsoft Exchange Infrastructure must be set up outside the SAP system to be able to send mail from SAP systems. It is not possible to connect the UNIX-based sendmail to SAP systems. SAPconnect allows you to send mail both by RFC and the SMTP plug-in of the SAP AS ABAP. SAPconnect is configured cross-client. A send process automatically runs periodically in every SAP system after the system installation.

The connection of a mail server to an ABAP-based SAP system to send e-mails using SMTP from the SAP system runs through an SAPconnect node. Determine whether this statement is true or false.

□ □

2013/Q1

True False

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

631

Test Your Knowledge

TADM12_1

Answers 1.

Which of the following statements regarding SAPconnect are correct? Answer: C SAPconnect contains two methods for sending mails: using an RFC connection or directly using a plug-in of the AS ABAP. The other statements are incorrect.

2.

The connection of a mail server to an ABAP-based SAP system to send e-mails using SMTP from the SAP system runs through an SAPconnect node. Answer: True To configure a send process for SMTP in the SAP system, you must, among other things, also have configured and activated an SMTP node in transaction SOADM/SCOT (SAPconnect).

632

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Course Summary

Course Summary You should now be able to: •

2013/Q1

process basic tasks within the technology environment of SAP systems

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

633

Course Summary

634

TADM12_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

Glossary central system A central SAP system consists of a single central instance that provides all required SAP services and the associated database. In the case of a central system, these are usually on the same host. Communication Type Type of communication supported by SAPconnect, such as sending data by e-mail or fax, transferring data to archiving systems or communication services, and so on, that allow data to be sent to pagers, or as an SMS. Communication types are configured in SAPconnect. dispatcher (ABAP) Central process of an AS ABAP instance. It is responsible, amongst other things, for starting work processes and distributing the transaction load across work processes. dispatcher (Java) Central process of a Java instance. It is, amongst other things, responsible for distributing the transaction load across server processes. instance Administrative unit in which components of an SAP system that provide one or more services are grouped together. These services are started and stopped at the same time. Instance Number Two-digit number that identifies the instance. Each instance of the SAP system requires its own instance number. Two instances with the same number can not run on one machine, because of the associated ports. Internet Communication Manager The Internet Communication Manager (ICM) is the component in the SAP architecture that allows the SAP system to communicate directly via http and related protocolls. It is started by the dispatcher of an instance. language import The import of language-dependent texts of an additional language into an SAP system. maintenance certificate A maintenance certificate enables the SAP software logistics tools (for example, SPAM, SAINT, and JSPM) to identify the system to be maintained and to determine the extent of maintenance required. It is also used to ensure that only customers with a valid maintenance contract can perform the relevant maintenance transactions.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

635

Glossary

TADM12_1

maintenance transaction To import Support Packages, among other things, SAP recommends that you create a maintenance transaction with the Maintenance Optimizer. This maintenance transaction is used to calculate a consistent combination of Support Packages for a specific system or a combination of systems in the landscape and to approve this combination for download. Modification Adjustment If SAP objects were modified by the customer, and these objects are imported with a SAP Support Package, SAP enhancement package, or a release upgrade, the objects have to be adjusted when they are imported. If these objects are not adjusted, the customer's modifications that have been made to the SAP objects are reset to the SAP delivery status. MTA Mail Transfer Agent; The program that is responsible for forwarding and delivering e-mails: When a mail is received from a Mail User Agent (MUA) (the actual e-mail program) or a different MTA, the MTA analyzes the mail and either sends it to the local user (that is, his or her MUA) or forwards it to a different MTA. The MTA that is still used most frequently in the Internet is sendmail. output request An output request contains the data from a spool request in a format for a particular printer model. PAL Printing Assistant for Landscapes (PAL): PAL allows output devices to be maintained in a (central) system, and then distributed across additional (target) systems. patch To be able to correct smaller problems in the SAP system, individual corrections, known as single patches are available as SAP Notes. SAP enhancement package An SAP system consists of various software components with a particular release level. Importing parts of an SAP enhancement package updates some of these software components to a higher release level. SAP Note SAP Notes enable you to make adjustments on the basis of changes in legal requirements, correct errors in the standard SAP software and enhance existing functions, or make new functions available. An SAP Note mainly affects changes to an individual object. Compare also “SAP Support Packages”.

636

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Glossary

SAP Support Package A SAP Support Package enables you to make adjustments on the basis of changes in legal requirements, correct errors in the standard SAP software and enhance existing functions, or make new functions available. A SAP Support Package contains a number of changed objects. Compare also “SAP Note” and “SAP Support Package Stack”. SAP Support Package Stack An SAP Support Package Stack is a recommended combination of SAP Support Packages and other patches for an SAP system. Compare also “SAP Support Package”. server process Process that uses its services to work through requests to the AS Java. In contrast to ABAP work processes, Java server processes are multi-threaded, and can therefore process a number of requests at the same time. SMTP Simple Mail Transfer Protocol (SMTP) is an Internet standard for a host-to-host mail transport protocol. SMTP uses TCP and standard port 25. SPAM/SAINT update 100% patch for the Support Package Manager (transaction SPAM) and the Add-On Installation Tool (transaction SAINT). The SPAM/SAINT update is used to update these two tools. spool request A spool request contains information about data to be output, its formatting, and the printer model used. Support Package Collection of corrections for software errors in the SAP system. Support Packages are summarized in periodic intervals and made available by SAP. Support Package Manager (SPAM) Tool (transaction SPAM) for importing SAP Support Packages. With the Support Package Manager, the tool itself is patched too. See also “SPAM/SAINT update”. Support Package Stack Collection of Support Packages. SAP does not advise you to import Support Packages individually; instead, you should always import the entire Support Package Stack for a System. TemSe Abbreviation for Temporary Sequential (database); file that temporarily includes information such as spool request data and background processing job logs. variant Preassignment of the input fields of a selection screen for reports, for example to enable the execution of the report in the background.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

637

Glossary

TADM12_1

work process Process that handles requests in an SAP system. The following work process types exist: Dialog (for executing dialog programs), update (for changing database entries), background (for executing background jobs), spool (for print formatting) and enqueue (for executing lock operations).

638

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

Index A

H

access method, 431 Activation of business functions, 209 AS ABAP, 13 AS ABAP ports, 109 AS Java, 13

Hardware sizing, 104 Help type, 177

B background users, 545 Backup, 160

C central instance, 13 Central Service instance, 17 central system, 13 Central system, 13 Change and Transport System (CTS), 194 Client copy, 201 communication types, 609 Configuration Wizard, 221 Configure local SLD, 80 Create own user, 192

D device type, 437 Disk layout, 111 Dispatcher ABAP, 13 Java, 15 Distributed system, 13

E external command, 546 external program, 546

F front-end printing, 433 function module BP_EVENT_RAISE, 533

2013/Q1

I IMAP, 604 Installation check, 202 Installation DVDs, 36 Installation guide, 36 Installation guides, 38 Installation user, 56 instance, 13 Instance Number, 14

J Java Support Package Manager, 404 JAVA_HOME environment variable, 41 JCE policy files, 42 JDK installation, 39 job class, 505 job server group, 544 Job Wizard, 507 JRE Installation, 39 JSPM, 404

K Kernel, 10 Kernel patch, 306

L language import, 205 Language installation, 203 local printing, 431

M maintenance certificate, 343 Maintenance Optimizer, 306, 308, 331 maintenance transaction, 335

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

639

Index

TADM12_1

MDMP, 19 Message Transfer Agent (MTA), 600 MIME, 604 Multi Display Multi Processing (MDMP), 19 multilingual capability, 203

N Network load, 110 NTFS file system, 55

O Online documentation, 176 Operation modes, 198 Output Request, 429

P PAL, 476 PAL Printer, 478 patch, 384 POP, 604 Prerequisite Checker, 43 Primary application server, 90 Printer Group, 478 Product, 384 profile parameter rdisp/btcname, 532 rdisp/btctime, 518 rdisp/max_wprun_time, 503 rdisp/tm_max_no, 602 rdisp/wp_no_btc, 519 rdisp/wp_no_spo_Fro_max, 434 rspo/local_print/server, 435 rspo/store_location, 430 zcsa/installed_languages, 208 Profile parameters, 197 program sapevt, 533

R Release, 9, 384 remote printing, 432

640

report BTC_EVENT_RAISE, 533 BTC_SWITCH_LIST_GRID, 509 SPCPC_DIST_PRG_TO_TSG, 481 SPCPC_SPOO_SERV_MASS_CHANGE, 480

S SAP Application, 6 SAP Application Server, 10 SAP Business Suite, 6 SAP component, 6 SAP CPS, 562 SAP ECC, 9 SAP enhancement package, 167, 416 SAP ERP, 6 SAP Gateway instance, 229 SAP GUI for HTML, 244 SAP GUI for Java, 244 SAP GUI for Windows, 244 SAP GUI installation package, 262 SAP GUI Installation Server, 255 SAP instance, 10 SAP license, 173 SAP Load Generator (SGEN), 210 SAP NetWeaver, 6 SAP Note, 306, 322 SAP Note Assistant, 324 SAP Solution, 6 SAP Solution Manager, 75 SAP Solution Manager key, 47 SAP Support Package, 306, 322 SAP Support Package stack, 306 SAP Support Package Stack, 322 SAP system, 6 SAPconnect, 594

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM12_1

Index

sapevt, 534 SAPinst, 28 SAPINST_JRE_HOME environment variable, 41 SAProuter, 179 SAPSprint, 433 sapxpg, 546 Secondary application server, 90 Single Code Page (SCP), 19 Single Support Packages, 411 SMTP, 600 SMTP plug-in, 594 Software component, 10, 384 SP Stack, 406 SPAM/SAINT update, 357 spool request, 429 Spool Request, 429 Standard background jobs, 199 standard jobs, 520 Standard users, 159 Start and stop, 159 Support Package, 384 Support Package Manager (SPAM), 357 Support Package Stack, 331, 384, 406 System Landscape Directory (SLD), 115

SBWP, 596 SE95, 373 SICF, 608 SLICENSE, 348 SM_WORKCENTER, 346 SM36, 507 SM36WIZ, 507 SM37, 508 SM37C, 552 SM37DISP, 552 SM61, 545 SM64, 532–533 SM65, 511 SM69, 549 SMLT, 203 SMX, 552 SNOTE, 324 SOADM, 609 SOLMAN_SETUP, 334 SP01, 467 SPAD, 435 SPAM, 357, 367 SPAU, 372 SPDD, 372 SU3, 445, 449 Transport host, 57 Transport Management System (STMS), 195

T

Unicode, 19 Usage type, 18, 107

table REORGJOBS, 521 Target System, 478 Target System Group, 478 TemSe, 430 transaction code AISUSER, 334 LMDB, 345 PAL, 476 RZ04, 544 SAINT, 357

2013/Q1

U W Windows domain, 55 Windows domain installation, 56 Windows file system cache, 55 Windows local installation, 56 Workprocess, 13

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

641

Index

642

TADM12_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

Feedback SAP AG has made every effort in the preparation of this course to ensure the accuracy and completeness of the materials. If you have any corrections or suggestions for improvement, please record them in the appropriate place in the course evaluation.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

643