BIApplicationFrame

Use

In a BIApplicationFrame, Web Templates that are based on BEx Web Applications can be accessed using a URL. Various attributes can be set for a Web template. They are transferred as parameters using the URL. When using the BIApplicationFrame, these parameters can be set as properties of the UI element.

For information on command URLs, see the Help Portal for SAP NetWeaver 2004 at Start of the navigation path BI Suite: Business Explorer Next navigation step BEx Web Web Application Design: BEx Web Application Designer End of the navigation path command URLs.

For information on command URLs, see the Help Portal for SAP NetWeaver 2004 at BI Suite: Business Explorer → BEx Web → Web Application Design: BEx Web Application Designer →

For round trips within the Web Dynpro ABAP application, the session and navigation state of the BI application are retained. The BIApplicationFrame UI element can thus also trigger navigation within the existing BI application. The technical prerequisite for this is that the BiApplicationFrame UI element accesses the content of the BI application using JavaScript in the browser. To enable this, the Web Dynpro ABAP application and the BI application must use the same protocol (either HTTP or HTTPS). For different servers, domain relaxing must take place. This means that the WDPROTECTEDAPPLICATION function cannot be used in a scenario with BIApplicationFrame.

Example of the Visual Display

Runtime Class

CL_WD_BIAPPLICATION_FRAME

Properties in View Designer

Name	Type	Initial Value	Bindable
id	STRING	(automatic)	No
contextMenuBehaviour	WDUI_CONTEXT_MENU_BEHAVIOUR	inherit	No
contextMenuId	WDY_MD_UI_ELEMENT_REFERENCE		No
dataMode	WDUI_BI_DATA_MODE	default	Yes
dataProviderStateName	STRING		Yes
dataProviderStateType	WDUI_BI_STATE_TYPE	default	Yes
debug	WDY_BOOLEAN	false	Yes
enabled	WDY_BOOLEAN	true	Yes
height	STRING		Yes
lifeTime	WDUI_LIFE_TIME	whenVisible	Yes
meltVariables	WDY_BOOLEAN	true	Yes
server	STRING		Yes
serverType	WDUI_BI_SERVER_TYPE	abap	Yes
sessionId	STRING		No
stateless	WDY_BOOLEAN	false	Yes
styleClassName	STRING		Yes
suppressSystemMessages	WDY_BOOLEAN	true	Yes
suppressWarnings	WDY_BOOLEAN	false	Yes
templateId	STRING		Yes
tooltip	Translatable text		Yes
URL	STRING		No
usePersonalization	WDY_BOOLEAN	true	Yes
variablesClear	WDY_BOOLEAN	true	Yes
variableScreen	WDY_BOOLEAN	false	Yes
variant	STRING		Yes
visible	WDUI_VISIBILITY	visible	Yes
width	STRING		Yes

Dynamic Programming

For dynamic programming, the same properties, events, and aggregations as in the View Designer are available. But note that the spelling format and use of upper/lower case is different.

Dynamic Programming of Properties

View Designer Name	Runtime Name	Type
contextMenuBehaviour	CONTEXT_MENU_BEHAVIOUR	WDUI_CONTEXT_MENU_BEHAVIOUR
contextMenuBehaviour: inherit	CL_WD_BIAPPLICATION_FRAME=>E_CONTEXT_MENU_BEHAVIOUR-INHERIT
contextMenuBehaviour: provide	CL_WD_BIAPPLICATION_FRAME=>E_CONTEXT_MENU_BEHAVIOUR-PROVIDE
contextMenuBehaviour: suppress	CL_WD_BIAPPLICATION_FRAME=>E_CONTEXT_MENU_BEHAVIOUR-SUPPRESS
contextMenuId	CONTEXT_MENU_ID	WDY_MD_UI_ELEMENT_REFERENCE
dataMode	DATA_MODE	WDUI_BI_DATA_MODE
dataMode: default	CL_WD_BIAPPLICATION_FRAME=>E_DATA_MODE-DEFAULT
dataMode: hybrid	CL_WD_BIAPPLICATION_FRAME=>E_DATA_MODE-HYBRID
dataMode: New	CL_WD_BIAPPLICATION_FRAME=>E_DATA_MODE-NEW
dataMode: static	CL_WD_BIAPPLICATION_FRAME=>E_DATA_MODE-STATIC
dataMode: staticHybrid	CL_WD_BIAPPLICATION_FRAME=>E_DATA_MODE-STATIC_HYBRID
dataMode: stored	CL_WD_BIAPPLICATION_FRAME=>E_DATA_MODE-STORED
dataProviderStateName	DATA_PROVIDER_STATE_NAME	STRING
dataProviderStateType	DATA_PROVIDER_STATE_TYPE	WDUI_BI_STATE_TYPE
dataProviderStateType: default	CL_WD_BIAPPLICATION_FRAME=>E_DATA_PROVIDER_STATE_TYPE-DEFAULT
dataProviderStateType: infoprovider	CL_WD_BIAPPLICATION_FRAME=>E_DATA_PROVIDER_STATE_TYPE-INFOPROVIDER
dataProviderStateType: query	CL_WD_BIAPPLICATION_FRAME=>E_DATA_PROVIDER_STATE_TYPE-QUERY
dataProviderStateType: view	CL_WD_BIAPPLICATION_FRAME=>E_DATA_PROVIDER_STATE_TYPE-VIEW
debug	DEBUG	WDY_BOOLEAN
enabled	ENABLED	WDY_BOOLEAN
height	HEIGHT	STRING
lifeTime	LIFE_TIME	WDUI_LIFE_TIME
lifeTime: whenAlive	CL_WD_BIAPPLICATION_FRAME=>E_LIFE_TIME-WHEN_ALIVE
lifeTime: whenVisible	CL_WD_BIAPPLICATION_FRAME=>E_LIFE_TIME-WHEN_VISIBLE
meltVariables	MELT_VARIABLES	WDY_BOOLEAN
server	SERVER	STRING
serverType	SERVER_TYPE	WDUI_BI_SERVER_TYPE
serverType: abap	CL_WD_BIAPPLICATION_FRAME=>E_SERVER_TYPE-ABAP
serverType: java	CL_WD_BIAPPLICATION_FRAME=>E_SERVER_TYPE-JAVA
sessionId	SESSION_ID	STRING
stateless	STATELESS	WDY_BOOLEAN
styleClassName	STYLE_CLASS_NAME	STRING
suppressSystemMessages	SUPPRESS_SYSTEM_MESSAGES	WDY_BOOLEAN
suppressWarnings	SUPPRESS_WARNINGS	WDY_BOOLEAN
templateId	TEMPLATE_ID	STRING
tooltip	TOOLTIP	WDY_MD_TRANSLATABLE_TEXT
URL	URL	STRING
usePersonalization	USE_PERSONALIZATION	WDY_BOOLEAN
variablesClear	VARIABLES_CLEAR	WDY_BOOLEAN
variableScreen	VARIABLE_SCREEN	WDY_BOOLEAN
variant	VARIANT	STRING
visible	VISIBLE	WDUI_VISIBILITY
visible: none	CL_WD_BIAPPLICATION_FRAME=>E_VISIBLE-NONE
visible: visible	CL_WD_BIAPPLICATION_FRAME=>E_VISIBLE-VISIBLE
width	WIDTH	STRING

More Information

Web Template Parameters

You can find more information about accessing actions in a BEx Web application in the system documentation for IF_WD_BI_APPLFRAME_METHOD_HNDL.