BI Pattern Wizard

Dear All,
I tried playing around with the Pattern Wizard in WAD on 2004s.
The problem there is, I can not see the reusable web items and the ICP template is not being displayed properly.
I tried searching for the sap_bw_pattern_objects role and was not able to find it.
Any inputs?
Thanks,
Karan.

Hello,
Please try to open any Reusable Web Item (RWI) in WAD directly (in the Reusable Web Item pane). Do you see any there?
Have you activated all RWIs that are delivered by SAP in your backend?
Regards, Karol
SAP BI Development

Similar Messages

BI Pattern Wizard Role Missing in 2004s!

Hi, In the Front-end design guidlines document for 2004s the BI Pattern Wizard Section mentions that the reuseable Web Items are available in role SAP_BW_PATTERN_OBJECTS. I can't find this role in the system and it doesn't show up in Business Content as available either. Googling shows that the Role is only mentioned in only one place and that's the document I'm referring to.
1. Is anyone using BI Patterns successfully in 2004s?
2. Anyone know how to access Role SAP_BW_PATTERN_OBJECTS?
Thanks!
Message was edited by:
Kenneth Murray
Can anyone from SAP confirm this Role?

Forgot to mention I am already on SP10 and have the wizard working fine. Just that when I go to specify a reuseable web item I do not see any of the standard items from SAP. According to the paper I need that Role!
How can I fix this so that I can see them?

2004s BI Pattern Wizard Use!

Hi, Do I have to install the Business Content Web Templates in order to use the BI Pattern Wizard? If so where is it documented which ones to activate?
Thanks!

Please review note 985119 to use the template wizard from SP 9 and above.

Pattern Wizard

Hi everyone,
We apply Note 985119 and can not find Pattern Wizard. We also updated to SP10 and still can not find it. Can anyone tell me what steps I need to do to have this Pattern Wizard.
Thanks, Jin

Using the ICP pattern results in all of the selection I spoke about earlier!
thanks

BI Pattern Wizard Question? BI 7.0

Hi, When creating a new Web Template in WAD I am invoking the BI Wizard. I select the "Small Web Template w/Analysis Item and 1DP", but only 2 steps are shown.
1. Web Template Properties and Data Provider Settings
2. Analysis Item (Confusing at best)
I was expecting to have to select and configure quite a bit more like filter area, drop downs, etc. Any ideas why only 2 steps are showing up?
Thanks,

Using the ICP pattern results in all of the selection I spoke about earlier!
thanks

BI Pattern Wizard not working

Hi, when I try to create a template in WAD using the ICP Pattern I get errors in the template.
RSWADMDERR1 169 Item not recognized; check spelling or metadata in system
RSWADMDERR1 064 Parameter not recognized; Check your metadata.
These errors are presented in a dialog box. Selecting OK brings me to the detail error messages which shows:
E001    Parameter of Object data_provider:QUERY_VIEW_DATA_PROVIDER:DP_1 unknown to system
E165    Itemtype of Object item::DATA_DISPLAY not known
E110    Parameter INITIAL_STATE of Object data_provider:QUERY_VIEW_DATA_PROVIDER:DP_1 cannot be parent of
E115    Item item::DATA_DISPLAY of type cannot be parent of VISIBILITY
E115    Item item::DATA_DISPLAY of type cannot be parent of DATA_PROVIDER_REF
E180    Illegal Parameter value of Paramter INITIAL_STATE of Object data_provider:QUERY_VIEW_DATA_PROVIDER:DP_1
The funny thing is that the wizard didn't even ask for a data provider. has anyone got experience with this wizard in BI 7.0 that might be able to help?

Just had to input an infoprovider in the appropriate place in the wizard. It's not intuitive. The place to input an infoprovider looks like part of the accompanying graphic.
Thanks

BI Wizard in 70

Hi, I'm on BI 7.0 sp9 and I don't see how to access the BI Wizard. Particularly I can't see the "List off Web Items and BI Patterns Tab Page" as listed in the instructions for step 2.
Any ideas?
Integration
The pattern wizard is an integral part of the Web Application Designer and does not require any additional installation. You can call the pattern wizard as follows in the Web Application Designer:
1. In the Web Application Designer menu bar, choose Web Template New.
2. On the List of All Web Items and BI Patterns tab page, choose a BI pattern from under the BI Patterns with Pattern Wizard node. The pattern wizard is started automatically.
Prerequisites
The pattern wizard is available as of SAP NetWeaver 2004s Support Package Stack 9.
Thanks

Hi Kenneth,
You need to change an entry in a table for this tab to become visible.
Check note 985119 for this.
regards,
Olav

