1 2 3 Previous Next

prakash.darji

31 Posts

Hey SDN and BPX folks,

I just thought I'd put a quick note out to say we have a CPM page on the BPX community area:

 This is the direct link:

You can get there by going to:
http://www.sdn.sap.com/irj/sdn/bpx-cpm 

BPX Community
 -> Business Process in Practice
   -> Corporate Performance Management

 This area includes information about the SAP CPM Suite as well as the SEM components including:

  • SAP Strategy Management (formerly Pilot)
  • SAP Business Planning and Consolidations (formlerly Outlooksoft)
  • SAP Business Profitability Management (Acorn Partnership)
  • SAP SEM-BCS
  • SAP SEM-CPM (Balanced Scorecard and Management Cockpit

Also, be sure to check out the e-learning section on the CPM page for all the cool demos of these products.

Cheers,
Prakash

Hey BPX and SDN Folks!

We've launched the new CPM Forum for any questions the community may have for the new SAP CPM Suite! This includes SAP BPC (formerly Outlooksoft), SAP SSM (formerly Pilot), and Acorn (SAP's reseller agreement).

Additionally, people have been asking about some roadmap and detailed questions around what to post where. Therefore, to get the most visibility to your questions with the right groups at SAP, I would post questions to the following forums:

SAP Solution -> ERP Financials Forum
SAP ERP Financials

Use this forum for the following product lines:

  • SAP Financial Components

Business Process Expert - Corporate Performance Management Forum - New SAP CPM components

NEW! - Enterprise Performance Management (SAP EPM)

Use this forum for the following products:

  • SAP BPC (Outlooksoft)
  • SAP SSM (Pilot)
  • SAP BPM (Acorn)
  • SEM Miscellaneous
  • Balanced Scorecard
  • Management Cockpit
  • Value Driver Trees
  • Roadmap, Etc...

