OfficeControl 

You can use UI element OfficeControl to add an Office document to a view. This means you can display the following Office documents within a Web Dynpro application:

●      Microsoft Word documents

●      Microsoft Excel documents

The OfficeControl UI element is made available as an ActiveX control, so that the UI element can be displayed in browsers that support ActiveX controls.

For browsers which do not support ActiveX controls, the following runtime exception is raised: Office Integration through Applet is not supported.

The implementation of the OfficeControl UI element supports the following functions for the Office documents mentioned earlier:

●      Open

●      Close

●      Backup

●      Create new documents

Note that you can open and close a document by setting the visible property of the OfficeControl UI elements to visible or none.

Also note that the OfficeControl is only active when the visible property is set to visible. Background processing is activated when the visible property is set, and width and height = 0.

In the Expert Mode additional method calls for complex operations are provided.

The integration of active controls like OfficeControl in Web Dynpro ABAP popups is not supported.

Examples of the Display

 

To enable the development of accessible applications, the tooltip property is not checked during the syntax check.

 

Runtime Class

CL_WD_OFFICE_CONTROL

 

Properties in View Designer

Name	Type	Initial Value	Bindable
ID	STRING	(automatic)	no
activateInPlace	WDY_BOOLEAN	true	yes
additionalArchives	STRING		no
archive	STRING		no
classId	STRING		no
codeBase	STRING		no
controlId	STRING		no
dataSource	XSTRING		yes
documentName	STRING		yes
documentType	WDUI_OFFICE_DOC_TYPE	ms_word	yes
enabled	WDY_BOOLEAN	true	yes
enableReadWrite	WDY_BOOLEAN	true	yes
expertMode	WDY_BOOLEAN	false	yes
height	STRING	300px	yes
showDecoration	WDY_BOOLEAN	true	yes
tooltip	Text		yes
type	STRING		no
visible	WDUI_VISIBILITY	visible	yes
width	STRING	300px	yes

 

Events in View Designer

Name

onClose

onSave

Other properties that can be inherited are defined in the associated higher-level classes. The associated UI elements are:

●        AbstractActiveComponent

●        UIElement

●        ViewElement

Dynamic programming

For dynamic programming, the same properties, events and aggregations are available as in the view designer. Bear in mind the different spellings.

Dynamic Programming of Properties

View Designer Name	Runtime Name	Type
activateInPlace	ACTIVATE_IN_PLACE	WDY_BOOLEAN
additionalArchives	ADDITIONAL_ARCHIVES	STRING
archive	ARCHIVE	STRING
classId	CLASS_ID	STRING
codeBase	CODE_BASE	STRING
controlId	CONTROL_ID	STRING
dataSource	DATA_SOURCE	XSTRING
documentName	DOCUMENT_NAME	STRING
documentType	DOCUMENT_TYPE	WDUI_OFFICE_DOC_TYPE
documentType: ms_excel	CL_WD_OFFICE_CONTROL=>E_DOCUMENT_TYPE-MS_EXCEL
documentType: ms_word	CL_WD_OFFICE_CONTROL=>E_DOCUMENT_TYPE-MS_WORD
enabled	ENABLED	WDY_BOOLEAN
enableReadWrite	ENABLE_READ_WRITE	WDY_BOOLEAN
expertMode	EXPERT_MODE	WDY_BOOLEAN
height	HEIGHT	STRING
showDecoration	SHOW_DECORATION	WDY_BOOLEAN
tooltip	TOOLTIP	WDY_MD_TRANSLATABLE_TEXT
type	TYPE	STRING
visible	VISIBLE	WDUI_VISIBILITY
visible: none	CL_WD_OFFICE_CONTROL=>E_VISIBLE-NONE
visible: visible	CL_WD_OFFICE_CONTROL=>E_VISIBLE-VISIBLE
width	WIDTH	STRING

 

Dynamic Programming of Events

View Designer Name	Runtime Name
onClose	ON_CLOSE
onSave	ON_SAVE

Example

You can find examples of this UI element in the system in collection sios.