BI Pattern Role Missing!?

Hi, In the Front-end design guidlines document for 2004s the BI Pattern Wizard Section mentions that the reuseable Web Items are available in role SAP_BW_PATTERN_OBJECTS. I can't find this role in the system and it doesn't show up in Business Content as available either. Googling shows that the Role is only mentioned in only one place and that's the document I'm referring to.
1. Is anyone using BI Patterns successfully in 2004s?
2. Anyone know how to access Role SAP_BW_PATTERN_OBJECTS?
Thanks!
Can anyone from SAP confirm this Role?

Hi, Thanks for the quick reply! After a search they still do not show up! And from looking at BC they are all installed. Maybe I need to have some other role?
Any ideas what I can do?
Thanks!

Message E FPRUNX 001 cannot be processed in plugin mode HTTP

Hi,
I am getting an error when i execute BSP application error is as follows.
Exception Class CX_SY_MESSAGE_IN_PLUGIN_MODE
Error Name
Program Z_GET_BOOKING_FORM_NET========CP
Include Z_GET_BOOKING_FORM_NET========CM001
ABAP Class Z_GET_BOOKING_FORM_NET
Method DO_REQUEST
Line 74
Long text -*
coding in the method is as follows
method DO_REQUEST.
*CALL METHOD SUPER->DO_REQUEST
runtime->server->response->delete_header_field( name = 'Expires' ).
runtime->server->response->delete_header_field( name = 'Pragma' ).
DATA: l_name TYPE funcname.
TRY.
 CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
 EXPORTING
 i_name = 'Z_CUST_FLIGHT_BOOKING_GEBO'
 IMPORTING
 e_funcname = l_name
 EXCEPTIONS
 OTHERS = 0.
 CATCH cx_fp_api_repository. "#EC NO_HANDLER
 CATCH cx_fp_api_usage. "#EC NO_HANDLER
 CATCH cx_fp_api_internal. "#EC NO_HANDLER
ENDTRY.
DATA: l_outputparams TYPE sfpoutputparams.
*Start Form Processing.
l_outputparams-getpdf = 'X'.
CALL FUNCTION 'FP_JOB_OPEN'
 CHANGING
 ie_outputparams = l_outputparams
 EXCEPTIONS
 cancel = 1
 usage_error = 2
 system_error = 3
 internal_error = 4
 OTHERS = 5.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Add a call to the Formu2019s function module. Notice the
settings on fp_docparams that allow for the generation
of an Interactive form Without these settings the form
will be generated as standard print form. Hint: Get the
form functional moduleu2019s generated name by testing it in
transaction SFP, and then use the Pattern wizard to insert
the function callin your code.
DATA: fp_docparams TYPE sfpdocparams,
 reservedonly TYPE bapisbodat-reserved,
 booking_data TYPE bapisbonew,
 fp_result TYPE fpformoutput.
fp_docparams-fillable = 'X'.
fp_docparams-langu = sy-langu.
CALL FUNCTION l_name
 EXPORTING
 /1bcdwb/docparams = fp_docparams
 reserved = reservedonly
 booking_data = booking_data
 IMPORTING
 /1bcdwb/formoutput = fp_result
 EXCEPTIONS
 usage_error = 1
 system_error = 2
 internal_error = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Get the returned PDF, and store it in a
fpformoutput-pdf type variable.
DATA: pdf TYPE fpformoutput-pdf.
_ pdf = fp_result-pdf._
*Close the form processing session by calling the
*FP_JOB_CLOSE function.
CALL FUNCTION 'FP_JOB_CLOSE'
 EXCEPTIONS
 usage_error = 1
 system_error = 2
 internal_error = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Set the content type to be of u201Capplication/pdfu201D. This way,
the client will know what kind of format the response is,
and will start the adobe reader to display it.
CALL METHOD response->set_content_type
 EXPORTING
 content_type = 'application/pdf'.
*Put the PDF into the response.
CALL METHOD response->set_data
 EXPORTING
 data = pdf.
endmethod.
error is in the line 74 in this coding line 74 is
pdf = fp_result-pdf.
Can any one suggest me some solutions.
Thanks,
Nethaji.

Hi,
I'm facing the same problem.
I wrote an very easy report. It works as intended, but when i set fillable='X' i get the error FPRUNX 001.
FP_GET_LAST_ADS_TRACE return following:
Begin operation:
Render, elapsed time = 16 ms.
# End operation: Render, elapsed time = 89 ms.
# Begin operation: UsageRights, elapsed time = 89 ms.
# End operation: UsageRights, elapsed time = 97 ms.#
...and the error string of FP_GET_LAST_ADS_ERRSTR is:
ADS: Request start time: Wed Jul 01 14:44:26 CEST 2009(200.101).
Any idea what the problem might be?