SAP Solutions - SEM-BCS Forum - The SEM-BCS product line 

  • SEM-BCS
  • NEW! - Business Consolidation (SEM-BCS)

     

    I've recently started working with these topics, and I plan on encouraging our developers from the Outlooksoft and Pilot acquisitions to actively monitor this forum. This product line and the expertise around these products are currently different from the SAP NetWeaver Business Planning and ERP Financials forums, so we wanted to make sure we can address these questions directly and share knowledge in this area. These companies had their own customer bases as well which can contribute to the wealth of knowledge on these software components and share their experience with SAP customers. Additionally, the old SEM-CPM (Balanced Scorecard/Management Cockpit) really never had a home on SDN, so I'd like to have those questions posted here as they are going to be tightly related to the roadmap questions between these SEM-CPM products and the newer SAP Strategy Management products.

    Due to feedback from SDN community members about SEM-BCS not having a specific home a new forum has been created for BCS as well.


    Lately, there has has been a lot of emails coming to my and my colleagues inbox around these new CPM topics, so therefore I thought a forum for this would be great.

    Business Intelligence - Business Planning Forum
    Business Planning



    Use this forum for the following products:

    • BI-IP
    • BW-BPS
    • SEM-BPS

    These topics refer to our current planning implementations of BI-IP and BPS. Any technical implementation questions about these topics should go in this forum as the experts in this area will be checking this forum.

    I look forward to working with the SDN community. If you post to the forum, I use this as feedback for what we should put into the product, so if you have any comments or feedback, please post it on the new CPM forum!

    h5. 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:

    image

     

    Screenshot of Widget Version 2.02:

    image

     

     

    Screenshot of Widget Version 3.x (Coming Soon!!!):

     

    !https://weblogs.sdn.sap.com/weblogs/images/28269/widg3x.jpg|height=390|alt=image|width=578|src=https://weblogs.sdn.sap.com/weblogs/images/28269/widg3x.jpg|border=0!"

     

    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).

     

    I’m 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! h5. Version History and Limitations

     

     

    Version 1.1:

     

      • Does not support structures in both rows and columns

      • Does not support structures and characteristics in both rows and columns

      • Does not support hierarchies

      • Does not support queries with mandatory variables

     

    Version 1.2:

     

    0.1. Added support for all query datasets with 2 structures and n characteristics

    0.2. Added support for structures in both rows and columns

    0.3. Added support for structures and characteristics in both rows and columns

    0.4. Does not support hierarchies

    0.5. Does not support queries with mandatory variables

     

    Version 1.3:

     

    0.1. Widget now refreshes when preferences are changed

     

    Version 2.01:

     

    0.1. Sap blue skin

    0.2. Ability to select demo data set from preferences

    0.3. Removed Change Background Color (not needed in blue skin)

     

    Version 2.02:

     

    0.1. Adjusted timer 

    0.2. Added 5 min option

     

    Version 2.04:

     

    0.1. Added Logon Language Support

    0.2. Added Support for 0CALDAY (ExtVal display)

     

    Version 2.05:

     

    0.1. Added Support for Hierarchies (no expand and collapse)

     

    Version 2.06:

     

    0.1. Added Expand/Collapse icons for Hierachies (not dynamic)

     

    Version 2.07:

     

    0.1. Added "no applicable data found" support

    0.2. Fixed the last updated display to support real time cubes

    0.3. User defined number for the refresh interval instead of pull down

    0.4. Added >1 header row query support

    0.5. Added color coding based on BI exceptions

    0.6. Added customizable height

    0.7. Added display of key if description is not available

    0.8. Added traffic light support (you need to use IOBJ 0TCTRQCSTA)

    0.9. Added text variable support (not dynamic i.e. fixed in widget code)

    0.10. Added secure check box that removes copy of the XML on the C: drive if any

    0.11. Removed password from PDF, Excel and query jumps (for security)

     

    Version 2.08:

     

    0.1. Added themes to prefrerence

    0.2. Added report navigation buttons, but did not enable it

    0.3. Added button and second window for query informtion, and partially enabled it, still need to source info

    0.4. Added a distraction image, but did not enable it

     

    Version 2.09:

     

    0.1. Added theme preference

    0.2. Changed group to CPM

    0.3. added last refresh date to query properties

    0.4. re-aligned buttons

     

    Version 2.10:</p><ul><li>Changed the tooltip on the information button</li><li>Fixed the query description when "no applicable data found" so that if it ran once, the desc will remain</li><li>Set the default theme to blue (in the preferences section)</li><li>Adjusted technical name display in cells (ChavlExt first then Chavl)</li><li>Display SAP logo instead of update icon in docking</li><li>Added multi language support to QueryInfo splash screen</li><li>Added multi language support to "Last refreshed date" </li><li>Remove the <name> tag in widget.xml to allow multiple widgets to run </li></ul><p>Version 2.6:

     

    0.1. Updated Version Number to 2.6 due to confusion on SDN

    0.2. Added underlying framework for expand/collapse hierarchy (dynamic hierarchies)

       - This is not complete yet...

     

    Version 2.70:

     

    0.1. Updated the Expand/Collapse Hierarchy WebApi Commands to include dynamically building parameters

    0.2. Added sample dataset for 1 char and 1 hier in rows

    0.3. Hid the preferences for dynamic hierarchies as this isn't complete

     

    Version 2.71:

     

    0.1. Added Widget Version to the Info Screen

     

    Version 2.73:

     

    0.1. Ported the web service to call BAPI with dynamic webservice

    0.2. Hierarchy icons were broken in this version

    0.3. Added "View" Support

     

    Version 2.74:

     

    0.1. Updated Connectivity

    0.2. Added eror handling

    0.3. Hierarchy icons were broken in this version

     

    *Version 2.75: </p><ul><li>Fixed Hierarchy Icons</li><li>Added more error handling</li><li>Added support for foreigh character sets (Japanese & the such)</li><li>Fixed Launching View URL to Web, PDF, and Excel</li></ul><p>Version 2.76:</p><ul><li>Upgraded to Yahoo Widget Engine 4.5</li><li>Bug in Deleting hierarchy icons when changing queries</li><li>Fixed bug in Preference Groups not showing up on subsequent executions</li></ul><p>Version 2.77:</p><ul><li>Fixed bug in Deleting hierarchy icons when changing queries</li></ul><p>Version 2.78:</p><ul><li>Enhanced Error Handling Framework to check if the RRW3_GET_QUERY_VIEW_DATA function is RFC enabled. It should be, but I added this check due to a rare customer issue where they did a core-mod</li><li>Published Widget in compressed format to reduce the size</li></ul><p>Version 2.79:</p><ul><li>Updated default widget width based on customer issue</li><li>Updated widget to handle secure mode even is SSO is not configured (using logon popup)</li><li>Updated initial widget view to hide scrollbar and info button until widget is rendered </li></ul><p>Version 2.80:</p><ul><li>Updated widget minumum column size for small datasets</li><li>Updated widget to include additional demo data</li></ul><p>_Latest Download (2.80) Available Here:

    _*

    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e01bb234-faf7-2a10-e9a8-aa41def64ffd

     

    Pre-requisites

    The latest versions of the BI Data Widget do not require the queryviewdata web service to be activated as the earlier versions did.

     

    Step 1

    Go to SICF and activate this web service: “/sap/bc/soap/rfc” 

    </p><p>Step 2

    Go to http://widgets.yahoo.com/download/  (http://widgets.yahoo.com/download/) and download and install the latest version of Yahoo’s Widget Engine. <br />!https://weblogs.sdn.sap.com/weblogs/images/28269/ywidg1.jpg|height=396|alt=image|width=256|src=https://weblogs.sdn.sap.com/weblogs/images/28269/ywidg1.jpg|border=0!</p><p>Optional:*

     

    Here is an example of how to pass parameters for filter values using WEB API commands. We are passing the FILTER_IOBJNM=0D_CHANNEL and FILTER_VALUE=3.

    image

     Here is an example of how to pass parameters for variable values using WEB API commands. In this case, we are using a selection option variable. We are passing the following parameters:

    VAR_NAME_1=DISTGOP

    VAR_OPERATOR_1=EQ

    VAR_VALUE_LOW_EXT_1=3

    VAR_VALUE_HIGH_EXT_1=5

     

    !https://weblogs.sdn.sap.com/weblogs/images/28269/qvw18.JPG|height=326|alt=image|width=594|src=https://weblogs.sdn.sap.com/weblogs/images/28269/qvw18.JPG|border=0!</body>

    This blog has been replaced with a newer version:

    BI Data Widget - Weblog Series & Pre-requisites

    This blog is replaced with a newer version located here:

    BI Data Widget - Weblog Series & Pre-requisites

    This blog has been replaced by a newer blog. See this link:

    BI Data Widget - Weblog Series & Pre-requisites

    Introduction
    Lately, I've had a few people ask about choosing multiple values for filtering within Visual Composer. This blog discusses the options for this.

     

    The Scenario
    There is no way to directly choose multiple values from a form box as the form element only stores a singular record per form field. Therefore, the focus of this blog discusses potential workarounds.

     

    The Options
    • Use Value Help Wizard - By far, the easiest option is to use the value help wizard. This will generate a popup iView to choose your values as displayed below. To build this, just right click on a field in your form, and choose the value help wizard option.

      image
    • Use Table Element - In this case, you can use a multiselect table element instead of a form as input for your data service. In this example, I'm going to base it off a BI Query. To build this, you would follow these steps:
      1. Insert InfoObject Dataservice into your model.
      2. Connect output of infoobject dataservice to a table.
      3. Specify the selection mode of the table as "Multiple".
      4. Connect the output of the table to the input of your BI Query Dataservice.
      5. Map the output of the table field to the input of your BI Dataservice.
      6. Create an output table from your BI Query to display your results.

      See the example below for selecting distribution channels. You can hold down the CTRL key to select multiple values. You have the option to put this table in a layer or a popup for preserving screen real-estate if need be.
      image
    • Use BI elements - Visual Composer doesn't natively allow you to multiselect values in a dropdown within a form. To do this, you have to use another UI Elements. This how-to guide shows how to do it in VC: http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5a40f2f7-0c01-0010-d69f-c6317c5165cd. In this scenario, you can get an output such as displayed below:
      image

     

    Summary
    These are the options as of SPS9. Hopefully you find this useful.

    Introduction
    In part 1 of this blog series, I presented the destination and tools matrix for SAP NetWeaver 2004s BI. This showed different tools and destinations for publishing. It also presented the different user types for publishing. I recently did a webinar on this topic and I've attached the slide deck to this blog. People were asking about TCO and full publishing strategy options as well as controlling presentation layer, so this is the focus of part 2 of this weblog series.

     

    Presentation Layer
    Stylesheets & Portal Themes

    • Look and feel is controlled completely by StyleSheets for Web applications
    • StyleSheets are available for manual editing and enhancement in the Theme Folders in the Portal File System
    • StyleSheets can be updated using the Portal Theme Editor
    • StyleSheets control more than font and color. Images, tab pages, etc., can all be controlled from within StyleSheets
    • StyleSheets for the BEx Web Analyzer are specified globally. Users can personalize a different portal theme for different look and feel
    • Rules can be defined for Portal Themes to assign themes to user groups or roles
    • Themes set in Consumer Portal take precedent over themes in the Producer Portal.
    • All User Interface, Theme Management, Portal Desktops, and Portal Desktop Rules should be managed in the Consumer Portal.
    • KM Navigation Presentation should be set for whatever KM repository is being utilized (either Producer or Consumer).


    • StyleSheet Scoping (SAP NetWeaver 2004s)
    • Format is defined by the Portal Theme StyleSheet StyleSheets in the Web application override the Portal StyleSheet
    • Individual "style" blocks in the BEx Web Application Designer override the stylesheets from the Portal and from the Web application


    • StyleSheet Scoping (SAP BW 3.x)
    • StyleSheet is defined in the BEx Web Application Designer
    • Portal StyleSheet overrides the stylesheet in the web application if the application is deployed on the SAP NetWeaver Portal
    • Specific "style" elements in the Web application override the global Portal StyleSheet


    • Presentation Layer in KM
    • 1. Navigate to the &#147;BEx Portfolio&#148; and click on the icon next to &#147;Public Documents&#148; and choose &#147;Details&#148;
    • 2. Go to &#147;Settings -> Presentation&#148;
    • 3. Choose &#147;Select Profile&#148;
    • 4. Choose a layout format and select &#147;OK&#148; and save your settings.


    • Visual Composer Styles
      There are plans to include the control of Visual Composer Styles within the Portal Theme Editor as of SPS10. Prior to this, you can update the styles manually in the filesystem as mentioned in OSS Note 959996.

      PDF Printing Styles
      PDF Printing does not allow you to specify your own custom portal themes. There are two themes available (SAP Standard &#150; Color) and (Black & White). You can customize a print template to specify which web items. This allows you to control look and feel and information being printed, but not colors and styles.

      BW 3.x query display
      Within the SAP NetWeaver 2004s BEx Query Designer, you can change the view to the SAP BW 3.x view while maintaining the new functionality. This may ease in transition for people who are accustomed to the old view. See attached powerpoint for details.

     

    End User Strategies
    Publishing Strategies within BW 3.x

    Within BW 3.x, this was the typical publishing strategy for workbooks:
    • Workbooks are accessed through BEx Browser or through the BEx Analyzer Directly
    • Most customers were not publishing workbooks to the NetWeaver Portal

    • Within BW 3.x, this was the typical publishing strategy for queries and web templates:
    • Most customers were using the Role Menu Web Item to display queries and web templates through the NetWeaver Portal
    • In some cases, customers were using portal roles and worksets for web template access and were only accessing adhoc queries through the Web Analyzer or BEx Analyzer


    • Option 1 - Publishing Strategy within SAP NetWeaver 2004s BI

      Based on Rolling out the New SAP NetWeaver 2004s BI Frontend Tools:
    • Replace BW 3.x Query Designer and BW 3.x BEx Analyzer with SAP NetWeaver 2004s Query Designer and BEx Analyzer.
    • Don&#146;t coexist these tools for end users

    • BEx Workbooks
    • To launch the BEx Analyzer, users can either go to their local PC and launch the BEx Analyzer or they can launch this from the portal via the SAP Transaction iView for BEx as outlined in the online help here: BEx Analyzer as iView. To launch this generically, you can use the "WBID=" as the application parameter but leave out the workbook id.
    • All queries or workbooks are then opened from the BEx Analyzer using the open dialog.
    • BEx Browser isn&#146;t used anymore

    • Queries
    • As Queries are created, they are saved to BI Roles or BI Favorites
    • All queries are accessed through the Web Analyzer using the &#147;New Analysis&#148; button
    • Web Analyses built with Web Analyzer are stored in KM and accessed through Web Analyzer using the &#147;Open&#148; button

    • End User Access
    • All End Users will enter through a Portal Role. From here, they can choose BEx Analyzer, Web Analyzer, Web Templates, or Formatted Reports
    • From the Web Analyzer, they can access any broadcasted or saved reports from KM or they can access BI Queries, BI Query Views, or BI InfoProviders
    • Users will only have 1 access point: Portal Role


    • Option 2 - Publishing Strategy within SAP NetWeaver 2004s BI

      Based on Rolling out the New SAP NetWeaver 2004s BI Frontend Tools:
    • Replace BW 3.x Query Designer and BW 3.x BEx Analyzer with SAP NetWeaver 2004s Query Designer and BEx Analyzer.
    • Don&#146;t coexist these tools for end users

    • BEx Workbooks
    • To launch the BEx Analyzer, users can either go to their local PC and launch the BEx Analyzer or they can launch this from the portal via the SAP Transaction iView for BEx as outlined in the online help here: BEx Analyzer as iView. To launch this generically, you can use the "WBID=" as the application parameter but leave out the workbook id.
    • All queries or workbooks are then opened from the BEx Analyzer using the open dialog.
    • BEx Browser isn&#146;t used anymore

    • Queries
    • As Queries are created, they are saved to BI Roles or BI Favorites
    • All queries are accessed through the Web Analyzer using the &#147;New Analysis&#148; button
    • Web Analyses built with Web Analyzer are stored in KM and accessed through Web Analyzer using the &#147;Open&#148; button

    • Web Templates and Formatted Reports
    • Web Templates and Formatted Reports are Broadcast to KM and stored there as documents
    • These reports are accessed through My Portfolo/BEx Portfolio in the Business Intelligence Role

    • End User Access
    • All End Users will enter through the Business Intelligence Portal Role. From here, they can choose Web Analyzer, My Portfolio, or BEx Portfolio
    • From the Web Analyzer, they can access any broadcasted or saved reports from KM or they can access BI Queries, BI Query Views, or BI InfoProviders
    • Users will use My Portfolio/BEx Portfolio to get Web Template, Formatted Reports, or Web Analyses
    • Users will only have 1 access point: Business Intelligence Portal Role with added iView for BEx Analyzer


    • Option 3 - Publishing Strategy within SAP NetWeaver 2004s BI

      Based on Rolling out the New SAP NetWeaver 2004s BI Frontend Tools:
    • Replace BW 3.x Query Designer and BW 3.x BEx Analyzer with SAP NetWeaver 2004s Query Designer and BEx Analyzer.
    • Don&#146;t coexist these tools for end users

    • BEx Workbooks
    • All Workbooks are published to the PCD as iViews manually and added to Worksets or Roles
    • Initially, SAP Role Upload can be used to migrate current workbooks to Portal Roles
    • BEx Browser isn&#146;t used anymore

    • Queries
    • As Queries are created, they are published to the PCD and added to Roles and Worksets manually
    • Web Analyses built with Web Analyzer are stored in KM and accessed through Web Analyzer or KM Navigation iViews

    • Web Templates and Formatted Reports
    • Web Templates and Formatted Reports are published to the PCD and added to Role or Worksets

    • End User Accesses
    • Users will be assigned to Groups which have Roles in them
    • Therefore, all users will see a tab in the portal navigation for their reports
    • KM Navigation iView will be used to link KM Folder with Portal Role per Application Area
    • Users will only have 1 access point: Portal Roles


    • Option 4 - Publishing Strategy within SAP NetWeaver 2004s BI

      Based on Rolling out the New SAP NetWeaver 2004s BI Frontend Tools:
    • Replace BW 3.x Query Designer and BW 3.x BEx Analyzer with SAP NetWeaver 2004s Query Designer and BEx Analyzer.
    • Don&#146;t coexist these tools for end users

    • BEx Workbooks
    • All Workbooks are broadcast to and stored in KM
    • In this scenario, there is no automatic migration so every workbook would need to be broadcast manually initially to store it in KM BEx Browser isn&#146;t used anymore

    • Queries
    • As Queries are created, they are broadcast to KM
    • Web Analyses built with Web Analyzer are stored in KM and accessed through Web Analyzer or KM Navigation iViews
      Web Templates and Formatted Reports
    • Web Templates and Formatted Reports are Broadcast to KM and stored there as documents
    • These reports are accessed through My Portfolo/BEx Portfolio in the Business Intelligence Role

    • End User Accesses
    • All End Users will enter through the Business Intelligence Portal Role. From here, they can choose Web Analyzer, My Portfolio, or BEx Portfolio
    • From the Web Analyzer, they can access any broadcasted or saved reports from KM or they can access BI Queries, BI Query Views, or BI InfoProviders
    • Users will use My Portfolio/BEx Portfolio to get Workbooks, Web Template, Formatted Reports, or Web Analyses
    • Users will only have 1 access point: Business Intelligence Portal Role

     

    Options Advantages and Disadvantages
    The options listed above are not the only options. These are just four possible options that you can use as a starting point to frame your discussion on your publishing strategy based on the destinations and tools matrix presented in the first part of this blog series. Options 1 and 2 listed above are definitely the lowest TCO/maintenance models. These are very easy to administrate and maintain. Options 3 and 4 require quite a bit higher TCO to manage and maintain.

     

    What's coming in Part 3 of this BLOG?
    Integral to publishing strategies are strategies around transporting. In part 3 of this BLOG, I'll be discussing options and key considerations for transporting all these reports! Part 4 will discuss how to work with permissions between a lot of the reporting destinations. Also, what I focus on is up to you. This presentation/blog presents a few different options for publishing strategies. It also takes you through (step by step) with each tool on how to publish. If you have additional questions, or have any comments on what you'd like to see next, please post them here and I'll base part 3 of the blog based on the SDN community feedback.


     

    Summary
    Hope you found this useful. Definitely define your reporting strategy. For a full rollout strategy, see this blog: Rolling out the New SAP NetWeaver 2004s BI Frontend Tools.

     

    h5. Introduction

     

    Recently, I've had lots of people ask about how to segment the navigation pane or deal with lots of objects within the navigation pane? In this blog I describe options for working with the navigation pane in SAP NetWeaver 2004s BI. As per the GA Limitations located here: https://websmp208.sap-ag.de/~sapdownload/011000358700003437292006E/FunctEnhancSchedNW2004sB.ppt, there are planned improvements in SPS11 in this area, but this blog will discuss the options before these enhancements are available.






    h5. Option 1 - Using the Tray Option

     

    The first option is you can turn on the tray option within the Navigation Pane web item. This will create a tray icon to show or hide the navigation pane to buy you screen real estate. If you need to create 3 separate trays for collapse functionality, you can do this by creating a different navigation pane for each area (row, column, free characteristics). To put these objects next to each other, you can creae these separate navigation panes, but there is no way to filter to a more granular level than “row, column, or free characteristic”. Once this is done, they can be put side by side by using the "Container Layout" web item or by using html tables.





    Collapsed (Side by Side):

    image





    Expanded (Side by Side):

    image

     

    image





    The limitation of using this is you cannot embed the div tag within a “Container Layout” or “Container” web item. You must use html tables to control layout and formatting when using div scrolling.





    h5. Summary

    Hopefully these workarounds will help you work with navigation panes that have lots of characteristics and key figures.

     

    Introduction
    In this blog, I'm going to discuss tips and tricks to consider when printing to PDF from the Web Application Designer in SAP NetWeaver 2004s BI.

     

    How it works?
    The most important thing to consider, is which objects are supported when printing to PDF. This is listed in the online help here: http://help.sap.com/saphelp_nw2004s/helpdata/en/43/68ce8391886e47e10000000a422035/frameset.htm. Therefore, these are the only web items you can print to pdf. When printing to PDF, you have 2 options:

    • 1. Print all web items in web template - In this case, any supported web item you choose will be printed in the order in which it appears in the web application.
    • 2. Bind printing to individual supported web items - In this option, you can display lots of web items on your web application, but only print a few when exporting to PDF.


    • The most important thing to note is when printing to PDF, the entire web application as displayed on the screen isn't printed to PDF. The web items used are sent sequentially, in the order they appear in the web application, to be printed in PDF. Therefore, the printing prints each web items sequentially and doesn't retain layout of these web items with respect to each other. Therefore, if two items are "side-by-side" on the web application, they won't be printed that way. The first one will be printed to PDF and the second one will be sent after it and appear underneath in on the PDF. The only way to retain format is to use the "Report" web item. This web item will print the format as it appears.

     

    Updating Headers and Footers
    As shown in the link above from the online help, the headers and footers support date, time, page numbers, and free text. If you want to add other parameters to the header or footer, currently, as of SPS9, this is not available natively. Currently, there are plans in SPS11 to allow including an image in the header of web applications via the print dialog as per the GA Limitations listed here: https://websmp208.sap-ag.de/~sapdownload/011000358700003437292006E/FunctEnhancSchedNW2004sB.ppt.

     

    Printing Pictures
    To embed images in your web application, you can use img tags to embed images within the body of the web application. This cannot be included in the header when printing to PDF as listed in the limitation above. To do this currently, any image in the body will be printed when printing to PDF. To embed an image from the MIME repository, you can use the following code:



    This image will be printed in the order in which it appears within the web application. Again, this does not retain the layout positioning of where the image is located in the web application. To print an image to PDF with regard to keeping layout, you must embed it in the report web item and use this report item within your web application.

     

    Working with objects in the body
    As mentioned in the online help, the export to PDF supports the Information Field web item. You can use this to display filter values, variable values, or generic text elements. If you use this in your web template, you can print out this information within your PDF export. If you want some of these properties to print at the top of your application, and some at the bottom, you will need to embed this twice and bind the individual parameters you want in each web item.

    The other option is to use the Text web item. If you this at the top of the web application, this information will show at the top of the PDF export. The difference with using these parameters at the top of the web application and using the header is that the header repeats on each page whereas these parameters will only show on page 1. Using this text web item, you can hardcode any header parameter you need. To dynamically populate this with parameters such as the query name, filter values, variable values, or even results cells, you can use XPATH statements. See this blog on using XPATH statements: Using XPATH statements within SAP NetWeaver 2004s BEx Web Application Designer - Part 1.

    The most important thing to note is that layout must be controlled within the report item. If you want to embed a formatted report and chart side by side, both must be embedded in the Report Item. Otherwise, these are serialized within the web application and they will be printed vertically, not horizontally.

     

    Summary
    I've tested these scenarios on SPS9 with FEP902. Hope this helps you with your printing needs!

    Introduction
    As part of our migration strategy, we need to decide what to do with our workbooks. As BEx Analyzer has been around the longest of most of our BI Tools, this is generally the most widely deployed in our current customer base. Therefore, over the years, users may have become very savvy with these workbooks and may have ventured into using Visual Basic within these applications. This blog shows what BW 3.x functions in VBA are part of the public API that was published. It also discusses what the corresponding function is in SAP NetWeaver 2004s BI.

     

    How do we compare?
    Within SAP NetWeaver 2004s BEx Analyzer, a design toolbar has been added that allows us to use many elements and features we did not have previously. Therefore, in general, the use of Visual Basic is generally going to less in the new environment. However, we are talking about what migrates, so let us take a look. Figure 1 shows what functions existed in BW 3.x and their corresponding functions in SAP NetWeaver 2004s BI.

    NOTE: Not all functions that existed in BW 3.x exist in SAP NetWeaver 2004s BI. In general, this is because these functions generally would not be needed due to being replaced by new objects available in the new design toolbar. However, this may cause some problems for migration.

    Figure 1 - Comparison of Functions
    BW 3.x
    SAP NetWeaver 2004s BI
    Comments
    SAPBEXgetWorkbookID
    SAPBEXgetWorkbookID
     
    SAPBEXreadWorkbook
    SAPBEXreadWorkbook
     
    SAPBEXsaveWorkbook
    SAPBEXsaveWorkbook
     
    SAPBEXgetErrorText
    SAPBEXgetErrorText
     
    SAPBEXsetFilterValue
    SAPBEXsetFilterValue
     
    SAPBEXgetFilterValue
    SAPBEXgetFilterValue
     
    SAPBExcopyFilterValue
      
    SAPBEXsetDrillState
    SAPBEXsetDrillState 
     
    SAPBEXgetDrillState
    SAPBEXgetDrillState
     
    SAPBEXrefresh
    SAPBEXrefresh
    In the 2004s Analyzer, ALL the items in the workbook can be refreshed, but refreshing a query individually is not supported
    SAPBEXpauseOn
    BEx.Synchronize = true
     
    SAPBEXpauseOff
    BEx.Synchronize = false
     
    SAPBEXfireCommand
      
    SAPBEXcheckContext
      
    SAPBEXgetFilterValue
      
    SAPBEXshowTextElements
      
    SAPBEXembedQuery
      
    SAPBEXgetResultRangeByID
    SAPBEXgetResultRangeByID
     
    SAPBEXjumpInitial
      
    SAPBEXjump
      
    SAPBEXgetResultRange_ResultArea
      
    SAPBEXgetResultRange
      
    SAPBEXtoolbar
      


     

    What to be careful of?
    We see the functions that are the same between BW 3.x and SAP NetWeaver 2004s BI. In general, these things will migrate ok. The functions that have changed and that do not exist will generally require manual work for migration.

     

    Are there other functions in SAP NetWeaver 2004s BI?
    Of Course! There are lots of new VBA functions available in the public xBEXapi module. In addition, the interface to call connection handling, BEx Precalculation, and other common functions are also in a public interface. Keep in mind that you should NOT use VBA as a first step. This is only after you've explored the new native capabilities in the BEx Design Toolbar.

     

    Where do I find details and examples?
    Easy. The best place to go for documentation is the online help. For a list of the functions for the BW 3.x runtime, see the online help here: Integration with Visual Basic for Applications. For SAP NetWeaver 2004s BI, you don't even need to go to the online help. The functions are documented directly within the modules. Open the Visual Basic Editor with the SAP NetWeaver 2004s BEx Analyzer and go to the xBExAPI module to see all the functions you can run! They are commented right there...

     

    Summary
    This is just one part of your migration picture. For a full view see: Rolling out the New SAP NetWeaver 2004s BI Frontend Tools

    Introduction
    To use external web services within the SAP NetWeaver 2004s platform, you will need to setup the http proxy to be able to access these web services. This blog will show you how to setup the web service proxies. Keep in mind this has changed between SP8 and SP9 within SAP NetWeaver 2004s.

     

    How do I set it up within SPS8 and lower?
    Within SPS8 and lower, the proxy configuration for web services that are used in Visual Composer are specified through "System Administration -> System Configuration -> Service Configuration -> Applications -> com.sap.portal.ivs.httpservice -> Services -> Proxy". For details on this see the online help at: Configuring Proxy Settings.

    Figure 1.1 - Configure Proxy Service
    image

    Figure 1.2 - Specify HTTP(s) proxy configuration
    image

     

    How do I set it up within SPS9 and higher?
    Within SPS9 and higher, proxy configuration for web services has been moved to the Visual Administrator. Within the Visual Administrator, navigate to "Server # -> Services -> Web Services Container -> Runtime -> Settings". Set the proxy information here. This is described in the online help here: Configuring Proxy Settings.

    Figure 2 - Configuring Proxy Settings in Visual Administrator
    image

     

    Example VC Applications Using Web Services

     

    What types of web services are currently supported?
    Web Services are handled differently between SPS8 and SPS9 within the NetWeaver stack.

    Within SPS8, see OSS Note 936768 for an explanation of the supported structure types.

    As of SPS9, Visual Composer supports Web services that are compliant with the Basic Profile 1 standard of the Web Services Interoperability (WS-I) Organization. Consistent use of WS-I compliant Web services will ensure technology-independent operability across platforms, operating systems and programming languages. This is mentioned in the release notes for Visual Composer in SPS9 here: http://help.sap.com/saphelp_nw2004s/helpdata/en/77/3f89af68304e2090d34f60506fd90c/frameset.htm. This is also mentioned in OSS Note 969418.

     

    Summary
    The reason I put this together was due to the numerous questions around web service consumption within Visual Composer. Hope this helps!

    h5. Introduction

    In this blog, I will show an example of the power of BI Commands within the BEx Web Application Designer in SAP NetWeaver 2004s BI. In this scenario, I demonstrate how you can show/hide a particular characteristic from displaying within your web application while keeping the data table as input ready for a planning enabled BEx Query! This will allow you flexibility in your presentation layer versus your integrated planning input layer.



    h5. Here's an example view

    The example application looks as follows:


    *Figure 1 - Sample Application (default view)*

    image



    *Figure 2 - Sample Application (after clicking hide currency)*

    image



    *Figure 3 - Sample Application (after clicking show currency)*

    image





    As we see here, the query has Fiscal Year, Currency, and Version. These are all required to be in the rows to be at the lowest of the query for planning. Therefore, this solution shows how you can be at the lowest level, but hide the display of a particular characteristic from your table. If you utilize this method, keep in mind that the data will be written for this particular "hidden" characteristic value. In general, it is recommended that the characteristics you plan on are specified in the query and not directly in the web application to drive the most consistency. This solution just shows how to control the presentation layer.




     

    h5. Implementation

     

    To implement this solution is very straightforward. We are using the command "SET_PRESENTATION" within the Command Wizard in the BEx Web Application Designer. The values for this presentation can be found in the online help here: http://help.sap.com/saphelp_nw2004s/helpdata/en/43/d8c6dcc0700235e10000000a11466f/content.htm .

    h5. What Next? - Toggle Buttons!

     

    So now you're probably thinking, hey, he's got two buttons there. That takes up screen real estate. Why doesn't he make that a toggle button. You can do that as well! The online help has an example of toggle buttons here: http://help.sap.com/saphelp_nw2004s/helpdata/en/43/935812ff0b274ee10000000a422035/frameset.htm . Definitely worth checking out.





    *Figure 4 - Web Template with Toggle Buttons (before click):*

    image






    *Figure 5 - Web Template with Toggle Buttons (after click):*

    image

     

     

     

    Introduction
    Recently, I did a webinar on Standard Reporting Authorizations within SAP NetWeaver 2004s BI. See the webinar presentation here: SAP NetWeaver 2004s BI Authorizations for Reporting. There has been lots of discussions about analysis authorizations because it is new, but I don't want people to forget about their reporting authorizations. In this webinar I discuss how to authorize what reports people can see.

     

    What is covered?
    We cover an overview with the types of objects we're authorizing (queries, workbooks, web templates, formatted reports, etc...). Also discussed is a delta of authorization objects between BW 3.x and SAP NetWeaver 2004s BI. After that, there is a discussion of different implementation scenarios with a specific focus on TCO (total cost of ownership). Then I talk about some personal lessons learned.

     

    Summary
    Definitely check out this webinar!