8. PLAN ECONÓMICO FINANCIERO
8.11 Análisis de riesgo
8.11.1 Análisis de sensibilidad
ager. Now, in addition, they are forcing Solution Man-ager usage by not providing
patches without it. The new SAP method for obtaining your patches is through the use of the Solution Manager Maintenance Optimizer. This article will walk you through the technical steps that are required for setup of the Maintenance Optimizer.
First Things First
First, you will need to install Solution Manager. These steps were closely outlined in my Solution Manager Instal-lation article, SAP’s Solution Manager: How Do You Get It, and How Do You Use It?, which you can find in the SAPtips document library (in the Basis category).
Configuring SAP
®’s Maintenance Optimizer in Solution Manager
By Eric Walter, SAP Basis Consultant
4 On Basis
Figure 1: Solution Manager System Status Display to View Support Stack Level
You can’t install or upgrade
SAP without the key that is
obtained in Solution Manager.
SAPtips
Page 55
S AP tip s Journal April/ May 2008 V olume VI Issue 2
4 On Basis
Now that you have veri-fied a minimum stack level of 9 (ST = 0011 in this example), you can continue configuring the Maintenance Optimizer. Start by opening SAP Service Marketplace OSS note 990534. This OSS note will contain two attach-ments that are in the zip file format. Download those attachments to your local workstation.
Set up your user authoriza-tions for Solution Manager Maintenance Optimizer by assigning role “SAP_
MAINT_OPT_ADMIN” to your user ID. This will pro-vide you with the standard optimizer menu paths in your initial login screen.
You will then need to make sure that your SAP_OSS connection test in SM59 is working successfully. Once you have verified your con-nection is good, you will need to replace the original user ID credentials with your Service Marketplace S number, and your password, to validate a successful con-nection with your ID.
Next, you must run the program SM_PREP_MAIN-TENANCE_OPTIMIZER,
using transaction SE38. This will run and initialize your system so you can configure Maintenance Optimizer.
If this program does not already exist in your system, you must obtain the patches that are shown in the OSS note. Figure 2 shows the section of the note that lists the patches that are included in the stacks.
Next, you will need to use “BC Sets” to activate the SOLMAN40_MOPZ_TTYP_SLMO_000 BC Set in your client. To do this, run transaction SCPR20. Select the BC Set as shown in Figure 3, and then activate it using the button that has a match stick on it. You will be prompted to “overwrite everything”. Choose this option and continue.
Once your BC Set is properly activated, you will need to create a transport that will move the proper data to configure Maintenance Optimizer. To do this, you must run transaction SE01, and transport the objects from client 000, as shown in Figure 4.
As an alternative, you may manually make a transport request using transaction SE09, and copy the list of objects that was contained in the zip file that you down-loaded from note 990534. If this is the case, you will need to run transaction SE09 to create a transport, and copy and paste the list (that is in the zipped text file) to your new transport request. This is shown in Figure 5.
Figure 2: Section of OSS Note That Shows the Validity with Respect to Version and Stack of the OSS Note
Figure 3: Transaction SCPR20 with the Proper BC Set Displayed to Activate Maintenance Optimizer
Figure 4: Shows Transaction SE01 with the Transport Request
SAPtips
Page 56
S AP tip s Journal April/ May 2008 V olume VI Issue 2
4 On Basis
The next step is to activate BC Set SOL-MAN40_CHARM_PROXYFACT_001. This is done in transaction SCPR20. Again, click the button with the match stick to activate this BC Set. This is shown in Figure 6.
Next, run transaction SM_MOPZ. This will start configuration of the Maintenance Optimizer. Figure 7 shows the selection box for this. Click “Yes” to confirm Maintenance Optimizer configuration.
Figure 5: SE09 Creation of a Transport Request (with zip file objects)
Figure 6: BC Set Configuration
Figure 7: Confirmation Popup for Transaction SM_MOPZ
SAPtips
Page 57
S AP tip s Journal April/ May 2008 V olume VI Issue 2
Next, you will have to define your system as it will be seen in Solution Manager.
To do this, use transaction SMSY. You will need to define your systems exactly as you defined them in this transaction (SMSY) when you obtained your system Solution Manager key (when you installed NetWeaver, or upgraded from a previous version). You will also need to define a logical compo-nent in transaction code SMSY for your Solution Manager system. I called this Z_SOLMAN in my example, shown in Figure 8.
You will then need to define a logical system and define it in the client you are using.
To do this, run transaction SCC4 and check if you have assigned a logical system for any other ALE applications.
This is shown in Figure 9.
If not, you can define a logi-cal system using transaction code BD54, and enter the details as shown in Figure 10.
Now, everything should be activated and ready for you to configure the Maintenance Optimizer. Now run transac-tion code SOLUTION_MAN-AGER. Select the Change Management tab, and then select Support Package Stacks. Then click on Main-tenance Optimizer, as shown in Figure 11.
4 On Basis
Figure 8: Logical Component Definition in Transaction Code SMSY
Figure 9: Logical System Definition in Transaction Code SCC4
Figure 10: Initial Screen for Transaction Code BD54
SAPtips
Page 58
S AP tip s Journal April/ May 2008 V olume VI Issue 2
You should then see all of your system components dis-played, as shown in Figure 12.
After clicking on the Mainte-nance Optimizer button, you then continue through the next several screens, which will prompt you for the systems (for which you want to approve patches) until you come to the screen with a button that prompts for
“Confirm Files in Download Basket”. Click this button, and the system will display the screen shown in Figure 13.
4 On Basis
Figure 11: Maintenance Optimizer Initial Screen Before Final Configuration
Figure 12: Main Maintenance Optimizer Screen
SAPtips
Page 59
S AP tip s Journal April/ May 2008 V olume VI Issue 2
After you click the “Down-load files from the Down“Down-load Basket” as shown in Figure 13, you will see a screen that prompts for selection of your download basket files. You can select the files (Figure 14) you would like to approve, and then click “Confirm Download”.
You will now be able to use your Download Manager to get patches that were released on Service Marketplace since April 2007.
Your Solution Manager Maintenance Optimizer is now set up.
Conclusion
This is a layer of complexity added by SAP to enforce your use of the application in your SAP landscape.
Since failure to comply is not an option, the sooner you accomplish this setup, the better. Hopefully, this article will assist you in the setup and implementation for all of your SAP patch management to come.
Eric Walter is a senior consultant specializing in SAP Basis technologies along with J2EE and Java integration with SAP. He has ten years of experience with SAP Basis and security, UNIX administration, Oracle® database administration, and seven years with Java technolo-gies, integration servers, and portal environments. In this time, he has led and supported numerous public and private implementations of these technologies along with developing and implementing architecture at all levels, from programming interfaces to hardware improvements and upgrades. You may contact the author at [email protected]. Be sure to mention the author’s name and/or the article title.
≈
4 On Basis
Figure 13: Confirmation of Download Basket Items
Figure 14: Final Confirmation of Download Basket Items
SAPtips
Page 60
S AP tip s Journal April/ May 2008 V olume VI Issue 2 This article is primarily intended for ABAP developers.
I will assume that the reader is familiar with ABAP programming, as well as the Classic BAdIs. For more information, refer to the SAP documentation on http://help.sap.com. All the screenshots in this article have been taken from ECC 6.0.
New Business Add-Ins (BAdI): An Overview SAP has provided an improved and faster BAdI technol-ogy in the ECC 6.0 release. The new BAdIs are based upon the same concept of object orientation as classic BAdIs. However, there are a few differences. The new BAdIs are provided as part of the new Enhancement Framework. In the new Enhancement Framework, the BAdI becomes an optional enhancement, or an anchor point into which coding may be plugged. The new BAdIs reside in containers known as Enhancement Spots. Each BAdI has an Interface composed of the BAdI method(s). It is this method which is accessed in the program.
Note: An entire discussion of Enhancement Framework is beyond the scope of this article. It will be discussed, however, in an upcoming article. For more on Classic BAdIs, see my article Enhancing Standard Programs Quickly & Easily Via Business Add-Ins (BADIs) in the
“ABAP, Java, and J2EE Development” category in the SAPtips Document Library.
In addition to the benefits provided by the Classic BAdI, one major advantage that comes with the new BAdIs is that they are faster in execution.
Editor’s Note: Pssstt…wanna check out something HOT in SAP? Take a look at the newly enhanced BAdIs avail-able in ECC 6.0. Rehan Zaidi addresses the benefits of the new Business Add-Ins, how they differ from previ-ous versions, their implementation, single vs. multi-use BAdIs, and even answers this question: What is an Enhancement Spot? Take a tour with Rehan and learn how you can get the most out of the BAdIs in your SAP system.
Introduction:
Over time, SAP has improved the ways it allows cus-tomer-specific requirements to be incorporated into the standard R/3 functionality. The enhancement options are no exception. One example of such an improvement is the introduction of the new BAdIs.
These BAdIs are faster in performance and are easy to define and implement. For these reasons, having the knowledge of the new BAdIs is an absolute must for developers and consultants.
The aim of this article is to discuss the new Business Add-ins (BAdIs) provided by SAP since ECC 6.0. I will begin with an overview of the new features, and then discuss the characteristics of multiple- and single-use BAdIs. The structure of the new BAdIs will be examined and examples will be presented. How to implement the new BAdIs will be explained in detail.
These are some of the questions this article will address:
• What are the benefits of the new Business Add-ins?
How do they differ from classic BAdIs?
• What is the new Enhancement Framework, and what is an Enhancement Spot?
• What would a typical call for the new BAdI look like?
• How do single-use and multiple-use BAdIs differ?
• How are the new BAdIs implemented?