Types of web reports

Hi gurus,
What are the types of web reports we have? Where do you specify them, Is it some sort of property setting?
i'll asign points.
regards
priya

Hi,
   Web application design, with the BEx Web Application Designer as its main tool, allows you to use generic OLAP navigation for your BI data in Web applications as well as in business intelligence cockpits for simple or highly individual scenarios. Web application design comprises a broad spectrum of Web-based business intelligence scenarios, which you can adjust to meet your individual needs using standard Web technologies.
Features
The following figure shows how the Web Application Designer is integrated into the function landscape and tool landscape of the Business Explorer:
You can use this BEx Web Application Designer, the desktop application used to create Web applications, to generate HTML pages that contain BI-specific contents such as tables, charts or maps. These objects, which retrieve BI data from a data provider and place it in a Web application as HTML, are known as Web items. For more information about the Web items available, see Web Items. Web Applications are based on Web Templates that you create and edit in the Web Application Designer. You can save the Web templates and access them from the Web Browser or the portal. Once they have been executed in the Web, Web templates are known as Web Applications.
Business Explorer Web application design allows you to create highly individual scenarios with user-defined interface elements by using standard markup languages and the Web design API. You can adjust and enhance the Web templates (the HTML pages that determine the structure of Web applications) on an individual basis. For more information on this, see Web Design API.
The BEx Web Application Designer is a desktop application for creating Web applications with BI-specific content. Using the BEx Web Application Designer, you can create an HTML page containing BI-specific content such as various tables, charts, or maps. This HTML page (Web application) is the basis not only for Web applications with complex interaction, but also for Web cockpits and iViews.
The command wizard and pattern wizard are integral parts of the Web Application Designer. Using the command wizard, you can easily generate commands from the Web Design API and include them in your Web template. Using the pattern wizard, you can configure BI patterns to a certain extent and tailor them to meet your needs.
The initial view of the BEx Web Application Designer has four different screen areas in addition to the menu and toolbars.
      Web Items Screen Area
      Web Template Screen Area
      Properties Screen Area
      Error and Warnings Screen Area
Applications with the BEx Web Application Designer. For more information about creating Web applications, see Creating Web Applications.
You can adjust the appearance of the Web Application Designer to meet your requirements. The object on which you are working, namely the Web template, is handled differently from the tools and help windows with which you are working.
      You can show and hide the individual screen areas and toolbars using the View menu option.
      You can reposition the three toolbars and the Web Items and Properties windows as required. Depending on where you reposition the object, it is either anchored or appears freely as a toolbox.
      Since the Web Application Designer is a Multiple Document Interface Application (MDI Application), you can open and manage different windows with Web templates simultaneously. You can use the Window menu option to arrange the windows differently: cascading (overlapping), vertical, or horizontal.
Using the BEx Web Application Designer, you can create a BEx Web application (an HTML page with BI-specific content) easily.
       1.      Creating a Web template
The Web template is the starting point for creating a Web application. The Web template is an XHTML document that is used to define the structure of a Web application. It contains placeholders for Web items, data providers, and commands. A Web template becomes a Web application when the data is displayed in the Web browser.
During the design process, you change the Web template by embedding placeholders for Web items and data providers. You can keep track of these changes in the XHTML view.
To create a new Web template, choose Web Template ® New in the Web Application Designer menu bar. You can also create Web templates from the Select Web Template window. Choose Create New Web Template.
       2.      Setting the data binding/selection of the data provider
The data for your Web items is provided by data providers that you create in the Web Application Designer. You can assign a data provider to multiple Web items. The data provider concept makes it possible to change the data source of a Web item easily. If a particular data provider is assigned to more than one Web item, any changes made affect all the assigned Web items. By means of navigation (by changing the drilldown), the Web item always displays the current drilldown data.
A data provider is a dynamic object that returns current data for one or more Web items at runtime. You define the start view of the data provider by selecting a query or a query view. For more information about data providers, see Data Providers in BI Applications.
There are several ways to create data providers:
          a.      In the Data Provider section in the Web Items screen area
           i.       Select whether you want to create a data provider of type Filter or type Query View, and drag the corresponding line into the lower data provider section of the Web template screen area. The Maintain Data Provider dialog box appears.
           ii.       Assign a name to the data provider and make the remaining settings required.
In the dropdown box beneath the name field, you can also select or change the data provider type.
           b.      Using the New Data Provider symbol in the lower data provider section of the Web Template screen area
           i.       Double-click to choose New Data Provider. The Maintain Data Provider dialog box appears.
           ii.       Proceed as described under a. ii.
            c.      Using the General tab page in the Properties screen area
