SAP NetWeaver 2004s Maintenance and Migration of Web Applications in Microsoft Office

Making DataMatrix in Microsoft Office SAP NetWeaver 2004s Maintenance and Migration of Web Applications

SAP NetWeaver 2004s Maintenance and Migration of Web Applications
Making Data Matrix 2d Barcode In C#
Using Barcode creator for .NET framework Control to generate, create Data Matrix 2d barcode image in .NET applications.
DataMatrix Maker In .NET
Using Barcode encoder for ASP.NET Control to generate, create Data Matrix image in ASP.NET applications.
Web Application Designer 3x migrate open save
Data Matrix 2d Barcode Creator In VS .NET
Using Barcode creation for .NET framework Control to generate, create ECC200 image in Visual Studio .NET applications.
Draw Data Matrix ECC200 In VB.NET
Using Barcode creator for VS .NET Control to generate, create Data Matrix ECC200 image in .NET framework applications.
Web Application Designer 2004s save open (Stored with new internal name and version to a new database table)
Bar Code Printer In Java
Using Barcode creation for Android Control to generate, create bar code image in Android applications.
Draw EAN13 In Objective-C
Using Barcode creation for iPhone Control to generate, create GS1 - 13 image in iPhone applications.
Web Templates 3x
Reading DataMatrix In Java
Using Barcode decoder for Java Control to read, scan read, scan image in Java applications.
Code-128 Creator In None
Using Barcode generation for Microsoft Word Control to generate, create Code 128 Code Set B image in Word applications.
Web Templates 2004s
Code 128C Scanner In C#
Using Barcode decoder for .NET framework Control to read, scan read, scan image in VS .NET applications.
ANSI/AIM Code 39 Generator In .NET
Using Barcode encoder for ASP.NET Control to generate, create Code 3/9 image in ASP.NET applications.
Copyright by SAP AG
Code-39 Recognizer In Visual C#.NET
Using Barcode scanner for .NET framework Control to read, scan read, scan image in Visual Studio .NET applications.
Encode Barcode In Java
Using Barcode generation for BIRT reports Control to generate, create barcode image in BIRT applications.
FIGURE 8-3
Barcode Printer In Java
Using Barcode creator for Android Control to generate, create bar code image in Android applications.
GS1 - 13 Reader In VS .NET
Using Barcode scanner for Visual Studio .NET Control to read, scan read, scan image in VS .NET applications.
Options for migration with the BEx Web Application Designer
ANSI/AIM Code 128 Scanner In .NET
Using Barcode reader for Visual Studio .NET Control to read, scan read, scan image in .NET applications.
Print 1D In VS .NET
Using Barcode drawer for ASP.NET Control to generate, create 1D image in ASP.NET applications.
8:
European Article Number 13 Encoder In Java
Using Barcode creation for Java Control to generate, create GTIN - 13 image in Java applications.
Generating Code 39 In Java
Using Barcode printer for BIRT Control to generate, create Code 39 Extended image in BIRT applications.
M i g r a t i n g 3 x t o 7 0 B E x We b R e p o r t s a n d t h e WA D
Make GS1 128 In Java
Using Barcode generator for Java Control to generate, create GS1-128 image in Java applications.
Code 128 Code Set B Maker In C#
Using Barcode creator for VS .NET Control to generate, create Code 128 image in .NET framework applications.
The migration process for BEx WAD templates is very different from that for the BEx queries You will use the migration tool in the NW 70 BEx WAD This is an easy and quick approach to migrating existing WAD templates Unfortunately, the migration tool will not convert some elements, such as JavaScript used to create tab pages in the older version or the BEx Web Designer API tables These elements must be rebuilt using the standard delivered Web items in the BI 70 WAD With this in mind, it may be an option in some cases, to rebuild the Web templates directly rather than rely on the migration tool This probably is not going to be as intense a task as you might think, because many of the different objects that we had to build from scratch in 3x are now standard delivered Web items in 70, such as the Tab Pages Web item and the command wizard option in BI 70
Approach to Migration of Web-Based Reports
There are a number of different aspects that we need to understand around this process and the success of a migration is not only due to the system process but also relies on the business and political environment at each company You will have to do a complete duediligence process initially so that you will not fall into any of the potholes embedded in the business culture This due diligence requires a round or two of meetings with all the different groups that will be affected by the migration You should very carefully pull together a hierarchical list of the critical issues and challenges that you might encounter during a migration process The migration process can be overwhelming without a list of items that you can check off as you complete them A good first step in the migration process is to clean up business users Favorites folders Business users tend to assign frequently used reports and other objects to their Favorites folders but fail to get them changed over to standard reports The issue is that nothing in the Favorites folder is migrated So, you need to find out which of these reports and objects lurking in the Favorites folders of each department, group, and team need to be moved over to a folder within a specific role so that they can be migrated You also need to come up with a strategy for moving them, including the variants associated with them You ll need to explain to business users which reports are candidates for being moved For example, if a business user has 75 reports in their Favorites folder, you need to instruct them to identify and list the reports that are essential to performing their job Then, you need to follow the company process for moving them to the appropriate role and folder Getting business users to give up less than all their favorites is not as easy as it may seem, but with a little nudging and some time limits (always put a time limit on this task), everyone will come up with a list Great, you have completed your first task in the migration process Now, you need to decide on which approach to use to do the migration Following are some questions to consider:
Go with a big bang approach and migrate everything in one session, or migrate the
reports in phases
Migrate the reports of each department based on need or requirements, or start with
the group that has the smallest list of reports and go from top to bottom via that approach numerous custom APIs or lots of broadcasting, or do this group last
Start with the group that needs the most help with VBA or customized reports with
Applied SAP BI 70 Web Reports
Whichever approach to migration you choose, make sure you establish some justification for it so that you have answers ready when users begin to question your timing What I try to do is understand the client s needs and timeline and then look at several aspects that would make or break the client s project, and then I make the choice based on those criteria There is not a strict rule for which approach to take, so it is more of an art than a science You need to make sure that you minimize complications in whichever approach you take; in other words, make the process as easy and as straightforward as possible Avoid a migration where 50 percent of the reports for a department are migrated and the other 50 percent are still using the 3x toolset for reporting The user is bound to get frustrated and use the wrong toolset, creating even more issues Take a step-by-step approach so that everyone can understand and feel comfortable with the migration process Importantly, you must inform business users about the migration process beforehand Conduct learning sessions, both formal and informal, where you demonstrate the functionality of the system so that the business users are comfortable with the change Demonstrate the newer functions of BI 70 reporting, such as the additional flexibility of the Information Broadcaster, the use of calculations within the frontend of the Web report, or the numerous new functions in the Web template and what s behind each of the buttons on the screen exceptions, conditions, all the key figure attributes, and so forth In my experience, the more I demonstrate functionality and talk to the business users, the lower the total number of defects I have to deal with and the more directly I can work with business users to resolve problems If you have 100 business users who are migrating reports that they ve been working with for years, you really need to train them on the new reporting functions thoroughly This will definitely reduce the complications when going live and eliminate much of the lower-level complaints about the new reporting tools You will definitely reduce the number of comments like this reporting toolset doesn t work the same as my former frontend or this reporting component doesn t do everything that the other frontend did If you demonstrate the functionality that has changed, you can avoid issues down the road For example, there is a significant change to the process of inserting a query into a workbook The 3x version has a command on the context menu Insert Query In the 70 version, that option is gone and you have to follow specific steps to insert a query into a workbook The reason for this is the use of the two different support stacks ABAP and Java In this case, demonstrate the multiple steps required Following are some of the other changes you might consider demonstrating:
Copyright © OnBarcode.com . All rights reserved.