SAP Business Explorer (BEx) tools:
Most of SAP Netweaver BI users are working with SAP Busines Explorer (BEx) tools built into there SAP Netweaver BI System. But SAP Netweaver 2004s release have new additions to this toolset. Each tool will address a variety of reporting requirements.
SAP BEx Tools:
1) BEx Query Desinger -- The central tool used within the BEx Suite to design your BI queries. These queries can later be used in the BEx Analyzer, Web Application Designer, and Visual Composer as data providers. BEx Query Designer is available in a desktop-based Excel version and a version for Web-based query design.
You can find the SAP help document related to BEx Query Desinger.
2)BEx Analyzer --- A Microsoft Excel add-on reporting tool used for analysis. BEx queries can be embedded within Excel workbooks; both the OLAP capabilities of the SAP NetWeaver BI platform and the calculations and formulas of Excel are available for analyzing reports. A Web version of this tool is also available for online access to interactive functions in reports based on HTMLB iViews.
You can find the SAP help document related to BEx Analyzer.
3)BEx Web Application Designer (WAD) — A desktop application used for creating Web and analytic applications that render SAP NetWeaver BI information using tables, charts, and graphs.
You can find the SAP help document related to BEx Web Application Desinger.
4)BEx Report Designer — A desktop application used to create static or dynamic formatted reports. The reports can be viewed within a Web browser or generated as a PDF.
You can find the SAP help document related to BEx Report Designer.
J2EE Administration Tools (Config Tool, Visual Admin, NWA):
The tools.
Configuration tool (aka config tool)
- Generally used to make changes to VM (virtual memory) settings, and and remove server nodes and change UME (user management engine)
- Requires the Java database be started
- Is not password protected (uses a secure storefor authentication)
- Also leads to the configuration editor
Which by default is read only, but can be changed into read/write to make changes. The Java engine should be stopped (but of course, not the underlying database) before any changes are made.
Visual administrator
- Generally used to run administration tasks, such as look at log files, changing key store etc
- Requires the Java engine to be running
- Password protected
- Replaced by NWA for NW AS Java >= 7.1
- Can connect to multiple Java engines (one at a time!)
After connecting (and waiting for some time...)
The Visual Administrator can be deployed to a Windows desktop by taking the whole admin folder and copying it to the desktop and installing a JRE.
On Windows, the admin folder is at disk:\usr\sap\<SID>\JCnn\admin
NetWeaver Administrator (NWA)
- Browser based tool to manage Java engine, including starting and stopping
- Java engine must be running
- Password protected
- Runs as a servlet on the Java engine (http://portal:port/nwa)
MDM Tools:
SAP NetWeaver MDM consists of several software components. This category collects useful information about the MDM Clients (like Console, Data Manager and so on) and other generic MDM tools (like Enrichment Controller, Data Extractors, and so on) provided by SAP.
General Information
 Integrating SAP NetWeaver MDM with SAP BusinessObjects Data Services |
| MDM Data Manager |
| MDM Language Selector |
MDM CLIX
| Automatic Backup of MDM Repository (Using MDM CLIX in Windows OS) |
| Getting Started with MDM CLIX |
MDM Console
| Troubleshooting for MDM Repository Load |
MDM Data Manager
| Access Multiple Links in Web Tab |
| Converting Attribute Types in MDM |
| How to replace in MDM |
| Violation of Role Permissions with MDM Workflows |
MDM Enrichment Controller
| Enrichment Controller using Workflow |
| Four Different Workflows for Enrichment Controller Process |
MDM Extractors
| MDM Generic Extractor |
MDM Import Manager & Syndicator
| How to import Hierarchy in MDM |
| Import Manager Restricted User |
| Mapping of Qualified Tables against a Segment |
| Multiple Main Tables and Import Manager — Some things to know about the import and multiple main tables. |
MDM PI Adapter
| Differences in Integration of PI with MDM 5.5 and MDM 7.1 |
MDM Portal, Web Dynpro Components & Web Services
| BPM Use Cases - Streamlining creation of master data |
| Importing records from MDM BP Resultset iview to Excel |
MDM Publisher, Indexer & Image Manager
| Print Publisher |
MDM Servers (MDS, MDIS, MDSS)
| No content found for label(s) MDM_SERVERS. |
MDM UoM Manager
| No content found for label(s) MDM_UOM. |
BW Tools:
This article is mainly intended to provide the overview of how to use the Program: "/SSA/BWT" through which you can learn to utilize some useful BW Tools.The Program "/SSA/BWT" provides the following BW Tools:- Process Chain Analysis
- Detailed Request Analysis
- Aggregate Toolset
- Infoprovider BPPO Analysis
In this article I will cover how to use the following tools:- Process Chain Analysis
- Detailed Request Analysis
a) Process Chain Analysis:As the name itself suggests this tool is used to perform the Runtime analysis of the Process Chains. The analysis can be performed not only at Process Chain level but also at the Process Type level.Process Chain level analysis mainly serves the purpose of comparing the Runtimes of a chain for different days. For example: A Process Chain in your project daily takes 2 hours to get Completed but for the last 2 days the chain is taking 3 hours to get completed. Now you want to check the runtime of this chain over some past period and also want to know because of which process exactly this time difference is occurring. Then you can use this tool as the option which will provide the comparison of Runtimes of different Processes in that chain for different runs.Note: Other than providing the comparisons of Runtimes, this tool is also very helpful in monitoring the Process Chains in your box, can be related to the way tcode: RSPCM works, showing the status of the Process Chain (Red, Green or Yellow) and opening the Log of the Process Chain from there by clicking on it. Also compared to RSPCM this tool is much more effective and quick.Process Type level analysis mainly serves the purpose of knowing how regularly a particular Process Type in a Process Chain is failing or the runtime it takes to get Completed.How to use:To access this tool Goto SE38 à Type in "/SSA/BWT" as the Program name and click on execute. The list of all the tools that this Program contents are displayed. (List includes the above mentioned four tools)By default the option 'Process Chain Analysis' is selected. Now click on the execute button. Then you are displayed with the options through which you can select to perform analysis at Process Chain level or Process Type level. (Along with that, the Time Zones used to display the information is also displayed)Process Chain level:If you click on the button 'Process Chains' a window Pops up, here you need to provide the Chain-ID and/or the Log-ID and the Start Date/Time and the End Date/Time.Decide the parameters to enter as per your requirement, suppose your requirement is to check the runtime of a particular process chain for the past one week, then provide the technical name of that chain in the field Chain-ID and the start and end dates as per last one week and click on execute.Then the logs of the Process Chain for the selected dates are displayed along with the status (Red, Green or Yellow). The logs of the local chains (if any exist in the Process Chain selected) are also displayed (Much more additional information exist which is self explanatory). Now you can have a look at the Runtimes of different logs.Now if you want to compare the runtime of the processes in the Process Chain for different logs then select all the logs you want to compare by using the Control key and then click on the button 'Compare Runtimes'. Now you can see the runtimes of all the processes in the chain for all the logs and the difference in Runtimes between different logs is also displayed.Note:When entering the parameters if you do not provide any Chain-ID and Log-ID then the status (Red, Green or Yellow) of all the Process Chains running in the box is displayed. Now you can use this tool as an alternative of tcode: RSPCM. The Refresh button at the top helps you to refresh the status of the Process Chains. (Refresh rate is very faster when compared to the refresh rate of RSPCM). If you want to go to the Log view of any chain just click on the Log field of that chain.Also as in RSPSM you do not need to add the Process Chains. But if you want to use this tool for monitoring and you do not want to display all the chains running in the box, as this is a program you can create different variants with different Chains included.Process Type level:And from the Process Chain Runtime Analysis screen if you click on the button 'Process types' a window pops up prompting you to enter the values which include Start/End Date/Time, Process Types, Process Variants and select the status(Red, Green or Yellow) of the Process Types to be displayed.Now consider you want to check a load in Process Chain for the past one week for its status and runtime, then you select loading as the Process Types and into the field Process Variants give the variant of the loading process from the chain, select all the status to be displayed and enter the dates for the past one week and execute. Now you can find the runtime and the status of that loading process and also by clicking on the Log ID which is also displayed you can go to the Log-ID of the chain in which the selected Process type exists.b) Detailed Request Analysis:As the name itself suggests this tool is used to perform the detailed analysis of an individual request.Generally in RSMO you find all the information of the request in the Header, Status and Details tabs. But if you think that the loads for a particular Infopackage is taking more time to get Completed and you want to analyse at which level exactly the load is taking time to get processed whether at transfer rules processing or update rules processing or something else then from RSMO the only information available is the total processing time of the request, in such cases you can use this tool.How to use:To access this tool Goto SE38 à Type in "/SSA/BWT" as the Program name and click on execute. The list of all the tools that this Program contents are displayed. (List includes the above mentioned four tools). Select the second option 'Detailed Request Analysis' amd click on execute. In the following screen provide the Request Number to be analysed and click on execute.Then you have all the information displayed at data package level. Along with the information available in the Header tab of RSMO, you have the following important information:- Avg. PSA Read DP runtime
- Avg. PSA Write DP runtime
- Avg. Transfer Rule DP runtime
- Avg. Update Rule DP runtime
- Avg. Insert DP runtime
- Min. DP runtime
- Avg. DP runtime
- Med. DP runtime
- Max. DP runtime
By analyzing the values of above parameters you can decide whether you need to improve your update rules, transfer rules or change the data package settings.Hope you all have found this article informative.
JOB MONITOR WIDGET:
This widget is especially made for administrators and checks the status of the most critical jobs (transaction SM37) and warns as soon as a problem occurs
Please find the below link to download it Note : you need to have SDN user id to download it
BI Data Widget - Weblog Series & Pre-requisites
This article is mainly intended to provide the overview of how to use the Program: "/SSA/BWT" through which you can learn to utilize some useful BW Tools.
The Program "/SSA/BWT" provides the following BW Tools:
- Process Chain Analysis
- Detailed Request Analysis
- Aggregate Toolset
- Infoprovider BPPO Analysis
In this article I will cover how to use the following tools:
- Process Chain Analysis
- Detailed Request Analysis
a) Process Chain Analysis:
As the name itself suggests this tool is used to perform the Runtime analysis of the Process Chains. The analysis can be performed not only at Process Chain level but also at the Process Type level.
Process Chain level analysis mainly serves the purpose of comparing the Runtimes of a chain for different days. For example: A Process Chain in your project daily takes 2 hours to get Completed but for the last 2 days the chain is taking 3 hours to get completed. Now you want to check the runtime of this chain over some past period and also want to know because of which process exactly this time difference is occurring. Then you can use this tool as the option which will provide the comparison of Runtimes of different Processes in that chain for different runs.
Note: Other than providing the comparisons of Runtimes, this tool is also very helpful in monitoring the Process Chains in your box, can be related to the way tcode: RSPCM works, showing the status of the Process Chain (Red, Green or Yellow) and opening the Log of the Process Chain from there by clicking on it. Also compared to RSPCM this tool is much more effective and quick.
Process Type level analysis mainly serves the purpose of knowing how regularly a particular Process Type in a Process Chain is failing or the runtime it takes to get Completed.
How to use:
To access this tool Goto SE38 à Type in "/SSA/BWT" as the Program name and click on execute. The list of all the tools that this Program contents are displayed. (List includes the above mentioned four tools)
By default the option 'Process Chain Analysis' is selected. Now click on the execute button. Then you are displayed with the options through which you can select to perform analysis at Process Chain level or Process Type level. (Along with that, the Time Zones used to display the information is also displayed)
Process Chain level:
If you click on the button 'Process Chains' a window Pops up, here you need to provide the Chain-ID and/or the Log-ID and the Start Date/Time and the End Date/Time.
Decide the parameters to enter as per your requirement, suppose your requirement is to check the runtime of a particular process chain for the past one week, then provide the technical name of that chain in the field Chain-ID and the start and end dates as per last one week and click on execute.
Then the logs of the Process Chain for the selected dates are displayed along with the status (Red, Green or Yellow). The logs of the local chains (if any exist in the Process Chain selected) are also displayed (Much more additional information exist which is self explanatory). Now you can have a look at the Runtimes of different logs.
Now if you want to compare the runtime of the processes in the Process Chain for different logs then select all the logs you want to compare by using the Control key and then click on the button 'Compare Runtimes'. Now you can see the runtimes of all the processes in the chain for all the logs and the difference in Runtimes between different logs is also displayed.
Note:
When entering the parameters if you do not provide any Chain-ID and Log-ID then the status (Red, Green or Yellow) of all the Process Chains running in the box is displayed. Now you can use this tool as an alternative of tcode: RSPCM. The Refresh button at the top helps you to refresh the status of the Process Chains. (Refresh rate is very faster when compared to the refresh rate of RSPCM). If you want to go to the Log view of any chain just click on the Log field of that chain.
Also as in RSPSM you do not need to add the Process Chains. But if you want to use this tool for monitoring and you do not want to display all the chains running in the box, as this is a program you can create different variants with different Chains included.
Process Type level:
And from the Process Chain Runtime Analysis screen if you click on the button 'Process types' a window pops up prompting you to enter the values which include Start/End Date/Time, Process Types, Process Variants and select the status(Red, Green or Yellow) of the Process Types to be displayed.
Now consider you want to check a load in Process Chain for the past one week for its status and runtime, then you select loading as the Process Types and into the field Process Variants give the variant of the loading process from the chain, select all the status to be displayed and enter the dates for the past one week and execute. Now you can find the runtime and the status of that loading process and also by clicking on the Log ID which is also displayed you can go to the Log-ID of the chain in which the selected Process type exists.
b) Detailed Request Analysis:
As the name itself suggests this tool is used to perform the detailed analysis of an individual request.
Generally in RSMO you find all the information of the request in the Header, Status and Details tabs. But if you think that the loads for a particular Infopackage is taking more time to get Completed and you want to analyse at which level exactly the load is taking time to get processed whether at transfer rules processing or update rules processing or something else then from RSMO the only information available is the total processing time of the request, in such cases you can use this tool.
How to use:
To access this tool Goto SE38 à Type in "/SSA/BWT" as the Program name and click on execute. The list of all the tools that this Program contents are displayed. (List includes the above mentioned four tools). Select the second option 'Detailed Request Analysis' amd click on execute. In the following screen provide the Request Number to be analysed and click on execute.
Then you have all the information displayed at data package level. Along with the information available in the Header tab of RSMO, you have the following important information:
- Avg. PSA Read DP runtime
- Avg. PSA Write DP runtime
- Avg. Transfer Rule DP runtime
- Avg. Update Rule DP runtime
- Avg. Insert DP runtime
- Min. DP runtime
- Avg. DP runtime
- Med. DP runtime
- Max. DP runtime
By analyzing the values of above parameters you can decide whether you need to improve your update rules, transfer rules or change the data package settings.
Hope you all have found this article informative.
Introduction
Yahoo Widgets are great applications for allowing users to interact with systems or applications directly on their desktop. Within the SAP space, there are casual users of BI that may want metrics on a daily basis. Many customers run their businesses off one or two key reports, such as a daily sales report, or a simplified financial statement. Therefore, this guide provides a way to consume BI Data within Yahoo Widgets.
Screenshot of Widget Version 1.0:
Screenshot of Widget Version 2.02:
Screenshot of Widget Version 3.x (Coming Soon!!!): 
"
"Scenario
As with any solution, the first thing you need to do is identify when to use the solution. The Yahoo Widgets solution is great for targeting your casual user. For example, many users have similar types of desktop applications to view their stock ticker every morning. This information is peripheral. You glance at it in the morning, but don’t really do anything or follow up unless your stock value changes drastically (either positive or negative).
Proposing that key enterprise metrics be treated in a similar manner. For example, if a company uses daily sales numbers to measure performance, this metric should be pervasive within the organization. Users should see their metric peripherally every day when they log onto their machine, and should only follow up if they see unexpected numbers.
The Yahoo Widget Application allows you to present this to the user in a very nice way. They won’t even know they are interacting with an SAP application!
MICRO -- APPS :
Underscoring the power of collaboration and innovation within the SAP ecosystem, SAP AG (NYSE: SAP) announced details of an innovative customer deployment of “micro-apps” that uses Google Gadgets™ technology to bring the business value of SAP® software to even more users. Developed by SAP partner SEAL Consulting Inc., the enterprise desktop notification (EDN) micro-app is significantly optimizing processes and improving customer service at Archean Group, a large Indian conglomerate with various businesses from chemicals and mining to renewable energy, shipping and shipbuilding. The announcement was made at the CeBIT trade fair, being held in Hanover , Germany , March 2-6.
Micro-apps are small applications, or gadgets, delivered into browsers or mobile-devices that extend the functionality of enterprise applications to broader groups of users, specific to their roles and requirements. Micro-apps are small applications, or gadgets, delivered into browsers or mobile-devices that extend the functionality of enterprise applications to broader groups of users, specific to their roles and requirements. SEAL Consulting’s award-winning EDN micro-app extends the wealth of information and business events processed by SAP applications to non-SAP users via Google Gadgets technology. Users simply deploy a gadget front-end on the desktops to receive direct and non-intrusive workflow and alert notifications. For SEAL Consulting customer Archean Group, the notifications deliver business benefits including:- Greater efficiency, responsiveness and customer satisfaction – The new automated solution handles shipping order status and ETA inquiries with no manual intervention. Previously, these had to be fulfilled via a five-step series of manual data searches and phone calls from customer, to customer service representative, to operations manager and back.
- Personalized visibility to stakeholders improved – Customizable, automated alerts deliver relevant information to SAP and non-SAP users, paving a mindset change from “information access” to “information delivery.”
- Quick deployment, rapid ROI, cost-effectiveness – The solution was implemented in four weeks with minimal end-user training and requiring no additional hardware or software.
No comments:
Post a Comment