You can only use this option if you have already inserted a Web item into your Web template.
             i.       In the header of the properties screen area, select the Web item for which you want to create a data provider.
             ii.       On the General tab page, choose New Data Provider. The Maintain Data Provider dialog box appears.
The data provider is assigned to the selected Web item. You can also create more than one data provider, as described under c. The data providers are listed in the dropdown box under Assigning Data Providers. This enables you to assign a different data provider to the selected Web item.
The Maintain Data Provider dialog box appears under data provider: . You can modify or change the settings for the data provider here.
When you have created a data provider, it is assigned to the inserted Web item. Assigning depends on the order of the data providers in the inner structure of the Web template. See also 4.a.
       3.      Adding a Web item
The Web items in the Web Items screen area serve as templates. By dragging a Web item into your Web template, you create an actual version of the Web item; this is called an object. The Web item has a name and certain other default parameters that you can change as required (see also 4.).
You see the changes in the XHTML view. A Web item tag for the Web item and a data provider tag for the data provider (assuming you have created a data provider) were integrated into the XHTML as placeholders. Change the name of the Web item and assign a data provider to it. In the XHTML view, you can see that your settings have been written to the Web item tag. The layout you choose is also applied in the XHTML.
                            a.      Drag a Web item from one of the Web item groupings Standard, Extended, or Miscellaneous in the Web Items screen area to the Web template by using drag and drop. The Web item appears in the Web template.
Underneath the selection area for Web items and data provider maintenance, you see the help area, which provides explanations for the Web items and data providers. To display the texts for a Web item, select the Web item by double-clicking with the secondary mouse button. To hide the texts, proceed in the same way. When you hide the display of texts and select a Web item by single-clicking it, a quick info is displayed for the Web item.
                          b.      If you want to rename the inserted Web item, proceed as follows:
In the Properties screen area, choose Rename Web Item to the right of the dropdown box in which the inserted Web items are listed. Name the Web item by overwriting the default text under Name in the Properties screen area next to the dropdown box in which the inserted Web items are listed.
       4.      Specifying the properties of the Web item
                            a.      In the Properties screen area, choose the General tab page to make or change the assignment of a data provider for the corresponding Web item. See also 2.
                            b.      Choose the Web Item Parameters tab page to set the parameters for the selected Web item.
You can also set the parameters for the Chart Web item using the Edit Chart dialog box. Choose Edit in the context menu of the Chart Web item or Edit Chart in the Internal Display parameter grouping of the Chart Web item. For more information, see Editing Charts.
       5.      Adding additional Web items
To insert additional Web items, repeat steps 3 and 4.
     When you insert additional Web items using Insert ® Web Item, pay attention to where you position the cursor in your Web template. The cursor position determines where the new Web item is inserted. See also Designing the Layout of Web Templates. When you insert Web items using drag and drop, the position of the cursor is irrelevant.
      Make sure that you set the data binding and any Web item-specific parameter settings for the correct Web item. To make settings for a Web item, select the Web item in the layout view. In the header of the Properties window, the system displays the Web item for which you can change the settings. As an alternative to selecting the individual Web items, you can use the dropdown box to toggle between the attributes of individual Web items.
       6.      Designing a Web template layout
In the Web Application Designer, you create your Web template in the same way you do in various XHTML editors. See also Designing the Layout of Web Templates.
       7.      Changing the Web template properties
                            a.      To change the default properties of the Web template, select the Web template from the dropdown box in the Properties screen area.
                            b.      Choose the Web Template Parameters tab page, where you can change the parameter settings for the Web template.
For more information, see Web Template Properties.
       8.      Saving and executing the Web template
You execute the Web template in the Web browser (portal). The Web template becomes a Web application, which means the template is saved on the Application Server for ABAP and a URL is generated for this Web application.
At runtime (triggered by calling the URL), the BI tags are replaced by corresponding HTML with the information determined by the Web item and data provider settings. When this is done, the Web template on the Application Server for ABAP is accessed. Therefore, you must save your Web template before you execute it.
                            a.      To save your Web template, in the menu bar of the Web Application Designer, choose Web Template ® Save.
                            b.      Choose Web Template ® Execute to view your Web application in the browser (portal).
