Editing Documents with WAS-Based Web Applications

Purpose

You can use the functions that are collected under the term WebDocuments to edit document info records in the Web interface. You can directly start the workstation application for processing a linked original application file from document processing (metadata).

Those users (such as employees from product management or engineering) who do not know the functions of document management , or do not have access to the SAP graphical user interface (SAP GUI), can still edit documents without any problems.

By making various settings you can tailor document processing specially to your business processes. It is therefore possible to organize the interfaces and editing processes for different document types (for example, engineering drawings, specifications, and training material) in different ways.

Integration

Document Management

The application logic corresponds to the logic for document management (application component CA-DMS).

SAP Web Application Server (SAP Web AS)

The SAP Web Application Server (SAP Web AS) provides the platform for the use of the WebDocuments application. The SAP Web AS utilizes a side-based programming model with server-sided scripting, similar to popular server page technology.

Business Server Pages (BSP) and MIME objects form the basis for document processing in the web interface. Access via the Internet is achieved using HTTP protocol. The exchange of different types of data over the Internet is controlled with Multipurpose Internet Mail Extensions (MIME) protocol.

Note Note

Business Server Pages are ready for document processing. You do not need to carry out any other activities.

End of the note.

Customizing (IMG) Document Management

You make the required system settings in Customizing for Document Management.

Global Settings

Document processing in the Web interface has been implemented as an additional feature. You therefore need to make the complete global settings for document management in Customizing for Document Management. You make these settings under the following structure nodes:

Control Data
Maintain general data

Note Note

Under these structure nodes you can choose to carry out the following activity:

Start Processing for Documents

This activity enables you to include enterprise-specific processes. You can carry out these processes from the Document Search result list, for example, to set a specific status. The profile ensures that a user may choose only from the processes relevant to their daily tasks.

End of the note.

Special Settings for WebDocuments

Special settings are required in addition to the global settings to enable processing in the Web interface. You make these settings in Customizing (IMG) for Document Management in the activity Define Document Type for Web Applications.

Carry out the following steps in this activity:

Activity	Setting
Define Document Type for Web Applications (obligatory)	You make settings to control the following processes: Processing original application files for a document type (original) Processing the data from the document info record (metadata)
Determine Sequence of Field Groups (obligatory)	You have to make the following decisions: From the dataset select the document type that is to be edited in the Web interface. Determine the sequence in which the dataset is to be presented in the Web interface.
Select Functions for Web Interface (optional)	You select the functions that can be used in the Web interface to prepare or process additional document information. See also: Integrating Enterprise-Specific Processes
Determine Application for Thumbnails (optional)	You determine a workstation application, which you use to display a preview (thumbnail) of a graphic file in the Web interface.

Note Note

You can get more information in the IMG of Document Management as you carry out individual substeps.

End of the note.

Features

The application logic of WebDocuments is identical to that of document management for mySAP Product Lifecycle Management (application component CA-DMS).

The following overview shows the BSP applications that you can call from the WebDocuments homepage.

BSP Application	Use
Finding Documents	For search criteria you can enter data from the document info record, class data, data from the linked object, or a character string from the original application file. You get a results list, from which you can edit the document that has been found.
Displaying and Changing Documents s	The data that you selected for a document type is displayed for the document info record (activity Display Sequence of Field Groups ). You can also maintain additional enterprise-specific data, or add an original application file. If you have defined a document type in such a way that additional functions for the Web interface are made available, then you could, for example, send a document to a recipient list (activity Define Document Type for Web Applications ).
Creating Documents	If you create original application files, you can import these into a central secure storage area (storage system).
Calling the Stack	The previous ten documents that you edited are displayed.

Example

As an engineer you have created a design drawing, which is to be integrated by mySAP Product Lifecycle Management in further processes.

You create a document info record for this design drawing on your Web interface.
After you have entered a German and English description, you also enter the enterprise-specific additional data, such as Drawing Format and Product Number.
You add your design drawing as an original application file (such as in CATIA format). You import this design drawing into the storage system for your engineering department.
After you have saved the document info record, you send the document to an employee in the area of engineering.

A converter is available in this area, which allows the employee to create an additional file for the design drawing in CompuServe (*.gif) format. This file format is used to display a preview image for the design file throughout the enterprise.

After conversion, the employee enters this file as an additional original application file, and checks it into the storage system. The employee sends the document to the team members who are on a standard recipient list.