If you are preparing for the PCOE certification or re-certification and you are supporting SAP Business All-In-One and/or SAP HANA, SAP Solution Manager is the mandatory platform for service delivery to your customers. This system must always be on the current or immediately preceding support package, which means only version 7.1 SP 8 and 9 will be accepted for any certification or re-certification requests starting July 1st 2013.
With ST-A/PI 01Q* several new exception key figures were introduced for different areas (e.g. SAP ERP sales, SAP CRM sales & services, SAP APO). The feedback of first customers in our Business Process Improvement projects was overwhelming as root cause analysis becomes a quick and straighforward task. Hence we decided to provide further such key figures in the future. In my previous blog about exceptions during Period End Closing I already gave some heads-up that we will develop further such key figures in the area of Controlling. Now with the shipment of support package 1 for ST-A/PI 01Q* several new monitoring objects and key figures are available in the area of CO-PC. In Business Process Monitoring and Business Process Analytics you can find now some new application area Controlling for filtering. Under this application area you find some "old" monitoring objects like Cost Estimates and Schedule Manager Monitor that were already available in the application area Fincancials (where they still resides as well). But now we also provide new objects and key figures in Controlling.
In product cost planning (CO-PC-PCP) you can find now the new monitoring object Exceptions in Costing where you find two new key figures. One key figure is Exceptions during costing run which checks for alle error messages (no matter if it happened during the selection, costing, marking or releasing process) that were raised during any costin run in the defined reference period.
The other key figure is Exceptions during cost calculation CK11N which checks fr errors during costing itself that were performed in dialog mode.
In the are of cost object calculation (CO-PC-OBJ) one new monitoring object Exceptions in Cost Object Controlling was introduced with two new key figures Exceptions in WIP calculation
and Exceptions in Variance calculation
Finally in the area of actual costing (CO-PC-ACT) we introduced one new object Cost Calculations from Confirmations with the new key figure
Incorrect Cost Calculations from Confirmations which lists all cost posting errors that happened during order confirmation (no matter if it comes from a production, process or maintenance order etc.)
Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and
http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.
The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.
Standard functionality:
When an Urgent Change is set into status 'In Development' from the status 'Created' a dialog window is opened up automatically. This dialog window allows the user to create transport requests.
Some background for developers and consultants:
Technically, the dialog window 'Create Transport Request' has an UI usage to the change document header UI component (which is AIC_CMCD_H) and is registered in the ChaRM Dialog Window Framework where you can register dialog windows to a PPF (Post Processing Action) action.
Depending from the customizing dialog windows can be started before or after the PPF action is executed.
The 'Create Transport Request' is from an implementation view an independent dialog window which means if it is called the code which does the real functionality is executed in the dialog window itself (this is different in the Transport to sandbox dialog window for example).
This means it just has to be called.
New use case for the Normal Change or (untested) the Defect Correction:
There might be customers who like the dialog window in the Urgent Change as much for the Normal Change or Defect Correction because it fastens up the process.
The nature of the implementation of the 'Create Transport Request' dialog window allows it to implement this dialog window for the Normal Change for an experienced PPF customizer in about 15 minutes which is a fine ROI :-).
How to do it:
1.) Maintain the PPF container class as an element in the PPF action which sets the user status 'in development'.
This is done in the IMG activity 'Define Action Profiles and Actions'. Normally if you copy the SMMJ to ZMMJ the PPF action is named 'ZMMJ_IN_PROCESS_MJ'.
2.) Here, you have two options. The one with and the one without modification:
2.a) Small modification (You need a developer key from the service marketplace for that): Enhance the filter for the BadI.
go to transaction SE19 and display the AIC_POPUP_EXAMPLE enhancement.
The filter looks for implementation AIC_CREATE_TRANSPORT_REQ like this:
Change the BadI filter to the value '*IN_PROCESS*. You need a developer key for the object R3TR ENHO AIC_POPUP_EXAMPLE to do that.
Save everything to a transport.
2.b) Without modification: Copy the PPF action which set the status 'In Development' to the name <transaction type>_PROCESS
Please be aware that we copy and then delete the old PPF action. This means you have first to check which schedule and start conditions the old PPF action ZMMJ_IN_PROCESS_MJ has (or have to look it up later in the productive system).
We do that in the IMG activities 'Define Conditions'. Switch to the Technical Name so you find the action profile more easily.
Be aware that you might have adopted the schedule and start condition as shown in the screenshot here. Note down the name of the schedule and start conditions assigned.
Then go to IMG activity 'Define Action Profiles and Actions' and to the action. Mark the PPF action and copy it
Rename it to 'ZMMJ_IN_PROCESS'
Copy all dependnet entries:
Save your changes in the transport request.
Delete the old PPF action ZMMJ_IN_PROCESS_MJ:
Now you have to create the PPF condition, so go back to the IMG activities 'Define Conditions' in the action profile. Create the PPF condition.
And assign again the start and schedule conditions which you marked down first:
Do it for the schedule and start condition (if you have any). Save your changes.
3.) Register the dialog window for the PPF action
Last action is to register the dialog window to the Dialog window framework and to the PPF action. If you have chosen variant 2.b) please notice that the name of the PPF action is ZMMJ_IN_PROCESS instead of the ZMMJ_IN_PROCESS_MJ as displayed in the screenshot. You can use the marked SMHF entry as a copy template.
Save your changes.
Now the dialog window 'Create Transport Request should be opened if you set a Normal Change from status 'Created' to status 'In development'.
The same should be possible for the Defect Correction of course I have to admit that I have not done it yet. The PPF action which is relevant for the Defect Correction is ZMTM_IN_PROCESS_TM. You have to create the same PPF container element in step 1.). You can skip 2a.) if you have done that. If you choose 2.b) you have to do it for PPF action ZMTM_IN_PROCESS_TM as well. For 3.) just fill in the entry with PPF action ZMTM_IN_PROCESS_TM and action profile ZMTM_ACTION.
As always if you find errors or have comments, please give me feedback,
Best,
Michael
That's an update for that post where i sho how it's possible to control the view of operation in ITSM withour autorization or customizing, but on a last update ( i don't remember when ) i found a change on VAR GUIDE for service provider https://websmp204.sap-ag.de/~sapidb/011000358700001075532012E.PDF on page 66, "How to Display all Messages of an Organization/Company".
You can control the operation view in 2 options:
1.- With Custom Code:
2.- Trough customizing using AGS_WORK_CUSTOM, :
* I don't have test if that work as well on ITSM as on in workcenter
6.7 How to Display all Messages of an Organization/Company
("Employee responsible for")
The BP Relation "Is the Employee
Responsible For" (technical name "BUR011") must be maintained for the
user.
To do this, follow the same steps as described for "Replaces" relationships, but instead maintain the
relationship "Is the Employee Responsible For".
If the system finds an "Is th
e Employee Responsible For" relation for the current user, all messages of the
related Business Partner (for example, Messages where the related Business Partner is entered as the
"Sold
-
to
-
Party") will be added to the "Processing by my team" list in the Wo
rk Center overview.
This behavior is turned off by default.
Adding an entry to table AGS_WORK_CUSTOM overrides the default:
IM_RESPONSIBLE_REL_ENABLE = X (Turned on)
IM_RESPONSIBLE_REL_ENABLE = blank (Turned off)
The Business Partner relationship catego
ry "BUR011" may also be overridden with an entry in table
AGS_WORK_CUSTOM:
IM_RESPONSIBLE_REL_CATEGORY= <new relationship category>
Regards,
Luis
For customers, consultants and developers ;-)
When a user status is changed via PPF action HF_SET_STATUS in the ChaRM Framework, sometimes the message 'You are not authorized to perform the activity selected last' comes up and the user status is reset.
A bit more information on the ChaRM Framework can be found here in the screenshot 'Request for Change - Standard Process Overview':
The message can have different reasons, described in note 1706259. As they are connected to wrong customizing or missing authority, I would like to give you some more information at hand, so the developers out there are able to analyze this for there own.
The possible reasons known to me are:
1.) authority B_USERSTAT
2.) status Lowest/Highest customizing
3.) status history
4.) Implemented Customer BadI Implementation for the User Status
1.) Missing authority for B_USERSTAT is the simplest thing. To check this via debugging set break-points (4 places) in class
CL_IM_CHM1_HF_CHECK_SET (set a break-point for all statements AUTHORITY-CHECK OBJECT 'B_USERSTAT' ).
2.) The Lowest/Highest Customizing defines if you are allowed to go from one user status to another user status. Each user status has a Status Number.
The Lowest - Highest value range defines to which status number you can go back from the current user status.
Take the example below. It is allowed to go from 'Approve Functional Spec' to 'Hard Release Approval', meaning from 15 to 35 because status 15 'Approve Functional is customized to allow next user status from 10 to 90 and 35 is in that range 'Hard Release Approval'.
But back from 'Hard Release Approval' (35) to 'Approve Functional Spec' (15) is not allowed because 'Hard Release Approval' (35) is only customized to set the next user status to 35 to 50 and 'Approve Functional Spec' (15) is out of range.
Please be aware that the user cannot jump to different user status without the customized PPF action to set the user status :-). So, this is just theoretically.
3.) Status history.
This is the most hardest case to explain. The status change history of a document is recorded. In our example again if we go from Create Functional Spec' (10) to lets say 'Hard Release Approval' (35) and then to 'UAT' (30) our status history from lowest to highest reads...
| Number | Status | Lowest | Highest |
|---|---|---|---|
| 10 | Create Functional Spec | 10 | 90 |
| 35 | 'Hard Release Approval' | 35 | 50 |
| 30 | UAT | 20 | 90 |
If I now try to go to 'Development & Unit Test (20) this is forbidden. From a Lower/Highest point of view user status 'Development & Unit Test (20) is allowed to be set because the range is 20-90 and 'Development & Unit Test (20) is in the range but the status history remembers that we were already in status 'Hard Release Approval' (35) and this status has a lowest/highest range customized from 35 to 50 and then this is out of range for 'Development & Unit Test (20).
Note 159553 describes this behaviour.
Then the error comes up like in the screenshot.
And unfortunately it is the same exception for 2.) The Lowest/Highest Customizing which makes it hard to create a specific message for the user.
4.) Implemented Customer BadI Implementation for the User Status
Be aware that there can be additionally BadI implementations for the BadI CRM_ORDER_STATUS which hinder user status change. Described in note 1627673 f.e.
Here is a taste of this :-)...it comes back with the same exception 2 NOT_ALLOWED as well.
The function CRM_ORDER_CHANGE_STATUS is hard to debug as it contains a lot of logic and layers, down from CRM to the user status management.
I had the feeling there are further issues not yet described or recognized by me which can lead to exception 2 NOT_ALLOWED and they have are connected with system status issues but as I was not able to understand and explain it in detail, I will skip this and leave this to more experienced colleagues,
Hope that sheds some light on the issue,
best,
Michael
SAP IT Incident Management Mobile App
Create and track incident messages from your mobile device – with our IT incident management app
http://www54.sap.com/pc/tech/mobile/software/lob-apps/it-incident-management/index.html
Evaluate the performance and availability of your IT landscape with our user experience monitoring app
http://www54.sap.com/pc/tech/mobile/software/lob-apps/it-user-experience-monitoring/index.html
Get real-time insight into system availability and performance – with our system monitoring app
http://www54.sap.com/pc/tech/mobile/software/lob-apps/it-system-monitoring/index.html
Access and manage your IT change requests on the go – with our IT change approval mobile app
http://www54.sap.com/pc/tech/mobile/software/lob-apps/it-change-oder-approval/index.html
YouTube Videos
http://youtube.com/watch?v=8X2U-Gs6zSY
http://www.youtube.com/watch?v=2UQ3_sU7aTU
Application Porfolio & compatibility
Problem:
You are looking for sap notes to solve your problem, and the limit to display the result is to short, I hate paging trough hundreds of sapnotes
You can short, can filter but if you have more than 10 page result you can’t di a quick search through results
Now just try that trick to “tune-up” SAP Marketplace
1.- open sap note search on a browser with an sourcecode inspect tools, G.Chrome for my case
2.- Configure sort criteria for dysplay results by release date descending and application area that you are interested, and just right click with the mouse and “Inspect” on field Results Per Page like that screenshot
Once on “Inspect mode”, search for “select” and change 50 to 500
Now, you will se that Results per page has been changed to a higer number
Just click and enjoy
We pass from 45 pages of results to only 5 that we can export to excel, search with CTRL+F in-site and sure that can found if there is something related to our search.
Hope that this trick can do someone the notes search more accurate and quick
P.D. don’t try to change calue to 99999, it dosen’t work ;-)
Regards,
Luis
On popular demand:
How do you add multiple SAP systems to the Solution Manager 7.1 – Technical Monitoring widget? I gave away some hints in the original blog post: “Solution Manager 7.1 Return of the widget” but still many questions came in my direction on how to exactly go about changing the widget.
In this example I show you have you can end up with seven managed SAP systems. I don't know if there is any upper limit in terms of how many you can add so you can follow these steps & change them to your liking in order to add <n> number of managed SAP systems.
So here we go:
Call up the System Monitoring widget, right click & choose Widget Preferences
In the preferences, you only have 5 input fields to insert managed SAP systems.
So this is the first place where we have to make a change in order to allow more inputs to be given to the widget.
Open up Main.kon with notepad ++ (or another editor)
If you look for “FavoriteSystem” you will soon notice XML that is related to the five input fields.
Copy one block (not the last one) & insert it twice
Change the <name> of the copied blocks as shown above into FavoriteSystemFive & FavoriteSystemSix
Rename the last block from FavoriteSystemFive to FavoriteSystemSeven
To check the result, zip your folder back into a zip file and rename it to .widget ~use another name than the original widget.
Now open up this widget with the Yahoo Widget Engine
Right click and navigate to preferences
So we have two additional input fields. It’s not very clean yet because the * text is displayed twice but we’ll fix that in a second.
You can use the find in files function in notepad ++ to detect other spots in the coding where FavoriteSystem is used
One of the first hits is in controller.js
Here you can see where the “Enter at least” text is coming from on the Fifth system. Since we added two more systems, we now change FavoriteSystemFive into FavoriteSystemSeven
Pack the widget back in, run it to check and you now see the text “*Enter …” is only displayed on the last system in the preferences.
Moving forward, the next “hit” on FavoriteSystem is still in controller.js
Here add && ( preferences.FavoriteSystemSix.value == 00) && ( preferences.FavoriteSystemSeven.value == 0) before the last )
Result
Moving forward, the next “hit” on FavoriteSystem is in Model.js
We are not going to change line 155 – 159 or add lines since this is purely commented code //
So we end up on line 166 in Model.js
Before line 180, add two blocks for six & seven
Result
Pack in, load widget again
You can see now that we have more than five systems!!!
But as you can see, the widget seems to be too small.
Two options, we can increase the widget pane and we can let the widget “scroll” by adding lines to the table.
C:\widget\sysmon\SAP System Monitor.widget\Contents\components\Main\js\view\view.js
Adjust the line for(var j=0; j<5; j++) into (var j=0; j<7; j++)
The screenshot above also represents the result!
Main.kon defines the main widget pane so we have to take a look there 
C:\widget\sysmon\SAP System Monitor.widget\Contents\Main.kon
In Main.kon we see a <height> tag for the mainWindow so this looks like the value we need. So we have enlarged the “placeholder” of the content by 138 pixels (original value was 262).
In the config.xml file that accompanies the “skin” of the widget, you also have height values which define the height of the respective rows.
To add some height here, we add 30 pixels to tools_height (from 255 to 285) and we add 30 pixels to <row height=”160” /> which makes us end up with the above result <row height="190" />
Again pack up & widget it
Voila, you now have more than five systems configured, seven to be accurate.
You don’t see all seven in above screenshot because I didn’t enlarge the pane to display them all. The bar on the bottom indicates you can scroll up / down to display the system(s) that are not visible at first sight. In order to scroll click next to the System Monitoring header and then you can just mouse scroll up & down the list.
Of course you can also enlarge the widget further if wanted using the instructions in the blog post (if you want to avoid scrolling).
Have fun!
Like last year, SAP America will be hosting an SAP Innovation Camp (July 30-31, 2013 | Chicago, Illinois) where you can learn how SAP can help solve your business challenges and introduce you to new groundbreaking innovations. Also the SAP “mission control center” approach will be shown to help keep your organization running at peak performance. The camp is spread over two days and divided into four main tracks
New this year are “Meet the Experts Hours” when you can visit each track and meet with SAP experts, as well as your peers, to discuss your own organization’s current business challenges.
As part of the Enable the Real-Time Enterprise for all Lines of Business track, it is planned to have a session Business Process Analysis: "Know your Baseline"(1:30 pm on Tuesday, July 30). During that session you will learn how the Business Process Analysis (as a service) and Business Process Analytics in SAP Solution Manager (as a tool) can help measuring your current baseline for a Business Process Improvement project, and how this can be the starting point for a larger Value Chain Optimization process.
If this, or the other tracks, sound interesting to you, then you can find further information and registration links on the event's landing page http://www.sap.com/sapinnovationcamp.
See you in Chicago...
Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and
http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.
The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.
Everybody is talking about end to end processes like Order to Cash, and for such an end to end Order to Cash process we already suggested key figures for monitoring about 4 yeas ago. Since then many key figures have been enhanced and new key figures were introduced with the different ST-A/PI releases. Something that became obvious during customer projects over the past few years, was the fact that most organizations are still not living the entire end to end process from Order to Cash. Instead most organizations are living an Order to Invoice process (with sales and logistics aspects) and the cash collection is handled separately within the finance department or some Financial Shared Service Center.
The challenge is now, if you want to improve your Order to Cash process really from an end to end perspective, then you somehow have to bridge the organizational gap between the sales folks on the one side and the finance folks on the other side. Of course you want to ensure that all SD billing documents are really transferred to accounting and hence reflected in your financial statements. For this purpose you can use the key figure Sales invoices not posted to FIthat was enhanced with further exception information as of ST-A/PI 01Q (you can find a more detailed description in my corresponding blog Enhanced key figures: Analyzing/monitoring SD invoices not transferred to FI). With the help of this key figure you can at least ensure that everything is successfully tranferred from the SD module to the FI/CO module.
But what happens then? How can the sales people track if the customers are paying their respective bills and how can the finance guys gain more insight how the open FI-AR items might affect the sales and related credit checks?
Sales invoices with open FI-AR items
In my blog about new key figures with ST-A/PI release 01P, I mentioned for the first time the key figure Sales invoices with open FI-AR items. This key figure was now (ST-A/PI 01Q SP1) slightly adjusted according to common customer requests, i.e. the key figure is now only showing those open items that are overdue according to the Net Due Date. So what is this key figure doing and what is so special about it? This key figure represents a subset of all open and overdue FI-AR items. Only those FI-AR items are shown, that have an SD document as referenced source. Usually that would be all those items with document type RV, but it can also include different document types depending on your customizing settings. So with a pure financial open FI-AR item analysis you are always running into the problem on how to figure out which open items are really sales related and which are not. The key figure Sales invoices with open FI-AR items provides this kind of distinction automatically. Besides the FI information (document type and posting key) you also get to see the sales information about document category, billing category and billing type. This allows an easy analysis which business process variants are making problems and which not. This key figure also provides information whether the open item is related to some invoice cancellation or not. This is very helpful, as it often happens that sales transactions are reversed several times and at the end the finance department is losing track whether a certain transaction is still awaiting some payment or whether the whole transaction should really be cancelled. The result list is also providing the information at what date the invocie was created and sent to the customer (billing date) and since when the corresponding open item is due for payment (net due date).
So the key figure Sales invoices with open FI-AR items should especially help your sales colleagues to gain an understanding of how much of their sales is overdue for payment/clearing. The key figure could also be helpful for the finance people in order to understand how much of the open and overdue FI-AR items are related to sales.
The key figure Overdue open items FI-AR (customer items) was already mentioned in the Best Practice blog about Order to Cash. Now with ST/A-PI release 01Q support package 1, we enriched the pure FI-AR key figure with information from the credit management module. Every open FI-AR item is assigned to some credit control area and customer. With this information you can uniquely identify credit management information that is also displayed in the open items list. The additional information that you get is
With this additional information you have some kind of light version of what the Collections Management provides in the Financial Supply Chain Management module. It should also help to evaluate which customers need to be re-revaluated with regards to credit risk and which open items have to be written-off.
Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and
http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.
The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.
In continuation to my previous blog, Problem Management is the new capability available from Solution Manager 7.1 version onwards.
This helps to identify the real issue behind several incidents corresponding to same major problem. For e.g. we visit a doctor and suffering from cough and cold with fever, doctor performs his analysis, test or finds root cause of it and informs us it’s a Viral Infection.
Thus, Problem Management is a process by which Support Team can identify and then resolve the root cause of the similar incidents.
The SAP standard transaction type for Problem Management is SMPR and it has the same status profile like we have for SMIN or Incidents.
As a process we can integrate problem management with incident management process. Typically, End User post incident incase of facing issues which can be SAP or Non SAP. Support Team is identified to resolve it. In case, if deeper analysis is required and also it is cause of many other incidents, Support Team member or Message Processor can create a problem ticket.
Creation of Problem Ticket as a follow up from incident will also link up the incident to problem ticket. In the below screenshot, we can see if we click "Create Follow-Up" button a pop up appears and allows to create a problem ticket.
Click on the SMPR or Problem, system will create a new Problem Ticket as shown below.
Well we can see here plenty of fields copied from incident automatically to problem message or ticket. This enables the person who is going to work on this Problem with all the details like relevant system, issue reported via incident etc.
In addition system creates a relationship with related incident and this is visible in the Related Incident section for the problem.
There is another great feature here that we can lock the incident so that extra efforts for the other Support Team will be saved and only one concerned person will work on the problem message.
To lock an incident click on Edit List button and choose the incident. Now click on the Lock option and you will notice incident is locked.
Thus now Problem Management Support Team member can work upon the problem ticket and resolves it followed by incident resolution as well.
Easy and quick remote connection option for a quick assistance from SAP
Hello mates,
How many time do you found a lot of problems with your customer's/collage when someone need to open and R/3 remote connection for SAP for a Very High message and you spend a lot of time while fighting with saprouter, firewalls, dmz's, external partnners, bla,bla, bla.
SAP AGS support team usually ask to us to open the R/3 remote connection, with that connection they can work better and found the root cause of the problem related quickly, but sometimes you found always a lot of problems, let go to see an usual customer scenario.
Problem:
One of our customer found a problem on a one of CRM linked to a netweaver portal system, hosted on a Exernal Partner Datacenter that have a strong DMZ security polices and a high security restrictions. That customer need support on to check a problem on web client crmui interface (that's not relevant).
If you need to open remote connection as indicated on sap Note 1281633 - Speed Up Processing of a Customer Message, for that type of problem you need to open R/3 connection, http remote connection anf if it's possible mstc, lets go to see what we have to setup for allow remote connection and how may time we can spend on it.
Honest process/time to open it with R/3
We will need more than 3 days (or more) to open R/3 remote connection on that DMZ scenario, we will spend more time for alow the remote connection that the time that support team need for fulfill SLA's.
Solution:
The is a littler remote software that it's not usually know-ed for old sap consultants, Remote Netviewer Software, collage that works with systems like BO use that software because on BO it's not possible to allow an R/3 connection. Let's go to see how many time we can spend on the same scenario explained before with that software.
Honest process/time to open the remote connection trough Netview:
1.- Open the remote connection on sap marketplace for related system
2.- Create/update message to indicate that the remote connection is allowed trough netview and request the message processor netview session number
3.- Once message processor give yu the netview session number, open client software from http://www.netviewer.com/sap-ags/en/ and enter the session number.
4.- Now Message Processor will be able to see your desktop and request control of for access to the system.
Just 4 quick and simple steps that allow message processor manage your laptop/computer/server from where you run the Netview client without any type of problem and without the need to open firewall ports, setup saprotuer, etc...
So...
If you need quick assistance for a very high issue, open Netview Remote connection.
Remember to don't do that if you don't have a big issue or a quick solution to solve the problem, use that type of connection is hard for support team
More information about Netview connection:
Download Software:
http://www.netviewer.com/sap-ags/en/
SAP Support Notes
Note 1036616 - Netviewer support sessions
Note 1311904 - Setup netviewer conection
Note 1311904 - How to setup and configure Netviewer connection from Service Market Place (SMP)
Bonus:
From Solution Manager higher than SP07 you can open that type of connection trough service backbone, just allow it from SMP and open Service Backbone on Solution Manager.
Best Regards,
Luis
I had problems during Retrofit regarding the assignment of Transport of copies in the first week of ChaRM 7.1 SP8 Golive last month. I saw people with the same error in the Discussions Forum, so here I show how we fixed this error and my understanding about how the functionality works. As a developer, I like to go deep into how things work. It's a good to way to learn. I don't want to spend too much time with similar errors, so it's always good to have an idea of what is behind the scenes. Sometimes the error messages are not clear enough, they do not show you immediately the reason for the error. In this case, the message can confuse the user and unless he/she knows the complete process, it may be difficult to start searching. The reason for the error is simple and easy to fix.
The symptom is that: when you decide to retrofit the changes in ChaRM 7.1, you receive an error message "No transports of copies assigned to request for retrofit".
For more detailed information about Enhanced Retroft and the different types (Auto-import, SCWB ad BC Sets) please refer to document http://scn.sap.com/docs/DOC-41654 and to blog http://scn.sap.com/people/hannes.kerber/blog/2013/07/06/retrofit-how-to-perform-retrofit-from-an-end-user-perspective. If all steps (ALL) are followed by you and/or your Basis team, you probably won't have any error.
I will focus on the specific error related to Transport of Copies during Automatic Import.
I assume you implemented SAP Note Note 1468044 - Retrofit extensions - for managed systems in your managed systems.
When a transport request is released and the objects can be auto-imported, a transport of copies (ToC) is created and released (exported). This is done remotely in the development system of the maintenance landscape by function module TMW_CREATE_TRANSPORT_OF_COPIES. This function module must exist in your managed systems.
In order to create and export the ToC, it's necessary that the target of the transport of copies is known by the development system where it's being created, which means that if you have dual landscape and your development systems are in different domains, you need a link between the domains. If not, you will see that the ToCs are created in the development system of the maintenance landscape, but not released. Function module TMW_CREATE_TRANSPORT_OF_COPIES will be able to create the ToC, but the export part will fail. When this function module fails during the release of the transport request, you will see a warning in the application log for "Release Transport Request":
"Internal error 8 occurred creating the retrofit data in TMW_CREATE_TRANSPORT_OF_COPIES".
This is the first symptom that something was wrong. Or the function moduled failed, or it was not found in your managed system. Below you can see the application log in the Change UI:
If this creation and export succeed, an entry is created in table /tmwflow/tocasng. This ToC will be used by the Auto-Import functionality and will be imported into the Retrofit system (the post-processing system of your logical component).
If you have the same error and/or warning, check your development system in the maintenance landcape. If you find the ToCs created by user SMTM<SID>, where <SID> is your SolMan system, but not exported (still modifiable), enter a target (target is probably there already) and try to save.
If you have an error message "Target system XXX is unknown in the current transport configuration", you miss a link between the different domains or, if they are in the same domain, something is wrong that one system is not "seeing" the other. If the ToC can't be exported, it will not be added to table /tmwflow/tocasng. You will not find those modifiable ToCs in this table.
Example of ToCs:
Modifiable ( It was created but not released because we missed the domain link in the first try )
Released by the system (in this case, everything worked fine and the standard programs could create and export)
Table /tmwflow/tocasng:
When the auto-import is finished, this table will be similar to that:
Scope:
When you have a loot of remote systems connected to your Sap Solution Manager, you wil need to update/change or verify you saprouter / saprouttab information usually; for add a new system, for change a remote public/private IP from a external system, etc...
Whit that Solution Manager Option you will be able to edit the content of saprouter from your central Solution Manager, that will be useful to add new rules or edit saprouttab without access to server where sapouter is installed.
Limitations:
We are not able to setup a new snc connection with that option or renew from SAP Solution Manager, for that you will need to access to Saprouter server.
Process:
1.- Access to Server where Saprouter is installed and install a ftp server, Firezilla is what i used on my own test.
2.- Check that you don't have any problem to access remotely to that ftp server, that will be save you communications problems trough firewall ports.
3.- go to solution manager spro img guide, open "SAP Solution Manager" -> "basic configuration" -> "Sap Router" -> "Update Saprouter information..."
(tested on Solution Manager 701, i don't found that setup path on img for Solutiom Manager 7.1SP8 but transactions still works)
4.- Add new entry, in that table you have to add the server name where saprouter is installed, and FTP account details for access remotely.
On that screen you have to add the next fields mandatory (sorry for Spanish screenshot)
Host Saprotuer: IP adress where is installed saprouter
Internal Saprouter: to indicate SAP that we don't need to read information from SAP.
Dir.IP.SAPServ: IP adress where is installed saprouter (the same yues i don't know why)
User: ftp user account
Password: *******
Account: account name ( not releant )
5.- one's the setup is done you will see something like that:
If you click on saprouttab you will access to the next screen that is the saprouttab editor.
6.- Now you only need to run the command "saprouter.exe -n" in the server, you can't do that using that tool, but you can found a solution in the next options:
- Run a bat process that or service that execute that command if you find some modification in saprouttab.
- a remote command created on SAP transaction SE69
- Calling a webservice
- With a litter script o program that execute the saprouter command in the server if you found any modification in saprouttab
Transactions:
SOLMAN_SAPCONECT ( don't work on Solution Manager 7.1 SP08 )
SOLMAN_SAPROUTER
Sources:
Regards,
Luis
them.
EVAL_STARTCOND_PPF has to be done and customized in the PPF condition for both actions, so the PPF action is visible only for those roles.
The following session will show how to copy the solution from one system to other system, example from Quality Environment to Production environment after the successful testing and Validation. In our case it’s transferring the Solution from older version to new, from Solman 7.0EHP to Solman 7.1(SP8). This document shows the step by step approach and also mentions the troubleshooting faced after moving the solution from Old Version to new
STEP 1: EXPORT SOURCE SOLUTION
First we need to export the Source solution from source System using Tcode SOLUTION_TRANSFER, i.e. Business Process Monitoring Solution from Solman 7.0 EHP 1 to local desktop in ZIP file.
Once the solution in uploaded, all the logical components are visible please click on EXPORT option below.
Now the Solution dump is downloaded in Local system.
STEP 2: CREATE NEW SOLUTION
Now we have to create a New Target solution in Target system with name “X” Business Process Monitoring
Go to Work center SOLUTION MANAGER ADMINISTRATOR
Now enter the New Target solution name “X Business Process Monitoring” in Solman 7.1 and save the solution.
STEP 3: IMPORT TO TARGET SOLUTION
Import the downloaded solution in target system by using Tcode SOLUTION_TRANSFER, and feed the source solution name and also newly created target solution in MNS and upload.
Once uploaded we can see the Target Solution System Landscape along with the Logical components in the target system.
We can select on COPY only (Don’t REPLACE) since replace will deactivate the old Solution and make the new copied solution as master.
Replace: The target solution replaces the source solution. This option can only be selected once per source. The Replace option ensures that SAP, recognizes the replacement after re sending the solution and its data (Top Issues). After importing and testing your solution data in the target system, you should no longer use the solution in the source system.
Copy: The source solution with data is the template for the target solution. If you send the target solution with your contents to SAP again, it is handled as a new solution Check whether it is advisable to put the data in Scope (Top Issues, Issues, Expertise on Demand Requests and Service Plans) in your new target solution
Now click on IMPORT OPTION, to import the solution to target system.
After completion of Solution transfer to target system, we need to set up in Bpmon and load monitors for the assigned logical components.
STEP 5: GENERATE AND ACTIVATE THE BUSINESS PROCESS
Now generate all the Business Process in the solution, and then activate it for monitoring and alert enabling.
Once activated the data collectors will be started and the monitoring process started according to the defined threshold and alert values.
TROUBLESHOOTING:
We might face errors normally when you migrate SP Level UP (mainly From SP5 , SP6 and SP7) or trying to Transfer solution from Lower version Solman to 7.1
Here we faced an error where LOGICAL COMPONENTS were missing Monitoring Objects after the transfer and unless we see the monitoring Objects there will be no Alerts in ALERT Inbox as shown below.
So in order to solve the problem we need to implement notes:
This tells us to run the report R_AGS_BPM_SOLUTION_MIGRATION and make sure Indicator for creating the backup version is set before executing the report.
Once the report is successfully executed now we can see the Monitoring Objects populated in Setup and also started receiving the Alerts in ALERT Inbox.
When looking at Business Process Analytics in SAP Solution Manager you basically have two ingredients
Key figure content with several hundred key figures available for all SAP Business Suite products.
The key figure content is constantly updated with every ST-A/PI release (or support package)
Now with so many key figures at hand it might be easy to lose track of what the different key figures are good for, what is the respective main use case and how are those key figures perhaps different from other SAP or non-SAP applications?!
Currently we provide basically 5 different key figure types that you see listed below.
Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and
http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.
The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.
Hi All,
I have done few installations and upgrades of solution manager (7.1 SP5/SP8 ), where I have faced number of issues. So, in this platform, I am sharing some of those which would surely help you :-
1. Don't apply the upgrade consolidated note at initial phase as it generally leads to numerous dumps in various T-Codes. So accept the warning while "system preparation " processing and apply the selected notes of that consolidated one later on (means after doing system preparation & basic configuration steps).
2. Activate all the required ICF services by running "RSXMB_ACTIVATE_ICF_SERVICES" program instead of manually preforming the same.
3. Increase the HTTP time out (Maximum processing Time ) in SMICM T-Code.
4. Change the following parameters :-
5. To get rid of "Not able to load function AGS_SISE_SET_CTC_STATUS" error follow below process :-
| 1. | Go to SAP Netweaver Application Server Java and click “User Management”. |
| 2. | Login with J2EE_ADMIN user. |
| 3. | Click “Configuration”. |
| 4. | Go to ABAP System tab. |
| 5. | Check the client, if it is not ABAP production client click “Modify Configuration” and change it to correct client (in my case client 100). |
| 6. | Click “Test Connection” to make sure that right credentials are used. |
| 7. | Save all changes. |
6. To get rid of "EXPORT_BUFFER_NO_MEMORY" error , change following instance profile parameters :-
rsdb/obj/buffersize 204800
rsdb/esm/max_objects 10000
rsdb/esm/buffersize_kb 204800
7. If you get RFC error in solman_workcenter T-Code , then perform the following settings:-
Run SECSTORE t-code and delete the entry "/HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM " (shows in RED color). Also delete the other entries shown in RED color. [Follow 1532825 note].
8. SOLMAN super user should have following roles:-
SAP_J2EE_ADMIN
SAP_RCA_AGT_ADM_VIA_SLD
SAP_SMWORK_BASIC
SAP_SMWORK_BASIC_SYSMON
SAP_SMWORK_CHANGE_MAN
SAP_SMWORK_CONFIG
SAP_SMWORK_DIAG
SAP_SMWORK_INCIDENT_MAN
SAP_SMWORK_SERVICE_DEV
SAP_SMWORK_SM_ADMIN
SAP_SMWORK_SYS_ADMIN
SAP_SMWORK_TECH_MON
SAP_SMWORK_BASIC_SYSMON
SAP_BI_E2E
SAP_PI_CCMS_SETUP
SAP_SDCCN_ALL
SAP_SM_BASIC_SETTINGS
SAP_SM_BI_ADMIN
SAP_SM_BI_EXTRACTOR
SAP_SM_CONF_SEC
SAP_SM_EEM_CONF
SAP_SM_SOLUTION_ALL
SAP_SM_USER_ADMIN
SAP_SOL_PROJ_ADMIN_ALL
SAP_SMWORK_SYS_MON (Assigning workcenter) [Assign this role to solman_Admin to view System Monitoring tab in solman_workcenter T-Code]
Hope, this content would help most of the SCNians.
Regards,
Nilutpal.
SAP Solution Manager 7.1 offers several features including the document management based upon inbuilt knowledge warehouse.
Typically we create a project or solution with structure and therefore store all the documents corresponding to business processe mapped to this project or solution.
Slowly there is huge growth of each document versions in the database because solution manager maintains versions of all the documents stored centrally for a project.
for e.g. see the below screenshot for document attributes for a single document stored under Project Documentation tab in solar01/02
As we can notice here that Solution Manager maintains complete track of all the changes, we have done for a single document stored like Status change, keywords, other attributes.
To archive/delete the older version of documents we can use below reports.
First Report is SOLMAN_DOCU_VERSION_ARCHIVE which helps us to do the archiving to a different location. The document header data and attributes are kept in Solution Manager but entire content of older version will be archived.
Press execute button, provide project name and other parameters as per requirements. for e.g. I have provided document status as RELEASED which means all the documents with this status but of any documentation type will be archived.
Now if you want to test it just click on the Test Run, press execute button
We can notice here that 8 version of this document will be archived. Imagine if we have huge library yes it will save lot of space.
Execute as per requirement by removing the ticket form the Test Run on the previous screen. The older versions will be archived for all the documents
Again this is just a standard report and incase it is not meeting our requirement we can enhance it as per customer requirements.
We will see the next report in part 2.
Connecting ABAP\JAVA systems to Solution Manager can sometimes be challenging.
From not finding the Diagnostics Agent in the System Preparation phase (last step) or in the Agent Admin to all kinds of errors during the "Managed Systems Configuration" wizard.
Here are some "pre-requisites" that will save you some trouble:
If an error is received by running this command instead of information it is probably due to a malfunctioning Host Agent. Another good reason to re-install it.
I will try to keep this Blog Post up to date with further tips.
Enjoy 
Adi J.