You must save the Web template before executing it in the Web browser. Therefore, when you execute the template, you are asked to save it if you have not already done so.
      To assign a Web template to a role, choose Web Template ® Publish ® In Role. See also Role Maintenance.
      To copy the URL of a Web template to the clipboard, choose Web Template ® Publish ® Copy URL to Clipboard. The Web template, however, must already be saved.
      To broadcast a Web template, choose Web Template ® Publish ® BEx Broadcaster. For more information, see Precalculating and Broadcasting Queries, Query Views, Web Templates and Reports.
Result
Your Web application is started and displayed in the portal, which in turn runs in a Web browser.
If you want to print your Web application, choose Print in the context menu for the executed Web application.

GA limitation

Hi,
We can check the document of GA limitation. But I could not understand the following sentence. I am very happy if you tell me the detail. it is welcome if you answer, not all, but one of any..
Report Designer: Formatting of frames (color, line styles and sizes), definition of cell frame margin
what is the frames?
General: List calculation: Normalization according to not visible values
Web Application Designer: Pattern Wizard in WAD
Modal Windows cannot be displayed in Firefox.
what is model windows
Wizard to customize button item
Using the standard Excel Commentary function to create BI documents
Search Objects in Portal in Open/Save Dialogs in Web Analyzer
what is the Object in portal?
Check referential integrity as part of transformation
Kind regards,
Masa

Report Designer: Formatting of frames (color, line styles and sizes), definition of cell frame margin
what is the frames?
- This is related to border color and width control
General: List calculation: Normalization according to not visible values
- Normailzation is a calculation option. If you want to include suppressed values that aren't displayed as part of your normalization, you can now do this.
Web Application Designer: Pattern Wizard in WAD
- This is new functionality. There will be a wizard to help create UI patterns.
Modal Windows cannot be displayed in Firefox.
what is model windows
- Modal windows are popup dialogs...
Wizard to customize button item
- This allows you a step by step guided approach to call commands that get executed when you hit a button.
Using the standard Excel Commentary function to create BI documents
- Excel allows you to have commentary mark (creating comments on a cell). There will be tighter integraton with these comments and KM documents.
Search Objects in Portal in Open/Save Dialogs in Web Analyzer
what is the Object in portal?
- The object is any BICS object (query, 3rd party data source, or infoprovider)

RRI in Visual Composer

Dear Colleagues,
Like Report-Report interface (RRI) in BW, wherein detailed report can be invoked from chart/graph, can similar thing is possible in Visual Composer?
Please advice.
Regards
Pankaj

Wih a workaround as below you can tailor to suite your needs ;however there are some limitations you may want to look below-
You can also combine the advantages of the VC and BEx Web runtime. For example, you can develop a VC model that renders the data in Adobe Flex and within this model you can define links to BEx Web Applications that calls the underlying query in order to analyze the data in more detail. There the data will be displayed in DHTML and you can use the BEx features to drill-down in a pivot table, for example
General Aspects - VC
In the area of Analytics you can use different tools to model reporting scenarios and analytical applications.
Deciding which tool best meets your requirements depends on several factors - features, UI technology, User
types, interaction, OLAP and/or OLTP data needed, for example. The UI tool decision tree (see Figure 3) will
support you in your choice and will help you determine which tool meets your requirements in the best way. Your
decision also depends on which criteria (e.g. features) are most important for you.
First you should think about whether you need to use the functionalities of the BI analytical engine (drill-down
navigation in reports, slice and dice analysis, and external presentation hierarchy, for example). If you dont
need those functionalities, then you should use Visual Composer, especially if you want to use query services
(Web Services and/or BAPIs) and/or if you want to embed OLAP data into operational processes. Also, use the
Visual Composer if your analytic application to be rendered with Adobe Flex. Adobe Flex is a presentation-tier
framework and server that enables the development of Rich Internet Applications. With the Adobe Flex UI you
can use interactive UI elements, for example. If you want to use just OLTP data in your reporting scenario, you
also have to use Visual Composer.
If you want to report based only on OLAP data (stored in Info Providers in a SAP BI system), you should use the
BI Suite tools. If the end users should access their reports using MS Excel, you must use the BEx Analyzer.
Beforehand you have to define a query using the Query Designer that then can be easily embedded into a BEx
Analyzer workbook. You can also do basic formatting with standard MS Excel functionality as well as integrating
BI Integrated planning functionality.
If you want to use formatted reporting and if you want to display the reports in a Web Browser, you should use
the Report Designer. With the Report Designer you are able to create formatted reports that are optimized for
presentation and printing. You can also access a number of formatting and layout functions.
If you need to deliver standardized reports, you should use the Pattern Wizard (integrated into the Web
Application Designer) to create pattern-based Web Templates. You can create Information Consumer Patterns
to ensure a standardized UI for the end users who access the Web Templates via the Enterprise Portal. If you
need special UI elements (for example, Tab Strips) or if you want to build planning applications, you have to use
the freestyle Web Application Designer capabilities.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/800a7bd4-7897-2910-c6b2-9ee791e9913c
Hope it Helps
Chetan
@CP..

BEx Explorer

when you open Business Explorer from Windows. you can go to analyzer, then enable the macros then SAP gives the message
" Please install Excel as a Viewer"
How to solve this problem ?

hi khan,
BEx Web Application Designer
The portal is an application that runs on the Web browser. The BEx Web Application Designer is a Windows application. It is technically possible to start Windows applications in the Web browser but this is not recommended for security reasons. Instead, you call the Windows application BEx Web Application Designer from the Windows start menu.
You can generate the BEx Web Application Designer in the Portal Content Studio as URL iView. The most important property is the URL that contains the value file://C:/Program%20Files/SAP/FrontEnd/Bw/wdbpwpub.exe
BEx Web Application Designer
Use
The BEx Web Application Designer is a desktop application for creating Web applications with BI-specific content. Using the BEx Web Application Designer, you can create an HTML page containing BI-specific content such as various tables, charts, or maps. This HTML page (Web application) forms the basis of Web applications with complex interaction, as well as Web cockpits and iViews.
The command wizard (see Commands) and pattern wizard are integral parts of the Web Application Designer. Using the command wizard, you can easily generate commands from the Web Design API and include them in your Web template. Using the pattern wizard, you can configure BI patterns to a certain extent and tailor them to meet your needs.
Features
The initial view of the BEx Web Application Designer has four different screen areas in addition to the menu and toolbars.
●      Web Items Screen Area
●      Web Template Screen Area
●      Properties Screen Area
●      Errors and Warnings Screen Area
For more information about creating Web applications, see Creating Web Applications with the BEx Web Application Designer. For more information about creating Web applications, see Creating Web Applications.
You can adjust the appearance of the Web Application Designer to meet your requirements. The object on which you are working, namely the Web template, is handled differently from the tools and help windows with which you are working.
●      You can show and hide the individual screen areas and toolbars using the View menu option.
●      You can reposition the three toolbars and the Web Items and Properties windows as required. Depending on where you position the object, it is either anchored or appears freely as a toolbox.
●      Since the Web Application Designer is a Multiple Document Interface Application (MDI Application), you can open and manage different windows with Web templates simultaneously. You can use the Window menu option to arrange the windows differently: cascading (overlapping), vertical, or horizontal.
BI Patterns
Use
BI patterns are Web applications that are tailored to the requirements of particular user groups and that are used to provide a uniform display of BI content. For the user, this means that the same function is always located in the same place with the same name.
The patterns can be configured to a certain extent using the pattern wizard of the Web Application Designer. The concept of patterns helps reduce the total cost of ownership because the actual logic to display and interact with BI applications is stored centrally for each pattern in one Web template. If changes need to be made, they only need to made to this central Web template.
For example, in the Information Consumer Pattern, a button for exporting data to Microsoft Excel is configured in the central Web template of the pattern. When you configure the Information Consumer Pattern, you can decide whether you want this button to be displayed.
Features
You can choose from the following patterns:
Pattern
Description
Information Consumer Pattern
Easy-to-use BEx Web application for users without specific BI knowledge.
For more information, see Information Consumer Pattern.
Analysis Pattern
BEx Web application for complex data analysis.
In the portal, the analysis pattern is called the BEx Web Analyzer.
For more information, see BEx Web Analyzer.
Creating Web Applications with the BEx Web Application Designer
Use
Using the BEx Web Application Designer, you can create a BEx Web application (an HTML page with BI-specific content) easily.
Procedure
       1.      Creating a Web Template
The Web template is the starting point for creating a Web application. The Web template is an XHTML document that is used to define the structure of a Web application. It contains placeholders for Web items, data providers, and commands. A Web template becomes a Web application when the data is displayed in the Web browser.
During the design process, you change the Web template by embedding placeholders for Web items and data providers. You can keep track of these changes in the XHTML view.
To create a new Web template, you have the following options:
○       In the menu of the Web Application Designer, choose Web Template ® New. A dialog box appears. Choose Blank Web Template.
○       Choose Create New Blank Web Template in the upper area to the right in the initial Web Application Designer view.
○       In the Web Application Designer tool bar, choose with the quick info text New.
       2.      Setting the data binding/selection of the data provider
The data for your Web items is provided by data providers that you create in the Web Application Designer. You can assign a data provider to multiple Web items. The data provider concept makes it possible to change the data source of a Web item easily. If a particular data provider is assigned to more than one Web item, any changes made affect all the assigned Web items. By means of navigation (by changing the drilldown), the Web item always displays the current drilldown data.
A data provider is a dynamic object that returns current data for one or more Web items at runtime. You define the start view of the data provider by selecting a query or a query view. For more information about data providers, see Working with Data Providers.
There are several ways to create data providers:
                            a.      Using the Data Provider pushbutton in the Web Items screen area
                                                  i.       Select whether you want to create a data provider of type Filter or type Query View, and drag the corresponding line into the lower data provider section of the Web template screen area. The New Data Provider dialog box appears.
                                                ii.       Assign a name to the data provider and make the remaining settings.
In the dropdown box beneath the name field, you can also select or change the data provider type.
                            b.      Using the New Data Provider icon in the lower data provider section of the Web Template screen area
                                                  i.       Double-click to choose New Data Provider. The New Data Provider dialog box appears.
                                                ii.       Proceed as described under a. ii.
                            c.      Using the General tab page in the Properties screen area
You can only use this option if you have already inserted a Web item into your Web template.
                                                  i.       In the header of the properties screen area, select the Web item for which you want to create a data provider.
                                                ii.       On the General tab page, choose New Data Provider. The New Data Provider dialog box appears. Proceed as described under a. ii.
The data provider is assigned to the selected Web item. You can also create more than one data provider, as described under c. The data providers are listed in the dropdown box under Assigning Data Providers. This enables you to assign a different data provider to the selected Web item.
The New Data Provider dialog box appears under data provider . You can modify or change the settings for the data provider here.
When you have created a data provider, it is assigned to the inserted Web item. Assigning depends on the order of the data providers in the inner structure of the Web template. See also 4.a.
       3.      Adding a Web item
The Web items in the Web Items screen area are used as templates. By dragging a Web item into your Web template, you create an actual version of the Web item; this is called an object. The Web item has a name and certain other default parameters that you can change as required (see also 4.).
You see the changes in the XHTML view. A Web item tag for the Web item and a data provider tag for the data provider (assuming you have created a data provider) were integrated into the XHTML as placeholders. Change the name of the Web item and assign a data provider to it. In the XHTML view, you can see that your settings have been written to the Web item tag. The layout you choose is also applied in the XHTML.
                            a.      Drag a Web item from one of the Web item groupings Standard, Advanced, or Miscellaneous in the Web Items screen area to the Web template by using drag and drop. The Web item appears in the Web template.
Underneath the selection area for Web items and data provider maintenance, you see the help area, which provides explanations for the Web items and data providers. To display the texts for a Web item, select the Web item by double-clicking with the secondary mouse button. To hide the texts, proceed in the same way. When you hide the display of texts and select a Web item by clicking it, a quick info is displayed for the Web item.
                            b.      If you want to rename the inserted Web item, proceed as follows:
In the Settings area of the screen, choose the Rename Web Item button to the right of the dropdown box in which the added Web items are listed. Name the Web item by overwriting the predefined text for Name in the Properties screen area next to the dropdown box where the added Web items are listed.
       4.      Specifying the properties of the Web item
                            a.      In the Properties screen area, choose the General tab page to make or change the assignment of a data provider for the corresponding Web item. See also 2.
                            b.      Choose the Web Item Parameters tab page to set the parameters for the selected Web item.
You can also set the parameters for the Chart Web item using the Edit Chart dialog box. Choose Edit in the context menu of the Chart Web item or Edit Chart in the Internal Display parameter grouping of the Chart Web item. For more information, see Editing Charts.
       5.      Adding additional Web items
To insert additional Web items, repeat steps 3 and 4.
●        When you insert additional Web items using Insert ® Web Item, pay attention to where you position the cursor in your Web template. The cursor position determines where the new Web item is inserted. See also Designing the Layout of Web Templates. When you insert Web items using drag and drop, the position of the cursor is irrelevant.
●        Make sure that you set the data binding and any Web-item-specific parameter settings for the correct Web item. To make settings for a Web item, select the Web item in the layout view. In the header of the Properties window, the system displays the Web item for which you can change the settings. As an alternative to selecting the individual Web items, you can use the dropdown box to toggle between the attributes of individual Web items.
       6.      Designing a Web template layout
In the Web Application Designer, you create your Web template in the same way you do in various XHTML editors. See also Designing the Layout of Web Templates.
       7.      Changing the Web template properties
                            a.      To change the default properties of the Web template, select the Web template from the dropdown box in the Properties screen area.
                            b.      Choose the Web Template Parameters tab page, where you can change the parameter settings for the Web template.
For more information, see Web Template Properties.
       8.      Saving and executing the Web template
You execute the Web template in the Web browser (portal). The Web template becomes a Web application, which means the template is saved on the Application Server for ABAP and a URL is generated for this Web application.
At runtime (triggered by calling the URL), the BI tags are replaced by corresponding HTML with the information determined by the Web item and data provider settings. When this is done, the Web template on the Application Server for ABAP is accessed. Therefore, you must save your Web template before you execute it.
                            a.      To save your Web template, in the menu bar of the Web Application Designer, choose Web Template ® Save.
                            b.      Choose Web Template ® Execute to view your Web application in the browser (portal).
You must save the Web template before executing it in the Web browser. Therefore, when you execute the template, you are asked to save it if you have not already done so.
●        To assign a Web template to a role, choose Web Template ® Publish ® In Role. See also Role Maintenance.
●        To copy the URL of a Web template to the clipboard, choose Web Template ® Publish ® Copy URL to Clipboard. The Web template, however, must already be saved.
●        To broadcast a Web template, choose Web Template ® Publish ® BEx Broadcaster. For more information, see Precalculating and Broadcasting Queries, Query Views, Web Templates, and Reports.
Result
Your Web application is started and displayed in the portal, which in turn runs in a Web browser.
regards
karthik
reward me points if helpfull

Web Dynpro Code Wizard - code patterns

Hello,
the code patterns that are generated by the very helpful Web Dynpro Code wizard seem to be a little inconsistent in their syntax structuring.
If I were to ask the wizard to read me a context node - I would get something like (some bits removed for brevity):
data lo_nd_result type ref to if_wd_context_node.
data lo_el_result type ref to if_wd_context_element.
data ls_result type wd_this->element_result.
* navigate from <CONTEXT> to <RESULT> via lead selection
lo_nd_result = wd_context->get_child_node( name = wd_this->wdctx_result ).
* get element via lead selection
lo_el_emp_search_result = lo_nd_emp_search_result->get_element( ).
* get all declared attributes
lo_el_emp_search_result->get_static_attributes(
 importing
 static_attributes = ls_emp_search_result ).
Yet if I were to ask the wizard to generate a message I would get:
* get message manager
data lo_api_controller type ref to if_wd_controller.
data lo_message_manager type ref to if_wd_message_manager.
lo_api_controller ?= wd_this->wd_get_api( ).
call method lo_api_controller->get_message_manager
 receiving
 message_manager = lo_message_manager
* report message
call method lo_message_manager->report_t100_message
 exporting
 msgid =
 msgno =
 msgty =
* p1 =
* p2 =
* p3 =
* p4 =
* msg_user_data =
* is_permanent = ABAP_FALSE
* scope_permanent_msg = CO_MSG_SCOPE_CONTROLLER
* view =
* show_as_popup =
* controller_permanent_msg =
* msg_index =
* cancel_navigation =
* enable_message_navigation =
 receiving
 message_id =
Edited by: Thomas Jung on Apr 27, 2010 8:56 AM

post split to avoid silly size/formatting limits
Ok - both work - but one is using the:
result = class_ref->methodname( parameters = paramvalue )
and one is using
call method class_ref->methodname
 exporting parameters = paramvalue
 receiving result = result.
As I often have to review code written by others, I encourage them to use these wizards - it helps speed code and prevents simple mistakes. But code that contains multiple different syntax structure approaches is harder to read (albeit only slightly), moreover - it looks sloppy.
But why are they not consistent in their syntax structure? (one could also argue why do we have multiple syntax structures for the same operation - but that's a different discussion).
Is there some way customers can update these structures to match with their own internal coding standards - or something we can change so that they go one way or another?
I look forward to other's thoughts on the same topic.
Cheers,
Chris

Reduce render time with wizard design pattern

I am making a long, complex interactive dynamic form. How do I make the form so that only the page/section the user is working on is visible and renders?

You could create pure virtual class that defines your test step API. Methods for the class would consist of things like setup, teardown, execute to name a few. Your developers could use this base class as the template and API for their tests. The methods regulate the format of the data exchange between your engine and their test. I would also recommend that you use packed libraries so that your test steps are basically plugins. Your test sequence would need to contain the name of the appropriate plugin to use in order to invoke the correct test step. This model is flexible and easy to extend.
We are actually investigating using this same approach for our test system. Our current system uses TestStand and we are going to investigate TestStand 2012 ability to use dynamic dispatch to invoke our test steps. It should be interesting. We use other features of TestStand so it would be nice if we can make this work. In your case a LabVIEW only implementation should be fairly straightforward.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

BI Pattern Wizard

Similar Messages

Maybe you are looking for